Lossy or Convertible Conversion Data or Invalid Binary Representation In SYS.REG$ Table
(Doc ID 1490394.1)
Last updated on FEBRUARY 28, 2019
Applies to:
Enterprise Manager Base Platform - Version 11.2.0.2 and laterDatabase Migration Assistant for Unicode - Version 2.0 to 2.0
Oracle Database - Enterprise Edition - Version 11.2.0.2 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Information in this document applies to any platform.
Symptoms
CSSCAN report shows:
DMU Scan Report also may report "Invalid Binary Representation" Data in sys.reg$.
Changes
The database used in our case is a test database which is an active clone of another database, which itself was an active clone of production.
Also in this test database no one else connected apart from just me - no oem, no users, nobody connected apart from our session.
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 |
| Changes |
| Cause |
| Solution |
| References |