Error While Loading Shared Libraries: libdb.so.2

I was installing EBS 12.1.1 Vision for testing purposes. Unix team member installed the additional packages using Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.1.1) for Linux x86-64 [ID 761566.1]. After downloading and extracting all packages I started the installer. Everything went well till this screen:

That doesn't look good... After stopping and starting EBS by using adstpall.sh and adstrtall.sh step adapcctl.sh showed an error:
Error
--> Process (index=1,uid=1191665904,pid=28020)
    failed to start a managed process after the maximum retry limit
    Log:
    /opt/oracle/VIS/inst/apps/VIS_vm-946-157/logs/ora/10.1.3/opmn/HTTP_Server~1.log
 
And at  HTTP_Server~1.log:
/opt/oracle/VIS/apps/tech_st/10.1.3/Apache/Apache/bin/httpd: error while loading shared libraries: libdb.so.2: cannot open shared object file: No such file or directory

On metalink there is a note (879522.1) to create a symbolic link to libgdbm.so.2.0.0: ln -s /usr/lib/libgdbm.so.2.0.0 /usr/lib/libdb.so.2

But after double checking note 761566.1, at the Other Requirements section, there is small note:
Download and apply the patch 6078836 from My Oracle Support to fix an issue with the Oracle HTTP Server (missing libdb.so.2) bundled with the
E-Business Suite technology stack.
Note that this patch (which includes a required operating system library) must be applied before installing Oracle E-Business Suite.
EBS went smooth after installing this small patch. 

Oracle Applications Manager Log

In PeopleSoft I know where I can find the log files and where I can find what information. In Oracle EBS it's not always clear for me where I can find what. Today the Applications Manager Log. It's not easy to find, it's in the Site Map of OAM, there is no direct navigation from the menu. You must first select a Responsibility from OAM, for example the Dashboard.

The information logged here is useful when you are trouble shooting connection issues. See the previous post and also Johan Louwers has an example of it. There are three log levels: USER, DEV and SUPPORT. I use DEV to troubleshoot. USER has very limited information. SUPPORT is useful to support for diagnosing problems.

It's described in the System Administrator's Guide - Maintenance, but it looks like the info is not accurate anymore. From the guide:
For a persistent setting, the log level
initialization parameter must be changed in zone.properties. The
parameter is: oracle.apps.oam.logger.level
There is no zone.properties file any more in release 12. But $ORACLE_HOME/sysman/webapps/emd/WEB-INF/web.xml contains the parameter oracle.apps.oam.logger.level,  when changing it and bouncing the app. doesn't change the value, it's still USER at the Application Managers Log... Maybe I create a SR for this but for me it's not very useful to have it always on DEV, I prefer switching it to DEV when I need it.

The log files are stored at $LOG_HOME/appl/rgf/oam/