CONNECT Statement on a UNIX server

M

m25tp

New Member
Hello, I need your help, please!

Progress 9.1d

Here is the deal, I use the CONNECT Statement to connect to different databases on running time, when I do that on Windows XP I have no problem, I can connect to several databases, but when I run it on a Unix server I just can connect to 2 o or 3 DB's. I need to connect to 7 DB's.

I disconnect each database after I use it, and I don't connect DB's concurrently, i mean, i connect to a DB and disconnect it before I use another one.

I hope you understood me, my english is not so good... Thanks!!
 
What exact error message do you get on the Unix machine?

The limit on how much database you can connect in one Progress session is not OS dependent. AFAIK the default limit is 5 - but you can increase it in supplying the -h (lower case) parameter.

HTH, RealHeavyDude.
 
RealHeavyDude said:
What exact error message do you get on the Unix machine?

The limit on how much database you can connect in one Progress session is not OS dependent. AFAIK the default limit is 5 - but you can increase it in supplying the -h (lower case) parameter.

HTH, RealHeavyDude.
Click to expand...

Yes, you are right, thanks!!

I got the message 1415: "The open database table is full, increase the -h parameter. (1415)
Progress cannot open additional databases. To open another database you must either close one that is currently open or increase the -h parameter on the command line."

I had to spread the error message because my app is running on an AppServer.

But, where do i have to modify the -h parameter? do i have to modify it where set the -db parameter?

Again, Thank you so much!!
 
In your original post it sounds like your intention is to connect to these databases sequentially, not concurrently. If so, the reason you are getting this error is because they are failing to disconnect. There is no limit to the number you can connect to sequentially.
 
The progress documentation mentions "By default, the AVM disconnects all databases at the end of a session. The DISCONNECT statement, which explicitly disconnects a database, does not execute until all active procedures that reference the database end or stop. "

My code is sth like this:

proc1.p

connect db1 -ld lgdb1.
run sth.p.
disconnect lgdb1.

connect db2 -ld lgdb2.
run sth.p.
disconnect lgdb1.

and so on...

So I guess that the db's don't get disconnected at all until the procedure proc1.p finish. What do you think?
 
Correct. You want to nest your connections and return to the calling program after each disconnect to actually release the DB. I'm a bit surprised this hasn't caused more issues than it has.
 
You must log in or register to reply here.
Back
Top