Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NNE support for thin client #1670

Open
brian-mendicino opened this issue May 8, 2024 · 6 comments
Open

NNE support for thin client #1670

brian-mendicino opened this issue May 8, 2024 · 6 comments

Comments

@brian-mendicino
Copy link

brian-mendicino commented May 8, 2024

  1. Describe your new request in detail

Is NNE support for the thin client coming in a later version of the node-oracledb lib? This will guide decisions on how to proceed if this support is being considered in the future as it is already in the python-oracledb.

  1. Give supporting information about tools and operating systems. Give relevant product version numbers
  • Oracle Instance client (thick client) versions >= v21 are too large to deploy on a lambda layer or to a lambda without making decisions around using containers. Where with version 19 the size was much smaller.
  • Upgrading the Lambda runtime to node 20, changes to Amazon Linux 2023 server and none of the thick clients work due to missing libnsl.so and libaio.so files.
@cjbj
Copy link
Member

cjbj commented May 8, 2024

@brian-mendicino NNE support is not in Thin mode node-oracledb nor Thin mode python-oracledb. It is available in Thick mode in both drivers.

As developers we would like to add support to Thin mode in both drivers, however there are some management decisions that are preventing this. If you (and any other reader affected) can email me (see my profile) your company names, I will add them to the internal business case we are renewing. This will help us make a good argument about adding support.

One potential path forward is for the NNE code to be distributed as a binary, presumably similar to the thick mode binary (but without needing Instant Client). What impact would this have on your deployment pipeline?

@sosoba
Copy link

sosoba commented May 9, 2024

@sharadraju
With reference to #1574. Is something known about dual NNE and TSL support in database lower than 23?

@sharadraju
Copy link
Member

@sharadraju With reference to #1574. Is something known about dual NNE and TSL support in database lower than 23?

@sosoba Will check internally on the backport of the fix mentioned in #1574 . Now that Oracle Database 23ai is officially out, I will push for the backport, if it is not done already,

@sharadraju
Copy link
Member

sharadraju commented May 9, 2024

@sosoba The word I received is that the fix mentioned in #1574 has been backported to latest Oracle Database 19c patch release.

@brian-mendicino
Copy link
Author

@cjbj Thank you for the information. We are discussing options will send an email directly if we need to escalate this.

Also, we did find a strange combination of binaries to get the oracle instant client version 21 to work on Amazon Linux 2023 (Nodejs 20 lambda server), however I have not found a solution for version 23. Ill include the combination here to close the loop.

libociicus.so           
libclntsh.so.21.1       
libclntshcore.so.21.1   
libnnz21.so             
libaio.so.1 

@sosoba
Copy link

sosoba commented Jul 22, 2024

@sosoba The word I received is that the fix mentioned in #1574 has been backported to latest Oracle Database 19c patch release.

I confirm. Patch 35639791: SQLNET.IGNORE_ANO_ENCRYPTION_FOR_TCPS DOES NOT IGNORE DATA INTEGRITY resolves the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants