Question The open database table is full

[palam]

When we are trying to compile the 4gl code, we got the error message below. We are using 11.7 64 bit progress version.
5 database instance here, last one didn't connected properly. 5th no db not connected.

[PCTCompile] Unable to connect to -db calldata -N TCP -S CALLDATA12.5.1 -ld calldata -H DEV-BLDAGT-VM3
[PCTCompile] The open database table is full, increase the -h parameter. (1415)

Would you please help us in this regard.

Thanks,
P. Alam

 

[TomBascom]

Have you increased -h yet?

 

[palam]

Thanks for your reply. We have added these way in strat.bat file

call C:\Progress\OpenEdge\bin\_MPROSRV C:\DB64BIT-12.5.1\CALLDATA -S CALLDATA12.5.1 -N tcp -spin 6000 -L 5000 -B 16000 -n 1000 -lruskips 100 -omsize 350 -Mn 200 -Mpb 50 -Ma 100 -ServerType 4GL -minport 35000 -maxport 35500 -h 200

And in build XML

<DBConnection id="db5" dbName="calldata" hostname="XXXXXXX" protocol="TCP" dbPort="CALLDATA12.5.1" dbDir="C:\DB64BIT-12.5.1" />

thanks

 

[Rob Fitzpatrick]

I don't understand what you are doing.

call C:\Progress\OpenEdge\bin\_MPROSRV

This batch file command runs a primary database broker for a database called calldata. You reported that you had a problem with your compile client, that it throws an error that it cannot connect to all of the databases it is attempting to connect to.

The -h parameter is a client startup parameter, not a database broker parameter. If specified for a broker, it will either be ignored or you will get an error; I haven't tested which will happen but it isn't important. You need to specify the -h parameter on the client that is reporting the error. Also, a value of 200 seems a little excessive.

Your broker parameters don't make a lot of sense either, but that is a topic for another thread.

 

[palam]

@Rob Fitzpatrick thanks for your comments. So how we specify the -h parameter in the compile client XML file.

Same databases use another machine without issues. Using windows server 2016.

 

[Rob Fitzpatrick]

The problem is not with the database. The issue is on the client side.

By default, an OpenEdge client can connect to up to five databases concurrently. This is a soft limit, it can be increased by specifying a higher value with the -h client startup parameter.
E.g.:

mpro -db db1 -db db2 -db db3 -db db4 -db db5                 # this works
mpro -db db1 -db db2 -db db3 -db db4 -db db5 -db db6         # this doesn't work; error 1415
mpro -db db1 -db db2 -db db3 -db db4 -db db5 -db db6 -h 6    # this works

You need to specify the -h parameter and its value on the OpenEdge client command line. That command could be an executable name (e.g. _progres.exe or prowin.exe) or it could be a client startup batch file, like pro, mpro, bpro, or mbpro. I don't know how that is done in PCT. Maybe if you post the entire XML configuration file we con figure it out.

 

[palam]

Hi @Rob Fitzpatrick thanks for your time to helping us. Attached here our apache ant script where we are trying to run the script to compile for progress 4gl code build. Always first 4 db are connected but last one didn't connected. And shows the error below.

[PCTCompile] Unable to connect to -db calldata -N TCP -S CALLDATA12.5.1 -ld calldata -H DEV-BLDAGT-VM3
[PCTCompile] The open database table is full, increase the -h parameter. (1415)

BUILD FAILED
C:\Users\jazzlab\Desktop\progress-build-demo\JAZZ\db-build.xml:149: The following error occurred while executing this line:
C:\Users\jazzlab\Desktop\progress-build-demo\JAZZ\db-build.xml:85: Return code : 14

 

[TomBascom]

I think that you should probably be talking to Gilles @ Riverside to determine how to configure PCT for your purpose.

 

[Rob Fitzpatrick]

Attached here our apache ant script

Attachment?

 

[Stefan]

You need to add "-h 6" (or however many entries you need) as option.

 

[palam]

@Stefan thanks for your comments. We didn't know where we set up this parameter. Eventually we found the path where added -h 6 parameter.
The path is C:\Progress\OpenEdge\startup.pf. Now its working.

Thanks everyone for your time.

 

[Stefan]

@Stefan thanks for your comments. We didn't know where we set up this parameter. Eventually we found the path where added -h 6 parameter.
The path is C:\Progress\OpenEdge\startup.pf. Now its working.

Find <pct:compile> or the <PCTCompile> element in your build.xml and add it there (hint: it is on line 149 of db-build.xml). Since your build.xml is covered by version control, you will not lose the change accidentally.

Adding it to startup.pf just means you need to remember to add it to all installations where it is needed.