%META:TOPICPARENT{name="ErrorMessagesF"}%
==Error Messages (F)==

[[UDAErrorMessages|A]] [[ErrorMessagesB|B]] [[ErrorMessagesC|C]] [[ErrorMessagesD|D]] [[ErrorMessagesE|E]] [[ErrorMessagesF|F]] [[ErrorMessagesG|G]] [[ErrorMessagesH|H]] [[ErrorMessagesI|I]] [[ErrorMessagesJ|J]] [[ErrorMessagesK|K]] [[ErrorMessagesL|L]] [[ErrorMessagesM|M]] [[ErrorMessagesN|N]] [[ErrorMessagesO|O]] [[ErrorMessagesP|P]] [[ErrorMessagesQ|Q]] [[ErrorMessagesR|R]] [[ErrorMessagesS|S]] [[ErrorMessagesT|T]] [[ErrorMessagesU|U]] [[ErrorMessagesV|V]] [[ErrorMessagesW|W]] [[ErrorMessagesX|X]] [[ErrorMessagesY|Y]] [[ErrorMessagesZ|Z]] [[ErrorMessagesSymbols|#]]

    
===file .../db2.o not found===


The db2.o file is not always immediately available on AIX installations, which can cause <nop>OpenLink's drivers for DB2 to fail.
    
If this file is not found at $DB2DIR/lib/db2.o, take the following steps --
    
       
* Log in as the root user
    
       
* Execute the command
    
    

find / -name libdb2.a -print | xargs ls -l
            

     
* You should see that one of the results of Step #2 is a file, located in $DB2DIR/lib/, while any others should be symlinks to this same file. Move to $DB2DIR/lib/. For example,
    
    
{{{
    
cd /usr/lpp/db2_07_01/lib/
            
}}}
     
* Ensure there is no existing shr.o, which may interfere with the current extraction attempt. If there is, execute the command
    
    
{{{
    
mv shr.o shr.o.bak
            
}}}
     
* Execute the command
    
    
{{{
    
ar x libdb2.a
            
}}}
     
* When you get a new file-listing, you should find the new fileshr.o

{{{
    
ls -l
            
}}}
     
* Execute the commands
    
    
{{{
    
mv shr.o db2.o
chmod 755 db2.o
            
}}}
     
* If you moved an existing shr.o to shr.o.bak, restore it with the command -
    
{{{
    
mv shr.o.bak shr.o
            
}}}
  

All binaries which depend on this dynamically loadable library should now work properly. Retest your <nop>OpenLink components.