Allow to create new PDB from an existing pdb file instead of pdbseed #62
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.
Allow to create PDB from a previously exported/unplugged
<PDB_NAME>.pdb
file instead of creating an empty PDB frompdbseed
.Our use-case:
<PDB_NAME>.pdb
fileCOPY
this fileIt would be nice to have ability to just upload custom
<PDB_NAME>.pdb
file into image and instruct container to create PDB with matching name upon startup by settingORACLE_DATABASE
property.Currently an empty PDB will be created using
pdbseed
which then needs to be dropped and re-imported from<PDB_NAME>.pdb
file in a user-script(s). This leads to a short time period in which empty PDB created frompdbseed
can be observed by outside world as available to outside world until user-script(s) replace it with a correct one, in particular this affects container's healthcheck.