Standby databse ??

Dear all,
Can I create a standby database at a different server/location.
thanks in advance
SL

Yes, most have pointed out that a different server is recommended. The other part of your question was another location and again the answer is yes. The caveat here is that your Standby will only be as reliable as your network and disparate locations tend to be a bit less reliable in terms of network stability and bandwidth. Not that it cannot be successful, but you need to review the capailities of the Wide area network so that you can set expectations accordingly. I would also recommend monitoring the Standby status through scripting. I normally do this in my local Standby's anyway. A simple check on the last log applied and comparing to the source's current log is a great start.

Similar Messages

Error in adding datafile in standby databse.

Hi all.
My Environment is as below:
Oracle-8.1.7.4.0
OS-HP Unix-11
Primary database (only 1): Production
Standby database: Different Machine but same location (HP box)
Yesterday I have added 2 datafiles to the two different tablespace. I have checked file is available at Production box and one of the file also avilable at standby databse.
When I am following steps for applying redo log to the standby manually.
I got error.
SVRMGRL>connect internal
SVRMGRL>show parameter db_name
SVRMGRL>recover standby databse
After above step I got the Error:
ORA-00283 recovery session canceled due to error
ORA-01157 can not identify/lock datafile 24 -see DBWR trace file
ORA-01110 data file 24: '/location of .dbf file on standby databse disk'
Please let me know in detail because I am new in this field.
Thanks in advance

You will have the datafile information on the standby alert log.
Something like '/u01/app/oracle/product/8174/db/<filename>.dbf'.
1. connect as sysdba on standby database.
2. alter database create datafile 'Production datafile name' as 'alert log filename';
Example :
alter database create datafile '/u01/data/user1.dbf'
as '/u01/app/oracle/product/8174/db/<filename>.dbf';
3. Recovery managed standby database;
HTH.
Regards,
Arun

How to recover my Standby databse

Hi every one,
I need a suggestion in recovering a standby database which is not in sync with primary for last 2 months. due to server issues we brought down our standby down and made my primary to no archive log mode ( disabled archive log mode).
Now I've to recover my standby.... Please suggest what would be the best plan...
Note : my primary databse is in no archive log mode now, i've to put it in archive before recovering the standby.
I came up with few plans... you all can see those below however please suggest which on is the best or any new plans..
1) take fresh rman backup and drop my old standby and recreate it..
2) we are taking daily full export backups however we cannot import those in standaby since mount state import cannot write..
Please suggest is there any other best way to mimise efforts in recovering this issues..
Regards,
Ramu

Hi,
Thanks alot for your reply... my database version is 10204..
the thing is my primary database is not generating archives for more than a month (archival process disabled)
now i will enable my archival process on primary...
so at this time my standby is out of sync for more than a month where there are no archives...
so if i take a incremental level 1 backup from the sequence where syandby received and recover the database
would the above this is help full...
because.... my primary last generated sequence was 16789, if i put my primary in archive then it will generate 16790 sequence...
so the level one backup will have only once one sequence difference of data?
Regards,
Ramu

Standby Databse Log Problem

Hi,
i am trying to Configure Data Guard in two server.
I have followed all the requisite steps in Primary Database and then copied the same to Standby to run adcfgclone.pl
in the standby.Then i have updated the pfile in Standby,checked that archieve log is enabled there[using archive log list]
and then generated one standby control file in the primary database and copied the same into Standby and made the changs
in the corresponding pfile.
But even then when i am trying to check the standby by runnning the following query it is showing:--
SQL> select thread#, sequence#, applied, to_char(first_time, 'mm/dd/yy hh24:mi:ss') first, to_char(next_time, 'mm/dd/yy
hh24:mi:ss') next, to_char(completion_time, 'mm/dd/yy hh24:mi:ss') completion from v$archived_log order by first_time;
no rows selected
while this is working fine:--
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
Database altered.
The following are the platform details and database version.
**Database Version:-- Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi**
**Platform:-- HP-UX B.11.23 U ia64 unlimited-user license**
I dont konw what mistake i have made and i am new to DBA job.Thus i am uploading both the pfile of standby and primary
database.
Please help me in this.
STANDBY PFILE
KMC.__db_cache_size=629145600
KMC.__java_pool_size=4194304
KMC.__large_pool_size=4194304
KMC.__shared_pool_size=419430400
KMC.__streams_pool_size=0
*._b_tree_bitmap_plans=FALSE# Required 11i setting
*._fast_full_scan_enabled=FALSE
*._index_join_enabled=FALSE# Required 11i setting
*._like_with_bind_as_equality=TRUE
*._sort_elimination_cost_ratio=5
*._sqlexec_progression_cost=2147483647
*._system_trig_enabled=true
*._trace_files_public=TRUE
*.aq_tm_processes=1
*.background_dump_dest='/u03/db/tech_st/10.2.0//admin/KMC_kmcpgw2/bdump'
*.compatible='10.2.0'
*.control_files='/u03/db/apps_st/data/standby_ctl'
*.core_dump_dest='/u03/db/tech_st/10.2.0//admin/KMC_kmcpgw2/cdump'
*.cursor_sharing='EXACT'# Required 11i settting
*.db_block_checking='FALSE'
*.db_block_checksum='TRUE'
*.db_block_size=8192
*.db_file_multiblock_read_count=8# Required 11i setting
*.db_files=512# Max. no. of database files
*.db_name='KMC'
*.db_unique_name='KMC_STBY'
*.dml_locks=10000
*.fal_client='KMC_STBY'
*.fal_server='KMC_PROD'
*.job_queue_processes=2
*.LOG_ARCHIVE_CONFIG='DG_CONFIG=(KMC_STBY,KMC_PROD)'
*.log_archive_dest_1='LOCATION=/u03/db/tech_st/10.2.0/dbs/arch'
*.log_archive_dest_2='service=KMC_PROD valid_for=(online_logfiles,primary_role) db_unique_name=KMC_PROD LGWR ASYNC=20480
OPTIONAL REOPEN=15 NET_TIMEOUT=30'
*.log_archive_dest_state_2='defer'
*.log_buffer=10485760
*.log_checkpoint_interval=100000
*.log_checkpoint_timeout=1200# Checkpoint at least every 20 mins.
*.log_checkpoints_to_alert=TRUE
*.max_dump_file_size='20480'# trace file size
*.nls_comp='binary'# Required 11i setting
*.nls_date_format='DD-MON-RR'
*.nls_language='american'
*.nls_length_semantics='BYTE'# Required 11i setting
*.nls_numeric_characters='.,'
*.nls_sort='binary'# Required 11i setting
*.nls_territory='america'
*.olap_page_pool_size=4194304
*.open_cursors=600# Consumes process memory, unless using MTS.
*.optimizer_secure_view_merging=false
*.parallel_max_servers=8
*.parallel_min_servers=0
*.pga_aggregate_target=1G
*.plsql_code_type='INTERPRETED'# Default 11i setting
*.plsql_native_library_dir='/u03/db/tech_st/10.2.0//plsql/nativelib'
*.plsql_native_library_subdir_count=149
*.plsql_optimize_level=2# Required 11i setting
*.processes=200# Max. no. of users x 2
*.query_rewrite_enabled='true'
*.session_cached_cursors=500
*.sessions=400# 2 X processes
*.sga_target=1G
*.shared_pool_reserved_size=40M
*.shared_pool_size=400M
*.standby_archive_dest='LOCATION=/u03/db/tech_st/10.2.0/dbs/arch'
*.timed_statistics=true
*.undo_management='AUTO'# Required 11i setting
*.undo_tablespace='APPS_UNDOTS1'# Required 11i setting
*.user_dump_dest='/u03/db/tech_st/10.2.0//admin/KMC_kmcpgw2/udump'
*.utl_file_dir='/usr/tmp','/usr/tmp/KMC/','/u03/db/tech_st/10.2.0//appsutil/outbound/KMC_kmcpgw2','/usr/tmp'
*.workarea_size_policy='AUTO'# Required 11i setting
PRIMARY PFILE
KMC.__db_cache_size=620756992
KMC.__java_pool_size=4194304
KMC.__large_pool_size=4194304
KMC.__shared_pool_size=419430400
KMC.__streams_pool_size=8388608
*._b_tree_bitmap_plans=FALSE# Required 11i setting
*._fast_full_scan_enabled=FALSE
*._index_join_enabled=FALSE# Required 11i setting
*._like_with_bind_as_equality=TRUE
*._sort_elimination_cost_ratio=5
*._sqlexec_progression_cost=2147483647
*._system_trig_enabled=true
*._trace_files_public=TRUE
*.aq_tm_processes=1
*.background_dump_dest='/u03/db/tech_st/10.2.0//admin/KMC_kmcpgw1/bdump'
*.compatible='10.2.0'
*.control_files='/u03/db/apps_st/data/cntrl01.dbf','/u03/db/apps_st/data/cntrl02.dbf','/u03/db/apps_st/data/cntrl03.dbf'
*.core_dump_dest='/u03/db/tech_st/10.2.0/admin/KMC_kmcpgw1/cdump'
*.cursor_sharing='EXACT'# Required 11i settting
*.db_block_checking='FALSE'
*.db_block_checksum='TRUE'
*.db_block_size=8192
*.db_file_multiblock_read_count=8# Required 11i setting
*.db_files=512# Max. no. of database files
*.db_name='KMC'
*.db_unique_name='KMC_PROD'
*.dml_locks=10000
*.fal_client='KMC_PROD'
*.fal_server='KMC_STBY'
*.job_queue_processes=2
*.LOG_ARCHIVE_CONFIG='DG_CONFIG=(KMC_PROD,KMC_STBY)'
*.log_archive_dest_1='LOCATION=/u03/db/tech_st/10.2.0/dbs/arch'
*.log_archive_dest_2='service=KMC_STBY valid_for=(online_logfiles,primary_role) db_unique_name=KMC_STBY LGWR ASYNC=20480 OPTI
ONAL REOPEN=15 NET_TIMEOUT=30'
*.log_archive_dest_state_2='ENABLE'
*.log_buffer=10485760
*.log_checkpoint_interval=100000
*.log_checkpoint_timeout=1200# Checkpoint at least every 20 mins.
*.log_checkpoints_to_alert=TRUE
*.max_dump_file_size='20480'# trace file size
*.nls_comp='binary'# Required 11i setting
*.nls_date_format='DD-MON-RR'
*.nls_language='american'
*.nls_length_semantics='BYTE'# Required 11i setting
*.nls_numeric_characters='.,'
*.nls_sort='binary'# Required 11i setting
*.nls_territory='america'
*.olap_page_pool_size=4194304
*.open_cursors=600# Consumes process memory, unless using MTS.
*.optimizer_secure_view_merging=false
*.parallel_max_servers=8
*.parallel_min_servers=0
*.pga_aggregate_target=1G
*.plsql_code_type='INTERPRETED'# Default 11i setting
*.plsql_native_library_dir='/u03/db/tech_st/10.2.0/plsql/nativelib'
*.plsql_native_library_subdir_count=149
*.plsql_optimize_level=2# Required 11i setting
*.processes=200# Max. no. of users x 2
*.query_rewrite_enabled='true'
*.session_cached_cursors=500
*.sessions=400# 2 X processes
*.sga_target=1G
*.shared_pool_reserved_size=40M
*.shared_pool_size=400M
*.standby_archive_dest='LOCATION=/u03/db/tech_st/10.2.0/dbs/arch'
*.timed_statistics=true
*.undo_management='AUTO'# Required 11i setting
*.undo_tablespace='APPS_UNDOTS1'# Required 11i setting
*.user_dump_dest='/u03/db/tech_st/10.2.0/admin/KMC_kmcpgw1/udump'
*.utl_file_dir='/usr/tmp','/usr/tmp/KMC/','/u03/db/tech_st/10.2.0/appsutil/outbound/KMC_kmcpgw1','/usr/tmp'
*.workarea_size_policy='AUTO'# Required 11i setting

Hi
i have tried tried
sql>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
Database AlteredBut still no logs get applied.
The altert log is showing the following error:--
Sat Nov 13 12:28:50 2010
Errors in file /u03/db/tech_st/10.2.0/admin/KMC_kmcpgw2/bdump/kmc_mrp0_28971.trc:
ORA-01110: data file 1: '/u03/db/apps_st/data/system01.dbf'
ORA-01122: database file 1 failed verification check
ORA-01110: data file 1: '/u03/db/apps_st/data/system01.dbf'
ORA-01206: file is not part of this database - wrong database id
Sat Nov 13 12:28:50 2010
MRP0: Background Media Recovery process shutdown (KMC)
Sat Nov 13 12:28:51 2010
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSIONand the trace file kmc_mrp0_28971.trc is showing the following error:--
MRP0: Background Media Recovery terminated with error 1110
ORA-01110: data file 1: '/u03/db/apps_st/data/system01.dbf'
ORA-01122: database file 1 failed verification check
ORA-01110: data file 1: '/u03/db/apps_st/data/system01.dbf'
ORA-01206: file is not part of this database - wrong database id
*** 2010-11-13 12:28:50.299 1200 krsm.c
Managed Recovery: Not Active posted.
ORA-01110: data file 1: '/u03/db/apps_st/data/system01.dbf'
ORA-01122: database file 1 failed verification check
ORA-01110: data file 1: '/u03/db/apps_st/data/system01.dbf'
ORA-01206: file is not part of this database - wrong database id
ARCH: Connecting to console port...
*** 2010-11-13 12:28:50.302 64165 kcrr.c
MRP0: Background Media Recovery process shutdown
*** 2010-11-13 12:28:50.302 1200 krsm.c
Managed Recovery: End-Of-Redo posted.
*** 2010-11-13 12:28:50.302 1200 krsm.cPlease help.

Standby databse - init file

Dear all,
Its going well with the creation of the physical standby database. I have copied the dbf, stbycf.ctl, init_stby.ora file to the standby system.
Now I need to modify the init_stby.ora file. This file has to be modified in standby system or the primary system. Please reply to this.
Thanks
SL

ORA-16009 remote archive log destination must be a STANDBY database
Cause: The database associated with the archive log destination service name is other than the required STANDBY type database. Remote archival of redo log files is not allowed to non-STANDBY database instances.
Action: Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing.
I earnestly recommend you to double check the steps you have taken. Uncle Oracle is saying that the remote database is not a standby database. I have already given a link for creating physical database. Follow step-by-step and get the success. Good luck.

Standby databse for a query database

Hi,
Can I use a standby database to make a query database.
My idee is :
create a standby database on production,
daily open this one in read/only,
and nightly recover standby database.
Is it available ?
thanks in advance for your help.
gnom92.

There is no rule of thumb. It really depends on how much REDO is generated by the primary database. If the primary is CPU-bound processing transactions 24 hours a day, it will take a lot longer to recover the standby than it would if the primary has a moderate transaction volume.
If you have tested your recovery plan recently, you can probably make a pretty good estimate, since that is basically what the standby is doing. If it takes you an hour to apply a day's worth of archive logs to recover your system, it will take an hour to recover your standby database (assuming identical hardware & software configuration).
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

Physical standby databse

I am using 10g release 2, my question is Physical standby swichover without downtime or manually should start the standby database.

you will have a short downtime while switching over.
It depends on the startupt time you need for the instance.
You can follow both alert.log files and see which processes are started and when the databases are shut down and restarted.
And of course you have to ensure that your listener-configuration is correct so the application or whatever is able to reach the new site.
Edited by: torgum on Nov 3, 2009 11:27 AM

ORACLE8I에서 STANDBY DB 구성 및 관리 방법

제품 : ORACLE SERVER
작성날짜 : 2004-08-16
database crash 시 backup받아둔 datafile과 archive file을 모두 restore하고,
recover하는 작업은 경우에 따라 고객의 요구 사항보다 길어지는 경우가 종종
있다.
이런 경우 미리 standy db를 구성하여 standby db에 recovery를 진행해 두고,
piramry db crash시 바로 stadnby db와 연결하면, db down time을 최소화하는데
많은 도움이 된다.
Oracle 8.1부터 이 standby db에 새로운 기능이 추가되어, 이전 version에서,
주기적으로 archive file 적용 및 recover 작업을 수행해야 하는 필요를 덜어
주었다.
단, Automated Standby database Feature는 8i~10g Standard Edition에서는
지원하지 않는다.
이 문서에서 자세한 설정 방법 및 추가된 기능들을 확인한다.
1. 추가된 기능 정리
(1) primary db에서 archive file생성시 standby db에도 자동 전달
(2) standby db에 전달된 archive file이 자동으로 standby db에 적용
(3) standby db activate없이, standy db를 read only mode로 open
2. 구성 절차
(1) standby db가 구성될 system에 oracle을 primary db와 동일한 version으로
install한다.
- OS는 primary db와 동일해야 한다.
- database는 install할 필요없이, software만 install하면 된다.
- datafile, controlfile, redo log file이 생성될 directory를 만들어
둔다.
(가능하면 primary db와 동일한것이 좋다),
(2) primary db의 init.ora를 standby db에 copy한다.
- primary db의 $ORACLE_HOME/dbs/initSID.ora file을 standby db에
copy한다.
- initSID.ora file에 ifile=로 정의된 file이 있다면 그 file도 해당
directory에 copy한다.
- 이러한 initial parameter중 background_dump_dest, user_dump_dest,
core_dump_dest, archive_log_dest 등에 지정된 directory도 standby 쪽,
server에 생성해둔다.
(3) primary db에 multiple archive destination을 위한 parameter지정
다음과 같은 형태로 primary db를 위한 archive parameter외에,
standby db쪽에 자동으로 archive file이 생성되도록 destination을
initSID.ora file에 지정한다.
log_archive_start = true
log_archive_dest_1 = "location=/user/oradata/archive"
log_archive_format = arch%s.arc
log_archive_dest_2 = 'SERVICE=sby OPTIONAL REOPEN=60'
log_archive_dest_state_2 = ENABLE
- 이 예에서 sby라는 것은 primary db의 tnsnames.ora file에 미리
정의되어 있어야 하며, standby db에 대한 description을 가져야 한다.
- REOPEN은 standby db쪽으로 archive가 실패한경우 지정된 초만큼 후에
다시 archive를 시도하라는 의미이다.
- OPTIONAL의 의미는 지정된 archive가 실패하는 경우라도 primary db의
log_archive_dest_1에 지정된 곳에 archive만 성공하면 archive작업을
중단없이 계속 진행하라는 것이다.
(4) standby db의 initSID.ora file 수정
primary db에서 자동으로 전달되어온 archive file이 위치하게 될
destination과 datafile이나 redo log file이 위치할 directory 구조가
primary db와 다른 경우를 대비한 parameter를 다음 예와 같이 설정한다.
standby_archive_dest=/user/oradata/archive
log_archive_start = true
log_archive_dest_1 = "location=/user/oradata/archive"
log_archive_format = arch%S.ARC
db_file_name_convert="PROD","SBY"
log_file_name_convert="PROD","SBY"
- standby_archive_dest는 primary db에서 multiple archive destination을
지정하는 경우 자동으로 생성될 archive file의 위치를 나타낸다.
- standby_archive_dest뒤에는 log_archive_dest와 같은 location=은
적으면 안된다. 적을시엔 자동으로 archive가 전달되지 않고, primary db의
alert.log에 오류가 기록된다.
- 실제 recover시나 이후 open되어 archive가 생성되는 시에는
log_archive_dest 부분이 참조된다.
- db_file_name_conver나 log_file_name_convert의 경우는, primary db와
standby db간에 datafile, redo log file이 위치하는 directory가 다른
경우 directory 이름중 다른 부분을 치환하도록 하는 것이다.
이 경우 primary db는 /user/oradata/PROD directory에 file이 존재하고,
standby db는 /user/oradata/SBY directory에 위치하는 경우에 대한 예이다.
- 만약 datafile이 여러군데 나뉘어져 있어 이런 변경 부분이 더 필요하다면
다음과 같이 할 수 있다.
db_file_name_convert=('/dbs/t1/','/dbs/t1/s_','dbs/t2/','dbs/t2/s_')
- WindowsNT의 경우는 반드시 directory이름을 반드시 대문자로 하여야 한다.
(5) standby db용 controlfile을 생성
다음 문장을 primary db에서 수행한다. 이후 이렇게 생성된 file은
standby db쪽으로 옮겨질 것이다.
SQL> alter database create standby controlfile as
'/user/oradata/temp/control01.ctl';
(5) primary db의 datafile을 backup받아둔다.
db를 shutdown 시켜 cold backup을 받거나, hot backup을 받는다.
tape등에 backup받는 대신 바로 ftp 등으로 standby db disk로
옮겨도 된다.
(6) 위의 (4),(5)에서 만들어진 controlfile과 datafile을 standby db쪽으로
옮긴다.
(7) standby db에서 다음과 같이 수행한다.
os> sqlplus internal
SQL> startup nomount
SQL> alter database mount standby database;
SQL> recover managed standby database;
- 만약 recover managed standby database대신에 그냥
recover standby database하면, ora-279, 280, 289가 발생하면서,
생성된 archive를 manual하게 적용하면 된다.
(8) standby db에서 primary db가 운영중에 test나 다른 목적으로 data를 읽고자
한다면 read only로 open가능
SQL>alter database open read only;
(9) primary db가 crash가 발생하여 standby db를 운영하고자 한다면 다음과 같이
activate시켜야 하며, 이렇게 한 이후로는 이 standby db는 standby 의 속성은
잃게 되며, 이후에 다시 standby db로 구축하려면 다시 (5)번부터 작업을
재수행하여 구축하여야 한다.
SQL>alter database activate standy database;
SQL>shutdown
SQL>startup
- shutdown후 이제는 더 이상 standby db가 아니므로 primary성격의 multiple
archive destination지정 등을 원하는 경우 parameter를 추가하면 된다.
3. managed recover, read only mode open 관리
(1) managed recover
recover managed database를 수행한 창은 계속 새로 전달되온 archive file을
자동으로 recovery를 시켜준다.
이때 필요에 의해 이 자동 recovery를 중단하고자 한다면,
standby에서 다른 session을 연결하여 다음과 같이 수행하면 된다.
SQL>alter database recover managed standby database cancel;
이렇게 하면,
recover managed standby 상태의 창에서,
ora-283, ora-16037 메시지와 함께, managed recovery가 중단되고,
SQL혹은 SVRMGR prompt상태가 된다.
recover managed standby database와 일반, recover standby database는 필요에
따라, 선택하여 사용하면 되며, recover managed standby databse의 경우 이
문장을 실행한 이후에 생성된 archive file만을 자동 recovery한다.
즉, recover managed standby database문장 수행전에 미리 전달되어 온 archive
file이 있다면, 일단 먼저 recover standby database문장을 통해 recovery를
수행한 이후에, recovey managed standby database문장을 수행하여야 한다.
(2) read only mode open
standby db를 standby db 속성은 그대로 유지하면서 dml 외에 data나 dictionary
조회가 필요한 상황에서는
alter database open read only문장을 수행하여 read only mode로 open할 수 있다.
이렇게 조회후에, 다른 작업없이 recover 문장을 수행하면 다시 mount상태가 되는
것이며, 필요하면 다시 open read only를 하여야 한다.
standby db는 운영 중에 shutdown가 mount, open을 마음대로 할 수 있으나
그 때마다 반드시,
startup nomount;
alter database mount standby database;
(필요한 경우 alter database open read only)
문장을 통해 mount나 open 상태가 되도록 하여야 한다.
Reference Documents
<Note:74185.1> Standby Database and Oracle 8.1
<Note:70233.1> How to Create a Oracle 8i Standby Database

How to create a clone of database from STANDBY?

How can i clone a database from physical standby database?

Steps to clone from standby:
1. cancle the managed recovery process on standby
sql>alter database recover managed standby database cancel;
2. Remember your standby databse would be in mount mode.
3. Connect to the auxiliary instance and to the standby database through RMAN
rman target sys/<pwd>@standby auxiliary sys/<pwd>@auxiliary-connection
4. If 11g, then run directly duplicate from active database
rman>duplicate target database to 'auxiliary_db_name' from active database nofilenamecheck;
5. Once, the duplication is done, start the MRP on the standby again
sql>alter database recover managed standby database disconnect from session;
Ok..You are on 10g.
Perform the above steps, but only thing is 1st you need to take the backup of the standby database first.
Refer this Create dev database from standby database
Already steps are given here
Edited by: Shivananda Rao on Mar 9, 2012 9:56 AM

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

OEM and Standby Database

I have not tried but I believe OEM does not automate creation of standby database be it physical or logical. Does it ?

I m on 10.2.0.4 , Solaris os. I saw lot of forum questions on standby databse creation where folks have run into some errors while creating the standby db. No body mentioned that they are getting into errors while creating standby db through OEM or any other kind of automation from Oracle. It seems that all of them were trying to create the standby db manually by ollowing the procedure that Oracle recommends.
Also, is data guard free ? Can I have a standby database without dataguard ? From the procedure, it looks like all you have to do is
creata a log archive destination of type service on the primary so that log can be shipped on the other side. Where does data guard comes in picture?
I am sorry if I sound dumb here but I am new to standby database and stuff like that.

