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.

Similar Messages

Primary and standby init file (switchove/failover)

I have created standby database, its working fine, and logs are copying and being applied. I have successfully opened standby database in read only mode.
Now I want to perform switchover and failover, please check parameters in init file that I have added.
Primary database init file :
*.control_files='D:\oracle\product\10.2.0/oradata/primary/\control01.ctl','D:\oracle\product\10.2.0/oradata/primary/\control02.ctl','D:\oracle\product\10.2.0/oradata/primary/\control03.ctl'
*.db_name='primary'
*.db_unique_name='PRIMARY'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=primaryXDB)'
*.log_archive_dest_1='location=D:\oracle\product\10.2.0\oradata\archive'
*.log_archive_dest_state_1=ENABLE
*.log_archive_dest_state_2=ENABLE
*.log_archive_dest_2='SERVICE=standby LGWR ASYNC'
*.log_archive_format='arc_%s_%t_%r.arc'
*.fal_client='PRIMARY'
*.fal_server='STANDBY'
standby database init file :
*.control_files='D:\oracle\product\10.2.0/oradata/primary/STANDBY_CONTROL.CTL'
*.db_name='primary'
*.db_unique_name='STANDBY'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=primaryXDB)'
*.log_archive_dest_1='location=D:\oracle\product\10.2.0\oradata\archive'
*.log_archive_format='arc_%s_%t_%r.arc'
*.log_archive_dest_state_2=ENABLE
*.fal_server='PRIMARY'
*.fal_client='STANDBY'
*.standby_file_management=auto
Please let me know if I need to add/modify any parameter to perform switchover & failover operations.
Regards.

Have a look on the below links:
http://www.orafaq.com/wiki/DataGuard_implementation_for_Oracle_10gR2_
http://emrebaransel.blogspot.com/2008/08/dataguard-switchover-guide-physical09.html_

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

Protection Mode Vs init file settings

Dear Friends,
In 11g databgurad i am setting the Protection mode of Primary to : Maximum protection at the DB level(so that it uses sync)
But while defining in init file if i say ASYNC for standby DB as mentioned below
LOG_ARCHIVE_DEST_2= 'SERVICE=boston ASYNC
Then will setting will take precednce , SYNC from maximum protection mode defined at DB level (or) ASYNC which is defined in init file?
(or) will it throw error if there is any mismatch?
Regards,
DB

839396 wrote:
Dear Friends,
In 11g databgurad i am setting the Protection mode of Primary to : Maximum protection at the DB level(so that it uses sync)
But while defining in init file if i say ASYNC for standby DB as mentioned below
LOG_ARCHIVE_DEST_2= 'SERVICE=boston ASYNC
Then will setting will take precednce , SYNC from maximum protection mode defined at DB level (or) ASYNC which is defined in init file?
(or) will it throw error if there is any mismatch?No error will be throw. BUT the Protection Mode is revert back to MAXIMUM PERFORMANCE mode.
you can confirm this in the alert log and v$database on the standby DB
SQL> alter database SET STANDBY DATABASE TO MAXIMIZE PROTECTION;
Database altered.
Perform a log switch at the primary DB i.e alter system switch logfile;
SQL> select PROTECTION_MODE from v$database;
PROTECTION_MODE
MAXIMUM PERFORMANCE
SQL> SYNC is a major attributes you need to set, if you want MAXIMUM PROTECTION mode.
HTH
Tobi

Drop a datafile from physical standby's control file

Hi,
I am trying to create a physical standby database for my production...
1) I have taken cold backup of my primary database on 18-Nov-2013...
2) I added a datafile on 19-nov-2013 ( 'O:\ORADATA\SFMS\SFMS_DATA4.DBF' )
3) Standby control file was generated on 20-ov-2013 (today) after shutting down and then mounting the primary database...
When i try to recover the newly setup standby using archive files, i am getting the following error (datafile added on 19th Nov is missing)
SQL> recover standby database;
ORA-00283: recovery session canceled due to errors
ORA-01110: data file 39: 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
ORA-01157: cannot identify/lock data file 39 - see DBWR trace file
ORA-01110: data file 39: 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
How to overcome this situation...
Can i delete the entry for the newly added datafile from the backup control file ?
When i tried to delete datafile using "alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF';", it is showing that database should be open..
SQL> alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
ERROR at line 1:
ORA-01109: database not open
SQL> show parameter STANDBY_FILE_MANAGEMENT
NAME                                 TYPE        VALUE
standby_file_management              string      AUTO
SQL> alter system set STANDBY_FILE_MANAGEMENT=manual;
System altered.
SQL> show parameter STANDBY_FILE_MANAGEMENT
NAME                                 TYPE        VALUE
standby_file_management              string      MANUAL
SQL> alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
ERROR at line 1:
ORA-01109: database not open
Regards,
Jibu

Jibu wrote:
Hi,
I am trying to create a physical standby database for my production...
1) I have taken cold backup of my primary database on 18-Nov-2013...
2) I added a datafile on 19-nov-2013 ( 'O:\ORADATA\SFMS\SFMS_DATA4.DBF' )
3) Standby control file was generated on 20-ov-2013 (today) after shutting down and then mounting the primary database..
Hi,
What is your version?
If you added new datafile or created new tablespace, take backup again for restore new created standby database.
If your standby database running well, DG configuration success, then this datafile will create on standby side, too.
Set STANDBY_FILE_MANAGEMENT=AUTO best practice.
When i try to recover the newly setup standby using archive files, i am getting the following error (datafile added on 19th Nov is missing)
SQL> recover standby database;
ORA-00283: recovery session canceled due to errors
ORA-01110: data file 39: 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
ORA-01157: cannot identify/lock data file 39 - see DBWR trace file
ORA-01110: data file 39: 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
How to overcome this situation...
Can i delete the entry for the newly added datafile from the backup control file ?
Not need any delete datafile from standby side, you must recreate standby database, or you can take RMAN backup and restore to standby side again.
When i tried to delete datafile using "alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF';", it is showing that database should be open..
SQL> alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
ERROR at line 1:
ORA-01109: database not open
SQL> show parameter STANDBY_FILE_MANAGEMENT
NAME                                 TYPE        VALUE
standby_file_management              string      AUTO
SQL> alter system set STANDBY_FILE_MANAGEMENT=manual;
System altered.
SQL> show parameter STANDBY_FILE_MANAGEMENT
NAME                                 TYPE        VALUE
standby_file_management              string      MANUAL
SQL> alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
ERROR at line 1:
ORA-01109: database not open
It is not logical, Physical standby must be bit-for-bit same with Primary database.
Regards
Mahir M. Quluzade

Logical Standby 'CURRENT' log files

I have an issue with a Logical Standby implementation where although everything in the Grid Control 'Data Guard' page is Normal, when I view Log File Details I have 62 files listed with a status of 'Committed Transactions Applied'.
The oldest (2489) of these files is over 2 days old and the newest (2549) is 1 day old. The most recent applied log is 2564 (current log is 2565).
As for the actual APPLIED_SCN in the standby, it's greater than the highest NEXT_CHANGE# for newest logfile 2549. The READ_SCN is less than the NEXT_CHANGE# of the oldest log (2489) appearing in the the list of files - which is why all these log files appear on this list.
I am confused why the READ_SCN is not advancing. The documentation states that once the NEXT_CHANGE# of a logfile falls below READ_SCN the information in those logs has been applied or 'persistently stored in the database'.
Is it possible that there is a transaction that spans all these log files? More recent logfiles have dropped off the list and have been applied or 'persistently stored'.
Basically I'm unsure how to proceed and clean up this list of files and ensure that everything has been applied.
Regards
Graeme King

Thank you Larry. I have actually already reviewed this document. We are not getting the error they list for long running transactions though.
I wonder if it is related to the RMAN restore we did where I restored the whole standby database while the standby redo log files were not obviously restored and therefore were 'newer' than the restored database?
After I restored I did see lots trace files with this message:
ORA-00314: log 5 of thread 1, expected sequence# 2390 doesn't match 2428
ORA-00312: online log 5 thread 1: 'F:\ORACLE\PRODUCT\10.2.0\PR0D_SRL0.F'
ORA-00314: log 5 of thread 1, expected sequence# 2390 doesn't match 2428
ORA-00312: online log 5 thread 1: 'F:\ORACLE\PRODUCT\10.2.0\PR0D_SRL0.F'
I just stopped and restarted the SQL apply and sure enough it was cycled through all the log files in the list from the (READ_SCN onwards) but they are still in the list. Also there is very little activity on this non-production database.
regards
Graeme

