 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
| HomeDiscussion Groups Database Servers DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybaseDesktop Databases FileMakerFoxProMS AccessParadoxGeneral General DB TopicsDatabase TheoryRelated Topics Java Development.NET DevelopmentVB DevelopmentMore Topics ... |
Database Forum / Oracle / Oracle Server / May 2005open read only standby database
hello, i have a problem when a switch from a recover standby to open read only. if i made : SQL> conn sys/syspass as sysdba --> OK SQL> startup nomount pfile='D:\standby\product\admin\orcl\pfile\init.ora' --> OK SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT; --> OK SQL> alter database recover managed standby database cancel; --> OK SQL> alter database open read only; --> OK SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT; --> OK SQL> alter database recover managed standby database cancel; --> OK SQL> alter database open read only; --> ORA-01092: ORACLE instance terminated. Disconnection forced Why the 2nd time it fails ??? Please consult the alert for the standby database. There simply must be errors in it. -- Sybrand Bakker Senior Oracle DBA I have already see them, I can read on alertSID.log : alter database open read only Mon May 30 13:34:18 2005 SMON: enabling cache recovery Mon May 30 13:49:40 2005 Errors in file d:\standby\product\admin\orcl\udump\standby_ora_7968.trc: ORA-00604: une erreur s'est produite au niveau SQL recursif 6 ORA-04021: temporisation pendant attente de verrouillage objet Mon May 30 13:49:40 2005 Error 604 happened during db open, shutting down database USER: terminating instance due to error 604 Mon May 30 13:49:40 2005 Errors in file d:\standby\product\admin\orcl\bdump\standby_reco_7392.trc: ORA-00604: une erreur s'est produite au niveau SQL recursif Mon May 30 13:49:40 2005 Errors in file d:\standby\product\admin\orcl\bdump\standby_smon_7668.trc: ORA-00604: une erreur s'est produite au niveau SQL recursif Mon May 30 13:49:41 2005 Errors in file d:\standby\product\admin\orcl\bdump\standby_ckpt_7560.trc: ORA-00604: une erreur s'est produite au niveau SQL recursif Mon May 30 13:49:41 2005 Errors in file d:\standby\product\admin\orcl\bdump\standby_pmon_4956.trc: ORA-00604: une erreur s'est produite au niveau SQL recursif Mon May 30 13:49:41 2005 Errors in file d:\standby\product\admin\orcl\bdump\standby_lgwr_4336.trc: ORA-00604: une erreur s'est produite au niveau SQL recursif Mon May 30 13:49:41 2005 Errors in file d:\standby\product\admin\orcl\bdump\standby_dbw0_6244.trc: ORA-00604: une erreur s'est produite au niveau SQL recursif Mon May 30 13:49:41 2005 Errors in file d:\standby\product\admin\orcl\bdump\standby_mman_7356.trc: ORA-00604: une erreur s'est produite au niveau SQL recursif Instance terminated by USER, pid = 7968 ORA-1092 signalled during: alter database open read only... Nothing that explain me why it fails ... >Nothing that explain me why it fails ... If you do read the error message carefully, it points you to other trace files. -- Sybrand Bakker, Senior Oracle DBA In all files .trc i have the same error : *** 2005-05-30 13:49:40.890 error 604 detected in background process ORA-00604: une erreur s'est produite au niveau SQL recursif is there a solution to have more traces, logs for this problem ??? > hello, > [quoted text clipped - 22 lines] > > Why the 2nd time it fails ??? [...] > In all files .trc i have the same error : [...] > is there a solution to have more traces, logs for this problem ??? Thank you for taking the time to examine the log files, as Sybrand suggested. It's unfortunate that they don't show any useful error message. Looking at your sequence of events, my first question is, why are you trying to do this twice? As you yourself say, it only fails the second time. I don't have time to test this myself right now, but here's my guess: With user-managed recovery, once open, you must shutdown and then re-mount the standby database before trying to recover or open it again. So, put a shutdown and a startup nomount after your first 'alter ... open', and it should work. The version 9i documentation does seem to indicate that you can resume Oracle-managed recovery directly from being open read-only, but I know that with user-managed recovery, it won't work, so I don't see how it could work under Oracle-managed recovery. The documentation also states that you must terminate all active sessions on the open-read-only database before re-starting managed recovery, so you're not losing anything, other than a few extra seconds, by doing a shutdown and startup nomount in between open statements. -Mark Bole >In all files .trc i have the same error : > [quoted text clipped - 3 lines] > >is there a solution to have more traces, logs for this problem ??? Please, PLEASE, READ the error message CAREFULLY!!!!!! In your previous post, every error message in the alert referred to a SECOND TRACE FILE, usually pmon or smon traces. Do you need glasses, or what? You didn't read the alert carefully, and you didn't read my response carefully!!! -- Sybrand Bakker, Senior Oracle DBA >>In all files .trc i have the same error : >> [quoted text clipped - 12 lines] > -- > Sybrand Bakker, Senior Oracle DBA I could be wrong, but I understood him to say that he did check the secondary trace files and still saw only the same error message. -Mark Bole I had already see alertSID.log : alter database open read only Mon May 30 13:34:18 2005 SMON: enabling cache recovery Mon May 30 13:49:40 2005 Errors in file d:\standby\product\admin\orcl\udump\standby_ora_7968.trc: ORA-00604: une erreur s'est produite au niveau SQL recursif 6 ORA-04021: temporisation pendant attente de verrouillage objet Mon May 30 13:49:40 2005 Error 604 happened during db open, shutting down database USER: terminating instance due to error 604 Mon May 30 13:49:40 2005 Errors in file d:\standby\product\admin\orcl\bdump\standby_reco_7392.trc: ORA-00604: une erreur s'est produite au niveau SQL recursif Mon May 30 13:49:40 2005 Errors in file d:\standby\product\admin\orcl\bdump\standby_smon_7668.trc: ORA-00604: une erreur s'est produite au niveau SQL recursif Mon May 30 13:49:41 2005 Errors in file d:\standby\product\admin\orcl\bdump\standby_ckpt_7560.trc: ORA-00604: une erreur s'est produite au niveau SQL recursif Mon May 30 13:49:41 2005 Errors in file d:\standby\product\admin\orcl\bdump\standby_pmon_4956.trc: ORA-00604: une erreur s'est produite au niveau SQL recursif Mon May 30 13:49:41 2005 Errors in file d:\standby\product\admin\orcl\bdump\standby_lgwr_4336.trc: ORA-00604: une erreur s'est produite au niveau SQL recursif Mon May 30 13:49:41 2005 Errors in file d:\standby\product\admin\orcl\bdump\standby_dbw0_6244.trc: ORA-00604: une erreur s'est produite au niveau SQL recursif Mon May 30 13:49:41 2005 Errors in file d:\standby\product\admin\orcl\bdump\standby_mman_7356.trc: ORA-00604: une erreur s'est produite au niveau SQL recursif Instance terminated by USER, pid = 7968 ORA-1092 signalled during: alter database open read only... Nothing explain me why it fails |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2010 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.