Corresponding with Oracle Support, we were missing a vital patch, which was not documented, and our SLES10 configuration is missing some RPMs. Once I can convince my SA that he must install the missing RPMs, I think we'll be on our way. Sandy On Mon, Mar 3, 2008 at 6:00 PM, Sandra Becker <sbecker6925@xxxxxxxxx> wrote: > We did remember to remove the LD_ASSUME_KERNEL so we know that wasn't the > problem. I'll look into the other suggestions first thing tomorrow. Oracle > support finally responded so I need to run some things and send them more > files. > > Sandy > > On Mon, Mar 3, 2008 at 3:53 PM, Sweetser, Joe <JSweetser@xxxxxxxx> > wrote: > > > A few possibilities: > > > > http://www.orafaq.com/forum/t/68299/0/ (permissions/account setup > > problem) > > > > http://www.orafaq.com/forum/t/81352/0/ (LD_LIBRARY_PATH not set > > correctly) > > > > hth, > > -joe > > > > ------------------------------ > > *From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto: > > oracle-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *Sandra Becker > > *Sent:* Monday, March 03, 2008 2:22 PM > > *To:* oracle-l > > *Subject:* Failed to link libclntsh.so.10.1 > > > > Environment: IBM Series z, SLES10, 64-bit 10.2.0.2 and 10.2.0.3, > > platform 209, s390x > > > > We are trying to install 10gR2 on an IBM Series Z. The instructions > > failed to mention that we need to install 10.2.0.2 and then the > > 10.2.0.3patchset. Having done the > > 10.2.0.2 install, we are attempting to install the patchset and are > > receiving the following errors: > > > > >>> > > > > INFO: Start output from spawned process: > > > > INFO: ---------------------------------- > > > > INFO: > > > > INFO: rm -f ldapadd ldapbind ldapcompare ldapdelete ldapmodify > > ldapsearch ldapmoddn ldapaddmt ldapmodifymt dsml2ldif > > > > INFO: Building client shared library libclntsh.so ... > > > > INFO: Call script /u01/app/oracle/product/10.2.0/idev/bin/genclntsh ... > > > > INFO: /u01/app/oracle/product/10.2.0/idev/bin/genclntsh > > > > INFO: > > /usr/lib64/gcc/s390x-suse-linux/4.1.2/../../../../s390x-suse-linux/bin/ld: > > skipping incompatible /u01/app/oracle/product/10.2.0/idev/lib/stubs/libdl.so > > when searching for -ldl > > > > /usr/lib64/gcc/s390x-suse-linux/4.1.2/../../../../s390x-suse-linux/bin/ld: > > skipping incompatible /u01/app/oracle/product/10.2.0/idev/lib/stubs/libm.so > > > > when searching for -lm > > > > /usr/lib64/gcc/s390x-suse-linux/4.1.2/../../../../s390x-suse-linux/bin/ld: > > skipping incompatible > > /u01/app/oracle/product/10.2.0/idev/lib/stubs/libnsl.so when sear > > > > INFO: ching for -lnsl > > > > /usr/lib64/gcc/s390x-suse-linux/4.1.2/../../../../s390x-suse-linux/bin/ld: > > skipping incompatible /u01/app/oracle/product/10.2.0/idev/lib/stubs/librt.so > > when searching for -lrt > > > > INFO: > > /usr/lib64/gcc/s390x-suse-linux/4.1.2/../../../../s390x-suse-linux/bin/ld: > > cannot find /usr/lib/libpthread_nonshared.a > > > > collect2: ld returned 1 exit status > > > > INFO: > > /usr/lib64/gcc/s390x-suse-linux/4.1.2/../../../../s390x-suse-linux/bin/ld: > > skipping incompatible /u01/app/oracle/product/10.2.0/idev/lib/stubs/libdl.so > > when searching for -ldl > > > > /usr/lib64/gcc/s390x-suse-linux/4.1.2/../../../../s390x-suse-linux/bin/ld: > > skipping incompatible /u01/app/oracle/product/10.2.0/idev/lib/stubs/libdl.so > > when searching for -ldl > > > > /usr/lib64/gcc/s390x-suse-linux/4.1.2/../../../../s390x-suse-linux/bin/ld: > > skipping incompatible /u01/app/oracle/product/10.2.0/idev/lib/stubs/libm.so > > > > when sear > > > > INFO: ching for -lm > > > > /usr/lib64/gcc/s390x-suse-linux/4.1.2/../../../../s390x-suse-linux/bin/ld: > > skipping incompatible > > /u01/app/oracle/product/10.2.0/idev/lib/stubs/libnsl.so when searching for > > -lnsl > > > > /usr/lib64/gcc/s390x-suse-linux/4.1.2/../../../../s390x-suse-linux/bin/ld: > > skipping incompatible /u01/app/oracle/product/10.2.0/idev/lib/stubs/librt.so > > when searching for -lrt > > > > INFO: End output from spawned process. > > > > <<< > > > > We haven't been able to find any answers on Metalink and are still > > waiting for Oracle support to get back to us. This was the only link that > > failed. We have more than enough memory, disk, etc. Does anyone have any > > ideas or suggestions? Thanks in advance. > > > > Sandy > > > >