Discussions
Categories
- 384.6K All Categories
- 2.5K Data
- 556 Big Data Appliance
- 1.9K Data Science
- 451.4K Databases
- 222.1K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 32 Multilingual Engine
- 561 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 561 SQLcl
- 4K SQL Developer Data Modeler
- 187.5K SQL & PL/SQL
- 21.4K SQL Developer
- 296.9K Development
- 1 Application Development
- 18 Developer Projects
- 140 Programming Languages
- 293.6K Development Tools
- 112 DevOps
- 3.1K QA/Testing
- 646.2K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 193 Java Community Process
- 106 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 21 Java Essentials
- 166 Java 8 Questions
- 86K Java Programming
- 81 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 206 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 536 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 178 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 236 Portuguese
How to Disable EBR during 19c database upgrade?
Hi All,
We have upgraded Oracle EBS to 12.2.7. We are now prepping to upgrade the 12.1.0.2 Enterprise Database up to 19.3.
The 19c database upgrade instructions (Doc ID 2539778.1) say “Disable any custom triggers that would get executed before / after DDL. You can enable it once upgrade is completed.”
We are using Edition Based Redefinition (EBR). Do we simply disable all triggers on tables owned by APPS? Than re-enable them afterwards?
Any thoughts (and references) would be appreciated.
Answers
-
EBS has it's own forum. But generally speaking, it's "disable any custom triggers". Have you created custom triggers on any tables?
-
No custom triggers on the regular tables owned by APPS.
-
A database upgrade does not touch user data (e.g. EBS data). It touches only the meta data itself (objects owned by Oracle Maintained users, e.g. SYS and SYSTEM). You can do whatever you want with user data and it will not conflict with a database upgrade. Also, Edition Based Redefinition works only on user data. You can't use it for SYS. So you can have e.g. two editions in your database at the same time.
The triggers you should worry about are those that trigger on a database event or a ddl event. If they work on a user schema they should be fine to keep during upgrade. However, if you have made triggers that works on any Oracle Maintained user or fire database-wide I recommend that you disable those during upgrade. They might conflict with the upgrade itself - although it might not necessarily be so.
Regards,
Daniel
-
By the way, have you considered using AutoUpgrade for the upgrade? There is a quick start guide here. Al the many manual steps that are listed in the MOS note are automatically executed by AutoUpgrade for now. You should be able to upgrade the database in just one command with AutoUpgrade.
We launched the tool last spring and it is our recommended method for database upgrades.
Regards,
Daniel
-
That's good info!