Pages

Search This Blog

Friday, June 18, 2021

OTA – not up and Running in 12.1.3

 

We were in the process of creating Purchase Orders from iProc Requisitions and to send the Auto-approved Purchase Orders through OSN. We created OSN accounts and then realized that the PO’s didn’t hit the OSN. We did check the Work-flow agents and listeners were Enabled and running fine. As part of the trouble-shooting the issue, we found that the OTA (OXTA) was not up and running.

SQL –

select machine,action, decode(count(*),0,’Error: OTA is Not Running’,’OTA is Running’)
from gv$session
where action like ‘%OXTA%’
group by machine, action;

The above query returned no rows.

Reason –

  1. ASADMIN password didn’t either match in the system-jazn-data.xml ($INST_TOP/ora/10.1.3/j2ee/oafm/config/system-jazn-data.xml) as of ASADMIN set through the User Management
  2. If there was an Upgrade the passwords got changed

Fix –

  1. Check and confirm that dbc file specified in $INST_TOP/ora/10.1.3/j2ee/oafm/application-deployments/oafm/data-sources.xml file exists and is correct.
  2.  Confirm that the ASADMIN user setup is correct as below

a. Set profile Applications SSO Login Types  (APPS_SSO_LOCAL_LOGIN) for ASADMIN user to ‘Local’.

b. Change the ASADMIN password from User Management as follows (note: in this example password is set to welcome)

– Log onto Oracle E-Business Suite using sysadmin/<sysadmin_pw>.
– Select the User Management responsibility in the Navigator.
– Click the Users link from the navigation menu to open the User Maintenance window.
– Locate ‘ASADMIN’ user by entering information in the search area to retrieve the ‘ASADMIN’ user.
– Click the Update icon next to the ASADMIN user to open the Update User window.
– Remove the Active to date field and click Apply in case is not already removed
– Click the Reset Password icon next to the ASADMIN user to open the Reset Password window.
– Enter new password twice and click Submit

c. Confirm the definition for ASADMIN user in $INST_TOP/ora/10.1.3/j2ee/oafm/application-deployments/oafm/data-sources.xml is defined correctly:

user=”ASADMIN”
password=”->ASADMIN”

Note: The password above must be set with exact value as above because ->ASADMIN is an indirection, it indicates AS 10.1.0.3 that the password of ASADMIN must be taken from system-jazn-data.xml

d. Change password for ASADMIN user in $ORA_CONFIG_HOME/10.1.3/j2ee/oafm/config/system-jazn-data.xml to be !(! in front is mandatory)

Mention: ! in front of password is mandatory and this sign means that password will be encrypted

e. Shutdown and restart the OAFM container and re-test:

sh $ADMIN_SCRIPTS_HOME/adoafmctl.sh stop

sh $ADMIN_SCRIPTS_HOME/adoafmctl.sh start

References –

  1. NOTE: 1O87499.1 – Cannot Start OXTA After Upgrade To R12.1.x
  2. NOTE:418926.1 – How to Configure OTA For XML Gateway in Release 12
  3. NOTE:419839.1 – How to enable Apache, OC4J and OPMN logging in Oracle Applications R12

No comments:

Post a Comment