My Oracle Support Banner

IPM SDK Tool For Tracing Commit Problems in Capture and IPM 7.6 / IPM 10g (Doc ID 808177.1)

Last updated on OCTOBER 07, 2019

Applies to:

Oracle WebCenter Capture 10g - Version 5.0 to 10.1.3.4.0 [Release Stellent to 10gR3]
Oracle WebCenter Distributed Capture - Version 5.0 to 10.1.3.4.0 [Release Stellent to 10gR3]
Information in this document applies to any platform.

Purpose

When errors are encountered committing from Capture to IPM, a utility is sometimes used to diagnose the functionality of the IPM SDK.  This helps to isolates the issue as either being a Capture problem or an IPM problem.

For Example, if one is facing the following error in Capture when attempting to commit to IPM:

Failed to commit batch FILING0000000469.

Error Number: 40008, Error: Commit Profile - Filing IPM Commit: The following error was reported by ReleaseDocument. Error Number: 505 Error Description: Failed to add page. Error Number: -2147179049, Error: Connections to the database have been lost, attempting to restore.

class ATL::CComObject<class CDocumentManager>::CreateDocument; Failed to commit batch XXXXXXXXX. Error Number: 40007, Error: Commit Profile - Filing IPM Commit: The following error was reported by PrereleaseDocument. Error Number: 505 Error Description: Failed to add page. Error Number: -2147179049, Error: Connections to the database have been lost, attempting to restore.

It would be difficult to trace out whether the problem is from Capture or IPM.  This tool can be used to determine if the problem is a result of the Capture integration to IPM or if the Oracle IPM SDK is returning this error.

Troubleshooting Steps

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Troubleshooting Steps

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.