Oracle startup error ora-7445 problem solution

Not long ago, a friend from encountered a problem, in the database startup process appear ora-7445, and then database CRASH, environment 11.1.0.7 windows version, temporarily disabled the smon tx recovery open database, no more tracking. Record it here.

# DB ALERT

Alter database open
Beginning crash recovery of 1 threads
Parallel recovery started with 15 processes
Started redo scan
Completed redo scan
503 redo blocks read, 54 data blocks need recovery
Started redo application
Thread 1: logseq 833357, block 3
Recovery of Online Redo Log: Thread 1 Group 7 Seq 833357 Reading mem 0
Mem #0: E: \ ORACLE \ APP \ ORADATA \ anbob \ REDO07.LOG
Completed redo application of 0.19 MB
Completed crash recovery
Thread 1: logseq 833357, block 506, scn 14928904673880
54 data blocks read, 54 data blocks writ10, 503 redo blocks read
Thu Jun 23 15:24:31 2016
Thread 1 advanced to log sequence 833358 (thread open)
Thread 1 opened at log sequence 833358
Current log #8 seq #833358 mem #0: E: \ ORACLE \ APP \ ORADATA \ anbob \ REDO08.LOG
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Thu Jun 23 15:24:32 2016
SMON: enabling cache recovery
Successfully onlined Undo Tablespace 2.
Verifying file header compatibility for 11g tablespace encryption ..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Exception [type: ACCESS_VIOLATION, UNABLE_TO_WRITE] [ADDR: 0x19DC0000] [PC: 0x52B428E, _ intel_fast_memcpy.A () + 18]
Database Characterset is ZHS16GBK
Errors in file e: \ oracle \ app \ diag \ rdbms \ anbob \ trace \ anbob_smon_484.trc (incident = 389522 ):
ORA-07445: exception encountered: core dump [intel_fast_memcpy.A () + 18] [ACCESS_VIOLATION] [ADDR: 0x19DC0000] [PC: 0x52B428E] [UNABLE_TO_WRITE] []
Incident details in: e: \ oracle \ app \ diag \ rdbms \ anbob \ incident \ incdir_389522 \ anbob_smon_484_i389522.trc
Opening with internal Resource Manager plan
Starting background process FBDA
Thu Jun 23 15:24:33 2016
FBDA started with pid = 52, OS id = 4484
Replication_dependency_tracking turned off (no async multimaster replication found)
Thu Jun 23 15:24:34 2016
Trace dumping is refreshing Ming id = [cdmp_20160623152434]
Starting background process QMNC
Thu Jun 23 15:24:34 2016
QMNC started with pid = 53, OS id = 4824
Thu Jun 23 15:24:35 2016
Sweep Incident [389522]: completed
Thu Jun 23 15:24:37 2016
Errors in file e: \ oracle \ app \ diag \ rdbms \ anbob \ trace \ anbob_pmon_81_trc:
ORA-00474: SMON process terminated with error.
PMON (ospid: 820): terminating the instance due to error 474
Thu Jun 23 15:24:39 2016
Opidrv aborting process S000 ospid (5468_5488) due to error ORA-474
Instance terminated by PMON, pid = 820
Zz

Oracle Database 11g Enterprise Edition Release 11.1.0.7.0-64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Windows NT Version V6.0 Service Pack 1
CPU: 16-type 8664, 16 Physical Cores
Process Affinity: 0x0000000000000000
Memory (Avail/Total): Ph: 11838 M/16377 M, Ph + PgF: 23713 M/32548 M
Instance name: anbob
Redo thread mounted by this instance: 1
Oracle process number: 13
Windows thread id: 484, image: ORACLE. EXE (SMON)

* ** 15:24:33. 319
* ** Session id: (873.1) 15:24:33. 319
* ** Client id :() 15:24:33. 319
* ** Service name :() 15:24:33. 319
* ** Module name :() 15:24:33. 319
* ** Action name :() 15:24:33. 319

Dump continued from file: e: \ oracle \ app \ diag \ rdbms \ anbob \ trace \ anbob_smon_484.trc
ORA-07445: exception encountered: core dump [intel_fast_memcpy.A () + 18] [ACCESS_VIOLATION] [ADDR: 0x19DC0000] [PC: 0x52B428E] [UNABLE_TO_WRITE] []

========= Dump for incident 389522 (ORA 7445 [intel_fast_memcpy.A () + 18]) ========
----- Beginning of Customized Incident Dump (s )-----
Exception [type: ACCESS_VIOLATION, UNABLE_TO_WRITE] [ADDR: 0x19DC0000] [PC: 0x52B428E, _ intel_fast_memcpy.A () + 18]

Oracle Database 11g Enterprise Edition Release 11.1.0.7.0-64bit Production
Process Id: 0x0000155c Thread Id: 0x000001e4 Time: Thu Jun 23 15:24:33
Excp. Code: 0xc0000005 Excp. Type: ACCESS_VIO Flags: 0x00000000

------------------- Registers ----------------------------
Ip = 00000000052B428E sp = 00000000197FAEE8 rp = 0000000000000002
R1 = 20171000019dbe104 r2 = 0000000000000010 r3 = 20171000019a2a9cc
R4 = 0000000000000054 r5 = 201710000197faee8 r6 = 0000000000000002 r7 = 20171000019a2c8c4
R8 = 0000000019 DBFFFC r9 = 20171000000001f7c r10 = 0000000000002104 r11 = 0000000000002104
R12 = 20171000000001f7c r13 = 201710000197fb4d0 r14 = 20171000019a28808 r15 = 20171000019a2a97e
------------------- End of Registers ---------------------

* ** 15:24:33. 320
----- SQL Statement (None )-----
Current SQL information unavailable-no cursor.

----- Call Stack Trace -----
Calling call entry argument values in hex
Location type point (? Means dubious value)
----------------------------------------------------------------------------
_ Intel_fast_memcpy. 0000000000000000 000000000 000000000
A () + 18 000000000
20171000019a2a978 CALL ??? _ Intel_fast_memcpy. 0198101CC 0012F2DB7 000030000
A () + 18 0 FFFFFFFF
Too many 198101cc CALL ??? 20171000019a2a978 0012F2DB7 000030000 0 FFFFFFFF
00000009C
Kturunlc () + 813 CALL ??? 201710000198101cc 000030000 0 FFFFFFFF 00000009C
000000000
Kturmmbu () + 65 CALL ??? Kturunlc () + 0 0197FB140 015725720 000000000
015725720
Kturrur () + 621 CALL ??? Kturmmbu () + 18 369006fa 30E075F27 000000003
007D5F54F
Ktundo () + 515 CALL ??? Kturrur () + 0 000000004 005D1DEB8 002050030
0000000FF
Ktubko () + 1435 CALL ??? Ktundo () + 0 000000002 B553B00C0131A
0198101C0 000000204
Kturrt () + 27766 CALL ??? Ktubko () + 0 0197FCEA8 0197FCE50 000000004
0197FD1A0
Kturec () + 1002 CALL ??? Kturrt () + 26107 0197FD1A0 30E070013
Cd352130001 000000000
Kturax () + 915 CALL ??? Kturec () + 0 000000046 000000000 000000001
CD3500000000
Ktprbeg () + 2391 CALL ??? Kturax () + 0 200000004 000000000 000021300
1FCC34F38
Ktmmon () + 11837 CALL ??? Ktprbeg () + 782 000000000 007B301A8 019D900A0
000000428
KtmSmonMain () + 232 CALL ??? Ktmmon () + 485 006F376B0 000002000 019D9CF90
015725CE0
Ksbrdp () + 1165 CALL ??? KtmSmonMain () + 0 006F376B0 00000A07C
3EDD00000424 14720012e133
Opirip () + 727 CALL ??? Ksbrdp () + 0 00000001E 005CDB518 0197FF9E0
000000000
Opidrv () + 855 CALL ??? Opirip () + 0 000000032 000000004 0197FFD30
000000000
Sou2o () + 52 CALL ??? Opidrv () + 213 000000032 000000004 0197FFD30
0197FFDB0
Opimai_real () + 295 CALL ??? Sou2o () + 0 000000000 0771BA967 000000000
000000000
Opimai () + 96 CALL ??? Opimai_real () + 0 000000000 000000000 000000000
000000000
BackgroundThreadSta CALL ??? Opimai () + 0 0197FFE98 000000001 000000000
Rt () + 695 000000000
201710000771b495d CALL ??? BackgroundThreadSta 01B917FA0 000000000 000000000
Rt () + 0 000000000
201710000773b8791 CALL ??? 201710000771b4950 000000000 000000000 000000000
000000000

The log shows that the smon process encountered a fatal error in tx recover at startup. First, the smon transaction rollback is disabled and the database is successfully opened.

Alter system set event = '2014 trace name context forever, level 2 'scope = spfile;
Shutdown immediate;
Startup;
Post-processing
1. You can try to query dead transactions in the database, confirm the objects involved, or modify the content.
2. You can try to track the undo application to configure the 10218 event, find the last undo block applied according to uba, and then find the current record of the data block.
This event simply shows the undo block addresses for the undo applied during recovery

Alter system set events '10218 trace name context forever, level 1 ';

Uba: 0x00c0aa56. 00e2. 12
Uba: 0x00c0aa56. 00e2. 11
Uba: 0x00c0aa56. 00e2. 10
Uba: 0x00c0aa56. 00e2. 0f
Uba: 0x00c0aa56. 00e2. 0e
Uba: 0x00c0aa56. 00e2. 0d
Trace monitor transaction recovery during startup

Alter system set events '10013 trace name context forever, level 10 ';
3. Try to delete the current table and rebuild it.
4. Confirm the problem. You can try to commit the transaction and clear the rollback segment with BBED.