cancel
Showing results for 
Search instead for 
Did you mean: 

Error During Relink

Former Member
0 Kudos

Hello,

We performed an AIX upgrade from 5.3 to 6.1 TL4 on our non prod server and when we try to perform a Relink of Oracle 10.2.0.2 we get an error for the oemagent portion. Log snippet below:

 
        /bin/make -f /oracle/ID1/102_64/sysman/lib/ins_sysman.mk emtgtctl2 LIBDIR=lib32
Target "emtgtctl2" is up to date.
        rm -f /oracle/ID1/102_64/bin/emtgtctl2
        mv emtgtctl2 /oracle/ID1/102_64/bin/emtgtctl2
        /bin/chmod 6751 /oracle/ID1/102_64/bin/emtgtctl2
chmod: /oracle/ID1/102_64/bin/emtgtctl2: No such file or directory
make: The error code from the last command is 1.

What's odd is that the Qa instance on the same server did not have the same issue, only the Dev instance has this issue. The DB starts up fine.

Has anyone had this issue before? Or have any suggestions?

Thanks!

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Prabu,

I had something like this once (prod linked fine but test did not)and it was because the environment variables for our test users were not the same as the environment variables for the production user (LD_LIBRARY_PATH path etc)

(run command set or env to see them from a shell and just compare)

Good luck,

Chris

Here are some Oracle notes that may help

Note:131207.1 How to Set UNIX Environment Variables

Note:109621.1 HP/UX: LD_LIBRARY_PATH and SHLIB_PATH

Note:1032747.6 HOW TO RELINK ORACLE USING THE 7.3.X INSTALLER

Bug:1337908 THE $ORACLE_HOME/BIN/RELINK SCRIPT DOES NOT RELINK EXP, IMP SQLLOADER

Former Member
0 Kudos

sorry.....

I see the make is set for 32 bit libs LIBDIR=lib32 but looking in 10qR2 64 bit dirs

also check 32 vs 64 bit (bootinfo -y in aix) is the same

an AIX migration install (upgrade) should not change this but a fresh/install mksysb/NIM from another image may

Edited by: Chris Rutherford on Oct 13, 2011 4:19 AM

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

Check the file system attributes. Binary files shouldn't be located at the file system with "cio" attribute.

Best regards,

Orkun Gedik

Former Member
0 Kudos

Thanks Chris and Orkun.

It ended up being something else entirely - the mv file step was not running right, and we were able to relink after fixing that.