Manual physical standby Db configuration...

Hi all,
We are using oracle 9.2 db on sun box, suddenly we faced problem in our DRSITE,one of the disk got unmounted.
and i have been told that we have to build another db .
Re: ORA-01110: data file 201: '/bkp/oradata/orcl_raw_system01'
{code]
i want to know in case of manual physical standby db can the configuration be differ or not...ile.
primary: sun solaris
drsite: rhel
can it be possible or not....
pls suggest me.

can it be possible or not....It cannot, the documentation has all necessary informations:
http://download.oracle.com/docs/cd/B10501_01/server.920/a96653/considerations.htm#52221
Werner

Similar Messages

How to open a "manual" Physical standby database in read/write mode

Hi,
I am running Oracle Database 10g Release 10.2.0.3.0 - 64bit Production Standard Edition on Linux version 2.6.9-42.0.8.ELsmp ([email protected]) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-3))
I've created a physical standby database, but since I am running Standard Edition, I am not using the DataGuard features. I use the rsync utility to copy over the archivelogs to the standby database, and I apply them periodically to the standby database.
The standby database is started this way :
startup nomount pfile='/u01/oradata/orcl/initorcl.stdby';
alter database mount standby database;
Everything runs perfectly fine, I can do "alter database open read only" and then I can do selects into tables to confirm that everything is up to date.
The thing is, if I shutdown immediate the database, then do just startup :
shutdown immediate;
startup;
The database opens with no error messages, but is still in read-only mode...
I read that the default behavior for a standby database is to open read-only, like I am experiencing, but I would like to know what is the right way to open it correctly in read-write mode (I understand that after that, my standby will not be standby anymore and that I will have to recreate my standby database).
Thanks,
Mat

Hello,
There're features which allows you to open a Standby database in Read/Write mode but for all I know
it needs Entreprise Edition.
In Enterprise Edition you can use Logical Standby database. More over, for Physical standby there's
a way by using flashback database so as to rolling backward the database and avoiding to recreate
the Standby.
In Standard Edition I'm afraid that you'll have to recreate your Standby database.
Best regards,
Jean-Valentin

Dgmgr - physical standby database

Hi,
We are having Oracle 10g R2 (latest patch) . We have created a primary - physical standby database configuration. While the show database verbose 'dbname' in dgmgrl shows "success" for standby , it flags the following error for the primary
Warning: ORA-16801: redo transport-related property is inconsistent with database setting
Can this be ignored safely ? If not how to eliminate this.
Also brief me safest way to switch over between primary and standby databases.
Thanks.

This warning occurs when you mix manual configuration and dataguard broker, use only one method,not both:
Oracle Error :: ORA-16801
redo transport-related property is inconsistent with database setting
Cause
The values of one or more redo transport-related configuration properties were inconsistent with database in-memory settings or server parameter file settings. This may happen by altering initialization parameters directly instead of altering property values using Data Guard broker.
Action
Query property the InconsistentLogXptProps on the primary database or check the Data Guard broker log to find which properties are set inconsistently. Reset these properties to make them consistent with the database settings. Alternatively, enable the database or the entire configuration to allow the configuration property settings to be propagated to to the initialization parameters.
Werner

Physical standby creation

Hi All,
Environment - Production and Disaster Recovery Centre have a active passive cluster on solaris 10. Oracle version - Oracle 11gR2.
Want to Set up Physical Standby and configure a DG Broker to manually manage the DG.
I have gone through the steps as per MOS 1075908.1. Is it similar OR what additional steps needed.
Please advise

>
Want to Set up Physical Standby and configure a DG Broker to manually manage the DG.
I have gone through the steps as per MOS 1075908.1. Is it similar OR what additional steps needed.I assume you mean "automatically", not "manually"? The extra steps are to enable the Broker! Start the DMON processes, create your configuration, add your databases, enable the configuration, sit back and relax.
Have a go, it is pretty straightforward.

Sys passowd change effect in physical standby environment.

Hi All,
We have a production environment with physical standby environment configured for it. Everything is working fine. My issue is with the sys password. We have a policy of changing sys password every month.
1) What should be the step by step process to reflect the same sys password to standby database?
2) As per one of the fourms, copying the production system's password file to standby database should work. but i am not sure is just copying the password file will change the change the password in standby database. As the standby database is in recovery mode (mount stage) what will be the best way of doing this?
Thanks
Shelly

Hi Shelly,
1) What should be the step by step process to reflect the same sys password to standby database?
change the sys pass in prodshudown and restart to check if the new password ids in effect
In standby you have options
cancel managed recovery and recraete a new password file (same password as primary)
or
(easy way)
Simply copy the prod modified password file to standby and restart managed recovery.

Datafile autoextend off possible in Physical standby?

Hi,
I am making datafiles auto extend off in primary database. is there anything i should do in standy database as well?
i have 10.2.0.4 version in IBM AIX machines with physical standby database configured...
I have standby_file_management is AUTO...
Any suggestions?
Thanks,
Raman.
standby_file_management string AUTO
SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE 10.2.0.4.0 Production
TNS for IBM/AIX RISC System/6000: Version 10.2.0.4.0 - Productio
NLSRTL Version 10.2.0.4.0 - Production

Means standy database will automatically propgate change of auto extend off? as DBA we dont do anything?Well, i have not tested it recently, but in back of my memories which i am trying to recall i have done it.For datafile/tablespace related standby_file_management parameter has to be set to auto, which is already set so you must must not face any problem.You can monitor the alert log file of the standby database.
Anand

Db_file parameter change in oracle 8i with physical standby configured

i have oracle 8i (8.1.7) with physical standby configured.
i need to change the db_file parameter value. kindly check the below steps are correct? Thanks.
1. alter database backup controlfile to trace;
2. edit the init.ora file as db_file=<new value> (after backing up the existing pfile)
3. edit the create control file statement in udump -- max datafile (and also remove the first line startup nomount)
4. shutdown immediate;
5. startup pfile ='file name';
6. in sqlplus run the create control file statement;
7. alter database backup controfl file for standby;
8. move the standby control file to standby db server
9. shutdown immediate in standby
10. copy the pfile and edit the new values
11. startup mount pfile='new pfile' (in standby)
12. recover control file <location> from rman
13. start the recovering of standby.
Thanks,
Raman.

Just change the db_files value to some higher value in the init.ora file and restart the database. With this you can create more datafiles no need to create control file.

Configuring a physical standby database in 9i

Hi all,
   SO: Solaris 10 SPARC x64
   DB: 9.2.0.6 x64
   I have a task of creating a physical standby database in a solaris 10 - Oracle 9.2.0.6 env. I am used to do this configuration on the 11.2 version of Oracle, and because of that i have some doubts regarding the possible different configurations necessary to do in a 9i Database.
   1) The main doubt that i have is regarding the RMAN use. I Would like to know if it is possible to restore a normal backup of my primary database into the standby database, and after that, apply the necessary archived logs to sync the standby with the primary? The controlfile that i would use would be the one created by the "BACKUP CURRENT CONTROLFILE FOR STANDBY" RMAN command. The RMAN script woulb be like the one below:
run {
allocate channel ch01 device type disk;
allocate channel ch02 device type disk;
allocate channel ch03 device type disk;
allocate channel ch04 device type disk;
restore controlfile from 'standby_controlfile.ctl';
sql 'alter database mount';
restore database;
recover database;
   2) The directory structure will be the same, so i think it is not necessary to use the SET NEWNAME and the DB_FILE_NAME_CONVERT/LOG_FILE_NAME_CONVERT, is that correct?
   3) Do you have any other considerations regarting the differences between a 9i and a 11g Physical Standby Configuration?
Thanks for your attention and pacience.

Hello;
On question 1 - See this:
http://docs.oracle.com/cd/B10500_01/server.920/a96566/rcmstand.htm
On question 2 - Assuming RMAN work then DB_FILE_NAME_CONVERT/LOG_FILE_NAME_CONVERT would NOT have to be set for the same directory structure.
On question 3 - double check this:
http://docs.oracle.com/cd/B10500_01/server.920/a96653.pdf
Best Regards
mseberg

Starting a Physical Standby DB which is configured with real-time apply

Hi,
I wanted to get clarification on the correct procedure for starting and stopping a physical standby database. The Dataguard documentation states the following:
1. Start and mount the database:
SQL> STARTUP MOUNT;
2. Start log apply services:
To start Redo Apply, issue the following statement:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
2> DISCONNECT FROM SESSION;
To start real-time apply, issue the following statement:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
2> USING CURRENT LOGFILE;
My configuration is using real-time apply based on the information provided by the RECOVERY_MODE column of the V$ARCHIVED_DEST_STATUS view. Should I execute both ALTER statements or just the second one. If only the second one, how will the database re-synchronize, especially after a long down time. Also, must I do anything on the primary database prior to starting up the physical standby?
I'm using Oracle 10g SP1 on a linux server.

No. But you can recover until the last arch file generated on the primary, then you cancel the recovery and then use query#2 to start applying real-time. Refer to Note:343424.1 on Metalink.

Oracle Configuration Manager 10.2.7 on physical standby database

Hi
Did anybody succeed to install and get running OCM on physical standby-database? When starting collection configuration script, i get
an known error ORA-01219.
Any help any tipps?
Felice

Hi Tom
Thank you for the information. I think it is the right place to install OCM - not standalone installation - software installed with Oracle Database Enterprise Edition. The problem is only that installCCRSQL.sh can't handle Mounted Database (Standby-Database).
We got similar problems with Grid Control Management Agents, when doing health checks.
Mayby there is as workaround/patch (Opatch).
Regards
Felice

Can I configure capture process of streams on physical standby

we have high oltp system that has dataguard setup with physical and logical. We are planning to build a datawarehouse and have streams setup for data feeding into the datawarehouse. Instead of taxing the primary, i was wondering if i could set up the physical standby as the source for my streams (basically configure the capture process on physical standby).
Appreciate your help in advance!
Thanks

Thanks for the reply Tekicora
This means then On the primary, I will have another destination that I send the archives to (In addition to Physical) that will be my source database for streams where I can configure capture process. if this understanding is right, then i have the following questions
1) Can i use cascaded standby to relieve my primary from having another log destination and use that database for the source
2) Do you know if PSB can be used as source in 11g? because we are planning to move to 11g soon.
Thanks
Smitha

Physical Standby Configuration Issue

Hi All,
DB Version:10.2.0
OS Version:Windows
I am trying to create Physical standby DB on the same machine where my pri db is running for testing purpose. I am following the Official Doc for configuring the physical standby
docs.oracle.com/cd/B19306_01/server.102/b14239/create_ps.htm
But this time what happens with me when i configure all the things as per the doc and issue
SQL>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION; on standby
what i saw redo files redo01,redo02,redo03 are generated again in standby folder which already contains standby logfiles. And this gnerates an error of unable to read file redo03.log on the standby path when i check the aler log files of standby db.below are my pfile for sec db:
*.audit_file_dest='E:\oracle\product\10.2.0\admin\pak\adump'
*.background_dump_dest='E:\oracle\product\10.2.0\admin\pak\bdump'
*.compatible='10.2.0.1.0'
*.control_files='E:\oracle\product\10.2.0\oradata\pak\control01.ctl'
*.core_dump_dest='E:\oracle\product\10.2.0\admin\pak\cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_file_name_convert='india','pak'
*.db_name='india'
*.db_recovery_file_dest='E:\oracle\product\10.2.0/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.db_unique_name=pak
*.dispatchers='(PROTOCOL=TCP) (SERVICE=indiaXDB)'
*.fal_client=pak
*.fal_server=india
*.job_queue_processes=10
*.log_archive_config='DG_CONFIG=(india,pak)'
*.log_archive_dest_1='LOCATION=E:\oracle\product\10.2.0\flash_recovery_area\pak\ VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=pak'
*.log_archive_dest_2='SERVICE=india LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=india'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_file_name_convert='E:\oracle\product\10.2.0\oradata\india\','E:\oracle\product\10.2.0\oradata\pak'
*.open_cursors=300
*.pga_aggregate_target=92274688
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=278921216
*.standby_file_management='AUTO'
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='E:\oracle\product\10.2.0\admin\pak\udump'
Kindly help me what i need to do
Thanks all in advance

Hi All,
When I check group# in primary DB by using sql
SQL> select group# from v$log;
it shows me
GROUP#
1
2
3
When i run the same query on standby i am getting the same result
This means that standby is not accessing the standby redo log file
Can anyone help me in this matter

Configuring Non RAC physical standby fro RAC

Hi,
EBS-R12i , Oracle Database:11g
We are in project design phase and following is the hardware setup for Critical banking domain:
Database (2 node RAC)-Solaris 10
Application server server (2 server) -Solaris 10
Web server (2 server for Failover)= RHEL
For DR
Database (1 node)-Solaris 10
need to know
1.What are the best practice to implement this kind of setup and steps to configure DR as Non-RAC physical standby for RAC database server.
2.What are implication if we go for single node except failover node unavailability for DR.
3.What are the steps of Switchover in this case.
4.What's the recommended backup solution for this setup of 8-10 Terabyte database with db growth rate of 50% per year.

1.What are the best practice to implement this kind of setup and steps to configure DR as Non-RAC physical standby for RAC database server.There really aren't any differences in setting up your physical standby in a non-RAC configuration. It is after the physical standby is setup that it is converted to a clustered database, if desired. In your case, you do not desire the conversion.
The best place to start for best practices in setting up your physical standby is the Oracle documentation on the subject.
http://download.oracle.com/docs/cd/E11882_01/server.112/e17022/toc.htm
2.What are implication if we go for single node except failover node unavailability for DR.The major implications are that you will be running with less horsepower after a failover. So depending on your DR resources, you may have to scale back application access. In addition to less resources, you will also have less availability because you only have one node. Should that node then fail, you will not have a node to failover to.
3.What are the steps of Switchover in this case.The steps are identical if the physical standby is a single node or multiple nodes. These steps are outlined in the Oracle documentation.
4.What's the recommended backup solution for this setup of 8-10 Terabyte database with db growth rate of 50% per year.What are your recovery requirements? Without knowing your recovery requirements, a valid backup solution cannot be determined. How much data loss can you afford in the event of a failure? Do you have data that can be read only? In the event of a failure, how long before you are required to be up and running? Are you required to restore and recover at an offsite location?
Cheers,
Brian

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

Problems while creating a physical Standby

Hi,
I am trying to setup a physical standby database with oracle 10g.
I configured a specific log archive destination:
LOG_ARCHIVE_DEST_3 = 'SERVICE=ORAMPSEC REOPEN=60 MAX_FAILURE=3 LGWR SYNC
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=ORAMPSEC'
The service is reachable via network.
To establish the standby database I copied all datafiles from the primary database using scp. I also created a standby controlfile and a modified pfile. In addition I added a standby redo logfile which has the same size as the online redo log files on the primary database.
After starting the standby database in open read only mode I receive the following error message:
Database mounted.
ORA-16004: backup database requires recovery
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oradata/ORAMPPRD/data/system01.dbf'
I tried to recover using "recover standby database" I receive the following message:
ORA-00279: change 884348 generated at 07/18/2006 17:08:07 needed for thread 1
ORA-00289: suggestion : /oradata/ORAMPPRD/archive/1_30_595767954.dbf
ORA-00280: change 884348 for thread 1 is in sequence #30
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
Although I transmitted all archived log files from the primary database the archived log file mentioned above is not available. After hitting RETURN I get this message:
ORA-00308: cannot open archived log
'/oradata/ORAMPPRD/archive/1_30_595767954.dbf'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory Additional information: 3
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oradata/ORAMPPRD/data/system01.dbf'
Here is a listing of all archived logfiles from the primary database:
bash-3.00$ ls -latr
total 494144
drwxr-xr-x 6 oracle oinstall 512 Jul 14 11:03 ..
-rw-r----- 1 oracle oinstall 20732928 Jul 17 11:47 1_6_595767954.dbf
-rw-r----- 1 oracle oinstall 86013440 Jul 17 13:56 1_7_595767954.dbf
-rw-r----- 1 oracle oinstall 214016 Jul 17 13:57 1_8_595767954.dbf
-rw-r----- 1 oracle oinstall 1986560 Jul 17 14:10 1_9_595767954.dbf
-rw-r----- 1 oracle oinstall 150016 Jul 17 14:10 1_10_595767954.dbf
-rw-r----- 1 oracle oinstall 504320 Jul 17 14:17 1_11_595767954.dbf
-rw-r----- 1 oracle oinstall 1807872 Jul 17 14:22 1_12_595767954.dbf
-rw-r----- 1 oracle oinstall 589824 Jul 17 14:25 1_13_595767954.dbf
-rw-r----- 1 oracle oinstall 1190912 Jul 17 14:37 1_14_595767954.dbf
-rw-r----- 1 oracle oinstall 584704 Jul 17 14:42 1_15_595767954.dbf
-rw-r----- 1 oracle oinstall 80896 Jul 17 14:45 1_16_595767954.dbf
-rw-r----- 1 oracle oinstall 6050816 Jul 17 15:08 1_17_595767954.dbf
-rw-r----- 1 oracle oinstall 4238848 Jul 17 16:04 1_18_595767954.dbf
-rw-r----- 1 oracle oinstall 4920832 Jul 17 17:21 1_19_595767954.dbf
-rw-r----- 1 oracle oinstall 1520128 Jul 17 17:30 1_20_595767954.dbf
-rw-r----- 1 oracle oinstall 360960 Jul 17 17:35 1_21_595767954.dbf
-rw-r----- 1 oracle oinstall 89186304 Jul 18 10:52
1_22_595767954.dbf
-rw-r----- 1 oracle oinstall 16216576 Jul 18 14:18
1_23_595767954.dbf
-rw-r----- 1 oracle oinstall 12288 Jul 18 14:18 1_24_595767954.dbf
-rw-r--r-- 1 oracle oinstall 2073 Jul 18 14:26 sqlnet.log
-rw-r----- 1 oracle oinstall 14387200 Jul 18 16:56
1_25_595767954.dbf
-rw-r----- 1 oracle oinstall 116736 Jul 18 16:58 1_26_595767954.dbf
-rw-r----- 1 oracle oinstall 1536000 Jul 18 17:04 1_27_595767954.dbf
-rw-r----- 1 oracle oinstall 156672 Jul 18 17:05 1_28_595767954.dbf
drwxr-xr-x 2 oracle oinstall 1024 Jul 18 17:08 .
-rw-r----- 1 oracle oinstall 65536 Jul 18 17:08 1_29_595767954.dbf
Nothing known about the *30*dbf file.
Although there still seems to be something wrong, the archived log file transmission seems to work since there is no error reported on the log archive destination:
SQL> select status, error from v$archive_dest where dest_id = 3;
STATUS ERROR
VALID
And after I manually force a log switch I see that archived redo logs were applied on the standby database:
select sequence#, applied from v$archived_log order by sequence#;
SEQUENCE# APPLIED
27 YES
28 NO
28 YES
29 NO
29 YES
Unfortunately because of the recovering problem I cannot open the database to see if the changes were applied. So my first question is, how can I get the standby database completely recovered ??
In addition to this I was expecting that the changes to the standby database were made immediately since I choosed LGWR sync but I have to manually force the logfile switch. As I already mentioned a standby redo log file is available as well.
Thanks for your help,
Philipp.

Hi,
since it does not seem to work with just copying the datafiles I switched to RMAN. I created a full database backup from Enterprise Manager. Similiar to http://dizwell.com/main/content/view/81/122/1/1/ I tried to duplicate the database to the standby instance (running on a different server). But unfortunately I receive error messages that the files, previously created, cannot be found:
channel d1: starting datafile backupset restore channel d1: specifying datafile(s) to restore from backup set restoring datafile 00001 to /oradata/ORAMPPRD/data/1.dbf restoring datafile 00002 to /oradata/ORAMPPRD/data/2.dbf restoring datafile 00003 to /oradata/ORAMPPRD/data/3.dbf restoring datafile 00004 to /oradata/ORAMPPRD/data/4.dbf channel d1: reading from backup piece /opt/oracle/ora10/product/10.2.0.1.0/dbs/0bhoiq60_1_1
ORA-19870: error reading backup
piece /opt/oracle/ora10/product/10.2.0.1.0/dbs/0bhoiq60_1_1
ORA-19505: failed to identify file
"/opt/oracle/ora10/product/10.2.0.1.0/dbs/0bhoiq60_1_1"
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory Additional information: 3 failover to previous backup
But when I crosscheck my backup inside RMAN it clearly shows the backup files:
RMAN> crosscheck backup;
backup piece
handle=/opt/oracle/ora10/product/10.2.0.1.0/dbs/0bhoiq60_1_1 recid=7
stamp=596207811
crosschecked backup piece: found to be 'AVAILABLE'
I already checked the file permissions, everybody on the system is able to access this file.
Do you know what is going wrong here ??
Cheers,
Philipp.

Manual physical standby Db configuration...

Similar Messages

Maybe you are looking for