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
System tablespace corrupted

System tablespace corrupted

2004-07-29       - By Tanel Poder
Reply:     1     2     3     4     5     6     7     8  

> But dbv still gives the error pointing to one block as corrupt page 223 is
> influx most likely Media corrupt and page 224 is marked corrupt.

Influx doesn 't mean corrupt, you are dbv 'ing an online file? In 9i, when
dbverify finds a block that is inconsistent, it reads it again - if the
block has changed, then dbv determines this block as in flux (being written
at same time dbv reads it). Dbverify probably retries a few times to try to
get the consistent image before marking the block as influx.

To which segment do those blocks belong to? Perhaps AUD$ or FGA_LOG$?

> Should I restore it from cold backup to get rid off this error?

If you got RMAN backups you could do block level recovery for your corrupt
block if you don 't have much downtime allowance. If you do, then just
restore the file from backup, then verify whether the restored file is ok
with dbv, if it is then shutdown, replace the file, recover and open up your
db again.

Tanel.


-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
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
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --