EBS R12.2 Upgrade Frequently Asked Questions Part – II

In this post, we are continuing with the part -II of FAQs that were asked during the recent batch of our EBS Upgrade R12.2.

If you haven’t checked the part -I yet, I would strongly suggest you please check from here,  EBS R12.2 Upgrade Frequently Asked Questions.

I hope these questions might help you in pursuing your upgrade target with more clarity and explanation. If you have any questions, then do let us know by commenting in the comment box.

Let’s have a look at the basic terms and information before proceeding to the FAQs:

DB 19c CDB/PDB Architecture Overview

With the launch of database 12c in 2013, Oracle introduced a new architectural concept, called “Multitenant Databases”, where you have one super database (=container; CDB) and one or more sub-databases (= pluggable; PDB).

To know more about the DB 19c Upgrade. check my previous blog  19c Database In Oracle EBS R12: Everything You Must Know

Below are the Related FAQs:

Q.1 Do we need to perform a restore for both CDB and PDB during refreshes?

OR

Since the PDB was already plugged into CDB. Do we take a backup only for CDB and restore it on the target server?

Ans. In the case of EBS, you got only one PDB and one CDB, either you plug out only the PDB and plug into the target or you can clone the PDB to the target.
Or the second option which is usually recommended take the backup of the entire CDB and PDB and restore to the target, It saves time.

Q.2 Do we need to add extra memory/storage for CDB creation to take care?

Ans. No, there is no such additional memory required, as at the time you can choose whether you want you CDB or non-CDB running, and both are allocated the same size, but only one will be up at a time.

Q.3 In 19c any DB parameters to add or modify to increase the DB performance.

Ans. Doc ID:396009.1 Database Initialization Parameters for Oracle E-Business Suite Release 12

Q.4 What is best practice for providing tns entry to end-users who use tools like a toad, etc for 19c DB considering editions so that they point to run edition?

Ans. point to the correct service, Oracle will automatically connect to the right edition.

Q.5 I was getting this error while running autoconfig in 19C UnsatisfiedLinkError exception loading native library: njni19

Ans. LD library path is wrong and if it’s a warning: it can be ignored.

Q.6 Have you done or aware of XLA archiving/purge? we have 50% space used of DB under xla. Oracle support doesn’t support and sends to Informatica or HP

Ans. Oracle doesn’t support, it will impact on the size of the database but doesn’t impact performance.

Supported Database Features and Options

The Supported Database Features and the Options list includes items that are supported but not explicitly certified by EBS. Oracle Database generic documentation applies to these features and options, even if we haven’t certified them specifically.

• Advanced Compression
• Database In-Memory
• Database Partitioning
• Native PL/SQL Compilation
• Oracle Application Express (APEX)
• Oracle Label Security (OLS)*
• SecureFiles
• Virtual Private Database (VPD)*

Certified Database Features and Options

The Certified Database Features and the Options list includes items that have been explicitly certified by EBS development.

• Container Database (CDB) Architecture (multitenant architecture) with a single Pluggable Database (PDB) (single tenant)
• Export/Import
• Oracle Real Application Clusters (Oracle RAC)
• Transparent Data Encryption (TDE) with Online Tablespace Encryption Conversion

Below are the Related FAQs:

Q.1 Do you use optimizer_features_enable=19.1.0? we had performance issues with 19.1.0. what are the recommended optimizer settings for EBS? (hit when upgrading f.rom 11.2.04 to 19c)

Ans. Either the query has to be rewritten or an optimizer hint should be placed at the query level.

Q.2 We have upgraded our 12c to 19c but after 19c upgrade, all shell script concurrent programs are failing since INSTANCE_NAME is hardcoded in the shell script and it is picking container database as INSTANCE_NAME instead of PDB name as INSTANCE_NAME.

Ans. This is expected as the architecture has changed, the customization should be rewritten

Q.3 If we have already upgraded to 19.3 first before the apps upgrade – do we have any application pre-tasks to worry about? Similar to adop actualize all?

Ans.If you have already upgraded the database to 19c.

The next step is to upgrade the apps tier to 12.2 from 12.1.3

*If you are upgrading to R12.2.x and your source database is already 19c, then the following should be done

Staging Area

StartCD consolidated bundle (Patch 25525148) and one-off Patch 29963728 also needs to be applied to the staging area after the software is staged.

Preinstall Patch Apply Stage

Apart from the usual pre-install patch, also apply patch 30520625

AD-TXK Patches

Go with the latest list of recommended post-AD-TXK patches on 1617461.1. These patches include fixes for 19c related known issues.

Q.4 DB upgrade from 11.0.2.0.3.0 -> 12.1.0.2.0 to 19 on AIX. Do you support this?

Ans. It is supported.

Q.5 I am on R12.1.3 and going to 19c then no need for me cleanup editions right but just follow left side EBS pre-requisites R12.1.

Ans. Yes, absolutely, no need.

Q.6 In one ADOP cycle suppose 20 patches applied successfully and one patch has issues that are not able to fix the patch issues how to proceed to the ADOP cycle by ignoring the failed patch.

Ans. You cannot proceed with a failed patch, you have to abort the current patching cycle and then reapply the patches.

Q.7 While upgrading from 12.1.3 to 12.2, so the custom top directory which exists in 12.1.3, do we need to copy it as it is to 12.2 instances.

Ans. Conditionally yes, As If you are upgrading from 11i existing environment, you will have custom forms in forms 6i (its an older format), so you have to copy across the custom top, but the forms and reports will have to be upgraded to the latest standards, which developers will be doing.

You need to copy the custom top but whatever forms and reports are not compatible with the current version that they need to be updated.

Once you copy the custom top then you need to synchronize the forms.

DB 19c High-Level Upgrade Steps

• Configure DB Home for EBS
• If R12.2.x, ensure that no ADOP cycle is active, Upgrade Database to 19c
• Prepare for PDB Conversion & Convert to PDB
• Execute Post PDB Conversion script txkPostPDBCreationTasks.pl
• MOS Doc Id. 396009.1 Modify Database Initialization parameters following
• Run autoconfig on the Application tier
• Rewrite customizations depending on UTL_FILE_DIR
• Rewrite customizations if impacted due to CDB/PDB model
• Start  Application services and carry out complete Health Check

To know more about the EBS Upgrade R12.2, do  check my previous blog EBS R12.2 Upgrade High-Level Overview/Steps 

Below are the Related FAQs:

Q.1 It is safe to upgrade GI from 12.1.0.2 to 19c and keep the database homes for ebs and other apps to 12.1.0.2, are there in impacts between the clusters, RAC, databases, components such as listener or scan.

Ans. The grid can definitely be higher version, should be either higher or same, no impact in that case.

Q.2 What is the English driver patch? is it the same as Upgrade patch? can you pls share the English driver patch ID I can go with README of that patch.

Ans. U10124646 is the English patch driver and it will update the ebs 12.1 base table to r12.2.

Q.3 in the upgrade to 12.2.9 from 12.2 — there is a section – fix opmn issue which talks about creating a new wallet – point 7.1.2 – is this mandatory for all sites? Or is this opmn issue something which may not concern everyone?

Ans. This step is required post-July 2019 ohs CPU, it is mandatory in that case

If you face OPMN fails issue while starting the application tier, [Fixed] opmnctl startall fails In EBS R12.2

EBS R12.2 File System

• R12.2 has a dual File system.
• Run File system and Patch File system and are identical.

To knoe more about the File System in EBS R12.2, check our previous blog File System in Oracle E-Business Suite R12.2 : Dual, APPL_TOP, INST_TOP, COMMON_TOP, FMW_HOME

Below are the Related FAQs:

Q.1 Do we need to copy the custom top to the run file system only or on both run and patch.

Ans. Technically, only run file system is sufficient, you copy the custom top to the run file system and then you run fs_clone and it is going to synchronize your run file system with the patch file system.

But for CEMLI deployment it is recommended to copy the custom top to both run and patch file system.

Q.2 Besides regular cust_top we have few other schemas which customer uses for ETL. because of the complexity of schema we decided to keep it non-editioned, but realized non-editioned objects like views cannot refer to editioned objects. Is there any best practice for non-seeded schemas?

Ans. If you can create those objects on the app schemas, rather than keeping them on the custom schema, make a custom application to point to that apps schema.

Otherwise, the only way is to do the editioning of that schema

Q.3 what is the ‘datapatch’ for the DB pre-task?

Ans. Data patch is a utility provided by Opatch, It’s an automation that is used to apply post database patching SQL.

When you apply a database patch, then that patch introduces some sqls, which you need to run on the database. This was manual until 11g, in 12c Oracle has modified it in such a way that all these sqls will be run as a part of the patching with this datapatch utility.

Q.4 In R122 environment – after fndnodes cleanup and run autoconfig on RUN F/s or try to apply the patch using adop cycle phase=prepare / phase=fs_clone it will throw the error that patch F/s not available – how to fix the issue.

Ans. However, you can upload the patch context file to the database for fixing this issue, never run setup_clean unless asked by support.

Fusion Middleware: WLS & OHS

• Software layer that lies between business application and database
• Infrastructure which facilitates the creation of business applications
• Includes Web Servers, Application Servers, Content Management, Identity Management, SOA, Business Intelligence
• Oracle EBS R12.2 uses WebLogic & OHS from FMW

Below are the Related FAQs:

Q.1 What is Struck threads on WebLogic? why do struck threads alerts occurred on Weblogic logs?

Ans. In 12.2 Weblogic will mark a thread struck if it is running for more than 600 seconds (10 minutes).

Invalid Parameters in DB 19c

In Operations such as upgrades, patches and DDL changes can invalidate schema objects. Provided these changes don’t cause compilation failures the objects will be revalidated by on-demand automatic recompilation, but this can take an unacceptable time to complete, especially where complex dependencies are present. For this reason, it makes sense to recompile invalid objects in advance of user calls. It also allows you to identify if any changes have broken your codebase.

Below are the FAQs on the same:

Q.1. So the steps you mentioned just now for the utl file dir are to be run in the 11.2.0.4 or 12.1 databases? Before installing and creating the 19c database?

Ans. Yes. This is before the DB upgrade, so it has to be done as a pre-task on 11g or 12.1.

Q.2 Any idea on this “desupport in Oracle Database 19c of the UTL_FILE_DIR database initialization parameter”.

Ans. Db 19c is de-supported, for EBS they have put a workaround, you can use UTL for 19c in EBS.

Q.3 So programs generating files using UTL_FILE_DIR will not be impacted?? if u follow the workaround.

Ans. Yes, as long as you call it from the apps_schema, not custom_schema.

Q.4 FND_STATS – do u recommend running on all schemas? And is there a percentage you can fix – for example, 40 percent?

Ans. For the upgrade, we give 50 percent.

References MOS

• MOS (Doc ID 2552181.1 Interoperability Notes: Oracle E-Business Suite Release 12.2 with Oracle Database 19c
• MOS (Doc ID 1545562.1) Oracle E-Business Suite – Product Support Analyzer Index.
• MOS (Doc ID 396009.1) Database Initialization Parameters for Oracle E-Business Suite Release 12
• MOS (Doc ID 2116869.1) EBS Analyzer FAQ and Known Issues & Solutions
• MOS (Doc ID 2634237.1) E-Business Suite Upgrade Analyzer – 12.X to 12.2.X
• MOS (Doc ID 2530665.1) Using Oracle Database 19c RAC Multitenant (Single PDB) with Oracle E-Business Suite Release 12.2
• MOS (Doc ID 2554156.1) Export/Import Process for Oracle E-Business Suite Release 12.2 Database Instances Using Oracle Database 19c

Related/ Further Readings

• Oracle E-Business Suite (EBS) 12.2.9 Now Available & Its Upgrade Steps
• Steps to download Oracle E-Business Suite R12 Software
• Oracle AppsDBA (R12.2) Training: Step by Step Activity Guides/Hands-On Lab Exercise
• 19c Database In Oracle EBS R12: Everything You Must Know
• EBS R12.2 Upgrade High-Level Overview/Steps

Next Task For You

Begin your journey towards becoming an Oracle EBS Upgrade R12.2 AppsDBA by joining our Training on Upgrade EBS R12/11i To R12.2

Click on the image below to join FREE Masterclass on Upgrade EBS R12/11i To R12.2:

FREE Community

The post EBS R12.2 Upgrade Frequently Asked Questions Part – II appeared first on Cloud Training Program.