Standby redo log file

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

What is the purpose of standby redo log files

Hi,
What is the purpose of the standby redo log files in DR?
what if the standby redo log files are created? or else not created?
Please explain
Thanks

3.1.3 Configure a Standby Redo LogA 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.>
Reference http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#i1225703
HTH
Anand

Unassigned Status Of Standby Redo Log Files

I created 2 standby redo log groups, and use LGWR in primary site to
transfer redo data, all are good. But when I query the V$STANDBY_LOG
view, I found that the status column of my both standby redo logs is UNASSIGNED".
also sequence#
THREAD# and all others are 0 and 0.
Any explains.

Thanks for the reply Sophie. I did perform log switch at my primary site but the status of standby redo log files remained unassinged. I am pasting here the message in my Alert Log file may be that can help you to diagonose the problem.
ALTER DATABASE SET STANDBY DATABASE PROTECTED
Tue Jul 26 15:35:18 2005
Completed: ALTER DATABASE SET STANDBY DATABASE PROTECTED
Tue Jul 26 15:35:22 2005
ALTER DATABASE OPEN
Tue Jul 26 15:35:23 2005
LGWR: Primary database is in CLUSTER CONSISTENT mode
LGWR: Primary database is in MAXIMUM PROTECTION mode
LGWR: Destination LOG_ARCHIVE_DEST_1 is not serviced by LGWR
LNS0 started with pid=18
Tue Jul 26 15:35:28 2005
LGWR: Error 16086 verifying archivelog destination LOG_ARCHIVE_DEST_2
LGWR: Continuing...
Tue Jul 26 15:35:28 2005
Errors in file e:\oracle\admin\test\bdump\test_lgwr_1864.trc:
ORA-16086: standby database does not contain available standby log files
LGWR: Error 16086 disconnecting from destination LOG_ARCHIVE_DEST_2 standby host 'TESTstdb'
LGWR: Minimum of 1 applicable standby database required
Tue Jul 26 15:35:28 2005
Errors in file e:\oracle\admin\test\bdump\test_lgwr_1864.trc:
ORA-16072: a minimum of one standby database destination is required
LGWR: terminating instance due to error 16072
Instance terminated by LGWR, pid = 1864

Dataguard lost both Primary redo log and standby redo log files

Hi,
I am new to data guard, i came acorss a scenario where we loose both primary redo log file and standby redo log files.
Can someone please help me understand how to recover from this situation.
Thanks!

>loose both primary redo log file and standby redo log files
We have to be very clear.
There are (set A) online redo log files and (set B) standby redo log files at (location 1) Primary and (location 2) Standby.
The standby redo log files, depending on the configuration, aren't strictly mandatory. The standby can be applying redo without online redo log files present as well, depending on how it was setup.
So, the question is : Did you lose online redo log files at the primary ? Didn't the primary shutdown itself then ? If so, you have to do an incomplete recovery at the primary OR switch over to the standby (which may or may not have received the last transaction, depending on how it was configured and operating) OR restore from the standby (again, with possible loss of transactions) to the primary.
Hemant K Chitale

Use of standby redo log files in primary database

Hi All,
What is the exact use of setting up standby redo log files in the primary database on a data guard setup?
any good documents?

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.
refer the link,and Perform the following steps to configure the standby redo log.:-
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#i1225703
If the real-time apply feature is enabled, log apply services can apply redo data as it is received, without waiting for the current standby redo log file to be archived. This results in faster switchover and failover times because the standby redo log files have been applied already to the standby database by the time the failover or switchover begins.
refer the link
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/log_apply.htm#i1023371

Standby destination control file enqueue unavailable

