Shulou(Shulou.com)06/01 Report--

Problem phenomenon:

Sun Sep 30 21:12:28 2018Errors in file / DBSoft2/oracle/diag/rdbms/fzdbcgbk/fzdbcgbk1/trace/fzdbcgbk1_psp0_221463.trc:ORA-27300: fork customers: Resource temporarily unavailableORA-27302: skgpspawn3Process J000 died, see its trace fileSun Sep 30 21:12:28 2018kkjcre1p: unable to spawn jobq slave process Sun Sep 30 21:12:28 2018Errors in file / DBSoft2/oracle/diag/rdbms/fzdbcgbk/fzdbcgbk1/trace/fzdbcgbk1_cjq0_222890.trc:Sun Sep 30 21:12:29 2018Process startup failed Error stack:Sun Sep 30 21:12:29 2018Errors in file / DBSoft2/oracle/diag/rdbms/fzdbcgbk/fzdbcgbk1/trace/fzdbcgbk1_psp0_221463.trc:ORA-27300: 11ORA-27301: Resource temporarily unavailableORA-27302: skgpspawn3

Reference:

Mos ID:392006.1

SYMPTOMS:

The following message reported in alert log:

Mon Sep 18 18:10:34 2006

Errors in file / u01/oracle/admin/orcl/bdump/orcl1_psp0_954436.trc:

ORA-27300: OS system dependent operation:fork failed with status: 11

ORA-27301: OS failure message: Resource temporarily unavailable

ORA-27302: failure occurred at: skgpspawn3

Mon Sep 18 18:10:35 2006

Process P073 died, see its trace file

CAUSE:

The error messages indicating that oracle has problem in forking more process, the maximum number of PROCESSES allowed per user could be too low.

This is configured by the following kernel settings:

AIX: maxuproc

HP and Solaris: maxuprc

Solaris 10/11: project.max-lwps

Linux: nproc (/ etc/security/limits.conf)

Check the configuration:

[root@fzdb1 trace] # su-oracle2 [oracle2@fzdb1 ~] $ulimit-acore file size (blocks,-c) 0data seg size (kbytes,-d) unlimitedscheduling priority (- e) 0file size (blocks,-f) unlimitedpending signals (- I) 1031748max locked memory (kbytes,-l) 64max memory size (kbytes -m) unlimitedopen files (- n) 1024pipe size (512 bytes,-p) 8POSIX message queues (bytes,-Q) 819200real-time priority (- r) 0stack size (kbytes,-s) 10240cpu time (seconds,-t) unlimitedmax user processes (- u) 3047virtual memory (kbytes -v) unlimitedfile locks (- x) unlimited [oracle2@fzdb1 ~] $ulimit-u 3047 [root@fzdb1 ~] # grep proc / etc/security/limits.conf#-nproc-max number of processes#-priority-the priority to run user process with#@student hard nproc 20#@faculty soft nproc 20#@faculty hard nproc 50#ftp hard nproc 0oracle soft nproc 3047oracle hard nproc 16384grid soft nproc 3047grid hard nproc 16384

Problem analysis:

From the above inspection, we can find that the number of oracle2 user processes has reached 1491, which is almost close to the user processes number of oracle2 users, so a large number of ORA-27300,ORA-27301,ORA-27302 frequently appear in the database log. According to MOS:392006.1 recommendations, we modify the oracle2 nProc value in the / etc/security/limits.conf file to a larger value, but in fact, we do not find any configuration for oracle2 users. So we can manually add the following configuration and restart the database server:

Oracle2 soft nproc 16384

Oracle2 hard nproc 16384

Oracle2 soft nofile 65536

Oracle2 hard nofile 65536

Oracle2 soft memlock 3145728

Oracle2 hard memlock 3145728

Start modifying:

[root@fzdb1] # cat > > / etc/security/limits.conf oracle2 soft nproc 16384 > oracle2 hard nproc 16384 > oracle2 soft nofile 65536 > oracle2 hard nofile 65536 > oracle2 soft memlock 3145728 > oracle2 hard memlock 3145728 > EOF

Restart the server:

[oracle2@fzdb1 ~] $su-root [root@fzdb1 ~] $reboot

Check the parameter changes you just made:

[oracle2@fzdb1] $ulimit-u16384

Check the database log:

After modifying the parameters, there is no error message such as ORA-27300,ORA-27301,ORA-27302 after one day of observation, and the fault has been dealt with.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.