Shulou(Shulou.com)06/01 Report--

Oracle Control File damage solution

Fault 1: lost (corrupted) a control file

Front desk error report: ORA-00205:error in identifying control file,check alert log for more info

Solution: (clean or non-clean way to close the database)

Use intact control files to copy (replace) rename missing (corrupted) control files

Fault 2: the versions of the two control files are not consistent

(1) one control file is normal, and the other control file comes from other backup or other database control files.

The front desk reported an error: ORA-00214:control file'/.. /.. / control01.ctl' version xxx inconsistent with file'/.. /.. / control02.ctl' version yyy

Solution: (clean or non-clean way to close the database)

Replace the lower version of the control file with the higher version

(2) both control files are backups from different times (both are lower than the current version)

The front desk reported an error: 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: (shut down the database cleanly)

Replace the lower version of the control file with the high version of the control file, then the mount database can be normal, but the database cannot be open. You need to manually create the control file (alter database backup to trace as'..\..\ cc.tcl'), regenerate the control file (noresetlogs mode), and then you can normal the open database.

Solution: (shut down the database in a non-clean way)

Non-clean shutdown (abnormal power outage of the database). Media recovery (recover database) is required when the database is started. After a successful recovery, the database can be opened normally.

Fault 3: both control files are corrupted, non-current log files are missing (or corrupted)

Error report: ORA-00205:error in identifying control file,check alert log for more info

Solution: (shut down the database cleanly)

Because a log file is missing, an error is reported when manually creating the control file in NORESETLOGS mode, and the control file can only be created in RESETLOGS mode; after the control file is created successfully, the database automatically mount, and the database can be started normally by executing alter database open resetlogs;

Solution: (shut down the database in a non-clean way)

If the database was previously shut down in an unclean manner (abort/ power outage), the open resetlogs database needs to be media restored before.

Recover database using backup controlfie

Because the control file is created by resetlogs, the log sequence number starts again, and the current log file is not automatically used in automatic recovery. You need to specify the specific log file manually.

For example: d:\ app_10.2.0.4\ chen_datafile\ redo01.log or D:\ app_10.2.0.4\ chen_datafile\ redo03.log

Perform media recovery. After the media recovery is successful, you can open the database through alter database open resetlogs.

Fault 4: both control files are corrupted and the current log file is missing (or corrupted)

Error report: ORA-00205:error in identifying control file,check alert log for more info

Solution:

(close the database in a clean way)

Because a log file is missing, an error is reported when manually creating the control file in NORESETLOGS mode, and the control file can only be created in RESETLOGS mode; after the control file is created successfully, the database automatically mount, and the database can be started normally by executing alter database open resetlogs;

Solution:

(shut down the database in a non-clean way)

If the database was previously shut down in an unclean manner (abort/ power outage), the open resetlogs database needs to be media restored before.

Recover database using backup controlfie

Because the control file is created by resetlogs, the log sequence number starts again, and the current log file is not automatically used in automatic recovery. You need to specify the specific log file manually.

For example: d:\ app_10.2.0.4\ chen_datafile\ redo01.log or D:\ app_10.2.0.4\ chen_datafile\ redo03.log

Media recovery is performed, but the information needed for the database media recovery is saved in the missing current log file, which causes the media recovery to fail. The consistency check can only be skipped through the implicit parameter "*. _ allow_resetlogs_corruption=true" (alter system set "_ allow_resetlogs_corruption" = true scope=spfile;) to open resetlogs the database.

Where the _ allow_resetlogs_corruption parameter may trigger multiple ORA-600 errors

(1) ORA-00600: internal error code, arguments: [2662] is reported. You can skip this BUG via _ minimum_giga_scn

(2) ORA-00600: internal error code, arguments: [kdsgrp1] is reported. For the specific reason, you need to check the trace file. In this case, you can skip this BUG by changing the undo management method from automatic to manual.

* .undo_tablespace=SYSTEM

* .undo_management=MANUAL

The specific process of solving the fault is as follows:

Fault 1: lost (corrupted) a control file

Front desk error report: ORA-00205:error in identifying control file,check alert log for more info

Solution: use intact control files to copy (replace) rename missing (corrupted) control files

-Control file loss by deleting control file control02.ctl simulation

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: unable to open file

O/S-Error: (OS 2) the system cannot find the specified file.

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 warning log

-text editing binary control file control02.ctl simulation control file corruption

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 size mismatch (OS 12763140)

ORA-205 signalled during: ALTER DATABASE MOUNT...

Solution: restore with another control file

Fault 2: the versions of the two control files are not consistent

(1) one control file is normal, and the other control file comes from other backup or other database control files.

The front desk reported an error: ORA-00214:control file'/.. /.. / control01.ctl' version xxx inconsistent with file'/.. /.. / control02.ctl' version yyy

Solution: replace low-version control files with high-version control files

In this case, the control02.ctl control file can be copied and renamed control01.ctl to replace the original control01.ctl file.

(2) the two control files are backed up at different times.

The front desk reported an error: 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 the lower version of the control file with the high version of the control file, then the mount database can be normal, but the database cannot be open. You need to manually create the control file (alter database backup to trace as'..\..\ cc.tcl'), regenerate the control file (noresetlogs mode), and then you can normal open database.

Controlfile1 version number is higher, replace the original controfile2 file with controlfile1 renamed controlfile2

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'

Solution: rebuild the control file

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

Using resetlogs will result in loss of content in redo logs and invalidation of all backups, using resetlogs mode only if the redo logs is corrupted or the control file is restored from the backup. In general, it is best to use noresetlogs to reconstruct control files.

Non-clean shutdown (abnormal power outage of the database). Media recovery (recover database) is required to start the database. After a successful recovery, the database can be opened normally.

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: file size mismatch (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: file size mismatch (OS 12763144)

ORA-205 signalled during: ALTER DATABASE MOUNT...

Rebuild control file

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

Fault 3: both control files are corrupted, non-current log files are missing (or corrupted)

Error report: ORA-00205:error in identifying control file,check alert log for more info

Solution: because a log file is missing, an error is reported when manually creating the control file in NORESETLOGS mode, and the control file can only be created in RESETLOGS mode; after the successful creation of the control file, the database automatically mount, if the database was closed in a clean way (immediate/normal), execute alter database open resetlogs; to start the database normally

If the database was previously shut down in an unclean manner (abort/ power outage), the open resetlogs database needs to be media restored before.

Recover database using backup controlfie

Because the control file is created by resetlogs, the log sequence number starts again, and the current log file is not automatically used in automatic recovery. You need to specify the specific log file manually.

For example: d:\ app_10.2.0.4\ chen_datafile\ redo01.log or D:\ app_10.2.0.4\ chen_datafile\ redo03.log

Perform media recovery. After the media recovery is successful, you can open the database through alter database open resetlogs.

Editing corrupts two control files and deletes non-current log files 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: file size mismatch (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: file size mismatch (OS 12763144)

ORA-205 signalled during: ALTER DATABASE MOUNT...

Sun May 29 16:40:55 2016

MMNL started with pid=16, OS id=10652

Manually create a control file (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: unable to open file

O/S-Error: (OS 2) the system cannot find the specified file.

ORA-1503 signalled during: CREATE CONTROLFILE REUSE DATABASE "ORCL" NORESETLOGS NOARCHIVELOG

Manually create a control file (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

Fault 4: both control files are corrupted and the current log file is missing (or corrupted)

Error report: ORA-00205:error in identifying control file,check alert log for more info

Solution: because a log file is missing, an error is reported when manually creating the control file in NORESETLOGS mode, and the control file can only be created in RESETLOGS mode; after the successful creation of the control file, the database automatically mount, if the database was closed in a clean way (immediate/normal), execute alter database open resetlogs; to start the database normally

If the database was previously shut down in an unclean manner (abort/ power outage), the open resetlogs database needs to be media restored before.

Recover database using backup controlfie

Because the control file is created by resetlogs, the log sequence number starts again, and the current log file is not automatically used in automatic recovery. You need to specify the specific log file manually.

For example: d:\ app_10.2.0.4\ chen_datafile\ redo01.log or D:\ app_10.2.0.4\ chen_datafile\ redo03.log

Media recovery is performed, but the information needed for the database media recovery is saved in the missing current log file, which causes the media recovery to fail. The consistency check can only be skipped through the implicit parameter "*. _ allow_resetlogs_corruption=true" (alter system set "_ allow_resetlogs_corruption" = true scope=spfile;) to open resetlogs the database.

Where the _ allow_resetlogs_corruption parameter may trigger multiple ORA-600 errors

(1) ORA-00600: internal error code, arguments: [2662] is reported. You can skip this BUG via _ minimum_giga_scn

(2) ORA-00600: internal error code, arguments: [kdsgrp1] is reported. For the specific reason, you need to check the trace file. In this case, you can skip this BUG by changing the undo management method from automatic to manual.

* .undo_tablespace=SYSTEM

* .undo_management=MANUAL

Failure: both control files are corrupted and the current log file is missing (or corrupted)

Solution:

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: file size mismatch (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: file size mismatch (OS 12763140)

ORA-205 signalled during: ALTER DATABASE MOUNT...

-manually create a control file (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

-manually create a control file (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

-in Windows environment, if there is a "?" and garbled code problem in cmd, you can set the client character set.

Or set NLS_LANG=SIMPLIFIED CHINESE_CHINA.ZHS16GBK.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.