|
DB2 Log Analysis Tool Version 3.1.0
|
|||||
| APAR | CLOSE DATE |
PTF(s) | Fixing APAR if PE |
HIPER? | Abstract |
|---|---|---|---|---|---|
2011 |
POSSIBLE S0C4 IN LOG ANALYSIS TOOL WHEN GENERATING SQL FOR A NULL FLOATING POINT COLUMN. | ||||
2011 |
POSSIBLE PROBLEMS WITHIN LOG ANALYSIS TOOL WHEN ARCHLOG1 OR ARCHLOG2 IS WRITTEN TO MULTIPLE VOLUMES BUT THE OTHER IS NOT | ||||
2011 |
PROBLEMS PROCESSING MULTIPLE OBJECTS WITH TABLE VERSIONING INFORMATION IN LOG ANALYSIS. ABEND0C7 IN ALADCNV + X'82A' | ||||
2011 |
ABEND0C4 RC11. TVFILE NOT BEING ALLOCATED IN TWO PHASE JOB DURING CREATION OFLOADFILE WHEN NEEDED. | ||||
2011 |
POSSIBLE S0C4 WHEN CREATING A LOADFILE DUE TO A TABLE WITH ROW REORDER FORMAT HAVING A COLUMN ADDED | ||||
2011 |
LOB/XML ISSUES WHEN LOADING BACK INTO DB2. | ||||
2011 |
U0073 ABEND DURING GENERAL REPORT | ||||
2011 |
ABENDU0013 WHEN USING DROPPED OBJECT MODE AND FIRST ITEM IN RECOVERY IS LOAD REPLACE LOG YES | ||||
2011 |
ALAA073W WARNING WHEN USING LARGE SEGMENTED TABLESPACES | ||||
2011 |
LOG ANALYSIS TOOL MAY NOT REPORT ON CERTAIN OBJECTS AFTER THE DB2 LOG RBA HAS BEEN RESET | ||||
2011 |
ABENDS0C4 DURING ERROR HANDLING OF ERROR IN LOG READING PHASE OF DTL REPORT | ||||
2011 |
PROBLEMS WITH ADVANCED FILTERS IN ONE PHASE WORK FILE MODE WHEN DEALING WITH LARGE VOLUMES OF DATA. ALAA172E U4038 | ||||
2011 |
ABENDSC03 OCCURS WHEN AN ERROR IS ENCOUNTERED DURING FORMATTINGGWHEN USING 1 PHASE WORK FILE MODE. | ||||
2011 |
MSGALAA447E DUE TO SEGMENTED TABLESPACE AND ORDER OF UPDATES. | ||||
2011 |
DB2 LOG ANALYSIS TOOL ADDING SUPPORT FOR LARGE BLOCK INTERFACE (LBI) FOR INLINE IMAGE COPIES | ||||
2011 |
PROBLEMS PROCESSING MULTIPLE OBJECTS WITH NEW TABLE VERSIONING INFORMATION IN LOG ANALYSIS TOOL | ||||
2011 |
ABEND0C4 OR ERROR MSGALAA506E COULD RESULT WHEN THERE ARE MULTIPLE SPANNNED DB2 LOG RECORDS FOR THE SAME PAGE. | ||||
2011 |
DB2 LOG ANALYSIS TOOL FAST APPLY SQL UNABLE TO HANDLE SOME SQL STATEMENTS WITH ONE VERY LARGE COLUMN STRING | ||||
2011 |
DB2 LOG ANALYSIS TOOL FAST APPLY SQL MAY ISSUE A -330 SQL ERROR CODE WHEN HANDLING SQL FOR A UNICODE TABLE WITH XML COLUMNS | ||||
2011 |
WHEN USING ONE PHASE MODE, LOG ANALYSIS MAY ABEND WITH A SC03 IFTHE FILTER SYNTAX IN THE JCL IS NOT CORRECT | ||||
2011 |
MESSAGE ALAA447E WITH PARTITIONED TABLE IN LOG-FORWARD MODE | ||||
2010 |
INCOMPLETE ERROR MESSAGES ISSUED AND ABEND0C4 | ||||
2010 |
ABEND0C4 INCORROUT SPANNED DB2 LOG RECORD FOR DB2 RESTART | ||||
2010 |
LOG ANALYSIS TOOL GETS ABENDS013 REASON=000000E1 WITH LBI IMAGE COPIES | ||||
2010 |
POSSIBLE S0C4 WHEN USING HI-SPEED MODE AND HAVE LARGE UNITS OF WORK OR A UOW THAT HAS A LARGE SPAN FROM START TO FINISH. | ||||
2010 |
S002 ABEND WHILE PROCESSING LOB DATA | ||||
2010 |
POSSIBLE LONG RUNNING JOB WHEN USING ADVANCED FILTERS AND CURRENT ROW | ||||
2010 |
LOADFILE NOT BEING GENERATED PROPERLY AFTER ADDING A COLUMN TO A TABLE. POSSIBLE ABEND0C4. | ||||
2010 |
HIGH CPU OCCURS IN GENERAL REPORT DUE TO ROLLBACK | ||||
2010 |
ABENDU0024 IN DB2 LOG ANALYSIS TOOL MODULE ALADTL1 WHEN DEALING WITH COMPRESSION DICTIONARIES FOR LARGE TABLESPACES | ||||
2010 |
DUPLICATE LRSN CAUSING SORTING SEQUENCES FOR GENERATED DB2 LOADFILE FROM LOG ANALYSIS TOOL | ||||
2010 |
MISC FILTERS AND LOAD LOG YES COMBINATION CAN OMIT LOG RECORDS THAT SHOULD NOT BE OMITTED, ABENDS0C7 CAN OCCUR. | ||||
2010 |
WHEN PROCESSING MANY COMPRESSION DICTIONARIES A S0C4 IS POSSIBLEDUE TO EXHAUSTED STORAGE | ||||
2010 |
TABLE VERSIONING ISSUES WHEN COLUMNS ADDED TO A TABLE IN DB2 9 OR LATER AND A COLUMN WAS PREVIOUSLY VERSIONED | ||||
2010 |
POSSIBLE PROBLEMS WITH ADVANCED FILTERS IN ONE PHASE WORK FILE MODE FOR PARTICULAR TIMEFRAMES | ||||
2010 |
DB2 LOG ANALYSIS MAY DISALLOW A VALID DSN WHEN SPECIFYING THE CONTINUOUS MODE FILE | ||||
2010 |
DB2 LOG ANALYSIS TOOL IS NOT HANDLING A DATE BEYOND THE MAXIMUM ALLOWED CORRECTLY, THIS COULD RESULT IN A S0C7 | ||||
2010 |
POSSIBLE S0C4 OR ALAA479E WHEN LAT FIND NO DATA TO REPORT WHEN USING HISPEED AND SYNCSORT | ||||
2010 |
ABENDSC03 ISSUED IN ALADTL1 WHEN ALAA064E MESSAGE ISSUED IN 1 PHASE MODE | ||||
2010 |
VARGRAPHIC COLUMNS NOT BEING HANDLED PROPERLY IN A UNICODE TABLESPACE THAT IS USING ROW REORDER FORMAT. | ||||
2010 |
IF A FLOATING POINT FIELD IS UPDATED BUT THE DISPLAYABLE FORMAT DOESN'T CHANGE, A POTENTIAL ALAA325E ERROR CAN OCCUR | ||||
2010 |
ALAGEN1 S0C4 WHEN COMPENSATION LOG RECORDS REMOVE ALL ACTIVITY IN A UOW AND THAT UOW IS SPLIT ACROSS MULTIPLE LOGS | ||||
2010 |
MATERIALIZED UNICODE CHAR FIELDS MAY BE MISSING A TRAILING X '0F' CHARACTER | ||||
2010 |
ABENDS0C4 IN ALADTL1 TRACKING REBIND COMMAND | ||||
2010 |
PROBLEMS GENERATING XML DATA WHEN XML SPANS MULTIPLE LOG RECORDS | ||||
2010 |
DB2 LOG ANALYSIS TOOL IS SPECIFYING THE FILE SEQUENCE NUMBER WHEN REQUESTING A CATALOGED IMAGE COPY THAT IS ON TAPE | ||||
2010 |
ABEND0C7 ALAGLOAD+B56 DURING A "LOAD DATA INTO DB2" JOB WHEN THEMODE FILE HAS BEEN OVERLAID AFTER THE "GEN/DTL REPORT" RUN | ||||
2010 |
S0C4 WHEN MULTIPLE DB2 ACTIVE LOGS ARE OVERWRITTEN WHILE DB2 LOGANALYSIS TOOL PROCESSING LOGS IN PARALLEL IN DATASHARING ENVIRON |
||||
2010 |
POSSIBLE SQLCODE -413 RUNNING DB2 LOG ANALYSIS TOOL WHEN COPYPAGESF COLUMN IN SYSCOPY IS OUT OF INTEGER RANGE. | ||||
2010 |
POSSIBLE ABEND0C4 WHEN PROCESSING MORE THAN 27,000 UTILITY RECORDS IN ONE RUN OF LOG ANALYSIS TOOL | ||||
2010 |
POSSIBLE ALAA440E OR ALAA447E WHEN PROCESSING LF AND LOG RECORD WAS READ BUT NOT USED IN GENERAL REPORT. | ||||
2010 |
MESSAGE ALAA521E DYN ALLOC ERR RETURN CODE 0002 REASON 1708 IMAGE COPY NEEDED FOR DICTIONARY NOT AVAILABLE IN HI SPEED MODE |
||||
2010 |
ABEND0C4 RC4 ALASTOR+6C4 R1 BAD IN ERROR HANDLING ROUTINE AFTER GETMAIN FAILURE IN THE DETAILS REPORT PROCESSING | ||||
2010 |
LONG CPU TIMES WITH MUTLIPLE IMAGE COPIES PER TABLESPACE | ||||
2010 |
WHEN LONG RUNNING UOWS HAVE ACTIVITY FROM MULTIPLE OBJECTS IT ISPOSSIBLE TO SKIP THE UOW IN CONTINUOUS MODE | ||||
2010 |
ABEND0C7 DURING DATA COMPRESSION IF LOG BACKWARD PROCESSING IS FORCED ACROSS A REORG. | ||||
2010 |
ADVANCED FILTERS DO NOT WORK PROPERLY WHEN PROCESSING ARCHIVED OUTPUT AND USING MULTIPLE ARCHIVE OUTPUT DATASETS | ||||
2010 |
THE TVFILE DSNAME IN 2 PHASE PROCESSING MUST CONFORM TO INTERNALNAMING STANDARDS OR RESULTS IN RC=8 WITHOUT ANY ERROR MESSAGE | ||||
2010 |
U073 ABEND WHEN USING RESOLVE STARTED UOW AND JOB ENDS BEFORE CURRENT LOG. | ||||
2010 |
POSSIBLE U0031 IN ALADTL2 USING A COMPRESSED TABLESPACE OF TYPE G. | ||||
2010 |
ABEND=SC03 U0000 REASON=00000000 MAY OCCUR WHEN PROCESSING TABLESPACES WITH MORE THAN 999 PARTITIONS | ||||
2010 |
USE OF SYSLGRNX INVALID WITH ANY MEMID > 9 | ||||
2010 |
S0C4 U0000 REASON=00000011 IN ALASBDF AT OFFSET=00002474 | ||||
2010 |
DB2 LOG ANALYSIS TOOL TABLE VERSIONING LOGIC IS INCORRECTLY FLAGGING SOME DELETES AS NEEDING TABLE VERSION 0. | ||||
2010 |
DB2 LOG ANALYSIS TOOL U077 ABEND WITH LOB INSERTS | ||||
2009 |
POSSIBLE S0C4 DURING QUIET TIME PROCESSING WHEN A FILTERED OBJECT CONTAINS A ROLLBACK THAT SPANS MULTIPLE LOGS. | ||||
2009 |
PROCESSING CAN BE SLOW DURING PROGAM ALAGLOAD WITH A HIGH NUMBEROF UOWS | ||||
2009 |
MISSING DETAIL RECORDS USING HIGH SPEED IN NON-DATA SHARING | ||||
2009 |
POSSIBLE S0C4 WHEN USING DB2 LOG ANALYSIS TOOL ADVANCED FILTERS WITH MORE THAN 200K LOG RECORDS TO PROCESS | ||||
2009 |
POSSIBLE S0C4 WHEN USING HISPEED AND THERE ARE MANY UOWS THAT HAVE A LARGE RANGE FROM START UOW TO END UOW | ||||
2009 |
MESSAGE LIBRARY MODIFICATION TO ALAA073 / ALAA549 | ||||
2009 |
DB2 LOG ANALYSIS TOOL PERFORMANCE ENHANCEMENT FOR LARGE UOWS IN HIGH SPEED MODE | ||||
2009 |
LOOP WHEN THE GETMAIL FAILURE NOT HANDLED PROPERLY SOME ERRORS IN SUBTASK NOT PROPERLY PROPAGATED BACK TO MAIN TASK |
||||
2009 |
THE "LOAD DATA INTO DB2" PANEL MAY INCORRECTLY GIVE AN ALAA546E ERROR WHEN THE USER SETS THE "GENERAL REPORT DATA" TO 'N' | ||||
2009 |
DB2 LOG ANALYSIS TOOL CAN ENCOUNTER ALAA440E/U=55 ABEND DUE TO AINCOMPATIBLE PARAMETER IN A SORT EXIT. | ||||
2009 |
THE ' POPULATE PANELS FROM MODE FILE ' FUNCTION DOES NOT WORK ONTHE ' RESOLVE STARTED UOWS ' FIELD | ||||
2009 |
SQL GENERATION ERROR HANDLING NOT PROPERLY HANDLED WHEN USING WORK FILES | ||||
2009 |
LONG RUN TIME AFTER 'START ETV' PROCESSING IN DB2 LOG ANALYSIS TOOL | ||||
2009 |
DB2 LOG ANALYSIS TOOL CONTINUOUS MODE ERROR HANDLING NOT PROPERLY HANDLED WHEN USING WORK FILES | ||||
2009 |
LOG ANALYSIS SOMETIMES ENDS WITH A RC=8 WHEN NO DATA WAS FOUND WHEN IT SHOULD HAVE ENDED WITH A MAX RC=2 OR BYPASSED STEPS | ||||
2009 |
LOG ANALYSIS TOOL 1 PHASE WORK FILE MODE ERRORS WITH STRIPED EXTENDED-FORMAT DATASETS. | ||||
2009 |
USER ABEND 71 CAN OCCUR WITH MASS DELETE ON BASE TABLE W/LOB | ||||
2009 |
LOG ANALYSIS TOOL HI-SPEED MODE CAN ENCOUNTER VARIOUS PROBLEMS WHEN THE LAST LOG RECORD EXTRACTED IS IN A UNIT OF WORK BY | ||||
2009 |
ABENDSS0C4 DURING ERROR HANDLING FOR DYNAMIC ALLOCATION ERROR MESSAGES OCCURING DURING SUBTASKING | ||||
2009 |
S0C4 WHILE PROCESSING DB2 LOG FORMAT PAGE RECORDS THAT ARE SPANNED ACROSS LOGS | ||||
2009 |
ALAA064E WHEN MULTIPLE DB2 ACTIVE LOGS ARE OVERWRITTEN WHILE LATIS PROCESSING LOGS IN PARALLEL | ||||
2009 |
POSSIBLE S0C4 IN ALASUBG DURING CONTINUOUS MODE PROCESSING DUE TO CONTIGUOUS MEMORY CONTENTS | ||||
2009 |
ALAA041E CATFILE LOOKUP ERROR RUNNING DETAIL REPORT THAT INCLUDES AN OBJECT IN RECOVERY THAT SPANS MORE THAN 2 LOGS | ||||
2009 |
LONG RUNNING DB2 LOG ANALYSIS TOOL HIGH SPEED MODE JOB WITH LARGE VOLUME OF EXTFILE (EXTRACT FILES) AND UOW (UNITS OF WORK) |
||||
2009 |
LOG ANALYSIS MAY REPORT A ALAA440E ERROR WHEN USING INCREMENTAL IMAGE COPIES. | ||||
2009 |
THIS ENHANCEMENT WILL INCREASE THE INTERNAL BSDS ARRAY FOR LOGS FROM 2788 ENTRIES TO 9659 ENTRIES | ||||
2009 |
S0C4 OCCURS IN ALASUBG PROCESSING TEMPORARY TABLES . ABENDS0C4 | ||||
2009 |
ROWDATA VALIDATION ERROR IN DROPPED OBJECT MODE | ||||
2009 |
ALLOW RECOVERY OF A DROPPED SIMPLE TABLESPACE INTO A SEGMENTED TABLESPACE IN DB2 V9 FROM OBJECT RESTORE | ||||
2009 |
ABEND0C4 IN LOG ANALYSIS QUIET TIME REPORTING WHEN A UNIT OF WORK IS SPREAD ACROSS TWO LOGS | ||||
2009 |
SUPPORT FOR GENERATED ALWAYS TIMESTAMP | ||||
2009 |
POSSIBLE MISSING UOW(S) IF A SYSTEM RESTART WAS PERFORMED DURINGTHE MIDDLE OF A UOW. ABENDU083 | ||||
2009 |
ABENDU031 ABEND WITH ACCESS TO INLINE IMAGE COPY | ||||
2009 |
XML PARSING ISSUES | ||||
2009 |
POSSIBLE ALAA440E WHILE USING RESOLVE STARTED UOWS AND CONTINUOUS MODE TOGETHER | ||||
2009 |
POSSIBLE IEC020I 001-4 C03 ALAA440E WHEN TABLE VERSIONING WAS DETECTED ON A PREVIOUS RUN, BUT NOT DETECTED ON THE CURRENT RUN |
||||
2009 |
POSSIBLE ERROR ALAA440E IN LOG ANALYSIS TOOL CAUSED BY A DB2 UPDATE RECORD WITH NO DATA CHANGE | ||||
2009 |
IMAGE COPY PROCESSING ISSUES DEALING WITH READS FOR DICTIONARY | ||||
2009 |
ABENDS0C4 WHEN A URID INVOLVING A FILTERED OBJECT IS ROLLED BACK BUT THE ABORT UR RECORD IS ON A SUBSEQUENT LOG | ||||
2009 |
A ABEND0C4 WILL OCCUR IF AN INVALID TARGET SSID VALUE IS USED IN THE "LOAD DATA INTO DB2" PANEL DURING A GENERAL REPORT RUN. |
||||
2009 |
USING WORK FILES IN ONE PHASE MODE WITH " LOAD OPTIONS " SELECTED MAY LEAD TO EMPTY ROWS OF DATA IN THE LOAD TABLES | ||||
2009 |
USING WORK FILES IN ONE PHASE MODE WITH " LOAD OPTIONS " SELECTED MAY LEAD TO ABENDS0C4 | ||||
2009 |
A MASS DELETE COULD BE REPORTED FOR TABLES WITH DCC ON UNDER CERTAIN CIRCUMSTANCES BY DB2 LOG ANALYSIS TOOL | ||||
2009 |
LOB HANDLING MAY FAIL WITHIN LOAD OPTION WITH NULLS OR EMPTY STRINGS | ||||
2009 |
ABEND0C4 IN ALASTOR DUE TO HIGH NON-ZERO ORDER WORD IN REGISTER 14 | ||||
2009 |
FAST APPLY SQL CAN NOT HANDLE AN EMPTY STRING ON A LOB COLUMN | ||||
2009 |
ABEND U077 USING LOBS IN PARTITIONED TABLESPACE DB2 LOG ANALYSISTOOL PROCESSING | ||||
2009 |
POSSIBLE MISSING ACTIVITY WHEN PERTINENT START UR RECORD FOLLOWSAN ORPHAN END UR RECORD IN LOG | ||||
2009 |
A ROLLBACK WITHOUT A CORRESPONDING ABORT CAN CAUSE A S0C4 DURINGA QUIET TIME REPORT IN DB2 LOG ANALYSIS TOOL | ||||
2009 |
FAST APPLY SQL DOES NOT PROPERLY HANDLE LOBS FOR UNICODE TABLES. | ||||
2009 |
ABEND0C4 WHILE TRYING TO HANDLE CALL ATTACH FACILITY ERRORS. | ||||
2009 |
ALAA440E WHEN USING ONLY MISC FILTERS ON NON DCC TABLES WHEN IN LOG FORWARD MODE | ||||
2009 |
LOB AS EMPTY STRING CAN CAUSE U077 | ||||
2009 |
ABENDU078 ABEND WITH DCC AND LONG DB2 LOG RECORDS ON UPDATES | ||||
2009 |
POSSIBLE 0C4 IN LOG ANALYSIS DURING MERGE WHILE USING 64 BIT ONEPHASE MODE. | ||||
2009 |
REDUCE CHANCE OF ALAA486E MESSAGE | ||||
2009 |
ABENDS001 RC05 WHEN USING THE COMBINATION OF CONTINUOUS MODE , WORK FILE , AND HI SPEED MODE | ||||
2009 |
POSSIBLE ALAA447E IN LOG ANALYSIS WHEN RECOVERYSITE IMAGE COPY IS TAKEN SEPARATELY FROM THE LOCALSITE IMAGE COPY | ||||
2009 |
EDITPROC FAILURE IN DB2 V9 IF RRF PRESENT | ||||
2009 |
UPDATED SUPPORT FOR THE CLEAR KEY ENCRYPTION EDITPROC FROM THE IBM DATA ENCRYPTION FOR IMS AND DB2 DATABASES. | ||||
2009 |
POSSIBLE USER 78 ABEND OR ALAA447E IN DETAILS REPORT, DUE TO SKIPPING CERTAIN LOG RECORDS IN THE GENERAL REPORT | ||||
2009 |
POSSIBLE ALAA411E IN DETAILS REPORT WHEN A MASS DELETE WAS DONE ON ANY TABLE WITHIN A TABLESPACE THAT IS BEING REPORTED. | ||||
2009 |
QUIET TIME REPORTING MAY MISS ACTIVITY IF IN-FLIGHT | ||||
2009 |
FAST APPLY SQL SQLCODE20186 FOR SUBSEQUENT MULTI-ROW INSERTS THAT CONTAIN MORE ROWS THAN THE VERY FIRST ONE. | ||||
2009 |
MESSAGE ALAA011E OCCURS DURING DETAIL REPORT PROCESSING | ||||
2009 |
CHOOSING TO SPECIFY THE ARCHIVE OUTPUT IN ONE PHASE MODE RESULTSIN THE DATA NOT BEING ARCHIVED | ||||
2009 |
SELECTING 'Y' ON THE "CURRENT ROW BY KEY" MAY LEAD TO S0C4, -311 OR -804 SQLCODES | ||||
2009 |
ABENDSOC4 IN DB2 LOG ANALYSIS GENERAL REPORT WHEN TOO MANY LOAD REPLACE UTILITIES ARE WITHIN THE TIMEFRAME OF THE FILTERS |
||||
2009 |
ABENDS0C4 OR SQLCODE310 IF USE THE CURRENT ROW BY KEY OPTION AND HAVE A LARGE PRECISION DECIMAL COLUMN IN THE KEY OF TABLE | ||||
2009 |
POSSIBLE VSAM RET CODE=20 ON ROWDATA WHEN THE ROWDATA FILE IS MANUALLY BUILT | ||||
2009 |
LOB/XML, AND THEIR SUPPORT DATA TYPES, HAVE HANDLING ERRORS | ||||
2009 |
CHANGING JOB IDENTIFIER IN LOAD STEP TO DIFFERENT FROM GENERAL REPORT FOR COMBINED JOB, JCLERRORS OR ABEND IN ISPF PANELS CAN |
||||
2009 |
THE GENERAL REPORT ISPF PANEL INCORRECTLY ALLOWS THE USER TO SPECIFY RESOLVE STARTED UOWS WHEN RUNNING A QUIET TIME REPORT | ||||
2009 |
A REORG OCCURRED AFTER REPORTING PERIOD WAS CAUSING TABLE VERSIONING LOGIC TABLE VERSIONING PROCESSING MORE COMPLICATED | ||||
2009 |
FAST APPLY SQL INCORRECTLY REPORTS A WARNING OR AN ERROR FOR MULTIPLE ROWS BEING AFFECTED WHEN AN SQL STATEMENT PREPARED | ||||
2009 |
BYPASSING REPORTS DURING GENERAL REPORT: DB2 LOGS INS/DEL ON UPDATE, DB2 LAT NOT COMBINING RECORDS INTO A SINGLE UPDATE. | ||||
2009 |
POSSIBLE ALAA447E WHEN MULTIPLE TABLES ARE BEING REPORTED AND ATLEAST ONE HAS IS FLAGGED AS BEING VERSIONED | ||||
2009 |
CHARACTER AND GRAPHIC STRINGS MAY BE IMPROPERLY TRANSLATED IN FAST APPLY SQL | ||||
2009 |
POSSIBLE ALAA107E ON PARTITION TABLESPACES THAT HAVE BOTH COMPRESSION AND DATA CAPTURE CHANGES TURNED ON. | ||||
2009 |
ROLL UP | ||||
2008 |
ALAA031E MSG GENERATING PIT RECOVERY JCL WITH DB2 OBJECT RESTORE | ||||
2008 |
POSSIBLE 0C4 DURING SQL CREATION FOR VERY WIDE ROWS THAT CONTAINSEVERAL DBCS COLUMNS AND WHERE CLAUSE BY KEY IS 'Y'. | ||||
2008 |
DISTRIBUTED TYPE FILTERS (END USER, WORKSTATION, ETC) MAY PROVIDE INCORRECT RESULTS WHEN USED IN COMBINATION WITH OTHER |
||||
2008 |
FAST APPLY SQL PARSES THE CHARACTERS X'0E' AND X'0F' AS SHIFT-OUT AND SHIFT-IN. THE DATA CORRECTLY | ||||
2008 |
POSSIBLE ALAA068E ON ROWDATA IF ATTEMPTING TO LOAD INTO DB2 WHENONLY A GENERAL REPORT RUN WAS SELECTED. | ||||
2008 |
POSSIBLE ALAA070W WHEN UNIT OF RECOVERY IS SPLIT ACROSS LOGS, WITH ACTIVITY IN FIRST LOG AND ONLY COMMIT/ABORT IN SECOND LOG. |
||||
2008 |
POSSIBLE ALAA440E WHEN DB2 UPDATE LOG RECORDS ENCOUNTERED HAVE ZERO LENGTH UPDATES | ||||
2008 |
MISSING LOG RECORDS WHICH EXIST ONLY IN ACTIVE LOGS | ||||
2008 |
S0C7 DURING DECOMPRESSION WITH MULTI-PARTITION IMAGE COPIES | ||||
2008 |
ABENDS0C4 WHILE PROCESSING GENERAL REPORT LOGS ON 32K PAGESIZES | ||||
2008 |
MISSING EXTFILE DD IN DB2 LOG ANALYSIS TOOL LOAD-GENERATED JCL CAN ALSO APPEAR AS S0C4 | ||||
2008 |
POSSIBLE DC2 ABEND DURING PROGRAM TERMINATION DUE TO AN ATTEMPT TO FREE AN INVALID ADDRESS | ||||
2008 |
FAST APPLY SQL MAY SHUT DOWN WITH A USER ABEND: MESSAGE "IN HPCB CONTROL BLOCK, THE EYE CATCHER IS DAMAGED" | ||||
2008 |
ADDS CAPABILITY TO REPORT ON COMPLETE UNITS OF WORK THAT START WITHIN AN ANALYSIS TIME FRAME BUT END OUTSIDE OF THE TIME FRAME. |
||||
2008 |
POSSIBLE S0C4 DURING DATA DECOMPRESSION DUE TO SYSOBD PAGES | ||||
2008 |
FAST APPLY SQL DOES NOT PROPERLY PARSE REAL OR FLOAT COLUMNS WHEN A COMMA IS THE DEFAULT DECIMAL POINT FOR THE DB2 SUBSYSTEM |
||||
2008 |
ABENDS0C4 WHEN USING LOG ANALYSIS WITH A TABLE THAT CONTAINS MORE THAN 580 COLUMNS | ||||
2008 |
DB2 LOG ANALYSIS NOT HANDLING GRAPHIC COLUMNS CORRECTLY DURING CURRENT ROW BY KEY PROCESSING WHICH COULD LEAD TO UNPREDICTABLE |
||||
2008 |
ALAA440E WHILE PROCESSING VARIATION TYPE 3 LOG RECORD | ||||
2008 |
POSSIBLE VSAM RET CODE=20 ON ROWDATA | ||||
2008 |
ADD AN INFORMATIONAL MESSAGE TO JOB LOG WHEN A RECOVERY POINT ISENCOUNTERED | ||||
2008 |
ISSUES FOUND WHILE PROCESSING MASS DELETES AND / OR LOAD UTILITIES PARTICULARLY WHEN MULTIPLE INSTANCES WERE FOUND IN ONE |
||||
2008 |
POSSIBLE USER 0078 ABEND DUE TO MISSED REORG / LOAD REPLACE DURING INTERNAL PROCESSING TO DETERMINE THE LOG READING MODE | ||||
2008 |
DATA HANDLED INCORRECTLY BY FAS IF TWO SIMILAR SQL STATEMENTS RUN USING DIFFERENT CODE SETS FOR ONE COLUMN IN UNICODE TABLE | ||||
2008 |
A -811 SQL ERROR WILL OCCUR IN FAST APPLY SQL WHILE PROCESSING ANY TABLE BELONGING TO A TABLESPACE THAT IS NOT UNIQUELY NAMED |
||||
2008 |
IN SOME CASES, A CHARACTER CAN BE WRITTEN INTO THE 73RD COLUMN OF THE SQLOUT PREVENTING THAT CHARACTER FROM BEING PROCESSED | ||||
2008 |
THIS APAR WILL CHANGE THE WAY LAT HANDLES STRING LENGTHS GREATERTHAN 40 BYTES IN A WHERE CLAUSE. | ||||
2008 |
POSSIBLE SQLCODE OF -302 WHEN EXECUTING A SQL STATEMENT WITH A SUBSTR FUNCTION ON A UNICODE COLUMN. | ||||
2008 |
FAS RECEIVES AN SQLCODE518 WHEN PROCESSING A DIVERSE SET OF SQL COMMANDS RUN IN NFM | ||||
2008 |
FAILURE HANDLING ALTER ADD COLUMN WITH DB2 V9 VARIABLE LENGTH TABLE | ||||
2008 |
ERROR MSG ALAA460E WITH NO OTHER ERROR INDICATION | ||||
2008 |
WHEN SPECIFYING LOGS THAT HAVE DSNS OF 44 CHARACTERS, LOG ANALYSIS MAY TERMINATE BEFORE PROCESSING ALL THE SPECIFIED LOGS. |
||||
2008 |
UTF-16 HEXADECIMAL STRINGS WILL NOW BE CREATED WITH THE UX'....'STRINGS INSTEAD OF X'....' STRINGS | ||||
2008 |
SC03 ABEND AND IEC999I ERROR MESSAGE. | ||||
2008 |
MATERIALIZED GRAPHIC FIELDS MAY HAVE AN INCORRECT TRAILING X'0F'CHARACTER. | ||||
2008 |
FAST APPLY SQL DOES NOT PROPERLY HANDLE HEXADECIMAL STRINGS WHENWORKING WITH UNICODE TABLES | ||||
2008 |
INVALID SQL CAN BE GENERATED WHEN THE LENGTH OF THE COLUMN NAME EXCEEDS 18 BYTES AND THE LENGTH OF THE DATA IS LESS THAN 40 BYTE |
||||
2008 |
ALAA440 MSG WHEN LOAD LOG YES PRESENT | ||||
2008 |
MISSING RECORDS MAY OCCUR IN HI SPEED MODE IF URLRTIME VALUES NOT IN TIME ORDER | ||||
2008 |
0C4, MULTIPLE LOAD STATEMENTS PER TABLE, AND MULTIPLE CREATE TABLE STATEMENTS PER TABLE USING DB2 LOG ANALYSIS OPTION TO LOAD |
||||
2008 |
ALLOW PIT RECOVERY OF DROPPED TABLESPACE AFTER LOAD LOG YES UTILITY HAS BEEN RUN | ||||
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 |
SQLCODE311 USING DB2 LOG ANALYSIS IN DB2 V8 CM, SPECIFICALLY IN ALAESQL, ALAARC1, AND QUIET TIME PROCESSING IN ALAGEN1. | ||||
2008 |
THE GENERAL REPORT ISPF PANEL INCORRECTLY ALLOWS THE USER TO SPECIFY A QUIET TIME REPORT ALONG WITH A LOAD, ABENDS0C7 | ||||
2008 |
IF THE GMT OFFSET INCLUDES A PARTIAL HOUR AMOUNT, IT IS POSSIBLETO GET NO DATA BACK FROM DB2 LOG ANALYSIS TOOL | ||||
2008 |
S0C4 IN ISPF PANELS WHEN USING FILTER FILES | ||||
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 |
DYNAMIC SQL PROCESSING USING FAST APPLY USES TOO MUCH MEMORY WHEN A JOB IS RE-RUN WITH THE RESTART OPTION | ||||
2008 |
REGISTER 0 AND REGISTER 8 HAVE A NON-ZERO HIGH WORD DURING 64 BITPROCESSING | ||||
2008 |
POSSIBLE MISSING RECORDS WHEN UR SPANS LOGS | ||||
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 |
RC16 WITHOUT AN ERROR MESSAGE IN ALADTL4 IS POSSIBLE, IF "WHERE CLAUSE BY KEY" IS CHOSEN AND A TABLE IS PRESENT THAT HAS | ||||
2008 |
ABENDS0C4 RC=10 IN ALASUBG AT OFFSET=1CD4 | ||||
2008 |
DB2 LOG ANALAYSIS CAN POTENTIALLY RECEIVE AN 0C4 IN MODULE ALASUBG DUE TO NOT HANDLING A STORAGE REQUEST FAILURE. | ||||
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 |
ALAA440E OR ALAA479E WHEN THE END DATE AND END TIME HAS BEEN MANUALLY CHANGED IN THE JCL TO EQUAL THE BEGN DATE AND BEGIN | ||||
2008 |
POSSIBLE ABENDS0C4 DURING LOG SELECTION PROCESSING WHEN USING CONTINUOUS MODE IN A DATA SHARING ENVIRONMENT | ||||
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 |
ERROR MSG OR INCORRECT OUTPUT USING HIGH SPEED MODE WITH DROPPEDOBJECTS | ||||
2008 |
ROLLUP APAR FOR LOG ANALYSIS V3.1 | ||||