If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > Connection error in DB2 (SQL1334)

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 07-23-09, 05:16
Ruth karin Ruth karin is offline
Registered User
 
Join Date: Jul 2009
Posts: 3
Post Connection error in DB2 (SQL1334)

hi,
When i try connecting to DB2 I am getting the below error "SQL1334N The database server cannot be used to route a remote request to a second database server in this configuration."

I have tried uncatalog and catalog the db. but it didnt help me.
I am connecting thru TCP/IP protocol...and we are using DB version 7.2..

Pls help me to solve this issue.

Last edited by Ruth karin; 07-23-09 at 06:32.
Reply With Quote
  #2 (permalink)  
Old 07-23-09, 08:19
ARWinner ARWinner is offline
Registered User
 
Join Date: Jan 2003
Posts: 3,575
You get this error when trying to connect from a client to a DB on a server (serrver1) that is on another server that is remote to server1 (server2). This is not supported. What you need to do is this:

1) uncatalog the database on the client.
2) catalog the node to server2 on the client
3) catalog the database on the client using the node from step 2.

Andy
Reply With Quote
  #3 (permalink)  
Old 07-23-09, 10:29
Ruth karin Ruth karin is offline
Registered User
 
Join Date: Jul 2009
Posts: 3
Andy,

I have tried the steps which u ve given.. but stil im getting the same error...
Reply With Quote
  #4 (permalink)  
Old 07-23-09, 10:34
ARWinner ARWinner is offline
Registered User
 
Join Date: Jan 2003
Posts: 3,575
Please post the following:

1) OS and DB2 version of server 1
2) OS and DB2 version of server 2
3) OS and DB2 client version of client
4) output of "db2 list node directory" on server 1
5) output of "db2 list db directory" on server 2
6) output of "db2 list node directory" on server 2
7) output of "db2 list db directory" on server 2
8) output of "db2 list node directory" on client
9) output of "db2 list db directory" on client
10) network name/tcpip address of server1, and server 2

Andy
Reply With Quote
  #5 (permalink)  
Old 07-24-09, 01:27
Ruth karin Ruth karin is offline
Registered User
 
Join Date: Jul 2009
Posts: 3
In this case, client and server are same. I am trying to connect to DB2 to the same machine.

1) OS- windows 2003
2) DB2 version 7.2
3) node:

Node name = TCP0002
Comment = connecting to DB2 dev DB
Protocol = TCPIP
Hostname = 10.184.80.171
Service name = 50000
4) DB:

Database alias = EIPRPT
Database name = EIPRPT
Node name = TCP0002
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1

It was working two months back. When I try to connect 3days back I got the SQL1334N error. I don't know when it stopped working.. no change has been done in past 2 months.
Reply With Quote
  #6 (permalink)  
Old 07-24-09, 08:28
ARWinner ARWinner is offline
Registered User
 
Join Date: Jan 2003
Posts: 3,575
I think your problem is that you DB is local, but it is catalogged as remote.

Andy
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On