IBM Support

MustGather: FileNet Content Engine Document Storage

Troubleshooting


Problem

Customer-provided background information (also known as "MustGather" data) helps in problem determination and saves time when resolving Problem Management Records (PMRs). This technote provides a description of the background information IBM® support will need.

Resolving The Problem

Tab navigation

 

Collecting MustGather data early, even before opening the PMR, helps IBM® Support quickly determine the root cause of the problem. With this information, Support can determine if:

  1. This is a known problem (rediscovery).
  2. There is a non-defect problem that can be identified and resolved.
  3. This is a known defect for which a workaround has been developed.
  4. A new problem has been discovered and a fix is required.


If you already contacted support, continue on to the Document Storage MustGather information. Otherwise, click MustGather: Read first for FileNet Content Engine
 

Document Storage MustGather information

The following is required troubleshooting information for document storage problems.
  1. All of the information described in MustGather: Read first for FileNet Content Engine
  2. The Content Engine Server trace file (p8_server_trace.log) with debug trace enabled for the following subsystems depending on the type of storage problem being encountered. At a minimum, always enable detail trace for the Content Storage, Content Cache, and Error subsystems for any document storage problem.
    1. If the problem is related to a Fixed Content Device, then also enable detail tracing for the Fixed Content Provider subsystem. Hence, you would have detail trace enabled for Content Storage, Content Cache, Error, and Fixed Content Device.
    2. If the problem is related to CFS for Image Services, then also enable detail tracing for the CFS Daemon and SSI subsystems. Hence, you would have detail trace enabled for Content Storage, Content Cache, Error, Fixed Content Device, CFS Daemon, and SSI.
    3. If the problem is related to all other CFS implementations (e.g. CFS-CS), then also enable detail tracing for the CFS Import Agent subsystem. Hence, you would have detail trace enabled for Content Storage, Content Cache, Error, Fixed Content Device, and CFS Import Agent.

      See FileNet Content Engine Server tracing for details on how to collect this information.

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNVNV","label":"FileNet Content Manager"},"Component":"Content Engine","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"5.2.x;5.5.x","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
12 September 2019

UID

swg21313968

Page Feedback