Troubleshooting the CMDB 2.0 upgrade process

This section provides information about troubleshooting errors that you might get while you are upgrading to CMDB 2.0.

To abort scanning of CMDB 1.0

If you do not see scanning progress on the screen, check the status of the job on the Apex Jobs page (Setup > Jobs > Apex Jobs). Depending on the platform availability, the process might take a while to complete. If scanning your CMDB is taking a long time, you might want to abort the scan.

1. Navigate to Setup > Monitoring > Apex Jobs.
   If you have enabled the improved Setup user interface in your Salesforce organization, navigate to Setup > Jobs > Apex Jobs.
   For more information about the improved Setup user interface, see http://help.salesforce.com/apex/HTViewHelpDoc?id=admin_setup_improved.htm&language=en_US.
2. In the Apex Class column, click CMDB_ScannerBatchJob.
3. In the Status column, if the status of the job is Queued or Preparing, in the Action column, click Abort.

To view the status of the CMDB data migration job

You can view the status of the CMDB data migration job (CMDBMigrator) on the Apex Jobs page. If required, you can also abort the job from this page.

1. Navigate to Setup > Monitoring > Apex Jobs.
   If you have enabled the improved Setup user interface in your Salesforce organization, navigate to Setup > Jobs > Apex Jobs.
   For more information about the improved Setup user interface, see http://help.salesforce.com/apex/HTViewHelpDoc?id=admin_setup_improved.htm&language=en_US.
2. In the Apex Class column, click CMDBMigrator.

3. In the Status column, view the status of the CMDBMigrator job.

   Note

   If the CMDBMigrator job status is Completed and the Apex heap size too large message is displayed in the Status Details column, you can restart the migration process.

4. (Optional) To abort the CMDB data migration job, in the Action column for the CMDBMigrator job, click Abort.

Configuring batch size of the CMDB 2.0 upgrade Apex jobs

In the upgrade to CMDB 2.0 process, while migrating to CMDB 2.0 or deleting CMDB 1.0 data, you might get either of the following errors:

• Apex CPU time limit exceeded
• Too many SOQL queries

These errors are shown when the batch size of the Apex job that is scheduled for these procedures is large. The batch size of an Apex job is specified in a custom setting.

The following table provides a list of custom settings that control the batch size of these Apex jobs.

To configure batch size of a CMDB 2.0 Upgrade Apex job

1. Click the Remedyforce Administration tab.
2. On the Home page, click the Application Settings tile, and from the menu, select Custom Setting.
   Alternatively, navigate to Setup > Develop > Custom Settings.
3. In the Action column for Remedyforce Settings, click Manage.
4. On the Custom Setting Remedyforce Settings page, click New.
5. In the Name field, type the name of the custom setting (for example, Cleanup_MaxErrorRecords). See the Custom Settings table.
   Leave the Sequence Id field blank.
6. In the value field, enter the appropriate value for the custom setting.
7. Click Save.