Merge 2.2.0 to Master #18
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
which will be used during dbca call as createAsContainerDatabase
…ultitenant / Container Databases Especially the support for Multitenant Databases has brought some Changes. It's now necessary to provide the information if the Databases running on a specific RDBMS is a CDB or not. It's not a real good implementation to control this in the rdbms_dict.yml cause the fact if it is a CDB or not, is defined per database and not per RDBMS. But since 21c no longer supports any NON-CDB setups, we implemented it there. The fact if is a CDB or not is controlled by setting the variable container_database within rdbms_dict.yml. Second major adjustment can be found during the patching of a container database. You can control if you want to get all PDBs within a CDB started up after the patch has been applied to the RDBMS by using the variable patch_all_pdbs within the patch_dict.yml. Keep in mind, this variable is optional within the dictionary, so you can specify it but you don't have to. When the variable patch_all_pdbs is set to false, only PDBs that are started up during CDB startup (by using a trigger) are opened and therefore patched. When you missed the point for patching all PDBs while patching a CDB with Pythia, you have to patch the PDBs (by using datapatch) manually on your own. Pythia will not know if there are PDBs not patched.
New Feature #17: Pythia now supports Oracle Database 21c as well as Multitenant / Container Databases Especially the support for Multitenant Databases has brought some Changes. It's now necessary to provide the information if the Databases running on a specific RDBMS is a CDB or not. It's not a real good implementation to control this in the rdbms_dict.yml cause the fact if it is a CDB or not, is defined per database and not per RDBMS. But since 21c no longer supports any NON-CDB setups, we implemented it there. The fact if is a CDB or not is controlled by setting the variable container_database within rdbms_dict.yml. Second major adjustment can be found during the patching of a container database. You can control if you want to get all PDBs within a CDB started up after the patch has been applied to the RDBMS by using the variable patch_all_pdbs within the patch_dict.yml. Keep in mind, this variable is optional within the dictionary, so you can specify it but you don't have to. When the variable patch_all_pdbs is set to false, only PDBs that are started up during CDB startup (by using a trigger) are opened and therefore patched. When you missed the point for patching all PDBs while patching a CDB with Pythia, you have to patch the PDBs (by using datapatch) manually on your own. Pythia will not know if there are PDBs not patched.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New Feature #17: Pythia now supports Oracle Database 21c as well as Multitenant / Container Databases
Especially the support for Multitenant Databases has brought some Changes.
It's now necessary to provide the information if the Databases running on a
specific RDBMS is a CDB or not. It's not a real good implementation to control
this in the rdbms_dict.yml cause the fact if it is a CDB or not, is defined per
database and not per RDBMS. But since 21c no longer supports any NON-CDB setups,
we implemented it there. The fact if is a CDB or not is controlled by setting
the variable container_database within rdbms_dict.yml.
Second major adjustment can be found during the patching of a container database.
You can control if you want to get all PDBs within a CDB started up after the
patch has been applied to the RDBMS by using the variable patch_all_pdbs within
the patch_dict.yml. Keep in mind, this variable is optional within the dictionary,
so you can specify it but you don't have to. When the variable patch_all_pdbs is
set to false, only PDBs that are started up during CDB startup (by using a trigger) are
opened and therefore patched.
When you missed the point for patching all PDBs while patching a CDB with Pythia,
you have to patch the PDBs (by using datapatch) manually on your own. Pythia will
not know if there are PDBs not patched.