Primary & standby db on same OS plaform but having different OS version

Hi,
I have primary & standby database 10.2.0.4 on AIX 5.3 Operating System platform .
I would like to Upgrade my Operating System(AIX) of standby databse server from 5.3 to 6.0.
Will diffenet Operating System version for primary & standby databases support ?
Thnaks.

so, if my primary db on aix 5.3 & standby db on aix 6.1 plaform, then it will not work
or oracle db will not support for this differnent os versions.
is it right?Yes, along with that I'm asking why you want to choose different versions/releases of OS?
I seen there some issues even if some RPM's are missing. So if the complete version changes then think of it.
Moreover check the certification in support.oracle.com
Recently i checked for Linux 6, it's not yet certified. I'm not sure of unix here. So please do refer http://support.oracle.com
Thanks.

Standby archive gap error ..

I have created a standby database,on the same site where my primary
database running,every thing works fine,but the problem i am facing
is that i am not able to recover my standby database,althogh log
transport service archiveing both the dir,primary abd standby database
and i query the primary database archive log list ;
Primary database
Database log mode Archive Mode
Automatic archival Enabled
Archive destination d:\oracle\admin\db01\arch
Oldest online log sequence 8
Next log sequence to archive 10
Current log sequence 10
Standby Database
Database log mode Archive Mode
Automatic archival Enabled
Archive destination d:\oracle\admin\stdby\arch1
Oldest online log sequence 5
Next log sequence to archive 5
Current log sequence 10
why this archive gap generating in standby databse ?
And how to recover my standy database up to my pr. Database ??
plz don't mention any link i've already gone through it..
plz solve it,the help would be highly appricated..

Hi,
The standby database don't generete archive log, this database only reapply archive log which sended by primary database (into a second arch dest).
In init.ora from your standby database :
Are standby database parameters standby_archive_dest and log_archive_dest_1 equal ?
standby_archive_dest parameter (from standby database) must equal to log_archive_dest_2 parameter (from primary database), is it the case ?
Is your standby database in recovery managed ?
Is standby database listener started ?
Nicolas.

Configuring data guard: how many standby redolog do I need?

Hi all, I want to add a standby databse to my RAC test environment but I don't understanad how many redolog I need.
The main db is a 2 node RAC (10.2.0.4.0); every node has 3 log groups; every log group has 2 logfile (every log group is multiplexed on DG_DATA1/ASR/ and FLASH_RECOVERY_AREA/ASR/ )
The standby db will have all its datafile on the same filesystem, so I already configured the trasnslations parameters:
DB_FILE_NAME_CONVERT='/opt/oracle/app/oracle/oradata1/ASRSB','+DG_DATA1/ASR','/opt/oracle/app/oracle/oradata2/ASRSB','+FLASH_RECOVERY_AREA/ASR'
LOG_FILE_NAME_CONVERT='/opt/oracle/app/oracle/oradata1/ASRSB','+DG_DATA1/ASR','/opt/oracle/app/oracle/oradata2/ASRSB','+FLASH_RECOVERY_AREA/ASR'
Replication via rman works well, but I have to manually add the standby redolog on the standby db and which formula to use to calculate the number of the standby redolog needed. Which is the correct formula between :
1)
# of standby log = ( # of redolog files + 1) * # of thread = (6 +1)*2 = 14 standby redolog files
2)
# of standby log = ( # of redolog groups + 1) * # of thread = (3 +1)*2 = 8 standby redolog files
thanks,
andrea

Andrea,
I think 8 should be the answer on your question. Because you have 3 log groups and 2 threads therefore (3+1)*2 = 8.
According to the documentation :
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#SBYDB00426
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
I think you may get confused with maximum number of logfiles. But sometimes logfile is used as a synonym to log group. The actual log group files are usually called log members. (for instance MAXLOGFILES parameter specifies the maximum number of log groups and MAXLOGMEMBERS specifies the maximum number of members for each group).
Each additional member in a redo log group is just a multiplexed copy. You can also consider multiplexing the standby redo log files, the same why you do for redo log members.
In order to learn more about the usage, benefits and limitations of Standby Redo Logs (SRL) you can refer to Metalink Note 2193444.1.
I hope this helps.
--Mihajlo

Data block corrupted on standby database (logical corruption)

Hi all,
we are getting the below error on our DRSITE,it is MANUAL PHYSCIAL STANDBY DATABSE...
The following error has occurred:
ORA-01578: ORACLE data block corrupted (file # 3, block # 3236947)
ORA-01110: data file 3: '/bkp/oradata/orcl_raw_cadata01'
ORA-26040: Data block was loaded using the NOLOGGING option
I have checked in the Primary database, that there are some object which are not being logged into the redo logfiles.....
SQL> select table_name,INDEX_NAME,logging from dba_indexes where logging='NO'
TABLE_NAME INDEX_NAME LOG
MENU_MENUS NUX_MENU_MENUS_01 NO
MENU_USER_MENUS MENU_USER_MENUS_X NO
OM_CITY IDM_OM_CITY_CITY_NAME NO
OM_EMPLOYER EMPLR_CODE_PK NO
OM_EMPLOYER IDM_EMPLR_EMPLR_NAME NOOM_STUDENT_HEAD OM_STUDENT_HEAD_HEAD_UK01 NO
OT_DAK_ENTRY_DETL DED_SYS_ID_PK NO
OT_DAK_ENTRY_HEAD DEH_SYS_ID_PK NO
OT_DAK_ENTRY_HEAD IDM_DEH_DT_APPL_REGION NO
OT_DAK_ENTRY_HEAD IDM_DEH_REGION_CODE NO
OT_DAK_REFUNDS_DETL DRD_SYS_ID_PK NO
TABLE_NAME INDEX_NAME LOG
OT_MEM_FEE_COL_DETL IDM_MFCD_MFCH_SYS_ID NO
OM_STUDENT_HEAD IDM_STUD_COURSE NO
13 rows selected.
so the main problem is in the OM_EMPOYER tables if i would delete the indexes from that table recreate it again with the logging clause,and then apply the archvied logs to the DRSITE.WILL THE problem will resolve.
Pls suggest me...

Hi..
Firstly how did you confirm that it was that index only.Can you post the output of
SELECT tablespace_name, segment_type, owner, segment_name
FROM dba_extents WHERE file_id = 3 and 3236947 between block_id
AND block_id + blocks - 1;
This query can take time, if are sure that its the index don't fire this command .
Secondly, when you will drop and recreate the index, it will be logged into the redo logfile.This information will be be logged in to an the archivelog file as its the replica of the redo logfile. Then when you apply this archive log maually, it will drop that index and then recreate it using the same sql.
HTH
Anand

Standby databse ??

Similar Messages

Maybe you are looking for