IBM Support

PM16278: USER INFORMATION IS READ INCORRECTLY ON DB2 FOR Z/OS WHEN PADIX=YES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • For performance reasons DB2 for z/OS pads varying-length index
    columns (VARCHAR) with whitespace characters (blanks) if global
    subsystem parameter PADIX is set to YES. This results in user
    IDs read, which show trailing blanks in their IDs. Such IDs do
    not match the expected IDs and thus entitlements are not
    associated correctly.
    Since resources stored in the database domain "jcr" are
    identified by string values, such objects can be affected. An
    example of such an error can be this message:
    
    [6/10/10 15:40:30:256 CEST] 00000012 StorageApi E
    com.ibm.wps.policy.commands.StorageApi getPolicyRoot
    EJQAB0067E:
    An error occurred while getting the policy root.
    com.ibm.portal.WpsException:
    EJQAB0067E: An error occurred while getting the policy root.
    
    [...]
    Caused by: com.ibm.icm.jcr.access.AccessDeniedException: The
    requested
    operation violates one or more access constraints.
    [...]
    
    When tracing is enabled, the object ID of the corresponding
    resource is displayed:
    
    [ExtIDImpl '6QReDe3BP4MIH6M1E03Q8C6JC4JS47P9EC6J56PHPAJGPCOPDC6J
    
    161JP02G0401802G0401802G0401802G0401802G0401802G0401802G0'
    [cebe46804bf229999ff19f5af87ff0af
    / ICM_CONTENT, Domain: [Domain: jcr]]
    
    Usually there should be only one (1) blank before the slash
    character (/).
    

Local fix

  • n/a
    

Problem summary

  • For performance reasons DB2 for z/OS pads varying-length
    index columns (VARCHAR) with whitespace characters (blanks) if
    global subsystem parameter PADIX is set to YES. This results in
    user IDs read, which show trailing blanks in their IDs. Such IDs
    do not match the expected IDs and thus entitlements are not
    associated correctly.
    
    Since resources stored in the database domain "jcr" are
    identified by string values, such objects can be affected. An
    example of such an error can be this message:
    
       [6/10/10 15:40:30:256 CEST] 00000012 StorageApi E
    com.ibm.wps.policy.commands.StorageApi getPolicyRoot EJQAB0067E:
    An error occurred while getting the policy root.
       com.ibm.portal.WpsException:
          EJQAB0067E: An error occurred while getting the policy
    root.
          [...]
       Caused by: com.ibm.icm.jcr.access.AccessDeniedException: The
    requested
          operation violates one or more access constraints.
          [...]
    
    When tracing is enabled, the object ID of the corresponding
    resource is displayed:
    
       [ExtIDImpl
    '6QReDe3BP4MIH6M1E03Q8C6JC4JS47P9EC6J56PHPAJGPCOPDC6J161JP02G040
    1802G0401802G0401802G0401802G0401802G0401802G0'
    [cebe46804bf229999ff19f5af87ff0af
    / ICM_CONTENT, Domain: [Domain: jcr]]
    
       Usually there should be only one (1) blank before the slash
    character (/).
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PM16278

  • Reported component name

    WEBSPHERE PORTA

  • Reported component ID

    5724E7600

  • Reported release

    61A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-06-10

  • Closed date

    2010-07-20

  • Last modified date

    2010-07-20

  • 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

    WEBSPHERE PORTA

  • Fixed component ID

    5724E7600

Applicable component levels

  • R61A PSY

       UP

  • R61C PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSHRKX","label":"WebSphere Portal"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1.0.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
20 July 2010