Sanity Check of Oracle NUMBERS, How to Find and Patch Invalid Numeric Data
(Doc ID 136620.1)
Last updated on NOVEMBER 22, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 6.0.0.0 and laterOracle Database Configuration Assistant - Version 8.1.7 and later
Enterprise Manager for Oracle Database - Version 8.1.7.4 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Purpose
PURPOSE
To share a method of analyzing tables and detecting invalid numeric data.
Scope
SCOPE & APPLICATION
Sometimes, doing calculations with numbers stored in an Oracle database you
may receive errors like:
ORA-27103: internal error
along with
ORA-00472: PMON process terminated with error
or one or more of the following:
ORA-00447: fatal error in background process
ORA-03113: end-of-file on communication channel
ORA-07445: exception encountered: core dump [%s] [%s]
for very specific number values.
In some cases the database can crash.
This can happen if you have invalid numeric data in your data base.
There are many ways this invalid data can be inserted into your database,
such as using a non-Oracle tool or using OCI in a C progam. Events can be
set to prevent this from occurring, see Note 979657.8
This bulletin shows one way to find and patch invalid numeric data in the
database. It does not find all the possible invalid data, bug it can be of
help in the time-consuming and arduous work of uncovering such corruptions.
Details
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |