noncdb_to_pdb.sql – why does it take so long?

What is noncdb_to_pdb.sql? The script noncdb_to_pdb.sql gets run only once in the life span of your database. It gets executed when a regular Oracle database (non-CDB) gets move to become part of a Single-/Multitenant deployment as a pluggable database (PDB). But why does it take so long? You will never run this script again for this database. The script is a sanity script to clean up and change things in a non-CDB, and unite it finally and irreversible with the CDB. How long does it take to complete? Runtime varies a lot. It depends mainly on the number of objects…

Move to Locally Managed Tablespaces

As I’ve got asked during the workshop in Warsaw how to migrate Dictionary Managed to Locally Managed tablespaces here’s some additional information and an example. To find out if a tablespace is dictionary or locally managed you’d use this query: SQL> select TABLESPACE_NAME, EXTENT_MANAGEMENT from DBA_TABLESPACES; The procedure to migrate to locally managed tablespace is: SQL> EXECUTE DBMS_SPACE_ADMIN.TABLESPACE_MIGRATE_TO_LOCAL(‘tbs’); And the whole migration procedure would look like this: STARTUP RESTRICT EXCLUSIVE; EXEC DBMS_SPACE_ADMIN.TABLESPACE_MIGRATE_TO_LOCAL(‘TBS’); — do this for all tablespaces except SYSTEM, TEMP and SYSAUX DROP TABLESPACE TEMP; — necessary if there’s no “real” temp tablespace definded yet – see Note:160426.1 CREATE…