Maximo Open Forum

I attempted to do a migration from a DEV environment to a TEST environment using Migration Manager.

The migration failed with an error, and the server then "thought" that database configuration was still happening.  It would not allow the Maximo UI server to be restarted.

I had to manually update the flag that indicated a DB Config was in process, after which Maximo server did start up.

The issue is that now the work order table is totally empty of records... associated tables such as wostatus, etc still do contain records.

The table that I was doing the configuration changes to was the work order table.
The question I have for the group, have you ever seen were a failed deployment of a migration package has cause Maximo database data to be deleted?

thanks
Steve H.

OK I learned something new about Maximo yesterday... when doing a database configuration, the table that is being updated is copied to a temporary table called XXtablename (in this case XXWORKORDER).  

On the Maximo server there are a series of small command files that will help correct the situation when your DB Config goes awry.  In the following folder on the server  install_home\tools\maximo  there are three tools that will help in the situation I found myself.

In all cases the Maximo Application Server needs to be stopped to run the commands

configdb.bat it can be used to run database configuration
restorefrombackup.bat is the command that will copy the XX table back into the main table (in my case XXWORKORDER  copied into WORKORDER.
dropbackup.bat to get rid of the backup table once it has been restored.

I needed to learn how to do this, because to be honest I cannot remember the last time a database configuration went sideways.

Here is the link to the page that helped me correct things.
https://maximobymanoj.blogspot.com/2015/01/how-to-recover-failed-database.html

I attempted to do a migration from a DEV environment to a TEST environment using Migration Manager.

The migration failed with an error, and the server then "thought" that database configuration was still happening.  It would not allow the Maximo UI server to be restarted.

I had to manually update the flag that indicated a DB Config was in process, after which Maximo server did start up.

The issue is that now the work order table is totally empty of records... associated tables such as wostatus, etc still do contain records.

The table that I was doing the configuration changes to was the work order table.
The question I have for the group, have you ever seen were a failed deployment of a migration package has cause Maximo database data to be deleted?

thanks
Steve H.

OK I learned something new about Maximo yesterday... when doing a database configuration, the table that is being updated is copied to a temporary table called XXtablename (in this case XXWORKORDER).  

On the Maximo server there are a series of small command files that will help correct the situation when your DB Config goes awry.  In the following folder on the server  install_home\tools\maximo  there are three tools that will help in the situation I found myself.

In all cases the Maximo Application Server needs to be stopped to run the commands

configdb.bat it can be used to run database configuration
restorefrombackup.bat is the command that will copy the XX table back into the main table (in my case XXWORKORDER  copied into WORKORDER.
dropbackup.bat to get rid of the backup table once it has been restored.

I needed to learn how to do this, because to be honest I cannot remember the last time a database configuration went sideways.

Here is the link to the page that helped me correct things.
https://maximobymanoj.blogspot.com/2015/01/how-to-recover-failed-database.html

I attempted to do a migration from a DEV environment to a TEST environment using Migration Manager.

The migration failed with an error, and the server then "thought" that database configuration was still happening.  It would not allow the Maximo UI server to be restarted.

I had to manually update the flag that indicated a DB Config was in process, after which Maximo server did start up.

The issue is that now the work order table is totally empty of records... associated tables such as wostatus, etc still do contain records.

The table that I was doing the configuration changes to was the work order table.
The question I have for the group, have you ever seen were a failed deployment of a migration package has cause Maximo database data to be deleted?

thanks
Steve H.

I attempted to do a migration from a DEV environment to a TEST environment using Migration Manager.

The migration failed with an error, and the server then "thought" that database configuration was still happening.  It would not allow the Maximo UI server to be restarted.

I had to manually update the flag that indicated a DB Config was in process, after which Maximo server did start up.

The issue is that now the work order table is totally empty of records... associated tables such as wostatus, etc still do contain records.

The table that I was doing the configuration changes to was the work order table.
The question I have for the group, have you ever seen were a failed deployment of a migration package has cause Maximo database data to be deleted?

thanks
Steve H.