Content Successfully Converted by the IBR Remains in the GenWWW Status (Doc ID 1360960.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle WebCenter Content - Version and later
Information in this document applies to any platform.


All new documents that are being checked into the WebCenter Content server (formerly UCM, Universal Content Managment) are being successfully converted by the Inbound Refinery. On the IBR, the Agent's Conversion History shows that the Conversion Status is a Success for the submitted items.

However on the WCC, the status of the items never changes from GenWWW.

During the WCC conversion status process, a typical process as looks like the following. Note that the job process id is 2967:

>ibrsupport/6 09.21 09:16:58.338 SubjectManager Next job: 2967; update to:PostProc; success: true
>ibrsupport/6 09.21 09:16:58.354 SubjectManager Conversion job state updating id 2967 at {ts '2011-09-21 09:16:58.354'}
>systemdatabase/7 09.21 09:16:58.354 SubjectManager (start) UPDATE RefineryJobs SET dConversionState = 'Finished', dConvActionDate = {ts '2011-09-21 09:16:58.354'}
systemdatabase/7 09.21 09:16:58.354 SubjectManager WHERE dConvJobID = 2967 AND dConversionState = 'PostProc'

>ibrsupport/6 09.21 09:16:58.356 SubjectManager Conversion job state updated from PostProc to Finished for id 2967 successfully.
>ibrsupport/7 09.21 09:16:58.356 SubjectManager Retrieving next conversion work. New state: PostProc

In this instance where the item's status doesn't change from GenWWW, this what's seen in the process. Note that the submitted conversion job id is 68567, but then the job id is changed to 52529:

>systemdatabase/7 09.15 07:43:44.261 IdcServer-84679 (start) INSERT INTO RefineryJobs (dConvJobID, dDocID, dID, dDocName, dConversion, dConversionState,
systemdatabase/7 09.15 07:43:44.261 IdcServer-84679 dConvStartDate, dConvActionDate) VALUES (68567, 225453, 112358, 'D101944', 'Direct PDFExport', 'New', {ts '2011-09-15 07:43:00.000'}, {ts '2011-09-15 07:43:00.000'})

>ibrsupport/6 09.15 07:43:47.803 Refinery MonitorDocsToTransfer Conversion job state updating id 68567 at {ts '2011-09-15 07:43:47.803'}


>ibrsupport/6 09.15 07:44:08.637 SubjectManager Next job: 52529; update to: PostProc; success: true

>ibrsupport/6 09.15 07:44:08.653 SubjectManager Conversion job state updating id 52529 at {ts '2011-09-15 07:44:08.653'}
>systemdatabase/7 09.15 07:44:08.654 SubjectManager (start) UPDATE RefineryJobs SET dConversionState = 'Failed', dConvMessage '!csRefineryPostProcessFailed,D085387,52529,Converted', dConvActionDate = {ts '2011-09-15 07:44:08.653'}
systemdatabase/7 09.15 07:44:08.654 SubjectManager WHERE dConvJobID = 52529 AND dConversionState = 'PostProc'

It's trying to complete the status process using a previous job id.

In some cases, the Inbound Refinery may have gotten "stuck" with hundreds of documents waiting in the RefineryJobs table in the database.  If there are no documents in Work in Progress or GenWWW on the Content Server, then these are all orphan documents.  The Content Server would need to time out all 700 documents before it would process the one's that were recently checked in.

Note: This data was gathered by running a WCC system audit trace using ibrsupport and systemdatabase active sections.


Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms