Oracle control file is damaged Solution
A failure: loss ( damage) a control file
前台报错：ORA-00205：error in identifying control file,check alert log for more info
:( solutions and clean or cleaner way to close the database)
With a normal copy control file ( replace) Rename missing ( corrupted) a control file;
Failure II: two control file versions are inconsistent
(1) a normal control file, the control file is derived from another control file backup or other databases of the other;
前台报错：ORA-00214:control file '/../../control01.ctl' version xxx inconsistent with file '/../../control02.ctl' version yyy;
:( solutions and clean or cleaner way to close the database)
Replacing the lower version control file high version control file;
(2) two control files are backed up from different times ( all lower than the current version) ;
前台报错：ORA-00214:control file '/../../control01.ctl' version xxx inconsistent with file '/../../control02.ctl' version yyy;
ORA-01207:file is more recent than control file - old control file
Solution :( a clean way to shut down the database)
Replace high-low version of the control file version control file, you can normally mount the database, but can not open the database, you need to create a control file (alter database backup to trace as ' \ .. \ .. \ cc.tcl') manual , regenerate control document (NORESETLOGS mode) , then normal open database;
Solution :( uncleaned way to close the database)
Non-Clean Shutdown ( database abnormal power failure) , the need to restore the database starts medium (Recover Database) , you can open the database after a successful recovery normal;
Failure three: two control files all the damage, non-current log file is missing ( or damaged)
报错：ORA-00205：error in identifying control file,check alert log for more info
Solution :( a clean way to shut down the database)
Because of the log file is missing, NORESETLOGS to manually create a control file when an error, only to RESETLOGS way to create a control file; create a control file after the success of the database automatically Mount , execute alter database open resetlogs; you can start the database normally;
Solution :( uncleaned way to close the database)
If you are not a clean way before the database (abort / off) off, open resetlogs need media recovery before the database,
recover database using backup controlfie;
Since resetlogs create a control file mode, causing the log sequence number to start again, it does not automatically use the current log file when automatic recovery, you need to manually specify a specific log file;
例如：D:\app_10.2.0.4\chen_datafile\redo01.log或D:\app_10.2.0.4\chen_datafile\redo03.log
Media recovery, media recovery after the success can alter database open resetlogs by way of open database;
Troubleshooting four: two control files all the damage, the current log file is missing ( or damaged)
报错：ORA-00205：error in identifying control file,check alert log for more info
solution:
( A clean way to close the database)
Because of the log file is missing, NORESETLOGS to manually create a control file when an error, only to RESETLOGS way to create a control file; create a control file after the success of the database automatically Mount , execute alter database open resetlogs; you can start the database normally;
solution:
( Uncleaned way to close the database)
If you are not a clean way before the database (abort / off) off, open resetlogs need media recovery before the database,
recover database using backup controlfie;
Since resetlogs create a control file mode, causing the log sequence number to start again, it does not automatically use the current log file when automatic recovery, you need to manually specify a specific log file;
例如：D:\app_10.2.0.4\chen_datafile\redo01.log或D:\app_10.2.0.4\chen_datafile\redo03.log
Media recovery, but the database media recovery required information in the current log file is lost, resulting in failure recovery media, only through the implicit parameter "* ._ allow_resetlogs_corruption = true" ( alter system set "_allow_resetlogs_corruption" = true scope = spfile;) skip the consistency check, in order to open resetlogs database;
Which _allow_resetlogs_corruption parameters may trigger more ORA-600 error;
(1) error-00600 ORA: Internal error code, arguments: [2662] , by _minimum_giga_scn skip this BUG ;
(2) error-00600 ORA: Internal error code, arguments: [kdsgrp1] , the specific reason to view the trace file, in this case by the undo managed by the automatic mode to manual, skip this BUG ;
*.undo_tablespace=SYSTEM
*.undo_management=MANUAL
Specific troubleshooting process is as follows:
A failure: loss ( damage) a control file
前台报错：ORA-00205：error in identifying control file,check alert log for more info
Solution: Use good control file copy ( replace) Rename loss ( damage) of the control file;
--- by deleting the control file control02.ctl missing analog control file
Sun May 29 14:56:12 2016
ALTER DATABASE MOUNT
ORA-00210: cannot open the specified control file
ORA-00202: control file: 'D:\APP_10.2.0.4\CHEN_DATAFILE\CONTROL02.CTL'
ORA-27041: unable to open file
OSD-04002: Can not open file
O / S-Error: (OS 2) The system can not find the file specified.
ORA-205 signalled during: ALTER DATABASE MOUNT...
Sun May 29 14:56:12 2016
MMNL started with pid=16, OS id=2476
--- alert_orcl.log alert log
--- by text editing binary control file control02.ctl damage the analog control file
Sun May 29 16:35:03 2016
ALTER DATABASE MOUNT
ORA-00210: cannot open the specified control file
ORA-00202: control file: 'D:\APP_10.2.0.4\CHEN_DATAFILE\CONTROL01.CTL'
ORA-27046: file size is not a multiple of logical block size
OSD-04012: file sizes do not match (OS 12763140)
ORA-205 signalled during: ALTER DATABASE MOUNT...
Solution: restore control file with another
Failure II: two control file versions are inconsistent
(1) a normal control file, the control file is derived from another control file backup or other databases of the other;
前台报错：ORA-00214:control file '/../../control01.ctl' version xxx inconsistent with file '/../../control02.ctl' version yyy;
Solution: Replace the low version of the control file high version of the control file;
The case can be control02.ctl control file copy rename control01.ctl control01.ctl replace the original file;
(2) two control files are backed up from different times;
前台报错：ORA-00214:control file '/../../control01.ctl' version xxx inconsistent with file '/../../control02.ctl' version yyy;
ORA-01207:file is more recent than control file - old control file
Solution: Replace with a high-low version of the control file version control file, you can normally mount the database, but can not open the database, you need to manually create a control file (alter database backup to trace as' \ .. \ .. \ cc.tcl ') , regenerated control document (NORESETLOGS mode) , then normal open database;
controlfile1版本号较高，用controlfile1重命名controlfile2替换原controfile2文件；
Sun May 29 15:12:45 2016
Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\orcl\orcl\trace\orcl_m000_9636.trc:
ORA-00338: log 1 of thread 1 is more recent than control file
ORA-00312: online log 1 thread 1: 'D:\APP_10.2.0.4\CHEN_DATAFILE\REDO01A.LOG'
ORA-00338: log 1 of thread 1 is more recent than control file
ORA-00312: online log 1 thread 1: 'D:\APP_10.2.0.4\CHEN_DATAFILE\REDO01.LOG'
解决方案：重建控制文件
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "ORCL" NORESETLOGS NOARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 2337
LOGFILE
GROUP 1 (
'D:\APP_10.2.0.4\CHEN_DATAFILE\REDO01.LOG',
'D:\APP_10.2.0.4\CHEN_DATAFILE\REDO01A.LOG'
) SIZE 50M BLOCKSIZE 512,
GROUP 2 'D:\APP_10.2.0.4\CHEN_DATAFILE\REDO02.LOG' SIZE 50M BLOCKSIZE 512,
GROUP 3 'D:\APP_10.2.0.4\CHEN_DATAFILE\REDO03.LOG' SIZE 50M BLOCKSIZE 512
DATAFILE
'D:\APP_10.2.0.4\CHEN_DATAFILE\SYSTEM01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\SYSAUX01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\UNDOTBS01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\USERS01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\EXAMPLE01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\CHEN01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_DATA01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_INDEX01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_DATA02.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\CHEN02.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_INDEX02.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\MHWZ01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_DATA02A.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\ISM01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_DATA01A.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_INDEX01A.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\UNDOTBS01A.DBF'
CHARACTER SET ZHS16GBK
;
使用resetlogs，将导致redo logs里的内容丢失，并且所有的备份失效，当redo logs 损坏或从备份恢复控制文件的情况下，才使用resetlogs模式。通常情况下重建控制文件最好采用noresetlogs方式；
非干净关闭(数据库异常断电)，数据库启动是需要介质恢复(recover database)，恢复成功后可以正常打开数据库；
Sun May 29 15:42:59 2016
ALTER DATABASE MOUNT
ORA-00210: cannot open the specified control file
ORA-00202: control file: 'D:\APP_10.2.0.4\CHEN_DATAFILE\CONTROL02.CTL'
ORA-27046: file size is not a multiple of logical block size
OSD-04012: 文件大小不匹配 (OS 12763144)
ORA-00210: cannot open the specified control file
ORA-00202: control file: 'D:\APP_10.2.0.4\CHEN_DATAFILE\CONTROL01.CTL'
ORA-27046: file size is not a multiple of logical block size
OSD-04012: 文件大小不匹配 (OS 12763144)
ORA-205 signalled during: ALTER DATABASE MOUNT...
重建控制文件
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "ORCL" NORESETLOGS NOARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 2337
LOGFILE
GROUP 1 (
'D:\APP_10.2.0.4\CHEN_DATAFILE\REDO01.LOG',
'D:\APP_10.2.0.4\CHEN_DATAFILE\REDO01A.LOG'
) SIZE 50M BLOCKSIZE 512,
GROUP 2 'D:\APP_10.2.0.4\CHEN_DATAFILE\REDO02.LOG' SIZE 50M BLOCKSIZE 512,
GROUP 3 'D:\APP_10.2.0.4\CHEN_DATAFILE\REDO03.LOG' SIZE 50M BLOCKSIZE 512
DATAFILE
'D:\APP_10.2.0.4\CHEN_DATAFILE\SYSTEM01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\SYSAUX01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\UNDOTBS01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\USERS01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\EXAMPLE01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\CHEN01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_DATA01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_INDEX01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_DATA02.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\CHEN02.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_INDEX02.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\MHWZ01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_DATA02A.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\ISM01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_DATA01A.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_INDEX01A.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\UNDOTBS01A.DBF'
CHARACTER SET ZHS16GBK
;
故障三：两个控制文件全部损坏，非当前日志文件丢失(或损坏)
报错：ORA-00205：error in identifying control file,check alert log for more info
解决方案：因为有日志文件丢失，以NORESETLOGS方式手动创建控制文件时报错，只能以RESETLOGS方式创建控制文件；创建控制文件成功后，数据库自动mount，如果数据库之前是以干净的方式(immediate/normal)关闭的，执行alter database open resetlogs;可以正常启动数据库；
如果数据库之前是以不干净的方式(abort/断电)关闭的，open resetlogs数据库之前需要进行介质恢复，
recover database using backup controlfie;
由于resetlogs方式创建控制文件，导致日志序列号重新开始，自动恢复时不会自动使用当前日志文件，需要手动指定具体的日志文件；
例如：D:\app_10.2.0.4\chen_datafile\redo01.log或D:\app_10.2.0.4\chen_datafile\redo03.log
进行介质恢复，介质恢复成功后可以通过alter database open resetlogs方式open数据库；
编辑损坏两个控制文件，删除非当前日志文件redo03.log
Sun May 29 16:40:55 2016
ALTER DATABASE MOUNT
ORA-00210: cannot open the specified control file
ORA-00202: control file: 'D:\APP_10.2.0.4\CHEN_DATAFILE\CONTROL02.CTL'
ORA-27046: file size is not a multiple of logical block size
OSD-04012: 文件大小不匹配 (OS 12763144)
ORA-00210: cannot open the specified control file
ORA-00202: control file: 'D:\APP_10.2.0.4\CHEN_DATAFILE\CONTROL01.CTL'
ORA-27046: file size is not a multiple of logical block size
OSD-04012: 文件大小不匹配 (OS 12763144)
ORA-205 signalled during: ALTER DATABASE MOUNT...
Sun May 29 16:40:55 2016
MMNL started with pid=16, OS id=10652
手动创建控制文件(NORESETLOGS)
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "ORCL" NORESETLOGS NOARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 2337
LOGFILE
GROUP 1 (
'D:\APP_10.2.0.4\CHEN_DATAFILE\REDO01.LOG',
'D:\APP_10.2.0.4\CHEN_DATAFILE\REDO01A.LOG'
) SIZE 50M BLOCKSIZE 512,
GROUP 2 'D:\APP_10.2.0.4\CHEN_DATAFILE\REDO02.LOG' SIZE 50M BLOCKSIZE 512,
GROUP 3 'D:\APP_10.2.0.4\CHEN_DATAFILE\REDO03.LOG' SIZE 50M BLOCKSIZE 512
DATAFILE
'D:\APP_10.2.0.4\CHEN_DATAFILE\SYSTEM01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\SYSAUX01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\UNDOTBS01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\USERS01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\EXAMPLE01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\CHEN01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_DATA01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_INDEX01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_DATA02.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\CHEN02.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_INDEX02.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\MHWZ01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_DATA02A.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\ISM01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_DATA01A.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_INDEX01A.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\UNDOTBS01A.DBF'
CHARACTER SET ZHS16GBK
;
Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\orcl\orcl\trace\orcl_ora_7516.trc:
ORA-01565: error in identifying file 'D:\APP_10.2.0.4\CHEN_DATAFILE\REDO03.LOG'
ORA-27041: unable to open file
OSD-04002: 无法打开文件
O/S-Error: (OS 2) 系统找不到指定的文件。
ORA-1503 signalled during: CREATE CONTROLFILE REUSE DATABASE "ORCL" NORESETLOGS NOARCHIVELOG
手动创建控制文件(RESETLOGS)
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "ORCL" RESETLOGS NOARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 2337
LOGFILE
GROUP 1 (
'D:\APP_10.2.0.4\CHEN_DATAFILE\REDO01.LOG',
'D:\APP_10.2.0.4\CHEN_DATAFILE\REDO01A.LOG'
) SIZE 50M BLOCKSIZE 512,
GROUP 2 'D:\APP_10.2.0.4\CHEN_DATAFILE\REDO02.LOG' SIZE 50M BLOCKSIZE 512,
GROUP 3 'D:\APP_10.2.0.4\CHEN_DATAFILE\REDO03.LOG' SIZE 50M BLOCKSIZE 512
DATAFILE
'D:\APP_10.2.0.4\CHEN_DATAFILE\SYSTEM01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\SYSAUX01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\UNDOTBS01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\USERS01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\EXAMPLE01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\CHEN01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_DATA01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_INDEX01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_DATA02.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\CHEN02.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_INDEX02.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\MHWZ01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_DATA02A.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\ISM01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_DATA01A.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_INDEX01A.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\UNDOTBS01A.DBF'
CHARACTER SET ZHS16GBK
;
故障四：两个控制文件全部损坏，当前日志文件丢失(或损坏)
报错：ORA-00205：error in identifying control file,check alert log for more info
解决方案：因为有日志文件丢失，以NORESETLOGS方式手动创建控制文件时报错，只能以RESETLOGS方式创建控制文件；创建控制文件成功后，数据库自动mount，如果数据库之前是以干净的方式(immediate/normal)关闭的，执行alter database open resetlogs;可以正常启动数据库；
如果数据库之前是以不干净的方式(abort/断电)关闭的，open resetlogs数据库之前需要进行介质恢复，
recover database using backup controlfie;
由于resetlogs方式创建控制文件，导致日志序列号重新开始，自动恢复时不会自动使用当前日志文件，需要手动指定具体的日志文件；
例如：D:\app_10.2.0.4\chen_datafile\redo01.log或D:\app_10.2.0.4\chen_datafile\redo03.log
进行介质恢复，但是数据库介质恢复所需的信息保存在丢失的当前日志文件中，导致介质恢复失败，只能通过隐含参数"*._allow_resetlogs_corruption=true"(alter system set "_allow_resetlogs_corruption"=true scope=spfile;)跳过一致性检查，才能open resetlogs数据库；
其中_allow_resetlogs_corruption参数可能会触发多个ORA-600错误；
(1)报错ORA-00600: internal error code, arguments: [2662]，可通过_minimum_giga_scn跳过此BUG；
(2)报错ORA-00600: internal error code, arguments: [kdsgrp1]，具体原因需要查看trace文件，本次案例可以通过将undo管理方式由自动改成手动，跳过此BUG；
*.undo_tablespace=SYSTEM
*.undo_management=MANUAL
故障：两个控制文件全部损坏，当前日志文件丢失(或损坏)
解决方案：
Sun May 29 20:00:47 2016
ALTER DATABASE MOUNT
ORA-00210: cannot open the specified control file
ORA-00202: control file: 'D:\APP_10.2.0.4\CHEN_DATAFILE\CONTROL02.CTL'
ORA-27046: file size is not a multiple of logical block size
OSD-04012: 文件大小不匹配 (OS 12763139)
ORA-00210: cannot open the specified control file
ORA-00202: control file: 'D:\APP_10.2.0.4\CHEN_DATAFILE\CONTROL01.CTL'
ORA-27046: file size is not a multiple of logical block size
OSD-04012: 文件大小不匹配 (OS 12763140)
ORA-205 signalled during: ALTER DATABASE MOUNT...
---手动创建控制文件(NORESETLOGS)
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "ORCL" NORESETLOGS NOARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 2337
LOGFILE
GROUP 1 (
'D:\APP_10.2.0.4\CHEN_DATAFILE\REDO01.LOG',
'D:\APP_10.2.0.4\CHEN_DATAFILE\REDO01A.LOG'
) SIZE 50M BLOCKSIZE 512,
GROUP 2 'D:\APP_10.2.0.4\CHEN_DATAFILE\REDO02.LOG' SIZE 50M BLOCKSIZE 512,
GROUP 3 'D:\APP_10.2.0.4\CHEN_DATAFILE\REDO03.LOG' SIZE 50M BLOCKSIZE 512
DATAFILE
'D:\APP_10.2.0.4\CHEN_DATAFILE\SYSTEM01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\SYSAUX01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\UNDOTBS01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\USERS01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\EXAMPLE01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\CHEN01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_DATA01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_INDEX01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_DATA02.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\CHEN02.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_INDEX02.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\MHWZ01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_DATA02A.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\ISM01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_DATA01A.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_INDEX01A.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\UNDOTBS01A.DBF'
CHARACTER SET ZHS16GBK
;
---手动创建控制文件(RESETLOGS)
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "ORCL" RESETLOGS NOARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 2337
LOGFILE
GROUP 1 (
'D:\APP_10.2.0.4\CHEN_DATAFILE\REDO01.LOG',
'D:\APP_10.2.0.4\CHEN_DATAFILE\REDO01A.LOG'
) SIZE 50M BLOCKSIZE 512,
GROUP 2 'D:\APP_10.2.0.4\CHEN_DATAFILE\REDO02.LOG' SIZE 50M BLOCKSIZE 512,
GROUP 3 'D:\APP_10.2.0.4\CHEN_DATAFILE\REDO03.LOG' SIZE 50M BLOCKSIZE 512
DATAFILE
'D:\APP_10.2.0.4\CHEN_DATAFILE\SYSTEM01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\SYSAUX01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\UNDOTBS01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\USERS01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\EXAMPLE01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\CHEN01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_DATA01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_INDEX01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_DATA02.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\CHEN02.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_INDEX02.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\MHWZ01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_DATA02A.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\ISM01.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_DATA01A.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\NNC_INDEX01A.DBF',
'D:\APP_10.2.0.4\CHEN_DATAFILE\UNDOTBS01A.DBF'
CHARACTER SET ZHS16GBK
;
---Windows环境下，如果cmd中存在"?"，乱码问题，可以设置客户端字符集
或者set NLS_LANG=SIMPLIFIED CHINESE_CHINA.ZHS16GBK
转载自：
http://blog.itpub.net/29785807/viewspace-2108945/