Q. A. 1. 2.

When to create control files ? Create controlfiles when You have lost all your control files. When you want to rename a database name (db_name)

Q. How to create control files. You need a create controlfile script for recreating control files. SQL*Plus: Release 9.2.0.2.0 - Production on Fri Feb 28 17:04:00 2003 Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved. Enter user-name: sys as sysdba Enter password: Connected to: Oracle9i Enterprise Edition Release 9.2.0.2.1 - Production With the Partitioning, Oracle Label Security, OLAP and Oracle Data Mining option s JServer Release 9.2.0.2.0 - Production SQL> alter database backup controlfile to trace; Database altered. SQL>

This will create a trace file in the udump directory. Im my case it was E:\oracle\admin\ORCL\udump\orcl_ora_2052.trc Edit the file to point the path of the datafiles and redologfiles. CREATE CONTROLFILE REUSE DATABASE "ORCL" RESETLOGS ARCHIVELOG MAXLOGFILES 5 MAXLOGMEMBERS 3 MAXDATAFILES 14 MAXINSTANCES 1 MAXLOGHISTORY 226 LOGFILE GROUP 1 'E:\ORACLE\ORADATA\ORCL\REDO01.LOG' SIZE 100M, GROUP 2 'E:\ORACLE\ORADATA\ORCL\REDO02.LOG' SIZE 100M, GROUP 3 'E:\ORACLE\ORADATA\ORCL\REDO03.LOG' SIZE 100M DATAFILE 'E:\ORACLE\ORADATA\ORCL\SYSTEM01.DBF', 'E:\ORACLE\ORADATA\ORCL\UNDOTBS01.DBF', 'E:\ORACLE\ORADATA\ORCL\EXAMPLE01.DBF', 'E:\ORACLE\ORADATA\ORCL\INDX01.DBF', 'E:\ORACLE\ORADATA\ORCL\TOOLS01.DBF', 'E:\ORACLE\ORADATA\ORCL\USERS01.DBF', 'E:\ORACLE\ORADATA\ORCL\OEM_REPOSITORY.DBF', 'E:\ORACLE\ORADATA\ORCL\CWMLITE01.DBF', 'E:\ORACLE\ORADATA\ORCL\DRSYS01.DBF', 'E:\ORACLE\ORADATA\ORCL\ODM01.DBF', 'E:\ORACLE\ORADATA\ORCL\XDB01.DBF',

'E:\ORACLE\ORADATA\ORCL\USERS02.DBF', 'E:\ORACLE\ORADATA\ORCL\USERS03.DBF', 'E:\ORACLE\ORADATA\ORCL\USERS04.DBF' CHARACTER SET WE8MSWIN1252 ; ALTER DATABASE OPEN RESETLOGS; and rename it to ctl.sql Then startup the database in nomount mode and run the ctl.sql file as sys as sys dba user SQL*Plus: Release 9.2.0.2.0 - Production on Fri Feb 28 17:25:14 2003 Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved. Enter user-name: sys as sysdba Enter password: Connected to an idle instance. SQL> startup nomount ORACLE instance started. Total System Global Area 80812648 bytes Fixed Size 453224 bytes Variable Size 54525952 bytes Database Buffers 25165824 bytes Redo Buffers 667648 bytes SQL> @E:\oracle\admin\ORCL\udump\ctl.sql Control file created. Database altered. SQL> select status from v$instance; STATUS -----------------------------------OPEN SQL> select name from v$controlfile; NAME -------------------------------------------------------E:\ORACLE\ORADATA\ORCL\CONTROL01.CTL E:\ORACLE\ORADATA\ORCL\CONTROL02.CTL E:\ORACLE\ORADATA\ORCL\CONTROL03.CTL

To rename the database change reuse to set in the create control file script as shown below CREATE CONTROLFILE SET DATABASE "ORCL" RESETLOGS ARCHIVELOG MAXLOGFILES 5

MAXLOGMEMBERS 3 MAXDATAFILES 14 MAXINSTANCES 1 MAXLOGHISTORY 226 LOGFILE GROUP 1 'E:\ORACLE\ORADATA\ORCL\REDO01.LOG' SIZE 100M, GROUP 2 'E:\ORACLE\ORADATA\ORCL\REDO02.LOG' SIZE 100M, GROUP 3 'E:\ORACLE\ORADATA\ORCL\REDO03.LOG' SIZE 100M DATAFILE 'E:\ORACLE\ORADATA\ORCL\SYSTEM01.DBF', 'E:\ORACLE\ORADATA\ORCL\UNDOTBS01.DBF', 'E:\ORACLE\ORADATA\ORCL\EXAMPLE01.DBF', 'E:\ORACLE\ORADATA\ORCL\INDX01.DBF', 'E:\ORACLE\ORADATA\ORCL\TOOLS01.DBF', 'E:\ORACLE\ORADATA\ORCL\USERS01.DBF', 'E:\ORACLE\ORADATA\ORCL\OEM_REPOSITORY.DBF', 'E:\ORACLE\ORADATA\ORCL\CWMLITE01.DBF', 'E:\ORACLE\ORADATA\ORCL\DRSYS01.DBF', 'E:\ORACLE\ORADATA\ORCL\ODM01.DBF', 'E:\ORACLE\ORADATA\ORCL\XDB01.DBF', 'E:\ORACLE\ORADATA\ORCL\USERS02.DBF', 'E:\ORACLE\ORADATA\ORCL\USERS03.DBF', 'E:\ORACLE\ORADATA\ORCL\USERS04.DBF' CHARACTER SET WE8MSWIN1252 ; ALTER DATABASE OPEN RESETLOGS; HAPPINESS IS REAL WHEN SHARED HomeAbout MeUseful QueriesUseful ScriptsDisclaimer In sweet memories of my ever loving brother "kutty thambi " ARUN KUMAR TUESDAY, SEPTEMBER 21, 2010 Re-create lost controlfile Here in this demo i deleted all control files and re-created using trace file. In Oracle forum OTN related to re-create controlfile, confusion between shutdown immediate and shutdown abort after controlfile lost. this demo helps you to recreate lost control file view plainprint? SQL> select name from v$controlfile; NAME -------------------------------------------------------------------------------/u01/app/oracle/oradata/rev1/control01.ctl /u01/app/oracle/oradata/rev1/control02.ctl /u01/app/oracle/oradata/rev1/control03.ctl SQL> select name from v$datafile; NAME -------------------------------------------------------------------------------/u01/app/oracle/oradata/rev1/system01.dbf /u01/app/oracle/oradata/rev1/undotbs01.dbf /u01/app/oracle/oradata/rev1/sysaux01.dbf /u01/app/oracle/oradata/rev1/users01.dbf SQL> col member format a50 SQL> select a.group#,a.member,b.status from v$logfile a, v$log b where a.group#= b.group#;

GROUP# MEMBER STATUS ---------- -------------------------------------------------- ---------------3 /u01/app/oracle/oradata/rev1/redo03.log ACTIVE 2 /u01/app/oracle/oradata/rev1/redo02.log CURRENT 1 /u01/app/oracle/oradata/rev1/redo01.log ACTIVE to create control file trace view plainprint? SQL> alter database backup controlfile to trace; Database altered. SQL> show parameter user_dump_dest NAME TYPE VALUE ------------------------------------ ----------- -----------------------------user_dump_dest p or SQL> ALTER DATABASE BACKUP CONTROLFILE TO TRACE 2 AS '/home/oracle/Desktop/create_ctl.sql'; Database altered. you can find the sample controlfile trace file in the location user_dump_dest /u 01/app/oracle/admin/rev1/udump the last recently created file. view plainprint? u01/app/oracle/admin/rev1/udump/rev1_ora_10939.trc Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production With the Partitioning and OLAP options ORACLE_HOME = /u01/app/oracle/product/10.2.0/db_1 System name: Linux Node name: rac1.localdomain Release: 2.6.9-42.0.0.0.1.ELhugemem Version: #1 SMP Sun Oct 15 14:06:18 PDT 2006 Machine: i686 Instance name: rev1 Redo thread mounted by this instance: 1 Oracle process number: 23 Unix process pid: 10939, image: oracle@rac1.localdomain (TNS V1-V3) *** SERVICE NAME:(SYS$USERS) 2010-09-21 16:52:23.473 *** SESSION ID:(142.32) 2010-09-21 16:52:23.473 *** 2010-09-21 16:52:23.472 -- The following are current System-scope REDO Log Archival related -- parameters and can be included in the database initialization file. --- LOG_ARCHIVE_DEST='' -- LOG_ARCHIVE_DUPLEX_DEST='' --- LOG_ARCHIVE_FORMAT=%t_%s_%r.dbf --- DB_UNIQUE_NAME="rev1" --- LOG_ARCHIVE_CONFIG='SEND, RECEIVE, NODG_CONFIG' string /u01/app/oracle/admin/rev1/udum

