Applies to:
Oracle Server - Enterprise Edition - Version: 10.2.0.1 and later   [Release: 10.2 and later ]
Information in this document applies to any platform.


Symptoms
The following errors are seen in the ALERT:
ORA-600: internal error code, arguments: [kmgs_parameter_update_timeout_1], [1565], [], [], [], [], [], []
ORA-01565: error in identifying file '/oradata/ZPVP/dbs/spfileZPVP.ora'
ORA-27041: unable to open file
IBM AIX RISC System/6000 Error: 22: Invalid argument
Additional information: 2

followed by an instance crash.


Cause
If the SPFILE is read by some other OS commands/programs that are putting a shared lock on it, 
while MMON tries to write dynamically modified parameters, the instance might crash with above above errors.

This happens because MMON needs to put an exclusive lock on the spfile in order to write it and cannot do this. 
If the update cannot be performed several error conditions are checked to see if that could be the cause.  
If we can't match the current condition to the list of known exceptions we raise the assert 
kmgs_parameter_update_timeout_1.  This causes MMON to crash, and if MMON is not alive DBW0 
also runs these actions and its failure leads to the instance crash.

Solution
This is fixed via unpublished bug:9715539 fixed in 11.2.0.2, which removes the assertion of the 
ORA-600 [kmgs_parameter_update_timeout_1] error in the case of an external error occurring, 
and so MMON just raises the external error.  For availability of one-off patches see Patch:9715539.
Alternatively you can workaround the problem by ensuring that no application/OS commands put shared 
locks on the SPFILE (more, touch etc):
1.	Check the operating system for any application/program accessing the SPFILE 
        while MMON/DBWR attempt to update the parameter file.
2.	If you see the same errors in ALERT, check from OS level what processes are holding/accessing SPFILE.
3.	Check file protections of SPFILE which might prevent MMON/DBWR from updating the SPFILE.

The SPFILE is a binary file and should not normally require to be read or touched.  
If access to that information is required, then you should create a parameter file (PFILE) to 
be able access the information rather than use the SPFILE.  That can be done using the command:
CONNECT / AS SYSDBA
CREATE PFILE='/<path>/<SID>_init.ora' FROM SPFILE='/<path>/spfile<SID>.ora';

References
NOTE:9715539.8 - Bug 9715539 - ORA-600 [kmgs_parameter_update_timeout_1] from MMON if some other error occurs

ORA-00600: internal error code, arguments: [kmgs_parameter_update_timeout_1], [1565], [], [], [], [], [], []
ORA-01565: error in identifying file '/dev/rvgoradata3_1_01'
ORA-00600: internal error code, arguments: [kmgs_parameter_update_timeout_1], [600], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [ksprcvsp1], [0], [0], [], [], [], [], []