My Oracle Support Banner

ORA-7445 [smboQbNxt()+96] When Trying to Create a Unique Index (Doc ID 400745.1)

Last updated on JUNE 13, 2013

Applies to:

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

Symptoms

When trying to create a unique index on a table having a DATE column, the following error is raised in the SQL*Plus session:
ORA-03113: end-of-file on communication channel
and on the server, an error similar to the following error is seen in the alert.log:
ORA-07445: exception encountered: core dump [smboQbNxt()+96] [SIGSEGV] [Address not mapped to object] [0x303104000C000A00] [] []
The trace file for the ORA-7445 shows a call stack:
... smboQbNxt ksxb1buf rworofprFastUnpackRow qersoFetch ...
After applying the patch for bug:4655998, an error like the following error is returned instead:
ORA-600 [smboFld2Kb:fixedlen2], [6], [7], [2], [50]
The 4th argument (2) will identify a column being of type DATE (column number starts with zero, so 2 would refer to the third column in the table).

Cause

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
  Symptoms
  Cause
  Solution
  References

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.

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.