122-blank-page-viewing

[kalyan.v3]

Hi,
We have recently upgraded the ebs 12.2.4/12c to 12.2.11/19c version.
Right now we are having an issue when trying to view the output/log file for concurrent requests they are blank from browser.
If we change the profile viewer:text to plain(remove browser) it displays in a window....Issue is when it's browser.

I came across your post
http://ermanarslan.blogspot.com/2017/04/ebs-122-blank-page-problem-viewing.html

Symptoms are same, but the node_file.txt is fine (hostname not in capital letters).Even in the FS Diagnostic Test Program report it shows Unable to transfer file successfully.

Oracle SR has been raise,couple of SR's, BNE patches nothing has resolved it yet.

Is there any other things can we check

Thanks,
Kalyan.

[ErmanArslansOracleBlog]

Is your hostname of your app node in capital letters?

[ErmanArslansOracleBlog]

Check your OS as well..

2 MOS notes for your ->

*-->Concurrent Request Report Log And Output Result In A Blank Page In Browser (Doc ID 1630055.1)
*-->Blank page when trying to View Request Output or Log (Doc ID 2177504.1)

Also a debug note ->

How to Troubleshoot FNDFS and FNDWRR (Problems Viewing Concurrent Request Output) (Doc ID 847844.1)

Also review the following one (don't concentrate on Dynatrace.. There may be something that is breaking the code -> in your Weblogic start scripts and env..)

*-->Unable to Access Log And Out Files from the Concurrent Request View And Output Buttons After Patching Using Dynatrace (Doc ID 2755839.1)

[kalyan.v3]

Hi,

As I have already mentioned hostname were not in capitals.

I have already gone through the DOC ID's : both are not relevant. As we are already on OL8.6 the mentioned RPM's not required for Linux 64 and moreover these RPMs won't even exists in OL8 versions.

I will review this DOC ID: 2755839.1 ...I haven't concentrated much as we don't have any third party monitoring tool in the systems.
But will still cross check them.

I also came across this particular ID:2914718.1 specific to OL8/RHEL8 ...any thoughts on this.

Thanks,

[ErmanArslansOracleBlog]

Okay again check that note -> 2755839.1 .. You might not have any third party tool there, but still you may have a modification in that start script and it may be causing the issue.. (just in case, check.)

The OS seems looks suspicious. (version 8, certified but can be considered new --)
So, "Patch 32931976: TECHP:REPACKAGING OF WLS PATCH FOR EBS 12.2 ORACLE E-BUSINESS SUITE ON OL8/RHEL8" looks promising.. It's worth a try I think.

[ErmanArslansOracleBlog]

Note that,

That patch is a mandatory one ->

Apply FMW Patch (Oracle Linux 8, RHEL 8 and SLES 15 only)
Customers on existing 12.2 systems who are cloning to the above operating systems must first apply the following patches on the source 12.2 environment:

Reference: Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.2) for Linux x86-64 (Doc ID 1330701.1)

[kalyan.v3]

Hi,

After applying this particular FMW patch issue got released.
I was checking this DOC ID: but was waiting if oracle support can suggest because I gave them the same information and asked their opinion.
I wanted to have assurance so that I am sure no issue comes as the Instance is under testing and it cannot be disturbed .

Well this particular Issue is specific to OL8, so this patch is mandatory if we are upgrading/ cloning.

Thanks for the support and the confirmation for me to proceed and apply the patch.

Best Regards,
Kalyan.

[ErmanArslansOracleBlog]

I' m glad that it is resolved. For the future; if there is a mandatory patch that is missing in your env, you can just apply it without confirmation. (But of course in a controlled way, testing and stuff like that)