Troubleshooting the response-time probe configuration


This topic contains the following troubleshooting information:

Check probe input parameters

  • A missing Probe ID creates the following message: Please enter Probe ID.
  • If the probe setup finds duplicate Probe IDs, PATROL shows the following message: Probe ID has already existed. Please choose another Probe ID.
  • A missing Local Patrol Agent Account Name creates the following message: Please enter Local Patrol Agent Account Name.
  • A missing Local Patrol Agent Account Password creates the following message: Please enter Local Patrol Agent Account Password.
  • A missing Remote Probe Agent Host Name creates the following message: Please enter Remote Probe Agent Host Name.
    A missing Remote Probe Agent Port Number creates the following message: Please enter Remote Probe Agent Port Number.
  • A missing Remote Probe Agent Account Name creates the following message: Please enter Remote Probe Agent Account Name.
  • A missing Remote Probe Agent Account Password creates the following message: Please enter Remote Probe Agent Account Password.
  • A missing Oracle Connect String creates the following message: Please enter Oracle Connect String. This error message will only occur if you are running a two-tier Oracle Applications environment.

A missing Remote $ORACLE_HOME for UNIX probe agent creates the following message: Please enter remote $ORACLE_HOME.

  • A missing Oracle Web Server Host Name with Domain Name creates the following message: Please enter Oracle Web Serve Host Name with Domain Name. This error message will only occur if you are running a three-tier Oracle Applications environment.
  • A missing Oracle Web Server Listener Port Number creates the following message: Please enter Oracle Web Server Listener Port Number. This error message will only occur if you are running a three-tier Oracle Applications environment.

Check local patrol agent information

Any wrong local Patrol Agent account name and password causes the following error message: Local Patrol user id or password are not correct.

Check remote probe patrol agent information

The following can cause the Either remote probe agent is not start or user ID or password are not correct error message from the probe setup error message to appear:

  • One of four remote input parameters (Remote Probe Agent Host Name, Remote Probe Agent Port Number, Remote Probe Agent Account Name, Remote Probe Agent Account Password) is wrong. When this occurs, the probe setup cannot connect and receive information from the remote Patrol probe agent.
  • If all four remote input parameters are correct, but the remote Patrol probe agent does not start, the probe setup cannot connect and receive information from the remote Patrol probe agent.

Check remote probe Patrol Agent Knowledge Module

If you receive the following error message from the probe setup, load the OA_PROBE_LST.kml file using the remote probe Patrol console: OA probe km is not loaded in remote probe agent. 

Check remote ORACLE HOME Directory (UNIX probe Patrol Agent only)

If you receive the following error message from the probe setup, the remote $ORACLE_HOME directory is not correctly specified: Incorrect remote Oracle Home directory ($ORACLE_HOME).  This error will only occur if you are running a UNIX remote probe agent under a two-tier Oracle Applications environment.

Check Oracle Connection from Remote Probe Patrol Agent (two tier via SQLPLUS)

  • If you receive the following error message, it means that the remote probe Patrol agent cannot find sqlplus, which is required for a two-tier based probe:  Can not find sqlplus. You must install sqlplus software and perform the probe setup again.
  • If you receive a message, which includes Oracle error messages, check the Oracle error messages (ORA-). These errors are usually caused by an incorrect input parameter for the Oracle Connect String.

Check Oracle connection from remote probe Patrol Agent (three tier via Oracle web server)

  • If you receive the following error message, make sure the Oracle Web Server Host Name with Domain Name and the Oracle Web Server Listener Port Number parameters are correct: Web server is down or web port is not correct. If both input parameters are correct, log on to the web server and check the web server status. In addition, check the web server through the web browser with the following URL: http://Oracle Web Server Host Name with Domain Name/ Oracle Web Server Listener Port Number.
  • If you receive the following error message, make sure that oa_thin.class is located on the Oracle web server under the http://Oracle Web Server Host Name with Domain Name/Oracle Web Server Listener Port Number/java virtual path URL: Can not run oa_thin.class.
  • If you receive the following error message, make sure the jdk 1.02 class is located on the Oracle web server: Class error: ... 
  • If you receive this error message, check the Oracle error messages: SQL error: ...
  • If you do not receive an error message but cannot complete the probe setup, the operation might have timed out. The Oracle web server might have timed out due to heavy network traffic, or the Oracle connection from the web server to the Oracle Applications server might have timed out because of a slow database connection.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC PATROL for Oracle e-Business Suite 3.4