All Oracle Error Codes
Oracle DBA Forum

Frequent Oracle Errors

TNS:could not resolve the connect identifier specified
Backtrace message unwound by exceptions
invalid identifier
PL/SQL compilation error
internal error
missing expression
table or view does not exist
end-of-file on communication channel
TNS:listener unknown in connect descriptor
insufficient privileges
PL/SQL: numeric or value error string
TNS:protocol adapter error
ORACLE not available
target host or object does not exist
invalid number
unable to allocate string bytes of shared memory
resource busy and acquire with NOWAIT specified
error occurred at recursive SQL level string
ORACLE initialization or shutdown in progress
archiver error. Connect internal only, until freed
snapshot too old
unable to extend temp segment by string in tablespace
Credential retrieval failed
missing or invalid option
invalid username/password; logon denied
unable to create INITIAL extent for segment
out of process memory when trying to allocate string bytes
shared memory realm does not exist
cannot insert NULL
TNS:unable to connect to destination
remote database not found ora-02019
exception encountered: core dump
inconsistent datatypes
no data found
TNS:operation timed out
PL/SQL: could not find program
existing state of packages has been discarded
maximum number of processes exceeded
error signaled in parallel query server
ORACLE instance terminated. Disconnection forced
TNS:packet writer failure
see ORA-12699
missing right parenthesis
name is already used by an existing object
cannot identify/lock data file
invalid file operation
quoted string not properly terminated

RE: Cursor_sharing=similar.....failed

Bryan Michael Lenihan





I do not know if this what you are encountering, but by the nature of the CURSOR_SHARING=SIMULAR several child parses are created based on the literal values.  There are several metalink and blog messages out there about the treeing effect when using CURSOR_SHARING as SIMULAR.   We are running and we had to apply a couple of patches for SIMULAR and FORCED. 


From what I understand – SIMULAR checks the literal values and see if the plan changes based on their values.  If it does, then it stores the plan as a child plan and creates a small tree in the shared pool.  If the statement is run enough the treeing effect can take up a large amount of memory.  We actually saw this pattern as you are describing.  I felt it was because of the traffic – test usually does not have the user load as a production database.




From: oracle-l-bounce@freelists.org [mailto:oracle-l-bounce@freelists.org] On Behalf Of daniel.hubler@aurora.org
Sent: Tuesday, August 07, 2007 10:13 AM
To: oracle-l@freelists.org
Subject: Cursor_sharing=similar.....failed


Looking for ideas/comments/suggestions..........

We changed cursor_sharing from EXACT to SIMILAR last Saturday morning at 6am.
Did that via an "ALTER SESSION SET....." command.
The environment is large (7TB) but not very busy on Saturday morning.
We had cursor_sharing=similar in multiple test environments, for many months without issue.

At 9:15am, we started to generated ora-04031 errors.
By 9:30am, we could no longer sign-on.
We ended up shutting down the middle-tier, and deleting all of the
OS processes on the DB server, that represented connections to the instance.
At that point, we were able to signon, backout the change, and startup the middle-tier again.

In the alert log, we saw the ora-04031 errors, and also many (thousands) of messages saying
"PMON failed to acquire latch, see PMON dump".

The PMON trace file show the same entry, repeated thousands of times:
"PMON unable to acquire latch 2c4cb108 library cache
  possible holder pid = 1000 ospid=42586708"

Any ideas on what happened would be appreciated.

Dan Hubler
Database Administrator
Aurora Healthcare