ORA-00600 ORA-01565, ORA-27046

ORA-00600 ORA-01565, ORA-27046
Yesterday in the Data Pump import and export, suddenly encountered a ude-00008 error, view the log file:

<span style="font-size:10px;">Errors in file /oracle/afcprd01/db/10.2.0/admin/afcprd01_afcdb/bdump/afcprd01_dbw0_1417220.trc: ORA-00600: internal error code, arguments: [kmgs_parameter_update_timeout_1], [1565], [], [], [], [], [], [] ORA-01565: error in identifying file '/oracle/afcprd01/db/10.2.0/dbs/spfileafcprd01.ora' ORA-27046: file size is not a multiple of logical block size Additional information: 1 Additional information: 2759 Additional information: 512 DBW0: terminating instance due to error 471 Instance terminated by DBW0, pid = 1417220</span>

The database is down and spfile is damaged. It is unclear how the database is damaged. In this case, only the spfile is restored.

MOS provides a very detailed solution:

ORA-600 [kmgs_parameter_update_timeout_1], [1565], Instance Terminated, Can't Startup Using Either Pfile Or Spfile (Doc ID 960080.1)

To Bottom

In this Document Symptoms Cause Solution References Applies to: Oracle Server-Enterprise Edition-Version: 10.2.0.4 and later [Release: 10.2 and later] Information in this document applies to any platform. SYMPTOMS Instance terminated with the following error: Errors in file/oracle/afcprd01/db/10.2.0/admin/afcprd01_afcdb/bdump/afcprd01_dbw0_1417220.trc: ORA-00600: internal error code, arguments: [kmgs_parameter_update_timeout_1], [1565], [], [], [], [], [], [] ORA-01565: error in identifying file '/oracle/afcprd01/db/10.2.0/dbs/spfileafcprd01.ora' ORA-27046: file size is not a multiple of logical block size Additional information: 1 Additional information: 2759 Additional information: 512 DBW0: terminating instance due to error 471 Instance terminated by DBW0, pid = 1417220 Now, database can not be started using either pfile or spfile. CAUSEIn this case, this is looking spfile upload uption issue, due to which database can not be open, but pfile is also having some problem, possibly some junk character is there, which not allowing to open the database using pfile. SOLUTION To solve the issue related to initialize upted PFILE/SPFILE, please follow the below steps. -Restore any old valid pfile/spfile from backup OR -If the backup of the pfile/spfile is not available, try to get the instance startup parameters from the alert log from last startup. OR -If the backup of the pfile/spfile nor old alert log is not available, follow the below steps: Startup the database in restricted mode using a new pfile. This new pfile shocould be created using old pfile by copying all the parameters one-by-one. First make it with minimum values, just to startup and check the possibility that there is even a problem with the new pfile. -- If it is unsuccessful, then there might be an issue with new pfile also. -- Now, edit and copy all the parameters in it one-by-one from old pfile. -- Open the database with new pfile again. -- Once database is open, create spfile from this new pfile. -- Shutdown the database. -- Startup the database with the spfile now.