Menu de navegação

[brazaParticipante]

Bom dia,

Pessoal, estou com a seguinte ideia e gostaria de saber se é possível.

Estou simulando uma migração de servidor de banco de dados. E nesne momento a ideia é a seguinte:

1) Fazer o backup da base de produção;

2) Restaurá-la no novo servidor;

3) Após a restauração, parar o banco de produção e aplicar todos os logs gerados desde do último backup até então. E depois desativar o servidor de banco antigo.

Esta jogada com os logs é para diminuir o tempo de parada ao máximo.

É válida essa ideia?

Eu já fiz o backup e restaurei no novo servidor. Falta aplicar os logs do servidor atual no novo servidor. qual a melhor forma de fazer isso?

Obrigado.

[rmanParticipante]

@braza

A ideia é essa mesma, só é necessário garantir que o novo servidor possui a mesma versão do antigo, exemplo: 10.2.0.4.0. Todo patch aplicado no antigo deve ser aplicado no novo.

Após o RESTORE DATABASE basta apenas o RECOVER DATABASE.

Antes do RECOVER DATABASE, copie todos os archives log para a área de archive.

[brazaParticipante]

[quote=”rman”:12onzdhg]@braza

A ideia é essa mesma, só é necessário garantir que o novo servidor possui a mesma versão do antigo, exemplo: 10.2.0.4.0. Todo patch aplicado no antigo deve ser aplicado no novo.

Após o RESTORE DATABASE basta apenas o RECOVER DATABASE.

Antes do RECOVER DATABASE, copie todos os archives log para a área de archive.[/quote]

OK.

Mas eu tenho uma dúvida.

É necessário subir o banco novo com o controlfile mais recente do servidor atual, Já que ele armazena o nome dos arquivelog gerados?

Outra coisa… No novo servidor, as unidades de armazenamento não são as mesmas. Passaram de G e J para unidade S.

[rmanParticipante]

@braza

É necessário restaurar o control file do backup, pois o control file do novo servidor não conhece o seu backup.


RMAN> RESTORE CONTROLFILE FROM '/PATH/COMPLETO/DO/BACKUP/DO/CONTROLFILE/'


Infelizmente você terá que manter toda hierarquia de pasta identicas ao servidor antigo, ele irá procurar em G e J.

[brazaParticipante]

[quote=”rman”:ndcx8xy1]@braza

É necessário restaurar o control file do backup, pois o control file do novo servidor não conhece o seu backup.


RMAN> RESTORE CONTROLFILE FROM '/PATH/COMPLETO/DO/BACKUP/DO/CONTROLFILE/'


Infelizmente você terá que manter toda hierarquia de pasta identicas ao servidor antigo, ele irá procurar em G e J.[/quote]

Ok.

Vou executar esses passos então. Depois posto o resultado.

Valeu rman !!!!

[brazaParticipante]

[quote=”braza”:1tran55g][quote=”rman”:1tran55g]@braza

É necessário restaurar o control file do backup, pois o control file do novo servidor não conhece o seu backup.


RMAN> RESTORE CONTROLFILE FROM '/PATH/COMPLETO/DO/BACKUP/DO/CONTROLFILE/'


Infelizmente você terá que manter toda hierarquia de pasta identicas ao servidor antigo, ele irá procurar em G e J.[/quote]

Ok.

Vou executar esses passos então. Depois posto o resultado.

Valeu rman !!!![/quote]

Amigo,

O restore não está procurando por archivelog, está procurando por backup de archivelog.

O oracle não está procurando os logs na área de recuperação flash, está procurando no servidor onde eu fiz o backup.

O que está de errado???

---

RMAN> run {
2>
3> recover database;
4>
5> }
Starting recover at 12-DEC-11
using channel ORA_DISK_1

starting media recovery

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 12/12/2011 15:41:12
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 57050 lowscn 6036803022 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57049 lowscn 6036767772 found to resto
re

[rmanParticipante]

@braza

Como é a sua politica de backup ?

Pelo que você disse, provavelmente você deve fazer backup de archive log de tempos em tempos… Copie então todos os backup de archive log gerados depois do backup que você quer restaurar…

Como disse, a hierarquia de diretorio deve ser identica, executa um TREE no diretorio do oracle, e confira com o do novo servidor.

Copie o backup e o backup de archive na mesma localização no novo servidor, já foi restaurado o control file no servidor novo ?

[brazaParticipante]

[quote=”rman”:1p1vinml]@braza

Como é a sua politica de backup ?

Pelo que você disse, provavelmente você deve fazer backup de archive log de tempos em tempos… Copie então todos os backup de archive log gerados depois do backup que você quer restaurar…

Como disse, a hierarquia de diretorio deve ser identica, executa um TREE no diretorio do oracle, e confira com o do novo servidor.

Copie o backup e o backup de archive na mesma localização no novo servidor, já foi restaurado o control file no servidor novo ?[/quote]

Já fiz o restore. Falta apenas copiar os logs.

Pela mensagem de erro, ele está procurando no servidor onde eu fiz o backup. Mas os logs estão na máquina local, na área de recuperação flash.

---

RMAN> run {
2>
3> recover database;
4>
5> }
Starting recover at 12-DEC-11
using channel ORA_DISK_1

starting media recovery

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 12/12/2011 15:41:12
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 57050 lowscn 6036803022 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57049 lowscn 6036767772 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57048 lowscn 6036720059 found to resto
re

[brazaParticipante]

[quote=”braza”:1e1qkczz][quote=”rman”:1e1qkczz]@braza

Como é a sua politica de backup ?

Pelo que você disse, provavelmente você deve fazer backup de archive log de tempos em tempos… Copie então todos os backup de archive log gerados depois do backup que você quer restaurar…

Como disse, a hierarquia de diretorio deve ser identica, executa um TREE no diretorio do oracle, e confira com o do novo servidor.

Copie o backup e o backup de archive na mesma localização no novo servidor, já foi restaurado o control file no servidor novo ?[/quote]

Já fiz o restore. Falta apenas copiar os logs.

Pela mensagem de erro, ele está procurando no servidor onde eu fiz o backup. Mas os logs estão na máquina local, na área de recuperação flash.

---

RMAN> run {
2>
3> recover database;
4>
5> }
Starting recover at 12-DEC-11
using channel ORA_DISK_1

starting media recovery

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 12/12/2011 15:41:12
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 57050 lowscn 6036803022 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57049 lowscn 6036767772 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57048 lowscn 6036720059 found to resto
re[/quote]

Amigo,

Já baguncei tanto esse banco de teste que vou fazer tudo de novo, agora com mais calma. Assim que terminar, posto os resultados.

Valeu !!!!!

[brazaParticipante]

Bom dia Amigo,

Refiz os passos citados e ainda não obtive êxito.

Fiz o backup e fiz o restore. Ambos realizado com sucesso.

O restore demorou 1 dia pra ser feito.

Peguei todos os redologs gerados no banco de produção e os cataloguei na área de recuperação flash.

RMAN> catalog recovery area;

Quando executei o recovery, ocorreu o seguinte erro:

++++++++++++++++++++++++++++++++++++++++++++

RMAN> @S:oracle_dadosBD_ajurirecovery.txt

RMAN> run {
2>
3> recover database;
4>
5> }
Starting recover at 16-DEC-11
using channel ORA_DISK_1

starting media recovery

archive log thread 1 sequence 57104 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57104.DBF
archive log thread 1 sequence 57105 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57105.DBF
archive log thread 1 sequence 57106 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57106.DBF
archive log thread 1 sequence 57107 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57107.DBF
archive log thread 1 sequence 57108 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57108.DBF
archive log thread 1 sequence 57109 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57109.DBF
archive log thread 1 sequence 57110 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57110.DBF
archive log thread 1 sequence 57111 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57111.DBF
archive log thread 1 sequence 57112 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57112.DBF
archive log thread 1 sequence 57113 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57113.DBF
archive log thread 1 sequence 57114 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57114.DBF
archive log thread 1 sequence 57115 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57115.DBF
archive log thread 1 sequence 57116 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57116.DBF
archive log thread 1 sequence 57117 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57117.DBF
archive log thread 1 sequence 57118 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57118.DBF
archive log thread 1 sequence 57119 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57119.DBF
archive log thread 1 sequence 57120 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57120.DBF
archive log thread 1 sequence 57121 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57121.DBF
archive log thread 1 sequence 57122 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57122.DBF
archive log thread 1 sequence 57123 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57123.DBF
archive log thread 1 sequence 57124 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57124.DBF
archive log thread 1 sequence 57125 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57125.DBF
archive log thread 1 sequence 57126 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57126.DBF
archive log thread 1 sequence 57127 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57127.DBF
archive log thread 1 sequence 57128 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57128.DBF
archive log thread 1 sequence 57129 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57129.DBF
archive log thread 1 sequence 57130 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57130.DBF
archive log thread 1 sequence 57131 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57131.DBF
archive log thread 1 sequence 57132 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57132.DBF
archive log thread 1 sequence 57133 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57133.DBF
archive log thread 1 sequence 57134 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57134.DBF
archive log thread 1 sequence 57135 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57135.DBF
archive log thread 1 sequence 57136 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57136.DBF
archive log thread 1 sequence 57137 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57137.DBF
archive log thread 1 sequence 57138 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57138.DBF
archive log thread 1 sequence 57139 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57139.DBF
archive log thread 1 sequence 57140 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57140.DBF
archive log thread 1 sequence 57141 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57141.DBF
archive log thread 1 sequence 57142 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57142.DBF
archive log thread 1 sequence 57143 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57143.DBF
archive log thread 1 sequence 57144 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57144.DBF
archive log thread 1 sequence 57145 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57145.DBF
archive log thread 1 sequence 57146 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57146.DBF
archive log thread 1 sequence 57147 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57147.DBF
archive log thread 1 sequence 57148 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57148.DBF
archive log thread 1 sequence 57149 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57149.DBF
archive log thread 1 sequence 57150 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57150.DBF
archive log thread 1 sequence 57151 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57151.DBF
archive log thread 1 sequence 57152 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57152.DBF
archive log thread 1 sequence 57153 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57153.DBF
archive log thread 1 sequence 57154 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57154.DBF
archive log thread 1 sequence 57155 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57155.DBF
archive log thread 1 sequence 57156 is already on disk as file S:ORACLE_DADOSB
D_AJURIREDO03.LOG
archive log thread 1 sequence 57157 is already on disk as file S:ORACLE_DADOSB
D_AJURIREDO02.LOG
archive log thread 1 sequence 57158 is already on disk as file S:ORACLE_DADOSB
D_AJURIREDO01.LOG
Oracle Error:
ORA-01547: advertencia: RECOVER obteve exito mas OPEN RESETLOGS obteria erro aba
ixo
ORA-01152: o arquivo 1 n?o foi restaurado a partir de um backup suficientemente
antigo
ORA-01110: 1 do arquivo de dados: ‘S:ORACLE_DADOSBD_AJURIAPLICACAO_AJURIDADO
SSYSTEM01.DBF’

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 12/16/2011 10:57:58
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 57103 lowscn 6041395820 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57102 lowscn 6041353448 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57101 lowscn 6041296228 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57100 lowscn 6041272906 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57099 lowscn 6041246391 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57098 lowscn 6041180445 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57097 lowscn 6041158004 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57096 lowscn 6041157126 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57095 lowscn 6041136677 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57094 lowscn 6041044527 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57093 lowscn 6040970937 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57092 lowscn 6040879708 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57091 lowscn 6040728419 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57090 lowscn 6040623003 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57089 lowscn 6040512803 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57088 lowscn 6040400179 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57087 lowscn 6040289560 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57086 lowscn 6040181708 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57085 lowscn 6040070854 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57084 lowscn 6039969640 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57083 lowscn 6039822559 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57082 lowscn 6039677896 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57081 lowscn 6039585847 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57080 lowscn 6039436250 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57079 lowscn 6039322526 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57078 lowscn 6039201810 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57077 lowscn 6039076462 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57076 lowscn 6038851039 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57075 lowscn 6038726945 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57074 lowscn 6038624604 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57073 lowscn 6038507335 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57072 lowscn 6038392475 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57071 lowscn 6038271452 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57070 lowscn 6038178794 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57069 lowscn 6038134894 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57068 lowscn 6038095186 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57067 lowscn 6038058116 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57066 lowscn 6038018898 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57065 lowscn 6037979662 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57064 lowscn 6037945238 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57063 lowscn 6037861237 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57062 lowscn 6037755300 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57061 lowscn 6037639490 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57060 lowscn 6037514192 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57059 lowscn 6037393122 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57058 lowscn 6037301195 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57057 lowscn 6037277375 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57056 lowscn 6037145246 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57055 lowscn 6037014404 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57054 lowscn 6036986659 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57053 lowscn 6036983133 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57052 lowscn 6036928343 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57051 lowscn 6036896435 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57050 lowscn 6036803022 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57049 lowscn 6036767772 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57048 lowscn 6036720059 found to resto
re
MAN-
RMAN> end-of-file

RMAN>

++++++++++++++++++++++++++++++++++++++++++++++

O que está de errado? alguém pode me ajudar?

O RMAN está procurando por logs que já foram deletados a muito tempo, bem antes do backup.

Obrigado.

[rmanParticipante]

@braza

Descreva comando a comando rodado no RMAN assim dá pra identificar se está faltando algo…

[fabiogaleraParticipante]

O seu recovery esta pedindo da sequence 57048 até 57103.

vamos tentar organizar isso:

• Como você fez o restore ?
• Me explica exatamente o que você fez, faz uma timeline ae do que se fez, quando, que archives você pegou, pra onde foi os backups pieces, etc …

Me desculpe, mas tá bem difícil saber como você esta fazendo.

[brazaParticipante]

[quote=”fabiogalera”:2rcpk7tb]O seu recovery esta pedindo da sequence 57048 até 57103.

vamos tentar organizar isso:

• Como você fez o restore ?
• Me explica exatamente o que você fez, faz uma timeline ae do que se fez, quando, que archives você pegou, pra onde foi os backups pieces, etc …

Me desculpe, mas tá bem difícil saber como você esta fazendo.[/quote]

Vamos lá…

Eu estou querendo fazer a migração de um banco de dados de um servidor para outro. Neste momento estou fazendo uma simulação disso.

1) Faço o backup no banco de produção;

RMAN> backup database plus archivelog;

2) Após esse backup faço o restore no novo servidor;

Esse restore leva 1 dia pra ser feito. Durante esse processo o banco de produção está gerando log.

Quando o meu restore terminar, eu pretendo parar o banco de produção e aplicar, esses logs gerados, no novo servidor e desativar o banco de produção, assim eu não perco nenhuma transação realizada.

Tudo isso com o intuito de parar o banco de produção pelo menor tempo possível nessa migração.

O comando foi o seguinte:

++++++++++++++++++++++++++++++++++

run {

set newname for datafile 1 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSSYSTEM01.DBF’;
set newname for datafile 2 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSUNDOTBS01.DBF’;
set newname for datafile 3 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSCWMLITE01.DBF’;
set newname for datafile 4 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSDRSYS01.DBF’;
set newname for datafile 5 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSINDX01.DBF’;
set newname for datafile 6 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSODM01.DBF’;
set newname for datafile 7 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSTOOLS01.DBF’;
set newname for datafile 8 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSUSERS01.DBF’;
set newname for datafile 9 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSXDB01.DBF’;
set newname for datafile 10 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSAJURI_DADOS.ORA’;
set newname for datafile 11 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSAJURI_INDICES.ORA’;
set newname for datafile 12 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSARRECADACAO_DADOS.ORA’;
set newname for datafile 13 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSARRECADACAO_INDICES.ORA’;
set newname for datafile 14 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSCLIENTE_DADOS.ORA’;
set newname for datafile 15 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSCLIENTE_INDICES.ORA’;
set newname for datafile 16 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSFATURAS_INDICES.ORA’;
set newname for datafile 17 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSFECHAMENTO_DADOS.ORA’;
set newname for datafile 18 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSFECHAMENTO_INDICES.ORA’;
set newname for datafile 19 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSLANCAMENTO_INDICES.ORA’;
set newname for datafile 20 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSOS_INDICES.ORA’;
set newname for datafile 21 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSFCADAS1.ORA’;
set newname for datafile 22 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSFCONSU1.ORA’;
set newname for datafile 23 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSFENTREG1.ORA’;
set newname for datafile 24 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSHMEDIC1.ORA’;
set newname for datafile 25 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSHMEDID1.ORA’;
set newname for datafile 26 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSLANC1.ORA’;
set newname for datafile 27 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSOCINT1.ORA’;
set newname for datafile 28 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSICMSDOC1.ORA’;
set newname for datafile 29 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSEVUC1.ORA’;
set newname for datafile 30 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSOSER1.ORA’;
set newname for datafile 31 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSHISTORICO_INDICES.ORA’;
set newname for datafile 32 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSTOAD.ORA’;
set newname for datafile 33 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSTESTEBAK.ORA’;
set newname for datafile 34 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSRAMO.ORA’;
set newname for datafile 35 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSW_DADOS.ORA’;
set newname for datafile 36 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSLANC_LIXO.ORA’;
set newname for datafile 37 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSW_DADOS2.ORA’;
set newname for datafile 38 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSFATURAS_COMPLEMENTO.ORA’;
set newname for datafile 39 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSFECHAMENTO_DADOS_2.ORA’;
set newname for datafile 40 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSFCADAS2.ORA’;
set newname for datafile 41 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSEMP_CEAL.ORA’;
set newname for datafile 42 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSAJURI_DADOS2.ORA’;
set newname for datafile 43 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSICMSDOC2.ORA’;
set newname for datafile 44 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSICMSDOC3.ORA’;
set newname for datafile 45 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSW_DADOS3.ORA’;
set newname for datafile 46 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSPERFSTAT_TBS.ORA’;
set newname for datafile 47 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSFCONSU2.ORA’;
set newname for datafile 48 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSW_DADOS3_1.ORA’;
set newname for datafile 49 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOS.FCADAS3ORA’;
set newname for datafile 50 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSICMSDOC3_1.ORA’;
set newname for datafile 51 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSFCADAS4.ORA’;
set newname for datafile 52 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSICMSDOC4.ORA’;
set newname for datafile 53 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSFECHAMENTO_DADOS_3.ORA’;
set newname for datafile 54 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSUNDOTBS02.ORA’;
set newname for datafile 55 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSUNDOTBS03.ORA’;
set newname for datafile 56 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSUNDOTBS04.ORA’;
set newname for datafile 57 to ‘S:oracle_dadosBD_ajuriaplicacao_ajuridadosDADOSAJURI_INDICES2.ORA’;

set until SCN 6042153424;

restore database;

switch datafile all;

}

++++++++++++++++++++++++++++++++++

Esse comando foi realizado com sucesso. (Eu vi esse script na documentação da Oracle).

3) Depois do restore, eu copiei os logs do banco de produção para a área de recuperação flash do novo servidor e os cataloguei.

RMAN> catalog recovery area;

4) Depois de catalogados, executei o comando recover.

++++++++++++++++++++++++++++++++++++

RMAN> recover database;

++++++++++++++++++++++++++++++++++++

5) E obtive o seguinte resultado:

++++++++++++++++++++++++++++++++++++

RMAN> recover database;

Starting recover at 16-DEC-11
using channel ORA_DISK_1

starting media recovery

archive log thread 1 sequence 57104 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57104.DBF
archive log thread 1 sequence 57105 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57105.DBF
archive log thread 1 sequence 57106 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57106.DBF
archive log thread 1 sequence 57107 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57107.DBF
archive log thread 1 sequence 57108 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57108.DBF
archive log thread 1 sequence 57109 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57109.DBF
archive log thread 1 sequence 57110 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57110.DBF
archive log thread 1 sequence 57111 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57111.DBF
archive log thread 1 sequence 57112 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57112.DBF
archive log thread 1 sequence 57113 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57113.DBF
archive log thread 1 sequence 57114 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57114.DBF
archive log thread 1 sequence 57115 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57115.DBF
archive log thread 1 sequence 57116 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57116.DBF
archive log thread 1 sequence 57117 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57117.DBF
archive log thread 1 sequence 57118 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57118.DBF
archive log thread 1 sequence 57119 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57119.DBF
archive log thread 1 sequence 57120 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57120.DBF
archive log thread 1 sequence 57121 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57121.DBF
archive log thread 1 sequence 57122 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57122.DBF
archive log thread 1 sequence 57123 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57123.DBF
archive log thread 1 sequence 57124 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57124.DBF
archive log thread 1 sequence 57125 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57125.DBF
archive log thread 1 sequence 57126 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57126.DBF
archive log thread 1 sequence 57127 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57127.DBF
archive log thread 1 sequence 57128 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57128.DBF
archive log thread 1 sequence 57129 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57129.DBF
archive log thread 1 sequence 57130 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57130.DBF
archive log thread 1 sequence 57131 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57131.DBF
archive log thread 1 sequence 57132 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57132.DBF
archive log thread 1 sequence 57133 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57133.DBF
archive log thread 1 sequence 57134 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57134.DBF
archive log thread 1 sequence 57135 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57135.DBF
archive log thread 1 sequence 57136 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57136.DBF
archive log thread 1 sequence 57137 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57137.DBF
archive log thread 1 sequence 57138 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57138.DBF
archive log thread 1 sequence 57139 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57139.DBF
archive log thread 1 sequence 57140 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57140.DBF
archive log thread 1 sequence 57141 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57141.DBF
archive log thread 1 sequence 57142 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57142.DBF
archive log thread 1 sequence 57143 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57143.DBF
archive log thread 1 sequence 57144 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57144.DBF
archive log thread 1 sequence 57145 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57145.DBF
archive log thread 1 sequence 57146 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57146.DBF
archive log thread 1 sequence 57147 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57147.DBF
archive log thread 1 sequence 57148 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57148.DBF
archive log thread 1 sequence 57149 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57149.DBF
archive log thread 1 sequence 57150 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57150.DBF
archive log thread 1 sequence 57151 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57151.DBF
archive log thread 1 sequence 57152 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57152.DBF
archive log thread 1 sequence 57153 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57153.DBF
archive log thread 1 sequence 57154 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57154.DBF
archive log thread 1 sequence 57155 is already on disk as file S:ORACLE_DADOSB
D_AJURIFLASH_RECOVERY_AREAAJURI1_57155.DBF
archive log thread 1 sequence 57156 is already on disk as file S:ORACLE_DADOSB
D_AJURIREDO03.LOG
archive log thread 1 sequence 57157 is already on disk as file S:ORACLE_DADOSB
D_AJURIREDO02.LOG
archive log thread 1 sequence 57158 is already on disk as file S:ORACLE_DADOSB
D_AJURIREDO01.LOG
Oracle Error:
ORA-01547: advertencia: RECOVER obteve exito mas OPEN RESETLOGS obteria erro aba
ixo
ORA-01152: o arquivo 1 n?o foi restaurado a partir de um backup suficientemente
antigo
ORA-01110: 1 do arquivo de dados: ‘S:ORACLE_DADOSBD_AJURIAPLICACAO_AJURIDADO
SSYSTEM01.DBF’

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 12/16/2011 14:15:36
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 57103 lowscn 6041395820 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57102 lowscn 6041353448 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57101 lowscn 6041296228 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57100 lowscn 6041272906 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57099 lowscn 6041246391 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57098 lowscn 6041180445 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57097 lowscn 6041158004 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57096 lowscn 6041157126 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57095 lowscn 6041136677 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57094 lowscn 6041044527 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57093 lowscn 6040970937 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57092 lowscn 6040879708 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57091 lowscn 6040728419 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57090 lowscn 6040623003 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57089 lowscn 6040512803 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57088 lowscn 6040400179 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57087 lowscn 6040289560 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57086 lowscn 6040181708 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57085 lowscn 6040070854 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57084 lowscn 6039969640 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57083 lowscn 6039822559 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57082 lowscn 6039677896 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57081 lowscn 6039585847 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57080 lowscn 6039436250 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57079 lowscn 6039322526 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57078 lowscn 6039201810 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57077 lowscn 6039076462 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57076 lowscn 6038851039 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57075 lowscn 6038726945 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57074 lowscn 6038624604 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57073 lowscn 6038507335 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57072 lowscn 6038392475 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57071 lowscn 6038271452 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57070 lowscn 6038178794 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57069 lowscn 6038134894 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57068 lowscn 6038095186 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57067 lowscn 6038058116 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57066 lowscn 6038018898 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57065 lowscn 6037979662 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57064 lowscn 6037945238 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57063 lowscn 6037861237 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57062 lowscn 6037755300 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57061 lowscn 6037639490 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57060 lowscn 6037514192 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57059 lowscn 6037393122 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57058 lowscn 6037301195 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57057 lowscn 6037277375 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57056 lowscn 6037145246 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57055 lowscn 6037014404 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57054 lowscn 6036986659 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57053 lowscn 6036983133 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57052 lowscn 6036928343 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57051 lowscn 6036896435 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57050 lowscn 6036803022 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57049 lowscn 6036767772 found to resto
re
RMAN-06025: no backup of log thread 1 seq 57048 lowscn 6036720059 found to resto
re
MAN-
RMAN>

