Bash script for listing running WebLogic Servers and Node Managers

-
If you have many domains running on the same Linux server it can be difficult to see what is running and what is not. I have created a Bash script that lists all WebLogic Server and Node Manager processes.
I have tested it on Red Hat 5 and 6.
Here is an example output.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
##############################################################################
# WebLogic Servers
# <owner>  <domain>  <server>  <pid>  <ports>
##############################################################################
prism01ora  prism01osb  AdminServer        23738  7011
prism01ora  prism01osb  prism01osbServer1  24018  7890,8011
prism01ora  prism01por  AdminServer        2943   7021
prism01ora  prism01por  prism01porServer1  28665  8021
prism01ora  prism01wls  AdminServer        22510  7001
prism01ora  prism01wls  prism01wlsServer1  22362  8001
prism02ora  prism02osb  AdminServer        14114  null
prism02ora  prism02osb  prism02osbServer1  14029  null
prism02ora  prism02wls  AdminServer        13396  null
prism02ora  prism02wls  prism02wlsServer1  16414  null
 
##############################################################################
# Node Managers
# <owner>  <mw_home>  <pid>  <port>
##############################################################################
prism01ora  /prism01/app/oracle/product/osb111  2473   5557
prism01ora  /prism01/app/oracle/product/por103  2552   5558
prism01ora  /prism01/app/oracle/product/wls103  2519   5556
prism02ora  /prism02/app/oracle/product/osb111  10430  null
prism02ora  /prism02/app/oracle/product/wls103  12603  null
The reason some ports are listed as null is because the script was run by the prism01ora Linux user, and some of the processes is owned by prism02ora. I use netstat to get the used ports, and it does not allow ordinary users to get information about processes of other users.

Referance: http://theheat.dk/blog/?p=1443



Comments

Post a Comment

Popular posts from this blog

RMAN backup Status (Remaining Time and Percentage)

-
On Running a huge database backup we often need to know the status of backup. 1) How much backup is taken. 2) How much is remain. 3) Estimate time to complete the backup. After lot of search i find out this amazing query below. col dbsize_mbytes for 99,999,990.00 justify right head "DBSIZE_MB" col input_mbytes for 99,999,990.00 justify right head "READ_MB" col output_mbytes for 99,999,990.00 justify right head "WRITTEN_MB" col output_device_type for a10 justify left head "DEVICE" col complete for 990.00 justify right head "COMPLETE %" col compression for 990.00 justify right head "COMPRESS|% ORIG" col est_complete for a20 head "ESTIMATED COMPLETION" col recid for 9999999 head "ID" select recid , output_device_type , dbsize_mbytes , input_bytes/1024/1024 input_mbytes , output_bytes/1024/1
Read more

EBS R12.2 Autoconfig Failed. Resolved

-
Hi, Please do the following and retest the issue: Due to the method required for "cleaning out" / "re-synchronizing" the following tables, it is EXPECTED / REQUIRED that the Applications have been shutdown. The only thing running should be the Database Tier. Note: A full backup should also be taken before any testing begins. Test the following steps in a development instance, and then migrate accordingly once the desired result is confirmed: 1. Backup the fnd_oam_context_files, fnd_nodes, and adop_valid_nodes tables in the EBS env: sqlplus applsys/pwd create table fnd_oam_context_files_bkp as select * from fnd_oam_context_files; create table fnd_nodes_bk as select * from fnd_nodes; create table adop_valid_nodes_bk as select * from adop_valid_nodes; 2. Truncate the following tables: truncate table fnd_oam_context_files; truncate table fnd_nodes; truncate table adop_valid_nodes; 3. Run AutoConfig on the DB tier
Read more

ADOP options availble in R12.2

-
 Need to find all the availble options in ADOP, here is the command. adop -examples [oracle@preprod appsTier]$ adop -examples Applications DBA Online Patching Tool (adop) See Oracle E-Business Suite Maintenance Guide for a full description of adop features, operation, and usage. Standard Online Patching Cycle:     In Oracle E-Business Suite Release 12.2, patches are normally applied     using an online patching cycle.  The online patching cycle consists of     five phases which are executed in order.     Example - Typical online patching cycle:         source <ebs_root>/EBSapps.env run         adop phase=prepare         adop phase=apply patches=123456         adop phase=finalize         adop phase=cutover         source <ebs_root>/EBSapps.env run         adop phase=cleanup     Note that after cutover the command line environment should be re-loaded     as the run edition file system has changed.     In a multi-node deployment, adop commands are only executed from the   
Read more