Links
• Home
• 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
Capture SQL stmt from ORA-54

Capture SQL stmt from ORA-54

2005-07-03       - By Connor McDonald

Reply:     1     2     3  

Check the application developers guide for "system events" in
triggers.  It lists some pre-defined "attribute function" calls that
return all sorts of useful attributes.

hth
connor

On 7/3/05, Herring Dave - dherri <Dave.Herring@(protected)> wrote:
>  
>  
>
> Is there any way to capture the SQL statement that generates an ORA-54 (See ORA-54.ora-code.com)?
> I've got a trigger set on my database to capture all possible ORA- errors,
> but for ORA-54 (See ORA-54.ora-code.com) errors, only the USERNAME, OSUSER, and PROGRAM get captured.
> I'm running on Oracle 9.2.0.4 on Tru64 5.1.  Any help would be appreciated.
>


--
Connor McDonald
===========================
email: connor_mcdonald@(protected)
web:   http://www.oracledba.co.uk

"Semper in excremento, sole profundum qui variat"
--
http://www.freelists.org/webpage/oracle-l