Introduction:
Encountering an issue where the Concurrent Request Report Output from the Oracle Report Manager Homepage dashboard redirects to the DMZ node instead of the primary node can be frustrating. This blog post provides two solutions, a permanent fix requiring downtime and a temporary fix with no downtime.
Navigation:
ORACLE*Report Manager Home Page –> Dashboard –> Output –> View Report Now
Cause:
The values for the profile’s are updated from DMZ node instead of PRIMARY node.
Permanent Fix (Solution 1):
========================
Step 1 :Run the following SQL query to identify the profile values
——————————————————————————-
SELECT
fpot.user_profile_option_name NAME,
DECODE (fpov.level_id,
10001, ‘Site’,
10002, ‘Application’,
10003, ‘Responsibility’,
10004, ‘User’,
10005, ‘Server’,
‘UnDef’)
LEVEL_SET,
fpov.profile_option_value VALUE
FROM fnd_profile_options fpo,
fnd_profile_option_values fpov,
fnd_profile_options_tl fpot,
fnd_user fu,
fnd_application fap,
fnd_responsibility frsp,
fnd_nodes fnod,
hr_operating_units hou
WHERE fpo.profile_option_id = fpov.profile_option_id(+)
AND fpo.profile_option_name = fpot.profile_option_name
AND fu.user_id(+) = fpov.level_value
AND frsp.application_id(+) = fpov.level_value_application_id
AND frsp.responsibility_id(+) = fpov.level_value
AND fap.application_id(+) = fpov.level_value
AND fnod.node_id(+) = fpov.level_value
AND hou.organization_id(+) = fpov.level_value
AND fpot.user_profile_option_name like ‘%Agent’
and fpov.level_id = 10001
ORDER BY 1,2;
The query will returns profile values related to DMZ node as given below
—————————————————————————————
Profile Option Name Site Profile Options Value
====================== ====== =======================================
Application Framework Agent Site https://DMZhostname.domainname:port
Applications JSP Agent Site https://DMZhostname.domainname:port
Applications Web Agent Site https://DMZhostname.domainname:port/pls/SID
Apps Servlet Agent Site https://DMZhostname.domainname:port:/OA_HTML
Step 2: Update Profile Values
Update the profile values related to the DMZ node with those of the primary node by running autoconfig in primary node only as shown below.
(i) Shutdown DMZ node application services
(ii) Shutdown PRIMARY node application services
(iii) Run “AUTOCONFIG” only in EBS primary node.
(iv) Start PRIMARY node application services.
(v) Start DMZ node application services.
Step 3: Verify Profile Values
Rerun the query to ensure the profile values now point to the primary node.
Profile Option Name Site Profile Options Value
=================== ======= ======================================
Application Framework Agent Site https://PRIMARYhostname.domainname:port
Applications JSP Agent Site https://PRIMARYhostname.domainname:port
Applications Web Agent Site https://PRIMARYhostname.domainname:port/pls/SID
Apps Servlet Agent Site https://PRIMARYhostname.domainname:port:/OA_HTML
Step 4: Confirm Resolution
Clicking on “View Report Now” from the Report Manager Homepage dashboard should now display the correct concurrent request output.
[OR]
Temporary Fix (Solution 2):
====================
Step 1:
Update the profile values related to the primary node through the EBS front-end application at the SITE level as shown below
Profile Option Name Site Profile Options Value
=================== ======= ======================================
Application Framework Agent Site https://PRIMARYhostname.domainname:port
Applications JSP Agent Site https://PRIMARYhostname.domainname:port
Applications Web Agent Site https://PRIMARYhostname.domainname:port/pls/SID
Apps Servlet Agent Site https://PRIMARYhostname.domainname:port:/OA_HTML
Step 2: Bounce Workflow Directory Services
Bounce workflow directory services .
Conclusion:
Choose the appropriate solution based on your operational requirements. The permanent fix ensures a long-term resolution but requires downtime, while the temporary fix provides a quick solution without service disruption. Always perform these actions in a controlled environment and back up critical data before making changes.
