oaea_server1 on PATCH

[big]

Hi,
On R12.2.9 DB 19c on AIX

oaea_server1 service starts on PATCH file system at any start of system.

How to prevent that?

Thanks and regards.

[ErmanArslansOracleBlog]

When did this arise? Maybe after a problematic patching cycle? a failed cutover?

Is your environment correct? (after setting it properly? -- for instance when you set the run environment, Does all the paths pointed by the relevant env. variables point to run filesystem?)

[big]

Thank you.

It arrived after creatin oaea_server1 after or during clonning the system.

For "Is your environment correct? (after setting it properly? -- for instance when you set the run environment, Does all the paths pointed by the relevant env. variables point to run filesystem?) "

I should verify. For the moment the users work and do not complaine.

Regards.

[ErmanArslansOracleBlog]

Ok please answer all the questions ->

1)Is your environment correct? (after setting it properly? -- for instance when you set the run environment,
Does all the paths pointed by the relevant env. variables point to run filesystem?)

2)are those cloning operations successful? --> seems not. (if so, you should re-do it properly)

3)what is your workaround for the moment?

[big]

Thank you.

 answer all the questions ->

1)Is your environment correct? (after setting it properly? -- for instance when you set the run environment,
Does all the paths pointed by the relevant env. variables point to run filesystem?)
patch base is fs1 then to test  I ran:
 $env | grep fs1
I had only.
PATCH_BASE=/u1/application/fs1

2)are those cloning operations successful? The only problem after clonning was SSO conection. A collegue suggested to create oaea_server1. We did and users could connect via SSO.


3)what is your workaround for the moment?
I run:
epatch
admanagedsrvctl.sh stop oaea_server1 forcepatch

Although without this action the users can work. Actually this is not a blocking problem.

Best regards.

[ErmanArslansOracleBlog]

oaea_server1 is closely related with Access Manager, so in that case having connection problems is normal.

Please go through the following document and ensure your access manager - EBS integration is properly done. -> Integrating Oracle E-Business Suite Release 12.2 with Oracle Access Manager 11gR2 (11.1.2) using Oracle E-Business Suite AccessGate (Doc ID 1576425.1)

Also ensure your cloning operation is right.

Do both of these checks and take necessary actions if there are any, to not to have the same issue after a future clone operation.

[big]

Yes, thank you.

Is there any way to verify if oaea_server is correctly created during clonning (befor user's complain that SSO does not function)?

With my best regards.

[big]

Hi,

Usually after a correct creation the file
$INST_TOP/appl/admin/oaea_wls.properties

would be completed.

Thanks and regards.

[ErmanArslansOracleBlog]

1)What do you modify in that file?
2)Before your modification, are the contents of the file wrong both in the patch fs and run fs versions?

[big]

Thank you.

1)What do you modify in that file? We modified nothing. It ( oaea_wls.properties
) was automatically filed as a consequence of running creation script or adding details script.
2)Before your modification, are the contents of the file wrong both in the patch fs and run fs versions?

Before (after running the script with wrong ports) there was nothing in that file. Then in script we corrected and put the correct port. Server was created and that file was filled automatically.
Best regards.

[ErmanArslansOracleBlog]

These don't help.. No information for further diagnostics, or concluding on an action plan, so please ->

Please go through the following document and ensure your access manager - EBS integration is properly done. -> Integrating Oracle E-Business Suite Release 12.2 with Oracle Access Manager 11gR2 (11.1.2) using Oracle E-Business Suite AccessGate (Doc ID 1576425.1)

Also ensure your cloning operation is right.

Do both of these checks and take necessary actions if there are any, to not to have the same issue after a future clone operation.

[big]

yes thank you.
I will pay attention next time.
Regards.