Все технические форумы на одном сайте Удобный поиск информации с популярных форумов в одном месте
Вопрос: Ошибка при RMAN duplicate target database for standby from active database

Подскажите, плиз, не могу понять в чем проблема:
+
RMAN> run
2> {
3> duplicate target database for standby
4>    FROM ACTIVE DATABASE
5>    DORECOVER
6>    SPFILE
7>    set db_unique_name='TMDSTB2'
8>    set fal_client='TMDSTB2'
9>    set fal_server='TMDLIVE','TMDSTBY'
10>    set log_archive_config='DG_CONFIG=(TMDLIVE,TMDSTBY,TMDSTB2)'
11>    set log_archive_dest_2='SERVICE=TMDLIVE LGWR ASYNC NOAFFIRM VALID_FOR=(ON
LINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=TMDLIVE'
12>    set log_archive_dest_3='SERVICE=TMDSTBY LGWR ASYNC NOAFFIRM VALID_FOR=(ON
LINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=TMDSTBY'
13>    nofilenamecheck;
14> }

Starting Duplicate Db at 19-SEP-16
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=23 device type=DISK
current log archived

contents of Memory Script:
{
   backup as copy reuse
   targetfile  'D:\Oracle\product\12.1.0\dbhome_1\DATABASE\PWDtmdlive.ORA' auxil
iary format
 'D:\Oracle\product\12.1.0\dbhome_1\DATABASE\PWDtmdstb2.ORA'   ;
   restore clone from service  'TMDLIVE' spfile to
 'D:\ORACLE\PRODUCT\12.1.0\DBHOME_1\DATABASE\SPFILETMDSTB2.ORA';
   sql clone "alter system set spfile= ''D:\ORACLE\PRODUCT\12.1.0\DBHOME_1\DATAB
ASE\SPFILETMDSTB2.ORA''";
}
executing Memory Script

Starting backup at 19-SEP-16
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=51 device type=DISK
Finished backup at 19-SEP-16

Starting restore at 19-SEP-16
using channel ORA_AUX_DISK_1

channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: using network backup set from service TMDLIVE
channel ORA_AUX_DISK_1: restoring SPFILE
output file name=D:\ORACLE\PRODUCT\12.1.0\DBHOME_1\DATABASE\SPFILETMDSTB2.ORA
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:08
Finished restore at 19-SEP-16

sql statement: alter system set spfile= ''D:\ORACLE\PRODUCT\12.1.0\DBHOME_1\DATA
BASE\SPFILETMDSTB2.ORA''

contents of Memory Script:
{
   sql clone "alter system set  db_unique_name =
 ''TMDSTB2'' comment=
 '''' scope=spfile";
   sql clone "alter system set  fal_client =
 ''TMDSTB2'' comment=
 '''' scope=spfile";
   sql clone "alter system set  fal_server =
 ''TMDLIVE'', ''TMDSTBY'' comment=
 '''' scope=spfile";
   sql clone "alter system set  log_archive_config =
 ''DG_CONFIG=(TMDLIVE,TMDSTBY,TMDSTB2)'' comment=
 '''' scope=spfile";
   sql clone "alter system set  log_archive_dest_2 =
 ''SERVICE=TMDLIVE LGWR ASYNC NOAFFIRM VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
DB_UNIQUE_NAME=TMDLIVE'' comment=
 '''' scope=spfile";
   sql clone "alter system set  log_archive_dest_3 =
 ''SERVICE=TMDSTBY LGWR ASYNC NOAFFIRM VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
DB_UNIQUE_NAME=TMDSTBY'' comment=
 '''' scope=spfile";
   shutdown clone immediate;
   startup clone nomount;
}
executing Memory Script

sql statement: alter system set  db_unique_name =  ''TMDSTB2'' comment= '''' sco
pe=spfile

sql statement: alter system set  fal_client =  ''TMDSTB2'' comment= '''' scope=s
pfile

