• USA : +1 973 910 5725
  • INDIA: +91 905 291 3388
  • info@tekslate.com
  • Login

Patching

1. Set Environment Variables
1.1. Login as Oracle user.
1.2. Change directory to,
$ cd /oracle/ visappl (11i)
$ cd /d01/oracle/VIS/apps/apps_st/appl (R12)
1.3. Execute APPSORA.env
$. ./APPSORA.env < ENTER>
Note: Make sure that there are double dots with space between them, . ./APPSORA.env

 

<<<<<<<————————-***********———————————>>>>>>>>

 

2. Stop Apps Services (on all nodes)
2.1. Change directory to,
$ cd /oracle/ viscomn/admin/scripts/VIS_vision (11i)
$ cd /d01/oracle/VIS/ inst/apps/VIS_vision/admin/ scripts (R12)
2.2. Execute script adstpall.sh to stop apps services.
2.3. $./ adstpall.sh apps/ apps (apps username and password)

Note: The scripts prompts provided here are of 11i as I found no major difference, so not provided R12 execution.

You are running adstpall.sh version 115.17Executing service control script:/oracle/ viscomn/admin/ scripts/VIS_vision/adapcctl.sh stop

script returned:

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

adapcctl.sh version 115.43

Stopping Apache Web Server Listener (dedicated HTTP) …

Stopping Apache Web Server Listener (dedicated PLSQL) …

/oracle/ viscomn/ conf/VIS_vision/ iAS/Apache/Apache/bin/apachectl stop: httpd stopped

adapcctl.sh: exiting with status 0

.end std out.

.end err out.* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *Executing service control script:

/oracle/ viscomn/admin/ scripts/VIS_vision/adalnctl.sh stop

script returned:

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

adalnctl.sh version

Shutting down listener process APPS_vis.

adalnctl.sh: exiting with status 0

.end std out.

.end err out.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Executing service control script:

/oracle/ viscomn/admin/ scripts/VIS_vision/adfrmctl.sh stop

script returned:

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

You are running adfrmctl.sh version 115.34

Stopping forms server for vis on port 9000.

adfrmctl.sh: exiting with status 0

.end std out.

.end err out.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Executing service control script:

/oracle/ viscomn/admin/ scripts/VIS_vision/adfmcctl.sh stop

script returned:

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

You are running adfmcctl.sh version 115.17

Stopping forms load balancing client for vis.

adfmcctl.sh: exiting with status 0

.end std out.

.end err out.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Executing service control script:

/oracle/ viscomn/admin/ scripts/VIS_vision/adfmsctl.sh stop

script returned:

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

You are running adfmsctl.sh version 115.13

Stopping forms metrics server for vis on port 9200.

adfmsctl.sh: exiting with status 0

.end std out.

.end err out.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Executing service control script:/oracle/ viscomn/admin/ scripts/VIS_vision/ jtffmctl.sh stopscript returned:

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

You are running jtffmctl.sh version 115.16

Shutting down Fulfillment Server for vis on port 9300 …

jtffmctl.sh: exiting with status 0

.end std out.

.end err out.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Executing service control script:

/oracle/ viscomn/admin/ scripts/VIS_vision/addisctl.sh stop

script returned:

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

addisctl.sh version 115.14

OAD is stopped

Osagent is stopped

Locator is stopped

Unable to stop gatekeeper. No process-id file found.

Unable to stop any Discoverer Sessions. No process-id file found.

Unable to stop any Discoverer Preference. No process-id file found.

Unable to stop any Discoverer Collector. No process-id file found.

addisctl.sh: exiting with status 0

.end std out.

.end err out.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

All enabled services on this node are stopped.

Check logfile /

 Note: Step 1 and 2 should be applied on all nodes. For demonstration I have performed on one node.

 

<<<<<<<————————-***********———————————>>>>>>>>
3. Enable Maintenance Mode
3.1. Use adadmin to change maintenance mode.
3.2. Change folder to,
$ cd /oracle/ visappl/ad/11.5.0/bin (11i)
$ cd /d01/oracle/VIS/apps/apps_st/appl/ad/12.0.0/bin (R12)
3.3. Execute script $./ adadmin

Oracle Applications AD AdministrationVersion 11.5.0NOTE: You may not use this utility for custom development

unless you have written permission from Oracle Corporation.

Your default directory is ‘/oracle/ visappl’.

Is this the correct APPL_TOP [Yes] ?

AD Administration records your AD Administration session in a text file

you specify. Enter your AD Administration log file name or press [Return]

to accept the default file name shown in brackets.

Filename [adadmin.log] :

* * * * * * * * * * * * * Start of AD Administration session * * * * * * * * * * * * *

AD Administration version: 11.5.0

AD Administration started at: Fri Sep 01 2006 11:26:39

APPL_TOP is set to /oracle/ visappl

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: I f 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: I f 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: I f you don’t have forms files installed in this area, you cannot

generate them or run them from this APPL_TOP.

Example 3: I f 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 [NO] ? NO *

Do you currently have Oracle Applications forms files installedin this APPL_TOP [NO] ? NO *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 [ vision] : vision *

You are about to use or modify Oracle Applications product tables

in your ORACLE database ‘vis’

using ORACLE executables in ‘/oracle/ visora/8.0.6’.

Is this the correct database [Yes] ?

AD Administration needs the password for your ‘SYSTEM’ ORACLE schema

in order to determine your installation configuration.

Enter the password for your ‘SYSTEM’ ORACLE schema:

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] :

AD Administration is verifying your username/password.

The status of various features in this run of AD Administration 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 24933

Reading product information from file…

Reading language and territory information from file…

Reading language information from applUS.txt …

Reading database to see what industry is currently installed.

Reading FND_LANGUAGES to see what is currently installed.

Currently, the following language is installed:

Code Language Status

US American English BaseYour base language will be AMERICAN.Setting up module information.

Reading database for information about the modules.

Saving module information.

Reading database for information about the products.

Reading database for information about how products depend on each other.

Reading topfile.txt …

Saving product information.

AD code level : [11i.AD.I .2]

AD Administration Main Menu

————————————————–

1. Generate Applications Files menu

2. Maintain Applications Files menu

3. Compile/Reload Applications Database Entities menu

4. Maintain Applications Database Entities menu

5. Change Maintenance Mode

6. Exit AD Administration

Enter your choice [6] : 5

Change Maintenance Mode

—————————————-

Maintenance Mode is currently: [Enabled] .

Maintenance mode should normally be enabled when patching

Oracle Applications and disabled when users are logged on

to the system. See the Oracle Applications Maintenance

Utilities manual for more information about maintenance mode.

Please select an option:

1. Enable Maintenance Mode

2. Disable Maintenance Mode

3. Return to Main Menu

Enter your choice [3] : 1

sqlplus -s &un_apps/ * * * * * @/oracle/ visappl/ad/11.5.0/patch/115/ sql/adsetmmd.sql ENABLE

Spawned Process 6370

Successfully enabled Maintenance Mode.

Review the messages above, then press [Return] to continue.

Backing up restart files, if any……Done.

Change Maintenance Mode

—————————————-

Maintenance Mode is currently: [Enabled] .

Maintenance mode should normally be enabled when patching

Oracle Applications and disabled when users are logged on

to the system. See the Oracle Applications MaintenanceUtilities manual for more information about maintenance mode.Please select an option:

1. Enable Maintenance Mode

2. Disable Maintenance Mode

3. Return to Main Menu

Enter your choice [3] : 3

AD Administration Main Menu

————————————————–

1. Generate Applications Files menu

2. Maintain Applications Files menu

3. Compile/Reload Applications Database Entities menu

4. Maintain Applications Database Entities menu

5. Change Maintenance Mode

6. Exit AD Administration

Enter your choice [6] : 6

Backing up restart files, if any……Done.

There is no timing information available for the current session.

AD Administration is complete.

Errors and warnings are listed in the log file

/oracle/ visappl/admin/ vis/ log/adadmin.log

and in other log files in the same directory.

 

Warning: There should be no space in the folder names where patches are placed.

 

<<<<<<<————————-***********———————————>>>>>>>>

 

4. Apply Patch using adpatch
4.1. Unzip the downloaded patch from metalink.
4.2. Open readme.html file from unzipped patch folder.
4.3. View the following readme.html of patch # 4712852 for 11i. I have applied this patch for demonstration for this document. Those who are practicing on R12 should download any patch related to R12.

91

 4.4. Follow all steps mentioned in readme.html of the patch you are going to apply.
4.5. In this patch there is no extra step and we have to apply the driver file u4712852.drv. Oracle has changed the patch files and now only one file is included that is has prefix u + patch number + .drv early patch had three files to apply with prefixes (c, d, g).

• The c copy driver (cXXXXXXX.drv) should be applied to Concurrent Processing/Admin/Forms/Web servers.
• The d database driver (dXXXXXXX.drv) should be applied to the Admin server.
• The g generate driver (g3016463.drv) should be applied to Concurrent Processing/Forms servers.

4.6. Change folder to,
$ cd /oracle/ visappl/ad/11.5.0/bin (11i)
$ cd /d01/oracle/VIS/apps/apps_st/appl/ad/12.0.0/bin (R12)
4.7. Execute $./ adpatch < ENTER> and follow the instructions and provide required
information.

Copyright (c) 2002 Oracle CorporationRedwood Shores, California, USAOracle 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 ‘/oracle/ 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] : 4712852.log

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: I f 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: I f 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: I f you don’t have forms files installed in this area, you cannot

generate them or run them from this APPL_TOP.

Example 3: I f 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 [NO] ? NO *

Do you currently have Oracle Applications forms files installedin this APPL_TOP [NO] ? NO *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 [ vision] : vision *

You are about to apply a patch to the installation of Oracle Applications

in your ORACLE database ‘vis’

using ORACLE executables in ‘/oracle/ 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:

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 24935

Reading product information from file…

Reading language and territory information from file…

Reading language information from applUS.txt …

Reading database to see what industry is currently installed.

Reading FND_LANGUAGES to see what is currently installed.

Currently, the following language is installed:

Code Language Status

—- ————————————— ———US American English BaseYour base language will be AMERICAN.

Setting up module information.

Reading database for information about the modules.

Saving module information.

Reading database for information about the products.

Reading database for information about how products depend on each other.

Reading topfile.txt …

Saving product information.

AD code level : [11i.AD.I .2]

Trying to obtain a lock…

Attempting to instantiate the current-view snapshot…

Was already instantiated. So no instantiation done this time.

* * * * * * * * * * * * * * * * S T A R T O F U P L O A D * * * * * * * * * * * * * * * *

Start date: Fri Sep 01 2006 12:07:48

0 “left over” javaupdates.txt files uploaded to DB: Fri Sep 01 2006 12:07:48

0 patches uploaded from the ADPSV format patch history files: Fri Sep 01 2006 12:07:48

Uploading information about files copied during the previous runs …

0 “left over” filescopied_< session_id> .txt files uploaded to DB: Fri Sep 01 2006 12:07:48

* * * * * * * * * * * * * * * * * * E N D O F U P L O A D * * * * * * * * * * * * * * * * * *

End date: Fri Sep 01 2006 12:07:48

Enter the directory where your Oracle Applications patch has been unloaded

The default directory is [ /oracle/ visappl/ad/11.5.0/bin] : /DUMP/DUMP/patches/act_patch/4712852

Please enter the name of your AutoPatch driver file : u4712852.drv

Getting Oracle Applications Release…

Current installed release is 11.5.10.2

Reading patch driver file…

Parsing and loading patch driver file…

Processing line 10000.

16358 lines processed.

Not checking patch integrity as integrity checking flag is turned off.

Successfully read patch driver file.

Determining target release…

Current target release is 11.5.10.2

Determining which bug fixes to apply…

Done determining which bug fixes to apply.Log and Info File sync point:Fri Sep 01 2006 12:09:49

Turning off actions that reference unrecognized products.

Log and Info File sync point:

Fri Sep 01 2006 12:09:49

End of unrecognized products checking.

AD utilities can support a maximum of 999 workers. Your

current database configuration supports a maximum of 91 workers.

Oracle recommends that you use between 16 and 32 workers.

Enter the number of parallel workers [16] :

Done purging timing information for prior sessions.

AutoPatch is complete.

AutoPatch may have written informational messages to the file

/oracle/ visappl/admin/ vis/ log/4712852.lgi

Errors and warnings are listed in the log file

/oracle/ visappl/admin/ vis/ log/4712852.log

and in other log files in the same directory.

4.8. The status is AutoPatch is complete. as show above means the patch applied
successfully.
4.9. I f there are more than one patches then all patches should be applied before proceeding to the next disabling maintenance mode step.

 

<<<<<<<————————-***********———————————>>>>>>>>

 

5. Disabling Maintenance Mode
5.1. The disabling steps are just same as enabling maintenance mode demonstrated above. Just to disable this time we will select 2 instead of 1, While all other steps are same. So I will not replicate the same text here. Please follow the topic Enable Maintenance Mode
5.2. View the following slide.

Maintenance Mode is currently: [Enabled] .Maintenance mode should normally be enabled when patchingOracle Applications and disabled when users are logged on

to the system. See the Oracle Applications Maintenance

Utilities manual for more information about maintenance mode.

Please select an option:

1. Enable Maintenance Mode

2. Disable Maintenance Mode

3. Return to Main Menu

Enter your choice [3] : 2sqlplus -s &un_apps/ * * * * * @/oracle/ visappl/ad/11.5.0/patch/115/ sql/adsetmmd.sql DISABLESpawned Process 19922

Successfully disabled Maintenance Mode.

Review the messages above, then press [Return] to continue.

Backing up restart files, if any……Done.

Change Maintenance Mode

—————————————-

Maintenance Mode is currently: [Disabled] .

 

<<<<<<<————————-***********———————————>>>>>>>>

 

6. Start Apps Services
6.1. Change directory to,
$ cd /oracle/ viscomn/admin/scripts/VIS_vision (11i)
$ cd /d01/oracle/VIS/ inst/apps/VIS_vision/admin/ scripts (R12)
6.2. Execute script adstrtal.sh to start apps services. The file name is with single “ l” of all as compare to adstpall.sh we used above to stop services.
6.3. $./ adstrtal.sh apps/ apps (apps username and password)

You are running adstrtal.sh version 115.14Executing service control script:/oracle/ viscomn/admin/ scripts/ vis_vision/adalnctl.sh start

script returned:

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

adalnctl.sh version

Checking for FNDFS executable.

Starting listener process APPS_vis.

adalnctl.sh: exiting with status 0

.end std out.

.end err out.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Executing service control script:

/oracle/ viscomn/admin/ scripts/ vis_vision/adcmctl.sh start

script returned:

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

You are running adcmctl.sh version 115.20

Starting concurrent manager for vis …

Starting vis_0901@vis Internal Concurrent Manager

Default printer is noprint

adcmctl.sh: exiting with status 0

.end std out.

.end err out.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Executing service control script:

/oracle/ viscomn/admin/ scripts/ vis_vision/adrepctl.sh start

script returned:

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

You are running adrepctl.sh version 115.29

starting Reports Server for vis on port 7000.

adrepctl.sh: exiting with status 0

.end std out.

.end err out.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

All enabled services for this node are started.

Check logfile /oracle/ viscomn/admin/ log/ vis_vision/09011226.log for details

Exiting with status 0

 

Summary
Review Date
Reviewed Item
Patching
Author Rating
5

“At TekSlate, we are trying to create high quality tutorials and articles, if you think any information is incorrect or want to add anything to the article, please feel free to get in touch with us at info@tekslate.com, we will update the article in 24 hours.”

0 Responses on Patching"

Leave a Message

Your email address will not be published. Required fields are marked *

Site Disclaimer, Copyright © 2016 - All Rights Reserved.