Creating standby DB after failover

Hi,
I have performed failover to my standby DB, now i need to re create the standby db for the new production.
But there is some confusion, because previously , in my production db_name and unique name was same, suppose
test1. And the db_name and unique_name for standby was test1 and test2. And i created standby db that way using test1 and test2 in log_archive_config.
After failover, the scenario changed , the production has two different value,db name test1 and db unique name test2. And i need create standby from this. It makes me confuse, how i will create standby? What will be the db unique name for new standby??
Please help me...
regards,

user8983130 wrote:
thanks.
we use db_unque_name in log_archive_config, ok???
and in the log_archive_dest_state_2, we service name..should it be necessary to be same of the db_unique_name???DB_NAME should be same across the primary and physical standby databases.
DB_UNIQUE_NAME choose different names for each database.
Service names whatever you use either in FAL_CLIENT/FAL_SERVER (or) DEST_n there is no relation with DB_NAME/DB_UNIQUE_NAME, Its just service name how you want to call.
HTH.

Similar Messages

Recreate standby after failover test

Hi -
I'm doing a failover test for the customer:
1. Disconnect all network between Primary and Standby
2. On the Standby - do a failover and open it to perform application tests.
3. After finish we need to re-create Standby again.
Is there a way to re-create Standby again without bringing it all from backup? it's a large 2TB database and it will take hours.
Is there a way like using flashback or other technology to do it?
We are talking 10.2.0.3 here...
Thanks
Edited by: 912294 on 04:07 06/02/2012

Is there a way to re-create Standby again without bringing it all from backup? it's a large 2TB database and it will take hours.
Is there a way like using flashback or other technology to do it?
We are talking 10.2.0.3 here...Its called "open the Standby database in read write mode for any reporting or testing and then move it back to standby database using the flashback technology".
In detail check this MOS note *How To Open Physical Standby For Read Write Testing and Flashback [ID 805438.1]*
Thanks.

How to restore standby from primary after failover.

HI we have a dr setup but the standby is provided archives through an application not the datagaurd.
So for applying application patch I cant switchover the database.
I have to shutdown the primary database and apply failover to the standby database to apply patch.
Can you please tell how can I restore my standby database to actual primary after failover.
As our actual activity will be in 2 weeks time. We want to apply patch on saturday.
DR DRILL is on 8th nov.

Your earlier statement "Can you please tell how can I restore my standby database to actual primary after failover"
means something different from "SO have to restore from cold backup of primary database"
What you seem to want is a procedure to recreate the Standby from a Backup of the Pirmary. (ie FROM Primary TO Standby).
You haven't specified your Oracle Version. DG has been available since 9i (was even backported to 8i) but I will presume that you are using 9i
You should follow the same process as used for the first creation of the standby, except that you don't have to repeat some of the setup steps (listener, tnsnames etc)
http://download.oracle.com/docs/cd/B10501_01/server.920/a96653/create_ps.htm#63563
Hemant K Chitale
http://hemantoracledba.blogspot.com

Add temporary datafiles after creating standby database

I used data guard manager to create standby database and it went fine. Before finish, system pop up a window and says,
"The data guard configuration has been created in a disabled state. It must be enabled using the Enable option in the configuration menu. Pior to ebaling the configuration, please verify the following:
The Primary database contains temporary datafiles. The files will not be duplicated in the new standby database. You must manually recreate the temporary files on the standby node by adding them to their respective tablespaces in the standby database after creation process in complete."
The problem is, in the standby database, how do I add tempfile without open the standby database? the documentation is very unclear...

Thanks for the reply and the useful link. I had followed the instructions when creating the standby database, although under database options there is a difference between the OEM version we are using and the version shown, whereby the 'RMAN backup location' option has been replaced with 'working directory location'.
Just found the following and am guessing this is the issue.
NFS mounts established within a zone are local to that zone. The mounts cannot be accessed from other zones, including the global zone.
I suspect I will need to copy the backup pieces onto the local server in order to create the standby database using OEM. Not something I was expecting to have to do as copying will take a long time due to the size of the backup, but unless anyone else can shed any light on the reason for the initial error
RMAN Backup Location - The specified RMAN backup is invalid. Could not identify controlfile from the backup
then I guess this is the only way forward.
Regards,
JP

Use standby-database as standby-database after creating primary database

First I will tell what we have and what I did.
We have a standby database on server B that was not started. We did a cold copy to server A and opened the database on server A as primary database. Now we wonder if we can use the standby database on server B to apply archives without creating a new copy to server B. The standby database on server B is waiting for sequence 2900, while the database on server A started with a new sequence.
Is it possible somehow to start the recovery again on the standby databsae on server B without creating a new copy?
Forgot to mention: db-version is 9.2.0.7.0, OS is SunOS 5.10

Writing seperate code is not needed, Oracle will copy the files if the log_archive_dest is set to the right value.
However, it is solved!
What I did:
- create standby controlfile on the primary
- copy standby controlfile to standby database
- on standby: startup nomount / alter database mount standby database
- on primary: set log_archive_dest_2 to trigger the copying of archivelogs to the standby
Right now the standby database is recovering.

ORA-19505: failed to identify file - RMAN in creating standby DR database.

I got this error when creating standby database at remote target server.
ORA-19505: failed to identify file "/backup/dxp1p/online/DXP1P_CF_c-2027711285-20131204-01"
Here is what I did:
1.   started the listener and created corresponding tnsnames entry at remote standyb server
2. startup nomount to the standby database at remote server for an empty instance (instance name dxp1p).
3. All rman backups are in the /backup mount point at primary and the mount point is shared on the remote server as nfs.   So, whatever have in the backup we should be able to see and read from the remote as well.
4. Run the following at primary rman:
sql 'alter system archive log current';
backup current controlfile for standby;
sql 'alter system archive log current';
crosscheck backup;
crosscheck archivelog all;
exit
5.   Start the rman command from primary after connected to the standby server, as the primary DB uses ASM and the standby DB uses file system for the database files:
RUN
SET NEWNAME FOR DATAFILE 1 to '/u01/dxp1p/data/system01.dbf';
SET NEWNAME FOR DATAFILE 2 to '/u01/dxp1p/data/sysaux01.dbf';
SET NEWNAME FOR DATAFILE 3 to '/u01/dxp1p/data/undotbs01.dbf';
SET NEWNAME FOR DATAFILE 4 to '/u01/dxp1p/data/users01.dbf';
SET NEWNAME FOR DATAFILE 5 to '/u01/dxp1p/data/fxtntdata.dbf';
SET NEWNAME FOR DATAFILE 6 to '/u01/dxp1p/data/fxtntindex.dbf';
SET NEWNAME FOR DATAFILE 7 to '/u01/dxp1p/data/mlogs.dbf';
SET NEWNAME FOR DATAFILE 8 to '/u01/dxp1p/data/dts.dbf';
SET NEWNAME FOR DATAFILE 9 to '/u01/dxp1p/data/dxpsoa.dbf';
SET NEWNAME FOR DATAFILE 10 to '/u01/dxp1p/data/expresso_ts.dbf';
SET NEWNAME FOR DATAFILE 11 to '/u01/dxp1p/data/jms_ts.dbf';
SET NEWNAME FOR DATAFILE 12 to '/u01/dxp1p/data/uup_ts.dbf';
SET NEWNAME FOR DATAFILE 13 to '/u01/dxp1p/data/newpage_ts.dbf';
ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
ALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE DISK;
DUPLICATE TARGET DATABASE for standby
nofilenamecheck
dorecover;
========================================================================
But I got this error from the rman log:
contents of Memory Script:
   set until scn 12245784375453;
   restore clone standby controlfile;
executing Memory Script
executing command: SET until clause
Starting restore at 04-DEC-13
channel aux1: starting datafile backup set restore
channel aux1: restoring control file
channel aux1: reading from backup piece /backup/dxp1p/online/DXP1P_CF_c-2027711285-20131204-01
channel aux1: ORA-19870: error while restoring backup piece /backup/dxp1p/online/DXP1P_CF_c-2027711285-20131204-01
ORA-19505: failed to identify file "/backup/dxp1p/online/DXP1P_CF_c-2027711285-20131204-01"
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
failover to previous backup
channel aux1: starting datafile backup set restore
channel aux1: restoring control file
channel aux1: reading from backup piece /backup/dxp1p/online/DXP1P_20131204_833310136_464
channel aux1: ORA-19870: error while restoring backup piece /backup/dxp1p/online/DXP1P_20131204_833310136_464
ORA-19505: failed to identify file "/backup/dxp1p/online/DXP1P_20131204_833310136_464"
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
failover to previous backup
channel aux1: starting datafile backup set restore
channel aux1: restoring control file
channel aux1: reading from backup piece /backup/dxp1p/online/DXP1P_CF_c-2027711285-20131204-00
channel aux1: ORA-19504: failed to create file "/oracle/product/11g/dbs/u02/dxp1p/control/control02.ctl"
ORA-27040: file create error, unable to create file
Linux-x86_64 Error: 2: No such file or directory
Additional information: 1
ORA-19600: input file is control file (/u01/dxp1p/control/control01.ctl)
ORA-19601: output file is control file (/oracle/product/11g/dbs/u02/dxp1p/control/control02.ctl)
Finished restore at 04-DEC-13
contents of Memory Script:
   sql clone 'alter database mount standby database';
executing Memory Script
sql statement: alter database mount standby database
released channel: aux1
released channel: aux2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 12/04/2013 19:06:13
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of sql command on clone_default channel at 12/04/2013 19:06:13
RMAN-11003: failure during parse/execution of SQL statement: alter database mount standby database
ORA-00205: error in identifying control file, check alert log for more info
=========================================
Not sure why, can somebody help?   Appreciated!

I used company regular script to login to standby instance as sys user from primary DB RMAN as oracle OS user and sys DB user.   We normally run this way for years.
Like this:
$ORACLE_HOME/bin/rman target=/ auxiliary 'sys/sys0rapr321!'@dxp1p_s11 CMDFILE=${HOME}/dba/scripts/rman_cr_dr.cmd
rman_cr_dr.cmd:
RUN
SET NEWNAME FOR DATAFILE 1 to '/u01/dxp1p/data/system01.dbf';
SET NEWNAME FOR DATAFILE 2 to '/u01/dxp1p/data/sysaux01.dbf';
SET NEWNAME FOR DATAFILE 3 to '/u01/dxp1p/data/undotbs01.dbf';
SET NEWNAME FOR DATAFILE 4 to '/u01/dxp1p/data/users01.dbf';
SET NEWNAME FOR DATAFILE 5 to '/u01/dxp1p/data/fxtntdata.dbf';
SET NEWNAME FOR DATAFILE 6 to '/u01/dxp1p/data/fxtntindex.dbf';
SET NEWNAME FOR DATAFILE 7 to '/u01/dxp1p/data/mlogs.dbf';
SET NEWNAME FOR DATAFILE 8 to '/u01/dxp1p/data/dts.dbf';
SET NEWNAME FOR DATAFILE 9 to '/u01/dxp1p/data/dxpsoa.dbf';
SET NEWNAME FOR DATAFILE 10 to '/u01/dxp1p/data/expresso_ts.dbf';
SET NEWNAME FOR DATAFILE 11 to '/u01/dxp1p/data/jms_ts.dbf';
SET NEWNAME FOR DATAFILE 12 to '/u01/dxp1p/data/uup_ts.dbf';
SET NEWNAME FOR DATAFILE 13 to '/u01/dxp1p/data/newpage_ts.dbf';
ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
ALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE DISK;
DUPLICATE TARGET DATABASE for standby
nofilenamecheck
dorecover;
exit
==========================
Oinstall is a group.   I am not sure to use oinstall as a user?

How to re-build the Production database after failover

We have performed a failover in our environment by the below method . It was worst we are not able to bring up the production the only choice left over is failover.
We have enabled the flash back and created a checkpoint then failover.
SQL> select max(sequence#) from v$log_history;
MAX(SEQUENCE#)
9221
SQL> alter system set db_recovery_file_dest_size=14G;
System altered.
SQL> alter system set db_recovery_file_dest='/u01/oradata/flashback';
System altered.
SQL> alter database recover managed standby database cancel;
Database altered.
SQL> alter database flashback on;
Database altered.
SQL> create restore point before_open_standby guarantee flashback database;
Restore point created.
SQL> alter database activate standby database;
Database altered.
SQL> select database_role from v$database;
DATABASE_ROLE
PRIMARY
SQL> shutdown immediate;
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
SQL> select max(sequence#) from v$log_history;
MAX(SEQUENCE#)
9221 (This is the log sequence same after the failover also)
after the we have nearly some 30 log sequence are generated but it started from the no 1.
Now we need to rebuild the Production DB and to sync with the standby.. please help us with the steps and suggest some documents.

Hi,
Please take a look at this http://shivanandarao.wordpress.com/2012/08/28/dataguard-failover/
SHANOJ
Handle:     SHANOJ
Status Level:     Newbie (5)
Registered:     Feb 15, 2006
Total Posts:     154
Total Questions:     *25 (21 unresolved)*
Name     SHANOJ
Location     Chennai - India
Occupation     DBA
Biography     OCP 10G, LPI, ITIL V3
If you feel your questions have been answered, then please consider closing your threads as answered by providing appropriate points rather than leaving it open. Follow the forums etiquette.

Reinstate the formerly primary db after failover

We have a data guard guard configuration, oracle 10g r2, windows servers 2003, RAC with two nodes, ASM, Data Broker Manager, same configuration on both primary and standby. After we failover to the standby db, we need to rebuild the formerly primary db. I know the steps using flashback db to reinstate the db. Unfortunately, due to performance reason, we can not use flashback db. Today I read an article with this statement for rebuild the formerly primary db:
If flashback database is not on, the database needs to be build up again with a new level 0 rman backup
I am just curious if anyone has done this before using RMAN level 0 backup instead of flashback to rebuild formerly primary db? This is what I am thinking:
1) From new primary, get the scn number
select to_char(standby_became_primary_scn) from v$database;
2) From formly primary (current standby), use the level 0 backup to restore db to this scn
then run alter database convert to physical standby; command in sqlplus. Shutdown the db and restart using real-time redo apply.
3) From new primary, run Reinstate database something from DGMGRL.
As I can only do the failover test next week, I am interested if someone has actually done this before and provide me more guidance on this task.
Thanks a lot in advance

The Orcale documentation said:
You can use any backup copy of the primary database to create the physical standby database, as long as you have the necessary archived redo log files to completely recover the database. Oracle recommends that you use the Recovery Manager utility (RMAN).
I prefer RMAN, because it's not required to shut down the primary database. With RMAN you can take a level 0 backup or the "duplicate for standby" command to create the standby database. In principle you also may use a cold file copy of your database. But using ASM, you must take RMAM - as far as I know.

Gating error while creating standby database in oracle 11g

Dear Gurus
I am getting following error while creating standby database. My database version is oracle 11g 11.2.0.1 in Redhat 5.2
RMAN> duplicate target database for standby from active database;
Starting Duplicate Db at 10-MAY-12
using channel ORA_AUX_DISK_1
contents of Memory Script:
backup as copy reuse
targetfile '/oracle/product/11.2.0/dbhome_1/dbs/orapworcl' auxiliary format
'/oracle/product/11.2.0/dbhome_1/dbs/orapwstdb' ;
executing Memory Script
Starting backup at 10-MAY-12
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/10/2012 15:44:18
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 05/10/2012 15:44:18
ORA-17629: Cannot connect to the remote database server
ORA-17627: ORA-12528: TNS:listener: all appropriate instances are blocking new connections
ORA-17629: Cannot connect to the remote database server
RMAN>
Regards
Rabi

Hello;
Generally for the connection to work you need to add something like this to the listener.ora file :
(SID_DESC =
    (global_dbname = STANDBY.hostname)
    (ORACLE_HOME = /u01/app/oracle/product/11.2.0.2)
    (sid_name = STANDBY)
)You should stop and start the listener on the Standby after adding this. Also your tnsnames.ora must be correct on both the primary and the Standby.
Also you need an INIT for the Standby side :
STANDBY.__db_cache_size=343932928
STANDBY.__java_pool_size=4194304
STANDBY.__large_pool_size=4194304
STANDBY.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
STANDBY.__pga_aggregate_target=281018368
STANDBY.__sga_target=834666496
STANDBY.__shared_io_pool_size=0
STANDBY.__shared_pool_size=469762048
STANDBY.__streams_pool_size=0
audit_file_dest='/u01/app/oracle/admin/PRIMARY/adump'
audit_trail='db'
compatible='11.2.0.0.0'
control_files='/u01/app/oracle/oradata/PRIMARY/control01.ctl','/u01/app/oracle/oradata/PRIMARY/control02.ctl'
db_block_size=8192
db_domain='SOME.DOMAIN.COM'
db_flashback_retention_target=2880
db_name='PRIMARY'
db_recovery_file_dest_size=2147483648
db_recovery_file_dest='/u01/app/oracle/flash_recovery_area'
diagnostic_dest='/u01/app/oracle'
dispatchers='(PROTOCOL=TCP) (SERVICE=PRIMARYXDB)'
log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST'
open_cursors=300
pga_aggregate_target=277872640
processes=150
remote_login_passwordfile='EXCLUSIVE'
sga_target=833617920
undo_tablespace='UNDOTBS1'
log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=STANDBY'
log_archive_dest_2='SERVICE=PRIMARY LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) '
LOG_ARCHIVE_DEST_STATE_1=ENABLE
LOG_ARCHIVE_DEST_STATE_2=DEFER
LOG_ARCHIVE_MAX_PROCESSES=30
FAL_SERVER=STANDBY
STANDBY_FILE_MANAGEMENT=AUTO
DB_UNIQUE_NAME=STANDBYFinally
startup nomount
Start RMAN and issue duplicate command
$ORACLE_HOME/bin/rman target=sys/@primary auxiliary=sys/@standby
RMAN>duplicate target database for standby from active database NOFILENAMECHECK;
Keys to success
1. New Standby start NOMOUNT on new password file. ( On Oracle 11 you must copy and rename the file from Primary server )
2. Hard coded listener on new Standby server.
3. Correct tnsnames.ora files.
4. Correct duplicate command.
Please consider closing some of you old answered questions
Best Regards
mseberg
Edited by: mseberg on May 10, 2012 7:06 AM

Server 2012 File Server Cluster Shadow Copies Disappear Some Time After Failover

Hello,
I've seen similar questions posted on here before however I have yet to find a solution that worked for us so I'm adding my process in hopes someone can point out where I went wrong.
The problem: After failover, shadow copies are only available for a short time on the secondary server. Before the task to create new shadow copies happens the shadow copies are deleted. Failing back shows them missing on the primary server as
well when this happens.
We have a 2 node (hereafter server1 and server2) cluster with a quorum disk. There are 8 disk resources which are mapped to the cluster via iScsi. 4 of these disks are setup as storage and the other 4 are currently set up as shadow copy volumes
for their respective storage volume.
Previously we weren't using separate shadow copy volumes and seeing the same issue described in the topic title. I followed two other topics on here that seemed close and then setup the separate shadow copy volumes however it has yet to alleviate the
issue. These are the two other topics :
Topic 1: https://social.technet.microsoft.com/Forums/windowsserver/en-US/ba0d2568-53ac-4523-a49e-4e453d14627f/failover-cluster-server-file-server-role-is-clustered-shadow-copies-do-not-seem-to-travel-to?forum=winserverClustering
Topic 2: https://social.technet.microsoft.com/Forums/windowsserver/en-US/c884c31b-a50e-4c9d-96f3-119e347a61e8/shadow-copies-missing-after-failover-on-2008-r2-cluster
After reading both of those topics I did the following:
1) Add the 4 new volumes to the cluster for shadow copies
2) Made each storage volume dependent on it's shadow copy volume in FCM
3) Went to the currently active node directly and opened up "My Computer", I then went to the properties of each storage volume and set up shadow copies to go to the respective shadow copy volume drive letter with correct size for spacing, etc.
4) I then went back to FCM and right clicked on the corresponding storage volume and choose "Configure Shadow Copy" and set the schedule for 12:00 noon and 5:00 PM.
5) I noticed that on the nodes the task was created and that the task would failover between the nodes and appeared correct.
6) Everything appears to failover correctly, all volumes come up, drive letters are same, shadow copy storage settings are the same, and 4 scheduled tasks for shadow copy appear on the current node after failover.
Thinking everything was setup according to best practice I did some testing by changing file contents throughout the day making sure that previous versions were created as scheduled on server1. I then rebooted Server1 to simulate failure. Server2
picked up the role within about 10 seconds and files were avaiable. I checked and I could still see previous versions for the files after failover that were created on server1. Unfortunately that didn't last as the next day before noon I was going
to make more changes to files to ensure that not only could we see the shadow copies that were created when Server1 owned the file server role but also that the copies created on Server2 would be seen on failback. I was disappointed to discover that
the shadow copies were all gone and failing back didn't produce them either.
Does anyone have any insight into this issue? I must be missing a switch somewhere or perhaps this isn't even possible with our cluster type based on this: http://technet.microsoft.com/en-us/library/cc779378%28v=ws.10%29.aspx
Now here's an interesting part, shadow copies on 1 of our 4 volumes have been retained from both nodes through the testing, but I can't figure out what makes it different though I do suspect that perhaps the "Disk#s" in computer management / disk
management perhaps need to be the same between servers? For example, on server 1 the disk #s for cluster volume 1 might be "Disk4" but on server 2 the same volume might be called "Disk7", however I think that operations like this
and shadow copy are based on the disk GUID and perhaps this shouldn't matter.
Edit, checked on the disk numbers, I see no correlation between what I'm seeing in shadow copy and what is happening to the numbers. All other items, quotas, etc fail and work correctly despite these diffs:
Disk Numbers on Server 1:
Format: "shadow/storerelation volume = Disk Number"
aHome storage1 = 16
aShared storage2 = 09
sHome storage3 = 01
sShared storage4 = 04
aHome shadow1 = 10
aShared shadow2 = 11
sHome shadow3 = 02
sShared shadow4 = 05
Disk numbers on Server 2:
aHome storage1 = 16 (SAME)
aShared storage2 = 04 (DIFF)
sHome storage3 = 05 (DIFF)
sShared storage4 = 08 (DIFF)
aHome shadow1 = 10 (SAME)
aShared shadow2 = 11 (SAME)
sHome shadow3 = 06 (DIFF)
sShared shadow4 = 09 (DIFF)
Thanks in advance for your assistance/guidance on this matter!

