How-to Rerun BI_TCO_ACTIVATION Job

The SAP BW job to activate the BI Technical Content failed; how do I start it again?

The MiniSAP installation is nearly complete, I’ve started the BW Administrator Workbench (AWB) using transaction RSA1 and a dialog box prompted the background execution of the BI_TCO_ACTIVATION job.

Unfortunately, using transaction SM37, I can see that it ran for a while but has stopped with a status of cancelled.

This is a common issue on new MiniSAP installations, due to a mis-match between optimised server/service configuration and the available hardware.

No problem, the BI_TCO_ACTIVATION job will pick up from where it fell over. Just re-execute it and keep an eye on the job logs for the real progress. On smaller hardware configurations, this has been known to require at least 3 re-starts before it completes successfully.

  1. In ‘Command Field’ option enter ‘/nSM37’ value.
  2. Click ‘Enter’ button.
  3. Ensure ‘Job Name’ option is ‘BI_TCO_ACTIVATION’ value.
  4. Ensure ‘User Name’ option is ‘*’ value.
  5. In ‘Job Start Condition’ group, ensure ‘From’ and ‘To’ options have appropriate dates.
  6. Click ‘Execute’ button.
    How-To Rerun BI_TCO_ACTIVATION Job 01 Job Selection
  7. Select the row of the failed job with a tick.
  8. Ensure all other rows are un-ticked.
    How-To Rerun BI_TCO_ACTIVATION Job 02 Job Overview
  9. Navigate ‘Job’ -> ‘Repeat Scheduling’ menu.
    How-To Rerun BI_TCO_ACTIVATION Job 03 Repeat Scheduling
  10. Click ‘Immediate’ button.
  11. Click ‘Save’ button.
    How-To Rerun BI_TCO_ACTIVATION Job 04 Start Immediately
  12. Click ‘Refresh’ button once in a while to see if the job has finished.
    It is very possible the BI_TCO_ACTIVATION job will fail for a second time.
    Rerun the BI_TCO_ACTIVATION job for a third (forth, fifth, etc) time until finished.
    Quite often the BI_TCO_ACTIVATION job will need to be run three (3) times.
    How-To Rerun BI_TCO_ACTIVATION Job 05 Job Overview
  13. Done.

Were you unfortunate enough to get to rerun 29? Then it’s probably an issue larger than system resources. Head on over to the SAP Community – Questions and Answers where you can engage with like minded Netweaver enthusiasts.