CDRPull-Monitor Application has NOT responded

Issue:

NexOSS cannot collect CDRs from OSPrey because it is having issues connecting to the database. The “Application has NOT responded” error shows up in the NexOSS CDR log file ($NexOSS_HOME/LOG/NexOSS-CDR-Collection.log).

Log message:

2008-09-03 08:46:16|CDRPull|INFO|License Accepted
2008-09-03 08:46:16|CDRPull|INFO|Loading JDBC Driver oracle.jdbc.driver.OracleDriver
2008-09-03 08:46:16|CDRPull|INFO|Connecting to the Database
2008-09-03 08:56:16|CDRPull-Monitor|ERROR |Application has NOT responded in more than 600 seconds
2008-09-03 08:57:16|CDRPull-Monitor|ERROR |Application has NOT responded in more than 600 seconds
2008-09-03 08:58:16|CDRPull-Monitor|ERROR |Application has NOT responded in more than 600 seconds
2008-09-03 08:59:16|CDRPull-Monitor|ERROR |Application has NOT responded in more than 600 second

Troubleshoot:

The error message indicates that NexOSS is having trouble connecting to the database.

Solution:

The CDR-Collection application must first connect to the database before it can collect any CDR files from OSPrey. Restart Oracle.

  • If there is an Oracle auto-start script in place, become user root and manually execute.
   # /etc/init.d/dbora stop
   # /etc/init.d/dbora start

You can check whether the auto-start script is in place by looking at the /etc/rc3.d to see if there is a link to an Oracle auto-start script in the /etc/init.d. The typical file name is dbore, but it doesn’t need to be. Become user root by issuing the su (super-user) command and also the root password.

   $ su
   Password:
   #
  • Alternatively, you can restart Oracle as the user that owns Oracle from the $ORACLE_HOME/bin directory.

    • Oracle-10 stop:
      $ cd $ORACLE_HOME/bin
      $ ./isqlplusctl stop
      $ ./emctl stop dbconsole
      $ ./lsnrctl stop
      $ ./dbshut
    
    • Oracle-10 start:
      $ ./dbstart
      $ ./emctl start dbconsole
      $ ./isqlplusctl start
    
    • Oracle-11 stop:
      $ cd $ORACLE_HOME/bin
      $ ./emctl stop dbconsole
      $ ./lsnrctl stop
      $ ./dbshut
    
    • Oracle-11 start:
      $ ./dbstart
      $ ./emctl start dbconsole
    
    • To determine what user owns Oracle, you may grep for Oracle, or just ora. The owner of the Oracle processes will be displayed to the far left.
      $ ps -ef|grep ora
      oracle 16667 1 0 Jan 22 ? 4:29 oraclelabdb (LOCAL=NO)
      oracle 17885 1 0 Jan 15 ? 10:08 ora_lgwr_labdb
      oracle 17879 1 0 Jan 15 ? 10:13 ora_dia0_labdb
      ~
      oracle 1345 1 0 18:46:54 ? 0:00 ora_w000_labdb
      oracle 11772 1 0 08:47:57 ? 0:01 oraclelabdb (LOCAL=NO)
      $
     
      [ossadmin@kermit ~]$ ps -ef|grep ora
      ossadmin 3786 1 0 Jan28 ? 00:00:02 ora_q002_dbappia
      ossadmin 4558 1 14 2012 ? 14-16:47:54 oracledbappia (LOCAL=NO)
      ossadmin 5160 1 0 2012 ? 00:15:48 /home/ossadmin/ORA/oracle/product/11.2.0/dbhome_1/bin/tnslsnr LISTENER -inherit
      ossadmin 5354 1 0 2012 ? 00:03:07 ora_pmon_dbappia
      ossadmin 5356 1 0 2012 ? 00:03:45 ora_vktm_dbappia
      ossadmin 5360 1 0 2012 ? 00:00:49 ora_gen0_dbappia
      ~
      ossadmin 20327 1 0 00:20 ? 00:00:11 oracledbappia (LOCAL=NO)
      ossadmin 20329 1 0 00:20 ? 00:00:06 oracledbappia (LOCAL=NO)
      ossadmin 20331 1 0 00:20 ? 00:00:00 oracledbappia (LOCAL=NO)
      [ossadmin@kermit ~]$