SRL on standby db
Hi all,
I have created a physical standby database following the steps mentioned in Metalink document id [ID 789370.1]. that worked well and logs are being applied when i switch logfile in primary.
But in the document in step 11 it is asking for creating standby redo log groups. I have added 4 srl on standby.
My question is whether it is necessary to add srl on standby database? I have added srl group 4,5,6,7 on primary. when i try to add srl group 4 on stand by it is showing already exist.
Tnx.
Edited by: user4468476 on Oct 4, 2010 10:41 PM
Hi,
From the doc:
3.1.3 Configure a Standby Redo Log
A standby redo log is required for the maximum protection and maximum availability modes and the LGWR ASYNC transport mode is recommended for all databases. Data Guard can recover and apply more redo data from a standby redo log than from archived redo log files alone.
You should plan the standby redo log configuration and create all required log groups and group members when you create the standby database. For increased availability, consider multiplexing the standby redo log files, similar to the way that online redo log files are multiplexed.
Perform the following steps to configure the standby redo log.
Step 1 Ensure log file sizes are identical on the primary and standby databases.
The size of the current standby redo log files must exactly match the size of the current primary database online redo log files. For example, if the primary database uses two online redo log groups whose log files are 200K, then the standby redo log groups should also have log file sizes of 200K.
Step 2 Determine the appropriate number of standby redo log file groups.
Minimally, the configuration should have one more standby redo log file group than the number of online redo log file groups on the primary database. However, the recommended number of standby redo log file groups is dependent on the number of threads on the primary database. Use the following equation to determine an appropriate number of standby redo log file groups:
(maximum number of logfiles for each thread + 1) * maximum number of threads
Using this equation reduces the likelihood that the primary instance's log writer (LGWR) process will be blocked because a standby redo log file cannot be allocated on the standby database. For example, if the primary database has 2 log files for each thread and 2 threads, then 6 standby redo log file groups are needed on the standby database.
Note:
Logical standby databases may require more standby redo log files (or additional ARCn processes) depending on the workload. This is because logical standby databases also write to online redo log files, which take precedence over standby redo log files. Thus, the standby redo log files may not be archived as quickly as the online redo log files. Also, see Section 5.7.3.1.
Step 3 Verify related database parameters and settings.
Verify the values used for the MAXLOGFILES and MAXLOGMEMBERS clauses on the SQL CREATE DATABASE statement will not limit the number of standby redo log file groups and members that you can add. The only way to override the limits specified by the MAXLOGFILES and MAXLOGMEMBERS clauses is to re-create the primary database or control file.
See Oracle Database SQL Reference and your operating system specific Oracle documentation for the default and legal values of the MAXLOGFILES and MAXLOGMEMBERS clauses.
Step 4 Create standby redo log file groups.
To create new standby redo log file groups and members, you must have the ALTER DATABASE system privilege. The standby database begins using the newly created standby redo data the next time there is a log switch on the primary database. Example 3-1 and Example 3-2 show how to create a new standby redo log file group using the ALTER DATABASE statement with variations of the ADD STANDBY LOGFILE GROUP clause.
Example 3-1 Adding a Standby Redo Log File Group to a Specific Thread
The following statement adds a new standby redo log file group to a standby database and assigns it to THREAD 5:
SQL> ALTER DATABASE ADD STANDBY LOGFILE THREAD 5
2> ('/oracle/dbs/log1c.rdo','/oracle/dbs/log2c.rdo') SIZE 500M;
The THREAD clause is required only if you want to add one or more standby redo log file groups to a specific primary database thread. If you do not include the THREAD clause and the configuration uses Real Application Clusters (RAC), Data Guard will automatically assign standby redo log file groups to threads at runtime as they are needed by the various RAC instances.
Example 3-2 Adding a Standby Redo Log File Group to a Specific Group Number
You can also specify a number that identifies the group using the GROUP clause:
SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 10
2> ('/oracle/dbs/log1c.rdo','/oracle/dbs/log2c.rdo') SIZE 500M;
Using group numbers can make administering standby redo log file groups easier. However, the group number must be between 1 and the value of the MAXLOGFILES clause. Do not skip log file group numbers (that is, do not number groups 10, 20, 30, and so on), or you will use additional space in the standby database control file.
Note:
Although the standby redo log is only used when the database is running in the standby role, Oracle recommends that you create a standby redo log on the primary database so that the primary database can switch over quickly to the standby role without the need for additional DBA intervention. Consider using Oracle Enterprise Manager to automatically configure standby redo log on both your primary and standby databases.
Step 5 Verify the standby redo log file groups were created.
To verify the standby redo log file groups are created and running correctly, invoke a log switch on the primary database, and then query either the V$STANDBY_LOG view or the V$LOGFILE view on the standby database once it has been created. For example:
SQL> SELECT GROUP#,THREAD#,SEQUENCE#,ARCHIVED,STATUS FROM V$STANDBY_LOG;
GROUP# THREAD# SEQUENCE# ARC STATUS
3 1 16 NO ACTIVE
4 0 0 YES UNASSIGNED
5 0 0 YES UNASSIGNED
And it's better to create both type of redo on each side to prevent the use of failover, switchover.
Verify what you already have on both database.
Loïc
Similar Messages
-
In what situation, standby redo logs are mandatory.
I have the below settings and my DATA GAURD setup (10.2.0.3) is working fine without Stdby redo logs.
Just wondering when do i need standby redo logs.
SQL> show parameter log_Archive_dest_2
NAME TYPE VALUE
log_archive_dest_2 string SERVICE=TO_STANDBY LGWR ASYNC
AFFIRM DB_UNIQUE_NAME=stand
SQL> select protection_mode from v$database;
PROTECTION_MODE
MAXIMUM PERFORMANCE888442 wrote:
In what situation, standby redo logs are mandatory.
I have the below settings and my DATA GAURD setup (10.2.0.3) is working fine without Stdby redo logs.
Just wondering when do i need standby redo logs.
SQL> show parameter log_Archive_dest_2
NAME TYPE VALUE
log_archive_dest_2 string SERVICE=TO_STANDBY LGWR ASYNC AFFIRM DB_UNIQUE_NAME=stand
SQL> select protection_mode from v$database;
PROTECTION_MODE
MAXIMUM PERFORMANCEHi,
Standby Redo Logs (SRL) require when you are using MAX AVAILABILITY and MAX PROTECTIN protection modes. So SRL using for Real Time Apply.
In your case (Max Performance) if you want real time apply on standby you must add SRLs to standby database.
Best practice we adding standby redo logs to primary and standby database same time, but when database role is standby then using SRLs.
You can ask, why also to primary? Because we can switchover to standby, then priamry role will change to standby, then will use SRLs.
Regards
Mahir M. Quluzade -
Hi,
From oracle document i know in the standby side the RFS process writes to Standby redo log file -> archive log and the MRP procees applys the archive logs to the standby database.
my question is ,if we dont create standby redo log file what happens?Hello;
When redo is received by an RFS on the standby , the RFS process writes the redo data into archived redo logs or optionally to the SRL.
Standby Redo Logs is where the RFS process at your Standby database writes incoming redo, they help performance because the RFS does not have to create the Archive log file.
Standby redo logs are a component of the Data Guard setup. They should be the same size as the redo logs on the Primary.
Standby Redo Logs do not not to be multiplexed.
I would create SRL them on both the Primary and the Standby. Think of it as one database in either Standby or Primary Mode. If you have to switchover you still need them.
If you have SRL's setup and need to do either a failover or switchover it should occur faster and safer.
Best Regards
mseberg -
I want to convert our old script based primary /standby database into a dataguard config using the LGWR as log transport.
I already have old log files on the standby database, but the data in them is from 2004. Not entirely interesting since the database gets recovered from the arch log files every night.
Point is, can I use these as standby log files, or do I have to (somehow) drop these and re-create new standby logfiles. I cant drop them anyway since when I try, I get "ORA-01624, log 1 needed for crash recovery". (Like h*ll, since the data is older than Noah).
Will these just get re-written?
null
nullNote:219344.1 This note from metalink gives "Usage, Benefits and Limitations of Standby Redo Logs (SRL)".
Standby Redo Logs are only supported for the Physical Standby Database in
Oracle 9i and as well for Logical Standby Databases in 10g. Standby Redo Logs
are only used if you have the LGWR activated for archival to the Remote Standby
Database.
The great Advantage of Standby Redo Logs is that every Entry written into
the Online RedoLogs of the Primary Database is transfered to the Standby
Site and written into the Standby Redo Logs at the same time; threfore, you
reduce the probability of Data Loss on the Standby Database. -
Hi All,
I have some doubts in Oracle Standby database configuration and log transfer and redo apply.
I have read the below document.
Oracle® Data Guard Concepts and Administration
Now my doubts are *(in Physical standby database with Maximum performance mode)*
1. When configuring the standby database we are creating standby redologs in primary database,Is this standby redologs are used only when the role transition happens or for anyother purpose?
2.The archivelogs are shipped from primary to standby and the archivelogs are applied to the standby database by doing the normal media recovery.Now, how and when the data is written in the standby database redologfiles,so that when we enable the real time apply it uses the standby database redologfile to apply the data without delay?
3.(if the second point is true)In the standby database will it generate the Archivelogfiles from the redo applied, apart from the primary archivelogs which are transfered?
Please Advice..
TIA,1. When configuring the standby database we are creating standby redologs in primary database,Is this standby redologs are used only when the role transition happens or for anyother purpose?It is not for role transition.
A standby redo log is required for the maximum protection and maximum availability modes and the LGWR ASYNC transport mode is recommended for all databases.
You can recover more data than only applying archive logs in case of failure.
SRLs' are a must for real time apply.
2.The archivelogs are shipped from primary to standby and the archivelogs are applied to the standby database by doing the normal media recovery.Now, how and when the data is written in the standby database redologfiles,so that when we enable the real time apply it uses the standby database redologfile to apply the data without delay?The data is directly written from production to SRL of standby database using lgwr process(with the help of RFS), that is why it real time. Not waiting for a log switch. See the [diagram.|http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/log_apply.htm#i1021537]
3.(if the second point is true)In the standby database will it generate the Archivelogfiles from the redo applied, apart from the primary archivelogs which are transfered?No. Only standby redo log will generate archived logs.
Regards,
S.K. -
Receveid Archivedlog from primary BUT not applied
Hi all,
We're using Oracle 10g Enterprise Edition.
I've created the physical standby database, and I've stated the MRP.
The archivedlog file are received like we can see on v$archived_log:
SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME, APPLIED
FROM V$ARCHIVED_LOG
ORDER BY SEQUENCE#;
SEQUENCE# FIRST_TIM NEXT_TIME APP
15767 27-OCT-11 27-OCT-11 NO
15768 27-OCT-11 27-OCT-11 NO
15769 28-OCT-11 28-OCT-11 NO
15770 28-OCT-11 28-OCT-11 NO
15771 28-OCT-11 28-OCT-11 NO
15772 28-OCT-11 28-OCT-11 NO
15773 28-OCT-11 28-OCT-11 NO
15774 28-OCT-11 28-OCT-11 NO
15775 28-OCT-11 28-OCT-11 NO
15776 29-OCT-11 29-OCT-11 NO
15777 29-OCT-11 29-OCT-11 NO
15778 29-OCT-11 29-OCT-11 NO
15779 29-OCT-11 29-OCT-11 NO
15780 29-OCT-11 29-OCT-11 NO
15781 29-OCT-11 29-OCT-11 NO
15782 29-OCT-11 29-OCT-11 NO
SQL> SELECT ARCH.THREAD# "Thread", ARCH.SEQUENCE# "Last Sequence Received", APPL.SEQUENCE# "Last Sequence Applied",
2 (ARCH.SEQUENCE# - APPL.SEQUENCE#) "Difference"
3 FROM
4 (SELECT THREAD# ,SEQUENCE# FROM V$ARCHIVED_LOG WHERE (THREAD#,FIRST_TIME ) IN
5 (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)) ARCH,
(SELECT THREAD# ,SEQUENCE# FROM V$LOG_HISTORY WHERE (THREAD#,FIRST_TIME ) IN
(SELECT THREAD#,MAX(FIRST_TIME) FROM V$LOG_HISTORY GROUP BY THREAD#)) APPL
6 7 8 WHERE ARCH.THREAD# = APPL.THREAD#
ORDER BY 1; 9
Thread Last Sequence Received Last Sequence Applied Difference
1 15782 15767 16But no archivedlog file wa applied. This means is not totally synchronized yet, or not?
Several days and no archivedlog file wa applied.
Is there problem here? How can I apply in physical standby?
thank you very much!!!!Hi,
I's stranger here.
Before I take backup, I've created the SRLs on primary:
ALTER DATABASE ADD STANDBY LOGFILE GROUP 4 ('+DATA', '+FRA') SIZE 300M;
ALTER DATABASE ADD STANDBY LOGFILE GROUP 5 ('+DATA', '+FRA') SIZE 300M;
ALTER DATABASE ADD STANDBY LOGFILE GROUP 6 ('+DATA', '+FRA') SIZE 300M;
ALTER DATABASE ADD STANDBY LOGFILE GROUP 7 ('+DATA', '+FRA') SIZE 300M;After I take backup e finally execute the duplicate for standby.
But no standby database ALL SRls are in standby.
Only one that I've created after the duplicate for standby.
It follows the redo logs and SRLs on standby:
GROUP# STATUS TYPE MEMBER IS_
1 ONLINE +REDO1/proj/onlinelog/redo01a.log NO
1 ONLINE +REDO2/proj/onlinelog/redo01b.log NO
2 ONLINE +REDO1/proj/onlinelog/redo02a.log NO
2 ONLINE +REDO2/proj/onlinelog/redo02b.log NO
3 ONLINE +REDO1/proj/onlinelog/redo03a.log NO
3 ONLINE +REDO2/proj/onlinelog/redo03b.log NO
8 STANDBY +REDO01/proj_std/onlinelog/group_8.256.764973797 NO
8 STANDBY +REDO02/proj_std/onlinelog/group_8.256.764973797 NO
18 rows selected.
SQL> set lines 140
col dbid format a17
select * from v$standby_log;SQL> SQL>
GROUP# DBID THREAD# SEQUENCE# BYTES USED ARC STATUS FIRST_CHANGE# FIRST_TIM LAST_CHANGE# LAST_TIME
8 1247984584 1 15788 314572800 0 YES ACTIVE 7.1402E+10 29-OCT-11 7.1403E+10 29-OCT-11So, I dont know if I must create again the SRLs in standby.
I didnt ge any error on duplicate. Only archivedlog necessary to recover.
Thank you very much!!!! -
Standby database SRL & Online logs
Hi,
I have just tried my hand at building a Physical standby database in Oracle 10gR2 using RMAN. I will detail out the steps that i have performed before asking my question.
I configured every pre-requisite and i did not create any SRL's on primary before building a standby database. I am using LGWR ASYNC for redo transmission. I have configured FAL_CLIENT and FAL_SERVER. Protection mode is MAX PERFORMANCE and it is on Solaris 10 x86_64
1. Took a RMAN full backup
and created a standby control file as
SQL> alter database create standby controlfile as '/tmp/standby.ctl';
2. On another server, I copied the pfile, standby controlfile (renamed it) from primary and mounted the database.
sqlplus /as sysdba'
SQL> startup mount pfile='...';
rman target /
RMAN> restore database;
SQL> alter database recover managed standby database disconnect from session;
Everything worked and MRP was applying the archived logs as they were received from the primary. But, i have seen the SRL's created with default names on the primary database & standby database by Oracle even though i did not explicitly create them. Is this a normal behaviour? I saw them using v$standby_log.
As a Physical standby database will not use any ONLINE REDO LOGS and i haven't created any with the procedure i have used. i have performed a SWITCHOVER, which has worked with out any problem. My question here is
1. How did Oracle open the database database when there were no redo logs physically present on the standby site? Is this a normal behavior in a standby environment where Oracle creates ONLINE REDO LOG files for a Standby database being transitioned to Primary whenever a SWITCHOVER or FAILOVER occurs? If this is the case, it is obvious that Oracle will take the LOG SEQUENCE from the last applied ARCHIVED LOG and will start the ONLINE LOG from that sequence?
Please correct me if i have understood anything wrong here or if i have configured anything wrong. But with the above configuration the Standby database worked perfectly well and switchover was successful too.
Thanks,
Harris.Correction: I have not created the Standby Database using RMAN but only performed a FULL backup, which i have restored before starting the MRP.
-
DataGuard Standby 環境で db が open できない.
DataGuard Standby 環境で db が open できなくて困っています。
詳しい方いれば、原因と対処方法を教えていただきたいと思います。
create した spfile が正確に読み込まれていないことが原因のようなのですが。。
なぜ読み込めないのかが分からない状態です。
pfile を読み込んだ起動は可能ですが、spfile を読み込んだ起動の前提条件とは、
何なのでしょうか。単に整合性が取れていないだけなのか、それとも、、。
[grid@osaka1 shell]$ asmcmd
ASMCMD> ls
DATA/
FRA/
ASMCMD> cd data
ASMCMD> ls
ASM/
WEST/
ASMCMD> ls -l
Type Redund Striped Time Sys Name
Y ASM/
N WEST/
ASMCMD>
ASMCMD> cd west
ASMCMD> ls
CONTROLFILE/
DATAFILE/
ONLINELOG/
PARAMETERFILE/
TEMPFILE/
spfilewest.ora
ASMCMD> ls -l
Type Redund Striped Time Sys Name
N CONTROLFILE/
N DATAFILE/
N ONLINELOG/
N PARAMETERFILE/
N TEMPFILE/
N spfilewest.ora => +DATA/WEST/PARAMETERFILE/spfile.257.824236121
ASMCMD> pwd
+data/west
ASMCMD>
ASMCMD> cd para*
ASMCMD> ls -l
Type Redund Striped Time Sys Name
PARAMETERFILE MIRROR COARSE AUG 23 18:00:00 Y spfile.257.824236121
ASMCMD>
ASMCMD> pwd
+data/west/PARAMETERFILE
ASMCMD> quit
[grid@osaka1 shell]$
[oracle@osaka1 dbs]$ more initHPYMUSIC.ora
SPFILE='+DATA/west/spfilewest.ora'
[oracle@osaka1 dbs]$
よろしくお願い致します。
ps.
ORA-12154 は整合性の問題であるので、それを合わせれば消えると思っています。
そもそも RAC を前提としていたのですが、それを standalone に置き換えて検証始めた結果、
こうなってしまっています。
open できない原因が ORA-12154 だったりして。。
■ プライマリの場合
○ open するほうは、シンプルに以下だけで open することが確認できる。
が、db_name を変更した関係で
「ORA-12154: TNS: 指定された接続識別子を解決できませんでした」
が出続けている。
ORA-12154 は db が open できない原因とは無関係かもしれない。
srvctl stop database -d east -f
srvctl start database -d east -o open
srvctl config database -d east
srvctl status database -d east
○ 参考出力
set linesize 500 pages 0
col value for a90
col name for a50
select name, value
from v$parameter
where name in ('db_name','db_unique_name','log_archive_config', 'log_archive_dest_1','log_archive_dest_2',
'log_archive_dest_state_1','log_archive_dest_state_2', 'remote_login_passwordfile',
'log_archive_format','log_archive_max_processes','fal_server','db_file_name_convert',
'log_file_name_convert', 'standby_file_management');
SQL>
db_file_name_convert
log_file_name_convert
log_archive_dest_1
log_archive_dest_2 SERVICE=HPYMUSIC SYNC NOAFFIRM VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=west
log_archive_dest_state_1 enable
log_archive_dest_state_2 enable
fal_server
log_archive_config
log_archive_format %t_%s_%r.dbf
log_archive_max_processes 4
standby_file_management AUTO
remote_login_passwordfile EXCLUSIVE
db_name HPYMUSIC
db_unique_name HPYMUSIC ← ▼ db_name だけを変更したつもりが db_unique_name も変更されていた
14行が選択されました。
[oracle@tokyo1 shell]$ srvctl stop database -d east -f
[oracle@tokyo1 shell]$ /u01/app/11.2.0/grid/bin/crsctl status resource -t
NAME TARGET STATE SERVER STATE_DETAILS
Cluster Resources
ora.east.db
1 OFFLINE OFFLINE Instance Shutdown
[oracle@tokyo1 shell]$ srvctl start database -d east -o open
[oracle@tokyo1 shell]$ /u01/app/11.2.0/grid/bin/crsctl status resource -t
NAME TARGET STATE SERVER STATE_DETAILS
Local Resources
ora.DATA.dg
ONLINE ONLINE tokyo1
ora.FRA.dg
ONLINE ONLINE tokyo1
ora.LISTENER.lsnr
ONLINE ONLINE tokyo1
ora.asm
ONLINE ONLINE tokyo1 Started
Cluster Resources
ora.cssd
1 ONLINE ONLINE tokyo1
ora.diskmon
1 ONLINE ONLINE tokyo1
ora.east.db
1 ONLINE ONLINE tokyo1 Open ← ▼
[oracle@tokyo1 shell]$
[oracle@tokyo1 shell]$ srvctl config database -d east
一意のデータベース名: east
データベース名: east
Oracleホーム: /u01/app/oracle/product/11.2.0/dbhome_1
Oracleユーザー: grid
spfile: +DATA/east/spfileeast.ora
ドメイン:
開始オプション: open
停止オプション: immediate
データベース・ロール: PRIMARY
管理ポリシー: AUTOMATIC
ディスク・グループ: DATA,FRA
サービス:
[oracle@tokyo1 shell]$ srvctl status database -d east
データベースは実行中です。
Fri Aug 23 19:44:10 2013
Error 12154 received logging on to the standby
Errors in file /u01/app/oracle/diag/rdbms/hpymusic/HPYMUSIC/trace/HPYMUSIC_arc2_7579.trc:
ORA-12154: TNS: 指定された接続識別子を解決できませんでした
PING[ARC2]: Heartbeat failed to connect to standby 'HPYMUSIC'. Error is 12154.
[oracle@tokyo1 dbs]$ pwd
/u01/app/oracle/product/11.2.0/dbhome_1/dbs
[oracle@tokyo1 dbs]$
[oracle@tokyo1 dbs]$
[oracle@tokyo1 dbs]$ more 2013.08.23_east_pfile.txt
HPYMUSIC.__db_cache_size=301989888
HPYMUSIC.__java_pool_size=4194304
HPYMUSIC.__large_pool_size=8388608
HPYMUSIC.__pga_aggregate_target=339738624
HPYMUSIC.__sga_target=503316480
HPYMUSIC.__shared_io_pool_size=0
HPYMUSIC.__shared_pool_size=176160768
HPYMUSIC.__streams_pool_size=0
*.audit_file_dest='/u01/app/oracle/admin/east/adump'
*.audit_trail='db'
*.compatible='11.2.0.0.0'
*.control_files='+DATA/east/controlfile/current.270.823277705','+FRA/east/controlfile/current.
260.823277707'
*.db_block_checking='TRUE'
*.db_block_checksum='TRUE'
*.db_block_size=8192
*.db_create_file_dest='+DATA'
*.db_domain=''
*.db_name='HPYMUSIC'
*.db_recovery_file_dest='+FRA'
*.db_recovery_file_dest_size=3038773248
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=HPYMUSICXDB)'
*.log_archive_format='%t_%s_%r.dbf'
*.memory_target=842006528
*.nls_language='JAPANESE'
*.nls_territory='JAPAN'
*.open_cursors=300
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.standby_file_management='AUTO'
*.undo_tablespace='UNDOTBS1'
Fri Aug 23 19:49:38 2013
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
ARCH: Warning; less destinations available than specified
by LOG_ARCHIVE_MIN_SUCCEED_DEST init.ora parameter
Autotune of undo retention is turned on.
IMODE=BR
ILAT =27
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
Using parameter settings in server-side spfile /u01/app/oracle/product/11.2.0/dbhome_1/dbs/spfileHPYMUSIC.ora
System parameters with non-default values:
processes = 150
nls_language = "JAPANESE"
nls_territory = "JAPAN"
memory_target = 804M
control_files = "+DATA/east/controlfile/current.270.823277705"
control_files = "+FRA/east/controlfile/current.260.823277707"
db_block_checksum = "TRUE"
db_block_size = 8192
compatible = "11.2.0.0.0"
log_archive_dest_2 = "SERVICE=HPYMUSIC SYNC NOAFFIRM VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=west"
log_archive_format = "%t_%s_%r.dbf"
db_create_file_dest = "+DATA"
db_recovery_file_dest = "+FRA"
db_recovery_file_dest_size= 2898M
standby_file_management = "AUTO"
undo_tablespace = "UNDOTBS1"
db_block_checking = "TRUE"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=HPYMUSICXDB)"
audit_file_dest = "/u01/app/oracle/admin/east/adump"
audit_trail = "DB"
db_name = "HPYMUSIC"
open_cursors = 300
diagnostic_dest = "/u01/app/oracle"
Fri Aug 23 19:49:39 2013
PMON started with pid=2, OS id=8442
Fri Aug 23 19:49:39 2013
VKTM started with pid=3, OS id=8444 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Fri Aug 23 19:49:39 2013
GEN0 started with pid=4, OS id=8448
Fri Aug 23 19:49:39 2013
DIAG started with pid=5, OS id=8450
Fri Aug 23 19:49:39 2013
DBRM started with pid=6, OS id=8452
Fri Aug 23 19:49:39 2013
PSP0 started with pid=7, OS id=8454
Fri Aug 23 19:49:39 2013
DIA0 started with pid=8, OS id=8456
Fri Aug 23 19:49:39 2013
MMAN started with pid=9, OS id=8458
Fri Aug 23 19:49:39 2013
DBW0 started with pid=10, OS id=8460
Fri Aug 23 19:49:39 2013
LGWR started with pid=11, OS id=8462
Fri Aug 23 19:49:39 2013
CKPT started with pid=12, OS id=8464
Fri Aug 23 19:49:39 2013
SMON started with pid=13, OS id=8466
Fri Aug 23 19:49:39 2013
RECO started with pid=14, OS id=8468
Fri Aug 23 19:49:39 2013
RBAL started with pid=15, OS id=8470
Fri Aug 23 19:49:39 2013
ASMB started with pid=16, OS id=8472
Fri Aug 23 19:49:39 2013
MMON started with pid=17, OS id=8474
Fri Aug 23 19:49:39 2013
MMNL started with pid=18, OS id=8478
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
NOTE: initiating MARK startup
starting up 1 shared server(s) ...
Starting background process MARK
Fri Aug 23 19:49:39 2013
MARK started with pid=20, OS id=8482
NOTE: MARK has subscribed
ORACLE_BASE not set in environment. It is recommended
that ORACLE_BASE be set in the environment
Reusing ORACLE_BASE from an earlier startup = /u01/app/oracle
Fri Aug 23 19:49:39 2013
ALTER DATABASE MOUNT
NOTE: Loaded library: System
SUCCESS: diskgroup DATA was mounted
ERROR: failed to establish dependency between database HPYMUSIC and diskgroup resource ora.DATA.dg
SUCCESS: diskgroup FRA was mounted
ERROR: failed to establish dependency between database HPYMUSIC and diskgroup resource ora.FRA.dg
Fri Aug 23 19:49:46 2013
NSS2 started with pid=24, OS id=8572
Successful mount of redo thread 1, with mount id 2951868947
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE MOUNT
ALTER DATABASE OPEN
LGWR: STARTING ARCH PROCESSES
Fri Aug 23 19:49:47 2013
ARC0 started with pid=26, OS id=8574
ARC0: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC0: STARTING ARCH PROCESSES
Fri Aug 23 19:49:48 2013
ARC1 started with pid=27, OS id=8576
Fri Aug 23 19:49:48 2013
ARC2 started with pid=28, OS id=8578
ARC1: Archival started
ARC2: Archival started
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
ARC2: Becoming the heartbeat ARCH
Fri Aug 23 19:49:48 2013
ARC3 started with pid=29, OS id=8580
LGWR: Setting 'active' archival for destination LOG_ARCHIVE_DEST_2
ARC3: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
Error 12154 received logging on to the standby
Fri Aug 23 19:49:51 2013
Errors in file /u01/app/oracle/diag/rdbms/hpymusic/HPYMUSIC/trace/HPYMUSIC_lgwr_8462.trc:
ORA-12154: TNS: ?????????????????????
Error 12154 for archive log file 2 to 'HPYMUSIC'
LGWR: Failed to archive log 2 thread 1 sequence 8 (12154)
Thread 1 advanced to log sequence 8 (thread open)
Thread 1 opened at log sequence 8
Current log# 2 seq# 8 mem# 0: +DATA/hpymusic/onlinelog/group_2.272.824213887
Current log# 2 seq# 8 mem# 1: +FRA/hpymusic/onlinelog/group_2.262.824213889
Successful open of redo thread 1
Fri Aug 23 19:49:51 2013
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Fri Aug 23 19:49:51 2013
SMON: enabling cache recovery
Error 12154 received logging on to the standby
Errors in file /u01/app/oracle/diag/rdbms/hpymusic/HPYMUSIC/trace/HPYMUSIC_arc2_8578.trc:
ORA-12154: TNS: 指定された接続識別子を解決できませんでした
PING[ARC2]: Heartbeat failed to connect to standby 'HPYMUSIC'. Error is 12154.
Archived Log entry 7 added for thread 1 sequence 7 ID 0xaff1210d dest 1:
Error 12154 received logging on to the standby
Errors in file /u01/app/oracle/diag/rdbms/hpymusic/HPYMUSIC/trace/HPYMUSIC_arc3_8580.trc:
ORA-12154: TNS: 指定された接続識別子を解決できませんでした
FAL[server, ARC3]: Error 12154 creating remote archivelog file 'HPYMUSIC'
FAL[server, ARC3]: FAL archive failed, see trace file.
Errors in file /u01/app/oracle/diag/rdbms/hpymusic/HPYMUSIC/trace/HPYMUSIC_arc3_8580.trc:
ORA-16055: FALリクエストが拒否されました。
ARCH: FAL archive failed. Archiver continuing
ORACLE Instance HPYMUSIC - Archival Error. Archiver continuing.
Successfully onlined Undo Tablespace 2.
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is AL32UTF8
No Resource Manager plan active
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
Fri Aug 23 19:49:55 2013
QMNC started with pid=32, OS id=8590
Completed: ALTER DATABASE OPEN
Fri Aug 23 19:49:59 2013
Starting background process CJQ0
Fri Aug 23 19:49:59 2013
CJQ0 started with pid=33, OS id=8609
Fri Aug 23 19:49:59 2013
db_recovery_file_dest_size of 2898 MB is 6.38% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
[root@tokyo1 app]#
[root@tokyo1 app]# more /u01/app/oracle/diag/rdbms/hpymusic/HPYMUSIC/trace/HPYMUSIC_arc2_8578.trc
Trace file /u01/app/oracle/diag/rdbms/hpymusic/HPYMUSIC/trace/HPYMUSIC_arc2_8578.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1
System name: Linux
Node name: tokyo1.oracle11g.jp
Release: 2.6.18-348.12.1.el5
Version: #1 SMP Wed Jul 10 05:28:41 EDT 2013
Machine: x86_64
Instance name: HPYMUSIC
Redo thread mounted by this instance: 1
Oracle process number: 28
Unix process pid: 8578, image: [email protected] (ARC2)
*** 2013-08-23 19:49:51.707
*** SESSION ID:(15.1) 2013-08-23 19:49:51.707
*** CLIENT ID:() 2013-08-23 19:49:51.707
*** SERVICE NAME:() 2013-08-23 19:49:51.707
*** MODULE NAME:() 2013-08-23 19:49:51.707
*** ACTION NAME:() 2013-08-23 19:49:51.707
Redo shipping client performing standby login
OCIServerAttach failed -1
.. Detailed OCI error val is 12154 and errmsg is 'ORA-12154: TNS: 指定された接続識別子を解決できませんでした
OCIServerAttach failed -1
.. Detailed OCI error val is 12154 and errmsg is 'ORA-12154: TNS: 指定された接続識別子を解決できませんでした
OCIServerAttach failed -1
.. Detailed OCI error val is 12154 and errmsg is 'ORA-12154: TNS: 指定された接続識別子を解決できませんでした
*** 2013-08-23 19:49:51.972 4132 krsh.c
Error 12154 received logging on to the standby
*** 2013-08-23 19:49:51.972 869 krsu.c
Error 12154 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'HPYMUSIC'
Error 12154 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'HPYMUSIC'
ORA-12154: TNS: 指定された接続識別子を解決できませんでした
*** 2013-08-23 19:49:51.973 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'HPYMUSIC'. Error is 12154.
*** 2013-08-23 19:49:51.973 2747 krsi.c
krsi_dst_fail: dest:2 err:12154 force:0 blast:1
*** 2013-08-23 19:50:49.816
Redo shipping client performing standby login
OCIServerAttach failed -1
.. Detailed OCI error val is 12154 and errmsg is 'ORA-12154: TNS: 指定された接続識別子を解決できませんでした
OCIServerAttach failed -1
.. Detailed OCI error val is 12154 and errmsg is 'ORA-12154: TNS: 指定された接続識別子を解決できませんでした
OCIServerAttach failed -1
.. Detailed OCI error val is 12154 and errmsg is 'ORA-12154: TNS: 指定された接続識別子を解決できませんでした
*** 2013-08-23 19:50:50.070 4132 krsh.c
Error 12154 received logging on to the standby
*** 2013-08-23 19:50:50.070 869 krsu.c
Error 12154 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'HPYMUSIC'
Error 12154 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'HPYMUSIC'
ORA-12154: TNS: 指定された接続識別子を解決できませんでした
*** 2013-08-23 19:50:50.070 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'HPYMUSIC'. Error is 12154.
*** 2013-08-23 19:50:50.070 2747 krsi.c
krsi_dst_fail: dest:2 err:12154 force:0 blast:1
*** 2013-08-23 19:51:51.147
Redo shipping client performing standby login
OCIServerAttach failed -1
.. Detailed OCI error val is 12154 and errmsg is 'ORA-12154: TNS: 指定された接続識別子を解決できませんでした
OCIServerAttach failed -1
.. Detailed OCI error val is 12154 and errmsg is 'ORA-12154: TNS: 指定された接続識別子を解決できませんでした
OCIServerAttach failed -1
.. Detailed OCI error val is 12154 and errmsg is 'ORA-12154: TNS: 指定された接続識別子を解決できませんでした
*** 2013-08-23 19:51:51.403 4132 krsh.c
Error 12154 received logging on to the standby
*** 2013-08-23 19:51:51.403 869 krsu.c
Error 12154 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'HPYMUSIC'
Error 12154 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'HPYMUSIC'
ORA-12154: TNS: 指定された接続識別子を解決できませんでした
*** 2013-08-23 19:51:51.403 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'HPYMUSIC'. Error is 12154.
*** 2013-08-23 19:51:51.403 2747 krsi.c
krsi_dst_fail: dest:2 err:12154 force:0 blast:1
[root@tokyo1 app]#
[grid@tokyo1 shell]$ ./grid_info_east-x.sh
+ export ORACLE_SID=+ASM
+ ORACLE_SID=+ASM
+ LOGDIR=/home/grid/log
+ PRIMARYDB=east_DGMGRL
+ STANDBYDB=
+ PASSWORD=dataguard
+ mkdir -p /home/grid/log
++ date +%y%m%d,%H%M%S
+ echo 'asm info,130823,195709'
+ sqlplus / as sysasm
SQL*Plus: Release 11.2.0.1.0 Production on 金 8月 23 19:57:09 2013
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Automatic Storage Management option
に接続されました。
SQL> SQL>
SYSDATE
13-08-23
SQL> SQL> SQL>
NAME TYPE VALUE
asm_diskgroups string FRA
asm_diskstring string /dev/sd*1
asm_power_limit integer 1
asm_preferred_read_failure_groups string
audit_file_dest string /u01/app/11.2.0/grid/rdbms/audit
audit_sys_operations boolean FALSE
audit_syslog_level string
background_core_dump string partial
background_dump_dest string /u01/app/grid/diag/asm/+asm/+ASM/trace
cluster_database boolean FALSE
cluster_database_instances integer 1
cluster_interconnects string
core_dump_dest string /u01/app/grid/diag/asm/+asm/+ASM/cdump
db_cache_size big integer 0
db_ultra_safe string OFF
db_unique_name string +ASM
diagnostic_dest string /u01/app/grid
event string
file_mapping boolean FALSE
filesystemio_options string none
ifile file
instance_name string +ASM
instance_number integer 1
instance_type string asm
large_pool_size big integer 12M
ldap_directory_sysauth string no
listener_networks string
local_listener string
lock_name_space string
lock_sga boolean FALSE
max_dump_file_size string unlimited
memory_max_target big integer 272M
memory_target big integer 272M
nls_calendar string
nls_comp string BINARY
nls_currency string
nls_date_format string
nls_date_language string
nls_dual_currency string
nls_iso_currency string
nls_language string AMERICAN
nls_length_semantics string BYTE
nls_nchar_conv_excp string FALSE
nls_numeric_characters string
nls_sort string
nls_territory string AMERICA
nls_time_format string
nls_time_tz_format string
nls_timestamp_format string
nls_timestamp_tz_format string
os_authent_prefix string ops$
os_roles boolean FALSE
pga_aggregate_target big integer 0
processes integer 100
remote_listener string
remote_login_passwordfile string EXCLUSIVE
remote_os_authent boolean FALSE
remote_os_roles boolean FALSE
service_names string +ASM
sessions integer 172
sga_max_size big integer 272M
sga_target big integer 0
shadow_core_dump string partial
shared_pool_reserved_size big integer 6081740
shared_pool_size big integer 0
sort_area_size integer 65536
spfile string +DATA/asm/asmparameterfile/registry.253.823204697
sql_trace boolean FALSE
statistics_level string TYPICAL
timed_os_statistics integer 0
timed_statistics boolean TRUE
trace_enabled boolean TRUE
user_dump_dest string /u01/app/grid/diag/asm/+asm/+ASM/trace
workarea_size_policy string AUTO
++ date +%y%m%d,%H%M%S
+ echo 'asmcmd info,130823,195709'
+ asmcmd ls -l
State Type Rebal Name
MOUNTED NORMAL N DATA/
MOUNTED NORMAL N FRA/
+ asmcmd ls -l 'data/asm/*'
Type Redund Striped Time Sys Name
ASMPARAMETERFILE MIRROR COARSE AUG 11 19:00:00 Y REGISTRY.253.823204697
+ asmcmd ls -l 'data/east/*'
Type Redund Striped Time Sys Name
+data/east/CONTROLFILE/:
CONTROLFILE HIGH FINE AUG 12 15:00:00 Y Current.260.823276231
CONTROLFILE HIGH FINE AUG 23 19:00:00 Y Current.270.823277705
+data/east/DATAFILE/:
DATAFILE MIRROR COARSE AUG 12 15:00:00 Y SYSAUX.257.823276133
DATAFILE MIRROR COARSE AUG 23 19:00:00 Y SYSAUX.267.823277615
DATAFILE MIRROR COARSE AUG 12 15:00:00 Y SYSTEM.256.823276131
DATAFILE MIRROR COARSE AUG 23 19:00:00 Y SYSTEM.266.823277615
DATAFILE MIRROR COARSE AUG 12 15:00:00 Y UNDOTBS1.258.823276133
DATAFILE MIRROR COARSE AUG 23 19:00:00 Y UNDOTBS1.268.823277615
DATAFILE MIRROR COARSE AUG 12 15:00:00 Y USERS.259.823276133
DATAFILE MIRROR COARSE AUG 23 19:00:00 Y USERS.269.823277615
+data/east/ONLINELOG/:
ONLINELOG MIRROR COARSE AUG 12 15:00:00 Y group_1.261.823276235
ONLINELOG MIRROR COARSE AUG 12 15:00:00 Y group_2.262.823276241
ONLINELOG MIRROR COARSE AUG 12 15:00:00 Y group_3.263.823276247
+data/east/PARAMETERFILE/:
PARAMETERFILE MIRROR COARSE AUG 23 12:00:00 Y spfile.265.823277967
+data/east/TEMPFILE/:
TEMPFILE MIRROR COARSE AUG 12 15:00:00 Y TEMP.264.823276263
TEMPFILE MIRROR COARSE AUG 23 19:00:00 Y TEMP.274.823277733
N spfileeast.ora => +DATA/EAST/PARAMETERFILE/spfile.265.823277967
+ asmcmd ls -l 'fra/east/*'
Type Redund Striped Time Sys Name
+fra/east/ARCHIVELOG/:
Y 2013_08_12/
Y 2013_08_15/
Y 2013_08_19/
Y 2013_08_22/
Y 2013_08_23/
+fra/east/CONTROLFILE/:
CONTROLFILE HIGH FINE AUG 12 15:00:00 Y Current.256.823276231
CONTROLFILE HIGH FINE AUG 23 19:00:00 Y Current.260.823277707
+fra/east/ONLINELOG/:
ONLINELOG MIRROR COARSE AUG 12 15:00:00 Y group_1.257.823276237
ONLINELOG MIRROR COARSE AUG 23 19:00:00 Y group_10.272.823535727
ONLINELOG MIRROR COARSE AUG 23 19:00:00 Y group_11.273.823535737
ONLINELOG MIRROR COARSE AUG 23 19:00:00 Y group_12.274.823535745
ONLINELOG MIRROR COARSE AUG 23 19:00:00 Y group_13.275.823535757
ONLINELOG MIRROR COARSE AUG 23 19:00:00 Y group_14.276.823535763
ONLINELOG MIRROR COARSE AUG 23 19:00:00 Y group_15.277.823535771
ONLINELOG MIRROR COARSE AUG 12 15:00:00 Y group_2.258.823276245
ONLINELOG MIRROR COARSE AUG 12 15:00:00 Y group_3.259.823276251
ONLINELOG MIRROR COARSE AUG 23 19:00:00 Y group_7.269.823535685
ONLINELOG MIRROR COARSE AUG 23 19:00:00 Y group_8.270.823535695
ONLINELOG MIRROR COARSE AUG 23 19:00:00 Y group_9.271.823535703
+fra/east/STANDBYLOG/:
N standby_group_07.log => +FRA/EAST/ONLINELOG/group_7.269.823535685
N standby_group_08.log => +FRA/EAST/ONLINELOG/group_8.270.823535695
N standby_group_09.log => +FRA/EAST/ONLINELOG/group_9.271.823535703
N standby_group_10.log => +FRA/EAST/ONLINELOG/group_10.272.823535727
N standby_group_11.log => +FRA/EAST/ONLINELOG/group_11.273.823535737
N standby_group_12.log => +FRA/EAST/ONLINELOG/group_12.274.823535745
N standby_group_13.log => +FRA/EAST/ONLINELOG/group_13.275.823535757
N standby_group_14.log => +FRA/EAST/ONLINELOG/group_14.276.823535763
N standby_group_15.log => +FRA/EAST/ONLINELOG/group_15.277.823535771
+ asmcmd find +data 'group*'
+data/EAST/ONLINELOG/group_1.261.823276235
+data/EAST/ONLINELOG/group_2.262.823276241
+data/EAST/ONLINELOG/group_3.263.823276247
+data/HPYMUSIC/ONLINELOG/group_1.271.824213881
+data/HPYMUSIC/ONLINELOG/group_2.272.824213887
+data/HPYMUSIC/ONLINELOG/group_3.273.824213895
+ asmcmd find +data 'spf*'
+data/EAST/PARAMETERFILE/spfile.265.823277967
+data/EAST/spfileeast.ora
+ asmcmd ls -l data/east/CONTROLFILE
Type Redund Striped Time Sys Name
CONTROLFILE HIGH FINE AUG 12 15:00:00 Y Current.260.823276231
CONTROLFILE HIGH FINE AUG 23 19:00:00 Y Current.270.823277705
+ asmcmd find +fra 'group*'
+fra/EAST/ONLINELOG/group_1.257.823276237
+fra/EAST/ONLINELOG/group_10.272.823535727
+fra/EAST/ONLINELOG/group_11.273.823535737
+fra/EAST/ONLINELOG/group_12.274.823535745
+fra/EAST/ONLINELOG/group_13.275.823535757
+fra/EAST/ONLINELOG/group_14.276.823535763
+fra/EAST/ONLINELOG/group_15.277.823535771
+fra/EAST/ONLINELOG/group_2.258.823276245
+fra/EAST/ONLINELOG/group_3.259.823276251
+fra/EAST/ONLINELOG/group_7.269.823535685
+fra/EAST/ONLINELOG/group_8.270.823535695
+fra/EAST/ONLINELOG/group_9.271.823535703
+fra/HPYMUSIC/ONLINELOG/group_1.261.824213883
+fra/HPYMUSIC/ONLINELOG/group_2.262.824213889
+fra/HPYMUSIC/ONLINELOG/group_3.263.824213897
+ asmcmd find +fra 'spf*'
+ asmcmd ls -l fra/east/CONTROLFILE
Type Redund Striped Time Sys Name
CONTROLFILE HIGH FINE AUG 12 15:00:00 Y Current.256.823276231
CONTROLFILE HIGH FINE AUG 23 19:00:00 Y Current.260.823277707
++ date +%y%m%d,%H%M%S
+ echo END,130823,195712
[grid@tokyo1 shell]$
■ 以下、スタンバイ側 ■ ■ ■ ■ ■ ■ ■
export ORACLE_SID=HPYMUSIC
sqlplus / as sysdba
startup nomount pfile='/u01/app/oracle/product/11.2.0/dbhome_1/dbs/pfile_for_standby_HPYMUSIC.txt'
create spfile='+data/west/spfilewest.ora' from pfile='/u01/app/oracle/product/11.2.0/dbhome_1/dbs/pfile_for_standby_HPYMUSIC.txt';
srvctl stop database -d west -f
srvctl start database -d west -o open
srvctl start database -d west -o mount
srvctl start database -d west
startup mount pfile='/u01/app/oracle/product/11.2.0/dbhome_1/dbs/pfile_for_standby_HPYMUSIC.txt'
srvctl start database -d west -o open
srvctl config database -d west
srvctl status database -d west
alter database recover managed standby database disconnect from session;
select name, database_role, open_mode from gv$database;
srvctl modify database -d west -s open
○ spfile を作成する
export ORACLE_SID=HPYMUSIC
sqlplus / as sysdba
startup nomount pfile='/u01/app/oracle/product/11.2.0/dbhome_1/dbs/pfile_for_standby_HPYMUSIC.txt'
create spfile='+data/west/spfilewest.ora' from pfile='/u01/app/oracle/product/11.2.0/dbhome_1/dbs/pfile_for_standby_HPYMUSIC.txt';
○ 落とす
srvctl stop database -d west -f
○ open したいが起動しない( Mounted (Closed) 状態で起動することもある)。
srvctl start database -d west -o open
PRCR-1079 : リソースora.west.dbの起動に失敗しました
CRS-2674: Start of 'ora.west.db' on 'osaka1' failed
○ open したいが起動しない( Mounted (Closed) 状態で起動することもある)。
srvctl start database -d west -o mount
PRCR-1079 : リソースora.west.dbの起動に失敗しました
CRS-2674: Start of 'ora.west.db' on 'osaka1' failed
○ open したいが起動しない( Mounted (Closed) 状態で起動することもある)。
srvctl start database -d west
PRCR-1079 : リソースora.west.dbの起動に失敗しました
CRS-2674: Start of 'ora.west.db' on 'osaka1' failed
○ 起動するがエラーあり( alert_HPYMUSIC.log )
startup mount pfile='/u01/app/oracle/product/11.2.0/dbhome_1/dbs/pfile_for_standby_HPYMUSIC.txt'
[oracle@osaka1 dbs]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on 金 8月 23 19:05:35 2013
Copyright (c) 1982, 2009, Oracle. All rights reserved.
アイドル・インスタンスに接続しました。
SQL> startup mount pfile='/u01/app/oracle/product/11.2.0/dbhome_1/dbs/pfile_for_standby_HPYMUSIC.txt'
ORACLEインスタンスが起動しました。
Total System Global Area 839282688 bytes
Fixed Size 2217992 bytes
Variable Size 515901432 bytes
Database Buffers 314572800 bytes
Redo Buffers 6590464 bytes
データベースがマウントされました。
Error 12154 received logging on to the standby
FAL[client, ARC3]: Error 12154 connecting to HPYMUSIC for fetching gap sequence
Errors in file /u01/app/oracle/diag/rdbms/west/HPYMUSIC/trace/HPYMUSIC_arc3_25690.trc:
ORA-12154: TNS: 指定された接続識別子を解決できませんでした
Errors in file /u01/app/oracle/diag/rdbms/west/HPYMUSIC/trace/HPYMUSIC_arc3_25690.trc:
ORA-12154: TNS: 指定された接続識別子を解決できませんでした
○ open にならず Mounted (Closed) としかなってくれない。
srvctl start database -d west -o open
[oracle@osaka1 dbs]$ srvctl start database -d west -o open
[oracle@osaka1 dbs]$ /u01/app/11.2.0/grid/bin/crsctl status resource -t
NAME TARGET STATE SERVER STATE_DETAILS
Local Resources
ora.DATA.dg
ONLINE ONLINE osaka1
ora.FRA.dg
ONLINE ONLINE osaka1
ora.LISTENER.lsnr
ONLINE ONLINE osaka1
ora.asm
ONLINE ONLINE osaka1 Started
Cluster Resources
ora.cssd
1 ONLINE ONLINE osaka1
ora.diskmon
1 ONLINE ONLINE osaka1
ora.west.db
1 ONLINE INTERMEDIATE osaka1 Mounted (Closed)
○
srvctl config database -d west
srvctl status database -d west
[oracle@osaka1 dbs]$ srvctl config database -d west
一意のデータベース名: west
データベース名: HPYMUSIC
Oracleホーム: /u01/app/oracle/product/11.2.0/dbhome_1
Oracleユーザー: grid
spfile: +data/west/spfilewest.ora
ドメイン:
開始オプション: open
停止オプション: immediate
データベース・ロール: physical_standby
管理ポリシー: AUTOMATIC
ディスク・グループ: DATA,FRA
サービス:
[oracle@osaka1 dbs]$ srvctl status database -d west
データベースは実行中です。
○ mrp プロセスが起動するが、Read Only ではない。
alter database recover managed standby database disconnect from session;
select name, database_role, open_mode from gv$database;
[oracle@osaka1 dbs]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on 金 8月 23 19:33:08 2013
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
に接続されました。
SQL>
SQL> alter database recover managed standby database disconnect from session;
データベースが変更されました。
SQL> select name, database_role, open_mode from gv$database;
NAME DATABASE_ROLE
OPEN_MODE
HPYMUSIC PHYSICAL STANDBY
MOUNTED
[root@osaka1 app]# ps -ef |egrep -i mrp
oracle 26269 1 0 19:33 ? 00:00:00 ora_mrp0_HPYMUSIC
○ modify しても open にならない。
srvctl modify database -d west -s open
[oracle@osaka1 dbs]$ srvctl modify database -d west -s open
[oracle@osaka1 dbs]$ /u01/app/11.2.0/grid/bin/crsctl status resource -t
NAME TARGET STATE SERVER STATE_DETAILS
Local Resources
ora.DATA.dg
ONLINE ONLINE osaka1
ora.FRA.dg
ONLINE ONLINE osaka1
ora.LISTENER.lsnr
ONLINE ONLINE osaka1
ora.asm
ONLINE ONLINE osaka1 Started
Cluster Resources
ora.cssd
1 ONLINE ONLINE osaka1
ora.diskmon
1 ONLINE ONLINE osaka1
ora.west.db
1 ONLINE INTERMEDIATE osaka1 Mounted (Closed)standby 側に、アーカイブログファイルを少し適用すれば open できそうに感じます。
これを解決するためには、以下のエラーを解決するのがよいと思います。
・ORA-12154: TNS: 指定された接続識別子を解決できませんでした
両ノードの tnsnames.ora を確認させて貰えますか?
この推測が間違えていたら再検討しましょう。 -
Unable to open the physical standby in read only (10g)
Hi,
I m trying to create physical standby using RMAN to another server . But at the last step when trying to test Real Time Apply i m unable to open the standby in read only mode.Can Anyone please let me know whats the issue and how to resolve it
SQL> select status from v$instance;
STATUS
MOUNTED
SQL> alter database recover managed standby database using current logfile disconnect from session;
Database altered.
SQL> alter database recover managed standby database cancel;
Database altered.
SQL> alter database open read only;
alter database open read only
ERROR at line 1:
ORA-16004: backup database requires recovery
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1:
'/u01/app/oracle/product/10.2.0/oradata/test1/system.dbf'Hi,
This is a newly created standby. I created just now. Below the o/p requested
In Primary
SQL> set line 200
SQL> set pagesize 200
SQL> col message format a90
SQL> select severity, error_code, to_char(timestamp,'DD-MON-YYYY HH24:MI:SS'), message from v$dataguard_status where dest_id=2;
SEVERITY ERROR_CODE TO_CHAR(TIMESTAMP,'D MESSAGE
Error 12541 04-MAR-2012 11:55:05 PING[ARC1]: Heartbeat failed to connect to standby 'test1'. Error is 12541.
Error 12541 04-MAR-2012 12:00:12 PING[ARC1]: Heartbeat failed to connect to standby 'test1'. Error is 12541.
Error 1034 04-MAR-2012 12:06:25 PING[ARC1]: Heartbeat failed to connect to standby 'test1'. Error is 1034.
Warning 3113 04-MAR-2012 13:21:24 ARC1: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3113)
Warning 3113 04-MAR-2012 13:21:24 ARC1: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
Error 3113 04-MAR-2012 13:21:24 PING[ARC1]: Error 3113 when pinging standby test1.
Warning 3113 04-MAR-2012 13:33:29 ARC1: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3113)
Warning 3113 04-MAR-2012 13:33:29 ARC1: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
Error 3113 04-MAR-2012 13:33:29 PING[ARC1]: Error 3113 when pinging standby test1.
Error 1034 04-MAR-2012 13:39:50 PING[ARC1]: Heartbeat failed to connect to standby 'test1'. Error is 1034.
Error 1034 04-MAR-2012 13:45:29 PING[ARC1]: Heartbeat failed to connect to standby 'test1'. Error is 1034.
Warning 3113 04-MAR-2012 13:57:56 ARC1: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3113)
Warning 3113 04-MAR-2012 13:57:56 ARC1: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
Error 3113 04-MAR-2012 13:57:56 PING[ARC1]: Error 3113 when pinging standby test1.
14 rows selected.
SQL> select ds.dest_id id
, ad.status
, ds.database_mode db_mode
, ad.archiver type
, ds.recovery_mode
, ds.protection_mode
, ds.standby_logfile_count "SRLs"
, ds.standby_logfile_active active
, ds.archived_seq#
from v$archive_dest_status ds
, v$archive_dest ad
where ds.dest_id = ad.dest_id
and ad.status != 'INACTIVE'
order by
ds.dest_id
/ 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
ID STATUS DB_MODE TYPE RECOVERY_MODE PROTECTION_MODE SRLs ACTIVE ARCHIVED_SEQ#
1 VALID OPEN ARCH IDLE MAXIMUM PERFORMANCE 0 0 64
2 VALID UNKNOWN ARCH UNKNOWN MAXIMUM PERFORMANCE 3 0 64In standby
SQL> select thread#,max(sequence#) from v$archived_log where applied='YES' group by thread#;
THREAD# MAX(SEQUENCE#)
1 64
SQL> select thread#,max(sequence#) from v$archived_log group by thread#;
THREAD# MAX(SEQUENCE#)
1 64
SQL> select message from v$dataguard_status;
MESSAGE
ARC0: Archival started
ARC1: Archival started
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
ARC0: Becoming the heartbeat ARCH
Attempt to start background Managed Standby Recovery process
MRP0: Background Managed Standby Recovery process started
Managed Standby Recovery starting Real Time Apply
Media Recovery Waiting for thread 1 sequence 63
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
MESSAGE
RFS[1]: Assigned to RFS process 9880
RFS[1]: Identified database type as 'physical standby'
Media Recovery Log /u01/app/oracle/product/10.2.0/archive/test1/1_63_776981781.arc
Media Recovery Log /u01/app/oracle/product/10.2.0/archive/test1/1_64_776981781.arc
Media Recovery Waiting for thread 1 sequence 65
16 rows selected. -
Issue with physical standby database not in sync with primary
Hi,
I created an physical standby database couple of Hours back . I am trying to keep the standby database in Managed recovery mode to make the standby in sync with primary but it is throwing the below erros. Please share your suggestion ...
SQL> select thread#,max(sequence#) from v$log_history group by thread#;
THREAD# MAX(SEQUENCE#)
1 7
PROCESS STATUS THREAD# SEQUENCE#
ARCH CONNECTED 0 0
ARCH CONNECTED 0 0
RFS OPENING 1 12
ALERT LOG :
Tue Mar 20 07:31:32 2012
alter database recover managed standby database disconnect from session
Tue Mar 20 07:31:32 2012
Attempt to start background Managed Standby Recovery process (PRIMARY)
MRP0 started with pid=18, OS id=16370
Tue Mar 20 07:31:32 2012
MRP0: Background Managed Standby Recovery process started (PRIMARY)
Managed Standby Recovery not using Real Time Apply
parallel recovery started with 8 processes
Media Recovery Log /oracle/STDBY/arch/1_3_777567883.dbf
Tue Mar 20 07:31:39 2012
Completed: alter database recover managed standby database disconnect from session
Tue Mar 20 07:31:54 2012
Incomplete recovery applied all redo ever generated.
Recovery completed through change 9677325080303
Tue Mar 20 07:31:54 2012
MRP0: Media Recovery Complete (PRIMARY)
Tue Mar 20 07:31:55 2012
MRP0: Background Media Recovery process shutdown (PRIMARY)
Thanks,
RakeshHI CKPT,
Thanks for the reply. All the Archives from primary are transferred to the standby by RFS. Also i tried to register the log files manually even but it says already registered. They are no errors in the primary instance alert log file. Please find the log
SEVERITY ERROR_CODE MESSAGE TO_CHAR(TIMESTAMP,'D
Informational 0 ARC0: Archival started 20-MAR-2012 06:51:36
Informational 0 ARC1: Archival started 20-MAR-2012 06:51:36
Informational 0 ARC0: Becoming the 'no FAL' ARCH 20-MAR-2012 06:51:36
Informational 0 ARC0: Becoming the 'no SRL' ARCH 20-MAR-2012 06:51:36
Informational 0 ARC1: Becoming the heartbeat ARCH 20-MAR-2012 06:51:36
Informational 0 Redo Shipping Client Connected as PUBLIC 20-MAR-2012 06:52:07
Informational 0 -- Connected User is Valid 20-MAR-2012 06:52:07
Informational 0 RFS[1]: Assigned to RFS process 15934 20-MAR-2012 06:52:07
Informational 0 RFS[1]: Identified database type as 'physical standby' 20-MAR-2012 06:52:07
Warning 0 RFS[1]: No standby redo logfiles created 20-MAR-2012 06:52:07
Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 06:52:42
Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 06:52:42
Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:52:47
Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 06:52:49
bf
Control 0 MRP0: Media Recovery Complete 20-MAR-2012 06:53:04
Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 06:53:06
Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:53:24
Control 0 Media Recovery Complete 20-MAR-2012 06:53:43
Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 06:54:55
Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 06:54:55
Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:55:00
Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 06:55:01
bf
Control 0 MRP0: Media Recovery Complete 20-MAR-2012 06:55:17
Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 06:55:18
Informational 0 Redo Shipping Client Connected as PUBLIC 20-MAR-2012 07:31:03
Informational 0 -- Connected User is Valid 20-MAR-2012 07:31:03
Informational 0 RFS[2]: Assigned to RFS process 16366 20-MAR-2012 07:31:03
Informational 0 RFS[2]: Identified database type as 'physical standby' 20-MAR-2012 07:31:03
Warning 0 RFS[2]: No standby redo logfiles created 20-MAR-2012 07:31:04
Warning 0 RFS[2]: No standby redo logfiles created 20-MAR-2012 07:31:06
Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 07:31:32
Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 07:31:32
Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 07:31:37
Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 07:31:38
bf
Control 0 MRP0: Media Recovery Complete 20-MAR-2012 07:31:54
Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 07:31:55
36 rows selected.
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /oracle/STDBY/arch/
Oldest online log sequence 13
Next log sequence to archive 0
Current log sequence 14
SQL> ho ls -ltra /oracle/STDBY/arch/
total 3754456
drwxr-xr-x 4 oracle dba 4096 Feb 13 17:38 ..
-rw-r----- 1 oracle dba 908516864 Mar 20 06:37 1_8_777567883.dbf
-rw-r----- 1 oracle dba 770419200 Mar 20 06:40 1_3_777567883.dbf
-rw-r----- 1 oracle dba 757698048 Mar 20 06:41 1_4_777567883.dbf
-rw-r----- 1 oracle dba 5171712 Mar 20 06:41 1_5_777567883.dbf
-rw-r----- 1 oracle dba 1060801024 Mar 20 06:43 1_6_777567883.dbf
-rw-r----- 1 oracle dba 323025920 Mar 20 06:43 1_7_777567883.dbf
-rw-r----- 1 oracle dba 1558016 Mar 20 06:43 1_9_777567883.dbf
-rw-r----- 1 oracle dba 4608 Mar 20 06:43 1_10_777567883.dbf
-rw-r----- 1 oracle dba 1579008 Mar 20 06:52 1_11_777567883.dbf
-rw-r----- 1 oracle dba 11876864 Mar 20 07:31 1_12_777567883.dbf
-rw-r----- 1 oracle dba 2560 Mar 20 07:31 1_13_777567883.dbf
drwxr-xr-x 2 oracle dba 36864 Mar 20 07:31 .
SQL> -
Manual Standby Database (10.2.0.2.0) on Windows 2003 R2
Hi,
We are setting up a standby database on a remote site for a simple oracle DB. As we already have a standby/master for another Oracle DB (from SAP) we want to stay as close as possible as what already exist.
For the SAP Oracle standby, we are copying manualy all archive to the stand by and apply them with brarchive. All is working fine.
For the new standby, we can not use brarchive as there is no SAP install on the standby but we stay with the "manual" copy of the archive from the master to the standby (using robocpy). It means all archive are on the standby (K:\oracle\oradata\archive).
The creation of the standby DB seems to be OK as i can open it, but i can't manage to apply de redo logs.
I'm quite new to oracle, so it's maybe a very basic issue, but i've already spent 3 days on it...
To start the DB, we lauch a bat script :
sqlplus /nolog @c:\backup\standby.sql
pause
the standby.sql:
connect /@TECDB01 as sysdba
startup nomount;
alter database mount standby database;
exit;
Then i connect to sqlplus and enter:
alter database recover managed standby database;
In another sqlplus session :
SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
wich give me :
PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
MR(fg) WAIT_FOR_GAP 1 45400 0 0
RFS IDLE 0 0 0 0
The sequence 45400 seems to be ok regarding the time of the backup restored on the standby.
The archive is well on the server, but it won't apply it.
The Alert_TECDB01.log :
Fri Oct 29 11:03:43 2010
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =121
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.2.0.
System parameters with non-default values:
processes = 999
sga_target = 7214202880
control_files = I:\ORACLE\ORADATA\CNTRL\STANDBY.CTL, J:\ORACLE\ORADATA\CNTRL\STANDBY.CTL, K:\ORACLE\ORADATA\CNTRL\STANDBY.CTL
db_block_size = 8192
compatible = 10.2.0.2.0
log_archive_dest_1 = LOCATION=K:\oracle\oradata\archive
log_archive_dest_2 = SERVICE=TECDB01
log_archive_dest_state_1 = enable
log_archive_dest_state_2 = enable
standby_archive_dest = K:\oracle\oradata\archive
archive_lag_target = 1800
db_file_multiblock_read_count= 16
undo_management = AUTO
undo_tablespace = RBS
undo_retention = 10800
recyclebin = OFF
remote_login_passwordfile= EXCLUSIVE
db_domain = WORLD
dispatchers = (ADDRESS=(PROTOCOL=tcp)(HOST=xxx.xxx.xxx.92))(DISPATCHERS=4)(CONNECTIONS=1000)
shared_servers = 100
local_listener = (ADDRESS=(PROTOCOL=TCP)(HOST=xxx.xxx.xxx.92)(PORT=1521))
session_cached_cursors = 300
utl_file_dir = \\srvuniway.vrithoff.srwt.tec-wl.be\hotspots
job_queue_processes = 10
audit_file_dest = I:\ORACLE\ADMIN\TECDB01\ADUMP
background_dump_dest = I:\ORACLE\ADMIN\TECDB01\BDUMP
user_dump_dest = I:\ORACLE\ADMIN\TECDB01\UDUMP
core_dump_dest = I:\ORACLE\ADMIN\TECDB01\CDUMP
db_name = TECDB01
open_cursors = 3000
pga_aggregate_target = 1086324736
PMON started with pid=2, OS id=4012
PSP0 started with pid=3, OS id=3856
MMAN started with pid=4, OS id=3580
DBW0 started with pid=5, OS id=1084
LGWR started with pid=6, OS id=576
CKPT started with pid=7, OS id=3516
SMON started with pid=8, OS id=508
RECO started with pid=9, OS id=3068
CJQ0 started with pid=10, OS id=2448
MMON started with pid=11, OS id=2840
MMNL started with pid=12, OS id=3024
Fri Oct 29 11:03:44 2010
starting up 4 dispatcher(s) for network address '(ADDRESS=(PROTOCOL=tcp)(HOST=xxx.xxx.xxx.92))'...
starting up 100 shared server(s) ...
Fri Oct 29 11:03:45 2010
alter database mount standby database
Fri Oct 29 11:03:51 2010
Setting recovery target incarnation to 2
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=118, OS id=3584
Fri Oct 29 11:03:51 2010
ARC0: Archival started
ARC1 started with pid=119, OS id=3688
Fri Oct 29 11:03:51 2010
ARC1: Archival started
ARCH: STARTING ARCH PROCESSES COMPLETE
Fri Oct 29 11:03:51 2010
ARC0: Becoming the 'no FAL' ARCH
Fri Oct 29 11:03:51 2010
Successful mount of redo thread 1, with mount id 3987142355
Fri Oct 29 11:03:51 2010
ARC0: Becoming the 'no SRL' ARCH
Fri Oct 29 11:03:51 2010
ARC1: Becoming the heartbeat ARCH
Fri Oct 29 11:03:51 2010
Physical Standby Database mounted.
Completed: alter database mount standby database
Fri Oct 29 11:04:06 2010
alter database recover managed standby database
Fri Oct 29 11:04:06 2010
Managed Standby Recovery not using Real Time Apply
parallel recovery started with 7 processes
Media Recovery Waiting for thread 1 sequence 45400
Fetching gap sequence in thread 1, gap sequence 45400-45499
+FAL[client]: Error fetching gap sequence, no FAL server specified+
Fri Oct 29 11:04:37 2010
+FAL[client]: Failed to request gap sequence+
GAP - thread 1 sequence 45400-45499
DBID 3776455083 branch 670241032
+FAL[client]: All defined FAL servers have been attempted.+
Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
parameter is defined to a value that is sufficiently large
enough to maintain adequate log switch information to resolve
archivelog gaps.
Fri Oct 29 11:04:51 2010
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[1]: Assigned to RFS process 3452
RFS[1]: Identified database type as 'physical standby'
Fri Oct 29 11:04:51 2010
RFS LogMiner: Client disabled from further notification
The tecdb01_arc1_3688.trc :
Dump file i:\oracle\admin\tecdb01\bdump\tecdb01_arc1_3688.trc
Fri Oct 29 11:03:51 2010
ORACLE V10.2.0.2.0 - 64bit Production vsnsta=0
vsnsql=14 vsnxtr=3
Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
Windows NT Version V5.2 Service Pack 2
CPU : 8 - type 8664, 2 Physical Cores
Process Affinity : 0x0000000000000000
Memory (Avail/Total): Ph:7467M/9215M, PhPgF:2454M/10796M+
Instance name: tecdb01
Redo thread mounted by this instance: 1
Oracle process number: 119
Windows thread id: 3688, image: ORACLE.EXE (ARC1)
*** SERVICE NAME:() 2010-10-29 11:03:51.177
*** SESSION ID:(1088.1) 2010-10-29 11:03:51.177
kcrrwkx: nothing to do (start)
*** 2010-10-29 11:04:51.129
Redo shipping client performing standby login
*** 2010-10-29 11:04:51.176 64529 kcrr.c
Logged on to standby successfully
Client logon and security negotiation successful!
kcrrwkx: nothing to do (end)
*** 2010-10-29 11:05:51.285
kcrrwkx: nothing to do (end)
*** 2010-10-29 11:06:51.300
kcrrwkx: nothing to do (end)
The initTECDB01.ora :
# Copyright (c) 1991, 2001, 2002 by Oracle Corporation
# Archive
archive_lag_target=1800
log_archive_dest_1='LOCATION=K:\oracle\oradata\archive'
# Cache and I/O
db_block_size=8192
db_file_multiblock_read_count=16
# Cursors and Library Cache
open_cursors=3000
session_cached_cursors=300
# Database Identification
db_domain=WORLD
db_name=TECDB01
# Diagnostics and Statistics
background_dump_dest=I:\oracle\admin\TECDB01\bdump
core_dump_dest=I:\oracle\admin\TECDB01\cdump
user_dump_dest=I:\oracle\admin\TECDB01\udump
# File Configuration
control_files=("I:\oracle\oradata\cntrl\standby.ctl", "J:\oracle\oradata\cntrl\standby.ctl", "K:\oracle\oradata\cntrl\standby.ctl")
# Job Queues
job_queue_processes=10
# Miscellaneous
compatible=10.2.0.2.0
recyclebin=OFF
# Processes and Sessions
processes=999
# SGA Memory
sga_target=6880M
# Pools
#java_pool_size=150M
# Security and Auditing
audit_file_dest=I:\oracle\admin\TECDB01\adump
remote_login_passwordfile=EXCLUSIVE
# Shared Server
shared_servers=100
dispatchers="(ADDRESS=(PROTOCOL=tcp)(HOST=xxx.xxx.xxx.92))(DISPATCHERS=4)(CONNECTIONS=1000)"
#dispatchers="(PROTOCOL=TCP) (SERVICE=TECDB01XDB)"
# Sort, Hash Joins, Bitmap Indexes
pga_aggregate_target=1036M
# System Managed Undo and Rollback Segments
undo_management=AUTO
undo_retention=10800
undo_tablespace=RBS
local_listener="(ADDRESS=(PROTOCOL=TCP)(HOST=xxx.xxx.xxx.92)(PORT=1521))"
# NIDA - 28.10.2010 - redo apply
log_archive_dest_state_1=enable
log_archive_dest_2 = 'SERVICE=TECDB01'
log_archive_dest_state_2=enable
#standby_file_management=auto
standby_archive_dest=K:\oracle\oradata\archive
And the TNSNAMES.ora :
# tnsnames.ora Network Configuration File: C:\oracle\102\network\admin\tnsnames.ora
# Generated by Oracle configuration tools.
#this is the standby
TECDB01.VRITHOFF.SRWT.TEC-WL.BE =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = xxx.xxx.xxx.92)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = TECDB01)
# This file is written by Oracle Services For MSCS
# on Sat Nov 08 10:44:27 2008
#this is the master
PRIMARY.VRITHOFF.SRWT.TEC-WL.BE =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = xxx.xxx.xxx.246)(PORT = 1521))
(CONNECT_DATA =
(SID = TECDB01)
EXTPROC_CONNECTION_DATA.VRITHOFF.SRWT.TEC-WL.BE =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = TECDB01))
(CONNECT_DATA =
(SERVICE_NAME = TECDB01)
Hope you have all information to bring me in the right way.
Regards,
NicolasHi,
The recover automatic is working fine, but I still have problems with the recover managed
Here is the Alert log :(the 46626 was there at 11:30)
Mon Nov 15 11:31:13 2010
alter database recover managed standby database using current logfile
Managed Standby Recovery starting Real Time Apply
parallel recovery started with 7 processes
Media Recovery Waiting for thread 1 sequence 46626
Mon Nov 15 16:36:01 2010
alter database recover managed standby database cancel
Mon Nov 15 16:36:05 2010
Managed Standby Recovery not using Real Time Apply
Recovery interrupted!
Mon Nov 15 16:36:06 2010
Media Recovery user canceled with status 16037
ORA-16043 signalled during: alter database recover managed standby database using current logfile...
Mon Nov 15 16:36:07 2010
Completed: alter database recover managed standby database cancel
Mon Nov 15 16:36:37 2010
ALTER DATABASE RECOVER automatic standby database until time'2010-11-15:15:50:00'
Mon Nov 15 16:36:37 2010
Media Recovery Start
Managed Standby Recovery not using Real Time Apply
parallel recovery started with 7 processes
Mon Nov 15 16:36:39 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46626_0670241032.001
Mon Nov 15 16:36:45 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46627_0670241032.001
Mon Nov 15 16:37:11 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46628_0670241032.001
Mon Nov 15 16:37:30 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46629_0670241032.001
Mon Nov 15 16:37:48 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46630_0670241032.001
Mon Nov 15 16:37:59 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46631_0670241032.001
Mon Nov 15 16:38:15 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46632_0670241032.001
Mon Nov 15 16:38:28 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46633_0670241032.001
Mon Nov 15 16:38:47 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46634_0670241032.001
Mon Nov 15 16:39:34 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46635_0670241032.001
Mon Nov 15 16:40:43 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46636_0670241032.001
Mon Nov 15 16:42:03 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46637_0670241032.001
Mon Nov 15 16:43:18 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46638_0670241032.001
Mon Nov 15 16:44:38 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46639_0670241032.001
Mon Nov 15 16:45:45 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46640_0670241032.001
Mon Nov 15 16:46:37 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46641_0670241032.001
Mon Nov 15 16:47:48 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46642_0670241032.001
Mon Nov 15 16:49:07 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46643_0670241032.001
Mon Nov 15 16:50:04 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46644_0670241032.001
Mon Nov 15 16:51:13 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46645_0670241032.001
Mon Nov 15 16:52:16 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46646_0670241032.001
Mon Nov 15 16:53:07 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46647_0670241032.001
Mon Nov 15 16:54:28 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46648_0670241032.001
Mon Nov 15 16:55:47 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46649_0670241032.001
Mon Nov 15 16:56:35 2010
Incomplete Recovery applied until change 4037420604
Completed: ALTER DATABASE RECOVER automatic standby database until time'2010-11-15:15:50:00'
I don't catch why the system wait for a sequence that is available...
Regards,
Nico -
How to verify that standby and primary are working correctly or not
Hi,
Oracle Version : 10.2.0.1.0
OperatingSystem : WindowsXp
I have configured a stand by database on my local database.Here i would like to know weather by stand by is configured correctly and working fine are not.
Please help me.
Thank & Regards
Poorna Prasad.Hi,
When i issue these statements in my primary database the output is like this
SQL> SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
SEQUENCE# FIRST_TIM NEXT_TIME
169 19-AUG-09 20-AUG-09
170 20-AUG-09 20-AUG-09
171 20-AUG-09 20-AUG-09
172 20-AUG-09 20-AUG-09
173 20-AUG-09 20-AUG-09
174 20-AUG-09 21-AUG-09
175 21-AUG-09 21-AUG-09
176 21-AUG-09 22-AUG-09
177 22-AUG-09 22-AUG-09
178 22-AUG-09 23-AUG-09
179 23-AUG-09 23-AUG-09
SEQUENCE# FIRST_TIM NEXT_TIME
180 23-AUG-09 24-AUG-09
180 23-AUG-09 24-AUG-09
181 24-AUG-09 24-AUG-09
181 24-AUG-09 24-AUG-09
182 24-AUG-09 24-AUG-09
182 24-AUG-09 24-AUG-09
183 24-AUG-09 24-AUG-09
183 24-AUG-09 24-AUG-09
184 24-AUG-09 24-AUG-09
184 24-AUG-09 24-AUG-09
185 24-AUG-09 24-AUG-09
SEQUENCE# FIRST_TIM NEXT_TIME
185 24-AUG-09 24-AUG-09
186 24-AUG-09 25-AUG-09
186 24-AUG-09 25-AUG-09
187 25-AUG-09 25-AUG-09
187 25-AUG-09 25-AUG-09
188 25-AUG-09 25-AUG-09
188 25-AUG-09 25-AUG-09
189 25-AUG-09 25-AUG-09
190 25-AUG-09 25-AUG-09
31 rows selected.
SQL> select * from v$dataguard_status;
FACILITY SEVERITY DEST_ID MESSAGE_NUM ERROR_CODE CAL TIMESTAMP MESSAGE
Log Transport Services Informational 0 1 0 NO 25-AUG-09 ARC0: Archival started
Log Transport Services Informational 0 2 0 NO 25-AUG-09 ARC1: Archival started
Log Transport Services Informational 0 3 0 NO 25-AUG-09 ARC2: Archival started
Log Transport Services Informational 0 4 0 NO 25-AUG-09 ARC3: Archival started
Log Transport Services Informational 0 5 0 NO 25-AUG-09 ARC4: Archival started
Log Transport Services Informational 0 6 0 NO 25-AUG-09 ARC5: Archival started
Log Transport Services Informational 0 7 0 NO 25-AUG-09 ARC6: Archival started
Log Transport Services Informational 0 8 0 NO 25-AUG-09 ARC7: Archival started
Log Transport Services Informational 0 9 0 NO 25-AUG-09 ARC8: Archival started
Log Transport Services Informational 0 10 0 NO 25-AUG-09 ARC9: Archival started
Log Transport Services Informational 0 11 0 NO 25-AUG-09 ARCa: Archival started
FACILITY SEVERITY DEST_ID MESSAGE_NUM ERROR_CODE CAL TIMESTAMP MESSAGE
Log Transport Services Informational 0 12 0 NO 25-AUG-09 ARCb: Archival started
Log Transport Services Informational 0 13 0 NO 25-AUG-09 ARCc: Archival started
Log Transport Services Informational 0 14 0 NO 25-AUG-09 ARCd: Archival started
Log Transport Services Informational 0 15 0 NO 25-AUG-09 ARCe: Archival started
Log Transport Services Informational 0 16 0 NO 25-AUG-09 ARCf: Archival started
Log Transport Services Informational 0 17 0 NO 25-AUG-09 ARCg: Archival started
Log Transport Services Informational 0 18 0 NO 25-AUG-09 ARCh: Archival started
Log Transport Services Informational 0 19 0 NO 25-AUG-09 ARCi: Archival started
Log Transport Services Informational 0 20 0 NO 25-AUG-09 ARCj: Archival started
Log Transport Services Informational 0 21 0 NO 25-AUG-09 ARCk: Archival started
Log Transport Services Informational 0 22 0 NO 25-AUG-09 ARCl: Archival started
FACILITY SEVERITY DEST_ID MESSAGE_NUM ERROR_CODE CAL TIMESTAMP MESSAGE
Log Transport Services Informational 0 23 0 NO 25-AUG-09 ARCm: Archival started
Log Transport Services Informational 0 24 0 NO 25-AUG-09 ARCn: Archival started
Log Transport Services Informational 0 25 0 NO 25-AUG-09 ARCo: Archival started
Log Transport Services Informational 0 26 0 NO 25-AUG-09 ARCp: Archival started
Log Transport Services Informational 0 27 0 NO 25-AUG-09 ARCq: Archival started
Log Transport Services Informational 0 28 0 NO 25-AUG-09 ARCr: Archival started
Log Transport Services Informational 0 29 0 NO 25-AUG-09 ARCs: Archival started
Log Transport Services Informational 0 30 0 NO 25-AUG-09 ARCt: Archival started
Log Transport Services Informational 0 31 0 NO 25-AUG-09 ARCi: Becoming the 'no FAL' ARCH
Log Transport Services Informational 0 32 0 NO 25-AUG-09 ARCi: Becoming the 'no SRL' ARCH
Log Transport Services Informational 0 33 0 NO 25-AUG-09 ARCl: Becoming the heartbeat ARCH
FACILITY SEVERITY DEST_ID MESSAGE_NUM ERROR_CODE CAL TIMESTAMP MESSAGE
Log Transport Services Error 0 34 1017 YES 25-AUG-09 Error 1017 received logging on to the standby
Fetch Archive Log Error 2 35 16191 YES 25-AUG-09 FAL[server, ARC0]: Error 16191 creating remote archivelog file 'stand'
Log Transport Services Error 0 36 1017 YES 25-AUG-09 Error 1017 received logging on to the standby
Log Transport Services Error 2 37 16191 YES 25-AUG-09 PING[ARCl]: Heartbeat failed to connect to standby 'stand'. Error is 16191.
Log Transport Services Error 0 38 1017 YES 25-AUG-09 Error 1017 received logging on to the standby
Log Transport Services Error 2 39 16191 YES 25-AUG-09 PING[ARCl]: Heartbeat failed to connect to standby 'stand'. Error is 16191.
Log Transport Services Error 0 40 1017 YES 25-AUG-09 Error 1017 received logging on to the standby
Log Transport Services Error 2 41 16191 YES 25-AUG-09 PING[ARCl]: Heartbeat failed to connect to standby 'stand'. Error is 16191.
Log Transport Services Error 0 42 12518 YES 25-AUG-09 Error 12518 received logging on to the standby
Log Transport Services Error 2 43 12518 YES 25-AUG-09 PING[ARCl]: Heartbeat failed to connect to standby 'stand'. Error is 12518.
Log Transport Services Error 0 44 1017 YES 25-AUG-09 Error 1017 received logging on to the standby
FACILITY SEVERITY DEST_ID MESSAGE_NUM ERROR_CODE CAL TIMESTAMP MESSAGE
Log Transport Services Error 2 45 16191 YES 25-AUG-09 PING[ARCl]: Heartbeat failed to connect to standby 'stand'. Error is 16191.
Log Transport Services Error 0 46 1017 YES 25-AUG-09 Error 1017 received logging on to the standby
Log Transport Services Error 2 47 16191 YES 25-AUG-09 PING[ARCl]: Heartbeat failed to connect to standby 'stand'. Error is 16191.
Log Transport Services Error 0 48 1017 YES 25-AUG-09 Error 1017 received logging on to the standby
Log Transport Services Error 2 49 16191 YES 25-AUG-09 PING[ARCl]: Heartbeat failed to connect to standby 'stand'. Error is 16191.
Log Transport Services Error 0 50 1017 YES 25-AUG-09 Error 1017 received logging on to the standby
Log Transport Services Error 2 51 16191 YES 25-AUG-09 PING[ARCl]: Heartbeat failed to connect to standby 'stand'. Error is 16191.
Log Transport Services Error 0 52 1017 YES 25-AUG-09 Error 1017 received logging on to the standby
Log Transport Services Error 2 53 16191 YES 25-AUG-09 PING[ARCl]: Heartbeat failed to connect to standby 'stand'. Error is 16191.
Log Transport Services Error 0 54 1017 YES 25-AUG-09 Error 1017 received logging on to the standby
Log Transport Services Error 2 55 16191 YES 25-AUG-09 PING[ARCl]: Heartbeat failed to connect to standby 'stand'. Error is 16191.
FACILITY SEVERITY DEST_ID MESSAGE_NUM ERROR_CODE CAL TIMESTAMP MESSAGE
Log Transport Services Error 0 56 1017 YES 25-AUG-09 Error 1017 received logging on to the standby
Log Transport Services Error 2 57 16191 YES 25-AUG-09 PING[ARCl]: Heartbeat failed to connect to standby 'stand'. Error is 16191.
Log Transport Services Error 0 58 1017 YES 25-AUG-09 Error 1017 received logging on to the standby
Log Transport Services Error 2 59 16191 YES 25-AUG-09 PING[ARCl]: Heartbeat failed to connect to standby 'stand'. Error is 16191.
Log Transport Services Error 0 60 1017 YES 25-AUG-09 Error 1017 received logging on to the standby
Log Transport Services Error 2 61 16191 YES 25-AUG-09 PING[ARCl]: Heartbeat failed to connect to standby 'stand'. Error is 16191.
Log Transport Services Error 0 62 1017 YES 25-AUG-09 Error 1017 received logging on to the standby
Log Transport Services Error 2 63 16191 YES 25-AUG-09 PING[ARCl]: Heartbeat failed to connect to standby 'stand'. Error is 16191.
Log Transport Services Error 0 64 1017 YES 25-AUG-09 Error 1017 received logging on to the standby
Log Transport Services Error 2 65 16191 YES 25-AUG-09 PING[ARCl]: Heartbeat failed to connect to standby 'stand'. Error is 16191.
Log Transport Services Error 0 66 1017 YES 25-AUG-09 Error 1017 received logging on to the standby
FACILITY SEVERITY DEST_ID MESSAGE_NUM ERROR_CODE CAL TIMESTAMP MESSAGE
Log Transport Services Error 2 67 16191 YES 25-AUG-09 PING[ARCl]: Heartbeat failed to connect to standby 'stand'. Error is 16191.and when i issue these statements in my stand by the output is.
SQL> select * from V$managed_standby;
PROCESS PID STATUS CLIENT_P CLIENT_PID CLIENT_DBID GROUP# RESETLOG_ID THREAD# SEQUENCE# BLOCK# BLOCKS DELAY_MINS KNOWN_AGENTS ACTIVE_AGENTS
ARCH 4504 CONNECTED ARCH 4504 1560521699 N/A 0 0 0 0 0 0 0 0
ARCH 3440 CONNECTED ARCH 3440 1560521699 N/A 0 0 0 0 0 0 0 0
ARCH 5504 CONNECTED ARCH 5504 1560521699 N/A 0 0 0 0 0 0 0 0
ARCH 5352 CONNECTED ARCH 5352 1560521699 N/A 0 0 0 0 0 0 0 0
ARCH 5344 CONNECTED ARCH 5344 1560521699 N/A 0 0 0 0 0 0 0 0
ARCH 1320 CONNECTED ARCH 1320 1560521699 N/A 0 0 0 0 0 0 0 0
ARCH 5088 CONNECTED ARCH 5088 1560521699 N/A 0 0 0 0 0 0 0 0
ARCH 3416 CONNECTED ARCH 3416 1560521699 N/A 0 0 0 0 0 0 0 0
ARCH 5916 CONNECTED ARCH 5916 1560521699 N/A 0 0 0 0 0 0 0 0
ARCH 5776 CONNECTED ARCH 5776 1560521699 N/A 0 0 0 0 0 0 0 0
ARCH 4744 CONNECTED ARCH 4744 1560521699 N/A 0 0 0 0 0 0 0 0
PROCESS PID STATUS CLIENT_P CLIENT_PID CLIENT_DBID GROUP# RESETLOG_ID THREAD# SEQUENCE# BLOCK# BLOCKS DELAY_MINS KNOWN_AGENTS ACTIVE_AGENTS
ARCH 1144 CONNECTED ARCH 1144 1560521699 N/A 0 0 0 0 0 0 0 0
ARCH 5900 CONNECTED ARCH 5900 1560521699 N/A 0 0 0 0 0 0 0 0
ARCH 4848 CONNECTED ARCH 4848 1560521699 N/A 0 0 0 0 0 0 0 0
ARCH 5560 CONNECTED ARCH 5560 1560521699 N/A 0 0 0 0 0 0 0 0
ARCH 4672 CONNECTED ARCH 4672 1560521699 N/A 0 0 0 0 0 0 0 0
ARCH 400 CONNECTED ARCH 400 1560521699 N/A 0 0 0 0 0 0 0 0
ARCH 4996 CONNECTED ARCH 4996 1560521699 N/A 0 0 0 0 0 0 0 0
ARCH 5356 CONNECTED ARCH 5356 1560521699 N/A 0 0 0 0 0 0 0 0
ARCH 5800 CONNECTED ARCH 5800 1560521699 N/A 0 0 0 0 0 0 0 0
ARCH 3104 CONNECTED ARCH 3104 1560521699 N/A 0 0 0 0 0 0 0 0
ARCH 6100 CONNECTED ARCH 6100 1560521699 N/A 0 0 0 0 0 0 0 0
PROCESS PID STATUS CLIENT_P CLIENT_PID CLIENT_DBID GROUP# RESETLOG_ID THREAD# SEQUENCE# BLOCK# BLOCKS DELAY_MINS KNOWN_AGENTS ACTIVE_AGENTS
ARCH 2400 CONNECTED ARCH 2400 1560521699 N/A 0 0 0 0 0 0 0 0
ARCH 3712 CONNECTED ARCH 3712 1560521699 N/A 0 0 0 0 0 0 0 0
ARCH 4248 CONNECTED ARCH 4248 1560521699 N/A 0 0 0 0 0 0 0 0
ARCH 5580 CONNECTED ARCH 5580 1560521699 N/A 0 0 0 0 0 0 0 0
ARCH 3160 CONNECTED ARCH 3160 1560521699 N/A 0 0 0 0 0 0 0 0
ARCH 4436 CONNECTED ARCH 4436 1560521699 N/A 0 0 0 0 0 0 0 0
ARCH 5116 CONNECTED ARCH 5116 1560521699 N/A 0 0 0 0 0 0 0 0
ARCH 1488 CONNECTED ARCH 1488 1560521699 N/A 0 0 0 0 0 0 0 0
MRP0 4464 WAIT_FOR_LOG N/A N/A N/A N/A 687453795 1 189 0 0 0 0 0
31 rows selected.Regards
Poorna -
Use of arc processess in standby location
Hi,
What is the use of archive processes in standby database when the log shipping is done by arch process.Sekar_BLUE4EVER wrote:
Hi,
What is the use of archive processes in standby database when the log shipping is done by arch process.Standby redo logs must be archived before the data can be applied to the standby database. The standby archival operation occurs automatically, even if the standby database is not in ARCHIVELOG mode. However, the archive process must be started on the standby database. Note that the use of the archiver process (ARCn) is a requirement for selection of a standby redo log.
Source:http://www.orafaq.com/node/957
...archive processes are responsible for archiving the ORL files as they become full and for resolving gaps in the redo stream to a standby database and on a standby database they are responsible for archiving the SRL files and forwarding the archive logs to a cascaded standby database.
Source:http://www.datadisk.co.uk/html_docs/oracle_dg/physical_setup.htm
Please read above lines at least 2 times, but slowly...
Regards
Girish Sharma -
MV Logs not getting purged in a Logical Standby Database
We are trying to replicate a few tables in a logical standby database to another database. Both the source ( The Logical Standby) and the target database are in Oracle 11g R1.
The materialized views are refreshed using FAST REFRESH.
The Materialized View Logs created on the source ( the Logical Standby Database) are not getting purged when the MV in the target database is refreshed.
We checked the entries in the following Tables: SYS.SNAP$, SYS.SLOG$, SYS.MLOG$
When a materialized view is created on the target database, a record is not inserted into the SYS.SLOG$ table and it seems like that's why the MV Logs are not getting purged.
Why are we using a Logical Standby Database instead of the Primary ? Because, the load on the Primary Database is too much and the machine doesn't have enough resources to support MV based replication. The CPU usage is 95% all the time. The appplication owner won't allow us to go against the Primary database.
Do we have to do anything different in terms of Configuration/Privileges etc. because we are using a Logical Standby Database as a source ?
Thanks in Advance.We have a 11g RAC database in solaris OS where there is huge gap in archive log apply.
Thread Last Sequence Received Last Sequence Applied Difference
1 132581 129916 2665
2 108253 106229 2024
3 107452 104975 2477
The MRP0 process seems not to be working also.Almost 7000+ archives lag in standby if compared with primary database.
i suggest you to go with Incremental rollforward backups to make it SYNC, use this below link for step by step procedure.
http://www.oracle-ckpt.com/rman-incremental-backups-to-roll-forward-a-physical-standby-database-2/
Here questions.
1) Whether those archives are transported & just not applied?
2) Is in production do you have archives or backup of archives?
3) What you have found errors in alert log file?
post
SQL> select severity,message,error_code,timestamp from v$dataguard_status where dest_id=2;
4) What errors in primary database alert log file?
Also post
select ds.dest_id id
, ad.status
, ds.database_mode db_mode
, ad.archiver type
, ds.recovery_mode
, ds.protection_mode
, ds.standby_logfile_count "SRLs"
, ds.standby_logfile_active active
, ds.archived_seq#
from v$archive_dest_status ds
, v$archive_dest ad
where ds.dest_id = ad.dest_id
and ad.status != 'INACTIVE'
order by
ds.dest_id
/Also check errors from standby database. -
How Real Time Apply works while physical standby is open in Read Only mode
Hi,
With Active data guard option, we can open physical standby DB in read only mode, while redo log are being applied. (Real Time Query)
Standby Redo log (SRL) enables Real Time Apply (with "USING CURRENT LOGFILE" clause in recover database command on standby DB)
I am interested to know, how Real Time Query works ?
What is the mechanism with allows us to open physical standby DB in read only mode while redo logs are being applied continuously ?
Regards,
SujitDear user7419391,
That is a new feature in Oracle Database 11g. MRP can use the real time apply in 10g but the concept here is different.
Taken from the following document;
http://www.ascent.co.za/documents/oracle/Oracle%20databse%2011g%20Active-Data-Guard%20datasheet.pdf
*Unique Advantages of Oracle Active Data Guard*
+Active Data Guard is an evolution of Data Guard technology, providing unique+
+performance advantages while leveraging all other enhancements included in Oracle+
+Data Guard 11g. For example, any Data Guard 11g physical standby database can+
+be easily converted to a Snapshot Standby. A Snapshot Standby is open read-write+
+and is ideally suited as a test system, able to process transactions independent of the+
+primary database. A Snapshot Standby maintains protection by continuing to receive+
+data from the production database, archiving it for later use. When tests are+
+complete, a single command discards changes made while open read-write and+
+quickly resynchronizes the standby database with the primary.+
The other link in the previous post is excellent and you really have to read it to understand the active data guard aspects.
Regards.
Ogan
Maybe you are looking for
-
How can I make sure my data add on doesn't automatically renew?
I bought the 1.99 100 MB of data, don't want this to anutorenew, how can i stop it from doing that?
-
I have photoshop CC. I cannot open two files such as Tiffs and view them side by side. When I open the second file it overrides the first. Do I need to do something with preferences?
-
Was Reports Developer 6.0 (not 6i) released for Oracle 8.0.3 to 8.0.6 (not 8i)? Thanks
-
How do I add font to a photo using iPhoto?
-
Hi Guys, We are developing a Email engine using Oracle. Can any one of you guys help us on this problem. How do I get the delivery status of an email. If I send an email from Oralce, I wish to know the delivery status of that particular email. Thanks