PJ39890: SUPPORT CREATING SQW EXECUTION SCHEMA WITHOUT DBADM AUTHORITY

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • For usual usage, users executing the dataflow always have DBADM
    authorization, they can create schema IWSCHEMA${RESERVED/RUN_ID}
    successfully.  However, sometimes user is revoked the DBADM
    priviledge for security cosideration. For such scenario, our
    flow can't be executed as it will first try to create temporary
    schema.
    But in theory, the schema can be created by,
    1. db2 set schema
    2. db2 create table
    So we need to support such customer's scenario by continuing
    flow execution even failed to create temporary schema
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users without DBADM AUTHORITY can not execute the data flow  *
    * successfully                                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * For usual usage, users executing the dataflow always have    *
    * DBADM                                                        *
    * authorization, they can create temporary schema              *
    * successfully.                                                *
    * However, sometimes user is revoked the DBADM                 *
    * priviledge for security cosideration. For such scenario, our *
    * flow can't be executed as it will first try to create        *
    * temporary                                                    *
    * schema.                                                      *
    * But in theory, the schema can be created by,                 *
    * 1. db2 set schema                                            *
    * 2. db2 create table                                          *
    * So we need to support such customer's scenario by continuing *
    * flow execution even failed to create temporary schema        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to InfoSphere Warehouse 9.7.7 or later release       *
    ****************************************************************
    

Problem conclusion

  • Applying SQW_9.7.3.v20120118, the flow can be executed
    successfully. And this error will recorded as warning mesage in
    log files.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PJ39890

  • Reported component name

    DWE SQL WHSE TO

  • Reported component ID

    5724DWESQ

  • Reported release

    973

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-01-31

  • Closed date

    2012-10-23

  • Last modified date

    2012-10-23

  • 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

    DWE SQL WHSE TO

  • Fixed component ID

    5724DWESQ

Applicable component levels

  • R973 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

InfoSphere Warehouse
DWE - SQL Warehousing Tool

Software version:

973

Reference #:

PJ39890

Modified date:

2012-10-23

Translate my page

Machine Translation

Content navigation