ORA-27300,ORA-27301,ORA-27302
来源:互联网 发布:淘宝市场调查问卷 编辑:程序博客网 时间:2024/05/21 17:03
运维工程师在一台IBM P750(AIX6.1)上部署了一套oracle(未建库),让我把商用的某库同其做一个DG容灾。我按正常步骤部署了DG。
1.在备库开始日志恢复
alter database recover managed standby database using current logfile disconnect;
2.查看备库是否正常接收日志
select process,client_process,sequence#,status from v$managed_standby;
--正常接收日志
3.查看备库是否正常应用日志
select THREAD#,SEQUENCE#,ARCHIVED,APPLIED,DELETED,STATUS from v$archived_log order by 1,2;
--正常应用日志
但是我在备库的alert日志里发现有如下报错
报错1
Process startup failed, error stack:Errors in file /apps/oracle/diag/rdbms/egbi/egbi2/trace/egbi2_psp0_29949962.trc:ORA-27300: OS system dependent operation:fork failed with status: 2ORA-27301: OS failure message: No such file or directoryORA-27302: failure occurred at: skgpspawn5
报错2
Process startup failed, error stack:Errors in file /apps/oracle/diag/rdbms/egbi/egbi2/trace/egbi2_psp0_29949962.trc:ORA-27300: OS system dependent operation:fork failed with status: 11ORA-27301: OS failure message: Resource temporarily unavailableORA-27302: failure occurred at: skgpspawn3
查看mos后发现是操作系统参数maxuproc设置不正确导致(具体见Doc ID 1125188.1和Doc ID 392006.1),该参数默认只有128,该参数决定了每个操作系统用户允许连接的最大进程数,该参数不足时alert日志中会报如上错误。
正常在装rac时这些参数我们都会提前检查,并设为oracle要求的值(要求值为16384),这里可能是运维根本没有检查该参数
检查该参数
lsattr -E -l sys0 -a maxuproc
root@egisbdb1:/#lsattr -E -l sys0 -a maxuproc
maxuproc 128 Maximum number of PROCESSES allowed per user True
修改该参数(增大maxuproc参数无需重启操作系统可以直接生效,如果是减小该值则需重启操作系统后生效)
chdev -l sys0 -a maxuproc=16384
修改后alert日志中不再报该错误
本文出自 “技术” 博客,请务必保留此出处http://589985.blog.51cto.com/1609992/1382435
- ORA-27300 ORA-27301 ORA-27302
- ORA-27300,ORA-27301,ORA-27302
- Troubleshooting ORA-27154 ORA-27300 ORA-27301 ORA-27302
- ORA-27300 ORA-27301 ORA-27302: failure occurred at: skgpalive1
- ORA-27300, ORA-27301, ORA-27302错误处理
- 记一次ORA-27300、ORA-27301、ORA-27302错误解决
- ORA-27300,ORA-27301,ORA-27302,ORA-04030导致crashed database
- 在启动DB时报错ORA-27154 ORA-27300 ORA-27301 ORA-27302
- oracle启动的时候报 ORA-27154、ORA-27300、ORA-27301、ORA-27302
- oracle启动的时候报 ORA-27154、ORA-27300、ORA-27301、ORA-27302
- 数据库启动报ORA-27154 ORA-27300 ORA-27301 ORA-27302错误
- ORA-27300,ORA-27301,ORA-27302,ORA-27303导致实例宕的问题分析
- dbca建库时遭遇ORA-27154 ORA-27300 ORA-27301 ORA-27302解决方法
- ORA
- ora
- 从ORA-27300,ORA-27301到ORA-00064
- ASM 启动报错 ORA-27300, ORA-27301 and ORA-27302: failure occurred at: sskgpsemsper 解决方法
- ASM 启动报错 ORA-27300, ORA-27301 and ORA-27302: failure occurred at: sskgpsemsper 解决方法
- oracle comment
- AIX账户密码不能重用和过期的解决
- 11.2.0.3.0 打PSU补丁--自动方式(p14727347_112030_AIX64-5L.zip )
- Why is "opatch auto" not patching my RAC database home?
- Error 12154 received logging on to the standby
- ORA-27300,ORA-27301,ORA-27302
- ORA-20079: full resync from primary database is not done
- LOG_ARCHIVE_CONFIG
- oracle 中带双下划线的参数如(*.__shared_pool_size=)
- oracle查看隐含参数脚本
- ASMM下查看shared_pool_size等内存大小
- ORA-01264: Unable to create logfile file name
- Solr查询语法总结
- PRCS-1007 : Server pool egapdb already exists