|
Home > Archive > Oracle Server > May 2005 > open read only standby database
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
open read only standby database
|
|
| georgesdeoliveira94@yahoo.fr 2005-05-30, 11:23 am |
| 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\pr
oduct\admin\orcl\pfi
le\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 ???
| |
| sybrandb@yahoo.com 2005-05-30, 11:23 am |
| Please consult the alert for the standby database. There simply must be
errors in it.
--
Sybrand Bakker
Senior Oracle DBA
| |
| georgesdeoliveira94@yahoo.fr 2005-05-30, 11:23 am |
| 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\a
dmin\orcl\udump\stan
dby_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\a
dmin\orcl\bdump\stan
dby_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\a
dmin\orcl\bdump\stan
dby_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\a
dmin\orcl\bdump\stan
dby_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\a
dmin\orcl\bdump\stan
dby_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\a
dmin\orcl\bdump\stan
dby_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\a
dmin\orcl\bdump\stan
dby_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\a
dmin\orcl\bdump\stan
dby_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 ...
| |
| georgesdeoliveira94@yahoo.fr 2005-05-30, 11:23 am |
| 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\a
dmin\orcl\udump\stan
dby_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\a
dmin\orcl\bdump\stan
dby_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\a
dmin\orcl\bdump\stan
dby_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\a
dmin\orcl\bdump\stan
dby_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\a
dmin\orcl\bdump\stan
dby_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\a
dmin\orcl\bdump\stan
dby_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\a
dmin\orcl\bdump\stan
dby_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\a
dmin\orcl\bdump\stan
dby_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
| |
| Sybrand Bakker 2005-05-30, 1:23 pm |
| On 30 May 2005 08:24:28 -0700, " georgesdeoliveira94@
yahoo.fr"
< georgesdeoliveira94@
yahoo.fr> wrote:
>
>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
| |
| georgesdeoliveira94@yahoo.fr 2005-05-31, 3:23 am |
| 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 ???
| |
| Mark Bole 2005-05-31, 11:23 am |
| georgesdeoliveira94@
yahoo.fr wrote:
> 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\pr
oduct\admin\orcl\pfi
le\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 ???
>
[...]
georgesdeoliveira94@
yahoo.fr wrote:
> 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
| |
| Sybrand Bakker 2005-05-31, 1:23 pm |
| On 31 May 2005 00:10:33 -0700, " georgesdeoliveira94@
yahoo.fr"
< georgesdeoliveira94@
yahoo.fr> wrote:
>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 ???
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
| |
| Mark Bole 2005-05-31, 1:23 pm |
| Sybrand Bakker wrote:
> On 31 May 2005 00:10:33 -0700, " georgesdeoliveira94@
yahoo.fr"
> < georgesdeoliveira94@
yahoo.fr> wrote:
>
>
>
>
> 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
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
|
|
|
|
|