Record the process of automatic Down machine a few minutes after an Oracle startup

Recently, in the process of work, we encountered an Oracle failure. The phenomenon is that the Oracle database will automatically shut down within ten seconds after the startup. After a day and a half of processing, Oracle will be temporarily recovered. It is hereby recorded for follow-up tracking.

1. Observe the problem

Find the Oracle exception and observe through the alert log. The alert log path is as follows:

startup mount;
SQL> show parameter back

NAME				     TYPE	 VALUE
------------------------------------ ----------- ------------------------------
_optimizer_use_feedback 	     boolean	 FALSE
background_core_dump		     string	 partial
background_dump_dest		     string	 /u01/app/oracle/diag/rdbms/orc
						 l/orcl/trace
backup_tape_io_slaves		     boolean	 FALSE
db_flashback_retention_target	     integer	 1440
fast_start_parallel_rollback	     string	 LOW
rollback_segments		     string
transactions_per_rollback_segment    integer	 5

The location of the background dump dest instant alert log.

Clear the alert log first (it is inconvenient to trace because the log is too large)

>alert_orcl.log
tail -200f alert_orc.log

Start the database under oracle user:

startup;

At this time, when the status changes from mount to open, there are multiple exception logs to be analyzed one by one.

Tue Feb 11 16:21:43 2020
alter database open
Beginning crash recovery of 1 threads
 parallel recovery started with 9 processes
Started redo scan
Completed redo scan
 read 78 KB redo, 9 data blocks need recovery
Started redo application at
 Thread 1: logseq 7, block 3
Recovery of Online Redo Log: Thread 1 Group 1 Seq 7 Reading mem 0
  Mem# 0: /u01/data/orcl/redo01.log
Completed redo application of 0.05MB
Completed crash recovery at
 Thread 1: logseq 7, block 159, scn 16334181718600
 9 data blocks read, 9 data blocks written, 78 redo k-bytes read
Tue Feb 11 16:21:44 2020
Thread 1 advanced to log sequence 8 (thread open)
Thread 1 opened at log sequence 8
  Current log# 2 seq# 8 mem# 0: /u01/data/orcl/redo02.log
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Tue Feb 11 16:21:44 2020
SMON: enabling cache recovery
[15868] Successfully onlined Undo Tablespace 2.
Undo initialization finished serial:0 start:717814394 end:717814554 diff:160 (1 seconds)
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is ZHS16GBK
No Resource Manager plan active
replication_dependency_tracking turned off (no async multimaster replication found)
Tue Feb 11 16:21:45 2020
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_p002_15891.trc  (incident=5686879):
ORA-01578: ORACLE data block corrupted (file # 42, block # 651993)
ORA-01110: data file 42: '/u02/oradata/GUMDBHN01.dbf'
Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_5686879/orcl_p002_15891_i5686879.trc
Tue Feb 11 16:21:45 2020
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_p013_15913.trc  (incident=5686967):
ORA-00600: internal error code, arguments: [ktbair1], [1], [3], [], [], [], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_5686967/orcl_p013_15913_i5686967.trc
Starting background process QMNC
Tue Feb 11 16:21:45 2020
QMNC started with pid=40, OS id=15933 
Tue Feb 11 16:21:45 2020
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_mmon_15861.trc  (incident=5686823):
ORA-00600: internal error code, arguments: [4193], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_5686823/orcl_mmon_15861_i5686823.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_15868.trc  (incident=5686855):
ORA-00600: internal error code, arguments: [4194], [ody "SYS.DBMS_STANDARD"
Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_5686855/orcl_ora_15868_i5686855.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_5686879/orcl_p002_15891_i5686879.trc:
ORA-10388: parallel query server interrupt (failure)
ORA-01578: ORACLE data block corrupted (file # 42, block # 651993)
ORA-01110: data file 42: '/u02/oradata/GUMDBHN01.dbf'
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_5686879/orcl_p002_15891_i5686879.trc:
ORA-10388: parallel query server interrupt (failure)
ORA-01578: ORACLE data block corrupted (file # 42, block # 651993)
ORA-01110: data file 42: '/u02/oradata/GUMDBHN01.dbf'
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Block recovery from logseq 8, block 149 to scn 16334181718756
Recovery of Online Redo Log: Thread 1 Group 2 Seq 8 Reading mem 0
  Mem# 0: /u01/data/orcl/redo02.log
Block recovery stopped at EOT rba 8.153.16
Block recovery completed at rba 8.153.16, scn 3803.421092068
SMON: Restarting fast_start parallel rollback
Tue Feb 11 16:21:46 2020
Dumping diagnostic data in directory=[cdmp_20200211162146], requested by (instance=1, osid=15913 (P013)), summary=[incident=5686967].
Block recovery from logseq 8, block 149 to scn 16334181718759
Recovery of Online Redo Log: Thread 1 Group 2 Seq 8 Reading mem 0
  Mem# 0: /u01/data/orcl/redo02.log
Block recovery stopped at EOT rba 8.153.16
Block recovery completed at rba 8.153.16, scn 3803.421092068
Block recovery from logseq 8, block 149 to scn 16334181718754
Recovery of Online Redo Log: Thread 1 Group 2 Seq 8 Reading mem 0
  Mem# 0: /u01/data/orcl/redo02.log
Block recovery completed at rba 8.152.16, scn 3803.421092067
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_mmon_15861.trc  (incident=5686824):
ORA-00600: internal error code, arguments: [4193], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_5686824/orcl_mmon_15861_i5686824.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Dumping diagnostic data in directory=[cdmp_20200211162147], requested by (instance=1, osid=15861 (MMON)), summary=[incident=5686823].
Block recovery from logseq 8, block 153 to scn 16334181718764
Recovery of Online Redo Log: Thread 1 Group 2 Seq 8 Reading mem 0
  Mem# 0: /u01/data/orcl/redo02.log
Block recovery stopped at EOT rba 8.155.16
Block recovery completed at rba 8.155.16, scn 3803.421092074
Block recovery from logseq 8, block 149 to scn 16334181718765
Recovery of Online Redo Log: Thread 1 Group 2 Seq 8 Reading mem 0
  Mem# 0: /u01/data/orcl/redo02.log
Block recovery stopped at EOT rba 8.155.16
Block recovery completed at rba 8.155.16, scn 3803.421092074
Block recovery from logseq 8, block 153 to scn 16334181718761
Recovery of Online Redo Log: Thread 1 Group 2 Seq 8 Reading mem 0
  Mem# 0: /u01/data/orcl/redo02.log
Block recovery completed at rba 8.155.16, scn 3803.421092074
Block recovery from logseq 8, block 149 to scn 16334181718755
Recovery of Online Redo Log: Thread 1 Group 2 Seq 8 Reading mem 0
  Mem# 0: /u01/data/orcl/redo02.log
Block recovery completed at rba 8.153.16, scn 3803.421092073
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_smon_15857.trc  (incident=5686807):
ORA-00600: internal error code, arguments: [4137], [26.11.412457], [0], [0], [], [], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_5686807/orcl_smon_15857_i5686807.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_p002_15891.trc  (incident=5686880):
ORA-00600: internal error code, arguments: [ktbair1], [1], [3], [], [], [], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_5686880/orcl_p002_15891_i5686880.trc
Tue Feb 11 16:21:48 2020
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_p000_15887.trc  (incident=5686863):
ORA-01578: ORACLE data block corrupted (file # 42, block # 651993)
ORA-01110: data file 42: '/u02/oradata/GUMDBHN01.dbf'
Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_5686863/orcl_p000_15887_i5686863.trc
Tue Feb 11 16:21:48 2020
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_p001_15889.trc  (incident=5686871):
ORA-00600: internal error code, arguments: [4198], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_5686871/orcl_p001_15889_i5686871.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_15868.trc  (incident=5686856):
ORA-00603: ORACLE server session terminated by fatal error
ORA-00600: internal error code, arguments: [4194], [ody "SYS.DBMS_STANDARD"
Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_5686856/orcl_ora_15868_i5686856.trc
Dumping diagnostic data in directory=[cdmp_20200211162148], requested by (instance=1, osid=15861 (MMON)), summary=[incident=5686824].
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
ORACLE Instance orcl (pid = 13) - Error 600 encountered while recovering transaction (26, 11).
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_smon_15857.trc:
ORA-00600: internal error code, arguments: [4137], [26.11.412457], [0], [0], [], [], [], [], [], [], [], []
Block recovery from logseq 8, block 149 to scn 16334181718756
Recovery of Online Redo Log: Thread 1 Group 2 Seq 8 Reading mem 0
  Mem# 0: /u01/data/orcl/redo02.log
Block recovery completed at rba 8.153.16, scn 3803.421092073
Dumping diagnostic data in directory=[cdmp_20200211162149], requested by (instance=1, osid=15891 (P002)), summary=[incident=5686880].
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_p000_15887.trc  (incident=5686864):
ORA-01578: ORACLE data block corrupted (file # , block # )
Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_5686864/orcl_p000_15887_i5686864.trc
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_smon_15857.trc  (incident=5686808):
ORA-01578: ORACLE data block corrupted (file # 42, block # 651993)
ORA-01110: data file 42: '/u02/oradata/GUMDBHN01.dbf'
Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_5686808/orcl_smon_15857_i5686808.trc
Block recovery from logseq 8, block 21 to scn 16334181718692
Recovery of Online Redo Log: Thread 1 Group 2 Seq 8 Reading mem 0
  Mem# 0: /u01/data/orcl/redo02.log
Block recovery completed at rba 8.89.16, scn 3803.421092005
Block recovery from logseq 8, block 155 to scn 16334181718766
Recovery of Online Redo Log: Thread 1 Group 2 Seq 8 Reading mem 0
  Mem# 0: /u01/data/orcl/redo02.log
opiodr aborting process unknown ospid (15868) as a result of ORA-603
Block recovery completed at rba 8.158.16, scn 3803.421092081
Tue Feb 11 16:21:50 2020
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x6E2D382A] [PC:0x97F38FA, kgebse()+776] [flags: 0x0, count: 1]
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x6E2D382A] [PC:0x97F38FA, kgebse()+776] [flags: 0x2, count: 2]
SMON: ignoring slave err,downgrading to serial rollback
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_smon_15857.trc  (incident=5686809):
ORA-00600: internal error code, arguments: [4137], [3.31.4779235], [0], [0], [], [], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_5686809/orcl_smon_15857_i5686809.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Dumping diagnostic data in directory=[cdmp_20200211162151], requested by (instance=1, osid=15857 (SMON)), summary=[abnormal process termination].
ORACLE Instance orcl (pid = 13) - Error 600 encountered while recovering transaction (3, 31).
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_smon_15857.trc:
ORA-00600: internal error code, arguments: [4137], [3.31.4779235], [0], [0], [], [], [], [], [], [], [], []
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_smon_15857.trc  (incident=5686810):
ORA-00600: internal error code, arguments: [4137], [10.5.6991346], [0], [0], [], [], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_5686810/orcl_smon_15857_i5686810.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
ORACLE Instance orcl (pid = 13) - Error 600 encountered while recovering transaction (10, 5).
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_smon_15857.trc:
ORA-00600: internal error code, arguments: [4137], [10.5.6991346], [0], [0], [], [], [], [], [], [], [], []
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_smon_15857.trc  (incident=5686811):
ORA-00600: internal error code, arguments: [4137], [16.32.1167277], [0], [0], [], [], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_5686811/orcl_smon_15857_i5686811.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
ORACLE Instance orcl (pid = 13) - Error 600 encountered while recovering transaction (16, 32).
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_smon_15857.trc:
ORA-00600: internal error code, arguments: [4137], [16.32.1167277], [0], [0], [], [], [], [], [], [], [], []
Tue Feb 11 16:21:54 2020
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_smon_15857.trc  (incident=5686812):
ORA-00600: internal error code, arguments: [4137], [26.11.412457], [0], [0], [], [], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_5686812/orcl_smon_15857_i5686812.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Tue Feb 11 16:21:57 2020
PMON (ospid: 15833): terminating the instance due to error 474
Tue Feb 11 16:21:58 2020
System state dump requested by (instance=1, osid=15833 (PMON)), summary=[abnormal instance termination].
System State dumped to trace file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_diag_15843_20200211162158.trc
Dumping diagnostic data in directory=[cdmp_20200211162158], requested by (instance=1, osid=15833 (PMON)), summary=[abnormal instance termination].
Instance terminated by PMON, pid = 15833

2. Problem 1 handling

Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_p000_6740.trc  (incident=9879108):
ORA-01578: ORACLE data block corrupted (file # 42, block # 651993)
ORA-01110: data file 42: '/u02/oradata/GUMDBHN01.dbf'
Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_9879108/orcl_p000_6740_i9879108.trc
replication_dependency_tracking turned off (no async multimaster replication found)
Wed Feb 12 20:27:39 2020

According to the log analysis, there is a problem with the data file. The violent solution is to take the data file offline, delete it, and rebuild it. (the database cannot be restored because there is no backup)

  1. First of all, because oracle cannot be started and data files cannot be deleted under mount, perform the following operations first
startup mount;
create pfile ='/home/oracle/orcl.ora' from spfile;
  1. Modify the ora file to add the following:
# If the database needs to be recovered and undo is inconsistent with redo, this parameter is required when some redo cannot be recovered. resetlogs are allowed
*._allow_resetlogs_corruption=TRUE
# UNDO segment management mode changed to manual
undo_management='MANUAL'
undo_tablespace='SYSTEM'
rollback_segments='SYSTEM'
  1. Start database
startup force pfile='/home/oracle/orcl.ora';
alter database open;
  1. Perform offline data file operation
alter database datafile '/u02/oradata/GUMDBHN01.dbf' offline drop;
alter database create datafile '/u02/oradata/GUMDBHN01.dbf';

This operation will cause data loss. Please consider it if it is not a special case.
You can also refer to the following websites:

3. Problem 2 handling

Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_smon_15857.trc  (incident=5686807):
ORA-00600: internal error code, arguments: [4137], [26.11.412457], [0], [0], [], [], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_5686807/orcl_smon_15857_i5686807.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_p002_15891.trc  (incident=5686880):
ORA-00600: internal error code, arguments: [ktbair1], [1], [3], [], [], [], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_5686880/orcl_p002_15891_i5686880.trc
Tue Feb 11 16:21:48 2020

After troubleshooting, it is found that this problem is caused by the undo table space problem. To solve this problem, do the following

  1. Troubleshooting the faulty undo section
startup force pfile='/home/oracle/orcl.ora';
SQL> select segment_name,status,tablespace_name from dba_rollback_segs where status = 'NEEDS RECOVERY';

SEGMENT_NAME		       STATUS		TABLESPACE_NAME
------------------------------ ---------------- ------------------------------
_SYSSMU3_4167512414$	       NEEDS RECOVERY	UNDOTBS1

Add the above to / home/oracle/orcl.ora you just created:
_CORRUPTED_ROLLBACK_SEGMENTS = ('_SYSSMU3_4167512414$')
2. Restart the database

shutdown immediate;
startup pfile='/home/oracle/orcl.ora';
  1. To view the existing undo tablespaces:
SELECT * FROM dba_data_files a WHERE a.TABLESPACE_NAME LIKE 'UNDO%';
SELECT * FROM dba_tablespaces a WHERE a.TABLESPACE_NAME LIKE 'UNDO%';
  1. Delete rebuild undo table space
SQL> drop tablespace undotbs1 including contents and datafiles;
drop tablespace undotbs1 including contents and datafiles
*
ERROR at line 1:
ORA-01548: active rollback segment '_SYSSMU10_116238249$' found, terminate
dropping tablespace


SQL> 
SQL> drop tablespace undotbs2 including contents and datafiles;
drop tablespace undotbs2 including contents and datafiles
*
ERROR at line 1:
ORA-01548: active rollback segment '_SYSSMU207_3501698357$' found, terminate
dropping tablespace

If there is any problem with the segment, execute:

SQL> select segment_name,status,tablespace_name from dba_rollback_segs where status = 'NEEDS RECOVERY';

SEGMENT_NAME		       STATUS		TABLESPACE_NAME
------------------------------ ---------------- ------------------------------
_SYSSMU10_116238249$	       NEEDS RECOVERY	UNDOTBS1
_SYSSMU16_2905918700$	       NEEDS RECOVERY	UNDOTBS1
_SYSSMU26_654891904$	       NEEDS RECOVERY	UNDOTBS1
_SYSSMU207_3501698357$	       NEEDS RECOVERY	UNDOTBS2

Add this information to / home/oracle/orcl.ora:
_CORRUPTED_ROLLBACK_SEGMENTS = ('_SYSSMU10_116238249$',...)
Restart Oracle:

shutdown immediate;
startup pfile='/home/oracle/orcl.ora';

At this time, it can be deleted normally. Then switch to undo table space:

SQL> create undo tablespace undotbs3 datafile '/u03/oradata/UNDOTBS3.dbf' size 30G autoextend off;

SQL> alter system set undo_tablespace='undotbs3';
alter system set undo_tablespace='undotbs3'
*
ERROR at line 1:
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-30014: operation only supported in Automatic Undo Management mode

At this time, undo processes the MANUAL status:

SQL> show parameter undo;

NAME				     TYPE	 VALUE
------------------------------------ ----------- ------------------------------
undo_management 		     string	 MANUAL
undo_retention			     integer	 900
undo_tablespace 		     string

Modify / home/oracle/orcl.ora: undo management = auto, restart Oracle, and execute alter system set undo tablespace = undotbs3 here; normal.
5. Restore and start Oracle Remove the following from the / home/oracle/xt2.ora file:

*._allow_resetlogs_corruption=TRUE
undo_management='MANUAL'
undo_tablespace='SYSTEM'
rollback_segments='SYSTEM'

Revised to:

orcl.__db_cache_size=13690208256
orcl.__java_pool_size=201326592
orcl.__large_pool_size=3959422976
orcl.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
orcl.__pga_aggregate_target=6777995264
orcl.__sga_target=20333985792
orcl.__shared_io_pool_size=0
orcl.__shared_pool_size=2348810240
orcl.__streams_pool_size=0
*._allow_resetlogs_corruption=TRUE
*._allow_terminal_recovery_corruption=TRUE
*._optimizer_use_feedback=FALSE
*.audit_file_dest='/u01/app/oracle/admin/orcl/adump'
*.audit_trail='NONE'
*.compatible='11.2.0.4.0'
*.control_files='/u01/data/orcl/control01.ctl','/u01/app/oracle/fast_recovery_area/orcl/control02.ctl'
*.db_block_checking='FALSE'
*.db_block_checksum='TRUE'
*.db_block_size=8192
*.db_domain=''
*.db_name='orcl'
*.db_recovery_file_dest='/u01/app/oracle/fast_recovery_area'
*.db_recovery_file_dest_size=4385144832
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=orclXDB)'
*.job_queue_processes=0
*.open_cursors=2500
*.pga_aggregate_target=6766460928
*.processes=10000
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=20299382784
undo_management='AUTO'

Rebuild spfile:

create spfile from pfile='/home/oracle/orcl.ora';
shutdown immediate;
startup;

At this point, the database is normal.

Reference article:
ORA-00600: internal error code, arguments: [kdBlkCheckError]
Oracle database start failure display ORA-01190 ORA-01110 ORA-19729
ORA-00600: internal error code, arguments: [4137]

Tags: Database Oracle SQL Session

Posted on Wed, 12 Feb 2020 21:55:19 -0800 by matecocido