IBM Support

JR38362: JOB WITH ORACLE CONNECTOR STAGE FAILS TO ACCESS THE REMOTE DATABASE TABLE.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Job failed with the following error.
    
       Item #: 20
       Event ID: 1840
       Timestamp: 2010-10-26 10:50:14
       Type: Fatal:
       User Name: VijayM
       Message Id: IIS-CONN-NGBR-00002
    Message: Oracle_Connector_34,3: [IIS-CONN-ORA-001031] The
    connector
    could not find the specified table or view
    GTSEQ.ARCH_GTSEQ_AUDIT.
    (CC_OraUtils::getColumnNamesAndTypes, file CC_OraUtils.cpp, line
    5,884)
    
    If switch to Oracle EE, it works fine.  Also the customer is
    able to execute the same sql accessing the remote table from
    sqlplus from Oracle client installed on IS server.
    

Local fix

  • NA
    

Problem summary

  • When the connector is configured to write data to a table
    (auto-generated DML) it inspects the table to get the names and
    types of columns. The names are necessary so that the connector
    can handle 'Drop unmatched fields' setting, for which it may
    need to fail the job if there are columns on the input link that
    do not exist in the target table. The code is inspecting
    dictionary views which is OK if the table (or view or synonym)
    resolves to an object in the local database. But if it is a
    remote table (in form table@dblink) or a synonym to such object,
    the code was failing because the metadata for remote objects is
    not maintained in the local dictionary.
    

Problem conclusion

  • The Oracle Connector was enhanced to run 'SELECT * FROM tblname'
    and describe columns for this statement, when the attempt to
    obtain tblname metadata directly from the dictionary fails. This
    is a fallback mechanism that will work for database links and
    any other scenarios where the connector cannot obtain metadata
    directly from the dictionary views.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR38362

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    810

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-11-30

  • Closed date

    2010-12-10

  • Last modified date

    2010-12-10

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

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

Modules/Macros

  • ORA EE
    

Fix information

  • Fixed component name

    WIS DATASTAGE

  • Fixed component ID

    5724Q36DS

Applicable component levels

  • R810 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":"8.1"}]

Document Information

Modified date:
06 October 2021