Has anyone experienced problems when using the ar_install script to perform an install on solaris with 7.0.1 patch 3 where the executable arserverd is unable to dynamically link to the oracle client?
The installer got pretty far along before this became an issue, meaning that most of the installer was able to link against the library: The new user was issued a fixed license of the following type Write : (1 of 14) (ARNOTE 31) Start of Import: Mon Aug 6 10:12:37 EDT 2007 Waiting for the AR System Server to respond... Setting the DSO User Password Setting the Application Password Setting the MidTier Password Restarting the AR System Server: Mon Aug 6 10:12:53 EDT 2007 Action Request System beginning the restart process. Action Request System shutdown in progress. Action Request System shutdown process complete. Action Request System initializing. Starting AR System Server (ARNOTE 0) AR Monitor version 7.0.01 patch 003 200705212328 started. (ARNOTE 0) AR Monitor started. (ARNOTE 0) ARMonitor child process (pid:24538) started. ./arserverd ld.so.1: arserverd: fatal: libclntsh.so.10.1: open failed: No such file or directory The installer created all the Remedy data dictionary forms just fine, started arserverd once, created the Demo account and issued a fixed license, but during the restart, it failed. Somewhere along the way the ar_install script lost track of the LD_LIBRARY_PATH set before running ar_install. Thanks, Axton Grams _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
