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: REDO LOG Concepts

DBA Deepak


Hi Alexander,
I do not think UNIX removes the directory entry immediately. Otherwise how would it access the REDO logs by their paths.
What might be happening is UNIX is marking it as deleted (may be using a flag or so). Please do correct me if am wrong.

On 5/17/07, Alexander Fatkulin <afatkulin@gmail.com> wrote:

As others have already pointed out - you actually didn't delete
anything. You just unlinked a directory entry in a file system. File
is still "there" and is open by the LGWR.

Shutdown immediate is a clean shutdown (no instance recovery is
required after it).

On 5/17/07, DBA Deepak < oracle.tutorials@gmail.com> wrote:
> Hi All,
> As we know when we issue a COMMIT the log buffer content is flushed to the
> online redo log file before the "Commit complete" status is returned to the
> user. Please correct me if I am wrong.
> I have the following scenario...
> SQL> select member from v$logfile;
> --------------------------------------------------------------------------------
> /u04/oradata/BIDWDB01/redo03.log
> /u04/oradata/BIDWDB01/redo02.log
>  /u04/oradata/BIDWDB01/redo01.log
> SQL> !rm /u04/oradata/BIDWDB01/redo01.log
> SQL> !rm /u04/oradata/BIDWDB01/redo02.log
> SQL> !rm /u04/oradata/BIDWDB01/redo03.log
> SQL> connect scott/oracle
> Connected.
> SQL> update emp set ename=ename;
> 14 rows updated.
> SQL> commit;
> Commit complete.
> SQL> commit;
> Commit complete.
> SQL> conn / as sysdba
> Connected.
> SQL> shutdown immediate
> Database closed.
> Database dismounted.
> ORACLE instance shut down.
> SQL> startup
> ORACLE instance started.
> Total System Global Area 4479516672 bytes
> Fixed Size            1984504 bytes
> Variable Size        905975816 bytes
> Database Buffers      3556769792 bytes
> Redo Buffers          14786560 bytes
> Database mounted.
> ORA-00313: open failed for members of log group 1 of thread 1
> ORA-00312: online log 1 thread 1:
> '/u04/oradata/BIDWDB01/redo01.log'
> -----------------------
> My question is even after deleting all the online redo log files how did
> Oracle returned the Commit complete status to the user? What happened to the
> log buffer data flush?
> I am using on Solaris 9 (64-bit)
> Regards,
> Deepak

Alexander Fatkulin


Oracle DBA