首页 » ORACLE » ORA-07445 [ACCESS_VIOLATION] [unable_to_trans_pc] [UNABLE_TO_READ] Troubleshooting

ORA-07445 [ACCESS_VIOLATION] [unable_to_trans_pc] [UNABLE_TO_READ] Troubleshooting

Today I to read a SR,  saw a case , to face a ora-7445 internal error  when open resetlogs database after do database  recovery. So here I collected some  ora-7445 [unable_to_trans_pc] [UNABLE_TO_READ] errors with  frequently ways to  Troubleshooting .

at first to check alert log, and trace file.

# alert log

**********************************************************
Sun Sep 14 08:01:16 2014
Errors in file d:\oracle\product\10.2.0\admin\anbob\udump\anbob_ora_5060.trc:
ORA-07445: 出现异常错误: 核心转储 [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x0] [ADDR:0x0] [UNABLE_TO_READ] []

TRACE FILE
———————–
File name = anbob_ora_5060.trc
See
Dump file d:\oracle\product\10.2.0\admin\anbob\udump\anbob_ora_5060.trc
Sat Sep 13 21:56:21 2014
ORACLE V10.2.0.4.0 – Production vsnsta=0
vsnsql=14 vsnxtr=3
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 – Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Windows NT Version V5.2 Service Pack 2
CPU : 8 – type 586, 8 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:7380M/8189M, Ph+PgF:11302M/12075M, VA:2594M/3071M
Instance name: anbob

Redo thread mounted by this instance: 0 <none>
Oracle process number: 15

Windows thread id: 5060, image: ORACLE.EXE (SHAD)
……….
*** 2014-09-14 08:01:16.046
ksedmp: internal or fatal error
ORA-07445: 出现异常错误: 核心转储 [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x0] [ADDR:0x0] [UNABLE_TO_READ] []
Current SQL statement for this session:
alter database open resetlogs
check trace file d:\oracle\product\10.2.0\db_1\rdbms\trace\anbob_ora_0.trc for preloading .sym file messages
—– Call Stack Trace —–
00000000 <- zlkepfie <- zlliaer <- zllegnp <- zllenfy
<- kscnfy <- adbdrv <- opiexe <- opiosq0 <- kpooprx
<- kpoal8 <- opiodr <- ttcpip <- opitsk <- opiino
<- opiodr <- opidrv <- sou2o <- opimai_real <- opimai
<- OracleThreadStart@ <- 7C82484C

probable issue

Search in MOS found the case very likely bug 4968706
Common precipitators of the ORA-07445 include:

  •     High volume user transactions
  •     Software bugs (i.e. Bug 4098853,Bug:8592848,Bug 4723824, bug 3838614, Bug 4968706).

Bug:8592848
Current SQL information unavailable – no SGA.
—– Call Stack Trace —–
calling              call     entry
location             type     point
——————– ——– ——————-
7D611D87                      00000000
7D60F983             CALLrel  7D60F666
7D610C82             CALL???  00000000
7D5342B0             CALL???  00000000
_ssbev_env+40        CALL???  00000000
_slzgetevar+278      CALLrel  _ssbev_env+0
_kpummpin+686        CALLrel  _slzgetevar+0

_kpupin+81           CALLrel  _kpummpin+0

_kpkipgi+83          CALLrel  _kpupin+0
_kpkipgn+14          CALLrel  _kpkipgi+0
_kscnfy+1334         CALLreg  00000000
_opirip+58           CALLrel  _kscnfy+0
_opidrv+857          CALLrel  _opirip+0
_sou2o+45            CALLrel  _opidrv+0
_opimai_real+227     CALLrel  _sou2o+0
_opimai+92           CALLrel  _opimai_real+0
_BackgroundThreadSt  CALLrel  _opimai+0
Bug:4968706
Error stack extracted from the Core file.
(gdb) where
#0  0x0000002a97637b69 in kill () from /lib64/tls/libc.so.6
#1  0x0000000002246dac in slcra ()
#2  0x0000000000740463 in ssexhd ()
#3  <signal handler called>
#4  0x0000000060021a90 in ?? ()
#5  0x00000000045b2473 in ociepacm ()
#6  0x0000000003335c84 in zlkepfie ()
#7  0x0000000002c2ec08 in zlliaer ()
#8  0x0000000002c298a8 in zllegnp ()
#9  0x0000000002c2a7f8 in zllenfy ()
#10 0x00000000010e7083 in kscnfy ()
#11 0x0000000000d732d9 in adbdrv ()
#12 0x0000000002319ae9 in opiexe ()
#13 0x00000000022e5dc9 in opiosq0 ()
#14 0x000000000228c0cf in kpooprx ()
#15 0x000000000228a3d6 in kpoal8 ()
#16 0x0000000000746878 in opiodr ()
#17 0x00000000038d7025 in ttcpip ()
#18 0x0000000000742a09 in opitsk ()
#19 0x0000000000745772 in opiino ()
#20 0x0000000000746878 in opiodr ()
#21 0x0000000000740977 in opidrv ()
#22 0x000000000073ef16 in sou2o ()
—Type <return> to continue, or q <return> to quit—q

  •     Too-small RAM regions (shared_pool_size, java pool, large_pool_size), and a too-small application memory stack (e.g. PL/SQL array too small)
  •     Too small undo and temp segments
  •     Program errors (addressing outside of RAM region)
  •     Improper NLS parameter settings
  •     Hardware errors
  •     Oracle block corruption
  •     Insufficient memory(out of memory for Windows)

— Call Stack —-
_clscugblmterm -> _clsc_term -> _clscterm -> _prom_terminate
or
malloc -> _malloc_unlocked -> cleanfree -> realfree

  •     High CPU usage

— Call Stack —-
_sldmGetHostName _sldmInit _ldmInit _keltnfy _kscnfy _ksucrp _opiino _opiodr _opidrv _sou2o  _opimai_real _opimai

  •     JVM is in REMOVING status.

—- Call Stack Trace —–
joxdrp opiexe opiosq0 opiosq opiodr rpidrus rpidru rpiswu2 rpidrv rpisplu rpispl kzdukl kzudrp opiexe opiosq0 kpooprx
kpoal8 opiodr ttcpip opitsk opiino opiodr opidrv sou2o

  •     You may have used DBCA (Database Configuration Assistant) to configure a database with Oracle Label Security enabled.

—- Call Stack Trace —–
ociepacm zlliaer zllegnp zllenfy kscnfy adbdrv
-OR-
ociepacm zlkepfie zlliaer zllegnp zllenfy kscnfy adbdrv

  •     etc..

Solution of the Problem

  1. Ensure that the existing memory is functioning properly. Verify you have enough memory available to support the configuration implemented.
  2. Another option is to decrease the size of the SGA to allow more memory for the processes.
  3. Check your OS log for hardware errors.
  4. Make sure SHARED_POOL_SIZE,DB_CACHE_SIZE, JAVA_POOL_SIZE, STREAMS_POOL_SIZE value more than 200M If the OS memory is sufficient
  5. Install KB 951312 from Microsoft to overcome this problem of high CPU usage
  6. Restart the instance.
  7. Restart the OS
  8. Scan and eliminate computer viruses
  9. refer 343508.1
  10. Upgrade or fixed bugs

References   Burleson ‘S Note  and MOS’s Notes

打赏

对不起,这篇文章暂时关闭评论。