DOC> Online Patching Enablement: Readiness Report - Manual Fixes

DOC>
DOC>#
DOC> DISCLAIMER: Customers should not attempt to fix any E-Business Suite code
DOC>
violations. E-Business Suite objects listed in sections that
DOC>
instruct to perform manual fixes should be reported to Oracle
DOC>
Support.
DOC>
DOC> Note: If you are running this report prior to the E-Business Suite 12.2
DOC>
Upgrade, you can ignore all the E-Business Suite objects listed in
DOC>
the report. The Upgrade process will address any violation to the
DOC>
EBR rule on the E-Business Suite code.
DOC>==========================================================================
DOC>#
DOC>
DOC> **********************************************************************
DOC> SECTION-1
DOC> **********************************************************************
DOC>
DOC> MANUAL FIX: Objects in Non-EBS schemas that depend on Editioned
DOC> Objects of EBS.
DOC>
DOC> To fix these violations, do one of the following:
DOC>
- Register object schema (owner) as a Custom EBS Schema, please refer t
o
DOC>
report ADZDPSUM.sql
DOC>
- Drop object, if not required
DOC>
- Redefine object to remove dependency
DOC>
- Move the object to a registered Custom EBS Schema
DOC>
DOC> Oracle recommends you perform the chosen fix by customizing template file
DOC> $AD_TOP/sql/ADZDPCUST.sql
DOC>
DOC>#
no rows selected
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>
n on
DOC>
ine
DOC>
DOC>
DOC>
DOC>
DOC>

**********************************************************************
SECTION-2
**********************************************************************
MANUAL FIX: Non-Editioned EBS objects that depend on editioned objects.
The objects reported in this section belong to the schemas already
registered in the application.
To fix these violations, do one of the following
- Drop object, if not required
- Redefine object to remove dependency.
Please refer to EBS "Online Patching Development Standards" for informatio
how to define objects that are compatible with editioned databases and Onl
Patching.
Oracle recommends you perform the chosen fix by customizing template file
$AD_TOP/sql/ADZDPCUST.sql

DOC>#
no rows selected
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>
iness
DOC>
DOC>
DOC>
d.
DOC>
3.1.
DOC>
DOC>
DOC>
DOC>
be
DOC>
e
DOC>
DOC>
DOC>#

**********************************************************************
SECTION-3
**********************************************************************
MANUAL FIX: Objects in non-editionable schemas that depend on Oracle E-Bus
Suite Code
To fix these violations move the objects to an schema that can be editione
If these objects are part of an APEX application please review Note:130656
This note provides detailed information on how to properly code APEX
applications that work with Oracle E-Business Suite. The key aspect in the
note is the requirement to have a separate schema for holding the APEX
generated objects that make up the custom application. This schema should
registered with the application and will be editioned as part of the Onlin
Patching Enablement process.

no rows selected
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>#

**********************************************************************
SECTION-4
**********************************************************************
MANUAL FIX: Editioning Views used in referential integrity constraints.
To fix these violations, remove the constraint or redefine it removing the
reference to the Editioning View.
Oracle recommends you perform the chosen fix by customizing template file
$AD_TOP/sql/ADZDPCUST.sql

no rows selected
DOC>
DOC>
DOC>
DOC>
ons
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>

**********************************************************************
SECTION-5
**********************************************************************
MANUAL FIX: Materialized Views must not depend on PLSQL Packages or Functi
- Matching materialized views will become INVALID if schema is enabled
for editions.
To fix these violations rewrite the Materialized View removing the PLSQL
function and replace it with a SQL join
Oracle recommends you perform the chosen fix by customizing template file

DOC> $AD_TOP/sql/ADZDPCUST.sql
DOC>
DOC>#
no rows selected
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>
DOC>#

**********************************************************************
SECTION-6
**********************************************************************
MANUAL FIX: Triggers defined on CLOB column are invalid
The EBS 12.2 upgrade has removed the use of LONG columns. All LONG columns
have been upgraded to CLOB columns. Triggers that reference a CLOB column
in the "UPDATE OF" clause will go invalid.
To Fix: Redefine the trigger removing CLOB type columns from the UPDATE OF
clause.

no rows selected
DOC> **********************************************************************
DOC> SECTION-7
DOC> **********************************************************************
DOC> MANUAL FIX: Synonyms from Unregistered schema(Editionable and Non-Editiona
ble)
DOC>
dependent on EBS tables
DOC>
DOC> Online Patching enablement moves synonyms from tables to editioning views.
DOC> The following synonyms are part of non-registered schemas therefore the
DOC> synonyms will not be moved. The synonyms in these schemas will not go
DOC> invalid, however you should register the schemas as all synoymns in 12.2 a
nd
DOC> beyond should point to Editioning Views and not Tables directly. Failure
to
DOC> register these schemas may result in SQL accessing obsolete columns.
DOC>
DOC> For each synonym reported below, please do one of the following:
DOC>
DOC>
- If the synonym should be retained and will continue to depend on
DOC>
EBS objects, then register the owning schema as a Custom EBS Schem
a.
DOC> Custom EBS Schemas will need to comply with new EBS Custom development
DOC>
standards. See the ADZDPCUST.sql template file for instructions
DOC>
on how to register custom schemas.
DOC>
- If the schema should be retained, but should not depend on EBS
DOC>
objects, then leave the schema unregistered and correct any
DOC>
object-level violations in the next phase of the readiness check.
DOC>
- If the owning schema is unused, drop it.
DOC>
DOC> Oracle recommends you perform the chosen fix by customizing template file
DOC> $AD_TOP/sql/ADZDPCUST.sql
DOC>
DOC>
DOC>#
PL/SQL procedure successfully completed.

no rows selected
DOC> **********************************************************************
DOC> SECTION-8
DOC> **********************************************************************
DOC> MANUAL FIX: Base Column Names may only use '#' as last character
DOC>
DOC> Online Patching uses the '#' character to indicate that a column has
DOC> been versioned. These columns will not show correctly when an
DOC> editioning view is created by the enablement process.
DOC>
DOC> For each column reported below, please do one of the following:
DOC>
DOC>
- If the column should be retained then is must be renamed
DOC>
DOC>
- If the column is no longer needed, then it should be dropped
DOC>
DOC> Oracle recommends you perform the chosen fix by customizing template file
DOC> $AD_TOP/sql/ADZDPCUST.sql
DOC>#
no rows selected
DOC> **********************************************************************
DOC> SECTION-9
DOC> **********************************************************************
DOC> A list of all E-biz schema objects that have non-existent dependencies
DOC>
DOC>#
no rows selected
DOC> ********************************* End ******************************
DOC>#