ORA-7445 IN OPIOSQ0()
(Doc ID 1061095.1)
Last updated on AUGUST 24, 2016
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.1 to 188.8.131.52.0 [Release 10.2 to 11.2]
Information in this document applies to any platform.
***Checked for relevance on 25-Jul-2012***
An error similar to the following is seen in alert.log:
ORA-07445: exception encountered: core dump [opiosq0()+64] [SIGSEGV] [Address not mapped to object] [0x00000005A]  
From the trace file a call stack similar to the following can be found:
... opiosq0 kpooprx kpoal8 opiodr ttcpip ...
Typically there will be no current SQL statement, but we can get the client machine details from the session state object:
SO: acb92da98, type: 4, owner: aca3da558, flag: INIT/-/-/0x00
(session) sid: 17147 trans: 0, creator: aca3da558, flag: (1) USR/- -/-/-/-/-/-
DID: 0000-0000-00000000, short-term DID: 0000-0000-00000000
txn branch: 0
oct: 0, prv: 0, sql: 0, psql: 0, user: 0/SYS
O/S info: user: Administrator, term: WS006, ospid: 73176:75704, machine: HQ\WS006
application name: sqlplus.exe, hash value=0
last wait for 'SQL*Net message from client' blocking sess=0x0 seq=6 wait_time=41058 seconds since wait started=0
driver id=54435000, #bytes=1, =0
The memory dump in the trace file shows:
FFFFFFFF7FFFC150 4F52412D 30303032 323A2069 6E76616C [ORA-00022: inval]
FFFFFFFF7FFFC160 69642073 65737369 6F6E2049 443B2061 [id session ID; a]
FFFFFFFF7FFFC170 63636573 73206465 6E696564 00000000 [ccess denied....]
There is no impact on the instance, ie. it continues to operate normally after the error.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|