Hi,
more than two days ..totally i tried 3 times for creating standby database in oralce 10g ..everthing working fine but i didnt get archive log from primary database..please help me
NOTE: both primary and standby database on same system
*#standby database 'stby' (omitted common parameters)*
*.compatible='10.2.0.3.0'
*.control_files='d:\oracle\product\10.2.0\oradata\stby\controlsb01.ctl','d:\oracle\product\10.2.0\oradata\stby\controlsb02.ctl','d:\oracle\product\10.2.0\oradata\stby\controlsb03.ctl'
*.db_file_name_convert='D:\oracle\product\10.2.0\oradata\live','D:\oracle\product\10.2.0\oradata\stby'
*.db_name='live'
*.fal_client='stby'
*.fal_server='live'
*.log_archive_config='DG_CONFIG=(live,stby)'
*.log_archive_dest_1='LOCATION=D:\oracle\product\10.2.0\flash_recovery_area\stby VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=stby'
*.log_archive_dest_2='SERVICE=live ARCH ASYNC VALID_FOR=(ONLINE_LOGFILE,PRIMARY_ROLE) DB_UNIQUE_NAME=live'
*.log_file_name_convert='D:\oracle\product\10.2.0\oradata\live','D:\oracle\product\10.2.0\oradata\stby'
*.remote_login_passwordfile=EXCLUSIVE
*.standby_file_management='AUTO'
*.instance_name=stby
*.db_unique_name=stby
*#primary database 'live'*
*.compatible='10.2.0.3.0'
*.control_files='d:\oracle\product\10.2.0\oradata\live\control01.ctl','d:\oracle\product\10.2.0\oradata\live\control02.ctl','d:\oracle\product\10.2.0\oradata\live\control03.ctl'
*.db_file_name_convert='D:\oracle\product\10.2.0\oradata\stby','D:\oracle\product\10.2.0\oradata\live'
*.db_name='live'
*.fal_client='live'
*.fal_server='stby'
*.log_archive_config='DG_CONFIG=(live,stby)'
*.log_archive_dest_1='LOCATION=D:\oracle\product\10.2.0\flash_recovery_area\live VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=live'
*.log_archive_dest_2='SERVICE=stby ARCH ASYNC VALID_FOR=(ONLINE_LOGFILE,PRIMARY_ROLE) DB_UNIQUE_NAME=stby'
*.log_file_name_convert='D:\oracle\product\10.2.0\oradata\stby','D:\oracle\product\10.2.0\oradata\live'
*.remote_login_passwordfile=EXCLUSIVE
*.standby_file_management='AUTO'
*.instance_name=live
*.DB_UNIQUE_NAME=live
*#standby database*
SQL> STARTUP MOUNT
ORACLE instance started.
Total System Global Area 251658240 bytes
Fixed Size 1290012 bytes
Variable Size 159383780 bytes
Database Buffers 83886080 bytes
Redo Buffers 7098368 bytes
Database mounted.
SQL> alter database recover managed standby database disconnect from session;
Database altered.
SQL> select group#,member from v$logfile;
GROUP#
MEMBER
3
D:\ORACLE\PRODUCT\10.2.0\ORADATA\STBY\REDO03.LOG
2
D:\ORACLE\PRODUCT\10.2.0\ORADATA\STBY\REDO02.LOG
1
D:\ORACLE\PRODUCT\10.2.0\ORADATA\STBY\REDO01.LOG
GROUP#
MEMBER
4
D:\ORACLE\PRODUCT\10.2.0\ORADATA\STBY\SREDO04.LOG
5
D:\ORACLE\PRODUCT\10.2.0\ORADATA\STBY\SREDO05.LOG
6
D:\ORACLE\PRODUCT\10.2.0\ORADATA\STBY\SREDO06.LOG
6 rows selected.
*#primary database*
SQL> ALTER SYSTEM SWITCH LOGFILE;
SQL> select SEQUENCE#, applied from v$archived_log;
SEQUENCE# APP
15 NO
16 NO
17 NO
18 NO
19 NO
20 NO
SQL> SELECT SEQUENCE#,STATUS FROM V$MANAGED_STANDBY;
SEQUENCE# STATUS
0 CONNECTED
19 CLOSING
20 CLOSING
0 CONNECTED
0 CONNECTED
0 CONNECTED
0 CONNECTED
0 CONNECTED
*#standby database*
SQL> select * from v$archived_log;
no rows selected
*#see even my standby database open .*
SQL> alter database open;
Database altered.
*# listener.ora*
STBY =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = selvaPC)(PORT = 2031))
LIVE =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = selvaPC)(PORT = 2030))
SID_LIST_STBY =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = live)
(SID_NAME = stby)
SID_LIST_LIVE =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = live)
(SID_NAME = live)
*# tnsnames.ora*
STBY =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = selvaPC)(PORT = 2030))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = live)
LIVE =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = selvaPC)(PORT = 2031))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = stby)
*#Error in alert file..during startup primary database*
Controlfile lock conflict at host 'stby'
Possible invalid cross-instance archival configuration
ORA-16146: standby destination control file enqueue unavailable
thanks
selva..

