DBMS_METADATA_DIFF.COMPARE_ALTER_XML DOES NOT CAPTURE CHAR/BYTE CHANGE
(Doc ID 2386683.1)
Last updated on FEBRUARY 21, 2019
Applies to:
Oracle Database Cloud Schema Service - Version N/A and laterOracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
When using DBMS_METADATA_DIFF.COMPARE_ALERT_XML, an alter table command to change just the length semantics from BYTE to CHAR or CHAR to BYTE is not captured, however DBMS_METADATA sees the change.
If we also change the length of the column, the change can be captured by DBMS_METADATA_DIFF.COMPARE_ALERT_XML.
The package should pick up the change as it alters the default of the character storage. If a table column's char semantics has been modified from BYTE to CHAR and DBMS_METADATA_DIFF.COMPARE_ALERT_XML() does not report this difference.
Changes
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 |