ORA-07445 [rnmobj1()] Seen from DROP TABLE Commands (Doc ID 752097.1)

Last updated on NOVEMBER 28, 2016

Applies to:

Oracle Server - Enterprise Edition - Version: 10.1.0 to 10.2.0.4
This problem can occur on any platform.

Symptoms

The following symptoms have been attributed to this issue :-

a) The following error or similar is seen in the alert log :-

ORA-07445: exception encountered: core dump [rnmobj1()+3895] [SIGSEGV] [Address
not mapped to object] [0x000000134]

The arguments will vary but first argument will be [rnmobj1]

b) DROP/CREATION of tables is likely to be extensive in the database, typically temporary
tables but this is not a specific requirement to hit the identified bug.

c) Current SQL statement for this session is typically an ALTER INDEX e.g. :-

ALTER INDEX "<SCHEMA_NAME"."<OBJECT_NAME>" RENAME TO "BIN$W4q1+
F04fTzgQFMKGGogHA==$0"

d) The call stack trace will be similar to :-

Function List (to Full stack) (to Summary stack)
funlockfile <- rnmobj1 <- rnmobj0 <- rnmobj <- aindrv
<- opiexe <- opiosq0 <- opiall0 <- opikpr <- opiodr
<- rpidrus <- skgmstack <- rpidru <- rpiswu2 <- kprball
<- kddrprnm <- kddrpidx <- kkdldidRecycle <- kkdldaiRecycle <- dtbdrv
<- opiexe <- opiosq0 <- kpooprx <- kpoal8 <- opiodr
<- ttcpip <- opitsk <- opiino <- opiodr <- opidrv
<- sou2o <- opimai_real <- main <- libc_start_main <- start

The key function for this article to be considered to be 'RNMOBJ1' but if other RNMOBJ
functions are seen the note might offer a solution, if no functions of this nature are seen
in the stack the note is unlikely to provide a resolution.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms