Starting and Stopping Oracle SSO services

 

1.      1. Stop Services

IP: 172.168.112.28

User:: oracle

[oracle@PRODSSO ~]$ cd scripts/

[oracle@PRODSSO scripts]$ ls

apps.env      nohup.out  shutdowndb.sql  startoam.sh    stopall.sh   stopoid.sh

apps.env.bkp  oam.env    startall.sh     startoid.sh    stopapps.sh  stopotp.sh

db.env        oid.env    startapps.sh    startotp.sh    stopdb.sh

line.txt      otp.env    startdb.sh      startupdb.sql  stopoam.sh

[oracle@PRODSSO scripts]$ sh oam.env

[oracle@PRODSSO scripts]$ ./stopoam.sh

Stopping Weblogic Server...

Initializing WebLogic Scripting Tool (WLST) ...

Welcome to WebLogic Server Administration Scripting Shell

Type help() for help on available commands

Connecting to t3://172.168.112.28:7002 with userid weblogic ...

Successfully connected to Admin Server "AdminServer" that belongs to domain "oam_domain".

Warning: An insecure protocol was used to connect to the server.

To ensure on-the-wire security, the SSL port or Admin port should be used instead.

Shutting down the server AdminServer with force=false while connected to AdminServer ...

Disconnected from weblogic server: AdminServer

Exiting WebLogic Scripting Tool.

Done

Stopping Derby Server...

Derby server stopped.

########################################################################################

<2024-06-13 +03 17:23:21> <Info> <StopNodeManager> <NODEMGR_HOME is already set to /u01/app/oracle/Middleware/Oracle_Home/user_projects/domains/oam_domain/nodemanager>

<2024-06-13 +03 17:23:21> <Info> <StopNodeManager> <Begin>

<2024-06-13 +03 17:23:21> <Info> <StopNodeManager> <Adding NodeManagerHome entry to JAVA_OPTIONS: -DNodeManagerHome=/u01/app/oracle/Middleware/Oracle_Home/user_projects/domains/oam_domain/nodemanager>

<2024-06-13 +03 17:23:21> <Info> <StopNodeManager> <Root Directory already set /u01/app/oracle/Middleware/Oracle_Home/user_projects/domains/oam_domain>

<2024-06-13 +03 17:23:21> <Info> <StopNodeManager> <Found process id from /u01/app/oracle/Middleware/Oracle_Home/user_projects/domains/oam_domain/nodemanager/nodemanager.process.id: 18895>

<2024-06-13 +03 17:23:21> <Info> <StopNodeManager> <Sending signal TERM to 18895>

<2024-06-13 +03 17:23:22> <Info> <StopNodeManager> <End>

/u01/app/oracle/Middleware/Oracle_Home/user_projects/domains/oam_domain/nodemanager/stopnodemanager.log was copied to /u01/app/oracle/Middleware/Oracle_Home/user_projects/domains/oam_domain/nodemanager/nodemanager.log

########################################################################################

[oracle@PRODSSO scripts]$ sh oid.env

[oracle@PRODSSO scripts]$ ./stopoid.sh

Stopping Weblogic Server...

Initializing WebLogic Scripting Tool (WLST) ...

Welcome to WebLogic Server Administration Scripting Shell

Type help() for help on available commands

Connecting to t3://PRODSSO.sipa.local:7001 with userid weblogic ...

Successfully connected to Admin Server "AdminServer" that belongs to domain "oid_domain".

Warning: An insecure protocol was used to connect to the server.

To ensure on-the-wire security, the SSL port or Admin port should be used instead.

Shutting down the server wls_ods1 with force=false while connected to AdminServer ...

Exiting WebLogic Scripting Tool.

Done

Stopping Derby Server...

Derby server stopped.

########################################################################################

Stopping Weblogic Server...

Initializing WebLogic Scripting Tool (WLST) ...

Welcome to WebLogic Server Administration Scripting Shell

Type help() for help on available commands

Connecting to t3://PRODSSO.sipa.local:7001 with userid weblogic ...

Successfully connected to Admin Server "AdminServer" that belongs to domain "oid_domain".

Warning: An insecure protocol was used to connect to the server.

To ensure on-the-wire security, the SSL port or Admin port should be used instead.

Shutting down the server AdminServer with force=false while connected to AdminServer ...

WLST lost connection to the WebLogic Server that you were connected to.

This may happen if the server was shut down or partitioned.

You will have to re-connect to the server once the server is available.

Disconnected from weblogic server: AdminServer

Disconnected from weblogic server:

Exiting WebLogic Scripting Tool.

Done

Stopping Derby Server...

Derby server stopped.

########################################################################################

<2024-06-13 +03 17:24:58> <Info> <StopNodeManager> <NODEMGR_HOME is already set to /u01/app/oracle/Middleware/Oracle_Home/user_projects/domains/oid_domain/nodemanager>

<2024-06-13 +03 17:24:58> <Info> <StopNodeManager> <Begin>

