|
DB2 Log Analysis Tool Version 2.2
|
|||||
| APAR | CLOSE DATE |
PTF(s) | Fixing APAR if PE |
HIPER? | Abstract |
|---|---|---|---|---|---|
2008 |
RECONCILIATION PROBLEM BETWEEN GENERAL REPORT AND LOAD IN DB2 LOG ANALYSIS TOOL HIGH SPEED MODE | ||||
2008 |
LOADFILE PROBLEMS WHEN ADVANCED DB2 LOG ANALYSIS TOOL OPTION BYPASS DEFAULTIF USED ON TABLE WITH NON NULL AND HAS DEFAULT | ||||
2008 |
POSSIBLE ALAA0440E OR ALAA0447E WHILE USING MISCELLANEOUS FILTERS AND TABLES WITH DCC TURNED LOG FORWARD MODE | ||||
2008 |
IF THE GMT OFFSET INCLUDES A PARTIAL HOUR AMOUNT, IT IS POSSIBLETO GET NO DATA BACK FROM DB2 LOG ANALYSIS TOOL | ||||
2008 |
UTILID MAY NOT BE UNIQUE, CAUSING DUPLICATE ERROR | ||||
2008 |
DB2 LOG ANALYSIS WAS NOT REPORTING ACTIVITY ON TABLES WITH AN OBID OF 1. | ||||
2008 |
ABENDS0C4 IN CSECT ALAURID WITH MASS DELETES AND DATA SHARING | ||||
2008 |
INVALID DATE OR DUPLICATE ENTRY ADDED TO ARCHIVE TABLE ARCHIVINGOUTPUT DB2 LOG ANALYSIS TOOL RUN IF NO ACTIVITY WAS REPORTED | ||||
2008 |
SQLCODE313 WHEN USING CURRENT ROW BY KEY AND THE TABLE HAS MULTIPLE UNIQUE INDEXES | ||||
2008 |
POSSIBLE ALAA447E, ALAA440E IF THERE ARE MANY ACTIONS FOR ONE ROW AND A MASS DELETE WAS FOUND ON A DIFFERENT OBJECT | ||||
2008 |
NULL VALUE MAY BE QUOTED IN SQL IF ALTER CONDITION FOUND | ||||
2008 |
INCORRECT TIME TRANSLATION IF LEAP SECONDS ARE PRESENT | ||||
2008 |
EXCLUDING OBJECTS IN DETAIL REPORT OR IN RESPONSE TO ALAA358E MSG RESULTED IN OBJECTS STILL BEING CONSIDERED | ||||
2008 |
WHEN MANY INSTANCES OF A MASS DELETE ARE FOUND WITHIN THE TIME FRAME BEING PROCESSED AN 0C4 IS LIKELY TO OCCUR | ||||
2008 |
WHEN CCSID CONVERSIONS FAIL DURING DB2 LOG ANALYSIS PROCESSING, INVALID SQL STATEMENTS CAN OCCUR | ||||
2007 |
ALAA051E-GET ERR FOR ROWDATA, RES CDE: 088 DUE TO RECORD ACCESSBIAS=SYSTEM WHICH CAUSES VSAM RET CODE=X'58' (DECIMAL 88) | ||||
2007 |
ALADTL3 RECEIVES AN 0C4 WHEN DB2 IDS CAN NOT BE FOUND IN A STORED FILE DURING LOG BACKWARD REPORTING. | ||||
2007 |
CHARACTER FOR BIT DATA WILL NOW BE GENERATED IN A HEXADECIMAL FORMAT IN THE SQLOUT FILE | ||||
2007 |
ADD SUPPORT FOR THE CLEAR KEY ENCRYPTION EDITPROC FROM THE IBM DATA ENCRYPTION FOR IMS AND DB2 DATABASES | ||||
2007 |
INCORRECT SQL STATEMENTS ARE BEING GENERATED FOR GRAPHIC COLUMNSCONTAINING MORE THAN 20 CHARACTERS SQLCODE322 | ||||
2007 |
LOG ANALYSIS MAY ENCOUNTER AN ALAA067E ERROR DURING CERTAIN RESTART CONDITIONS | ||||
2007 |
DB2 LOG ANALYSIS TOOL MAY END IN AN 0C4, IF PROCESSING INCLUDES NON-CATALOGED ARCHIVED LOG DATASETS | ||||
2007 |
POSSIBLE ALAA447E, ALAA440E MESSAGE WHEN MANY UPDATES TO SAME ROW | ||||
2007 |
POSSIBLE BAD OUTPUT OR S0C4 INVOLVING DECLARED GLOBAL TEMP TABLE | ||||
2007 |
ABENDB37 RC04 USING DB2 LOG ANALYSIS TOOL REPORT UTILITY | ||||
2007 |
SQLCODE104 WHEN PROCESSING ARCHIVED OUTPUT IF USING DB2 V8 COMPATIBILITY | ||||
2007 |
MESSAGE ALAA358E MAY INCORRECTLY BE RETURNED | ||||
2007 |
MESSAGE ALAA447E MAY OCCUR WHEN MASSIVE NUMBERS OF UPDATES OCCURTO SAME ROW | ||||
2007 |
ALAA058W MESSAGE CAUSES S001 RC04 IN LOG-FORWARD MODE | ||||
2007 |
DB2 DATA TYPES OF 'FLOAT' NOT ACCURATE ENOUGH DURING CONVERSION FROM INTERNAL TO DISPLAY FORMAT. MESSAGE ALAA325E MAY RESULT. |
||||
2007 |
ALAA036E-THE REQUESTED FILTER OBJECT XXXXX .%%%%%%%% WAS NOT FOUND. | ||||
2007 |
CONTINUOUS MODE PROBLEM HANDLING 32K PAGESIZES ABENDS AND OTHER UNPREDICTABLE RESULTS | ||||
2007 |
ALAA041E MESSAGE WHILE DECOMPRESSING DATA. | ||||
2007 |
A S0C4 IS POSSIBLE WHEN USING CONTINUOUS MODE AND NO DATA IS READ . THE ABEND OCCURS IN PROGRAM ALASUBG | ||||
2007 |
SQL RETURN CODE = +100 | ||||
2007 |
ABENDSB37 POSSIBLE AGAINST SYSPRINT DURING REPORT UTILITY PROCESSING | ||||
2007 |
INCORRECT HANDLING OF DB2 LOAD RECORDS FOUND IN THE LOG | ||||
2007 |
GENERATED SQL IS NOT CORRECT WHEN A DELIMETER IS EMBEDDED OR X'00' IS EMBEDDED | ||||
2007 |
ALAA415E MESSAGE ON A NEW DB2 SUBSYSTEM | ||||
2007 |
A00 ABEND DURING LOG-BACKWARD DETAIL REPORT | ||||
2006 |
GENERATED SQL IS NOT USABLE WHEN A X'0E' IS EMBEDDED WITHIN A CHARACTER STRING WITHOUT A TRAILING X'0F' | ||||
2006 |
MASS DELETE NOT FILTERED OUT IN DETAIL REPORT | ||||
2006 |
USE OF MISCELLANEOUS FILTERS ONLY CAUSING ALAA440E | ||||
2006 |
COMBINATION OF MISCELLANEOUS AND OBJECT FILTERS CAN CAUSE MSGALAA440E | ||||
2006 |
DISTINCT COLUMN TYPES CAUSE USER ABEND 50 IN ALAGLOAD EXTERNAL SYMPTOM CODE | ||||
2006 |
S0C4 OR BAD OUTPUT FORMATTING GRAPHIC UNICODE DATA | ||||
2006 |
FAST APPLY SQL PROCESSING MAY RETURN PARSER ERRORS WHEN PARSING SQL STATEMENTS THAT HAVE EMBEDDED QUOTES. | ||||
2006 |
ABEND OR INCORRECT OUTPUT WHEN LGBFLGS2=LGBFLOG | ||||
2006 |
POSSIBLE S0C4 READING BSDS AFTER DSNJCNVB | ||||
2006 |
INCORRECT OUTPUT DURING DROPPED OBJECT MODE WHEN IDS ARE SWAPPED | ||||
2006 |
EMBEDDED QUOTE AT END OF A LINE CAUSING GENERATED SQL TO FAIL | ||||
2006 |
FAST APPLY TREATING DOUBLE PRECISION FLOATING POINT VALUES AS SINGLE PRECISION | ||||
2006 |
ERROR MESSAGE ALAA157E DURING CONTINUOUS MODE PROCESSING | ||||
2006 |
LONG SQL STATEMENTS CAUSING SQL GENERATION FAILURE | ||||
2006 |
UNNEEDED LOG RECORDS ARE TRACKED, MAY CAUSE ABENDS | ||||
2006 |
FLOAT FIELDS MAY CAUSE ALAA325E MESSAGE | ||||
2006 |
ALAA190E DURING DATA DECOMPRESSION | ||||
2006 |
POSSIBLE S0C4 ON ALAGLOAD WITH MANY COLUMN NAMES | ||||
2006 |
POSSIBLE S0C4 IN ALASUBG PROCESSING DECLARED GLOBAL TEMPORARY TABLES | ||||
2006 |
ALAA440E DUE TO DB2 RECOVER UTILITY IN-PROCESS | ||||
2006 |
GENERATED SQL MAY EXCEED COLUMN 72 | ||||
2006 |
MISCELLANEOUS FILTERS NOT WORKING IN DETAIL REPORT | ||||
2006 |
PREVIOUSLY USED JOB ID REQUIRED FOR #6 OF PRIMARY MENU | ||||
2006 |
ARCHIVING ISSUES WITH PANEL AND RUNTIME ERRORS | ||||
2006 |
S0C4 WHEN MANY TABLES USED AS INPUT DURING AUDIT MODE LOAD PROCESS | ||||
2006 |
CONTINUOUS MODE CAN HANG AFTER CLOCK CHANGE. | ||||
2006 |
ABENDS0C4 DURING ALAESQL EXECUTION USING AUDIT MODE | ||||
2006 |
POSSIBLE B37 ON ARCHIVE FILE GENERATED BY LOG ANALYSIS TOOL | ||||
2006 |
POSSIBLE ALAA190E OR S0C7 DURING DECOMPRESSION ROUTINE. | ||||
2006 |
POSSIBLE ABEND S0C4 DURING LOG READS. | ||||
2006 |
ABEND S0C4 DURING PROGRAM ALAGEN1 DUE TO EXCESSIVE LOG DATA TRACKED | ||||
2006 |
POSSIBLE ALAA190E OR ALAA041E RUNNING IN DROPPED OBJECT MODE | ||||
2006 |
USE OF MISCELLANEOUS FILTERS ONLY CAUSES POSSIBLE ABEND0C4 IN ALASUBG | ||||
2006 |
DECOMPRESSION ISSUES REGARDING PAGE SIZES > 4K | ||||
2006 |
MISSING RECORDS DUE TO MEMBER CLUSTER OPTION | ||||
2006 |
NEED TO SUPPRESS REPORTING ON CERTAIN DB2 LOGGED ACTIVITY | ||||
2006 |
NEGATIVE DECIMAL CONVERSION ERROR GENERATING LOADFILE | ||||
2006 |
SYSTABLESPACE COLUMN TYPE=K NOT TREATED AS LARGE TABLESPACE | ||||
2006 |
ALAA040E ERROR MSG USING INCREMENTAL IMAGE COPIES AND MASS DELETES | ||||
2006 |
WHEN EXCESSIVE AMOUNTS OF DATA ARE TRACKED, POSSIBLE S0C4 IN GENERAL REPORT. | ||||
2006 |
GENERATED SQL MAY BE INCORRECT WHEN USING DBCS STRINGS | ||||
2006 |
TIME RANGE REQUESTS YIELD INCORRECT RESULTS IN DISABLED DATA SHARING | ||||
2006 |
PROBLEMS GENERATING JCL USING INTERFACE BETWEEN DB2 OBJECT RESTORE R210 AND DB2 LOG ANALYSIS R220 | ||||
2005 |
FULL ROW IMAGES NOT PROPERLY MATERIALIZED IF RE-CREATED OBJECT HAS NEW | ||||
2005 |
POSSIBLE ALAA040E ERROR MESSAGE PROCESSING LOG-FORWARD DETAIL REPORT | ||||
2005 |
ENHANCE INFORMATIONAL MESSAGE WHEN "SUPPORT FOR UNICODE" INTERFACE | ||||
2005 |
S0C4 OCCURS DURING PROGRAM ALADTL1 DUE TO EXHAUSTED MEMORY | ||||
2005 |
MESSAGE ALAA156I INCORRECTLY GENERATED DURING UNICODE CONVERSIONSERVICES | ||||
2005 |
LONG RUNNING DETAIL REPORT DURING IMAGE COPY READ | ||||
2005 |
S0C7 DURING DATA DECOMPRESSION DUE TO FASTPATH OPTION | ||||
2005 |
INTERFACE WITH OBJECT RESTORE FAILS TO PROPERLY HANDLE DROP TABLE | ||||
2005 |
ERROR HANDLING IMPROPER IN SOME CASES AND MAY CAUSE PROGRAM TO CONTINUE | ||||
2005 |
DECLARED GLOBAL TEMPORARY TABLES CAUSES S0C4 IN GENERAL REPORT MODULE ALASUBG | ||||
2005 |
PROBLEMS DURING READING AMONGST MULTIPLE DATASET TABLESPACES | ||||
2005 |
INVALID SQL CONCAT STATEMENT BUILT BY PRODUCT IN GENERATED SQL | ||||
2005 |
MESSAGE HELP FACILITY CAN GO INTO LOOP WHEN USER CONTINUOUSLY ENTERS INVALID INPUT | ||||
2005 |
SUPPORT "STCK TO LRSN DELTA" IN THE DB2 BSDS | ||||
2005 |
USER ABEND 61 PROCESSING TABLESPACES WITH DSSIZE SPECIFICATION | ||||
2005 |
S0C4 IN ALADTL1 PROCESSING CATALOG TABLE SYSINDEXES | ||||
2005 |
MISSING QUIET TIME REPORT ON A DATA SHARING SYSTEM | ||||
2005 |
RETURN CODE 8 ON VSAM PUT DUE TO IDENTICAL LRSNS RC08 | ||||
2005 |
MESSAGE ALAA073W INCORRECTLY GENERATED USING EXPERT OPTIONS. | ||||
2005 |
ICH408I INSUFFICIENT ACCESS AUTHORITY READING MULTI-VOLUME TAPE ARCHIVE LOG | ||||
2005 |
S0C4 IN CSECT ALASKLR WHEN MANY ICTYPE='P' RECORDS IN SYSCOPY | ||||
2005 |
POSSIBLE BUFFER OVERLAYS CAN CAUSE INCORRECT REPORT OUTPUT | ||||
2005 |
FAST APPLY - U4083 ABEND ON V8 WITH LONG TABLE NAME | ||||
2005 |
S0C4 USING FAST APPLY WITH RESTART=I WITH NO RESTART NAME | ||||
2005 |
FAILURE CALLING FIELD PROCEDURE WHEN PARAMETER LIST IS NOT NULL | ||||
2005 |
POSSIBLE BAD OUTPUT IN DETAIL REPORT AND SUBSEQUENT PROCESSES HANDLING ABORTED URS | ||||
2005 |
MESSAGE ALAA460E INCORRECTLY GENERATED IN PLACE OF MORE SPECIFICMESSAGE | ||||
2005 |
POSSIBLE S0C7 DURING DATA DECOMPRESSION IN CSECT ALAEXP | ||||
2005 |
POSSIBLE MISSING DATA IN GENERAL REPORT OUTPUT USING DB2 SUBSYSTEM WITH NO ARCHIVING | ||||
2005 |
MESSAGE ALAA024E RETURN CODE 000 REASON CODE 000 RETURNED ON DISABLED DB2 DATA SHARING SUBSYSTEM | ||||
2005 |
PRODUCT MISINTERPRETS RETURN CODE OF SPACES FROM FIELD PROCEDUREAS ERROR | ||||
2005 |
LRSN VALUES FROM DB2 LOG REFLECTING YEAR-END VALUES CAN BE INCORRECTLY TRANSLATED | ||||
2005 |
MSG ALAA0411E DETECTED DURING LOG-BACKWARD PROCESSING OF DETAIL REPORT | ||||
2005 |
INCORRECT DATA RETURNED WITH USE OF SINGLE % WILDCARD FOR AUTHID FILTERS | ||||
2005 |
CLARIFICATION OF DISTRIBUTED TYPE FILTER USAGE IN HELP | ||||
2005 |
PRODUCT ERRORS WHEN USING DISABLED DATA SHARING BSDS | ||||
2005 |
LOADCARD CAN BE IMPROPERLY GENERATED IF TARGET TABLE OWNER/NAME = 26 CHARACTERS | ||||
2004 |
POSSIBLE S0C4 IN FECLINKL IN ALADTL1 USING LOG-FORWARD MODE | ||||
2004 |
INCORRECT ERROR MESSAGE GENERATED WITH MISSING ALA ARCHIVE DATASET | ||||
2004 |
INVALID OUTPUT AFTER FIELDPROC CONVERSION | ||||
2004 |
ALA 2.2 ROLLUP APAR | ||||