Re: Ignore RE: Weird read-only error Solaris 10, 10.2.0.2
- From: Gerwin Hendriksen <gerwin.hendriksen@xxxxxxxxx>
- To: cjnewman@xxxxxxxxxxxxx
- Date: Fri, 9 Oct 2009 08:25:25 +0200
Hi Chris,
The described observance is very strange. Can you first give some more
information like the following:
1.) select * from dba_segments where segment_name = 'T_SAP_CD';
* Just to make sure there is just one table and not more.
2) select * from dba_objects where object_name = 'T_SAP_CD'
3) can you reproduce the issue ?
4) how is the clone exactly made ?
With kind regards,
Gerwin
2009/10/7 Newman, Christopher <cjnewman@xxxxxxxxxxxxx>:
> Synonym went invalid for some reason. Good to go now.
>
>
>
> From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
> On Behalf Of Newman, Christopher
> Sent: Wednesday, October 07, 2009 10:32 AM
> To: oracle-l@xxxxxxxxxxxxx
> Subject: 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
>
> When fully qualifying the table name, ie sales.t_sap_cd, the query works.
> I’ve checked the synonyms and they look to be OK. The only clue here is
> that there was DDL executed against the primary last night before the clone
> was created. Other tables in the same schema can be queried without fully
> qualifying without issue. Anyone see this behavior before?
>
> Thanks- Chris
--
//www.freelists.org/webpage/oracle-l
Other related posts:
