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: Help - Corrupted Block - Lob Segment - NOLOGGING

Mladen Gogala

2006-10-23

Replies:

On 10/23/2006 02:46:43 PM, Sam Bootsma wrote:

> Documents are stored in a BLOB column in an Oracle table. It is NOT
> stored "in_row" and logging is turned off (for performance reasons they
> told me).

The problem with "NOLOGGING" is the fact that your blocks are no longer protected
by logging mechanism, which means that you cannot recover them. That's excellent
for performance - until you have to recover. The general advice for nologging is to
to use it for things that can be easily re-created, like indexes or MV's.

>
> We recently encountered a bad block, and I have since determined there
> are additional bad blocks, but it is just one block that is continually
> giving us a problem.
>
> When a user attempts to check an object into the repository, they often
> get the error message:
>
> E03020003: Database Error: [CAI/PT][ODBC Oracle 8
> driver][Oracle]ORA-01578: ORACLE data block corrupted (file # 31, block
> # 123533)
> ORA-01110: data file 31: '/san1/oradata/PROD/harvestblob01.dbf'
> ORA-26040: Data block was loaded using the NOLOGGING option

It's either DBMS_REPAIR or your harvest has failed. Position of a DBA is comparable
to the position of a director of FEMA. It's a very comfortable position, until disaster
strikes.....May Bacchus, the god of harvest be with you.
--
Mladen Gogala
http://www.mladen-gogala.com

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