IBM Support

JR35048: ERROR HAPPENS IF THE 1ST CHARACTER OF PASSWORD IS NUMERIC

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • Even though the password is correct, the following err happens
    if the 1st character of password is numeric:"Incorrect dboptions
    option list; ..."
    It is requesting to add any explanation about it.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of Oracle Enterprise Operator stage when the password
    starts with a number.
    ****************************************************************
    PROBLEM DESCRIPTION:
    Even though the password is correct, the following error
    happens if the 1st character of password is numeric:
    Incorrect dboptions option list; it failed on Expected "," or
    "}", got: "mH1C3ic", line 1
    Password is "5mH1C3ic" and it seems from the 1st error message
    that the 1st numeric character '5' is removed.
    Similar error happens at viewing data, too.
    
    ****************************************************************
    RECOMMENDATION:
    Q: Are there any special requirements for the Username and
    Password property values?
    A:
    The same restrictions apply to both Username and Password
    property values. Those restrictions are as follows:
    
    1) The value must not contain single quote or double quote
    characters. The stage does not support working with username and
    password values which contain single or double quote characters.
    
    
    2) If the value starts with a numeric character, it should be
    enclosed in a pair of double quote characters.
    
    3) If the value contains one or more special characters, it
    should be enclosed in a pair of double quote characters. Also
    the special characters themselves should be escaped with a
    backslash characters. Note that characters other than
    alphanumeric and underscore characters are considered special
    characters.
    
    For example, presume that the Oracle user was defined in the
    database with the user#1 username and 1a\b password.
    
    The value "user\#1" should be specified in the Username
    property, and the value "1a\\b" should be specified in the
    Password property.
    
    When the DB Options Mode property is set to value User-defined,
    then the Username and Password properties are disabled, and the
    user needs to manually specify the DB Options property. This
    property value contains the username and password parameters to
    use for the connection. The same rules and restrictions for the
    username and password values apply in this case. For example if
    Oracle username and password are user$1 and 1test then the value
    {user="user\$1",password="1test"} should be specified in
    the DB Options property.
    
    Note that when DB Options Mode property is set to value
    User-defined, the password value will not be encrypted if
    manually typed in as part of the DB Options property. In order
    for the password value in DB Options property to be encrypted,
    it should be specified through an encrypted job parameter
    instead of being manually typed in.
    
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    JR35048

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    810

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-12-06

  • Closed date

    2009-12-15

  • Last modified date

    2009-12-15

  • 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

  • R810 PSN

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"IBM InfoSphere DataStage"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
15 December 2009