How Are New Not Nullable Columns Handled During An Argus Safety Upgrade

(Doc ID 1215305.1)

Last updated on OCTOBER 13, 2010

Applies to:

Oracle Argus Safety - Version: 4.1.3 to 6.0 - Release: 4.1 to 6.0
Information in this document applies to any platform.

Goal

How will the new NOT NULL columns be populated during Argus database upgrade (see examples listed below)?
a. Argus 4.2 HF1 Database Schema Change
-- Argus table CMN_PROFILE, inserted column KEY_TYPE
-- ESM table EDI_INFO, inserted column EDI_INTERNAL_ID
b. Argus Database Schema Change between 42 SP1 HF1 B and 42 SP2
-- Argus table CFG_REG_REPORT_RULES, inserted column AUTO_DISTRIBUTE_REPORTS
-- Argus table CFG_USERS, inserted column ENABLE_CHECKLIST_ON_ROUTE
-- Argus table CMN_REG_REPORTS, inserted column AUTO_DISTRIBUTE_REPORTS
-- Argus table LM_LICENSE, inserted column OTC_PRODUCT
-- Argus table LM_REGULATORY_CONTACT, inserted columns AUTO_ACCEPT_ICSR, TRANSMIT_E2B_ATTACHMENT
c. Argus Database Schema Change between 42 SP2 and 5.0
-- Argus table CFG_REG_REPORT_RULES, inserted column BLIND_STUDY_PRODUCT
-- Argus table LM_DOSE_UNITS, inserted column DOSAGE_UNIT
-- Argus table CFG_MEDWATCH_CODES, inserted column SORTBY
d. ORACLE ARGUS SAFETY DATABASE SCHEMA CHANGES BETWEEN 5.0.2 AND 5.1
-- Argus table LM_MFR_EVAL_REASON, inserted column MFR_EVAL_CODE
e. ORACLE ARGUS SAFETY DATABASE SCHEMA CHANGES BETWEEN 5.1 AND 6.0
-- Argus table CMN_FIELDS, inserted column LANG


Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms