Remove HS as a CONNECT_DATA parameter and add it as a DESCRIPTION par…

[gheinze]

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:

net_service_name= 
 (DESCRIPTION=
   (ADDRESS_LIST=
     (ADDRESS=...)
     (ADDRESS=...))
   (CONNECT_DATA=
    (SID=sales6)
    )
(HS=ok))

while this example from the 11g doc is incorrect:

net_service_name= 
 (DESCRIPTION=
   (ADDRESS=...)
   (ADDRESS=...)
   (CONNECT_DATA=
    (SID=sales6)
    (HS=ok)))

[pagrf]

I concur. I noticed this myself a few months ago, but I was too lazy to file a pull request. Phillip Griffith From: Glenn ***@***.***> Sent: Sunday, July 25, 2021 4:54 PM To: NormanDunbar/Tnsnames_checker ***@***.***> Cc: Subscribed ***@***.***> Subject: [EXTERNAL] [NormanDunbar/Tnsnames_checker] Remove HS as a CONNECT_DATA parameter and add it as a DESCRIPTION par… (#3) 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<https://docs.oracle.com/en/database/oracle/oracle-database/12.2/netrf/database-net-services-reference.pdf> and section 6.9.4 of the 19c document<https://docs.oracle.com/en/database/oracle/oracle-database/19/netrf/database-net-services-reference.pdf> 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: net_service_name= (DESCRIPTION= (ADDRESS_LIST= (ADDRESS=...) (ADDRESS=...)) (CONNECT_DATA= (SID=sales6) ) (HS=ok)) while this example from the 11g doc<https://docs.oracle.com/cd/E11882_01/network.112/e10835/tnsnames.htm#NETRF283> is incorrect: net_service_name= (DESCRIPTION= (ADDRESS=...) (ADDRESS=...) (CONNECT_DATA= (SID=sales6) (HS=ok)))

…

________________________________ You can view, comment on, or merge this pull request online at: #3 Commit Summary * Remove HS as a CONNECT_DATA parameter and add it as a DESCRIPTION parameter instead as per 12c and 19c doc examples File Changes * M tnsnames.test.ora<https://github.com/NormanDunbar/Tnsnames_checker/pull/3/files#diff-79ae9dee1d5d3158caa7179361e0c406b4bea0bc7c59cb16c83251383cfb63f3> (4) * M tnsnamesInterfaceListener.java<https://github.com/NormanDunbar/Tnsnames_checker/pull/3/files#diff-07806d929c05466e28c910c935e1e7fecc931c0744d64da50065ac8d40a0bd97> (28) * M tnsnamesParser.g4<https://github.com/NormanDunbar/Tnsnames_checker/pull/3/files#diff-84f116ff859de811127e40f720c15097ea0e40d987251fc4548096b2c129bfd1> (6) Patch Links: * https://github.com/NormanDunbar/Tnsnames_checker/pull/3.patch * https://github.com/NormanDunbar/Tnsnames_checker/pull/3.diff — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#3>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AINWFJVHEAD74DWPJ2XJFP3TZR2UZANCNFSM5A64OT7A>.