Sei sulla pagina 1di 9

Frequently Asked Questions (FAQ)

Oracle Projects
Installation, Patching & Upgrade
Release 10.7, 11.0 and 11.5 (11i)

The information in this document has been reviewed and is current as of 14-Jun-
2005.

Instructions for the reader: This FAQ document identifies the most frequently
reported how-to questions relating to Oracle Projects Installation, Patching &
Upgrade. The articles below do not include bugs/patches or troubleshooting as
these are addressed in great detail in the notes referenced at the bottom of this
document.

FAQ Summary
1. Patching: After you apply a patch, there may be an invalid view. How do
you validate the view?
2. General: How do you compile all objects for the APPS schema?
3. General: How do you generate a form, report, library, or menu from a
failed patch application?
4. General: How do you determine what patch set you are currently utilizing?
5. General: What are the current mini packs, patchsets or one off patches for
the Projects products?
6. Invalid Objects: There are specific invalid PA% objects in your database
that will not compile. What do you do to clean up these objects?
7. Patching: The Projects adpatch process may fail while running the
database driver. What actions do you need to complete to finish the patch
process?
8. Versions: How do you determine version information about a form, view,
package or executable?
9. Patching: What log files are generated when a patch is applied, and where
are they located?
10. License Manager: How do you change a shared install to a full install
using the License Manager?
11. Patching: How do you find any critical high priority/mandatory patches for
Oracle Projects?
12. Patching: How do you receive the enhanced trace options for the forms
diagnostics menu?

FAQ Details
Q1. After you apply a patch, there may be an invalid view. How do you
validate the view?

A: Most views are recreated via a new Projects sql script. These scripts would be
located in your $PA_TOP/patchsc/107/sql directory for release 10.7, and in
$PA_TOP/patch/110/sql directory for release 11.0.x, and in
$PA_TOP/patch/115/sql directory for release 11.5.x. After you run a select
statement to locate your invalid view, you can go to one of the above directories
and grep for that invalid view name. The following is an example of a select
statement to find invalid objects:

Login to sql as apps/[pwd]

SQL> select object_name, object_type


from user_objects
where status = 'INVALID';

OBJECT_NAME OBJECT_TYPE
------------------------------------------------ --------------------
PA_EXPENDITURE_TYPES_EXPEND_V VIEW

The following is a grep statement example for release 11.0 in unix to locate a
script to recreate a view:

Change directory to the corresponding $PA_TOP/patch/110/sql directory.


Type the following command in the $PA_TOP/ .. /sql directory:

$PA_TOP/patch/110/sql> grep -i PA_EXPENDITURE_TYPES_EXPEND_V *

There will be many resulting lines, but only one line has the required information.
An example of a resulting line is as follows:
pavw110.sql:CREATE OR REPLACE FORCE VIEW
pa_expenditure_types_expend_v
The pavw110.sql script is an update script that will recreate the view and validate
the invalid view. This is known by the "CREATE OR REPLACE FORCE VIEW"
statement from the grep.

You should log an iTAR with Projects if you do not find a current script to recreate
a view. Support will resolve any invalid object issue that you have. For additional
information, see Note 74660.1, Resolving Invalid Objects in Oracle Applications

[top]

Q2. How do you compile all objects for the APPS schema?
A: You can compile objects using the compile objects selection from the
ADADMIN tool. To compile all objects manually for the APPS schema you either
need to change directory to the $AD_TOP/sql directory or verify it is in your path.
Login to SQLPlus as system/manager and run the following command to compile
all APPS objects:

SQL> @adcompsc.pls apps apps %


You can replace the "%" sign with an actual object name to compile a single
object.

For mote information, see Note 104457.1, Invalid Objects FAQ's.

[top]

Q3. How do you generate a form, report, library, or menu from a failed patch
application?

A:

a. Find the name for the form that needs regenerating as stated in question
number 8 under the FORM heading.
b. Logon to the server as the applmgr that contains the forms, reports,
libraries, or menus that need to be regenerated
c. cd $AU_TOP
d. Run the corresponding command as follows:

Oracle Forms executables used to generate forms depends on platform and


Oracle Applications versions:

Unix Windows 95 Windows NT


10.7SC N/A f45gen.exe f45gen32.exe
10.7NCA f45gen N/A f45gen32.exe
11.0.x f45gen N/A f45gen32.exe
11.5.x f60gen N/A f60gen.exe

f45gen to generate forms syntax is:


f45gen userid=APPS/APPS module=[form name].fmb
output_file=[full path of schema top]/forms/US/[form name].fmx
module_type=form batch=no compile_all=special

r25convm to generate reports syntax is:


r25convm userid=APPS/APPS
source=/[full path of schema top]/reports/[report name].rdf
dest=/[full path of schema top]/reports/[report name].rdf
stype=rdffile dtype=rdffile logfile=[report name].log
overwrite=yes batch=yes dunit=character

f45gen to generate .pll (forms libraries) syntax is:


f45gen userid= APPS/APPS module=[library name].pll module_type=library
output_file=/[full path of schema top]/resource/[library name].pll
compile_all=Yes

FNDMDGEN to generate menus yntax is:


FNDMDGEN APPS/APPS 0 Y [language codename]
DB_TO_RUNTIME [application shortname] [message filename].msb

[top]

Q4. How do you determine what patch set you are currently utilizing?

A:

a. If you are on release level 10.7.16.1, patch set level PA.H (784658) or
higher, you run the following command in SQLPlus:

select pa_server_pkg.get_patch_level from dual;

b. For any release level lower than PA.H or release level of 11.0.x or 11.5.x,
there is no easy way to determine your patch set level. You will need to
retrieve a list of patch set numbers from MetaLink. Using that list, you can
utilize the find file utility to search for a file in the APPL_TOP/admin/
[SID_NAME] directory for Release 11.0.x or 11.5.x and in the APPL_TOP
directory for Release 10.7.16.1 called "applptch.txt". If the file exists, look in
the file for patch numbers from your patch set list (start with the latest patch
number and work backwards in the list until a hit is made).

You can also run the following grep statement in the directory where the
applptch.txt file resides to list all product groups patches:

fgrep 'begin bug pa' applptch.txt

c. If options a or b from above are not possible, you will have to select a
random number of views, forms, and packages. You can determine what
version the objects are based on. You will have to contact Oracle Projects
Support for an estimated patchset level. (To learn how to get version
information go to question 8)

For more information, review the following note:


Note.97398.1, What Patches have been applied to an instance?

[top]

Q5. What are the current mini packs, patchsets or one off patches for the
Projects products?

A:

Review Note:108691.1 for the latest patchset/family pack information for the
Projects products.
Review Note:108255.1 for the latest Internet Time (formerly Self-Service Time)
patching information.

[top]

Q6. There are specific invalid PA% objects in your database that will not
compile. What do you do to clean up these objects?

A: There are Oracle Projects objects in the database that may not compile. They
are part of Oracle Projects products, but you may not have that product installed
or implemented on your system.

The following are common product files that may be affected:

PA_PURGE%
--------------------
All objects starting with this name are part of the Oracle Projects Archive Purge
product.
a. a. If on release 10.7 or 11.0.x then download and install the patch for
Oracle Projects Archive Purge. Patch numbers are:
Release 11 - 1235250 Release 10.7 - 982722 (server-side) Release 10.7 -
982724 (client-side)
b. b. If upgrading to release 11i, Oracle Projects Archive Purge is not
currently available on that release.

You may complete one of the two options:

1. Drop all of these objects from the database.


2. Keep them in the Database as invalid, which will not affect Projects.

PA_%_UPGRADE%
--------------------
All objects starting with this name were part of the Oracle Projects upgrade from
9.x., 10.x to 10.7.16.1. You may drop all of these objects from the database with
no affect on the Oracle Projects product.

PA_ONLINE%
--------------------
Objects starting with this name are part of Oracle Projects Online Time and
Expense application.

Install the latest patchset or mini pack for Projects on any application version
level or drop the objects if you are not planning to use Oracle Projects Online
Time and Expense.

PA_ADW%
--------------------
Objects starting with this name are part of Oracle Projects Data Warehousing
product. You should setup Oracle Projects and Oracle Data Warehousing to
utilize this new product. Or, you can drop these objects if you are not going to
implement Oracle Data Warehousing.

[top]

Q7. The Projects adpatch process may fail while running the database
driver. What actions do you need to complete to finish the patch process?

A: You should restart the adpatch process for the database driver using only one
worker. There may be a conflict with another patch not completing before the
current patch starts.

For more information, see Note:47709.1, AutoInstall Frequently Asked Questions

[top]

Q8. How do you determine version information about a form, view, package
or executable?

A:

FORMS:
In the application, open the form you are having a problem with then, from the
menu bar, select Help>About Oracle applications. Near the bottom of the
information screen you will find a heading of "FORMS". Under this heading you
will find the name and version information of the currently selected form.
VIEWS:
Logon to the database using SQLPLUS as apps/ and run the following sql
command:

SELECT text
FROM user_views
WHERE name LIKE '[ENTER THE NAME OF THE VIEW IN ALL CAPS]'
AND text LIKE '%Header%';

PACKAGES:
Logon to the database using SQLPLUS as apps/ and run the following sql
command:

SELECT text
FROM user_source
WHERE name LIKE '[ENTER THE NAME OF THE PACKAGE IN ALL CAPS]'
AND text LIKE '%Header%';

EXECUTABLES:
To find the version of an executable you first must go to the
APPL_TOP\PRODUCT_TOP\bin directory where that file is located. Then run the
following command:

strings [NAME OF EXECUTABLE] | grep -i header > [somefilename.txt]

[top]

Q9. What log files are generated with adpatch, and where are they located?

A: The adpatch process will produce a log file which lists the actual process
steps and if any workers are spawned, worker logs will be created also. The
adpatch process will either use a default log file name, adpatch.log, or you are
prompted to create your own unique name. For release 10.7.16.1, the adpatch
log file is located in the $APPL_TOP/install/log directory. For Release 11.0.x or
11.5.x, the adpatch log file is located in the APPL_TOP/admin/[SID_NAME]
directory. If you do not create a unique log file name, the adpatch process will
append the log file each time you rerun it.

Most patches will utilize workers and each worker will create their own worker log
file. These log files are named adwork01.log, adwork02.log, etc. For release
10.7.16.1, the adwork0x.log log file is located in the $APPL_TOP/install/log
directory. For Release 11.0.x or 11.5.x, the adwork0x.log log file is located in the
APPL_TOP/admin/[SID_NAME]/log directory.
The adaimgr process will also generate a log file, which is located in the
$APPL_TOP/admin or $APPL_TOP/install/log directory.

If you are having problems applying a patch, please upload these log files when
you log a Service Request with Oracle Support.

[top]

Q10. How do you change a shared install to a full install using the License
Manager?

A: To change the status of an install from shared to full do the following:

$cd $COMMON_TOP/admin/assistants/licmgr
$LicenseMgr
If you are using 11.5.5 you can do the following:
$ cd $AD_TOP/bin
$adlicmgr.sh

[top]

Q11. How do you find any critical high priority/mandatory patches for
Oracle Projects?

A:

a. Sign on to MetaLink
b. Select the Patches button from the left Menu bar.
c. Select the Release, Product, Platform and Language based on your
configuration. If you would like to see patches for all products, click on the
first product, then Shift-Click on the last product to select all. Alternately, you
can select several individual products by holding down the Ctrl key while
selecting each one.
d. In the Limit Search to field, select High Priority Product Patches or High
Priority Product Patches NOT in Latest Mini Pack.

[top]

Q12. How do you receive the enhanced trace options for the forms
diagnostics menu?

A: Apply patch:1552649 to enhance the trace capabilities in 11i. This patch


provides an enhanced database trace utility for Application forms. A new trace
menu is provided that allows a regular trace, trace with binds, trace with waits
and trace with binds and waits. Once trace has been enabled, all forms opened
after that will also be running with trace enabled. When trace is disabled for a
form, all forms running in trace mode will have trace disabled when they gain
focus. For additional information, refer to Note:47709.1, AutoInstall Frequently
Asked Questions.

[top]

IMPORTANT: If you did not find the information you were searching for,
please review the following Installation, Patching & Upgrade information:

Installation, Patching & Upgrade Current Issues [Note:224814.1]


Installation, Patching & Upgrade Patches Guide [Note:225088.1]
Installation, Patching & Upgrade Setup and Usage Guide [Note:225813.1]
Installation, Patching & Upgrade Troubleshooting Guide [Note:224816.1]

Potrebbero piacerti anche