Oracle GoldenGate IRCTC

Copyright 2015 Oracle and/or its affiliates. All rights reserved.
|
ORACLE GOLDENGATE
Oracle GoldenGate, IRcTC
(Incompatible Record cum Trail Corruption)
Veeratteshwaran Sridhar
Oracle GoldenGate, IRcTC (Incompatible Record cum Trail Corruption)
Oracle India Pvt Ltd
June 10, 2017
veeratteshwaran.sridhar@oracle.com
Blogger - www.oracle-scn.com
OTN community - ORASCN
Copyright 2014, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential Internal/Restricted/Highly Restricted
Safe Harbor Statement
The following is intended to outline our general product direction. It is intended for
information purposes only, and may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or functionality, and should not be relied upon
in making purchasing decisions. The development, release, and timing of any features or
functionality described for Oracles products remains at the sole discretion of Oracle.
Copyright 2016 Oracle and/or its affiliates. All rights reserved. | 3

GOLDENGATE ARCHITECTURE FLOW DIAGRAM
SOURCE TARGET
Transaction Logs
Trail Files
MANAGER MANAGER
Transactions
EXTRACT REPLICAT
N
E
T
W
O
R
K
DATAPUMP COLLECTOR
STORAGE STORAGE
Copyright 2015 Oracle and/or its affiliates. All rights reserved. |

TRAIL FILE
Prior to OGG 12.2

TRAIL FILE
Trail File Header
2017/04/10 18:13:52.707.000 FileHeader Len 1395 RBA 0
Name: *FileHeader*
3000 0321 3000 0008 4747 0d0a 544c 0a0d 3100 0002 | 0..!0...GG..TL..1...
0005 3200 0004 2000 0000 3300 0008 02f2 7302 c89d | ..2... ...3.....s...
2bb8 3400 003a 0038 7572 693a 5645 4553 5249 4448 | +.4..:.8uri:VEESRIDH
2d49 4e3a 696e 3a6f 7261 636c 653a 636f 6d3a 6472 | -IN:in:oracle:com:dr
6976 652d 433a 6f67 6731 3232 5f73 6f75 7263 653a | ive-C:ogg121_source:
5245 5854 3600 0025 0023 633a 5c6f 6767 3132 325f | REXT6..%.#c:\ogg121_
736f 7572 6365 5c64 6972 6461 745c 7265 3030 3030 | source\dirdat\re0000

TRAIL FILE
Length of
the Record Operation Before /
Type Captured
After Image Image Type
(Before or
After)
Hdr-Ind : E (x45) Partition : . (x04)
UndoFlag : . (x00) BeforeAfter : A (x41)
RecLength : 35 (x0023) IO Time : 2015/09/29 11:58:09.000.000
IOType : 5 (x05) OrigNode : 255 (xff)
TransInd : . (x03) FormatType : R (x52)
SyskeyLen : 0 (x00) Incomplete : . (x00)
Transaction
AuditRBA : 50 AuditPos : 514576
Type
Continued : N (x00) RecCount : 1 (x01)
Archive Log Position of

Sequence Record
No

LOGDUMP UTILITY RECORD OPERATION TYPE
1 - Abort 19 - NetworkAbort 133 - GGSAlterSequence

2 - Commit 20 - CurrentPos 134 - GGSDropSequence
3 - Delete 89 - SQL/MX DDL OP 150 - RestartAbend
4 - EndRollBack 90 - GGSSQLCol 151 - RestartOK
5 - Insert 100 - GGSPurgedata 152 - RecoveryEnd
6 - Prepared 101 - GGSPurgeFile 200 - GGSBulkio
7 - TMF-Shutdown 102 - GGSCreateFile 201 - GGSFileClose
8 - TransBegin 103 - GGSAlterFile 202 - GGSLoggerTS
9 - TransRelease 104 - GGSRenameFile 203 - GGSExtractTS
10 - Update 105 - GGSSetmode 204 - GGSCollectTS
11 - UpdateComp 107 - GGSControl 205 - GGSComment
12 - FileAlter 106 - GGSChangeLabel 250 - LibOpenTrace
13 - FileCreate 160 - DDL OP 251 - LibCloseTrace
14 - FilePurge 115 - GGSKeyFieldComp 252 - LoggerOpenTrace
15 - FieldComp 117 - GGSKeyFieldComp32 253 - LoggerCloseTrace
16 - FileRename 161 - RecordFragment 254 - LoggerAddedInfo
17 - AuxPointer 116 - LargeObject 249 - LoggerAddedStats
18 - NetworkCommit 132 - GGSCreateSequence

TRAIL FILE
TRANSACTION INDICATOR DESCRIPTION
TransInd x00 First Statement in the Transaction

TransInd x01 Statement in Middle of the Transaction
TransInd x02 Last Statement in the Transaction
Single Operation or Single record
TransInd x03
Transaction

Timestamp
TRAIL FILE
and
Operation Record Record Position
Type Length in the Trail File
Source Object
Name
Captured
Image Type
2015/09/29 11:58:09.000.000 Insert Len 35 RBA 1516
(Before or
Name: SCOTT.TAB1
After)
After Image: Partition 4 G s
0000 000a 0000 0000 0000 0000 0002 0001 0009 0000 | ....................
0005 7669 636b 7900 0200 04ff ff00 00 | ..vicky........
Column 0 (x0000), Len 10 (x000a)
Column 0000 0000 0000 0000 0002 | ..........
Information Data in ASCII
Column 1 (x0001), Len 9 (x0009)
with Data Format
0000 0005 7669 636b 79 | ....vicky
Column 2 (x0002), Len 4 (x0004)
ffff 0000 | ....
Data in Hex
Format

TRAIL FILE
Row ID
GGS tokens:
SCN TokenID x52 'R' ORAROWID Info x00 Length 20
4141 4156 6172 4141 4541 4141 4146 4c41 4142 0001 | AAAVarAAEAAAAFLAAB..
TokenID x74 't' ORATAG Info x01 Length 0
TokenID x4c 'L' LOGCSN Info x00 Length 7
3333 3733 3438 33 | 3373483
TokenID x36 '6' TRANID Info x00 Length 9
342e 3235 2e31 3130 34 | 4.25.1104
TRANSACTION
ID

HOW TO OPEN THE
TRAIL FILES?

LOGDUMP
UTILITY
LOGDUMP UTILITY
It is the tool used to troubleshoot Oracle
GoldenGate during Data corruption or trail file
corruption.
This tool allows a user to navigate through the

trail file.
It is used to compare the information of the trail

file with the data extracted and replicated by the
processes.
This is mainly used when Data error occurs in the

Oracle GoldenGate.

LOGDUMP UTILITY
Transactions Information.
Operation type and Time when the Record written.
Source Object name.
Image type, whether it is a Before Image or After Image.
Column information with data and sequence information.
Record length, Record data in ASCII format.
RBA Information.

LOGDUMP
COMMANDS
LOGDUMP UTILITY
1. To view the record header with the data:
Logdump 1 >GHDR ON - The record header contains information about the transaction
2. To add column information:
Logdump 2 >DETAIL ON - Column information includes the number and length in hex and ASCII
3. To add hex and ASCII data values to the column information:
Logdump 3 >DETAIL DATA
4. To view user tokens:
Logdump 4 >USERTOKEN ON - User tokens are custom user-defined information that is specified in a
TABLE or FILE mapping statement and stored in the trail file for specific purposes.
5. To view automatically generated tokens:
Logdump 5 >GGSTOKEN ON - Oracle GoldenGate automatically generated tokes include the transaction ID (XID), the
row id for DML operations, the fetching status (if applicable), and tag value.
6. To control how much record data is displayed:
Logdump 6 >RECLEN length

LOGDUMP UTILITY PERFORMING SOME TASKS
7. To Open a trail file, follow the below steps.,
Logdump 7 >OPEN file_name
file_name is either the relative name or fully qualified name of the file, including the file sequence
number.
For example:
open /home/ggs/dirdat/jd000000
8. To go to the first record and then move through records in sequence
Logdump 8 >NEXT
Logdump 9 >N

9. To find the next good record header, enter the following command,
Logdump 10 >SCANFORHEADER
Logdump 11 >SFH
10. To scan for the end of a transaction, enter the following command,
Logdump 12 >SCANFORENDTRANS
Logdump 13 >SFET
11. To go to a specific RBA in the file, you can do either of the following,
To go to an RBA anywhere in the file,
Logdump 14 >POS rba

Logdump 15 >N
To go to the first record in the file,
Logdump 16 >POS FIRST

Logdump 17 >POS 0
12. The following command shows a count summary followed by counts for each table or data file.,
Logdump 18 >COUNT
Logdump 22 >COUNT
LogTrail /vol3/ogg/dirdat/et000000 has 7 records
Total Data Bytes 8217
Avg Bytes/Record 1173
Delete 1
DDL 5
Others 1
Before Images 1
After Images 5
Average of 7 Transactions
Bytes/Trans ..... 1221
Records/Trans ... 1
Files/Trans ..... 1
13. To save the whole file, enter the following command, where file is the name of the new file
Logdump 7 >SAVE file

14. To close the current file and open the next one in the trail, enter the following command.,
Logdump 18 >NEXTTRAIL
Logdump 19 >NT
15. To keep a log of the Session,
To start logging, enter the following command
Logdump 20 >LOG TO filename.txt
16. To stop logging
Logdump 21 >LOG STOP

17. To see the current Logdump environment, enter the following command.,
Logdump 22 >ENV
Version : Linux, x64, 64bit (optimized) on Sep 24 2013 18:18:53
Current Directory : /vol3/ogg

LogTrail : /vol3/ogg/dirdat/et000000
Trail Format : New
End of File : 9063
Current Position : 0 Forward
Next Position :0
Last Modtime : 2015/09/13 11:38:12.000.000
Display RecLen : 140
Logtrail Filter : On
Trans History : 0 Transactions, Records 100, Bytes 100000
LargeBlock I/O : On, Blocksize 57344
Local System : LittleEndian
Metadata Byte Order : BigEndian
Logtrail Data : BigEndian/ASCII
Logtrail Headers : ASCII
Dump : ASCII
Savefile comments : Off
Timeoffset : LOCAL
Scan Notify Interval: 10000 records, Scrolling On

18. To exit Logdump, enter either of the following commands.,
Logdump 23 >EXIT
Logdump 24 >QUIT

Trail Files
in
OGG 12.2?
Quick Quiz Identify The Missing Parameter
EXTRACT ext1
USERIDALIAS ggs_admin REPLCAT rep1
DDL include mapped USERIDALIAS ggs_replicat
RMTTRAIL ./dirdat/et DDL include all
TABLE hr.*; MAP hr.*, TARGET hr.*;
No SourceDefs
No AssumeTargetDefs

Self-Describing Trail Files
No more SOURCEDEFS
Simpler to configure replication
Eliminates the SOURCEDEFS or ASSUMETARGETDEFS parameters
Supports replication even if source and target have different structures or different databases
Eliminate many manual steps and reduces errors during replication

Metadata information in the trail file is accurate unlike ASSUMETARGETDEFS which assumes
target table has the same internal structure as source table

Metadata records used to interpret DML records
instead of SOURCEDEFS or ASSUMETARGETDEFS
Each trail file contains a Database Definition Record

(DDR) before first occurrence of a DML record or a
SEQUENCE from a particular database
TDR DDR Each trail file contains a Table Definition Record (TDR)
DML TDR before first occurrence of a DML record for a particular
table
- TDR contains table and column definition
including column number, data types, column
lengths, etc.
Ref TDR
DML records have a reference to the TDR and no
longer contain the object name
- Typically results in smaller trail files

DDR Database Definition Record
SEQUENCE records have a reference to the DDR and
TDR Table Definition Record no longer contain the SEQUENCE name

USE
SOURCEDEFS
&
ASSUMETARGETDEFS
in OGG 12.2?

You can easily switch between the old and new ways of resolving the
table metadata by:
Using the new NO_USE_TRAILDEFS in GLOBALS

parameter file.
Default is USE_TRAILDEFS
Use the OVERRIDE option for individual SOURCEDEFS and

ASSUMETARGETDEFS parameters in the pump or Replicat parameter
files.

Trail File Header
2017/04/10 18:13:52.707.000 FileHeader Len 1395 RBA 0

Name: *FileHeader*
3000 0321 3000 0008 4747 0d0a 544c 0a0d 3100 0002 | 0..!0...GG..TL..1...
0005 3200 0004 2000 0000 3300 0008 02f2 7302 c89d | ..2... ...3.....s...
2bb8 3400 003a 0038 7572 693a 5645 4553 5249 4448 | +.4..:.8uri:VEESRIDH
2d49 4e3a 696e 3a6f 7261 636c 653a 636f 6d3a 6472 | -IN:in:oracle:com:dr
6976 652d 433a 6f67 6731 3232 5f73 6f75 7263 653a | ive-C:ogg122_source:
5245 5854 3600 0025 0023 633a 5c6f 6767 3132 325f | REXT6..%.#c:\ogg122_
736f 7572 6365 5c64 6972 6461 745c 7265 3030 3030 | source\dirdat\re0000

DDR Database Definition Record
___________________________________________________________________
UndoFlag : . (x00) BeforeAfter: A (x41)
IOType : 170 (xaa) OrigNode : 1 (x01)
DDR/TDR Idx: (001, 000) AuditPos : 9964560 Database Type
2017/04/10 18:13:52.926.000 Metadata Len 81 RBA 1403

Name:
* Database
DDR Version: 1 Characterset
Database type: ORACLE
Character set ID: we8mswin1252
National character set ID: UTF-16
Locale: neutral
Case sensitivity: 14 14 14 14 14 14 14 14 14 14 14 14 11 14 14 14
TimeZone: GMT
Database Name
Global name: TESTDB

UndoFlag : . (x00) BeforeAfter: A (x41)
TDR Table Definition Record
RecLength : 192 (x00c0) IO Time : 2017/04/10 18:13:52.927.000
IOType : 170 (xaa) OrigNode : 2 (x02)
Table Name
DDR/TDR Idx: (001, 001) AuditPos : 9964560
2017/04/10 18:13:52.927.000 Metadata Len 192 RBA 1535 Table Definition

Name: SOURCE.T33
*
1)Name 2)Data Type 3)External Length 4)Fetch Offset 5)Scale 6)Level
7)Null 8)Bump if Odd 9)Internal Length 10)Binary Length 11)Table Length 12)Most Sig DT
13)Least Sig DT 14)High Precision 15)Low Precision 16)Elementary Item 17)Occurs 18)Key Column
19)Sub DataType 20)Native DataType 21)Character Set 22)Character Length 23)LOB Type 24)Partial Type
*
TDR version: 1 Number of
Definition for table SOURCE.T33 Columns
Record Length: 82
Columns: 2
ID 64 50 0 0 0 1 0 50 50 50 0 0 0 0 1 0 1 2 2 -1 000
NAME 64 20 56 0 0 1 0 20 20 000001 00 0 1 -1 000
End of definition

Hdr-Ind : E (x45) Partition : . (x0c)
UndoFlag : . (x00) BeforeAfter: B (x42)
IOType : 15 (x0f) OrigNode : 255 (xff)
AuditRBA : 420 AuditPos : 9964560
2017/04/10 18:10:59.000.000 FieldComp Len 22 RBA 1788

Name: SOURCE.T33 (TDR Index: 1)
Before Image: Partition 12 G b
6b79
Column 0 (x0000), Len 5 (x0005)
| ky Transactional Record
0000 0005 0000 0001 3200 0100 0900 0000 0576 6963 | ........2........vic
0000 0001 32 | ....2

Column 1 (x0001), Len 9 (x0009)
0000 0005 7669 636b 79 | ....vicky
GGS tokens:
TokenID x52 'R' ORAROWID Info x00 Length 20
4141 4158 6b48 4141 4541 4141 4139 3941 4142 0001 | AAAXkHAAEAAAA99AAB..
TokenID x74 't' ORATAG Info x01 Length 0
TokenID x4c 'L' LOGCSN Info x00 Length 7
3634 3530 3833 34 | 6450834
TokenID x36 '6' TRANID Info x00 Length 9
362e 3235 2e33 3431 39 | 6.25.3419

IRCTC
OGG
IRCTC
INCOMPATIBLE RECORD
CUM
TRAIL CORRUPTION
TYPES OF CORRUPTION
Trail file corruption
Data Corruption in buffer.
Archive log file corruption.
Data is not properly sync to Disk.

Why
Corruptions

REASONS OF CORRUPTION
Network Glitch
Multiple process writing to same trail file
Space issues
Filesystem /Disk Issues
Old trail files not cleaned up properly
Abnormal System Shutdown
Unsupported File system
If FORMAT RELEASE 9.5 is used

IMPACTS OF CORRUPTION
When trail file gets corrupted, Pump extract/ Replicat abends with
either of the following error
ERROR OGG-01449 Oracle GoldenGate Capture for Oracle, p1.prm:

Scan failed in trail file ./dirdat/pk000011, with scan start seqno 11, rba
325929194.
ERROR OGG-01028 Incompatible record (104) in ./dirdat//aa000000,

rba 433792090 (getting header).

IMPACTS OF CORRUPTION
Oracle GoldenGate Extract/Replicat has ability to read from buffer
before Synced to disk. Due to file system or space issue, if the data is not
sync properly to Disk
Input checkpoint position 52755539 for input

trail file './dirdat/ca004207' is greater than the size of
the file (52617450).

OPEN SR?????????

RECOVERY OF CORRUPTION
Note down the Last Applied SCN in the Target by the Replicat process
Classic Integrated
select group_name, seqno, rba, log_csn, select server_name, applied_low_position,

log_cmplt_csn, to_char(last_update_ts, 'DD- applied_high_position, logbsn from
MON-YYYY HH24:MI:SS AM') last_update_ts DBA_GG_INBOUND_PROGRESS;
from GGADMIN.GGSCHKPT;

CHECKPOINT TABLE
GGSCI (Oracle12c.localdomain) 5> info rep1 detail
REPLICAT REP1 Initialized 2017-06-17 11:54 Status STOPPED

Checkpoint Lag 00:00:00 (updated 00:00:03 ago)
Log Read Checkpoint File /ogg/dirdat/target/ft000000000
First Record RBA 0
Current Log BSN value: (requires database login)
Last Committed Transaction CSN value: (requires database login)
Extract Source Begin End
/ogg/dirdat/target/ft000000 * Initialized * First Record
Current directory /ogg
Report file /ogg/dirrpt/REP1.rpt

Parameter file /ogg/dirprm/rep1.prm
Checkpoint file /ogg/dirchk/REP1.cpr
Checkpoint table ggadmin.ggschkpt
Process file /ogg/dirpcs/REP1.pcr
Error log /ogg/ggserr.log
CHECKPOINT TABLE FOR CLASSIC REPLICAT
SQL> desc ggadmin.ggschkpt
Name Null? Type
----------------------------------------- -------------------------- ----------
GROUP_NAME NOT NULL VARCHAR2(8)
GROUP_KEY NOT NULL NUMBER(19)
SEQNO NUMBER(10)
RBA NOT NULL NUMBER(19)
AUDIT_TS VARCHAR2(29)
CREATE_TS NOT NULL DATE
LAST_UPDATE_TS NOT NULL DATE
CURRENT_DIR NOT NULL VARCHAR2(255)
LOG_BSN VARCHAR2(128)
LOG_CSN VARCHAR2(128)
LOG_XID VARCHAR2(128)
LOG_CMPLT_CSN VARCHAR2(128)
LOG_CMPLT_XIDS VARCHAR2(2000)
VERSION NUMBER(3)

CHECKPOINT TABLE FOR INTEGRATED REPLICAT
SQL> desc DBA_GG_INBOUND_PROGRESS
Name Null? Type
----------------------------------------- -------- ----------------------
SERVER_NAME NOT NULL VARCHAR2(128)
PROCESSED_LOW_POSITION VARCHAR2(4000)
APPLIED_LOW_POSITION VARCHAR2(4000)
APPLIED_HIGH_POSITION VARCHAR2(4000)
SPILL_POSITION VARCHAR2(4000)
OLDEST_POSITION VARCHAR2(4000)
APPLIED_LOW_SCN NOT NULL NUMBER
APPLIED_TIME DATE
APPLIED_MESSAGE_CREATE_TIME DATE
SOURCE_DATABASE VARCHAR2(128)
SOURCE_ROOT_NAME VARCHAR2(128)

Note down the Time Stamp of the Last
Applied SCN Record in the Target Side.

SEARCH FOR SCN
Logdump> open <trail file>
Logdump>ghdr on
Logdump> ggstoken detail
Logdump> filter include ggstoken logcsn = <log_cmplt_csn> or <LWM>
Logdump> n
If reaches EOF of trail file, then nt to search in next trail file
Logdump> nt
Logdump> n
When record is found, for classic mode
Logdump> filter clear
Logdump> n
This is the point of next transaction which we need to start.

SEARCH FOR SCN
For Integrated
When record is found,

Logdump>filter clear
Logdump> n
If this shows High water mark SCN, then do a next and note
down the RBA. This means there are no transactions between LWM
and HWM
Logdump>n
REPOSITION THE PROCESSES
On Source
ggsci> alter extract <pump_name, extseqno <seqno>, extrba <rba>
ggsci> alter extract <pump_name>, etrollover
ggsci> info <pump_name>, showch and note down write checkpoint seqno
On Target
Alter replicat <rep_name>, extseqno<write checkpoint seqno> extrba 0

RECOVERY STEPS PRIOR TO OGG 12cR2
If Classic Replicat, find the LOG_CMPLT_CSN from Checkpoint table. If
Integrated, get the Low Watermark SCN (LWM) from the info detail
output of the Replicat process.
Use the Logdump utility and find the Timestamp that contains the
SCN on the Target trail.
Now check the Trail file that covers the timestamp and then use the
Logdump to search for the SCN in the Local Trail file.
Alter the Pump to the respective local trail file and RBA which
contains the next new transaction and perform ETROLLOVER.
Alter the replicat to the new Trail file and start it.

AUTOMATED
REMOTE TRAIL FILE
RECOVERY
BY
PUMP PROCESS
IMPROVED TRAIL FILE RECOVERY
For use when Replicat abends due to missing or corrupt trail file
If the trail is corrupt, delete all the trail files first from the corrupted seq#.
Any missing trails are now automatically rebuilt by bouncing the Extract Pump.
Once trail files have been restored, restart the Replicat Do not use
NOFILTERDUPTRANSACTIONS
Requires at least 1 valid, complete trail on the target

Due to this, you may want to modify your PURGEOLDEXTRACTS parameter

FILTERDUPTRANSACTIONS | NOFILTERDUPTRANSACTIONS
Causes Replicat to ignore transactions that it has already processed.
Use when Extract was repositioned to a new start point (ATCSN or AFTERCSN
option of "START EXTRACT") and you are confident that there are duplicate
transactions in the trail that could cause Replicat to abend.
This option requires the use of a checkpoint table.
If the database is Oracle, this option is valid only for Replicat in nonintegrated
mode.
The default is FILTERDUPTRANSACTIONS
To override this, use NOFILTERDUPTRANSACTIONS

RECOMMENDATIONS TO AVOID CORRUPTIONS
Use recommended mount options with caching and async io

disabled for file system where OGG resides
Clean up the trail file when reconfiguring extract/pump
Stop OGG process during system shutdown
Configure PURGEOLDEXTRACT parameter in manager parameter file

to delete processed trail files.


Oracle GoldenGate IRCTC

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle GoldenGate IRCTC

Uploaded by

Copyright:

Available Formats

Copyright 2015 Oracle and/or its affiliates. All rights reserved.

Copyright 2016 Oracle and/or its affiliates. All rights reserved. | 3

Copyright 2015 Oracle and/or its affiliates. All rights reserved. |

Copyright 2015 Oracle and/or its affiliates. All rights reserved. |

Copyright 2015 Oracle and/or its affiliates. All rights reserved. |

Archive Log Position of

Copyright 2015 Oracle and/or its affiliates. All rights reserved. |

1 - Abort 19 - NetworkAbort 133 - GGSAlterSequence

Copyright 2015 Oracle and/or its affiliates. All rights reserved. |

TRANSACTION INDICATOR DESCRIPTION

TransInd x00 First Statement in the Transaction

Copyright 2015 Oracle and/or its affiliates. All rights reserved. |

Copyright 2015 Oracle and/or its affiliates. All rights reserved. |

342e 3235 2e31 3130 34 | 4.25.1104

Copyright 2015 Oracle and/or its affiliates. All rights reserved. |

Copyright 2015 Oracle and/or its affiliates. All rights reserved. |

This tool allows a user to navigate through the

It is used to compare the information of the trail

This is mainly used when Data error occurs in the

Copyright 2015 Oracle and/or its affiliates. All rights reserved. |

Operation type and Time when the Record written.

Source Object name.

Image type, whether it is a Before Image or After Image.

Column information with data and sequence information.

Record length, Record data in ASCII format.

Copyright 2015 Oracle and/or its affiliates. All rights reserved. |

2. To add column information:

3. To add hex and ASCII data values to the column information:

Logdump 3 >DETAIL DATA

4. To view user tokens:

5. To view automatically generated tokens:

6. To control how much record data is displayed:

Logdump 6 >RECLEN length

Copyright 2015 Oracle and/or its affiliates. All rights reserved. |

Logdump 7 >OPEN file_name

8. To go to the first record and then move through records in sequence

Copyright 2015 Oracle and/or its affiliates. All rights reserved. |

To go to an RBA anywhere in the file,

Logdump 14 >POS rba

To go to the first record in the file,

Logdump 16 >POS FIRST

Logdump 7 >SAVE file

Copyright 2015 Oracle and/or its affiliates. All rights reserved. |

15. To keep a log of the Session,

To start logging, enter the following command

Logdump 20 >LOG TO filename.txt

16. To stop logging

Logdump 21 >LOG STOP

Copyright 2015 Oracle and/or its affiliates. All rights reserved. |

Current Directory : /vol3/ogg

Copyright 2015 Oracle and/or its affiliates. All rights reserved. |

18. To exit Logdump, enter either of the following commands.,

Copyright 2015 Oracle and/or its affiliates. All rights reserved. |

Copyright 2015 Oracle and/or its affiliates. All rights reserved. |

Eliminate many manual steps and reduces errors during replication

Copyright 2015 Oracle and/or its affiliates. All rights reserved. |

Each trail file contains a Database Definition Record

- Typically results in smaller trail files

Copyright 2015 Oracle and/or its affiliates. All rights reserved. |

Copyright 2015 Oracle and/or its affiliates. All rights reserved. |

Using the new NO_USE_TRAILDEFS in GLOBALS

Use the OVERRIDE option for individual SOURCEDEFS and

Copyright 2015 Oracle and/or its affiliates. All rights reserved. |

2017/04/10 18:13:52.707.000 FileHeader Len 1395 RBA 0