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
Q: Filesystem choice for log_archive_dest

Q: Filesystem choice for log_archive_dest

2005-06-23       - By Kevin Closson

Reply:     1     2     3     4     5     6     7     8     9     10     >>  

 
>   As long as your archiver processes are able to keep up with the
log file switches, it doesn't matter what type of filesystem they're on.


I disagree. One should consider the memory load of spooling
logs to a buffered filesytem.  I'd recommend spooling them
to a direct IO locale so you don't load down memory with
a bunch of filesystem blocks of archived logs...just a waste
of both processor cycles (lots of kernel sice memcpy) and
memory capacity.

If this is RAC, you better put the archived logs someplace that
other nodes can see them...and while you're at it, make
sure you acatually *need* RAC...

but, oh, wait, we don't need filesystems anymore. I forgot
--
http://www.freelists.org/webpage/oracle-l