Skip to content
Home » Oracle Database » GoldenGate » How to Resolve OGG-05500 Detected database metadata mismatch between current trail file

How to Resolve OGG-05500 Detected database metadata mismatch between current trail file

OGG-05500

Saw an error after trying to resume a pump extract that was stopped a few weeks ago.

2017-05-10 14:34:34  ERROR   OGG-05500  Detected database metadata mismatch between current trail file /u01/app/ogg/dirdat/ET000360 and the previous sequence.
*DBCHARSET: [0]/[10226].

Here are the steps to resolve the problem.

Renew and stop the extract.

GGSCI (source) 2> SEND EXTRACT ERPAPP_E LOGEND

GGSCI (source) 3> STOP EXTRACT ERPAPP_E

Renew and stop the replicat.

GGSCI (target) 22> SEND REPLICAT ERPAPP_R STATUS

GGSCI (target) 23> STOP REPLICAT ERPAPP_R

Stop the pump, it may have been abended in this moment.

GGSCI (source) 4> STOP EXTRACT ERPAPP_P

Skip some trails, start extract and make sure the newest trail is created.

GGSCI (source) 5> ALTER EXTRACT ERPAPP_E, ETROLLOVER

GGSCI (source) 6> ALTER EXTRACT ERPAPP_P, ETROLLOVER

GGSCI (source) 7> START EXTRACT ERPAPP_E

GGSCI (source) 8> shell ls -l ./dirdat
...
-rw-r----- 1 oracle oinstall     1397 2017-05-10 15:02 ET000364

The new file contains the new trail for us, and sequence number is 364. So we make PUMP point to the right extractfile.

GGSCI (source) 9> ALTER EXTRACT ERPAPP_P, EXTSEQNO 364, EXTRBA 0

Check the sequence number of PUMP for REPLICAT.

GGSCI (source) 10> info ERPAPP_P, detail
...
  Trail Name                                       Seqno        RBA     Max MB Trail Type

  ./dirdat/RT                                        384          0        100 RMTTRAIL
...
GGSCI (source) 11> START EXTRACT ERPAPP_P

Change the sequence number into 384 in order to make REPLICAT point to the right pump file.

GGSCI (target) 24> ALTER REPLICAT ERPAPP_R, EXTSEQNO 384, EXTRBA 0

GGSCI (target) 25> START REPLICAT ERPAPP_R

Leave a Reply

Your email address will not be published. Required fields are marked *