one of our dev systems that has Registry, VSE and Workstation has a corrupted derby DB..
how do I start over with the derby db without product re-install?
I don't find that in the doc.
Looks like you are using the default Derby database. If you rename the existing lisa.db folder to something else in the DevTest/database folder and then restart the Registry...it should create a fresh lisa.db folder with the required files and you should be all set.
well.. maybe not..I'm checking to see if this user has lisa.user.properties file (shared install)
Configuring logging from 'C:\PROGRA~1\CA\DevTest\logging.properties'
DevTest Solutions, Copyright (c) 2002-2015 CA, All rights reserved.
DevTest Solutions Version :: 8.1.0 (188.8.131.523)
Installed patches: none
ACL enabled: true
Creating a DevTest Registry, name=Registry
Wed Jul 22 09:19:13 EDT 2015 : Apache Derby Network Server - 10.8.3.0 - (1405108) started and ready to accept connections on port 1528
The database has not been initialized correctly. There is at least one missing table.
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)
at com.exe4j.runtime.WinLauncher.main(Unknown Source)
at com.install4j.runtime.launcher.WinLauncher.main(Unknown Source)
No new lisa.db folder created in ..Ca\devtest\database folder
works on my machine, doesn't work on the other users system .. both cases running registry from admin commandline on windows. running 8.1.0
When 'the other user' installed DevTest initially, did he use the default name (lisa.db) for the database or did he give a custom name? If it is a custom name, then -
1. that custom database name should be commented out as that is corrupted
2. and then on Registry restart it will recreate the same name database.
If it works in your environment, then there is something else going on in his environment....
thanks.. he used the default, debug later
Retrieving data ...