Переименование базы. : Oracle

Это надо сделать в рабочей базе?
Просто эта команда не выполняется в базе которая не Open.

Это последний этап при восстановлении из онлайн-бекапа.....

до этого дойти не могу
*
ORA-00900: invalid SQL statement
SVRMGR> recover database using backup controlfile;
ORA-00279: change 601118765 generated at 10/23/2007 15:15:31 needed for thread 1

ORA-00289: suggestion : C:\ORACLES\ORANTS\RDBMS\ARC00001.001
ORA-00280: change 601118765 for thread 1 is in sequence #1
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
g:\oradata\db2000\redo01.log
ORA-00339: archived log does not contain any redo
ORA-00334: archived log: 'G:\ORADATA\DB2000\REDO01.LOG'
SVRMGR> recover database using backup controlfile;
ORA-00279: change 601118765 generated at 10/23/2007 15:15:31 needed for thread 1

ORA-00289: suggestion : C:\ORACLES\ORANTS\RDBMS\ARC00001.001
ORA-00280: change 601118765 for thread 1 is in sequence #1
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
g:\oradata\db2000\redo02.log
ORA-00339: archived log does not contain any redo
ORA-00334: archived log: 'G:\ORADATA\DB2000\REDO02.LOG'
SVRMGR> recover database using backup controlfile;
ORA-00279: change 601118765 generated at 10/23/2007 15:15:31 needed for thread 1

ORA-00289: suggestion : C:\ORACLES\ORANTS\RDBMS\ARC00001.001
ORA-00280: change 601118765 for thread 1 is in sequence #1
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
g:\oradata\db2000\redo03.log
Log applied.
Media recovery complete.
SVRMGR> alter database open;
alter database open
*
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SVRMGR> alter database open resetlogs;
alter database open resetlogs
*
ORA-03113: end-of-file on communication channel
SVRMGR> alter database open;
alter database open
*
ORA-03114: not connected to ORACLE
SVRMGR> connect internal/qqq
ORA-12571: TNS:packet writer failure
SVRMGR> connect internal/qqq
ORA-12571: TNS:packet writer failure
SVRMGR> connect internal/qqq
ORA-12571: TNS:packet writer failure
SVRMGR> connect internal/qqq
Connected.
SVRMGR> alter database open resetlogs;
alter database open resetlogs
*
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
SVRMGR> recovery
2> ;
recovery
*
ORA-00900: invalid SQL statement
SVRMGR> recover
Media recovery complete.
SVRMGR> startup open
ORA-01081: cannot start already-running ORACLE - shut it down first
SVRMGR> ALTER TABLESPACE TEMP ADD TEMPFILE 'FILESPEC'
2> ;
ALTER TABLESPACE TEMP ADD TEMPFILE 'FILESPEC'
*
ORA-01109: database not open
SVRMGR> recover until cancel;
ORA-00279: change 601138887 generated at 10/23/2007 15:23:00 needed for thread 1

ORA-00289: suggestion : C:\ORACLES\ORANTS\RDBMS\ARC00002.001
ORA-00280: change 601138887 for thread 1 is in sequence #2
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cencel
ORA-00308: cannot open archived log 'cencel'
ORA-27041: unable to open file
OSD-04002: ¤ї Є ┐│┐Р│Я¤°° │Р·│ЮРЭ │Ёv
O/S-Error: (OS 2) =х єфрхЄё эрщЄш єърчрээvщ Їрщы.
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: 'E:\ORADATA\DB2000\SYSTEM01.DBF'
SVRMGR> ALTER DATABASE CLEAR LOGFILE 'system01.dbf';
ALTER DATABASE CLEAR LOGFILE 'system01.dbf'
*
ORA-01514: error in log specification: no such log
ORA-01517: log member: 'system01.dbf'
SVRMGR> ALTER DATABASE CLEAR LOGFILE 'filename';
ALTER DATABASE CLEAR LOGFILE 'filename'
*
ORA-01514: error in log specification: no such log
ORA-01517: log member: 'filename'
SVRMGR> ALTER DATABASE CLEAR LOGFILE 'redo04.log';
ALTER DATABASE CLEAR LOGFILE 'redo04.log'
*
ORA-01514: error in log specification: no such log
ORA-01517: log member: 'redo04.log'
SVRMGR> ALTER DATABASE CLEAR LOGFILE '4';
ALTER DATABASE CLEAR LOGFILE '4'
*
ORA-01514: error in log specification: no such log
ORA-01517: log member: '4'
SVRMGR> ALTER DATABASE CLEAR LOGFILE '3';
ALTER DATABASE CLEAR LOGFILE '3'
*
ORA-01514: error in log specification: no such log
ORA-01517: log member: '3'
SVRMGR> alter database open;
alter database open
*
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SVRMGR> startup mount
ORA-01081: cannot start already-running ORACLE - shut it down first
SVRMGR> shutdown immediate
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SVRMGR> startup mount
ORACLE instance started.
Total System Global Area 874103772 bytes
Fixed Size 70620 bytes
Variable Size 167219200 bytes
Database Buffers 696320000 bytes
Redo Buffers 10493952 bytes
Database mounted.
SVRMGR> alter system clear logfile;
alter system clear logfile
*
ORA-02065: illegal option for ALTER SYSTEM
SVRMGR> recover database until cancel using backup controlfile ;
ORA-00279: change 601138887 generated at 10/23/2007 15:23:00 needed for thread 1

ORA-00289: suggestion : C:\ORACLES\ORANTS\RDBMS\ARC00002.001
ORA-00280: change 601138887 for thread 1 is in sequence #2
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
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: 'E:\ORADATA\DB2000\SYSTEM01.DBF'
SVRMGR> alter database open resetlogs;
alter database open resetlogs
*
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: 'E:\ORADATA\DB2000\SYSTEM01.DBF'
SVRMGR> recover data
ORA-00274: illegal recovery option DATA
SVRMGR> recover
ORA-00283: recovery session canceled due to errors
ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
SVRMGR> recover database until cancel using backup controlfile ;
ORA-00279: change 601138887 generated at 10/23/2007 15:23:00 needed for thread 1

ORA-00289: suggestion : C:\ORACLES\ORANTS\RDBMS\ARC00002.001
ORA-00280: change 601138887 for thread 1 is in sequence #2
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
2
ORA-00308: cannot open archived log '2'
ORA-27041: unable to open file
OSD-04002: ¤ї Є ┐│┐Р│Я¤°° │Р·│ЮРЭ │Ёv
O/S-Error: (OS 2) =х єфрхЄё эрщЄш єърчрээvщ Їрщы.
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: 'E:\ORADATA\DB2000\SYSTEM01.DBF'
SVRMGR> recover database until cancel using backup controlfile ;
ORA-00279: change 601138887 generated at 10/23/2007 15:23:00 needed for thread 1

ORA-00289: suggestion : C:\ORACLES\ORANTS\RDBMS\ARC00002.001
ORA-00280: change 601138887 for thread 1 is in sequence #2
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
g:\oradata\db2000\redo02.log
ORA-00339: archived log does not contain any redo
ORA-00334: archived log: 'G:\ORADATA\DB2000\REDO02.LOG'
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: 'E:\ORADATA\DB2000\SYSTEM01.DBF'
SVRMGR> recover database using backup controlfile;
ORA-00279: change 601138887 generated at 10/23/2007 15:23:00 needed for thread 1

ORA-00289: suggestion : C:\ORACLES\ORANTS\RDBMS\ARC00002.001
ORA-00280: change 601138887 for thread 1 is in sequence #2
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
g:\oradata\db2000\redo03.log
ORA-00310: archived log contains sequence 1; sequence 2 required
ORA-00334: archived log: 'G:\ORADATA\DB2000\REDO03.LOG'
SVRMGR> recover database using backup controlfile;
ORA-00279: change 601138887 generated at 10/23/2007 15:23:00 needed for thread 1

ORA-00289: suggestion : C:\ORACLES\ORANTS\RDBMS\ARC00002.001
ORA-00280: change 601138887 for thread 1 is in sequence #2
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
g:\oradata\db2000\redo04.log
ORA-00310: archived log contains sequence 749433; sequence 2 required
ORA-00334: archived log: 'G:\ORADATA\DB2000\REDO04.LOG'
SVRMGR> recover database using backup controlfile;
ORA-00279: change 601138887 generated at 10/23/2007 15:23:00 needed for thread 1

ORA-00289: suggestion : C:\ORACLES\ORANTS\RDBMS\ARC00002.001
ORA-00280: change 601138887 for thread 1 is in sequence #2
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
g:\oradata\db2000\redo05.log
ORA-00310: archived log contains sequence 749434; sequence 2 required
ORA-00334: archived log: 'G:\ORADATA\DB2000\REDO05.LOG'
SVRMGR> g:\oradata\db2000\redo06.log
2> ;
g:\oradata\db2000\redo06.log
*
ORA-00900: invalid SQL statement
SVRMGR> recover database using backup controlfile;
ORA-00279: change 601138887 generated at 10/23/2007 15:23:00 needed for thread 1

ORA-00289: suggestion : C:\ORACLES\ORANTS\RDBMS\ARC00002.001
ORA-00280: change 601138887 for thread 1 is in sequence #2
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
g:\oradata\db2000\redo06.log
ORA-00310: archived log contains sequence 749435; sequence 2 required
ORA-00334: archived log: 'G:\ORADATA\DB2000\REDO06.LOG'
SVRMGR> recover database using backup controlfile;
ORA-00279: change 601138887 generated at 10/23/2007 15:23:00 needed for thread 1

ORA-00289: suggestion : C:\ORACLES\ORANTS\RDBMS\ARC00002.001
ORA-00280: change 601138887 for thread 1 is in sequence #2
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
g:\oradata\db2000\redo07.log
ORA-00310: archived log contains sequence 749431; sequence 2 required
ORA-00334: archived log: 'G:\ORADATA\DB2000\REDO07.LOG'
SVRMGR> recover database using backup controlfile;
ORA-00279: change 601138887 generated at 10/23/2007 15:23:00 needed for thread 1

ORA-00289: suggestion : C:\ORACLES\ORANTS\RDBMS\ARC00002.001
ORA-00280: change 601138887 for thread 1 is in sequence #2
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
g:\oradata\db2000\redo08.log
ORA-00310: archived log contains sequence 749432; sequence 2 required
ORA-00334: archived log: 'G:\ORADATA\DB2000\REDO08.LOG'
SVRMGR> g:\oradata\db2000\redo09.log
2> ;
g:\oradata\db2000\redo09.log
*
ORA-00900: invalid SQL statement
SVRMGR> recover database using backup controlfile;
ORA-00279: change 601138887 generated at 10/23/2007 15:23:00 needed for thread 1

ORA-00289: suggestion : C:\ORACLES\ORANTS\RDBMS\ARC00002.001
ORA-00280: change 601138887 for thread 1 is in sequence #2
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
g:\oradata\db2000\redo08.log
ORA-00310: archived log contains sequence 749432; sequence 2 required
ORA-00334: archived log: 'G:\ORADATA\DB2000\REDO08.LOG'
SVRMGR> recover database using backup controlfile;
ORA-00279: change 601138887 generated at 10/23/2007 15:23:00 needed for thread 1

ORA-00289: suggestion : C:\ORACLES\ORANTS\RDBMS\ARC00002.001
ORA-00280: change 601138887 for thread 1 is in sequence #2
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
g:\oradata\db2000\redo09.log
ORA-00310: archived log contains sequence 749429; sequence 2 required
ORA-00334: archived log: 'G:\ORADATA\DB2000\REDO09.LOG'
SVRMGR> g:\oradata\db2000\redo10.log
2> ;
g:\oradata\db2000\redo10.log
*
ORA-00900: invalid SQL statement
SVRMGR> recover database using backup controlfile;
ORA-00279: change 601138887 generated at 10/23/2007 15:23:00 needed for thread 1

ORA-00289: suggestion : C:\ORACLES\ORANTS\RDBMS\ARC00002.001
ORA-00280: change 601138887 for thread 1 is in sequence #2
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
g:\oradata\db2000\redo10.log
ORA-00310: archived log contains sequence 749430; sequence 2 required
ORA-00334: archived log: 'G:\ORADATA\DB2000\REDO10.LOG'
SVRMGR> recover database using backup controlfile;
ORA-00279: change 601138887 generated at 10/23/2007 15:23:00 needed for thread 1

ORA-00289: suggestion : C:\ORACLES\ORANTS\RDBMS\ARC00002.001
ORA-00280: change 601138887 for thread 1 is in sequence #2
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
g:\oradata\db2000\redo01.log
Log applied.
Media recovery complete.
SVRMGR> alter database open;
alter database open
*
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SVRMGR> _allow_resetlogs_corruption=true
2> ;
_allow_resetlogs_corruption=true
*
ORA-00911: invalid character
SVRMGR> _allow_resetlogs_corruption=true
2> startup mount
3> ;
_allow_resetlogs_corruption=true
*
ORA-00911: invalid character
SVRMGR> allow_resetlogs_corruption=true
2> ;
allow_resetlogs_corruption=true
*
ORA-00900: invalid SQL statement
SVRMGR> allow_resetlogs_corruption=true

Без обид, но это похоже на певоапрельский розыгрыш :)
Судя по "g:\oradata\db2000\redo03.log" - у тебя холодный бекап а ты его пытаешься восстановить... Просто запустить базу то не получается?

вообще-то это надо в ini-файле прописать.
_allow_resetlogs_corruption=true

после этого рестартануть базу.

сделал не помогло

У меня давно есть подозрения, что это холодный бэкап он делает "нагорячую", не останавливая базу...
Просто что-то часто он пытается базу из бэкапа поднять...

Судя по твоему логу,

Нет не хочет.
В конце выдала что надо контралы пересоздать . Пересоздал и опять все сначала.

Автору на выбор предлагаю 3 ссылки:
[ ➜ ]



Так как проблема не касается продакшн сервера: тему можно закрывать.