Forum OpenACS Q&A: Oracle 10g/Fedora Core 3
Will ACS work with Oracle 10g on a Fedora Core 3 installation?
If you do find any bugs, feel free to commit fixes or patches via the bug-tracker.
Anyone who has already succeeded, feel free to jump in and tell us all about it.
MODLIBS = -L$(ORACLE_HOME)/lib -lclntsh -lcore9 -lcommon9 -lgeneric9 -lclient9
MODLIBS = -L$(ORACLE_HOME)/lib -lclntsh -lcore10 -lcommon10 -lgeneric10 -lclient10
and that was it. (If you are not using the source code to compile aolserver, you must need to change the NSHOME var too, and assign the right path to it)
I hope this helps.
-lcore10 -lcommon10 -lgeneric10 -lclient10
or other variants during linking. Have anyone experienced the same problem?
I don't now what "oracle-xe" is exactly, is that some 3rd party Debian or Ubuntu package for Oracle Express Edition? Do you know for a fact that it is supposed to provide the same libraries that you get with the normal Oracle 10g server?
I'm facing the same problem.
I found out that libs are missing from Oracle XE.
Did you find a workaround (other than installing regular Oracle 1O.2, compile and de-install?).
Would you share your binary driver for 10.2?
Since nsoracle 2.7 works fine when compiled with the changes to the make file mentioned by Jose Pablo, I'd recommend you just use it ...
Unfortunately, nsoracle won't load at startup (from the logs):
[14/Apr/2005:02:06:05][2992.3086952672][-main-] Warning: modload: could not find Ns_ModuleInit in /software/stow/ao
[14/Apr/2005:02:06:05][2992.3086952672][-main-] Fatal: modload: failed to load module '/software/stow/aolserver/bin
Any idea how we should proceed?
Connie-Lynne (I work with Cynthia; this is the same installation she references above)
[root@holden nsoracle-2.7]# make
gcc -pipe -I/u01/app/oracle/product/10.1.0/Db_1/rdbms/demo -I/u01/app/oracle/product/10.1.0/Db_1/rdbms/public -I/u01/app/oracle/product/10.1.0/Db_1/network/public -I/u01/app/oracle/product/10.1.0/Db_1/plsql/public -O -D__NO_STRING_INLINES -D__NO_MATH_INLINES -Wall -Wno-implicit-int -fPIC -I/software/stow/aolserver-4.0.10/include -I/software/stow/tcl-8.4.6/include -DNO_CONST -DHAVE_UNISTD_H=1 -DHAVE_LIMITS_H=1 -DTCL_THREADS=1 -DUSE_THREAD_ALLOC=1 -D_REENTRANT=1 -D_THREAD_SAFE=1 -DHAVE_PTHREAD_ATTR_SETSTACK\
SIZE=1 -DHAVE_PTHREAD_ATFORK=1 -DHAVE_READDIR_R=1 -D_LARGEFILE64_SOURCE=1 -DTCL_WIDE_INT_TYPE=long\ long -DHAVE_STRUCT_STAT64=1 -DHAVE_TYPE_OFF64_T=1 -DHAVE_GETCWD=1 -DHAVE_OPENDIR=1 -DHAVE_STRSTR=1 -DHAVE_STRTOL=1 -DHAVE_STRTOLL=1 -DHAVE_STRTOULL=1 -DHAVE_TMPNAM=1 -DHAVE_WAITPID=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_PARAM_H=1 -DUSE_TERMIOS=1 -DHAVE_SYS_TIME_H=1 -DTIME_WITH_SYS_TIME=1 -DHAVE_TM_ZONE=1 -DHAVE_GMTIME_R=1 -DHAVE_LOCALTIME_R=1 -DHAVE_TM_GMTOFF=1 -DHAVE_TIMEZONE_VAR=1 -DHAVE_ST_BLKSIZE=1 -DSTDC_HEADERS=1 -DHAVE_SIGNED_CHAR=1 -DHAVE_LANGINFO=1 -DPEEK_XCLOSEIM=1 -DHAVE_SYS_IOCTL_H=1 -DTCL_CFG_OPTIMIZED=1 -DTCL_CFG_DEBUG=1 -DHAVE_INTTYPES_H=1 -DHAVE_TIMEGM=1 -DHAVE_POLL=1 -DHAVE_DRAND48=1 -DHAVE_RANDOM=1 -DHAVE_CMMSG=1 -DHAVE_GETADDRINFO=1 -DHAVE_GETNAMEINFO=1 -DHAVE_ZLIB_H=1 -DHAVE_LIBZ=1 -c -o nsoracle.o nsoracle.c
nsoracle.c:272: warning: conflicting types for built-in function 'log'
nsoracle.c: In function `Ns_DbDriverInit':
nsoracle.c:897: warning: passing arg 3 of `log' discards qualifiers from pointer target type
nsoracle.c:901: warning: passing arg 3 of `oci_error_p' discards qualifiers from pointer target type
nsoracle.c:907: warning: passing arg 3 of `error' discards qualifiers from pointer target type
nsoracle.c:918: warning: passing arg 3 of `log' discards qualifiers from pointer target type
...and so on with warnings about arg 3 of log for what appears to be most functions in the module.
We've tried the following options to get nsoracle 2.7 to compile and build properly:
NSHOME set to /install/src/aolserver-4.0.10 (our source directory)
NSHOME set to /software/stow/aolserver-4.0.10 (our build directory)
Neither of these appear to make a difference in terms of the number of warnings we get when building nsoracle. I've also set AOLSERVER to both those values, and tried all four combos of those values, and we still get the warnings. Just for kicks, I also set the following environment variables:
Again, we still got the "type mismatch" error message on build, and the fatal error message about nsoracle being unable to load (because it can't locate Ns_ModuleInit) when starting AOLServer.
Any idea what we can do? Jose, you said you got it running, could you give us some more details? We're on RHEL 4.0, for the record.
I'm sorry I can't help you more. Ypu could try searching for RHEL specific documentation (http://www.puschitz.com/InstallingOracle10g.shtml maybe?).
Good luck! =)
I have AOLServer up and running, without trying to load the oracle driver.
I compiled the oracle driver OK.
I duly note the warnings on the config.tcl file and I think I have it right.
So why am I getting "could not find Ns_ModeInit" error when I brave out into the oracle driver world world?
I posted a few bug fixes to the OpenACS installation on HEAD, but I wasn't getting the error message you were so perhaps this is irrelevant to you.
What do I put (in the .tcl config file) as the Datasource for Oracle? Localhost/localdomain?
ps Nick and Steve say hi to C. Kiser.
If AOLserver and the Oracle RDBMS are on the same box, you can just set ns_param DataSource to empty string, which will use the Bequeath connection method.
If they are on different boxes, you must make sure that the Oracle listener is configured properly, and then set ns_param DataSource to the proper SID, "ora10" or whatever else you named it.
By the way, may I ask an Oracle question?
I keep getting "The Network Adaptor could not establish the connection" error when I try to access Oracle Enterprise Manager (from a remote machine). What are the proper settings for the tsanames and listener files?