Skip to Main Content

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Standby do not apply logs

995a7537-0317-4415-a163-55ba05b39605Mar 1 2017 — edited Mar 1 2017

Hi gurus,

Oracle Version 11.2.0.1 STANDARD EDITION

I'm having this issue with this physical standby in Standard Edition.

To be honest I'm not used to work with standrtd edition but this is the configuration I've.

After following the instruction to create the standby in standrd edition, with RMAN, my standby is created not withous some issues.

Here' what I've

Those are the last line from the duplication for standby process

.

.

.

contents of Memory Script:

{

   set until scn  6625561364;

   recover

   standby

   clone database

    delete archivelog

   ;

}

executing Memory Script

executing command: SET until clause

Starting recover at 01-MAR-17

starting media recovery

archived log for thread 1 with sequence 22002 is already on disk as file /oracle/flash_recovery_area/SICAVPRA/arch/sicav_1_22002_785354316.arc

archived log for thread 1 with sequence 22003 is already on disk as file /oracle/flash_recovery_area/SICAVPRA/arch/sicav_1_22003_785354316.arc

archived log file name=/oracle/flash_recovery_area/SICAVPRA/arch/sicav_1_22002_785354316.arc thread=1 sequence=22002

archived log file name=/oracle/flash_recovery_area/SICAVPRA/arch/sicav_1_22003_785354316.arc thread=1 sequence=22003

media recovery complete, elapsed time: 00:00:25

Finished recover at 01-MAR-17

ORACLE error from auxiliary database: ORA-19527: le fichier de journalisation de secours physique doit etre renomme

ORA-00312: journal en ligne 1 thread 1 : '/oracle/oradata/SICAV/redo01.log'

RMAN-05535: WARNING: All redo log files were not defined properly.

ORACLE error from auxiliary database: ORA-19527: le fichier de journalisation de secours physique doit etre renomme

ORA-00312: journal en ligne 2 thread 1 : '/oracle/oradata/SICAV/redo02.log'

RMAN-05535: WARNING: All redo log files were not defined properly.

ORACLE error from auxiliary database: ORA-19527: le fichier de journalisation de secours physique doit etre renomme

ORA-00312: journal en ligne 3 thread 1 : '/oracle/oradata/SICAV/redo03.log'

RMAN-05535: WARNING: All redo log files were not defined properly.

ORACLE error from auxiliary database: ORA-19527: le fichier de journalisation de secours physique doit etre renomme

ORA-00312: journal en ligne 4 thread 1 : '/oracle/oradata/SICAV/redo04.log'

RMAN-05535: WARNING: All redo log files were not defined properly.

ORACLE error from auxiliary database: ORA-19527: le fichier de journalisation de secours physique doit etre renomme

ORA-00312: journal en ligne 5 thread 0 : '/oracle/oradata/SICAV/stbyredo05.log'

RMAN-05535: WARNING: All redo log files were not defined properly.

ORACLE error from auxiliary database: ORA-19527: le fichier de journalisation de secours physique doit etre renomme

ORA-00312: journal en ligne 6 thread 0 : '/oracle/oradata/SICAV/stbyredo06.log'

RMAN-05535: WARNING: All redo log files were not defined properly.

ORACLE error from auxiliary database: ORA-19527: le fichier de journalisation de secours physique doit etre renomme

ORA-00312: journal en ligne 7 thread 0 : '/oracle/oradata/SICAV/stbyredo07.log'

RMAN-05535: WARNING: All redo log files were not defined properly.

ORACLE error from auxiliary database: ORA-19527: le fichier de journalisation de secours physique doit etre renomme

ORA-00312: journal en ligne 8 thread 0 : '/oracle/oradata/SICAV/stbyredo08.log'

RMAN-05535: WARNING: All redo log files were not defined properly.

ORACLE error from auxiliary database: ORA-19527: le fichier de journalisation de secours physique doit etre renomme

ORA-00312: journal en ligne 9 thread 0 : '/oracle/oradata/SICAV/stbyredo09.log'

RMAN-05535: WARNING: All redo log files were not defined properly.

Finished Duplicate Db at 01-MAR-17

starting full resync of recovery catalog

full resync complete

released channel: prm1

released channel: stby1

*

I've recreated the redologs manually

SQL>  select group#,member from v$logfile;

    GROUP#

----------

MEMBER

----------------------------------------------------------------------------------------------------

         3

/oracle/oradata/SICAVPRA/redo03.log

         1

/oracle/oradata/SICAVPRA/redo01.log

         2

/oracle/oradata/SICAVPRA/redo02.log

    GROUP#

----------

MEMBER

----------------------------------------------------------------------------------------------------

         4

/oracle/oradata/SICAVPRA/redo04.log

         5

/oracle/oradata/SICAVPRA/stbyredo05.log

         6

/oracle/oradata/SICAVPRA/stbyredo06.log

    GROUP#

----------

MEMBER

----------------------------------------------------------------------------------------------------

         7

/oracle/oradata/SICAVPRA/stbyredo07.log

         8

/oracle/oradata/SICAVPRA/stbyredo08.log

         9

/oracle/oradata/SICAVPRA/stbyredo09.log

9 ligne(s) selectionnee(s).

I've started the recovery process

SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION;

Base de donnees modifiee.

SQL> select thread#, sequence#, status from v$managed_standby ;

   THREAD#  SEQUENCE# STATUS

---------- ---------- ------------

         0          0 CONNECTED

         0          0 CONNECTED

         0          0 CONNECTED

         0          0 CONNECTED

         1      22008 WAIT_FOR_LOG

I've switch logfiles in the primary site until log seq 220011 and copy the logs into the secondary site but nothing happens

I've check some post but everything they suggest didn't change anything.

Any Ideas?

TY for your help

This post has been answered by John Stegeman on Mar 1 2017
Jump to Answer
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Mar 29 2017
Added on Mar 1 2017
4 comments
1,160 views