Monitoring of Oracle sessions and processes

Background: oracle monitoring was previously configured on the production database and the database was connected every 5 minutes. If the connection fails, an automatic alarm is triggered through nagios + fetion. For details about this configuration, see ylw6006.blog. 51cto. com4

Background: oracle monitoring was previously configured on the production database and a database connection attempt was made every 5 minutes. If the connection fails, an automatic alarm is reported through nagios + fetion. This configuration reference article: http://ylw6006.blog.51cto.com/4

Background: oracle monitoring was previously configured on the production database and the database is connected once every 5 minutes. If the connection fails, an alarm is triggered automatically through nagios + fetion. For details about this configuration, refer:

After receiving the alarm in the morning, the Hong Kong virtual host will log on to the database and execute ps-ef to check that the background processes of oracle are all there. Use the conn/as sysdba method to log on to the database, prompting you to connect to the idle instance, if you use the easy connect method to connect to an oracle database, it is reported that the memory cannot be allocated to the oracle instance. From the error message, it is like the status of the oracle database instance that is not opened! The following error message is generated when alert logs are analyzed:
Process J002 died, see its trace file
Kkjcre1p: unable to spawn jobq slave process
Errors in file/u01/app/oracle/diag/rdbms/orcl/trace/orcl_cjq0_18577.trc:

The abstract information of the trace file is as follows:
* ** 2012-07-26 10:20:31. 068
Process J002 is dead (pid = 13857 req_ver = 1136 cur_ver = 1136 state = KSOSP_SPAWNED ).

* ** 2012-07-26 10:20:32. 069
Process J002 is dead (pid = 13876 req_ver = 1594 cur_ver = 1594 state = KSOSP_SPAWNED ).

After a google query, it was found that most of the descriptions were related to the number of oracle processes, or caused by insufficient memory! Therefore, the oracle 10 Gb environment is tested, and the online database environment is 11.2.0.3.

I. Set the initialization parameter value of processes to 20 for the Hong Kong server. After the database is restarted, 19 processes are occupied.

When a new session is connected, an error is reported in the alert Log.

Refer :? Uid = 854 & do = blog & id = 84

2. I thought of monitoring oracle processes and sessions to further determine the problem.
1: First, you must grant the display authorization to the user. Otherwise, an error will be reported when compiling the stored procedure.

2: Create a table to store results

Table created.

3: Create a stored procedure and insert data into the table

4: create a task

5: Test Results

6: If you want to delete a task, run the following command, 145 represents the job column in The user_jobs view.

3. Use nagios + fetion to regularly monitor sessions and processes
1: create a monitoring script, which is run in the task plan and automatically executed every 2 minutes.

EOF

2: Create a second script to process the log output of the preceding monitoring script and return the result to the monitoring server.

Iv. Actual results
[Root @ server198 ~] #/Usr/local/nagios/libexec/check_nrpe-H 192.168.1.240-c check_oracle_session
Current session is 138, process is 153

V. Later observation results, estimation related to memory problems
[Oracle @ server240 ~] $ Sar-r | grep 10: 20
10:20:02 AM 3481492 21195164 85.89 675584 13661448 3683012 413552 10.10
[Oracle @ server240 ~] $ Sar-r | grep
04:40:01 2076748 22599908 91.58 734088 14581728 4048864 47700 1.16

This article is from the "Bo Yue" blog and will not be reproduced!