If worst comes to worst, move the Oracle stuff back to /Application Support and reset your alias to the new location (just to be on the safe side)
I agree with you, I cannot figure out WHY Apple decided to use a critical directory with a space in its name...
On Nov 25, 2003, at 9:04 AM, Jon van der Raadt wrote:
The Oracle directory location is now /Library/Oracle (Seems cleaner with no space in the path) but the Oracle connection appears to be broken in the new version of OSX (10.3.1) and Witango Server 5.0.65. I had this running but it no longer works. I do not know which app is the culprit. I can no longer connect to OCI datasources from the Editor and an attempted connection to the application server using an OCI connection crashes the server. I have reported this to Phil
My jdbc connections and my odbc connections seem to be ok (after re-creating a symbolic link to the odbc.ini from the .odbc.ini in my home directory) however I have not attempted either type of connection to our Oracle8i databases.
Jon On Nov 25, 2003, at 6:44 AM, Dale Graham wrote:
There are several components to doing this.
1] Most of this is covered in a PDF file posted to Witango's website. Get that.
<http://www2.witango.com/downloads/iODBC_unixODBC_OracleOCI.pdf>
2] Be sure that you also set up the following on BOTH your development and server...
the environment.plist file, inside a .MacOSX directory at the root of the user directory that's appropriate in each case.
Also, you can use the same tnsnames.ora file that you were using before...
Basically what you need to make this work is
1] Oracle driver(s) - I run both OCI and JDBC - both are located in /Library/Application Support/Oracle
2] Framework info - located in /Library/Frameworks/OracleOCI
this requires setting up a Unix (not regular Mac) alias. Follow the directions in the PDF file (this may only be required if you're using OCI, I'm not sure whether it is needed for JDBC)
3] environment.plist doc, correctly configured
If you don't have all three it won't work, and they have to be present on both development and server machines.
On Nov 21, 2003, at 5:42 PM, MJPinckard wrote:
I'm attempting to migrate my site from Tango 3.5.2 (isn't that scary) to Witango 5.
At this point, I'm trying to get the Dev. Studio to connect to my Oracle datasource, but am stuck. There was a discussion back in May about this problem, but I didn't see a resolution posted. I'd quote the discussion, but the archive isn't responding right now. By following all the recommendations in the discussions, I've managed to get the Dev. Studio (5.0.9) to know that Oracle exists, but can't open the datasource, it asks for username and password, but is unable to connect "verify that the datasource is properly configured and the database server is on-line". Obviously something is still wrong, but I don't know what to do.
My plan had been to use Oracle OCI to connect, but frankly I don't care how it connects, I just want it to connect. If anyone has a set of instructions (including directions on where to get any needed drivers) on how to connect to Oracle in any way (OCI, ODBC, JDBC) I really appreciate the help.
My new OS X server is due in any day, so I'd like to get this resolved.
Thanks,
Maggie
-- * * * * * * * * * * * * * * * * * * * * * Margaret Pinckard * [EMAIL PROTECTED] * Principal Research Associate * End-use Forecasting Group * E.O. Lawrence Berkeley National Laboratory
_____________________________________________________________________ ___
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
______________________________________________________________________ __
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
_______________________________________________________________________ _
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
