Adop Patch with nohup option (R12.2)

 

Oracle Apps adop patch with nohup option

adop_patch.sh

adop phase=prepare,apply,finalize,cutover patches=patch_no<<EOF
appspassword
systempassword
weblogicpassword
EOF

$ nohup sh adop_patch.sh &

Attempting to Start Apache (adapcctl.sh) Throws an 'Error While Loading Shared Libraries: libdb.so.2' on Linux

Issue:

After cloning or installing an Oracle E-Business Suite Release 12 instance on a Linux based server, an error similar to the following may occur while starting up the Apache service.

Note: This issue may occur on E-Business Suite release 12.0.x or release 12.1.x. It may also occur on any Linux release 5.x (or higher).

Cause:

The error is very clear about the missing soft link. It would show this error:
...
<physical Path>/10.1.3/Apache/Apache/bin/apachectl startssl: execing httpd
<physical Path>/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
...

Soft link libdb.so.2 is missing.

Solution:

To implement the solution, execute the following steps:

1. Shut down all services on the Application tier

2. As the unix root user, create a soft link as follows:

      ln -s /usr/lib/libgdbm.so.2.0.0 /usr/lib/libdb.so.2

3. Start up all services on the Application tier

NOTE: Linux release 7 (or higher) delivers a version of libgdbm.so that is higher than 2.0.0. A soft link to a version of libgdbm.so is higher than 2.0.0 may trigger the same error. A potential solution is to manually copy libgdbm.so.2.0.0 from an earlier Linux environment (5 of 6) and use it to create the link. Until the publishing of this note, this error does not occur when creating a softlink to libgdbm.so.2.0.0.

[Troubleshoot Socket:000445] Connection Rejected, Filter Blocked Socket While Accessing EBS R12 WebLogic Console

Issue:- The Server is not able to service this request: [Socket:000445]Connection rejected, filter blocked Socket, weblogic.security.net.FilterException: [Security:090220]rule 2

Solution:-   

1. Source the env file 

2. Bring Down the application Services 

3. Go to the location ----> cd $EBS_DOMAIN_HOME/config/

4. Take Backup of config.xml Change below parameter 

From: -

    <connection-filter-rule>0.0.0.0/0 * * deny</connection-filter-rule>

 To: -

    <connection-filter-rule>0.0.0.0/0 * * allow</connection-filter-rule>

 5. Bring up the Application Services.

 6.  After start the Admin Server, able to open the login page.

 

How to create directory in oracle database

            How to create directory in oracle database

Syntax:-

Using the 'create directory' statement to create a directory object in an Oracle database. The following statement creates a directory database object that points to a directory on the server:
CREATE OR REPLACE DIRECTORY <directory_name> AS '<UNIXBOX_system_path>';

Note:- 'directory_name’ is unique directory name and ‘UNIXBOX_system_path' specify the full path name of operating system directory of the server.


SQL> CREATE OR REPLACE DIRECTORY testing AS '/u01/TESTING';

SQL> GRANT READ, WRITE ON DIRECTORY testing TO APPS;


To check the Directory created.

SQL>SELECT * FROM DBA_DIRECTORIES;

SQL> SELECT * FROM ALL_DIRECTORIES;

OS Commend to create a directory:-

#mkdir -p /u01/TESTING
#chmod -R 777 /u01/TESTING

#ls -ltr /u01/TESTING

Oracle Apps R12.2 Log Files Location

1. R12.2 Start/Stop Log Files:
$INST_TOP/logs/appl/admin/log
Logfiles for start/stop of services from $ADMIN_SCRIPTS_HOME

Here is an image representing EBS R12.2 Service control (start/stop) logs:
Green color boxes indicate the location of log files

2. Patching log files
a) Online patching files are located in on the non-editioned file system(fs_ne) under:
$NE_BASE/ EBSapps/log/adop/<adop_session_id>/<phase>_<date>_<time>/<context_name>/log

3. Log files for concurrent programs/managers
$NE_BASE/ inst/<CONTEXT_NAME>/logs/appl/conc/log
Output files for concurrent programs/managers
$NE_BASE/inst/<CONTEXT_NAME>/logs/appl/conc/out

Here is an image representing EBS R12.2 Non-Editioned file system Logs:

Patching Logfile location:

4. Cloning related Log files:

a) Pre-clone log files in the source instance

     I. Database Tier
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/(StageDBTier_MMDDHHMM.log)

    II. Application Tier
$INST_TOP/admin/log/ (StageAppsTier_MMDDHHMM.log)

b) Clone log files in target instance

    I. Database Tier
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/ApplyDBTier_<time>.log

    II. Apps Tier
$INST_TOP/admin/log/ApplyAppsTier_<time>.log

5. AutoConfig log file:
a) Autoconfig log location on application tier:
$INST_TOP/admin/log/$MMDDHHMM/adconfig.log

b) Autoconfig Log Location on Database tier:
$ORACLE_HOME/ appsutil/ log/ $CONTEXT_NAME/ <MMDDHHMM>/ *.log

6.  Installation Related Logs:

Four Phases of R12.2 installation
1) RapidWiz Configuration file saved in below locations:
$TMP/<MMDDHHMM>/conf_<SID>.txt
$INST_TOP/conf_<SID>.txt
<RDBMS ORACLE_HOME>/ appsutil/ conf_<SID>.txt

2) Pre-install system check logs:
$TMP/<MMDDHHMM>/<MMDDHHMM>.log
$TMP/dbPreInstCheck.xxxxx.log
$TMP/wtprechk.xxxx/wtprechk.xxxx.log
<Global Inventory>/logs/installActions<timestamp>.log

3) Database Tier logs:
a) Main installation logs:
RDBMS $ORACLE_HOME/ appsutil/ log/ $CONTEXT_NAME/ <MMDDHHMM>.log

b) ORACLE_HOME installation logs:
RDBMS $ORACLE_HOME/ temp/ $CONTEXT_NAME/ logs/ *.log
<Global Inventory>/logs/*.log

d) Application tier
Both primary(Run) and Secondary Edition (Patch) file systems will each contain these logs:
1. Main Installation logs:
$INST_TOP/logs/<MMDDHHMM>.log

2. FMW and OHS TechStack Installation/Patching logs:
$APPL_TOP/admin/$CONTEXT_NAME/log/*<Global Inventory>/logs/*.log

REPORT THIS AD

3.Forms Oracle Home installation logs:
$APPL_TOP/admin/$CONTEXT_NAME/log/*.log

Here is an image representing the R12.2 Installation logs,

6. Fusion Middleware (FMW_HOME) Log Files:

 a) Log files for OPMN and OHS processes: Below directory contains log files related OPMN process(opmn.log), OPMN Debug logs(debug.log), HTTP Transaction logs (access.log), security settings related logs.

$IAS_ORACLE_HOME/ instances/ <ohs_instance>/diagnostics/logs

b) Log files for weblogic node manager: Log file is generated by Node Manager and contains data for all domains that are controlled by Node Manager on a given physical machine.

$FMW_HOME/ wlserver_10.3/ common/ nodemanager/ nmHome1/ nodemanager.log

c) Log files for weblogic Oracle Management Service log file: Initial settings AdminServer and Domain level information is written in this log file.
$EBS_DOMAIN_HOME/sysman/log

d) Log files for server processes initiated through WebLogic: Stdout and stderr messages generated by the server instance (server instances like forms, oafm, oacore etc) at NOTICE severity level or higher are written by Weblogic Node Manager to the below directory.
$EBS_DOMAIN_HOME/ servers/ <server_name>/ logs/ <server_name>.out

Here is an image representing EBS R12.2 Fusion Middleware Log files: