Transcription

1 It s here and online patching works great!! Oracle has released R12.2 in September 2013 long awaited release, oracle spent a lot of time in developing Online patching to avoid long downtime windows for upgrade We discussed about R12.2 VISION/DEMO install steps in past Blogs Now we will talk about Technical Upgrade steps and care to be taken during R12.2 upgrade We have performed this exercise in our Demo Environment and found upgrade steps are similar to 11i to R12.1 with the exception of Online patching enablement, We have taken basic R12.1.3/11gR2.03 Setup and upgraded to R12.2/11gR2.03 Reference: Oracle E-Business Suite Documentation Resources, Release 12.2 document (Doc ID: ) Oracle E-Business Suite Upgrade Guide Release 12.0 and 12.1 to 12.2 Part No E Oracle E-Business Suite Release Notes, Release 12.2 (Doc ID ) Oracle E-Business Suite Release Readme (Doc ID ) Online Patching Readiness Report in Oracle E-Business Suite Release 12.2 (Doc ID ) Applying the AD and TXK Release Update Pack (Doc ID ) Upgrade Planning: - Release 12.2 includes a re-packaged Rapid install that makes it possible to upgrade existing 12.0 (12.0.4, ) and 12.1(12.1.1, and ) systems directly to Release is minimum required RDBMS Version - CPU requirements for running Oracle E-Business Suite depend on, Number of concurrent users and their usage profiles Number of concurrent manager processes and the types of jobs that they are running Load for activities other than Oracle E-Business Suite Size of the database Desired response time - Minimum of 16GB memory is recommended by upgrade guide during assessment run - Online patching in R12.2 means significantly larger disk space requirement, approximately 70 GB for application File system Components: Technology Stack: For a new Release 12.2 installation, Rapid Install automatically installs and configures the required technology stack components for both the database tier and the application tier. On the database tier, the technology stack includes: Oracle Database 11g Release 2 ( ) On the application tier, the technology stack includes: Oracle Fusion Middleware 11g PS3 ( ) Oracle WebLogic Server 11g PS3 Oracle WebLogic JSP compiler Oracle FMW 11g Java Required Files (JRF) libraries (except the use of ADF and MDS 11g) Oracle WebLogic Portlet 11g PS3 Container

2 JRockit or JDK 6.0 Apache version 2.2 Oracle 10g (10.1.2) Applications Server for Oracle EBS Forms based Applications Web Services: The Web services component of Oracle Application Server processes requests received over the network from the desktop clients, and includes the following major components: Web Listener (Oracle HTTP Server powered by Apache) Java Servlet Engine (Oracle WebLogic Server, WLS) The Web listener component of the Oracle HTTP server accepts incoming HTTP requests (for particular URLs) from client browsers, and routes the requests to WLS. If possible, the Web server services the requests itself, for example by returning the HTML to construct a simple Web page. If the page referenced by the URL needs advanced processing, the listener passes the request on to the servlet engine, which contacts the database server as needed R12.2 Upgrade Tasks: Review Upgrade Tasks Database and System Administration Tasks Application DBA (AD) Tasks Applications Technology Tasks Prepare for the Upgrade 1. Back up database, Oracle E-Business Suite, and customizations (recommended): Note: Shut down the database with the NORMAL option. You may not be able to restore it from the backup if you use the IMMEDIATE or ABORT option. 2. Drop event alert triggers in custom schemas (conditional): To drop all event alert database triggers in custom schemas, run the alrdtrig.sql script, located in $ALR_TOP/patch/115/sql. Re-create the triggers after the upgrade is complete. 3. Review sizes of old and new tablespaces (required): 4. Migrate Existing Objects to New Tablespace Model (recommended): 5. Application DBA (AD) Tasks (Conditional) 6. Oracle Application Object Library: Ensure that the GUEST account is valid and active and that the fnd_user USER_ID for the GUEST account is set to a value of '6'. SQL> SELECT USER_ID FROM FND_USER WHERE USER_NAME = 'GUEST'; USER_ID Perform this task only if you are using Oracle Advanced Collections with Strategies. Strategy Workflow checks Applies to 12.0 and 12.1 release levels.

3 Apply the diagnostic scripts patch :R12.IEX.A when upgrading from R12.0.X and apply :R12.IEX.B when upgrading from 12.1.X. This patch contains scripts for Collection Strategy Workflow. From the Collections Agent responsibility using the user name 'SYSADMIN', stop any scheduled Workflow Background Process concurrent program request for the following Item Types: IEXSTRY - IEX: Collection Strategy Work Flow IEXSTFFM - IEX: Strategy Fulfilment Mailer IEXSTRCM - IEX: Strategy Custom Work Flow Run the script $IEX_TOP/patch/115/sql/iexswowf.sql to check and clean the strategies running without workflow. This script requires two parameters: FND username and Reponsibility for audit table and logs. For Example, you can run the script using the following: username: SYSADMIN responsibility: Collections Agent ***Patch applied as HOT*** 8. Subledger Accounting: <-- <-- (10/30/2013 SS) ***ATTENTION***ATTENTION -We need to Execute Script listed in README file **See execution below Perform this task if you are using Oracle Subledger Accounting. 1. Clean up Advance Queues from prior Create Accounting processes before enabling EBR. Applies to 12.0 and 12.1 release levels. Apply patch :R12.XLA.A when upgrading from Release 12.0.x and apply Patch :R12.XLA.B when upgrading from Release 12.1.x to clean up temporary advance queues that were created by prior Create Accounting program processes. Pending Advance Queues of completed Create Accounting processes do not create upgrade issues, but must be cleaned up for EBR. Note: You can perform this pre-upgrade step while the pre-upgrade system is online. ***Patch applied as HOT Patch*** a) Description 1. Problem Description Need a script to drop all the Advance queues created by Create accounting program. 2. Solution Description This patch delivers script xlaqclen.sql to STOP and DROP the Advance Queues from prior completed runs of Create Accounting program. Advance Queues of Create Accounting program were not dropped after program completion, if there were no accounting events processed by the program. These pending Advance Queues of already completed Create Accounting programs do not cause any corruption, however need to be cleaned up for EBR. This patch needs to be applied only by customers preparing for Oracle Applications release 12.2 upgrade. This patch is essential before enabling EBR

