Re: ORA-16000: database open for read-only access

  • From: sumit Tyagi <dba.tyagisumit@xxxxxxxxx>
  • To: Kim Berg Hansen <kibeha@xxxxxxxxx>
  • Date: Thu, 5 Jun 2014 23:54:32 +0530

Dear all,

Thanks for the information . We are checking the java packages / methods
for invalidation . Most probably this is the issue . we are getting same
issue for some other packages also lets c:

**** 2014-06-05 11:45:54.036*

**** SESSION ID:(8.18551) 2014-06-05 11:45:54.036*

**** CLIENT ID:() 2014-06-05 11:45:54.036*

**** SERVICE NAME:(SYS$BACKGROUND) 2014-06-05 11:45:54.036*

**** MODULE NAME:(MMON_SLAVE) 2014-06-05 11:45:54.036*

**** ACTION NAME:(JAVAVM JIT slave action) 2014-06-05 11:45:54.036*



*joez_compile_method beginning compile of method
sun/security/pkcs/PKCS7.getContentInfo*

*Reading CompilerOptions...*



**** 2014-06-05 11:45:55.358*

*joxjitexe(1) caught: 16000; Aborting*

*joxjitexe(2) caught: 16000;*

*ORA-16000: database open for read-only access*




On Tue, Jun 3, 2014 at 7:34 PM, Kim Berg Hansen <kibeha@xxxxxxxxx> wrote:

> Hiya
>
> I would guess for some reason the method 
> java/security/spec/DSAParameterSpec.getQ
> has become invalidated on your primary database.
> Then when some code on your Active Data Guard standby tries to use this
> method, the database attempts an automatic recompilation, which is not
> allowed in the read-only standby database.
>
> We have had similar issues with views becoming invalid in primary, and
> thus in standby shortly after.
> See blogposts we wrote with example:
> http://dspsd.blogspot.dk/2013/09/active-data-guard-and-invalidations.html
>
> http://www.bluegecko.dk/oracle/challenges-with-object-invalidation-and-ora-04045-in-active-data-guard-standby-database/
>
> The only solution we could find was to manually recompile our views on the
> primary, so that the Active Data Guard standby would never have to attempt
> automatic recompilation/revalidation of invalid objects.
>
> I am not quite sure this can be the same issue with java stored
> procedures, but I would guess it could.
> Try checking for invalid java objects on the standby, and then recompile
> those objects on the primary (which then will be propagated in VALID state
> to the standby.)
>
>
>
> Regards
>
>
> Kim Berg Hansen
>
> http://dspsd.blogspot.com
> kibeha@xxxxxxxxx
> @kibeha
>
>
>
>
> On Sat, May 31, 2014 at 7:57 AM, sumit Tyagi <dba.tyagisumit@xxxxxxxxx>
> wrote:
>
>> Dear Experts , please help on the below ORA reported on the physical
>> standby ( ADG) oracle 11.2.0.3.0 .
>>
>>
>> *ALERT LOG ENTRY:*
>> Sat May 31 05:11:01 2014
>> Errors in file
>> /oracle/app/product/11.2.0/diag/rdbms/xxxxxxrpt/xxxxxx/trace/xxxxxx_
>> *m000_4524.trc:*
>> ORA-16000: database open for read-only access
>> Sat May 31 05:11:10 2014
>> Errors in file
>> /oracle/app/product/11.2.0/diag/rdbms/xxxxxxrpt/xxxxxx/trace/xxxxxx_
>> *m000_4557.trc:*
>> ORA-16000: database open for read-only access
>> Sat May 31 05:12:04 2014
>>
>> *TRACE FILE ENTRY:*
>> [oracle@reporting-srvr trace]$ cat
>> /oracle/app/product/11.2.0/diag/rdbms/xxxxxxrpt/xxxxxx/trace/xxxxxx_m000_4557.trc
>>
>> Trace file
>> /oracle/app/product/11.2.0/diag/rdbms/xxxxxxxx/xxxxxxx/trace/xxxxxxx_m000_4557.trc
>> Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit
>> Production
>> With the Partitioning, Automatic Storage Management, OLAP, Data Mining
>> and Real Application Testing options
>> ORACLE_HOME = /oracle/app/product/11.2.0/db_1
>> System name:    Linux
>> Node name:      reporting-srvr
>> Release:        2.6.18-238.el5
>> Version:        #1 SMP Sun Dec 19 14:22:44 EST 2010
>> Machine:        x86_64
>> Instance name: xxxxxx
>> Redo thread mounted by this instance: 1
>> Oracle process number: 42
>> Unix process pid: 4557, image: oracle@reporting-srvr (M000)
>>
>>
>> *** 2014-05-31 05:11:09.495
>> *** SESSION ID:(770.3233) 2014-05-31 05:11:09.496
>> *** CLIENT ID:() 2014-05-31 05:11:09.496
>> *** SERVICE NAME:(SYS$BACKGROUND) 2014-05-31 05:11:09.496
>> *** MODULE NAME:(MMON_SLAVE) 2014-05-31 05:11:09.496
>> *** ACTION NAME:(JAVAVM JIT slave action) 2014-05-31 05:11:09.496
>>
>> joez_compile_method beginning compile of method
>> java/security/spec/DSAParameterSpec.getQ
>> Reading CompilerOptions...
>>
>> *** 2014-05-31 05:11:10.832
>> joxjitexe(1) caught: 16000; Aborting
>> joxjitexe(2) caught: 16000;
>> ORA-16000: database open for read-only access
>>
>>
>> *--*
>> *BR*
>> *Sumit Tyagi*
>> *+91-7829543355*
>>
>
>


-- 

*--*
*BR*
*Sumit Tyagi*
*+91-7829543355*

Other related posts: