Standby database creation notes by metalink

Can any body send me good Standby database creation notes by metalink.

Are you wanting to see notes for physical or logical standby and what Database version and OS?
Use the knowledge browser in Metalink and click the database link in the Support Categories section on the left of the page and select Dataguard under the High Availability Section on the resulting page.

Similar Messages

Physical Standby Database Creation with RMAN

Hi,
I'm in 10g on Linux. I want to create a standby database on another Linux server. I did not find a clear procedure to create it in Oracle® Database Backup and Recovery Advanced User's Guide 10g Release 2 (10.2) Part Number B14191-02
and niether in Oracle® Data Guard Concepts and Administration 10g Release 2 (10.2) B14239-04
In the last one chapter 3 sends you to F appendix and F appendix says do nothing before having than all in chapter 3 :
In F.1.1 page F-2 it is said :
See Chapter 3 for a complete discussion of physical standby database preparation,including initialization parameter settings. You must perform all necessary preparation tasks described in these chapters before RMAN can successfully create the standby database files and mount the standby database.
Any way I'm looking for a procedure or clear article to create it.
Many thanks before.

Physical Standby Database Creation with RMAN
Use the DUPLICATE command.
Check out this metalink doc: Note:374069.1 and Note:118409.1
Message was edited by:
STW
Message was edited by:
STW

ORA-16821: logical standby database dictionary not yet loaded

Dear all,
I have a dataguard architecture with a primary and a standby database (for reporting stuffs). Since I upgraded physical standby to logical standby, I receive this error !
ORA-16821: logical standby database dictionary not yet loaded
If someone has an idea, should be great !!
Thanks
oldschool

Hi,
Ok I applied :
SQL> ALTER DATABASE STOP LOGICAL STANDBY APPLY;
Database altered.
SQL> alter database start logical standby apply immediate;
Database altered.
SQL>
And now I received this :
ORA-16825: Fast-Start Failover and other errors or warnings detected for the database
Cause: The broker has detected multiple errors or warnings for the database. At least one of the detected errors or warnings may prevent a Fast-Start Failover from occurring.
Action: Check the StatusReport monitorable property of the database specified.
What does it mean to check the status report.....
I found this about monitorable status report !!
DGMGRL> show database 'M3RPT' 'StatusReport';
STATUS REPORT
INSTANCE_NAME SEVERITY ERROR_TEXT
* WARNING ORA-16821: logical standby database dictionary not yet loaded
DGMGRL>
What can I do ?
Thanks a lot
oldschool
Edited by: oldschool on Jun 4, 2009 2:37 AM

Add new datafile to logical standby database but not in primary

Hi,
Is it ok to add a new datafile to the SYSAUX tablespace on the logical standby database but not on primary? We are running out of disk space on the partition where SYSAUX01.dbf resides so we want to add a new SYSAUX02.dbf in another partition which has space. but this will only be on the logical standby not on primary, there is still lots of space in primary. standby_file_management is MANUAL and this is LOGICAL STANDBY not PHYSICAL.
Is this possible or where there be any issues?
Thanks.

Logical Standby can differ from Primary, it can have extra tablespaces, datafiles, tables, indexes, users ...
HTH
Enrique

Standby database is not applying redo logs due to missing archive log

We use 9.2.0.7 Oracle Database. My goal is to create a physical standby database.
I have followed all the steps necessary to fulfill this in Oracle Data Guard Concepts and Administration manual. Archived redo logs are transmitted from primary to standby database regularly. But the logs are not applied due to archive log gap.
SQL> select process, status from v$managed_standby;
PROCESS STATUS
ARCH CONNECTED
ARCH CONNECTED
MRP0 WAIT_FOR_GAP
RFS RECEIVING
RFS ATTACHED
SQL> select * from v$archive_gap;
THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
1 503 677
I have tried to find the missing archives on the primary database, but was unable to. They have been deleted (somehow) regularly by the existing backup policy on the primary database. I have looked up the backups, but these archive logs are too old to be in the backup. Backup retention policy is 1 redundant backup of each file. I didn't save older backups as I didn't really need them from up to this point.
I have cross checked (using rman crosscheck) the archive log copies on the primary database and deleted the "obsolete" copies of archive logs. But, v$archived_log view on the primary database only marked those entries as "deleted". Unfortunately, the standby database is still waiting for those logs to "close the gap" and doesn't apply the redo logs at all. I am reluctant to recreate the control file on the primary database as I'm afraid this occurred through the regular database backup operations, due to current backup retention policy and it probably might happen again.
The standby creation procedure was done by using the data files from 3 days ago. The archive logs which are "producing the gap" are older than a month, and are probably unneeded for standby recovery.
What shall I do?
Kind regards and thanks in advance,
Milivoj

On a physical standby database
To determine if there is an archive gap on your physical standby database, query the V$ARCHIVE_GAP view as shown in the following example:
SQL> SELECT * FROM V$ARCHIVE_GAP;
THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
1 7 10
The output from the previous example indicates your physical standby database is currently missing log files from sequence 7 to sequence 10 for thread 1.
After you identify the gap, issue the following SQL statement on the primary database to locate the archived redo log files on your primary
database (assuming the local archive destination on the primary database is LOG_ARCHIVE_DEST_1):
SQL> SELECT NAME FROM V$ARCHIVED_LOG WHERE THREAD#=1 AND DEST_ID=1 AND 2> SEQUENCE# BETWEEN 7 AND 10;
NAME
/primary/thread1_dest/arcr_1_7.arc /primary/thread1_dest/arcr_1_8.arc /primary/thread1_dest/arcr_1_9.arc
Copy these log files to your physical standby database and register them using the ALTER DATABASE REGISTER LOGFILE statement on your physical standby database. For example:
SQL> ALTER DATABASE REGISTER LOGFILE
'/physical_standby1/thread1_dest/arcr_1_7.arc';
SQL> ALTER DATABASE REGISTER LOGFILE
'/physical_standby1/thread1_dest/arcr_1_8.arc';
After you register these log files on the physical standby database, you can restart Redo Apply.
Note:
The V$ARCHIVE_GAP fixed view on a physical standby database only returns the next gap that is currently blocking Redo Apply from continuing. After resolving the gap and starting Redo Apply, query the V$ARCHIVE_GAP fixed view again on the physical standby database to determine the next gap sequence, if there is one. Repeat this process until there are no more gaps.
Restoring the archived logs from the backup set
If the archived logs are not available in the archive destination then at that time we need to restore the required archived logs from the backup step. This task is accomplished in the following way.
To restore range specified archived logs:
Run {
Set archivelog destination to '/oracle/arch/arch_restore'
Restore archivelog from logseq=<xxxxx> until logseq=<xxxxxxx>
To restore all the archived logs:
Run {
Set archivelog destination to '/oracle/arch/arch_restore';
Restore archivelog all;
}

Switchover_status in standby database showing NOT ALLOWED

Hi All,
My oracle database version is Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit on windows platform.
I need to perform switchover activity with dg_broker=TRUE.
When I checked the status of DR database I found that switchover_status is NOT ALLOWED rather than SESSION ACTIVE or TO PRIMARY.I have doubt whether switchover can be done successfully or not with this configuration?
*Parameters from spfile in production database
=======================================
maxprod.__db_cache_size=2046820352
maxprod.__java_pool_size=16777216
maxprod.__large_pool_size=16777216
maxprod.__shared_pool_size=352321536
maxprod.__streams_pool_size=0
*.audit_file_dest='C:\oracle\product\10.2.0\admin\maxprod\adump'
*.background_dump_dest='C:\oracle\product\10.2.0\admin\maxprod\bdump'
*.compatible='10.2.0.1.0'
*.control_files='D:\MaximoData\oradata\maxprod\CONTROL01.CTL','D:\MaximoData\oradata\maxprod\CONTROL02.CTL','D:\MaximoData\oradata\maxprod\CONTROL03.CTL'
*.core_dump_dest='C:\oracle\product\10.2.0\admin\maxprod\cdump'
*.cursor_sharing='EXACT'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='maxprod'
*.db_recovery_file_dest='D:\MaximoData\flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.dg_broker_start=TRUE
*.dispatchers='(PROTOCOL=TCP) (SERVICE=maxprodXDB)'
*.fal_client='MAXPROD'
*.fal_server='EAMDR'
*.job_queue_processes=10
*.log_archive_config='DG_CONFIG=(MAXPROD,EAMDR)'
*.log_archive_dest_1='location=D:\MaximoData\Archive_Log valid_for=(all_logfiles,all_roles)'
*.log_archive_dest_2='SERVICE=EAMDR VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) db_unique_name=EAMDR'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_max_processes=30
*.log_archive_start=true
*.log_buffer=100000000
*.nls_language='AMERICAN'
*.open_cursors=8000
*.pga_aggregate_target=848297984
*.processes=300
*.remote_login_passwordfile='EXCLUSIVE'
*.session_cached_cursors=20
*.sga_max_size=4294967296
*.sga_target=2550136832
*.sql92_security=TRUE
*.standby_archive_dest='D:\MaximoData\Archive_Log\standby'
*.standby_file_management='auto'
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='C:\oracle\product\10.2.0\admin\maxprod\udump'*
*Parameters from spfile in DR database
============================
maxprod.__db_cache_size=3187671040
eamdr.__db_cache_size=1073741824
maxprod.__java_pool_size=16777216
eamdr.__java_pool_size=16777216
maxprod.__large_pool_size=16777216
eamdr.__large_pool_size=16777216
maxprod.__shared_pool_size=1056964608
eamdr.__shared_pool_size=486539264
maxprod.__streams_pool_size=0
eamdr.__streams_pool_size=0
*.audit_file_dest='C:\oracle\product\10.2.0\admin\EAMDR\adump'
*.background_dump_dest='C:\oracle\product\10.2.0\admin\EAMDR\bdump'
*.compatible='10.2.0.1.0'
*.control_files='D:\MAXIMODATA\ORADATA\MAXPROD\CONTROL01.CTL','D:\MAXIMODATA\ORADATA\MAXPROD\CONTROL02.CTL','D:\MAXIMODATA\ORADATA\MAXPROD\CONTROL03.CTL'#Restore Controlfile
*.core_dump_dest='C:\oracle\product\10.2.0\admin\EAMDR\cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='maxprod'
*.db_recovery_file_dest_size=10737418240
*.db_recovery_file_dest='D:\MaximoData\flash_recovery_area'
*.DB_UNIQUE_NAME='EAMDR'
*.dg_broker_start=TRUE
*.dispatchers='(PROTOCOL=TCP) (SERVICE=maxprodXDB)'
*.fal_client='EAMDR'
*.fal_server='MAXPROD'
*.job_queue_processes=10
*.log_archive_config='DG_CONFIG=(MAXPROD,EAMDR)'
*.log_archive_dest_1='LOCATION=D:\MaximoData\Archive_Log VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=EAMDR'
*.log_archive_dest_2='service=maxprod valid_for=(online_logfiles,primary_role) db_unique_name=MAXPROD'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_max_processes=30
*.nls_language='AMERICAN'
*.open_cursors=8000
*.pga_aggregate_target=194967296
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_max_size=4294967296
*.sga_target=1594967296
*.standby_archive_dest='D:\MaximoData\Archive_Log\standby'
*.standby_file_management='AUTO'
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='C:\oracle\product\10.2.0\admin\EAMDR\udump'*
I didn't find any DG_BROKER_CONFIG_FILE1, DG_BROKER_CONFIG_FILE2 parameters from spfile in both production and DR db?
Is anything missing in spfile?
When I am trying to connect with dgmgrl
DGMGRL>connect sys;
connected
DGMGRL>show configuration;
Error: ORA-16532: Data Guard broker configuration does not exist
what does it mean when dgmgrl is set to true?
I have attached PRODUCTION and DR queries outputs for better understanding.
IN PRIMARY DATABASE
SQL>select database_role from v$database;
DATABASE_ROLE
PRIMARY
SQL> select switchover_status from v$database;
SWITCHOVER_STATUS
SESSIONS ACTIVE
SQL> select db_unique_name,database_role,open_mode,log_mode,protection_mode from v$database;
DB_UNIQUE_NAME DATABASE_ROLE OPEN_MODE LOG_MODE PROTECTION_MODE
maxprod PRIMARY READ WRITE ARCHIVELOG MAXIMUM PERFORMANCE
SQL> select process,status,client_process,sequence# from v$managed_standby;
PROCESS STATUS CLIENT_P SEQUENCE#
ARCH CLOSING ARCH 7820
ARCH CLOSING ARCH 7835
ARCH CLOSING ARCH 7835
ARCH CLOSING ARCH 7821
ARCH CLOSING ARCH 7822
ARCH CLOSING ARCH 7822
ARCH CLOSING ARCH 7793
ARCH CLOSING ARCH 7823
ARCH CLOSING ARCH 7824
ARCH CLOSING ARCH 7824
ARCH CLOSING ARCH 7825
ARCH CLOSING ARCH 7825
ARCH CLOSING ARCH 7826
ARCH CLOSING ARCH 7826
ARCH CLOSING ARCH 7827
ARCH CLOSING ARCH 7827
ARCH CLOSING ARCH 7828
ARCH CLOSING ARCH 7828
ARCH CLOSING ARCH 7829
ARCH CLOSING ARCH 7829
ARCH CLOSING ARCH 7830
ARCH CLOSING ARCH 7830
ARCH CLOSING ARCH 7831
ARCH CLOSING ARCH 7831
ARCH CLOSING ARCH 7832
ARCH CLOSING ARCH 7832
ARCH CLOSING ARCH 7833
ARCH CLOSING ARCH 7833
ARCH CLOSING ARCH 7834
ARCH CLOSING ARCH 7834
30 rows selected.
SQL> sho parameter log_archive_config
NAME TYPE VALUE
log_archive_config string DG_CONFIG=(MAXPROD,EAMDR)
SQL> spool off
IN SECONDARY DATABASE
SQL> select database_role from v$database;
DATABASE_ROLE
PHYSICAL STANDBY
SQL> select switchover_status from v$database;
SWITCHOVER_STATUS --------------------
NOT ALLOWED
SQL> select db_unique_name,database_role,open_mode,log_mode,protection_mode from v$database;
DB_UNIQUE_NAME DATABASE_ROLE OPEN_MODE LOG_MODE PROTECTION_MODE
EAMDR PHYSICAL STANDBY MOUNTED ARCHIVELOG MAXIMUM PERFORMANCE
SQL> select process,status,client_process,sequence# from v$managed_standby;
PROCESS STATUS CLIENT_P SEQUENCE#
ARCH CLOSING ARCH 7809
ARCH CLOSING ARCH 7810
ARCH CLOSING ARCH 7812
ARCH CLOSING ARCH 7813
ARCH CLOSING ARCH 7814
ARCH CLOSING ARCH 7815
ARCH CLOSING ARCH 7816
ARCH CLOSING ARCH 7817
ARCH CLOSING ARCH 7818
ARCH CLOSING ARCH 7819
ARCH CLOSING ARCH 7820
ARCH CLOSING ARCH 7821
ARCH CLOSING ARCH 7822
ARCH CLOSING ARCH 7823
ARCH CLOSING ARCH 7824
ARCH CLOSING ARCH 7825
ARCH CLOSING ARCH 7826
ARCH CLOSING ARCH 7827
ARCH CLOSING ARCH 7828
ARCH CLOSING ARCH 7829
ARCH CLOSING ARCH 7830
ARCH CLOSING ARCH 7831
ARCH CLOSING ARCH 7832
ARCH CLOSING ARCH 7833
ARCH CLOSING ARCH 7835
ARCH CLOSING ARCH 7804
ARCH CLOSING ARCH 7805
ARCH CLOSING ARCH 7806
ARCH CLOSING ARCH 7807
ARCH CLOSING ARCH 7808
MRP0 WAIT_FOR_LOG N/A 7836
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE

Meenakshy singh wrote:
Hi All,
My oracle database version is Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit on windows platform.
I need to perform switchover activity.When I checked the status of DR database I found that switchover_status is NOT ALLOWED rather than SESSION ACTIVE or TO PRIMARY.I have doubt whether switchover can be done successfully or not?
I have attached PRODUCTION and DR queries outputs for better understanding.
IN PRIMARY DATABASE
SQL>select database_role from v$database;
DATABASE_ROLE
PRIMARY
SQL> select switchover_status from v$database;
SWITCHOVER_STATUS
SESSIONS ACTIVE
SQL> select db_unique_name,database_role,open_mode,log_mode,protection_mode from v$database;
DB_UNIQUE_NAME DATABASE_ROLE OPEN_MODE LOG_MODE PROTECTION_MODE
maxprod PRIMARY READ WRITE ARCHIVELOG MAXIMUM PERFORMANCE
SQL> select process,status,client_process,sequence# from v$managed_standby;
PROCESS STATUS CLIENT_P SEQUENCE#
ARCH CLOSING ARCH 7820
ARCH CLOSING ARCH 7835
ARCH CLOSING ARCH 7835
ARCH CLOSING ARCH 7821
ARCH CLOSING ARCH 7822
ARCH CLOSING ARCH 7822
ARCH CLOSING ARCH 7793
ARCH CLOSING ARCH 7823
ARCH CLOSING ARCH 7824
ARCH CLOSING ARCH 7824
ARCH CLOSING ARCH 7825
ARCH CLOSING ARCH 7825
ARCH CLOSING ARCH 7826
ARCH CLOSING ARCH 7826
ARCH CLOSING ARCH 7827
ARCH CLOSING ARCH 7827
ARCH CLOSING ARCH 7828
ARCH CLOSING ARCH 7828
ARCH CLOSING ARCH 7829
ARCH CLOSING ARCH 7829
ARCH CLOSING ARCH 7830
ARCH CLOSING ARCH 7830
ARCH CLOSING ARCH 7831
ARCH CLOSING ARCH 7831
ARCH CLOSING ARCH 7832
ARCH CLOSING ARCH 7832
ARCH CLOSING ARCH 7833
ARCH CLOSING ARCH 7833
ARCH CLOSING ARCH 7834
ARCH CLOSING ARCH 7834
30 rows selected.
SQL> sho parameter log_archive_config
NAME TYPE VALUE
log_archive_config string DG_CONFIG=(MAXPROD,EAMDR)
SQL> spool off
IN SECONDARY DATABASE
SQL> select database_role from v$database;
DATABASE_ROLE
PHYSICAL STANDBY
SQL> select switchover_status from v$database;
SWITCHOVER_STATUS --------------------
NOT ALLOWED
SQL> select db_unique_name,database_role,open_mode,log_mode,protection_mode from v$database;
DB_UNIQUE_NAME DATABASE_ROLE OPEN_MODE LOG_MODE PROTECTION_MODE
EAMDR PHYSICAL STANDBY MOUNTED ARCHIVELOG MAXIMUM PERFORMANCE
SQL> select process,status,client_process,sequence# from v$managed_standby;
PROCESS STATUS CLIENT_P SEQUENCE#
ARCH CLOSING ARCH 7809
ARCH CLOSING ARCH 7810
ARCH CLOSING ARCH 7812
ARCH CLOSING ARCH 7813
ARCH CLOSING ARCH 7814
ARCH CLOSING ARCH 7815
ARCH CLOSING ARCH 7816
ARCH CLOSING ARCH 7817
ARCH CLOSING ARCH 7818
ARCH CLOSING ARCH 7819
ARCH CLOSING ARCH 7820
ARCH CLOSING ARCH 7821
ARCH CLOSING ARCH 7822
ARCH CLOSING ARCH 7823
ARCH CLOSING ARCH 7824
ARCH CLOSING ARCH 7825
ARCH CLOSING ARCH 7826
ARCH CLOSING ARCH 7827
ARCH CLOSING ARCH 7828
ARCH CLOSING ARCH 7829
ARCH CLOSING ARCH 7830
ARCH CLOSING ARCH 7831
ARCH CLOSING ARCH 7832
ARCH CLOSING ARCH 7833
ARCH CLOSING ARCH 7835
ARCH CLOSING ARCH 7804
ARCH CLOSING ARCH 7805
ARCH CLOSING ARCH 7806
ARCH CLOSING ARCH 7807
ARCH CLOSING ARCH 7808
MRP0 WAIT_FOR_LOG N/A 7836
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
RFS IDLE UNKNOWN 0
56 rows selected.
SQL> sho parameter log_archive_config
NAME TYPE VALUE
log_archive_config string DG_CONFIG=(MAXPROD,EAMDR)
SQL> spool off
1.In this case,is switchover is possible?No
2.If not possible then what will be the next step?If the value in the SWITCHOVER_STATUS column is SESSIONS ACTIVE, identify and terminate active user or SQL sessions that might prevent a switchover from being processed.
If, after performing these steps, the SWITCHOVER_STATUS column still displays SESSIONS ACTIVE, you can successfully perform a switchover by appending the WITH SESSION SHUTDOWN clause to the
ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY statement.
3.Is this will impact to our production database when switchover is not successfully perform?
4.In DR RFS is idle,why?Can you paste here log_archive_dest_n paramete which is you are using for transport?
Did you using DELAY attribute in log_archive_dest_n parameter?
Mahir

Steps to rollback when Logical Standby Database creation fails

Hi,
In case while creating a logical standby database it fails. What steps should be done on primary to rollback the earlier steps. Because while creating logical standby we do certain tasks on primary e.g.
1) create supplemental logging.
2) update init file.
Regards,
Tushar

Hi,
Thanks for the mail. Should I drop the supplemental logging using
"Alter database DROP Supplemental Log data;".
or if we need to disable, how can we do so?
Rest is ok. Anyways I would not be using force logging.
Droping of additional tablespace created to keep logminer tables on primary.
Removing of log_archive_dest_2 information from primary init.
I think the above should do.
Regards,
Tushar

Standby Database Location not listed

We have the primary database created and the primary database, server, and agent and the standby server and agent are listed in grid control targets. but when I go to create a new standby database, the standby server is not listed for selection in the list of servers to select for Standby Database Location.
The agent on the server appears to be running and uploading fine.
Windows 2003 server SP2
Oracle 10.2.0.3 on Primary
Oracle 10.2.0.2 repository
Grid Control 10.1.0.4

We don't have a standby database because the server isn't listed in the list of Standby Database Locations to choose from. We are trying to create the standby database.
We've tried to Discover the standby server but it seems to already be Discovered because it is listed as a target when all targets are displayed (target type of host).
It's almost like the grid control sees the server but for some reason feels it's inelligible to be a standby server.

Standby Database Creation in the same Box Oracle 9.2.0.1

Box - Sun Solaris 64 bit
Oracle Version - 9.2.0.1
I have a database called 'sales' in the above box. I want to create a standby database in the same box (in different mount point). This is what I did:
1. took cold backup of all datafiles
2. created standby controlfile
3. updated init file.
-when I tried to start the stabdby db, it is throwing error because the controlfile is confusing with the same db name as the primary ('sales').
My question is: Can I create a standby db in the same box?

