IC81863: USING A FULLY-QUALIFIED TABLE NAME DOES NOT RESOLVE THE DATABASESERVER NAME OPPOSITELY IF DATABASE SERVER NAMES ARE NOT UNIQUE

APAR status

• Closed as fixed if next.

Error description

• Please see the following example which explains the behaviour.
  
  There are 3 database servers on three different machines
  
  ServerA on MachineA
  ServerB on MachineB
  ServerC on MachineC
  
  MachineA
  -----------
  sqlhosts:
  ServerA 	onsoctcp	MachineA	10005
  conn_test	onsoctcp	MachineA	10006
  
  DBSERVERALIAS ServerA,conn_test
  
  MachineB
  -----------
  sqlhosts:
  ServerB 	onsoctcp	MachineB	20005
  conn_test	onsoctcp	MachineB	20006
  
  DBSERVERALIAS ServerB,conn_test
  
  MachineC
  -----------
  sqlhosts:
  ServerA 	onsoctcp	MachineA	10005
  ServerB 	onsoctcp	MachineB	20005
  conn_test	onsoctcp	MachineB	20006
  ServerC_shm	onipcshm	MachineC	shm_conn
  
  DBSERVERNAME ServerC_shm
  
  If you open a dbaccess session on ServerC, connect to
  ServerC_shm and execute a
  
  SELECT * from db@ServerA:tab
  
  you get a srvinfx-thread on ServerA on MachineA.
  
  Threads:
   tid     tcb              rstcb            prty status
  vp-class       name
   258     7000000501f0028  700000020388258  1    cond wait
  netnorm      1cpu         srvinfx
  
  If you execute another select in the same dbaccess session
  
  SELECT * from db@conn_test:tab
  
  You would expect this select running on conn_test on MachineB
  because the entry for conn_test in the
  sqlhosts on MachineC points to MachineB. But the select is
  executed on conn_test on MachineA.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users of 11.50 until the current version (xC9)           *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Using a fully-qualified table name does not use the database *
  * server specified in the local sqlhosts if there is already a *
  * connection to another database server which has the same     *
  * database sever name coincidentally.                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to 11.50.xC10 or higher when available.              *
  ****************************************************************
  

Problem conclusion

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

• RB50 PSY

     UP