How to Use the PowerPoint Template - · PDF fileOracle GoldenGate UniDirectional or Bi-Directional If Oracle, then is it a Single Instance or RAC –Real Application Clusters

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

EXTRACT REPLICAT

DATAPUMP COLLECTOR

MANAGER MANAGER

N

E

T

W

O

R

K

SOURCE TARGETTransaction Logs

Trail Files

Transactions

GOLDENGATE ARCHITECTURE FLOW DIAGRAM

STORAGE STORAGE


SQL> select * from scott.dept;

DEPTNO DNAME LOC------------- -------------- -------------

10 ACCOUNTING NEW YORK20 RESEARCH DALLAS30 SALES CHICAGO50 DBA BOSTON

SQL> insert into scott.dept values(40,'IT','CHINA');

1 row created.

SQL> commit;

Commit complete.

GGSCI (OGG2.localdomain) 33> info all

Program Status Group Lag at Chkpt Time Since Chkpt

MANAGER RUNNINGREPLICAT ABENDED REP1 00:00:06 00:00:31

REPLICAT ABENDED

PROCESS ABENDED


PROCESS ABENDEDSQL> select * from scott.dept;

DEPTNO DNAME LOC------------- -------------- -------------

10 ACCOUNTING NEW YORK20 RESEARCH DALLAS30 SALES CHICAGO60 PURCHASE BOSTON40 IT CHINA

SQL> update scott.dept set dname='SPORTS' where dname='PURCHASE' and deptno=60;

1 row updated.

SQL> commit;

Commit complete.



MANAGER RUNNINGREPLICAT ABENDED REP1 00:00:06 00:00:31

REPLICAT ABENDED




MANAGER RUNNINGEXTRACT RUNNING INEXT 00:00:06 00:00:31EXTRACT RUNNING EXT1 00:00:00 00:00:03

PROCESS ABENDED

Performing an Initial Load in Oracle GoldenGate. By seeing the below status, the Initial Load Extract process is running fine.

During the course of time, suddenly Extract process Abend, with the following error.,



MANAGER RUNNINGEXTRACT ABENDED INEXT 00:00:06 00:00:45EXTRACT RUNNING EXT1 00:00:00 00:00:02

INITIAL LOAD EXTRACT ABENDED:2014-11-26 06:22:49 WARNING OGG-01194 Oracle GoldenGate

Capture for Oracle, INITLD1.prm: EXTRACT task INITLD1 abended : There is no trail to reposition to

when doing direct load task.



Copyright © 2015 Oracle and/or its affiliates. All rights reserved. | Oracle Confidential – Internal/Restricted/Highly Restricted 8

Veeratteshwaran Sridhar

Senior Software Engineer, Oracle GoldenGate Global Customer Support,

Oracle India Pvt Ltd.

o Nine years of Experience in Oracle Technologies – Core DBA, Replication –OGG, Performance Tuning

o Oracle GoldenGate 11g Certified Implementation Specialist, Oracle 11g OCP, Oracle 11g RAC Certified

o Blog: www.oracle-scn.como Twitter - @veeratteshwaran

http://www.oracle-scn.com/


LEVELS

OF

FAILURE


LEVELS OF FAILURE

FAILURES

GOLDENGATE

DATABASE

NETWORKSTORAGE

USER


EXTRACT REPLICAT

DATAPUMP COLLECTOR

MANAGER MANAGER

N

E

T

W

O

R

K


Trail Files

Transactions

GOLDENGATE LEVEL FAILURES

EXTRACT ABENDS

EXTRACT PUMP ABENDS

REPLICAT ABENDS

TRAIL FILE CORRUPTS

MANAGER ABENDS

STORAGE STORAGE

COLLECTOR ABENDS


EXTRACT REPLICAT

DATAPUMP COLLECTOR

MANAGER MANAGER

N

E

T

W

O

R

K


Trail Files

Transactions

STORAGE STORAGE

Tablespace filled

Redo log corruption

Archive log destination filled

No Primary Key or Unique Index on the tables

Archive log Mode not enabled

Reset Log performed

Memory Problem with Streams_Pool_Size

Database Hung

DATABASE LEVEL FAILURES


EXTRACT REPLICAT

DATAPUMP COLLECTOR

MANAGER MANAGER

N

E

T

W

O

R

K


Trail Files

Transactions

NETWORK LEVEL FAILURE

STORAGE STORAGE

Network Fails

Network slow

Ports Unavailability

Firewall Enabled


EXTRACT REPLICAT

DATAPUMP COLLECTOR

MANAGER MANAGER

N

E

T

W

O

R

K


Trail Files

Transactions

STORAGE STORAGE

File System fills

File System corruption

No Proper privileges given to the File System

Connection Problem between Database Server and Storage

No Free Disks Available in Storage

Improper dismount and mount of file system

STORAGE LEVEL FAILURES


USER LEVEL FAILURE

EXTRACT REPLICAT

DATAPUMP COLLECTOR

MANAGER MANAGER

N

E

T

W

O

R

K


Trail Files

Transactions

STORAGE STORAGE

Mistakenly Delete the GoldenGate Admin User at Database level.

Performing an ETROLLOVER at Extract / Pump / Replicat Processes.

Manually deleting / removing the Trail Files either from Source server or Target server.

Forcefully Stopping any Oracle GoldenGate Processes like Manager, Extract, Pump, Collector or Replicat.

Killing the Oracle GoldenGate Processes at OS level.

Manually Performing Operations like Insert, Delete and Update at Target Side.


APPROACH

TO

PROBLEM


Learn and Understand the Environment

Operating Provider and Operating System Version

Database Provider and Database Version

Is it a Cluster, Active / Passive?

Oracle GoldenGate UniDirectional or Bi-Directional

If Oracle, then is it a Single Instance or RAC – Real Application Clusters

Is it a Homogeneous or Heterogeneous Environment Replication

Network Flow, Ports Used and Firewalls configured

Components used in Oracle GoldenGate like Extract, Pump, Replicat processes and Trails files

HOW TO APPROACH


PROCESSES RUNNING

GGSCI (OGG1.localdomain) 2> INFO ALL


MANAGER RUNNINGEXTRACT EXT1 00:00:00 00:02:53EXTRACT EXT2 00:42:20 00:01:08EXTRACT DMP1 00:00:00 00:00:01EXTRACT DMP2 00:00:03 00:00:02

Check the ORACLE GOLDENGATE PROCESSES running in the Environment

INFO ALL is command to check the status of the processes configured.

RUNNING

STOPPED

STARTING

ABENDED


STATUS OF PROCESSES

RUNNING – The Process has started and running normally.

STOPPED – The Process has stopped either normally (Controlled Manner) or due to an error.

STARTING – The Process is starting.

ABENDED – The Process has been stopped in an uncontrolled manner. Abnormal End is known as ABEND.


STATUS OF PROCESSES - STARTING

When the Abended or Stopped Extract Process is STARTED, the Extract will take time to start.

Searches for Last Open Transaction in the Online Redo Logs or Archive Logs when it crashed.

Recovers from that point.

It takes more time depending upon how long back the Open transaction is in the Redo Logs or Archive Logs.

GGSCI (OGG1.localdomain) 2> send extract ext1, status

Sending STATUS request to EXTRACT EXT1 ...

EXTRACT EXT1 (PID 4498)Current status: In recovery[1]: Processing data


MAJOR FILES


MAJOR FILES

Error Log File – ggserr.log

Report File

Discard File

Trace File

Alert Log File

DDL Trace File


ERROR LOG FILE


WHAT IS GOLDENGATE ERROR LOG

Created during the Installation of Oracle GoldenGate.

Exists in the <OGG_HOME> directory with the name

One file for each installation.

Updated by all the processes of Oracle GoldenGate. Messages like,

Start and Stop of the Oracle GoldenGate Processes. Processing Information like Bounded Recovery operations. Error Messages. Informational messages like normal operations happening in Oracle GoldenGate. WARNING Messages like Long Running Transactions. Commands executed in GGSCI Prompt.

<Message Timestamp> <Message Type> <OGG message code> <OGG Message Text>

ggserr.log


EXAMPLE - GOLDENGATE ERROR LOG

2015-09-13 12:55:09 INFO OGG-00991 Oracle

GoldenGate Capture for Oracle, ext1.prm:

EXTRACT EXT1 stopped normally.

2015-09-13 16:48:37 WARNING OGG-00938 Oracle

GoldenGate Manager for Oracle, mgr.prm: Manager

is stopping at user request.

2015-09-13 17:00:45 ERROR OGG-01668 Oracle

GoldenGate Capture for Oracle, dmp1.prm:

PROCESS ABENDING.


With GGSERR.LOG file, the below can be identified basically.,

What is the Error?

When the Error occurred?

How Frequently it occurred?

What were the operations performed before the Error occurred?

GOLDENGATE ERROR LOG


REPORT FILE


WHAT IS GOLDENGATE REPORT FILE

A Process specific Log File.

Each Process has it’s own Report File Generated.

Created during the Instantiation of the Process.

Stored in the directory <OGG_HOME>/dirrpt

Format of the file is <process_name><sequence_no>.rpt

Automatically renamed on a new Instantiation of the Process.

REPORTROLLOVER parameter is used on the process to forcefully create a new report file.

To view the current of any process (Extract, Pump or Replicat), use the below command,

VIEW REPORT <PROCESS_NAME>


GOLDENGATE REPORT FILE

Oracle GoldenGate Product Version and Release

Operating Version, Release, Machine Type, Hostname and Ulimit settings of the respective process

Memory Utilized by the respective process

Configured Parameters of the respective Oracle GoldenGate Process

Database Provider, Version and Release

Trail files Information

Mapping of Tables



Informational messages with respective to a particular process

Warning messages with respective to a particular process

Error messages with respective to a particular process

All DDL Operations performed.

All the Discarded Errors and Ignored Operations

Crash dumps

Any commands which are performed on that particular process.


GGSCI (OGG1.localdomain) 30> VIEW REPORT EXT1

***********************************************************************

Oracle GoldenGate Capture for Oracle

Version 12.1.2.0.0 17185003 OGGCORE_12.1.2.0.0_PLATFORMS_130924.1316_FBO

Linux, x64, 64bit (optimized), Oracle 11g on Sep 25 2013 00:44:16

Copyright (C) 1995, 2013, Oracle and/or its affiliates. All rights reserved.

Starting at 2015-09-13 18:16:09

***********************************************************************

Operating System Version:

Linux

Version #1 SMP Wed Feb 2 18:40:23 EST 2011, Release 2.6.32-100.28.5.el6.x86_64

Node: OGG1.localdomain

Machine: x86_64

soft limit hard limit

Address Space Size : unlimited unlimited

Heap Size : unlimited unlimited

File Size : unlimited unlimited

CPU Time : unlimited unlimited

Process id: 9815

Command to view the Report of a Process

Oracle GoldenGate Product Version and

Release

Operating Version, Release, Machine Type, Hostname, Process ID and Ulimit settings of the respective

process



***********************************************************************

** Running with the following parameters **

***********************************************************************

2015-09-13 18:16:09 INFO OGG-03059 Operating system character set

identified as UTF-8.

2015-09-13 18:16:09 INFO OGG-02695 ANSI SQL parameter syntax is used for

parameter parsing.

EXTRACT EXT1

USERID ggadmin, PASSWORD ******

DDL INCLUDE MAPPED INCLUDE OTHER;

DDLOPTIONS ADDTRANDATA, REPORT

EXTTRAIL /vol3/ogg/dirdat/et

TABLE scott.*;

2015-09-13 18:16:09 INFO OGG-01815 Virtual Memory Facilities for: BR

anon alloc: mmap(MAP_ANON) anon free: munmap

file alloc: mmap(MAP_SHARED) file free: munmap

target directories:

/vol3/ogg/BR/EXT1.

Bounded Recovery Parameter:

BRINTERVAL = 4HOURS

BRDIR = /vol3/ogg

Configured Parameters of the Process



Database Version:

Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production

PL/SQL Release 11.2.0.4.0 - Production

CORE 11.2.0.4.0 Production

TNS for Linux: Version 11.2.0.4.0 - Production

NLSRTL Version 11.2.0.4.0 - Production

Database Language and Character Set:

NLS_LANGUAGE = "AMERICAN"

NLS_TERRITORY = "AMERICA"

NLS_CHARACTERSET = "WE8MSWIN1252"

2015-09-13 18:16:09 INFO OGG-01513 Positioning to Sequence 161, RBA 22944784, SCN

0.2121493.

2015-09-13 18:16:09 INFO OGG-01516 Positioned to Sequence 161, RBA 22944784, SCN

0.2121493, Sep 13, 2015 6:15:09 PM.

2015-09-13 18:16:09 INFO OGG-01055 Recovery initialization completed for target

file /vol3/ogg/dirdat/et000004, at RBA 1468.

2015-09-13 18:16:09 INFO OGG-01478 Output file /vol3/ogg/dirdat/et is using format

RELEASE 12.1.

2015-09-13 18:16:09 INFO OGG-01026 Rolling over remote file

/vol3/ogg/dirdat/et000004.

2015-09-13 18:16:09 INFO OGG-01053 Recovery completed for target file

/vol3/ogg/dirdat/et000005, at RBA 1468.

2015-09-13 18:16:09 INFO OGG-01057 Recovery completed for all targets.

Database Provider, Version and Release

Trail File Information




***********************************************************************

** Run Time Messages **

***********************************************************************

2015-09-13 18:16:09 INFO OGG-01517 Position of first record processed

Sequence 161, RBA 22944784, SCN 0.2121493, Sep 13, 2015 6:15:09 PM.

2015-09-13 18:32:01 INFO OGG-01021 Command received from GGSCI: LAG.

2015-09-13 18:32:12 INFO OGG-01021 Command received from GGSCI:

SHOWTRANS.

Wildcard TABLE resolved (entry scott.*):

TABLE "SCOTT"."HR";

Using the following key columns for source table SCOTT.HR: EMPNO.

Wildcard MAP resolved (entry scott.*):

MAP "SCOTT"."HR", TARGET scott."HR";

Using following columns in default map by name:

EMPNO, NAME

Using the following key columns for target table SCOTT.HR: EMPNO.

Commands Executed

Insert Operation Performed. Table in

the TABLE clause resolved

MAP Resolution at Replicat Side



Source Context :

SourceModule : [ggdb.ora.sess]

SourceID : [/scratch/aime1/adestore/views/aime1_adc4150472/oggcore/OpenSys/src/gglib/ggdbora/ocisess.c]

SourceFunction : [oci_try]

SourceLine : [800]

ThreadBacktrace : [17] elements

: [/vol3/ogg/libgglog.so(CMessageContext::AddThreadContext()+0x1e) [0x7f359431fdee]]

: [/vol3/ogg/libgglog.so(CMessageFactory::CreateMessage(CSourceContext*, unsigned int, ...)+0x31c)

[0x7f359431cc2c]]

: [/vol3/ogg/libgglog.so(_MSG_ERR_ORACLE_OCI_ERROR_WITH_DESC(CSourceContext*, int, char const*, char const*,

CMessageFactory::MessageDisposition)+0

x41) [0x7f3594304753]]

: [/vol3/ogg/extract(OCISESS_context_def::oci_try(int, char const*, ...)+0x4a2) [0x6d3772]]

: [/vol3/ogg/extract(OCISESS_context_def::logon(ggs::gglib::ggapp::CLoginName const&,

ggs::gglib::ggapp::CDBObjName<(DBObjType)12> const&, ggs::ggl

ib::ggunicode::UString const&, int, bool, int)+0x724) [0x6d0634]]

: [/vol3/ogg/extract(DBOCI_init_connection_logon(ggs::gglib::ggapp::CLoginName const&,

ggs::gglib::ggapp::CDBObjName<(DBObjType)12> const&, char co

nst*, int, int, int, char*)+0x81) [0x698d51]]

: [/vol3/ogg/extract() [0x6c68ad]]

: [/vol3/ogg/extract() [0x6c6a93]]

: [/vol3/ogg/extract(gl_odbc_param(char const*, char const*, char (&) [2048])+0x5a) [0x6c6dca]]

: [/vol3/ogg/extract(get_infile_params(time_elt_def*, time_elt_def*, char**)+0x10b2) [0x586882]]

: [/vol3/ogg/extract(extract_main(int, char**)+0xff) [0x5b07cf]]

: [/vol3/ogg/extract(ggs::gglib::MultiThreading::MainThread::ExecMain()+0x4f) [0x68743f]]

:

[/vol3/ogg/extract(ggs::gglib::MultiThreading::Thread::RunThread(ggs::gglib::MultiThreading::Thread::ThreadArgs*)+0x104) [0x687694]]

: [/vol3/ogg/extract(ggs::gglib::MultiThreading::MainThread::Run(int, char**)+0x8b) [0x68785b]]

: [/vol3/ogg/extract(main+0x3f) [0x5b047f]]

: [/lib64/libc.so.6(__libc_start_main+0xfd) [0x32c961ec5d]]

: [/vol3/ogg/extract() [0x51dc59]]

Crash Dump



2015-09-13 18:15:40 ERROR OGG-00664 OCI Error beginning session

(status = 1017-ORA-01017: invalid username/password; logon denied).

2015-09-13 18:15:40 ERROR OGG-01668 PROCESS ABENDING.

Error Messages



With REPORT file, the below can be identified basically.,

In which Trail File the Process gets Abend.

Whether the Trail File is moving forward?

Whether the process is getting failed with Same Trail File?

What operations has been performed before the process abend?

Whether any errors in the Parameter configuration?

Whether the MAP statements has the correct table names?


DISCARD FILE


WHAT IS GOLDENGATE DISCARD FILE

A log file for logging failed operations of Oracle GoldenGate Processes.

Mainly used for Data Errors.

By default, Discard File is not created.

DISCARDFILE is the parameter to enable the Discard File logging.

Format of the Log File is <group name><n>.<extension> and can also be manually named when enabling.

Extension of the File is .DSC and located in the <OGG_HOME>/dirrpt

Can be manually maintained by using PURGE and APPEND keywords in the Process parameter files.

DISCARDFILEROLLOVER parameter is used on the process to forcefully create a new report file.


GOLDENGATE DISCARD FILE

DISCARDFILE { [file_name] [, APPEND | PURGE] [, MAXBYTES n | MEGABYTES n] } | NODISCARDFILE

SYNTAX

filename

APPEND

PURGE

MAXBYTES n

The relative or fully qualified name of the discard file, including the actual file name

Adds new content to existing content if the file already exists.

Purges the file before writing new content.

Sets the maximum size of the file in bytes. The valid range is from 1 to 2147483646. The default is 50000000. If the specified size is exceeded, the process abends.

NODISCARDFILE Prevents the process of creating a Discard File.

MEGABYTES n Sets the maximum size of the file in megabytes. The valid range is from 1 to 2147. The default is 50 MB. If the specified size is exceeded, the process abends.



Note: The Discard File is mainly used in the Target Side. Each and Every Replicat Process should have it’s own Discard File. This is a mandatory one.

