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

[suse-oracle] SLES10 - network failure on DataGuard log streams

Alexei_Roudnev

2007-07-02

Replies:
Some time ago I found a strange problem with Oracle @ SLES10 (used SP1 beta
those time).
- Under a heavy load;
- With Oracle Data Guard configured;
- Primary database reported Async IO error on archive logs stream, and so
lost syncronization with standby
database (can't ship logs anymore);
- It recovered in time, because of FAL feature of the DataGuard (standby
pull absent logs and syncronize);

Configuration used SLES10 on one side and UL4.4 on another side, and problem
occur only when primary DB was on SLES10.

Now I retested the same configuration with 2 x SLES9 SP3 servers, and
everything works fine.

So I can conclude, that there is a bug in Oracle implementation on Linux
SLES10 (or in SLES10 related to the network IO, or
in Oracle sysctl setting for SLES10 - have not time to investigate).

Did anyone seen anything like this on SLES10?


--
To unsubscribe, email: suse-oracle-unsubscribe@(protected)
For additional commands, email: suse-oracle-help@(protected)
Please see http://www.suse.com/oracle/ before posting