oraswdb-install: added autostart support to multiple listeners for database in filesystems #137
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
…ilesystem The stupid dbstart and dbstop has been replaced by a completly new designed script manage_oracle_rdbms_procs.sh. The script is placed in /usr/local/bin and must be executed as the owner of the Oracle software. Instances are started when the state in oratab is 'Y' or 'M' for only 'startup mount' which is important in data-guards to protect against accidently using the active data-guard option. All listeners are started when 'listener_name' is defined in oracle_databases for the instance. The script has some parameter: manage_oracle_rdbms_procs.sh -a <start|stop> -m <abort|immediate> The default is shutdown immediate This can be changed with the parameter '-m abort'.
Fixed wrong execution of include from testing.
This was referenced Nov 17, 2018
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 stupid dbstart and dbstop has been replaced by a completly new designed script manage_oracle_rdbms_procs.sh.
The script is placed in /usr/local/bin and must be executed as the owner of the Oracle software. Instances are started when the state in oratab is 'Y' or 'M' for only 'startup mount' which is important in data-guards to protect against accidently using the active data-guard option.
All listeners are started when 'listener_name' is defined in oracle_databases for the instance.