Search results

We're running a large scale Intel platform with Red Hat. Quad Intel Xeon 2.8 Gz MP, 16 GB RAM, attached to a midsize 2GB SAN. It has the best performance our ERP vendor has ever seen. We can sustain 125K locks per second under this configuration with approximately 1.5GB updates per minute...

I would strongly suggest upgrading to 91D09. We had crashes related to SQL pulls for years. Our database is finally stable after this release came out.

Under the Advanced Tab in your ODBC Config, you need to set it to Read Uncommited. The default value is for Read Commited. Progress treats the Read Commited as a Table Scan and locks ever row of a table on a query when this is used. We have two configured connections and use the updates for...

It sounds like the dbbroker is not set for sql connections. This has to be done on the server side. Make sure you have your minservers and maxservers assigned correctly for the connections as well. I have normally seen the error in network daemon when the port connecting to did not have sql...

Raj, First Setup the DB with access for Both SQL and 4GL. Determine the port communicating to the DB. Verify you have a sysprogress login or other SQL logins to the DB. There are support docs at Progress's site to help with this. Setup the client to connect the the DB on the port...

That is the beauty of the utility. Are you using NxTrends SX.Enterprise? If so, you can go to customer care and download a document, "Fixing SQL Lengths with dbtool". I think that's the name. This tool can be run while the database is up and can analyze the entire database. This will...

Your SQLLength value is too short. Progress allows variable lenght data behind the scenes. The length of a fields data exceeds the defined length to be returned from SQL. There is a progress utility called dbtool that can analyze the configuration of your database and reset the lengths for...

Your lock table entries is set too low for the ODBC connection. You need to adjust the parameter for the Progress database for the connections. You may also need to adjust the number of server that can attach odbc. Other issues to verify; 1. Login Authentication 2. appbroker setting for...

You may also change your SASO security to allow stocking of catalog items. Then place an OE for the items. You will be prompted as to whether you want the catalog item converted to a stock.