UNIX for Dummies Questions & Answers

Ahhh... well, I know nothing about the
Informatica products but I would look for
differences in the setup and configuration
of the Informatica server between the two
machines. I would seriously doubt it has
anything to do with Solaris.
(but you never know)

Assuming that this is a magic number error, meaning that the some executable in the execution chain is not the type of binary executable image expected by Solaris 8, and given the output of the file command you ran on each machine, this is either a problem with a 32 bit executable and shared library set running on a 64 bit operating system (not likely but possible), or the shared libraries that were installed were of the wrong executable format.

If you run

truss -f pmconfig > /truss.out 2>&1

and look at the /truss.out output file, the end of the file should show some type of error, probably an error after an execve and a stat or an open call. If the file is fairly short, you could post it here for more help.

A silly question. What is the hardware architecture of the two boxes in question?

They are both Sun boxes. I do not deep things about their hardware but they are both identical.

Set your LD_LIBRARY_PATH to have the lib directory of the Informatica libraries first in the directory list. If this still doesn't work, then

does

isainfo -kv

show that both kernels are running the same kernel (i.e. both 32 bit or 64 bit)? Also, if you use the file command to look at the Informatica shared libraries

i.e. file shared_lib.so.1

Does the output of the file command on the shared libraries show the same output?

If the hardware architecture is the same, the OS is the same, the install media/image is the same and is for Solaris 8, and both kernels are running in the same mode (i.e. 32 bit or 64 bit), then I'm at a loss as to the reason.

The only way we could possibly figure this out is to get the output of

truss -f <executable_name> > /truss.out 2>&1

where <executable_name> is pmconfig or whatever executable you run to get the error. If you can post this we can see where it's failing.

Sorry I haven't been a lot of help, but this error usually signifies an executable image that was compiled/linked for a different OS/arch.