AD_APPLIED_PATCHES

Links

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

AD_APPLIED_PATCHES

AD_APPLIED_PATCHES

2004-06-04 - By Jared.Still@(protected)

Reply: 1 2 3 4 5 6 7 8 9 10 >>

> Mike,
>
> God I love auditors! LOL.
>

We had PWC auditing us a couple years ago. They had some rather
vague questions about the DB, so I had to help them define their
requirements.

I then wrote a script to supply everything they wanted.

The following year, they were back, but this time they had a
script for me to run. Guess which script it was. ;)

My boss wanted them to pay us for using it, as they were sure
to be using it elsewhere.

The year after that, the same auditor asked about database access.

To make a long story short, I informed him that I could access
any data I wanted, I didn 't have to tell him about it, and there
was very little he could do about it.

His reply, "But you wouldn 't do that, would you? "

Well, no. But the point was I could. Funny response from an auditor.

Jared

 <tt >> Mike, </tt > 
 <tt >> </tt > 
 <tt >> God I love auditors! LOL. </tt > 
 <tt >> </tt > 
 
 <tt >We had PWC auditing us a couple years ago. They
had some rather </tt > 
 <tt >vague questions about the DB, so I had to help them
define their </tt > 
 <tt >requirements. </tt > 
 
 <tt >I then wrote a script to supply everything they wanted.
</tt > 
 
 <tt >The following year, they were back, but this time
they had a </tt > 
 <tt >script for me to run. Guess which script it
was. ;) </tt > 
 
 <tt >My boss wanted them to pay us for using it, as they
were sure </tt > 
 <tt >to be using it elsewhere. </tt > 
 
 <tt >The year after that, the same auditor asked about
database access. </tt > 
 
 <tt >To make a long story short, I informed him that I
could access </tt > 
 <tt >any data I wanted, I didn 't have to tell him about
it, and there </tt > 
 <tt >was very little he could do about it. </tt > 
 
 <tt >His reply, "But you wouldn 't do that, would you?" </tt > 
 
 <tt >Well, no. But the point was I could. Funny
response from an auditor. </tt > 
 
 <tt >Jared </tt >