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: corrupt datafile

Terry Sutton

2004-06-15

Replies:
Hi Mark,

We're trying some experimentation with underscore parameters. Not sure if
it'll work out. I tried BBED, but all I could get was "BBED-00400: invalid
blocktype (00)". I'd be interested in bp, but I don't know anything about
it. And we're trying the other options. Except the $$$$$ one- the client
isn't willing to spend money, which is how they got into this situation in
the first place.

Stale data is not a concern. If we can get day old data, the client would
be ecstatic.

Thanks,

--Terry

> if that outdated file is really all you've got, then you *might* be able
to:
>
> 1) cycle off your current undo and make a new one. (Unless you want it to
> try to roll back incomplete transactions. I'm not sure whether the
_corrupt
> undo and rollback inits are still operative.)
> 2) use od or that cool block dumper Steve Adams uses in his classes to
look
> at the headers
> 3) use bp to patch the headers to make the file look current (dump the
> headers of a few current "good" tablespaces to give you a clue, and/or
plead
> for mercy from someone who knows the block header details intimately
($$$$$
> usually can provide mercy).
> 4) turn on the event that keeps scanning after hitting corrupt blocks, and
> turn off block checking
> 5) give it a whirl and unload or export a table at a time.
>
> Of course your data will be stale and relational integrity will likely be
> screwed up unless there really was no action on the tablespace.
>
> So understand that unless that tablespace actually was cold and you get no
> block errors logged, then your data will not be perfect. Depending on
> whether you have parallel logical logs (non-Oracle application logs or
> something like that) from which you can replay the subsequent
transactions,
> you may be able to get most or all of what you need.

----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@(protected)
put 'unsubscribe' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------