[Veritas-bu] Failed to restore to different client using Netbackup for SAP on oracle db with RMAN
hi all, I am trying to restore oracle database from production server into uat server using sap agent with rman option. The source destination server have similar hardware platform, oracle and nbu level. I've shut down the database and installed the archivelogs and control file using NBU backup, restore archive option. i then duplicate the control file cntrlP01.dbf to two other locations (/oracle/P01/sapdata1/cntrl/ and /oracle/P01/origlogA/cntrl/..). I restart the database using command startup and proceed with brrestore -d rman_util -b last -m full -c force but failed. fyi, i have no experience in oracle as all dbas are away for the weekend holiday. Please help me. Thank you. sapl02:orap01 56 sqlplus /nolog SQL*Plus: Release 9.2.0.6.0 - Production on Sun Apr 1 14:12:26 2007 Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved. SQL connect / as sysdba Connected to an idle instance. SQL startup ORACLE instance started. Total System Global Area 569337496 bytes Fixed Size 743064 bytes Variable Size 268435456 bytes Database Buffers 298835968 bytes Redo Buffers1323008 bytes ORA-00214: controlfile '/oracle/P01/saparch/cntrl/cntrlP01.dbf' version 43406 inconsistent with file '/oracle/P01/sapdata1/cntrl/cntrlP01.dbf' version 43131 SQL shutdown immediate ORA-01507: database not mounted ORACLE instance shut down. SQL exit Disconnected from Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production With the Partitioning and OLAP options JServer Release 9.2.0.6.0 - Production sapl02:orap01 57 cd /oracle/P01/saparch/cntrl/ sapl02:orap01 58 ls -al total 24828 drwxr-xr-x 2 orap01 dba4096 2006-12-09 15:03 . drwxr-xr-x 3 orap01 dba 53248 2007-04-01 12:15 .. -rw-r- 1 orap01 dba 8757248 2007-04-01 12:56 cntrlP01.dbf -rw-r- 1 orap01 dba 8282112 2007-03-31 09:36 cntrlP01.dbf.31032007 -rw-r- 1 orap01 dba 8282112 2007-01-05 05:55 cntrlP01.dbf.bak sapl02:orap01 59 cp cntrlP01.dbf /oracle/P01/sapdata1/c clud_1/ clui_1/ cntrl/ sapl02:orap01 59 cp cntrlP01.dbf /oracle/P01/sapdata1/cntrl/cntrlP01.dbf sapl02:orap01 60 cp cntrlP01.dbf /oracle/P01/origlogA/cntrl/cntrlP01.dbf sapl02:orap01 61 sqlplus /nolog SQL*Plus: Release 9.2.0.6.0 - Production on Sun Apr 1 14:14:48 2007 Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved. SQL connect / as sysdba Connected to an idle instance. SQL startup ORACLE instance started. Total System Global Area 569337496 bytes Fixed Size 743064 bytes Variable Size 268435456 bytes Database Buffers 298835968 bytes Redo Buffers1323008 bytes Database mounted. ORA-01157: cannot identify/lock data file 1 - see DBWR trace file ORA-01110: data file 1: '/oracle/P01/sapdata1/system_1/system.data1' SQL exit Disconnected from Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production With the Partitioning and OLAP options JServer Release 9.2.0.6.0 - Production sapl02:orap01 62 brrestore -d rman_util -b last -m full -c force BR401I BRRESTORE 6.20 (114) BR405I Start of file restore: rduydtqn.rsb 2007-04-01 14.17.53 BR564W File /oracle/P01/sapbackup/cntrlP01.dbf cannot be restored/verified with other data files BR564W File /oracle/P01/sapdata1/cntrl/cntrlP01.dbf cannot be restored/verified with other data files BR564W File /oracle/P01/origlogA/cntrl/cntrlP01.dbf cannot be restored/verified with other data files BR564W File /oracle/P01/saparch/cntrl/cntrlP01.dbf cannot be restored/verified with other data files BR567I Please restore/verify these files in a separate run BR565W Due to running database instance control file cannot be restored during restore using RMAN BR566I Stop the database instance and restore the control file separately BR456I Probably the database must be recovered due to restore from online backup BR280I Time stamp 2007-04-01 14.17.53 BR407I Restore of database: P01 BR408I BRRESTORE action ID: rduydtqn BR409I BRRESTORE function ID: rsb BR449I Restore mode: FULL BR419I Files will be restored from backup: bduhjwje.fnr 2007-01-02 22.09.34 BR416I 41 files found to restore, total size 132700.320 MB BR424I Files will not be decompressed BR421I Restore device type: rman_util BR134I Unattended mode with 'force' active - no operator confirmation allowed BR280I Time stamp 2007-04-01 14.17.53 BR554I Starting restore from full database backup using RMAN... BR278E Command output of 'SHELL=/bin/sh /oracle/P01/920_64/bin/rman nocatalog': Recovery Manager: Release 9.2.0.6.0 - 64bit Production Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved. RMAN RMAN connect target system/***; connected to target database: P01 (DBID=1321861136) using target database controlfile instead of recovery catalog RMAN **end-of-file** RMAN host command complete RMAN 2 3 4 5 6 7 allocated channel: sbt_1 channel sbt_1: sid=11 devtype=SBT_TAPE channel sbt_1: VERITAS NetBackup for Oracle - Release 6.0 (2005090703)
[Veritas-bu] Multiple Retention Levels
Environment NBU 5.1MP4 HP-UX 11.11 Does anyone know which command, if any, I can use from the command line (and thefore shell scripts) to determine if the allow multiple retention level box has been ticked by some idiot in another country who will not fess up to it. In case you think I'm pissed off, you're right. I have now had to go to the remote site twice in one week to cycle tapes and will have to go again on Monday, because of this screwup (normally we only have to go every two weeks). So if there is a command line way to check, than I can write a script to catch it before it does too much harm. Thank you for allowing me to rant. Regards, Patrick * The message is intended for the named addressee only and may not be disclosed to or used by anyone else, nor may it be copied in any way. The contents of this message and its attachments are confidential and may also be subject to legal privilege. If you are not the named addressee and/or have received this message in error, please advise us by e-mailing [EMAIL PROTECTED] and delete the message and any attachments without retaining any copies. Internet communications are not secure and COLT does not accept responsibility for this message, its contents nor responsibility for any viruses. No contracts can be created or varied on behalf of COLT Telecommunications, its subsidiaries or affiliates (COLT) and any other party by email Communications unless expressly agreed in writing with such other party. Please note that incoming emails will be automatically scanned to eliminate potential viruses and unsolicited promotional emails. For more information refer to www.colt.net or contact us on +44(0)20 7390 3900. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Windows 2003: Faulting application bpbkar32.exe
Gilles, I think it's one of those fixes that they won't make publicly available because it may only be required/work in certain circumstances; it might not fix your problem. Have you contacted Symantec? Cheers, Tim -Original Message- From: POUSSARD, Gilles (INFOTEL) [mailto:[EMAIL PROTECTED] Sent: Friday, 30 March 2007 7:00 PM To: Wilkinson, Tim; Justin Piszcz; veritas-bu@mailman.eng.auburn.edu Cc: GARCIA, Rene (STERIA) Subject: RE: [Veritas-bu] Windows 2003: Faulting application bpbkar32.exe Tim, Thanks for this information. We also have Windows 2K DFS server So it seems that there is a specific binary which allow us to backup the DFS server with the ALL_LOCAL_DRIVES directive staying with 6.0 MP4 level. We don't need to go back to 6.0 MP3 if we have this fix. And we can backup the SHAD0W_COPY_COMPONENTS successfully. Do you think that this specific correction ( nbbeclass.dll ) can be officially available on Symantec site ?? Thanks, Gilles POUSSARD-BORREL Mailto:[EMAIL PROTECTED] -Message d'origine- De : Wilkinson, Tim [mailto:[EMAIL PROTECTED] Envoyé : vendredi 30 mars 2007 00:23 À : POUSSARD, Gilles (INFOTEL); Justin Piszcz; veritas-bu@mailman.eng.auburn.edu Objet : RE: [Veritas-bu] Windows 2003: Faulting application bpbkar32.exe Gilles, The binary they sent me was a replacement for nbbeclass.dll but it fixes the problem I had regarding backing up a DFS server using ALL_LOCAL_DRIVES (I think it was the Shadow_copy_components it had problems with as opposed the file backups of each drive). We stayed on MP4. Cheers, Tim -Original Message- From: POUSSARD, Gilles (INFOTEL) [mailto:[EMAIL PROTECTED] Sent: Thursday, 29 March 2007 5:13 PM To: Wilkinson, Tim; Justin Piszcz; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Windows 2003: Faulting application bpbkar32.exe Hi Tim, Did Symantec send you a specific bpbkar32 binary or did you go to 6.0 MP3 instead of 6.0 MP4 ?? Best regards, Gilles. -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part de Wilkinson, Tim Envoyé : jeudi 29 mars 2007 08:13 À : Justin Piszcz; veritas-bu@mailman.eng.auburn.edu Objet : Re: [Veritas-bu] Windows 2003: Faulting application bpbkar32.exe Have a look at http://support.veritas.com/docs/286954 We had an issue with ALL_LOCAL_DRIVES on a server; if we specified the drives explicitly it was OK. Apparently the problem was that it had DFS and this was a known bug; we were sent a binary by Symantec and this fixed the problem. It now works fine. This obviously may not be the same issue. Cheers, Tim -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Piszcz Sent: Thursday, 29 March 2007 4:18 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Windows 2003: Faulting application bpbkar32.exe When trying to backup the registry, and ONLY the registry, I get this: Faulting application bpbkar32.exe, version 5.1.0.164, faulting module vssapi.dll, version 5.2.3790.1830, fault address 0x00020030. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. 1. Master Server Media Server: All 6.0MP4. 2. Client is 5.1MP4. 3. Yes, I have added the client and turned off all snapshotting technology. 4. However, I believe it is still used for the registry backup. The backups for all of the hard drives/arrays, not a single failure. This ONLY occurs with the registry. I do not though this is Windows 2003 R2 on the x86_64 platform. I believe the client installed was the regular 32bit client; but x86_64 should be backwards compatible with 32bit, yes? At least for simple things, I am not sure if the registry requires the 64bit MP4 patch? Has anyone dealt with anything like this before? There is just this one pesky server that this is happening on, all of the server servers use, ALL_LOCAL_DRIVES and backup the registry with no issues. Justin. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This mail has originated outside your organization, either from an external partner or the Global Internet. Keep this in mind if you answer this message. This e-mail is intended only for the above addressee. It may contain privileged information. If you are not the addressee you must not copy, distribute, disclose or use any of the information in it. If you have received it in error please delete it and
