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: [suse-oracle] Strange error on log transport / data guard, SLES10

McAllister, Andrew

2007-04-17

Replies:
We've had an open TAR on a corrupt archive logs on dataguard issue with
Oracle for two years. The last update to the TAR just a week ago said
that Oracle development could reproduce and solve the problem by setting
filesystemio_options = setall or directio instead of asynch. Only
problem with that is you must create ALL of your original data files
with directio in the first place, so we are stuck.

The problems we see are much more subtle, just a message about a corrupt
log on the standby. The standby eventually recovers, but the result is
that many archive logs must be shipped to the standby multiple times.
That just makes things worse and slower. At one point we could reproduce
on test equipment 100% of the time. We were clobbered with this issue
after an SLES8 kernel upgrade and an Oracle upgrade so we stopped
upgrading.

We have given up trying to solve the issue and we'll stick with what
we've got until our next hardware refresh as we have reached an
"understanding" with our hardware and software combinations. Sad really.

Best of luck solving this issue.

Andy

> -----Original Message-----
> From: Alexei_Roudnev [mailto:Alexei_Roudnev@(protected)]
> Sent: Monday, April 16, 2007 10:25 PM
> To: suse-oracle@(protected)
> Cc: Arun Singh
> Subject: Re: [suse-oracle] Strange error on log transport /
> data guard, SLES10
>
> I tested connection - works pretty well, FTP speed is
> 35MB/second in both
> directions (then limited by the File System).
>
> It can be UL4.4 problem (on receiving side), but it looks
> more likely as
> Async IO problem in SLES10 - Oracle 10.2.0.3 uses
> async io when sending logs in SYNC mode (I run MAx
> Availiability mode + Fast
> Failover in the lab), and somethinh runs out of the limits.
>
> Will retest on SLES9 <->SLES9 in a short time.
>
snip

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