This blog post will discuss how to deal with adrelink failures when applying patches in EBS tech_st home. Sometimes, when you apply OPatch to EBS $ORACLE_HOME in cloned instances, the patch may try to relink some objects as part of the patching process. However, this can cause library errors that prevent the patch from completing successfully.
Sample Error message:
/usr/bin/ld: cannot find $ORACLE_HOME/lib/stubs/libc.so.6
/usr/bin/ld: cannot find /usr/lib/libc_nonshared.a
collect2: error: ld returned 1 exit status
Cause:
The problem is that the file $ORACLE_HOME/lib/stubs/libc.so contains the hardcoded entry of the old ORACLE_HOME path.
GROUP ( Old ORACLE_HOME >/lib/stubs/libc.so.6 /usr/lib/libc_nonshared.a )
Solutions:
To prevent errors, DBA should relink the library files after cloning the application. This is because the adcfgclone or autoconfig script does not do this automatically when copying the library files from source to target environment.
- adrelink.sh force=y “ad all”
- Relink the binaries for all modules using adadmin.
- Update lib file contents from Old ORACLE_HOME to New ORACLE_HOME.