-- LOG_ARCHIVE_MAX_PROCESSES=2 -- STANDBY_FILE_MANAGEMENT=MANUAL -- STANDBY_ARCHIVE_DEST=?/dbs/arch -- FAL_CLIENT='' -- FAL_SERVER='' --- LOG_ARCHIVE_DEST_10='LOCATION=USE_DB_RECOVERY_FILE_DEST' -- LOG_ARCHIVE_DEST_10='OPTIONAL REOPEN=300 NODELAY' -- LOG_ARCHIVE_DEST_10='ARCH NOAFFIRM NOEXPEDITE NOVERIFY SYNC' -- LOG_ARCHIVE_DEST_10='REGISTER NOALTERNATE NODEPENDENCY' -- LOG_ARCHIVE_DEST_10='NOMAX_FAILURE NOQUOTA_SIZE NOQUOTA_USED NODB_UNIQUE_NAME ' -- LOG_ARCHIVE_DEST_10='VALID_FOR=(PRIMARY_ROLE,ONLINE_LOGFILES)' -- LOG_ARCHIVE_DEST_STATE_10=ENABLE --- Below are two sets of SQL statements, each of which creates a new -- control file and uses it to open the database. The first set opens -- the database with the NORESETLOGS option and should be used only if -- the current versions of all online logs are available. The second -- set opens the database with the RESETLOGS option and should be used -- if online logs are unavailable. -- The appropriate set of statements can be copied from the trace into -- a script file, edited as necessary, and executed when there is a -- need to re-create the control file. --Set #1. NORESETLOGS case --- The following commands will create a new control file and use it -- to open the database. -- Data used by Recovery Manager will be lost. -- Additional logs may be required for media recovery of offline -- Use this only if the current versions of all online logs are -- available. -- After mounting the created controlfile, the following SQL -- statement will place the database in the appropriate -- protection mode: -- ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE STARTUP NOMOUNT CREATE CONTROLFILE REUSE DATABASE "REV1" NORESETLOGS FORCE LOGGING ARCHIVELOG MAXLOGFILES 16 MAXLOGMEMBERS 3 MAXDATAFILES 100 MAXINSTANCES 8 MAXLOGHISTORY 292 LOGFILE GROUP 1 '/u01/app/oracle/oradata/rev1/redo01.log' SIZE 5M, GROUP 2 '/u01/app/oracle/oradata/rev1/redo02.log' SIZE 5M, GROUP 3 '/u01/app/oracle/oradata/rev1/redo03.log' SIZE 5M -- STANDBY LOGFILE DATAFILE '/u01/app/oracle/oradata/rev1/system01.dbf', '/u01/app/oracle/oradata/rev1/undotbs01.dbf', '/u01/app/oracle/oradata/rev1/sysaux01.dbf', '/u01/app/oracle/oradata/rev1/users01.dbf' CHARACTER SET WE8ISO8859P1 ; -- Configure RMAN configuration record 1 VARIABLE RECNO NUMBER; EXECUTE :RECNO := SYS.DBMS_BACKUP_RESTORE.SETCONFIG('CONTROLFILE AUTOBACKUP','ON ');

-- Commands to re-create incarnation table -- Below log names MUST be changed to existing filenames on -- disk. Any one log file from each branch can be used to -- re-create incarnation records. -- ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/flash_recovery_area/REV1/arc hivelog/2010_09_21/o1_mf_1_1_%u_.arc'; -- ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/flash_recovery_area/REV1/arc hivelog/2010_09_21/o1_mf_1_1_%u_.arc'; -- ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/flash_recovery_area/REV1/arc hivelog/2010_09_21/o1_mf_1_1_%u_.arc'; -- ALTER DATABASE REGISTER LOGFILE '/u01/app/oracle/flash_recovery_area/REV1/arc hivelog/2010_09_21/o1_mf_1_1_%u_.arc'; -- Recovery is required if any of the datafiles are restored backups, -- or if the last shutdown was not normal or immediate. RECOVER DATABASE -- All logs need archiving and a log switch is needed. ALTER SYSTEM ARCHIVE LOG ALL; -- Database can now be opened normally. ALTER DATABASE OPEN; -- Commands to add tempfiles to temporary tablespaces. -- Online tempfiles have complete space information. -- Other tempfiles may require adjustment. ALTER TABLESPACE TEMP ADD TEMPFILE '/u01/app/oracle/oradata/rev1/temp01.dbf' SIZE 20971520 REUSE AUTOEXTEND ON NEXT 655360 MAXSIZE 32767M; -- End of tempfile additions. copy and paste the following lines in the notepad/text editor from the above tra ce files and save it as create_ctl.sql CREATE CONTROLFILE REUSE DATABASE "REV1" RESETLOGS MAXLOGFILES 16 MAXLOGMEMBERS 3 MAXDATAFILES 100 MAXINSTANCES 8 MAXLOGHISTORY 292 LOGFILE GROUP 1 '/u01/app/oracle/oradata/rev1/redo01.log' GROUP 2 '/u01/app/oracle/oradata/rev1/redo02.log' GROUP 3 '/u01/app/oracle/oradata/rev1/redo03.log' -- STANDBY LOGFILE DATAFILE '/u01/app/oracle/oradata/rev1/system01.dbf', '/u01/app/oracle/oradata/rev1/undotbs01.dbf', '/u01/app/oracle/oradata/rev1/sysaux01.dbf', '/u01/app/oracle/oradata/rev1/users01.dbf' CHARACTER SET WE8ISO8859P1 ; FORCE LOGGING ARCHIVELOG

SIZE 5M, SIZE 5M, SIZE 5M

remove the control files(control01.ctl,control02.ctl,control03.ctl) from the loc ation /u01/app/oracle/oradata/rev1/ for testing purpose to re-create it. view plainprint? SQL> select name from v$controlfile; NAME --------------------------------------------------

/u01/app/oracle/oradata/rev1/control01.ctl /u01/app/oracle/oradata/rev1/control02.ctl /u01/app/oracle/oradata/rev1/control03.ctl SQL> host rm -rf /u01/app/oracle/oradata/rev1/control01.ctl SQL> ! rm -rf /u01/app/oracle/oradata/rev1/control02.ctl SQL> ! rm -rf /u01/app/oracle/oradata/rev1/control03.ctl SQL> shutdown immediate SQL> startup ORACLE instance started. Total System Global Area 444596224 bytes Fixed Size 1219904 bytes Variable Size 167772864 bytes Database Buffers 272629760 bytes Redo Buffers 2973696 bytes ORA-00205: error in identifying control file, check alert log for more info run the create_ctl.sql script to recreate a lost control files SQL> @/home/oracle/Desktop/create_ctl.sql Control file created. SQL> alter database open resetlogs; alter database open resetlogs * ERROR at line 1: ORA-01194: file 1 needs more recovery to be consistent ORA-01110: data file 1: '/u01/app/oracle/oradata/rev1/system01.dbf' SQL> recover database using backup controlfile until cancel; ORA-00279: change 557988 generated at 09/21/2010 16:13:51 needed for thread 1 ORA-00289: suggestion : /u01/app/oracle/flash_recovery_area/REV1/archivelog/2010_09_21/o1_mf_1_4_%u_.arc ORA-00280: change 557988 for thread 1 is in sequence #4 Specify log: {=suggested filename AUTO CANCEL} auto ORA-00308: cannot open archived log '/u01/app/oracle/flash_recovery_area/REV1/archivelog/2010_09_21/o1_mf_1_4_%u_.ar c' ORA-27037: unable to obtain file status Linux Error: 2: No such file or directory Additional information: 3 ORA-00308: cannot open archived log '/u01/app/oracle/flash_recovery_area/REV1/archivelog/2010_09_21/o1_mf_1_4_%u_.ar c' ORA-27037: unable to obtain file status Linux Error: 2: No such file or directory Additional information: 3

ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below ORA-01194: file 1 needs more recovery to be consistent ORA-01110: data file 1: '/u01/app/oracle/oradata/rev1/system01.dbf' apply the current online redolog files for recover the database here in our exam ple the current logfile is redo02.log SQL> col member format a50 SQL> select a.group#,a.member,b.status from v$logfile a, v$log b where a.group#= b.group#; GROUP# MEMBER STATUS ---------- -------------------------------------------------- ---------------3 /u01/app/oracle/oradata/rev1/redo03.log ACTIVE 2 /u01/app/oracle/oradata/rev1/redo02.log CURRENT 1 /u01/app/oracle/oradata/rev1/redo01.log ACTIVE SQL> recover database using backup controlfile until cancel; ORA-00279: change 557988 generated at 09/21/2010 16:13:51 needed for thread 1 ORA-00289: suggestion : /u01/app/oracle/flash_recovery_area/REV1/archivelog/2010_09_21/o1_mf_1_4_%u_.arc ORA-00280: change 557988 for thread 1 is in sequence #4 Specify log: {=suggested filename AUTO /u01/app/oracle/oradata/rev1/redo02.log Log applied. Media recovery complete. SQL> alter database open resetlogs; Database altered. SQL> archive log list; Database log mode Automatic archival Archive destination Oldest online log sequence Next log sequence to archive Current log sequence Archive Mode Enabled USE_DB_RECOVERY_FILE_DEST 0 1 1 CANCEL}

hope, this will helps you