Remove HS as a CONNECT_DATA parameter and add it as a DESCRIPTION par… #3
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.
Thank-you for publishing this grammar. In case it may be of interest to others, this is a modification I made in order to successfully parse my own tnsnames.
The HS parameter (Heterogeneous Services) was configured as part of the CONNECT_DATA clause as described in the 11g documentation. However, it seems the 11g documentation is incorrect.
Section 6.9.4 of the 12c documentation and section 6.9.4 of the 19c document both list the HS parameter under the CONNECT_DATA section, however, the examples demonstrate HS being used as part of the DESCRIPTION. All implementation examples I have found and our own usage has the HS parameter as part of the DESCRIPTION. The response from Oracle support regarding the discrepancy between the documentation text and the documentation example was that we should follow the example.
i.e. this example from the 19c doc is supposed to be correct:
while this example from the 11g doc is incorrect: