Kbase P19052: Too small a value for -L Lock Table entries may cause No Schema error when connect via SQL92
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/5/2010 |
|
Status: Verified
SYMPTOM(s):
Errors connecting to database via SQL Explorer
SQLState=HY000
ErrorCode=-211019
[JDBC Progress Driver]:No SQL schema found in database ( run mkschema ).
java.lang.UnsatisfiedLinkError:
java/security/AccessController.doPriveleged. Possible causes: If you are trying to use J/Direct (@dll.import), check your compiler version (for JVC, requires 4336 or greater.) If you are trying to use RNI, there are new requirements: see documenation
Error in database log file
Lock table overflow, increase -L on server (915)
Running mkschema gives error
mkschema failed: Error: mkschema was already run for this database.
(Error code -210046)
FACT(s) (Environment):
All Supported Operating Systems
CAUSE:
Database is being started with the -L set too low. SQL connections require share locks to the SQL Schema tables. If the locks are not obtained to all tables, then the connection does not recognize that mkschema was run. For example, if connecting to a copy of a sports database that was started with a -L lower than 100, you will receive the above errors.
FIX:
The default value for Lock Table entries is 8192. Either increase the value or allow the database to accept the default value.