Results 1 to 5 of 5

Thread: SQL30082N rc=19

  1. #1
    Join Date
    Oct 2004
    Posts
    1

    Unanswered: SQL30082N rc=19

    Hello,

    I have installed DB2 v8.1 with last FP 7a under Windows 2000 Server.
    When I tried to connect to my database SAMPLE with : db2 connect to SAMPLE user db2adm using dbpasswd, I have this error :
    SQL30082N reason code=19 ("USERID DISABLEDor RESTRICTED"). SQLSTATE=08001.

    ps: When I installed DB2 v8.1 with FP 6 it's work.

    Thanks for your response.

  2. #2
    Join Date
    Mar 2004
    Location
    Toronto, ON, Canada
    Posts
    513
    Quote Originally Posted by vinstrial
    Hello,

    I have installed DB2 v8.1 with last FP 7a under Windows 2000 Server.
    When I tried to connect to my database SAMPLE with : db2 connect to SAMPLE user db2adm using dbpasswd, I have this error :
    SQL30082N reason code=19 ("USERID DISABLEDor RESTRICTED"). SQLSTATE=08001.

    ps: When I installed DB2 v8.1 with FP 6 it's work.

    Thanks for your response.
    Did you find a solution for this? I'm seeing similar behaviour, worked, installed 7a, now fails. The login id is fine with Windows, not disabled/restricted.
    --
    Jonathan Petruk
    DB2 Database Consultant

  3. #3
    Join Date
    Oct 2004
    Location
    DELHI INDIA
    Posts
    338

    Jayanta, Xansa India

    Step1 : First make it sure that the User name is provided during the time of installation only. Give that user admin privilege from control panel --> administrative tool --> Computer Management --> Local User and Group

    Add that user in the User and Password field in Control Panel.

    Step2 : Drop the sample database

    Step3 : in the start-->run--> db2cmd

    db2sampl

    Sample database would be created again.

    Step4: Now connect to sample database with the admin user id.

    If required uninstall and install again Db2 ESE and follow the steps mentioned.

    Thanks,
    Jayanta

  4. #4
    Join Date
    Mar 2004
    Location
    Toronto, ON, Canada
    Posts
    513
    That won't resolve it, this is a connection and database which worked fine before installation of a fixpack.

    I've openned a PMR, post with what they figure out...

    jono
    --
    Jonathan Petruk
    DB2 Database Consultant

  5. #5
    Join Date
    Mar 2004
    Location
    Toronto, ON, Canada
    Posts
    513
    They fixed it.

    I had to run the "db2secv82" command.
    http://publib.boulder.ibm.com/infoce...e/r0011802.htm

    I also had to add my userid to the DB2USERS group in Windows, which I didn't have to do before.
    --
    Jonathan Petruk
    DB2 Database Consultant

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •