ERROR OGG-01028 Detect inconsistency in pdata after 6 retries

Last weekend i was alerted of gg abend with error gode ogg-01028.

Been working with oracle gg for almost 6 years but this the first i encounter such issue.

  ***********************************************************************
**                     Run Time Messages                             **
***********************************************************************


2016-09-04 00:19:15  WARNING OGG-01027  Detect inconsistency in pdata after 0 retries, expecting tb 1048576, nf 20, got tb 196863, nf 255, bc 1572884, nb 1277498645, on record with seqno 9759
, rba 119140084 for data starts at rba 32480300.

Source Context :
  SourceModule            : [er.redo.ora.rtc]
  SourceID                : [/scratch/aime1/adestore/views/aime1_staxj16/oggcore/OpenSys/src/app/er/redo/oracle/rtc.c]
  SourceFunction          : [RTC_producer(void *)]
  SourceLine              : [2118]

2016-09-04 00:19:44  ERROR   OGG-01028  Detect inconsistency in pdata after 6 retries, expecting tb 1048576, nf 20, got tb 196863, nf 255, bc 1572884, nb 1277498645, on record with seqno 9759
, rba 119140084 for data starts at rba 32480300.

***********************************************************************
*                   ** Run Time Statistics **                         *
***********************************************************************


As per oracle note GoldenGate: Extract Abend with Detect Inconsistency in Pdata (Doc ID 1355067.1), it didn’t help.

    SYMPTOMS
    
    Oracle GoldenGate (OGG) extract abends with error
    ERROR OGG-01028 Detect inconsistency in pdata with pdata start at rba XXXX, seqno XXXX
     
    Most likely Oracle RAC DB with log files on ASM with readahead enabled is in use
    Using parameter TRANLOGOPTIONS _NOREADAHEAD ANY doesn't help

    Workaround:

    Restart the extract. The extract will get restarted without any issue and will continue processing the records.If needed you could have the Autorestart parameter for the extract in the manager.

    Solution:

    Apply an OGG build which contains the fix for bug 12629456 + 13072229

    The issue is fixed in OGG 11.2.1.0.0

    The fix is included in OGG 11.1.1.1.2

    The same issue was later reported in v11.1.1.1.5 via Bug 16865401. The issue happened here when the redo record size is greater than 65k.
    The issue is fixed in 12.1.x and it is backported to 11.2.1.0.7 & 11.1.1.1.5_09 version.

With Sev 1 ticket oracle support requested to add below parameter, but same thing happen., gg extract still got abended.

    TRANLOGOPTIONS _SKIPINCOMPLETELOGDATA 
    TRANLOGOPTIONS _DISABLESTREAMLINEDDBLOGREADER 

After a very long hour with oracle, we don’t have fixed answer from oracle. so we decided to refresh the database using rman cloning.

After rman cloning, gg is up and running again. oracle support updated the sr below.

Oracle Support	- 5+ hours ago		[ODM Action Plan]

This is likely due to the usage of streamlined db logreader code which is enabled by default on the version you are using. 

With the latest fix and version your should be good to run with TRANLOGOPTIONS _DISABLESTREAMLINEDDBLOGREADER 

Thanks,

Updated the SR if we can simulate the issue in our test environment.

Hi, 

Unfortunately, this is one of such rare cases where we are not able to simulate. 
One option I can think of is run against the archive logs when the issue has been reported and see if we can reproduce. 

As suggested earlier, please use the parameters to fix the extract abend. 

Note: My working hours are in my signature below. This SR is a non 24*7 and will worked during my working hours. 

Regards, 
Oracle Global Support

🙂

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s