Skip to end of metadata
Go to start of metadata

 

Scenario: Promotion Management problems 

Scenario Description: Some form of problem using Promotion Management

 

 

 

 

 

 

 

Scenario Owner is responsible for maintaining these pages

Scenario Owner: Patrick Bulteel

Feedback

Your feedback is very valuable to us. Please take a few moments to complete a simple survey

 

The following table shows which 'Hypotheses' (An idea where the issue is. High level symptoms) are applicable for different workflows.

Simply pick your workflow and then chose the most appropriate Hypotheses.

 

 

Hypothesis

An idea where the issue is.

High level symptoms

Purpose of troubleshooting task

How can the troubleshooting task help

Rating(1to5)
5 is high

Higher the number the more relevant the tool

Tool name

the name of the tool(s) to use

Why tool is suitable

Explains why this tool is helpful for this particular hypothesis.

How to use the tool for this hypothesis

Description (or links to) how the tool can be used to prove/deny the hypothesis

Next Steps/ Recommendations

Optionally some possible 'solutions'. Include any references to KBAs

(1) Problem with the 'meta data' of the source or target repository

Task: Identify problematic objects and fix any issues found

(star)(star)(star)(star)

Tool(s): Repository Diagnostic Tool (reposcan)

Why: Identifies common discrepancy within the repository (the issues identified may or may not be the cause of the issue)

How & Next Steps: Run the 'reposcan' tool against the repository. This identifies (and can fix) issues. Generally recommended to run reposcan against a system shutdown. More is described here

Task: Identify problematic  relationships between objects

(star)(star)(star)

Tool(s):Query Builder

Why: When the Repository Diagnostic Tool does not identify the issues. It's a different way to check the repository meta data integrity

How & Next Steps: Query the repository and identify strange relationships between objects and then delete or correct problem objects. More is described here

(2) Web based timeout caused by long running user action for example when adding objects into a promotion job within the CMC.
Task: Confirm if the timeout is caused by the web interface rather than the job itself.

(star)(star)(star)(star)

Tool(s):LCM command line interface (LCMCLI)

Why: Doesn't use web application server and so avoids all web based timeouts.How & Next Steps: Either promote the job into the target using the LCMCLI, or create a new promotion job using the LCMCLI. If the job is successful this proves the issue likely to be caused by web based timeout. More details described here.
(3) Known workflow causes a problem.
(Could be almost anywhere including: 'CMS objects and their relationships', OS level problems, web application issues, security issues)
Task: Isolating the problem

(star)(star)(star)(star)(star)

Tool(s):End to End trace (to collect) and Flexilog reader (to read)

Why: As the workflow is known, the End to End trace generates a limited amount of logs that are related to the troublesome workflow.

 

How & Next Steps: Enable the End to End trace, collect the logs, review the logs and take appropriate action. More detailed here.

(4) Individual object causing a problem somewhere (source/target)
Task: Isolating the problem

(star)(star)(star)(star)

Tool(s): Promotion Management 'interactive interface' or LCM command line (LCM CLI)Why: Quick and easy way isolate and reduce complexity.

How: Create a job of half the objects, and continue until isolated to 1 object.

Next Steps: Once the problematic object has been identified delete it, or promote a valid version from another system to overwrite it.
(5) Promotion Job fails during 'live' to 'live' Promotion
Task: Isolate the problem to either the import part or the export part.

(star)(star)(star)(star)(star)

Tool(s): Promotion Management

 

Why: Quick and easy way isolate and reduce complexity.

How: Run the job so to export to an LCMBIAR file. If this errors the problem is with the export.

Next, import the LCMBIAR and promote the contents into the target. If this errors the problem is with the import.

Next Steps: Look at other hypothesis to isolate the problem further.
(6) Promotion Job fails during import into target due to target objects being corrupt
Task: This illuminates the corrupt target objects from the process.

(star)(star)(star)(star) 

Tool(s): Promotion ManagementWhy: Quick and easy way isolate and reduce complexity.How: Run the Promotion Job into the target but disable the 'rollback' capability first.Next Steps: Look at other hypothesis to isolate the problem further.
(7) An existing object is somehow invalid or corrupt on the destination.
Task: Isolate the problem to individual target object and delete it

(star) (star) (star) 

Tool(s):Standard log tracing and Flexi log reader and Query Builder and CMS Console Mode

Why: You need to isolate the issue against a live system, since 'reposcan' is typically recommended to run against a system shutdown.

 

How & Next Steps: Enable standard product logs.

Review the logs and look for errors that should an invalid or corrupt object.

Identify the corrupt object and delete it within the Central Management Console or BI LaunchPad.

More described here

(8) 'Promotion Management Overrides scanning' fails due to a problem on the source system.
Task: Isolating the problem

(star)(star)(star)

Tool(s):End to End trace (to collect) and Flexilog reader (to read)

Why: The End to End trace generates a limited amount of logs that are related to the troublesome workflow.

How & Next Steps: Enable the End to End trace, collect the logs, review the logs and take appropriate action. More detailed here.



(9) Corruption in the 'Promotion Management Overrides' database causing overrides not to be applied. 
Task: Identify problematic overrides held and correct them

 

(star)(star)(star)(star)(star)

Tool(s):Razor SQL tool to read the 'local derby database' (applicable prior to BI4.1 SP3)

Why:

Easily see all the overrides held in the overrides database. Any 'corrupt' overrides can be removed in an easy way.

How & Next Steps: View the overrides held in the BI Platform and inspect them for corruption. For any correction either remove the corrupted override or 'reset' the overrides database and remove all overrides. More is described here

Tool(s):Query Builder to read the overrides' database and CMS Console Mode
(applicable to BI4.1 SP3 onwards)

How & Next Steps: View the overrides held in the BI Platform and inspect them for corruption. Then delete any corrupt ones. More is described here

 

(10) Problem remains un-isolated but suspect source metadata (CMS)
Task: Further isolation

(star)

Tool(s): Database dump tool. Send CMS database to SAP. FRS content may not need to be sent.Why: Last resort and when all attempts using the Customers own environment has not been successful.

How & Next Steps: SAP Support will need the Cluster Key and if possible the Administrator Password.

Read KBA 1197125 (internal), 195238 (internal), 1275068 and this SCN Blog on backup/recover of databases to allow import internally.

When working on a copy of the Repository, remove a large number of objects from the repository. For example drop all 'publications', to see if this works and continue to isolate issue.

(11) The Dependency Relationships between objects is somehow invalid or corrupt preventing correct object dependencies being determined

Task: Identify problematic overrides held in the CMS database and correct them

(star)(star)(star)(star)

Tool(s):End to End trace (to collect) and Flexilog reader (to read)

Why: As the workflow is known, the End to End trace generates a limited amount of logs that are related to the troublesome workflowHow & Next Steps: Enable the End to End trace, collect the logs, review the logs and take appropriate action. More detailed here.

Important Related Articles

SAP Promotion Management Support wiki.

Within Official Product Tutorials – SAP BusinessObjects Business Intelligence Platform 4.x the

  • Create a promotion job to promote content from a live source system to a live destination system  process flow
  • Run a promotion job to promote content from a live source system to a live destination system  process flow

 

 

  • No labels