If you user this then a lot of information ( threads) can be found with the same problem.
Anyway the original ORA-message/solution is:
Error:     ORA-16146 (ORA-16146)
Text:     standby destination control file enqueue unavailable
Cause:     The target standby destination control file is currently
     unavailable to the Remote File Server (RFS) process. This
     indicates that the target destination is the primary database
     itself.
Action:     Check for and eliminate the standby destination archive log
     parameter in question.
This means you have an error in the log_archive_dest entries on the standby server.
Can you use Dataguard Manager (dgmgrl) to verify the configuration?
Edit:
Our Dataguard config e.g. has on primary:
log_archive_config='dg_config=(STDBY)'
On the standby it is:
log_archive_config='dg_config=(PRIMARY)'

Do I need to create new group for standby redo log files?

I have 10 group of redo log files with 2 members for each group for my primary database , Do I need to create new group for standby redo log files for the standby database
Group#     Members
==============
1              2
2              2
3             2
4             2
5             2
6             2
7             2
8             2
9             2
10           2
If So, The following statment is correct? or nto
ALTER DATABASE ADD STANDBY LOGFILE GROUP 1 ('D:\Databases\epprod\StandbyRedoLog\REDO01.LOG',D:\Databases\epprod\StandbyRedoLog\REDO01_1.LOG');
please correct me if am doin mistake
becuase when I issue the statment I getting error message sayin the group is already created.

Thanks John
I just find the answer
Yes, it's recomeded to add new group , for instnace If I have 10 group from 1 to 10 then the standby shoudl be from 11 to 20
Thanks I found the answer.

Missing parameters in init file

Dear All,
What would happen is following parmeters are missing in the init file of Oracle11g Database?
*.dispatchers='(PROTOCOL=TCP) (SERVICE=xyzXDB)'
*.shared_servers=1
Thanks

user9291399 wrote:
Dear All,
What would happen is following parmeters are missing in the init file of Oracle11g Database?
*.dispatchers='(PROTOCOL=TCP) (SERVICE=xyzXDB)'
*.shared_servers=1
Thanksyour database will operate just fine, but it will not accept shared server connections, only dedicated server.
For more info, you might look at the section on initialization parameters in fine Reference Manual found at tahiti.oracle.com

Dataguard Solution for standby redo log file groups

Respected Experts,
My database version is 10.2.0.1.0 and Red Hat 5 os.I want to create a standby database using RMAN.
Can any one help me with the full steps.And i'm also confuse about number of standby redo log file members
need to be created.
Thanks and Regards
Monoj Das

My database version is 10.2.0.1.0 and Red Hat 5 os.I want to create a standby database using RMAN.To configure standby either you can use duplicate target database for standby
or
1) restore standby controlfile
2) mount standby database
3) restore database
and configure standby paraemter then start MRP, will do.
http://docs.oracle.com/cd/B19306_01/server.102/b14239/create_ps.htm
Can any one help me with the full steps.And i'm also confuse about number of standby redo log file members
need to be created.It depends which parameter you want to use, if you mention log_archive_dest_2='service ARCH ' then no need to create any standby redo log file groups,
If you use log_archive_dest_2='service LGWR ' here transport will be in terms of redo and you need standby redo log files on standby database. Which is realtime.
When you use LGWR, data lost will be less if in case of any online redo log file lost. which is recommended.
HTH.

Standby databse - init file

Similar Messages

Maybe you are looking for