What data/control files to backup?
Dear All,
I can't perfom the proper backup - no room at the servers at the moment so I thought of making physical copies of datafiles and maybe control files. Though I'm not sure whether it's save or not and actually what files I have to take. Should I shutdown the database first hand?
If anyone did the same thing before please help)))
Thanks in advance
Marina
Hi,
Before planning the backup, Check for the following things.
1. Archiving mode of database(archive log or nonarchivelog).
2. How critical is the database.
If the database is in noarchivelog mode then you should shutdown the database first and then take the physical backup of All datafiles, control files and Parameter file.
If the database is in archivelog mode then you can simply take a online hot backup of the database. In the documentation you can get the method of taking hot backup.
Hope it helps.
Similar Messages
-
Hi Gurus,
Please explain me that what is Control file and what was the purpose of it in SAP Oracle DataBase.
Thanks.Hi Kalyan
<b>What Is a Control File?</b>
Every Oracle Database has a control file, which is a small binary file that records the physical structure of the database. The control file includes:
The database name
Names and locations of associated datafiles and redo log files
The timestamp of the database creation
The current log sequence number
Checkpoint information
The control file must be available for writing by the Oracle Database server whenever the database is open. Without the control file, the database cannot be mounted and recovery is difficult.
The control file of an Oracle Database is created at the same time as the database. By default, at least one copy of the control file is created during database creation. On some operating systems the default is to create multiple copies. You should create two or more copies of the control file during database creation. You can also create control files later, if you lose control files or want to change particular settings in the control files.
<b>Guidelines for Control Files</b>
This describes guidelines you can use to manage the control files for a database, and contains the following topics:
Provide Filenames for the Control Files
Multiplex Control Files on Different Disks
Back Up Control Files
Manage the Size of Control Files
Role of Control File will remain the same even when you use Oracle with SAP. Just there will be some more entries in the file.
Refer the link below as well:
http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14231/control.htm#i1006143
Hope this should clear you doubt.
Regards
Sumit Jain
[Reward with points if useful]
Message was edited by:
Sumit Jain -
Control File Auto Backup Alert Log
Hello-
Is there a parameter in the 11g database that needs to be configured to write to the alert log when the controlfile is auto-backed up ?
I have this configured but there are no entries in the alert logs for 11g databases.
I do have them in my 10g alert logs.
Thanks-No there is no such parameter.
It seems that Oracle 11g does not write anything to alert log when control file is auto backed up but instead writes to a trace file in diagnostic_dest directory tree:
Trace file /u01/app/oracle/diag/rdbms/db112/DB112/trace/DB112_ora_5837.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /u01/app/oracle/product/11.2.0/EE
System name: Linux
Node name: lx01.localdomain
Release: 2.6.18-92.el5
Version: #1 SMP Fri May 23 22:17:30 EDT 2008
Machine: i686
Instance name: DB112
Redo thread mounted by this instance: 1
Oracle process number: 29
Unix process pid: 5837, image: [email protected] (TNS V1-V3)
*** 2011-04-18 19:21:39.223
*** SESSION ID:(17.34) 2011-04-18 19:21:39.223
*** CLIENT ID:() 2011-04-18 19:21:39.223
*** SERVICE NAME:(SYS$USERS) 2011-04-18 19:21:39.223
*** MODULE NAME:(backup full datafile) 2011-04-18 19:21:39.223
*** ACTION NAME:(0000023 STARTED111) 2011-04-18 19:21:39.223
Starting control autobackup
*** 2011-04-18 19:21:40.050
Control autobackup written to DISK device
handle '/tmp/c-732354255-20110418-011'Edited by: P. Forstmann on 18 avr. 2011 19:25 -
How to recover datafile.when control file auto backup is off
hi friend
i took hot backup of my database using following command
rman>backup database;
in my case controlfile auto backup is off.
and i have lost my all controlfiles as well as datafiles except spfile.
i have recovered control file using dbms_backup_restore package.
know i am able to mount database using following command
rman> startup mount;
when i wrote following command
rman> restore database;
i got following error
RMAN-06023: no backup or copy of datafile name found to restore
enven i have backup of datbase.
can anybody tell me how to recover datafiles in this case.
thanking you
sohailhi,
I think you might have a problem here as the error from RMAN is described in the following metalink note
Doc ID: Note:100565.1
You should change you backup script to be something like
rman {
backup database include current controlfile;
do you have any earlier backups of your database?
regards
Alan -
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 -
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 -
Hi,
I am interested in time of snapshot control file creation.
I have read that snapshot control file is created before the backup take the place. I have tried to take the simple rman>backup database command, but I have seen that snapshot control file is created after all backup process (I have seen the time of creating the snapshot control file).
Can anybody tell me about this? When the snapshot control file is created (before backup, maybe in the memory, because I can't see it on the file system).
Regards,
DraganHi,
I have read this sentence from Oracle Database 10g RMAN Backup & Recovery:
RMAN needs to get a consistent view of the control file when it sets out to make backup of every datafile. It only needs to know the most recent checkpoint information and file schematic information at the time backup begins. After the backup starts, RMAN needs this information to stay consistent for duration of the backup operation; in other words, it needs a read consistent view of the control file. With the constant updates from the database, this is nearly impossible - unless RMAN were to lock the control file for the duration of the backup. But that would mean the database could not advance checkpoint or switch logs or produce new archive logs. Impossible.
To get around this, RMAN uses the snapshot control file, an exact copy of your control file that is only used by RMAN during backup and resync operations. At the beginning of these operations, RMAN refreshes the snapshot control file from the actual control file, thus putting a momentary lock on the control file. Then, RMAN switches to the snapshot and uses it for the duration of the backup; in this way, it has read consistency without holding up database activity.
I must ask you if I am using control file only (not recovery catalog) what is happening when I am executing simple RMAN command> backup database;
You have said that I don't create snapshot of control file at that moment, only at the end of the backup process (I have also try it in my environment and snapshot is created at the end of the backup process).
How RMAN knows what to backup (which files), he takes this information from original control file (not from snapshot) I suppose.
What is happening when he finished backup of some backup set, he writes that information again in original control file I suppose.
And at the end of all process why he takes snapshot of control file (to backup control file from it, not from original control file, because control file is always changing, need to lock it). In that snapshot control file (and in the its backup) we will have the pointers on files that are made after the backup process started (is this true).
Thanks,
Regards
Dragan -
Upgraded to 10.2.0.2.0, but problem with 'identifying control file'
I just applied the metalink patch to upgrade from 10.2.0.1.0 to 10.2.0.2.0 in order to install the SOA Suite. It was a clean install for 10.2.0.1.0, followed by applying the patch. I am now trying to run the new database, but I get an error:
ORA-00205: error in identifying controle file, check alert log for more info.
I edited by init.ora file, and the two control files are there as (ora_control1, ora_control2).
Any help would be greatly appreciated.
Kind regards,
AnthonyWe had a similar issue and had to fix it by copying all the data files and control files to backup then ...
1) run database creation assistant to delete the database
2) using database creation assistant, create a new database with the same name
3) shut down the new database
4) leaving the new spfile in place, copy all the backups back over including controlfiles.
5) startup the database.
Don't know if it will help in your situation or not, but worth a try if someone else has the same type of problem. -
Howdy:
I'm running Oracle 9i (9.0.2) on Redhat Linux 7.3.
I am trying to append data from a flat file into a
table where one of the field is timestamp(6).
The data has fractional seconds and looks like so:
[snip data]
2002-12-08 22:29:38.216712
[snip data]
I want to use sqlldr to load the data, but when
I try to create the control file, I am getting
errors telling me my method is wrong.
In my control file, I am trying to do things like:
[snip versions of the 'UPDATED' timestamp field]
* UPDATED TIMESTAMP "YYYY-MM-DD HH24:MI:SS"
* UPDATED TIMESTAMP "YYYY-MM-DD HH24:MI:SS.FFF"
* UPDATED POSITION(132:151)"TO_DATE(:UPDATED, 'YYYY-MM-DD HH24:MI:SS')"
[snip versions ...]
I am having no success.
Can someone give an example of how to create
a control file for sqlldr when defining a
timestamp field with fractional seconds six
digits past the decimal?
Thanks!
-X--update:
--this is pretty much for my notes (as i'm
--sure i will need this info again).
--i have figured out how to fix my problem.
--re-cap:
--so, i'm running Oracle 9i (9.2.0) on Redhat Linux 7.2 as
--you know. I want to append my data from a flat file
--into a table that i've created. i also want to use SQLLDR
--to do it. i have create a bunch of scripts to do this
--and i was close - the problem was that in one of the
--fields (table) was a TIMESTAMP field and i couldn't
--figure out how to create a control file to say 'hey, there
--is a timestamp field in there and it has fractions in
--the seconds area ... 6 decimal places over'.
--so, this is what my table looks like:
[snip table]
SQL> describe hmp_dates
Name Null? Type
CONTRACT CHAR(12)
MBR_NUM CHAR(2)
DATE DATE
EVENT_ID NUMBER(38)
VALUE VARCHAR2(50)
RESULT VARCHAR2(50)
UPDATED TIMESTAMP(6) WITH TIME ZONE
USERNAME VARCHAR2(50)
CLAIM VARCHAR2(50)
[snip table]
--this is what my data looks like:
[snip data]
xxxxxxxxx |02|2000-05-31|38|\N|\N|2002-12-08 22:29:38.216712|ADMIN|\N
xxxxxxxxx | |1999-06-06|38|\N|\N|2002-12-08 22:29:38.216712|ADMIN|\N
xxxxxxxxx | |1998-12-28|38|\N|\N|2002-12-08 22:29:38.216712|ADMIN|\N
xxxxxxxxx | |1999-12-03|38|\N|\N|2002-12-08 22:29:38.216712|ADMIN|\N
[snip data]
--this is what my control file looks like:
[snip control]
LOAD DATA
INFILE '/var/local/table_backup/hmp_dates_03July2003.txt'
APPEND
INTO TABLE HMP_DATES
FIELDS TERMINATED BY '|' OPTIONALLY ENCLOSED BY '"'
CONTRACT,
MBR_NUM,
"DATE" DATE "YYYY-MM-DD",
EVENT_ID,
VALUE,
RESULT,
UPDATED TIMESTAMP WITH TIME ZONE 'YYYY-MM-DD HH24:MI:SSXFF', *****
USERNAME,
CLAIM
[snip control]
--please note the astrisks. that is the elfin goodness. (SSXFF to denote precision
--seconds).
--hopes this helps someone besides me.
-X -
i got a backset but rman is not restoring the control file from backup set
So what error you are getting??
How you are restoring??
What type of backup do you have??
Do you have controlfile autobackup??
Can you see the backups using RMAN??
Daljit Singh -
SQL*LOADER control file for Multiple Tables
Dear DBA's
I am loading data throgh SQL*LOADER in Oracle. I have some problem, While
Inserting data into multiple table I have created single Control file in
following way which is giving me error, Data is stored in seprate fileswith
tablename.dat, So each tables data is stored in seprate .DAT file. So Iwant to
insert data from single control file taking data from .dat multiple files into
multiple tables. Is it possible?? or some different method
Please help me as early as possiable.
Thanks & Regards
Shailesh
CREATE TABLE T1 (
L1 VARCHAR2(10),
L2 NUMBER(10),
L4 NUMBER(10),
MYDATE DATE);
CREATE TABLE T2 (
L1 VARCHAR2(10),
L2 NUMBER(10),
L3 LONG,
L4 NUMBER(10),
MYDATE DATE)
CONTROL FILE :-
UNRECOVERABLE LOAD DATA
INFILE 't2.dat'
INSERT INTO TABLE t2
FIELDS TERMINATED BY ','
OPTIONALLY ENCLOSED BY '"'
TRAILING NULLCOLS
( l1 char,l2 char,l4 char,mydate date,l3 char(2000000))
INFILE 't1.dat'
INSERT INTO TABLE t1
FIELDS TERMINATED BY ','
OPTIONALLYENCLOSED BY '"'
TRAILING NULLCOLS
( f1 char,f2 char,f4 char))
T2.DAT
Raju,14,1,09-NOV-2000,"Has a powerful data parsing,engine which putslittle
limitation on the format of the data in thedatafile."
Manu,14,2,09-NOV-2000,"Can load data from multiple datafiles, during the same
load session. "
T1.DAT
Raj,14,1,09-NOV-2000
Mau,14,2,09-NOV-2000
nullHi,
I tried to use your control file and got numerous erros.
try using seperate control files:
T1.CTL:
LOAD DATA
INFILE 'D:\T2.dat'
INSERT INTO TABLE t2
( l1 char,l2 char,l4 char,mydate date,l3 char(20000))
T2.CTL
LOAD DATA
INFILE 'D:\T1.dat'
INSERT INTO TABLE t1
( l1 char,l2 char,l4 char,mydate date) -
Mv control files, redo.log, database fies
Hello,
I installed Oracle 10.2. on Unix.
we have created file systems for our data/control files.
some how we missed that part to define location for dbf, control & redo.log files during installation.
My question is how to mv all control files, redo.log and dbf files to one location to another.
for. eg:
currently there are installed in /opt/oracle/oradata.
now i want o move in /u03/oradata.
Please note:
Prior to that I'd like to put in archive log mode.
shutdown immediate;
startup mount;
alter database archivelog;
alter database open;
DNFor DB and Redo files
conn / as sysdba
shutdown immediate;
startup mount
host
$ cp old_name new_name
$ exit
alter database rename file old_name
to new_name;
alter database open
host
$ rm old_name
$ exitFor control files
1. Shut down the database.
2. Copy an existing control file to a different locations, using operating system commands.
3. Edit the CONTROL_FILES parameter in the database's initialization parameter file to add the new control file's name, or to change the existing control filename.
4. start the database.
Message was edited by:
tekicora -
What is the difference between data file & control file
what is the difference between data file & control file
Dear Deba s
Control file
Every Oracle Database has a control file, which is a small binary file that records the physical structure of the database. The control file includes:
The database name
Names and locations of associated datafiles and redo log files
The timestamp of the database creation
The current log sequence number
Checkpoint information
For more info look into these
[Control File Basic|http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14231/control.htm#i1006143]
Data File
You manage Data File in your Oracle database as part of Space Management. You can extend, create, drop, and alter tablespaces.
You especially need to avoid tablespace overflow, which is when a tablespace runs out of freespace in the allocated file or files. This happens when an object requires a new extent but there is either no freespace or insufficient freespace in the tablespace
For more info look into these links
[Data files |http://help.sap.com/saphelp_nw04/helpdata/en/98/5dd5890f32274aa884e45e736752a2/frameset.htm]
http://help.sap.com/saphelp_nw04/helpdata/en/98/5dd5890f32274aa884e45e736752a2/frameset.htm
Hope it helps you,Revert me back if you have any queries
Assign points if helpful
Regards
Bala -
Control file lost and datafile addeed restore/recovery with no data loss
Here i have tried to the following
created new table called t2 and made sure data went to a specific tablespace...
took a level 0 backup
removed the control file
added couple of datafile to above tablespace and then inserted more data
then went out to restore control file and the database...but datafile still could not be opened ?? what did i do wrong here....
SQL> @datafile
-- list of datafile
Tablespace File Typ Tablespac File Stat Used MB Free MB FILE_MB MAXMB Datafile_name FILE_ID AUT
UNDOTBS1 Datafile ONLINE AVAILABLE 16 84 100 1,024 /data/trgt/undotbs01.dbf 3 YES
USERS Datafile ONLINE AVAILABLE 1153 895 2048 3,072 /data3/trgt/user02.dbf 5 YES
CNT_TST Datafile ONLINE AVAILABLE 1 9 10 0 /data3/trgt/cnt_tst01.dbf 7 NO
SYSAUX Datafile ONLINE AVAILABLE 626 35 660 32,768 /data/trgt/sysaux01.dbf 2 YES
USERS Datafile ONLINE AVAILABLE 2031 17 2048 2,048 /data3/trgt/move/users01.dbf 4 YES
SYSTEM Datafile ONLINE AVAILABLE 712 58 770 32,768 /data/trgt/system01.dbf 1 YES
USERS Datafile ONLINE AVAILABLE 65 35 100 32,768 /data3/trgt/users03.dbf 6 YES
7 rows selected.
-- new table is created called t2 and its going into TS called cnt_tst
SQL> CREATE TABLE TEST.T2
C1 DATE,
C2 NUMBER,
C3 NUMBER,
C4 VARCHAR2(300 BYTE)
TABLESPACE cnt_tst; 2 3 4 5 6 7 8
Table created.
-- data inserted
SQL> INSERT INTO
test.T2
SELECT
FROM
(SELECT
SYSDATE,
ROWNUM C2,
DECODE(MOD(ROWNUM,100),99,99,1) C3,
RPAD('A',300,'A') C4
FROM
DUAL
CONNECT BY
LEVEL <= 10000)
; 2 3 4 5 6 7 8 9 10 11 12 13 14 15
10000 rows created.
SQL> commit;
Commit complete.
-- to check of cnt_tst has any free space or not, as we can see its full
SQL> @datafile
Tablespace File Typ Tablespac File Stat Used MB Free MB FILE_MB MAXMB Datafile_name FILE_ID AUT
UNDOTBS1 Datafile ONLINE AVAILABLE 16 84 100 1,024 /data/trgt/undotbs01.dbf 3 YES
USERS Datafile ONLINE AVAILABLE 1153 895 2048 3,072 /data3/trgt/user02.dbf 5 YES
SYSAUX Datafile ONLINE AVAILABLE 626 35 660 32,768 /data/trgt/sysaux01.dbf 2 YES
USERS Datafile ONLINE AVAILABLE 2031 17 2048 2,048 /data3/trgt/move/users01.dbf 4 YES
SYSTEM Datafile ONLINE AVAILABLE 712 58 770 32,768 /data/trgt/system01.dbf 1 YES
USERS Datafile ONLINE AVAILABLE 65 35 100 32,768 /data3/trgt/users03.dbf 6 YES
CNT_TST Datafile ONLINE AVAILABLE 10 0 10 0 /data3/trgt/cnt_tst01.dbf 7 NO
7 rows selected.
SQL> select count(*) from test.t2;
COUNT(*)
10000
1 row selected.
-- to get a count and max on date
SQL> select max(c1) from test.t2;
MAX(C1)
29-feb-12 13:47:52
1 row selected.
SQL> -- AT THIS POINT A LEVEL 0 BACKUP IS TAKEN (using backup database plus archivelog)
SQL> -- now control files are removed
SQL> select name from v$controlfile;
NAME
/ctrl/trgt/control01.ctl
/ctrl/trgt/control02.ctl
2 rows selected.
SQL>
SQL> ! rm /ctrl/trgt/control01.ctl
SQL> ! rm /ctrl/trgt/control02.ctl
SQL> ! ls -ltr /ctrl/trgt/
ls: /ctrl/trgt/: No such file or directory
SQL>
-- new datafile is added to CNT_TST TABLESPACE and new data is added as well
SQL> ALTER TABLESPACE CNT_TST ADD DATAFILE '/data3/trgt/CNT_TST02.dbf' SIZE 100M AUTOEXTEND OFF;
Tablespace altered.
SQL> ALTER SYSTEM CHECKPOINT;
System altered.
SQL> alter system switch logfile;
System altered.
SQL> /
System altered.
SQL> /
System altered.
SQL> ALTER TABLESPACE CNT_TST ADD DATAFILE '/data3/trgt/CNT_TST03.dbf' SIZE 100M AUTOEXTEND OFF;
Tablespace altered.
SQL> INSERT INTO
test.T2
SELECT
FROM
(SELECT
SYSDATE,
ROWNUM C2,
DECODE(MOD(ROWNUM,100),99,99,1) C3,
RPAD('A',300,'A') C4
FROM
DUAL
CONNECT BY
LEVEL <= 10000)
; 2 3 4 5 6 7 8 9 10 11 12 13 14 15
10000 rows created.
SQL> /
10000 rows created.
SQL> commit;
Commit complete.
SQL> INSERT INTO
test.T2
SELECT
FROM
(SELECT
SYSDATE,
ROWNUM C2,
DECODE(MOD(ROWNUM,100),99,99,1) C3,
RPAD('A',300,'A') C4
FROM
DUAL
CONNECT BY
LEVEL <= 40000)
; 2 3 4 5 6 7 8 9 10 11 12 13 14 15
40000 rows created.
SQL> commit;
Commit complete.
SQL> @datafile
-- to make sure new datafile has been registered with the DB
Tablespace File Typ Tablespac File Stat Used MB Free MB FILE_MB MAXMB Datafile_name FILE_ID AUT
CNT_TST Datafile ONLINE AVAILABLE 9 91 100 0 /data3/trgt/CNT_TST03.dbf 9 NO
UNDOTBS1 Datafile ONLINE AVAILABLE 16 84 100 1,024 /data/trgt/undotbs01.dbf 3 YES
USERS Datafile ONLINE AVAILABLE 1153 895 2048 3,072 /data3/trgt/user02.dbf 5 YES
CNT_TST Datafile ONLINE AVAILABLE 9 91 100 0 /data3/trgt/CNT_TST02.dbf 8 NO
SYSAUX Datafile ONLINE AVAILABLE 626 35 660 32,768 /data/trgt/sysaux01.dbf 2 YES
USERS Datafile ONLINE AVAILABLE 2031 17 2048 2,048 /data3/trgt/move/users01.dbf 4 YES
SYSTEM Datafile ONLINE AVAILABLE 712 58 770 32,768 /data/trgt/system01.dbf 1 YES
USERS Datafile ONLINE AVAILABLE 65 35 100 32,768 /data3/trgt/users03.dbf 6 YES
CNT_TST Datafile ONLINE AVAILABLE 10 0 10 0 /data3/trgt/cnt_tst01.dbf 7 NO
9 rows selected.
-- now the count and max ... note count before backup was 10000 and max(c1) was diff
SQL> select count(*) from test.t2;
COUNT(*)
70000
1 row selected.
SQL> select max(c1) from test.t2;
MAX(C1)
29-feb-12 13:58:25
1 row selected.
SQL> -- now restore starts
SQL> shutdown abort;
ORACLE instance shut down.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@berry trgt]$ rman
Recovery Manager: Release 11.2.0.1.0 - Production on Wed Feb 29 14:01:48 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
RMAN> connect catalog rman/pass@rcat
connected to recovery catalog database
RMAN> connect target /
connected to target database (not started)
RMAN> startup nomount;
Oracle instance started
Total System Global Area 188313600 bytes
Fixed Size 1335388 bytes
Variable Size 125833124 bytes
Database Buffers 58720256 bytes
Redo Buffers 2424832 bytes
RMAN> restore controlfile from autobackup;
Starting restore at 29-FEB-12 14:02:37
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=20 device type=DISK
recovery area destination: /backup/trgt/flash_recovery_area
database name (or database unique name) used for search: TRGT
channel ORA_DISK_1: no AUTOBACKUPS found in the recovery area
channel ORA_DISK_1: looking for AUTOBACKUP on day: 20120229
channel ORA_DISK_1: AUTOBACKUP found: /backup/trgt/backup/cont_c-3405317011-20120229-09
channel ORA_DISK_1: restoring control file from AUTOBACKUP /backup/trgt/backup/cont_c-3405317011-20120229-09
channel ORA_DISK_1: control file restore from AUTOBACKUP complete
output file name=/ctrl/trgt/control01.ctl
output file name=/ctrl/trgt/control02.ctl
Finished restore at 29-FEB-12 14:02:39
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN> recover database;
Starting recover at 29-FEB-12 14:02:55
Starting implicit crosscheck backup at 29-FEB-12 14:02:55
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=20 device type=DISK
Crosschecked 96 objects
Finished implicit crosscheck backup at 29-FEB-12 14:02:57
Starting implicit crosscheck copy at 29-FEB-12 14:02:57
using channel ORA_DISK_1
Finished implicit crosscheck copy at 29-FEB-12 14:02:57
searching for all files in the recovery area
cataloging files...
no files cataloged
using channel ORA_DISK_1
starting media recovery
archived log for thread 1 with sequence 13 is already on disk as file /redo_archive/trgt/online/redo01.log
archived log for thread 1 with sequence 14 is already on disk as file /redo_archive/trgt/online/redo02.log
archived log for thread 1 with sequence 15 is already on disk as file /redo_archive/trgt/online/redo03.log
archived log file name=/redo_archive/trgt/archive/1_10_776523284.dbf thread=1 sequence=10
archived log file name=/redo_archive/trgt/archive/1_10_776523284.dbf thread=1 sequence=10
archived log file name=/redo_archive/trgt/archive/1_11_776523284.dbf thread=1 sequence=11
archived log file name=/redo_archive/trgt/archive/1_12_776523284.dbf thread=1 sequence=12
archived log file name=/redo_archive/trgt/online/redo01.log thread=1 sequence=13
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 02/29/2012 14:02:59
ORA-01422: exact fetch returns more than requested number of rows
RMAN-20505: create datafile during recovery
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/redo_archive/trgt/online/redo01.log'
ORA-00283: recovery session canceled due to errors
ORA-01244: unnamed datafile(s) added to control file by media recovery
ORA-01110: data file 9: '/data3/trgt/CNT_TST03.dbf'
RMAN> -- wnet to session 2 and renamed datafile from unammed-- wnet to session 2 and renamed datafile for unammed file
SQL> select name from v$datafile;
NAME
/data/trgt/system01.dbf
/data/trgt/sysaux01.dbf
/data/trgt/undotbs01.dbf
/data3/trgt/move/users01.dbf
/data3/trgt/user02.dbf
/data3/trgt/users03.dbf
/data3/trgt/cnt_tst01.dbf
/oracle/app/product/11.2.0/dbhome_1/dbs/UNNAMED00008
/oracle/app/product/11.2.0/dbhome_1/dbs/UNNAMED00009
9 rows selected.
SQL> alter database create datafile '/oracle/app/product/11.2.0/dbhome_1/dbs/UNNAMED00008' as '/data3/trgt/CNT_TST02.dbf';
Database altered.
SQL> alter database create datafile '/oracle/app/product/11.2.0/dbhome_1/dbs/UNNAMED00009' as '/data3/trgt/CNT_TST03.dbf';
Database altered.
SQL> select name from v$datafile;
NAME
/data/trgt/system01.dbf
/data/trgt/sysaux01.dbf
/data/trgt/undotbs01.dbf
/data3/trgt/move/users01.dbf
/data3/trgt/user02.dbf
/data3/trgt/users03.dbf
/data3/trgt/cnt_tst01.dbf
/data3/trgt/CNT_TST02.dbf
/data3/trgt/CNT_TST03.dbf
9 rows selected.after above was done, went back to session 1 and tried recovered the DB
RMAN> recover database;
Starting recover at 29-FEB-12 14:06:16
using channel ORA_DISK_1
starting media recovery
archived log for thread 1 with sequence 13 is already on disk as file /redo_archive/trgt/online/redo01.log
archived log for thread 1 with sequence 14 is already on disk as file /redo_archive/trgt/online/redo02.log
archived log for thread 1 with sequence 15 is already on disk as file /redo_archive/trgt/online/redo03.log
archived log file name=/redo_archive/trgt/online/redo01.log thread=1 sequence=13
archived log file name=/redo_archive/trgt/online/redo02.log thread=1 sequence=14
archived log file name=/redo_archive/trgt/online/redo03.log thread=1 sequence=15
media recovery complete, elapsed time: 00:00:00
Finished recover at 29-FEB-12 14:06:17
RMAN> alter database open resetlogs;
database opened
new incarnation of database registered in recovery catalog
starting full resync of recovery catalog
full resync complete
starting full resync of recovery catalog
full resync complete
RMAN> exit
Recovery Manager complete.
[oracle@berry trgt]$
[oracle@berry trgt]$
[oracle@berry trgt]$ sq
SQL*Plus: Release 11.2.0.1.0 Production on Wed Feb 29 14:07:18 2012
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> alter session set NLS_DATE_FORMAT="dd-mon-yy hh24:mi:ss:
2
SQL>
SQL> alter session set NLS_DATE_FORMAT="dd-mon-yy hh24:mi:ss";
Session altered.
SQL> select count(*) from test.t2;
select count(*) from test.t2
ERROR at line 1:
ORA-00376: file 8 cannot be read at this time
ORA-01110: data file 8: '/data3/trgt/CNT_TST02.dbf'
SQL> select max(c1) from test.t2;
select max(c1) from test.t2
ERROR at line 1:
ORA-00376: file 8 cannot be read at this time
ORA-01110: data file 8: '/data3/trgt/CNT_TST02.dbf'
SQL> alter database datafile 8 online;
alter database datafile 8 online
ERROR at line 1:
ORA-01190: control file or data file 8 is from before the last RESETLOGS
ORA-01110: data file 8: '/data3/trgt/CNT_TST02.dbf'
{code}
so what did i do wrong in my recovery that i could not get my data?? how can i avoid this?? and restore my DB?
Edited by: user8363520 on Feb 29, 2012 12:24 PMuser8363520 wrote:
Here i have tried to the following
created new table called t2 and made sure data went to a specific tablespace...
took a level 0 backup
removed the control file
added couple of datafile to above tablespace and then inserted more data
then went out to restore control file and the database...but datafile still could not be opened ?? what did i do wrong here....
SQL> @datafile
-- list of datafile
Tablespace File Typ Tablespac File Stat Used MB Free MB FILE_MB MAXMB Datafile_name FILE_ID AUT
UNDOTBS1 Datafile ONLINE AVAILABLE 16 84 100 1,024 /data/trgt/undotbs01.dbf ; 3 YES
USERS Datafile ONLINE AVAILABLE 1153 895 2048 3,072 /data3/trgt/user02.dbf ; 5 YES
CNT_TST Datafile ONLINE AVAILABLE 1 9 10 0 /data3/trgt/cnt_tst01.dbf ; 7 NO
SYSAUX Datafile ONLINE AVAILABLE 626 35 660 32,768 /data/trgt/sysaux01.dbf ; 2 YES
USERS Datafile ONLINE AVAILABLE 2031 17 2048 2,048 /data3/trgt/move/users01.dbf ; 4 YES
SYSTEM Datafile ONLINE AVAILABLE 712 58 770 32,768 /data/trgt/system01.dbf ; 1 YES
USERS Datafile ONLINE AVAILABLE 65 35 100 32,768 /data3/trgt/users03.dbf ; 6 YES
7 rows selected.
-- new table is created called t2 and its going into TS called cnt_tst
SQL> CREATE TABLE TEST.T2
C1 DATE,
C2 NUMBER,
C3 NUMBER,
C4 VARCHAR2(300 BYTE)
TABLESPACE cnt_tst; 2 3 4 5 6 7 8
Table created.
-- data inserted
SQL> INSERT INTO
test.T2
SELECT
FROM
(SELECT
SYSDATE,
ROWNUM C2,
DECODE(MOD(ROWNUM,100),99,99,1) C3,
RPAD('A',300,'A') C4
FROM
DUAL
CONNECT BY
LEVEL <= 10000)
; 2 3 4 5 6 7 8 9 10 11 12 13 14 15
10000 rows created.
SQL> commit;
Commit complete.
-- to check of cnt_tst has any free space or not, as we can see its full
SQL> @datafile
Tablespace File Typ Tablespac File Stat Used MB Free MB FILE_MB MAXMB Datafile_name FILE_ID AUT
UNDOTBS1 Datafile ONLINE AVAILABLE 16 84 100 1,024 /data/trgt/undotbs01.dbf ; 3 YES
USERS Datafile ONLINE AVAILABLE 1153 895 2048 3,072 /data3/trgt/user02.dbf ; 5 YES
SYSAUX Datafile ONLINE AVAILABLE 626 35 660 32,768 /data/trgt/sysaux01.dbf ; 2 YES
USERS Datafile ONLINE AVAILABLE 2031 17 2048 2,048 /data3/trgt/move/users01.dbf ; 4 YES
SYSTEM Datafile ONLINE AVAILABLE 712 58 770 32,768 /data/trgt/system01.dbf ; 1 YES
USERS Datafile ONLINE AVAILABLE 65 35 100 32,768 /data3/trgt/users03.dbf ; 6 YES
CNT_TST Datafile ONLINE AVAILABLE 10 0 10 0 /data3/trgt/cnt_tst01.dbf ; 7 NO
7 rows selected.
SQL> select count(*) from test.t2;
COUNT(*)
10000
1 row selected.
-- to get a count and max on date
SQL> select max(c1) from test.t2;
MAX(C1)
29-feb-12 13:47:52
1 row selected.
SQL> -- AT THIS POINT A LEVEL 0 BACKUP IS TAKEN (using backup database plus archivelog)
SQL> -- now control files are removed
SQL> select name from v$controlfile;
NAME
/ctrl/trgt/control01.ctl
/ctrl/trgt/control02.ctl
2 rows selected.
SQL>
SQL> ! rm /ctrl/trgt/control01.ctl
SQL> ! rm /ctrl/trgt/control02.ctl
SQL> ! ls -ltr /ctrl/trgt/
ls: /ctrl/trgt/: No such file or directory
SQL>
-- new datafile is added to CNT_TST TABLESPACE and new data is added as well
SQL> ALTER TABLESPACE CNT_TST ADD DATAFILE '/data3/trgt/CNT_TST02.dbf' SIZE 100M AUTOEXTEND OFF;
Tablespace altered.
SQL> ALTER SYSTEM CHECKPOINT;
System altered. Upto this i was clear, but now i cann't understand when you actually dropped the control file from you database(in running stat) how can you perform "alter system checkpoint" and other "alter tablespace.." command? Once controlfile is inaccessible, oracle database is not suppose to function. -
How to create parameter and control file like filename + date
Hello there
I am trying to create parameter and control file with following command
in SQLPLUS
create pfile='/u03/oradata/WEBDB/backup/initWEBDB.ora' from spfile;
In RMAN
copy current controlfile to '/u03/oradata/WEBDB/backup/cf_longterm.cpy';
how can I put date at the end of filename like
initWEBDB8jan06.ora and cf_longterm8jan06.cpy
Thanks in advance
LionelASM is reliable but a smart DBA is very careful. If ASM is doing mirroring this is like RAID doing mirroring. What happens if you accidentally delete one copy ... the other one disappears instantly. Not a good idea.
With respect to redo logs you need a minimum of three groups, two members, and one thread per instance. So a 2 node cluster should, at a minimum have 12 physical files.
Not mirroring the redo logs, assuming multiple members, is not as critical.
Maybe you are looking for
-
SYSTEM CHECK FOR CREATION OF EXCISE INVOICE WITHOUT PGI
Hi SAP guru's i need help in this issue++ See i am creating delivery and i did'nt do PGI ,after this i am creating Proforma invoice (here Proforma is must before creating commercial Invoice),with reference to Proforma system is accepting to create Ex
-
Different tint between Cinema Display/PC montior and TV?
Hello! I purchased a Samsung LED TV for monitoring FC Studio trough a AJA Hi5 HDMI miniconverter. I can't afford a Hires SDI HD Pro monitor (3.000 euro or more). Image on the TV looks bluish than on the Apple Cinema Display or another PC monitor. But
-
Recording through line in on a v p
hi Alli have just bought the above and i am really pleased with it but i have one question, as i am a certain age i purchased the above so it would be easy to put some of my record collection onto my v plus ( via the line in) i was wondering if anyon
-
Hello Our Client has a peculiar requirement of closing To extract Account Balances Profit Centrewise example Profit Centres P1 P2 P3 Expenses in Profit & Loss
-
FBL1N & FBL5N shows amounts in thousands
Hi experts FBL1N & FBL5N shows amounts in thousands 14,50080 $ instead of a normal display 14 500,80 $ Can anyone help to resolve this problem. Thanks