4 in Please refer to Oracle Applications release 12.2 release notes for more details on EBR. b) Fixed File Names and versions $xla/patch/115/sql/xlaqclen.sql Check $XLA_TOP/patch/115/sql/xlaqclen.sql strings -a $XLA_TOP/patch/115/sql/xlaqclen.sql grep '$Header' REM $Header: xlaqclen.sql /11/23 05:28:04 vdamerla noship $ Here is the details of the input values: The owner for QUEUE_TABLE = 'XLA_ACCOUNTING_QTAB is XLA. So value for 1 should be XLA The owner for FND_CONCURRENT_REQUESTS should be APPS. So value for 2 should be APPS sqlplus apps/apps SQL*Plus: Release Production on Wed Oct 30 20:29: Copyright (c) 1982, 2005, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options Enter value for 1: XLA Enter value for 2: APPS PL/SQL procedure successfully completed. Commit complete. Disconnected from Oracle Database 11g Enterprise Edition Release bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options 9. Human Resource Management (HRMS) All custom database objects that are mapped to seeded APIs/Row Handlers must be changed from LONG/LONG RAW to CLOB. SELECT package_name,object_name,argument_name,data_type FROM all_arguments WHERE (package_name,object_name) IN (SELECT call_package,call_procedure FROM hr_api_hook_calls ) AND data_type = 'LONG'; PACKAGE_NAME OBJECT_NAME ARGUMENT_NAME DATA_TYPE PSB_HR_POPULATE_DATA_PVT INSERT_POSITION_TXN_INFO P_COMMENTS LONG

5 select object_name, object_type, owner from dba_objects where object_name = 'PSB_HR_POPULATE_DATA_PVT'; OBJECT_NAME OBJECT_TYPE OWNER PSB_HR_POPULATE_DATA_PVT PACKAGE APPS PSB_HR_POPULATE_DATA_PVT PACKAGE BODY APPS I checked in VISION R instance select object_name, object_type, owner from dba_objects where object_name = 'PSB_HR_POPULATE_DATA_PVT'; no rows selected This means - we don't need to convert - it should be taken care of it while Upgrade process 10. Supply Chain Management Tasks The tasks in this section are required only if you are using Oracle Supply Chain Management products. Order Management: Perform these tasks if you are using Oracle Order Management. 1. Check for the Nullable Hold Entity ID. Applies to: Release 12.1 If you are upgrading from release 12.1, then you should check for the Nullable Hold Entity ID and fix it to NOT NULL. Carefully follow the instructions in the readme of Patch :R12.ONT.B. As seen below - in our R environment HOLD_ENTITY_CODE NOT NULL VARCHAR2(30) SQL> desc OE_HOLD_SOURCES_ALL Name Null? Type HOLD_SOURCE_ID NOT NULL NUMBER LAST_UPDATE_DATE NOT NULL DATE LAST_UPDATED_BY NOT NULL NUMBER LAST_UPDATE_LOGIN NUMBER CREATION_DATE NOT NULL DATE CREATED_BY NOT NULL NUMBER PROGRAM_APPLICATION_ID NUMBER PROGRAM_ID NUMBER PROGRAM_UPDATE_DATE DATE REQUEST_ID NUMBER HOLD_ID NOT NULL NUMBER HOLD_ENTITY_CODE NOT NULL VARCHAR2(30) HOLD_ENTITY_ID NOT NULL VARCHAR2(250) HOLD_ENTITY_CODE2 VARCHAR2(30)

6 HOLD_ENTITY_ID2 VARCHAR2(250) HOLD_UNTIL_DATE DATE RELEASED_FLAG NOT NULL VARCHAR2(1) HOLD_COMMENT VARCHAR2(2000) ORG_ID NUMBER CONTEXT VARCHAR2(30) ATTRIBUTE1 VARCHAR2(240) ATTRIBUTE2 VARCHAR2(240) ATTRIBUTE3 VARCHAR2(240) ATTRIBUTE4 VARCHAR2(240) ATTRIBUTE5 VARCHAR2(240) ATTRIBUTE6 VARCHAR2(240) ATTRIBUTE7 VARCHAR2(240) ATTRIBUTE8 VARCHAR2(240) ATTRIBUTE9 VARCHAR2(240) ATTRIBUTE10 VARCHAR2(240) ATTRIBUTE11 VARCHAR2(240) ATTRIBUTE12 VARCHAR2(240) ATTRIBUTE13 VARCHAR2(240) ATTRIBUTE14 VARCHAR2(240) ATTRIBUTE15 VARCHAR2(240) HOLD_RELEASE_ID NUMBER 11. Product Hub: - Checking for Duplicate Records Applies to: Release 12.0 and 12.1 Run the following query and verify the output: SELECT COUNT(1) FROM SYS.ALL_IND_COLUMNS WHERE INDEX_NAME = 'EGO_MTL_SY_ITEMS_EXT_B_U2' AND COLUMN_NAME = 'UNIQUE_VALUE' AND INDEX_OWNER = 'EGO'; SQL> SELECT COUNT(1) FROM SYS.ALL_IND_COLUMNS WHERE INDEX_NAME = 'EGO_MTL_SY_ITEMS_EXT_B_U2' AND COLUMN_NAME = 'UNIQUE_VALUE' AND INDEX_OWNER = 'EGO'; COUNT(1) If the above query returns '0' as the output, then perform the following steps: 1. Take backup of ego_mtl_sy_items_ext_b table 2. Refer to Note ID: and run the script provided in the 'Identification Script' column within the 'Solution - Datafix' section to identify duplicate records. If there are duplicate records, then run the scripts provided in the 'Fix' column within the 'Solution - Datafix' section for the appropriate base version to delete

7 duplicate records. Note: You must eliminate duplicate records before upgrading to Release If you require help eliminating duplicate records, then contact Oracle Support. REFER Duplicate User Defined Attribute (UDA) Records Created in EGO_MTL_SY_ITEMS_EXT_B (Doc ID ) b. For R12.1 and above releases, use the below query to identify the duplicate records: SELECT COUNT(*) AS v_count, inventory_item_id, organization_id, revision_id, attr_group_id, data_level_id, pk1_value, pk2_value FROM apps.ego_mtl_sy_items_ext_b a WHERE EXISTS (SELECT 1 FROM apps.ego_fnd_dsc_flx_ctx_ext b WHERE a.attr_group_id = b.attr_group_id AND application_id = 431 AND multi_row <> 'Y') GROUP BY inventory_item_id, organization_id, revision_id, attr_group_id, data_level_id, pk1_value, pk2_value HAVING COUNT(*) > 1; no rows selected 12. Submitted - Request -Gather Schema Statistics (Keep % Field Blank) To Check which objects or tables are locked SELECT OWNER,TABLE_NAME,STATTYPE_LOCKED FROM DBA_TAB_STATISTICS WHERE STATTYPE_LOCKED IS NOT NULL; TO Unlock all the tables in a schema at once : exec dbms_stats.unlock_schema_stats('schema_owner'); e.g : sql> exec dbms_stats.unlock_schema_stats('applsys'); Following SQL should have returned one row, not two. select a.column_name, nvl(a.hsize,254) hsize from FND_HISTOGRAM_COLS a

8 where table_name = 'JE_BE_LINE_TYPE_MAP' order by column_name; COLUMN_NAME HSIZE SOURCE 254 SOURCE 254 Column does not exist on the table but still listed in FND_HISTOGRAMS_COL table. Solution: Find out all duplicates and/or obsolete rows in FND_HISTOGRAM_COLS and delete one of them. Remember to take backup of the FND_HISTOGRAM_COLS table before deleting any data. -- identify duplicate rows select table_name, column_name, count(*) from FND_HISTOGRAM_COLS group by table_name, column_name having count(*) > 1; -- Use above results on the following SQL to delete duplicates delete from FND_HISTOGRAM_COLS where table_name = '&TABLE_NAME' and column_name = '&COLUMN_NAME' and rownum=1; <-- Performed above to remove Duplicate value SQL> select table_name, column_name, count(*) from FND_HISTOGRAM_COLS group by table_name, column_name having count(*) > 1; no rows selected Re Run GSS Completed Successfully 13. Install JRE on the database tier (conditional) If you are planning to run Rapid Install in Upgrade Mode by using the Use Existing ORACLE HOME option, then you must install JRE in the Database ORACLE_HOME as follows: Download the latest JRE 6.0 Update. For optimum stability, performance, scalability, and OS vendor support, use the latest available update of JRE for the Oracle E-Business Suite database tier. The JRE download location is: Note: Do not download the Java SE Development Kit (JDK). To download platform specific JRE and additional information on installation, refer to Using Latest Java 6.0 Update With Oracle E-Business Suite Release 12 (Doc ID ). cd jre/bin./java -version

9 java version "1.6.0_17" Java(TM) SE Runtime Environment (build 1.6.0_17-b04) Java HotSpot(TM) 64-Bit Server VM (build 14.3-b01, mixed mode) 14. Reset init.ora parameters (required) Follow the instructions in Database Initialization Parameters for Oracle E-Business Suite Release 12.2 and reset the init.ora parameters as needed. Review the requirements for database initialization parameters before you begin. See Database Initialization Parameters for Oracle E-Business Suite Release 12 (Doc ID ). Additional Database Initialization Parameters For Oracle E-Business Suite Release 12.2 recyclebin=off service_names=%s_dbsid%,ebs_patch local_listener=%s_dbsid%_local Added followings in init.ora file ###Addition as part of R Upgrade # # # SERVICE_NAMES specifies one or more names by which clients can connect to the # instance. The instance registers its service names with the listener. When a # client requests a service, the listener determines which instances offer the # requested service and routes the client to the appropriate instance. # service_names=tr122i,ebs_patch ######### # # recyclebin parameter # # The Online patching infrastructure requires that the database recyclebin is turned off # in order to to perform the cleanup phase with out having to connect as SYS each time. # This feature may still be used at other times. # ######### recyclebin=off **Restart database SQL> shutdown immediate; Database closed. Database dismounted. ORACLE instance shut down.

10 SQL> startup; ORACLE instance started. Total System Global Area bytes Fixed Size bytes Variable Size bytes Database Buffers bytes Redo Buffers bytes Database mounted. Database opened. SQL> show parameter recyclebin NAME TYPE VALUE recyclebin string off SQL> show parameter service_names NAME TYPE VALUE service_names string TR122I, ebs_patch SQL> show parameter local_listener NAME TYPE VALUE local_listener string TR122I_LOCAL 15. Migrate or Upgrade Your Database to Oracle 11g Release 2 (required) is minimum requirement for R12.2 Follow the instructions in Database Preparation Guidelines for an Oracle E-Business Suite Release 12.2 Upgrade (Doc ID: ). Note: In performing the upgrade to 12.2 from 11i or 12.0/12.1, ensure you have the latest Rapid Install patch (or startcd patch) before you begin your upgrade. This document assumes that the startcd version is 46 or higher. Path B: Standard 12.2 Upgrade Path for customers already on /12.0/12.1 with 11gR2 ( ) (Refer ) Path B similarly follows the 12.2 upgrade path as documented in the Oracle E-Business Suite Upgrade Guide: Release 11i to Release 12.2 and Oracle E-Business Suite Upgrade Guide: Release 12.0 and 12.1 to Release Rapid Install to install the applications technology stack which also includes a Oracle Home. We will not use this Oracle Home for the upgrade since we have already upgraded to prior to doing the R12 upgrade and would be using existing Database Oracle Home.

11 We picked the 'Use Existing Oracle Home' in the Database node configuration window of Rapid Install and pick the existing database. 16. Prior to running Rapid Install in Chapter 2 ('Preparing for the Upgrade') of the Upgrade Guide, apply database patches to the existing 11g Oracle Home and perform all tasks documented in the patch readmes as noted below, before continuing with installing the new application tier with Rapid Install and the standard R12 upgrade process. For all platforms, the following patches must be downloaded from My Oracle Support's 'Patches and Updates' tab and applied in the following order after reviewing and following all the steps in the README files associated with them: REFER Database Preparation Guidelines for an E-Business Suite Release 12.2 Upgrade (Doc ID ) ((a)) Patch Please remove the contents of $ORACLE_HOME/OPatch directory (Please do not remove $ORACLE_HOME/OPatch directory itself) <-- This is Wrong - We needed to rename OPatch directory from $ORACLE_HOME and unzip p _112000_linux-x86-64.zip in $ORACLE_HOME <-- this will create OPatch directory in $ORACLE_HOME cd $ORACLE_HOME/OPatch./opatch version OPatch Version: OPatch succeeded. ((b)) (Bundle Patch) export PATH=$PATH:$ORACLE_HOME/OPatch (1) Ensure that you also meet the DST-specific prerequisites described in My Oracle Support note ** select * from v$timezone_file; FILENAME VERSION timezlrg_10.dat 10 SQL> SELECT version FROM v$timezone_file; VERSION Download Scripts to automatically update the RDBMS DST (timezone) version in an 11gR2 or 12cR1 database. (Doc ID ) DBMS_DST_scriptsV1.3.zip

12 sqlplus / as sysdba SQL*Plus: Release Production on Thu Oct 31 16:32: Copyright (c) 1982, 2011, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options INFO: Starting with RDBMS DST update preparation. INFO: NO actual RDBMS DST update will be done by this script. INFO: If an ERROR occurs the script will EXIT sqlplus. INFO: Database version is INFO: Database RDBMS DST version is DSTv10. INFO: Doing checks for known issues... INFO: No known issues detected. INFO: Now detecting new RDBMS DST version. A prepare window has been successfully started. INFO: Newest RDBMS DST version detected is DSTv14. INFO: Next step is checking all TSTZ data. INFO: It might take a while before any further output is seen... A prepare window has been successfully ended. INFO: A newer RDBMS DST version than the one currently used is found. INFO: Note that NO DST update was yet done. INFO: Now run upg_tzv_apply.sql to do the actual RDBMS DST update. INFO: Note that the upg_tzv_apply.sql script will INFO: restart the database 2 times WITHOUT any confirmation or prompt. INFO: If an ERROR occurs the script will EXIT sqlplus. INFO: The database RDBMS DST version will be updated to DSTv14. WARNING: This script will restart the database 2 times WARNING: WITHOUT asking ANY confirmation. WARNING: Hit control-c NOW if this is not intended. INFO: Restarting the database in UPGRADE mode to start the DST upgrade. Database closed. Database dismounted. ORACLE instance shut down. ORACLE instance started. Total System Global Area bytes Fixed Size bytes Variable Size bytes Database Buffers bytes Redo Buffers bytes Database mounted.

13 Database opened. INFO: Starting the RDBMS DST upgrade. INFO: Upgrading all SYS owned TSTZ data. INFO: It might take time before any further output is seen... An upgrade window has been successfully started. INFO: Restarting the database in NORMAL mode to upgrade non-sys TSTZ data. Database closed. Database dismounted. ORACLE instance shut down. ORACLE instance started. Total System Global Area bytes Fixed Size bytes Variable Size bytes Database Buffers bytes Redo Buffers bytes Database mounted. Database opened. INFO: Upgrading all non-sys TSTZ data. INFO: It might take time before any further output is seen... INFO: Do NOT start any application yet that uses TSTZ data! INFO: Next is a list of all upgraded tables: Table list: "ASO"."AQ$_ASO_ORDER_FEEDBACK_T_S" Table list: "OKC"."AQ$_OKC_AQ_EV_TAB_S" Table list: "AR"."AQ$_AR_REV_REC_QT_S" Table list: "XNP"."AQ$_XNP_OUT_MSG_QTAB_S" Table list: "CS"."AQ$_CS_SERVICE_REQUEST_OQT_S" Table list: "CS"."AQ$_CS_SERVICE_REQUEST_IQT_S" Table list: "APPLSYS"."AQ$_WF_DEFERRED_TABLE_M_S" Table list: "APPLSYS"."AQ$_WF_DEFERRED_S" Table list: "APPLSYS"."AQ$_WF_ERROR_S" Table list: "APPLSYS"."AQ$_WF_REPLAY_OUT_S" Table list: "APPLSYS"."AQ$_WF_IN_S" Table list: "APPLSYS"."AQ$_WF_OUT_S" Table list: "APPLSYS"."AQ$_WF_REPLAY_IN_S"

14 Table list: "APPLSYS"."AQ$_WF_JMS_IN_S" Table list: "APPLSYS"."AQ$_WF_JMS_OUT_S" Table list: "APPLSYS"."AQ$_WF_CONTROL_S" Table list: "APPLSYS"."AQ$_WF_NOTIFICATION_IN_S" Table list: "APPLSYS"."AQ$_WF_NOTIFICATION_OUT_S" Table list: "APPLSYS"."AQ$_WF_WS_JMS_IN_S" Table list: "APPLSYS"."AQ$_WF_JAVA_DEFERRED_S" Table list: "APPLSYS"."AQ$_WF_JAVA_ERROR_S" Table list: "APPLSYS"."AQ$_WF_WS_JMS_OUT_S" Table list: "APPLSYS"."AQ$_WF_JMS_JMS_OUT_S" Table list: "APPLSYS"."AQ$_WF_WS_SAMPLE_S" Table list: "APPLSYS"."AQ$_FND_CP_GSM_OPP_AQTBL_S" Table list: "APPLSYS"."AQ$_FND_CP_TM_RET_AQTBL_S" Table list: "APPLSYS"."AQ$_FND_CP_TM_AQTBL_S" Table list: "AR"."AQ$_HZ_JMS_OUT_S" Table list: "PO"."AQ$_PO_OTM_OUT_S" Table list: "APPS"."AQ$_WF_BPEL_QTAB_S" Table list: "DEV_SOAINFRA"."MEDIATOR_CONTAINERID_LEASE" Table list: "DEV_SOAINFRA"."AQ$_IP_QTAB_S" Table list: "DEV_SOAINFRA"."AQ$_EDN_EVENT_QUEUE_TABLE_S" Table list: "DEV_SOAINFRA"."AQ$_EDN_OAOO_DELIVERY_TABLE_S" Table list: "AR"."AQ$_AR_REV_REC_QT_L" Table list: "ASO"."AQ$_ASO_ORDER_FEEDBACK_T_L" Table list: "PO"."AQ$_PO_OTM_OUT_L"

15 Table list: "XNP"."AQ$_XNP_OUT_MSG_QTAB_L" Table list: "APPS"."AQ$_WF_BPEL_QTAB_L" Table list: "OKC"."AQ$_OKC_AQ_EV_TAB_L" Table list: "CS"."AQ$_CS_SERVICE_REQUEST_OQT_L" Table list: "CS"."AQ$_CS_SERVICE_REQUEST_IQT_L" Table list: "APPLSYS"."AQ$_WF_DEFERRED_TABLE_M_L" Table list: "APPLSYS"."AQ$_WF_DEFERRED_L" Table list: "APPLSYS"."AQ$_WF_ERROR_L" Table list: "APPLSYS"."AQ$_WF_REPLAY_OUT_L" Table list: "APPLSYS"."AQ$_WF_IN_L" Table list: "APPLSYS"."AQ$_WF_OUT_L" Table list: "APPLSYS"."AQ$_WF_REPLAY_IN_L" Table list: "APPLSYS"."AQ$_WF_JMS_IN_L" Table list: "APPLSYS"."AQ$_WF_JMS_OUT_L" Table list: "APPLSYS"."AQ$_WF_CONTROL_L" Table list: "APPLSYS"."AQ$_WF_NOTIFICATION_IN_L" Table list: "APPLSYS"."AQ$_WF_NOTIFICATION_OUT_L" Table list: "APPLSYS"."AQ$_WF_WS_JMS_IN_L" Table list: "APPLSYS"."AQ$_WF_JAVA_DEFERRED_L" Table list: "APPLSYS"."AQ$_WF_JAVA_ERROR_L" Table list: "APPLSYS"."AQ$_WF_WS_JMS_OUT_L" Table list: "APPLSYS"."AQ$_WF_JMS_JMS_OUT_L" Table list: "APPLSYS"."AQ$_WF_WS_SAMPLE_L" Table list: "DEV_SOAINFRA"."AQ$_IP_QTAB_L"

16 Table list: "APPLSYS"."AQ$_FND_CP_GSM_OPP_AQTBL_L" Table list: "APPLSYS"."AQ$_FND_CP_TM_RET_AQTBL_L" Table list: "APPLSYS"."AQ$_FND_CP_TM_AQTBL_L" Table list: "AR"."AQ$_HZ_JMS_OUT_L" Table list: "DEV_SOAINFRA"."AQ$_EDN_EVENT_QUEUE_TABLE_L" Table list: "DEV_SOAINFRA"."AQ$_EDN_OAOO_DELIVERY_TABLE_L" Table list: "APPLSYS"."AQ$_FND_SOA_JMS_IN_S" Table list: "APPLSYS"."AQ$_FND_SOA_JMS_IN_L" Table list: "APPLSYS"."AQ$_FND_SOA_JMS_OUT_S" Table list: "APPLSYS"."AQ$_FND_SOA_JMS_OUT_L" Table list: "APPLSYS"."AQ$_FND_CP_GSM_IPC_AQTBL_S" Table list: "APPLSYS"."AQ$_FND_CP_GSM_IPC_AQTBL_L" Table list: "APEX_040100"."WWV_FLOW_WORKSHEET_NOTIFY" Table list: "APEX_040100"."WWV_FLOW_FEEDBACK" Table list: "APEX_040100"."WWV_FLOW_FEEDBACK_FOLLOWUP" Table list: "APEX_040100"."WWV_FLOW_DEBUG_MESSAGES" Table list: "APEX_040100"."WWV_FLOW_DEBUG_MESSAGES2" INFO: Total failures during update of TSTZ data: 0. An upgrade window has been successfully ended. INFO: Your new Server RDBMS DST version is DSTv14. INFO: The RDBMS DST update is successfully finished. INFO: Make sure to exit this sqlplus session. INFO: Do not use it for timezone related selects. SQL> select * from v$timezone_file; FILENAME VERSION timezlrg_14.dat 14 1 row selected. SQL> SELECT version FROM v$timezone_file;

17 VERSION row selected. (2) Pre Installation Note: Perform this instruction ONLY if patch for fix is applied previously. (3) Installation cd /u01/app/orati/patches/ opatch napply -skip_subset -skip_duplicate ***Snippet's from above patch session 801, , , , , , , , , , , , , , , , , , , , , , , , Checking skip_subset Conflicts/Supersets for each patch are: Patch : Bug Superset of Super set bugs are: OPatch found that the following patches are not required. They are either subset of the patches in Oracle Home (or) subset of the patches in the given list (or) duplicate : Patches [ ] will be rolled back. Do you want to proceed? [y n] y User Responded with: Y OPatch continues with these patches:

18 Do you want to proceed? [y n] y User Responded with: Y All checks passed. Provide your address to be informed of security issues, install and initiate Oracle Configuration Manager. Easier for you if you use your My Oracle Support address/user Name. Visit for details. address/user Name: You have not provided an address for notification of security issues. Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: Y Please shutdown Oracle instances running out of this ORACLE_HOME on the local system. (Oracle Home = '/u01/app/orati/tr122i/db/tech_st/ ') Is the local system ready for patching? [y n] y Patching component oracle.rdbms.rsf, Verifying the update... Applying interim patch ' ' to OH '/u01/app/orati/tr122i/db/tech_st/ ' Patching component oracle.rdbms, Verifying the update... Patches , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , successfully applied. OPatch Session completed with warnings. Log file location: /u01/app/orati/tr122i/db/tech_st/ /cfgtoollogs/opatch/opatch _ pm_1.log OPatch completed with warnings.

19 ***Found following error which can be ignore*** [Oct 31, :59:32 PM] OPatch failed to configure Oracle Configuration Manager in "/u01/app/orati/tr122i/db/tech_st/ ". Please refer log file for details. AND [Oct 31, :02:05 PM] UtilSession: N-Apply done. [Oct 31, :02:05 PM] [Oct 31, :02:05 PM] The following warnings have occurred during OPatch execution: [Oct 31, :02:05 PM] 1) OUI-67302: OPatch found that the following patches are not required. They are either subset of the patches in Oracle Home (or) subset of the patches in the given list (or) duplicate : [Oct 31, :02:05 PM] 2) OUI-67303: Patches [ ] will be rolled back. [Oct 31, :02:05 PM] [Oct 31, :02:05 PM] OUI-67008:OPatch Session completed with warnings. [Oct 31, :02:05 PM] Finishing UtilSession at Thu Oct 31 17:02:05 EDT 2013 (4)Post installation After you install the patch, reload the packages into the Oracle Database. change directory to $ORACLE_HOME/rdbms/admin and then connect as SYSDBA and run the following in given order : SQL> startup; ORACLE instance started. Total System Global Area bytes Fixed Size bytes Variable Size bytes Database Buffers bytes Redo Buffers bytes Database mounted. Database opened. cd /u01/app/orati/tr122i/db/tech_st/ /rdbms/admin Note : Below steps must be executed in the order they appear in. SQL> spool catbundle out EBS apply PL/SQL procedure successfully completed.

20 11 'Patch 3'); 1 row created. SQL> COMMIT; Commit complete. SQL> SPOOL off SQL> SET echo off Check the following log file for errors: /u01/app/orati/tr122i/db/tech_st/ /cfgtoollogs/catbundle/catbundle_ebs_tr122i_app LY_2013Oct31_17_23_15.log <-- 5 Seconds or less PL/SQL procedure successfully completed. SQL> spool off Note: If XDB is installed the it is required to run "catmetx.sql" script also. SQL> ALTER SESSION SET CURRENT_SCHEMA=CTXSYS; SQL> ALTER SESSION SET CURRENT_SCHEMA=SYS; SQL> execute sys.dbms_metadata_util.load_stylesheets; -- recompile dbms_metadata_int to enable the diffing code SQL> alter package dbms_metadata_int compile plsql_ccflags = 'ku$xml_enabled:true'; -- recompile dbms_metadata_util to enable the xmlschema load code SQL> alter package dbms_metadata_util compile plsql_ccflags = 'ku$xml_enabled:true'; If script 'fixtza.sql' terminates in any way other than printing the message ######################################################## Bug is in fact present, so this patch is needed Proceed by restarting the database and running script fixtzb ######################################################## (followed by a few lines that do not contain ###) inspect the output to determine whether the script was either incorrectly run or the bug is in fact not present. If the latter, take no further action. If the former, correct the indicated condition and rerun the fixtza script. shutdown and startup database using startup migrate. connect as SYS and run script : If it terminates in any way other than printing the message ########################################################

21 Bug is no longer present. Patch succeeded. ######################################################## (followed by a few lines that do not contain ###) inspect the output to determine what was done incorrectly and retry as indicated. restart the database without startup migrate. ***I received following message*** ######################################################## Bug is in fact present, so this patch is needed Proceed by restarting the database and running script fixtzb ######################################################## PL/SQL procedure successfully completed. SQL> SQL> spool off SQL> shutdown; Database closed. Database dismounted. ORACLE instance shut down. SQL> startup migrate; ORACLE instance started. Total System Global Area bytes Fixed Size bytes Variable Size bytes Database Buffers bytes Redo Buffers bytes Database mounted. Database opened. **Output Testing various timezone DST attributes ######################################################## Bug is no longer present. Patch succeeded. ######################################################## PL/SQL procedure successfully completed. SQL> SQL> begin 2 initjvmaux.drp('drop java source fixtz');

22 3 initjvmaux.drp('drop package fixtz'); 4 end; 5 / drop java source fixtz drop package fixtz PL/SQL procedure successfully completed. SQL> SQL> spool off SQL> SQL> shutdown; Database closed. Database dismounted. ORACLE instance shut down. SQL> startup; ORACLE instance started. Total System Global Area bytes Fixed Size bytes Variable Size bytes Database Buffers bytes Redo Buffers bytes Database mounted. Database opened. SQL> ((c)) Patch export PATH=$PATH:$ORACLE_HOME/OPatch cd /u01/app/orati/patches/ opatch apply Verifying the update... Patch successfully applied OPatch Session completed with warnings. Log file location: /u01/app/orati/tr122i/db/tech_st/ /cfgtoollogs/opatch/ _oct_31_2013_18_2 5_51/apply _ PM_1.log OPatch completed with warnings. **Warning as below Can be skipped [Oct 31, :26:23 PM] Patch successfully applied [Oct 31, :26:23 PM] The following warnings have occurred during OPatch execution: [Oct 31, :26:23 PM] 1) OUI-67634: The following patch(es) are already installed in the Oracle Home. [ ]

23 You have already installed earlier versions of the above patch(es). OPatch would rollback the patches and re-apply the later ones. ((d)) Patch cd /u01/app/orati/patches/ opatch apply Verifying the update... Patch successfully applied Log file location: /u01/app/orati/tr122i/db/tech_st/ /cfgtoollogs/opatch/ _oct_31_2013_18_3 0_22/apply _ PM_1.log OPatch succeeded. ((e)) Patch cd /u01/app/orati/patches/ opatch apply Patching component oracle.rdbms, Verifying the update... Patch successfully applied Log file location: /u01/app/orati/tr122i/db/tech_st/ /cfgtoollogs/opatch/ _oct_31_2013_18_3 2_12/apply _ PM_1.log OPatch succeeded. ((f)) Patch cd /u01/app/orati/patches/ opatch apply Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: Y Backing up files... Patching component oracle.rdbms.dbscripts, Verifying the update... Patch successfully applied Log file location: /u01/app/orati/tr122i/db/tech_st/ /cfgtoollogs/opatch/ _oct_31_2013_18_3 5_59/apply _ PM_1.log OPatch succeeded.

24 ***Now startup for Post Step*** SQL> startup; ORACLE instance started. Total System Global Area bytes Fixed Size bytes Variable Size bytes Database Buffers bytes Redo Buffers bytes Database mounted. Database opened. Calling rdbms/admin/catprc.sql on 31-OCT PM -04: Comment created. SQL> ((g)) Patch cd /u01/app/orati/patches/ opatch apply Patching component oracle.rdbms.rsf, Patching component oracle.nlsrtl.rsf, Patching component oracle.nlsrtl.rsf.ic, Verifying the update... Patch successfully applied Log file location: /u01/app/orati/tr122i/db/tech_st/ /cfgtoollogs/opatch/ _oct_31_2013_18_3 9_21/apply _ PM_1.log OPatch succeeded. ((h)) Patch cd /u01/app/orati/patches/ opatch apply

25 Patching component oracle.rdbms, Verifying the update... Patch successfully applied Log file location: /u01/app/orati/tr122i/db/tech_st/ /cfgtoollogs/opatch/ _oct_31_2013_18_4 1_35/apply _ PM_1.log OPatch succeeded. ((i)) Patch cd /u01/app/orati/patches/ opatch apply Patching component oracle.rdbms.dbscripts, Verifying the update... Patch successfully applied Log file location: /u01/app/orati/tr122i/db/tech_st/ /cfgtoollogs/opatch/ _oct_31_2013_18_4 3_43/apply _ PM_1.log OPatch succeeded. ***Now startup for Post Step*** SQL> startup; ORACLE instance started. Total System Global Area bytes Fixed Size bytes Variable Size bytes Database Buffers bytes Redo Buffers bytes Database mounted. Database opened. System altered. System altered. PL/SQL procedure successfully completed. Procedure dropped.

26 ((j)) Patch <-- This patch is defective - We should download and apply Patch : PL/SQL COMPILATION THROWS ERROR ORA-4063 instead ((GO TO NEXT PATCH)) Patch PL/SQL COMPILATION THROWS ERROR ORA-4063 <-- Can be applied in Online Mode cd /u01/app/orati/patches/ opatch prereq CheckConflictAgainstOHWithDetail -ph./ Oracle Interim Patch Installer version Copyright (c) 2013, Oracle Corporation. All rights reserved. PREREQ session Oracle Home : /u01/app/orati/tr122i/db/tech_st/ Central Inventory : /u01/orainventory from : /u01/app/orati/tr122i/db/tech_st/ /orainst.loc OPatch version : OUI version : Log file location : /u01/app/orati/tr122i/db/tech_st/ /cfgtoollogs/opatch/opatch _ pm_1.log Invoking prereq "checkconflictagainstohwithdetail" Prereq "checkconflictagainstohwithdetail" passed. OPatch succeeded. opatch apply OPatch found the word "warning" in the stderr of the make command. Please look at this stderr. You can re-run this make command. Stderr output: ins_precomp.mk:19: warning: overriding commands for target `pcscfg.cfg' /u01/app/orati/tr122i/db/tech_st/ /precomp/lib/env_precomp.mk:2160: warning: ignoring old commands for target `pcscfg.cfg' /u01/app/orati/tr122i/db/tech_st/ /precomp/lib/ins_precomp.mk:19: warning: overriding commands for target `pcscfg.cfg' /u01/app/orati/tr122i/db/tech_st/ /precomp/lib/env_precomp.mk:2160: warning: ignoring old commands for target `pcscfg.cfg' Verifying the update... Patch successfully applied OPatch Session completed with warnings.

27 Log file location: /u01/app/orati/tr122i/db/tech_st/ /cfgtoollogs/opatch/ _oct_31_2013_18_5 6_10/apply _ PM_1.log OPatch completed with warnings. ***Warnings as below*** [Oct 31, :56:42 PM] The following warnings have occurred during OPatch execution: [Oct 31, :56:42 PM] 1) OUI-67215: OPatch found the word "warning" in the stderr of the make command. Please look at this stderr. You can re-run this make command. Stderr output: ins_precomp.mk:19: warning: overriding commands for target `pcscfg.cfg' /u01/app/orati/tr122i/db/tech_st/ /precomp/lib/env_precomp.mk:2160: warning: ignoring old commands for target `pcscfg.cfg' /u01/app/orati/tr122i/db/tech_st/ /precomp/lib/ins_precomp.mk:19: warning: overriding commands for target `pcscfg.cfg' /u01/app/orati/tr122i/db/tech_st/ /precomp/lib/env_precomp.mk:2160: warning: ignoring old commands for target `pcscfg.cfg' [Oct 31, :56:42 PM] [Oct 31, :56:42 PM] OUI-67008:OPatch Session completed with warnings. ***Opatch warning: overriding commands for target xxxx (Doc ID ) (Above can be ignore) ((k)) Patch CLEAN UP OBSOLETE ORACLE/QSMA SYNONYMS FROM DB 11.2 <-- Has to be Offline Mode cd /u01/app/orati/patches/ opatch apply Backing up files... Patching component oracle.rdbms.dbscripts, Verifying the update... Patch successfully applied Log file location: /u01/app/orati/tr122i/db/tech_st/ /cfgtoollogs/opatch/ _oct_31_2013_19_0 0_08/apply _ PM_1.log OPatch succeeded. Post installation

28 There is no post installation for this patch as a sql only gets executed during an upgrade process, it is not a script that would be executed in any other context. The database would need to be in upgrade mode. ((l)) Patch MERGE REQUEST ON TOP OF FOR BUGS <- - Has to be Offline Mode cd /u01/app/orati/patches/ opatch apply OPatch back to application of the patch ' ' after auto-rollback. Patching component oracle.ctx, Patching component oracle.ctx.rsf, Patching component oracle.rdbms, Verifying the update... Patch successfully applied Log file location: /u01/app/orati/tr122i/db/tech_st/ /cfgtoollogs/opatch/ _oct_31_2013_19_0 2_26/apply _ PM_1.log OPatch succeeded. ((m)) Patch CLEAN UP OBSOLETE ORACLE/QSMA SYNONYMS POST INSTALL SCRIPT <- - Has to be Offline Mode and this one has Post Step cd /u01/app/orati/patches/ opatch apply User Responded with: Y Backing up files... Patching component oracle.rdbms.dbscripts, Verifying the update... Patch successfully applied Log file location: /u01/app/orati/tr122i/db/tech_st/ /cfgtoollogs/opatch/ _oct_31_2013_19_0 4_50/apply _ PM_1.log OPatch succeeded. ***Now startup for Post Step*** SQL> startup; ORACLE instance started.

29 Total System Global Area bytes Fixed Size bytes Variable Size bytes Database Buffers bytes Redo Buffers bytes Database mounted. Database opened. SQL> SQL> SQL> Rem Display any QSMA synonyms currently present. There should be no synonyms now. SQL> Rem SQL> SELECT synonym_name FROM dba_synonyms WHERE lower(synonym_name) LIKE '%qsma%'; no rows selected SQL> SQL> Rem =============================== SQL> Rem End Drop SQL Advisor Synonyms SQL> Rem =============================== SQL> SQL> SQL> SQL> Restarted Database SQL> shutdown; Database closed. Database dismounted. ORACLE instance shut down. SQL> startup; ORACLE instance started. Total System Global Area bytes Fixed Size bytes Variable Size bytes Database Buffers bytes Redo Buffers bytes Database mounted. Database opened. SQL> exit

30 REFER Database Preparation Guidelines for an E-Business Suite Release 12.2 Upgrade (Doc ID ) Run post-install steps for Database Patches In addition to performing all the post install steps mentioned in the READMEs of patches listed in Step 2, additional post install steps for the following patches need to be performed: a) Run the command: $ perl $OH/nls/data/old/cr9idata.pl cd /u01/app/orati/tr122i/db/tech_st/ /nls/data/old perl cr9idata.pl perl cr9idata.pl Directory /u01/app/orati/tr122i/db/tech_st/ /nls/data/9idata already exist. Overwriting... Copying files to /u01/app/orati/tr122i/db/tech_st/ /nls/data/9idata... Copy finished. Please reset environment variable ORA_NLS10 to /u01/app/orati/tr122i/db/tech_st/ /nls/data/9idata! echo $ORA_NLS10 /u01/app/orati/tr122i/db/tech_st/ /nls/data/9idata b) Perform DST upgrade steps as outlined in Steps 3 and 4 of the My Oracle Support Knowledge Document ('Updating the RDBMS DST version in 11g Release 2 ( and up) using DBMS_DST') due to the inclusion of the DST patch in the ((n))bundle Patch As per Updated DST transitions and new Time Zones in Oracle Time Zone File patches (Doc ID ) Latest DST Patch is 21 (Version 21 - tzdata2013e update - patch * patch ) ((o))patch cd /u01/app/orati/patches/ opatch apply Oracle Interim Patch Installer version Copyright (c) 2013, Oracle Corporation. All rights reserved. Oracle Home : /u01/app/orati/tr122i/db/tech_st/ Central Inventory : /u01/orainventory from : /u01/app/orati/tr122i/db/tech_st/ /orainst.loc OPatch version : OUI version :

31 Log file location : /u01/app/orati/tr122i/db/tech_st/ /cfgtoollogs/opatch/ _oct_31_2013_21_5 2_14/apply _ PM_1.log Applying interim patch ' ' to OH '/u01/app/orati/tr122i/db/tech_st/ ' Verifying environment and performing prerequisite checks... All checks passed. Provide your address to be informed of security issues, install and initiate Oracle Configuration Manager. Easier for you if you use your My Oracle Support address/user Name. Visit for details. address/user Name: You have not provided an address for notification of security issues. Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: Y Backing up files... Patching component oracle.oracore.rsf, Verifying the update... Patch successfully applied Log file location: /u01/app/orati/tr122i/db/tech_st/ /cfgtoollogs/opatch/ _oct_31_2013_21_5 2_14/apply _ PM_1.log OPatch succeeded. POST STEP TO GET DB UPDATED FOR LATEST DST (21) REFER Scripts to automatically update the RDBMS DST (timezone) version in an 11gR2 or 12cR1 database. (Doc ID ) cd /u01/app/orati/patches sqlplus / as sysdba SQL*Plus: Release Production on Thu Oct 31 21:55: Copyright (c) 1982, 2011, Oracle. All rights reserved. Connected to an idle instance. SQL> startup; ORACLE instance started. Total System Global Area bytes Fixed Size bytes

32 Variable Size bytes Database Buffers bytes Redo Buffers bytes Database mounted. Database opened. INFO: Starting with RDBMS DST update preparation. INFO: NO actual RDBMS DST update will be done by this script. INFO: If an ERROR occurs the script will EXIT sqlplus. INFO: Database version is INFO: Database RDBMS DST version is DSTv14. INFO: Doing checks for known issues... INFO: No known issues detected. INFO: Now detecting new RDBMS DST version. A prepare window has been successfully started. INFO: Newest RDBMS DST version detected is DSTv21. INFO: Next step is checking all TSTZ data. INFO: It might take a while before any further output is seen... A prepare window has been successfully ended. INFO: A newer RDBMS DST version than the one currently used is found. INFO: Note that NO DST update was yet done. INFO: Now run upg_tzv_apply.sql to do the actual RDBMS DST update. INFO: Note that the upg_tzv_apply.sql script will INFO: restart the database 2 times WITHOUT any confirmation or prompt. SQL> INFO: If an ERROR occurs the script will EXIT sqlplus. INFO: The database RDBMS DST version will be updated to DSTv21. WARNING: This script will restart the database 2 times WARNING: WITHOUT asking ANY confirmation. WARNING: Hit control-c NOW if this is not intended. INFO: Restarting the database in UPGRADE mode to start the DST upgrade. Database closed. Database dismounted. ORACLE instance shut down. ORACLE instance started. Total System Global Area bytes Fixed Size bytes Variable Size bytes Database Buffers bytes Redo Buffers bytes Database mounted. Database opened. INFO: Starting the RDBMS DST upgrade. INFO: Upgrading all SYS owned TSTZ data. INFO: It might take time before any further output is seen...

33 An upgrade window has been successfully started. INFO: Restarting the database in NORMAL mode to upgrade non-sys TSTZ data. Database closed. Database dismounted. ORACLE instance shut down. ORACLE instance started. Total System Global Area bytes Fixed Size bytes Variable Size bytes Database Buffers bytes Redo Buffers bytes Database mounted. Database opened. INFO: Upgrading all non-sys TSTZ data. INFO: It might take time before any further output is seen... INFO: Do NOT start any application yet that uses TSTZ data! INFO: Next is a list of all upgraded tables: Table list: "ASO"."AQ$_ASO_ORDER_FEEDBACK_T_S" Table list: "OKC"."AQ$_OKC_AQ_EV_TAB_S" Table list: "AR"."AQ$_AR_REV_REC_QT_S" Table list: "XNP"."AQ$_XNP_OUT_MSG_QTAB_S" Table list: "CS"."AQ$_CS_SERVICE_REQUEST_OQT_S" Table list: "CS"."AQ$_CS_SERVICE_REQUEST_IQT_S" Table list: "APPLSYS"."AQ$_WF_DEFERRED_TABLE_M_S" Table list: "APPLSYS"."AQ$_WF_DEFERRED_S" Table list: "APPLSYS"."AQ$_WF_ERROR_S" Table list: "APPLSYS"."AQ$_WF_REPLAY_OUT_S" Table list: "APPLSYS"."AQ$_WF_IN_S" Table list: "APPLSYS"."AQ$_WF_OUT_S" Table list: "APPLSYS"."AQ$_WF_REPLAY_IN_S" Table list: "APPLSYS"."AQ$_WF_JMS_IN_S" Table list: "APPLSYS"."AQ$_WF_JMS_OUT_S"