Oracle   Home  

 

Oracle Database 9i, 10g, 11g

Oracle Data Warehouse & BI

Oracle Applications EBS 11i, R12

 Oracle Middleware

SQL & PL/SQL

UNIX/ Linux

   Home  >  Oracle Applications 11i/ R12  >  Oracle Application 11i DBA  >  Patching in NON-interactive Mode

 

Oracle Applications 11i eBusiness Suite DBA

Patching in NON-interactive Mode

 

 

1. Why Patching in NON-interactive mode ?

 

Instead of responding to the adpatch prompts, you can create a file which keeps the adpatch responses. In this case you don't have to asnswer to the adpatch prompt and because of this the down time is smaller. 

 

 

2. How could I create the response file (the defaultsfile file) ?

 

This could be done by running the AutoPatch in interactive mode using the defaultsfile = <file name> argument. When AutoPatch ask you for the location of the patch type abort and <ENTER>.

 

Example:

 

$ adpatch defaultsfile=$APPL_TOP/admin/VIS/mydefaults.txt

Copyright (c) 2002 Oracle Corporation
Redwood Shores, California, USA

Oracle Applications AutoPatch

Version 11.5.0

NOTE: You may not use this utility for custom development
unless you have written permission from Oracle Corporation.

Attention: AutoPatch no longer checks for unapplied pre-requisite patches.
You must use OAM Patch Wizard for this feature. Alternatively, you can
review the README for pre-requisite information.

Your default directory is '/APPS/visappl'.
Is this the correct APPL_TOP [Yes] ?

AutoPatch records your AutoPatch session in a text file
you specify. Enter your AutoPatch log file name or press [Return]
to accept the default file name shown in brackets.

Filename [adpatch.log] :

Defaults Feature Enabled = YES.

You can be notified by email if a failure occurs.
Do you wish to activate this feature [No] ?

Please enter the batchsize [1000] :


Please enter the name of the Oracle Applications System that this
APPL_TOP belongs to.

The Applications System name must be unique across all Oracle
Applications Systems at your site, must be from 1 to 30 characters
long, may only contain alphanumeric and underscore characters,
and must start with a letter.

Sample Applications System names are: "prod", "test", "demo" and
"Development_2".

Applications System Name [VIS] : VIS *


NOTE: If you do not currently have certain types of files installed
in this APPL_TOP, you may not be able to perform certain tasks.

Example 1: If you don't have files used for installing or upgrading
the database installed in this area, you cannot install or upgrade
the database from this APPL_TOP.

Example 2: If you don't have forms files installed in this area, you cannot
generate them or run them from this APPL_TOP.

Example 3: If you don't have concurrent program files installed in this area,
you cannot relink concurrent programs or generate reports from this APPL_TOP.


Do you currently have files used for installing or upgrading the database
installed in this APPL_TOP [YES] ? YES *


Do you currently have Java and HTML files for HTML-based functionality
installed in this APPL_TOP [YES] ? YES *


Do you currently have Oracle Applications forms files installed
in this APPL_TOP [YES] ? YES *

Do you currently have concurrent program files installed
in this APPL_TOP [YES] ? YES *

Please enter the name Oracle Applications will use to identify this APPL_TOP.

The APPL_TOP name you select must be unique within an Oracle Applications
System, must be from 1 to 30 characters long, may only contain
alphanumeric and underscore characters, and must start with a letter.

Sample APPL_TOP Names are: "prod_all", "demo3_forms2", and "forms1".

APPL_TOP Name [apps] : apps *

You are about to apply a patch to the installation of Oracle Applications
in your ORACLE database 'VIS'
using ORACLE executables in '/APPS/visora/8.0.6'.

Is this the correct database [Yes] ?

AutoPatch needs the password for your 'SYSTEM' ORACLE schema
in order to determine your installation configuration.

Enter the password for your 'SYSTEM' ORACLE schema: manager

The ORACLE username specified below for Application Object Library
uniquely identifies your existing product group: APPLSYS

Enter the ORACLE password of Application Object Library [APPS] :

AutoPatch is verifying your username/password.
The status of various features in this run of AutoPatch is:

<-Feature version in->
Feature Active? APPLTOP Data model Flags
------------------------------ ------- -------- ----------- -----------
CHECKFILE Yes 1 1 Y N N Y N Y
PREREQ Yes 6 6 Y N N Y N Y
CONCURRENT_SESSIONS No 2 2 Y Y N Y Y N
PATCH_TIMING Yes 2 2 Y N N Y N Y
PATCH_HIST_IN_DB Yes 6 6 Y N N Y N Y
SCHEMA_SWAP Yes 1 1 Y N N Y Y Y

Identifier for the current session is 26930

Reading product information from file...

Reading language and territory information from file...

 

More information about this subject ( Patching in NON-interactive Mode ) you can get from  www.in-oracle.com

 

 

Apply Patches in Non-interactive Mode

You can automate much of the patching process by applying patches in non-interactive mode. This process allows you to store the responses to the patching prompts in a defaults file, and then specify the name of this file when you run AutoPatch. See Oracle Applications Maintenance Procedures (11i) and Oracle Applications Patching Procedures (R12) for more information.

 

More information you can get from here.

 

Different Romanian Links/ Linkuri romanesti diferite

 

 

 

Oracle Database 9i, 10g, 11g

Oracle Data Warehouse & BI Oracle Applications EBS 11i, R12  Oracle Middleware

SQL & PL/SQL

UNIX/ Linux

   Home  >  Oracle Applications 11i/ R12  >  Oracle Application 11i DBA  >  Patching in NON-interactive Mode

 

Disclaimer: The views expressed on this web site are my own and do not reflect the views of Oracle Corporation. You may use the information from this site only at your risk. Copyright (c) 2009-2011 Paul Catalin Tomoiu. All rights reserved.