As update, today IBM answer my issue, it is a open issue in the development of the JDBC driver, and issue that came with version 7.4.1, and appear the fix is WIP.
"Cognos Analytics retrieves metadata via the DatabaseMetadata interface implemented by a JDBC driver. No column metadata is retrieved when the object name includes an underscore.
This version of the JDBC driver has an issue
The JDBC DatabaseMetadata interface methods accept values used to scope the metadata which should be retrieved. Several methods support pattern matching characters where JDBC uses the underscore character to match any single character and percentage as a wildcard.
When Cognos Analytics calls a method such as DatabaseMetadata.getColumns, it will pass the name of a database object (i.e. table). Should the name include either JDBC meta character, Cognos Analytics will escape those characters with an escape character.
Microsoft's 7.4.1 JDBC driver incorrectly handles parameter values where characters in a name include an escaped character
https://github.com/microsoft/mssql-jdbc/issues/1139
Reference in
https://www.ibm.com/support/pages/node/1073792
"
------------------------------
Jose Galvan
------------------------------
Original Message:
Sent: Mon January 27, 2020 02:37 PM
From: Jose Galvan
Subject: XQE-PLN-0012 error on Audit Package in 11.1.4
Good Afternoon.
I have several reports from the Audit Package (installed samples from 11.1.2). Started to run correctly in 11.1.2. Around 2 months ago we updated to 11.1.4 Cognos (no update to the package) and reports ran still ok.
Some days ago I updated the JDBC Drivers (from 7.2 to 7.4 latest) and next day all reports using the audit package started to fail with error:
RSV-VAL-0010 Failed to load the report specification. XQE-PLN-0012 The column 'COGIPF_LOGON_OPERATION' could not be found in the model.
If I repoint the report to the package from Cognos 10, the report works again.
If I rollback the drivers to 7.2 and reboot the servers, the reportsrun again.
Someone else have experienced this problem? just checking before entering an IBM Ticket.
------------------------------
Jose Galvan
------------------------------
#CognosAnalyticswithWatson