Node-oracledb: CLIENT_IDENTIFIER is not set with version 2.1.1

Created on 20 Feb 2018  路  3Comments  路  Source: oracle/node-oracledb

We are using the connection.clientId property to pass a user ID to the database. With version 1.13.1 this is working as expected. However with 2.1.1 the CLIENT_IDENTIFIER stays null.

I can reproduce the behavior with the endtoend.js example.
See the following. With 2.1.1 I get
image

With 1.13.1
image

Answer the following questions:

  1. What is your Node.js version? Is it 64-bit or 32-bit?
    v8.9.3 64bit

  2. What is your node-oracledb version?
    2.1.1 (not working)
    1.13.1 (working as expected)

  3. What is your Oracle client (e.g. Instant Client) version? Is it 64-bit or 32-bit? How was it installed? Where is it installed?
    instantclient--windows.x64-12.2.0.1.0
    C:\dev\programs\instantclient_64

  4. What is your Oracle Database version?
    Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production

  5. What is your OS and version?
    Windows 7 64bit

bug

Most helpful comment

@cjbj @anthony-tuininga Thank you very much for the quick fix! I can confirm, that it's working as expected. :+1:

All 3 comments

I have confirmed the issue and already have a solution which corrects it. @cjbj can comment on when that will become part of an official release.

@ronnn an interesting little buglet. Thanks for reporting it. It's fixed in 2.1.2, which I just pushed to npm.

@cjbj @anthony-tuininga Thank you very much for the quick fix! I can confirm, that it's working as expected. :+1:

Was this page helpful?
0 / 5 - 0 ratings

Related issues

ainthek picture ainthek  路  3Comments

nicholas-ochoa picture nicholas-ochoa  路  3Comments

xpro666 picture xpro666  路  3Comments

klaus82 picture klaus82  路  4Comments

satodu picture satodu  路  3Comments