Results 1 to 14 of 14

Thread: error SQL30082N

  1. #1
    Join Date
    Jan 2003
    Posts
    21

    Unhappy Unanswered: error SQL30082N

    db2 connect 7.1 on linux red hat 7.2 (d72pcfp5.zip)
    db2 server 7.1 on windows 2000 server

    WHen I try to connect to a remote database, it return the error :

    SQL30082N Attempt to establish connection failed with security reason "17" ("UNSUPPORTED FUNCTION"). SQLSTATE=08001

    I don't understand some things about the db2 connect :
    - i create an instance whith login and password on the linux
    - this login and pass doesn't exist
    - i try to connect with "connect to testdb user myuser using mypass" with 2 issues :
    -> the log / pass of the remote db owner : it returns an authentification error, this user isn't declared on the linux
    -> the log / pass of the instance manager : it returns the SQL30082N error, as if the connexion was accepted (log / pass correct) but something after that doesn't work.

    What I'm suppose to do to reference a valid user on the linux who have rights to use the db2 database on the windows2000 ?

    thks for answer or id about this

  2. #2
    Join Date
    Jan 2003
    Posts
    24
    Hi.

    I think you need to check the AUTHENTICATION setting in the database manager configuration. The default setting is "SERVER", meaning that DB2 will request user authentication from the server OS.
    If you change the setting to "CLIENT" you should be able to connect with your linux user. You can read more about it in the administration guide.

    Regards
    /Daniel

  3. #3
    Join Date
    Jul 2003
    Location
    Hamburg, Germany
    Posts
    31

    Red face my problem

    Hi,

    I have nearly the same problem!??

    I get whenever I try connecting with several different users from client to the server (and the users are existing also on serverside!) I receive the following:

    SQL30082N Attempt to establish connection failed with security reason =
    "24"("USERNAME AND/OR PASSWORD INCALID"). SQLSTATE=08001


    But the username and the password are correct and exist on server side!!!?

    My authenticatin parameters are: CLIENTSIDE
    - Security options = SERVER
    - connecting with CLI ( I tried also Standard,...)

    SERVERSIDE:
    (AUTHENTICATION) = SERVER
    (CATALOG_NOAUTH) = NO
    (TRUST_ALLCLNTS) = YES
    (TRUST_CLNTAUTH) = CLIENT
    (USE_SNA_AUTH) = NO
    (FED_NOAUTH) = NO

    Any ideas?!!

    Thank you !!!!!!!!!!

  4. #4
    Join Date
    Jan 2003
    Posts
    1,605
    Hi,

    This maybe will not help, but...
    To establish connection between Linuw and Windows you don't need the connect at Linux site. You only need the run-time client at Linux site or you may need administrative client, depending what you would like to do.

    Hope this helps,
    Grofaty

  5. #5
    Join Date
    Jul 2003
    Location
    Hamburg, Germany
    Posts
    31

    It doesn't help

    Sorry, but I don't know what you mean?!!



    Originally posted by grofaty
    Hi,

    This maybe will not help, but...
    To establish connection between Linuw and Windows you don't need the connect at Linux site. You only need the run-time client at Linux site or you may need administrative client, depending what you would like to do.

    Hope this helps,
    Grofaty

  6. #6
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650

    Re: It doesn't help

    Grofaty says :

    For a client to connect to DB2 on Linix, Unix and Windows, you will need Runtime Client(or Admin client or app dev client)

    For a client to connect to DB2 on os390,z/os,as400,vm, you will need DB2 Connect installed on the client

    Cheers

    Sathyaram
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  7. #7
    Join Date
    Jul 2003
    Location
    Hamburg, Germany
    Posts
    31

    Question Re: It doesn't help

    My Database runs on Solaris and I work clientside with an IBM DB2 Administration Client V8.1 for Windows! Will I need to install DB2 Connect anyway? And when it's right, what is DB2-Connect? Is that a software?? Sorry if I'm asking so stupid questions, but that's my first time with DB2!!!

    It would be nice for any posts!

    Thanks out there...

    Originally posted by sathyaram_s
    Grofaty says :

    For a client to connect to DB2 on Linix, Unix and Windows, you will need Runtime Client(or Admin client or app dev client)

    For a client to connect to DB2 on os390,z/os,as400,vm, you will need DB2 Connect installed on the client

    Cheers

    Sathyaram
    Last edited by savas; 07-30-03 at 04:32.

  8. #8
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650

    Re: It doesn't help

    You do not need DB2 Connect to connect to a database server on Solaris

    (DB2 Connect is a client product which provides access to DB2 on legacy systems)

    Cheers

    Sathyaram
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  9. #9
    Join Date
    Jul 2003
    Location
    Hamburg, Germany
    Posts
    31

    Unhappy And now?

    Hi,

    I'm working clientside with an IBM DB2 Administration Clients, V8.1 for Windows and I do not need an BD2 Connect!

    But what can I do now? I mean, at connecting to database I give the right username and password and anyway it doesn't work

    Isnt't there a log on solaris, where I can look into to find a failure? Do you know the path it could be?

    Thanks again

  10. #10
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650

    Re: And now?

    Increase your diaglevel and notify level to 4(and restart the instance), connect from your client and check your db2diag.log and instance.nfy(solaris)/eventlog on win ... Also check your OS security log(ask your sysadmin )

    To chage diaglevel and notifylevel

    db2 update dbm cfg using diaglevel 4 notifylevel 4

    Do the same on client and server ...

    Let us know if you see any info ..

    Originally posted by savas
    Hi,

    I'm working clientside with an IBM DB2 Administration Clients, V8.1 for Windows and I do not need an BD2 Connect!

    But what can I do now? I mean, at connecting to database I give the right username and password and anyway it doesn't work

    Isnt't there a log on solaris, where I can look into to find a failure? Do you know the path it could be?

    Thanks again
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  11. #11
    Join Date
    Jul 2003
    Location
    Hamburg, Germany
    Posts
    31

    Post db2diag.log

    This is the db2diag.log:

    DIA3218I "2" TCP/IP connection manager(s) was/were successfully started.

    2003-07-30-10.24.32.026432 Instance:db2inst1 Node:000
    PID:26666(db2sysc 0) TID:1 Appid:none
    common communication sqlcctcp_start_listen Probe:80

    DIA3000I "TCPIP" protocol support was successfully started.

    2003-07-30-10.24.33.213106 Instance:db2inst1 Node:000
    PID:26661(db2star2) TID:1 Appid:none
    base sys utilities startdbm Probe:911

    ADM7513W Database manager has started.

    2003-07-30-10.24.33.283824 Instance:db2inst1 Node:000
    PID:26659(db2start) TID:1 Appid:none
    oper system services sqlofica Probe:10

    ALERT :997
    PID:26659 TID:1 Node:000 Title: Not available!
    5351 4c43 4120 2020 0000 0088 ffff fbd9 SQLCA ....
    0000 2020 2020 2020 2020 2020 2020 2020 ..
    2020 2020 2020 2020 2020 2020 2020 2020
    2020 2020 2020 2020 2020 2020 2020 2020
    2020 2020 2020 2020 2020 2020 2020 2020
    2020 2020 2020 2020 5351 4c45 5046 494e SQLEPFIN
    0000 0000 0000 0000 0000 0000 0000 0000 ................
    0000 0000 0000 0000 2020 2020 2020 2020 ........
    2020 2020 2020 2020

    2003-07-30-10.25.07.050451 Instance:db2inst1 Node:000
    PID:26670(db2tcpcm 0) TID:1 Appid:none
    common communication sqlcctcpconnmgr_child Probe:103

    DIA3421W "TCPIP" protocol support: Environment Variable value
    "DB2SOSNDBUF" = "65536" is "accepted".

    2003-07-30-10.25.07.085450 Instance:db2inst1 Node:000
    PID:26670(db2tcpcm 0) TID:1 Appid:none
    common communication sqlcctcpconnmgr_child Probe:108

    DIA3421W "TCPIP" protocol support: Environment Variable value
    "DB2SORCVBUF" = "65536" is "accepted".

    2003-07-30-10.25.07.109768 Instance:db2inst1 Node:000
    PID:26670(db2tcpcm 0) TID:1 Appid:none
    common communication sqlcctcpconnmgr_child Probe:117

    DIA3219I Client connecting from IP address = "134.100.11.230", port = "4149".
    On clientside:
    In db2diag.log I get something like
    ...DIA3202C The TCP/IP call "connect" returned an errno="10060".
    and in the DB2Journal I get something..
    SQL22212N ..A communicationerror was found on DB2-Controlserver . Clientsystem: "134.100.11.230". Serversystem "134.100.6.4"
    (I translated it from german to english )

    What about http://www-1.ibm.com/support/docview...f-8&lang=en+en
    Last edited by savas; 07-30-03 at 06:24.

  12. #12
    Join Date
    Sep 2008
    Posts
    2

    Error connect to DB2 DB on AIX m/c

    I have same problem-
    Iam trying to access DB2 Db on AIX m/c on my DB2 client installation on windows XP.
    Getting the following error msg while testing the connection-

    CLI connection failed.
    SQL30082N Security processing failed with reason "24" ("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001

    BTW, i used 'Server side authentication', while configuring the DB.

    Thanks in Advance
    Last edited by machikere; 09-08-08 at 15:30.

  13. #13
    Join Date
    Jan 2007
    Location
    Jena, Germany
    Posts
    2,721
    What's your AUTHENTICATION setting at the server? If it is SERVER, then the DB2 server needs user name and password to do the authentication, for example.
    Knut Stolze
    IBM DB2 Analytics Accelerator
    IBM Germany Research & Development

  14. #14
    Join Date
    Sep 2008
    Posts
    2
    I tried to access DB using the configuration assistant with following options-

    Protocol- TCP/IP
    Security options- Use authentication value in server's DBM configuration( i tried with client authenticatin, & server authentication) , but with same result.

    To your question what authentication on sever , i have no clue. Is this the question i can ask my DB admin??

    Now iam getting this msg-

    CLI connection failed.
    SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "9.3.148.114". Communication function detecting the error: "connect". Protocol specific error code(s): "10060", "*", "*". SQLSTATE=08001

Posting Permissions

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