A fix is available
APAR status
Closed as program error.
Error description
Some Oracle Connector jobs that perform READ partitioning may fail after upgrading to a new release of Information Server. The READ partitioning rules were strengthened in the fix for APAR JR58003. However, depending on the original, user-defined SQL, running the same job "as is" might result in this error: The OCI function OCIStmtExecute returned status -1. Error code: 904, Error message: ORA-00904: MY_ALIAS.ROWID: invalid identifier. (CC_OraStatement::executeSelect, file CC_OraStatement.cpp, line NNNN) Why does this happen? When Oracle prepares the statement, it creates multiple temporary views for different parts of the query plan and may lose track of the table aliases that appear earlier in the SQL.
Local fix
Use only one player node to eliminate partitioning.
Problem summary
The changes in this APAR allow the pre JR58003 partitioning behavior.
Problem conclusion
The solution is to provide more than one way for Oracle Connector to accomplish the partioning. Jobs can be reverted to the earlier method (prior to the fix for APAR JR58003 by setting a user defined environment variable in the job. CC_ORA_PRE_JR58003_PARTITIONING=TRUE
Temporary fix
One way to work around this is to change the value of the Oracle Connector property "Table name for partitioned reads". It is recommended to use the table name from the first SELECT inner statement. This work around may not be feasible for some customers who have too many jobs to modify in this manner. Furthermore, in some cases, changing the value of the "Table name for partitioned reads" may produce duplicate records. If this is the case, use the environment variable supplied in this APAR fix to revert to the weaker partitioning rules. Set the user-defined environment variable CC_ORA_PRE_JR58003_PARTITIONING=TRUE
Comments
APAR Information
APAR number
JR60452
Reported component name
WIS DATASTAGE
Reported component ID
5724Q36DS
Reported release
B70
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-12-18
Closed date
2019-01-01
Last modified date
2019-01-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WIS DATASTAGE
Fixed component ID
5724Q36DS
Applicable component levels
RB70 PSY
UP
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"InfoSphere DataStage"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.7"}]
Document Information
Modified date:
03 September 2021