Does the user MIGRATION_REPO have SYSDBA privileges?
It may be that allowing NULL into the ID column causes problems later.
Is there a sequence that looks likely to be the source of the ID column.
Perhaps try changing the default value of the ID column to be that sequence.
Is this a new or existing migration project?
On Wed, Oct 14, 2020 at 5:22 PM Lynne Flatley <lflatley@xxxxxxxxx> wrote:
We have a MySQL database that we would like to convert to Oracle. I set
up SQL Developer (19.4) to use the MySQL jar file (5.1.29) so I am able to
view the MySQL schema and I can migrate tables by right-clicking on a table
or a set of tables and selecting Oracle copy but I would really like to set
a script that will migrate all of them via the script, i.e. not having to
manually right-click to initiate each table's conversion.
Using the migration project wizard, SQL Developer creates the migration
repository but when I try to run it, I get a constraint issue (null not
ORA-01400 cannot insert NULL into MIGRATION_REPO.MD_PROJECTS.ID
I was thinking of removing the column constraint of not allowing NULL for
all tables in the Migration repository?
Thanks in advance for any ideas that you have.