Hello Alex,
Thank you for your reply. I will go through your questions in order as best I can, though I'm not the backup expert here.
1) "Did you see any event ID when the VSS fail?
please offer us more information about your environment, such as what type backup you are using the soft ware based or hard ware VSS device."
I saw a number of events on inspection. Interestingly enough, the event ID 60 issues did not occur on the drive where shadow copies did remain after the two reboots. I'm putting my event notes in a code block to try to preserve formatting/readability.
I've written down events from both server 1 and 2 in this code block, documenting the first reboot causing the role to move to server 2 and then the second reboot going back to server 1:
JANUARY 2
9:34:20 PM - Server 1 - Event ID: 1074 - INFO - Source: User 32 - Standard reboot request from explorer.exe (Initiated by me)
9:34:21 PM - Server 1 - Event ID: 7036 - INFO - Source: Service Control Manager - "The Volume Shadow Copy service entered the running state."
9:34:21 PM - Server 1 - Event ID: 60 - ERROR - Source: volsnap - "The description for Event ID 60 from source volsnap cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\HarddiskVolumeShadowCopy49
F:
T:
The locale specific resource for the desired message is not present"
9:34:21 PM - Server 1 - Event ID 60 - ERROR - Source: volsnap - "The description for Event ID 60 from source volsnap cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\HarddiskVolumeShadowCopy1
H:
V:
The locale specific resource for the desired message is not present"
***The above event repeats with only the number changing, drive letters stay same, citing VolumeShadowCopy# numbers 6, 13, 18, 22, 27, 32, 38, 41, 45, 51,
9:34:21 PM - Server 1 - Event ID: 60 - ERROR - Source: volsnap - "The description for Event ID 60 from source volsnap cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\HarddiskVolumeShadowCopy4
E:
S:
The locale specific resource for the desired message is not present"
***The above event repeats with only the number changing, drive letters stay same, citing VolumeShadowCopy# numbers 5, 10, 19, 21, 25, 29, 37, 40, 46, 48, 48
9:34:28 PM - Server 1 - Event ID: 7036 - INFO - Source: Service Control Manager - "The NetBackup Legacy Network Service service entered the stopped state."
9:34:28 PM - Server 1 - Event ID: 7036 - INFO - Source: Service Control Manager - "The Volume Shadow Copy service entered the stopped state.""
9:34:29 PM - Server 1 - Event ID: 7036 - INFO - Source: Service Control Manager - "The NetBackup Client Service service entered the stopped state."
9:34:30 PM - Server 1 - Event ID: 7036 - INFO - Source: Service Control Manager - "The NetBackup Discovery Framework service entered the stopped state."
10:44:07 PM - Server 2 - Event ID: 7036 - INFO - Source: Service Control Manager - "The Volume Shadow Copy service entered the running state."
10:44:08 PM - Server 2 - Event ID: 7036 - INFO - Source: Service Control Manager - "The Microsoft Software Shadow Copy Provider service entered the running state."
10:45:01 PM - Server 2 - Event ID: 48 - ERROR - Source: bxois - "Target failed to respond in time to a NOP request."
10:45:01 PM - Server 2 - Event ID: 20 - ERROR - Source: bxois - "Connection to the target was lost. The initiator will attempt to retry the connection."
10:45:01 PM - Server 2 - Event ID: 153 - WARN - Source: disk - "The IO operation at logical block address 0x146d2c580 for Disk 7 was retried."
10:45:03 PM - Server 2 - Event ID: 34 - INFO - Source: bxois - "A connection to the target was lost, but Initiator successfully reconnected to the target. Dump data contains the target name."
JANUARY 3
At around 2:30 I reboot Server 2, seeing that shadow copy was missing after previous failure. Here are the relevant events from the flip back to server 1.
2:30:34 PM - Server 2 - Event ID: 60 - ERROR - Source: volsnap - "The description for Event ID 60 from source volsnap cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\HarddiskVolumeShadowCopy24
F:
T:
The locale specific resource for the desired message is not present"
2:30:34 PM - Server 2 - Event ID: 60 - ERROR - Source: volsnap - "The description for Event ID 60 from source volsnap cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\HarddiskVolumeShadowCopy23
E:
S:
The locale specific resource for the desired message is not present"
We are using Symantec NetBackup. The client agent is installed on both server1 and 2. We're backing them up based on the complete drive letter for each storage volume (this makes recovery easier). I believe this is what you would call "software
based VSS". We don't have the infrastructure/setup to do hardware based snapshots. The drives reside on a compellent san mapped to the cluster via iScsi.
2) "Confirm the following registry is exist:
- HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VSS\Settings"
The key is there, however the DWORD value is not, would that mean that the
default value is being used at this point?

Server for NFS deletes the partially copied file after failover

Hello,
I found the strange behaviour in Server for NFS in the microsoft foc cluster.
I have a foc cluster of two nodes(windows server 2k12r2) and server for nfs role is installed on both. now I did mount the export from the client(windows server 2k12r2) where client for nfs role is installed;
and a large file copying from the clients local drive to the mounted export is started.
Now during this copying operation I did switch the export to second node(moved it using the failover cluster manager wizard). and what I found is the copying interrupts with
error message "there is problem accessing file path" and on retry the copying starts all over again, I mean if the 50% was copied previously then
after retry it will start from 0%.
I watched the system events on second node with the "procmon" and I found; after the disk gets attached to the second node, the delete operation is get called for this file.
Now what I need to know is why this delete is been called and who made this called. In the stack of the delete operation I could track the nfssvr.sys but not sure what attributes of that file made it to call the
delete.

Hi,
It takes us some time to create a failover cluster for testing.
We tried to copy a large folder which contains many files, and a large VHD file we created.
The result is the same - it will not restart the copy after failover. Thus as you said it is not caused by design and it should be an issue on your side which causes a Delete and redo the copy.
Is there any application or specific network settings could terminate a disconnected copy process? Currently I do not have much information about this.
Edit: I noticed that it is NFS share and in our test we are using SMB share. Will do the test again to see if any difference.