Hello,
For keeping the standby database on same HOST....it does seems to be great...i must be on separate box....may be on different network...i believe you would be using it for some failiover purpose...Isn't it.
For Unix it is quite easy..you may implement like this...The Issue which you are referring may be because of wrong Oracle Home or SID....(i'm not very much sure..) You may try following steps:
1. Create a separate Unix A/c and set ORACLE_HOME and ORACLE_SID relevant to your StandBy Database. I believe the Home would be same whereas SID would be your standby databse.
2. Take a Cold Backup of All your database files from Production.
3. Copy these files on separate mount points for standby Db. Put them all to relevant directory and be sure to set the Group of all these files as "SYSDBA" This is Must.
4. And then modify your INIT.ORA file i.e. InitSID.ora file accordingly and put the file in ORACLE_HOME
5. Login to Newly created Unix A/c. Check whether ORACLE_SID is set ot not to your standby database instance.
6. Login to sys as sysdba and start up the database. It will by default would try to check & do for your relevant Oracle SID for this profile...
HTH
Regards,
Kamesh Rastogi

Standby database is not completing recovery.

All,
I applied a PSU to 10.2.0.4 (8576156) patch this afternoon on both the primary and standby oracle_home(s). Upon starting up the standby database, I no longer see the “media recovery waiting” message in the alert log when an archive log is sent from the primary.
Not sure if I have an issue with the patch or DG is configured or started.
Perhaps another set of eyes can lead me to an issue I am not seeing.
The standby database was started as follows:
alter database RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION
Example alert log message before:
Sun Sep 13 02:20:39 2009
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: '/oradat1/cwsiqa2/cwsiqa2_sb_redo04_a.log'
Sun Sep 13 02:20:47 2009
Media Recovery Waiting for thread 1 sequence 52 (in transit) <<== NOTE
Sun Sep 13 02:20:47 2009
Recovery of Online Redo Log: Thread 1 Group 4 Seq 52 Reading mem 0
Mem# 0: /oradat1/cwsiqa2/cwsiqa2_sb_redo04_a.log
Mem# 1: /oradat2/cwsiqa2/cwsiqa2_sb_redo04_b.log
Example alert log message after:
Primary database is in MAXIMUM PERFORMANCE mode
Tue Sep 15 15:56:27 2009
RFS[3]: Successfully opened standby log 4: '/oradat1/cwsiqa2/cwsiqa2_sb_redo04_a.log'
Tue Sep 15 15:56:27 2009
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: Successfully opened standby log 6: '/oradat3/cwsiqa2/cwsiqa2_sb_redo06_a.log'
Tue Sep 15 15:57:05 2009
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[5]: Assigned to RFS process 29772
RFS[5]: Identified database type as 'physical standby'
Tue Sep 15 16:12:56 2009
The same messages are listed in v$datagurd_status
1* select message from v$dataguard_status
SQL> /
MESSAGE
ARC0: Archival started
ARC1: Archival started
ARC2: Archival started
ARC3: Archival started
ARC4: Archival started
ARC5: Archival started
ARC6: Archival started
ARC7: Archival started
ARC8: Archival started
ARC9: Archival started
ARC9: Becoming the 'no FAL' ARCH
ARC9: 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
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[1]: Assigned to RFS process 28316
RFS[1]: Identified database type as 'physical standby'
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[2]: Assigned to RFS process 28318
RFS[2]: Identified database type as 'physical standby'
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[3]: Assigned to RFS process 29693
RFS[3]: Identified database type as 'physical standby'
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[4]: Assigned to RFS process 29691
RFS[4]: Identified database type as 'physical standby'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: Successfully opened standby log 4: '/oradat1/cwsiqa2/cwsiqa2_sb_redo04_a.log'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: Successfully opened standby log 6: '/oradat3/cwsiqa2/cwsiqa2_sb_redo06_a.log'
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[5]: Assigned to RFS process 29772
RFS[5]: Identified database type as 'physical standby'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: Successfully opened standby log 4: '/oradat1/cwsiqa2/cwsiqa2_sb_redo04_a.log'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[4]: Successfully opened standby log 6: '/oradat3/cwsiqa2/cwsiqa2_sb_redo06_a.log'
I also have a “gap” that is not getting resolved.
SQL> select * from v$archive_gap
2 /
THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
1 53 53
SELECT MAX(R.SEQUENCE#) LAST_SEQ_RECD, MAX(L.SEQUENCE#) LAST_SEQ_SENT
2* FROM V$ARCHIVED_LOG R, V$LOG L WHERE R.DEST_ID=2 AND L.ARCHIVED='YES'
SQL> /
LAST_SEQ_RECD LAST_SEQ_SENT
54 58
Any insight would be appreciated.

Problem has been resolved.

Standby Database Creation problem

Hi,
I have setup Standby Database for our Primary DAtabae,
I am facing probel while applying redo logs, if somebody nows the solution, Please help me.
SQL> startup nomount PFILE='E:\oracle\admin\fno\pfile\init.ora';
ORACLE instance started.
Total System Global Area 730931140 bytes
Fixed Size 454596 bytes
Variable Size 285212672 bytes
Database Buffers 444596224 bytes
Redo Buffers 667648 bytes
SQL> ALTER DATABASE MOUNT STANDBY DATABASE;
Database altered.
SQL> RECOVER STANDBY DATABASE;
ORA-00279: change 7990686470 generated at 04/01/2006 15:53:57 needed
for threa
1
ORA-00289: suggestion : F:\ORACLE\ORADATA\FNO\ARCH\LOG_17032.ARC
ORA-00280: change 7990686470 for thread 1 is in sequence #7032
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
AUTO
ORA-00283: recovery session canceled due to errors
ORA-00600: internal error code, arguments: [3020], [8388681], [1],
[7032],
[137367], [16], [], []
ORA-10567: Redo is inconsistent with data block (file# 2, block# 73)
ORA-10564: tablespace UNDOTBS1
ORA-01110: data file 2: 'G:\ORACLE\ORADATA\FNO\UNDOTBS01.DBF'
ORA-10560: block type 'KTU SMU HEADER BLOCK'
ORA-01112: media recovery not started
Ramesh
pls mail me : [email protected]
+91 080 9341018616

Hi,
I have setup Standby Database for our Primary DAtabae,
I am facing probel while applying redo logs, if somebody nows the solution, Please help me.
SQL> startup nomount PFILE='E:\oracle\admin\fno\pfile\init.ora';
ORACLE instance started.
Total System Global Area 730931140 bytes
Fixed Size 454596 bytes
Variable Size 285212672 bytes
Database Buffers 444596224 bytes
Redo Buffers 667648 bytes
SQL> ALTER DATABASE MOUNT STANDBY DATABASE;
Database altered.
SQL> RECOVER STANDBY DATABASE;
ORA-00279: change 7990686470 generated at 04/01/2006 15:53:57 needed
for threa
1
ORA-00289: suggestion : F:\ORACLE\ORADATA\FNO\ARCH\LOG_17032.ARC
ORA-00280: change 7990686470 for thread 1 is in sequence #7032
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
AUTO
ORA-00283: recovery session canceled due to errors
ORA-00600: internal error code, arguments: [3020], [8388681], [1],
[7032],
[137367], [16], [], []
ORA-10567: Redo is inconsistent with data block (file# 2, block# 73)
ORA-10564: tablespace UNDOTBS1
ORA-01110: data file 2: 'G:\ORACLE\ORADATA\FNO\UNDOTBS01.DBF'
ORA-10560: block type 'KTU SMU HEADER BLOCK'
ORA-01112: media recovery not started
Ramesh
pls mail me : [email protected]
+91 080 9341018616

Standby database is not Sync with primary DB

Hi,
One week back I configured standby database and It was running fine.
But 2 days back(Saturday) somebody had down my standby database. Today when I mounted my database; I saw this is not sync with primary database.
Database Name :- pcs
Primary db_unique_name :- pcs
standby db_unique_name :- pcstd
Present scanerio is...
Status of Standby Database is...
SQL> startup mount;
ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE instance started.
Total System Global Area 1073741824 bytes
Fixed Size 2063792 bytes
Variable Size 301990480 bytes
Database Buffers 763363328 bytes
Redo Buffers 6324224 bytes
Database mounted.
SQL> select GROUP# ,SEQUENCE# ,ACTIVE_AGENTS,STATUS from v$managed_standby;
GROUP# SEQUENCE# ACTIVE_AGENTS STATUS
N/A 0 0 CONNECTED
N/A 0 0 CONNECTED
SQL> recover managed standby database disconnect from session;
Media recovery complete.
SQL> select GROUP# ,SEQUENCE# ,ACTIVE_AGENTS,STATUS from v$managed_standby;
GROUP# SEQUENCE# ACTIVE_AGENTS STATUS
N/A 0 0 CONNECTED
N/A 0 0 CONNECTED
N/A 130 0 WAIT_FOR_LOG
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /backup/bkpcs/
Oldest online log sequence 121
Next log sequence to archive 0
Current log sequence 126
Status of Primary database is..
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /data/pcs10g/archive/
Oldest online log sequence 129
Next log sequence to archive 131
Current log sequence 131
SQL>
Somebody can help me to resolve the following issues
(1). Why archive log list not showing exact log sequence number on Standby Database.
(2). How can I configure automatic archive logs apply from Live to Standby again.
Regards,

Problem has been resolved.

Standby database creation on oracle8.0.6

Folks...can anyone point me to right documentation for creating standby database on oracle 8.0.6.
I found very good doc for version 8.1.5 but not 8.0.6.
Thanks S

what is the tablespace size for the following:
system:
temp:
user:
rollback:
index:
shah
null

Oracle standby database creation different backup location

Hi,
I am using Oracle EE 11gR2 on aix 6.2.I am tring to create a standby database.The directory structure od primary and standby database server are different.
I am taking backup (RMAN) at /u01/backup directory on primary server and shipping those backup to standby server at /u05/backup.While duplication the rman unable to locate backup pieces at Dr server as those backups are located on different location from Dc.How to over come this situation.catalog start with is not working.
Regards
DBAFORU

Hello;
Since you are on Oracle 11 one option would be duplicate from active primary. You can use the Standby parameters of DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT for the directory structure.
duplicate target database for standby from active database NOFILENAMECHECK;
How To Restore From An Old Backupset Using RMAN? (Doc ID 209214.1)
Step by Step Guide on Creating Physical Standby Using RMAN DUPLICATE...FROM ACTIVE DATABASE (Doc ID 1075908.1)
RMAN ACTIVE DUPLICATE WHEN CONNECTED TO STANDBY AS TARGET (Doc ID 1343515.1)
Creating a Physical Standby Database (Doc ID 1475344.1)
Best Regards
mseberg

StandBy database creation in oracle 10g

Respected Sir's
I have to create stand by database in oracle 10g i am working on (Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod) .Plz any body provide steps required for creating stand by database in oracle10g.Both the database db1 and db2 are running on archivelog.I am confuse how to set archivelog parameter that goes to db2(standby database) from db(primary database).Any one provide me steps to properly configuring the stand by database.
Thanks

Respected Sir
These are the detailed steps that i performed on standby and primary database.
On both the systems i install the oracle in E drive and the database i create in G drive and archive destination also in G drive.
Like G:\prod1\(all the datafiles,logfiles and control file).
G:\arch\(all the archive files).
ON PRIMARY DATABASE(IP:192.168.2.14):
1.First i create a database with DBCA and the database SID is prod1.
2.Put the database in archive mode and also enable the force logging.
3.Shutdown the Primary database and modify the following parameters in pfile.
log_archive_dest_1='LOCATION=G:\ARCH'
log_archive_dest_2 = "service=STDBY mandatory reopen=60"
log_archive_dest_state_1 = enable
log_archive_dest_state_2 = enable
log_archive_min_succeed_dest = 2
4.Mount the primary database and create the standby controle file and create the spfile from the modified pfile.
5.Shutdown the primary database and take the backup of all the datafile,logfile,standby controlfile ,passwordfile,pfile in a folder.
6.Startup the primary database.
Tnsname.ora Configuration.
Create the connection string using the Net Manager with name STDBY and in host name i provide the IP address of the standby database.
ON STANDBY DATABASE(IP 192.168.2.9):
Listener.ora Configuration.
Create a listener using the Net configuration Assistance.
1.I copy the datafile,logfile and standby controle file in g:\prod1
2.Copy the E:\oracle\product\10.2.0\admin\prod1 folder from primary database and past it on the same location on the standby database.
3.On standby pfile i change only the standby_archive_dest parameter to g:\arch.
4.Create the service with oradim -SID -NEW prod1 -STARTMODE manuall
5.Start the standby database in nomount mode.
6.Create the spfile from pfile and shutdown the database.
7.Startup the database in nomount mode using spfile.
8.ALTER DATABASE MOUNT STANDBY DATABASE;
These are the occurs when i use tnsping stdby on primary database.
C:\Documents and Settings\Administrator>TNSPING STDBY
TNS Ping Utility for 32-bit Windows: Version 10.2.0.1.0 - Production on 04-FEB-2009 12:03:55
Copyright (c) 1997, 2005, Oracle. All rights reserved.
Used parameter files:
E:\oracle\product\10.2.0\db_1\network\admin\sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.2.9
NECT_DATA = (SERVICE_NAME = prod1)))
OK (20 msec)
sqlnet.ora file on stand by database.
SQLNET.AUTHENTICATION_SERVICES= (NTS)
NAMES.DIRECTORY_PATH= (TNSNAMES, LDAP)
BEQUEATH_DETACH=yes
AUTOMATIC_IPC = ON
NAMES.DEFAULT_DOMAIN = IDEVELOPMENT.INFO
SQLNET.EXPIRE_TIME=2
This occurs when i use tnsping prod1 on standby database.
TNS Ping Utility for 32-bit Windows: Version 10.2.0.1.0 - Production on 04-FEB-2
009 12:01:40
Copyright (c) 1997, 2005, Oracle. All rights reserved.
Used parameter files:
E:\oracle\product\10.2.0\db_1\network\admin\sqlnet.ora
TNS-03505: Failed to resolve name
Please help me bec i have to create the stand database as soon as possible.Thanks Sir

Standby database creation notes by metalink

Similar Messages

Maybe you are looking for