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: dataguard logical standby issue

Mark Strickland

2007-03-19

Replies:
Edward, if you don't actually need DML and/or DDL for the SYSMAN schema propogated to the logical standby, then just set the schema to be skipped and it should be able to move past the statement(s) that are failing.  However, having said that, a few weeks ago, a few transactions for an already-set-to-skip schema caused SQL Apply to stop.   Both DDL and DML for this schema were set to be skipped and have been all along.  I ended up calling the skip procedure again for that schema and SQL Apply was then able to move on with its life.  The name of the object that your standby is choking on looks like something that is system-generated and, therefore, will probably be different in every database where the DDL is run to create it.  Also, you can call the skip_error or skip_transaction procedures or you can "alter database start logical standby apply skip failed transaction" as many times as it takes to get past the problem transactions.

BTW, I'm on 10.1.0.5, so whatever I recommend is based on my experiences with logical standby in that version.

Regards,
Mark Strickland
Seattle, WA