Creating standby database

Hi
I want create standby database in Oracle 10g.
I can create standart database by using database configuration assistant.
How can I create standby database in Oracle 10g?

Hi,
Standby databases, in a nutshell, acts as a failover for our mission critical production databases. When production database crashes, applications can quickly switchover to the stand by databases.
What type of Standy you are willing to go for ??
Physical Standby Database
Standby database is called “physical” if the physical structure of stand by exactly matches with stand by structure. Archived redo log transferred from primary database will be directly applied to the stand by database.
Logical Standby Database
Stand by database is called “logical”, the physical structure of both
databases do not match and from the archived redo log we create SQL statements then these statements will be applied to stand by database.
Follow this link for creating standby database
http://www.oracle-base.com/articles/8i/StandbyDatabase.php
http://download.oracle.com/docs/cd/B10501_01/server.920/a96653/create_ps.htm
Thanks
Pavan Kumar N

Create Standby Database using RMAN changing backuppiece location ID753902.1

[https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWTO&id=753902.1] I am trying to create standby using above document however when I do recover database I get below error
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 07/06/2011 13:50:40
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 1899 and starting SCN of 25926696
logsequence 1899 is very very old sequence and doesnt exist on primary.this sequence is not needed because backu pwas taken after this sequence so I dont undrestand why rman is asking for a sequence that doesnt exists?
my db is 11.2 and in archivelog mode , i have all the archivelogs from the date backup was taken until now...
thanks
Edited by: user9198889 on Jul 6, 2011 8:29 AM

