Kbase P141445: Initial connection to the schema holder is very slow from the ABL client in a client/server environm
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
23/02/2009 |
|
Status: Unverified
SYMPTOM(s):
Initial connection to the schema holder is very slow from the ABL client in a client/server environment
FACT(s) (Environment):
Schema holder is running as a server using -H, -S and -N
The DataServer is also on a remote machine
Only Client Networking is installed on the client machine
All Supported Operating Systems
DataServers
Progress 9.1x
OpenEdge 10.x
CAUSE:
In a client/server environment to both schema holder and the DataServer there are two tcp connections involved, which can make make the connections little slower than the non client/server environment.
Also, the 4GL/ABL client caches the schema as well as verifies the foreign database schema by sending the OCI (for oracle) /ODBC (for SQL Server and ODBC DataServer) call to the foreign database. This can cause noticeable delay during the initial connections. If the "-Dsrv skip_schema_check" without the double quotes is used during the 4GL/ABL startup parameter for the DataServer, this stops the DataServer from sending SQL describe call to validate the tables on the schema holder to the foreign database. This saves the overhead time for the schema verification process. This DataServer switch should be used only on the production environment or during the stress test for the application performance where the changes to schema holder are minimum. Using the -Dsrv skip_schema_check on the development environment may corrupt the foreign database records.
FIX:
In order to reduce the initial connection time you can use the following configuration:
1. Create schema holder on the client and connect to the schema holder using -RO mode. You do not need to run the schema holder as a server. On the multiple windows environment, keep the schema holder on the network drive and connect to it as -RO.
2. If the schema holder runs as a server, create a schema holder cache file and keep it on the one location on the client and using -cache to connect to it.
3. Use *-Dsrv skip_schema_check* to stop the schema verification between client schema and server (foreign database) schema. (use this parameter only on the environment where schema changes are very minimum).