Database Administration (MOSC)

MOSC Banner

DMU.PDB_SYNC$ internal table with Invalid Binary Representation

Oracle Database Enterprise Edition 19.19

DMU 19.1

We have executed an upgrade from 11.2.0.4 to 19.19 (NON-CDB)

Now we have to convert characterset from WE8ISO8859P1 to AL32UTF8

After execute DMU SCAN, in "Database Scan Report" we have found a row with "Invalid binary Representation" in PDB_SYNC$ internal table.


---------------------------------------------------------------------------------

The rows of PDB_SYNC$ have been inserted by dbupgrade execution script:

---------------------------------------------------------------------------------

SQL> select max(CTIME) from pdb_sync$;

MAX(CTIME)

-------------------

04-OCT-2023 21:02:22

SQL> select min(CTIME) from pdb_sync$;


MIN(CTIME)

--------------------

04-OCT-2023 20:44:01

SQL>

set lines 400

col ACTION_TIME for a20

col ACTION for a10

col NAMESPACE for a9

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center