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: 9205 to 9206

david hill


With 9206 on RHEL 3 you need


Patch 3238244 - fix your agent
Patch 3208258 - for you Asynch IO

You could always check out docid 283899.1 for known issues

-----Original Message-----
From: oracle-l-bounce@(protected)
Sent: Wednesday, August 17, 2005 10:40 AM
To: oracle list
Subject: Re: 9205 to 9206

Two positive notes:
1. It seemed to fix some CBO issues that we had been experiencing (we
were on with core patch, and that version seemed far
more prone to choosing ridiculous execution paths than when we were on
"pure" or
2. It eliminated a RAC-specific ORA-600 bug in one of our more
database-intensive batch processes.

Two bugs noted:
1. If you have a view that is SELECT ROWID, * from some_table, you
can no longer INSERT into such a view on
2. One of our other teams found a new bug with database links (I'm
sorry I don't recall the details).

There was also a third bug that caused an instance shutdown when the
host machine was heavily utilized. Apparently this was a known bug
and fixed in It has only happened to us once in 2 months but
it is enough to make us paranoid about machine loads...


On 8/17/05, Loughmiller, Greg <greg.loughmiller@(protected):
> Seems to be stable.. Fixed a few of the 9205 perf issues as well as
> streams issues.. And finally, you can avoid using any one off patches
if you
> are in a RAC environment with 9206. So far, early testing on 9206/RAC
> all is well
> ________________________________
> From: raja rao [mailto:raja4list@(protected)]
> Sent: Tuesday, August 16, 2005 2:43 PM
> To: oracle list
> Subject: 9205 to 9206
> Hi All,
> we are planning to migrate from 9205 to 9206 (oracle apps 11.5.10).
> is 9206 stable compare with 9205 ?
> anybody encountered any issues ?
> Thanks,
> Raj
> ________________________________
> Start your day with Yahoo! - make it your home page

This message contains confidential information intended only for the use of
the individual or entity named as recipient. Any dissemination, distribution
or copying of this communication by anyone other than the intended recipient
is strictly prohibited. If you have received this message in error, please
immediately notify us and delete your copy. Thank you.

Les informations contenues aux pr?sentes sont de nature privil?gi?e et
confidentielle. Elles ne peuvent ?tre utilis?es que par la personne ou
l'entit? dont le nom para?t comme destinataire. Si le lecteur du pr?sent
message n'est pas le destinataire pr?vu, il est par les pr?sentes pri? de
noter qu'il est strictement interdit de divulguer, de distribuer ou de
copier ce message. Si ce message vous a ?t? transmis par m?garde, veuillez
nous en aviser imm?diatement et supprimer votre copie. Merci.