Description

If your snapshot is stuck at the compute step and the DssEngine log is also stuck at the following then this page will help you troubleshoot the issue if one of the index is missing.
Example given is for 7.0.x

2014-07-18 14:03:27.025 Run snapshot...
2014-07-18 14:16:26.052 Run D:\Program Files (x86)\CAST\7.0.10 - SIEBEL_V4.0.5/DssRun.exe -LOCAL_IFPUG_GRAPH

The performance issue is encountered due to one of the missing primary key index on table ObjDsc on your local base.

Observed in CAST AIP
Release
Yes/No
8.3.x(error)
8.2.x (error)
8.1.x (error)
8.0.x(error)
7.3.x(tick)
7.2.x(tick)
7.0.x(tick)
Observed on RDBMS
RDBMS
Yes/No
Oracle Server(error)
Microsoft SQL Server(error)
CSS3(error)
CSS2(tick)
CSS1(tick)
Step by Step Scenario
  1. Run Snapshot
  2. The snapshot is stuck at "Compute snapshot in 'XXXX_Central' "
  3. Check the DssEngine log file to see it is stuck at the step as mentioned in the Description
Action Plan
  1. Check your local base and see if this primary key, 'pk_objdsc' is missing. If yes, the solution is to create the missing primary key by running the following query on your local base:

    alter table objdsc add CONSTRAINT pk_objdsc PRIMARY KEY (idobj, inftyp, infsubtyp, blkno, ordnum);
  2. After the PK is created you can run the snapshot once again.
Impact on Analysis Results and Dashboard

NA

Notes/comments

This issue is seen in 7.0.10 version and the WA has been tested successfully at support.

Related Pages