Databases
StackOverflow2013
Postsdbo
POdb2 can't connect from clients after restart
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POdb2 can't connect from clients after restart
    primarykey
    data
    text
    <p>I stopped my db using db2stop force. The started did a backup restarted and after that i cannot connect to db from the a client anymore i get: using the command </p> <blockquote> <p>db2 connect to "dbname" using "user"</p> <p>SQL30082N Security processing failed with reason "42" ("ROOT CAPABILITY REQUIRED"). SQLSTATE=08001</p> </blockquote> <p>password and username are correct. When im on the server connecting using command</p> <blockquote> <p>db2 connect to "dbname"</p> </blockquote> <p>or </p> <blockquote> <p>db2 connect to "dbnmae" user "user"</p> </blockquote> <p>or</p> <blockquote> <p>db2 connect to "dbname" user db2inst1</p> </blockquote> <p>works just fine. I m really confused. Any help is much appreciated Thanks.</p> <p>What i tried so far :</p> <blockquote> <p>db2 get dbm cfg | grep -i auth GSS Plugin for Local Authorization<br> (LOCAL_GSSPLUGIN) = Server Connection Authentication<br> (SRVCON_AUTH) = NOT_SPECIFIED Database manager authentication<br> (AUTHENTICATION) = SERVER Cataloging allowed without authority<br> (CATALOG_NOAUTH) = NO Trusted client authentication<br> (TRUST_CLNTAUTH) = CLIENT Bypass federated authentication<br> (FED_NOAUTH) = NO</p> </blockquote> <p>switched to client but did not using</p> <blockquote> <p>db2 update dbm cfg using authentication client</p> </blockquote> <h3>Update:</h3> <p>Despite the age of this question, it would be wonderful to have a solid answer to this question. Hi locojay, how did you manage? :-)</p> <p>I'm having the SQL30082N reason code 24 issue in my Windows PC, and today we experienced the same issue in an AIX server. </p> <p>I googled for a couple hours and didn't find but one happy answer, related to having users with the same name both in the server and the client. IMO it does not apply to me, as I'm running into a VBox that´s isolated from the domain (no network). </p> <p>My case: I installed DB2 as user db2admin, no security. Then I granted DBADM to VIRTUALUSR01 and gave this user a password. </p> <pre><code> db2 connect to TheBase </code></pre> <p>works fine. But</p> <pre><code> db2 connect to TheBase user VIRTUALUSR01 using TheRightPassword </code></pre> <p>returns SQL30082N with reason code 24. </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBill the Lizard
    1. USlocojay
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POdb2 can't connect from clients after restart
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POdb2 can't connect from clients after restart
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POdb2 can't connect from clients after restart
      1. This table or related slice is empty.
      1. VTUpMod
    1. COthnks to chris did solve it by using db2 update dbm cfg using authentication client db2 update dbm cfg using trust_allclnts yes db2 update dbm cfg using trust_clntauth server db2stop db2start i still don't know what the hell happend. Google didn't help so hope this post will make googling for that prob better
      singulars
      1. POdb2 can't connect from clients after restart
      1. USlocojay
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload