1. Analytical Application Infrastructure User Guide
  2. Data Model Management
  3. OFSAA Data Model Extensions through the SQL Data Modeler
  4. Customization Process
  5. Modification of Columns of Existing Tables

Modification of Columns of Existing Tables

  • Column UDP ‘Custom’ must be set as YES for all the columns being customized. (Table UDP ‘Custom’ is not required to be set for out-of-the-box tables.)
  • Support is extended for column length change and addition of new columns. Ensure that the existing column, when represented in SQL Modeler, must be intact with the base model definition for information such as UDPs, domains, and other logical information. Otherwise, it can create inconsistencies in the populated information of the OFSAA metadata repository.

    Note:

    Oracle recommends that you import only the altered columns into the SQL Modeler. If you import all the columns (altered and unaltered), the changes from the previous upload will be overwritten.

    However, if you choose to import all the columns and avoid overwriting the existing changes, select the blank value (do not select BYTE or CHAR) from the Units drop-down list in the Column Properties tab in the SQL Modeler.

  • As model level UDPs are not supported by SQL Modeler, Model UDP - VERSION is expected to be added at the table level. Ensure that the version for an existing table undergoing customization is equal or higher than that of the previous model. If it is missing for any table, the default value is 80000. Therefore, there are possibilities to ignore customizations.