federation windows-aix

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

hikums@gmail.com - 14 Feb 2005 22:28 GMT

By mistake, posted in informix group..Here it is now...

On Windows:
In db abc:
1. create wrapper drda
(LIBRARY LIBDB2DRDA.a not available in windows box)
2. CREATE SERVER "AIX" TYPE DB2/AIX VERSION 8.1 WRAPPER "DRDA"
AUTHORIZATION xxxxxxxx PASSWORD xxxxxxxx OPTIONS ( DBNAME 'DFP' );
3. If the above steps are through, probably user mapping/nicknames are
straight forward.

The create server step is failing as drda is not valid for aix.

What steps should be followed, please elaborate with examples.

Database abc on windows has same tables on aix, should be able to
flip/flop between both located on different servers(windows/aix), db2
is version 8.1.

Reply to this Message

hikums@gmail.com - 14 Feb 2005 22:30 GMT

SQL1822N Unexpected error code "-30082" received from data
source "AIX". Associated text and tokens are
"func="DriverConnect" msg=" SQL30082N Attempt to establ".

Explanation:

While referencing a data source, the federated server received an
unexpected error code from the data source that does not map to a
DB2 equivalent.

Possible error codes include:

o 4901 Trying to open more than 15 cursors

o 4902 Row size exceeds 32K limit

This error might also be returned if the data source is not
available.

User Response:

Ensure the data source is available, then identify and correct
the root cause of the problem by locating the appropriate message
text and corrective action for the specified error at the data
source.

sqlcode : -1822

sqlstate : 560BD

Reply to this Message

Knut Stolze - 15 Feb 2005 07:55 GMT

> SQL1822N Unexpected error code "-30082" received from data
> source "AIX". Associated text and tokens are
> "func="DriverConnect" msg=" SQL30082N Attempt to establ".

$ db2 "? sql30082"

SQL30082N Attempt to establish connection failed with security
reason "<reason-code>" ("<reason-string>").

As Larry guessed, you can't connect to the remote data source/DB2 instance.
(The exact error message is probably in the db2diag, depending on your
DIAGLEVEL.)

Is your user-name/password case-sensitive? If it is, you might want to
enclose it in double-quotes.

Signature

Knut Stolze
Information Integration
IBM Germany / University of Jena

Reply to this Message

hikums@gmail.com - 15 Feb 2005 15:14 GMT

aix node/db is already cataloged in the windows server.

In windows db,
1. There is only option to choose wrapper library db2drda.dll
2. While creating server on windows, there is no errors if I create as
Type DB2/UDB
3. If I do as above, and create username mapping--here I specify
userid/password for aix. and then nickname, while I issue a
select-still I get sqlcode 30082.
4. If I give the username/pass used in windows for this db, it works
well and accesses windows. If I give the aix username/pass, I get
sqlcode 30082.

I can do successfully -Ping, connect to db etc

Error message is

hik...@gmail.com Feb 14, 2:30 pm show options

Newsgroups: comp.databases.ibm-db2
From: hik...@gmail.com - Find messages by this author
Date: 14 Feb 2005 14:30:50 -0800
Local: Mon, Feb 14 2005 2:30 pm
Subject: Re: federation windows-aix
Reply | Reply to Author | Forward | Print | Individual Message | Show
original | Remove | Report Abuse

SQL1822N Unexpected error code "-30082" received from data
source "AIX". Associated text and tokens are
"func="DriverConnect" msg=" SQL30082N Attempt to establ".

Explanation:

While referencing a data source, the federated server received an
unexpected error code from the data source that does not map to a
DB2 equivalent.

Possible error codes include:

o 4901 Trying to open more than 15 cursors

o 4902 Row size exceeds 32K limit

This error might also be returned if the data source is not
available.

User Response:

Ensure the data source is available, then identify and correct
the root cause of the problem by locating the appropriate message
text and corrective action for the specified error at the data
source.

sqlcode : -1822

sqlstate : 560BD

Reply to this Message

Larry - 15 Feb 2005 16:45 GMT

30082 is a security error. Is there a complete SQL30082N msg with reason
code in your db2diag.log? It is likely related to the userid or pw being
passed to the backend server and whether the backend server considers
them valid or not. This can also happen due to the fact that UNIX is
case-sensitive.

Larry Edelstein

> aix node/db is already cataloged in the windows server.
>
[quoted text clipped - 52 lines]
>
> sqlstate : 560BD

Reply to this Message

hikums@gmail.com - 28 Feb 2005 14:14 GMT

Finally I resolved this by:
1. properly specifying remote server's credentials while running
"create server"
2. I had another issue(30082 error ) while I tried to "create nickname"
from control center. I tried running the same command from CLP and it
went fine.

Thanks Larry for your replies!!

> 30082 is a security error. Is there a complete SQL30082N msg with reason
> code in your db2diag.log? It is likely related to the userid or pw being
> passed to the backend server and whether the backend server considers

> them valid or not. This can also happen due to the fact that UNIX is
> case-sensitive.
[quoted text clipped - 57 lines]
> >
> > sqlstate : 560BD

Reply to this Message

Larry - 14 Feb 2005 23:36 GMT

What's your FEDERATED parameter set to in your dbm cfg?

Can you successfully access the remote database from your Federated
server using the DB2 client by issuing a DB2 Connect ?

Larry Edelstein

> By mistake, posted in informix group..Here it is now...
>
[quoted text clipped - 14 lines]
> flip/flop between both located on different servers(windows/aix), db2
> is version 8.1.

Reply to this Message

hikums@gmail.com - 15 Feb 2005 01:19 GMT

DBM parameter is set to a YES for federated.

We do not have DB2 connect, do we need it?
I am able to federate between different servers running on windows.

>From Windows-unix, or unix-windows, I am not able to.

> What's your FEDERATED parameter set to in your dbm cfg?
>
[quoted text clipped - 21 lines]
> > flip/flop between both located on different servers(windows/aix), db2
> > is version 8.1.

Reply to this Message

Larry - 15 Feb 2005 01:25 GMT

You don't need DB2 Connect. But you do need to be able to connect from
the machine that you are issuing the commands on (i.e. the Federated
Server) and the machine that you are trying to access (the backend data
source). The first thing you should do before doing anything else is
attempt to CONNECT from the Federated Server to the backend data source
without Federated support to see if you can establish connectivity and a
CONNECT. Can you ping it? And can you CONNECT to it (you need to
establish the proper catalog entries in order to CONNECT to it those
being the NODE and DB catalog entries ... you can do this at the command
line or use the Configuration Assistant)? If you can, then it proves
connectivity and then you'll need to do further analysis to find out
what the problem is. If you cannot, then post the exact error msg and
perhaps someone can help.

Larry Edelstein

> DBM parameter is set to a YES for federated.
>
[quoted text clipped - 33 lines]
>
>>>is version 8.1.

Reply to this Message