Frightening number of linking errors for on AIX 5.3 TL11

I just applied PSU 3 for on AIX 5.3 TL11. That would have been more straight forward, had  there not been a host of errors when relinking oracle. There were loads of these:

SEVERE:OPatch invoked as follows: 'apply '
Oracle Home       : /u01/app/oracle/product/
Central Inventory : /u01/app/oracle/product/oraInventory
 from           : /etc/oraInst.loc
OPatch version    :
OUI version       :
OUI location      : /u01/app/oracle/product/
Log file location : /u01/app/oracle/product/
[more output]
INFO:Running make for target ioracle
INFO:Start invoking 'make' at Mon Nov 01 09:29:26 GMT 2010Mon Nov 01 09:29:26 GMT 2010
INFO:Finish invoking 'make' at Mon Nov 01 09:29:40 GMT 2010
OPatch found the word "error" in the stderr of the make command.
Please look at this stderr. You can re-run this make command.
Stderr output:
ld: 0711-415 WARNING: Symbol ldxdts is already exported.
ld: 0711-415 WARNING: Symbol ldxsto is already exported.
ld: 0711-415 WARNING: Symbol lnxadd is already exported.
ld: 0711-319 WARNING: Exported symbol not defined: cout__3std
ld: 0711-224 WARNING: Duplicate symbol: .kotgscid
ld: 0711-783 WARNING: TOC overflow. TOC size: 219488    Maximum size: 65536
 Extra instructions are being generated for each reference to a TOC
 symbol if the symbol is in the TOC overflow area.

Wow, that looked like a completely corrupted installation of Oracle now, and I got ready to roll the change back. However, MOS had an answer to this!

These errors can be ignored as per this MOS document: Relinking causes many warning on AIX [ID 1189533.1]. See also MOS note Note 245372.1 TOC overflow Warning Can Safely Be Ignored and BUG:9828407 – TOO MANY WARNING MESSAGES WHEN INSTALLING ORACLE 11.2 for more information.


6 thoughts on “Frightening number of linking errors for on AIX 5.3 TL11

  1. Niall Litchfield


    You may find that issuing

    export LDFLAGS=”-Wl,-bbigtoc”

    before the opatch command will suppress the TOC warning (actually get around it). The others are dumb, but self explanatory, warnings in my view.

    1. Martin Post author

      Hi Niall,

      totally agree, and after checking MOS and using my favourite search engine I came to the same conclusion. Still was a bit worried after looking at all those lines of output …


      1. Niall Litchfield

        Don’t get me wrong – my favourite number of link warnings is zero – anything else is a bug IMO, I don’t like the various “you can safely ignore these invalid objects if…” notes on MOS for various upgrade sql scripts for the same reason. I’m not necessarily convinced that a familiarity with ld is a pre-requisite for a DBA job :).

  2. Leighton

    Hi Martin,
    We found similar warning messages while applying PSU2 to GI and DB homes. I must agree that it is rather unsettling to see so many messages. Fortunately these seem to be benign but uncomfortable non the less.

    Great blog by the way :)


  3. Julian Dyke

    This is still a problem in with PSU9.

    I hate this – I think it is really sloppy porting by Oracle. AIX is still a big platform for the Oracle database, so surely IBM and Oracle can get together and eliminate these warnings. Apart from confusing their customers, there is also the danger that a genuine issue is missed within the spurious messages.

  4. Steve Gray

    And it’s still a problem in, the terminal release, with PSU1 on AIX6.1. Hey ho.

Comments are closed.