OK, we have version 6.5.1 running on AIX 5.2 in our development environment and I am trying to apply the patch for 6.5.2…
BO has released 6.5.2 for AIX as a patch to apply on top of 6.5.1.
There is a shell script named setup.sh in the install directory and one of the things it tries to launch when you run it is a compiled program in the same directory named cpsetup.
On running the shellscript (or the compiled program directly) I get the following message:
The named library file is located in /bi/bo/lib/libcplib.so
(/bi/bo is the root of our BO installation directory).
Our hardware is an RS6000 H50 and except for the ssa adapters supports 64 bit operations, but we are presently running our kernel in 32 bit mode.
I have already tried modifying the LIBPATH and PATH variables to include the directory that contains the named library file yet I get the same error message every time. Google has never heard of this error.
The BO PAR document says that 6.5.2 will run on AIX version 5.1, 5.2, and 5.3.
Has anyone gotten 6.5.2 up on AIX 5.2 yet?
Has anyone ever seen and resolved this error before?
Our dev repository is Oracle 10g with 9i middleware - running on the same server.
This is probably more of an AIX problem than a BO problem, but I’ll still sytmied.
I finally copied that library file into the directory and re-ran setup.sh. It went past that, but halted when it could not find some other library file.
I copied it (and a couple of others it was asking for locally) and kept getting other errors.
In frustration I copied ALL of the library files locally and got through all of the other issues.
The seem to expect to find an environemnt variable named WI that is set to the path of the base install. In our case:
export WI=/bi/bo
Running it at that point then gives you a help screen telling you how to run it. The command line I am trying now is.
Ran into the same error but could fix it by running the two scripts that wstart calls to set the environment variables:-
/setup/WebiEnv.sh
/nodes///MyWebiEnv.sh
…and then running setup.sh -i -a -v -t mysp2log
seems that the wstop script clears out thes env variables.
Ran into the same error but could fix it by running the two scripts that wstart calls to set the environment variables:-
/setup/WebiEnv.sh
/nodes///MyWebiEnv.sh
…and then running setup.sh -i -a -v -t mysp2log
seems that the wstop script clears out thes env variables.
(BOB member since 2003-08-19)
(BOB member since 2003-08-19)