When comparing two Oracle schemas, one in Oracle Cloud Autonomous Transaction Processing database (18c 184.108.40.206.0), the other in Oracle Cloud Virtual machine oracle database (18c 220.127.116.11.0), Toad for Oracle schema compare finds differences of "default collation" on tables and views. SYS_Context for the USERENV SESSION_DEFAULT_COLLATION is null in both instances.
The sync script generates Alter Table ##### Default Collation ; which oracle rejects because it does not include a collation option. Plus, both instances/schema appear to have Null for default collation.
I tried unchecking the "Compare Storage Clause" options in the schema compare to no effect.
I google searched, but could not find any references to this issue.
I am using Toad for Oracle 18.104.22.168 and an update check says this is most current version.