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: Database Connection Control

Michael Chan

2005-11-15

Replies:
I also implemented logon trigger to for audit purposes, and from trace files output and analysis from Oracle support,  the problem was triggered before the logon trigger was fired.
 
Trace file extract :-
==================================
The statment is the same in all trace files
SELECT VALUE FROM NLS_INSTANCE_PARAMETERS WHERE PARAMETER ='NLS_DATE_FORMAT'

The error is a NLS date issue that can be caused by the jdbc version.
 
[$Revision: 92453]
8000000100000010 2D303720 6C696E6B 65722063 6F6D6D61 [-07 linker comma]
8000000100000020 6E642073 3830302E 73677320 63727430 [nd s800.sgs crt0]
8000000100000030 2E6F2042 2E31312E 34332050 424F2030 [.o B.11.43 PBO 0]
8000000100000040 35303132 34202400 63727430 3A206E75 [50124 $.crt0: nu]
8000000100000050 6D626572 20746F6F 206C6172 67652000 [mber too large .]
 
=> Logon trigger code followed.....
============================
 
Cheers,
 
Michael Chan

 
On 11/15/05, Radoulov, Dimitre <cichomitiko@gmail.com> wrote:
>>> use logon triggers and see if you can spot then in module from v$session
 
As far as I know the v$session.module column is populated after a logon trigger is fired, so this is not possible.
 
 
 
Cheers,
Dimitre Radoulov