Control File Backups
Hello-
I was looking over some configurations that was setup by another DBA.
There are 3 control files created but they all are on the same disk/directory.
Control file auto backup is on to tape.
If there was a hardware failure and all three control were corrupted/lost then a backup would be used but
full recovery and RESETLOGS would be needed which would lead to redo data loss.
If I configured 1 control file on a seperate disk. I would be able to copy this one and create 3 files again and the database
would be started again without needing recovery if all else was fine.
If the control keeps track of redo logs SCN, Archive logs history and RMAN backups when these change then wouldn't another control file backup/ trace need to be done ?
Control File Trace only alllows to rebuild the database not to copy. How often is the need to taken ? Every change in the database ?
Backup to the Flash Recovery is another backup not an updated copy to copy from but to restore/recovery with.
Do have have these theories correct and my best setup would to send at least one to another disk.
Thanks-
If there was a hardware failure and all three control were corrupted/lost then a backup would be used but
full recovery and RESETLOGS would be needed which would lead to redo data loss. No. If you lose all three controlfiles, you either
a. RESTORE a backup of the controlfile
OR
b. CREATE CONTROLFILE (from a script)
In either case, you do NOT need to do an INCOMPLETE Recovery. You will be doing a COMPLETE Recovery (if you have the Online Redo Logs). However, an OPEN RESETLOGS is still required. The %r in the log_archive_format since 10g allows ArchiveLogs to be retained through ResetLogs.
If the control keeps track of redo logs SCN, Archive logs history and RMAN backups when these change then wouldn't another control file backup/ trace need to be done ? If you RESTORE the controlfile you lose no information. However, you still have to OPEN RESETLOGS.
If you do a CREATE CONTROLFILE, yes, you lose information about ArchiveLogs history and RMAN Backups.
You can issue a CATALOG command to re-catalog available Backups.
Control File Trace only alllows to rebuild the database not to copy.A Control File Trace is to recreate the Controlfile. Not rebuild the database.
Backup to the Flash Recovery is another backup not an updated copy to copy from but to restore/recovery with. I don't understand what your statement or question might be here.
Hemant K Chitale
http://hemantoracledba.blogspot.com
Edited by: Hemant K Chitale on Mar 2, 2011 2:44 PM
Edited by: Hemant K Chitale on Mar 2, 2011 2:45 PM
Similar Messages
-
Control file backup is hung.
Hi,
When I initiate control file backup it is struck. Pls. see my Rman configuration.
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/oracle/rmanbkup/cf%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/oracle/rmanbkup/%U';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/S01/102_64/dbs/snapcf_S01.f'; # default
RMAN> backup current controlfile;
Starting backup at 28-JUN-09
using channel ORA_DISK_1
It is in this situation since 4 Hrs.
I had set all the permissions as mentioned in the SAP Note : 113747. Backup was happening as normal till 25th June thru DB13.
My observation is, I had alter the oracle parameter as per the quiry results. ( i.e added the events .. I had executed the script attached in the S.Note : 1171650. ST04 --> Performance --> Additional Function --> SQL Command Editor )
O/S : AIX 5.3,
DB : Oracle 10.2.0.2.0
ECC 6.0
Backup in all other servers are happening without any problem..
I appreciate your expert suggestions.
Thanks!
Sundaresh SuryanarayanHi Surendara Jain,
Still this problem persisting.. I have tried all.. I checked all the relevent S-Notes. I updated the brtools version also..
Even if I execute BRBACKUP it starts.. It creates the folder. But, the folder will be empty.. Pls. see the *.and file below..
MBES01:oras01 10> more beayrvav.and
BR0051I BRBACKUP 7.00 (41)
BR0055I Start of database backup: beayrvav.and 2009-07-07 08.12.17
BR0484I BRBACKUP log file: /oracle/S01/sapbackup/beayrvav.and
BR0477I Oracle pfile /oracle/S01/102_64/dbs/initS01.ora created from spfile /oracle/S01/102_64/dbs/spfileS01.ora
BR0101I Parameters
Name Value
oracle_sid S01
oracle_home /oracle/S01/102_64
oracle_profile /oracle/S01/102_64/dbs/initS01.ora
sapdata_home /oracle/S01
sap_profile /oracle/S01/102_64/dbs/initS01.sap
backup_mode ALL
backup_type online
backup_dev_type disk
backup_root_dir /oracle/S01/sapbackup
compress no
disk_copy_cmd rman
cpio_disk_flags -pdcu
exec_parallel 0
rman_compress no
system_info oras01/oras01 MBES01 AIX 3 5 00CD16724C00
oracle_info S01 10.2.0.2.0 8192 2959 21202296 MBES01 UTF8 UTF8
sap_info 700 SAPSR3 0002LK0003S010011E21297128880015Maintenance_ORA
make_info rs6000_64 OCI_102 Apr 8 2009
command_line /usr/sap/S01/SYS/exe/run/brbackup -p initS01.sap -d disk -t online -m all -k no -e 0 -o dist,time -l E -U
BR0116I ARCHIVE LOG LIST before backup for database instance S01
Parameter Value
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /oracle/S01/oraarch/S01arch
Archive format %t_%s_%r.dbf
Oldest online log sequence 2956
Next log sequence to archive 2959
Current log sequence 2959 SCN: 21202296
Database block size 8192 Thread: 1
Current system change number 21209894 ResetId: 674792151
BR0118I Tablespaces and data files
Tablespace TS-Status F-Status File Size Id. Device Link Type
MaxSize IncrSize BlkSize
PSAPSR3 ONLINE* ONLINE+ /oracle/S01/sapdata2/sr3_1/sr3.data1 2579505152 4 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ /oracle/S01/sapdata2/sr3_10/sr3.data10 1069555712 13 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ /oracle/S01/sapdata2/sr3_2/sr3.data2 2558533632 5 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ /oracle/S01/sapdata2/sr3_3/sr3.data3 3334479872 6 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ /oracle/S01/sapdata2/sr3_4/sr3.data4 3984596992 7 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ /oracle/S01/sapdata2/sr3_5/sr3.data5 3166707712 8 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ /oracle/S01/sapdata2/sr3_6/sr3.data6 2998935552 9 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ /oracle/S01/sapdata2/sr3_7/sr3.data7 2977964032 10 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ /oracle/S01/sapdata2/sr3_8/sr3.data8 2852134912 11 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3 ONLINE* ONLINE+ /oracle/S01/sapdata2/sr3_9/sr3.data9 2810191872 12 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ /oracle/S01/sapdata3/sr3700_1/sr3700.data1 3523223552 14 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ /oracle/S01/sapdata3/sr3700_2/sr3700.data2 4299169792 15 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ /oracle/S01/sapdata3/sr3700_3/sr3700.data3 3607109632 16 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3700 ONLINE* ONLINE+ /oracle/S01/sapdata3/sr3700_4/sr3700.data4 3428851712 17 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3DB ONLINE* ONLINE+ /oracle/S01/sapdata4/sr3db_1/sr3db.data1 2097160192 19 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3DB ONLINE* ONLINE+ /oracle/S01/sapdata4/sr3db_2/sr3db.data2 2097160192 20 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3DB ONLINE* ONLINE+ /oracle/S01/sapdata4/sr3db_3/sr3db.data3 1048584192 21 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPSR3USR ONLINE* ONLINE+ /oracle/S01/sapdata4/sr3usr_1/sr3usr.data1 20979712 18 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPTEMP ONLINE# ONLINE+ /oracle/S01/sapdata1/temp_1/temp.data1 1017126912 -1 3276802 NOLINK FILE 104
85760000 20971520 8192
PSAPUNDO ONLINE- ONLINE+ /oracle/S01/sapdata1/undo_1/undo.data1 2705334272 2 3276802 NOLINK FILE 104
85760000 20971520 8192
SYSAUX ONLINE* ONLINE+ /oracle/S01/sapdata1/sysaux_1/sysaux.data1 230694912 3 3276802 NOLINK FILE 104
85760000 20971520 8192
SYSTEM ONLINE* SYSTEM+ /oracle/S01/sapdata1/system_1/system.data1 513810432 1 3276802 NOLINK FILE 104
85760000 20971520 8192
BR0119I Redo log files
File Size Group Device Status Link Type
/oracle/S01/origlogA/log_g11m1.dbf 52429312 1 3276802 INUSE NOLINK FILE
/oracle/S01/mirrlogA/log_g11m2.dbf 52429312 1 3276802 INUSE NOLINK FILE
/oracle/S01/origlogB/log_g12m1.dbf 52429312 2 3276802 INUSE NOLINK FILE
/oracle/S01/mirrlogB/log_g12m2.dbf 52429312 2 3276802 INUSE NOLINK FILE
/oracle/S01/origlogA/log_g13m1.dbf 52429312 3 3276802 INUSE NOLINK FILE
/oracle/S01/mirrlogA/log_g13m2.dbf 52429312 3 3276802 INUSE NOLINK FILE
/oracle/S01/origlogB/log_g14m1.dbf 52429312 4 3276802 INUSE NOLINK FILE
/oracle/S01/mirrlogB/log_g14m2.dbf 52429312 4 3276802 INUSE NOLINK FILE
BR0120I Control files
File Size Id. Device Link Type
/oracle/S01/origlogA/cntrl/cntrlS01.dbf 14368768 0 3276802 NOLINK FILE
/oracle/S01/origlogB/cntrl/cntrlS01.dbf 14368768 0 3276802 NOLINK FILE
/oracle/S01/sapdata1/cntrl/cntrlS01.dbf 14368768 0 3276802 NOLINK FILE
BR0616I Tablespaces in table TSORA for SAP owner SAPSR3:
PSAPSR3, PSAPSR3700, PSAPSR3USR
BR0379I Distribution of files on volume #1:
Position Size Rate Compressed Duration Speed Name
[m:s] [MB/h]
1 2579505152* 2:19 63712 /oracle/S01/sapdata2/sr3_1/sr3.data1
2 1069555712* 0:59 62238 /oracle/S01/sapdata2/sr3_10/sr3.data10
3 2558533632* 2:19 63194 /oracle/S01/sapdata2/sr3_2/sr3.data2
4 3334479872* 2:48 68143 /oracle/S01/sapdata2/sr3_3/sr3.data3
5 3984596992* 3:19 68744 /oracle/S01/sapdata2/sr3_4/sr3.data4
6 3166707712* 2:49 64332 /oracle/S01/sapdata2/sr3_5/sr3.data5
7 2998935552* 2:38 65165 /oracle/S01/sapdata2/sr3_6/sr3.data6
8 2977964032* 2:39 64302 /oracle/S01/sapdata2/sr3_7/sr3.data7
9 2852134912* 2:28 66162 /oracle/S01/sapdata2/sr3_8/sr3.data8
10 2810191872* 2:29 64752 /oracle/S01/sapdata2/sr3_9/sr3.data9
11 3523223552* 2:49 71574 /oracle/S01/sapdata3/sr3700_1/sr3700.data1
12 4299169792* 3:38 67707 /oracle/S01/sapdata3/sr3700_2/sr3700.data2
13 3607109632* 3:09 65524 /oracle/S01/sapdata3/sr3700_3/sr3700.data3
14 3428851712* 2:48 70072 /oracle/S01/sapdata3/sr3700_4/sr3700.data4
15 2097160192* 1:59 60504 /oracle/S01/sapdata4/sr3db_1/sr3db.data1
16 2097160192* 1:58 61017 /oracle/S01/sapdata4/sr3db_2/sr3db.data2
17 1048584192* 0:59 61017 /oracle/S01/sapdata4/sr3db_3/sr3db.data3
18 20979712* 0:06 12005 /oracle/S01/sapdata4/sr3usr_1/sr3usr.data1
19 2705334272* 2:19 66820 /oracle/S01/sapdata1/undo_1/undo.data1
20 230694912* 0:19 41686 /oracle/S01/sapdata1/sysaux_1/sysaux.data1
21 513810432* 0:38 46422 /oracle/S01/sapdata1/system_1/system.data1
22 14368768 0:00 0* /oracle/S01/sapbackup/cntrlS01.dbf
Total: 51919052800* 45:29 65317
BR0284I BRBACKUP time stamp: 2009-07-07 08.12.19, elapsed time: 0:00
BR0057I Backup of database: S01
BR0058I BRBACKUP action ID: beayrvav
BR0059I BRBACKUP function ID: and
BR0110I Backup mode: ALL
BR0077I Database file for backup: /oracle/S01/sapbackup/cntrlS01.dbf
BR0061I 22 files found for backup, total size 49513.867 MB
BR0143I Backup type: online
BR0112I Files will not be compressed
BR0130I Backup device type: disk
BR0106I Files will be saved on disk in directory: /oracle/S01/sapbackup/beayrvav
BR0284I BRBACKUP time stamp: 2009-07-07 08.12.19, elapsed time: 0:00
BR0256I Enter 'c[ont]' to continue, 's[top]' to cancel BRBACKUP:
BR0284I BRBACKUP time stamp: 2009-07-07 08.12.54, elapsed time: 0:35
BR0257I Your reply: 'c'
BR0259I Program execution will be continued...
BR0370I Directory /oracle/S01/sapbackup/beayrvav created
end **************************************************
it won't move furthe after this.. I checked and compared SPFILE & init<SID>.sap with other servers (DEV,QA & PRD) all are same.. But, backup is happening on those server without any problem.
Can anybody help me on this..
Thanks!
Sundaresh Suryanarayan -
ORA-00245: control file backup failed; target is likely on a local file sys
Hello,
our RAC (Linux, 11.2.0.3.0) is rather new and we are still on gaining experiences with that system...
When starting the backup with RMAN we are getting the following error:
Starting Control File and SPFILE Autobackup at 04-JUL-12
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of Control File and SPFILE Autobackup command on ORA_DISK_1 channel at 07/04/2012 16:41:48
ORA-00245: control file backup failed; target is likely on a local file system
The reason for the error is clear ORA-00245 - in a RAC environment the location of the Snapshot Controlfile must be on a shared location.
When executing the RMAN command "show all" on each node, we are getting
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0.3/db/dbs/snapcf_PROD021.f'; # default
for node #1
and
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0.3/db/dbs/snapcf_PROD022.f'; # default
for node #2
When using a shared location for the Snapshot Controlfile do we still need to setup 2 different names for that file?
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/<shared location>/snapcf_PROD021.f'; # default
for node #1 and
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/<shared location>/snapcf_PROD022.f'; # default
for node #2
Or should we configure just one Snapshot Controlfile?
The RMAN setup for "CONFIGURE SNAPSHOT CONTROLFILE NAME TO..." must be changed on both nodes - correct?
Hopefully my question is clear enough - any help will be appreciated.
Rgds
JH
Edited by: VivaLaVida on 05.07.2012 11:41No, it must be configured on a shared storage:Not really required, i've RAC setup and snapshot is configured on local storage.
Configuring the RMAN Snapshot Control File Location
The snapshot control file is a copy of a database control file created in an operating system-specific location by Recovery Manager. RMAN creates the snapshot control file so that it has a consistent version of a control file to use when either resynchronizing the recovery catalog or backing up the control file. In Oracle RAC, the snapshot control file is only needed on the nodes on which RMAN performs backups; the snapshot control file does not need to be globally available to all instances in an Oracle RAC environment.
See below from doc.
http://docs.oracle.com/cd/B28359_01/rac.111/b28254/rman.htm#i455026 -
I have executed the following commands as I was not sure about the control file backup :-
1) ALTER DATABASE BACKUP CONTROLFILE TO '/DBJPC/control.bkp';
2)ALTER DATABASE BACKUP CONTROLFILE TO TRACE;
could anybody tell me whether these two statements override my database's previous configuration of control file backup or not (I think yes...) ??? If yes, is there any chances of database non-availability??? Finally, is there any drawbacks to run these two commands ...Hi
>>I'm new in Oracle and using Oracle 10G Enterprise Edition (10.2.0.1.0) on Red Hat Linux 32bits OS. I worked as a J2EE developer and there is no DBA in my office right now. So, I'm working as a stop gap person.
In that case you should not think about the recovery scenario.. However you can play with your test database on your personal m/c. but before doing this please read first.
>>I cann't find whether RMAN is used for control file back up or not and that's the reason to execute those queries. Are these files (backup of control files) automatically backed up or not (I think not).
Connect with RMAN and the type the command
RMAN> SHOW ALL;
>>Lastly, in case of damage/lost control files, this command will work or not- cp '/DBJPC/control.bkp' <location of control file>;
No, It wont work.. these are the trace file format(readable) while your database control file are binary
Start from here :Backup and Recovery
HTH -
A question about restoring from cold backup(control file backup not clear)
Hi,
I had another question about restoring the cold backup. My database is in noarchivelog mode and after taking a consistent cold backup, all I need to do is to restore the backup right? -Why I got this question is because: when I backup my control file to trace, I see statements like this:-----
-- Commands to re-create incarnation table
-- Below log names MUST be changed to existing filenames on
-- disk. Any one log file from each branch can be used to
-- re-create incarnation records.
-- ALTER DATABASE REGISTER LOGFILE '/uo1/app1/arch1_1_647102958.dbf';
-- Recovery is required if any of the datafiles are restored backups,
-- or if the last shutdown was not normal or immediate.
RECOVER DATABASE
-- Database can now be opened normally.
ALTER DATABASE OPEN;
My database is in noarchivelog mode now so don't know why these statements (of register the logfile) is there in the backup of control file? so when I restore the cold backup of this database, it will still work correct? (there is no logfile I have only CRD files in cold backup -no archive log files.)
thanks
NiravThanks for your inputs! It is most useful to me.
Regards
Nirav -
hi,
RMAN>backup database
on executing the above command does rman backsup the control file also????
Edited by: 793097 on Dec 7, 2010 12:49 AMHi 793097,
Yes it does backup the controlfile implicitly by the command.
There are two flavors.
- If you have configured controlfile autobackup to on (use show all to check) rman will create a separate backup in a file with format c-dbid-date-xx.
- without configuration the backup piece containing datafile 1 (system01.dbf) will also contain the controlfile backup.
Regards,
Tycho -
Can there be two control file auto file backups one to disk and one to tape ?
Thanks,Hi
In our RMAN setup SHOW ALL; there is both disk and tape configured. but it does not backup to disk anymore
and I am getting the errors below in my alert.log.
There are about ten old copies on the disk. How do these get purged ?
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'D:\DONT_TOUCH\CONTROL_FILE_BACKUP\%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default Starting control autobackup
Wed Feb 03 00:20:31 2010
Errors in file d:\oracle\product\10.2.0\admin\udump\_ora_3600.trc:
Wed Feb 03 00:20:31 2010
Errors in file d:\oracle\product\10.2.0\admin\udump\_ora_3600.trc:
Wed Feb 03 00:20:31 2010
Errors in file d:\oracle\product\10.2.0\admin\udump\_ora_3600.trc:
Wed Feb 03 00:20:31 2010
Control autobackup written to SBT_TAPE device
comment 'API Version 2.0,MMS Version 5.0.0.0',
media '/database/_1265174399_C1_F1'
handle 'c-1624991920-20100203-01'
Wed Feb 03 08:59:14 2010 -
Control file backup using RMAN
Hi,
I need to take the backup of control file using RMAN and I am using ASM non RAC.
DB : 10.2.0.4.0
oS : SunOS rmohsitut01 5.10 Generic_144488-17 sun4u sparc SUNW,SPARC-Enterprise
I have tried bellow commands
======
RMAN> backup format '/tmp/backup/control.back' current controlfile;
Starting backup at 21-JUL-12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=19983 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=9983 devtype=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: sid=19982 devtype=DISK
allocated channel: ORA_DISK_4
channel ORA_DISK_4: sid=9982 devtype=DISK
allocated channel: ORA_DISK_5
channel ORA_DISK_5: sid=19981 devtype=DISK
allocated channel: ORA_DISK_6
channel ORA_DISK_6: sid=19980 devtype=DISK
allocated channel: ORA_DISK_7
channel ORA_DISK_7: sid=9981 devtype=DISK
allocated channel: ORA_DISK_8
channel ORA_DISK_8: sid=19979 devtype=DISK
allocated channel: ORA_DISK_9
channel ORA_DISK_9: sid=19978 devtype=DISK
allocated channel: ORA_DISK_10
channel ORA_DISK_10: sid=9980 devtype=DISK
allocated channel: ORA_DISK_11
channel ORA_DISK_11: sid=19985 devtype=DISK
allocated channel: ORA_DISK_12
channel ORA_DISK_12: sid=9979 devtype=DISK
allocated channel: ORA_DISK_13
channel ORA_DISK_13: sid=19977 devtype=DISK
allocated channel: ORA_DISK_14
channel ORA_DISK_14: sid=19976 devtype=DISK
allocated channel: ORA_DISK_15
channel ORA_DISK_15: sid=9978 devtype=DISK
allocated channel: ORA_DISK_16
channel ORA_DISK_16: sid=19975 devtype=DISK
allocated channel: ORA_DISK_17
channel ORA_DISK_17: sid=19974 devtype=DISK
allocated channel: ORA_DISK_18
channel ORA_DISK_18: sid=9986 devtype=DISK
BACKUP CURRENT CONTROLFILE TO ':/tmp/control.bak'; RMAN allocating channels but backup is not happening.
Any idea ?
--Thanks in AdvanceHi,.
I have given the bellow command
RMAN> BACKUP AS COPY CURRENT CONTROLFILE FORMAT '/tmp/control_stdby_backup.ctl';
Starting backup at 21-JUL-12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=19985 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=9981 devtype=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: sid=19977 devtype=DISK
allocated channel: ORA_DISK_4
channel ORA_DISK_4: sid=9980 devtype=DISK
allocated channel: ORA_DISK_5
channel ORA_DISK_5: sid=9979 devtype=DISK
allocated channel: ORA_DISK_6
channel ORA_DISK_6: sid=9978 devtype=DISK
allocated channel: ORA_DISK_7
channel ORA_DISK_7: sid=19976 devtype=DISK
allocated channel: ORA_DISK_8
channel ORA_DISK_8: sid=9986 devtype=DISK
allocated channel: ORA_DISK_9
channel ORA_DISK_9: sid=19975 devtype=DISK
allocated channel: ORA_DISK_10
channel ORA_DISK_10: sid=9977 devtype=DISKBut it keeps on allocating channels and never ending
Please help ..
Edited by: Vijay.Cherukuri on Jul 21, 2012 7:19 PM -
Control file restore without backup
I installed oracle 10g
Backed it up with rman ... backup database
Now I lost the control file
With out auto backup of control file ..how can i restore my control file and get it in sync with my database fileHi,
As you stated as the below things
I installed oracle 10g
Backed it up with rman ... backup database Does the backup is taken is of full backup, then you can restore the controlfile. Basic thing, when ever the System.dbf is backup implicity the control file backup is done, don't forget, then is no need to set autobackup on looking into this case.
try to restore as from backup, sa I stated above, your issue will be solved, remember if any strucutal changes are carried out after your backup, then those can not be recovered based on backup controlfile (like addition of new datafiles)
- Pavan Kumar N
Oracle 9i/10g - OCP
http://oracleinternals.blogspot.com/ -
Control file and spfile auto backup backup is failing
Hello All,
I am using Oracle RAC 11gR2 with ASM. My database is 2 nodes RAC1 and RAC2.
I am taking RMAN database backups to ASM diskgroup (FRA) and to a Network File System mounted on both RAC1 and RAC2. I have this requirement to take backup also outside ASM.
I have set: CONFIGURE CONTROL FILE AUTOBACKUP ON;
I am runing the RMAN backup job from node 2 (RAC2)
I am facing the below error when taking a backup to the Network File system;
Starting Control File and SPFILE Autobackup at 08-SEP-12
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of Control File and SPFILE Autobackup command on ORA_DISK_1 channel at 09/08/2012 18:20:06
ORA-00245: control file backup failed; target is likely on a local file systemHow could I solve that ?
Regards,NB wrote:
Is that general configuration ? or i can only do it for the sessions that RMAN to NFS?at rman
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'location_of_shared_storage%F'; -
Hi friends,
I want to do homogeneous system copy.
I want to know the steps in homogeneous copy, and how to create control file from source system for target system.
And after that what activity is required .
thanks
Regards
Manojhi
while doing homogeneous copy sap will do some functinalaties through one sql file I think it will take control file backup and recreate it.
if u want to do manually
issue command
sql>alter database backup controlfile to trace;
look for trace file in udump dir from that file u can recreate controlfile or rename database.
before doing take complete cold backup of source.
start process with sap inst
it will do certain tasks ref in manual
let me know if u knoe some more inputs
vinod -
Creation of control file in Oracle 10g
Hi,
I had taken the backup of control file(backup control file to trace) and edited it to change the new location of the datafile.But when i try to create the Control file(Startup nomount,@cntrl.sql) it fails with the following error
ERROR at line 1:
ORA-01503: CREATE CONTROLFILE failed
ORA-01276: Cannot add file
/oracle/DBS/redolog/DBS/controlfile/o1_mf_2s4ho2n8_.ctl. File has an Oracle
Managed Files file name.
how can i recreate it?
Regards,
CherryHI,
what are you actually trying to do...
relocation of datafile or control file.
if you want to relocation of data file then go through below link
http://download-uk.oracle.com/docs/cd/B14117_01/server.101/b10739/dfiles.htm#i1006457
ORA-01276
http://www.idevelopment.info/data/Oracle/DBA_tips/Tablespaces/TBS_8.shtml
hope this helps
Taj -
Hi All,
11.2.0.1 on AIX 7.1 and Level 0 happens on every SATURDAY and L1 backup run every day.
We are using following script for level0 RMAN backup:
RUN {
SHOW ALL;
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 4;
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
ALLOCATE CHANNEL ch1 TYPE DISK;
ALLOCATE CHANNEL ch2 TYPE DISK;
ALLOCATE CHANNEL ch3 TYPE DISK;
ALLOCATE CHANNEL ch4 TYPE DISK;
BACKUP FORMAT '/oraclebackup/HFM11PROD/DF_L0_%d_%D%M%Y_%u_%s_%p' INCREMENTAL LEVEL 0 AS COMPRESSED BACKUPSET DATABASE TAG='LEVEL0';
BACKUP FORMAT '/oraclebackup/HFM11PROD/ARC_L0_%d_%D%M%Y_%u_%s_%p' ARCHIVELOG ALL NOT BACKED UP 2 TIMES TAG='LEVEL0';
BACKUP FORMAT '/oraclebackup/HFM11PROD/CF_L0_%d_%D%M%Y_%u_%s_%p' CURRENT CONTROLFILE TAG='LEVEL0';
BACKUP FORMAT '/oraclebackup/HFM11PROD/SP_L0_%d_%D%M%Y_%u_%s_%p' SPFILE TAG='LEVEL0';
CROSSCHECK ARCHIVELOG ALL;
DELETE NOPROMPT OBSOLETE;
RELEASE CHANNEL ch1;
RELEASE CHANNEL ch2;
RELEASE CHANNEL ch3;
RELEASE CHANNEL ch4;
}Now backup logs shows that we have backup of control file in two backup pieces : One implicitly in a backup piece DF_L0_HFM11PRD_10112012_l8npv5b6_13992_1
and other one is explicitly in CF_L0_HFM11PRD_10112012_lhnpv62e_14001_1 .
RMAN> RUN {
2> SHOW ALL;
3> CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 4;
4> CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
5> ALLOCATE CHANNEL ch1 TYPE DISK;
6> ALLOCATE CHANNEL ch2 TYPE DISK;
7> ALLOCATE CHANNEL ch3 TYPE DISK;
8> ALLOCATE CHANNEL ch4 TYPE DISK;
9> BACKUP FORMAT '/oraclebackup/HFM11PROD/DF_L0_%d_%D%M%Y_%u_%s_%p' INCREMENTAL LEVEL 0 AS COMPRESSED BACKUPSET DATABASE TAG='LEVEL0';
10> BACKUP FORMAT '/oraclebackup/HFM11PROD/ARC_L0_%d_%D%M%Y_%u_%s_%p' ARCHIVELOG ALL NOT BACKED UP 2 TIMES TAG='LEVEL0';
11> BACKUP FORMAT '/oraclebackup/HFM11PROD/CF_L0_%d_%D%M%Y_%u_%s_%p' CURRENT CONTROLFILE TAG='LEVEL0';
12> BACKUP FORMAT '/oraclebackup/HFM11PROD/SP_L0_%d_%D%M%Y_%u_%s_%p' SPFILE TAG='LEVEL0';
13> CROSSCHECK ARCHIVELOG ALL;
14> DELETE NOPROMPT OBSOLETE;
15> RELEASE CHANNEL ch1;
16> RELEASE CHANNEL ch2;
17> RELEASE CHANNEL ch3;
18> RELEASE CHANNEL ch4;
19> }
RMAN configuration parameters for database with db_unique_name HFM11PRD are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 4;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/orahyp_p/product/11.2/dbs/snapcf_HFM11PRD.f'; # default
old RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 4;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 4;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
allocated channel: ch1
channel ch1: SID=1210 device type=DISK
allocated channel: ch2
channel ch2: SID=1477 device type=DISK
allocated channel: ch3
channel ch3: SID=66 device type=DISK
allocated channel: ch4
channel ch4: SID=1156 device type=DISK
Starting backup at 10-NOV-12
channel ch1: starting compressed incremental level 0 datafile backup set
channel ch1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u04/oradata/HFM11PRD/system01.dbf
input datafile file number=00008 name=/u04/oradata/HFM11PRD/EPM_HFM4.DBF
input datafile file number=00012 name=/u04/oradata/HFM11PRD/EPM_HFM8.DBF
input datafile file number=00017 name=/u04/oradata/HFM11PRD/EPM_HFM12.DBF
input datafile file number=00004 name=/u04/oradata/HFM11PRD/EPM_HSS1.DBF
input datafile file number=00020 name=/u04/oradata/HFM11PRD/EPM_HFM3.DBF
channel ch1: starting piece 1 at 10-NOV-12
channel ch2: starting compressed incremental level 0 datafile backup set
channel ch2: specifying datafile(s) in backup set
input datafile file number=00003 name=/u04/oradata/HFM11PRD/undots01.dbf
input datafile file number=00009 name=/u04/oradata/HFM11PRD/EPM_HFM5.DBF
input datafile file number=00013 name=/u04/oradata/HFM11PRD/EPM_HFM9.DBF
input datafile file number=00018 name=/u04/oradata/HFM11PRD/EPM_HFM13.DBF
input datafile file number=00005 name=/u04/oradata/HFM11PRD/EPM_BI1.DBF
input datafile file number=00021 name=/u04/oradata/HFM11PRD/EPM_HFM15.DBF
channel ch2: starting piece 1 at 10-NOV-12
channel ch3: starting compressed incremental level 0 datafile backup set
channel ch3: specifying datafile(s) in backup set
input datafile file number=00007 name=/u04/oradata/HFM11PRD/EPM_HFM2.DBF
input datafile file number=00011 name=/u04/oradata/HFM11PRD/EPM_HFM7.DBF
input datafile file number=00016 name=/u04/oradata/HFM11PRD/EPM_HFM11.DBF
input datafile file number=00002 name=/u04/oradata/HFM11PRD/sysaux01.dbf
input datafile file number=00022 name=/u04/oradata/HFM11PRD/EPM_HSS_new1.DBF
channel ch3: starting piece 1 at 10-NOV-12
channel ch4: starting compressed incremental level 0 datafile backup set
channel ch4: specifying datafile(s) in backup set
input datafile file number=00006 name=/u04/oradata/HFM11PRD/EPM_HFM1.DBF
input datafile file number=00010 name=/u04/oradata/HFM11PRD/EPM_HFM6.DBF
input datafile file number=00015 name=/u04/oradata/HFM11PRD/EPM_HFM10.DBF
input datafile file number=00019 name=/u04/oradata/HFM11PRD/EPM_HFM14.DBF
input datafile file number=00014 name=/u04/oradata/HFM11PRD/userdata01.dbf
channel ch4: starting piece 1 at 10-NOV-12
channel ch2: finished piece 1 at 10-NOV-12
_*piece handle=/oraclebackup/HFM11PROD/DF_L0_HFM11PRD_10112012_l8npv5b6_13992_1 tag=LEVEL0 comment=NONE*_
channel ch2: backup set complete, elapsed time: 00:10:46
channel ch2: starting compressed incremental level 0 datafile backup set
channel ch2: specifying datafile(s) in backup set
_*including current control file in backup set*channel ch2: starting piece 1 at 10-NOV-12_
channel ch2: finished piece 1 at 10-NOV-12
piece handle=/oraclebackup/HFM11PROD/DF_L0_HFM11PRD_10112012_lbnpv5vc_13995_1 tag=LEVEL0 comment=NONE
channel ch2: backup set complete, elapsed time: 00:00:01
channel ch2: starting compressed incremental level 0 datafile backup set
channel ch2: specifying datafile(s) in backup set
including current SPFILE in backup set
channel ch2: starting piece 1 at 10-NOV-12
channel ch2: finished piece 1 at 10-NOV-12
piece handle=/oraclebackup/HFM11PROD/DF_L0_HFM11PRD_10112012_lcnpv5ve_13996_1 tag=LEVEL0 comment=NONE
channel ch2: backup set complete, elapsed time: 00:00:01
channel ch1: finished piece 1 at 10-NOV-12
piece handle=/oraclebackup/HFM11PROD/DF_L0_HFM11PRD_10112012_l7npv5b6_13991_1 tag=LEVEL0 comment=NONE
channel ch1: backup set complete, elapsed time: 00:11:03
channel ch4: finished piece 1 at 10-NOV-12
piece handle=/oraclebackup/HFM11PROD/DF_L0_HFM11PRD_10112012_lanpv5b7_13994_1 tag=LEVEL0 comment=NONE
channel ch4: backup set complete, elapsed time: 00:11:32
channel ch3: finished piece 1 at 10-NOV-12
piece handle=/oraclebackup/HFM11PROD/DF_L0_HFM11PRD_10112012_l9npv5b6_13993_1 tag=LEVEL0 comment=NONE
channel ch3: backup set complete, elapsed time: 00:11:52
Finished backup at 10-NOV-12
Starting backup at 10-NOV-12
current log archived
channel ch1: starting compressed archived log backup set
channel ch1: specifying archived log(s) in backup set
input archived log thread=1 sequence=40007 RECID=40001 STAMP=798971664
input archived log thread=1 sequence=40008 RECID=40002 STAMP=798972711
input archived log thread=1 sequence=40009 RECID=40003 STAMP=798973470
input archived log thread=1 sequence=40010 RECID=40004 STAMP=798974835
input archived log thread=1 sequence=40011 RECID=40005 STAMP=798975943
channel ch1: starting piece 1 at 10-NOV-12
channel ch2: starting compressed archived log backup set
channel ch2: specifying archived log(s) in backup set
input archived log thread=1 sequence=40012 RECID=40006 STAMP=798976804
input archived log thread=1 sequence=40013 RECID=40007 STAMP=798977866
input archived log thread=1 sequence=40014 RECID=40008 STAMP=798978754
input archived log thread=1 sequence=40015 RECID=40009 STAMP=798980083
input archived log thread=1 sequence=40016 RECID=40010 STAMP=798981194
channel ch2: starting piece 1 at 10-NOV-12
channel ch3: starting compressed archived log backup set
channel ch3: specifying archived log(s) in backup set
input archived log thread=1 sequence=40017 RECID=40011 STAMP=798982283
input archived log thread=1 sequence=40018 RECID=40012 STAMP=798983171
input archived log thread=1 sequence=40019 RECID=40013 STAMP=798984077
input archived log thread=1 sequence=40020 RECID=40014 STAMP=798985146
input archived log thread=1 sequence=40021 RECID=40015 STAMP=798985212
channel ch3: starting piece 1 at 10-NOV-12
channel ch4: starting compressed archived log backup set
channel ch4: specifying archived log(s) in backup set
input archived log thread=1 sequence=40022 RECID=40016 STAMP=798985214
input archived log thread=1 sequence=40023 RECID=40017 STAMP=798985992
input archived log thread=1 sequence=40024 RECID=40018 STAMP=798987561
input archived log thread=1 sequence=40025 RECID=40019 STAMP=798988338
channel ch4: starting piece 1 at 10-NOV-12
channel ch4: finished piece 1 at 10-NOV-12
piece handle=/oraclebackup/HFM11PROD/ARC_L0_HFM11PRD_10112012_lgnpv61k_14000_1 tag=LEVEL0 comment=NONE
channel ch4: backup set complete, elapsed time: 00:00:15
channel ch1: finished piece 1 at 10-NOV-12
piece handle=/oraclebackup/HFM11PROD/ARC_L0_HFM11PRD_10112012_ldnpv61j_13997_1 tag=LEVEL0 comment=NONE
channel ch1: backup set complete, elapsed time: 00:00:26
channel ch2: finished piece 1 at 10-NOV-12
piece handle=/oraclebackup/HFM11PROD/ARC_L0_HFM11PRD_10112012_lenpv61j_13998_1 tag=LEVEL0 comment=NONE
channel ch2: backup set complete, elapsed time: 00:00:26
channel ch3: finished piece 1 at 10-NOV-12
piece handle=/oraclebackup/HFM11PROD/ARC_L0_HFM11PRD_10112012_lfnpv61j_13999_1 tag=LEVEL0 comment=NONE
channel ch3: backup set complete, elapsed time: 00:00:25
Finished backup at 10-NOV-12
Starting backup at 10-NOV-12
channel ch1: starting compressed full datafile backup set
channel ch1: specifying datafile(s) in backup set
_*including current control file in backup set*_
channel ch1: starting piece 1 at 10-NOV-12
channel ch1: finished piece 1 at 10-NOV-12
_*piece handle=/oraclebackup/HFM11PROD/CF_L0_HFM11PRD_10112012_lhnpv62e_14001_1 tag=LEVEL0 comment=NONE*_channel ch1: backup set complete, elapsed time: 00:00:01
Finished backup at 10-NOV-12
Starting backup at 10-NOV-12
channel ch1: starting compressed full datafile backup set
channel ch1: specifying datafile(s) in backup set
including current SPFILE in backup set
channel ch1: starting piece 1 at 10-NOV-12
channel ch1: finished piece 1 at 10-NOV-12
piece handle=/oraclebackup/HFM11PROD/SP_L0_HFM11PRD_10112012_linpv62i_14002_1 tag=LEVEL0 comment=NONE
channel ch1: backup set complete, elapsed time: 00:00:01
Finished backup at 10-NOV-12Following is the script of Leve 1 RMAN backup.
RUN {
SHOW ALL;
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 4;
ALLOCATE CHANNEL ch1 TYPE DISK;
ALLOCATE CHANNEL ch2 TYPE DISK;
ALLOCATE CHANNEL ch3 TYPE DISK;
ALLOCATE CHANNEL ch4 TYPE DISK;
BACKUP FORMAT '/oraclebackup/HFM11PROD/DF_L1_%d_%D%M%Y_%u_%s_%p' INCREMENTAL LEVEL 1 AS COMPRESSED BACKUPSET DATABASE TAG='LEVEL1';
BACKUP FORMAT '/oraclebackup/HFM11PROD/ARC_L1_%d_%D%M%Y_%u_%s_%p' ARCHIVELOG ALL NOT BACKED UP 2 TIMES TAG='LEVEL1';
CROSSCHECK ARCHIVELOG ALL;
DELETE NOPROMPT OBSOLETE;
RELEASE CHANNEL ch1;
RELEASE CHANNEL ch2;
RELEASE CHANNEL ch3;
RELEASE CHANNEL ch4;
}Following is the log from Level 1 backup which shows that it has marked the backup of control file in backup piece CF_L0_HFM11PRD_10112012_lhnpv62e_14001_1 as obsolete and deleted.
RMAN> RUN {
2> SHOW ALL;
3> CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 4;
4> ALLOCATE CHANNEL ch1 TYPE DISK;
5> ALLOCATE CHANNEL ch2 TYPE DISK;
6> ALLOCATE CHANNEL ch3 TYPE DISK;
7> ALLOCATE CHANNEL ch4 TYPE DISK;
8> BACKUP FORMAT '/oraclebackup/HFM11PROD/DF_L1_%d_%D%M%Y_%u_%s_%p' INCREMENTAL LEVEL 1 AS COMPRESSED BACKUPSET DATABASE TAG='LEVEL1';
9> BACKUP FORMAT '/oraclebackup/HFM11PROD/ARC_L1_%d_%D%M%Y_%u_%s_%p' ARCHIVELOG ALL NOT BACKED UP 2 TIMES TAG='LEVEL1';
10> CROSSCHECK ARCHIVELOG ALL;
11> DELETE NOPROMPT OBSOLETE;
12> RELEASE CHANNEL ch1;
13> RELEASE CHANNEL ch2;
14> RELEASE CHANNEL ch3;
15> RELEASE CHANNEL ch4;
16> }
RMAN configuration parameters for database with db_unique_name HFM11PRD are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 4;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/orahyp_p/product/11.2/dbs/snapcf_HFM11PRD.f'; # default
old RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 4;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 4;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
allocated channel: ch1
channel ch1: SID=1718 device type=DISK
allocated channel: ch2
channel ch2: SID=1499 device type=DISK
allocated channel: ch3
channel ch3: SID=119 device type=DISK
allocated channel: ch4
channel ch4: SID=1166 device type=DISK
Starting backup at 12-NOV-12
channel ch1: starting compressed incremental level 1 datafile backup set
channel ch1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u04/oradata/HFM11PRD/system01.dbf
input datafile file number=00008 name=/u04/oradata/HFM11PRD/EPM_HFM4.DBF
input datafile file number=00012 name=/u04/oradata/HFM11PRD/EPM_HFM8.DBF
input datafile file number=00017 name=/u04/oradata/HFM11PRD/EPM_HFM12.DBF
input datafile file number=00004 name=/u04/oradata/HFM11PRD/EPM_HSS1.DBF
input datafile file number=00020 name=/u04/oradata/HFM11PRD/EPM_HFM3.DBF
channel ch1: starting piece 1 at 12-NOV-12
channel ch2: starting compressed incremental level 1 datafile backup set
channel ch2: specifying datafile(s) in backup set
input datafile file number=00003 name=/u04/oradata/HFM11PRD/undots01.dbf
input datafile file number=00009 name=/u04/oradata/HFM11PRD/EPM_HFM5.DBF
input datafile file number=00013 name=/u04/oradata/HFM11PRD/EPM_HFM9.DBF
input datafile file number=00018 name=/u04/oradata/HFM11PRD/EPM_HFM13.DBF
input datafile file number=00005 name=/u04/oradata/HFM11PRD/EPM_BI1.DBF
input datafile file number=00021 name=/u04/oradata/HFM11PRD/EPM_HFM15.DBF
channel ch2: starting piece 1 at 12-NOV-12
channel ch3: starting compressed incremental level 1 datafile backup set
channel ch3: specifying datafile(s) in backup set
input datafile file number=00007 name=/u04/oradata/HFM11PRD/EPM_HFM2.DBF
input datafile file number=00011 name=/u04/oradata/HFM11PRD/EPM_HFM7.DBF
input datafile file number=00016 name=/u04/oradata/HFM11PRD/EPM_HFM11.DBF
input datafile file number=00002 name=/u04/oradata/HFM11PRD/sysaux01.dbf
input datafile file number=00022 name=/u04/oradata/HFM11PRD/EPM_HSS_new1.DBF
channel ch3: starting piece 1 at 12-NOV-12
channel ch4: starting compressed incremental level 1 datafile backup set
channel ch4: specifying datafile(s) in backup set
input datafile file number=00006 name=/u04/oradata/HFM11PRD/EPM_HFM1.DBF
input datafile file number=00010 name=/u04/oradata/HFM11PRD/EPM_HFM6.DBF
input datafile file number=00015 name=/u04/oradata/HFM11PRD/EPM_HFM10.DBF
input datafile file number=00019 name=/u04/oradata/HFM11PRD/EPM_HFM14.DBF
input datafile file number=00014 name=/u04/oradata/HFM11PRD/userdata01.dbf
channel ch4: starting piece 1 at 12-NOV-12
channel ch1: finished piece 1 at 12-NOV-12
piece handle=/oraclebackup/HFM11PROD/DF_L1_HFM11PRD_12112012_lvnq4e3a_14015_1 tag=LEVEL1 comment=NONE
channel ch1: backup set complete, elapsed time: 00:01:36
channel ch1: starting compressed incremental level 1 datafile backup set
channel ch1: specifying datafile(s) in backup set
channel ch4: finished piece 1 at 12-NOV-12
piece handle=/oraclebackup/HFM11PROD/DF_L1_HFM11PRD_12112012_m2nq4e3a_14018_1 tag=LEVEL1 comment=NONE
channel ch4: backup set complete, elapsed time: 00:01:35
channel ch4: starting compressed incremental level 1 datafile backup set
channel ch4: specifying datafile(s) in backup set
including current SPFILE in backup set
channel ch4: starting piece 1 at 12-NOV-12
including current control file in backup set
channel ch1: starting piece 1 at 12-NOV-12
channel ch1: finished piece 1 at 12-NOV-12
piece handle=/oraclebackup/HFM11PROD/DF_L1_HFM11PRD_12112012_m3nq4e6a_14019_1 tag=LEVEL1 comment=NONE
channel ch1: backup set complete, elapsed time: 00:00:01
channel ch4: finished piece 1 at 12-NOV-12
piece handle=/oraclebackup/HFM11PROD/DF_L1_HFM11PRD_12112012_m4nq4e6a_14020_1 tag=LEVEL1 comment=NONE
channel ch4: backup set complete, elapsed time: 00:00:01
channel ch3: finished piece 1 at 12-NOV-12
piece handle=/oraclebackup/HFM11PROD/DF_L1_HFM11PRD_12112012_m1nq4e3a_14017_1 tag=LEVEL1 comment=NONE
channel ch3: backup set complete, elapsed time: 00:01:39
channel ch2: finished piece 1 at 12-NOV-12
piece handle=/oraclebackup/HFM11PROD/DF_L1_HFM11PRD_12112012_m0nq4e3a_14016_1 tag=LEVEL1 comment=NONE
channel ch2: backup set complete, elapsed time: 00:02:41
Finished backup at 12-NOV-12
Starting backup at 12-NOV-12
current log archived
channel ch1: starting compressed archived log backup set
channel ch1: specifying archived log(s) in backup set
input archived log thread=1 sequence=40201 RECID=40195 STAMP=799144567
input archived log thread=1 sequence=40202 RECID=40196 STAMP=799145383
input archived log thread=1 sequence=40203 RECID=40197 STAMP=799146296
input archived log thread=1 sequence=40204 RECID=40198 STAMP=799147040
input archived log thread=1 sequence=40205 RECID=40199 STAMP=799147640
input archived log thread=1 sequence=40206 RECID=40200 STAMP=799148271
channel ch1: starting piece 1 at 12-NOV-12
channel ch2: starting compressed archived log backup set
channel ch2: specifying archived log(s) in backup set
input archived log thread=1 sequence=40207 RECID=40201 STAMP=799149018
input archived log thread=1 sequence=40208 RECID=40202 STAMP=799150009
input archived log thread=1 sequence=40209 RECID=40203 STAMP=799150549
input archived log thread=1 sequence=40210 RECID=40204 STAMP=799151041
input archived log thread=1 sequence=40211 RECID=40205 STAMP=799151860
input archived log thread=1 sequence=40212 RECID=40206 STAMP=799152535
channel ch2: starting piece 1 at 12-NOV-12
channel ch3: starting compressed archived log backup set
channel ch3: specifying archived log(s) in backup set
input archived log thread=1 sequence=40213 RECID=40207 STAMP=799153553
input archived log thread=1 sequence=40214 RECID=40208 STAMP=799153980
input archived log thread=1 sequence=40215 RECID=40209 STAMP=799154283
input archived log thread=1 sequence=40216 RECID=40210 STAMP=799155243
input archived log thread=1 sequence=40217 RECID=40211 STAMP=799155964
input archived log thread=1 sequence=40218 RECID=40212 STAMP=799156899
channel ch3: starting piece 1 at 12-NOV-12
channel ch4: starting compressed archived log backup set
channel ch4: specifying archived log(s) in backup set
input archived log thread=1 sequence=40219 RECID=40213 STAMP=799157722
input archived log thread=1 sequence=40220 RECID=40214 STAMP=799158015
input archived log thread=1 sequence=40221 RECID=40215 STAMP=799158018
input archived log thread=1 sequence=40222 RECID=40216 STAMP=799158847
input archived log thread=1 sequence=40223 RECID=40217 STAMP=799159640
input archived log thread=1 sequence=40224 RECID=40218 STAMP=799160590
channel ch4: starting piece 1 at 12-NOV-12
channel ch4: finished piece 1 at 12-NOV-12
piece handle=/oraclebackup/HFM11PROD/ARC_L1_HFM11PRD_12112012_m8nq4e8h_14024_1 tag=LEVEL1 comment=NONE
channel ch4: backup set complete, elapsed time: 00:00:25
channel ch1: finished piece 1 at 12-NOV-12
piece handle=/oraclebackup/HFM11PROD/ARC_L1_HFM11PRD_12112012_m5nq4e8g_14021_1 tag=LEVEL1 comment=NONE
channel ch1: backup set complete, elapsed time: 00:00:36
channel ch2: finished piece 1 at 12-NOV-12
piece handle=/oraclebackup/HFM11PROD/ARC_L1_HFM11PRD_12112012_m6nq4e8g_14022_1 tag=LEVEL1 comment=NONE
channel ch2: backup set complete, elapsed time: 00:00:36
channel ch3: finished piece 1 at 12-NOV-12
piece handle=/oraclebackup/HFM11PROD/ARC_L1_HFM11PRD_12112012_m7nq4e8g_14023_1 tag=LEVEL1 comment=NONE
channel ch3: backup set complete, elapsed time: 00:00:35
Finished backup at 12-NOV-12
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402011737949656.ARC RECID=40195 STAMP=799144567
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402021737949656.ARC RECID=40196 STAMP=799145383
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402031737949656.ARC RECID=40197 STAMP=799146296
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402041737949656.ARC RECID=40198 STAMP=799147040
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402051737949656.ARC RECID=40199 STAMP=799147640
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402061737949656.ARC RECID=40200 STAMP=799148271
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402071737949656.ARC RECID=40201 STAMP=799149018
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402081737949656.ARC RECID=40202 STAMP=799150009
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402091737949656.ARC RECID=40203 STAMP=799150549
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402101737949656.ARC RECID=40204 STAMP=799151041
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402111737949656.ARC RECID=40205 STAMP=799151860
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402121737949656.ARC RECID=40206 STAMP=799152535
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402131737949656.ARC RECID=40207 STAMP=799153553
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402141737949656.ARC RECID=40208 STAMP=799153980
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402151737949656.ARC RECID=40209 STAMP=799154283
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402161737949656.ARC RECID=40210 STAMP=799155243
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402171737949656.ARC RECID=40211 STAMP=799155964
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402181737949656.ARC RECID=40212 STAMP=799156899
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402191737949656.ARC RECID=40213 STAMP=799157722
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402201737949656.ARC RECID=40214 STAMP=799158015
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402211737949656.ARC RECID=40215 STAMP=799158018
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402221737949656.ARC RECID=40216 STAMP=799158847
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402231737949656.ARC RECID=40217 STAMP=799159640
validation succeeded for archived log
archived log file name=/u05/oradata/HFM11PRD/HFM11PRD_402241737949656.ARC RECID=40218 STAMP=799160590
Crosschecked 24 objects
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Backup Set 18521832 10-NOV-12
Backup Piece 18521838 10-NOV-12 /oraclebackup/HFM11PROD/CF_L0_HFM11PRD_10112012_lhnpv62e_14001_1
Backup Set 18521846 10-NOV-12
Backup Piece 18521848 10-NOV-12 /oraclebackup/HFM11PROD/SP_L0_HFM11PRD_10112012_linpv62i_14002_1
deleted backup piece
backup piece handle=/oraclebackup/HFM11PROD/CF_L0_HFM11PRD_10112012_lhnpv62e_14001_1 RECID=14000 STAMP=798988367
deleted backup piece
backup piece handle=/oraclebackup/HFM11PROD/SP_L0_HFM11PRD_10112012_linpv62i_14002_1 RECID=14001 STAMP=798988370
Deleted 2 objects
released channel: ch1
released channel: ch2
released channel: ch3
released channel: ch4
RMAN> exit;Now, on Friday when i am trying to do a restore for this database on another server i am getting error as below. Restore script is as below.
run
allocate AUXILIARY channel c1 device type disk;
allocate AUXILIARY channel c2 device type disk;
allocate AUXILIARY channel c3 device type disk;
allocate AUXILIARY channel c4 device type disk;
set until scn 699575816;
duplicate target database to HFM11TMP;
release channel c1;
release channel c2;
release channel c3;
release channel c4;
}Error is as:
sql clone "alter system set db_unique_name =
''HFM11TMP'' comment=
''Modified by RMAN duplicate'' scope=spfile";
shutdown clone immediate;
startup clone force nomount
restore clone primary controlfile;
alter clone database mount;
executing Memory Script
executing command: SET until clause
sql statement: alter system set db_name = ''HFM11PRD'' comment= ''Modified by RMAN duplicate'' scope=spfile
sql statement: alter system set db_unique_name = ''HFM11TMP'' comment= ''Modified by RMAN duplicate'' scope=spfile
Oracle instance shut down
Oracle instance started
Total System Global Area 4275781632 bytes
Fixed Size 2213632 bytes
Variable Size 2298480896 bytes
Database Buffers 1962934272 bytes
Redo Buffers 12152832 bytes
allocated channel: c1
channel c1: SID=112 device type=DISK
Starting restore at 06-NOV-12
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 11/06/2012 15:13:32
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06024: no backup or copy of the control file found to restoreRMAN is searching for backup of controlfile in backup piece CF_L0_HFM11PRD_10112012_lhnpv62e_14001_1. But this has been already obsolete.
Now, if it not possible to get above backup piece back, then how to proceed with restore with backup piece DF_L0_HFM11PRD_10112012_l8npv5b6_13992_1 as it also has control file backup and available on disk, not obsolete. I can understand the reason for marking CF* file as obsolete because of redundency 1. But how to proceed with restore with available backup ?Hello;
I would change my configure for one :
RMAN>CONFIGURE CONTROLFILE AUTOBACKUP ON;Would use this to check :
list backup of controlfile completed before <date>And would catalog everything again just to be sure before starting the restore.
You may have to catalog use the control file piece to avoid the error.
RMAN> catalog backuppiece ...Another idea is to test the restore using something like this :
RMAN> run {
set until time "to_date('2012 NOV 17 07:00','YYYY MON DD HH24:MI')";
restore controlfile preview;
}Best Regards
mseberg
Edited by: mseberg on Nov 16, 2012 10:12 AM
Edited by: mseberg on Nov 16, 2012 11:13 AM -
I have a question about creating another control file. If I want to create another control file, do I need to put the values/paths of the current control files in the CREATE CONTROLFILE statement?
996403 wrote:
If I am wanting to create a new control file, do you recommend:
1. Use the Create Control file statementWhen to Create New Control Files:
All control files for the database have been permanently damaged/missing and you do not have a control file backup.
You want to change one of the permanent database parameter settings originally specified in the CREATE DATABASE statement.
These settings include the database name and the following parameters: MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, MAXDATAFILES, and MAXINSTANCES.
For example, you would change a database name if it conflicted with another database name in a distributed environment,
or you would change the value of MAXLOGFILES if the original setting is too low.
2. Copy an existing control file and then edit the parameter file?i will recommend 2nd (if you have healthy control file) if you want multiplex control files. -
Control File and SPFILE Autobackup command struck
O.S Version:
Linux Version "Red Hat Enterprise Linux Server release 6.2 (Santiago)
Linux version 2.6.32-220.13.1.el6.x86_64 ([email protected]) (gcc version 4.4.6 20110731 (Red Hat 4.4.6-3) (GCC) ) #1 SMP Thu Mar 29 11:46:40 EDT 2012
2.6.18-308.16.1.el5 x86_64
Tape Archiver : HP Data Protector
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
Problem :
In one of our environment, OEM grid 11g scheduled Level 0 backup struck at the Control File and SPFILE Autobackup.
RMAN Script:
run {
2> backup format '<%d_%s:%t:%p:%f>.df' incremental level 0 cumulative database;
3> sql 'alter system archive log current';
4> backup format '<%d_%s:%t:%p>.al' archivelog all not backed up;
5> }
RMAN Configuration
RMAN> show all;
RMAN configuration parameters for database with db_unique_name TestDB are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 45 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO 'TestDB_%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'TestDB_%F';
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 4 BACKUP TYPE TO BACKUPSET;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'SBT_LIBRARY=/opt/omni/lib/libob2oracle8_64bit.so,ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=TestDB,OB2BARLIST=Siv_ORA_TESTSrvr1_TestDB_DB,OB2BARHOSTNAME=TESTSrvr1)';
CONFIGURE MAXSETSIZE TO UNLIMITED;
CONFIGURE ENCRYPTION FOR DATABASE OFF;
CONFIGURE ENCRYPTION ALGORITHM 'AES128';
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+DG_TestDB_UAT_DATA_01/TestDB/TEMPFILE/snapcf_TestDB.f';
RMAN Log:
1. Backup started at 07-SEP-2013 07:09:46
Finished backup at 07-SEP-2013 07:16:38
Wherein the Control file backup started at 07-SEP-2013 07:16:38 failed at 09/07/2013 12:44:38. It kept struck for 5 Hours.
Starting backup at 07-SEP-2013 07:09:46
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: SID=250 instance=TestDB device type=SBT_TAPE
channel ORA_SBT_TAPE_1: Data Protector A.06.20/370
allocated channel: ORA_SBT_TAPE_2
Finished backup at 07-SEP-2013 07:16:38
Starting Control File and SPFILE Autobackup at 07-SEP-2013 07:16:38
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of Control File and SPFILE Autobackup command on ORA_SBT_TAPE_1 channel at 09/07/2013 12:44:38
ORA-19506: failed to create sequential file, name="TestDB_c-2078060264-20130907-ff", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
Vendor specific error: Cannot find requested element ERR(-2)
ORACLE error from recovery catalog database: ORA-03113: end-of-file on communication channel
Process ID: 2045
Session ID: 89 Serial number: 36509
RMAN> delete noprompt archivelog all backed up 1 times to sbt;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 09/07/2013 13:00:07
RMAN-06004: ORACLE error from recovery catalog database: ORA-03114: not connected to ORACLE
RMAN> **end-of-file**
Why does the RMAN Backup struck at Controlfile , SPFile autobackup?Hello;
I believe the issue is caused by your media management software. You should contact your media management vendor.
Try the same operation to disk and I bet it works.
Best Regards
mseberg
Maybe you are looking for
-
How can I transfer videos from my PC to my iPod touch (iOS 7.0.2)?
Hi, I'd like to know how I can transfer videos from my PC to my iPod touch (iOS 7.0.2)? Thank u for your help.
-
Is dv6-6135dx SATA III compatible​?
I upgraded my dv6-6135dx to a OCZ Agility 3 SSD, but am only getting SATA II speeds. I know the chipset supports SATA III, but did HP choose not to support it? Will there be a BIOS update to turn it on? This question was solved. View Solution.
-
Unnecessary payment orders generated in F110
Hi All, F110 is generating unnecessary payment orders for a particular Company Code for two of its vendors. This issue came up only for one company code in the system. I am wondering as unnecessay payment orders got generated for two vendors of a com
-
Dear Friends, I have experience in abap development for MM and SD module, now i need to do for HR module also, when i was looking into table its totally different all are in the form of clusters. I dont know how and when the data will be loaded in th
-
How to enable Auto-complete in web dynpro abap? just like in sap gui, client side every inputfield entered value gets stored, as and when we press back button in the inputfields it lists previously entered values list. Abhi