Setting appropriate values for the database parameters based on the actual needs can reduce the occurrence of database deadlock and block hence can improve the concurrency and stability of the Web application.
Specify the timeout period for the commands. In the following table, it shows how to set Command Timeout to 120 seconds in different databases.
Table 4. Command timeout settings in different databases
|
Database Type |
Parameter |
Remark |
|---|---|---|
|
SAP ASA/SQL Anywhere |
BLOCKING_TIMEOUT |
Execute the following command: SET OPTION Public.BLOCKING_TIMEOUT = 120000 |
|
ASE |
lock wait period |
Execute the following command: sp_configure "lock wait period", 120 |
|
SQL Server |
- |
Modify the Command Timeout parameter in Edit Data Source page of AEM. Command Timeout = 120 |
|
Oracle |
IDLE_TIME |
Execute the following command: ALTER PROFILE default LIMIT IDLE_TIME 2; |
|
Informix |
DEADLOCK_TIMEOUT |
Modify the DEADLOCK_TIMEOUT parameter in ONCONFIG.std file. DEADLOCK_TIMEOUT = 120 |
|
Teradata |
- |
Modify the Command Timeout parameter in Edit Data Source page of AEM. Command Timeout = 120 |
