Node 20 support?

[jorool]

Hello,

How do we make this lib work with lambda with node runtime version 20?

Right now, getting this message:
DPI-1047: Cannot locate a 64-bit Oracle Client library: "libclntsh.so: cannot open shared object file: No such file or directory".See https: //node-oracledb.readthedocs.io/en/latest/user_guide/installation.html for help Node-oracledb installation instructions: https://node-oracledb.readthedocs.io/en/latest/user_guide/installation.html You must have Linux 64-bit Oracle Client libraries configured with ldconfig, or in LD_LIBRARY_PATH. If you do not have Oracle Database on this computer, then install the Instant Client Basic or Basic Light package from https://www.oracle.com/database/technologies/instant-client/linux-x86-64-downloads.html

[romanbalayan]

Hi @jorool,

Is the error from an AWS Lambda environment?

Tested locally, and should work:

START RequestId: a47b93bf-81e2-46ad-9987-61dd648cfc9d Version: $LATEST
2024-02-10T14:13:45.191Z        23cd8061-c6c3-4780-bec1-b1f47aee61df    INFO    Node Version is: v20.11.0
2024-02-10T14:13:45.223Z        23cd8061-c6c3-4780-bec1-b1f47aee61df    INFO    Oracle Version is: 60300
END RequestId: 23cd8061-c6c3-4780-bec1-b1f47aee61df
REPORT RequestId: 23cd8061-c6c3-4780-bec1-b1f47aee61df  Init Duration: 0.83 ms  Duration: 1254.10 ms    Billed Duration: 1255 ms        Memory Size: 128 MB Max Memory Used: 128 MB

[jorool]

Hey, Yes, the error happens in lambda runtime environment. I tried upgrading my lambda runtimes from node 18 to 20 and started getting that error. I did not change anything else. Maybe I missed something?

[sathiappancei]

@jorool @romanbalayan did you guys make it work in AWS Lambda environment with Node V20? I am facing exactly the same issue! All works fine with Node V18 but if I switch to Node V20 then error DPI-1047: Cannot locate a 64-bit Oracle Client library: \"libclntsh.so: cannot open shared object file.

Any input is much appreciated.

Thanks.

[rgare-jeffa]

The main issue having this work with the node20 may be because Lambda went from AWS - Linux 2 to Linux 2023. This removed some critical portions of the infrastructure required to utilize the oracle binaries and how they are built with Linux 2 (namely libaio and libnsl(?)).

[renanwilliam]

@rgare-jeffa, do you find any alternative?

[casyalex]

Any solutions, guys? it's pretty annonying

[jsirenenfuce]

Stumbled upon this as well now - has anyone figured out a solution for this?

[casyalex]

Stumbled upon this as well now - has anyone figured out a solution for this?

node-oracledb support thin-mode since 6.6.0, pure js, no extra layer needed anymore. just use latest client

[jsirenenfuce]

Stumbled upon this as well now - has anyone figured out a solution for this?

node-oracledb support thin-mode since 6.6.0, pure js, no extra layer needed anymore. just use latest client

Thanks for the reply - our oracle database does not support thin client connections (regulated by compliance) so we are unfortunately stuck with thick client..

[surendranexturn]

Hi ,

@romanbalayan @jorool @sathiappancei did we get any solution for this issue

[surendranexturn]

Stumbled upon this as well now - has anyone figured out a solution for this?

node-oracledb support thin-mode since 6.6.0, pure js, no extra layer needed anymore. just use latest client

Thanks for the reply - our oracle database does not support thin client connections (regulated by compliance) so we are unfortunately stuck with thick client..

@jsirenenfuce did you find any solution for Thick Client apps for Lambda, need help on this

[wgeiger-barrett]

With the upcoming end of support for Node 18.x in AWS Lambdas, I am wondering if there's been any movement on a new version of this project.

[wgeiger-barrett]

I want to give an update for anyone still tracking this task. I was able to successfully create an aws lambda layer that appears to work with advance queuing (requires thick client) running on the node22.x runtime. I am still working on getting any edge cases figured out (if there are any), but I am hoping this will help us keep moving in lambdas.

Steps I had to take:

1. Download latest zip from this project for core resources. (I downloaded my latest used layer for node18.x)
2. Download version 21.12.0.0.0 oracle instant client for x84_64: https://www.oracle.com/database/technologies/instant-client/linux-x86-64-downloads.html
3. Replaced the files in the original zip's lib folder to match this list:
   
4. Create a new zip of just the new lib and nodejs folder (no changes to nodejs)
5. Upload to S3 and create a new layer
6. Set newest layer in serverless configuration

I attempted to utilize the ARM64 instant client without much luck.

[wgeiger-barrett]

any file with timestamp of 6/13 and newer was copied from the instant client. The ones from 11/8 are from the original 18.x supported layer from this project. I added a TNSNames.ora to my network folder, but I am not sure if that's actually needed.

[brettvd]

any file with timestamp of 6/13 and newer was copied from the instant client. The ones from 11/8 are from the original 18.x supported layer from this project. I added a TNSNames.ora to my network folder, but I am not sure if that's actually needed.

@wgeiger-barrett I've attempted your steps, however I'm getting a TNS:Connect timeout error so I'm wondering if it might be related to this last comment. Can you give any more information on what you did with TNSNames.ora exactly?

Nevermind! This worked for me (without TNSNames.ora). My issue was related to AWS Security Policies/VPC stuff.