IBM Support

Fixed APAR list for interim fixes of IBM InfoSphere Optim Performance Manager

Product Documentation


Abstract

This document lists APARs and other key customer issues that are fixed in different interim fixes for IBM® InfoSphere® Optim™ Performance Manager V5.3.1, V5.3, V5.2, and V5.1.1.1.

Content

See the list of APARs for the following releases of InfoSphere Optim Performance Manager:

  • Version 5.3.1
  • Version 5.3
  • Version 5.2
  • Version 5.1.1.1

    Tip: For details about a specific APAR, copy and then search the APAR number in the InfoSphere Optim Performance Manager support portal.

     

    InfoSphere Optim Performance Manager Version 5.3.1

     

    1. Interim fix 8377 for InfoSphere Optim Performance Manager Version 5.3.1

     

    2. Interim fix 8391 for InfoSphere Optim Performance Manager Version 5.3.1

     

    3. Interim fix 8402 for InfoSphere Optim Performance Manager Version 5.3.1

     

    4. Interim fix 8409 for InfoSphere Optim Performance Manager Version 5.3.1

     

      • IT04491 - OPM - THE PARSER OF THE MESSAGE THROWS JSON EXCEPTION ORG.APACHE.COMMONS.JSON.JSONEXCEPTION
      • IT04677 - OPM - RUNNING PERFORMANCE OVERVIEW REPORT FOR DB2 9.5 DPF INSTANCE CAN CAUSE 'NON-NUMERICAL DATA' ERROR
      • IT05304 - OPTIM PERFORMANCE MANAGER - EXECSQLANDGENALERTS() EXPECTED TOKENS ERROR MAY INCLUDE: ")".. SQLCODE=-104, SQLSTATE=42601
      • IT04917 - OPTIM PERFORMANCE MANAGER - NOT ABLE TO CREATE REPORT IN INTERNET EXPLORER 8
      • IT05058 - OPM - METRICS VALUES IN THE DATABASE GLOBAL MEMORY (GRID TABLE) OF THE "MEMORY DASHBOARD" ARE NOT DISPLAYED CORRECTLY
      • IT05231 - OPM - THE MONITORED DATA COULD NOT BE PROCESSED WITHIN 180000 MILLISECONDS BY THE STATEMENT TEXT COLLECTOR
      • IT05415 - OPTIM PERFORMANCE MANAGER - LOCKS ARE BEING HELD BY OPM WHEN CREATING REPORTS WITH REPORT SCHEDULER
      • IT05735 - OPTIM PERFORMANCE MANAGER - PERFORMANCE OVERVIEW REPORT SHOWING 0% HIT RATIO IN TABLESPACE SECTION
      • IT05736 - OPTIM PERFORMANCE MANAGER - TIME FORMAT CORRECTION IN TOP PACKAGE REPORT TO MAINTAIN CONSISTENCY ACROSS REPORTS
      • IT05941 - OPTIM PERFORMANCE MANAGER - SCHEDULE REPORTS FAIL WHEN BROWSER LANGUAGE IS SET TO JAPANESE
      • IT03993 - OPTIM PERFORMANCE MANAGER - BLANK SCREEN WHEN OPMSTARTSERVICE.BAT AND RESPOSITORY SERVER WINDOWS SERVICE HAS AN INCORRECT PASSWORD
      • IT04350 - OPTIM PERFORMANCE MANAGER - NO ALERTS DETAILS ARE SHOWN IN ALERT DETAIL REPORT
      • IT04781 - OPTIM PERFORMANCE MANAGER - ALERT DETAIL FOR THE ALERTS DOES NOT SHOW DETAILS
      • IT05910 - OPM - GET JAPANESE REPORT EVEN IF SETTING ENGLISH AS REPORT LOCALE IN JAPANESE WEB UI WHEN THE REPORT IS GENERATED IMMEDIATELY
      • IT05985 - OPM REPORT SCHEDULING FAILS WITH AND INVALID CHARACTER ERROR 'SQLCODE=-7, SQLSTATE=42601
      • IT06057 - OPM REPORTS CONNECTIONS - SNAPSHOT MODE ISSUES DB2 SQLCODE 180 WHEN COLUMN CPU TIME IS SORTED
      • IT06235 - IN LOCKING DASHBOARD, THE ALERT NAME ARE GARBLED IN WEB UI UNDER JAPANESE
      • IT06220 - ALERT TYPE "OPERATIONAL ALERT" IS GARBLED UNDER BOTH JAPANESE AND ENGLISH BROWSER
      • IT06657 - RUN PERFORMANCE REPORTS FOR A DATABASE, NOTHING IS POPPED-UP IN THE BROWSER
      • IT06655 - OPM - PARTIAL ERROR MESSAGE CDPMA5127E IS GARBLED IN OPM CONSOLE UNDER JAPANESE BROWSER
      • IT07012 - OPTIM PERFORMANCE MANAGER - VISUAL EXPLAIN FAILS FOR TOP INDIVIDUAL EXECUTIONS WITH UNQUALIFIED TABLE REFERENCES
      • IT07013 - OPTIM PERFORMANCE MANAGER - SQL STATEMENT TEXT IS TRUNCATED AT 1024 CHARACTERS FOR TOP INDIVIDUAL EXECUTIONS
      • IT06872 - OPTIM PERFORMANCE MANAGER - ALERT DATA IN THE REPOSITORY TABLES DOES NOT GET PURGED
      • IT05737 - OPM - AFTER LOGGING ENHANCEMENTS, OPM STARTED TO SHOW FATAL ERRORS IN DSSERVER.LOG FILE
      • IT06405 - OPM - USES DEFAULT VALUE OF 0 FOR MEMBER ID IN A NON-PARTITIONED SYSTEM EVEN THOUGH USER SET NODE TO NON-ZERO VALUE
      • IT07020 - OPM - SHOWS db2jcc_license_cu.jar ERROR in opminstall.log FILE DURING OPM INSTALLATION
      • IT07758 - OPM - WTI CHECKPURESCALE FAILURE. SHOWED UP ON LOGS OVER AND OVER AGAIN
      • IT07471 - OPM - UNABLE TO CREATE/UPDATE STORAGE SPACE NAME DURING ADVANCE INSTALLATION
      •  

    • 5. Interim fix 8440 for InfoSphere Optim Performance Manager Version 5.3.1

       

      • IT08279 - OPM - TO ENSURE ALL OPM EVENT MONITORS TABLES IRRESPECTIVE OF ANY NAME IS DELETED
      • IT06116 - OPTIM PERFORMANCE MANAGER - CHANGE THE OPM EVM CLEANUP CODE TO DISABLE AND DROP EVENT MONITORS THAT DIFFER ONLY BY "@" OR "_".
      • IT06756 - OPM - LONG TIME (5MIN OR MORE) AT "CHOOSE PARAMETERS FOR PREDEFINED REPORT" OF TOP SQL PACKAGE REPORT IN JAPANESE BROWSER
      • IT07537 - OPM - DUPLICATE ALERTS FROM DATABASE PERFORMANCE MONITORING
      • IT08279 - OPM EVENT MONITORS ON SELF MONITORED REPOSITORY DB ARE NOT CLEANEDUP WHEN OPM IS STOPPED
      • IT07158 - OPTIM PERFORMANCE MANAGER - DB2 UTILITIES LIKE DB2UPDV*, DB2 CREATE DATABASE ETC CAN CRASH IF DTRC IS INSTALLED
      • IT07073 - OPTIM PERFORMANCE MANAGER - GETTING DIFFERENT RETURN CODE WHEN RUNNING A SHELL SCRIPT JOB
      • IT07849 - OPTIM PERFORMANCE MANAGER - USER WITH CAN_MONITOR_IN_REAL TIME PRIVILEGE IS NOT ABLE TO DOWNLOAD REPORT
      • IT07838 - OPTIM PERFORMANCE MANAGER - IF THERE ARE MANY UNQIUE PATH FOR SQLS, OPM TAKES LONG TIME TO PROCESS THE DATA
      • IT06711 - OPTIM PERFORMANCE MANAGER - UDA,IF THERE IS A SPACE(BLANK) AFTER THE SQL LINE, CRITICAL/WARNING ALERT MIGHT NOT GET GENERATED
      • IT07024 - JAPANESE CHARS ARE DISPLAYED AS GARBED WHEN VIEWING LOG FILES WITH WEB CONSOLE
      • IT09489 - OPM TRIES TO AUTHENTICATE WITH PUREAPPLICATION SYSTEMS AND DOES NOT RETURN ANY RESULTS

      6. Interim fix 8448 for InfoSphere Optim Performance Manager Version 5.3.1

       

      • IT12582 - OPTIM PERFORMANCE MANAGER - CLI OR .NET APPLICATIONS USING THE DATA TOOLS RUNTIME CLIENT DO NOT TERMINATE GRACEFULLY
      • IT10958 - OPTIM PERFORMANCE MANAGER - SHOWS SQLCODE=-204 WHEN MONITORING Z/OS DATABASES

      7. Interim fix 8494 for InfoSphere Optim Performance Manager Version 5.3.1

       

      • IT10328 - OPTIM PERFORMANCE MANAGER - SHOWS SQLCODE=-840 WHEN MONITORING WLM
      • IT12415 - OPTIM PERFORMANCE MANAGER - SQL COMING FROM OPM THAT SHOULD NEVER BE EXECUTED AGAINST A DB2 Z/OS SYSTEM IS CAUSING DELAY IN DB2 SHUTDOWN
      • IT12755 - OPTIM PERFORMANCE MANAGER - SHOWING HTTP ERROR ACESSING: UNDEFINED ERROR WHEN RUNNING WORKLOAD MANAGER SERVICE SUBCLASS REPORT
      • 82114 - OPTIM PERFORMANCE MANAGER - (internal defect) QWT integration regression in Interim fix 8448
       

      InfoSphere Optim Performance Manager Version 5.3

       

      1. Interim fix 7320 for InfoSphere Optim Performance Manager Version 5.3

       

      • IC96748 - AGGREGATION TO LEVEL 4 FOR THE TABLE FACT_EXECUTING_STATEMENTS_4 MAY FAIL WITH SQLCODE -20408.
      • IC96579 - SHUTDOWN OF THE MONITORED INSTANCE IN OPM RS SERVER MAY BE BLOCKED DUE TO HANGING "POOL-#-THREAD-#" THREAD
      • IC98672 - ON DATABASE PAGE ALL DATABASES MONITORING STATUS SHOWS "LOADING"
      • IC96787 - DB2 CRASHES WHEN OPM RUNS AND CALLS DB2 PD_GET_DIAG_HIST TABLE FUNCTION
      • IC95169 - JCC EXCEPTION ERRORS CAUSED IN UOW EVENT MONITOR MAY AFFECT EI TRANSACTION DATA COLLECTION.
      • IC92877 - OPM MONITORING COLLECTION HALTS AFTER A MESSAGE STATING SUCCESSFULLY RESTARTED
      • IC94591 - OPM - INCORRECT TIME VALUE SORTING ON TOP DYNAMIC SQL REPORT WHICH IS USED WHEN MONITORING DATABASES IN SNAPSHOT (LESS THAN V9.7) MODE
      • IC93234 - OPTIM PERFORMANCE MANAGER - REPORTS HANGS IN SOME CASES, LIKE SELECTING ALL FOR NUMBER OF CONNECTIONS, ON IE9R
       

      2. Interim fix 7334 for InfoSphere Optim Performance Manager Version 5.3

       

      • IC92957 - PROVIDED FIX TO CONFIGURE log4j TO WORK CORRECTLY AS SOON AS THE COMMAND LINE UTILITY STARTS FOR REPORTS.
      • IC93873 - WHEN CREATING REPORTS USING COMMAND LINE UTILITY, A LOG FILE UNDER FOLDER <CLU>/BIRT/CONFIGURATION WOULD BE CREATED CONTAINING MESSAGE "java.lang.ClassCastException".
      • IC93881 - OPTIM PERFORMANCE MANAGER - PROVIDE AN OPTION TO START PESTART AS NOHUP
      • IC95607 - OPTIM PERFORMANCE MANAGER CAPABILITY TO ALLOW AUTOMATIC LOADING OF PDQ.PROPERTIES TO ELIMINATE CONFIGURATION ON EACH CLIENT
      • IC95758 - IN SOME OF THE PANELS IN THE 5.2 VERSION OF THE PE LEGACY CLIENT INTEGER VALUES ARE DISPLAYED AS DECIMALS WITH 20 ZERO PRECISION.
      • IC95864 - OPTIM PERFORMANCE MANAGER CONNECTION AUTHORIZATION FAILURE WITH ERRORCODE=-4214 WHEN EDITING MONITORED DATABASE IN WEB UI
      • IC96017 - OPTIM PERFORMANCE MANAGER - HEALTH AND PERFORMANCE ALERTS DO NOT GET REFRESHED WHEN SWITCHING FROM HISTORICAL TO REAL-TIME MODE
      • IC96029 - OPTIM PERFORMANCE MANAGER - LOCK WAIT WARNING ALERTS ARE STILL BEING GENERATED AFTER UNCONFIGURING THE LOCK WAIT WARNING ALERT
      • IC96160 - OPTIM PERFORMANCE MANAGER - IN SQL REPORTS SQL TEXT IS TRUNCATED BEYOND 15000 CHARACTERS WHEN THE PERFDB IS 9.7
      • IC96379 - IOPM - TEST CONNECTION TO THE MONITORED DATABASE MAY FAIL WITH COM.IBM.DB2.JCC.AM.SQLINVALIDAUTHORIZATIONSPECEXCEPTION ERROR
      • IC96497 - IOPM - JAVA.SQL.BATCHUPDATEEXCEPTION: SYNTAX ERROR: ENCOUNTERED "BUFFERPOOL" ERROR MAY BE TRACED IN DS_SYSTEM.0 AND DSSERVER.LOG
      • IC96857 - OPTIM PERFORMANCE MANAGER ERROR SQL STATE = 23503, ERROR CODE = 20000 (A VIOLATION OF FOREIGN KEY CONSTRAINT) IN DSSERVER.LOG
      • IC97278 - OPTIM PERFORMANCE MANAGER - WEB UI INFLIGHT DASHBOARD SHOWS ALL MEMBERS IN THE PULL DOWN LIST INSTEAD OF SUB SET.
      • PM93867 - CUSTOMERS WHO ARE USING CLI BASED CLIENTS TO CONNECT TO DB2 DATA SERVERS IN CONJUNCTION WITH OPM'S EI MONITORING FEATURE MIGHT OBSERVE AN OPERATIONAL ALERT IN DB2PESRV.LOG THAT REFERS TO MEMORY CAP.
      • IC98214 - OPTIM PERFORMANCE MANAGER - UI SQL DASHBOARD COLUMNS AFFECTING TIME FILTERS DOES NOT DISPLAY CORRECT VALUES
      • IC99611 - OPTIM PERFORMANCE MANAGER - IF THE JOB SCRIPT CONTAINS '{' THIS CHARACTER, IT WILL NOT RUN AND USER COULD SEE AN ERROR LIKE JSONEException: EXPECTING EITHER ',' or '}' ON LINE 1, COLUMN 132" IN THE LOG
      • IC97621 - WHEN CUSTOMER GENERATES THE REPORTS BY COMMAND LINE, MANY 'BIRT_XLS_XXXXXXXX' FILES ARE GENERATED IN THE '/TMP' DIR

      3. Interim fix 7356 for InfoSphere Optim Performance Manager Version 5.3

       

      • IC98083 - OPTIM PERFORMANCE MANAGER - FORCING SHUTDOWN OF STATEMENT TRACKER THREAD MAY LEAD TO LOCK IN SYSIBM.SYSPLAN TABLE
      • IC98672 - OPTIM PERFORMANCE MANAGER - ON DATABASE PAGE ALL DATABASES MONITORING STATUS SHOWS LOADING
      • IC96939 - IOPM - CONFIGURING A DATABASE FOR MONITORING MAY FAIL WITH UNABLE TO CREATE TABLE: DB2PM_##.EV_LOCK, SQLCODE=-204 ,SQLSTATE=42704
      • IC98653 - OPTIM PERFORMANCE MANAGER - ADD SUPPORT TO DELETE OPERATIONAL ALERTS ISSUED AGAINST REPOSITORY DATABASE AND REPOSITORY SERVER
      • IC99340 - OPTIM PERFORMANCE MANAGER - PARAMETER MARKER INVALID ERROR FILLED IN DSSERVER.LOG FROM DB2LUWMESSAGESNAPSHOTSERVICE WHEN MONITORING 9.5 DB
      • IC99358 - OPTIM PERFORMANCE MANAGER - REPOSITORY SERVER TERMINATES ABRUPTLY BECAUSE IT ENCOUNTERED A NULL POINTER EXCEPTION
      • IC99611 - OPTIM PERFORMANCE MANAGER - LEAVES LOST PROCESSES AND IT SHOWS [ERR] ORG.APACHE.COMMONS.JSON.JSONEXCEPTION ERROR IN LOG FILE
      • IC99391 - OPTIM PERFORMANCE MANAGER - WEB-BASED WORKLOAD QUERY TUNING WITH CLIENT AUTHENTICATION RETURNS ERROR - LIKE CAN_MANAGE_JOB PRIVILEGE PROBLEM
      • IC99420 - OPTIM PERFORMANCE MANAGER - WEB CONSOLE DOES NOT OPEN ANY DASHBOARDS, SHOWS BLANK PAGE
      • IC99427 - OPTIM PERFORMANCE MANAGER - WEB CONSOLE - DATABASE DASHBOARD SHOWS 'NOT CONFIGURED'
      • IC99452 - OPTIM PERFORMANCE MANAGER - AGGREGATION TO LEVEL4 FOR SOME OF THE FACT* TABLES CAN FAIL"
      • IC99394 - OPTIM PERFORMANCE MANAGER - THE DISK SPACE FOR OPM REPOSITORY DB CONTINUES TO GROW"
      • IC99636 - OPTIM PERFORMANCE MANAGER - EXCEPTION IN PERFORMANCE OVERVIEW REPORT WHEN RENDERING DATA FOR A SNAPSHOT DPF DATABASE"
      • IC94711 - EI CLIENT DRIVER SHOULD STOP COLLECTING AND SENDING MONITORING INFO IF OPM EI CONTROLLER GOES DOWN.

      4. Interim fix 7370 for InfoSphere Optim Performance Manager Version 5.3

       

      • IT00727 - OPTIM PERFORMANCE MANAGER - COORDINATOR ACTIVITIES LIFETIME PEAK IN WLM SUBCLASS REPORT DOES NOT SHOW CORRECT VALUE

      5. Interim fix 7384 for InfoSphere Optim Performance Manager Version 5.3

       

      • IT02040 - OPM SOME COLUMNS DO NOT DISPLAY THE WHOLE DATA IN THE EXPORTED PDF FOR 'TABLE USAGE REPORT' AND 'TOP SQL PACKAGE REPORT'
      • IT02121 - OPM SOME COLUMNS ARE DISPLAYED OUT OF ALIGNMENT IN DATABASE CONFIGURATION REPORT (WEB PAGE)
      • IT02617 - OPM DISPLAY ISSUE FOR MAXIMUM INDOUBT TRANSACTIONS, LOG TO BE READ FOR RECOVERY (MB), SORT OVERFLOWS IN PERFORMANCE OVERVIEW REPORT
      • IT03405 - OPM 'SORT PROCESSING TIME' IS HIGHER THAN ACTUAL VALUE IN TOP SQL PACKAGE REPORT
      • IT04469 - OPM - ADDED JCC DRIVER VERSION 3.68.61 (RS backend) TO SUPPORT DB2 10.5 FP4
      • PI25463 - Certain DB2 utilities like create database, db2updv* will crash if DTRC 3.1 is installed
       

       



      InfoSphere Optim Performance Manager Version 5.2

       

      1. Interim fix 6167 for InfoSphere Optim Performance Manager Version 5.2

       
      • IC87532 - IOPM 5.1.1.1 MIGRATION FAILS WITH DROP VIEW DB2PM_%.V_DIM_STATEMENTS SQLCODE=-478
      • IC88108 - OPTIM PERFORMANCE MANAGER - REPORTS LAUNCHPAD IS ALWAYS DISPLAYING THE LAST APPLIED FILTERS EVEN THOUGH THEY MIGHT NOT BE ACTIVE
      • IC88833 - OPTIM PERFORMANCE MANAGER - INCORRECT DATA IN EMAIL NOTIFICATION BODY FOR DEADLOCKS, LOCK WAITS, AND LOCK TIMEOUTS
      • IC88698 - OPTIM PERFORMANCE MANAGER INSTALLATION DOES NOT COPY CLU.ZIP FILE TO THE INSTANCE FOLDER CAUSING ERRORS IN OPM REPORTS
      • IC88734 - OPTIM PERFORMANCE MANAGER - INSTALLATION DOES NOT ACCEPT BACKSLASH CHARACTER AT THE END OF THE AUTOSTORAGE PATHS
      • IC89191 - #1 INTERNAL IMPROVEMENTS AND FIXES IN INFOSPHERE OPTIM PERFORMANCE MANAGER VERSION 5.2.0.0
       

      2. Interim fix 6227 for InfoSphere Optim Performance Manager Version 5.2

       
      • IC88944 - OPTIM PERFORMANCE MANAGER - SQL TEXT IN THE GRID OF THE REPORTS ARE NOT WRAPPED PROPERLY WHEN NO SPACE IS PRESENT
      • IC89065 - OPTIM PERFORMANCE MANAGER - EVERY LINE IN DOWNLOADED REPORT SCRIPTS ENDS WITH '\R\N'
      • IC88737 - OPTIM PERFORMANCE MANAGER - ALERT DETAIL REPORT DOESN'T SHOW DATA OR THE MESSAGE "DETAILS NOT AVAILABLE" FOR SOME ALERTS
      • IC89358 - IOPM OA NOTIFICATION IS NOT REPORTING THE CORRECT VALUES AND LABEL FOR FAILED TRANSACTIONS
      • IC89640 - IOPM CDPMA5127E THE REALTIME DATA COLLECTION FOR USER ID XXXXX, DASHBOARD ID YYYYY, AND SESSION ID ZZZZZ CANNOT BE CARRIED OUT
      • IC89374 - IOPM - WHEN CHANGING THE RETENTION VALUES IN THE CONFIGURATION DIALOG, THE OK BUTTON BECOMES DISABLED
      • IC89851 - IOPM - JAVA RUNTIME ENVIRONMENT UPGRADE
      • IC90043 - OPTIM PERFORMANCE MANAGER - BLACKOUT MENU IS MISSING FROM DATABASES GRID WHEN USING INTERNET EXPLORER
      • IC90165 - IOPM THE OPERATIONAL ALERT WEB PANEL DISPLAYS THE STRING __OPMREPOSERVERALERTSOURCE__ FOR THE DATA SOURCE COLUMN
      • IC90234 - OPTIM PERFORMANCE MANAGER - FORCE THE IMMEDIATE EXIT OF THE WEB CLIENT CONSOLE SERVER PROCESS WHEN THE STOP SCRIPT IS RUN
      • IC89744 - IOPM IN THE WEB UI DATABASES TAB. IF A FILTER IS APPLIED, THE LIST CAN FAIL TO RETURN AND DISPLAYS LOADING
      • IC89936 - IOPM THE PRODUCT DATA COLLECTOR 'COLLECTOR.SH' CAN FILL THE PRODUCT INSTALL LOCATION TRYING TO COLLECT THE SERVICE DATA
      • IC89962 - OPTIM PERFORMANCE MANAGER - CROSS SITE SCRIPTING ISSUE WITH THE LOGERROR.JSP URL
      • IC90311 - #2 INTERNAL IMPROVEMENTS AND FIXES IN INFOSPHERE OPTIM PERFORMANCE MANAGER VERSION 5.2.0.0

      3. Interim fix 6237 for InfoSphere Optim Performance Manager Version 5.2

       

      • IC90306 - OPTIM PERFORMANCE MANAGER CHANGES THE PARAMETER MON_OBJ_METRICS TO BASE WHEN THE VALUE IS EXTENDED
      • IC90646 - OPTIM PERFORMANCE MANAGER - WRONG DATE FORMAT ON PRE-DEFINED REPORTS LAUNCHPAD SCREEN ON OPM 5.2 FOR FRENCH LOCALE
      • IC90755 - CDPMA1177E ERROR HAPPENS WITH NO ERROR MESSAGE TEXT DISPLAYED
      •  

      4. Interim fix 6242 for InfoSphere Optim Performance Manager Version 5.2

       
      • IC91608 - IOPM THE HISTORY TIMELINE DISPLAY IN THE WEB CLIENT PANELS SHOWS LARGE GAPS IN THE COLLECTION INTERVAL
      • IC91130 - OPTIM PERFORMANCE MANAGER - GENERATING REPORTS TAKES LONGER TIMEAFTER UPGRADING TO 5.2.0
      • IC91878 - #3 INTERNAL IMPROVEMENTS AND FIXES IN INFOSPHERE OPTIM PERFORMANCE MANAGER VERSION 5.2.0.0

       

      5. Interim fix 6249 for InfoSphere Optim Performance Manager Version 5.2

       
      • IC92877 - IOPM MONITORING COLLECTION HALTS AFTER THE AFTER A MESSAGE STATING A SUCCESSFULLY RESTARTED
      • IC91872 - IOPM WEB PANELS WILL FAIL TO DISPLAY SNAPSHOT DATA IN THE 1 HOUR INTERVAL IF THE TIMEZONE IS DIFFERENT ON THE MONITORED
      • IC91764 - SLOW SCROLLING PERFORMANCE ON SQL DASHBOARD IF STATEMENTS HAVE A LONG STATEMENT TEXT
      • IC91599 - WHEN OPM WLM IS CONFIGURED, IT MAY CORRUPT THE SAVE DRAFT OF EXISTING WLM CONFIGURATION AND THROW ERROR CODE WLM51018E
      • IC89640 - IOPM CDPMA5127E THE REAL-TIME DATA COLLECTION FOR USER ID XXXXX,DASHBOARD ID YYYYY AND SESSION ID ZZZZZ CANNOT BE CARRIED OUT.
      • IC93234 - OPTIM PERFORMANCE MANAGER - REPORTS HANGS IN SOME CASES, LIKE SELECTING ALL FOR NUMBER OF CONNECTIONS, ON IE9R

      6. Interim fix 6255 for InfoSphere Optim Performance Manager Version 5.2

       
      • IC93204 - OPTIM PERFORMANCE MANAGER SETS UMASK TO 000 WHAT LEADS OPM RS SERVER TO CREATE JAVA DUMPS WITH 666 PERMISSION WRITE FOR ALL
      • IC94483 - OPMN* UNFORMATTED EVENT TABLE OF THE NEW LOCKING EVENT MONITOR MAY NOT BE PRUNED AND CAN SLOWLY GROW ON THE MONITORED DB.
      • IC94591 -INCORRECT TIME VALUE SORTING ON TOP DYNAMIC SQL REPORT WHICH IS USED WHEN MONITORING DATABASES IN SNAPSHOT (LESS THAN V9.7) MODE
      • IC95169 - JCC EXCEPTION ERRORS CAUSED in UoW EVENT MONITOR MAY AFFECT EI TRANSACTION DATA COLLECTION.
      • IC96036 OPTIM PERFORMANCE MANAGER - SQL STATEMENTS COLLECTED THROUGH TOP EXECUTIONS TAB IS TRUNCATED AT 1024
      •  

      7. Interim fix 6264 for InfoSphere Optim Performance Manager Version 5.2

       

      • IC95759 - OPTIM PERFORMANCE MANAGER DOES NOT WAKE UP AFTER A BLACKOUT PERIOD IF OPM WAS RECYCLED IN THE MIDDLE OF BLACKOUT PERIOD
      • IC96029 - OPTIM PERFORMANCE MANAGER - LOCK WAIT WARNING ALERTS ARE STILL BEING GENERATED AFTER UNCONFIGURING THE LOCK WAIT WARNING ALERT
      • IC95864 - OPTIM PERFORMANCE MANAGER CONNECTION AUTHORIZATION FAILURE WITH ERRORCODE=-4214 WHEN EDITING MONITORED DATABASE IN WEB UI
      • IC96160 - OPTIM PERFORMANCE MANAGER - IN SQL REPORTS SQL TEXT IS TRUNCATEDBEYOND 15000 CHARACTERS WHEN THE PERFDB IS 9.7
      • IC96379- OPM TEST CONNECTION TO THE MONITORED DATABASE MAY FAIL WITH COM.IBM.DB2.JCC.AM.SQLINVALIDAUTHORIZATIONSPECEXCEPTION ERROR
      • IC96579 - OPM SHUTDOWN OF THE MONITORED INSTANCE IN OPM RS SERVER MAY BE BLOCKED BUE TO HANGING "POOL-#-THREAD-#" THREAD
      • IC96857 - OPTIM PERFORMANCE MANAGER ERROR SQL STATE = 23503, ERROR CODE = 20000 (A VIOLATION OF FOREIGN KEY CONSTRAINT) IN DSSERVER.LOG
      • IC97278 - OPTIM PERFORMANCE MANAGER - WEB UI INFLIGHT DASHBOARD SHOWS ALL MEMBERS IN THE PULL DOWN LIST

      8. Interim fix 6268 for InfoSphere Optim Performance Manager Version 5.2

       

      • IC97621 - WHEN CUSTOMER GENERATES THE REPORTS BY COMMAND LINE, MANY 'BIRT_XLS_XXXXXXXX' FILES ARE GENERATED IN THE '/TMP' DIR
      • IC98083 - OPTIM PERFORMANCE MANAGER - FORCING SHUTDOWN OF STATEMENT TRACKER THREAD MAY LEAD TO LOCK IN SYSIBM.SYSPLAN TABLE
      • IC98672 - OPTIM PERFORMANCE MANAGER - ON DATABASE PAGE ALL DATABASES MONITORING STATUS SHOWS LOADING
      • IC98653 - OPTIM PERFORMANCE MANAGER - ADD SUPPORT TO DELETE OPERATIONAL ALERTS ISSUED AGAINST REPOSITORY DATABASE AND REPOSITORY SERVER
      • IC99420 - OPTIM PERFORMANCE MANAGER - WEB CONSOLE DOES NOT OPEN ANY DASHBOARDS, SHOWS BLANK PAGE
      • IC99427 - OPTIM PERFORMANCE MANAGER - DATABASE DASHBOARD SHOWS 'NOT CONFIGURED'
      • IC99636 - EXCEPTION IN PERFORMANCE OVERVIEW REPORT WHEN RENDERING DATA FOR A SNAPSHOT DPF DATABASE
       

      InfoSphere Optim Performance Manager Version 5.1.1.1

       

      1. Interim fix 5181 for InfoSphere Optim Performance Manager Version 5.1.1.1

       
      • IC86074 - "IOPM REPOSITORY SERVER SETS PDQ TRACE LEVEL TO CONFIGURE AFTER STARTUP. NO WAY TO CHANGE THE TRACE LEVEL IN PDQ.PROPERTIES"
      • IC85994 - "OPM REPOSITORY SERVER BLOCKS CMX EVENT HANDLING WHICH INDIRECTLY PREVENTS MONITORED APPLICATION SHUTDOWN"
      • IC85703 - "OPTIM PERFORMANCE MANAGER - STATEMENT METRIC TRACKER FAILED IN LAST N CONSECUTIVE ITERATIONS"
      • IC83286 - "OPM CDPMR0001E THERE IS NO PRE-DEFINED METRIC DEFINITION WITH THE NAME OPM_BP_BP_ID"
      • IC85905 - "OPTIM PERFORMANCE MANAGER CONNECTION SUMMARY REPORT, DATE FORMAT FOR CONNECTION ESTABLISHED AND CONNECTION CLOSED IS WRONG"
      • IC85960 - "OPTIM PERFORMANCE MANAGER - LONG STATEMENT TEXT MAY LOOSE BLANK CHARACTERS AND GIVES SYNTAX ERRORS WHEN TRYING TO EXPLAIN"
      • IC86060 - "IOPM DATABASES BEING MONITORED GET MARKED AS NEEDING MIGRATION AFTER THE MIGRATION IS COMPLETE"
      • IC86213 - "IOPM IN THE WEB UI THE LIST OF DATABASES TO SELECT FROM FOR MONITORING TAKES MINUTES TO POPULATE"
      • IC85821 - "IOPM GETS GET AN ERROR DIALOG WITH A CODE OF ERROR #1009 WHEN TRYING TO DISPLAY EXECUTION SUMMARY"
      • IC86223 - "IOPM WEB UI HEALTH SUMMARY WAS SLOW TO POPULATE THE DATA FROM THE >200 DATABASES IN THE SET BEING MONITORED"
      • IC86247 - "FLEXIBLE ALERTS NOTIFICATION IN OPM 511 DOES NOT HANDLE DISABLED HTTP (PORT=-1)"
      • IC85783 - "OPTIM PERFORMANCE MANAGER - LOCKING DASHBOARD DISPLAYS <ERROR MESSAGE TEXT> WHEN MULTIPLE REQUESTS ARE SENT"
      • IC86763 - "IOPM STATEMENT METRIC TRACKER FAILED IN LAST NN CONSECUTIVE ITERATIONS."
      • IC86795 - "INTERNAL IMPROVEMENTS AND FIXES IN INFOSPHERE OPTIM PERFORMANCE MANAGER VERSION 5.1.1.1"
      • IC86871 - "OPTIM PERFORMANCE MANAGER - PDF, PPT AND XLS VERSIONS OF THE TOP SQL REPORT SHOW 0.000000 FOR ALL TIME VALUES IN THE GRID."
      • IC86866 - "OPTIM PERFORMANCE MANAGER - CPU UTILIZATION IMPROVEMENTS IN 'DELETE FROM PROCMGMT' AND 'UPDATE DBPM.DATABASES' STATEMENTS"
      • IC86965 - "IOPM EXECUTION OF REPORT CHARTS IS GENERATING A LOG FILE IN THE PRODUCT DIRECTORY AND IS ONLY CLEARED ON RESTART OF WEB SERVER"
       

       

      2. Interim fix 5182 for InfoSphere Optim Performance Manager Version 5.1.1.1

       

      • IC87465 - "IOPM MONITORED DATABASE GETS A MESSAGE IN THE DB2DIAG.LOG OF DIA8053C EVENT MONITOR CANNOT BE DEACTIVATED"
      • IC87369 - "OPTIM PERFORMANCE MANAGER - PEREORG.DDL AND PERUNSTATS.DDL SCRIPTS TRYING TO REORG AND RUNSTATS OPM VIEWS"
      • IC87320 - "OPTIM PERFORMANCE MANAGER - REPORT_SQLSUMMARY_SHORT_TERM() WHICH IS UDF OF CUSTOM REPORTS RETURNS 0 RECORDS"
      • IC87269 - "OPTIM PERFORMANCE MANAGER - TOPSQL REPORT SHOWS A MAXIMUM OF 7500 CHARACTERS FOR SQL STATEMENT TEXT"
      • IC87493 - "OPTIM PERFORMANCE MANAGER - GETALERTDETAILS THROWS NUMBER FORMATEXCEPTION N/P WHEN DISPLAYING ALERT DETAILS"
      • IC87335 - "OPTIM PERFORMANCE MANAGER THROWS SQL204 EXCEPTION"
      • IC87368 - "OPTIM PERFORMANCE MANAGER - CROSS DATABASE REPORT CANNOT BE GENERATED USING COMMAND LINE UTILITY"
      • IC86767 - "OPTIM PERFORMANCE MANAGER - ALERT EMAIL NOTIFICATION: INCORRECT METRIC ID FILTERS CAUSES DUPLICATE DATA IN THE EMAIL"
      • IC87619 - "IOPM - INCORRECT OPERATIONAL ALERT ABOUT ELAPSED INFLIGHT COLLECTION TIME"
      • IC87522 - "IOPM REPOSITORY SERVER RUNS OUT OF MEMORY THUS INDIRECTLY BLOCKS EXTENDED INSIGHT CLIENTS"
       

       

      3. Interim fix 5186 for InfoSphere Optim Performance Manager Version 5.1.1.1

       

      • IC88227 - OPTIM PERFORMANCE MANAGER WILL ALWAYS UPDATE MON_LW_THRESHOLD PARAMETER ALTHOUGH CURRENT VALUE IS THE SAME AS DESIRED
      • IC88076 - OPTIM PERFORMANCE MANAGER - EI CLIENT METRICS ARE NOT COLLECTED AFTER IPL AND OTHER MONITORING RESTART
      • IC88108 - OPTIM PERFORMANCE MANAGER-REPORTS LAUNCHPAD IS ALWAYS DISPLAYING THE LAST APPLIED FILTERS EVENTHOUGH THEY MIGHT NOT BE ACTIVE
      • IC88698 - OPTIM PERFORMANCE MANAGER INSTALLATION DOES NOT COPY CLU.ZIP FILE TO THE INSTANCE FOLDER CAUSING ERRORS IN OPM REPORTS
      • IC88119 - IOPM - DATA TOOLS RUNTIME CLIENT 2.1.1.0 NOT SUPPORTED WITH INFOSPHERE OPTIM PERFORMANCE MANAGER VERSION 5.1.1.1
      • IC87510 - IOPM FOUND AN INTERNAL SQL QUERY THAT HAS A POOR ACCESS PLAN CAUSING HIGHER THEN REQUIRED OVERHEAD.
      • IC87532 - IOPM 5.1.1.1 MIGRATION FAILS WITH DROP VIEW DB2PM_%.V_DIM_STATEMENTS SQLCODE=-478
      • IC88402 - IOPM - INSTALLATION INCORRECTLY REMOVES PEREORG.DDL AND PERUNSTATS.DDL SCRIPTS
       

       

      4. Interim fix 5189 for InfoSphere Optim Performance Manager Version 5.1.1.1

       

      • IC88944 - OPTIM PERFORMANCE MANAGER - SQL TEXT IN THE GRID AT THE OF REPORTS ARE NOT WRAPPED PROPERLY WHEN NO SPACE IS PRESENT
      • IC89374 - IOPM - WHEN CHANGING THE RETENTION VALUES IN CONFIGURATION DIALOG, THE OK BUTTON BECOMES DISABLED.
      • IC89065 - OPTIM PERFORMANCE MANAGER - EVERY LINE IN DOWNLOADED REPORT SCRIPTS ENDS WITH \R\N
      • IC88833 - OPTIM PERFORMANCE MANAGER - INCORRECT DATA IN EMAIL NOTIFICATION BODY FOR DEADLOCKS, LOCK WAITS, AND LOCK TIMEOUTS
      • IC88832 - OPTIM PERFORMANCE MANAGER - LOCKING ALERT DETAILS ARE NOT POPULATED IN HEALTH SUMMARY AND ALERTS LIST AND RESULT IS HANGING
      • IC88737 - OPTIM PERFORMANCE MANAGER - ALERT DETAIL REPORT DOES NOT SHOW DATA OR DETAILS NOT AVAILABLE MESSAGE FOR SOME ALERTS
      • IC89358 - IOPM OA NOTIFICATION IS NOT REPORTING THE CORRECT VALUES AND LABEL FOR FAILED TRANSACTIONS
       

      5. Interim fix 5193 for InfoSphere Optim Performance Manager Version 5.1.1.1

       

      • IC89844 - IOPM - JAVA RUNTIME ENVIRONMENT UPGRADE

[{"Product":{"code":"SSBH2R","label":"InfoSphere Optim Performance Manager for Db2 for Linux, UNIX, and Windows"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"5.1.1.1;5.2;5.3;5.3.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
08 July 2021

UID

swg27024687

Page Feedback