Kevin Kempf's Blog

July 28, 2010

Not Feasible to Fix

Filed under: 11i, Discoverer — kkempf @ 1:15 pm

Stopping Discoverer 10g

Anyone familiar with Discoverer 10g on AS 10g (10.1.2.3) has probably seen the following error message when trying to use opmnctl to stop Discoverer:

opmnctl: stopping opmn and all managed processes...
================================================================================
opmn id=hostname-01:6200
    6 of 7 processes stopped.

ias-instance id=BI10g_PROD.hostname-01.domain.com
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
--------------------------------------------------------------------------------
ias-component/process-type/process-set:
    OC4J/OC4J_BI_Forms/default_island

Error
--> Process (pid=8331)
    time out while waiting for a managed process to stop
    Log:
    /u02/appprod/proddisco/opmn/logs/OC4J~OC4J_BI_Forms~default_island~1

For whatever reason, last maintenance windows I decided I was sick of waiting on this thing, and wanted to get rid of the ugly (but harmless) error message.   I was amused by what I found.

Bug 7357325

From My Oracle Support:

Solution
To implement the solution, please execute the following steps:

Discoverer development back-ported a fix to the second Discoverer cumulative patch on top of Oracle Application Server patchset 3 (10.1.2.3); however since then, per Bug 7357325, this workaround fix has been removed as it causes other regressions. Development has marked this as not feasible to fix in 10g. The message is harmless and can be avoided once all the Discoverer sessions exit cleanly (see above note).  We do recommend that you apply the latest cumulative patch, per Note 237607 ‘ALERT: Required and Recommended Patch Levels For All Discoverer Versions’

Goodness.  I hope they don’t cop that attitude with too many products.

Advertisements

Blog at WordPress.com.