On Oracle

How to make triggers disappear without actually dropping them? I recently ran into this situation and reported it to Oracle as a possible bug. This is still being investigated by Oracle. I am going to explain this using the testcase I built for Oracle Support. Let's start by creating a simple table. Connected to: Oracle Database 18c EE Extreme Perf Release 18.0.0.0.0 - Production Version 18.5.0.0.0 CREATE TABLE t1_ (id NUMBER(6) NOT NULL ,col1 DATE NOT NULL ,col2 VARCHAR2(10 CHAR) ,ts TIMESTAMP(9) NOT NULL ); Table created. ALTER TABLE t1_ ADD CONSTRAINT t1_pk PRIMARY KEY (ID) ; Table altered. Because I want to be able to do near zero downtime patching I use Oracle Edition Based Redefinition (EBR). So this means I also need an Editioning view on the table. CREATE OR REPLACE EDITIONING VIEW t1 AS SELECT id , col1 , col2 , ts FROM t1_ ; View created. Now I am going to create a simple trigger on the Editioning view. Not o