Product Support > SPECvirt_sc2013

invalid initial Mfg DB State

(1/2) > >>

tdeneau:
I am seeing this error consistently now on a 1-tile run, although I managed to do a successful one tile run yesterday.  I do always run jAppInitRstr.sh from client1 before starting the 1-tile specvirt run.

Exception encountered in auditor.validateInitialValues(). Aborting.
java.rmi.RemoteException: Failure in calling validateInitialValues() java.rmi.RemoteException: Invalid initial Mfg DB State


Do I need to rebuild the database on dbserver1?

Is there a quick way to discover this "invalid initial Mfg DB State" problem rather than waiting for it to happen during the specvirt run?

(I do check for Atomicity Tests before the run and those pass).

-- Tom

lroderic:
Tom, I've run into this error in the past. The only way I could get around it was to recreate and reload the entire dbserver. Sorry I don't have a better answer.

Lisa

tdeneau:
Yes, that's what I ended up doing.  Thanks.


--- Quote from: lroderic on January 09, 2017, 01:20:25 PM ---Tom, I've run into this error in the past. The only way I could get around it was to recreate and reload the entire dbserver. Sorry I don't have a better answer.

Lisa

--- End quote ---

AnoopGupta:
Reload the DB should work, recreate should not be necessary. Ensure you update your backup with the newly loaded db for restore to work after that.

tdeneau:
Anoop, what does "reload the DB" mean here?
I am only familiar with re-creating (which creates backup copy as well) and restoring it


--- Quote from: AnoopGupta on January 09, 2017, 03:05:03 PM ---Reload the DB should work, recreate should not be necessary. Ensure you update your backup with the newly loaded db for restore to work after that.

--- End quote ---

Navigation

[0] Message Index

[#] Next page