Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

facebook Twitter
Print Bookmark Alert me when this article is updated


DIH publication could not publish partial data to the staging due to staging database crash
Problem Description
The publication was stuck in "Processing" state. This happened because the database crashed while the publication session had published X records out of N (where N=X+Y) to the staging. 
The database server crash did not allow the rollback operation to the database. Also, as the corresponding PowerCenter session failed with the following error:

ORA-03114: not connected to ORACLE

Database driver error...
Function Name : Commit
Database driver error...
Function Name : Rollback]​

Hence, the staging had partial published data.
To resolve this issue, do as follows:

1) Mark the publication event as ERROR.
2) Re-run the publication.
3) After the new publication is completed, make sure the previously published partial records are re-published with the new publication instance ID too.
4) After this is verified, discard the above publication event which was marked as ERROR.

The subscriptions and next publications would run as expected now.

If the previously published partial records are not published with the latest publication run (only previously unpublished records and the latest source records are published), then mark the above ERROR publication event  as "Completed" and use the "Get Previous Publication" option for the Subscriptions to consume the data published by this publication event.
More Information
Applies To
Product: Data Integration Hub
Problem Type: Crash/Hang
User Type: Business Analyst
Project Phase: Optimize
Product Version:
Operating System:
Other Software:

Last Modified Date:6/26/2019 10:45 PMID:570913
People who viewed this also viewed


Did this KB document help you?

What can we do to improve this information (2000 or fewer characters)