3.3.2.2 Application Root Objects Conversion

  • By default sharing type of all DB objects loaded in the Application Root will be none.
  • A static table will hold the information of selected tables for which the sharing type is DATA LINK. Other tables will be treated as METADATA LINK.
  • Sharing of object types such as INDEX, LOB, TABLE PARTITION, SEQUENCE, JOB, MATERIALIZED VIEW and DYNAMIC PACKAGES will remain as NONE.
  • All other object types such as SYNONYM, VIEW, TRIGGER FUNCTION, PROCEDURE, and PACKAGE would be converted as METADATA LINK.
Object Conversion
  • With the above sharing type considerations, DB object types will be converted as DATA LINK and METADATA LINK as part of this application root object conversion step.
  • User has to connect to Application Root as common user and then apply changes in upgrade mode with the same application name used in step 3.
  • This step will be done from the installer and user will have 4 options to do the conversion as,
    • Shared Application
    • Shared Application and User Authentication
    • Shared Application and Shared Data – Default
    • Shared Application and Shared Data – Custom

Note:

Application root will be created through cloning from Application Template PDB which will have only the static data. Transaction or maintenance related data will not be available in the Application root.
Shared Application
Here all the function Ids will be available as PDB function ids.
Shared Application and User Authentication
SMS function ids will be available in Approot and the remaining all function ids will be available as PDB function ids.
Shared Application and Shared Data – Default
Identified list of entities will be available in approot and sharing of entities from Approot to individual PDBs is applicable in this model.
Shared Application and Shared Data – Custom
Identified list of entities will be available in approot and sharing of entities from Approot to individual PDBs is applicable in this model.
Additionally, User can opt-out the entities which are not required to be the candidates of approot and those function ids will be moved to PDB.
The application name and type of deployment will be stored in CSTB_PARAM table in approot.
PARAM_NAME PARAM_VAL
MULTI_TENANT_APP_NAME OBTFM
MULTI_TENANT_DEPLOYMENT_MODEL SA (or) SAUA (or) SASDD (or) SASDC
Object conversion is a one-time activity and if it is tried again, system will validate based on the availability of cstb_param values.

Parent topic: Steps for Manual Application Setup