TYPE changes with /abortonwarnings switch

mbruegelmbruegel Philadelphia, PAPosts: 17 Bronze 1
edited April 12, 2019 10:54AM in Schema Compare for Oracle
We're running SCO version 5.2.4.1278 from the command line and observed some odd behavior when changing an object type definition (referenced by a collection type) when combined w/ the /abortonwatnings:high switch.

Scenario:
- changing the attribute definition on object used in a collection
- execute a SCO deployment w/ /abortonwatnings:high
- expected behavior:
  -- abort / error prior to drop of collection type and exit w/ code 63
  -- underlying object type is not updated

- observed behavior:
  -- object type attributes are updated
  -- SCO exits w/ 63 (because of the drop of the collection type)
  -- after the SCO failure, when we look at the object on the target DB the datatypes of the object has been updated despite the abort on warnings failure
     -- note from the captured UPDATE DDL the actual DROP appears to be executed before the type update


   /* UPDATE DDL generated from SCO: */
   --
   -- Script generated by Schema Compare for Oracle 5.2.4.1278 on 10/04/2019 17:24:35
   --
   SET DEFINE OFF

   DROP TYPE parameter_var_t;

   CREATE OR REPLACE TYPE PARAMETER_PAIR_OBJ_T AS OBJECT
    (param_name VARCHAR2(100),
     param_value VARCHAR2(1000));
   /

   CREATE OR REPLACE TYPE PARAMETER_VAR_T AS VARRAY(10) OF parameter_pair_obj_t;
   /


   /* Original Object Definition */
   CREATE OR REPLACE TYPE PARAMETER_PAIR_OBJ_T AS OBJECT
    (param_name VARCHAR2(50),
     param_value VARCHAR2(500)); 
   /

   CREATE OR REPLACE TYPE PARAMETER_VAR_T AS VARRAY(10) OF parameter_pair_obj_t; 
   /


   /* Target / Updated Definition */
   CREATE OR REPLACE TYPE PARAMETER_PAIR_OBJ_T AS OBJECT
    (param_name VARCHAR2(100),
     param_value VARCHAR2(1000)); 
   /

   CREATE OR REPLACE TYPE PARAMETER_VAR_T AS VARRAY(10) OF parameter_pair_obj_t; 
   /

Any explanation for this behavior?

- martin
Sign In or Register to comment.