Menu de navegação

[vieriParticipante]

após restaurar um backup de 1.2Tb com sucesso, chegou a hora do recover, e como preciso dos archives,
olha o erro que me aparece. nao estou usando catalogo.

RMAN> catalog archivelog ‘/u03/rman/archive/arch_ibm94ebi_1_1_ORA10G_20043_747780466.rman’ ;

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of catalog command on default channel at 04/29/2011 11:33:02
ORA-19698: /u03/rman/archive/arch_ibm94ebi_1_1_ORA10G_20043_747780466.rman is from different database: id=169869312, db_name=eORA10G

até ai td bem, mas ele me diz que meu archive tem d=169869312, db_name=eORA10G,
sendo que ele é o archive do backup da base connected to target database: ORA10G (DBID=3909485338, not open).
com certeza absoluta, eu mesmo fiz o backup e restaurei todas as peças, me parece que no header dos archive meu dbid e dbname estão diferente.. :S

ai tento restaurar :

RMAN> restore archivelog all from ‘/u03/rman/archive/arch_ibm94ebi_1_1_ORA10G_20043_747780466.rman’ ;

Starting restore at 29-APR-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=1089 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=1088 devtype=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: sid=1093 devtype=DISK
allocated channel: ORA_DISK_4
channel ORA_DISK_4: sid=1094 devtype=DISK

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 04/29/2011 11:35:01
RMAN-06509: only SPFILE or control file can be restored from autobackup

alguem tem alguma idéia desse absurdo.??

voltando de férias ache to meio enferrujado no rman.. rs

[Rodrigo AlmeidaParticipante]

Vieri,

Vai nos logs do BACKUP que foram gerados e verifique se no LOG os archives necessários foram gerados nesse backuppiece:

‘/u03/rman/archive/arch_ibm94ebi_1_1_ORA10G_20043_747780466.rman’

Como deve estar restaurando o banco de dados de produção, procure nos logs e caso já tenha restaurado o controlfile, veja qual os archives que foram gerados e o backuppiece correto.

Sobre o DBID e o db_name, no momento que realizar novamente o RECOVER, faça um SET DBID = ; para forçar a usar o DBID dos backups.

Abraços,
Rodrigo Almeida

[vieriParticipante]

Vai nos logs do BACKUP que foram gerados e verifique se no LOG os archives necessários foram gerados nesse backuppiece:

‘/u03/rman/archive/arch_ibm94ebi_1_1_ORA10G_20043_747780466.rman’
este é um dos backup pieces dos archives, como a base é grande tem mais uns 8 que precisa catalogar.
foi sim rodrigo, essa é a única base de dados aqui que tem nome de ora10g.

e foi retornada de uma fita pelo mesmo job do backupexec, e ela é a única base de dados de oracle que eu faço pelo backupexec aqui.,
e tanto o backup como os archives estão na sequencia certinha de horário.

esse é meu script.

rman log=/home/oracle/rman/scripts/log/log_bi_rman_hot_$3$2$6.log catalog rman/rman@rman target backup/backup00@ora10g <<EOF

run {
allocate channel t2 type disk maxpiecesize = 50G;
allocate channel t3 type disk maxpiecesize = 50G;
backup as compressed backupset database include current controlfile tag 'BKP_BI_FULL_HOT'
format '/u03/rman/data/bkp_full_%U.rman';
backup current controlfile tag 'BKP_CTL'
format '/u03/rman/data/bkp_ctl_%U.rman';
backup spfile tag 'BKP_SPFILE'
format '/u03/rman/data/bkp_spfile_%U.rman';
release channel t2;
release channel t3;
}

run {
allocate channel ch1 type Disk maxpiecesize = 5000M;
sql "alter system archive log current";
backup archivelog all filesperset 5
format '/u03/rman/archive/arch_%U_%d_%s_%t.rman'
tag 'BI_ARCH_BKP'
delete all input;
release channel ch1;
resync catalog;
}

crosscheck backupset;
crosscheck archivelog all;
CROSSCHECK BACKUP;
#RESTORE TABLESPACE SYSTEM VALIDATE;
#RESTORE ARCHIVELOG ALL VALIDATE;
LIST BACKUP OF DATABASE;
REPORT UNRECOVERABLE;
REPORT SCHEMA;
REPORT NEED BACKUP;
REPORT OBSOLETE;

