Home
All Oracle Error Codes
Oracle DBA Forum

Frequent Oracle Errors

TNS:could not resolve the connect identifier specified
Backtrace message unwound by exceptions
invalid identifier
PL/SQL compilation error
internal error
missing expression
table or view does not exist
end-of-file on communication channel
TNS:listener unknown in connect descriptor
insufficient privileges
PL/SQL: numeric or value error string
TNS:protocol adapter error
ORACLE not available
target host or object does not exist
invalid number
unable to allocate string bytes of shared memory
resource busy and acquire with NOWAIT specified
error occurred at recursive SQL level string
ORACLE initialization or shutdown in progress
archiver error. Connect internal only, until freed
snapshot too old
unable to extend temp segment by string in tablespace
Credential retrieval failed
missing or invalid option
invalid username/password; logon denied
unable to create INITIAL extent for segment
out of process memory when trying to allocate string bytes
shared memory realm does not exist
cannot insert NULL
TNS:unable to connect to destination
remote database not found ora-02019
exception encountered: core dump
inconsistent datatypes
no data found
TNS:operation timed out
PL/SQL: could not find program
existing state of packages has been discarded
maximum number of processes exceeded
error signaled in parallel query server
ORACLE instance terminated. Disconnection forced
TNS:packet writer failure
see ORA-12699
missing right parenthesis
name is already used by an existing object
cannot identify/lock data file
invalid file operation
quoted string not properly terminated

ora - 07445

DBA Chirag

2005-09-07

Replies:
Hi...!!!
 
Error  - 7445 and the description on Metalink.
 
I have got another arguments then the described in the document. I opened an iTAR with previous employer and
oracle said this is not gonna corrupt yr database. Neither at physical or logical level.
 
Is the arguments really matters? The query given with this is very simple select query.
 
Any idea ??? I don have much idea about the arguements but know that it says abt the kind of operation you were doing like.
 
Regards - Chirag
 
ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [0000000101375D20] [SIGSEGV] [Address not mapped to object] [0x000000020] [] []
Current SQL statement for this session:
SELECT COUNT(*) FROM (SELECT PRIVILEGE FROM USER_SYS_PRIVS WHERE PRIVILEGE = 'CREATE USER'
UNION ALL SELECT PRIVILEGE FROM ROLE_SYS_PRIVS WHERE PRIVILEGE = 'CREATE USER')
 
 
 

Doc ID:  Note:278302.1
Subject:  ORA-07445 OCCURS DURING SHUTDOWN OPERATION IN FUNCTIONS KPOGUP OR LMXSPAX
Type:  PROBLEM
Status:  PUBLISHED
 Content Type:  TEXT/X-HTML
Creation Date:  13-JUL-2004
Last Revision Date:  20-AUG-2004
 


The information in this article applies to:
Oracle Server - Enterprise Edition - Version: 8.1.7.4 to 9.2.0.7
This problem can occur on any platform.

Errors

The following errors have all been observed for the this issue:-

ORA-07445[KPOGUP]
ORA-07445[LXMSPAX]
ORA-07445[SIGSEGV] [ADDRESS NOT MAPPED TO OBJECT]

Symptoms
All of the following symptoms will be observed

a) The failing functions KPOGUP or LXMSPAX will be reported in the 7445 error and the function KPOGUP will be reported in the stack trace OR (b)
b) The failing function KPOGUP will be reported in the stack trace and the 7445 error will contain SIGSEGV
c) The ORA-07445 will be reported after a SHUTDOWN IMMEDIATE operation.
d) The current SQL session will report : Current SQL information unavailable - no session.
e) Crash/Media recovery is not affected on startup

The stack will be similar to:-
sigacthandler kpogup kpofli kpolon opiodr ttcpip opitsk opiino opiodr opidrv
sou2o main start

OR

ksedmp ssexhd sigacthandler lxmspax kpogup kpofli kpolon opiodr ttcpip opitsk
opiino opiodr opidrv sou2o main start

The key function that needs to be present in the stack trace is KPOGUP
Cause
The root cause of the problem relates to which addresses an issue in accessing
NLS object list information during SHUTDOWN IMMEDIATE. There is no impact to the database
other than a 7445 trace file taking space on disk.

Fix

The fix is provided in Oracle10g but due to the architectural changes required is not backportable to earlier releases. There is no recommended workaround for this error as it has no impact to the database and no known set of circumstances that avoid/cause it.

References
<BUG:2295368> - Race Condition In Shutdown Immediate And Nls/Sga Fetch
<BUG:2554103> - Ora-07445 Dump [Lxmspax()+40] [Sigsegv] [Address Not Mapped To Object] With Oex