Tag Archives: Patching - Page 2

11i Pre Patching Script

Problem: How can I minimize errors occurring while patching on the Windows platform?

Solution: Use a script to ensure that all environment variables are set and all supporting utilities are accessible.

Read more »

Sample 11.5.9 to 12.1.1 Upgrade Steps

1. Preparing for the Upgrade

Apply 11i.AD.I
Back up database, Applications, and customizations
Prepare an upgrade plan for customizations
Convert to Multiple Organizations architecture
Review sizes of old and new tablespaces
Review Upgrade Tasks and Apply 11i.AD.I

Convert Oracle Alert E-mail Processing to the Workflow Notification Mailer
Financials and Procurement Tasks
Gather schema statistics for CBO
Back up the database
Run Rapid Install
Migrate or upgrade your database to Oracle 10g Release 2
Port application to Linux servers

2. Upgrading to Release 12

Disable AOL Audit Trail
Migrate database to Oracle10g Release 2
Back up the database
Apply Release 12 AD minipack
Run the American English upgrade patch driver
Run the NLS upgrade patch driver
Apply latest product patches
Synchronize NLS and American English product patches
Back up Oracle Applications

Finish the Upgrade
Configure Applications client software for forms applet (required)
Reapply customizations (conditional)
Integrate custom objects and schemas (conditional)

Finish System Administration Tasks
Complete Workflow Notification Mailer configuration (required)
Complete setup for Oracle XML Gateway (required)
Enable PDF printing (required)

3. Post-upgrade Tasks
Install online help
Update/verify custom responsibilities
Migrate custom development to new technologies
Migrate the CUSTOM library
Copy and re-customize modified scripts or reports
Review user responsibility assignments
Associate organization names with custom Alert definitions
Set operating unit mode for customizations
Assign the Report Manager Data Migration Program to a request group
Run the Data Migration Program

Update Status Monitor URLs
Synchronize Product License and Workflow BES license status
Financials and Procurement Tasks
Additional Tasks

adalnctl.sh: exiting with status 127

Problem: After installing 11.5.9 Vision instance, the apps listener exits with status 127.

Solution: Apply operating system patch 3830807

Metalink Reference:

Subject:  Attempt To Start Listener Exits With Status 127

Doc ID:  299810.1

Error in invoking target install of makefile ins_plsql.mk

Problem:

While installing Oracle 9.2.0.4 on Oracle Enterprise Linux 4 Update 4, the following error appears:

Error in invoking target install of makefile
/u01/app/oracle/plsql/lib/ins_plsql.mk

Solution:

Applied patch 4198954 (COMPATIBILITY PACKAGES FOR ORACLE ON RHEL 4)

Applying patch 4198954 resolved the installation error.

GLIBC_2.0 not defined in file libc.so.6

Problem: While installing Oracle 9.2.0.4 on Oracle Enterprise Linux 4 Update 4, the following error appears:

Error occurred during initialization of VM

Unable to load native library: /tmp/OraInstall2009-08-31_01-27-21PM/jre/lib/i386/libjava.so:

symbol __libc_wait, version GLIBC_2.0 not defined in file libc.so.6 with link time reference

Solution: Apply patch 3006854.

Metalink Reference:

Subject: RUNINSTALLER FAILS ON RED HAT 3 TRYING TO INSTALL ORACLE9I

Doc ID: 264178.1

Checking for Prerequisite Patches and Patch Levels

In a patch’s README file, the prerequisite patches and patch levels that must be in place before that patch is applied are listed. Patches are indicated by a patch number (usually seven digits long), for example, 4712852. Patch levels  are usually of the form 11i.<PRODUCT CODE>.<LETTER>, for example, 11i.GL.H.

To determine if a particular prerequisite patch has already been applied to the system, query the AD_BUGS table.

Step 1:        Source the environment to load SQL*Plus. Either the applications tier environment or database tier environment can be sourced.

[applmgr@appslinux /]$ cd /u2/oracle/vis2appl/
[applmgr@appslinux vis2appl]$ . APPSORA.env

Step 2:        Load SQL*Plus:

[applmgr@appslinux vis2appl]$ sqlplus apps/apps

Step 3:        To determine whether a particular patch has been applied, query the BUG_NUMBER column of the AD_BUGS table for the patch number. For example, to determine if the patch 4712852 has been applied to the system, issue this SQL query:

SQL> select bug_number, creation_date from ad_bugs where bug_number = '4712852';
BUG_NUMBER                     CREATION_DATE
------------------------------ -------------
4712852                        16-MAR-07

If the query returns a row, the patch has been applied, whereas if the query does not return any rows, then the patch has not been applied.

Step 4:        To determine the patch level of a product, query the PATCH_LEVEL columns of the FND_PRODUCT_INSTALLATIONS table. For example, to determine the patch level for the GL product, issue this SQL query:

SQL> select patch_level, status from fnd_product_installations where patch_level like '%GL%';
PATCH_LEVEL                    S
------------------------------ -
11i.GL.H                       I

Obtaining PeopleTools 8.49.15

Log on to Metalink3 and click the Patches and Downloads tab. Click PeopleSoft Products. Enter the following search criteria:

Search for:
Product Line: PeopleTools
Product: PeopleTools
Release: 8.49

Check the Bundles checkbox.
Then click the search button (a right arrow).

Update ID: 768890
Name: PT 8.49.15 Product Patch

https://psft-updates.oracle.com/psc/UGPRD/CUSTOMER/CUST/c/ICE_MAIN_MENU.ICE_SRCH_COMPONENT.GBL

https://psft-updates.oracle.com/ice/Resolutions/768890/PT84915-PSCA.htm
https://psft-updates.oracle.com/ice/Resolutions/768890/PT84915UserDoc_rev2.htm

Build and Alter Step (MP5) returns errors

Problem:

When running the Build and Alter Task > Build and Alter Step, the follow appear in the log file:

SQL Build process began on 12/29/2008 at 3:43:44 PM for database FSDEV.
 Warning: SAC_SRCNODE_VW - Record definition does not exist. Record not processed. (76,73)
 Warning: The record SPL_PEGGING_INF has more than 16 keys. Table will be altered to support functional index.
 Warning: The record WTHD_SENT_DTL has more than 16 keys. Table will be altered to support functional index.
 Warning: The record WTHD_SNT_D_HST has more than 16 keys. Table will be altered to support functional index.
 Warning: The record WTHD_TO_SND_DTL has more than 16 keys. Table will be altered to support functional index.
 Warning: The record WTHD_TO_SND_TMP has more than 16 keys. Table will be altered to support functional index.
 Warning: The record WTHD_TRXN_TMP3 has more than 16 keys. Table will be altered to support functional index.
 Warning: GM_CONT_CERT_VW - Record definition does not exist. Record not processed. (76,73)
 Warning: GM_CONT_JHDR_VW - Record definition does not exist. Record not processed. (76,73)
 Warning: GM_CONT_PROF_VW - Record definition does not exist. Record not processed. (76,73)
 Warning: PL_SOHOLD3_VW - Record definition does not exist. Record not processed. (76,73)
 Warning: RE_OPEXADT_PADD - Record definition does not exist. Record not processed. (76,73)
 Warning: RE_OPEXADT_RADD - Record definition does not exist. Record not processed. (76,73)
 Warning: SAC_TGTNODE_VW - Record definition does not exist. Record not processed. (76,73)
 Warning: SHIPTO_ADDR_VW1 - Record definition does not exist. Record not processed. (76,73)
 Warning: SHIPTO_ADDR_VW2 - Record definition does not exist. Record not processed. (76,73)
 Warning: SPA_SP_RC_PD_V2 - Record definition does not exist. Record not processed. (76,73)
 Warning: VNDR_ORDER_TMP - Record definition does not exist. Record not processed. (76,73)
 Warning: VNDR_REMIT_TMP - Record definition does not exist. Record not processed. (76,73)
**** Begin Build Settings for this Run
 Create Tables = Yes
 Create Indexes = Yes
 Create Views = Yes
 Create Triggers = Yes
 Alter Tables = Yes
 Log to File = Yes
 Log to Window = No
 Write comments to script = Yes
 Always overwrite files = Yes
 Execute SQL Now = No
 Write SQL to script file = Yes
 Logging level = Log fatal errors and warnings only
 Table creation option = Skip table if it exists
 View creation option = Drop and recreate view if it exists
 IndexCreationOption = Recreate index only if modified
 Alter Adds = Yes
 Alter Changes = Yes
 Alter Renames = Yes
 Alter Deletes = Yes
 Alter even if no changes = No
 Alter Table Option = Alter in Place
 Write script output to: Separate files
 Log filename = E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/BuildAndAlter.log
 Table creation script filename = E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateTables.sql
 Index creation script filename = E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateIndexes.sql
 View creation script filename = E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateView.sql
 Trigger creation script filename = E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateTriggers.sql
 Alter table script filename = E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/AlterTables.sql
 Alter drop column option = drop column if data present
 Alter truncate column option = truncate column if data present
 Target database platform = MICROSFT
 Target sizing set = 0
SQL Build process ended on 12/29/2008 at 3:45:28 PM.
 1641 records processed, 0 errors, 19 warnings.
 SQL Build script for Create Tables written to file E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateTables.sql.
 SQL Build script for Create Indexes written to file E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateIndexes.sql.
 SQL Build script for Create Views written to file E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateView.sql.
 SQL Build script for Create Triggers written to file E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateTriggers.sql.
 SQL Build script for Alter Tables written to file E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/AlterTables.sql.
 SQL Build log file written to E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/BuildAndAlter.log.

Solution:

This is acceptable according to the documentation for the step:

Important!
If you receive the following warning message during the Build and Alter Step of the Build and Alter task, it is due to the Record being deleted by the Project. Please ignore the warning: Record definition does not exist. Record not processed. (76,73). If you receive the following warning message during the Build and Alter Step of the Build and Alter task, it is due to the field being deleted by the Project. Please ignore the warning: Field to be deleted has data present. Record processed. (76,23).DB2 Customers may need to recreate All Views manually by running createvw.dms using Datamover. This is because some views might become inoperable due to dependencies.If Run Create Triggers Script step fails because a trigger does not exist in the database then go to the CREATETRIGGERS.sql script in the Output directory, remove the offending statement and rerun the script.

Cannot locate any Change Packages in the apply directory

Problem:

In Change Assistant (on glwebapp), navigated to Tools > Apply Change Packages. Went through wizard and reached Select apply directory. Chose directory E:staging, but the following error appeared:

Cannot locate any Change Packages in the apply directory

Solution:

Choose directory that contains the zip file of the downloaded patch (e.g. the directory that contains upd745700.zip, E:stagingCDImagescd849-FinMP5Cumulative).

Errors while running createvw.dms

Errors while running createvw.dms:

Related language record RE_LANDLORD_LG used by record RE_LANDLORD not found. (20,52)
Related Language Record VCHR_SRCHLG1_VW used by VCHR_SRCHCRT_VW not found (20,52)
Related language record BI_SHP_LANG_VW used by record BI_SHP_ADDR_VW2 not found. (20,52)

Data Mover crashes out.

Solution:

Did not perform step 10 of the PT 8.49.15 Product Patch User Documentation (https://psft-updates.oracle.com/ice/Resolutions/768890/PT84915UserDoc_rev2.htm). Using Application Designer, log on as user VP1 and copy project PATCH849. Then, in Data Mover, log on as VP1 and rerun CREATEVW.DMS.

10. Copy Patch Project – ONLY if PATCH849 exists –

Note: If no database changes have been made in PT 8.49 by the time this patch is released, the PATCH849 project will not exist in the projects folder and this step can be ignored.

a. Using PeopleTools 8.49.15, launch Application Designer, and sign on to the database as a PeopleSoft User. [VP1]
b. Select Tools > Copy Project > From File
c. Enter projects and select PATCH849 from the list of projects
d. Select Options and highlight the languages Common and English ONLY.
e. Select Copy to begin copying updated PeopleTools objects to your database.

After rerunning CREATEVW.DMS, the last four lines of the CREATEVW.LOG file shows:

SQL Views: 27267
Ended: Wed Dec 17 18:23:25 2008
Successful completion
Script Completed.

Other steps to try:

Stop SQL Server services and restart.
Log on as user VP1 when running createvw.dms

Reference:

http://www.pinpointps.com/?q=node/59

Restarting data mover after a crash
A data mover script can be restarted by coding in the DMS ‘set start after record name’ before the Import * command. If the record is name ps_tablename, then do not code the ‘ps_’, just code tablename.

Attempted to create views using Application Designer: In Application Designer, click Ctrl+F7 (Insert > Definitions from Project…), and search for all Records. Select All records and insert them into the current project (takes about 10 minutes to complete). Then click Build > Project and check only Create Views (modify other settings as necessary). Build the SQL script, and after creating,