Monday, May 13, 2013

Adstrtal.Sh Does Not Initiate Adcmctl.Sh Process

Adstrtal.Sh Does Not Initiate Adcmctl.Sh Process:


Step 1:To fire the sqlp query to find the result

SQL> select node_name "Node Name", node_mode "Mode", support_cp "C",
support_web "W", support_admin "A", support_forms "F"
from FND_NODES;

Step 2: Backup the CONTEXT_FILE from R12 ($INST_TOP/appl/admin) & Verify the below parameters

Before :
a). grep -i s_concstatus $CONTEXT_FILE
<oa_service_status oa_var="s_concstatus">disabled</oa_service_status>

After Modification:

$grep -i s_concstatus $CONTEXT_FILE
                                <oa_service_status oa_var="s_concstatus">enabled</oa_service_status>

<oa_service_name oa_var="s_concname">OracleConcMgrUAT_svruatal1</oa_service_name>

Step 3. Save the changes and run the autoconfig

Step 4. Check the status of the adcmctl.sh after running the adstrtal.sh

++++++++++++++++++++++++++++++++++++++++++++++++++++++

The script adstrtal.sh calls the ServiceControl.java.

This java class reads the service information in your context file under$INST_TOP/appl/admin.

To prevent the concurrent managers from starting on your second node, you need to edit
$INST_TOP/appl/admin/<SID_hostname>.xml and change:-

s_concstatus">enabled<
To
s_concstatus">disabled<

Please make this change after the service is already stopped, as this change will also affect adstpall.sh.

There is no need to run AutoConfig, as ServiceControl.class reads the "s_<service>status"
variables directly from the XML file.

Adstrtal.Sh Does Not Initiate Adcmctl.Sh Process [ID 389516.1]

How to Prevent The Concurrent Managers to Start When Launching the Apps Middle Tier Startup Script "adstrtal.sh" ? [ID 417437.1]
233428.1 & 384248.1

+++++++++++++++++++++++++++++++++++++

No comments:

Post a Comment