ORA-27300, ORA-27301, ORA-27302

O & M Engineers deployed a set of Oracle (Database not built) on an IBM P750 (AIX6.1), allowing me to perform a disaster tolerance for a commercial database with its DG. I deployed the DG following the normal steps.

1. Start log recovery in the slave Database

Alter database recover managed standby database using current logfile disconnect;

2. Check whether the standby database receives logs normally.

Select process, client_process, sequence #, status from v $ managed_standby;

-- Logs are received normally.

3. Check whether the standby database is running properly.

Select THREAD #, SEQUENCE #, ARCHIVED, APPLIED, DELETED, STATUS from v $ archived_log order by 1, 2;

-- Normal Application Log

However, I found the following error in the alert log of the slave database:

Mon Mar 24 14:11:14 2014

Process startup failed, error stack:

Errors in file/apps/oracle/diag/rdbms/primary/egap/trace/egap_psp0_18481392.trc:

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

ORA-27301: OS failure message: No such file or directory

ORA-27302: failure occurred at: skgpspawn5

Process PR0S died, see its trace file

It was found that the parameter maxuproc is insufficient. By default, this parameter is only 128. This parameter determines the maximum number of processes that each operating system user can connect to. If this parameter is insufficient, the alert Log reports the above error.

Normally, when installing rac, we will check these parameters in advance and set them to the value required by oracle (the required value is 16384). This may be because O & M does not check this parameter at all.

Check this parameter

Lsattr-E-l sys0-a maxuproc

Root @ egisbdb1:/# lsattr-E-l sys0-a maxuproc

Maxuproc 128 Maximum number of PROCESSES allowed per user True

Modify this parameter

Chdev-l sys0-a maxuproc = 16384

This error is not reported in the alert Log after modification.