If you restart the server while an action is being performed
on the database, the server restart may fail. You will see a message similar to
the following in the SystemOut log files: "java.lang.Exception:
BMXAA6454E - Database configuration is in process.
The ConfigDB and RestoreFromBackup action s must complete
before the Maximo server can start.
Or sometime It is
possible for configdb to leave a flag set, which can stop Maximo from starting.
Run the following SQL
select * from MAXVARS where varname='CONFIGURING';
Check the VARVALUE returned. It will be a '1' to signify
that configdb is running . If it is not, then do not continue and call into
support to report the error.
update MAXVARS set varvalue='0' where varname='CONFIGURING';
This will reset the flag that signifies configdb to be
running.
Maximo should now start.
Do you think maybe we should re-run configdb so that the script will clear the configdb flag in the database? Why would you want to start Maximo without finishing the required changes via configdb?
ReplyDeleteHi Sunk;
ReplyDeleteI have explained both the option, But some time When you run database configuration, it will show you nothing to configure, and when you start server you get this error. Then to fix it we need to follow the procedure.
I ran into a situation where I erased default fields on a custom Maximo table before I ran configdb. ConfigDB finished with errors and the update query with varvalue=0 helped.
ReplyDelete