REPLICAT REP1USERID ggadmin, PASSWORD oracleDDL INCLUDE MAPPED INCLUDE OTHERDDLOPTIONS REPORTDDLERROR DEFAULT IGNORE RETRYOPASSUMETARGETDEFSDISCARDFILE /vol3/ogg/dirrpt/REP1.DSC, PURGEMAP scott.*, TARGET scott.*;



Oracle GoldenGate Delivery for Oracle process started, group REP2 discard file

opened: 2015-06-08 22:32:43.414970

Skipping compressed update from HR.EMPLOYEE at seqno 0 rba 2086

*

EMP_NO = NULL

EMP_NAME = sridhar

000000: 73 72 69 64 68 61 72 |sridhar |

*

Current time: 2015-06-08 22:32:43

Discarded record from action ABEND on error 1403

OCI Error ORA-01403: no data found, SQL <UPDATE "HR"."EMPLOYEE" x SET x."EMP_NAME"

= :a1 WHERE x."EMP_NO" = :b0>

Aborting transaction on /vol3/ogg/dirdat/ft beginning at seqno 0 rba 2227

error at seqno 0 rba 2227

Problem replicating HR.EMPLOYEE to HR.EMPLOYEE

Record not found

Mapping problem with compressed update record (target format)...

*

EMP_NO =

EMP_NAME = hari

000000: 68 61 72 69 |hari |

*

Process Abending : 2015-06-08 22:32:43


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 UTILITY

Hdr-Ind : E (x45) Partition : . (x04)UndoFlag : . (x00) BeforeAfter : A (x41)RecLength : 35 (x0023) IO Time : 2015/09/29 11:58:09.000.000IOType : 5 (x05) OrigNode : 255 (xff)TransInd : . (x03) FormatType : R (x52)SyskeyLen : 0 (x00) Incomplete : . (x00)AuditRBA : 50 AuditPos : 514576Continued : N (x00) RecCount : 1 (x01)

Transaction Type

Length of the Record Operation

Type

Captured Image Type (Before or

After)


1 - Abort2 - Commit3 - Delete4 - EndRollBack5 - Insert6 - Prepared7 - TMF-Shutdown8 - TransBegin9 - TransRelease10 - Update11 - UpdateComp12 - FileAlter13 - FileCreate14 - FilePurge15 - FieldComp16 - FileRename17 - AuxPointer18 - NetworkCommit

19 - NetworkAbort20 - CurrentPos89 - SQL/MX DDL OP90 - GGSSQLCol100 - GGSPurgedata101 - GGSPurgeFile102 - GGSCreateFile103 - GGSAlterFile104 - GGSRenameFile105 - GGSSetmode107 - GGSControl106 - GGSChangeLabel160 - DDL OP115 - GGSKeyFieldComp117 - GGSKeyFieldComp32161 - RecordFragment116 - LargeObject132 - GGSCreateSequence

133 - GGSAlterSequence134 - GGSDropSequence150 - RestartAbend151 - RestartOK152 - RecoveryEnd200 - GGSBulkio201 - GGSFileClose202 - GGSLoggerTS203 - GGSExtractTS204 - GGSCollectTS205 - GGSComment250 - LibOpenTrace251 - LibCloseTrace252 - LoggerOpenTrace253 - LoggerCloseTrace254 - LoggerAddedInfo249 - LoggerAddedStats

LOGDUMP UTILITY – RECORD OPERATION TYPE


LOGDUMP UTILITY

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

TransInd x03Single Operation or Single record Transaction


LOGDUMP UTILITY

2015/09/29 11:58:09.000.000 Insert Len 35 RBA 1516Name: SCOTT.TAB1After Image: Partition 4 G s0000 000a 0000 0000 0000 0000 0002 0001 0009 0000 | ....................0005 7669 636b 7900 0200 04ff ff00 00 | ..vicky........

Column 0 (x0000), Len 10 (x000a)0000 0000 0000 0000 0002 | ..........

Column 1 (x0001), Len 9 (x0009)0000 0005 7669 636b 79 | ....vicky

