2009年07月28日
11g DGMGRL測試
Thread 1 advanced to log sequence 139
Current log# 2 seq# 139 mem# 0: /u01/app/oracle/oradata/tpdb/redo02.log
******************************************************************
LGWR: Setting 'active' archival for destination LOG_ARCHIVE_DEST_3
******************************************************************
alter system set log_archive_dest_3='service="tldb"',' LGWR SYNC AFFIRM delay=0 OPTIONAL compression=DISABLE max_failure=0 max_connections=1 reopen=300 db_unique_name="tldb" net_timeout=30 valid_for=(online_logfile,primary_role)';
但設定完後,還是出現相同的訊習
經查原來是指令的問題,直接貼官方說明文件
To start a physical standby database, use SQL*Plus to connect to the database with administrator privileges, and then use either the SQL*Plus STARTUP or STARTUP MOUNT statement. When used on a physical standby database:
- The STARTUP statement starts the database, mounts the database as a physical standby database, and opens the database for read-only access.
- The STARTUP MOUNT statement starts and mounts the database as a physical standby database, but does not open the database.
Once mounted, the database can receive archived redo data from the primary database. You then have the option of either starting Redo Apply or opening the database for read-only access. Typically, you start Redo Apply. The following example shows how to start a physical standby database:
- Start and mount the database:
SQL> STARTUP MOUNT;
- Start log apply services:
To start Redo Apply, issue the following statement:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
2> DISCONNECT FROM SESSION;To start real-time apply, issue the following statement:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
2> USING CURRENT LOGFILE;
On the primary database, query the RECOVERY_MODE column in the V$ARCHIVED_DEST_STATUS view, which displays the standby database's operation as MANAGED_RECOVERY for Redo Apply and MANAGED REAL TIME APPLY for real-time apply.
- Start and mount the database: