Wednesday, February 4, 2015

OGG-00868 Error code 1291, error message: ORA-01291: missing logfile

OGG-00868 Error code 1291, error message: ORA-01291: missing logfile

When you are working on GoldenGate with INTEGRATED CAPTURE and you are missing some of the old archive logs; you can’t start the extract like classic capture; INTEGRATED CAPTURE will work differently; it will try to start from the registered SCN number or if it is running then you will provide all the old archive logs till the latest one;

Note: if you are missing some old archive logs then you have to rebuild the entire GG setup

You need to do the below activity

GGSCI> STOP EXTRACT E0000032
GGSCI> UNREGISTER EXTRACT E0000032 DATABASE
GGSCI> REGISTER EXTRACT E0000032 DATABASE
GGSCI> START EXTRACT E0000032
GGSCI> INFO E0000032

You should see the extract changing from STARTING to RUNNING STATE;

if you feel still it is not getting started; then you have to follow like below(wait for atleast 10 min, some time INTEGRATED CAPTURE would take time depending on your database load)

GGSCI> STOP EXTRACT E0000032
GGSCI> UNREGISTER EXTRACT E0000032 DATABASE
GGSCI> delete EXTRACT E0000032
GGSCI> REGISTER EXTRACT E0000032 DATABASE
GGSCI> ADD EXTRACT E0000032, INTEGRATED TRANLOG, BEGIN NOW, Description "Some details about extract"
GGSCI> ADD EXTTRAIL ./dirdat/app/ap, EXTRACT E0000032
GGSCI> START EXTRACT E0000032
GGSCI> INFO E0000032


If you have any issue, you can see the ggserr.log or view report <extract_name> would give more details about the error message.

Happy Reading :)
Posted by at

6 comments:

  1. k lawFebruary 10, 2015 at 10:57 PM

    you can try
    first_scn - 54815885975
    required_checkpoint_scn- 55718648103

    The capture on restart is looking to restart from the first_scn rather than the required_checkpoint_scn.

    Implement the following workaround to alter the first_scn of the capture process to the required_checkpoint_scn assuming that the required_checkpoint_scn is higher than the first_scn.

    BEGIN
    DBMS_CAPTURE_ADM.ALTER_CAPTURE(
    capture_name => 'CAPTURE',
    first_scn => 55718648103);
    END;
    /

    ReplyDelete
  2. 21st Century Software SolutionsMarch 4, 2015 at 6:13 AM

    No matter what database platform you’re running, dbaDIRECT is your answer for 24×7 monitoring and expert skill, at a lower cost than what’s possible with internal administration. We offer each of our core remote management services for all major database platforms, including Oracle, Sybase, MySQL, SQLServer, and IBM DB2. Our team of DBAs is here ’round the clock for your database needs, capable of servicing any size organization at any time of the day. Period.
    Remote dba services support 24x7 of below mentioned applications - more… Online Training- Corporate Training- IT Support U Can Reach Us On +917386622889 - +919000444287
    http://www.21cssindia.com/support.html

    ReplyDelete
  3. Augusto FerronatoSeptember 9, 2015 at 9:50 PM

    Hello,
    When i to do that, i lost all past sync? How i just resync this database?

    Thanks

    ReplyDelete
  4. UnknownApril 4, 2018 at 5:39 AM

    unregister and registering the extract solved the error for me. Thanks.

    ReplyDelete
  5. UnknownAugust 12, 2018 at 10:22 PM

    Just unregistering and Registering the extract resolved the issue, can you please explain what will happen when you unregister and register the extract back and how that will resolve the issue

    ReplyDelete
  6. Abhay ShuklaMay 21, 2019 at 11:15 AM

    Please mention in your post that there will be data loss in this approach.
    After re-registering , extract will capture from the time it was started, not from the time it was stopped.
    So, please mention data loss.

    ReplyDelete

Subscribe to: Post Comments (Atom)