Menu de navegação

[Anônimo]

Relatando os problemas enfrentados no restore com RMAN:

Oracle apresentado problema ao realizar backup

Erro ao tentar efetuar o backup com o RMAN no dia 22/02, eu estava tentando fazer um Backup não agendado para corrigir um problema de timeout via uma rede com NAT (não a usada regularmente).

RMAN-06169: could not read file header for datafile 46 error reason 6

released channel: ch1

released channel: ch2

released channel: ch3

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of backup command at 02/22/2010 14:21:01

RMAN-06056: could not access datafile 46

File 46 é o Datafile = /dev/vx/rdsk/ds2p006dat2/peftsdt102_001

Erros tambem nos Datafiles:

/dev/vx/rdsk/ds2p006dat2/peftsdt020_001

/dev/vx/rdsk/ds2p006dat2/peftsdt065_002

/dev/vx/rdsk/ds2p006dat2/peftsdt124_002

Este problema foi relatado ao pessoal do Storage que prontamente me informou ter corrigido o problema.
BELEZA !!! Vou perder a manhã do sábado dando um recover no Database e tudo ficará perfeito.

ERRADO !!!!!!
Durante a manhã do sábado eu tentei o recover como segue:

RMAN>
RMAN> run {
2> ALLOCATE CHANNEL ch1 TYPE ‘sbt_tape’ PARMS
‘BLKSIZE=524288 ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo01.opt)’;
3> 4> ALLOCATE CHANNEL ch2 TYPE ‘sbt_tape’ PARMS
‘BLKSIZE=524288 ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo01.opt)’;
5> ALLOCATE CHANNEL ch3 TYPE ‘sbt_tape’ PARMS
‘BLKSIZE=524288 ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo01.opt)’;
6> 7> recover database until scn 698052224;
8> RELEASE CHANNEL ch1;
9> RELEASE CHANNEL ch2;
10> RELEASE CHANNEL ch3;
11> }
12>
using target database control file instead of recovery catalog
allocated channel: ch1
channel ch1: SID=148 device type=SBT_TAPE
channel ch1: Tivoli Data Protection for Oracle: version 5.2.0.0

allocated channel: ch2
channel ch2: SID=147 device type=SBT_TAPE
channel ch2: Tivoli Data Protection for Oracle: version 5.2.0.0

allocated channel: ch3
channel ch3: SID=154 device type=SBT_TAPE
channel ch3: Tivoli Data Protection for Oracle: version 5.2.0.0

Starting recover at 28-FEB-10
released channel: ch1
released channel: ch2
released channel: ch3
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 02/28/2010 19:25:03
RMAN-20208: UNTIL CHANGE is before RESETLOGS change

Bom.. para tentar resumir o que houve, os disco continuaram a apresentar erro mesmo após a equipe de Storage JURAR de pés JUNTOS por 2 semanas que o problema estava no RMAN ou na operaçào do Oracle (eu e mais 2 DBA’s). Finalmente eles desistiram pois eu mostrei o output do sistema que mostrava um erro de escrita em disco reportado pelo Kernel:

Mar 6 17:04:55 cr0000ux006 vxio: [ID 771159 kern.warning] WARNING: VxVM vxio V-5-0-2 Subdisk ds2p006dat235-01 block 2585888: Uncorrectable write error
Mar 6 19:45:11 cr0000ux006 vxio: [ID 771159 kern.warning] WARNING: VxVM vxio V-5-0-2 Subdisk ds2p006dat235-01 block 303136: Uncorrectable write error

Após mais 1 semana eles conseguiram corrigir este problema e recomeçou o meu. Tenho um banco com 5 Tera que está TOTALMENTE desponteirado e perdido após várias tentativas de restore, recover e um infeliz RESETLOGS em que apenas a system foi colocada em um novo incarnation.
Eu tenho o Backup dele, mas estou recebendo erros que eu não consigo corrigir pro estar morto de cansado acompanhando o trabalho das outras equipes.

Segue o erro do recover database

Recovery Manager: Release 11.1.0.7.0 – Production on Sat Mar 13 02:11:43 2010

Copyright (c) 1982, 2007, Oracle. All rights reserved.

RMAN> #!/bin/ksh
2> connect target *
3> connect catalog *
4> run
5> {
6> debug on;
7> ALLOCATE CHANNEL ch1 TYPE ‘sbt_tape’ PARMS
8> ‘BLKSIZE=524288 ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo_006.opt)’;
9> ALLOCATE CHANNEL ch2 TYPE ‘sbt_tape’ PARMS
10> ‘BLKSIZE=524288 ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo_006.opt)’;
11> recover database;
12> RELEASE CHANNEL ch1;
13> RELEASE CHANNEL ch2;
14> debug off;
15> }
16>
connected to target database: ORAPRD01 (DBID=879841304, not open)

connected to recovery catalog database

RMAN-03036: Debugging set to level=9, types=ALL

RMAN-08030: allocated channel: ch1
RMAN-08500: channel ch1: SID=147 device type=SBT_TAPE
RMAN-08526: channel ch1: Data Protection for Oracle: version 5.5.1.0

RMAN-08030: allocated channel: ch2
RMAN-08500: channel ch2: SID=150 device type=SBT_TAPE
RMAN-08526: channel ch2: Data Protection for Oracle: version 5.5.1.0

RMAN-03090: Starting recover at 13-MAR-10
RMAN-08031: released channel: ch1
RMAN-08031: released channel: ch2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 03/13/2010 02:19:43
RMAN-06094: datafile 208 must be restored

Recovery Manager complete.

Ok.. Restauremos o File 208, que é o UNDO

Recovery Manager: Release 11.1.0.7.0 – Production on Sat Mar 13 13:31:58 2010

Copyright (c) 1982, 2007, Oracle. All rights reserved.

RMAN> connect target *
2> connect catalog *
3> run
4> {
5> ALLOCATE CHANNEL ch1 TYPE ‘sbt_tape’ PARMS
6> ‘BLKSIZE=524288 ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo_006.opt)’;
7> #SET UNTIL SEQUENCE 706753847;
8> RESTORE DATAFILE 208;
9> RECOVER DATABASE;
10> RELEASE CHANNEL ch1;
11> }
12>
13>
connected to target database: ORAPRD01 (DBID=879841304, not open)

connected to recovery catalog database

allocated channel: ch1
channel ch1: SID=145 device type=SBT_TAPE
channel ch1: Data Protection for Oracle: version 5.5.1.0

Starting restore at 13-MAR-10

the file name for datafile 208 is missing in the control file
restore not done; all files read only, offline, or already restored
Finished restore at 13-MAR-10

Starting recover at 13-MAR-10

starting media recovery
media recovery failed
released channel: ch1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 03/13/2010 13:38:49
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database recover if needed
start until cancel using backup controlfile
ORA-00283: recovery session canceled due to errors
ORA-19909: datafile 1 belongs to an orphan incarnation
ORA-01110: data file 1: ‘/dev/vx/rdsk/ds2p006dat1/p006sys001’

Recovery Manager complete.

————————-

Adicionalmente envio a lista dos Datafiles e seus SCN’s

NAME STATUS CHECKPOIN CHECKPOINT_CHANGE#
/dev/vx/rdsk/ds2p006dat1/p006sys001 SYSTEM 04-MAR-10 706753847
/dev/vx/rdsk/ds2p006dat2/peftsdt090_003 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006rbs/peftsrs001_001 RECOVER 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt010_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt020_001 ONLINE 11-FEB-10 705795754
/dev/vx/rdsk/ds2p006dat1/peftsdt001_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt011_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt030_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt021_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt040_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt050_001 RECOVER 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt031_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt060_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt041_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt070_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt080_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt090_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt051_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt100_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt110_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt002_001 ONLINE 11-FEB-10 705795646
/dev/vx/rdsk/ds2p006dat2/peftsdt012_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt022_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt032_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt061_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt042_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt052_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt062_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt071_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt081_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt091_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt101_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt111_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt003_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt013_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt033_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt053_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt043_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt072_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt023_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt091_003 ONLINE 01-DEC-09 700634495
/dev/vx/rdsk/ds2p006dat2/peftsdt082_001 ONLINE 11-FEB-10 705795651
/dev/vx/rdsk/ds2p006dat1/peftsdt073_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt092_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt083_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt102_001 ONLINE 11-FEB-10 705795658
/dev/vx/rdsk/ds2p006dat1/peftsdt093_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt004_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt112_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt014_001 ONLINE 11-FEB-10 705795664
/dev/vx/rdsk/ds2p006dat2/peftsdt034_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt054_001 ONLINE 11-FEB-10 705795667
/dev/vx/rdsk/ds2p006dat2/peftsdt044_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt064_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt024_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt074_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt036_001 ONLINE 11-FEB-10 705795672
/dev/vx/rdsk/ds2p006dat2/peftsdt084_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt094_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt103_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt113_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt015_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt005_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt055_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt045_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt065_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt104_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt075_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt025_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt037_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt085_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt095_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt114_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt105_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt092_003 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt016_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt006_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt056_001 ONLINE 11-FEB-10 705795679
/dev/vx/rdsk/ds2p006dat2/peftsdt046_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt066_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt076_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt017_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt038_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt026_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt096_001 ONLINE 28-JAN-10 704780115
/dev/vx/rdsk/ds2p006dat2/peftsdt086_001 ONLINE 11-FEB-10 705795687
/dev/vx/rdsk/ds2p006dat2/peftsdt106_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt093_003 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt007_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt057_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt018_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt008_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt058_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt047_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt067_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt048_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt077_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt068_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt039_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt097_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt078_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt094_003 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt107_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt027_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt087_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt019_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt059_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt009_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt049_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt095_003 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt088_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt028_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt069_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt108_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt079_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt098_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt119_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt089_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt029_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt109_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt099_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt096_003 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/p006sysaux001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt035_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt024_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt106_004 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt064_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt065_002 ONLINE 11-FEB-10 705795703
/dev/vx/rdsk/ds2p006dat2/peftsdt099_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt106_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt074_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt075_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt016_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt038_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt075_003 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt074_003 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt006_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt007_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt008_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt023_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt078_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt079_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt080_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt081_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt082_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt083_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt105_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt101_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt102_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt107_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt032_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt001_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt037_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt039_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt087_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt106_003 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt040_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt041_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt019_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt020_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt070_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt071_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt104_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt103_002 ONLINE 11-FEB-10 705795715
/dev/vx/rdsk/ds2p006dat1/peftsdt086_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt088_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt098_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt100_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt015_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt017_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt014_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt016_003 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt035_002 ONLINE 11-FEB-10 705795724
/dev/vx/rdsk/ds2p006dat1/peftsdt087_003 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt099_003 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt121_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt122_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt123_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt124_002 ONLINE 11-FEB-10 705795729
/dev/vx/rdsk/ds2p006dat1/peftsdt074_004 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt075_004 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt002_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt003_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt004_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt005_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt009_002 ONLINE 11-FEB-10 705795734
/dev/vx/rdsk/ds2p006dat1/peftsdt010_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt011_002 ONLINE 11-FEB-10 705795737
/dev/vx/rdsk/ds2p006dat2/peftsdt013_002 ONLINE 11-FEB-10 705795742
/dev/vx/rdsk/ds2p006dat1/peftsdt012_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt006_003 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt007_003 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt008_003 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt090_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt091_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt093_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt092_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt094_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt095_002 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt096_002 ONLINE 14-DEC-09 701636915
/dev/vx/rdsk/ds2p006dat2/peftsdt074_005 ONLINE 11-FEB-10 705795749
/dev/vx/rdsk/ds2p006dat1/peftsdt075_005 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006tmp/peftstp001_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006prd/segtsdt001_oraprd01 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006idx/peftsix001_001 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat1/peftsdt074_006 ONLINE 25-FEB-10 706726319
/dev/vx/rdsk/ds2p006dat2/peftsdt075_006 ONLINE 25-FEB-10 706726319
/u00/app/oracle/oradata/oraprd01/undotbs_001.dbf ONLINE 25-FEB-10 706726319

——————————————————————————

Pessoal é isso, ao meu ver, meu problema é que a minha System esta em uma incarnation e o resto dos datafiles em outra.
Preciso colocar esse cara online Anteontem (heheh)
Muito obrigado por qualquer ajuda desde já e adicionalmente eu tenho qualquer arquivo de log a disposição de quem se dispuser ajudar.

[vieriParticipante]

Faça os passos com rman até a base está montada após isso
tente subir com o sqlplus com a claúsula recover database until cancel.

vc também pode subir a base com um parâmetro oculto que deixe subir a base inconsistente. (ma isso vc deixa para ultimo caso).

vc tem os archives dos dia 11 até o dia 25 disponível na sua área de arch. ?

[Regis AraujoParticipante]

Fala Fred.. bom dia..!

Bom meu velho.. seguinte.. eu passei por um problema parecido com o seu..

Faz o seguinte.. da uma olhada nestas views…!!

v$recovery_log
v$recover_file
v$datafile_header

Na v$recovery_log vc vai obter a informação de quais archives vc vai precisar restaurar para aplicar na sua base para que todos os datafiles tenham a mesma data de checkpoint..

Na v$recover_file vc vai oter a informação de quais datafiles estão precisando de recover..

Na v$datafile_header na coluna RECOVER vc vai saber cada datafile que precisa de um recover..

Mas só um adendo.. se tu deu um open resetlogs.. amigo.. sinto lhe informar mas vc nao vai conseguir aplicar os archives.. pois no RESETLOGS ele mata o banco e cria uma nova incarnação e também muda o sequencial dos archives.. da uma olhada na view v$database_incarnation e verifica a data do RESETLOGS_TIME..

Só uma dica.. quanto vc for recuperar algum datafile.. não de um RECOVER DATABASE, utilize o RECOVER DATAFILE XX pois assim vc evita que seja restaurado os controlfiles…

Oq vc pode fazer é restaurar seu ultimo backup.. literalmente tudo.. datafiles, redos e controls.. e ir aplicando os archives até o ultimo gerado pela incarnação anterior a este seu ultimo resetlogs..

Eu tive q fazer isto mas não pelo resetlogs.. e sim devido ao corrompimento de toda a minha base… Da uma lida no meu blog q eu relatei o ocorrido..!!

Qualquer coisa.. posta ai… q iremos lhe ajudar..!

Abraços..!

[Anônimo]

Muito obrigado pela ajuda, estou testando e postarei os progressos.

[RodrigofsParticipante]

Thunder_Catz acho que houve algum engano, pois na versão 10g é possível sim utilizar backups feitos em incarnações anteriores. Acredito que isso também é possível na versão 11g. No caso do FredR basta resetar o banco de dados para a incarnação anterior, e ele conseguirá usar esses backups.
Eu fiz um artigo explicando como utilizar backups feitos em incarnações anteriores, talvez te ajude FredR.

segue o link: http://rodrigo-oracle.blogspot.com/2010 … os-em.html

Um abraço,
Até mais.

[Regis AraujoParticipante]

Opa.. opa..!

Sim Rodrigo, vc esta certissimo.. acabei me esquecendo disto..
Mas isto é possivel até quanto tempo após o RESETLOGS? Pois dependendo do tempo, já não da para garantir a integridade dos dados…

Nunca tentei fazer isto nem para teste.. pois só uso o RESETLOGS quando realmente não tem jeito.. e depois de testar todas as alternativas..

Mas creio que cada caso é um caso.. tem q analisar a base do FRED.. pois como eu disse antes.. o perido ta no que ja foi salvo no controlfile.. seria interessante ele restaurar um controlfile do ultimo backup e aplicar os archives…

Bom.. é mais uma maneira do Fred recuperar a base dele…!

Abraços e valeu pela lembrança Rodrigo..!! Vou ler seu Post..!

[RodrigofsParticipante]

Sim Regis, com certeza tem que analisar a base do FRED como você disse. 🙂
Pelos testes que já fiz você consegue aplicar os archives da incarnação anterior. Regis eu acho que se consegue recuperar até o ultimo archive da incarnação desejada. Por exemplo:

backup full
archives..
archives..
archives..
archives..

Alter database open reset logs; – Nova incarnação.

reset database to incarnation 1- volta a incarnação anterior.

restaura o backup e recupera todos os archives da incarnação 1 normalmente.

Isso é possível pois, o controlfile corrente “sabe” da existência de tal incarnação e ao resetar o banco para incarnação anterior, o controlfile sabe quais são os archives de tal incarnação.

Bom, espero ter ajudado.
Abraço!

[Rodrigo AlmeidaParticipante]

Seguinte,

Primeiramente o que tu tem de backup do banco de dados?

Tu tem toda as sequencias de archived logs desde quando se deu inicio do problema?

Restaure tudo para uma área grande, faça o CROSSCHECK BACKUP OF DATAABASE e CROSSCHECK BACKUP OF ARCHIVELOG ALL;

E depois refaça as operações de recover database until time.

veja no LIST INCARNATION OF DATABASE quais as incarnações que tem disponíveis…

Abraços,

[Autor]

Posts