CKPT wrote:
user9198889 wrote:
[https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWTO&id=753902.1] I am trying to create standby using above document however when I do recover database I get below error
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 07/06/2011 13:50:40
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 1899 and starting SCN of 25926696
logsequence 1899 is very very old sequence and doesnt exist on primary.this sequence is not needed because backu pwas taken after this sequence so I dont undrestand why rman is asking for a sequence that doesnt exists?
my db is 11.2 and in archivelog mode , i have all the archivelogs from the date backup was taken until now...
thanks
Edited by: user9198889 on Jul 6, 2011 8:29 AMHave you restored from the recent backup?
validate the backup compeltion_time and then retry the operation, Are you restoring from tapes?yes its recent backup(last and only backup infact ) , the backup took couple of days to run..
the backup was executing using this command BACKUP INCREMENTAL LEVEL 1 AS COMPRESSED BACKUPSET DATABASE TAG 'LEV1_BCKP_2011-06-27_11_54' PLUS ARCHIVELOG DELETE INPUT
there was no full backup so oracle must have taken full one and not incremental correct?
first logseq that was back's up is : 35818
primary uses local disk for its db and backup
standby that i am trying to create is on asm. i have copied backup to FRA and restored to +data its recovery that is failing now

How to create standby controlfile from restored backup

Hi Techies,
I am re-building one of my DR server, Source and target DB is oracle 10g.
I have taken the source backup which is going to be restored on target, But I forgot to take a standby controlfile from source DB at the time (Pre/Post) backup.
Now the issue is I can create a standby controlfile on primary and copy the same to target, But so many datafiles are added after the backup which I have taken to restore and medias are already shipped.
I can send the other set of backup to DR site, but it takes a week time and I don't want to do that If I can regenerate it.
So any clue to create standby controlfile on target with restored datafiles?
Regards,
Nick Loy

Hmm... sounds like you perform this in a rather manual fashion...
Do you use RMAN for taking the backups?
Or maybe the BR*TOOLS?
With these tools you are usually safe from such mistakes - I can only recommend to use them!
However, since you don't have a control file at all on the target side, the only thing left to do would be to
ALTER DATABASE BACKUP CONTROLFILE TO TRACE NORESETLOGS;
on the primary side and manually remove the files that have been added since you took the backup from the control file script,
Afterwards you use the script on the standby side to create the control files.
regards,
Lars

Task: Create Standby DatabaseFailed

Hi,
I am creating a physical standby database using grid control. I first have grid control do a backup, one that can be used later for standby creation, then I ftp those files to the standby host.
After the files are there, I go back to grid control and create the standby using files from previous backup (now located on the standby host). Everything seems OK, the process starts, then fails on the step below.
Task: Create Standby Database Failed
Step: sourceCloningPreparation
Succeeded
Step: createControlFile
Succeeded
Step: destDirCreation
Succeeded
Step: copyInitPasswdFiles
Succeeded
Step: copyControlFile
Succeeded
Step: destCloningPreparation
Failed
If I follow the link I see the output below. What do I need to fix? Is there another logfile somewhere that gives more information?
LSNRCTL for 32-bit Windows: Version 10.2.0.1.0 - Production on 07-MAY-2008 15:50:10
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=TestBox)(PORT=1521)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for 32-bit Windows: Version 10.2.0.1.0 - Production
Start Date 21-APR-2008 15:44:25
Uptime 16 days 0 hr. 5 min. 50 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File G:\oracle\product\10.2.0\db_1\network\admin\listener.ora
Listener Log File G:\oracle\product\10.2.0\db_1\network\log\listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=TestBox)(PORT=1521)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "WRsite2_DGMGRL" has 1 instance(s).
Instance "WRdg2", status UNKNOWN, has 1 handler(s) for this service...
Service "emrep.systems.de.ittind.com" has 1 instance(s).
Instance "emrep", status READY, has 1 handler(s) for this service...
Service "emrep_XPT.systems.de.ittind.com" has 1 instance(s).
Instance "emrep", status READY, has 1 handler(s) for this service...
Service "site2_DGMGRL" has 1 instance(s).
Instance "dg2", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
LSNRCTL for 32-bit Windows: Version 10.2.0.1.0 - Production on 07-MAY-2008 15:50:11
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=TestBox)(PORT=1521)))
The command completed successfully
THANKS,
JOE

Any luck figuring this out?
I am encountering similar problem - except I am using the option on the clone to let the job do the copying directly from the directories where the backup is saved.
The strange thing is that the step fails - but there are no error messages in the step at all - just successful status received from the listener - is there something in the listener's status that it doesn't like?

Creating standby DB after failover

Similar Messages

Maybe you are looking for