You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm hoping you all can help me out. I'm just trying to connect to an oracle db on a mac pro running Lion. I've installed the 64bit instantclient (10.2.0.4.0) and gotten db-oracle installed successfully. When I try to connect, nothing happens. The callback never fires, no events get emitted, and my sadness is total. I DO get a warning (and the port is not standard, as you can see):
I tried running sqlplus with the instantclient to check that I could connect to the db. it seg faults. That's apparently a known issue with the 64bit client and they who wish to overcome use the 32bit client. So I installed the 32bit client, and reinstalled db-oracle. I'm able to connect to the db with sqlplus with no problems, but even just requiring db-oracle fails:
I have given up on using Node+Oracle on OSX, just switched to a Linux VM (running on OSX).
There is a 32Bit version of Node, but I do not know if that just opens another can of worms ...
Good morning,
I'm hoping you all can help me out. I'm just trying to connect to an oracle db on a mac pro running Lion. I've installed the 64bit instantclient (10.2.0.4.0) and gotten db-oracle installed successfully. When I try to connect, nothing happens. The callback never fires, no events get emitted, and my sadness is total. I DO get a warning (and the port is not standard, as you can see):
I tried running sqlplus with the instantclient to check that I could connect to the db. it seg faults. That's apparently a known issue with the 64bit client and they who wish to overcome use the 32bit client. So I installed the 32bit client, and reinstalled db-oracle. I'm able to connect to the db with sqlplus with no problems, but even just requiring db-oracle fails:
I don't really care if I'm using the 32bit or the 64, as long as it works. Suggestions?
The text was updated successfully, but these errors were encountered: