.ora-code.com

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
8.1.7 connection problems

8.1.7 connection problems

2005-10-30       - By Stephan Eichenlaub
Reply:     1     2     3  

Paul,

thanks for your advice. Gotta admit that I'm a bit surprised as at least
for 8.1.7 Oracle documentation recommends cold backups whereever
possible. Doing that both as physical backup of the datafiles and as export.

As additional security measure I've set up a standby database that runs
with a time lag and performs daily (scripted) manual recovery from the
archivelogs in the morning before business starts. For 8.1.7 that means
without doing it without rman as rman only learned that feature (time
lag and recovery at a certain time) with Oracle 9.

What I'll do for now is changing the nightly maintenance schedule from
simply time based to time based plus error conditions plus parallelizing
as much as possible to reduce database downtime.

Could you elaborate why you consider cold backups a real pain?

Stephan.

Paul Drake wrote:

>Ah. So one possible solution is, have them stop performing offline backups.
>
>Their options would be:
>
>hot physical backups
>rman backups
>
>IMHO, cold backups are a real pain.
>  
>


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