Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / DB2 Topics / December 2005

Tip: Looking for answers? Try searching our database.

TCP/IP Error, rc1=22

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Anurag - 27 Dec 2005 11:14 GMT
ENVIRONMENT:
________________________________________________________
"Server 1" = DB2 UDB ESE 7.1 FP7 on AIX 5.1
"Server 2" = DB2 UDB ESE 8.1 FP2 on AIX 5.1
________________________________________________________

SCENARIO:
___________________________________________________________________________
1) I catalog tcpip node ("Server 2") & database "db_test" on "Server 1"

   from "Server 2".
2) An attempt to connect to database "db_test" from "Server 1" gives
  "SQL30081N........ Protocol specific error code(s): "22", "*", "*"

3) I have checked all the basics - SVCENAME, DB2COMM etc.
4) I can connect to lot of other DB2 UDB ESE 8.1 FP2 databases from
  "Server 1".
5) I can connect to "db_test" database from my windows machine with
  DB2 UDB ESE 8.2
___________________________________________________________________________

QUESTION:
___________________________________________________________________________
"Server 2" settings are ok - can connect to it from lot of machines.
"Server 1" settings are ok - I have cataloged a whole range of
databases (v7, v8) and successfully connect.

So, what could be the possible reason of this TCP/IP communication
failure? Any hints as to what does "rc1=22" mean?

Many thanks and wish you a festive season....Anurag
P.S. - "Server 1" is dev and "Server 2" is Production
mike_li - 27 Dec 2005 22:27 GMT
Try to drop the node server 2 and test_db from server 1.
Then use db2ca to help you catalog node and db.
Try again.

If it fails again, then i think you need to upgrade Server 1 to ESE 8 .

mike

> ENVIRONMENT:
> ________________________________________________________
[quoted text clipped - 28 lines]
> Many thanks and wish you a festive season....Anurag
> P.S. - "Server 1" is dev and "Server 2" is Production
Mark Yudkin - 28 Dec 2005 07:25 GMT
There are very serious restrictions on accessing DB2 V7 servers from DB2 V8
clients. Basically, it doesn't work unless you're very very careful, and
even then it only just works on the odd occasion. If you absolutely must go
this route, read the documentation carefully and try to lower your voice
during the utterance of the expletives.

Upgrading Server 1 to V8 is the best route.

> ENVIRONMENT:
> ________________________________________________________
[quoted text clipped - 28 lines]
> Many thanks and wish you a festive season....Anurag
> P.S. - "Server 1" is dev and "Server 2" is Production
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.