Important

   

Starting version 8.9.03, BMC Server Automation is renamed to TrueSight Server Automation. This space contains information about BMC Server Automation 8.9.02 and previous versions. For TrueSight Server Automation 8.9.03 and later releases, see TrueSight Server Automation 8.9.

Database and data migration issues

The following topics apply to troubleshooting issues with database and data migration:

Database cleanup command does not work

The first attempt to delete some BMC Server Automation objects using Delete cleanupDatabase might fail. However, subsequent runs of Delete cleanupDatabase delete the objects.

Online database cleanup process hangs on SQL Server

When performing an online database cleanup on a SQL Server database, certain cleanup options cause the database cleanup process to go into an unresponsive state. For example, after running the BLCLI command Delete cleanupHistoricalData, the BLCLI hangs. This issue occurs when the Compatibility Level setting of the SQL Server database is set to too low a version, that is, SQL Server 2005 or earlier — database versions that are no longer supported by BMC Server Automation.

Workaround:

Perform the following steps to reset the Compatibility Level setting of your SQL Server database:

  1. Through the Microsoft SQL Server Management Studio, find the name of your database in the list of databases.
  2. Right-click the database name and select Properties.
  3. In the Properties dialog box, select the Options page from the list of pages on the left.
  4. At the top of the Options page, check what value appears in the Compatibility level field. If the value in this field is too low (SQL Server 2005 or earlier), set it to SQL Server 2008 or later.

After adjusting the compatibility level, run the online database cleanup process once again.

Offline database cleanup fails to launch after an upgrade

After a BMC Server Automation upgrade, the dbm.exe or dbm.nsh file fails to launch the Database Maintenance Wizard for offline database cleanup.

Workaround:

  1. Navigate to the <InstallDir>\NSH\br\dbm-rcp\configuration directory.
    For example, C:\Program Files\BMC Software\BladeLogic\NSH\br\dbm-rcp\configuration (on Windows) or /opt/bmc/bladelogic/NSH/br/dbm-rcp/configuration (on Linux or UNIX).
  2. From this directory, delete all files and subdirectories, except for the config.ini file.
  3. Run the dbm.exe or dbm.nsh file (in the <InstallDir>\NSH\br\dbm-rcp directory) again.

Offline database schema fails with a BLFILE error

Offline database clean up fails with the below error, if either the Snapshot module or the Audit module is selected individually for an offline database clean up.

alter table snapshot_blfile WITH CHECK add constraint FKX5_snapshot_blfile foreign key (blfile_id) references BLFILE(blfile_id) 
Error Message - The ALTER TABLE statement conflicted with the FOREIGN KEY constraint "FKX5_snapshot_blfile". 

Workaround: To avoid this issue, BMC recommends you to run clean up on the Snapshot and Audit modules together while executing the offline clean up. 

Schema changes

BMC does not recommend, nor does it support database schema changes.

DB migration fails with error message ORA-39212 

 The following behaviors are observed:

  • Database migration fails.
  • The ORA-39212 exception is thrown.
  • The following code is observed in the blmigration.log
2015-01-28 23:35:17,534 [Thread-62 -- Task: com.bmc.install.product.bladelogic.BSAStandaloneStatelessConfiguratorTask] INFO com.bladelogic.mig.framework.singlestepmigration.SingleStepMigrationResult  - [1] SingleStepMigrationResult: TSK NM=mig_chng_contnts_tbl_98005  ; TSK SCR NM=    ; TO=8.6.00  ; TSK MSG=ORA-39212: installation error: XSL stylesheets not loaded correctly
ORA-06512: at "SYS.DBMS_METADATA", line 5088
ORA-06512: at "SYS.DBMS_METADATA", line 7589
ORA-06512: at line 1
ORA-06512: at "BLADELOGIC.LIB_DATA_DICT", line 237 
[2] SingleStepMigrationResult: TSK NM=mig_chng_contnts_tbl_98005  ; TSK SCR NM=    ; TO=8.6.00  ; TSK MSG=Upgrade halted. mig_chng_contnts_tbl_98005 did not complete step change contents of table at point 0. Contact BladeLogic Support before resuming. 

Cause

Oracle is not able to execute the Oracle-supplied package DBMS_METADATA, which loads the XSL stylesheet data in the Oracle data dictionary when it runs.

Workaround

Use the following procedure to resolve this issue: 

  1. Connect to the Oracle database with the following credentials:
    • User: SYS
    • Role: SYSDBA
  2. To reload the stylesheets, execute the following SQL command: SQL> exec dbms_metadata_util.load_stylesheets;
  3. Rerun the migration.
Was this page helpful? Yes No Submitting... Thank you

Comments