RE: Weird read-only error Solaris 10, 10.2.0.2
- From: "Newman, Christopher" <cjnewman@xxxxxxxxxxxxx>
- To: <paul.baumgartel@xxxxxxxxxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Fri, 9 Oct 2009 12:09:14 -0500
Hi Paul,
In this case it was exactly as Yong described; several columns were
added to the table on which the synonym pointed to.
- Chris
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Baumgartel, Paul
Sent: Friday, October 09, 2009 12:01 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: RE: Weird read-only error Solaris 10, 10.2.0.2
What kind of change was made to the object to which the synonym refers?
Paul Baumgartel
CREDIT SUISSE
Information Technology
Prime Services Databases Americas
One Madison Avenue
New York, NY 10010
USA
Phone 212.538.1143
paul.baumgartel@xxxxxxxxxxxxxxxxx
www.credit-suisse.com
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Yong Huang
Sent: Friday, October 09, 2009 12:58 PM
To: oracle-l@xxxxxxxxxxxxx
Cc: cjnewman@xxxxxxxxxxxxx
Subject: Re: Weird read-only error Solaris 10, 10.2.0.2
> We have a daily clone that we open in read-only mode. User reports
the
> following error:
>
> select * from t_sap_cd
>
> ORA-00604: error occurred at recursive SQL level 1
>
> ORA-16000: database open for read-only access
With some private emails, Chris told me what happened and I think it's
interesting to everybody. The database is open read only. But the status
of the synonym is still invalid (beginning with 10g, a synonym can
become
invalid), due to an earlier specification change of the object the
synonym
points at. When you later use the synonym, as in select * from
this_synonym or even desc this_synonym, the status must be changed to
valid because the translated object perfectly exists. But because the
database is read only, its status in the system tablespace is frozen,
hence the error.
If I were at it, I would probably alter session to enable SQL trace (not
set autotrace on) and systematically troubleshoot the issue, unless I
already thought of it. The trace file should have "err=16000" in it.
Yong Huang
--
//www.freelists.org/webpage/oracle-l
========================================================================
=======
Please access the attached hyperlink for an important electronic
communications disclaimer:
http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
========================================================================
=======
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
