DB2/UDB on UNIX:

[user001]

Quick Question:

If I have an instance of UDB/DB2 on a UNIX box, can I have it act as
something like a load balancer, where all it's doing is sending the SQL
traffic out to another DB2 instance? So the traffic would look like:
client --> DBInst1 --> DBinst2 --> DBInst2.database

Thanks for any thoughts.

[Larry]

Can I ask why you would want to do this? Is this an application
requirement? Why wouldn't you use the new connection concentrator function
that is built natively into DB2 UDB? It allows you to maintain a limit on
the number of concurrently executing agents while servicing the same number
of connections (some become inactive).

Larry Edelstein

user001 wrote:

Quick Question:

If I have an instance of UDB/DB2 on a UNIX box, can I have it act as
something like a load balancer, where all it's doing is sending the SQL
traffic out to another DB2 instance? So the traffic would look like:

client --> DBInst1 --> DBinst2 --> DBInst2.database

Thanks for any thoughts.

[Gert van der Kooij]

In article <bV*****************@news4.srv.hcvlny.cv.net>, user001
@aol.com says...

Quick Question:

If I have an instance of UDB/DB2 on a UNIX box, can I have it act as
something like a load balancer, where all it's doing is sending the SQL
traffic out to another DB2 instance? So the traffic would look like:
client --> DBInst1 --> DBinst2 --> DBInst2.database

That shouldn't be a problem. You need to catalog DB2inst2.database as
local database within DBInst1 and catalog this DB2inst1 database at
the client.