ORA-00600 [kmgs_parameter_update_timeout_1], [27072] ORA-27072 Solution

 

I. Problem Description

 

The information in the database Alert Log is as follows:

Mon Jul 30 22:01:00 2012

Errors in file/g01/APP/Oracle/diag/rdbms/gumd/Trace/gumd_mmon_21407.trc (incident = 76981 ):

ORA-00600: Internal error code, parameter: [kmgs_parameter_update_timeout_1], [27072], [], [], [], [], [], [], [] [], []

ORA-27072: file I/O errors

Linux-x86_64 error: 9: Bad file descriptor

Additional information: 4

Additional information: 4

Additional information:-1

Incident Details in:/g01/APP/Oracle/diag/rdbms/gumd/Incident/incdir_76981/gumd_mmon_21407_i76981.trc

Mon Jul 30 22:01:02 2012

Trace dumping is required mingid = [cdmp_20120730220102]

Mon Jul 30 22:01:04 2012

Errors in file/g01/APP/Oracle/diag/rdbms/gumd/Trace/gumd_dbw0_3375.trc (incident = 76937 ):

ORA-00600: Internal error code, parameter: [kmgs_parameter_update_timeout_1], [27072], [], [], [], [], [], [], [] [], []

ORA-27072: file I/O errors

Linux-x86_64 error: 9: Bad file descriptor

Additional information: 4

Additional information: 4

Additional information:-1

Incident Details in:/g01/APP/Oracle/diag/rdbms/gumd/Incident/incdir_76937/gumd_dbw0_3375_i76937.trc

Errors in file/g01/APP/Oracle/diag/rdbms/gumd/Trace/gumd_dbw0_3375.trc:

ORA-00600: Internal error code, parameter: [kmgs_parameter_update_timeout_1], [27072], [], [], [], [], [], [], [] [], []

ORA-27072: file I/O errors

Linux-x86_64 error: 9: Bad file descriptor

Additional information: 4

Additional information: 4

Additional information:-1

Dbw0 (ospid: 3375): Terminating theinstance due to error 471

Instance terminated by dbw0, pid = 3375

 

 

Ii. Solution

 

2.1 error cause:

Starting with10g, The mmon background process manages all memory resize activity by modifyingthe related parameters. The parameter update activity is triggered by atimeout.

 

If the updatecannot be passed med, several error conditions are checked to see if that couldbe the cause.

 

If we cannotmatch the current condition to the list of known conditions, we raise theassert kmgs_parameter_update_timeout_1

In such a case, we need to look at the first argument returned with the ORA-600.
This will give you the error number of the triggering condition.

 

In the presentcase, the key error is the ORA-27091 "unable to queue I/O"
In other words, we raise such an error when a "read/write/readv/writevsystem call returned error ".

 

Finally, here, we found out that the problem was actually due to the spfile having root asowner

 

The cause of the ORA-00600: [kmgs_parameter_update_timeout_1] may be as follows:

(1) Insufficient disk space for ORACLE_HOME

(2) If the file system containing spfile is damaged, Oracle cannot access spfile.

(3) The user and group where the spfile file is located, or the permission is incorrect.

 

2.2 solution:

(1) If the permission problem occurs, modify the spfile file to the Oracle user, and the DBA group will be OK.

 

(2) Most ORA-600 [kmgs_parameter_update_timeout_1] errors can be solved by trying to recreate the spfile.

 

The procedure is as follows:

-- Create a pfile based on the current spfile:

SQL> createpfile = '<replace_by_full_path> \ init. ora' from spfile;

 

-- Check the new pfile.

 

-- Close the database and start it with the new pfile:

SQL> shutdown immediate
SQL> startup pfile = ''<replace_by_full_path_of_newly_created_pfile> ';

 

-- Create a new spfile:

SQL> Create spfile from pfile;

 

-- Close the database and start it with a new spfile:

SQL> shutdown immediate
SQL> startup

 

 

 

Refer:

ORA-00600 [kmgs_parameter_update_timeout_1], [27072] Error crashes the database [id1149073.1]

ORA-600 [kmgs_parameter_update_timeout_1], [27072] when trying to start instance [ID 1457938.1]

ORA-600 [kmgs_parameter_update_timeout_1], [27091], [] [ID 1286640.1]

 

 

 

 

Bytes -------------------------------------------------------------------------------------------------------

All rights reserved. reprinted articles are allowed, but source addresses must be indicated by links. Otherwise, the documents will be held legally responsible!

Skype: tianlesoftware

QQ: tianlesoftware@gmail.com

Email: tianlesoftware@gmail.com

Blog: http://www.tianlesoftware.com

WEAVER: http://weibo.com/tianlesoftware

Twitter: http://twitter.com/tianlesoftware

Facebook: http://www.facebook.com/tianlesoftware

LinkedIn: http://cn.linkedin.com/in/tianlesoftware

 

 

------- Add a group to describe the relationship between Oracle tablespace and data files in the remarks section. Otherwise, reject the application ----

Dba1 group: 62697716 (full); dba2 group: 62697977 (full) dba3 group: 62697850 (full)

Super DBA group: 63306533 (full); dba4 group: 83829929 dba5 group: 142216823

Dba6 group: 158654907 dba7 group: 172855474 DBA group: 104207940