Home » Server Options » Data Guard » using DBMS_LOGSTDBY (ORACLE 9i)
using DBMS_LOGSTDBY [message #459483] Sat, 05 June 2010 23:42 Go to next message
TrongC500
Messages: 3
Registered: May 2010
Junior Member
I used to skip DBMS_LOGSTDBY.skip logical standby apply DDL in the database but the following error. can you help me fix error
SQL> ALTER DATABASE STOP LOGICAL STANDBY APPLY;
ALTER DATABASE STOP LOGICAL STANDBY APPLY
*
ERROR at line 1:
ORA-01109: database not open

SQL> EXECUTE DBMS_LOGSTDBY.SKIP('SCHEMA_DDL', 'ADMIN', '*', NULL);
BEGIN DBMS_LOGSTDBY.SKIP('SCHEMA_DDL', 'ADMIN', '*', NULL); END;

*
ERROR at line 1:
ORA-06550: line 1, column 7:
PLS-00201: identifier 'DBMS_LOGSTDBY.SKIP' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
SQL>


Shocked

[Updated on: Sat, 05 June 2010 23:48]

Report message to a moderator

Re: using DBMS_LOGSTDBY [message #459492 is a reply to message #459483] Sun, 06 June 2010 03:01 Go to previous messageGo to next message
John Watson
Messages: 8922
Registered: January 2010
Location: Global Village
Senior Member
DBMS_LOGSTDBY is implemented as stored PL/SQL, therefore your database must be open before you can use it.
Re: using DBMS_LOGSTDBY [message #459563 is a reply to message #459492] Mon, 07 June 2010 01:47 Go to previous messageGo to next message
TrongC500
Messages: 3
Registered: May 2010
Junior Member
John Watson wrote on Sun, 06 June 2010 03:01
DBMS_LOGSTDBY is implemented as stored PL/SQL, therefore your database must be open before you can use it.

can you teil me step by step by setp bugs fix error
Re: using DBMS_LOGSTDBY [message #459567 is a reply to message #459563] Mon, 07 June 2010 02:05 Go to previous messageGo to next message
Michel Cadot
Messages: 68625
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Have a look at alert.log and trace file to know why Oracle can't open the database.

Regards
Michel
Re: using DBMS_LOGSTDBY [message #459671 is a reply to message #459563] Mon, 07 June 2010 20:34 Go to previous messageGo to next message
trantuananh24hg
Messages: 744
Registered: January 2007
Location: Ha Noi, Viet Nam
Senior Member
TrongC500 wrote on Mon, 07 June 2010 13:47
John Watson wrote on Sun, 06 June 2010 03:01
DBMS_LOGSTDBY is implemented as stored PL/SQL, therefore your database must be open before you can use it.

can you teil me step by step by setp bugs fix error


There're not step by step to fix the bug because you did not post any error here. If you want to do, return our house, so, we can discuss Vietnamese, can't you? Cool
Re: using DBMS_LOGSTDBY [message #460037 is a reply to message #459567] Wed, 09 June 2010 07:10 Go to previous messageGo to next message
TrongC500
Messages: 3
Registered: May 2010
Junior Member
tail pv_mrp0_9403.trc

*** SESSION ID:(12.1) 2010-06-09 12:41:43.805
Background Managed Standby Recovery process started
*** 2010-06-09 12:41:48.816
Managed Recovery: Active posted.
Background Media Recovery user canceled with status 16037
*** 2010-06-09 12:44:48.853
Managed Recovery: Not Active posted.
Background Media Recovery process shutdown
*** 2010-06-09 12:44:48.853

tail alert_PV.log
Datafile 6: '/u02/oradata/PV/indx01'
Starting datafile 7 recovery in thread 1 sequence 58
Datafile 7: '/u02/oradata/PV/tools01'
Starting datafile 8 recovery in thread 1 sequence 58
Datafile 8: '/u02/oradata/PV/user01'
Starting datafile 9 recovery in thread 1 sequence 58
Datafile 9: '/u02/oradata/PV/data01'
Media Recovery Waiting for thread 1 seq# 58
Wed Jun 9 14:35:23 2010
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DI





[Updated on: Wed, 09 June 2010 07:12]

Report message to a moderator

Re: using DBMS_LOGSTDBY [message #460106 is a reply to message #460037] Wed, 09 June 2010 11:57 Go to previous message
John Watson
Messages: 8922
Registered: January 2010
Location: Global Village
Senior Member
You are confusing logical standby with physiocal standby.
Previous Topic: Recreating Physical Standby
Next Topic: fast-start failover in data guard
Goto Forum:
  


Current Time: Fri Mar 29 10:50:47 CDT 2024