Pin_ctl Shows Wrong Status of Batch_controller (Doc ID 2312728.1)

Last updated on OCTOBER 24, 2017

Applies to:

Symptoms

On Oracle Communications Billing and Revenue Management(BRM), 7.5.0.16.0 version, it is observed that the 'pin_ctl' utility is showing wrong status of batch_controller.

As a result, OEM would always show wrong status of batch_controller.

When pin_ctl status batch_controller got called, pin_ctl code got executed in below fashion:

1. status_of_service routine is called which calls get_procid
2. get_procid gets called
3. $stat_pid = get_pid($service_name) is called which tries to get the process id of service. In this case batch_controller
4. $subsystem_info{$service_name}{'pidfile'} is called to get the value of pid_file_name from the hash
5. If you try to print the hash this is how batch_controller hash will look like  

It meant the value of pid_file_name was $PIN_HOME/var/batch_controller/batch_controller.pid which would be used to get the process id of batch_controller.

ACTUAL BEHAVIOR  
---------------------------
The portal would not create any batch_controller.pid file in $PIN_HOME/var/batch_controller/
As there was no $PIN_HOME/var/batch_controller/batch_controller.pid, pin_ctl status batch_controller would always show batch_controller as down even if batch_controller was up and running.

EXPECTED BEHAVIOR
------------------------------
Ideally, the value should be looked up inside $PIN_HOME/apps/batch_controller/BatchController.pid;
OR, copy the BatchController.pid into $PIN_HOME/var/batch_controller/batch_controller.pid

STEPS
-----------------------
>>pin_ctl status batch_controller
pin_ctl: service <batch_controller> is NOT running

Cause