IBM Support

JR39601: ORACLE EE STAGE CREATING SQL*LOADER FILES WITH CONFLICTING NAMES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Oracle Enterprise Load stage is creating a SQL*Loader files that
    are not unique across job runs.
    

Local fix

Problem summary

  • Oracle Enterprise stage creates configuration files used by
    SQL*Loader during the bulk load process. These files were
    created using the PID of the process with the player node. This
    naming convention was not unique enough for some users who run
    hundreds of job per week. If the file already existed the job
    would abort with error message: error: Permission denied.
    

Problem conclusion

  • The solution is to make the file name more unique by adding a
    random number to its name. The file name now has this format:
    ora.<PID>.<INSTANCE ID>.<RANDOM NUM>.<PLAYER ID>.*
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR39601

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-05-17

  • Closed date

    2011-05-31

  • Last modified date

    2011-05-31

  • 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

  • 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.5"}]

Document Information

Modified date:
07 October 2021