|
DB2 Log Analysis Tool Version 2.1
|
|||||
| APAR | CLOSE DATE |
PTF(s) | Fixing APAR if PE |
HIPER? | Abstract |
|---|---|---|---|---|---|
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 |
SQL RETURN CODE = +100 | ||||
2007 |
POSSIBLE S0C4 WHEN LGBFLGS2=LGBFLOG USING LOG-FORWARD MODE | ||||
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 | ||||
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 |
DISTINCT COLUMN TYPES CAUSE USER ABEND 50 IN ALAGLOAD EXTERNAL SYMPTOM CODE | ||||
2006 |
S0C4 OR BAD OUTPUT FORMATTING GRAPHIC UNICODE DATA | ||||
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 |
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 |
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 |
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 |
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 | ||||
2005 |
FULL ROW IMAGES NOT PROPERLY MATERIALIZED IF RE-CREATED OBJECT HAS NEW | ||||
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 |
S0C4 IN ALAGEN1 USING OBJECT RESTORE INTERFACE ONLY | ||||
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 |
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 |
POSSIBLE ALAA190E MSG (MISSING DICTIONARY) WHEN INCREMENTAL IMAGE COPIES ACCESSED | ||||
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 |
FAILURE CALLING FIELD PROCEDURE WHEN PARAMETER LIST IS NOT NULL | ||||
2005 |
POSSIBLE BAD OUTPUT IN DETAIL REPORT AND SUBSEQUENT PROCESSES HANDLING ABORTED URS | ||||
2005 |
PRODUCT MISINTERPRETS RETURN CODE OF SPACES FROM FIELD PROCEDUREAS ERROR | ||||
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 |
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 |
ALLOW USER TO HAVE GREATER CONTROL OVER FORMAT OF GENERATED LOADFILE. | ||||
2005 |
BAD LOADCARD GENERATED IF TARGET TABLE LEFT BLANK | ||||
2005 |
INCORRECT ERROR MESSAGE GENERATED WITH MISSING ALA ARCHIVE DATASET | ||||
2004 |
INVALID OUTPUT AFTER FIELDPROC CONVERSION | ||||
2004 |
PRODUCT ERRORS WHEN USING DISABLED DATA SHARING BSDS MESSAGE ALAA415E | ||||
2004 |
IMAGE COPY READS TAKE EXCESSIVE TIME WHEN ONLY DICTIONARY NEEDED | ||||
2004 |
ALAA190E POSSIBLE DUE TO MISSING DICTIONARIES ON PARTITIONED TABLESPACE | ||||
2004 |
POSSIBLE MISSING REPORTED DATA DUE TO MISHANDLING OF INTERNAL RE-USEABLE STORAGE AREAS FOR ROLLBACKS. | ||||
2004 |
DECOMPRESSION FAILURE DUE TO INCOMPLETE IMAGE COPY ACCESS POSSIBLE ABENDS S0C7/S0C4 AT D60 IN ALAEXP IN ALADTL2 | ||||
2004 |
Possible incorrect product-generated audit header column names, Load Details Step 4 RC8, MSGDSNU089I | ||||
2004 |
MERGE PROCESS WITH DATA CAPTURE CHANGES CAN BE SLOW AND/OR GENERATE INCORRECT RESULTS. | ||||
2004 |
MESSAGE ALAA190E (MISSING DICTIONARY) IN LOG-FORWARD MODE DETAILREPORT. | ||||
2004 |
POSSIBLE PUT ERROR RC08 DUE TO VIEW/ALIAS ON TABLE INVOLVED IN LOAD REPLACE. | ||||
2004 |
POSSIBLE S0C4 IN A DATA SHARING ENVIRONMENT WHILE READING DB2 LOGS. | ||||
2004 |
S0C1 ABEND in module ALAMMIF, load module ALATDLI possible when reading active logs | ||||
2004 |
ERRONEOUS SQL GENERATED WITH LONG VARCHAR COLUMN DATA OF LENGTH 500 | ||||
2004 |
Possible ALAA415E message incorrectly written during CMODE processing | ||||
2004 |
RACF FAILURE READING ACTIVE LOGS ONLY WHEN UACC(NONE) FOR CURRENT USER. | ||||
2004 |
S0c7 possible when user incorrectly edits filters | ||||
2004 |
UNNEEDED LOG RECORDS (USED FOR ROW MOVEMENT BY DB2) ERRONEOUSLY USED IN REPORTING: RESULTS IN INCORRECT OUTPUT | ||||
2004 |
Log records resulting in physical row movement from one dataset to another causing ABENDU0061 in log-backward mode | ||||
2004 |
POSSIBLE BAD OUTPUT WHEN FILTERING ON SPECIFIC TYPES OF DML ACTIVITY ALAA172E | ||||
2004 |
GENERAL PERFORMANCE IMPROVEMENTS TO ALLEVIATE LONGER ELAPSED ANDCPU TIMES | ||||
2004 |
Possible missing detail report data due to DATA CAPTURE CHANGES with INSERT or DELETE. | ||||
2004 |
If decimal point = ',' generated SQL can be incorrect | ||||
2004 |
Abend S0C1 or S0C4, or other possible problems, in load module ALAGLOAD in any module due to storage overlay | ||||
2004 |
POSSIBLE ABEND OR ERROR DURING LOG-FORWARD MODE WHEN LOGGED UTILITIES AFFECT MANY PAGES | ||||
2004 |
S0c4 in ALAGEN1 when using wildcards on table filters | ||||
2004 |
Rollbacks improperly bypassed in standard LOAD mode (i.e, non-audit mode). | ||||
2004 |
Archive log access failure may not properly attempt active log access | ||||
2004 |
LOOPING CAN OCCUR IN PROGRAM ALADTL2 DURING CCSID CONVERSION | ||||
2004 |
UPDATES CAN BE INCLUDED IN REPORTS WHEN ONLY DELETES/INSERTS WERE REQUESTED. | ||||
2004 |
S0C4 RUNNING GENERAL REPORT WITH NO FILTERS IN CSECT ALASKLR. | ||||
2004 |
POSSIBLE BAD OUTPUT OR ABEND USING LOG-FORWARD IN DATA SHARING ENVIRONMENT | ||||
2004 |
POSSIBLE BAD CHANGE INDICATOR VALUES AFTER LOADING DATA INTO DB2TABLE. | ||||
2004 |
ALAA037E MESSAGE WHEN RUNNING GENERAL REPORT WITH NO OBJECT FILTERS (OR VERY MANY OBJECT FILTERS). | ||||
2004 |
USER ABEND 61 DURING DETAIL REPORT PROCESSING ACCESSING TABLESPACE GREATER THAN 2GB | ||||
2004 |
S0C4 in module ALAGEN1 (csect ALAQT) while processing quiet time report. | ||||
2004 |
POSSIBLE SQLCODE104 WHEN RUNNING DYNAMIC SQL AND DECIMAL POINT = COMMA | ||||
2004 |
TUTORIAL TEXT FOR V2.1 INCORRECTLY REFLECTS SOME PRE-V2.1 RELEASE INFORMATION. | ||||
2004 |
IEC024I HANDLING USER ERROR WHEN REQUESTING INVALID JOB IDENTIFIER FROM DETAIL REPORT PANEL. | ||||
2004 |
LOWER CASE SEARCH ON ALAAA11 CHANGES TO UPPER CASE ADVANCED FILTERS DO NOT ALLOW LOWERCASE VALUES FROM PANEL. | ||||
2004 |
INCORRECT OUTPUT GENERATED DURING "LOAD DETAILS INTO DB2" WITH CHANGE INDICATOR COLUMN. | ||||
2004 |
INCORRECT OUTPUT POSSIBLE IN DETAIL REPORT WHEN SUBMITTING JCL REPEATEDLY WITHOUT ISPF FRONT END. | ||||
2004 |
LONG RUNNING DETAIL REPORT JOB DURING MERGE PROCESSING DUE TO REPETITIVE INSERT/DELETE ACTIVITY AGAINST SINGLE TABLE. | ||||
2004 |
PROGRAM ALALF1 CAN FORCE A ABENDS0C1 WHEN PARTITIONED TABLESPACEIS ACCESSED IN DROPPED-OBJECT MODE | ||||
2004 |
INCORRECT DDL GENERATED WHEN TARGET TABLE OWNER AND NAME EXCEEDSONE LINE OF INPUT. | ||||
2004 |
SUMMARY REPORT CAN DISPLAY IMPROPERLY FORMATTED TABLE NAME WHEN USING DB2 V8 LONG TABLE NAME. | ||||
2004 |
DETAIL REPORT ERRORS DURING LOG BACKWARD ONLY IN DB2 V8 | ||||
2004 |
INCORRECT SQL GENERATION AS A RESULT OF VARIABLE LENGTH COLUMNS WITH LENGTH=0 | ||||
2004 |
'LOAD DETAILS INTO DB2' MAY CAUSE INCORRECT OUTPUT IN LOAD FILE & CARDS, CAUSING ERRORS IN LOAD PROCESS, AND/OR BAD PERFORMANCE. |
||||
2004 |
SQLCODE519 IN DETAIL REPORT POSSIBLE WHEN MULTIPLE TABLESPACES IN GENERAL REPORT RESULT SET | ||||
2004 |
INCORRECT HANDLING OF 3-CHARACTER SSID USING ALA#LOAD MAY CAUSE BAD CONFIGURATION OR RETURN CODE =4 | ||||
2004 |
ALAA052E ERROR MSG FROM DETAIL REPORT WITH RETURN CODE = 20, RESOURCE CONTENTION | ||||
2004 |
CONTINUOUS MODE FUNCTIONING IMPROPERLY WITH EXTRACT FILE | ||||
2004 |
MSGIEC161I DB2 LOG ANALYSIS TOOL V2.1 ACCESS OF DB2 ACTIVE LOG CAUSES CORRUPTED VSI CHAIN DURING ENQ PROCESSING. | ||||
2004 |
IF DB2 DECIMAL POINT DEFINED AS COMMA, SQL ERRORS OCCUR DURING LOAD PROCESS (DDL CREATE) AND STATIC SQL PROGRAM EXECUTION | ||||
2004 |
ABEND SOC4 IN MODULE ALADTL1 WHILE RUNNING DETAIL REPORT OR BAD DETAIL REPORT OUTPUT | ||||
2004 |
S0C4 ABEND CAN OCCUR DURING GENERAL OR DETAIL REPORTS IF ARCHIVELOGS ARE REQUESTED THAT ARE NOT CONTAINED IN BSDS | ||||
2004 |
S0C4 RC=11 IN ALAGEN1 | ||||
2004 |
USING CONTINUOUS MODE DETAIL REPORT CAN REFLECT INCORRECT VALUES | ||||
2003 |
ABEND A78-18 MAY OCCUR IN DATA SHARING ENVIRONMENT | ||||