Column 2 (x0002), Len 4 (x0004)ffff 0000 | ....

Timestamp and

Operation Type

Source Object Name

Captured Image Type (Before or

After)

Record Position in the Trail File

Record Length

Data in ASCII Format

Data in Hex Format

Column Information

with Data


LOGDUMP UTILITY

GGS tokens:TokenID x52 'R' ORAROWID Info x00 Length 204141 4156 6172 4141 4541 4141 4146 4c41 4142 0001 | AAAVarAAEAAAAFLAAB..TokenID x74 't' ORATAG Info x01 Length 0TokenID x4c 'L' LOGCSN Info x00 Length 73333 3733 3438 33 | 3373483TokenID x36 '6' TRANID Info x00 Length 9342e 3235 2e31 3130 34 | 4.25.1104


LOGDUMP UTILITY1. 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 >SCANFORHEADERLogdump 11 >SFH

10. To scan for the end of a transaction, enter the following command,

Logdump 12 >SCANFORENDTRANSLogdump 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 FIRSTLogdump 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 >COUNTLogTrail /vol3/ogg/dirdat/et000000 has 7 recordsTotal Data Bytes 8217Avg Bytes/Record 1173Delete 1DDL 5Others 1Before Images 1After Images 5

Average of 7 TransactionsBytes/Trans ..... 1221Records/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

15. To keep a log of the Session,

To start logging, enter the following command

Logdump 19 >LOG TO filename.txt

To write text to the log

Logdump 20 >WRITELOG "text"

To stop logging

Logdump 21 >LOG STOP



16. 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/oggLogTrail : /vol3/ogg/dirdat/et000000Trail Format : NewEnd of File : 9063Current Position : 0 ForwardNext Position : 0Last Modtime : 2015/09/13 11:38:12.000.000Display RecLen : 140Logtrail Filter : OnTrans History : 0 Transactions, Records 100, Bytes 100000LargeBlock I/O : On, Blocksize 57344Local System : LittleEndianMetadata Byte Order : BigEndianLogtrail Data : BigEndian/ASCIILogtrail Headers : ASCIIDump : ASCIISavefile comments : OffTimeoffset : LOCALScan Notify Interval: 10000 records, Scrolling On



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

Logdump 23 >EXIT

Logdump 23 >QUIT



Steps to Avoid Process Abend


>>>>>>>>>>>>>>>>>>>>>>>>>

Loading Data to the Target to make it sync with the Source.

Mandatory Pre-requisite process to be performed before starting the Change Replication.

Perform a batch load to populate database tables for migration.

ORALCE GOLDENGATE INTIAL LOAD


ORACLE GOLDENGATE

HANDLECOLLISIONS - NOHANDLECOLLISIONS

HANDLECOLLISIONS can be used in the following ways.,

HANDLECOLLISIONS and NOHANDLECOLLISIONS can be used globally at root level in the parameter file. If HANDLECOLLISIONS is used, it remains active for all the MAP statements subsequently used until it faces or encounters the parameter NOHANDLECOLLISIONS. NOHANDLECOLLISIONS is the opposing parameter. It disables it.

HANDLECOLLISIONS and NOHANDLECOLLISIONS can be enabled for specific tables or within specific MAP statements for error handling.

SEND REPLICAT <REPLICAT_NAME>, NOHANDLECOLLISIONS


ORACLE GOLDENGATE

HANDLECOLLISIONS - NOHANDLECOLLISIONS

These parameters are configured in the Replicat side and they are set to continue the data processing if there are some data integrity issues on the Target tables.

Upon setting these parameters Replicat Process tries to resolve the duplicate and missing records when applying the sql on the Target tables.

These parameters are mainly used during the Initial Loads, when loading the data for synchronizing the Target Tables with Source.


Documents

How to Use the PowerPoint Template - · PDF fileOracle GoldenGate UniDirectional or Bi-Directional If Oracle, then is it a Single Instance or RAC –Real Application Clusters