IBM Support

PH55651: THE EXPECTED BEHAVIOUR WHEN USING DATABASE SCHEMA NAME REPLACEMENT AND AN ORACLE PACKAGE IS NOT DOCUMENTED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as documentation error.

Error description

  • The expected behaviour when using database schema name
    replacement is not documented.
    This leads to misunderstands and confusion about how customers
    should use it and what they should expect to happen.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus or App Connect Enterprise who
    make use of Oracle database stored procedures that are contained
    in an Oracle package.
    
    
    Platforms affected:
    AIX, Linux on x86-64 platform, Windows on x86-64 platform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    In ESQL you omit the database schema name when declaring a
    database function or a database stored procedure which resides
    in an Oracle package.
    If you then attempt to dynamically override the database schema
    name at run time then the Oracle database package may not be
    found.
    
    The documentation did not make it clear that when using an
    Oracle package that the ESQL database function or database
    procedure declaration must contain both the Oracle database
    schema name and the Oracle database package name for the dynamic
    substitution to work.
    

Problem conclusion

  • The documentation page "Using the CALL statement to call a
    user-written routine " has been updated to cover this.
    
    A new paragraph has been added to clarify what is expected
    
     When using an Oracle database, if a database stored procedure
    or a database function is contained in a database package, then
    both the database schema name and the database package name must
    be provided in the EXTERNAL NAME clause. If only the database
    package name is provided and the default schema name is chosen
    dynamically at run time then the database package may not be
    found.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH55651

  • Reported component name

    INT BUS FOR Z/O

  • Reported component ID

    5655AB110

  • Reported release

    A10

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-07-10

  • Closed date

    2023-09-13

  • Last modified date

    2023-09-13

  • 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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNQH8","label":"IBM Integration Bus for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A10","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"}}]

Document Information

Modified date:
27 February 2024