Archive log missing causes Ogg synchronization problem, workaround

Source: Internet
Author: User

During the migration of the database, the last boot GGs

After starting GGs found the extraction process error, check the log found the following error:



2016-03-16 00:15:42 INFO OGG-01517 Position of first record processed for Thread 2, Sequence 17643, RBA 793616, SCN 1 389.3430888557, Mar 15, 2016 11:18

: Wuyi PM.


Source Context:

Sourcemodule: [ER.REDO.ORA.RTC]

SourceID: [/SCRATCH/AIME1/ADESTORE/VIEWS/AIME1_ADC4150256/OGGCORE/OPENSYS/SRC/APP/ER/REDO/ORACLE/RTC.C]

Sourcefunction: [Rtc_producer]

Sourceline: [2088]

Threadbacktrace: [6] Elements

: [/opt/ggs/libgglog.so (Cmessagecontext::addthreadcontext () +0x1e) [0x2b2b07c7206e]]

: [/opt/ggs/libgglog.so (Cmessagefactory::createmessage (csourcecontext*, unsigned int, ...) +0X2CC) [0x2b2b07c6e44c]]

: [/opt/ggs/libgglog.so (_msg_err_er_generic_failure (csourcecontext*, Char const*, cmessagefactory:: messagedisposition) +0x31) [0x2b

2B07C562A9]]

: [/opt/ggs/extract (RTC_PRODUCER+0X4E1) [0X71FCC1]]

: [/lib64/libpthread.so.0 [0x33a8c0673d]]

: [/lib64/libc.so.6 (CLONE+0X6D) [0X33A80D44BD]]


2016-03-16 00:16:03 ERROR OGG-01028 Opening ASM file +dgrecovery/qfangsh/qfangsh_arch_1_20021_837910999.log in Dblogre ADER mode: (308) Ora-00308:cannot

Open archived log ' +dgrecovery/qfangsh/qfangsh_arch_1_20021_837910999.log '

Ora-17503:ksfdopn:2 Failed to open file +dgrecovery/qfangsh/qfangsh_arch_1_20021_837910999.log

Ora-15173:entry ' Qfangsh_arch_1_20021_837910999.log ' does not exist in directory ' Qfangsh '.



The discovery was caused by an archive log that could not find the triggered error.

Because we are migrating the data by using Rman to make a level 0 backup of the source library before the target repository restore.

You then recover to the latest status with Level 1 backup and archive log backups.

Ogg was stopped before the library was stopped, and the previous archive log was required to synchronize when the Ogg was reopened.


Originally my archive log was recovered through Rman all in the repository, but the source library generated an archive before shutting down, which caused this problem to occur.


Steps to resolve:

1. Obtain the required archive log from the Source Library ASM instance to the local disk.

2. SCP to target library Local disk

3. CP to the appropriate location in ASM

cp/arch/rmanbackup/thread_1_seq_20021.9753.906592877 +dgrecovery/qfangsh/qfangsh_arch_1_20021_837910999.log

4. If the archive log has been backed up by Rman, it can be restored via the Restore command, as follows:

Restore Archivelog from Logseq 20021 until logseq 20021 thread 1;


5. Restart the Ogg process, problem solving


Archive log missing causes Ogg synchronization problem, workaround

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.