Tags: connect, d72pcfp5, database, db2, error, hat, linux, mysql, oracle, red, remote, return, server, serverwhen, sql, sql30082n, windows, zip

error SQL30082N

On Database » DB2

8,042 words with 10 Comments; publish: Sat, 01 Dec 2007 11:36:00 GMT; (25062.50, « »)

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

All Comments

Leave a comment...

  • 10 Comments
    • 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

      #1; Tue, 11 Dec 2007 17:43:00 GMT
    • 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 !!!!!!!!!!

      #2; Tue, 11 Dec 2007 17:44:00 GMT
    • 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

      #3; Tue, 11 Dec 2007 17:45:00 GMT
    • Sorry, but I don't know what you mean?!!

      === Original Words ===

      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

      #4; Tue, 11 Dec 2007 17:46:00 GMT
    • 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

      #5; Tue, 11 Dec 2007 17:47:00 GMT
    • 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...

      === Original Words ===

      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

      #6; Tue, 11 Dec 2007 17:48:00 GMT
    • 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

      #7; Tue, 11 Dec 2007 17:49:00 GMT
    • 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

      #8; Tue, 11 Dec 2007 17:50:00 GMT
    • 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 ..

      === Original Words ===

      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

      #9; Tue, 11 Dec 2007 17:51:00 GMT
    • 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.wss?rs=71&context=SSEPGG&q=SQL22212N&uid=swg1JR18099&loc=en_US&cs=utf-8&lang=en+en

      #10; Tue, 11 Dec 2007 17:52:00 GMT