Delete noprompt expired backup;
Delete noprompt expired archivelog all;
Delete noprompt obsolete;
delete archivelog all completed before 'sysdate -3';

Sobre o DBID e o db_name, no momento que realizar novamente o RECOVER, faça um SET DBID = ; para forçar a usar o DBID dos backups.

eu setei o dbid da base antes de iniciar o restore,
fiz o controlfile com sucesso, fiz os dartafiles com sucesso,
mas os archives estão nas minhas bkppieces.. não consigo extrair.:

[oracle@admbi1 log]$ rman target /

Recovery Manager: Release 10.2.0.3.0 – Production on Fri Apr 29 16:33:51 2011

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

connected to target database: ORA10G (DBID=3909485338, not open)

meu dbid é o 3909485338 , mas ele diz que meus archives são do DBID:
169869312, db_name=eORA10G nunca existiu nenhuma base com dbname eora10g…

repare: SQL> select dbid from v$database;

DBID

3909485338

List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time

---

403611 403612 ORA10G 3909485338 PARENT 1 16-MAY-06
403611 1136924 ORA10G 3909485338 PARENT 9849649634 15-APR-11
403611 1136925 ORA10G 3909485338 PARENT 9849649636 15-APR-11
403611 1136926 ORA10G 3909485338 PARENT 9849689647 15-APR-11
403611 1136866 ORA10G 3909485338 PARENT 9849689649 15-APR-11
403611 3485795 ORA10G 3909485338 CURRENT 9852251106 22-APR-11

eo dbid dessa base sempre foi o mesmo..

quer que rode alguma query ou comando do rman pra te mostrar a saida?

sempre restuarei bases de prod em desenv com pé nas costas,
mas nesse banco ta complicado..

[vieriParticipante]

no meu recover.. mesmo com dbid setado ele não encontra os archives pq eu não consegui extrair eles dos meu bkppieces… pq não consegui catalogar.. os bkppieces dos datafiles e CTL eu cataloguei e restaurei sem problemas

RMAN> recover database ;

Starting recover at 29-APR-11
using channel ORA_DISK_1
using channel ORA_DISK_2
using channel ORA_DISK_3
using channel ORA_DISK_4

starting media recovery

Oracle Error:
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: ‘/u01/app/oracle/oradata/ora10g/system01.dbf’

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 04/29/2011 16:46:22
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 351745 lowscn 9832938357 found to restore
RMAN-06025: no backup of log thread 1 seq 351744 lowscn 9832819031 found to restore
RMAN-06025: no backup of log thread 1 seq 351743 lowscn 9832716647 found to restore
RMAN-06025: no backup of log thread 1 seq 351742 lowscn 9832716586 found to restore
RMAN-06025: no backup of log thread 1 seq 351741 lowscn 9832715376 found to restore
RMAN-06025: no backup of log thread 1 seq 351740 lowscn 9832706584 found to restore
RMAN-06025: no backup of log thread 1 seq 351739 lowscn 9832701604 found to restore
RMAN-06025: no backup of log thread 1 seq 351738 lowscn 9832696867 found to restore
RMAN-06025: no backup of log thread 1 seq 351737 lowscn 9832691913 found to restore
RMAN-06025: no backup of log thread 1 seq 351736 lowscn 9832686920 found to restore
RMAN-06025: no backup of log thread 1 seq 351735 lowscn 9832680980 found to restore
RMAN-06025: no backup of log thread 1 seq 351734 lowscn 9832671565 found to restore
RMAN-06025: no backup of log thread 1 seq 351733 lowscn 9832659824 found to restore
RMAN-06025: no backup of log thread 1 seq 351732 lowscn 9832644956 found to restore
RMAN-06025: no backup of log thread 1 seq 351731 lowscn 9832625769 found to restore
RMAN-06025: no backup of log thread 1 seq 351730 lowscn 9832616762 found to restore
RMAN-06025: no backup of log thread 1 seq 351729 lowscn 9832607660 found to restore
RMAN-06025: no backup of log thread 1 seq 351728 lowscn 9832598552 found to restore
RMAN-06025: no backup of log thread 1 seq 351727 lowscn 9832589177 found to restore
RMAN-06025: no backup of log thread 1 seq 351726 lowscn 9832579939 found to restore
RMAN-06025: no backup of log thread 1 seq 351725 lowscn 9832574254 found to restore
RMAN-06025: no backup of log thread 1 seq 351724 lowscn 9832569537 found to restore
RMAN-06025: no backup of log thread 1 seq 351723 lowscn 9832564597 found to restore
RMAN-06025: no backup of log thread 1 seq 351722 lowscn 9832558773 found to restore
RMAN-06025: no backup of log thread 1 seq 351721 lowscn 9832549554 found to restore
RMAN-06025: no backup of log thread 1 seq 351720 lowscn 9832539161 found to restore
RMAN-06025: no backup of log thread 1 seq 351719 lowscn 9832530149 found to restore
RMAN-06025: no backup of log thread 1 seq 351718 lowscn 9832521085 found to restore
RMAN-06025: no backup of log thread 1 seq 351717 lowscn 9832511755 found to restore
RMAN-06025: no backup of log thread 1 seq 351716 lowscn 9832502543 found to restore
RMAN-06025: no backup of log thread 1 seq 351715 lowscn 9832492768 found to restore
RMAN-06025: no backup of log thread 1 seq 351714 lowscn 9832479079 found to restore
RMAN-06025: no backup of log thread 1 seq 351713 lowscn 9832472431 found to restore
RMAN-06025: no backup of log thread 1 seq 351712 lowscn 9832462905 found to restore
RMAN-06025: no backup of log thread 1 seq 351711 lowscn 9832450807 found to restore
RMAN-06025: no backup of log thread 1 seq 351710 lowscn 9832441531 found to restore
RMAN-06025: no backup of log thread 1 seq 351709 lowscn 9832433304 found to restore
RMAN-06025: no backup of log thread 1 seq 351708 lowscn 9832426116 found to restore
RMAN-06025: no backup of log thread 1 seq 351707 lowscn 9832411563 found to restore
RMAN-06025: no backup of log thread 1 seq 351706 lowscn 9832403619 found to restore
RMAN-06025: no backup of log thread 1 seq 351705 lowscn 9832397730 found to restore
RMAN-06025: no backup of log thread 1 seq 351704 lowscn 9832392006 found to restore
RMAN-06025: no backup of log thread 1 seq 351703 lowscn 9832386184 found to restore
RMAN-06025: no backup of log thread 1 seq 351702 lowscn 9832380375 found to restore
RMAN-06025: no backup of log thread 1 seq 351701 lowscn 9832373664 found to restore
RMAN-06025: no backup of log thread 1 seq 351700 lowscn 9832366091 found to restore
RMAN-06025: no backup of log thread 1 seq 351699 lowscn 9832358734 found to restore
RMAN-06025: no backup of log thread 1 seq 351698 lowscn 9832351295 found to restore
RMAN-06025: no backup of log thread 1 seq 351697 lowscn 9832343929 found to restore
RMAN-06025: no backup of log thread 1 seq 351696 lowscn 9832336519 found to restore
RMAN-06025: no backup of log thread 1 seq 351695 lowscn 9832329186 found to restore
RMAN-06025: no backup of log thread 1 seq 351694 lowscn 9832321837 found to restore
RMAN-06025: no backup of log thread 1 seq 351693 lowscn 9832314663 found to restore
RMAN-06025: no backup of log thread 1 seq 351692 lowscn 9832307484 found to restore
RMAN-06025: no backup of log thread 1 seq 351691 lowscn 9832300113 found to restore
MAN-06025: no backup of log thre

[vieriParticipante]

repare na sequencia dos horários dos arquivos…

oracle@admbi1 data]$ ls -slrt
total 100287564
18252280 -rw-r—– 1 oracle dba 18672074752 Apr 6 16:37 bkp_full_hum93ni6_1_1.rman
34378800 -rw-r—– 1 oracle dba 35169501184 Apr 6 17:10 bkp_full_hsm93359_1_1.rman
8614712 -rw-r—– 1 oracle dba 8812838912 Apr 6 17:55 bkp_full_hvm93vme_1_1.rman
7362620 -rw-r—– 1 oracle dba 7531954176 Apr 6 18:25 bkp_full_i0m941js_1_1.rman
7699992 -rw-r—– 1 oracle dba 7877083136 Apr 6 19:13 bkp_full_i1m94492_1_1.rman
6887372 -rw-r—– 1 oracle dba 7045775360 Apr 6 19:33 bkp_full_i2m94608_1_1.rman
5573900 -rw-r—– 1 oracle dba 5702090752 Apr 6 20:04 bkp_full_i3m948r2_1_1.rman
4671340 -rw-r—– 1 oracle dba 4778770432 Apr 6 20:16 bkp_full_i4m94a12_1_1.rman
1936728 -rw-r—– 1 oracle dba 1981267968 Apr 6 20:23 bkp_full_i5m94bpq_1_1.rman
1418928 -rw-r—– 1 oracle dba 1451556864 Apr 6 20:36 bkp_full_i7m94ctp_1_1.rman
3386992 -rw-r—– 1 oracle dba 3464888320 Apr 6 20:46 bkp_full_i6m94cgp_1_1.rman
103884 -rw-r—– 1 oracle dba 106266624 Apr 6 20:47 bkp_ctl_i8m94ea2_1_1.rman
4 -rw-r—– 1 oracle dba 1689 Apr 28 08:30 tnsnames.ora
4 -rw-r—– 1 oracle dba 186 Apr 28 08:30 sqlnet.ora
4 -rw-r—– 1 oracle dba 1536 Apr 28 08:30 orapwora10g
4 -rw-r—– 1 oracle dba 1974 Apr 28 08:30 listener.ora
[oracle@admbi1 data]$ cd ../archive/
[oracle@admbi1 archive]$ ls -lsrt
total 22668608
1193684 -rw-r—– 1 oracle dba 1221129728 Apr 6 20:48 arch_ibm94ebi_1_1_ORA10G_20043_747780466.rman
1192864 -rw-r—– 1 oracle dba 1220294656 Apr 6 20:48 arch_icm94ecq_1_1_ORA10G_20044_747780506.rman
1191892 -rw-r—– 1 oracle dba 1219299840 Apr 6 20:49 arch_idm94ee2_1_1_ORA10G_20045_747780546.rman
1189752 -rw-r—– 1 oracle dba 1217106432 Apr 6 20:50 arch_iem94ef8_1_1_ORA10G_20046_747780584.rman
1186548 -rw-r—– 1 oracle dba 1213829632 Apr 6 20:50 arch_ifm94ege_1_1_ORA10G_20047_747780622.rman
1186372 -rw-r—– 1 oracle dba 1213652992 Apr 6 20:51 arch_igm94ehk_1_1_ORA10G_20048_747780660.rman
1184008 -rw-r—– 1 oracle dba 1211236352 Apr 6 20:52 arch_ihm94eiq_1_1_ORA10G_20049_747780698.rman
1183804 -rw-r—– 1 oracle dba 1211027456 Apr 6 20:52 arch_iim94ejv_1_1_ORA10G_20050_747780735.rman
1181564 -rw-r—– 1 oracle dba 1208732160 Apr 6 20:53 arch_ijm94el5_1_1_ORA10G_20051_747780773.rman
1181000 -rw-r—– 1 oracle dba 1208155136 Apr 6 20:53 arch_ikm94emb_1_1_ORA10G_20052_747780811.rman
1180680 -rw-r—– 1 oracle dba 1207830016 Apr 6 20:54 arch_ilm94eng_1_1_ORA10G_20053_747780848.rman
1178256 -rw-r—– 1 oracle dba 1205350400 Apr 6 20:55 arch_imm94eom_1_1_ORA10G_20054_747780886.rman
1178008 -rw-r—– 1 oracle dba 1205093376 Apr 6 20:55 arch_inm94eps_1_1_ORA10G_20055_747780924.rman
1177644 -rw-r—– 1 oracle dba 1204723200 Apr 6 20:56 arch_iom94er1_1_1_ORA10G_20056_747780961.rman
1176120 -rw-r—– 1 oracle dba 1203165184 Apr 6 20:57 arch_ipm94es7_1_1_ORA10G_20057_747780999.rman
1175052 -rw-r—– 1 oracle dba 1202071552 Apr 6 20:57 arch_iqm94etd_1_1_ORA10G_20058_747781037.rman
1174824 -rw-r—– 1 oracle dba 1201840128 Apr 6 20:58 arch_irm94eui_1_1_ORA10G_20059_747781074.rman
1174568 -rw-r—– 1 oracle dba 1201574400 Apr 6 20:58 arch_ism94evo_1_1_ORA10G_20060_747781112.rman
1041556 -rw-r—– 1 oracle dba 1065504768 Apr 6 20:59 arch_itm94f0u_1_1_ORA10G_20061_747781150.rman
340412 -rw-r—– 1 oracle dba 348232192 Apr 6 20:59 arch_ium94f23_1_1_ORA10G_20062_747781187.rman

um minuto em seguida do backup dos datafiles iniciou dos archives..
esse problema não entra na minha cabeça.. 🙄

[vieriParticipante]

http://forums.oracle.com/forums/thread. … 41#9554841

estão me ajudando no forum da oracle tb…

[Rodrigo AlmeidaParticipante]

Vieri,

Estranho mesmo.

O RMAN para archives sempre coloca em backuppiece diferente dos datafiles, porém, no modo que seu script de backup foi feito, deveria ler seus archives.

Me passa o resultado no RMAN para as sequências abaixo:

Da sequência 351691 até 351745, verifique se foi gerado os archives.

Outras dúvidas:

Esse banco de dados em algum momento esteve em NOARCHIVELOG?

O serviço de archive foi parado em algum momento?

Outro teste:

Tente realizar o RECOVER do banco até a sequência 351690.

RMAN> recover database until sequence 351690;

Outro ponto:

Veja quantas incarnações estão no seu banco de dados.

Veja se existe tabelas em NOLOG ou READ-ONLY;

Existe alguma tablespace em READ_ONLY?

Abraços,

[Rodrigo AlmeidaParticipante]

Vieri,

Veja outros pontos de atuação:

1) Catalogue os archives dos últimos 3 ou 4 dias;
2) Execute um RESTORE PREVIEW para simular o restore, exemplo:

run {

set dbid = 3909485338;
set until sequence 351690;
restore database preview;

}

3) Verifique esses sequências no banco de dados (mount) na v$archvied_logs;

Abraços,

[vieriParticipante]

Rodrigo entrei aqui, para dar uma posição do post.

testando alguma comandos, hoje eu consegui restaurar os archive com o seguinte comando:

restore archivelog scn between 9833061732 and 9833933809;

mas descobri que esses archives não são os archives correspondente ao horário correto do backup, apesar de ser da mesma base, já solicitei ao pessoa de redes baixar os archives corretos da fita.

vou responder seus questionamentos no proximo post.

[vieriParticipante]

então vamos as respostas:

Da sequência 351691 até 351745, verifique se foi gerado os archives.

foram gerados sim.. mas nos archives que eu restaurei estão os da sequencia
351771 até 351821, por isso não consegui fazer o recover ainda.
estou baixando mais 70Gb de arch da fita do dia 06 que é o dia do backup.

Outras dúvidas:

Esse banco de dados em algum momento esteve em NOARCHIVELOG?
não
O serviço de archive foi parado em algum momento?
não

Tente realizar o RECOVER do banco até a sequência 351690.

RMAN> recover database until sequence 351690;

RMAN> recover database until sequence 351690;

Starting recover at 02-MAY-11
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=1086 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=1084 devtype=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: sid=1089 devtype=DISK
allocated channel: ORA_DISK_4
channel ORA_DISK_4: sid=1085 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 05/02/2011 17:14:39
RMAN-06556: datafile 1 must be restored from backup older than scn 9832292980

Veja quantas incarnações estão no seu banco de dados.

[oracle@admbi1 archive]$ rman target /
Recovery Manager: Release 10.2.0.3.0 – Production on Mon May 2 17:15:19 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: ORA10G (DBID=3909485338, not open)
RMAN> list incarnation ;
using target database control file instead of recovery catalog
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time

---

1 1 ORA10G 3909485338 CURRENT 1 16-MAY-06

Veja se existe tabelas em NOLOG ou READ-ONLY;
não
Existe alguma tablespace em READ_ONLY?
não

RMAN> run {

set dbid = 3909485338;
set until sequence 351690;
restore database preview;

} 2> 3> 4> 5> 6> 7>

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03032: this option of set command needs to be used outside of a run block

RMAN> set dbid = 3909485338;

executing command: SET DBID
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of CSET command at 05/02/2011 17:17:11
RMAN-06188: cannot use command when connected to a mounted target database

/u02/oracle/archive/1_351787_590613210.dbf
351787 1 16-MAY-06

/u02/oracle/archive/1_351788_590613210.dbf
351788 1 16-MAY-06

NAME

SEQUENCE# RESETLOGS_CHANGE# RESETLOGS

---

/u02/oracle/archive/1_351789_590613210.dbf
351789 1 16-MAY-06

/u02/oracle/archive/1_351790_590613210.dbf
351790 1 16-MAY-06

/u02/oracle/archive/1_351791_590613210.dbf
351791 1 16-MAY-06

NAME

SEQUENCE# RESETLOGS_CHANGE# RESETLOGS

---

/u02/oracle/archive/1_351792_590613210.dbf
351792 1 16-MAY-06

/u02/oracle/archive/1_351793_590613210.dbf
351793 1 16-MAY-06

/u02/oracle/archive/1_351794_590613210.dbf
351794 1 16-MAY-06

NAME

SEQUENCE# RESETLOGS_CHANGE# RESETLOGS

---

/u02/oracle/archive/1_351795_590613210.dbf
351795 1 16-MAY-06

/u02/oracle/archive/1_351796_590613210.dbf
351796 1 16-MAY-06

/u02/oracle/archive/1_351797_590613210.dbf
351797 1 16-MAY-06

NAME

SEQUENCE# RESETLOGS_CHANGE# RESETLOGS

---

/u02/oracle/archive/1_351798_590613210.dbf
351798 1 16-MAY-06

/u02/oracle/archive/1_351799_590613210.dbf
351799 1 16-MAY-06

/u02/oracle/archive/1_351800_590613210.dbf
351800 1 16-MAY-06

NAME

SEQUENCE# RESETLOGS_CHANGE# RESETLOGS

---

/u02/oracle/archive/1_351801_590613210.dbf
351801 1 16-MAY-06

/u02/oracle/archive/1_351802_590613210.dbf
351802 1 16-MAY-06

/u02/oracle/archive/1_351803_590613210.dbf
351803 1 16-MAY-06

NAME

SEQUENCE# RESETLOGS_CHANGE# RESETLOGS

---

/u02/oracle/archive/1_351804_590613210.dbf
351804 1 16-MAY-06

/u02/oracle/archive/1_351805_590613210.dbf
351805 1 16-MAY-06

/u02/oracle/archive/1_351806_590613210.dbf
351806 1 16-MAY-06

NAME

SEQUENCE# RESETLOGS_CHANGE# RESETLOGS

---

/u02/oracle/archive/1_351807_590613210.dbf
351807 1 16-MAY-06

/u02/oracle/archive/1_351808_590613210.dbf
351808 1 16-MAY-06

/u02/oracle/archive/1_351809_590613210.dbf
351809 1 16-MAY-06

NAME

SEQUENCE# RESETLOGS_CHANGE# RESETLOGS

---

/u02/oracle/archive/1_351810_590613210.dbf
351810 1 16-MAY-06

/u02/oracle/archive/1_351811_590613210.dbf
351811 1 16-MAY-06

/u02/oracle/archive/1_351812_590613210.dbf
351812 1 16-MAY-06

NAME

SEQUENCE# RESETLOGS_CHANGE# RESETLOGS

---

/u02/oracle/archive/1_351813_590613210.dbf
351813 1 16-MAY-06

/u02/oracle/archive/1_351814_590613210.dbf
351814 1 16-MAY-06

/u02/oracle/archive/1_351815_590613210.dbf
351815 1 16-MAY-06

NAME

SEQUENCE# RESETLOGS_CHANGE# RESETLOGS

---

/u02/oracle/archive/1_351816_590613210.dbf
351816 1 16-MAY-06

/u02/oracle/archive/1_351817_590613210.dbf
351817 1 16-MAY-06

/u02/oracle/archive/1_351818_590613210.dbf
351818 1 16-MAY-06

NAME

SEQUENCE# RESETLOGS_CHANGE# RESETLOGS

---

/u02/oracle/archive/1_351819_590613210.dbf
351819 1 16-MAY-06

/u02/oracle/archive/1_351820_590613210.dbf
351820 1 16-MAY-06

/u02/oracle/archive/1_351821_590613210.dbf
351821 1 16-MAY-06

NAME

SEQUENCE# RESETLOGS_CHANGE# RESETLOGS

---

/u02/oracle/archive/1_351822_590613210.dbf
351822 1 16-MAY-06

/u02/oracle/archive/1_351823_590613210.dbf
351823 1 16-MAY-06

/u02/oracle/archive/1_351824_590613210.dbf
351824 1 16-MAY-06

NAME

SEQUENCE# RESETLOGS_CHANGE# RESETLOGS

---

/u02/oracle/archive/1_351825_590613210.dbf
351825 1 16-MAY-06

/u02/oracle/archive/1_351826_590613210.dbf
351826 1 16-MAY-06

/u02/oracle/archive/1_351827_590613210.dbf
351827 1 16-MAY-06

NAME

SEQUENCE# RESETLOGS_CHANGE# RESETLOGS

---

/u02/oracle/archive/1_351828_590613210.dbf
351828 1 16-MAY-06

/u02/oracle/archive/1_351829_590613210.dbf
351829 1 16-MAY-06

/u02/oracle/archive/1_351830_590613210.dbf
351830 1 16-MAY-06

NAME

SEQUENCE# RESETLOGS_CHANGE# RESETLOGS

---

/u02/oracle/archive/1_351831_590613210.dbf
351831 1 16-MAY-06

/u02/oracle/archive/1_351832_590613210.dbf
351832 1 16-MAY-06

/u02/oracle/archive/1_351833_590613210.dbf
351833 1 16-MAY-06

NAME

SEQUENCE# RESETLOGS_CHANGE# RESETLOGS

---

/u02/oracle/archive/1_351834_590613210.dbf
351834 1 16-MAY-06

/u02/oracle/archive/1_351835_590613210.dbf
351835 1 16-MAY-06

/u02/oracle/archive/1_351836_590613210.dbf
351836 1 16-MAY-06

NAME

SEQUENCE# RESETLOGS_CHANGE# RESETLOGS

---

/u02/oracle/archive/1_351837_590613210.dbf
351837 1 16-MAY-06

/u02/oracle/archive/1_351838_590613210.dbf
351838 1 16-MAY-06

/u02/oracle/archive/1_351839_590613210.dbf
351839 1 16-MAY-06

NAME

SEQUENCE# RESETLOGS_CHANGE# RESETLOGS

---

/u02/oracle/archive/1_351840_590613210.dbf
351840 1 16-MAY-06

/u02/oracle/archive/1_351841_590613210.dbf
351841 1 16-MAY-06

🙄

[CleitonHanzenParticipante]

Vieri,

Quando vc fez o restore dos archives através do comando “restore archivelog scn between 9833061732 and 9833933809; ” de qual backuppiece que o RMAN leu?

[vieriParticipante]

varreu todos backupsets que eu já havia catalogado.

O problema do catalog dos archives eu resolvi.

O RMAN gera um erro totalmente sem sentido quando catalogamos um backuppiece que contem archivelogs com o comando catalog archivelog,
ao invês de ele dizer pra usar o backuppiece ele diz erro de DBID diferentes, esse foi o motivo da confusão.
Já restaurei os archives, mas to fazendo o restore novamente, pois aquele deu problema.

QQ novidade eu posto ai.. como é uma base de relatório de 1.2TB eu tenho até segunda feira para liberar o servidor… o problema é que a infra de backup/restore aqui naõ é tão potente para uma base mto grande. temos mta falhas.

[Autor]

Posts