Lession 3 Tools
Lession 3 Tools
SA
NK
AR
no GA
n- NE
tra S
ns AN
fe (s
ra a
ble nk
lic ar.g
en a
Tools
se ne
to san
us @
e or
th ac
is le
Gu .c
Copyright © 2014, Oracle and/or its affiliates. All rights reserved.
ide om
. ) ha
sa
Unauthorized reproduction or distribution prohibited. Copyright© 2022, Oracle University and/or its affiliates.
Objectives
sa
• ShowSyntax parameter
. ) ha
• logdump utility
ide om
Gu .c
is le
th ac
e or
us @
to san
se ne
en a
lic ar.g
ble nk
Tools: Overview
sa
– Configuration instructions and descriptions of Oracle GoldenGate
. ) ha
errors, commands, parameters, and functions
• ShowSyntax parameter
ide om
– Shows Replicat SQL statements
Gu .c
is le
• logdump utility
th ac
– Tool for viewing and analyzing Oracle GoldenGate trails
e or
• Trace and TLTrace parameters
us @
to san
– Debugging feature to detect bottlenecks
• Oracle GoldenGate Veridata
se ne
Roadmap
• Knowledge documents
– Web-based
• Documentation
• ShowSyntax parameter
sa
• logdump utility
. ) ha
ide om
Gu .c
is le
th ac
e or
us @
to san
se ne
en a
lic ar.g
ble nk
Knowledge Documents
sa
• The customer portal enables you to search knowledge
. ) ha
documents about known issues:
ide om
– Enter GoldenGate as the product.
Gu .c
is le
th ac
e or
us @
to san
se ne
en a
lic ar.g
ble nk
Roadmap
• Knowledge documents
• Documentation
– HTML
– PDF
sa
• ShowSyntax parameter
. ) ha
• logdump utility
ide om
Gu .c
is le
th ac
e or
us @
to san
se ne
en a
lic ar.g
ble nk
Oracle GoldenGate:
• Installation and Setup Guides
• Windows and UNIX Administrator’s Guide
sa
• Windows and UNIX Reference Guide
. ) ha
• Windows and UNIX Troubleshooting and Tuning Guide
• Release Notes
ide om
• Error Messages Guide
Gu .c
is le
Download or view this documentation from the following
th ac
location:
e or
us @
http://www.oracle.com/technetwork/middleware/goldengate/doc
to san
umentation/index.html
se ne
en a
lic ar.g
ble nk
• Oracle GoldenGate Installation and Setup Guides: Provide an installation guide and
ns AN
setup guide for each database that is supported by Oracle GoldenGate. Each guide
tra S
GoldenGate components and explains how to plan for, configure, and implement Oracle
GoldenGate on Windows and UNIX platforms
AR
information about Oracle GoldenGate parameters, commands, and functions for the
Windows and UNIX platforms
SA
•
•
•
•
SA
NK
AR
no GA
Documentation
logdump utility
n- NE
tra S
ns AN
fe (s
Knowledge documents
ra a
ShowSyntax parameter
ble nk
lic ar.g
en a
se ne
Roadmap
to san
us @
e or
th ac
is le
Gu .c
Copyright © 2014, Oracle and/or its affiliates. All rights reserved.
ide om
. ) ha
sa
sa
– The WHERE clause may be using a non-indexed column.
. ) ha
– A row may be locked by another process.
ide om
– There may be no value for the SET clause.
Gu .c
is le
th ac
e or
us @
to san
se ne
en a
lic ar.g
ble nk
When you use ShowSyntax for the first time, use it only with guidance from an Oracle
ns AN
support analyst. It is a debugging parameter and can cause unwanted results if it is used
tra S
improperly.
n- NE
suspended.
• It slows down processing and can cause processing backups and latency.
AR
This parameter is recommended for use in a test environment; create duplicates of your
NK
Important: This parameter is valid only for Replicat from the OS prompt, and not from inside
GGSCI.
sa
• Start Replicat from the command shell in the home
. ) ha
directory.
ide om
– Do not specify a report file. The output must go to screen.
Gu .c
is le
Shell> ./replicat paramfile dirprm/<replicat_name>.prm
th ac
• The first SQL statement is displayed with some prompts.
e or
• In Oracle GoldenGate 12c, ShowSyntax now works with
us @
dynamic SQL.
to san
se ne
en a
lic ar.g
ble nk
In releases prior to Oracle GoldenGate 12c, ShowSyntax required the use of other
tra S
In Oracle GoldenGate 12c, by default, Replicat does not show LOB data or other data types
no GA
that are treated as a LOB by the database or by Oracle GoldenGate, whether or not the data
is bound in SQL. Examples include LOB, XML, and UDT data types. Instead, Replicat shows
AR
a data identifier (for example, <LOB data>). To display this type of data, specify the
NK
INCLUDELOB option of ShowSyntax. If the column data is not bound in a SQL statement,
Replicat does not show the data even when INCLUDELOB is used.
SA
**************************************************************
**
Run Time Messages
**************************************************************
**
sa
Opened trail file ./dirdat/aa000000 at 2014-02-09 13:38:35
MAP resolved (entry ODS.SCUSTMER):
. ) ha
MAP ODS.SCUSTMER, TARGET ODS.TCUSTMER, SQLEXEC (ID sel_tcust,
QUERY "SELECT city from ODS.TCUSTMER WHERE cust_code = 'ABC'",
ide om
NOPARAMS), colmap (cust_code = cust_code, name = name, city =
Gu .c
@getval (sel_tcust.city), state = state), REPERROR (1403,
is le
EXCEPTION), REPERROR (0001, EXCEPTION);
th ac
Using the following key columns for target table ODS.TCUSTMER:
e or
CUST_CODE.
us @
INSERT INTO "ODS"."TCUSTMER" ("CUST_CODE","NAME","STATE")
VALUES to san
('WILL','BG SOFTWARE CO.','WA')
se ne
Prompts
ns AN
• K=Keep Displaying: This is the default. To execute the current statement and
tra S
display the next. Even though K is the default, you still have to type K to make it do
n- NE
• S=Stop Display: To resume normal processing and stop printing SQL statements to
screen
AR
In this example, the literal SQL statement that Replicat delivers to the target database is
NK
displayed. These statements can be used with an Oracle explain plan to determine if the
database will use indexes to access the data. Sometimes a full-table scan, that is, not using
SA
•
•
•
•
SA
NK
AR
no GA
Documentation
logdump utility
n- NE
tra S
ns AN
fe (s
Knowledge documents
ra a
ShowSyntax parameter
ble nk
lic ar.g
en a
se ne
Roadmap
to san
us @
e or
th ac
is le
Gu .c
Copyright © 2014, Oracle and/or its affiliates. All rights reserved.
ide om
. ) ha
sa
sa
– Edit and reuse a history of numbered logdump command
. ) ha
lines
ide om
• Use logdump only if you need to view data in the Oracle
GoldenGate trail files.
Gu .c
is le
th ac
e or
us @
to san
se ne
en a
lic ar.g
ble nk
Note: For detailed information about using logdump, see the Oracle GoldenGate Windows
ns AN
Operation type
sa
and the time
. ) ha
that the record
was written
ide om
Source table
Gu .c
is le
Image type:
th ac
Can be a before or
e or
after image
us @
Record data
Column to san Record data (in ASCII)
information (in hex)
se ne
Oracle GoldenGate trail files are unstructured. The Oracle GoldenGate record header
ns AN
provides metadata of the data contained in the record and includes the following information:
tra S
• Transaction information (such as the transaction group and commit time stamp)
AR
The data area of the Oracle GoldenGate record contains the following:
• Time that the change was written to the GoldenGate file
NK
• Hdr-Ind
– Should always be E, indicating that the record was created
by Extract. Any other value indicates invalid data.
• UndoFlag
sa
– (NonStop) This is set when extracting aborted transactions
. ) ha
from the TMF trail.
ide om
• RecLength
Gu .c
– The length (in bytes) of the record buffer
is le
th ac
• IOType
e or
– The type of operation represented by the record. The most
us @
common types are 3 (delete), 5 (insert), 10 (update), 15
to san
(compressed update), and 116 (LOB).
se ne
en a
lic ar.g
ble nk
Hdr-Ind
ns AN
This should always be a value of E, indicating that the record was created by the Extract
tra S
UndoFlag
no GA
Normally, UndoFlag is set to 0. But if the record is the backout of a previously successful
operation, UndoFlag is set to 1. An undo that is performed by the disc process because of a
AR
RecLength
SA
This is always 28 KB. The data portion accommodates up to 24 KB of data (excluding LONG,
LOB, and UDT data), plus four for internal indicators. Extract abends when the length of the
data being written exceeds 24 KB. Update operations are most affected by this. In addition to
writing the after image of the updated columns to the record, GoldenGate also must write the
following for use in locating the target row:
• For updated rows that have a defined key, a substitute key defined with a KeyCols
clause, or a unique index, Extract sends the before image of the key or indexed
columns.
• For updated rows without a unique identifier, Extract sends the entire before image of
the row.
The 24 KB limit does not include the full size of VARCHAR2 and LOB/LONG/XML columns. It
includes only a specific number of bytes. GoldenGate stores a database change record in two
segments in the trail file: the base segment and the LOB segment. The base segment stores
all of the basic data types (such as CHAR, NUMBER, DATE, and so on) and reserves space
for the following types (if any of these columns exist):
• The first 200 bytes of each VARCHAR2
• The first 8000 bytes of each BLOB/LONG RAW
• The first 4000 bytes of each XML/CLOB/LONG
sa
The LOB segment stores the rest of a VARCHAR2 or LOB/LONG/XML column―namely, the
. ) ha
part that could not fit into the base segment. As many LOB segments as are needed are
created in 2000-byte chunks that follow the base segment in the trail. (Exception: If a
ide om
VARCHAR2 is part of the primary key, the whole VARCHAR2 is stored in the base segment,
regardless of its size.)
Gu .c
is le
It is the base segment that has the size limitation of 24 KB. To prevent data from exceeding
th ac
that size, GoldenGate sums the defined length of each column in a table (excluding any
e or
VARCHAR2 or LOB/LONG/XML), the assumption being that at least some rows will reach the
us @
defined lengths. That sum is reduced by the fixed amount of space reserved for VARCHAR2s
to san
(200 bytes each), BLOB/LONG RAWs (8000 bytes each), and XML/CLOB/LONGs (4000
bytes each). An additional 2 bytes per column are allocated to internal GoldenGate identifiers.
se ne
IOType
For a list of record types, see the Logdump chapter of the Oracle GoldenGate Windows and
ble nk
Note: this IOT is not to be confused with database index-organized tables (IOT).
fe (s
ns AN
tra S
n- NE
no GA
AR
NK
SA
• TransInd
– The position of the record in the current transaction, with the
following values:
— 0: The first record in the transaction
sa
— 1: Neither the first record nor the last record in the transaction
. ) ha
— 2: The last record in the transaction
3: The only record in the transaction
ide om
—
• SysKeyLen
Gu .c
is le
– (NonStop) The length of the system key (4 bytes or 8 bytes)
th ac
if the source is a NonStop file and has a system key
e or
us @
to san
se ne
en a
lic ar.g
ble nk
• AuditRBA
– For Oracle, this is the sequence number of the data source
(redo log).
• Continued
sa
– For Windows and UNIX, this identifies a BLOB segment.
. ) ha
– BLOBs that are too large to fit within one record are stored
ide om
across multiple records.
Gu .c
– Y = BLOB segment; N = not a BLOB segment
is le
•
th ac
Partition
e or
– This depends on the record type.
us @
– For NonStop BulkIO records, this indicates the number of the
to san
source partition where the bulk operation was performed.
se ne
AuditRBA
ns AN
For some data sources, such as NonStop, this is the relative byte address of the commit
tra S
record. In this case, all records in a transaction will have the same relative byte address. The
n- NE
Partition
AR
Partition tells GoldenGate the NonStop source partition to which the data was originally
written. Replicat uses the Partition field to determine the name of the target partition. The
NK
file name in the record header is always the name of the primary partition. Valid values for
BulkIO records are 0 through 15. For nonbulk operations, the partition can be either 0 or 4,
SA
• BeforeAfter
– BeforeAfter identifies whether the record is a before (B)
or after (A) image of an update operation.
– Inserts are always after images; deletes are always before
sa
images.
. ) ha
• IO Time
ide om
– Time stamp of the commit record
Gu .c
– All records in a transaction have the same commit time
is le
stamp.
th ac
•
e or
OrigNode
us @
– (NonStop) Node number of the system where the data was
to san
extracted
se ne
BeforeAfter
ns AN
If the primary key is part of the update, both a before image and an after image are saved.
tra S
IO Time
no GA
The time stamp uses local system time (based on GMT). If the transaction comes in over
AR
TCP/IP, the Server Collector checks the time; if the time differs from the local CPU clock, the
Server Collector makes an adjustment. This adjustment can be suppressed by using
NK
NoTCPSourceTimer.
SA
OrigNode
Each system in a NonStop cluster has a unique node number. Node numbers can range from
0 through 255. For records other than NonStop in origin, OrigNode is 0.
• FormatType
– Identifies whether the data was read from the transaction log or
fetched from the database:
— F: Fetched from database
sa
— R: Readable in transaction log
. ) ha
• Incomplete
– Is no longer used
ide om
• AuditPos
Gu .c
– Identifies the position of the Extract process in the transaction log
is le
th ac
– For an Oracle database, this is the relative byte address in the
e or
redo log.
us @
• RecCount to san
– When Windows and UNIX LOB data is divided into 2 KB chunks
se ne
When you use the “Extract to File” initial load method from an Oracle database with
ns AN
SOURCEISTABLE and either EXTFILE or RMTFILE, the FormatType shows R rather than
tra S
F.
n- NE
no GA
AR
NK
SA
sa
home directory.
. ) ha
3. Open the file:
ide om
Syntax:
Gu .c
is le
Logdump > Open <file_name>
th ac
Example:
e or
us @
Logdump > Open /home/ggs/dirdat/rt000000
to san
se ne
en a
lic ar.g
ble nk
Using logdump
sa
• Add column information.
. ) ha
Logdump > Detail On
• Add hex and ASCII data values to the column list.
ide om
Gu .c
Logdump > Detail Data
is le
• Control how much record data is displayed.
th ac
e or
Logdump > RecLen 280
us @
to san
se ne
en a
lic ar.g
ble nk
Detail Data
ns AN
Including column data can add significantly to the size of the displayed record if the table has
tra S
many columns.
n- NE
RecLen
no GA
Use RecLen to control how much of the record data is displayed. You can use RecLen to
AR
control the amount of scrolling that must be done when records are large, while still showing
enough data to evaluate the record. Data beyond the specified length is truncated.
NK
UserToken
SA
You can also choose to view user tokens. By default, the name of the token and its length are
displayed. Use the UserToken Detail option to show the actual token data.
sa
Logdump > Next (or just enter N)
. ) ha
To position at an approximate starting point and locate the next
ide om
good header record:
Gu .c
is le
th ac
Logdump > Pos <approximate_location>
e or
Logdump > ScanForHeader (or just enter sfh)
us @
to san
se ne
en a
lic ar.g
ble nk
sa
UndoFlag : . (x00) BeforeAfter: A (x41)
RecLength : 66 (x0042) IO Time : 2014/02/10 17:46:09.181
. ) ha
IOType : 5 (x05) OrigNode : 108 (x6c)
TransInd : . (x02) FormatType : F (x46)
ide om
SyskeyLen : 0 (x00) Incomplete : . (x00)
Gu .c
AuditRBA : 126445880 AuditPos : 0
is le
th ac
2014/02/10 17:46:09.181 Insert Len 66 Log RBA 0
e or
Name: TCUSTORD
us @
After Image: Partition 0
5749 4C4C 3139 3934 2D30 392D | to san WILL1994-09-30:15:33
3A30 3043 4152 2020 2020 2020 | :00CAR ........
se ne
ScanForEndTransaction
ns AN
Use ScanForEndTransaction (or sfet) to scan for a record in an Oracle GoldenGate trail
tra S
with a transaction indicator (TransInd) of x02. Other indicators can be the following:
n- NE
transaction. You can also find the beginning of the next transaction by using the
SA
ScanForNextTrans command.
TransInd
Examining TransInd can help you determine if records are corrupted. For example, if you
see an x02 end-of-transaction record, and if the next record is either x01 or x02, there is a
record missing from the transaction (the first operation was lost). This indicates that the trail
was overwritten. You can determine whether this is true by looking at the IO Time field to
see if there are unusual time differences (maybe the next record is older than the previous
one rather than newer). Also, the AuditPos and AuditRBA in the next record could reflect
an unexpected result (perhaps an earlier position in the file instead of the expected later
position).
sa
Hdr-Ind : E (x45) Partition : . (x00)
. ) ha
UndoFlag : . (x00) BeforeAfter: A (x41)
RecLength : 56 (x0038) IO Time : 2014/01/30 15:56:40.814
ide om
IOType : 5 (x05) OrigNode : 108 (x6c)
TransInd : . (x01) FormatType : F (x46)
Gu .c
SyskeyLen : 0 (x00) Incomplete : . (x00)
is le
AuditRBA : 105974056
th ac
e or
2014/02/03 15:56:40.814 Insert Len 56 Log RBA 1230
us @
Name: HR.SALES Partition 0
After Image:
to san
3220 2020 4A61 6D65 7320 2020 2020 4A6F 686E 736F | 2 James Johnso
6E20 2020 2020 2020 2020 2020 2020 4368 6F75 6472 | n Choudr
se ne
Filter is case sensitive. Enter table names as they appear in the source database. They will
ns AN
appear in the trail record in the same case in which they appear in the database. If the source
tra S
database is not case sensitive, names are converted by Oracle GoldenGate to uppercase
n- NE
before writing them to the trail, and you then use uppercase in your filter specification.
no GA
• Match All: Is required only if there are multiple filter criteria and you want the filter to
match all of them
AR
• Match Any: Applies the filter if the criteria match any of the multiple filters
NK
SA
sa
Hdr-Ind : E (x45) Partition : . (x00)
. ) ha
UndoFlag : . (x00) BeforeAfter: B (x42)
RecLength : 56 (x0038) IO Time : 2014/01/30 16:22:14.205
IOType : 3 (x03) OrigNode : 108 (x6c)
ide om
TransInd : . (x01) FormatType : F (x46)
SyskeyLen : 0 (x00) Incomplete : . (x00) If more data was
Gu .c
AuditRBA : 109406324 showing, you could
is le
Found hex string see ASCII values.
th ac
2014/01/30 16:22:14.205 Delete Len 56 Log RBA 64424
e or
File: TCUSTMER Partition 0
us @
Before Image:
to san
3620 2020 4A61 6D65 7320 2020 2020 4A6F 686E 736F
6E20 2020 2020 2020 2020 2020 2020 4574 6865 6C20
| 6 James Johnso
| n Ethel
2020 2020 2020 2020 2020 2020 2020 4C41 | LA
se ne
suppressed by filtering
lic ar.g
ble nk
Filter provides many options. For a complete reference, see the logdump documentation
ns AN
Use the RecLen command to specify the amount of data that is displayed.
n- NE
no GA
AR
NK
SA
sa
. ) ha
(Displays the record located at that RBA)
ide om
To go to the first record in the file:
Gu .c
is le
th ac
Logdump > Pos First
e or
Current position set to RBA 0
us @
Logdump > N
to san
se ne
en a
lic ar.g
ble nk
The position of each record is noted in the record header in the AuditPos field.
ns AN
Note: There is also a logdump command named ScanForRBA, which searches based on
the transaction RBA. This is not the command to use when searching for an RBA in the trail.
no GA
sa
Total Data Bytes 334802
. ) ha
Avg Bytes/Record 69
Delete 900
ide om
Insert 3902
Gu .c
FieldComp 26
is le
Before Images 900
th ac
After Images 3928
e or
us @
Average of 25 Transactions to san
Bytes/Trans ..... 22661
se ne
• Number of records in the file as of the RBA where the count began
• Total number of data bytes and average number of bytes per record
no GA
With options, you can view count information for each table and specify how the count is
generated:
SA
• Detail: Produces a summary count plus a count for each table or file that was
processed by Extract. The information includes the total and average numbers of data
bytes, as well as information about the operations on the table.
• START[TIME] <time_string>: Begins the count with the first record written at the
specified time
• END[TIME] <time_string>: Stops the count with the last record written at the
specified time
sa
. ) ha
ide om
Gu .c
is le
th ac
e or
us @
to san
se ne
en a
lic ar.g
ble nk
ra a
fe (s
ns AN
tra S
n- NE
no GA
AR
NK
SA
:
(Continued)
sa
:
TCUSTMER
. ) ha
Total Data Bytes 105624
Avg Bytes/Record 55
ide om
Delete 300
Gu .c
Insert 1578
is le
FieldComp 12
th ac
Before Images 300
e or
After Images 1590
us @
to san
se ne
en a
lic ar.g
ble nk
• The statistics in GGSCI show statistics from the process startup. They are reset if
tra S
restarted.
n- NE
TCUSTORD
Total Data Bytes 229178
sa
Avg Bytes/Record 78
Delete 600
. ) ha
Insert 2324
FieldComp 14
ide om
Before Images 600
Gu .c
After Images 233
is le
th ac
e or
us @
to san
se ne
en a
lic ar.g
ble nk
Because Count did not filter on table, each table’s count is shown.
ns AN
tra S
n- NE
no GA
AR
NK
SA
sa
Logdump > Save /home/oracle/save/sv000005
. ) ha
ide om
Gu .c
is le
th ac
e or
us @
To close the current file and open the next file in the trail:
to san
se ne
Saving Records
ns AN
Use Save to write a subset of the records to a new trail or Extract file.
tra S
n- NE
• By saving a subset to a new file, you can work with a smaller file that is easier to debug.
• Saving to another file also enables you to extract valid records that can be processed by
no GA
To set the version of the trail or file (to an old or a new format), use the TrailFormat
command. Note: Including the ! symbol (exclamation point) overwrites an existing file of the
NK
same name.
SA
sa
Shows features that are enabled (such as filter and header
. ) ha
views) and environment information (such as current trail and
position)
ide om
Gu .c
is le
th ac
e or
us @
to san
se ne
en a
lic ar.g
ble nk
LogTrail: /home/ggs/dirdat/rt000000
Trail Format: New
no GA
sa
Scan Notify Interval: 10000 records, Scrolling On
. ) ha
ide om
Gu .c
is le
th ac
e or
us @
to san
se ne
en a
lic ar.g
ble nk
ra a
fe (s
ns AN
tra S
n- NE
no GA
AR
NK
SA
sa
Logdump > log stop
. ) ha
To write text to the log:
Logdump > writelog "Customer name is ABC Company"
ide om
Gu .c
is le
th ac
e or
us @
to san
se ne
en a
lic ar.g
ble nk
To get help:
Logdump > Help
sa
Oracle GoldenGate Troubleshooting and Tuning Guide.
. ) ha
To exit logdump, use either of the following:
ide om
Gu .c
Logdump > Exit
is le
th ac
e or
Logdump > Quit
us @
to san
se ne
en a
lic ar.g
ble nk
sa
. ) ha
ide om
Gu .c
is le
th ac
e or
us @
to san
se ne
en a
lic ar.g
ble nk
ra a
fe (s
ns AN
tra S
n- NE
no GA
AR
NK
SA
• CD | Volume
• Decrypt On|Off
• ScanForRBA (sfr)
•
sa
ScanForTime (sfts)
. ) ha
• ScanForType (sft)
•
ide om
Skip
•
Gu .c
Time
is le
• TimeOffset
th ac
e or
• X
us @
to san
se ne
en a
lic ar.g
ble nk
• ScanForRBA (sfr): Scans for the record at a relative byte address specified by the
n- NE
• ScanForTime (sfts): Scans for a record that contains a specific time stamp. The
time stamp is contained in the IO Time field of the record header.
AR
NK
SA
sa
. ) ha
ide om
Gu .c
is le
th ac
e or
us @
to san
se ne
en a
lic ar.g
ble nk
ra a
fe (s
ns AN
tra S
n- NE
no GA
AR
NK
SA
sa
in bytes (200 max).
. ) ha
• Use either TransRecLimit or TransByteLimit to set a
ide om
lower boundary for what is considered a normal-sized
Gu .c
transaction.
is le
th ac
• Use the Count command to display statistics about
e or
transaction size.
us @
to san
• Use the logdump Position <RBA> command to go to
each RBA listed in the Count output. This gives you the
se ne
Using TransHist
ns AN
Transactions are tracked in descending order (according to the total number of bytes) to help
tra S
When the history table is full, the smallest transaction is removed to enable a larger
transaction to be added to the list.
NK
SA
sa
finishes scanning the files:
. ) ha
Transactions with at least 100 records or 100000 bytes
2014/02/01 09:31:24.000.000 00:00:00.000, Seq 0, RBA 13101
ide om
Bytes/Trans ..... 1168167
Records/Trans ... 1001
Gu .c
Files/Trans ..... 1
2014/02/01 09:31:35.000.000 00:00:11.000, Seq 0, RBA 1205292
is le
Bytes/Trans ..... 1168167
th ac
Records/Trans ... 1001
e or
Files/Trans ..... 1
2014/02/01 09:31:41.000.000 00:00:06.000, Seq 0, RBA 2397483
us @
Bytes/Trans ..... 1168167
Records/Trans ... 1001
Files/Trans ..... 1
to san
2014/02/01 09:42:36.000.000 00:10:55.000, Seq 0, RBA 3589674
se ne
Files/Trans ..... 1S
ble nk
In the screenshot, the first line (Transactions with at least 100 records or
ns AN
100000 bytes) indicates that the size boundary was set to the default of 100 operations or
tra S
100 KB. The defaults can be changed with the TransByteLimit and TransRecLimit
n- NE
parameters.
no GA
reduces the amount of data that is stored and, consequently, the amount of data that must be
reviewed when troubleshooting.
NK
logdump Filtering
sa
STRING [BOTH] /<text>/ [<column range>]
HEX <hex string> [<column range>]
. ) ha
TransID <transaction identifier>
FILENAME <filename template>
ide om
STARTTIME <date-time string>
Gu .c
ENDTIME <date-time string>
is le
TransIND [<comparison>] <nn>
th ac
RecLEN [<comparison>] <nn>
e or
AUDITRBA [<comparison>] <nnnnnnnn>
us @
<column range> is <start column>:<end column> e.g.
to san
0:231
se ne
<comparison> is one of =, ==, !=, <>, <, >, <=, >= EQ,
en a
Adding a filter to your search criteria is one of the best features of logdump. Here are some
ns AN
FILTER SHOW
n- NE
<options> are
RecTYPE <type number | type name>
STRING [BOTH] /<text>/ [<column range>]
HEX <hex string> [<column range>]
TransID <TMF transaction identifier>
FILENAME <filename template>
PROCESS <processname template>
sa
ANSINAME <ansi table name>
<filterid>
. ) ha
RecTYPE,STRING,HEX,TransID,FILENAME,PROCESS,INT16,
INT32,INT64,RBA,STARTTIME,ENDTIME
ide om
TransIND, UNDOFLAG, RecLEN, AUDITRBA, ANSINAME
Gu .c
<column range>
is le
<start column>:<end column> e.g. 0:231
th ac
<comparison>
e or
=, ==, !=, <>, <, >, <=, >= EQ, GT, LE, GE, LE, NE
us @
X <program> [string] - Execute <program>
to san
se ne
en a
lic ar.g
ble nk
ra a
fe (s
ns AN
tra S
n- NE
no GA
AR
NK
SA
sa
[OLDFORMAT] - force oldformat records
. ) ha
[NEWFORMAT] - force newformat records
[EXT ( <pri>, <sec> [,<max>])] - Savefile Extent sizes on NSK
ide om
[MEGabytes <nnnn>] - For extent size calculation
Gu .c
is le
th ac
e or
us @
to san
se ne
en a
lic ar.g
ble nk
ra a
fe (s
ns AN
tra S
n- NE
no GA
AR
NK
SA
sa
TRAILFORMAT old| new - force trail type
. ) ha
ide om
Gu .c
is le
th ac
e or
us @
to san
se ne
en a
lic ar.g
ble nk
ra a
fe (s
ns AN
tra S
n- NE
no GA
AR
NK
SA
Quiz
sa
c. Execute the Detail On command.
. ) ha
d. None of the above
ide om
Gu .c
is le
th ac
e or
us @
to san
se ne
en a
lic ar.g
ble nk
Answer: a
ns AN
tra S
n- NE
no GA
AR
NK
SA
Practice 3 Overview:
Examining the Evidence
The practices in this lesson cover the use of the following:
• ShowSyntax
• logdump
sa
. ) ha
ide om
Gu .c
is le
th ac
e or
us @
to san
se ne
en a
lic ar.g
ble nk
Summary
sa
• Documentation
. ) ha
• ShowSyntax parameter
• Logdump utility
ide om
Gu .c
is le
th ac
e or
us @
to san
se ne
en a
lic ar.g
ble nk