++++++++++++++++++++++++++++++++++++

Existiam neste momento as sequencias de 57104 a 57157.

Esses outros arquives que o Oracle está pedindo são antigos e nem existiam mais quando foi feito o backup.

Conseguimos ter um entendimento do situação?

[fabiogaleraParticipante]

Vamos lá.

Primeiro, verifique se você esta fazendo backup de controlfile:

— RMAN
show all;

Verifique se o AUTOBACKUP está ativado.

Se estiver, você não precisa catalogar qualquer archive, pois o Controlfile já vai saber qual é qual.

No seu restore, qual o intuito de usar set until SCN 6042153424 ?

Provavelmente você apenas tá fazendo restore até esse ponto e por isso que o Oracle esta pedindo novos archives, provavelmente o archive 102 é o SCN 6042153424 + 1.

Entendeu ?

Retire o set until SCN 6042153424 e seja feliz.

[brazaParticipante]

[quote=”fabiogalera”:32495ds5]Vamos lá.

Primeiro, verifique se você esta fazendo backup de controlfile:

— RMAN
show all;

Verifique se o AUTOBACKUP está ativado.

Se estiver, você não precisa catalogar qualquer archive, pois o Controlfile já vai saber qual é qual.

No seu restore, qual o intuito de usar set until SCN 6042153424 ?

Provavelmente você apenas tá fazendo restore até esse ponto e por isso que o Oracle esta pedindo novos archives, provavelmente o archive 102 é o SCN 6042153424 + 1.

Entendeu ?

Retire o set until SCN 6042153424 e seja feliz.[/quote]

Entendi.

Vou refazer o restore novamente e depois posto os resultados. Isso vai levar mais um dia.

Valeu!!!

[Autor]

Posts