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: A tale of data dictionary corruption in Oracle10gR2

Mark W. Farnham


One more thing. In addition to using the subdirectory structure count thing,
you might consider the "do the whole database" thing. That is done in a "not
really available" UPGRADE mode, so not nearly as many catch-22 situations
are possible. As a fraction of APPS' routines, the rest is pretty trivial.

-----Original Message-----
From: oracle-l-bounce@(protected)]
On Behalf Of Mark W. Farnham
Sent: Friday, October 06, 2006 9:49 AM
To: Amir.Hameed@(protected)
Subject: RE: A tale of data dictionary corruption in Oracle10gR2

First, since I'm usually pretty sure about APPS stuff and I am definitely
guessing here, I want to make sure everyone knows this is just a guess. I'm
not using compiled PL/SQL with APPS anywhere yet.

Have you tried compiling schema in this order:


My guess is based on the quite possibly misguided notion that one of the
storage management procedures is forced to recompile under the chain of
events from recompiling APPS, and that it is not functioning at the time it
is trying to be recompiled and some place in the code is retrying forever
instead of telling you what is really wrong.

If I'm even in the right ballpark, you might work around this by
pre-allocation of extents to the relevant tables (and clusters) in the SYS
schema if the order of compilation thing doesn't work.

The other big deal is that 30,000+ probably trashes your file system inode
structure pretty badly, so you're going to want to set up the multiple
subdirectory thingy as described in the very fine manual. If I recall
correctly, Oracle tells you to do this if you're over 10K or 15K entries.
I'd probably do it much smaller than that.

Good luck.


-----Original Message-----
From: oracle-l-bounce@(protected)]
On Behalf Of Hameed, Amir
Sent: Friday, October 06, 2006 8:41 AM
To: oracle-l@(protected)
Subject: A tale of data dictionary corruption in Oracle10gR2

I just wanted to share some information with this list on a corruption
scenario that I have recently experienced in my lab environment. I
recently upgraded an Oracle applications 11.5.9 database from version to version (64-bit) on Solaris9. The upgrade
went fine. While testing the new plsql setting where the plsql code can
be natively compiled, I ran into some issues that eventually corrupted
the data dictionary. This is what happened:

1. The plsql_code_type parameter was set to "native". The goal was to
natively generate the plsql code of the APPS schema. A very brief
description of the APPS schema (for those who do not know what the APPS
schema is) is that this schema owns all the standard PLSQL code in the
11i applications and the count of the combined
packages/procedures/triggers/functions is in thousands. In my
environment, the count was 34,647

2. Because in order to natively generate the PLSQL code, the code needs
to be re-compiled. The option that I used was to execute procedure
dbms_utility.compile_schema for the APPS schema as shown below:

The caveat of running this procedure is that it compiles everything
(unconditionally) including the views.

3. This procedure first invalidated all the plsql code as well as views.
It then started to compile them but the compilation process was very
slow and after approximately 16 hours, I checked and the invalid-count
showed that it was almost half way done. I decided to terminated the
process so I issued the "startup force" command. The instance got
terminated but then would not start in NORMAL mode and kept returning
ORA-0600 error as shown below:
 ORA-00600: internal error code, arguments:
[kksfbc-reparse-infinite-loop], [0xFFFFFFFF7A7F62F0], [], [], [], [],
[], []
I was able to start the instance only in the RESTRICT mode

4. At this point there were a lot of invalid packages owned by SYS;
which was not the case when I had started the compilation of APPS code

5. I tried to re-compile the INVALID packages owned by SYS manually via
SQLPLUS but I started to get the same ORA-0600 error

6. I opened a TAR. The analyst suggested running the catproc.sql script
which I did but it did not help and the script errored out with message:
   ERROR at line 1:
   ORA-04045: errors during recompilation/revalidation of
   ORA-00942: table or view does not exist
   ORA-00942: table or view does not exist
   ORA-00942: table or view does not exist
   ORA-00942: table or view does not exist
 I tried to also manually re-compile this package but got the
same error

7. Oracle has concluded that because I forcefully disrupted the
compilation process, some of the timestamps in the dictionary dependency
tree have gone out of synch and that the dictionary is now corrupted.
They are suggesting that I re-run the upgrade, which I can but they have
not been able to provide me the answer on how to natively compile the
PLSQL code in a relatively quick time because we have mission critical
systems and if the only way to compile PLSQL is via the compile_schema
procedure then based upon the test timing, it is not feasible

Does anyone has any suggestions/comments on this?