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

Lost one in Migration

Kline.Michael

2005-04-28

Replies:
HPUX
Going from 8.1.7.4 to 9.2.0.4.
I and another DBA have just about exhausted our things to try.

I had a compatible='9.2.0' in the init.ora for the 9i migration. You
can't do this, but must set it AFTER the migration. I had obtained a
copy of the init.ora from a working Version 9 and went over the lines
one by one comparing them to "PFTST" to make the version 9 init.ora.

Now I get the stuff below. I've tried using:
_allow_resetlogs_corruption=TRUE
EVENT = "10619 trace name context forever, level 1"
Both of which were mentioned as ways to get around the problem.

You would think they'd test for that "invalid at this point" setting.

I've saved off the export, just in case.

The log gives me this:

alter database open resetlogs
Thu Apr 28 11:37:45 2005
RESETLOGS is being done without consistancy checks. This may result
in a corrupted database. The database should be recreated.
RESETLOGS after incomplete recovery UNTIL CHANGE 1670398987
Resetting resetlogs activation ID 3053850856 (0xb60610e8)
Thu Apr 28 11:41:26 2005
Errors in file /u001/app/oracle/admin/PFTST/udump/pftst_ora_12463.trc:
ORA-00600: internal error code, arguments: [2765], [9.2.0.0.0], [], [],
[], [], [], []
ORA-600 signalled during: alter database open resetlogs...
Thu Apr 28 11:42:47 2005
Shutting down instance: further logons disabled
Shutting down instance (immediate)
License high water mark = 2
Thu Apr 28 11:42:47 2005
ALTER DATABASE CLOSE NORMAL
ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
Thu Apr 28 11:42:47 2005
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archiving is disabled
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archiving is disabled
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active

SQL> startup mount
ORACLE instance started.

Total System Global Area 2158983784 bytes
Fixed Size             739944 bytes
Variable Size        1610612736 bytes
Database Buffers       536870912 bytes
Redo Buffers          10760192 bytes
Database mounted.
SQL> alter database open
2 /
alter database open
*
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open


SQL> alter database open noresetlogs;
alter database open noresetlogs
*
ERROR at line 1:
ORA-01588: must use RESETLOGS option for database open


SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-00600: internal error code, arguments: [2765], [9.2.0.0.0], [], [],
[], [], [], []


SQL> shutdown immediate;
ORA-01109: database not open

Database dismounted.
ORACLE instance shut down.
SQL> exit


Michael Kline
Database Administration
SunTrust Technology Center
1030 Wilmer Avenue
Richmond, Virginia 23227
Outside 804.261.9446
STNet 643.9446
Cell 804.744.1545
michael.kline@(protected)
************************************************
The information transmitted is intended solely
for the individual or entity to which it is
addressed and may contain confidential and/or
privileged material. Any review, retransmission,
dissemination or other use of or taking action
in reliance upon this information by persons or
entities other than the intended recipient is
prohibited. If you have received this email in
error please contact the sender and delete the
material from any computer. [ST:A234]
************************************************


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