With the introduction of the multitenant architecture, it is possible to duplicate PDBs by cloning or even convert nonCDBs into PDBs. This opens up new possibilities in the operation and maintenance of databases:
Fast provision of test and development stages from the production state : If a separate environment is required for the currently planned sprint or to analyze a bug, the state of the productively used PDB is quickly and easily cloned and the tests are carried out with the cloned state.
Testing a new application version : If the application used is also set up as a test installation with a new release, it is also worthwhile to provide a australia telegram screening clone from the productive PDB. This allows the new release to be tested and accepted separately. The same applies to Oracle patches that need to be tested. If everything works, the cloned PDB can be used as the new productive PDB.
Analysis of performance problems : For this purpose, you can quickly and easily set up an analysis system using a clone of the PDB used.
Rollback to old state : If something is wrong with the application patch or the Oracle release upgrade together with the application, you can simply switch back to the source PDB.
Minimal maintenance effort : Cloning PDBs is possible live, which is why downtime of the PDB to be cloned is not necessary.