Direct links to fixes
7.1.0-TIV-NCI-ZLINUX-FP0006
7.1.0-TIV-NCI-WINDOWS-FP0006
7.1.0-TIV-NCI-SOLARIS-FP0006
7.1.0-TIV-NCI-LINUX-FP0006
7.1.0-TIV-NCI-AIX-FP0006
6.1.1-TIV-BSM-FP0004-windows
6.1.1-TIV-BSM-FP0004-zlinux
6.1.1-TIV-BSM-FP0004-solaris
6.1.1-TIV-BSM-FP0004-linux
6.1.1-TIV-BSM-FP0004-aix
6.1.1-TIV-NCI-FP0004-windows
6.1.1-TIV-NCI-FP0004-zlinux
6.1.1-TIV-NCI-FP0004-solaris
6.1.1-TIV-NCI-FP0004-aix
6.1.1-TIV-NCI-FP0004-linux
7.1.0-TIV-NCI-ZLINUX-FP0005
7.1.0-TIV-NCI-LINUX-FP0005
7.1.0-TIV-NCI-WINDOWS-FP0005
7.1.0-TIV-NCI-SOLARIS-FP0005
7.1.0-TIV-NCI-AIX-FP0005
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 4(7.1.0-TIV-NCI-FP0004)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 5(7.1.0-TIV-NCI-FP0005)
IBM Tivoli Netcool/Impact V6.1.1 Fix Pack 4 (6.1.1-TIV-NCI-FP0004)
IBM Tivoli Business Service Manager V6.1.1 Fix Pack 4(6.1.1-TIV-BSM-FP0004)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 6(7.1.0-TIV-NCI-FP0006)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 7(7.1.0-TIV-NCI-FP0007)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 8(7.1.0-TIV-NCI-FP0008)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 9(7.1.0-TIV-NCI-FP0009)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 10(7.1.0-TIV-NCI-FP0010)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 11(7.1.0-TIV-NCI-FP0011)
IBM Tivoli Netcool/Impact V6.1.1 Fix Pack 5 (6.1.1-TIV-NCI-FP0005)
IBM Tivoli Business Service Manager V6.1.1 Fix Pack 5(6.1.1-TIV-BSM-FP0005)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 12 (7.1.0-TIV-NCI-FP0012)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 13 (7.1.0-TIV-NCI-FP0013)
APAR status
Closed as program error.
Error description
When using a database event reader, the format used for the generated SQL for the timestampfield in the select statement changes to a format which is incompatible with the date column it is selecting on. Believed to be an issue with the date format in the .state file. Recreate scenario: APAR being requested: NO Product: Impact Product Version: 6.1.1 Fix/Build Level: FP2 Test Fixes installed: Target Component: DatabaseEventReader OS and version: Linux INTEGRATION DETAILS: SUMMARY OF PROBLEM: When using a database event reader against the ImpactDB, the format used for the generated select statement changes to a format which is incompatible with the date column it is selecting on. INFORMATION COLLECTED: Scenario reproduced in the lab. PD ALREADY PERFORMED: Tried using the formatpattern field in the .props file for the database event reader - made no difference. Replicated locally?: Yes Replication steps: Create a table in the ImpactDB with columns: COLUMN_NAME |TYPE_NAME|DEC&|NUM&|COLUM&|COLUMN_DEF|CHAR_OCTE&|IS_NULL& ---------------------------------------------------------------- CUSTOMER_ID |INTEGER |0 |10 |10 |NULL |NULL |YES LOG_DATE |DATE |0 |10 |10 |NULL |NULL |YES EXECUTE_FLAG |INTEGER |0 |10 |10 |NULL |NULL |YES CUSTOMER_NAME |VARCHAR |NULL|NULL|128 |NULL |256 |YES EXECUTION_TIME |VARCHAR |NULL|NULL|32 |NULL |64 |YES SCHEDULED_ON_DAY |VARCHAR |NULL|NULL|32 |NULL |64 |YES STATUS |VARCHAR |NULL|NULL|50 |NULL |100 |YES JOB_TYPE |VARCHAR |NULL|NULL|128 |NULL |256 |YES JOB_ACTION |VARCHAR |NULL|NULL|1024 |NULL |2048 |YES Create a database event reader with the following properties: impact.pmr87249.executeallmatchingpolicies=false impact.pmr87249.autostartup=true impact.pmr87249.numfilters=1 impact.pmr87249.timestampfield=LOG_DATE impact.pmr87249.restriction.1=EXECUTE_FLAG\=1 impact.pmr87249.fields=* impact.pmr87249.policyname.1=PMR87249 impact.pmr87249.ispolicyinchainforfilter.1=false impact.pmr87249.polltime=3000 impact.pmr87249.logtofile=true impact.pmr87249.formatpattern='yyyy-MM-dd' impact.pmr87249.datasource=ImpactDB impact.pmr87249.getupdates=true impact.pmr87249.datatype=PMR87249 impact.pmr87249.isfilteractive.1=true impact.pmr87249.keyfield=JOB_ACTION Create a arbitrary policy that just logs the EventContainer. Create some records in the ImpactDB table with values in the LOG_DATE column of 'YYYY-mm-dd'. Start the event reader. If you then restart Impact without deleting the .state file the event reader will fail with messages like: 17 Jun 2015 09:33:33,000: Query: select * from IMPACT.PMR87249 where LOG_DATE >= 'Wed Jun 17 00:00:00 BST 2015' AND (EXECUTE_FLAG=1) order by LOG_DATE 17 Jun 2015 09:33:33,013: Error while reading events: __LOGVIEWER__STACKTRACE_ GenericEventDriver.readEvents(): could not get the Result Set for the query: select * from IMPACT.PMR87249 where LOG_DATE >= 'Wed Jun 17 00:00:00 BST 2015' AND (EXECUTE_FLAG=1) order by LOG_DATE See the LOG_DATE specified in the above select statement. When it is working you see something like: 17 Jun 2015 09:10:00,490: Query: select * from IMPACT.PMR87249 where LOG_DATE >= '2015-06-17' AND (EXECUTE_FLAG=1) order by LOG_DATE 17 Jun 2015 09:10:00,496: Read: 1 New Read: 0 OSQueue: 0 ReadBuffer: 7 NumReaderBuffer: 3 Time: 0 Events Read/Sec: 1 New Events Read/Sec: 0 Memory: 242141712
Local fix
It is not an ideal workaround, but deleting the .state file when you restart will allow the DatabaseEventReader to restart correctly.
Problem summary
**************************************************************** * USERS AFFECTED: * * All Impact Users * **************************************************************** * PROBLEM DESCRIPTION: * * DATABASEEVENTREADER USES INCORRECT DATE FORMAT ON RESTARTING * **************************************************************** * RECOMMENDATION: * * None * **************************************************************** When using a database event reader, the format used for the generated SQL for the timestampfield in the select statement changes to a format which is incompatible with the date column it is selecting on.
Problem conclusion
Changed to save the .state file in the format specified by the formatpattern property. The fix for this APAR is contained in the following maintenance packages: |Fix Pack | 6.1.1-TIV-NCI-FP0004 |Fix Pack | 7.1.0-TIV-NCI-FP0004
Temporary fix
Comments
APAR Information
APAR number
IV74485
Reported component name
NETCOOL/IMPACT
Reported component ID
5724O59IS
Reported release
611
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-06-24
Closed date
2015-08-07
Last modified date
2015-08-07
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
UNKNOWN
Fix information
Fixed component name
NETCOOL/IMPACT
Fixed component ID
5724O59IS
Applicable component levels
R611 PSY
UP
R710 PSY
UP
Document Information
Modified date:
07 August 2015