Lossy or Convertible Conversion Data or Invalid Binary Representation In SYS.REG$ Table
Last updated on AUGUST 13, 2017
Applies to:Database Migration Assistant for Unicode - Version 2.0 to 2.0
Oracle Database - Enterprise Edition - Version 220.127.116.11 and later
Enterprise Manager Base Platform - Version 18.104.22.168 and later
Information in this document applies to any platform.
CSSCAN report shows:
DMU Scan Report also may report "Invalid Binary Representation" Data in sys.reg$.
The database used in our case is a test database which is an active clone of another database, whiich 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.
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