|
|
|
Interoperability Notes
Oracle Applications Release 10.7
with Enterprise Edition Release 8.1.7
October 2002
This document describes the process to upgrade an existing Oracle
Applications Release 10.7 database instance to use Oracle8i
Enterprise Edition Release 8.1.7.x, where x denotes the patch set
level (currently 4). The most current version of these notes is document 148901.1 on OracleMetaLink.
This document contains three sections. Determine which of the
first two sections applies to your requirement, and follow the
instructions for that section. The third section is background
information that is relevant if you intend to run your Release 10.7
installation with Oracle8i.
If you are upgrading your database as a category 1 step from the
manual Upgrading Oracle Applications, Release 11i, follow
the instructions in Section 1. Category 1
steps are done in
advance of your actual Applications upgrade. If you are upgrading
your database as a category 3 step, follow the instructions in
Upgrading Oracle Applications, Release 11i.
| Attention: These notes apply to
UNIX and Windows NT/2000 platforms. However, you may need to
modify some instructions slightly depending upon your
platform. For example, these notes typically use UNIX syntax
when specifying a directory, so Windows NT/2000 users will need to
substitute the appropriate syntax when accessing that
directory(folder). |
Section 1:
Upgrade existing Oracle Applications Release 10.7 to run with
Oracle8i
This section contains instructions for migrating or upgrading an
existing Oracle Applications Release 10.7 database from Oracle7
Server Release 7.3.4, from Oracle8 Enterprise Edition Release 8.0.x, or
from older Oracle8i Enterprise Edition Release 8.1 to the current
Oracle8i Enterprise Edition Release.
If you are already using Oracle8i Enterprise Edition Release
8.1.7 database, do not proceed. Follow the instructions in Section 2.
- Update Oracle7 Technology Stack
If you are using Oracle7 Server Release 7.3.2.3 or Release
7.3.3, you must upgrade the technology stack to Release
7.3.4 and apply the corresponding interoperability patches
before beginning the upgrade to Oracle8i Enterprise
Edition.
If you are using Oracle Web Application Server 3.0.2 on the
Solaris operating system, you
also require the Web Server patch 1673924. Follow the
instructions in the readme file included in the patch.
- Ensure minimum Release 10.7 patch levels
You must be at the following patch set levels for Oracle
Applications Release 10.7 to work properly with
Oracle8i Enterprise Edition:
| Product |
Patch Level |
| AP |
Payables |
Patch Set V (or higher) |
| AR |
Receivables |
Patch Set W (or higher) |
| AS |
Sales & Marketing |
Patch Set H (or higher) |
|
| AX |
Global Accounting Engine |
Patch Set F (or higher) |
|
| OE |
Order Entry |
Patch Set J (or higher) |
|
| PO |
Purchasing |
Patch Set M (or higher) |
|
- Shut Down Applications
All of the prior steps in this section can be done prior to
the database migration or upgrade. From this point forward
your Applications system will be unavailable until the
process is complete.
- Backup Database
It is appropriate at this time to make a backup copy of your
database.
- Modify init.ora parameters
Log in to the machine where the Oracle Applications Release
10.7 database is running as the user who manages the Oracle
Server files and database.
Some of the database initialization parameters have changed or
become obsolete in Oracle8i Enterprise Edition
Release. Details are available in the Oracle8i
Migration Guide. If any such parameter exists in the database
initialization file (init.ora), you must remove them or
comment them out from the initialization file of the Oracle
Applications Release 10.7 database.
The following events are required in the database
initialization file to maintain the compatibility of PL/SQL
constructs supported in Oracle 7 and earlier releases of
Oracle8. Add them to the init.ora file if they do not
already exist.
- event = "10929 trace name context forever"
- event = "10932 trace name context level 2"
- Install Oracle8i Enterprise Edition
Log in to the machine where the Oracle Applications Release 10.7
database is running as a user whom you wish to manage the
Oracle8i Enterprise Edition files and database.
Make sure that none of the environment settings, such as
ORACLE_HOME, PATH, ORA_NLS, etc. refer to the existing
Oracle7 Server Release 7.3.4, Oracle8 Enterprise Edition
Release 8.0.x, or earlier Oracle8i Enterprise Edition
Release environment. You must install the latest
Oracle8i Enterprise Edition release into a separate
ORACLE_HOME.
| Attention:
On Windows NT/2000 machines, the Oracle7 Server installation
architecture requires special handling to support multiple
ORACLE_HOME directories. If you wish to put both ORACLE_HOMEs
on the same Windows NT/2000 machine, you must install Release
7.3.4 first, and then install Release 8.1.7 into a separate
directory.
You should already have 7.3.4 installed, so
this is not a problem.
|
Follow the instructions in the Oracle8i Installation
Guide to perform the installation. We recommend the Custom
installation type with at least the following components :
- Oracle8i Server
- Net8 Server
- Net8 Client
- Oracle Utilities
Do not run any migration scripts at this time.
- Apply latest certified 8.1.7 Patch Set
Apply the latest certified Oracle8i Release 8.1.7
patchset to the 8.1.7 Oracle Home using Oracle Universal
Installer.
Do not run any SQL scripts documented in the patchset
release notes at this time.
- Check OracleMetaLink/Certify for additional patches
Additional issues with Applications running on 8.1.7 may have
been identified since this document was authored. Check the
Certify section of OracleMetaLink for the latest issues.
- Ensure Adequate Rollback and System Space
Ensure that there is sufficient free space in the SYSTEM
tablespace (greater than 500 MB) and for the Rollback
segments (greater than 250 MB).
- Migrate or Upgrade the Oracle Applications Database
If your Oracle Applications database is currently using Oracle7
Server Release 7.3.4, you must migrate the database to
Oracle8i Enterprise Edition Release.
If your Oracle Applications database is currently using Oracle8
Enterprise Edition Release 8.0.x or earlier Oracle8i
Enterprise Edition Release, you must upgrade the database
to Oracle8i Enterprise Edition Release.
Refer to Oracle8i Migration Release 4 (8.1.7) for
a description of these methods and complete instructions on how to
migrate or upgrade the database. Ensure that you have the latest
version of the manual, which can be found on the
Oracle Technology Network.
You will be upgrading or migrating directly to latest patchset
version Enterprise Server Release 8.1.7. You may disregard
the admonition in the 8.1.7 patchset release notes that warns
that you cannot upgrade directly to 8.1.7 patchset.
Migrate or upgrade the database only, unless you have installed
additional components for your own customizations. Additional
components such as interMedia or JServer are not used by Oracle
Applications Release 10.7.
- Configure the Net8 listener
The Net8 listener must be configured such that the database can be
accessed from the Oracle Applications Release 10.7 file system and
the Oracle7 Server Release 7.3.4 technology stack. Refer to the
Net8 Administrator's Guide. Start the listener
once it has been configured.
- Set up the SQL*Net client
Log in to the machine where Oracle Applications Release 10.7 is
installed as the user who manages the Oracle7 Server technology
stack. (If you are using Release 10.7 NCA, log in to the
Applications concurrent manager server, not the forms
server.) Make sure
that all of the environment settings, such as ORACLE_HOME, PATH,
ORA_NLS, etc. refer to the Oracle7 Server Release 7.3.4 technology
stack environment. They must not refer to the new Oracle8i
Enterprise Edition Release environment.
Configure the SQL*Net client on the machine where Oracle
Applications Release 10.7 is installed such that the Oracle
Applications Release 10.7 file system can connect to the
Oracle8i Enterprise Edition Release Applications
database. Refer to Understanding SQL*Net, Release 2.3.
The TWO_TASK environment variable on UNIX, or the LOCAL
environment setting on Windows NT/2000, must be set to the connect
string of the Applications database that you define. The
ORACLE_SID environment setting must not be set. Use SQL*Plus to
test the connection.
- Apply Applications interoperability patches
If you are already using Oracle Applications Release 10.7 in a
server partitioning environment with a previous
Oracle8i Enterprise Edition release, you should have
already applied these patches
to your environment and can skip this step.
| Product |
Patch Number |
Special Instructions |
| Application Install |
499648 |
apply only the copy driver only. Do not apply the
db494405.drv driver and ignore the special
instructions in the readme.txt.
|
| Oracle Receivables |
480129 |
use adpatch utility with patch.drv driver
|
| Applications Install |
487890 |
use adpatch utility with patch.drv driver. Ignore the
special instructions in the readme.txt. See the comments
in the ADXGNPNS.sql script
|
| Oracle Payroll |
583816 |
use adpatch utility with patch.drv and d583816.drv
driver file.
|
| Oracle Master Scheduling |
622114 |
use adpatch utility with patch.drv and d622114.drv
driver file.
|
| Oracle Assets |
1054707 |
use adpatch utility with patch.drv and d1054707.drv
driver file.
|
- Compile invalid objects
You may use the standard utility utlrp.sql (found in
$ORACLE_HOME/rdbms/admin) to compile all the invalid objects in
the Oracle Applications.
Most of the database objects will be marked as invalid due to the
database migration or upgrade. To compile the objects that belong
to the APPS schema, run AD Administration and choose the "Compile
APPS schema(s)" option from the Maintain Applications Database
Objects menu.
- Restart your Applications
The process is complete.
Section 2: Applying the latest certified Oracle8i
Release 8.1.7 Patchset
Follow instructions in this section, only if you have an existing
Oracle Applications Release 10.7 installation using Oracle8i
Enterprise Edition Release 8.1.7 Database.
- Shut Down Servers, Concurrent Managers and Database
All servers and processes such as the Oracle Applications forms
server, Web Server and Concurrent Managers must be shut down and
all users must be logged out before starting the database upgrade.
Oracle Applications will be unavailable to users until all tasks
in this section are completed.
- Log in as the Oracle User
Log in again as the user who manages (owns) the existing the
Oracle8i Enterprise Edition files and database. Make
sure that none of the environment settings, such as ORACLE_HOME,
PATH, ORA_NLS, etc. refer to the existing Oracle7 Server
Release 7.3.4 environment.
- Ensure Adequate Rollback and System Space
Ensure that there is sufficient free space in the SYSTEM tablespace
(greater than 500 MB) and for the Rollback segments (greater than
750 MB).
- Install latest certified 8.1.7 Patch Set
Install the latest certified Oracle8i Release 8.1.7 patch
set into the 8.1.7 Oracle Home using Oracle Universal Installer.
Oracle8i Release 8.1.7 patchset release notes contains
database update steps required for this patchset. Follow the
instructions in the How to Install This Patch Set section
to upgrade the Oracle Applications Databases.
- Check OracleMetaLink for additional patches
Additional issues with Applications running on 8.1.7 may have
been identified since this document was authored. Check the
Certify section of OracleMetaLink for the latest issues.
- Compile All Apps objects.
You may use the standard utility utlrp.sql (found in
$ORACLE_HOME/rdbms/admin) to compile all the invalid objects in
the Oracle Applications.
Many database objects will become invalid due to the database
upgrade. Compile the objects that belong to the APPS schema.
Run AD Administration on the administration server and choose
the "Compile APPS schema(s)" option from the Maintain Applications
Database Objects menu.
- Restart your Applications
The process is complete.
Section 3: Using Oracle8i with Release 10.7
Multiple Oracle Homes (Server Partitioning)
Oracle Applications supports running with data in a database of
one version, while linking Oracle Applications programs using the
tools from another version of the database server. This
is known as multiple Oracle Homes. This is also known as Server
Partitioning. This model allows Oracle to support features in
later database server versions and still maintain compatibility
with an earlier release. Multiple Oracle Homes or Server
Partitioning is not unusual or difficult. Release 11i has
three Oracle Homes.
Oracle Applications Release 10.7 supports Oracle8i
Enterprise Edition Release through server partitioning. The Oracle
Applications file system continues to use one ORACLE_HOME using
the Oracle7 Server Release 7.3.4 technology stack. An
Oracle8i Enterprise Edition Release database server is
installed in a second ORACLE_HOME, which is not necessarily on the
same machine as the Oracle Applications file system.
Oracle Applications Release 10.7 database objects and data are
stored in the database, which is located in the second
ORACLE_HOME. SQL*Net and Net8 handles communication between the
Oracle Applications file system and the Oracle8i Enterprise
Edition Applications database.
The following diagram illustrates the layers in a server
partitioning model with two ORACLE_HOMEs. The server partitioning
model works whether the Oracle7 ORACLE_HOME and the Oracle8i
ORACLE_HOME are on the same machine or on different machines. If
they are on the same machine, they must be in separate directories.
| APPL_TOP ORACLE HOME |
|
Database ORACLE HOME |
Oracle APPS 10.7 File System
Oracle7 Release 7.3.4 Tech Stack
SQL*Net V2 client
|
Ü
SQL*Net
Þ
Ü
Net8
Þ
|
Oracle8i Database Server
Oracle APPS 10.7 Database
Net8 listener
|
Changes in PL/SQL syntax from Oracle7 to Oracle8i
The syntax of certain Oracle7 PL/SQL constructs has changed in
Oracle8i. As a result, some of the Oracle Applications Release
10.7 PL/SQL objects, which were originally created using Oracle7
PL/SQL syntax, are not compilable once the database has been upgraded
to Oracle8i.
The prerequisite patch sets and interoperability patches listed in
these release notes should fix all such Oracle Applications
objects. However, if you have custom PL/SQL objects that you created
based on the original Oracle Applications PL/SQL object syntax, or if
you have customized Oracle Applications PL/SQL objects, you may find
that they are not compilable after the upgrade.
Here are some examples of PL/SQL errors that occurred when trying to
compile certain Oracle Applications objects in an Oracle8i
database before the objects were fixed:
- PLS-00103: Encountered the symbol "VARCHAR2" when expecting one
of the following: ( The symbol "(" was substituted for "VARCHAR2"
to continue.
- PLS-00103: Encountered the symbol "DATE" when expecting one of
the following: ( The symbol "(" was substituted for "DATE" to
continue.
- PLS-00103: Encountered the symbol "NUMBER" when expecting one
of the following: ( The symbol "(" was substituted for "NUMBER"
to continue.
- PLS-00566: type name "TAX_AMT_REC_TYPE" cannot be constrained.
Refer to the Oracle8i Supplied PL/SQL Packages Reference and
the PL/SQL User's Guide and Reference for information about
the new PL/SQL syntax, which will allow you to update your custom code
so that it is compatible with Oracle8i.
|
|