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
Re: Red Hat 2.1, Oracle 9.2.0.5 and 25GB file block corruption on
   HP

Re: Red Hat 2.1, Oracle 9.2.0.5 and 25GB file block corruption on
   HP

2005-01-27       - By Tim Gorman


April,

After all, EXP will drop dead on only the first corrupt block within the
high-water mark of tables;  it won't check indexes.

Some better alternatives:

1) If error messages (or the trace files accompanying the ORA-00600 (See ORA-00600.ora-code.com))
displayed actual block addresses (either FILE#/BLOCK# or DBA), then you can
use the DBMS_REPAIR.CHECK_OBJECT procedure to verify, after obtaining the
name of the segment by querying DBA_EXTENTS...

2) ALTER SYSTEM DUMP DATAFILE [ file-id | 'file-name' ] [ BLOCK block-id |
BLOCK MIN min-block-id BLOCK MAX max-block-id ] can help as well?  It
produces a trace file in the USER_DUMP_DEST, and usually if the block is
corrupted, the dump will say exactly that...

3) RMAN "backup validate" command performs a "false backup" (i.e. just reads
datafiles, doesn't write to backup media).  This is the "EXP FULL=Y
FILE=/dev/null" command done the right way...

Hope this helps...

-Tim


on 1/27/05 3:04 PM, aj wells at awellsdba@(protected) wrote:

> Okay... not that that is out of the way...
>
> We have a multi TB databae (one of several) that has many 25GB files
> (since it seems that is the biggest file we can make... ) and we have
> several file systems.  "we" just created two new file systems that are
> 600+ GB each across several disks (0+1).
>
> When we allocated new files on the first of these file systems, we got
> block corruption... (ORA-00600 (See ORA-00600.ora-code.com): INTERNAL ERROR CODE, ARGUMENTS:
> [25012], [27]) on several of the files.
>
> HP says not hardware, RH says either Oracle or Hardware and Oracle
> says it is OS or hardware.
>
> Anyone else seen anything vaguely resembling this... it is becoming a
> big giant Charlie Foxtrot and no one is of much help (although Oracle
> did have us start an export 13 hours ago on the tablespace and it is
> now nearly half done... that will tell us if the two extents in the
> only file left showing corruption is actually corrupt or only
> pretending to be... )
>
> thanks
> aj
> --
> http://www.freelists.org/webpage/oracle-l
>

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