Parallel Concurrent Processing (PCP) In Oracle EBS
Parallel Concurrent Processing (PCP) In Oracle EBS
PCP is the method by which we configure the Concurrent Manager in a multi-tier environment with 2 or more concurrent nodes.
This allows the load to be distributed across the defined nodes and provides high availability and failover. Concurrent Managers will move to the surviving node (failover)when one of the concurrent nodes goes down and migrate back (failback) when the failed node comes back.
The concurrent manager(s) connect via sqlnet to the database using tns alias specified by TWO_TASK in adcmctl.sh and gsmstart.sh on each concurrent node.
When the primary node fails, the ICM will restart the manager on the secondary node. If the ICM’s node fails, an Internal Monitor on the surviving node can spawn a new ICM on that node.
Services/Managers move back to their primary nodes when those nodes come back up.
What is the role of ICM in PCP
Internal Manager (ICM) monitors, activates and deactivates all managers.
ICM migrates managers during node and/or instance failures and needs to be active for failover/failback to work.
ICM uses the Service Manager (FNDSM) to spawn and terminate all concurrent manager processes, and to manage GSM services like Workflow mailer, Output Post Processor, etc.
ICM will contact the APPS TNS Listener on each local and remote concurrent processing node to start the Service Manager on that node.
ICM will not attempt to start a Service Manager if it is unable to TNS ping the APPS TNS Listener
One Service Manager is defined for each application node registered in FND_NODES.
Each service/manager may have a primary and a secondary node. Initially, a concurrent manager is started on its primary node. In case of node failure, all concurrent managers on that node migrate to their respective secondary nodes.
Service Manager and PCP
The service manager (FNDSM process) is used to manage services/managers on each concurrent node. It is a requirement in all concurrent processing environments and is therefore an integral part of PCP. PCP cannot be implemented without a Service manager.
The Service Manager is spawned from the APPS TNS Listener
The APPS TNS Listener must be started on every application node in the system and started by the user that starts ICM (e.g. applmgr)
TNS Listener spawns Service Manager to run as agent of ICM for the local node
The Service Manager is started by ICM on demand when needed. If no management actions are needed on a node, Service Manager will not be started by ICM until necessary. When ICM exits its Service Managers exit as well.
The Service Manager environment is set by gsmstart.sh and APPSORA.env as defined in listener.ora
Internal Monitors and PCP
The only function of Internal Monitor (FNDIMON process) is to check if ICM is running and restart failed ICM on local node.
Internal Monitors are seeded on every registered node by default by autoconfig.
Activate Internal Monitor on each concurrent node where the ICM can start in case of a failure. By default, Internal Monitor is deactivated.
If the ICM goes down, the Internal Monitor will attempt to start a new ICM on the local node.
If multiple ICMs are started, only the first will stay active. The others will gracefully exit.
Steps to configure (PCP) in EBS R12
A) Backup all .ora files
Copy the existing tnsnames.ora, listener.ora and sqlnet.ora files, where they exist, under the 10.1.2 and 10.1.3 ORACLE_HOME locations on the each node to preserve the files
B) Edit Context file
Stop the application on all nodes. Edit the applications context file via Oracle Applications Manager
Set the value of the variable in the context file
Configure GSM on each node
> APPLDCP to ON
<APPLDCP oa_var="s_appldcp"> ON </APPLDCP>
Setup APPLCSF
> s_applcsf to <shared location between apps servers>
> s_appltmp to <shared location between apps servers>
C) Edit parameters in spfile (for the transaction manager)
It has to be done by sysdba
alter system set “_lm_global_posts”=true scope=spfile;
alter system set “_immediate_commit_propagation”=true scope=spfile;
D) Edit utl_file_dir variable
From database node as sysdba
ALTER SYSTEM SET utl_file_dir='<shared temp location’ SCOPE=BOTH sid=’*’;
E) Bounce database to reflect the changes made. In case of rac use srvctl else use the normal method.
Using grid user from any database node
srvctl stop database -d <db_name>
srvctl start database -d <db_name>
F) Execute AutoConfig
Execute AutoConfig by running the following command on all concurrent processing nodes:
$INST_TOP/admin/scripts/adautocfg.sh
G) Check the tnsnames.ora and listener.ora configuration files
Check the tnsnames.ora and listener.ora configuration files, located in $INST_TOP/ora/10.1.2/network/admin. Ensure that the required FNDSM and FNDFS entries are present for all other concurrent nodes.
H) Start the Applications
Log on to Oracle E-Business Suite Release 12 using the SYSADMIN account, and choose the System Administrator Responsibility.
• Navigate to Install > Nodes screen, and ensure that each node in the cluster is registered.
• Set up the primary and secondary node names
Navigate to Concurrent > Manager > Define, and set up the primary and secondary node names for all the concurrent managers according to the desired configuration for each node workload.
• Verify that the Internal Monitor and Service Manager for each node is defined properly, with correct primary node specification, and work shift details. For example, Internal Monitor: Host1 must have primary node as host1. Assign a standard work shift with one process to both managers. Also ensure that the Internal Monitor manager is activated: this can be done from Concurrent > Manager > Administrator.
• set Concurrent: TM Transport Type profile
Navigate to Profile > System, change the profile option ‘Concurrent: TM Transport Type’ to ‘QUEUE’, and verify that the transaction manager works across the Oracle RAC instance.
• If any of the transaction managers are in deactivated status, activate them from Concurrent > Manager > Administrator
What happens if we don’t assign any primary/secondary node
Managers with no primary node assignment will be assigned a default target node. In general this will be the node where the ICM is currently running.
Troubleshooting
>> In the tnsnames.ora file of each Concurrent Processing node ensure that there is an alias that matches the instance name from GV$INSTANCE of each Oracle instance on each RAC node in the cluster.
>> Ensure that the Applications Listener is active on each node in the cluster where Concurrent or Service processes will execute.
>> Stop and restart the Concurrent Manager processes on their primary node(s) and verify that the managers are starting on their appropriate nodes. On the target (secondary) node in addition to any defined managers you will see an FNDSM process (the Service Manager), along with the FNDIMON process (Internal Monitor).
Help -> Diagnostic ->Examine returns Error : Function Not Available For This Responsibility
While running "Help -> Diagnostic ->Examine returns Error : Function Not Available For This Responsibility"
Error:
Error:
Function Not Available For This Responsibility
Cause:
The Profile "Utilities: Diagnostic" is not set to YES. This profile needs to be set for examine to return rows and not error
Solution:
Execute the following steps to resolve the issue:
1) Set the Profile Utilities: Diagnostic to YES
This can be done at user level to test.
2) If needed, this can be set at SITE level depending upon requirements.
ADOP fails with ORA-12516: TNS:listener could not find available handler with matching protocol stack
While running ADOP I saw below error in adconfig log file.
Error:
ORA-12516: TNS:listener could not find available handler with matching protocol stack
CAUSE;
This is an issue with the number of database process/sessions.
SOLUTION:
We can check utilization of processes and session.
SQL> select resource_name, current_utilization, max_utilization from v$resource_limit where resource_name in ('processes','sessions');
RESOURCE_NAME CURRENT_UTILIZATION MAX_UTILIZATION
------------------------------ ------------------- ---------------
processes 478 500
sessions 499 540
We can bounce the database, and increase the number of processes/sessions . Re-run the patch application.
Reference: adop fails with "ORA-12516: TNS:listener could not find available handler with matching protocol stack" (Doc ID 2105049.1)
How to check/configure Oracle Apps EBS and ASCP(APS) integration
In this post we are going to see the steps that are needed to validate/configure the EBS and ASCP instance integration. This Setup changes might be required after cloning and setting up new APS destination and EBS source.
Source EBS: DEBS
Destination APS : DAPS
Steps:
1) Create DBapps and public schema of both source and destination instance.
On Source Instance DEBS create DB link with name
DAPS connecting to DAPS instance. DB link should be present in both public and APPS schema.
On Destination Instance DAPS create DB link with name
DEBS connecting to DEBS instance. DB link should be present in both public and APPS schema.
2. Log in to the Target (ASCP) System and choose “Advanced Planning Administrator”.
Navigate to Admin --> Instances. The Application Instances window appears.
Insert record for the Source (ERP) system as follows:
Instance Code : Give a new name for the Instance Code (uniquely identified).
Instance Type : Select “Discrete” (consult Functional Consultant).
Version : 11i (default, for 11i E Business Suite).
From Source to APS : Database Link created on the Source System for Target System Database.
From APS to Source : Database Link created on the Target System for Source System Database.
Check “Enable Flag”, “Allow ATP” and “Allow Release”.
You can verify the values from below table on APS side
select * from MSC_APPS_INSTANCES.
3) On EBS source set Below profile value as DB link name pointing to APS instance.
MRP:ATP Database Link = DAPS
4) On EBS side check below table/view should be having correct value.
select * from MRP_AP_APPS_INSTANCES_ALL;
In case multiple rows are available in the above query, then update
MRP_AP_APPS_INSTANCES_ALL.ALLOW_ATP_FLAG = 1 for only the one correct instance we want to use for ATP.
For all other rows update it as 2.
In case no rows are present in the table the we can insert.
insert into mrp.MRP_AP_APPS_INSTANCES_ALL values (1,46523506,'27-SEP-18','FUN','DEBS','DAPS',-1,'27-SEP-18',1396,'30-APR-08',104,6269,'HR',2,2,2,14,13,14,13,12,11,NULL,13,14,14,14,14,14,NULL,NULL,NULL,NULL,0,NULL,0,NULL,NULL,NULL,NULL,NULL,NULL,1,1,NULL,2,'x.SEGMENT1',2,NULL,NULL,'C');
There might be various other steps than need to worked upon by you functional or technical consultant.
Source EBS: DEBS
Destination APS : DAPS
Steps:
1) Create DBapps and public schema of both source and destination instance.
On Source Instance DEBS create DB link with name
DAPS connecting to DAPS instance. DB link should be present in both public and APPS schema.
On Destination Instance DAPS create DB link with name
DEBS connecting to DEBS instance. DB link should be present in both public and APPS schema.
2. Log in to the Target (ASCP) System and choose “Advanced Planning Administrator”.
Navigate to Admin --> Instances. The Application Instances window appears.
Insert record for the Source (ERP) system as follows:
Instance Code : Give a new name for the Instance Code (uniquely identified).
Instance Type : Select “Discrete” (consult Functional Consultant).
Version : 11i (default, for 11i E Business Suite).
From Source to APS : Database Link created on the Source System for Target System Database.
From APS to Source : Database Link created on the Target System for Source System Database.
Check “Enable Flag”, “Allow ATP” and “Allow Release”.
You can verify the values from below table on APS side
select * from MSC_APPS_INSTANCES.
3) On EBS source set Below profile value as DB link name pointing to APS instance.
MRP:ATP Database Link = DAPS
4) On EBS side check below table/view should be having correct value.
select * from MRP_AP_APPS_INSTANCES_ALL;
In case multiple rows are available in the above query, then update
MRP_AP_APPS_INSTANCES_ALL.ALLOW_ATP_FLAG = 1 for only the one correct instance we want to use for ATP.
For all other rows update it as 2.
In case no rows are present in the table the we can insert.
insert into mrp.MRP_AP_APPS_INSTANCES_ALL values (1,46523506,'27-SEP-18','FUN','DEBS','DAPS',-1,'27-SEP-18',1396,'30-APR-08',104,6269,'HR',2,2,2,14,13,14,13,12,11,NULL,13,14,14,14,14,14,NULL,NULL,NULL,NULL,0,NULL,0,NULL,NULL,NULL,NULL,NULL,NULL,1,1,NULL,2,'x.SEGMENT1',2,NULL,NULL,'C');
There might be various other steps than need to worked upon by you functional or technical consultant.
Oracle Apps R12-->REP-0004: Warning: Unable to open user preference file
If we are getting Error while running reports.
Error:
REP-0004: Warning: Unable to open user preference file
Solution:
Make sure the file prefs.ora is located in your "home" directory If it is not, change the directory or filename as appropriate.
Copy $ORACLE_HOME/tools/admin/prefs.ora to $HOME
If error is not solved after copy the prefs.ora also then you have to check privileges.
After changing privileges bounce application services.
Error:
REP-0004: Warning: Unable to open user preference file
Solution:
Make sure the file prefs.ora is located in your "home" directory If it is not, change the directory or filename as appropriate.
Copy $ORACLE_HOME/tools/admin/prefs.ora to $HOME
If error is not solved after copy the prefs.ora also then you have to check privileges.
After changing privileges bounce application services.
Adding and Deleting Managed Server in Oracle Apps R12.2
Adding a New Managed Server
The below steps needs to be executed on run file system when there is no active ADOP cycle. During the next adop prepare, the Configuration Change Detector identifies that the addition has been made and the managed servers are automatically synced up from the run file system to the patch file system. The synchronization also gets done when fs_clone is executed.
Note: Managed server creation should be done only through the adProvisionEBS.pl script as mentioned in this section. Managed servers should not be created from the WebLogic Server Administration Console.
To add a new managed server of a specific service type, perform the following steps on the run file system:
Step 1:
Execute the following command to add a new managed server. This will create a managed server and add a new entry to the context file for starting and stopping the new managed server via the adstrtal and adstpall scripts:
$ perl $AD_TOP
ebs-create-managedserver -contextfile=
-managedsrvname=
-managedsrvport=
For example, to add a managed server 'oacore_server2' of type 'oacore' with port 7203, run the following command:
$ perl $AD_TOP/patch/115/bin/adProvisionEBS.pl \
ebs-create-managedserver -contextfile=$CONTEXT_FILE \
-managedsrvname=oacore_server2 -servicetype=oacore \
-managedsrvport=7203 -logfile=$APPLRGF/TXK/addMS_oacoreserver2.log
Note:
The managed server name must be of the form_server, where n is an integer.
As well as being free, the port number for each managed server must be unique: no two managed servers across the run and patch file systems can have the same port number.
Step 2:
Startup the managed server as follows:
On Unix:
$ sh ./admanagedsrvctl.sh start
Example:
$ sh ./admanagedsrvctl.sh start oacore_server2
Step 3:
Perform the following steps on all application tier nodes participating in the same cluster where this managed server is added:
Source the run file system.
Execute the following command to add details of the newly added managed servers into the OHS configuration files mod_wl_ohs.conf and apps.conf on the current node:
$ perl $FND_TOP/patch/115/bin/txkSetAppsConf.pl \
where
The argument contextfile accepts the complete path to the context file.
The arguments oacore, oafm, forms, formsc4ws accept a comma-separated list of managed server details in the following format:
.:
host and domain are the hostname and domain name of the newly added node
port is the port of the new managed server whose reference is to be added
For example, if the managed server oacore_server2 has been added on host 'testserver' and domain 'example.com' with port 7205, the following command should be executed:
$ perl $FND_TOP/patch/115/bin/txkSetAppsConf.pl -contextfile=$CONTEXT_FILE \
-configoption=addMS -oacore=testserver.example.com:7205
Step 4:
If Oracle HTTP Server is enabled on the node, restart it as follows:
On UNIX:
$ sh/adapcctl.sh stop
$ sh/adapcctl.sh start
Removing a Managed Server
The below steps needs to be executed on run file system when there is no active ADOP cycle. As in the case of managed server addition, deletion of managed servers should be done on the run file system, with synchronization between the run and the patch file systems subsequently being performed automatically during adop prepare execution or during fs_clone.
Note: Managed server deletion should be done only through the adProvisionEBS.pl script as mentioned in this section. Managed servers should not be deleted from the WebLogic Server Administration Console.
To delete a managed server of a specific service type, perform the following steps on the run file system:
Perform the following steps on the application tier where the managed server resides.
Step 1:
If the managed server to be deleted is running, shut it down as follows:
On Unix:
$ sh/admanagedsrvctl.sh stop
For example, before deleting a managed server 'oacore_server2', execute the following command to shut it down.
$ sh/admanagedsrvctl.sh stop oacore_server2
Step 2:
Run the command below on the application tier node where the managed server resides. This will delete the managed server, and also update the respective context variables that contain references to the deleted managed server.
$ perl $AD_TOP/patch/115/bin/adProvisionEBS.pl \
ebs-delete-managedserver \
-contextfile= -managedsrvname= \
-servicetype= -logfile=
For example, for deleting a managed server 'oacore_server2' of type 'oacore', execute the following command:
$ perl $AD_TOP/patch/115/bin/adProvisionEBS.pl \
ebs-delete-managedserver \
-contextfile= -managedsrvname=oacore_server2 \
-servicetype=oacore -logfile=$APPLRGF/TXK/delMS_oacoreserver2.log
Step 3:
Perform the following steps on all application tier nodes participating in the same cluster as the deleted managed server:
Source the run file system.
If the deleted managed server is part of the cluster configuration defined on the current node, execute the following command to delete details of the managed server from the OHS configuration files mod_wl_ohs.conf and apps.conf on the current node:
where
The argument contextfile accepts the complete path to the context file.
The arguments oacore, oafm, forms, formsc4ws, ekanban, accessgate and yms accept a comma-separated list of managed server details in the following format:
.:
host, domain and port are the hostname, domain and port of the managed server whose reference is to be deleted.
For example, to remove references of the deleted managed server oacore_server2 with port 7205 on host 'testserver' and domain 'example.com', the following command should be executed:
$ perl $FND_TOP/patch/115/bin/txkSetAppsConf.pl -contextfile= \
-configoption=removeMS -oacore=testserver.example.com:7205
Step 4:
If Oracle HTTP Server is enabled on the node, restart it as follows:
On UNIX:
$ sh/adapcctl.sh stop
$ sh/adapcctl.sh start
-managedsrvname=oacore_server2 -servicetype=oacore \
-managedsrvport=7203 -logfile=$APPLRGF/TXK/addMS_oacoreserver2.log
Note:
The managed server name must be of the form
As well as being free, the port number for each managed server must be unique: no two managed servers across the run and patch file systems can have the same port number.
Step 2:
Startup the managed server as follows:
On Unix:
$ sh .
Example:
$ sh .
Step 3:
Perform the following steps on all application tier nodes participating in the same cluster where this managed server is added:
Source the run file system.
Execute the following command to add details of the newly added managed servers into the OHS configuration files mod_wl_ohs.conf and apps.conf on the current node:
$ perl $FND_TOP/patch/115/bin/txkSetAppsConf.pl \
-contextfile= <context_file>\
-configoption=addMS \
-oacore=<host>.<domain>:port \
-oafm=<host>.<domain>:port \
-forms=<host>.<domain>:port \
-formsc4ws=<host>.<domain>:port
where
The argument contextfile accepts the complete path to the context file.
The arguments oacore, oafm, forms, formsc4ws accept a comma-separated list of managed server details in the following format:
host and domain are the hostname and domain name of the newly added node
port is the port of the new managed server whose reference is to be added
For example, if the managed server oacore_server2 has been added on host 'testserver' and domain 'example.com' with port 7205, the following command should be executed:
$ perl $FND_TOP
-configoption=addMS -oacore=testserver.example.com:7205
Step 4:
If Oracle HTTP Server is enabled on the node, restart it as follows:
On UNIX:
$ sh
$ sh
Removing a Managed Server
The below steps needs to be executed on run file system when there is no active ADOP cycle. As in the case of managed server addition, deletion of managed servers should be done on the run file system, with synchronization between the run and the patch file systems subsequently being performed automatically during adop prepare execution or during fs_clone.
Note: Managed server deletion should be done only through the adProvisionEBS.pl script as mentioned in this section. Managed servers should not be deleted from the WebLogic Server Administration Console.
To delete a managed server of a specific service type, perform the following steps on the run file system:
Perform the following steps on the application tier where the managed server resides.
Step 1:
If the managed server to be deleted is running, shut it down as follows:
On Unix:
$ sh
For example, before deleting a managed server 'oacore_server2', execute the following command to shut it down.
$ sh
Step 2:
Run the command below on the application tier node where the managed server resides. This will delete the managed server, and also update the respective context variables that contain references to the deleted managed server.
$ perl $AD_TOP
ebs-delete-managedserver \
-contextfile=
-servicetype=
For example, for deleting a managed server 'oacore_server2' of type 'oacore', execute the following command:
$ perl $AD_TOP
ebs-delete-managedserver \
-contextfile=
-servicetype=oacore -logfile=$APPLRGF/TXK/delMS_oacoreserver2.log
Step 3:
Perform the following steps on all application tier nodes participating in the same cluster as the deleted managed server:
Source the run file system.
If the deleted managed server is part of the cluster configuration defined on the current node, execute the following command to delete details of the managed server from the OHS configuration files mod_wl_ohs.conf and apps.conf on the current node:
$ perl $FND_TOP/patch/115/bin/txkSetAppsConf.pl \
-contextfile=<context_file> \
-configoption=removeMS \
-oacore=<host>.<domain>:port \
-oafm=<host>.<domain>:port \
-forms=<host>.<domain>:port \
-formsc4ws=<host>.<domain>:port \
-ekanban=<host>.<domain>:port \
-accessgate=<host>.<domain>:port \
-yms=<host>.<domain>:port
where
The argument contextfile accepts the complete path to the context file.
The arguments oacore, oafm, forms, formsc4ws, ekanban, accessgate and yms accept a comma-separated list of managed server details in the following format:
host, domain and port are the hostname, domain and port of the managed server whose reference is to be deleted.
For example, to remove references of the deleted managed server oacore_server2 with port 7205 on host 'testserver' and domain 'example.com', the following command should be executed:
$ perl $FND_TOP
-configoption=removeMS -oacore=testserver.example.com:7205
Step 4:
If Oracle HTTP Server is enabled on the node, restart it as follows:
On UNIX:
$ sh
$ sh
Reference:
Managing Configuration of Oracle HTTP Server and Web Application Services in Oracle E-Business Suite Release 12.2 (Doc ID 1905593.1)
How to Create New Application user from an existing user in Oracle Apps R12
In this post I am going to share the steps to create an application user from an exiting user.
This can be used to create a user in same EBS instance or any other EBS instance.
I am creating a new user with name john.cena from existing user himanshu.singh . This I am doing on the same EBS instance. This will bring all responsibility also to user.
SOURCE USER : himanshu.singh
TARGET USER : john.cena
To find the responsibilities of source user:
set pages 1200
set lines 200
SELECT frt.RESPONSIBILITY_NAME, furg.end_date
FROM
fnd_user_resp_groups furg,
FND_RESPONSIBILITY fr,fnd_responsibility_tl frt,fnd_user fu
WHERE fu.user_name = '&username'
AND fu.user_id = furg.user_id
AND furg.responsibility_id = fr.RESPONSIBILITY_ID
AND frt.responsibility_id = fr.RESPONSIBILITY_ID
ORDER BY 1;
STEP 1: Use FNDLOAD to download user himanshu.singh from source instance:
FNDLOAD apps/apps 0 Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct user_metadata.ldt FND_USER USER_NAME=himanshu.singh
STEP 2: Modify the ldt file (himanshu.singh_USER.ldt for the example above):
Change the line to
BEGIN FND_USER “john.cena”
OWNER = “APPSMGR”
LAST_UPDATE_DATE = “2014/01/06”
START_DATE = “1951/01/01”
In case you are doing in other instance transfer the to other instance using scp or some other command.
STEP 3: Use FNDLOAD to upload new user to target instance:
FNDLOAD apps/apps 0 Y UPLOAD $FND_TOP/patch/115/import/afscursp.lct user_metadata.ldt FND_USER USER_NAME=john.cena
STEP 4: Change the password of the new user from application front end,email and other details as required.
This can be used to create a user in same EBS instance or any other EBS instance.
I am creating a new user with name john.cena from existing user himanshu.singh . This I am doing on the same EBS instance. This will bring all responsibility also to user.
SOURCE USER : himanshu.singh
TARGET USER : john.cena
To find the responsibilities of source user:
set pages 1200
set lines 200
SELECT frt.RESPONSIBILITY_NAME, furg.end_date
FROM
fnd_user_resp_groups furg,
FND_RESPONSIBILITY fr,fnd_responsibility_tl frt,fnd_user fu
WHERE fu.user_name = '&username'
AND fu.user_id = furg.user_id
AND furg.responsibility_id = fr.RESPONSIBILITY_ID
AND frt.responsibility_id = fr.RESPONSIBILITY_ID
ORDER BY 1;
STEP 1: Use FNDLOAD to download user himanshu.singh from source instance:
FNDLOAD apps/apps 0 Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct user_metadata.ldt FND_USER USER_NAME=himanshu.singh
STEP 2: Modify the ldt file (himanshu.singh_USER.ldt for the example above):
Change the line
BEGIN FND_USER “john.cena”
OWNER = “APPSMGR”
LAST_UPDATE_DATE = “2014/01/06”
START_DATE = “1951/01/01”
In case you are doing in other instance transfer the to other instance using scp or some other command.
STEP 3: Use FNDLOAD to upload new user to target instance:
FNDLOAD apps/apps 0 Y UPLOAD $FND_TOP/patch/115/import/afscursp.lct user_metadata.ldt FND_USER USER_NAME=john.cena
STEP 4: Change the password of the new user from application front end,email and other details as required.
Understanding Service Groups in R12.2
The Applications services are categorized into service
groups according to the type of service provided. They were enabled and disabled
as per the requirement.
Link to earlier post Service
group in R12.
In this post we are going to see the services
group in R12.2 and changes when compared to previous versions.
Root Service Group: It contains Node Manager and not Oracle
Process Manager (OPMN) as in previous version. Node manager services should run
on all application nodes.
Web Administration Service
Group: has been introduced
in Release 12.2 and it contains WebLogic Administration server. It is not
supported to enable WebLogic Administration server on any other Application
tier node except the node on which it was enabled during Rapid Install.
Web Entry Point Services
Group: In R12.2 OPMN only
manages Oracle HTTP Server and it is now part of the
|
Service Group
|
Service(s)
|
Service Control Script
|
|
Root Service
|
Node Manager
|
adnodemgrctl.sh
|
|
Web Administration
|
WebLogic Admin
Server
|
adadminsrvctl.sh
|
|
Web Entry Point Services
|
Oracle HTTP Server
|
adapcctl.sh
|
|
Oracle Process
Manager
|
adopmnctl.sh
|
|
|
Web Application Services
|
oacore
|
admanagedsrvctl.sh
|
|
oafm
|
admanagedsrvctl.sh
|
|
|
forms
|
admanagedsrvctl.sh
|
|
|
forms-c4ws
|
admanagedsrvctl.sh
|
|
|
Batch Processing Services
|
Oracle TNS Listener
|
adalnctl.sh
|
|
Concurrent Manager
|
adcmctl.sh
|
|
|
Fulfillment Server
|
jtffmctl.sh
|
|
|
Oracle ICSM
|
ieoicsm.sh
|
|
|
Other Services
|
Forms Server
|
adformsrvctl.sh
|
|
Oracle MWA Service
|
mwactlwrpr.sh
|
Parameters in Context file related to Service Groups
Cloning EBS R12.2.5 Environment Step by Step
Cloning EBS R12.2.5 Environment
Pre-Req Tasks:
1.
Make sure all rpms all installed as
we installed during our EBS installation process.
2.
Make sure we had the oracle and
applmgr user created on target system.
Note: I am taking a cold backup from source in this post as I am focusing on the cloning procedure and creating a new target machine with EBS cloned environment.
Note: I am taking a cold backup from source in this post as I am focusing on the cloning procedure and creating a new target machine with EBS cloned environment.
Preparation of the Source DB Tier:
1.
Make sure to have latest appsutil
on database side.
2.
Login to Database node as oracle.
3.
Download patch 17537119 from My
Oracle Support, unzip it under /u01/database/SEBS122/12.1.0/appsutil/etcc and
run /u01/database/SEBS122/12.1.0/appsutil/etcc/checkDBpatch.sh to avoid ADOP
related issues.
4.
Go to Oracle
Home>appsutil/scripts/$CONTEXT_NAME/
Run
perl adpreclone.pl dbTier
[oracle@sebs
SEBS122_sebs]$ perl adpreclone.pl dbTier
Copyright (c) 2011, 2014
Oracle Corporation
Redwood Shores, California, USA
Oracle E-Business Suite
Rapid Clone
Version 12.2
adpreclone Version
120.31.12020000.22
Enter the
APPS User Password:
Verifying
if Database Patch checker (ETCC) exists in
/u01/database/SEBS122/12.1.0/appsutil/etcc
Running:
perl
/u01/database/SEBS122/12.1.0/appsutil/bin/adclone.pl
java=/u01/database/SEBS122/12.1.0/jdk mode=stage
stage=/u01/database/SEBS122/12.1.0/appsutil/clone component=dbTier
method=CUSTOM dbctx=/u01/database/SEBS122/12.1.0/appsutil/SEBS122_sebs.xml
showProgress
Beginning
database tier Stage - Tue Mar 27 08:00:23 2018
/u01/database/SEBS122/12.1.0/jdk/bin/java
-Xmx600M -DCONTEXT_VALIDATED=false -Doracle.installer.oui_loc=/u01/database/SEBS122/12.1.0/oui
-classpath
/u01/database/SEBS122/12.1.0/lib/xmlparserv2.jar:/u01/database/SEBS122/12.1.0/jdbc/lib/ojdbc6.jar:/u01/database/SEBS122/12.1.0/appsutil/java:/u01/database/SEBS122/12.1.0/oui/jlib/OraInstaller.jar:/u01/database/SEBS122/12.1.0/oui/jlib/ewt3.jar:/u01/database/SEBS122/12.1.0/oui/jlib/share.jar:/u01/database/SEBS122/12.1.0/oui/jlib/srvm.jar:/u01/database/SEBS122/12.1.0/jlib/ojmisc.jar oracle.apps.ad.clone.StageDBTier -e
/u01/database/SEBS122/12.1.0/appsutil/SEBS122_sebs.xml -stage
/u01/database/SEBS122/12.1.0/appsutil/clone -tmp /tmp -method CUSTOM -showProgress
APPS
Password :
Log file
located at
/u01/database/SEBS122/12.1.0/appsutil/log/SEBS122_sebs/StageDBTier_03270800.log
\
50% completed
Completed
Stage...
Tue Mar 27
08:01:43 2018
5.
Go to Application server and login
as applmgr
6.
cd $ADMIN_SCRIPTS_HOME
perl adpreclone.pl appsTier
[applmgr@sebs scripts]$ perl adpreclone.pl appsTier
Copyright (c) 2011, 2014 Oracle Corporation
Redwood Shores, California, USA
Oracle E-Business Suite Rapid Clone
Version 12.2
adpreclone Version 120.31.12020000.22
Enter the APPS User Password:
Enter the Weblogic AdminServer password :
Checking the
status of the Oracle WebLogic Administration Server....
Running perl
/u01/application/SEBS122/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/adProvisionEBS.pl
ebs-get-serverstatus
-contextfile=/u01/application/SEBS122/fs2/inst/apps/SEBS122_sebs/appl/admin/SEBS122_sebs.xml
-servername=AdminServer -promptmsg=hide
The Oracle WebLogic Administration Server is up.
Running:
perl
/u01/application/SEBS122/fs2/EBSapps/appl/ad/12.0.0/bin/adclone.pl
java=/u01/application/SEBS122/fs2/EBSapps/comn/util/jdk64 mode=stage
stage=/u01/application/SEBS122/fs2/EBSapps/comn/clone component=appsTier
method= appctx=/u01/application/SEBS122/fs2/inst/apps/SEBS122_sebs/appl/admin/SEBS122_sebs.xml
showProgress
Setting the wls
environment
Beginning application tier Stage - Tue Mar 27 08:30:45
2018
/u01/application/SEBS122/fs2/EBSapps/comn/util/jdk64/bin/java
-Xmx600M -DCONTEXT_VALIDATED=false -Doracle.installer.oui_loc=/oui -classpath
/u01/application/SEBS122/fs2/FMW_Home/webtier/lib/xmlparserv2.jar:/u01/application/SEBS122/fs2/FMW_Home/webtier/jdbc/lib/ojdbc6.jar:/u01/application/SEBS122/fs2/EBSapps/comn/java/classes:/u01/application/SEBS122/fs2/FMW_Home/webtier/oui/jlib/OraInstaller.jar:/u01/application/SEBS122/fs2/FMW_Home/webtier/oui/jlib/ewt3.jar:/u01/application/SEBS122/fs2/FMW_Home/webtier/oui/jlib/share.jar:/u01/application/SEBS122/fs2/FMW_Home/webtier/../Oracle_EBS-app1/oui/jlib/srvm.jar:/u01/application/SEBS122/fs2/FMW_Home/webtier/jlib/ojmisc.jar:/u01/application/SEBS122/fs2/FMW_Home/wlserver_10.3/server/lib/weblogic.jar:/u01/application/SEBS122/fs2/FMW_Home/oracle_common/jlib/obfuscatepassword.jar oracle.apps.ad.clone.StageAppsTier -e
/u01/application/SEBS122/fs2/inst/apps/SEBS122_sebs/appl/admin/SEBS122_sebs.xml
-stage /u01/application/SEBS122/fs2/EBSapps/comn/clone -tmp /tmp -method
CUSTOM -showProgress -nopromptmsg
Log file located at
/u01/application/SEBS122/fs2/inst/apps/SEBS122_sebs/admin/log/clone/StageAppsTier_03270830.log
/ 20% completed
Completed Stage...
Tue Mar 27 08:56:25 2018
7.
Stop the application services and
database services on your source system.
8.
Take a backup of database files and
Oracle Home from database node.
9.
Take a backup EBSapps directory of
your RUN file system on fs1/fs2.
10. Go to database node and then go to Oracle Base
directory.
11. tar
-zcvf data.tar.gz data
12. tar
-zxvf 12.1.0.tar.gz 12.1.0
13. Go
to appplication node
14. cd
$RUN_BASE/..
tar -zxvf EBSapps.tar.gz EBSapps
15. Login
to target machine
Make sure below users exists
[root@clone122 u01]# id oracle
uid=54321(oracle) gid=54321(oinstall)
groups=54321(oinstall),492(vboxsf),54322(dba)
[root@clone122 u01]# id applmgr
uid=54322(applmgr) gid=54321(oinstall)
groups=54321(oinstall),492(vboxsf),54322(dba)
16. Make
sure you have below directories.
[root@clone122 u01]# chown -R oracle:dba oracle
database
[root@clone122 u01]# chown -R applmgr:dba application
[root@clone122 u01]# ls -ltr
total 28
drwx------. 2 root
root 16384 Feb 19 22:20 lost+found
drwxr-xr-x. 3 oracle
dba 4096 Feb 21 21:51 oracle
drwxrwxrwx. 2 oracle
dba 4096 Mar 25 22:39 database
drwxrwxrwx. 2 applmgr dba 4096 Mar 25 22:46 application
[root@clone122 u01]# chmod -R 777 oracle database/
application/
[root@clone122 u01]# ls -ltr
total 28
drwx------. 2 root
root 16384 Feb 19 22:20 lost+found
drwxrwxrwx. 3 oracle
dba 4096 Feb 21 21:51 oracle
drwxrwxrwx. 2 oracle
dba 4096 Mar 25 22:39 database
drwxrwxrwx. 2 applmgr dba 4096 Mar 25 22:46 application
17. [oracle@clone122
TESTCLN]$ pwd
/u01/database/TESTCLN
18. Copy
the database home and data tar file to this directory.
19. Create folder on application end as well.
[applmgr@clone122 application]$ pwd
/u01/application
[applmgr@clone122 application]$ ls -ltr
total 4
drwxrwxrwx. 2 applmgr oinstall 4096 Mar 28 22:00 TESTCLN
20. Create
application file system.
[applmgr@clone122 application]$ pwd
/u01/application
[applmgr@clone122 application]$ ls -ltr
total 4
drwxrwxrwx. 2 applmgr oinstall 4096 Mar 28 22:00
TESTCLN
[applmgr@clone122 application]$ cd TESTCLN
[applmgr@clone122 TESTCLN]$ ls -ltr
total 0
[applmgr@clone122 TESTCLN]$ ls
[applmgr@clone122 TESTCLN]$ mkdir fs1 fs2
[applmgr@clone122 TESTCLN]$ mkdir fs_ne
[applmgr@clone122 TESTCLN]$ ls -ltr
total 12
drwxr-xr-x. 2 applmgr oinstall 4096 Mar 28 22:02 fs2
drwxr-xr-x. 2 applmgr oinstall 4096 Mar 28 22:02 fs1
drwxr-xr-x. 2 applmgr oinstall 4096 Mar 28 22:02 fs_ne
21. Copy
EBSapps.tar.gz to fs2 on target system.
22. Untar
the 3 files files.
tar -zxvf
23. Once
Untar is done , please remove tar files to release space.
24. On
Database Node
export ORACLE_HOME=/u01/database/TESTCLN/12.1.0
export
PATH=$ORACLE_HOME/perl/bin:$ORACLE_HOME/bin:$PATH
export ORACLE_SID=TEST122
cd /u01/database/TESTCLN/12.1.0/appsutil
mkdir -p jre/bin
cd jre/bin
ln -s /usr/bin/java java
25. Goto
Oracle home and move to clone directory.
Cd /u01/database/TESTCLN/12.1.0/appsutil/clone/bin
26. Configure
Database Node.
[oracle@clone122
bin]$ perl adcfgclone.pl dbTier
Copyright (c) 2002, 2015
Oracle Corporation
Redwood Shores,
California, USA
Oracle E-Business Suite
Rapid Clone
Version 12.2
adcfgclone Version
120.63.12020000.60
Enter the
APPS password :
Running:
Context clone...
Log file
located at
/u01/database/TESTCLN/12.1.0/appsutil/clone/bin/CloneContext_0329222240.log
Provide the
values required for creation of the new Database Context file.
Target
System Hostname (virtual or normal) [clone122] :
Target
Instance is RAC (y/n) [n] : n
Target
System Database SID : TEST122
Target
System Base Directory : /u01/database/TESTCLN
Role
separation is supported y/n [n] ? : n
Target
System utl_file_dir Directory List : /tmp
Number of
DATA_TOP's on the Target System [1] :
Target
System DATA_TOP Directory 1 [/u01/database/TESTCLN/data] :
Target
System RDBMS ORACLE_HOME Directory [/u01/database/TESTCLN/12.1.0] :
Do you want
to preserve the Display [:0.0] (y/n) : n
Target
System Display [clone122:0.0] :
Do you want
the target system to have the same port values as the source system (y/n) [y] ?
: n
Target
System Port Pool [0-99] : 40
Checking
the port pool 40
done: Port
Pool 40 is free
Report file
located at /u01/database/TESTCLN/12.1.0/appsutil/temp/portpool.lst
The new
database context file has been created :
/u01/database/TESTCLN/12.1.0/appsutil/TEST122_clone122.xml
Check Clone
Context logfile /u01/database/TESTCLN/12.1.0/appsutil/clone/bin/CloneContext_0329222240.log
for details.
Running
Rapid Clone with command:
Running:
perl
/u01/database/TESTCLN/12.1.0/appsutil/clone/bin/adclone.pl
java=/u01/database/TESTCLN/12.1.0/appsutil/clone/bin/../jre mode=apply
stage=/u01/database/TESTCLN/12.1.0/appsutil/clone component=dbTier
method=CUSTOM
dbctxtg=/u01/database/TESTCLN/12.1.0/appsutil/TEST122_clone122.xml showProgress
contextValidated=true
Beginning
database tier Apply - Thu Mar 29 22:23:29 2018
/u01/database/TESTCLN/12.1.0/appsutil/clone/bin/../jre/bin/java
-Xmx600M -DCONTEXT_VALIDATED=true
-Doracle.installer.oui_loc=/u01/database/TESTCLN/12.1.0/oui -classpath
/u01/database/TESTCLN/12.1.0/appsutil/clone/jlib/xmlparserv2.jar:/u01/database/TESTCLN/12.1.0/appsutil/clone/jlib/ojdbc6.jar:/u01/database/TESTCLN/12.1.0/appsutil/clone/jlib/java:/u01/database/TESTCLN/12.1.0/appsutil/clone/jlib/oui/OraInstaller.jar:/u01/database/TESTCLN/12.1.0/appsutil/clone/jlib/oui/ewt3.jar:/u01/database/TESTCLN/12.1.0/appsutil/clone/jlib/oui/share.jar:/u01/database/TESTCLN/12.1.0/appsutil/clone/jlib/oui/srvm.jar:/u01/database/TESTCLN/12.1.0/appsutil/clone/jlib/ojmisc.jar oracle.apps.ad.clone.ApplyDBTier -e
/u01/database/TESTCLN/12.1.0/appsutil/TEST122_clone122.xml -stage
/u01/database/TESTCLN/12.1.0/appsutil/clone
-showProgress
APPS
Password : Log file located at
/u01/database/TESTCLN/12.1.0/appsutil/log/TEST122_clone122/ApplyDBTier_03292223.log
/
15% completed
Completed
Apply...
Thu Mar 29
22:39:07 2018
Starting
database listener for TEST122:
Running:
/u01/database/TESTCLN/12.1.0/appsutil/scripts/TEST122_clone122/addlnctl.sh
start TEST122
Logfile:
/u01/database/TESTCLN/12.1.0/appsutil/log/TEST122_clone122/addlnctl.txt
You are
running addlnctl.sh version 120.4
Starting
listener process TEST122 ...
Listener
TEST122 has already been started.
addlnctl.sh:
exiting with status 0
addlnctl.sh:
check the logfile
/u01/database/TESTCLN/12.1.0/appsutil/log/TEST122_clone122/addlnctl.txt for
more information ...
Do you want
to change the password for all EBS Schemas? (y/n) [n]) : n
Do you want
to change the password for sysadmin user? (y/n) [n]) : n
Do you want
to change the apps password? (y/n) [n]) : n
Do you want
to change the sys and system passwords? (y/n) [n]) : n
Running
ETCC to check status of DB technology patches...
+===============================================================+
|
Copyright (c) 2005, 2017 Oracle and/or its affiliates. |
| All rights reserved. |
| Oracle E-Business Suite Release
12.2 |
|
Database EBS Technology Codelevel Checker |
+===============================================================+
Using
context file from command line argument:
/u01/database/TESTCLN/12.1.0/appsutil/TEST122_clone122.xml
Starting
Database EBS Technology Codelevel Checker, Version 120.57
Thu Mar 29
22:39:59 EDT 2018
Log file
for this session :
/u01/database/TESTCLN/12.1.0/appsutil/etcc/checkDBpatch_19693.log
Bugfix XML
file /u01/database/TESTCLN/12.1.0/appsutil/etcc/txk_R1220_DB_base_bugs.xml
version: 120.0.12020000.41
This file
will be used for identifying missing bugfixes.
Mapping XML
file /u01/database/TESTCLN/12.1.0/appsutil/etcc/txk_R1220_DB_mappings.xml
version: 120.0.12020000.15
This file
will be used for mapping bugfixes to patches.
[WARNING]
DB-ETCC: Bugfix XML file
(/u01/database/TESTCLN/12.1.0/appsutil/etcc/txk_R1220_DB_base_bugs.xml) in
current directory is more than 30 days old.
Check if a newer version is available in patch
17537119.
Identifying
database release.
Database
release set to 12.1.0.2.
Connecting
to database.
Database
connection successful.
Database
TEST122 is in READ WRITE mode.
Identifying
APPS and APPLSYS schema names.
- APPS schema : APPS
- APPLSYS schema : APPLSYS
Checking
for DB-ETCC results table.
Table to
store DB-ETCC results already exists in the database.
Checking if
InMemory option is enabled.
InMemory
option is not enabled in the database.
Checking
Bugfix XML file for 12.1.0.2
Obtained
list of bugfixes to be applied and the list to be rolled back.
Now
checking Database ORACLE_HOME.
The opatch
utility is version 12.1.0.1.10.
DB-ETCC is
compatible with this opatch version.
Found patch
records in the inventory.
Checking
Mapping XML file for 12.1.0.2
All the
required one-off bugfixes are present in Database ORACLE_HOME.
Stored
Technology Codelevel Checker results in the database TEST122 successfully.
Finished
checking fixes for Oracle Database: Thu Mar 29 22:40:44 EDT 2018
Log file
for this session:
/u01/database/TESTCLN/12.1.0/appsutil/etcc/checkDBpatch_19693.log
===============================================================================
27. Create a Environment file on Database node
[oracle@clone122 ~]$ ln -s /u01/database/TESTCLN/12.1.0/TEST122_clone122.env
[oracle@clone122 ~]$ ls -ltr
total 0
lrwxrwxrwx. 1 oracle oinstall 49 Mar 29 22:42
TEST122_clone122.env -> /u01/database/TESTCLN/12.1.0/TEST122_clone122.env
[oracle@clone122 ~]$ . TEST122_clone122.env
[oracle@clone122 ~]$ sqlplus '/as sysdba'
SQL*Plus: Release 12.1.0.2.0 Production on Thu Mar 29
22:43:09 2018
Copyright (c) 1982, 2014, Oracle. All rights reserved.
Connected to:
Oracle Database 12c Enterprise Edition Release
12.1.0.2.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and
Real Application Testing options
SQL> select name from v$database;
NAME
---------
TEST122
28. Login
to application node (applmgr)
29. Goto
Directory where we untar the EBSapps . i.e fs2 in our case.
30. Goto
clone/bin directory.
[applmgr@clone122 bin]$ pwd
/u01/application/TESTCLN/fs2/EBSapps/comn/clone/bin
[applmgr@clone122 bin]$ ls -ltr
total 292
-rwxr-xr-x. 1 applmgr oinstall 96789 Mar 26 23:01 adclone.pl
-rwxr-xr-x. 1 applmgr oinstall 48268 Mar 26 23:01 adclonectx.pl
-rwxr-xr-x. 1 applmgr oinstall 5101 Mar 26 23:01 adchkutl.sh
-rwxr-xr-x. 1 applmgr oinstall 127116 Mar 26 23:01
adcfgclone.pl
-rwxr-xr-x. 1 applmgr oinstall 10887 Mar 26 23:01 adaddnode.pl
31. Run
adcfgclone.pl appsTier dualfs
[applmgr@clone122 bin]$ perl adcfgclone.pl appsTier
dualfs
Copyright (c) 2002, 2015 Oracle Corporation
Redwood Shores, California, USA
Oracle E-Business Suite Rapid Clone
Version 12.2
adcfgclone Version 120.63.12020000.60
Enter the APPS password :
Enter the Weblogic AdminServer password :
Do you want to add a node (yes/no) [no] : no
Running: Context clone...
Log file located at
/u01/application/TESTCLN/fs2/EBSapps/comn/clone/bin/CloneContext_0329225840.log
Provide the values required for creation of the new
APPL_TOP Context file.
Target System Hostname (virtual or normal) [clone122]
:
Target System Database SID : TEST122
Target System Database Server Node [clone122] :
Target System Database Domain Name [training] :
Target System Base Directory :
/u01/application/TESTCLN
Target System Base Directory set to
/u01/application/TESTCLN
Target System Current File System Base set to
/u01/application/TESTCLN/fs2
Target System Other File System Base set to
/u01/application/TESTCLN/fs1
Target System Fusion Middleware Home set to
/u01/application/TESTCLN/fs2/FMW_Home
Target System Other File System Fusion Middleware Home
set to /u01/application/TESTCLN/fs1/FMW_Home
Target System Web Oracle Home set to
/u01/application/TESTCLN/fs2/FMW_Home/webtier
Target System Other File System Web Oracle Home set to
/u01/application/TESTCLN/fs1/FMW_Home/webtier
Target System Appl TOP set to
/u01/application/TESTCLN/fs2/EBSapps/appl
Target System Other File System Appl TOP set to
/u01/application/TESTCLN/fs1/EBSapps/appl
Target System COMMON TOP set to
/u01/application/TESTCLN/fs2/EBSapps/comn
Target System Other File System COMMON TOP set to
/u01/application/TESTCLN/fs1/EBSapps/comn
Target System Instance Home Directory
[/u01/application/TESTCLN] :
Target System Current File System Instance Top set to
/u01/application/TESTCLN/fs2/inst/apps/TEST122_clone122
Do you want to preserve the Display [sebs:0.0]
(y/n) : n
Target System Display [clone122:0.0] :
Target System Root Service [enabled] :
Target System Web Entry Point Services [enabled] :
Target System Web Application Services [enabled] :
Target System Batch Processing Services [enabled] :
Target System Other Services [disabled] :
Do you want the target system to have the same port
values as the source system (y/n) [y] ? : n
Target System Port Pool [0-99] : 40
Checking the port pool 40
done: Port Pool 40 is free
Report file located at
/u01/application/TESTCLN/fs2/inst/apps/TEST122_clone122/admin/out/portpool.lst
UTL_FILE_DIR on database tier consists of the
following directories.
1. /usr/tmp
2. /tmp
3. /u01/database/TESTCLN/12.1.0/appsutil/outbound/TEST122_clone122
4. /usr/tmp
Choose a value which will be set as APPLPTMP value on
the target node [1] : 3
The new APPL_TOP context file has been created :
/u01/application/TESTCLN/fs2/inst/apps/TEST122_clone122/appl/admin/TEST122_clone122.xml
Check Clone Context logfile
/u01/application/TESTCLN/fs2/EBSapps/comn/clone/bin/CloneContext_0329225840.log
for details.
Creating Patch file system context file.....
Log file located at
/u01/application/TESTCLN/fs2/EBSapps/comn/clone/bin/CloneContextPatch_0329230352.log
Target System Other File System Instance Top set to
/u01/application/TESTCLN/fs1/inst/apps/TEST122_clone122
Target System Port Pool [0-99] : 50
Checking the port pool 50
done: Port Pool 50 is free
Report file located at /u01/application/TESTCLN/fs1/inst/apps/TEST122_clone122/admin/out/portpool.lst
The new APPL_TOP context file has been created :
/u01/application/TESTCLN/fs1/inst/apps/TEST122_clone122/appl/admin/TEST122_clone122.xml
Check Clone Context logfile /u01/application/TESTCLN/fs2/EBSapps/comn/clone/bin/CloneContextPatch_0329230352.log
for details.
FMW Pre-requisite check log file location :
/u01/application/TESTCLN/fs2/EBSapps/comn/clone/FMW/logs/prereqcheck.log
Running: FMW pre-req check...
Configuring: Run file system....
LogFile located at
/u01/application/TESTCLN/fs2/inst/apps/TEST122_clone122/admin/log/clone/run/RCloneApplyAppstier_03292305.log
Configuring: Patch file system....
LogFile located at
/u01/application/TESTCLN/fs2/inst/apps/TEST122_clone122/admin/log/clone/patch/RCloneApplyAppstier_03300007.log
Do you want to startup the Application Services for
TEST122? (y/n) [n] : y
Starting application Services for TEST122:
You are running adstrtal.sh version 120.24.12020000.11
The logfile for this session is located at
/u01/application/TESTCLN/fs2/inst/apps/TEST122_clone122/logs/appl/admin/log/adstrtal.log
Executing service control script:
/u01/application/TESTCLN/fs2/inst/apps/TEST122_clone122/admin/scripts/jtffmctl.sh
start
Timeout specified in context file: 100 second(s)
script returned:
****************************************************
You are running jtffmctl.sh version 120.3.12020000.4
Validating Fulfillment patch level via
/u01/application/TESTCLN/fs2/EBSapps/comn/java/classes
Fulfillment patch level validated.
Starting Fulfillment Server for TEST122 on port 9340
...
jtffmctl.sh: exiting with status 0
.end std out.
.end err out.
****************************************************
Executing service control script:
/u01/application/TESTCLN/fs2/inst/apps/TEST122_clone122/admin/scripts/adopmnctl.sh
start
Timeout specified in context file: 100 second(s)
script returned:
****************************************************
You are running adopmnctl.sh version 120.0.12020000.2
Starting Oracle Process Manager (OPMN) ...
adopmnctl.sh: exiting with status 0
adopmnctl.sh: check the logfile
/u01/application/TESTCLN/fs2/inst/apps/TEST122_clone122/logs/appl/admin/log/adopmnctl.txt
for more information ...
.end std out.
.end err out.
****************************************************
Executing service control script:
/u01/application/TESTCLN/fs2/inst/apps/TEST122_clone122/admin/scripts/adapcctl.sh
start
Timeout specified in context file: 100 second(s)
script returned:
****************************************************
You are running adapcctl.sh version 120.0.12020000.6
Starting OPMN managed Oracle HTTP Server (OHS)
instance ...
adapcctl.sh: exiting with status 0
adapcctl.sh: check the logfile /u01/application/TESTCLN/fs2/inst/apps/TEST122_clone122/logs/appl/admin/log/adapcctl.txt
for more information ...
.end std out.
.end err out.
****************************************************
Executing service control script:
/u01/application/TESTCLN/fs2/inst/apps/TEST122_clone122/admin/scripts/adnodemgrctl.sh
start -nopromptmsg
Timeout specified in context file: -1 second(s)
script returned:
****************************************************
You are running adnodemgrctl.sh version
120.11.12020000.12
Calling txkChkEBSDependecies.pl to perform dependency
checks for ALL MANAGED SERVERS
Perl script txkChkEBSDependecies.pl got executed
successfully
Starting the Node Manager...
Refer /u01/application/TESTCLN/fs2/inst/apps/TEST122_clone122/logs/appl/admin/log/adnodemgrctl.txt
for details
NodeManager log is located at
/u01/application/TESTCLN/fs2/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1
adnodemgrctl.sh: exiting with status 0
adnodemgrctl.sh: check the logfile /u01/application/TESTCLN/fs2/inst/apps/TEST122_clone122/logs/appl/admin/log/adnodemgrctl.txt
for more information ...
.end std out.
*** ALL THE FOLLOWING FILES ARE REQUIRED FOR RESOLVING
RUNTIME ERRORS
*** Log File =
/u01/application/TESTCLN/fs2/inst/apps/TEST122_clone122/logs/appl/rgf/TXK/txkChkEBSDependecies_Fri_Mar_30_03_18_54_2018/txkChkEBSDependecies_Fri_Mar_30_03_18_54_2018.log
.end err out.
****************************************************
Executing service control script:
/u01/application/TESTCLN/fs2/inst/apps/TEST122_clone122/admin/scripts/adalnctl.sh
start
Timeout specified in context file: 100 second(s)
script returned:
****************************************************
adalnctl.sh version 120.3.12020000.4
Checking for FNDFS executable.
Starting listener process APPS_TEST122.
adalnctl.sh: exiting with status 0
adalnctl.sh: check the logfile
/u01/application/TESTCLN/fs2/inst/apps/TEST122_clone122/logs/appl/admin/log/adalnctl.txt
for more information ...
.end std out.
.end err out.
****************************************************
Executing service control script:
/u01/application/TESTCLN/fs2/inst/apps/TEST122_clone122/admin/scripts/adcmctl.sh
start
Timeout specified in context file: 1000 second(s)
script returned:
****************************************************
You are running adcmctl.sh version 120.19.12020000.7
Starting concurrent manager for TEST122 ...
Starting TEST122_0330@TEST122 Internal Concurrent
Manager
Default printer is noprint
adcmctl.sh: exiting with status 0
adcmctl.sh: check the logfile
/u01/application/TESTCLN/fs2/inst/apps/TEST122_clone122/logs/appl/admin/log/adcmctl.txt
for more information ...
.end std out.
.end err out.
****************************************************
Executing service control script:
/u01/application/TESTCLN/fs2/inst/apps/TEST122_clone122/admin/scripts/adadminsrvctl.sh
start -nopromptmsg
Timeout specified in context file: -1 second(s)
script returned:
****************************************************
You are running adadminsrvctl.sh version
120.10.12020000.10
Starting WLS Admin Server...
Refer
/u01/application/TESTCLN/fs2/inst/apps/TEST122_clone122/logs/appl/admin/log/adadminsrvctl.txt
for details
AdminServer logs are located at
/u01/application/TESTCLN/fs2/FMW_Home/user_projects/domains/EBS_domain_TEST122/servers/AdminServer/logs
adadminsrvctl.sh: exiting with status 0
adadminsrvctl.sh: check the logfile
/u01/application/TESTCLN/fs2/inst/apps/TEST122_clone122/logs/appl/admin/log/adadminsrvctl.txt
for more information ...
.end std out.
.end err out.
****************************************************
Executing service control script:
/u01/application/TESTCLN/fs2/inst/apps/TEST122_clone122/admin/scripts/admanagedsrvctl.sh
start forms_server1 -nopromptmsg
Timeout specified in context file: -1 second(s)
script returned:
****************************************************
You are running admanagedsrvctl.sh version
120.14.12020000.11
Starting forms_server1...
Server specific logs are located at
/u01/application/TESTCLN/fs2/FMW_Home/user_projects/domains/EBS_domain_TEST122/servers/forms_server1/logs
admanagedsrvctl.sh: exiting with status 0
admanagedsrvctl.sh: check the logfile /u01/application/TESTCLN/fs2/inst/apps/TEST122_clone122/logs/appl/admin/log/adformsctl.txt
for more information ...
.end std out.
.end err out.
****************************************************
Executing service control script:
/u01/application/TESTCLN/fs2/inst/apps/TEST122_clone122/admin/scripts/admanagedsrvctl.sh
start oafm_server1 -nopromptmsg
Timeout specified in context file: -1 second(s)
script returned:
****************************************************
You are running admanagedsrvctl.sh version 120.14.12020000.11
Starting oafm_server1...
Server specific logs are located at
/u01/application/TESTCLN/fs2/FMW_Home/user_projects/domains/EBS_domain_TEST122/servers/oafm_server1/logs
admanagedsrvctl.sh: exiting with status 0
admanagedsrvctl.sh: check the logfile
/u01/application/TESTCLN/fs2/inst/apps/TEST122_clone122/logs/appl/admin/log/adoafmctl.txt
for more information ...
.end std out.
.end err out.
****************************************************
Executing service control script:
/u01/application/TESTCLN/fs2/inst/apps/TEST122_clone122/admin/scripts/admanagedsrvctl.sh
start oacore_server1 -nopromptmsg
Timeout specified in context file: -1 second(s)
script returned:
****************************************************
You are running admanagedsrvctl.sh version
120.14.12020000.11
Starting oacore_server1...
Server specific logs are located at
/u01/application/TESTCLN/fs2/FMW_Home/user_projects/domains/EBS_domain_TEST122/servers/oacore_server1/logs
admanagedsrvctl.sh: exiting with status 0
admanagedsrvctl.sh: check the logfile
/u01/application/TESTCLN/fs2/inst/apps/TEST122_clone122/logs/appl/admin/log/adoacorectl.txt
for more information ...
.end std out.
.end err out.
****************************************************
All enabled services for this node are started.
adstrtal.sh: Exiting with status 0
adstrtal.sh: check the logfile
/u01/application/TESTCLN/fs2/inst/apps/TEST122_clone122/logs/appl/admin/log/adstrtal.log
for more information ...
32. Open
the login link and verify.
To do using RMAN, please follow below post
Subscribe to:
Posts
(
Atom
)
2 comments :
Post a Comment