Hi,
The derby.properties file needs to be in the dir where you start your 'java' command. Should be the same place where your derby.log shows up now.
Myrna
Zahra Zahid wrote:
Ok i added the values in derby.properties file ...n placed it at C:/DERBY/TRUNK....here how my properties file lookssss.... derby.system.home =C:\derby\trunk derby.connection.requireAuthentication=true derby.user.omar=omar derby.stream.error.logSeverityLevel=0
derby.language.logStatementText=true
I am still getting the same!!! OMAR schema not found...but it doesnt show in derby.log file .... Am i placing the cerby.properties file in the rite place... or shud i place it wid in the application!!! i.e. OMAR!!!
regards Zahra
Derby doesn't have a CREATE USER command and its built-in user support is only for authentication, it does not affect schema creation. If you are using CREATE SCHEMA OMAR in the database just created and you are still seeing the no such schema exception then it would be a bug.
The best approach is to set this property so that all errors are reported to the derby.log file. derby.stream.error.logSeverityLevel=0
The log file should include a stack trace of what is failing.
Adding this property might also help in seeing what SQL statement is causing the problem. derby.language.logStatementText=true
These would be set by either adding these two lines to the derby.properties file (create one if needed)
derby.stream.error.logSeverityLevel=0 derby.language.logStatementText=true
or starting the JVM with these two additional arguments - -Dderby.language.logStatementText=true - -Dderby.stream.error.logSeverityLevel=0
Dan. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFBXASdIv0S4qsbfuQRArQgAKDT/PxeVzLKzSFQwQsqAwIAMl28ngCfcwME LsdWXEUDPirztZEZrpYLms0= =sr8V -----END PGP SIGNATURE-----
