HRMS 补丁常见问题

gaoyiming

ORACLE  HRMS
-------------------------------
Patch Installations
----------------
FREQUENTLY ASKED QUESTIONS
-----------------------------------------------
28-Jun-2006

CONTENTS
---------------
HRMS PATCH FAQ
1. Where do I find a list of HRMS Mandatory Patchsets/minipacks/family packs?
2. Any special tips for applying Mandatory Patchsets/minipacks/family packs?
3. Does HR have to be installed in order to install Payroll?
4. Is there a preferred order of applying minipacks and mandatory patches after an install or upgrade?
5. How do I use ADPATCH to apply a patch?
6. How do I restart a failed patch?   
7. What are the patch drivers contained in a patch?
8. Where do I find patch logs on my server?
9. What are worker logs?
10. If a patch signals a failure and asks if I want to skip the error and continue,
    what should I do?
11. My patch is executing slowly, or is hanging.  What may I do to improve performance?
12. How do I determine what products that I have installed, and if they are fully
    installed or shared?
13. What HRMS patches should I apply if I have a Shared HR installation?
14. Once I have a Full Install of HR/Payroll, can I go back to a Shared installation?
15. How do I tell if I have invalid objects after a patch has been applied?
16. What are the HRMS Post Install steps?
17. How do I run the DataInstaller?
18. How do I install Geocodes?
19. How do I run the Hrglobal.drv driver?
20. How do I find the latest version of Hrglobal.drv?
21. How do I install Quantum from Vertex?
22. Where do I go to install Legislations?
23. Where do I find information on any issues with Family packs?
24. How do I install self service HR ?  Is there a patchset that delivers it ?



QUESTIONS & ANSWERS
-----------------------------------

1.Where do I find a list of HRMS Mandatory Patchsets/minipacks/family packs, minipacks,
family packs?

Answer
--------
Mandatory and Highly Recommended Patches and Patchsets/minipacks/family packs,
minipacks, family packs can be found on Metalink:
Navigate to: Top Tech Docs > E-Buisiness Suite:ERP >
and then;
For Payroll :
>Alerts>North American Payroll Newsletter
For Benefits:
>Patchset Information
For SSHR
>Patchset Information
For Oracle Time and Labor
>Patchset Information


(For additional information on patching, see the Patch Install link
under Human Resources and Payroll.

If using both HR and Payroll, both HR and Payroll mandatory patches
should be determined and applied in prerequisite order.   If not using Oracle
Payroll, only the HR patchsets/minipacks, should be applied.
Family Packs however include fixes for most of the products in the HRMS suite
of products and it would make no difference if you have HR and Payroll or HR only.

2. Any special tips for applying Mandatory Patchsets/minipacks/family packs,
and HRMS patches?

Answer
--------
There are many factors in making the application of Oracle HRMS
patchsets/minipacks/family packs, successful.

a. Patchsets/minipacks/family packs, should always be applied to test
    instances first, and tested, before being applied to production instances.

b. Always download and read the "README" documentation included with
    patches for special dependencies, application instructions, and any
    other appropriate warnings before applying patches.

c. Check for any patch prerequisites and make sure they have been
    successfully applied to the instance.

d. Keep adpatch and worker logs as a reference and as a means of
    trouble shooting the patch application..  Keep a record of all the
    patches that have been applied to each instance, with the date and
    time applied.  The log files are extremely important for determining
    patch errors and needed by Support to effectively resolve the
    patching issue.

e. Keep in mind that there are other Oracle Application mandatory
    patches that make application of HRMS patchsets/minipacks/family packs, successful.  
    Remember to check for necessary AD and FND patching.  It is
    necessary to stay current with core application patching, as new HRMS functionality
    depends on the most current core application software to support HRMS functionality.

e. Mandatory patches should be applied timely and in order of release
    to assure that versions of software are synchronized.  

    Patching in HRMS 11i does do version checking when patches are
    applied so that newer versions of software modules are not
    overwritten by older versions.  Keep in mind that patches have been
    developed and tested in release order of application, so applying
    patches in this same order helps to insure that the application will
    function as designed and patches will apply successfully.

    Patching in Oracle HRMS 10.7 and Oracle HRMS 11 is still highly
    dependent on applying patches in strict order.


3.  Does HR have to be installed in order to install Payroll?

Answer
--------
Yes, HR must be installed to install and use Payroll. However, Payroll
does not need to be installed to use HR.


4.  Is there a preferred order of applying patchsets/minipacks and mandatory
patches after an install or upgrade?

Answer
--------
The preferred order of applying patchsets/minipacks and mandatory patches in
relation to a new installation or upgrade to Oracle HR/Payroll Rel.11 is
to completely install the application,  apply the HR and Payroll
post-install drivers listed in the US Oracle HRMS Release 11
Implementation Guide, Appendix C, and then apply any mini-pack upgrade.  
The mandatory patches are the last to be applied.  

However, for new installations of Oracle Human Resources 11i, it is
appropriate to install the application, apply patchsets/minipacks/family packs,  
and then apply the post-installation steps (Data Installer and
hrglobal.drv), followed by any mandatory patching.

Keep in mind that the Data Installer and the hrglobal.drv must be run
after every HRMS patchset according to the instructions delivered in the
patchsets/minipacks/family packs, minipacks, family packs.  
Always apply the most current version of the hrglobal.drv.
If you are applying multiple minipacks/patchsets consecutively e.g.
PER then PAY then BEN, you can run the Data Installer and relevant
hrglobal.drv driver after all of the patchsets/minipacks are applied.

5. How do I use ADPATCH to apply a patch?

Answer
--------
ADPATCH is a utility that is responsible for applying a patch.  It is
normally called from the command line in the directory to which the
patch has been loaded.  It is responsible for executing the patch,
logging the details of patch execution, and all related housekeeping.  

Reference
----------
For detailed information regarding the use of ADPATCH, see Metalink note
130608.1, "ADPATCH BASICS".

6.  How do I restart a failed patch?  

Answer
--------
Restart a patch from the point it failed by starting ADPATCH, as it will
remember where it stopped and it will restart in the failed step.  To
restart from the beginning for a patch that has not completed, drop the
Fnd_Install_Processes table before starting the patch from the beginning.

If a patch stops before successful completion, and the patch is
restarted from the beginning, it is wise to recompile invalid objects
prior the restart.  Try recompiling several times until the number of
invalids does not diminish.  Recompiling the Apps schema may be
accomplished by running ADADMIN.  It may not be possible to recompile
every invalid object in the instance, but recompiling the Apps schema
will help the patch apply properly.

If a patch has run to completion but must be reapplied,  check with
Oracle Support.  Most of the Oracle HRMS patches may be re-applied, as
version checking is in place with Oracle patching, but some of the
legislative patches may not be re-applied.

If the patch is re-applied and it errors saying that the patch has
already been applied, check the Pay_Patch_Status table.  Restoring from
backup may be a reasonable solution if the wrong patch has been applied,
if a product has been installed by mistake, or if a patch has been run to
completion and modified data in a way that was not intended.  Restoring
an instance from backup is insurance of maintaining database integrity,
but it is not a mandated task if a patch does not apply successfully.


7. What are the patch drivers contained in a patch?

Answer
--------
A patch will always contain one or more drivers, which are responsible
for implementing software, and will always contain a "Readme" text to
explain the patch application and prerequisites.

The drivers a patch contains are:
   "c" driver, to copy software to respective directories and do a
    variety of tasks.   
   "d" driver, which delivers information to the database.  The d driver
   is only present if there are database updates.
   "g" driver, which delivers forms, reports, and concurrent processes.  
   Only present if the patch delivers form server updates.

The drivers are all executed using ADPATCH, and the drivers should be
applied in "c", "d", "g" order.

Each of the drivers will be located in the directory where the patch is
downloaded.  ADPATCH will be run from that directory.

If the form server is located on a separate physical machine, and a
patch has forms that must be installed ( i.e., "g" driver),  the patch
must be installed on the form server, and the "c" and "g" drivers
applied.  Specifically, the "c" driver must be installed on all servers,
the "d" driver on the database server, and the "g" driver on the server
with forms, reports, and concurrent manager.


8.  Where do I find patch logs on my server?

Answer
--------
The "log" files will be written by default to:
$APPL_TOP/admin/<sid>/log.

Supporting "out" files will be written by default to:
$APPL_TOP/admin/<sid>/out.


9. What are worker logs?

Answer
--------
Patches and patchsets/minipacks/family packs, minipacks, family packs have "workers"
that divide up the tasks to be performed and accomplish them simultaneously.  Unless
otherwise specified in the Readme, the number of workers for a patch will be
approximately 1 1/2 to 2 times the number of processors.

Each worker task will build its own worker log file, and are named
"adworkernn.log", where nn is the worker's number.   Often very detailed
errors appear in the log files that belong to each worker, and may
provide more information than the ADPATCH log.  Be aware of them in the
log directory.  If a patch fails, the log file will list the worker that
failed.

The worker log file number will be referenced in the adpatch log, and
that worker log will contain error messages.  Worker logs also create
even more individual logs for many of the tasks a worker performs.  If
the error messages in the worker log are not helpful, find these
individual logs, generally named with a reference number and
a .req extension.

The worker log files should always be reviewed for helpful error
information.  The worker logs are also useful and often necessary to
Support in troubleshooting  patching issues.

Worker log files keeps appending. To have fresh worker logs, make a backup
and delete the existing files

10. If a patch signals a failure and asks if I want to skip the error
and continue, what should I do?

Answer
--------
Often when the patch fails, it is failing on something that can be fixed
after the rest of the patch is complete.  Examples of this are formulas
(FFXBCP), forms, and reports.

When a worker fails, before restarting, check the worker log file to make sure
where the worker failed. Once the patch is continues, the messages are appended,
and to check the error you have to search up and down.

11.  My patch is executing slowly, or is hanging.  What may I do to
improve performance?

Answer
--------
There are many factors that affect software performance, but the
following are important considerations:
   a. Allocated resources devoted to the patch:
      Are there other processes running at the same time as the patch,
        which will contend for  system resources?
      Available CPU, i/o on the system  
      Are users or processes using tables that the patch will need,
        potentially creating a table "deadlock"?
      Database and system configuration?
      Space - are tables sized correctly?  Is tablespace sized correctly?
        Extent availability?
      Is TEMP tablespace sized correctly?
   b. Database optimization:
      11i database statistics should be run against an instance
        periodically.   Statistics may be run as a concurrent process in
        Oracle Applications Release 11i:
        Navigation: System Administrator -> Concurrent -> Requests
        Select the process  Gather Schema Statistics.  
        Select HR or BEN for the Schema parameter.
        Submit the process to the concurrent manager.
        Optimization is Cost Based in Release 11i, and Rule Based
                in Release 11 and 10.7.
   c.  Rollback Segment sizing:
       Often, rollback segments are not sized correctly, or are sized
         large enough and contribute to performance issues, as well as
         patch failure on rollback segment.  

12. How do I determine what Oracle HRMS products that I have installed
on my system, and if they are fully installed or shared?

Answer
--------
Run the following script in SQL*PLUS:

column application_name format a50
column application_short_name format a8
column status format a15
SELECT application_name, application_short_name,
  decode (status, 'I', 'Installed', 'S', 'Shared',
  'Not Installed') status,
   a.application_id
FROM fnd_application_all _view a,
             fnd_product_installations i
WHERE a.application_id = i.application_id
order by 1;

13.What HRMS patches should I apply if I have a Shared HR installation?


Answer
--------
For Oracle HR Release 11 and Oracle HR Release 11i, apply the most
current PER Patchset.

14.Once I have a Full Install of HR/Payroll, can I go back to a
   Shared installation?

Answer
--------
For Oracle HR Release 11 and Oracle HR Release 11i, the application must
be reinstalled as Shared.

For Oracle Release 10.7, complete the following steps:
  Login to the application as System Administrator
  Navigate:  Install> Information
  Query Oracle Human Resources in the Application field
  Using the Status Drop Down list box, choose Shared.

15.How do I tell if I have invalid objects after a patch has been
   applied?

Answer
--------  
It is advisable to recompile all database objects by using ADADMIN
to recompile the Apps schema, as directed after applying a patch.  If
unsure of the status of the database objects, query database object
table by using the following query in SQL*PLUS

      SELECT object_name, object_type, status
      FROM  dba_objects
      WHERE status != 'VALID';

16.What are the HRMS Post Install steps?

Answer
The Post Install steps for HRMS comprise the Updating your Quantum/Vertex with
holds tax information, DataInstaller which allows you to select the legislations
that you run on your instance as well as the JIT/Geocode information necessary for
Jurisdiction and address validation. DataInstaller will also allow you to select OTL  
You will also need to run hrglobal.drv as part of your post install steps.

17.         How do I run the DataInstaller?
       
        Answer:
        DataInstaller is run after every HRMS Patchsets/minipacks/family packs.
        Please refer to Note 145837.1 Latest HRMS (HR Global) Legislative Data Patch Available

18.         How do I install Geocodes?
       
        Answer:
       
        Geocodes seed your address information.  As of 11i.PER.F, the Geocode information
        is delivered by the hrglobal.drv, you do not need to apply a separate file from Vertex.
        Please refer to Note 140511.1  :  How to Install Legislative Data Using Data Installer and hrglobal.drv

19.         How do I run the Hrglobal.drv driver?
       
        Answer:
        Please refer to Note 140511.1  :  How to Install Legislative Data Using Data Installer and hrglobal.drv

20.         How do I find the latest version of Hrglobal.drv?
       
        Answer:
        Hrglobal.drv files are released on a constant basis.
        Have a look these notes available on Metalink for the latest file version of this file
       
        Note 145837.1  Latest HRMS (HR Global) Legislative Data Patch available
        Note 175846.1  How to find the latest version of hrglobal.drv on Metalink.
       
21.         How do I install Quantum from Vertex?
       
        Answer:
        All the instructions are in:
       
        Note 224273.1  Installing Quantum for Oracle Payroll (release 11i)
        Note 156478.1  How To Apply the Vertex Monthly Update Patch for Release 10.7 and Release 11
22.         Where do I go to install Legislations?
       
        Answer:
       
        Your legislations are installed as part of your DataInstall.  When you run
        DataInstall you indicate the various legislations which you would like to install.
       
       
       
23.         Where do I find information on any issues with Family packs?
       
        Answer:
       
        Any issues found after the release of this family-pack will be
        highlighted on metalink in the "Oracle HRMS Product Family -
        Release 11i Information" page Note 135266.1
        You are strongly encouraged to check this page for any high priority
        alerts before applying this family-pack.
       
       
24.         How do I install self service HR ?  Is there a patchset that delivers it ?

Answer:

Self service HR  (SSHR) is included as part of the patching in the HRMS suite.  There is
no separate patch for this, as each HRMS product contains an element of Self Service.  
(i.e.  Payroll has the online payslip) It is important however that you refer to the
mandatory spreadsheet for this product: In Metalink Navigate to: Top Tech Docs >
E-Buisiness Suite:ERP > SSHR >Patchset Information