8.07 to 9.1 BSM Upgrade - Failed to perform update of profile dbs (879 Views)
Reply
Respected Contributor
Ben.Shirley
Posts: 487
Registered: ‎09-01-2009
Message 1 of 7 (879 Views)
Accepted Solution

8.07 to 9.1 BSM Upgrade - Failed to perform update of profile dbs

Hi,

 

Following the procedure on my test system I get the message 'Summary - Upgrade Failure - Upgrade process failed. Click finish to exit the wizard' when running the Upgrade wizard.  As per the attached screen capture. Since the update fails almost immediately after I imput the settings on the profile database, is there some kind of database consistency tool I can run to check the database beforehand?

 

 

Please use plain text.
Respected Contributor
Ben.Shirley
Posts: 487
Registered: ‎09-01-2009
Message 2 of 7 (875 Views)

Re: 8.07 to 9.1 BSM Upgrade - Failed to perform update of profile dbs

and the screen capture!

Please use plain text.
HP Expert
Dmitry Shevchenko
Posts: 4,785
Registered: ‎01-30-2008
Message 3 of 7 (867 Views)

Re: 8.07 to 9.1 BSM Upgrade - Failed to perform update of profile dbs


Ben.Shirley wrote:

 is there some kind of database consistency tool I can run to check the database beforehand?


HPBAC/DBVerify/bin/run_db_verify.bat

Please use plain text.
Respected Contributor
Ben.Shirley
Posts: 487
Registered: ‎09-01-2009
Message 4 of 7 (865 Views)

Re: 8.07 to 9.1 BSM Upgrade - Failed to perform update of profile dbs

Thanks Dmitry, I did manage to run this again and got a little further but after ages upgrading the schema the upgrade_wizard failed with the following (sorry for the paste) should I log a case?

 

The current schema is not compatible with version 8.0.0.0.
The repair scripts located in D:\HPBSM\dbverify\tmp\ may help resolve schema incompatibility.
Warning: Only use the repair scripts in coordination with Customer Support as running these scripts can result in data loss.
Problems found before partition switching:
Differences for DataBase [Profile]
TABLE
  Name:EM_ADD_INFO_290
  Table:
    name:[EM_ADD_INFO_290].problem[extra table]
TABLE
  Name:EM_ADD_INFO_291
  Table:
    name:[EM_ADD_INFO_291].problem[extra table]
TABLE
  Name:EM_ADD_INFO_292
  Table:
    name:[EM_ADD_INFO_292].problem[extra table]
TABLE
  Name:EM_ADD_INFO_294
  Table:
    name:[EM_ADD_INFO_294].problem[extra table]
TABLE
  Name:EM_ADD_INFO_293
  Table:
    name:[EM_ADD_INFO_293].problem[extra table]
TABLE
  Name:EM_ADD_INFO_296
  Table:
    name:[EM_ADD_INFO_296].problem[extra table]
TABLE
  Name:EM_ADD_INFO_295
  Table:
    name:[EM_ADD_INFO_295].problem[extra table]
TABLE
  Name:EM_ADD_INFO_280
  Table:
    name:[EM_ADD_INFO_280].problem[extra table]
TABLE
  Name:EM_ADD_INFO_281
  Table:
    name:[EM_ADD_INFO_281].problem[extra table]
TABLE
  Name:EM_ADD_INFO_285
  Table:
    name:[EM_ADD_INFO_285].problem[extra table]
TABLE
  Name:EM_ADD_INFO_284
  Table:
    name:[EM_ADD_INFO_284].problem[extra table]
TABLE
  Name:EM_ADD_INFO_283
  Table:
    name:[EM_ADD_INFO_283].problem[extra table]
TABLE
  Name:EM_ADD_INFO_282
  Table:
    name:[EM_ADD_INFO_282].problem[extra table]
TABLE
  Name:EM_ADD_INFO_289
  Table:
    name:[EM_ADD_INFO_289].problem[extra table]
TABLE
  Name:EM_ADD_INFO_288
  Table:
    name:[EM_ADD_INFO_288].problem[extra table]
TABLE
  Name:EM_ADD_INFO_287
  Table:
    name:[EM_ADD_INFO_287].problem[extra table]
TABLE
  Name:EM_ADD_INFO_286
  Table:
    name:[EM_ADD_INFO_286].problem[extra table]
TABLE
  Name:EM_ADD_INFO_270
  Table:
    name:[EM_ADD_INFO_270].problem[extra table]
TABLE
  Name:EM_ADD_INFO_279
  Table:
    name:[EM_ADD_INFO_279].problem[extra table]
TABLE
  Name:pm_native_catalog_bck1
  Table:
    name:[pm_native_catalog_bck1].problem[extra table]
TABLE
  Name:EM_ADD_INFO_276
  Table:
    name:[EM_ADD_INFO_276].problem[extra table]
TABLE
  Name:EM_ADD_INFO_275
  Table:
    name:[EM_ADD_INFO_275].problem[extra table]
TABLE
  Name:EM_ADD_INFO_278
  Table:
    name:[EM_ADD_INFO_278].problem[extra table]
TABLE
  Name:EM_ADD_INFO_277
  Table:
    name:[EM_ADD_INFO_277].problem[extra table]
TABLE
  Name:EM_ADD_INFO_272
  Table:
    name:[EM_ADD_INFO_272].problem[extra table]
TABLE
  Name:EM_ADD_INFO_271
  Table:
    name:[EM_ADD_INFO_271].problem[extra table]
TABLE
  Name:EM_ADD_INFO_274
  Table:
    name:[EM_ADD_INFO_274].problem[extra table]
TABLE
  Name:EM_ADD_INFO_273
  Table:
    name:[EM_ADD_INFO_273].problem[extra table]
TABLE
  Name:EM_ADD_INFO_269
  Table:
    name:[EM_ADD_INFO_269].problem[extra table]
TABLE
  Name:EM_ADD_INFO_268
  Table:
    name:[EM_ADD_INFO_268].problem[extra table]
TABLE
  Name:EM_ADD_INFO_267
  Table:
    name:[EM_ADD_INFO_267].problem[extra table]
TABLE
  Name:pm_catalog_bck1
  Table:
    name:[pm_catalog_bck1].problem[extra table]
PARTITIONING
  Name:EM_ADD_INFO_271_func
  Partition Function:
    name:[EM_ADD_INFO_271_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_267_func
  Partition Function:
    name:[EM_ADD_INFO_267_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_296_func
  Partition Function:
    name:[EM_ADD_INFO_296_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_291_func
  Partition Function:
    name:[EM_ADD_INFO_291_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_275_func
  Partition Function:
    name:[EM_ADD_INFO_275_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_282_func
  Partition Function:
    name:[EM_ADD_INFO_282_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_295_func
  Partition Function:
    name:[EM_ADD_INFO_295_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_281_func
  Partition Function:
    name:[EM_ADD_INFO_281_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_294_func
  Partition Function:
    name:[EM_ADD_INFO_294_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_279_func
  Partition Function:
    name:[EM_ADD_INFO_279_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_286_func
  Partition Function:
    name:[EM_ADD_INFO_286_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_280_func
  Partition Function:
    name:[EM_ADD_INFO_280_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_283_func
  Partition Function:
    name:[EM_ADD_INFO_283_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_273_func
  Partition Function:
    name:[EM_ADD_INFO_273_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_290_func
  Partition Function:
    name:[EM_ADD_INFO_290_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_272_func
  Partition Function:
    name:[EM_ADD_INFO_272_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_289_func
  Partition Function:
    name:[EM_ADD_INFO_289_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_293_func
  Partition Function:
    name:[EM_ADD_INFO_293_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_276_func
  Partition Function:
    name:[EM_ADD_INFO_276_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_278_func
  Partition Function:
    name:[EM_ADD_INFO_278_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_268_func
  Partition Function:
    name:[EM_ADD_INFO_268_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_285_func
  Partition Function:
    name:[EM_ADD_INFO_285_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_269_func
  Partition Function:
    name:[EM_ADD_INFO_269_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_288_func
  Partition Function:
    name:[EM_ADD_INFO_288_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_274_func
  Partition Function:
    name:[EM_ADD_INFO_274_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_284_func
  Partition Function:
    name:[EM_ADD_INFO_284_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_270_func
  Partition Function:
    name:[EM_ADD_INFO_270_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_287_func
  Partition Function:
    name:[EM_ADD_INFO_287_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_292_func
  Partition Function:
    name:[EM_ADD_INFO_292_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_277_func
  Partition Function:
    name:[EM_ADD_INFO_277_func].problem[extra partition function]
PARTITIONING
  Name:EM_ADD_INFO_296_sch
  Partition Function:
    name:[EM_ADD_INFO_296_sch].problem[extra partition scheme]
PARTITIONING
  Name:EM_ADD_INFO_284_sch
  Partition Function:
    name:[EM_ADD_INFO_284_sch].problem[extra partition scheme]
PARTITIONING
  Name:EM_ADD_INFO_267_sch
  Partition Function:
    name:[EM_ADD_INFO_267_sch].problem[extra partition scheme]
PARTITIONING
  Name:EM_ADD_INFO_281_sch
  Partition Function:
    name:[EM_ADD_INFO_281_sch].problem[extra partition scheme]
PARTITIONING
  Name:EM_ADD_INFO_271_sch
  Partition Function:
    name:[EM_ADD_INFO_271_sch].problem[extra partition scheme]
PARTITIONING
  Name:EM_ADD_INFO_293_sch
  Partition Function:
    name:[EM_ADD_INFO_293_sch].problem[extra partition scheme]
PARTITIONING
  Name:EM_ADD_INFO_273_sch
  Partition Function:
    name:[EM_ADD_INFO_273_sch].problem[extra partition scheme]
PARTITIONING
  Name:EM_ADD_INFO_289_sch
  Partition Function:
    name:[EM_ADD_INFO_289_sch].problem[extra partition scheme]
PARTITIONING
  Name:EM_ADD_INFO_287_sch
  Partition Function:
    name:[EM_ADD_INFO_287_sch].problem[extra partition scheme]
PARTITIONING
  Name:EM_ADD_INFO_270_sch
  Partition Function:
    name:[EM_ADD_INFO_270_sch].problem[extra partition scheme]
PARTITIONING
  Name:EM_ADD_INFO_291_sch
  Partition Function:
    name:[EM_ADD_INFO_291_sch].problem[extra partition scheme]
PARTITIONING
  Name:EM_ADD_INFO_282_sch
  Partition Function:
    name:[EM_ADD_INFO_282_sch].problem[extra partition scheme]
PARTITIONING
  Name:EM_ADD_INFO_290_sch
  Partition Function:
    name:[EM_ADD_INFO_290_sch].problem[extra partition scheme]
PARTITIONING
  Name:EM_ADD_INFO_278_sch
  Partition Function:
    name:[EM_ADD_INFO_278_sch].problem[extra partition scheme]
PARTITIONING
  Name:EM_ADD_INFO_272_sch
  Partition Function:
    name:[EM_ADD_INFO_272_sch].problem[extra partition scheme]
PARTITIONING
  Name:EM_ADD_INFO_292_sch
  Partition Function:
    name:[EM_ADD_INFO_292_sch].problem[extra partition scheme]
PARTITIONING
  Name:EM_ADD_INFO_294_sch
  Partition Function:
    name:[EM_ADD_INFO_294_sch].problem[extra partition scheme]
PARTITIONING
  Name:EM_ADD_INFO_295_sch
  Partition Function:
    name:[EM_ADD_INFO_295_sch].problem[extra partition scheme]
PARTITIONING
  Name:EM_ADD_INFO_285_sch
  Partition Function:
    name:[EM_ADD_INFO_285_sch].problem[extra partition scheme]
PARTITIONING
  Name:EM_ADD_INFO_279_sch
  Partition Function:
    name:[EM_ADD_INFO_279_sch].problem[extra partition scheme]
PARTITIONING
  Name:EM_ADD_INFO_283_sch
  Partition Function:
    name:[EM_ADD_INFO_283_sch].problem[extra partition scheme]
PARTITIONING
  Name:EM_ADD_INFO_286_sch
  Partition Function:
    name:[EM_ADD_INFO_286_sch].problem[extra partition scheme]
PARTITIONING
  Name:EM_ADD_INFO_288_sch
  Partition Function:
    name:[EM_ADD_INFO_288_sch].problem[extra partition scheme]
PARTITIONING
  Name:EM_ADD_INFO_277_sch
  Partition Function:
    name:[EM_ADD_INFO_277_sch].problem[extra partition scheme]
PARTITIONING
  Name:EM_ADD_INFO_269_sch
  Partition Function:
    name:[EM_ADD_INFO_269_sch].problem[extra partition scheme]
PARTITIONING
  Name:EM_ADD_INFO_274_sch
  Partition Function:
    name:[EM_ADD_INFO_274_sch].problem[extra partition scheme]
PARTITIONING
  Name:EM_ADD_INFO_280_sch
  Partition Function:
    name:[EM_ADD_INFO_280_sch].problem[extra partition scheme]
PARTITIONING
  Name:EM_ADD_INFO_268_sch
  Partition Function:
    name:[EM_ADD_INFO_268_sch].problem[extra partition scheme]
PARTITIONING
  Name:EM_ADD_INFO_276_sch
  Partition Function:
    name:[EM_ADD_INFO_276_sch].problem[extra partition scheme]
PARTITIONING
  Name:EM_ADD_INFO_275_sch
  Partition Function:
    name:[EM_ADD_INFO_275_sch].problem[extra partition scheme]

 

Differences for DataBase [CMDB]
TABLE
  Name:_1611$T8
  Table:
    name:[_1611$T8].problem[extra table]

 

Database Schema Operation Completed: Database schema operation terminated before all tasks were completed,
View the log file (located at:'D:\HPBSM\log\upgrade').

Please use plain text.
HP Expert
Dmitry Shevchenko
Posts: 4,785
Registered: ‎01-30-2008
Message 5 of 7 (858 Views)

Re: 8.07 to 9.1 BSM Upgrade - Failed to perform update of profile dbs


Ben.Shirley wrote:

I did manage to run this again and got a little further but after ages upgrading the schema the upgrade_wizard failed with the following (sorry for the paste) should I log a case?


If you have a backup copy of your DB then you can run the SQL scripts created by DBVerify on your own and see if it helps. If it doesn't - nothing prevents you from restoring the original DB and creating a support case.

Please use plain text.
Respected Contributor
Ben.Shirley
Posts: 487
Registered: ‎09-01-2009
Message 6 of 7 (852 Views)

Re: 8.07 to 9.1 BSM Upgrade - Failed to perform update of profile dbs

Thanks, I ran the scripts located in hpbsm\dbverify\tmp, it seemed to get past this point however the schema upgrade has been running for over four hours (largest db was only the profile one at 50GB+) not sure if it is working,the wizard still says 'Please wait' and the upgrade log is being written to, but only with:-

 

2011-10-09 10:50:15,469 [Keyed Object Pool Held Timeout Monitor] (ConnectionManager.java:772) INFO  - 1 Total active Connections, 0 Idle Connections.
 DbContext :  dbType=(SQL Server); hostName=hpbacsql; dbName=Profile; userName=hpbac; server=hpbacsql; sid=; port=1433
 Number of active connection :  1

2011-10-09 10:52:15,469 [Keyed Object Pool Held Timeout Monitor] (ConnectionManager.java:772) INFO  - 1 Total active Connections, 0 Idle Connections.
 DbContext :  dbType=(SQL Server); hostName=hpbacsql; dbName=Profile; userName=hpbac; server=hpbacsql; sid=; port=1433
 Number of active connection :  1

2011-10-09 10:54:15,469 [Keyed Object Pool Held Timeout Monitor] (ConnectionManager.java:772) INFO  - 1 Total active Connections, 0 Idle Connections.
 DbContext :  dbType=(SQL Server); hostName=hpbacsql; dbName=Profile; userName=hpbac; server=hpbacsql; sid=; port=1433
 Number of active connection :  1

2011-10-09 10:56:15,469 [Keyed Object Pool Held Timeout Monitor] (ConnectionManager.java:772) INFO  - 1 Total active Connections, 0 Idle Connections.
 DbContext :  dbType=(SQL Server); hostName=hpbacsql; dbName=Profile; userName=hpbac; server=hpbacsql; sid=; port=1433
 Number of active connection :  1

2011-10-09 10:58:15,469 [Keyed Object Pool Held Timeout Monitor] (ConnectionManager.java:772) INFO  - 1 Total active Connections, 0 Idle Connections.
 DbContext :  dbType=(SQL Server); hostName=hpbacsql; dbName=Profile; userName=hpbac; server=hpbacsql; sid=; port=1433
 Number of active connection :  1

2011-10-09 11:00:15,469 [Keyed Object Pool Held Timeout Monitor] (ConnectionManager.java:772) INFO  - 1 Total active Connections, 0 Idle Connections.
 DbContext :  dbType=(SQL Server); hostName=hpbacsql; dbName=Profile; userName=hpbac; server=hpbacsql; sid=; port=1433
 Number of active connection :  1

2011-10-09 11:02:15,469 [Keyed Object Pool Held Timeout Monitor] (ConnectionManager.java:772) INFO  - 1 Total active Connections, 0 Idle Connections.
 DbContext :  dbType=(SQL Server); hostName=hpbacsql; dbName=Profile; userName=hpbac; server=hpbacsql; sid=; port=1433
 Number of active connection :  1

 

 

etc...... etc....

 

 

Not sure if it is worth killing the upgrade, restoring and starting again. Log isn't very helpful.

 

According to the wizard, I still have 'Update Environment', 'CMDB Upgrade', 'Data Upgrade', 'Historic Data Upgrade' to go!

 

The db instances are still called CMDB and CMDB_History, I take it after the schema upgrade I will see these changed to RTSM, and RTSM_History?

Please use plain text.
HP Expert
Dmitry Shevchenko
Posts: 4,785
Registered: ‎01-30-2008
Message 7 of 7 (850 Views)

Re: 8.07 to 9.1 BSM Upgrade - Failed to perform update of profile dbs

Upgrade procedure never changes original schema names, so don't expect to see new names like RTSM_History.

 

4+ hours for 50+GB of data is not enormous, so you should keep waiting at this point.

Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation