ORA-01075错误问题解决

来源:互联网 发布:网络西红柿哥真实名字 编辑:程序博客网 时间:2024/05/12 09:27

1.今天收到报警数据库出现错误;

2.登录数据库后台查看,用sqlplus 登录时报如下错误:

ERROR:
ORA-01075: 

3.查看alert日志,发现如下报错信息:

Errors in file /home/oracle/admin/coolpad/bdump/coolpad_j000_8695.trc::
ORA-00604:  SQL  1 
      018: 55;26H
Thu Sep 18 15:56:25 CST 2014
Errors in file /home/oracle/admin/coolpad/bdump/coolpad_q002_8924.trc:
ORA-00018: 58;26H
Thu Sep 18 16:00:48 CST 2014
Errors in file /home/oracle/admin/coolpad/bdump/coolpad_m000_9051.trc:
ORA-00018: 61;26H
Thu Sep 18 16:01:48 CST 2014
Errors in file /home/oracle/admin/coolpad/bdump/coolpad_m000_9062.trc:


Thu Sep 18 16:02:4
                                                        ora_9091.trc:
ORA-00018: 67;1H
Thu Sep 18 16:02:49 CST 2014
Process m001 died, see its trace file
Thu Sep 18 16:02:49 CST 2014
ksvcreate: Process(m001) creation failed
Thu Sep 18 16:03:49 CST 2014
Errors in file /home/oracle/admin/coolpad/bdump/coolpad_m000_9132.trc:
ORA-00018: 67;139H
Thu Sep 18 16:04:49 CST 2014
Errors in file /home/oracle/admin/coolpad/bdump/coolpad_m000_9162.trc:
ORA-00018: 67;139H
Thu Sep 18 16:05:49 CST 2014
Errors in file /home/oracle/admin/coolpad/bdump/coolpad_m000_9174.trc:
ORA-00018: 67;139H
Thu Sep 18 16:06:49 CST 2014
Errors in file /home/oracle/admin/coolpad/bdump/coolpad_m000_9221.trc:
ORA-00018: 67;139H
Thu Sep 18 16:07:49 CST 2014
Errors in file /home/oracle/admin/coolpad/bdump/coolpad_m000_9229.trc:
ORA-00018: 67;139H
Thu Sep 18 16:08:49 CST 2014
Errors in file /home/oracle/admin/coolpad/bdump/coolpad_m000_9243.trc:
ORA-00018: 67;139H
Thu Sep 18 16:09:49 CST 2014
Errors in file /home/oracle/admin/coolpad/bdump/coolpad_ora_9296.trc:
ORA-00018: 67;139H
Thu Sep 18 16:09:50 CST 2014
Process m000 died, see its trace file
Thu Sep 18 16:09:50 CST 2014
ksvcreate: Process(m000) creation failed

Thu Sep 18 16:09:55 CST 2014



4.打开后台查看trc文件,发现如下错误信息,原来是session数据太大导致系统出错,并到最终岽m000进程挂死

ORA-00018: OPIRIP: Uncaught error 447. Error stack:
ORA-00447: fatal error in background process
ORA-00018: maximum number of sessions exceeded

5.解决方法,找出oracle相关进程,直接kill

ps -ef |grep $ORACLE_SID|grep -v grep|awk '{print $2}' | xargs kill -9
ipcs -m | grep oracle | awk '{print $2}' | xargs ipcrm shm


6.重新启动数据库,alert日志中恢复信息如下所示,意思是并未有数据丢失,并不需要进行数据恢复。

Thu Sep 18 16:17:11 CST 2014
db_recovery_file_dest_size of 20480 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.

0 0