.ora-code.com

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
10.1.0.4 patchset 2 catcpu.sql slop

10.1.0.4 patchset 2 catcpu.sql slop

2005-06-28       - By Paul Drake
Reply:     1     2     3     4     5     6  

w2k3 server std ed, 32 bit.
Oracle 10g R1, 10.1.0 patchset 3 applied (10.1.0.4)

While running the 10.1.0.4 patchset 2 post-installation script
(catcpu.sql) against a newly created database there were a rather
large amount of ORA-00955 (See ORA-00955.ora-code.com) (457) and ORA-02303 (See ORA-02303.ora-code.com) (63) errors.

These can sometimes be ignored, but basically, this means having to
compare the previous definitions of the objects against the new
definition on a line by line basis in order to determine if in fact
the object definition has changed. This is a huge waste of time, IMHO.

I was thinking of rather than taking that approach, of manually
dropping all of these objects prior to re-running catcpu.sql and
examining the results (HUGE hammer approach).

this is in testing in a db with no users.

yeah, I could just ignore the patchset and stick with 10.1.0.4 patchset 1.
we've hit an issue covered by 10.1.0.4 patchset 2 so I'd rather get
the bugfix out there than wait for the next iteration.

just trolling for some thoughts before I vent into an iTAR.

Paul
--
http://www.freelists.org/webpage/oracle-l