<2024-06-13 +03 17:24:58> <Info> <StopNodeManager> <Adding NodeManagerHome entry to JAVA_OPTIONS: -DNodeManagerHome=/u01/app/oracle/Middleware/Oracle_Home/user_projects/domains/oid_domain/nodemanager>

<2024-06-13 +03 17:24:58> <Info> <StopNodeManager> <Root Directory already set /u01/app/oracle/Middleware/Oracle_Home/user_projects/domains/oid_domain>

<2024-06-13 +03 17:24:58> <Info> <StopNodeManager> <Found process id from /u01/app/oracle/Middleware/Oracle_Home/user_projects/domains/oid_domain/nodemanager/nodemanager.process.id: 10178>

<2024-06-13 +03 17:24:58> <Info> <StopNodeManager> <Sending signal TERM to 10178>

<2024-06-13 +03 17:24:59> <Info> <StopNodeManager> <End>

/u01/app/oracle/Middleware/Oracle_Home/user_projects/domains/oid_domain/nodemanager/stopnodemanager.log was copied to /u01/app/oracle/Middleware/Oracle_Home/user_projects/domains/oid_domain/nodemanager/nodemanager.log

########################################################################################

2.      If needed shutdown the DB and restart the VM

[oracle@PRODSSO ~]$ cd scripts/

[oracle@PRODSSO scripts]$ ls

apps.env      nohup.out  shutdowndb.sql  startoam.sh    stopall.sh   stopoid.sh

apps.env.bkp  oam.env    startall.sh     startoid.sh    stopapps.sh  stopotp.sh

db.env        oid.env    startapps.sh    startotp.sh    stopdb.sh

line.txt      otp.env    startdb.sh      startupdb.sql  stopoam.sh

[oracle@PRODSSO scripts]$ ./db.env

$export ORACLE_HOME=/u01/app/oracle/product/12.2.0/dbhome_1

$export PATH=$ORACLE_HOME/bin:$PATH

$ export ORACLE_SID=SSODB

echo $ORACLE_HOME

which sqlplus

$cd /u01/app/oracle/product/12.2.0/dbhome_1/bin/

./sqlplus / as sysdba

sqlplus / as sysdba

SQL>shut immediate;

lsnrctl status LISTENER

lsnrctl stop LISTENER

---restart the VM and start the db

[oracle@PRODSSO scripts]$ ./db.env

$export ORACLE_HOME=/u01/app/oracle/product/12.2.0/dbhome_1

$export PATH=$ORACLE_HOME/bin:$PATH

$ export ORACLE_SID=SSODB

echo $ORACLE_HOME

which sqlplus

$cd /u01/app/oracle/product/12.2.0/dbhome_1/bin/

./sqlplus / as sysdba

sqlplus / as sysdba

SQL>startup;

lsnrctl start LISTENER

3.      Start Services

[oracle@PRODSSO scripts]$ ./startoid.sh

Start WebLogic Domain was completed

########################################################################################

Start NodeManager was completed

########################################################################################

Start the managed Server wls_ods1  was completed

########################################################################################

 

-          To check oid service is running or not

[oracle@PRODSSO ~]$ ps -ef | grep 'oidldapd'

oracle    1706 32478  0 13:23 pts/1    00:00:00 grep --color=auto oidldapd

oracle   12043     1  0 00:39 ?        00:00:07 /u01/app/oracle/Middleware/fmw12.4/wlserver/../bin/oidldapd connect=oiddb instance=1 inst=1  key=5631 host=PRODSSO.sipa.local

oracle   12058     1  0 00:39 ?        00:02:19 oidldapd                                                                                                      control=12043 connect=oiddb servers=2 worker=6 debug=0 configset=0 instance=1 key=5631 host=PRODSSO.sipa.local logchange=FALSE port=3060 sport=3131

oracle   12219     1  0 00:39 ?        00:02:27 oidldapd                                                                                                      control=12043 connect=oiddb servers=2 worker=6 debug=0 configset=0 instance=1 key=5631 host=PRODSSO.sipa.local logchange=FALSE port=3060 sport=3131

[oracle@PRODSSO ~]$ ps -ef | grep oidldapd | grep -v grep | wc -l

3

If the command results in 0 (zero), it means that the oid instance is not running.

[oracle@PRODSSO scripts]$ sh oam.env

[oracle@PRODSSO scripts]$ ./startoam.sh

Start WebLogic Domain was completed

########################################################################################

########################################################################################

Start NodeManager was completed

########################################################################################

Start the managed Server oam_server1  was completed

########################################################################################

########################################################################################

 

-          To check oam service is running or not

 [oracle@PRODSSO ~]$ ps -ef | grep oam

[oracle@PRODSSO ~]$ ps -ef | grep oam | grep -v grep | wc -l

11

If the command results in 0 (zero), it means that the oam instance is not running.

4.       Start oid component

Note: You have to manually start oid component if you have rebooted the VM because the startoid.sh script doesn't contain command to start oid component.

[oracle@PRODSSO scripts]$ cd /u01/app/oracle/Middleware/Oracle_Home/user_projects/domains/oid_domain/bin/

-          To check the oid component is running or not

