merlinux commented on issue #62526:
URL: https://github.com/apache/airflow/issues/62526#issuecomment-4032733149

   Hi all. I´ve manually applied the proposed commit to my running dev host and 
sadly I observing 
   the issue persists, while using Extra Fields, 
   {  "thick_mode": "TRUE",  "thick_mode_lib_dir": 
"/airflow/instantclient_23_26/" }
   
   the only working conf, once proposed commit was applied, is
   
   <img width="894" height="719" alt="Image" 
src="https://github.com/user-attachments/assets/99d3d3b3-e322-483d-827a-73847454ef2f";
 />
   
   Following this docs 
https://airflow.apache.org/docs/apache-airflow-providers-oracle/stable/connections/oracle.html
 seems to be a confusion with the Host parameter here:
   
   Host = 
"(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=dbhost.example.com)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=orclpdb1)))"
   
   IMHO it should be named DSN, avoiding confusion with 
   
   Host = "dbhost.example.com"
   
   Which of course aren´t and couldn´t refer to the same value
   
   Same relative to SERVICE_NAME=orclpdb1 and  Schema = "orclpdb1".
   Schema is referred to a user, and multiples schemas can be loaded in a 
single  SERVICE_NAME
   i.e.: user1@orclpdb1 , user2@orclpdb1  , etc.
   
   So, IMHO Schema should be called DSN at the UI, meaning the entry at 
tnsnames.ora which will be used by thick client, whith the user and password 
provided. 
   
   Please have in mind that using tnsnames.ora DSN and SERVICE_NAME (aka SID) 
shoul be
   totally different strings, ie:
   DSN  <should be a unique name>  =
   (DESCRIPTION=(ADDRESS=(PROTOCOL=protocol) (HOST=dbhost.example.com) 
(PORT=port))
   (CONNECT_DATA =(SERVICE_NAME = orclpdb1 )))
   
   Sorry the philosophic stuff, the aim of the post is report the issue 
persists the issue persists.
   Glad to help if it is the case. 
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to