System Administration > System maintenance > Maintaining the database server > Maintaining the Oracle database
Migrate a non-CDB database to a CDB database
Teamcenter supports Oracle's multitenant database architecture if you use Oracle 12c or later. A multitenant architecture is deployed as a Container Database (CDB) with one or more Pluggable Databases (PDB). A Container Database (CDB) is similar to a conventional (non-CDB) Oracle database, with familiar concepts like control files, data files, undo, temp files, redo logs, and so on. It also houses the data dictionary for objects owned by the root container and those that are visible to databases in the container. A Pluggable Database (PDB) contains information specific to the database itself, relying on the container database for its control files, redo logs and so on. The PDB contains data files and temp files for its own objects, plus its own data dictionary that contains information about objects specific to the PDB. From Oracle 12.2 onward a PDB can and should have a local undo tablespace. You can migrate a non-CDB database to a CDB database using Oracle tools. The following example illustrates the database architectures before and after migration. Teamcenter supports CDB and non-CDB databases. Be aware that Oracle has deprecated support for non-CDB databases and may discontinue support after Oracle 19c. If you migrate a non-CDB Teamcenter database to a CDB database, you must perform the migration after you upgrade to Teamcenter 2606.
Source: https://docs.sw.siemens.com/documentation/external/PL20251212545240207/en-US/tc_help/AWAdmin/fhs4814155880506/kkz1737238614272/opl1737238615588/yqk1737238615674/migrateToCDB.html · retrieved Fri Jul 31 2026 00:00:00 GMT+0000 (Coordinated Universal Time)