1. Which products provide patch sets?
Answer
------
For character mode, there are no patch sets. Development does, when
warranted, create cumulative server patches, but you may request
single patches. For GUI, however, patch sets exist today for several
products including Payables, Purchasing, Receivables, Order Entry, Assets,
Projects, Inventory, Sales and Marketing, Cash Management and MRP.
Any product with modular interdependencies has the potential for a
product patch set.
2. Why aren't one-off client side patches provided as they have been for
the server side?
Answer
------
Oracle Applications code is highly modular and interdependent. When a fix
is made to a single file, that file may in turn be included in several
other application files. On UNIX and VMS servers, Oracle would send
one single patched file and relink all affected files. In a 16-bit
SmartClient environment relinking on site is not an option. So,
Oracle includes all of the affected files when sending a patch.
Other fixes may also have previously been made to the file being
patched, or to affected files. For the patch to be complete, and
to represent a configuration that was tested, all changed files must
be sent.
NCA is regenerated on site. As such, more granular patching is
possible in more cases.
3. Why do patch sets override all forms, causing you to have to
re-apply all customizations?
Answer
------
As a rule, a product patch set does not override all forms. All forms
that include a piece of changed code will be generated and included
in a product patch set. Unfortunately, customizations tend to be done
on high volume transactional forms that are constructed from pieces of
many other forms. These high volume forms tend to be always included
in product patch sets.
4. Is upgrading to GUI versions 15.1 & 16.1 now required?
What is Oracle's 'official' stance on this?
Answer
------
All customers on P15 or P16 are strongly encouraged to move to
15.1/16.1. Where it is possible, Oracle will provide patches to the
original P15 and P16 releases on a very limited basis. AR and OE
customers are required to move to 15.1 and 16.1. Releases 15.1 and 16.1
include an accumulation of fixes some of which form a baseline for
future fixes. P15.1 and P16.1 were created largely to address issues
with translation, but there are also numerous fixes to base functionality.
As noted in previous answers, there is a tremendous amount of
interdependency in product files. There will be many instances where
it will not be possible to patch to P15 or P16, the patch release will
be a necessary prerequisite.
5. How can a patch be backed out once it has been applied?
Answer
------
Character and GUI products:
Most components of these patches can be backed out. All file system
components can be reversed. Adpatch and Otto make backup copies of
files before patching them. To back out the patch, review the patch
driver to determine what actions were taken, and restore the backup
files.
Database patches:
Database patches may or may not be reversible, and may or may not need
to be reversed as part of backing out a patch. Database patches are
first file system patches and the script to accomplish the database
upgrade is stored in the file system. PL/SQL updates can potentially
be reversed by running the backed-up script to reverse the PL/SQL object.
Seed data updates are not as easily reversed, but in general would not
require reversal.
If severe problems are found after a patch has been applied then the
only supportable position may be to restore from backup. This
should be done only after the situation has been reviewed with
Oracle's Support Services organization.
6. Are patch sets be dependent upon each other? For example, do you
have to apply the previous patch set before applying the latest or most
current patch set?
Answer
------
Patch sets are cumulative. You need only install the latest patch set.
7. Do you always need to apply the entire patch set, or can you pick and
choose which fixes you wish to patch?
Answer
------
No. You need to apply the entire patch set.
8. Will all patch sets include both a server-side and client-side
patch(s)?
Answer
------
No. Not all patch sets include both a server side and client side
components. However, if there are both client and server components,
then they will both be required for patch sets. Check the README file
to determine whether a server side as well as a client side patch is
required.
9. What information will be included in the 'README' files ?
The readme file for a patch should include a description of the problem
being fixed and how to apply the fix. The patch driver file includes a
list of files that have been altered and a list a patches included in the
patch set.
10: How may I order a patch set?
Patch sets are available for downloading directly from Metalink.
Navigate to the Metalink home page and click on the "Download" option
on the sidebar.
Answer
------
For character mode, there are no patch sets. Development does, when
warranted, create cumulative server patches, but you may request
single patches. For GUI, however, patch sets exist today for several
products including Payables, Purchasing, Receivables, Order Entry, Assets,
Projects, Inventory, Sales and Marketing, Cash Management and MRP.
Any product with modular interdependencies has the potential for a
product patch set.
2. Why aren't one-off client side patches provided as they have been for
the server side?
Answer
------
Oracle Applications code is highly modular and interdependent. When a fix
is made to a single file, that file may in turn be included in several
other application files. On UNIX and VMS servers, Oracle would send
one single patched file and relink all affected files. In a 16-bit
SmartClient environment relinking on site is not an option. So,
Oracle includes all of the affected files when sending a patch.
Other fixes may also have previously been made to the file being
patched, or to affected files. For the patch to be complete, and
to represent a configuration that was tested, all changed files must
be sent.
NCA is regenerated on site. As such, more granular patching is
possible in more cases.
3. Why do patch sets override all forms, causing you to have to
re-apply all customizations?
Answer
------
As a rule, a product patch set does not override all forms. All forms
that include a piece of changed code will be generated and included
in a product patch set. Unfortunately, customizations tend to be done
on high volume transactional forms that are constructed from pieces of
many other forms. These high volume forms tend to be always included
in product patch sets.
4. Is upgrading to GUI versions 15.1 & 16.1 now required?
What is Oracle's 'official' stance on this?
Answer
------
All customers on P15 or P16 are strongly encouraged to move to
15.1/16.1. Where it is possible, Oracle will provide patches to the
original P15 and P16 releases on a very limited basis. AR and OE
customers are required to move to 15.1 and 16.1. Releases 15.1 and 16.1
include an accumulation of fixes some of which form a baseline for
future fixes. P15.1 and P16.1 were created largely to address issues
with translation, but there are also numerous fixes to base functionality.
As noted in previous answers, there is a tremendous amount of
interdependency in product files. There will be many instances where
it will not be possible to patch to P15 or P16, the patch release will
be a necessary prerequisite.
5. How can a patch be backed out once it has been applied?
Answer
------
Character and GUI products:
Most components of these patches can be backed out. All file system
components can be reversed. Adpatch and Otto make backup copies of
files before patching them. To back out the patch, review the patch
driver to determine what actions were taken, and restore the backup
files.
Database patches:
Database patches may or may not be reversible, and may or may not need
to be reversed as part of backing out a patch. Database patches are
first file system patches and the script to accomplish the database
upgrade is stored in the file system. PL/SQL updates can potentially
be reversed by running the backed-up script to reverse the PL/SQL object.
Seed data updates are not as easily reversed, but in general would not
require reversal.
If severe problems are found after a patch has been applied then the
only supportable position may be to restore from backup. This
should be done only after the situation has been reviewed with
Oracle's Support Services organization.
6. Are patch sets be dependent upon each other? For example, do you
have to apply the previous patch set before applying the latest or most
current patch set?
Answer
------
Patch sets are cumulative. You need only install the latest patch set.
7. Do you always need to apply the entire patch set, or can you pick and
choose which fixes you wish to patch?
Answer
------
No. You need to apply the entire patch set.
8. Will all patch sets include both a server-side and client-side
patch(s)?
Answer
------
No. Not all patch sets include both a server side and client side
components. However, if there are both client and server components,
then they will both be required for patch sets. Check the README file
to determine whether a server side as well as a client side patch is
required.
9. What information will be included in the 'README' files ?
The readme file for a patch should include a description of the problem
being fixed and how to apply the fix. The patch driver file includes a
list of files that have been altered and a list a patches included in the
patch set.
10: How may I order a patch set?
Patch sets are available for downloading directly from Metalink.
Navigate to the Metalink home page and click on the "Download" option
on the sidebar.
Comments
Post a Comment