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.
Behalf Of DIANNA GIBBS
Sent: Wednesday, November 15, 2006 9:37 AM
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 1ORA-01456
: may not perform insert/delete/update operation inside a READ ONLY
: at line 27ORA-12570
: TNS:packet reader failure