V2026-02-17 Fix error for instances not registered in GI#40
Merged
JanSchnacki merged 2 commits intoopitzconsulting:mainfrom Feb 18, 2026
Merged
V2026-02-17 Fix error for instances not registered in GI#40JanSchnacki merged 2 commits intoopitzconsulting:mainfrom
JanSchnacki merged 2 commits intoopitzconsulting:mainfrom
Conversation
causing GV_DB_SID_LIST entries to be empty for oratab and running processes
Rendanic
approved these changes
Feb 18, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Databases not registered in the GI were detected correctly, but the entry in GV_DB_SID_LIST was created empty due to a copy and paste error using the wrong variable name, causing scripts using this array to fail.