Online backup recovery

Hi All,
I have the tape of online backup and that I have restored to the system. But it is asking about the more archive file i.e. I do not have. How can I restore these archive from this online backup tape. Can you guide me. Is it possible or not. Is archive file backed into online backup tape or not.
Kindly suggest how to sort out this issue.
Awaiting your reply.
Regards,
Ashu

Hi Markus,
I have used the following commands for restoring the backup :
brrestore -m full -b <det_log_file> -c
The above said command is not restoring the archive file but except archive all data file has been restored successfully.
Regards,
Jitendra

Similar Messages

Database open fails after online backup recovery

Hi Friends
We are trying to set up an additional server using the online backup of our DEV server. We have been following SAP Note 549828 for the same. Having restored the online backup, the open database failed.
To resolve the same, in accordance to SAP Note 549828, we created a backup control file with success using the command
create controlfile reuse set database DEV resetlogs noarchivelog
However on issuance of the command
RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL
we run into an error as to
ORA-00279: change 794638222 generated at 10/25/2007 12:43:20 needed for thread 1
ORA-00289: suggestion : /oracle/DEV/oraarch/DEVarch1_9766.dbf
ORA-00280: change 794638222 for thread 1 is in sequence #9766
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log '/oracle/DEV/oraarch/DEVarch1_9766.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: '/oracle/DEV/sapdata1/system_1/system.data1'
We even manually copied the file system.data1 from the source to the target server but to no avail.
Also the SQL command
SELECT FILE#, CHANGE# FROM V$RECOVER_FILE
displays a different change# for system.data1 while it is showing same number for all other datafiles.
Please advice at the earliest as we are struck. Points awaiting their master.
Regards
Lokesh Gupta

Some inputs addition to Erics comments
The problem is you dont have archives ie Offline redo logfiles in correct location.
/oracle/DEV/oraarch/DEVarch1_9766.dbf Here DEVarch1_9766 is archive file which is misssing from location /oracle/DEV/oraarch. To recover DB you need Archives generated during hot backup.
Generally these steps willl give you desired result.
select * from v$logfile;
We normally switch the log files to the number of log groups that exist
alter system switch logfile;
create a Backup directory to hold our hot back datafiles and Archives
When the backup is complete check the backup location to see if all the files are available. We could now either FTP the same to the other system or copy over these files to another location in case of cloning on the same system.
Copy over all the files to their respective filesystems and directories and then edit the file that was created using the backup controlfile to trace. Copy that file to the remote system and edit it accordingly.
check that all the files are in the right location and edit that information in the control file
Once the controlfile is run successfully and you get the statement processed, we can start applying the archive logs that we have moved to the archive log destination directory as per the init<sid>.ora file.
do a recover of the database to its consistent state
recover database using backup controlfile until cancel;
The create control file command only changes the structure of the database and the SID name, the header of the datafiles still hold all the required information. The above command would ask you to input the archive log file names one by one to do recovery or you could choose the AUTO option. Once the recovery process is complete, open the database with the resetlogs option
Regards
Vinod

BI Online Backup recovery

Hi experts,
We need to make an online bakup of our BI system. But we had some infopackages that ran after the online backup, so the delta timestamps in ECC are greater than the timestamp of the backup.
Do you know if after the recovery of the BI online backup the timestamps in ECC will be also reverted?
If not, is there any way of performing this activity?
Thanks in advance
Best Regards

hi,
Find the document below it may help you.
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/001ef297-9bbf-2910-bbaa-babedc1b01ca;jsessionid=(J2EE3414800)ID1551428150DB11188012514138478496End
Regards,
Shiva.
Edited by: Shivu Kumar on Sep 17, 2009 7:16 AM

Online Backup Recovery Error-1033

Hi,
1.I took a successful Online Backup for Net Weaver Sytem through DB13 Functionality.
2.Database is Oracle .
3.When I try to Restore the Backup through BRTOOLS on the Server ,It gives SQL Error 1033.
Pl. find the enclosed Error Details:
Starting user session: OCISessionBegin(con=0, usr='SAPSR3', svc=152820D0, srv=152822D0, usr=15291560)
C     OCISessionBegin(OCI_DEFAULT) failed with SQL error 1033:
C     ORA-01033: ORACLE initialization or shutdown in progress
C Server handle (con=0,svchp=152820D0,srvhp=152822D0) detached
C *** ERROR => CONNECT failed with sql error '1033'
B ***LOG BV3=> severe db error 1033      ; work process is stopped
B ***LOG BY2=> sql error 1033   performing CON
B ***LOG BY0=> ORA-01033: ORACLE initialization or shutdown in progress
M ***LOG R19=> ThInit, db_connect ( DB-Connect 000256)
M in_ThErrHandle: 1
M *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1)
Ive already Consulted the Notes 655240 & 556232 for Solution. But, the problem still persist.
Please provide some Input for the same .
Regards,
Nimish Bhatnagar

Hi Nimish,
Check out OSS note 35278, 445038 and 400241.
Can you please check
R3trans -d and get the log of trans.log
remove any old trans.log if you have any at that location.
if that doen't help try R3trans -x and get the log. Both write the log in file trans.log
Try the command "recover database".
Regards,
Deepanshu Sharma

How does recovery work after an online backup

Hello,
While trying to conceptually understand how backup and recovery works, I came accross a question concerning hot (online) backup.
This is a conceptual question (I am trying to understand how things work), it is not a "how should I proceed/ what should I do step by step" question.
As far as I understand, an online backup of a tablespace can be performed by copying the OS files making up a tablespace while the database is up and being used (i.e. transactions are modifying data in the database). Before the copying of the OS files starts, the Oracle RDMS must be notified that an online backup is being taken via "ALTER...BEGIN BACKUP" (such that some additional information is written to the Redo Log, which may be required for subsequent recovery using the online backup). During recovery the Oracle RDBMS uses the copies of the OS files together with the online and archived redo logs in order to reconstruct all committed transactions and it further uses the UNDO tablespace to rollback open (uncommitted) transactions.
Thinking about this, it seems to me, that in order for this to work in all possible scenarios the undo information from the time the backup was taken may be required. Therefore backup of the UNDO tablespace should be taken as well (see the explanation for this assumption below). However browsing the internet (including the Oracle online documentation) I did not find any statements concerning the backup of the UNDO tablespace when an online backup is taken. Moreover I couldn't figure out when exactly such a backup of the UNDO tablespace must be done, to ensure that the database can be recovered in all scenarios.
I believe that undo information from the time the hot backup was taken may be required e.g. in the following scenario:
Assume we are taking a hot backup of a given tablespace, i.e. we are copying all OS files that make up this tablespace, while the database is potentially being used. Let D1 be one of the datafiles in our tablespace and let transaction T1 modify datafile D1. Let transaction T1 further be uncommitted while the copy of datafile D1 is being made and let (at least some of) the changes from T1 be included in the backup copy D1' of D1 (because DBWR has already written the modified blocks at the time they were being copied to the backup). Let transaction T1 be rolled back after the copy is completed. D1' will thus contain modifications from T1, while D1 will not.
Now some time later the datafile D1 is lost. When recovering D1 from the copy D1', the (archived) redo logs will be applied to D1'. Before that, transaction T1 should be rolled back in the copy D1', because modifications from T1 must not appear in the recovered version of the database.
I do however not understand, where the information to rollback transaction T1 exactly comes from. It may still be in the current UNDO tablespace. I do however assume that rollback information is not kept in the UNDO tablespace forever. I see three possible answers to this
(a) There are some requirements which I missed so far to backup the UNDO tablespace whenever a hot backup is made.
(b) Since the Oracle "RDBMS" has to be notified that an online backup is being done, it might store all relevant undo information (e.g. write it to the redo log) when the tablespace is put in backup mode.
(c) There are situations when recovery is not possible due to "missing old UNDO information".
Answer (b) seems the most plausible to me. I did however not find any confirmation of this and if (b) really is the answer, I would be interested to understand what information is stored where by the Oracle RDMBS and how it is used for recovery.
To summarize I have the following questions:
(I) Is there any requirement to backup the UNDO tablespace together with an online backup of a tablespace, and if so, where is this stated in the Oracle documentation?
(II) What mechanisms ensure that uncommitted transactions can be cleared from the online copy of a tablespace (potentially a long time after the copy was taken)?
(III) Do you know any links (Oracle documentation or other online resources) explaining these datails?
Thank you for any hints and answers
kind regards
Martin

Its a highly technical question and I can be completely wrong due to my very less knowledge but I would attempt to answer still. Hope I say something sensible so bear with me.
As far as I understand, an online backup of a tablespace can be performed by copying the OS files making up a tablespace while the database is up and being used (i.e. transactions are modifying data in the database).Correct. But it would depend on the tool you are going to use to do so.Using o/s level commands like CP and all would require you to manually copy the files to the backup location. Using RMAN, it would be lot easier and RMAN would take care of everything.
Before the copying of the OS files starts, the Oracle RDMS must be notified that an online backup is being taken via "ALTER...BEGIN BACKUP" (such that some additional information is written to the Redo Log, which may be required for subsequent recovery using the online backup). Again, this is a requirement only in the case of user-managed backup . In that case, because of the fractured block issue , its important that the corresponding older information/image of the buffer is also copied in the redo stream and that's done when the begin backup command is used. Using RMAN, this is not needed as RMAN can read the consistent image which it would store in the backup piece, exactly in the same way in which select request is fulfilled by oracle for a dirty buffer which is yet to be made consistent.
During recovery the Oracle RDBMS uses the copies of the OS files together with the online and archived redo logs in order to reconstruct all committed transactions and it further uses the UNDO tablespace to rollback open (uncommitted) transactions.Correct!
Thinking about this, it seems to me, that in order for this to work in all possible scenarios the undo information from the time the backup was >taken may be required. Therefore backup of the UNDO tablespace should be taken as well (see the explanation for this assumption below). >However browsing the internet (including the Oracle online documentation) I did not find any statements concerning the backup of the UNDO >tablespace when an online backup is taken. Moreover I couldn't figure out when exactly such a backup of the UNDO tablespace must be done, to >ensure that the database can be recovered in all scenarios.The reason that its not a must to do so is that if the transaction is yet active, there is no way that Oracle would overwrite the Undo information of it, even if you may come after 100 years, it would be there. The Undo segment would mark those blocks as active undo blockswhich contains the information of that transaction whose status within the transacton table of that undo segment is still marked as active. So its there all the time in the undo tablespace. Now, for an instance, let's assume that the undo is not there as well( it would be but let's assume), the changes made to the undo segment's blocks are also recored in the redo as its just a change happening to any other segment like EMP,DEPT except with the difference that its not done by you but by oracle. So using that information, in the future , if there would be a need to replay those changes, necessary information to do so can be brought up from the redo blocks stored in the redo/archive logs. Yes, if there would be pending transactions that would require Undo information to get them rolled back and you have lost Undo tablespace and have no backup of it , you wont be able to bring back the database as it would be inconsistent and oracle would not let you to do it. In that case, you may require to use hacks to get it up and that would be really tricky situation.
(I) Is there any requirement to backup the UNDO tablespace together with an online backup of a tablespace, and if so, where is this stated in the Oracle documentation?As I said above, it must be there if you are anticipating loss of Undo tablespace. If you have lost it, you would need a backup and all the archive logs and redo logs to recover and get it back to the point where the current database is . Rest, oracle would take care as it would reapply the redo contents of the undo segments over the undo segment and get it consitent.
(II) What mechanisms ensure that uncommitted transactions can be cleared from the online copy of a tablespace (potentially a long time after the copy was taken)?As I said , pending transaction's undo is never overwritten by Oracle. Its always kept and marked as active undo . Only a transaction end would make it elgible to get overwritten and that too won't happen immediately(undo_retention would kick in) .
(III) Do you know any links (Oracle documentation or other online resources) explaining these datails?I have to see if its there some where step by step mentioned and I shall update the reply once I shall find the link. Hoep someone else in the meantime finds it .
HTH
Aman....

ORA-01195: online backup of file 65 needs more recovery to be consistent

Hi,
I was doing a clone by taking the hot backup from prod to dev. The backup was good. And then I created the control file, Then I passed the command
recover database until cancel using backup controlfile;
It asked for the archived logs files. I supplied them until current time.
Then I canceled.
That's when I got this error
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01195: online backup of file 65 needs more recovery to be consistent
ORA-01110: data file 65: '/d10/oradata/dwdev/kt01.dbf'
ORA-01112: media recovery not started
What am I doing wrong? I have not yet passed the command "Alter database open resetlogs"
Should I do more logswitches in prod and pass those files to dev ? Or should I just put the kt tablespace in backup mode and copy the data files?

Which set of archivelogs did you copy over to apply ? All the archivelogs from the first ALTER TABLESPACE ... BEGIN BACKUP to the archivelogs subsequent to the last ALTER TABLESPACE ... END BACKUP ?
In the cloned datadabase, what messages do you see in the alert.log on having issued the RECOVER DATABASE command ? Does it complain about the datafiles being fuzzy ? Which archivelogs does it show as having been applied ?
Can you check the log sequence numbers for the duration of the Backup PLUS ArchiveLogs subsequent to the Backup ?

Open resetlogs is not working when creating clone db with online backup

Hi All,
I am trying to create a clone database using hot backup of a database .
STEPS THAT I FOLLOWED
LET ----- >CURRENT_DB NAME=DEV
CLONE DATABASE NAME=DEVCLONE
steps PERFORMED FORM DEV DB
- put the database in backup mode using 'alter database begin backup'
- copy all the data files to a different folder
- during copy i have performed some operations on the DB (creating users, tables, dmls etc...)
- in between copying i also performed log switch
- after completion of copy , "alter database end backup"
- created a backup control file in a human readable format (alter database backup controlfile to trace as ........)
steps performed for clone DB side ((DEVCLONE)
- created a parameter file for the database .
- modified the backup control file so that it will point to the location of copied destination of datafiles
- set the ORACLE_SID
- then 'sqlplus / as sysdba
- starup nomount
- run the modified control file ( created a control file for the clone database)
- recover the database using "recover database using backup controlfile"
I have provided the archive files that it was asking for (archive logs that has been generated in DEV DB)
then i canceled the recovery by typing "cancel"
- recover database using backup controlfile until cancel;
then typed "cancel"
- then try to open the database with open resetlogs but it showed below error
alter database open resetlogs
ERROR at line 1:
ORA-01195: online backup of file 1 needs more recovery to be consistent
ORA-01110: data file 1: 'D:\DATA_GUARD\DEVHOT\SYSTEM01.DBF'
please help me on this ......
Thanks

Thanks , now i am able to open the DB in open reset logs mode .
Previously , when i had not taken the archive log after "alter database end backup" , i was not able to open the db with open resetlogs because the
fuzzy status of all the datafile headers were YES .
But after taking the archive log that got generated after "alter database end backup" and applying it on the clone db(Created with HOT backup ) the datafile_header status got changed from YES to NO .
So for that i am able to open the clone db with open resetlogs .
Can you please help me with a small description why this is happening ?
Thanks.......

Actions to be performed after a online backup restore

Hello Guru's,
I have an online backup of a system.
(AIX - ORACLE)
If I restore the backup using Tivoli Storage Manager I still have to perform some actions to recover the database.
I have read through the SAP documentation and it seems I can restore the logs using brtools (brrecover).
My questions actually is, which option do I have to take if I want to apply the offline archive logs as far as possible ?
"Complete database recovery" of "database point in time recovery" ?
I want to make sure that only the archivelogs are being applied and that the database restore is not peformed again.
Thank you all !
bye
BUD

Hello Hans,
> and it seems I can restore the logs using brtools (brrecover).
If you only want to restore your archivelogs, then use brrestore.
brrecover is for recovering the database, not for restoring.
Take a look at here:
http://help.sap.com/saphelp_nw04/helpdata/en/88/cadaca94734ae5b8ea3491f615741b/content.htm
and here:
http://help.sap.com/saphelp_nw04/helpdata/en/0d/d3077b4a0c11d182b80000e829fbfe/content.htm
> My questions actually is, which option do I have to take if I want to apply the offline archive logs as far as possible ?
> "Complete database recovery" of "database point in time recovery" ?
In this case you have to do an incomplete database recovery or in other words called "point in time recovery". For the difference between these two restore types take a look at the oracle documentation:
http://download-uk.oracle.com/docs/cd/B19306_01/backup.102/b14192/intro004.htm#i1016863
After you have restored your archive logs you can perform the recovery manually:
> SQL> recover database using backup controlfile until cancel;
> SQL> cancel;
> SQL> alter database open resetlogs;
Btw.as you are using TDP for SAP you can use backfm to restore only some several files.
Regards
Stefan

Restore Online Backup in SCDPM 2012 R2

Dear all,
i have a question on SCDPM 2012 R2 + Azure Backup.
i had deployed such solution and disk backup are perfect! However, i had configured online backup policy to Azure Backup since February and i noticed i do not have the options to allow me to perform online restore!
Below is my online protection policy:
i believe i configured it correct to adhere below policy:
- perform a monthly backup and keep for ONE year
- perform a yearly backup and keep for SEVEN years
but when i go to recovery tab, it just doesnt show February backup, nor March 2nd have any backup. all the backup available are disk short term of 30 days.

Hi DeVaLiaN,
Thanks for posting here!
Each DPM backup to Azure Backup is a recovery point. With an Azure current limit of 366 recovery points your retention time for all backups shouldn’t exceed the 366 limit. In other words the retention times you set for you daily + weekly + monthly
+ yearly backups should sum up to 366 or less.
You might want to double check your configuration.
Refer to the below listed articles which might help you narrow down the issue.
http://blogs.technet.com/b/systemcenter/archive/2014/03/16/using-azure-backup-with-dpm.aspx
http://social.technet.microsoft.com/wiki/contents/articles/19751.system-center-2012-data-protection-manager-dpm-sp1-part-4-backup-to-azure.aspx
https://msdn.microsoft.com/en-us/library/azure/dn337332.aspx
Hope this helps!
Regards,
Sadiqh

Problem in Backup/Recovery 10g

Hi
I am Trying to Take Backup in Oracle 10g ........
RMAN > Configure retention policy to recovery window of 4 days
RMAN > configure controlfile autobackup on;
RMAN > Configure device type disk backup type to compressed backupset;
RMAN> backup as backupset database spfile;
Starting backup at 14-MAR-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/14/2007 10:20:
49
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current controlfile in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 14-MAR-07
channel ORA_DISK_1: finished piece 1 at 14-MAR-07
piece handle=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2007_03
_14\O1_MF_NCSNF_TAG20070314T102048_2ZGY13BK_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 14-MAR-07
channel ORA_DISK_1: finished piece 1 at 14-MAR-07
piece handle=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2007_03
_14\O1_MF_NNSNF_TAG20070314T102048_2ZGY15PK_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/14/2007 10:20:
49
I can identefy the Problem .

Your database is running in NOARCHIVELOG mode. You cannot make an online backup.
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode

Online backup

Hi
After an online backup, if there is no checkpoint, there is no need for recovery, true?
beacuse CHECKPOINT_CHANGE# of the datafiles are not modified therefore no need to recovery..

nop during online backup the controlfile chekpoint and datafile checkpoint header is not synced.Upon restoration it will require recovery.
Khurram

Online backup via BRTOOLS

Hi there!
I am planning to implement an online backup using brtools. When I did the testing, I noticed an error that prevents me from completing the backup. Hope anybody can help me. It seems that there is an error with the compress command but I cant seem to understand why. Below is the entire log of my backup. Btw, Im using ECC6 and Oracle Database 10g.
Thanks in advance.
>>> TNVT - to host 172.16.0.5
su - e6padm
AMC-E6P-DB:e6padm 1> brtools
BR0651I BRTOOLS 7.00 (18)
BR0280I BRTOOLS time stamp: 2008-10-26 00.32.45
BR0656I Choice menu 1 - please make a selection
BR*Tools main menu
1 = Instance management
2 - Space management
3 - Segment management
4 - Backup and database copy
5 - Restore and recovery
6 - Check and verification
7 - Database statistics
8 - Additional functions
9 - Exit program
Standard keys: c - cont, b - back, s - stop, r - refr, h - help
BR0662I Enter your choice:
4
BR0280I BRTOOLS time stamp: 2008-10-26 00.32.50
BR0663I Your choice: '4'
BR0280I BRTOOLS time stamp: 2008-10-26 00.32.50
BR0656I Choice menu 9 - please make a selection
Backup and database copy
1 = Database backup
2 - Archivelog backup
3 - Database copy
4 - Non-database backup
5 - Backup of database disk backup
6 - Verification of database backup
7 - Verification of archivelog backup
8 - Additional functions
9 - Reset program status
Standard keys: c - cont, b - back, s - stop, r - refr, h - help
BR0662I Enter your choice:
1
BR0280I BRTOOLS time stamp: 2008-10-26 00.32.51
BR0663I Your choice: '1'
BR0280I BRTOOLS time stamp: 2008-10-26 00.32.51
BR0657I Input menu 15 - please check/enter input values
BRBACKUP main options for backup and database copy
1 - BRBACKUP profile (profile) ....... [initE6P.sap]
2 - Backup device type (device) ...... [disk]
3 # Tape volumes for backup (volume) . []
4 # BACKINT/Mount profile (parfile) .. []
5 - Database user/password (user) .... [/]
6 - Backup type (type) ............... [online]
7 # Disk backup for backup (backup) .. [no]
8 # Delete disk backup (delete) ...... [no]
9 ~ Files for backup (mode) .......... [all]
Standard keys: c - cont, b - back, s - stop, r - refr, h - help
BR0662I Enter your choice:
c
BR0280I BRTOOLS time stamp: 2008-10-26 00.32.55
BR0663I Your choice: 'c'
BR0259I Program execution will be continued...
BR0280I BRTOOLS time stamp: 2008-10-26 00.32.55
BR0657I Input menu 16 - please check/enter input values
Additional BRBACKUP options for backup and database copy
1 - Confirmation mode (confirm) ....... [yes]
2 - Query mode (query) ................ [no]
3 - Compression mode (compress) ....... [yes]
4 - Verification mode (verify) ........ [no]
5 - Fill-up previous backups (fillup) . [no]
6 - Parallel execution (execute) ...... [0]
7 - Additional output (output) ........ [no]
8 - Message language (language) ....... [E]
9 - BRBACKUP command line (command) ... [-p initE6P.sap -d disk -t online -m all -k yes -e 0 -l E]
Standard keys: c - cont, b - back, s - stop, r - refr, h - help
BR0662I Enter your choice:
c
BR0280I BRTOOLS time stamp: 2008-10-26 00.32.59
BR0663I Your choice: 'c'
BR0259I Program execution will be continued...
BR0291I BRBACKUP will be started with options '-p initE6P.sap -d disk -t online -m all -k yes -e 0 -l E'
BR0280I BRTOOLS time stamp: 2008-10-26 00.32.59
BR0670I Enter 'c[ont]' to continue, 'b[ack]' to go back, 's[top]' to abort:
c
BR0280I BRTOOLS time stamp: 2008-10-26 00.33.00
BR0257I Your reply: 'c'
BR0259I Program execution will be continued...
BR0051I BRBACKUP 7.00 (18)
BR0055I Start of database backup: bdzcoptc.and 2008-10-26 00.33.00
BR0477I Oracle pfile /oracle/E6P/102_64/dbs/initE6P.ora created from spfile /oracle/E6P/102_64/dbs/spfileE6P.ora
BR0280I BRBACKUP time stamp: 2008-10-26 00.33.01
BR0319I Control file copy created: /oracle/E6P/sapbackup/cntrlE6P.dbf 18268160
BR0280I BRBACKUP time stamp: 2008-10-26 00.33.02
BR0057I Backup of database: E6P
BR0058I BRBACKUP action ID: bdzcoptc
BR0059I BRBACKUP function ID: and
BR0110I Backup mode: ALL
BR0077I Database file for backup: /oracle/E6P/sapbackup/cntrlE6P.dbf
BR0061I 44 files found for backup, total size 178457.758 MB
BR0143I Backup type: online
BR0111I Files will be compressed
BR0130I Backup device type: disk
BR0106I Files will be saved on disk in directory: /installer/backup/E6P/bdzcoptc
BR0280I BRBACKUP time stamp: 2008-10-26 00.33.02
BR0256I Enter 'c[ont]' to continue, 's[top]' to cancel BRBACKUP:
c
BR0280I BRBACKUP time stamp: 2008-10-26 00.33.03
BR0257I Your reply: 'c'
BR0259I Program execution will be continued...
BR0370I Directory /installer/backup/E6P/bdzcoptc created
BR0370I Directory /installer/backup/E6P/E6P created
BR0202I Saving init_ora
BR0203I to /installer/backup/E6P/E6P ...
BR0202I Saving /oracle/E6P/102_64/dbs/initE6P.sap
BR0203I to /installer/backup/E6P/E6P ...
BR0280I BRBACKUP time stamp: 2008-10-26 00.33.03
BR0198I Profiles saved successfully
BR0280I BRBACKUP time stamp: 2008-10-26 00.33.04
BR0315I 'Alter tablespace PSAPSR3 begin backup' successful
BR0201I Compressing /oracle/E6P/sapdata1/sr3_1/sr3.data1
BR0203I to /installer/backup/E6P/bdzcoptc/sr3.data1.Z ...
BR0278E Command output of 'LANG=C compress -c /oracle/E6P/sapdata1/sr3_1/sr3.data1 > /installer/backup/E6P/bdzcoptc/sr3.data1.Z':
/oracle/E6P/sapdata1/sr3_1/sr3.data1: Invalid argument
BR0280I BRBACKUP time stamp: 2008-10-26 00.33.04
BR0279E Return code from 'LANG=C compress -c /oracle/E6P/sapdata1/sr3_1/sr3.data1 > /installer/backup/E6P/bdzcoptc/sr3.data1.Z': 1
BR0224E Compressing /oracle/E6P/sapdata1/sr3_1/sr3.data1 to /installer/backup/E6P/bdzcoptc/sr3.data1.Z failed due to previous errors
BR0280I BRBACKUP time stamp: 2008-10-26 00.33.07
BR0317I 'Alter tablespace PSAPSR3 end backup' successful
BR0056I End of database backup: bdzcoptc.and 2008-10-26 00.33.04
BR0280I BRBACKUP time stamp: 2008-10-26 00.33.08
BR0054I BRBACKUP terminated with errors
BR0292I Execution of BRBACKUP finished with return code 5
BR0668I Warnings or errors occurred - you can continue to ignore them or go back to repeat the last action
BR0280I BRTOOLS time stamp: 2008-10-26 00.33.08
BR0670I Enter 'c[ont]' to continue, 'b[ack]' to go back, 's[top]' to abort:
s
BR0280I BRTOOLS time stamp: 2008-10-26 00.33.12
BR0257I Your reply: 's'
BR0679I Do you really want to cancel BRTOOLS? Enter y[es]/n[o]:
y
BR0280I BRTOOLS time stamp: 2008-10-26 00.33.13
BR0257I Your reply: 'y'
BR0260E BRTOOLS cancelled by user
BR0280I BRTOOLS time stamp: 2008-10-26 00.33.13
BR0654I BRTOOLS terminated with errors
AMC-E6P-DB:e6padm 2> exit
AMC-E6P-DB:e6padm 3> logout
>>>Closing capture file.

Hi Scott,
Thank you for the quick reply. However, I have another thing to bring up. I created an exact replica of this instance to a separate server for my online backup testing. I used mksysb for my rootvg and created a backup of my datavg and restored it to the new server. To my surprise, my online backup worked. Im currently running it so that I can upload the log in this thread. I checked on the version of the brtools and they are both of the same level. Also, I forgot to mention that I've been using offline backup via brtools since last year. It was only now that Im trying to implement an online backup. Would this problem still be caused by brarchive patch 18?
Thanks in advance!

Regarding Full online Backup failed

Dear All,
I have faceing one issue related to SAP system backup, i have shedule sap backup by DB13(full online backup) but frequently it will failed and showing same return code 005. Bellow mentioned is log details pls. check:-
datafile copy filename=/oracle/P01/sapbackup/behgluac.spa/p01.data26 recid=40001 stamp=767722216
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of catalog command on default channel at 11/20/2011 16:10:16
ORA-19665: size 517120 in file header does not match actual file size of 514560
ORA-19664: file type: datafile copy, file name: /oracle/P01/sapbackup/behgluac.spa/p01.data27RMAN>
Recovery Manager complete.
BR0280I BRBACKUP time stamp: 2011-11-20 16.10.17
*BR0279E Return code from 'SHELL=/bin/sh /oracle/P01/102_64/bin/rman nocatalog': 1*
BR0536E RMAN call for database instance P01 failedBR0280I BRBACKUP time stamp: 2011-11-20 16.10.17
BR0532E Cataloging backups of all database files failedBR0056I End of database backup: behgluac.fnt 2011-11-20 16.10.17
BR0280I BRBACKUP time stamp: 2011-11-20 16.10.17
BR0054I BRBACKUP terminated with errors
Pls. guide me and help me to reslove this issue.
Our server OS is solaries 10 and DB is Oracle 10g.
Regards,
Sweetdiya.

Hii,
Can you tell me option to take backup again on same day if 1st bakup will failure? Bcoz we have try to take backup on same day on same tape when 1st backup had terminated due to error sytem is not take backup. e.g if today tuesday i have take(sunday S01B01,mon S01B02 likethis) tape name S01B03 our backup is failed due to error RC:- 005. we can re-execute bakup or shedule bckup in DB13 again it is agin failed.
so can any body can guide us on this issue plz..
Thanks in advance.
Regards,
Sweetdiya
Edited by: sweetdiya on Nov 22, 2011 10:11 AM

Online backup fail through DB13

Dear experts,
I am using sap BW 7.4 under oracle 11.0.2.4
I am trying to take online backup on disk
I select action whole database online backup + redo file backup as will as
Full database online backup and BRACHIVE function is -sd
but backup was failed I am unable to resolve it following are logs generated during backup
#SAVED.... /oracle/online/beokvzrl/system.data1 #1/17
BR0280I BRBACKUP time stamp: 2014-08-02 10:58:20
BR0063I 17 of 17 files processed - 51610.133 of 51610.133 MB done
BR0204I Percentage done: 100.00%, estimated end time: 10:58
BR0001I **************************************************
BR0280I BRBACKUP time stamp: 2014-08-02 10:58:20
BR0317I 'Alter tablespace SYSTEM end backup' successful
BR0252W Function kill() failed for '17891582:15' at location BrKill-3
BR0253W errno 3: No such process
BR0278I Command output of '/usr/sap/BWD/SYS/exe/run/brconnect':
BR0801I BRCONNECT 7.40 (6)
PID=17891582
BR0252E Function fopen() failed for '/oracle/BWD/sapbackup/.user.pas' at location global_set-1
BR0253E errno 13: Permission denied
BR0074W BRCONNECT call failed
BR0280I BRBACKUP time stamp: 2014-08-02 10:58:22
BR0530I Cataloging backups of all database files...
BR0278E Command output of 'SHELL=/bin/sh /oracle/BWD/112_64/bin/rman nocatalog':
Recovery Manager: Release 11.2.0.4.0 - Production on Sat Aug 2 10:58:23 2014
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
RMAN>
RMAN> connect target *
connected to target database: BWD (DBID=2340275772)
using target database control file instead of recovery catalog
RMAN> **end-of-file**
RMAN>
host command complete
RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of catalog command on default channel at 08/02/2014 10:58:25
ORA-19564: error occurred writing 8192 bytes at block number 1
ORA-27091: unable to queue I/O
ORA-27041: unable to open file
IBM AIX RISC System/6000 Error: 13: Permission denied
Additional information: 3
Additional information: 4
Additional information: 4194434
RMAN>
Recovery Manager complete.
BR0280I BRBACKUP time stamp: 2014-08-02 10:58:25
BR0279E Return code from 'SHELL=/bin/sh /oracle/BWD/112_64/bin/rman nocatalog': 1
BR0536E RMAN call for database instance BWD failed
BR0200I BR_TRACE: location BrRmanCall-56, commands for RMAN in: /oracle/BWD/sapbackup/.beokvzrl.cmd
@/oracle/BWD/sapbackup/..beokvzrl..cmd
host '/usr/sap/BWD/SYS/exe/run/brtools -f delete /oracle/BWD/sapbackup/..beokvzrl..cmd';
catalog datafilecopy
'/oracle/online/beokvzrl/sr3.data1',
'/oracle/online/beokvzrl/sr3.data2',
'/oracle/online/beokvzrl/sr3.data3',
'/oracle/online/beokvzrl/sr3.data4',
'/oracle/online/beokvzrl/sr3.data5',
'/oracle/online/beokvzrl/sr3.data6',
'/oracle/online/beokvzrl/sr3740.data1',
'/oracle/online/beokvzrl/sr3740.data2',
'/oracle/online/beokvzrl/sr3740.data3',
'/oracle/online/beokvzrl/sr3740.data4',
'/oracle/online/beokvzrl/sr3740.data5',
'/oracle/online/beokvzrl/sr3740x.data1',
'/oracle/online/beokvzrl/sr3740x.data2',
'/oracle/online/beokvzrl/sr3usr.data1',
'/oracle/online/beokvzrl/undo.data1',
'/oracle/online/beokvzrl/sysaux.data1',
'/oracle/online/beokvzrl/system.data1'
level 0 tag beokvzrl;
exit;
BR0280I BRBACKUP time stamp: 2014-08-02 10:58:25
BR0532E Cataloging backups of all database files failed
BR0056I End of database backup: beokvzrl.fnd 2014-08-02 10:58:25
BR0280I BRBACKUP time stamp: 2014-08-02 10:58:25
BR0054I BRBACKUP terminated with errors
BR0280I BRBACKUP time stamp: 2014-08-02 10:58:25
I am unable to understand why RMAN is use ?
and what parameters are used when I will take backup on tape
Kindly guide me
Regards

Dear Srivastava for your reply,
I download latest brtools patch and apply it and change authorization profile parameters is also OK ( I run whole database online backup from brtools using same profile it done successfully )
full permission ( 777) in sapbackup folder and sub folder but through db13 backup is successfully with warning
BR0204I Percentage done: 100.00%, estimated end time: 11:57
BR0001I **************************************************
BR0252W Function kill() failed for '10420324:15' at location BrKill-3
BR0253W errno 3: No such process
BR0278I Command output of '/usr/sap/BWD/SYS/exe/run/brconnect':
BR0801I BRCONNECT 7.40 (10)
PID=10420324
BR0252E Function fopen() failed for '/oracle/BWD/sapbackup/.user.pas' at location global_set-1
BR0253E errno 13: Permission denied
BR0074W BRCONNECT call failed
BR0280I BRBACKUP time stamp: 2014-08-04 11:57:59
BR0340I Switching to the next online redolog file for database instance BWD ...
BR0321I Switch to the next online redolog file for database instance BWD successful
BR0117I ARCHIVE LOG LIST after backup for database instance BWD
Parameter                      Value
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            /oracle/BWD/oraarch/BWDarch
Archive format                 %t_%s_%r.dbf
Oldest online log sequence     838
Next log sequence to archive   841
Current log sequence           841              SCN: 28074154
Database block size            8192             Thread: 1
Current system change number   28074155         ResetId: 842452156
BR0202I Saving space_log
BR0203I to /oracle/bck/online/BWD ...
BR0202I Saving /oracle/BWD/sapbackup/beolgapq.and
BR0203I to /oracle/bck/online/BWD ...
BR0202I Saving /oracle/BWD/sapbackup/backBWD.log
BR0203I to /oracle/bck/online/BWD ...
BR0056I End of database backup: beolgapq.and 2014-08-04 11:58:01
BR0280I BRBACKUP time stamp: 2014-08-04 11:58:01
BR0053I BRBACKUP completed successfully with warnings or non-fatal errors
1. BR0252W Function kill() failed for '10420324:15' at location BrKill-3
    BR0253W errno 3: No such process
2. BR0252E Function fopen() failed for '/oracle/BWD/sapbackup/.user.pas' at location global_set-1
BR0253E errno 13: Permission denied
BR0074W BRCONNECT call failed
why it backup not open file .user.pas ( it is not exist in this folder )
Kindly guide me
Regards

ORACLE8 OPS BACKUP & RECOVERY

제품 : ORACLE SERVER
작성날짜 : 2004-08-16
ORACLE8 OPS BACKUP & RECOVERY
=============================
SCOPE
Standard Edition 에서는 Real Application Clusters 기능이 10g(10.1.0) 이상 부터 지원이 됩니다.
Explanation
OPS에서의 database backup & recovery 방법은 single instance의 backup 방법과
비슷하다. 즉, Single instance에서의 모든 backup 방법은 ops에서도 지원된다.
1. Backup 방법
다음의 backup 방법 모두 사용이 가능하다. 여기서는 2)의 os 명령을 이용한
backup 방법에 대해 기술합니다.
1) Recovery Manager (RMAN) : <Bulletin 11451> 참고
2) OS 명령을 활용한 백업
Noarchive log mode : full offline backup only
Archive log mode : full or partial, offline or online backup
3) export : <Bulletin 10080> 참고 : ORACLE 7 BACKUP 및 RECOVERY 방법
2. backup 정책 수립 시 고려 사항
1) disk crash나 user error 등으로 말미암은 손실을 허용하지 않는다면 ARCHIVE
LOG MODE를 사용해야 한다.
2) 대부분 모든 instance는 자동 archiving을 사용한다.
3) 모든 data backup 작업이 어떤 instance 건 가능하다.
4) media recovery 시 모든 thread의 archive file이 사용된다.
5) Instance recovery 시 살아있는 instance의 smon에 의해 자동으로 recovery된다.
3. Noarchive log mode : Full offline backup
1) 다음의 view들을 query하여 backup이 필요한 file을 알아낸다.
V$DATAFILE or DBA_DATA_FILES
V$LOGFILE
V$CONTROLFILE
2) 모든 instance를 shutdown한다.
3) 확인된 file을 backup destination으로 copy한다.
4. Archive log mode : Partial or Full Online Backup
1) 백업을 수행하기 전에 ALTER SYSTEM ARCHIVE LOG CURRENT 명령 실행(이 명령을
실행하여 현재 운영되지 않는 데이터베이스를 포함한 모든 노드의 current redo
log에 대한 로그 스위치와 그에 따른 아카이브를 모든 인스턴스에서 실행시킨다.)
2) ALTER TABLESPACE tablespace BEGIN BACKUP 명령 실행
3) ALTER TABLESPACE 명령이 성공적을 실행될 때까지 대기
4) OS에서 적절한 명령어를 활용하여 테이블스페이스에 속하는 데이터파일들을 백업
(tar, cpio, cp 등)
5) OS 명령을 활용한 백업이 다 끝날 때까지 대기
6) ALTER TABLESPACE tablespace END BACKUP 명령 수행
7) ALTER DATABASE BACKUP CONTROLFILE TO filename 이나
ALTER DATABASE BACKUP CONTROLFILE TO TRACE
명령을 수행시켜 컨트롤 파일을 백업.
만약 아카이브 로그 파일을 백업받는다면 END BACKUP 명령을 실행시킨 이후
ALTER SYSTEM ARCHIVE LOG CURRENT 명령을 실행시켜 END BACKUP 시점까지의
모든 리두 로그 파일들을 확보한다.
5. Import Parameter
1) Controlfile 내의 Redo Log History (MAXLOGHISTORY )
CREATE DATABASE 명령이나 CREATE CONTROLFILE 명령에서 MAXLOGHISTORY 값을
지정하여 parallel server에서 다 채워진 리두 로그 파일에 대한 history를
컨트롤 파일이 저장하도록 할 수 있다. 이미 데이터베이스를 생성한 후라면
log history 값을 증가시키거나 감소시키기 위해서는 컨트롤 파일을 재생성
하여야만 한다.
MAXLOGHISTORY는 컨트롤 파일 내의 archive history를 얼마나 저장할 수
있는지를 지정하며, 기본값은 플랫폼 별로 다르다. 이 값이 0이 아닌 다른
값으로 지정된다면 log switch가 발생할 때마다 LGWR 프로세스에서는 컨트롤
파일에 다음 정보를 기록한다.
thread number, log sequence number, low SCN, low SCN timestamp, next SCN
(next log의 가장 낮은 SCN값)
(이 정보는 리두 로그 파일이 archive된 후가 아니라 log switch가 발생할 때
컨트롤 파일에 저장된다.)
MAXLOGHISTORY 값에서 지정한 값을 넘어서 log history가 저장되어야 할 경우
가장 오래된 history를 overwrite하는 방식으로 저장된다. Log history 정보는
OPS에서 자동 media recovery 시 SCN, thread number를 기준으로 적절한
아카이브 로그 파일을 찾아 재구성하는 데 사용된다. 데이터베이스를 exclusive
모드에서 한개의 쓰레드만 사용하는 환경에서는 log history 정보가 필요하지 않다.
Log history 관련 정보는 V$LOG_HISTORY를 이용해 조회해 볼 수 있다.
서버 관리자에서 V$RECOVERY_LOG를 조회하면 media recovery에 필요한 아카이브
로그에 대한 정보를 얻을 수 있다.
Multiplex된 리두 로그 파일에 대해서, log history 내에서 여러개의 entry가
사용되지 않는다. 각각의 entry는 개개의 파일에 대한 정보가 아니라, multiplex
된 log 파일의 그룹에 대한 정보를 가지고 있다.
2) Archive Log Mode 시 Parameter
OPS에서 archive log mode로 변경 시 exclusive mode로 db mount 후에 변경한다.
a. LOG_ARCHIVE_FORMAT
파라미터     설명     예
%T     thread number, left-zero-padded     arch0000000001
%t     thread number, not padded     arch1
%S     log sequence number, left-zero-padded     arch0000000251
%s     log sequence number, not padded     arch251
이 가운데 %T와 %t는 OPS에서만 유효한 파라미터이다.
모든 instance의 format은 같아야 하며 OPS 환경에서는 반드시 thread 번호를
포함시켜야 한다.
예) log_archive_format = %t_%s.arc
b. LOG_ARCHIVE_START
- 자동 archiving : TRUE로 지정한 후 인스턴스를 구동시키면 background process
인 ARCH에서 자동 archiving을 수행한다. Closed Thread의 경우에는 실행 중인
thread에서 closed thread를 대신해 log switch와 archiving을 수행한다.
이것은 모든 노드에서 비슷한 SCN을 유지하도록 하기 위해 강제적으로 log switch
가 발생할 때 일어난다
- 수동 Archiving : FALSE이면 archive를 시작하도록 지시하는 명령을 명시적으로
내리지 않는 이상 동작을 멈추고 대기한다. OPS에서는 각각의 인스턴스에서 서로
다른 LOG_ARCHIVE_START 값을 사용할 수 있다.
다음과 같은 방법으로 수동 archiving을 수행할 수 있다.
ALTER SYSTEM ARCHIVE LOG SQL 명령을 실행
ALTER SYSTEM ARCHIVE LOG START 명령을 실행하여 자동 archiving을 실행하도록
지정.
수동 archiving은 명령을 실행시킨 노드에서만 실행 되며, 이 때 archiving
작업을 ARCH 프로세스가 처리하지 않는다.
c. LOG_ARCHIVE_DEST
archive log file이 만들어질 directory를 지정한다.
예) log_archive_dest = /arch2/arc
6. OPS Recovery
1) Instance Failure 시
Instance failure는 S/W나 H/W 상의 문제, 정전이나 background process에서
fail이 발생하거나, shutdown abort를 시키거나 OS crash 등 여러가지 이유로
인해 instance가 더 이상 작업을 진행할 수 없을 때 발생할 수 있다.
Single instance 환경에서는 instance failure는 instance를 restart 시키고
database를 open하여 해결된다. Mount 상태에서 open 되는 중간 단계에서 SMON은
online redo log 파일을 읽어 instance recovery 작업을 수행한다.
OPS에서는 instance failure가 발생 했을 경우 다른 방식으로 instance
recovery가 수행된다. OPS에서는 한 노드에서 fail이 발생했다고 하더라도
다른 노드의 인스턴스는 계속 운영될 수 있기 때문에 instance failure는
database가 가용하지 않다는 것을 의미하지는 않는다.
Instance recovery는 dead instance를 처음으로 발견한 SMON 프로세스에서
수행한다. Recovery가 수행되는 동안 다음과 같은 작업이 일어난다.
- Fail이 발생하지 않은 다른 인스턴스에서는 fail이 발생한 인스턴스의
redo log 파일을 읽어 들여 데이터파일에 그 내용을 적용시킨다.
- 이 기간 동안 fail이 발생하지 않은 다른 노드에서도 buffer cache 영역의
내용을 write 하지는 못한다.
- DBWR disk I/O가 일어나지 못한다.
- DML 사용자에 의해 lock request를 할 수 없다.
a. Single-node Failure
한 인스턴스에서 fail이 난 다른 인스턴스에 대한 recovery를 수행하는 동안,
정상적으로 운영 중인 인스턴스는 fail이 난 인스턴스의 redo log entry를
읽어 들어 commit이 된 트랜잭션의 결과치를 데이터베이스에 반영시킨다.
따라서 commit 된 데이터에 대한 손실은 일어나지 않으며, fail이 난
인스턴스에서 commit 시키지 않은 트랜잭션에 대해서는 rollback을 수행하고,
트랜잭션에서 사용 중이던 자원을 release시킨다.
b. Multiple-node Failure
만약 OPS의 모든 인스턴스에서 fail이 발생했을 경우, 인스턴스 recovery는
어느 한 인스턴스라도 open이 될 때 자동으로 수행된다. 이 때 open되는 인스턴스는
fail이 발생한 인스턴스가 아니라도 상관 없으며, OPS에서 shared 모드
혹은 execlusive 모드에서 데이터베이스를 mount 하더라도 상관 없이 수행된다.
오라클이 shared 모드에서 수행되던, execlusive 모드에서 수행되건,
recovery 절차는 하나의 인스턴스에서, fail이 난 모든 인스턴스에 대한
recovery를 수행하는지 여부를 제외하고는 동일하다.
2) Media Failure 시
Oracle에서 사용하는 file을 저장하는 storage media에 문제가 발생했을 경우
발생한다. 이와 같은 상황에서는 일반적으로 data에 대한 read/write가 불가능하다.
Media failure가 발생했을 경우 recovery는 single instance의 경우와
마찬가지로 recovery가 수행되어야 한다. 두 경우 모드 archive log 파일을
이용해서 transaction recovery를 수행하여야 한다.
3) Node Failure 시
OPS 환경에서, 한 노드 전체에 fail이 발생했을 때, 해당 노드에서 동작하던
instance와 IDLM 컴포넌트에서도 fail이 발생한다. 이 경우 instance recovery를
하기 위해서는 IDLM은 lock에 대한 remaster를 시키기 위해 그 자신을
reconfigure시켜야 한다.
한 노드에서 fail이 발생했을 때 Cluster Manager 또는 다른 GMS product에서는
failure를 알리고, reconfiguration을 수행하여야만 한다. 이 작업이 수행되어야만
다른 노드에서 운영 중인 LMD0 프로세스와의 통신이 가능하다.
오라클에서는 fail이 발생한 노드에서 잡고 있는 lock 정보를 access할 경우나,
LMON 프로세스에서 heartbeat을 이용해서 fail이 발생한 노드가 더 이상
가용하지 않다는 것을 감지할 때 failure가 발생한 것을 알게 된다.
IDLM에서 reconfigure가 일어나면 instance recovery가 수행된다.
Instance recovery는 recovery를 수행하는 동안 자원에 대한 contention을
피하기 위해 전체 데이터베이스의 작업을 일시 중지시킬 수 있다.
FREEZE_DB_FOR_FAST_INSTANCE_RECOVERY initialization parameter 값을
TRUE로 지정하며 전체 데이터베이스가 일시적으로 작업을 멈추게 된다.
데이터 화일에서 fine-grain lock을 사용할 경우 기본값은 TRUE이다.
이 값을 FALSE로 지정할 경우 recovery가 필요한 데이터만이 일시적으로 작업이
멈춰진다. 데이터 화일이 hash lock을 사용할 경우 FALSE가 기본 값이다.
4) IDLM failure 시
한 노드에서 다른 연관된 프로세스의 fail이나 memory fault 등의 이유로 인해
IDLM 프로세스만 fail이 발생했다면 다른 노드의 LMON에서는 이 문제를 감지하여
lock reconfiguration process를 시작한다.
이 작업이 진행 중인 동안 lock 관련 작업은 처리가 정지되고 PCM lock 또는
다른 resource를 획득하기 위해 일부 사용자들은 대기 상태로 들어간다.
5) Interconnect Failure ( GMS failure ) 시
노드 간의 interconnect에서 fail이 발생하면 각각의 노드에서는 서로 다른
노드의 IDLM과 GMS에서 fail 이 발생했다고 간주하게 된다. GMS에서는 quorum
disk나 node에 pinging 등을 수행하는 다른 방법을 통해 시스템의 상태를 확인한다.
이 경우 Fail이 발생한 connection에 대해 두 노드 혹은 한쪽 노드에서
shutdown 이 일어난다.
Oracle 8 recovery mechanism에서는 노드 혹은 인스턴스에서 강제로 fail이
발생했을 경우 IDLM이나 instance가 startup 될 수 없게 된다. 경우에 따라서는
노드 간의 IDLM communication이 가용한지 여부를 확인하기 위해 cluster
validation code를 직접 작성하여 사용할 수도 있다. 이 방법을 사용하여
GMS에서 제공하지는 않지만, 문제를 진단한 후 shutdown을 수행하도록 할 수 있다.
이같은 code를 작성하기 위해서는 단일 PCM lock에서 처리되는 단일 data block에
대해 계속해서 update 를 수행해 보는 루틴이 들어가면 된다. 서로 연결된
두 노드에서 이 프로그램을 실행시키게 될 경우 interconnect에서 fail이
난 상황을 진단할 수 있게 된다.
만약 여러개의 노드가 cluster를 구성할 경우에는 매 interconnect 마다
다른 PCM lock에 의해 처리되는 data block을 update 함으로써, 어떤 노드와의
interconnect에 문제가 발생했는지를 알아낼 수 있다.
7. Parallel Recovery
Parallel Recovery의 목표는 compute와 I/O parallelism을 사용해서 crash
recovery, single-instance recovery, media recovery 시 소요되는 시간을 줄이는
데 있다.
Parallel recovery는 여러 디스크에 걸쳐 몇 개의 데이터파일에 대해 동시에
recovery를 수행할 때 가장 효율적이다
다음과 같이 2가지 방식으로 병렬화시킬 수 있다.
- RECOVERY_PARALLELISM 파라미터 지정
- RECOVER 명령의 옵션에 지정
오라클 서버는 하나의 프로세스에서 log file을 순차적으로 읽어들이고, redo
정보를 여러 개의 recovery 프로세스에 전달해, log file에 기록된 변동 사항을
데이터파일에 적용시킬 수 있다.
Recovery Process는 오라클에서 자동적으로 구동되므로, recovery를 수행할 경우
한 개 이상의 session을 사용할 필요가 없다.
RECOVERY_PARALLELISM의 최대값은 PARALLEL_MAX_SERVERS 파라미터에 지정된 값을
초과할 수 없다.
Reference Ducumment
Oracle8 ops manual

Configuration files of the Oracle Application server can be backed up by "Backup and Recovery Tool"
Pls refer to the documentation,
http://download.oracle.com/docs/cd/B32110_01/core.1013/b32196/part5.htm#i436649
Also "backup to tapes feature" is not yet supported by this tool
thanks,
Murugesh
Message was edited by:
Murugesan Appukuttty

Online backup recovery

Similar Messages

Maybe you are looking for