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: Standby database errors running Crystal reports

Mark W. Farnham

2006-11-15

Replies:
It's been a while since I've used Crystal, but if memory serves a client
control-C throws a gratuitous rollback.

I don't have a standby open in read only mode I can throw gratuitous
rollbacks at handy at the moment (and besides the result might be release
and patch specific).

On 10.1+ a rollback to a read only transaction for a "primary" database does
not throw that error, but I suspect that if you just open a session, set
transaction read only, and toss off a rollback on your open for read standby
you'll get the same error. If so, then it is a pretty benign overloading of
an error message. If not, I really would look for something else. I would
not ultimately rely on convincing people not to hit certain characters on
the keyboard; even if they cooperate in intent they can make mistakes. Still
asking them to cut it out in the meantime seems useful.

Regards,

mwf

-----Original Message-----
From: oracle-l-bounce@(protected)
Behalf Of DIANNA GIBBS
Sent: Wednesday, November 15, 2006 9:37 AM
To: oracle-l@(protected);
cerner_dbarchitecture@(protected)
Subject: Standby database errors running Crystal reports


We have Crystal running against a standby database. We've started seeing
these errors while developing new reports. We
believe it's when the developer aborts the process w/control c. I did open
an SR w/oracle and their best bet
was an ODBC connection error.

Has anyone else seen these errors? The database shuts down each night for
recovery and opens in read-only
each morning without any issues.   I do have a trigger that writes a trace
file anytime a connection is made from certain
servers using IP addresses. I thought this might be part of the problem.

Should I be concerned with any type of corruption or any comments/thoughts
would be appreciated?

My errors are:
ORA-00604: error occurred at recursive SQL level 1
ORA-01456: may not perform insert/delete/update operation inside a READ ONLY
transaction
ORA-06512: at line 27
ORA-12570: TNS:packet reader failure

Thanks.
Dianna G.


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



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