|
DB2 Log Analysis Tool Version 1.3
|
|||||
| APAR | CLOSE DATE |
PTF(s) | Fixing APAR if PE |
HIPER? | Abstract |
|---|---|---|---|---|---|
2006 |
WHEN EXCESSIVE AMOUNTS OF DATA ARE TRACKED, POSSIBLE S0C4 IN GENERAL REPORT. | ||||
2005 |
USER ABEND = 61 FOR INCORRECT RELATIVE PAGE NUMBER DETERMINATION | ||||
2005 |
PROBLEMS DURING READING AMONGST MULTIPLE DATASET TABLESPACES | ||||
2005 |
SUPPORT "STCK TO LRSN DELTA" IN THE DB2 BSDS | ||||
2005 |
USER ABEND 61 PROCESSING TABLESPACES WITH DSSIZE SPECIFICATION | ||||
2005 |
LRSN VALUES FROM DB2 LOG REFLECTING YEAR-END VALUES CAN BE INCORRECTLY TRANSLATED | ||||
2004 |
DB2 LOG ANALYSIS TOOL R130 DOES NOT SUPPORT ALL METHODS OF CHARACTER CONVERSION WITH UNICODE DATA | ||||
2004 |
LOAD CARDS INCORRECTLY GENERATED WHEN LONG ROW LENGTH IS ENCOUNTERED | ||||
2004 |
BAD SQL GENERATED WITH LONG VARCHAR COLUMN DATA OF LENGTH 500 | ||||
2004 |
UPDATES CAN BE INCLUDED IN REPORTS WHEN ONLY DELETES/INSERTS WERE REQUESTED. | ||||
2004 |
Archive log access failure may not properly attempt active log access | ||||
2004 |
If decimal point = ',' generated SQL can be incorrect | ||||
2004 |
ALAA172W messages, bad SQL and detail report output possible handling certain update type log records | ||||
2004 |
POSSIBLE SQLCODE104 WHEN RUNNING DYNAMIC SQL AND DECIMAL POINT = COMMA | ||||
2004 |
PROGRAM ALALF1 CAN FORCE A ABENDS0C1 WHEN PARTITIONED TABLESPACEIS ACCESSED IN DROPPED-OBJECT MODE | ||||
2004 |
LONG RUNNING DETAIL REPORT JOB DURING MERGE PROCESSING DUE TO REPETITIVE INSERT/DELETE ACTIVITY AGAINST SINGLE TABLE. | ||||
2004 |
ABENDU0061 DURING DETAIL REPORT PROCESSING ACCESSING TABLESPACE GREATER THAN 2GB | ||||
2004 |
INCORRECT SQL GENERATION AS A RESULT OF VARIABLE LENGTH COLUMNS WITH LENGTH=0 | ||||
2004 |
ALAA052E ERROR MSG FROM DETAIL REPORT WITH RETURN CODE = 20, RESOURCE CONTENTION | ||||
2004 |
IF DB2 DECIMAL POINT DEFINED AS COMMA, SQL ERRORS OCCUR DURING LOAD PROCESS (DDL CREATE) AND STATIC SQL PROGRAM EXECUTION | ||||
2004 |
INCORRECT HANDLING OF 3-CHARACTER SSID USING ALA#LOAD MAY CAUSE BAD CONFIGURATION OR RETURN CODE =4 | ||||
2004 |
DB2 COMMIT ISSUED MORE FREQUENTLY THAN REQUESTED WHILE RUNNING 'DYNAMIC SQL IN BATCH' | ||||
2004 |
COLUMN NAMES WITH EMBEDDED SPACES NOT HANDLED PROPERLY IN REPORTS, SQL, AND LOAD PROCESSING | ||||
2004 |
ABEND SOC4 IN MODULE ALALF1 IN DETAIL STEP7 OR BAD DETAIL REPORTOUTPUT | ||||
2004 |
S0C4 RC=11 IN ALAMAIN | ||||
2003 |
ABENDs0978 ( S0978 ) - Error in FREEMAIN due to Storage overlay | ||||
2003 |
POSSIBLE S0C4 ABEND (W/O WILDCARDS) OR ERROR MSG ALAA036E (WITH WILDCARDS) WHEN REQUESTING MANY OBJECTS FROM LIST. | ||||
2003 |
LONG ALALF1 RUNTIME, MESSAGE ALAA156I: RE-READING BSDS ISSUED SEVERAL TIMES AND DB2 LOGS ARE READ OVER AND OVER AGAIN. | ||||
2003 |
INVALIDE CARRIAGE CONTROL CHARACTER IN COLUMN 1 OF REPORT | ||||
2003 |
ABEND0C4 OR ABEND0E0 IN MODULE ALALF1: OR ABEND0C4 IN ALABSQL: REDUCE MSGALAA156I WHEN DATA COMPRESSION IS PRESENT | ||||
2003 |
DYN ALLOC FAILURE (NO DEVICES AVAILABLE) ALLOWS NO RETRY: FALSE ALAA061W MSGS: ALALOAD PROBLEM: ABENDS0C4 IN ALAREC3 | ||||
2003 |
ALAA073W GENERATED IN ERROR DUE TO ALA NOT PROPERLY RETRIEVING DICTIONARY PAGE FOR PGLOGRBA VALUE, ABENDS0C4 OR ABENDS0C1 | ||||
2003 |
INCORRECT HANDLING OF MULTI-VOLUME CATALOGED ARCHIVE LOGS IN THEBSDS CAN RESULT IN INCORRECT LOG READING. | ||||
2003 |
INCORRECT OUTPUT CAN OCCUR IF NUMBER OF ACTIVE LOGS ARE LOW AND ARCHIVING OCCURS RAPIDLY WHEN 'ACTIVE LOG PRIORITY=Y' | ||||
2003 |
INCORRECT HANDLING OF MULTI-VOLUME CATALOGED ARCHIVE LOGS IN THEBSDS CAN RESULT IN INCORRECT LOG READING. | ||||
2003 |
INCORRECT OUTPUT IN GENERATED UNDO/REDO SQL DURING DETAIL REPORTRUN | ||||
2003 |
I/O PERFORMANCE, STORAGE REUSE AND AUO INTERFACE IMPROVEMENTS: ADDITION OF EXTENDED REPORT OPTION: HELP TEXT ADDITIONS | ||||
2003 |
ABENDS013 RC4C IN DETAIL RPT: INCORROUT IN DETAIL REPORT FOR UPDATES WHERE EVERY COLUMN INCORRECTLY FLAGGED AS CHANGED | ||||
2003 |
ABENDS0C4 IN ALAREC3/ALALF3 FIELDPROCS PRESENT: MSGCTC910E IN IN SETUP: LOOP IN ALALF1: ABENDS0C4 IN ALALF3 | ||||
2003 |
DB2 OBJECT RESTORE INTERFACE JCL ERRORS: IMPROPER SUMMARY REPORTFORMATTING: LOAD UTILITY ERROR: ABENDS0C4 IN ALAREC3 OR ALALF3 |
||||