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

Re: Identifying the content of a corrupted block in system
tablespace

Mladen Gogala

2005-01-06

Replies:

On 01/06/2005 09:23:33 PM, Vlado Barun wrote:

> BTW, this is 8.0.6, they identified this problem 3 months ago in =20
> their
> Peoplesoft application, and of course they don't have a good backup
> from
> which to recover...

They can try restarting and hope that the corruption is only in =20
software. If it isn't and given that it is a dictionary table that is =20
corrupt, they cannot really trust DBMS_REPAIR, even if they had it, =20
which they do not, because of the version. That leaves recovery as the =20
only option. If they don't have any backups, they are, and this is a =20
scientific term, royally screwed. The best solution for them is to rent
the movie "Deliverance" and start squealing....

--=20
Mladen Gogala
Oracle DBA


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