[oracle@PRODSSO ~]$ netstat -an | grep 3060

-          If oid component is not running then start the oid component

[oracle@PRODSSO bin]$ ./startComponent.sh oid1

ps -ef | grep 'wls_ods1'- to check which server is used for dip

[oracle@PRODSSO bin]$ ps -ef | grep 'oidldapd'  - to check oid service is running or not.

$ netstat -an | grep 3060   -- to check ldap process is running or not

5.      Start otp service

Note: You have to start this service also manually, as it is related to isupplier otp.

[oracle@PRODSSO scripts]$. otp.env

[oracle@PRODSSO scripts]$./startotp.sh

-          To check otp service is running or not

[oracle@PRODSSO ~]$ ps -ef | grep otp

[oracle@PRODSSO ~]$ ps -ef | grep otp | grep -v grep | wc -l

8

If the command results in 0 (zero), it means that the otp service is not running.

 

·        Log files Locations:

LOG FILES OF OAM:

/u01/app/oracle/Middleware/Oracle_Home/user_projects/domains/oam_domain/servers/oam_server1/logs/

LOG FILES OF OID:

/u01/app/oracle/Middleware/Oracle_Home/user_projects/domains/oid_domain/servers/OID/logs/oid1/

LOG FILES OF WLS:

/u01/app/oracle/Middleware/Oracle_Home/user_projects/domains/oid_domain/servers/wls_ods1/logs/

LOG FILES OF Node Manager:

/u01/app/oracle/Middleware/Oracle_Home/user_projects/domains/otp_domain/nodemanager/

LOG FILES OF OTP:

/u01/app/oracle/Middleware/Oracle_Home/user_projects/domains/otp_domain/servers/ums_server1/logs/

 

URLs:

1.       WLS

http://172.168.112.28:7002/console/login/LoginForm.jsp

2.       http://172.168.112.28:7001/odsm/faces/odsm.jspx

 

Comments

Post a Comment

Popular posts from this blog

adop phase=prepare failed with error "data dictionary corrupted"

  After fresh clone when I run adop phase=prepare then prepare phase failed with the error "data dictionary corrupted". Solution: Follow the instructions in the "Fix data dictionary corruption" section of My Oracle Support Knowledge Document 1531121.1 . *  Fix Data Dictionary Corruption ( Conditional ) Copy the script $AD_TOP/patch/115/sql/adzddmpfix.sql to the database tier. On the database tier, connect to the database as SYSDBA. Run the $AD_TOP/patch/115/sql/adzddmpfix.sql script. [oraprod@deverpdb01 12.1.0]$ sqlplus / as sysdba SQL> @adzddmpfix.sql On the application tier, run the $AD_TOP/sql/ADZDDBCC.sql script again to identify whether data dictionary corruption is still present. [applprod@deverpapp01 sql]$ cd $AD_TOP/sql [applprod@deverpapp01 sql]$ sqlplus apps @ADZDDBCC.sql a.     If no corruption is found, proceed with the upgrade or patching cycle. b.   ...
Read more

Apply Latest CPU Patch of April 2024 on Oracle EBS R12.2.7 Application and Database 19c

Image
  Ref: Oracle E-Business Suite Release 12.2 Critical Patch Update Availability Document (April 2024) (Doc ID 3007752.1) As mentioned in the above document, before applying the Latest CPU patch we need to run ECPUC tool to identify any missing patches at Application node. To run ECPUC, download  Patch 35583866  and follow the instructions in the patch  Readme.txt  file. 3.2.1 EBS CPU Patches and Security Fixes  [applprod@upgapp03 oracle]$ . EBSapps.env run [applprod@upgapp03 scripts]$ cd $PATCH_TOP [applprod@upgapp03 patch]$ pwd /applprod/oracle/fs_ne/EBSapps/patch [applprod@upgapp03 patch]$ cd ECPUC/ [applprod@upgapp03 ECPUC]$ unzip p35583866_R12_GENERIC.zip [applprod@upgapp03 ECPUC]$ sqlplus apps/apps@UPG SQL> @ECPUC.sql SECTION-2 Oracle E-Business Suite (EBS): Instance Information ======================================================================== ***************************************************************************...
Read more

upgrade the AD/TXK Delta Patch to 14 in Oracle EBS R12.2.7

Image
  Environment: - Multi-node Applications (1 Internal Node & 1 External Node)    - Single Database Node - Version: Oracle EBS R12.2.7 and Database 19c ----------------------------------------------------------------------------------------------------------- We have to upgrade the AD/TXK level to 14. Follow the read me of AD patch 33600809 and perform all the steps as per read me and apply the patch using ADOP - Usually there will be only 2 patches to be applied to upgrade to AD/TXK. i.e. one patch for AD and another patch for TXK. But, in our environment we have Arabic Language enabled so I have to apply the AD/TXK patches for Arabic also. But, if no additional language is installed then you have to apply only English language patches which is the default. Below are the 4 patches which I have downloaded for English and Arabic If you have only English language in your setup then you have to download and install the below 2 patches only. 33600809:u33600809.drv  ...
Read more