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;
DN

For 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

Similar Messages

Only a cold datafile backup. No control files, redo files, archived redo

Hi everyone,
I made a stupid mistake and am in a bad condition with only a cold database backup without control files, redo files and archived redo files. My oracle database is oracle 9i. Is there any way to get my data back?
Thanks,
Yanping

Hi,
Have you a backup trace of a Control File ??
You can try perform this:
eg:
oracle@linux:/u01> cp -a /backup/*.dbf /u01/oradata/DB01
oracle@linux:~> sqlplus
SQL*Plus: Release 9.2.0.4.0 - Production on Mon Sep 18 21:35:04 2006
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Enter user-name: / as sysdba
Connected to an idle instance.
SQL> startup nomount
ORACLE instance started.
Total System Global Area   93394180 bytes
Fixed Size                   451844 bytes
Variable Size              67108864 bytes
Database Buffers           25165824 bytes
Redo Buffers                 667648 bytes
SQL>CREATE CONTROLFILE REUSE DATABASE "DB01" RESETLOGS ARCHIVELOG
    MAXLOGFILES 3
    MAXLOGMEMBERS 2
    MAXDATAFILES 10
    MAXINSTANCES 1
    MAXLOGHISTORY 226
LOGFILE
GROUP 1 '/u01/oradata/DB01/redo01.log' SIZE 500K,
GROUP 2 '/u01/oradata/DB01/redo02.log' SIZE 500K,
GROUP 3 '/u01/oradata/DB01/redo03.log' SIZE 500K
DATAFILE
'/u01/oradata/DB01/system01.dbf',
'/u01/oradata/DB01/undotbs01.dbf',
'/u01/oradata/DB01/indx01.dbf',
'/u01/oradata/DB01/tools01.dbf',
'/u01/oradata/DB01/users01.dbf'
CHARACTER SET WE8ISO8859P1;
Control file created.
SQL> alter database open resetlogs;
Database altered.
SQL> ALTER TABLESPACE TEMP ADD TEMPFILE '/u01/oradata/BDRPS/temp01.dbf' SIZE 5242880 REUSE AUTOEXTEND OFF;
Tablespace altered.
SQL> select * from v$controlfile;
STATUS NAME
        /u01/oradata/DB01/control01.ctl
        /u01/oradata/DB01/control02.ctl
        /u01/oradata/DB01/control03.ctl
SQL> select * from v$logfile;
    GROUP# STATUS TYPE    MEMBER
         3         ONLINE /u01/oradata/DB01/redo03.log
         2         ONLINE /u01/oradata/DB01/redo02.log
         1         ONLINE /u01/oradata/DB01/redo01.logCheers
Message was edited by:
Legatti

RECREATE DATABASE Using CONTROL File After SUSPEND Database

Hello All,
Does someone can tell me if he does achieve recreating a database using "Backup Control File" after putting database in "suspend" mode?
The procedure looks like this :
1 - Alter DATABASE Suspend
2 - A Snapshot of the filesystem where the oracle datafile are located
3 - Copy of those files to another file systeme
4 - Startup setting a new database name
Does someone as do it successfully ?
Thanks for your answer

Carlos,
I tried to do it without putting the tablespaces in backup mode and it didn't work for me. At that time adding the backup mode wasn't a big deal for me, so I didn't investigate the problem thoroughly.
Logically thinking you sould be able to do:
1. suspend database
the SCNs recored in datafiles headers could be incosistent at this point
2. make a snapshot
3. mount the backup database
4. run recover until cancel using backup controlfile - I don't think you can avoid this step in case if you have inconsistent SCNs in the datafiles headers - you'll need to synchronize them
5. open resetlogs.
the suspend database should eliminate the possibility of inconsistent data within a block during the backup.
Just out of curiosity - why don't you want to put the tablespace in the backup mode?
Mike

Recover from missing files(redo log file/control file) and state of the DB

Hello,
i hv go through the doc. as well. But have some doubts what will happen in each on these situations.
Pls help me to clarify these!
Scenario is like this;
hv 3 redo log files - multiplxed
hv 3 control files - multiplxed
- What will happen if 1 redo log file missing when starting the DB?
- What will happen if 1 redo log file missing when using(performing operations) the DB?
(will it recover automatically/db abort/even redo log lost will the DB run as usual... ?)
-How to recover this lost redo log?
- What will happen if 1 control file missing when starting the DB?
- What will happen if 1 control file missing when using(performing operations) the DB?
(will it recover automatically/db abort/even control file lost will the DB run as usual... ?)
-How to recover this lost redo log?
thanks

- What will happen if 1 redo log file missing when starting the DB?IF you have multiplexed the members you can drop the lost file and will be able to open the DB
What will happen if 1 redo log file missing when using(performing operations) the DB?Again if multiplexed it will drop a warinign in the alert log and contnue to write on othere members
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/recoscen.htm#sthref1385
- What will happen if 1 control file missing when starting the DB?Just remove the entry from the init.ora and start the DB
What will happen if 1 control file missing when using(performing operations) the DB?Will shutdown

ORA-00205: error in identifying control file while startup database

Dear Experts,
we are using Oracle 10g on RHEL5.4 64Bit ecc 6.0 with eph 4 i have moved all my sap data files along with Temp file.
when i startup my database getting error.
SQL> startup mount
ORACLE instance started.
Total System Global Area 535662592 bytes
Fixed Size 1334380 bytes
Variable Size 306185108 bytes
Database Buffers 222298112 bytes
Redo Buffers 5844992 bytes
ORA-00205: error in identifying control file, check alert log for more info
when i checked initSID.ora then found old location of control file.
1)/oracle/SID/sapdata1/cntrl
2)/oracle/SID/origlogA/cntrl
3)/oracle/SID/origlogB/cntrl
i have manually changed location of control file.
1)/oracle/SID/sapdata10/cntrl
2)/oracle/SID/origlogA/cntrl
3)/oracle/SID/origlogB/cntrl
SQL> Create Pfile from Spfile;
File Created.
i would like to mount my database from Pfile plese help me i execute scripts below.
SQL> STARTUP MOUNT=/oracle/SID/ORACLE_HOME/dbs/initSID.ora
invalid startup option.
or suggest me some other way so that i can startup my Database.
with Regards

Thanks,LOG of alert_SID.log control_files = /oracle/PRD/origlogA/cntrl/cntrlPRD.dbf, /oracle/PRD/origlogB/cntrl/cntrlPRD.dbf, /oracle/PRD/sapdata1/cntrl/cntrlPRD.dbf, control_file_record_keep_time= 30, Mon Nov 14 08:24:52 2011
CREATE DATABASE PRD CONTROLFILE REUSE MAXLOGFILES 255 MAXLOGMEMBERS 3 MAXLOGHISTORY 1000 MAXDATAFILES 254 MAXINSTANCES 50 NOARCHIVELOG CHARACTER SET UTF8 NATIONAL CHARACTER SET UTF8 DATAFILE '/oracle/PRD/sapdata1/system_1/system.data1' SIZE 350M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M EXTENT MANAGEMENT LOCAL DEFAULT TEMPORARY TABLESPACE PSAPTEMP TEMPFILE '/oracle/PRD/sapdata1/temp_1/temp.data1' SIZE 570M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M UNDO TABLESPACE PSAPUNDO DATAFILE '/oracle/PRD/sapdata1/undo_1/undo.data1' SIZE 700M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M SYSAUX DATAFILE '/oracle/PRD/sapdata1/sysaux_1/sysaux.data1' SIZE 200M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
LOGFILE GROUP 1 ('/oracle/PRD/origlogA/log_g11m1.dbf',
'/oracle/PRD/mirrlogA/log_g11m2.dbf') SIZE 50M REUSE ,GROUP 2 ('/oracle/PRD/origlogB/log_g12m1.dbf',
'/oracle/PRD/mirrlogB/log_g12m2.dbf') SIZE 50M REUSE ,GROUP 3 ('/oracle/PRD/origlogA/log_g13m1.dbf',
'/oracle/PRD/mirrlogA/log_g13m2.dbf') SIZE 50M REUSE ,GROUP 4 ('/oracle/PRD/origlogB/log_g14m1.dbf',
'/oracle/PRD/mirrlogB/log_g14m2.dbf') SIZE 50M REUSEMon Nov 14 08:24:53 2011Database mounted in Exclusive Mode
Mon Nov 14 08:25:06 2011Successful mount of redo thread 1, with mount id 1830841300
Assigning activation ID 1830841300 (0x6d206bd4) Thread 1 opened at log sequence 1
Current log# 1 seq# 1 mem# 0: /oracle/PRD/origlogA/log_g11m1.dbf
Current log# 1 seq# 1 mem# 1: /oracle/PRD/mirrlogA/log_g11m2.dbf,m Successful open of redo thread 1
Mon Nov 14 08:25:06 2011 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Mon Nov 14 08:25:06 2011 SMON: enabling cache recovery
Mon Nov 14 08:25:06 2011
create tablespace SYSTEM datafile '/oracle/PRD/sapdata1/system_1/system.data1' SIZE 350M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
EXTENT MANAGEMENT LOCAL online
Mon Nov 14 08:25:09 2011
Incremental checkpoint up to RBA [0x1.3.0], current log tail at RBA [0x1.3.0]
Mon Nov 14 08:25:15 2011
Completed: create tablespace SYSTEM datafile '/oracle/PRD/sapdata1/system_1/system.data1' SIZE 350M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
EXTENT MANAGEMENT LOCAL online
Mon Nov 14 08:25:15 2011
create rollback segment SYSTEM tablespace SYSTEM
storage (initial 50K next 50K)
Completed: create rollback segment SYSTEM tablespace SYSTEM
storage (initial 50K next 50K)
Mon Nov 14 08:25:19 2011
CREATE UNDO TABLESPACE PSAPUNDO DATAFILE '/oracle/PRD/sapdata1/undo_1/undo.data1' SIZE 700M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
Mon Nov 14 08:25:36 2011
Successfully onlined Undo Tablespace 1.
Completed: CREATE UNDO TABLESPACE PSAPUNDO DATAFILE '/oracle/PRD/sapdata1/undo_1/undo.data1' SIZE 700M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
Mon Nov 14 08:25:36 2011
create tablespace SYSAUX datafile '/oracle/PRD/sapdata1/sysaux_1/sysaux.data1' SIZE 200M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO online
Completed: create tablespace SYSAUX datafile '/oracle/PRD/sapdata1/sysaux_1/sysaux.data1' SIZE 200M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO online

Remove the current control file when the database is running on linux or un

Question From Oracler:
下面这个例子中，假如controlfile被删除掉了，instance还没有关闭，可以通过lsof找出controlfile的file descriptors,再通过dd把文件恢复过来...
我觉得这样dd出来的控制文件是没有办法直接启动这个数据库的，因为CKPT每3S一次，你dd恢复出来的控制文件SCN肯定和datafile不一样，比datafile小，... 要是recover会提示控制文件太久，不知道我理解正不正确啊？
http://www.oracledatabase12g.com/archives/unix-linux%e4%b8%8b%e5%88%a0%e9%99%a4oracle%e6%8e%a7%e5%88%b6%e6%96%87%e4%bb%b6controlfile%e4%b8%ba%e4%bb%80%e4%b9%88%e5%ae%9e%e4%be%8binstance%e6%b2%a1%e6%9c%89%e7%ab%8b%e5%8d%b3%e5%a5%94%e6%ba%83.html
dd恢复的控制文件怎么会比打他file、
怎么会比datafile的scn 小呢
一旦关库，那么fd是不是就消失了，没有办法dd了，那么造成scn不相同的原因是dd过程中scn的变化么？
还请大致谈一下造成scn更新的必要条件。

有网友提问，若控制文件是 create controlfile 重建得来的又会如何？这里我们可以看一下：
我们来看一下：
SQL> alter system switch logfile;
System altered.
SQL> select distinct checkpoint_change# from v$datafile_header;
CHECKPOINT_CHANGE#
15169797
SQL> alter system checkpoint;
System altered.
SQL> select distinct checkpoint_change# from v$datafile_header;
CHECKPOINT_CHANGE#
15169802 =>E7783A
15169802 =>E7783A 最近的一次FULL CHECKPOINT的SCN
SQL> select name from v$tablespace;
NAME
SYSTEM
UNDOTBS1
SYSAUX
USERS
EXAMPLE
TEMP
SQL> alter tablespace SYSTEM begin backup;
Tablespace altered.
SQL> alter tablespace UNDOTBS1 begin backup;
Tablespace altered.
SQL> alter tablespace SYSAUX begin backup;
Tablespace altered.
SQL> alter tablespace USERS begin backup;
Tablespace altered.
SQL> alter tablespace EXAMPLE begin backup;
Tablespace altered.
SQL> alter tablespace SYSTEM end backup;
Tablespace altered.
SQL> alter tablespace UNDOTBS1 end backup;
Tablespace altered.
SQL> alter tablespace SYSAUX end backup;
Tablespace altered.
SQL> alter tablespace USERS end backup;
Tablespace altered.
SQL> alter tablespace EXAMPLE end backup;
Tablespace altered.
begin /end backup 会引发FILE CHECKPOINT ，造成datafile_header的 checkpoint_change# 更新
SQL> select distinct checkpoint_change# from v$datafile_header;
CHECKPOINT_CHANGE#
15169814
15169827
15169842
15169821
15169835
15169814 =>E77916 是最小的一个 datafile header checkpoint_change#
SQL> oradebug setmypid;
Statement processed.
SQL> oradebug dump controlf 3;
Statement processed.
SQL> oradebug tracefile_name;
但是此时去dump controlf 可以发现控制文件中的database checkpint 仍是 E7783A 15169802 即上一次FULL CHECKPOINT的 SCN
DATABASE ENTRY
(size = 316, compat size = 316, section max = 1, section in-use = 1,
last-recid= 0, old-recno = 0, last-recno = 0)
(extent = 1, blkno = 1, numrecs = 1)
03/09/2012 23:04:33
DB Name "G10R21"
Database flags = 0x00404001 0x00001000
Controlfile Creation Timestamp 03/09/2012 23:04:33
Incmplt recovery scn: 0x0000.00000000
Resetlogs scn: 0x0000.00e7784f Resetlogs Timestamp 03/09/2012 23:11:46
Prior resetlogs scn: 0x0000.00e77780 Prior resetlogs Timestamp 03/09/2012 22:57:44
Redo Version: compatible=0xa200100
#Data files = 16, #Online files = 16
Database checkpoint: Thread=1 scn: 0x0000.00e7790a ==>15169802
Threads: #Enabled=1, #Open=1, Head=1, Tail=1
REDO THREAD RECORDS
(size = 256, compat size = 256, section max = 8, section in-use = 1,
last-recid= 0, old-recno = 0, last-recno = 0)
(extent = 1, blkno = 9, numrecs = 8)
THREAD #1 - status:0xf thread links forward:0 back:0
#logs:3 first:1 last:3 current:2 last used seq#:0x2
enabled at scn: 0x0000.00e7784f 03/09/2012 23:11:46
disabled at scn: 0x0000.00000000 01/01/1988 00:00:00
opened at 03/09/2012 23:11:46 by instance G10R21
Checkpointed at scn: 0x0000.00e7790a 03/09/2012 23:12:12
thread:1 rba:(0x2.3.10)
SQL> alter database backup controlfile to trace;
Database altered.
SQL> oradebug setmypid;
Statement processed.
SQL> oradebug tracefile_name;
SQL> shutdown abort;
ORACLE instance shut down.
[oracle@vrh8 ~]$ rm /s01/recreate.ctl
我们以NORESETLOGS重建控制文件:
SQL> startup nomount;
ORACLE instance started.
Total System Global Area 620756992 bytes
Fixed Size 2022760 bytes
Variable Size 234881688 bytes
Database Buffers 377487360 bytes
Redo Buffers 6365184 bytes
SQL> show parameter control
NAME TYPE VALUE
control_file_record_keep_time integer 7
control_files string /s01/recreate.ctl
SQL> CREATE CONTROLFILE REUSE DATABASE "G10R21" NORESETLOGS ARCHIVELOG
2 MAXLOGFILES 16
3 MAXLOGMEMBERS 3
4 MAXDATAFILES 100
5 MAXINSTANCES 8
6 MAXLOGHISTORY 2921
7 LOGFILE
8 GROUP 1 (
9 '/s01/oradata/G10R21/onlinelog/o1_mf_1_7ch812dg_.log',
10 '/s01/flash_recovery_area/G10R21/onlinelog/o1_mf_1_7ch813h5_.log'
11 ) SIZE 50M,
12 GROUP 2 (
13 '/s01/oradata/G10R21/onlinelog/o1_mf_2_7ch8144q_.log',
14 '/s01/flash_recovery_area/G10R21/onlinelog/o1_mf_2_7ch815cj_.log'
15 ) SIZE 50M,
16 GROUP 3 (
17 '/s01/oradata/G10R21/onlinelog/o1_mf_3_7ch816g2_.log',
18 '/s01/flash_recovery_area/G10R21/onlinelog/o1_mf_3_7ch817gp_.log'
19 ) SIZE 50M
20 -- STANDBY LOGFILE
DATAFILE
21 22 '/s01/oradata/G10R21/datafile/o1_mf_system_7ch8004t_.dbf',
23 '/s01/oradata/G10R21/datafile/o1_mf_undotbs1_7ch80081_.dbf',
24 '/s01/oradata/G10R21/datafile/o1_mf_sysaux_7ch8004x_.dbf',
25 '/s01/oradata/G10R21/datafile/o1_mf_users_7ch80085_.dbf',
26 '/s01/oradata/G10R21/datafile/o1_mf_example_7ch81ch3_.dbf',
27 '/s01/oradata/G10R21/datafile/o1_mf_users_7gvd5pwh_.dbf',
28 '/s01/oradata/G10R21/datafile/o1_mf_users_7h6t6fdt_.dbf',
29 '/s01/oradata/G10R21/datafile/o1_mf_users_7h6t6nxy_.dbf',
30 '/s01/oradata/G10R21/datafile/o1_mf_users_7h6t6qc2_.dbf',
31 '/s01/oradata/G10R21/datafile/o1_mf_users_7h6t6stt_.dbf',
32 '/s01/oradata/G10R21/datafile/o1_mf_users_7h6t6w5w_.dbf',
33 '/s01/oradata/G10R21/datafile/o1_mf_users_7h6t6yo0_.dbf',
34 '/s01/oradata/G10R21/datafile/o1_mf_users_7h6t717x_.dbf',
35 '/s01/oradata/G10R21/datafile/o1_mf_undotbs1_7h6ttkkx_.dbf',
36 '/s01/oradata/G10R21/datafile/o1_mf_undotbs1_7h6ttpn1_.dbf',
37 '/s01/oradata/G10R21/datafile/o1_mf_undotbs1_7h6ttsbd_.dbf'
38 CHARACTER SET AL32UTF8;
Control file created.
SQL> oradebug setmypid;
Statement processed.
SQL> oradebug dump controlf 3;
Statement processed.
DATABASE ENTRY
(size = 316, compat size = 316, section max = 1, section in-use = 1,
last-recid= 0, old-recno = 0, last-recno = 0)
(extent = 1, blkno = 1, numrecs = 1)
03/09/2012 23:16:57
DB Name "G10R21"
Database flags = 0x00400103 0x00001000
Controlfile Creation Timestamp 03/09/2012 23:16:58
Incmplt recovery scn: 0x0000.00000000
Resetlogs scn: 0x0000.00e7784f Resetlogs Timestamp 03/09/2012 23:11:46
Prior resetlogs scn: 0x0000.00e77780 Prior resetlogs Timestamp 03/09/2012 22:57:44
Redo Version: compatible=0xa200100
#Data files = 16, #Online files = 16
Database checkpoint: Thread=1 scn: 0x0000.00e77902 15169794
Threads: #Enabled=1, #Open=1, Head=1, Tail=1
Database checkpoint: 变成了 00e77902 =》 15169794，比上次FULL CHECKPOINT的15169802 还要小
这个
00e77902 =》 15169794从哪里来？
REDO THREAD RECORDS
(size = 256, compat size = 256, section max = 8, section in-use = 1,
last-recid= 0, old-recno = 0, last-recno = 0)
(extent = 1, blkno = 9, numrecs = 8)
THREAD #1 - status:0x7 thread links forward:0 back:0
#logs:3 first:1 last:3 current:2 last used seq#:0x2
enabled at scn: 0x0000.00e7784f 03/09/2012 23:11:46
disabled at scn: 0x0000.00000000 01/01/1988 00:00:00
opened at 01/01/1988 00:00:00 by instance
Checkpointed at scn: 0x0000.00e77902 03/09/2012 23:11:54
thread:1 rba:(0x2.2.0)
LOG FILE RECORDS
(size = 72, compat size = 72, section max = 16, section in-use = 3,
last-recid= 0, old-recno = 0, last-recno = 0)
(extent = 1, blkno = 10, numrecs = 16)
LOG FILE #1:
(name #3) /s01/oradata/G10R21/onlinelog/o1_mf_1_7ch812dg_.log
(name #4) /s01/flash_recovery_area/G10R21/onlinelog/o1_mf_1_7ch813h5_.log
Thread 1 redo log links: forward: 2 backward: 0
siz: 0x19000 seq: 0x00000001 hws: 0x4 bsz: 512 nab: 0xb6 flg: 0x0 dup: 2
Archive links: fwrd: 2 back: 0 Prev scn: 0x0000.00000000
Low scn: 0x0000.00e7784f 03/09/2012 23:11:46
Next scn: 0x0000.00e77902 03/09/2012 23:11:54
LOG FILE #2:
(name #1) /s01/oradata/G10R21/onlinelog/o1_mf_2_7ch8144q_.log
(name #2) /s01/flash_recovery_area/G10R21/onlinelog/o1_mf_2_7ch815cj_.log
Thread 1 redo log links: forward: 3 backward: 1
siz: 0x19000 seq: 0x00000002 hws: 0x1 bsz: 512 nab: 0xffffffff flg: 0xa dup: 2
Archive links: fwrd: 0 back: 1 Prev scn: 0x0000.00e7784f
Low scn: 0x0000.00e77902 03/09/2012 23:11:54
Next scn: 0xffff.ffffffff 01/01/1988 00:00:00
LOG FILE #3:
(name #5) /s01/oradata/G10R21/onlinelog/o1_mf_3_7ch816g2_.log
(name #6) /s01/flash_recovery_area/G10R21/onlinelog/o1_mf_3_7ch817gp_.log
Thread 1 redo log links: forward: 0 backward: 2
siz: 0x19000 seq: 0x00000000 hws: 0x2 bsz: 512 nab: 0x2 flg: 0x1 dup: 2
Archive links: fwrd: 0 back: 0 Prev scn: 0x0000.00000000
Low scn: 0x0000.00000000 01/01/1988 00:00:00
Next scn: 0x0000.00000000 01/01/1988 00:00:00
原来这个
00e77902 =》 15169794 来源于 current online redo logfile中最小的LOW SCN
DATA FILE RECORDS
(size = 428, compat size = 428, section max = 100, section in-use = 19,
last-recid= 0, old-recno = 0, last-recno = 0)
(extent = 1, blkno = 11, numrecs = 100)
DATA FILE #1:
(name #22) /s01/oradata/G10R21/datafile/o1_mf_system_7ch8004t_.dbf
creation size=0 block size=8192 status=0x12 head=22 tail=22 dup=1
tablespace 0, index=1 krfil=1 prev_file=0
unrecoverable scn: 0x0000.00000000 01/01/1988 00:00:00
Checkpoint cnt:2314 scn: 0x0000.00e77916 03/09/2012 23:12:46
Stop scn: 0xffff.ffffffff 03/09/2012 23:16:58
Creation Checkpointed at scn: 0x0000.00000008 10/22/2005 21:44:31
thread:0 rba:(0x0.0.0)
DATAFILE 1 的checkpoint scn最小为 00e77916 =》15169814
SQL> recover database using backup controlfile;
ORA-00279: change 15169814 generated at 03/09/2012 23:12:46 needed for thread 1
ORA-00289: suggestion :
/s01/flash_recovery_area/G10R21/archivelog/2012_03_09/o1_mf_1_2_%u_.arc
ORA-00280: change 15169814 for thread 1 is in sequence #2
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 15169814 generated at 03/09/2012 23:12:46 needed for thread 1
可以看到 recover database using backup controlfile 的起点是 15169814 即最小的一个 datafile header 的CHECKPOINT CHANGE#，
也就是说丢失控制文件并(create controlfile)重建后的recover 从最小的datafile header CHECKPOINT_CHANGE#开始，直到NEXT SCN 无穷大的 current logfile的 end 为止!
我们在看一下 RESETLOGS的情况：
SQL>
SQL> CREATE CONTROLFILE REUSE DATABASE "G10R21" RESETLOGS ARCHIVELOG
MAXLOGFILES 16
2 3 MAXLOGMEMBERS 3
4 MAXDATAFILES 100
5 MAXINSTANCES 8
6 MAXLOGHISTORY 2921
7 LOGFILE
8 GROUP 1 (
9 '/s01/oradata/G10R21/onlinelog/o1_mf_1_7ch812dg_.log',
10 '/s01/flash_recovery_area/G10R21/onlinelog/o1_mf_1_7ch813h5_.log'
11 ) SIZE 50M,
12 GROUP 2 (
13 '/s01/oradata/G10R21/onlinelog/o1_mf_2_7ch8144q_.log',
14 '/s01/flash_recovery_area/G10R21/onlinelog/o1_mf_2_7ch815cj_.log'
15 ) SIZE 50M,
16 GROUP 3 (
17 '/s01/oradata/G10R21/onlinelog/o1_mf_3_7ch816g2_.log',
18 '/s01/flash_recovery_area/G10R21/onlinelog/o1_mf_3_7ch817gp_.log'
19 ) SIZE 50M
20 -- STANDBY LOGFILE
21 DATAFILE
22 '/s01/oradata/G10R21/datafile/o1_mf_system_7ch8004t_.dbf',
23 '/s01/oradata/G10R21/datafile/o1_mf_undotbs1_7ch80081_.dbf',
'/s01/oradata/G10R21/datafile/o1_mf_sysaux_7ch8004x_.dbf',
24 25 '/s01/oradata/G10R21/datafile/o1_mf_users_7ch80085_.dbf',
26 '/s01/oradata/G10R21/datafile/o1_mf_example_7ch81ch3_.dbf',
27 '/s01/oradata/G10R21/datafile/o1_mf_users_7gvd5pwh_.dbf',
28 '/s01/oradata/G10R21/datafile/o1_mf_users_7h6t6fdt_.dbf',
29 '/s01/oradata/G10R21/datafile/o1_mf_users_7h6t6nxy_.dbf',
30 '/s01/oradata/G10R21/datafile/o1_mf_users_7h6t6qc2_.dbf',
31 '/s01/oradata/G10R21/datafile/o1_mf_users_7h6t6stt_.dbf',
32 '/s01/oradata/G10R21/datafile/o1_mf_users_7h6t6w5w_.dbf',
33 '/s01/oradata/G10R21/datafile/o1_mf_users_7h6t6yo0_.dbf',
34 '/s01/oradata/G10R21/datafile/o1_mf_users_7h6t717x_.dbf',
35 '/s01/oradata/G10R21/datafile/o1_mf_undotbs1_7h6ttkkx_.dbf',
36 '/s01/oradata/G10R21/datafile/o1_mf_undotbs1_7h6ttpn1_.dbf',
37 '/s01/oradata/G10R21/datafile/o1_mf_undotbs1_7h6ttsbd_.dbf'
CHARACTER SET AL32UTF8; 38
Control file created.
SQL> oradebug setmypid;
Statement processed.
SQL> oradebug dump controlf 3;
Statement processed.
SQL> oradebug tracefile_name;
DATABASE ENTRY
(size = 316, compat size = 316, section max = 1, section in-use = 1,
last-recid= 0, old-recno = 0, last-recno = 0)
(extent = 1, blkno = 1, numrecs = 1)
03/09/2012 23:20:03
DB Name "G10R21"
Database flags = 0x00400147 0x00001000
Controlfile Creation Timestamp 03/09/2012 23:20:03
Incmplt recovery scn: 0x0000.00e77932
Resetlogs scn: 0x0000.00e7784f Resetlogs Timestamp 03/09/2012 23:11:46
Prior resetlogs scn: 0x0000.00e77780 Prior resetlogs Timestamp 03/09/2012 22:57:44
Redo Version: compatible=0xa200100
#Data files = 16, #Online files = 16
Database checkpoint: Thread=0 scn: 0x0000.00000000
Threads: #Enabled=1, #Open=0, Head=0, Tail=0
REDO THREAD RECORDS
(size = 256, compat size = 256, section max = 8, section in-use = 1,
last-recid= 0, old-recno = 0, last-recno = 0)
(extent = 1, blkno = 9, numrecs = 8)
THREAD #1 - status:0x6 thread links forward:0 back:0
#logs:3 first:1 last:3 current:3 last used seq#:0x0
enabled at scn: 0x0000.00000000 01/01/1988 00:00:00
disabled at scn: 0x0000.00000000 01/01/1988 00:00:00
opened at 01/01/1988 00:00:00 by instance
Checkpointed at scn: 0x0000.00000000
thread:0 rba:(0x0.0.0)
LOG FILE RECORDS
(size = 72, compat size = 72, section max = 16, section in-use = 3,
last-recid= 0, old-recno = 0, last-recno = 0)
(extent = 1, blkno = 10, numrecs = 16)
LOG FILE #1:
(name #5) /s01/oradata/G10R21/onlinelog/o1_mf_1_7ch812dg_.log
(name #6) /s01/flash_recovery_area/G10R21/onlinelog/o1_mf_1_7ch813h5_.log
Thread 1 redo log links: forward: 2 backward: 0
siz: 0x19000 seq: 0x00000000 hws: 0x0 bsz: 512 nab: 0x0 flg: 0x1 dup: 2
Archive links: fwrd: 0 back: 0 Prev scn: 0x0000.00000000
Low scn: 0x0000.00000000 01/01/1988 00:00:00
Next scn: 0x0000.00000000 01/01/1988 00:00:00
LOG FILE #2:
(name #3) /s01/oradata/G10R21/onlinelog/o1_mf_2_7ch8144q_.log
(name #4) /s01/flash_recovery_area/G10R21/onlinelog/o1_mf_2_7ch815cj_.log
Thread 1 redo log links: forward: 3 backward: 1
siz: 0x19000 seq: 0x00000000 hws: 0x0 bsz: 512 nab: 0x0 flg: 0x1 dup: 2
Archive links: fwrd: 0 back: 0 Prev scn: 0x0000.00000000
Low scn: 0x0000.00000000 01/01/1988 00:00:00
Next scn: 0x0000.00000000 01/01/1988 00:00:00
LOG FILE #3:
(name #1) /s01/oradata/G10R21/onlinelog/o1_mf_3_7ch816g2_.log
(name #2) /s01/flash_recovery_area/G10R21/onlinelog/o1_mf_3_7ch817gp_.log
Thread 1 redo log links: forward: 0 backward: 2
siz: 0x19000 seq: 0x00000000 hws: 0x0 bsz: 512 nab: 0x2 flg: 0xb dup: 2
Archive links: fwrd: 0 back: 0 Prev scn: 0x0000.00000000
Low scn: 0x0000.00000000 01/01/1988 00:00:00
Next scn: 0x0000.00000000 01/01/1988 00:00:00
虽然database checkpoint scn 等都是0 ，但是不影响从最小的datafile header checkpoint change 开始recover的结论。
SQL> recover database using backup controlfile;
ORA-00279: change 15169814 generated at 03/09/2012 23:12:46 needed for thread 1
ORA-00289: suggestion :
/s01/flash_recovery_area/G10R21/archivelog/2012_03_09/o1_mf_1_2_%u_.arc
ORA-00280: change 15169814 for thread 1 is in sequence #2
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}

How to move temp file, redo log to different drive oracle 9i

Hi ,
I am using oracle 9i
by mistakenly, i have instaled oracle installable on system drive i mean c: drive.I have installed teh database on D: drive.
For tunning perfomance i would like to move the redlog files and temp files to different drive.
Could you please explain me the step by step procedure how to do this
Thanks
AITS

Very easy -
Create a new temp tablespace with the files on the drive you want, make it the default temp tablespace for any users/schemas you have created, then drop the old temp tablespace including datafiles.
For the redo logs, create new groups, again with the logfiles on the dirves you want them on, cycle out of the old ones with "alter system switch logfile;" then drop them.

Multiplexing redo logs and control files to a separate diskgroup

General question this one...
I've been using ASM for a few years now and have always installed a new system with 3 diskgroups
+DATA - for datafiles, control files, redo logs
+FRA - for achive logs, flash recovery. RMAN backup
Those I guess are the standards, but I've always created an extra (very small) diskgroup, called +ONLINE where I keep multiplexed copies of the redo logs and control files.
My reasoning behind this is that if there are any issues with the +DATA diskgroup, the redo logs and control files can still be accessed.
In the olden days (all those 5 years ago!), on local storage, this was important, but is it still important now? With all the striping and mirroring going on (both at ASM and RAID level), am I just being overtly paranoid? Does this additional +ONLINE diskgroup actually hamper performance? (with dual write overheads that are not necessary)
Thoughts?

Some of the decision will probably depend on your specific environment's data activity, volume, and throughput.
Something to remember is that redo logs are sequential write, which benefit from a lower RAID overhead (RAID-10, 2 writes per IOP vs RAID-5, 4 writes per IOP). RAID-10 is often not cost-effective for the data portion of a database. If your database is OLTP with a high volume of random reads/writes, you're potentially hurting redo throughput by creating contention on the disks sharing data and redo. Again, that depends entirely on what you're seeing in terms of wait events. A low volume database would probably not experience any noticeable degraded performance.
In my environment, I have RAID-5 and RAID-10 available, and since the RAID-10 requirement from a capacity perspective for redo is very low, it makes sense to create 2 diskgroups for online redo, separate from DATA, and separate from each other. This way, we don't need to be concerned with DATA transactions impacting REDO performance, and vice versa, and we still maintain redo redundancy.
In my opinion, you can't be too paranoid. :)
Good luck!
K

Is it possible to use Archive Redo log file

Hi friends,
My database is runing in archive log mode.I had taken cold backup on Sunday but i am taking archive log file daily evening.
Wednesday my database crash that means i lost all control file,redo log file,datafile etc.
I have archived log file backup till Tuesday Night and other files like control file,datafile etc of Sunday .
1)Is it possible to recover database till tuesday if yes HOW to use archive log file.
(See SCN no of control file and datafiles is same ,if we use RECOVER DATABASE command oracle shows that media recovery is not requide.)
we don't have current control file we had lost in media crash.
null

Dear friend
In this scenario
you lost the contorl file
1>If you have old copy of Contorl file,
which has the current structure of the
database and all the archive files then
you can recover the database with
Ponint in time recovery (Using Backup Controlfile)
suresh

Sample Response File for Oracle Database 12c Standard Edition on Oracle Linux 6.4 -- working

oracle@styles-and-artists-development-oracle database]$ cat response/db_install.rsp
## Copyright(c) Oracle Corporation 1998,2013. All rights reserved.##
## Specify values for the variables listed below to customize     ##
## your installation.                                             ##
## Each variable is associated with a comment. The comment        ##
## can help to populate the variables with the appropriate        ##
## values.                                                        ##
## IMPORTANT NOTE: This file contains plain text passwords and    ##
## should be secured to have read permission only by oracle user ##
## or db administrator who owns this installation.                ##
# Do not change the following system generated value.
oracle.install.responseFileVersion=/oracle/install/rspfmt_dbinstall_response_schema_v12.1.0
# Specify the installation option.
# It can be one of the following:
#   - INSTALL_DB_SWONLY
#   - INSTALL_DB_AND_CONFIG
#   - UPGRADE_DB
oracle.install.option=INSTALL_DB_AND_CONFIG
# Specify the hostname of the system as set during the install. It can be used
# to force the installation to use an alternative hostname rather than using the
# first hostname found on the system. (e.g., for systems with multiple hostnames
# and network interfaces)
ORACLE_HOSTNAME=styles-and-artists-development-oracle
# Specify the Unix group to be set for the inventory directory.
UNIX_GROUP_NAME=oracle
# Specify the location which holds the inventory files.
# This is an optional parameter if installing on
# Windows based Operating System.
INVENTORY_LOCATION=/home/oracle/oracleInventory
# Specify the languages in which the components will be installed.
# en   : English                  ja   : Japanese
# fr   : French                   ko   : Korean
# ar   : Arabic                   es   : Latin American Spanish
# bn   : Bengali                  lv   : Latvian
# pt_BR: Brazilian Portuguese     lt   : Lithuanian
# bg   : Bulgarian                ms   : Malay
# fr_CA: Canadian French          es_MX: Mexican Spanish
# ca   : Catalan                  no   : Norwegian
# hr   : Croatian                 pl   : Polish
# cs   : Czech                    pt   : Portuguese
# da   : Danish                   ro   : Romanian
# nl   : Dutch                    ru   : Russian
# ar_EG: Egyptian                 zh_CN: Simplified Chinese
# en_GB: English (Great Britain) sk   : Slovak
# et   : Estonian                 sl   : Slovenian
# fi   : Finnish                  es_ES: Spanish
# de   : German                   sv   : Swedish
# el   : Greek                    th   : Thai
# iw   : Hebrew                   zh_TW: Traditional Chinese
# hu   : Hungarian                tr   : Turkish
# is   : Icelandic                uk   : Ukrainian
# in   : Indonesian               vi   : Vietnamese
# it   : Italian
# all_langs   : All languages
# Specify value as the following to select any of the languages.
# Example : SELECTED_LANGUAGES=en,fr,ja
# Specify value as the following to select all the languages.
# Example : SELECTED_LANGUAGES=all_langs
SELECTED_LANGUAGES=en
# Specify the complete path of the Oracle Home.
ORACLE_HOME=/extended2/oracleBase/db12c1
# Specify the complete path of the Oracle Base.
ORACLE_BASE=/extended2/oracleBase
# Specify the installation edition of the component.
# The value should contain only one of these choices.
#   - EE     : Enterprise Edition
#   - SE     : Standard Edition
#   - SEONE : Standard Edition One
#   - PE     : Personal Edition (WINDOWS ONLY)
oracle.install.db.InstallEdition=SE
# PRIVILEGED OPERATING SYSTEM GROUPS                                          #
# Provide values for the OS groups to which OSDBA and OSOPER privileges       #
# needs to be granted. If the install is being performed as a member of the   #
# group "dba", then that will be used unless specified otherwise below.       #
# The value to be specified for OSDBA and OSOPER group is only for UNIX based #
# Operating System.                                                           #
# The DBA_GROUP is the OS group which is to be granted OSDBA privileges.
oracle.install.db.DBA_GROUP=osdba
# The OPER_GROUP is the OS group which is to be granted OSOPER privileges.
# The value to be specified for OSOPER group is optional.
oracle.install.db.OPER_GROUP=osoper
# The BACKUPDBA_GROUP is the OS group which is to be granted OSBACKUPDBA privileges.
oracle.install.db.BACKUPDBA_GROUP=bckdba
# The DGDBA_GROUP is the OS group which is to be granted OSDGDBA privileges.
oracle.install.db.DGDBA_GROUP=dbdba
# The KMDBA_GROUP is the OS group which is to be granted OSKMDBA privileges.
oracle.install.db.KMDBA_GROUP=kmdba
#                               Grid Options                                  #
# Specify the type of Real Application Cluster Database
#   - ADMIN_MANAGED: Admin-Managed
#   - POLICY_MANAGED: Policy-Managed
# If left unspecified, default will be ADMIN_MANAGED
oracle.install.db.rac.configurationType=
# Value is required only if RAC database type is ADMIN_MANAGED
# Specify the cluster node names selected during the installation.
# Leaving it blank will result in install on local server only (Single Instance)
# Example : oracle.install.db.CLUSTER_NODES=node1,node2
oracle.install.db.CLUSTER_NODES=
# This variable is used to enable or disable RAC One Node install.
#   - true : Value of RAC One Node service name is used.
#   - false : Value of RAC One Node service name is not used.
# If left blank, it will be assumed to be false.
oracle.install.db.isRACOneInstall=
# Value is required only if oracle.install.db.isRACOneInstall is true.
# Specify the name for RAC One Node Service
oracle.install.db.racOneServiceName=
# Value is required only if RAC database type is POLICY_MANAGED
# Specify a name for the new Server pool that will be configured
# Example : oracle.install.db.rac.serverpoolName=pool1
oracle.install.db.rac.serverpoolName=
# Value is required only if RAC database type is POLICY_MANAGED
# Specify a number as cardinality for the new Server pool that will be configured
# Example : oracle.install.db.rac.serverpoolCardinality=2
oracle.install.db.rac.serverpoolCardinality=
#                        Database Configuration Options                       #
# Specify the type of database to create.
# It can be one of the following:
#   - GENERAL_PURPOSE/TRANSACTION_PROCESSING
#   - DATA_WAREHOUSE
oracle.install.db.config.starterdb.type=GENERAL_PURPOSE
# Specify the Starter Database Global Database Name.
oracle.install.db.config.starterdb.globalDBName=cbd
# Specify the Starter Database SID.
oracle.install.db.config.starterdb.SID=cdb1
# Specify whether the database should be configured as a Container database.
oracle.install.db.ConfigureAsContainerDB=true
# Specify the Pluggable Database name for the pluggable database in Container Database.
oracle.install.db.config.PDBName=pdb1
# Specify the Starter Database character set.
# One of the following
# AL32UTF8, WE8ISO8859P15, WE8MSWIN1252, EE8ISO8859P2,
# EE8MSWIN1250, NE8ISO8859P10, NEE8ISO8859P4, BLT8MSWIN1257,
# BLT8ISO8859P13, CL8ISO8859P5, CL8MSWIN1251, AR8ISO8859P6,
# AR8MSWIN1256, EL8ISO8859P7, EL8MSWIN1253, IW8ISO8859P8,
# IW8MSWIN1255, JA16EUC, JA16EUCTILDE, JA16SJIS, JA16SJISTILDE,
# KO16MSWIN949, ZHS16GBK, TH8TISASCII, ZHT32EUC, ZHT16MSWIN950,
# ZHT16HKSCS, WE8ISO8859P9, TR8MSWIN1254, VN8MSWIN1258
oracle.install.db.config.starterdb.characterSet=AL32UTF8
# This variable should be set to true if Automatic Memory Management
# in Database is desired.
# If Automatic Memory Management is not desired, and memory allocation
# is to be done manually, then set it to false.
oracle.install.db.config.starterdb.memoryOption=true
# Specify the total memory allocation for the database. Value(in MB) should be
# at least 256 MB, and should not exceed the total physical memory available
# on the system.
# Example: oracle.install.db.config.starterdb.memoryLimit=512
oracle.install.db.config.starterdb.memoryLimit=512
# This variable controls whether to load Example Schemas onto
# the starter database or not.
oracle.install.db.config.starterdb.installExampleSchemas=true
# Passwords can be supplied for the following four schemas in the             #
# starter database:                                                           #
#   SYS                                                                       #
#   SYSTEM                                                                    #
#   DBSNMP (used by Enterprise Manager)                                       #
# Same password can be used for all accounts (not recommended)                #
# or different passwords for each account can be provided (recommended)       #
# This variable holds the password that is to be used for all schemas in the
# starter database.
oracle.install.db.config.starterdb.password.ALL=CDBadmin12345#
# Specify the SYS password for the starter database.
oracle.install.db.config.starterdb.password.SYS=CBDsys12345#
# Specify the SYSTEM password for the starter database.
oracle.install.db.config.starterdb.password.SYSTEM=PDBsys12345#
# Specify the DBSNMP password for the starter database.
oracle.install.db.config.starterdb.password.DBSNMP=DBsnmp12345#
# Specify the PDBADMIN password required for creation of Pluggable Database in the Container Database.
oracle.install.db.config.starterdb.password.PDBADMIN=PDBadmin12345#
# Specify the management option to use for managing the database.
# Options are:
# 1. CLOUD_CONTROL - If you want to manage your database with Enterprise Manager Cloud Control along with Database Express.
# 2. DEFAULT   -If you want to manage your database using the default Database Express option.
oracle.install.db.config.starterdb.managementOption=DEFAULT
# Specify the OMS host to connect to Cloud Control.
# Applicable only when oracle.install.db.config.starterdb.managementOption=CLOUD_CONTROL
oracle.install.db.config.starterdb.omsHost=
# Specify the OMS port to connect to Cloud Control.
# Applicable only when oracle.install.db.config.starterdb.managementOption=CLOUD_CONTROL
oracle.install.db.config.starterdb.omsPort=
# Specify the EM Admin user name to use to connect to Cloud Control.
# Applicable only when oracle.install.db.config.starterdb.managementOption=CLOUD_CONTROL
oracle.install.db.config.starterdb.emAdminUser=
# Specify the EM Admin password to use to connect to Cloud Control.
# Applicable only when oracle.install.db.config.starterdb.managementOption=CLOUD_CONTROL
oracle.install.db.config.starterdb.emAdminPassword=
# SPECIFY RECOVERY OPTIONS                                                    #
# Recovery options for the database can be mentioned using the entries below #
# This variable is to be set to false if database recovery is not required. Else
# this can be set to true.
oracle.install.db.config.starterdb.enableRecovery=true
# Specify the type of storage to use for the database.
# It can be one of the following:
#   - FILE_SYSTEM_STORAGE
#   - ASM_STORAGE
oracle.install.db.config.starterdb.storageType=FILE_SYSTEM_STORAGE
# Specify the database file location which is a directory for datafiles, control
# files, redo logs.
# Applicable only when oracle.install.db.config.starterdb.storage=FILE_SYSTEM_STORAGE
oracle.install.db.config.starterdb.fileSystemStorage.dataLocation=/extended1/db/data
# Specify the recovery location.
# Applicable only when oracle.install.db.config.starterdb.storage=FILE_SYSTEM_STORAGE
oracle.install.db.config.starterdb.fileSystemStorage.recoveryLocation=/extended1/db/recovery
# Specify the existing ASM disk groups to be used for storage.
# Applicable only when oracle.install.db.config.starterdb.storageType=ASM_STORAGE
oracle.install.db.config.asm.diskGroup=/dev/oracleasm
# Specify the password for ASMSNMP user of the ASM instance.
# Applicable only when oracle.install.db.config.starterdb.storage=ASM_STORAGE
oracle.install.db.config.asm.ASMSNMPPassword=ASMsnmp122345#
# Specify the My Oracle Support Account Username.
# Example   : [email protected]
MYORACLESUPPORT_USERNAME=
# Specify the My Oracle Support Account Username password.
# Example    : MYORACLESUPPORT_PASSWORD=password
MYORACLESUPPORT_PASSWORD=
# Specify whether to enable the user to set the password for
# My Oracle Support credentials. The value can be either true or false.
# If left blank it will be assumed to be false.
# Example    : SECURITY_UPDATES_VIA_MYORACLESUPPORT=true
SECURITY_UPDATES_VIA_MYORACLESUPPORT=false
# Specify whether user doesn't want to configure Security Updates.
# The value for this variable should be true if you don't want to configure
# Security Updates, false otherwise.
# The value can be either true or false. If left blank it will be assumed
# to be false.
# Example    : DECLINE_SECURITY_UPDATES=false
DECLINE_SECURITY_UPDATES=flase
# Specify the Proxy server name. Length should be greater than zero.
# Example    : PROXY_HOST=proxy.domain.com
PROXY_HOST=
# Specify the proxy port number. Should be Numeric and atleast 2 chars.
# Example    : PROXY_PORT=25
PROXY_PORT=
# Specify the proxy user name. Leave PROXY_USER and PROXY_PWD
# blank if your proxy server requires no authentication.
# Example    : PROXY_USER=username
PROXY_USER=
# Specify the proxy password. Leave PROXY_USER and PROXY_PWD
# blank if your proxy server requires no authentication.
# Example    : PROXY_PWD=password
PROXY_PWD=
# Specify the proxy realm.
# Example    : PROXY_REALM=metalink
PROXY_REALM=
# Specify the Oracle Support Hub URL.
# Example    : COLLECTOR_SUPPORTHUB_URL=https://orasupporthub.company.com:8080/
COLLECTOR_SUPPORTHUB_URL=
# Specify the auto-updates option. It can be one of the following:
#   - MYORACLESUPPORT_DOWNLOAD
#   - OFFLINE_UPDATES
#   - SKIP_UPDATES
oracle.installer.autoupdates.option=SKIP_UPDATES
# In case MYORACLESUPPORT_DOWNLOAD option is chosen, specify the location where
# the updates are to be downloaded.
# In case OFFLINE_UPDATES option is chosen, specify the location where the updates
# are present.
oracle.installer.autoupdates.downloadUpdatesLoc=
# Specify the My Oracle Support Account Username which has the patches download privileges
# to be used for software updates.
# Example   : [email protected]
AUTOUPDATES_MYORACLESUPPORT_USERNAME=
# Specify the My Oracle Support Account Username password which has the patches download privileges
# to be used for software updates.
# Example    : AUTOUPDATES_MYORACLESUPPORT_PASSWORD=password
AUTOUPDATES_MYORACLESUPPORT_PASSWORD=

This is the simplest installation you can get, but if you want to do a fast response file based installation, there it is.

How Do I Restore Deleted Redo Logs

I currently have alter database archivelog set and am backing up my archive log redo file. However, I am trying to test a scenario where all of my redo log files have been deleted, and thus need to be restored. I have backups of my archivelog files. I'm trying to recover my redo log files by executing the following:
RMAN> restore archivelog all;
Starting restore at 14-AUG-02
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=9 devtype=DISK
archive log thread 1 sequence 102 is already on disk as file C:\ORACLE\ORA90\RDBMS\ARC00102.001
archive log thread 1 sequence 103 is already on disk as file C:\ORACLE\ORA90\RDBMS\ARC00103.001
archive log thread 1 sequence 104 is already on disk as file C:\ORACLE\ORA90\RDBMS\ARC00104.001
restore not done; all files readonly, offline, or already restored
Finished restore at 14-AUG-02
Since this doesn't work I'm assuming I'm doing something wrong. Therefore, what are the necessary steps for recovering my redo log files after they have been deleted? Thanks to all for your help.

Since my test assumes that the Control files, redo logs and all tablespaces and data files have been deleted. These are the steps I'm using to attempt a full backup & recovery.
3.     Login to SQLPLUS sys/jalisco@bas as sysdba
4.     SQL> startup mount bas <enter>
5.     SQL> alter database archivelog; <enter>
6.     Stop the Listener and Instance through Services or Net Stop as before.
7.     From a command enter C:\Oracle\startoracle jalisco bas.
8.     Login to RMAN: rman target sys/jalisco@bas <enter>
9.     RMAN> configure controlfile autobackup on; <enter>
10.     RMAN> backup database format
a.     2> /oraclebackup/rman_%d_%t.bas plus archivelog; <enter>
At this point Oracle is configured so that both the archivelog and control files get backed up to oracle\ora90\database. The archivelogs get stored in oracle\ora90\rdbms.
1.     Restore the control files.
2.     Restore the archivelogs.
3.     Restore the tablespaces and data files.
4.     Create new reset logs.
1.     Confirm that the Listener and BAS service have been started through the Contol Panel, or by using Net Start.
2.     Login to RMAN: rman target sys/jalisco@bas as sysdba
3.     RMAN> startup nomount
4.     RMAN> restore controlfile from /oracle/ora90/database/C-493922189-2002MMYYYY-00;
5.     RMAN> startup mount
6.     RMAN> run {
a.     2> restore archivelog all; }
7.     RMAN> restore database;
8.     Exit RMAN and Login to SQLPLUS sys/jalisco@bas as sysdba
9.     SQL> alter database open resetlogs;
At this point I get the error which is listed in the above thread.
At this point a complete recovery should have taken place. It is extremely important to create a new backup now before proceeding.

Database information in control file

hi, i want to know what is database information in control file(reset logs scn and timestamp)
what this information is .as the control file contains checkpoint information .i.e it also contain scn.how does this database information related to archivelog which is applied to datafile and does redo log contain scn information.
thanks in advance.

control file contains all the infromation about the database like scn, database name, database created date, datafile and location, logfile and location, max log group, and so many infromation.
But this is the common question, before post your question kindly check in the internet, if you dont get any answer then post your question here.
Cheers

Database Control: File System Alert -

I am using 10.2 on HP UNIX 11. My development database is installed on a server, which is hared by many other applications/database. DB Control sends me alerts when file system is more than 80% used or so. I do not want to receive any file system alerts because these file systems are not my file systems.
I do not find any place to turn this alert off. Appreciate any help?

Gee whiz. In this thread (Database Control: Not sending e-mail you were complaining about not* getting email for that same condition. You say "I do not want to receive any file system alerts because these file systems are not my file systems.
" Some of the file systems are yours ... the ones holding $ORACLE_BASE and any fs holding any file even remotely related to your db ... .dbf files, redo logs, backup sets, archivelog files, bdump and other *dump directories. I like to be notified if they go over 80%.

Control file not updated till date in RAC two node database

Hi,
Good day.
To my surprise i found that control files, in our database RAC with two nodes, are not updated till date except one from node 1 and another from node 2.
But we got all the controlfile names in the init parameter file, in both the nodes.
Node 1
bash-3.00$ ls -lrt
total 922128
-rw------- 1 oracle dba 157286400 Nov 3 2007 cntrl03.dbf
-rw------- 1 oracle dba 157286400 Nov 3 2007 cntrl02.dbf
-rw------- 1 oracle dba 157286400 Apr 12 17:21 cntrl01.dbf
Node 2
bash-3.00$ ls -lrt
total 922128
-rw------- 1 oracle dba 157286400 Mar 30 09:17 cntrl03.dbf
-rw------- 1 oracle dba 157286400 Mar 30 09:17 cntrl02.dbf
-rw------- 1 oracle dba 157286400 Apr 12 17:20 cntrl01.dbf
As you could see cntrl01.dbf is the only file updated till date in both the nodes. The database is running fine.
what is actually happening?
Any suggestions?
Thanks,
Balu.

As you're using RAC it is very likely that you are using an SPFILE.
Connect as a DBA account (or an account with SELECT ANY DICTIONARY privileges) in both the instances and do "show parameter spfile" and "show parameter control" (or query V$parameter)
It is likely that the spfile is referencing only 1 controlfile.

How do I manually archive 1 redo log at a time?

The database is configured in archive mode, but automatic archiving is turned off.
For both Oracle 901 and 920 on Windows, when I try to manually archive a single redo log, the database
archives as many logs as it can up to the log just before the current log:
For example:
SQL> select * from v$log order by sequence#;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
1 1 14 104857600 1 NO INACTIVE 424246 19-JAN-05
2 1 15 104857600 1 NO INACTIVE 425087 28-MAR-05
3 1 16 104857600 1 NO INACTIVE 425088 28-MAR-05
4 1 17 512000 1 NO INACTIVE 425092 28-MAR-05
5 1 18 512000 1 NO INACTIVE 425100 28-MAR-05
6 1 19 512000 1 NO CURRENT 425102 28-MAR-05
6 rows selected.
SQL> alter system archive log next;
System altered.
SQL> select * from v$log order by sequence#;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
1 1 14 104857600 1 YES INACTIVE 424246 19-JAN-05
2 1 15 104857600 1 YES INACTIVE 425087 28-MAR-05
3 1 16 104857600 1 YES INACTIVE 425088 28-MAR-05
4 1 17 512000 1 YES INACTIVE 425092 28-MAR-05
5 1 18 512000 1 NO INACTIVE 425100 28-MAR-05
6 1 19 512000 1 NO CURRENT 425102 28-MAR-05
See - instead of only 1 log being archive, 4 of them were. Oracle behaves the same way if I use the "sequence" option:
SQL> select * from v$log order by sequence#;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
1 1 14 104857600 1 NO INACTIVE 424246 19-JAN-05
2 1 15 104857600 1 NO INACTIVE 425087 28-MAR-05
3 1 16 104857600 1 NO INACTIVE 425088 28-MAR-05
4 1 17 512000 1 NO INACTIVE 425092 28-MAR-05
5 1 18 512000 1 NO INACTIVE 425100 28-MAR-05
6 1 19 512000 1 NO CURRENT 425102 28-MAR-05
6 rows selected.
SQL> alter system archive log next;
System altered.
SQL> select * from v$log order by sequence#;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
1 1 14 104857600 1 YES INACTIVE 424246 19-JAN-05
2 1 15 104857600 1 YES INACTIVE 425087 28-MAR-05
3 1 16 104857600 1 YES INACTIVE 425088 28-MAR-05
4 1 17 512000 1 YES INACTIVE 425092 28-MAR-05
5 1 18 512000 1 NO INACTIVE 425100 28-MAR-05
6 1 19 512000 1 NO CURRENT 425102 28-MAR-05
Is there some default system configuration property telling Oracle to archive as many logs as it can?
Thanks,
DGR

Thanks Yoann (and Syed Jaffar Jaffar Hussain too),
but I don't have a problem finding the group to archive or executing the alter system archive log command.
My problem is that Oracle doesn't work as I expect it.
This comes from the Oracle 9.2 online doc:
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96540/statements_23a.htm#2053642
"Specify SEQUENCE to manually archive the online redo log file group identified by the log sequence number integer in the specified thread."
This implies that Oracle will only archive the log group identified by the log sequence number I specify in the alter system archive log sequence statement. However, Oracle is archiving almost all of the log groups (see my first post for an example).
This appears to be a bug, unless there is some other system parameter that is configured (by default) to allow Oracle to archive as many log groups as possible.
As to the reason why - it is an application requirement. The Oracle db must be in archive mode, automatic archiving must be disabled and the application must control online redo log archiving.
DGR

Mv control files, redo.log, database fies

Similar Messages

Maybe you are looking for