Oracle ACE Pro
Oracle Solution Architect
Oracle E-Business Suite
Oracle Cloud Infrastructure
Oracle Fusion Middleware
Oracle Database Administration
Oracle Weblogic Administration
Oracle ACE Pro
Oracle Solution Architect
Oracle E-Business Suite
Oracle Cloud Infrastructure
Oracle Fusion Middleware
Oracle Database Administration
Oracle Weblogic Administration
“AutoPatch (adpatch) is the utility you use to apply patches to the Oracle E-Business Suite file system or database.”
There Are Four Modes given Below In which ADpatch Can Be User
It is the default mode of ADpatch. We can apply patch in this mode by going into patch directory and simply type adpatch in command prompt and hit enter.
You can apply Patch in this mode as:
$adpatch Interactive=no
It uses default files to store prompt values and can be applied from patch directory.
This mode is purposely used to check what exactly patch will do without actually changing anything.
We can apply patch in this mode as:
$adpatch apply=no
By default apply=yes
This mode is used for any upgrade or consolidated update of utilities itself. It is suggested to apply pre-install patch first.
When we apply patch in preinstall mode, it updates all AD utilities before upgrade or update.
We can apply adpatch in this mode as:
$adpatch preinstall=y
We have multiple adpatch options and based on the requirement we can use specific options.
This options is used to skip the autoconfig execution, whereas by default it executes the autoconfig and updates the configuration file if any template file is added. This option is helpful when we apply multiple adpatch and they are not merged.
$adpatch options=noautoconfig
While we apply adpatch, It may create invalid objects and by default adpatch compiles the invalid objects after patch application. But in case you do not want to compile invalid objects to ensure the minimal autopatch time, you can apply adpatch as below:
$adpatch options=nocompiledb
This option is used to apply adpatch without copying the files present in copy driver. This can be applies as:
$adpatch options=nocopyportion
Adpatch also compiles the java server pages(JSP) after completion of patch application and can be skipped using the option nocompilejsp as below:
$adpatch options=nocompilejsp
Nodatabaseportion option is used to skip the adpatch the activity of database driver. It can be used as:
$adpatch options=nodatabaseportion
Nogenerateportion option is used to skip the adpatch activity of generate driver portion of the patch and you can use the option nogenerateportion as below:
$adpatch options=nogenerateportion
This option is used to apply patch without enabling maintenance mode. It can be used as:
$adpatch options=hotpatch
This option is used to skip the relinking and can be used as:
$adpatch options=nolink
This option is used to skip the generate form file. It can be used as:
$adpatch options=nogenform
This Option is used to execute the maintain MRC schema as part of patch. By default maintain MRC is done for standard patch and is disabled for documentation and translation patches.
$adpatch options=nomaintainmrc
This option is used to skip the pre-requisite Checks of Patches. This option can be used as below:
$adpatch options=noprereq
$ cd $IAS_ORACLE_HOME/Apache/Apache/bin/
$ pwd
/apps/ebs/apps/tech_st/10.1.3/Apache/Apache/bin
$ httpd -v
Server version: Oracle-Application-Server-10g/10.1.3.0.0 Oracle-HTTP-Server
Server built: Dec 27 2006 02:31:21
Finding Oracle Database Version on your system through Operating System
$ cd $ORACLE_HOME
$ cd bin
$ file oracle
oracle: ELF-64 executable object file – IA64
Finding Oracle Database Version on your system through SQL Prompt
SQL> select metadata from sys.kopm$ ;
METADATA
——————————————————————————–
0000006001240F050B0C030C0C0504050D0609070805050505050F05050505050A05050505050405
0607080823472347081123081141B0470083000107D0130000000000000000000000000000000000
0000000000000000000000000000000000000000
Here As you can See the Output Contains B4047 which means Database is 64-Bit Version.
If the Output contains B4023 then the Database is 32-Bit Version.
SQL> alter session set nls_date_format=’DD/MONTH/YYYY’;
Session altered.
SQL> select sysdate from dual;
SYSDATE
—————–
20/OCTOBER /2017
SQL> alter session set nls_date_format=’DD/MONTH/YYYY HH24:MI:SS’;
Session altered.
SQL> select sysdate from dual;
SYSDATE
————————–
20/OCTOBER /2017 17:19:12 –It is 24 hours format.
SQL> alter session set nls_date_format=’DD/MONTH/YYYY HH:MI:SS’;
Session altered.
SQL> select sysdate from dual;
SYSDATE
————————–
20/OCTOBER /2017 05:19:43 –It is 12 hours format.
All Rights Reserved