Changing the permission of .lisa.properties.lock, .local.properties.lock and .site.properties.lock files in $LISA_HOME/locks directory will avoid the "Database Error" dialog and the error messages workstation.log, but these files are used for interprocess concurrency. So changing the permission of these files can't be recommended.
If the Linux user for starting DevTest Workstation can be "root", then using the "root" user for starting DevTest Workstation is one of the solutions.
But if the Linux user for starting DevTest Workstation must not be "root", then solutions are based on the Installation Type when installing. There are two Installation Types like below:
- If DevTest was installed with Local Installation Type (Default Installation Type), then please uninstall DevTest and install DevTest with Shared Installation Type.
- If DevTest was installed with Shared Installation Type, then please check if the Linux user which started DevTest Workstation has the lisa.user.properties file in $USER_HOME.
If the Linux user does not have lisa.user.properties file in $USER_HOME, then
|A.||Copy lisa.user.properties file from the $LISA_HOME to $USER_HOME|
|B.||Open the $USER_HOME/lisa.user.properties file by using a text editor|
|C.||In the $USER_HOME/lisa.user.properties file, the property named lisa.data.dir is defined as $LISA_HOME directory, so change this value to the directory that the Linux user has the write access|
|D.||Save the $USER_HOME/lisa.user.properties file|
If the Linux user has lisa.user.properties file in $USER_HOME, then
|E.||Open the $USER_HOME/lisa.user.properties file by using a text editor|
|F.||Change the lisa.data.dir value to the directory that the Linux user has the write access|
If the same problem occurs in the Windows Operating System, the resolution of the problem is almost the same except for the way the file system is represented, the way the environment variables are represented and the "Administrator" user ("root" user in Linux).