Home
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: How to find out the original SQL resulted the ERROR message?

chao zhu

2005-10-05

Replies:
Hi, Dick
    Your theory is right and I am aware of it. But it does not help.
    Unfortunately, in our case, mostly it is database very active, and one SQL execute too long. SQL is sometimes iin-efficient and it timed out with 1555. I need to find out the original SQL and contact PD for a solution.
 
 
On 10/5/05, Goulet, Dick <DGoulet@vicr.com> wrote:
You've found the statement that errored out in the alert log.  The reason is one of two things that you now need to figure out.  The first is the infamous commit across a cursor problem which can be found from a review of the application code.  The other is a resource issue that you may or may not be able to solve.  The query in question start out life with a particular SCN.  Over the time of it's execution data under it was changed and those changes committed.  Now normally your UNDO or ROLLBACK segments will retain the changes so that Oracle can reconstruct what those rows looked like for this query.  The problem is that those undo or rollback segments are no longer available.  Now commits across a cursor do this because you yourself have released the data and according to the ANSI Sql standard you should close & reopen the cursor.  The other half of it is either a lack of undo or rollback space on your database or a query that just takes way too long to run.



--
Regards
Zhu Chao
www.cnoug.org