sql statement: alter system set  fal_server =  ''TMDLIVE'', ''TMDSTBY'' comment=
 '''' scope=spfile

sql statement: alter system set  log_archive_config =  ''DG_CONFIG=(TMDLIVE,TMDS
TBY,TMDSTB2)'' comment= '''' scope=spfile

sql statement: alter system set  log_archive_dest_2 =  ''SERVICE=TMDLIVE LGWR AS
YNC NOAFFIRM VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=TMDLIVE'' c
omment= '''' scope=spfile

sql statement: alter system set  log_archive_dest_3 =  ''SERVICE=TMDSTBY LGWR AS
YNC NOAFFIRM VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=TMDSTBY'' c
omment= '''' scope=spfile

Oracle instance shut down

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/19/2016 10:56:03
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-04006: error from auxiliary database: ORA-03113: end-of-file on communication channel

alert.log:
+
Mon Sep 19 10:54:48 2016
ALTER SYSTEM SET log_archive_dest_3='SERVICE=TMDSTBY LGWR ASYNC NOAFFIRM VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=TMDSTBY' SCOPE=SPFILE;
Shutting down instance (immediate)
Shutting down instance: further logons disabled
Stopping background process MMNL
Stopping background process MMON
License high water mark = 5
alter database close
ORA-1507 signalled during: alter database close...
alter database dismount
ORA-1507 signalled during: alter database dismount...
Mon Sep 19 10:54:57 2016
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Mon Sep 19 10:54:58 2016
Stopping background process VKTM
Mon Sep 19 10:55:02 2016
Instance shutdown complete

Вроде ORA-1507 signalled during: alter database close... вполне ожидаемо, так как запущено c nomount, не из-за этого же происходит "ORA-03113: end-of-file on communication channel"?
Ответ: Спасибо, уже неактуально уже помог :)
автор
A1.8) Windows only:
If the Server's sqlnet.ora file contains Authentication services
which are NOT reachable by Oracle, then an ORA-3113 error will
result.
For example, if the sqlnet.ora file contains the parameter:
SQLNET.AUTHENTICATION_SERVICES = (NTS) and the Oracle database
is moved from a Windows NT Domain to an Active Directory one,
or if a Domain Controller is introduced, then an error will result
trying to start the database.
Remove the sqlnet.authentication_services line so that Oracle
does not look for a non-existent KDC (Kerberos Domain Controller).
Вопрос: RMAN требует неизвестные backup piece

Здравствуйте.
Встретился со следующей проблемой:
1. Делаю rman backup:
run {
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION ON; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE DEVICE TYPE DISK PARALLELISM 4;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backup01/RMAN/back%U';
CONFIGURE CHANNEL 1 DEVICE TYPE DISK CLEAR;
CONFIGURE CHANNEL 2 DEVICE TYPE DISK CLEAR;
CONFIGURE CHANNEL 3 DEVICE TYPE DISK CLEAR;
CONFIGURE CHANNEL 4 DEVICE TYPE DISK CLEAR;
BACKUP DATABASE INCLUDE CURRENT CONTROLFILE;
}
Получаю 5 backup piece :
>/backup01/RMAN
ls -al
total 1363999668
drwxrwxrwx 2 oracle dba 1024 Jul 5 00:36 .
drwxr-xr-x 7 110 dba 1024 Jul 5 16:28 ..
-rw-r--r-- 1 oracle dba 164282834944 Jul 5 00:46 backbcodubao_1_1
-rw-r--r-- 1 oracle dba 192142024704 Jul 5 00:55 backbdodubat_1_1
-rw-r--r-- 1 oracle dba 191940526080 Jul 5 00:54 backbeodubb4_1_1
-rw-r--r-- 1 oracle dba 149980872704 Jul 5 00:36 backbfodubba_1_1
-rw-r--r-- 1 oracle dba 16973824 Jul 5 00:36 backbgodugs1_1_1
LOG=
Recovery Manager: Release 11.2.0.1.0 - Production on Thu Jul 4 23:00:16 2013

Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

connected to target database: AISTPS (DBID=90882830)
using target database control file instead of recovery catalog

RMAN> run { 
2> CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
3> CONFIGURE BACKUP OPTIMIZATION ON; # default
4> CONFIGURE DEFAULT DEVICE TYPE TO DISK;
5> CONFIGURE DEVICE TYPE DISK PARALLELISM 4;
6> CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
7> CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
8> CONFIGURE CONTROLFILE AUTOBACKUP ON;
9> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   '/backup01/RMAN/back%U';
10> CONFIGURE CHANNEL 1 DEVICE TYPE DISK CLEAR;
11> CONFIGURE CHANNEL 2 DEVICE TYPE DISK CLEAR;
12> CONFIGURE CHANNEL 3 DEVICE TYPE DISK CLEAR;
13> CONFIGURE CHANNEL 4 DEVICE TYPE DISK CLEAR;
14> BACKUP DATABASE INCLUDE CURRENT CONTROLFILE; 
15> }
16> 
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
new RMAN configuration parameters are successfully stored

old RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters are successfully stored

old RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters are successfully stored

old RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 4 BACKUP TYPE TO BACKUPSET;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 4 BACKUP TYPE TO BACKUPSET;
new RMAN configuration parameters are successfully stored

old RMAN configuration parameters:
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
new RMAN configuration parameters:
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
new RMAN configuration parameters are successfully stored

old RMAN configuration parameters:
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
new RMAN configuration parameters:
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
new RMAN configuration parameters are successfully stored

old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters are successfully stored

old RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   '/backup01/RMAN/back%U';
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   '/backup01/RMAN/back%U';
new RMAN configuration parameters are successfully stored

old RMAN configuration parameters are successfully deleted

old RMAN configuration parameters are successfully deleted

old RMAN configuration parameters are successfully deleted

old RMAN configuration parameters are successfully deleted

Starting backup at 04-JUL-13
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=249 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=315 device type=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: SID=335 device type=DISK
allocated channel: ORA_DISK_4
channel ORA_DISK_4: SID=369 device type=DISK
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00008 name=+AISTPSDATA/aistps/datafile/users_04.dba
input datafile file number=00015 name=+AISTPSDATA/aistps/datafile/indx4m_02.dba
input datafile file number=00020 name=+AISTPSDATA/aistps/datafile/indx_03.dba
input datafile file number=00025 name=+AISTPSDATA/aistps/datafile/users_4m_01.dba
input datafile file number=00029 name=+AISTPSDATA/aistps/datafile/users4m_05.dba
input datafile file number=00034 name=+AISTPSDATA/aistps/datafile/users_4m_06.dba
input datafile file number=00003 name=+AISTPSDATA/aistps/datafile/undotbs1.276.809630909
input datafile file number=00031 name=+AISTPSDATA/aistps/datafile/repl_03.dba
input datafile file number=00024 name=+AISTPSDATA/aistps/datafile/tools_01.dba
channel ORA_DISK_1: starting piece 1 at 04-JUL-13
channel ORA_DISK_2: starting full datafile backup set
channel ORA_DISK_2: specifying datafile(s) in backup set
input datafile file number=00005 name=+AISTPSDATA/aistps/datafile/users_01.dba
input datafile file number=00009 name=+AISTPSDATA/aistps/datafile/users_05.dba
input datafile file number=00018 name=+AISTPSDATA/aistps/datafile/indx_02.dba
input datafile file number=00022 name=+AISTPSDATA/aistps/datafile/indx_04.dba
input datafile file number=00027 name=+AISTPSDATA/aistps/datafile/users_4m_03.dba
input datafile file number=00032 name=+AISTPSDATA/aistps/datafile/indx_05.dba
input datafile file number=00036 name=+AISTPSDATA/aistps/datafile/indx_06.dba
input datafile file number=00001 name=+AISTPSDATA/aistps/datafile/system.282.809630937
input datafile file number=00002 name=+AISTPSDATA/aistps/datafile/sysaux.281.809630933
channel ORA_DISK_2: starting piece 1 at 04-JUL-13
channel ORA_DISK_3: starting full datafile backup set
channel ORA_DISK_3: specifying datafile(s) in backup set
input datafile file number=00004 name=+AISTPSDATA/aistps/datafile/users.257.809630783
input datafile file number=00016 name=+AISTPSDATA/aistps/datafile/indx4m_03.dba
input datafile file number=00021 name=+AISTPSDATA/aistps/datafile/indx4m_05.dba
input datafile file number=00026 name=+AISTPSDATA/aistps/datafile/users_4m_02.dba
input datafile file number=00030 name=+AISTPSDATA/aistps/datafile/indx_01.dba
input datafile file number=00035 name=+AISTPSDATA/aistps/datafile/indx_07.dba
input datafile file number=00013 name=+AISTPSDATA/aistps/datafile/repl_02.dba
input datafile file number=00006 name=+AISTPSDATA/aistps/datafile/users_02.dba
input datafile file number=00017 name=+AISTPSDATA/aistps/datafile/system02
channel ORA_DISK_3: starting piece 1 at 04-JUL-13
channel ORA_DISK_4: starting full datafile backup set
channel ORA_DISK_4: specifying datafile(s) in backup set
input datafile file number=00007 name=+AISTPSDATA/aistps/datafile/users_03.dba
input datafile file number=00014 name=+AISTPSDATA/aistps/datafile/indx4m_01.dba
input datafile file number=00019 name=+AISTPSDATA/aistps/datafile/indx4m_04.dba
input datafile file number=00023 name=+AISTPSDATA/aistps/datafile/indx4m_06.dba
input datafile file number=00028 name=+AISTPSDATA/aistps/datafile/users_4m_04.dba
input datafile file number=00033 name=+AISTPSDATA/aistps/datafile/users_4m_07.dba
input datafile file number=00037 name=+AISTPSDATA/aistps/datafile/indx4m_07.dba
input datafile file number=00010 name=+AISTPSDATA/aistps/datafile/users_06.dba
input datafile file number=00011 name=+AISTPSDATA/aistps/datafile/users_07.dba
input datafile file number=00012 name=+AISTPSDATA/aistps/datafile/users_08.dba
channel ORA_DISK_4: starting piece 1 at 04-JUL-13
channel ORA_DISK_4: finished piece 1 at 05-JUL-13
piece handle=/backup01/RMAN/backbfodubba_1_1 tag=TAG20130704T230140 comment=NONE
channel ORA_DISK_4: backup set complete, elapsed time: 01:34:13
channel ORA_DISK_4: starting full datafile backup set
channel ORA_DISK_4: specifying datafile(s) in backup set
including current control file in backup set
channel ORA_DISK_4: starting piece 1 at 05-JUL-13
channel ORA_DISK_4: finished piece 1 at 05-JUL-13
piece handle=/backup01/RMAN/backbgodugs1_1_1 tag=TAG20130704T230140 comment=NONE
channel ORA_DISK_4: backup set complete, elapsed time: 00:00:07
channel ORA_DISK_1: finished piece 1 at 05-JUL-13
piece handle=/backup01/RMAN/backbcodubao_1_1 tag=TAG20130704T230140 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 01:44:43
channel ORA_DISK_3: finished piece 1 at 05-JUL-13
piece handle=/backup01/RMAN/backbeodubb4_1_1 tag=TAG20130704T230140 comment=NONE
channel ORA_DISK_3: backup set complete, elapsed time: 01:53:12
channel ORA_DISK_2: finished piece 1 at 05-JUL-13
piece handle=/backup01/RMAN/backbdodubat_1_1 tag=TAG20130704T230140 comment=NONE
channel ORA_DISK_2: backup set complete, elapsed time: 01:53:39
Finished backup at 05-JUL-13

Starting Control File Autobackup at 05-JUL-13
piece handle=/backup01/CTRL/contc-90882830-20130705-00 comment=NONE
Finished Control File Autobackup at 05-JUL-13

Recovery Manager complete.


Controlfile сохраняю
run { 
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION ON; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backup01/CTRL/cont%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 4;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/backup01/CTRL/snapcf_AISTPS.f';
BACKUP AS COPY
  CURRENT CONTROLFILE FORMAT '/backup01/CTRL/control01.ctl';
}



2. Пытаюсь восстановить на аналогичном сервере(тестовом), подмонтировав диск backup01/:
run {
SET DBID = 90882830;
RESTORE CONTROLFILE FROM '/backup01/CTRL/contc-90882830-20130705-01';
ALTER DATABASE MOUNT;
CONFIGURE DEVICE TYPE DISK PARALLELISM 4;
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   '/backup01/RMAN/back%U';
CONFIGURE CHANNEL 1 DEVICE TYPE DISK CLEAR;
CONFIGURE CHANNEL 2 DEVICE TYPE DISK CLEAR;
CONFIGURE CHANNEL 3 DEVICE TYPE DISK CLEAR;
CONFIGURE CHANNEL 4 DEVICE TYPE DISK CLEAR;
SET ARCHIVELOG DESTINATION TO '/backup01/ARCH';
SET UNTIL SCN=22040698009;
RESTORE DATABASE;
RECOVER DATABASE;
}


Получаю ошибку :
RA-19870: error while restoring backup piece /backup01/RMAN/backavodp2lh_1_1
ORA-19505: failed to identify file "/backup01/RMAN/backavodp2lh_1_1"
ORA-27037: unable to obtain file status
HPUX-ia64 Error: 2: No such file or directory
Additional information: 3

LOG - в файле .

Не понимаю, откуда берется инфа по кускам :
backup01/RMAN/backb7odrn1m_1_1
backup01/RMAN/backb4odrn0r_1_1
...
Пытался control заменять просто руками - то же самое..
прошу помощи...

К сообщению приложен файл (log111.LOG - 63Kb)
Ответ: kabanasy,

копи-паст, конечно же, не работает? нужно было обязательно порвать монитор огромной картинкой?
Вопрос: Ошибка при восстановлении: ORA-01666: control file is for a standby database

Восстанавливаюсь из бэкапа, сделанного со стендбая.

Восстановил:
1. файл параметров
2. контрольник

Посмотрел rman> list backup; контрольника,
там говорится, что есть sequence 85727:

 1    85726   31676338602 06-OCT-15 31676606756 06-OCT-15
 1    85727   31676606756 06-OCT-15 31676752041 07-OCT-15
 1    85728   31676752041 07-OCT-15 31676861477 07-OCT-15


Хочу выполнить неполное восстановление до последовательности 85727.

Выполнил restore database успешно, далее
recover database until sequence 85727; 

и ошибка:
Oracle Error:
ORA-01547: ┐┐┐┐┐┐┐┐┐┐┐┐┐┐: ┐┐┐┐┐┐┐┐┐┐┐┐┐┐ ┐┐┐┐┐┐ ┐┐┐┐┐┐┐, ┐┐┐┐┐┐ ┐┐┐┐┐┐┐ 
OPEN RESETLOGS ┐┐┐┐┐ ┐┐┐┐┐┐┐ ┐┐┐┐┐┐
ORA-01152: ┐┐┐┐ 1 ┐┐ ┐┐┐ ┐┐┐┐┐┐┐┐┐┐┐┐ ┐┐ ┐┐┐┐┐┐┐ ┐┐┐┐┐┐┐┐┐┐ ┐┐┐┐┐┐ ┐┐┐┐┐
ORA-01110: ┐┐┐┐ ┐┐┐┐┐┐ 1: 'D:\ORACLE\ORADATA\ORCL\SYSTEM01.DBF'


channel default: deleting archived log(s)
archived log file name=E:\ORACLE\FLASHRECOVERY\ORCL\ARCHIVELOG\2015_10_09\O1_MF_
1_85727_C1GSYYOR_.ARC RECID=41494 STAMP=892634929
media recovery complete, elapsed time: 00:13:42
Finished recover at 09-OCT-15


автор
ORA-01547
warning: RECOVER succeeded but OPEN RESETLOGS would get error below

Cause: Media recovery with one of the incomplete recovery options ended without error.
However, if the ALTER DATABASE OPEN RESETLOGS command were attempted now, it would fail with the specified error.
The most likely cause of this error is forgetting to restore one or more datafiles from a sufficiently old backup before executing the incomplete recovery.

Action: Rerun the incomplete media recovery using different datafile backups, a different control file, or different stop criteria.


при попытке открыть БД с ресетом журналов ошибка:

SQL> ALTER DATABASE OPEN RESETLOGS;
ALTER DATABASE OPEN RESETLOGS
*
ERROR at line 1:
ORA-01666: control file is for a standby database


SQL> select status from v$instance;

STATUS
------------
MOUNTED

SQL> alter database activate physical standby database;
alter database activate physical standby database
*
ERROR at line 1:
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: 'D:\ORACLE\ORADATA\ORCL\SYSTEM01.DBF'


автор
alter database activate physical standby database
Begin: Standby Redo Logfile archival
End: Standby Redo Logfile archival
Signalling error 1152 for datafile 1!
Beginning Standby Crash Recovery.
Serial Media Recovery started


вопрос в том, почему если в контрольнике есть данные о sequence 85727, и в бэкапе данный архивлог есть,
возникает ошибка?

если дать команду recover database until sequence 85729, то oracle накатит 85727, 85728 и затем поругается, что нет 85729.

попытка открыть с опцией upgrade
SQL> startup upgrade;
ORACLE instance started.

Total System Global Area 7482626048 bytes
Fixed Size                  2295784 bytes
Variable Size            4412409880 bytes
Database Buffers         3053453312 bytes
Redo Buffers               14467072 bytes
Database mounted.
ORA-16003: standby database is restricted to read-only access


подложил 85729, стало всё ок, но вопрос остался, как восстановиться до последовательности 85727.

SQL> alter database recover automatic standby database until cancel;
alter database recover automatic standby database until cancel
*
ERROR at line 1:
ORA-00279: change 31676966507 generated at 10/07/2015 01:06:12 needed for
thread 1
ORA-00289: suggestion :
E:\ORACLE\FLASHRECOVERY\ORCL\ARCHIVELOG\2015_10_09\O1_MF_1_85730_%U_.ARC
ORA-00280: change 31676966507 for thread 1 is in sequence #85730
ORA-00278: log file
'E:\ORACLE\FLASHRECOVERY\ORCL\ARCHIVELOG\2015_10_09\O1_MF_1_85730_%U_.ARC' no
longer needed for this recovery
ORA-00308: ┐┐┐┐┐┐┐┐┐┐ ┐┐┐┐┐┐┐ ┐┐┐┐┐┐┐┐┐┐┐┐┐┐ ┐┐┐┐┐┐┐┐
'E:\ORACLE\FLASHRECOVERY\ORCL\ARCHIVELOG\2015_10_09\O1_MF_1_85730_%U_.ARC'
ORA-27041: ┐┐┐┐┐┐┐┐┐┐ ┐┐┐┐┐┐┐ ┐┐┐┐
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.


SQL> alter database recover automatic cancel;

Database altered.


SQL> alter database activate physical standby database;

Database altered.
Ответ:
-13-
Q.Tarantino
пропущено...

нет, я так понял у oracle home уже версия выше, а вот словарь БД то старый.


Т.е. помимо catupgrd.sql прогнать ещё какие скрипты?

почитай доку по upgrade и сделай все правильно. я всех подробностей не помню.