I know pdb databases are not supported, but hey: Then there is reality.

Mostly I get errors of the type: "ORA-65040: operation not allowed from within a pluggable database"

So far I had to re-edit three 8.0 sql-scripts for the migration to even continue.

• ./database/Create Scripts/Create_User_Grants.sql
• ./database/migration/sys_adjust_optimizer.sql
• ./database/migration/sys_enable_options.sql

... but it never ends... so many errors I have to re-edit and send exceptions to null

So I have a feeling this will take a while.

Then there is this (faulty) knowledge article which gives hope about improvements being "on the way" in P02

1. but P02 is not released while I am writing this
2. This article is also giving incorrect instructions:

• "$AVEKSA_HOME/database/cliAveksa.sh -check dbcredentials" will not test all credentials to the database, and those tests are not enough for giving a "go" for a schema migration
  • When schema migration is done it is not using the basic 4 users (at least not in base 8.0 version) -> it is using SYS-user, which is NOT tested.

Anyway:

My question is: Are there scripts that can manage a database migration if running on multiple-tenant pdb?

I mean: I can't be the only one struggling with this.

The more I look into these scripts I see that the AMAZON-cloud parts seem much smarter in all they do.

And where the standard database parts, seem to expect a to change system wide dba-roles, etc... which would not work in the cloud or pdb databases.

So must be a "middle-way"... like having scripts that have a structure that have parts compatible with pdb-databases. For example (small snippet):

DECLARE

is_cdb varchar2(3);

BEGIN

select cdb into is_cdb from v$database;

if is_cdb = 'YES' then

<do pdb-migration-magic>

end if;

END;

BTW the above works on ANY oracle database, and you can even get cdb-type with an extra check.

If it is not a pdb you get the answer 'NO'.