Skip to Main Content

DevOps, CI/CD and Automation

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

41214 with 12c Reports Standalone run_report_object, but not Inprocess

user12072642Oct 5 2018 — edited Oct 9 2018

An odd circumstance here, which crosses into Forms territory a bit.

Specifically, a 12c Reports inprocess server has been used in the past for executing run_report_object from Forms. This inprocess-server-using request succeeds, and Forms moves on to other things. However, when a standalone server is used for the report_object's REPORT_SERVER instead of the inprocess server, the result is a 41214.

Some further background:

The host running the servers goes through this process when firing up - start Node Manager, start OHS, start WebLogic, start WLS_FORMS, start WLS_REPORTS, start standalone server, start inprocess server (the last two sometimes happen in opposite order).

The run_report_object's report_object parameter has properties REPORT_DESTYPE=CACHE, REPORT_COMM_MODE=1, and REPORT_OTHER='RECURSIVE_LOAD=NO'.

While it does not SEEM to affect the server's execution or lack thereof, the Reports server on the specified host has port 9002, while both OHS and Forms have port 7777.

Might anybody recognize this scenario?

This post has been answered by user12072642 on Oct 9 2018
Jump to Answer
Comments
Post Details
Added on Oct 5 2018
6 comments
1,459 views