oradb_manage_db: customize ocenv init in bashrc #310
Merged
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The default
ocenvinitialization in.bashrcfile can cause issues, that is why it should be customizable. For example, on a newly provisioned DB server withocenvinstalled, the EM agent deployment fails (see EM 12c/13c: Agent Deployment Fails at Remote Validations step with error "Banner check failed" (Doc ID 1453099.1)). This pull request introduces two new variables to control whether.bashrcshould be changed (ocenv_bashrc_initvariable) and how (ocenv_bashrc_init_sectionvariable).