PI99076: REPORTS FAILING THAT CONTAIN REFERENCE TO ORACLE SYNONYM WHERE THE DATABASE QUERY SUBJECT HAS BEEN RENAMED.

APAR status

• Closed as Vendor Solution.

Error description

• XQE-PLN-0011 The relation <synonym_name> could not be found in
  the model.
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• This is not a IBM Cognos defect.
  
  In Cognos 10.x, hand written sql statements are used to retrieve
  metadata information from JDBC data sources. In Cognos 11.x,
  Cognos makes JDBC calls DatabaseMetadata.getTables(catalogName,
  schemaName, synonymName, null) instead as this is a better way
  to retrieve this metadata.
  
  For this APAR's testcase in which the database username is
  different from schema name,
  DatabaseMetadata.getTables(catalogName, schemaName, synonymName,
  null) returns empty result set, which is wrong. This is Oracle
  server defect. Problem does not happen on Oracle server
  12.1.0.2. Problem happens on Oracle server 12.2.0.1 and
  11.2.0.4.
  
  This problem always happens when Oracle database user name is
  different from Oracle schema name in Framework Manager, no
  matter which Oracle server is used.
  Current workaround is to ask customer to check Oracle schema
  name in FM, to make Oracle database user name the same as Oracle
  schema name.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels