To create a PDM with support for features specific to the Oracle DBMS family, select the appropriate version in the DBMS field of the New Model dialog. To view these extensions to the PowerDesigner metamodel in the Resource Editor, select Profile node. and expand the
When working with Oracle triggers, you can use the TRGBODY and TRGDESC variables. For information about working with variables, see Customizing and Extending PowerDesigner > DBMS Definition Files > PDM Variables and Macros.
The following table lists Oracle dimension objects and their equivalents in PowerDesigner:
Oracle object |
PowerDesigner object |
---|---|
Dimension |
Dimension (see Dimensions (PDM)) |
Hierarchy |
Dimension hierarchy (see Hierarchies (PDM)) |
Level |
Dimension attribute used in a hierarchy (see Fact and Dimension Attributes (PDM)) |
Attribute |
Dimension attribute used as detail attribute (seeFact and Dimension Attributes (PDM)) |
The following sections list the extensions provided for Oracle.
The following extensions are available on the Oracle tab for attributes of abstract data types of type OBJECT or SQLJ_OBJECT:
The following extensions are available on the Oracle tab:
Name |
Description |
---|---|
Deferrable |
[v11g and higher] Specifies that in subsequent transactions you can use the SET CONSTRAINT clause to defer checking of this constraint until after the transaction is committed. Scripting name: CheckDeferrable, NotNullDeferrable |
Initially deferred |
[v11g and higher] Specifies that Oracle should check this constraint at the end of subsequent transactions. Scripting name: CheckInitiallyDeferred, NotNullInitiallyDeferred |
Deferred option of check constraint |
[up to v10gR2] Defines the deferred option of a column constraint check. It is used in the definition or create and add items statements. Scripting name: ExtColumnDeferOption |
Constraint name/Name of not null constraint |
[v8i and higher] Defines the name of the not null constraint for a column. Scripting name: ExtNotNullConstraintName |
Deferred option of not null constraint |
[up to v10gR2] Defines the deferred option of a column not null constraint. It is used in "create" and "add" statement items definition. An empty value means "Not deferrable". Scripting name: ExtNotNullDeferOption |
Encrypted |
[v10gR2 and higher] Specifies if column is encrypted. Scripting name: Encrypted |
Algorithm |
[v10gR2 and higher] Specifies the algorithm used for encryption. Scripting name: Algorithm |
With salt |
[v10gR2 and higher] Specifies if encryption adds salt to encoded data. Scripting name: EncryptionWithSalt |
Identified by Password |
[v10gR2 and higher] Identifies by password. Scripting name: IdentifiedByPassword |
If the table type is set to XML, the Columns tab is replaced by the XML Virtual Columns tab.The following extensions are available on the General tab of XML virtual columns:
Name |
Description |
---|---|
Expression |
Specifies the SQL expression used to compute virtual column value. Scripting name: Expression |
The following extensions are available on the Oracle tab:
Name |
Description |
---|---|
Add serially_reusable pragma on package specification |
[v9i and higher] When set to True, defines that the pragma serially_reusable clause must be applied on the database package specification. Scripting name: IsSpecPragma |
Add serially_reusable pragma on package body |
[v9i and higher] When set to True, defines that the pragma serially_reusable clause must be applied on the database package body declaration. Scripting name: IsPragma |
The following extensions are available on the Oracle tab:
Name |
Description |
---|---|
Password Encryption |
[v10gR2 and higher] Specifies the master key for encoding and decoding encrypted data. Scripting name: PasswordEncryption |
The following extensions are available on the Oracle tab:
Name |
Description |
---|---|
Deferred option |
Defines the deferred option of a reference. It is used in the definition of create and add items statements. Scripting name: ExtReferenceDeferOption |
Exceptions into |
Specifies a table into which Oracle places the ROWIDs of all rows violating the constraint. Scripting name: ExceptionsInto |
Rely |
[v8i and higher] Specifies whether an enabled constraint is to be enforced. Specify RELY to enable an existing constraint without enforcement. Specify NORELY to enable and enforce an existing constraint. Scripting name: Rely |
Disable |
Disables the integrity constraint. Scripting name: Disable |
Validate |
Checks that all old data also obeys the constraint. Scripting name: Validate |
The following extensions are available on the Oracle tab:
Name |
Description |
---|---|
Materialized view log |
Specifies the materialized view log associated with the table. Scripting name: MaterializedViewLog |
The following extensions are available on the XML properties tab (for v11g and higher) when the table type is set to XML:
Name |
Description |
---|---|
Definition |
Specifies that the properties of object tables are essentially the same as those of relational tables. However, instead of specifying columns, you specify attributes of the object. Scripting name: XmlTypeObjProperty |
Storage type |
Specifies that XMLType columns can be stored in LOB, object-relational, or binary XML columns. Scripting name: XMLTypeStorage |
Basic file |
Use this clause to specify the traditional LOB storage. Scripting name: BasicFile |
Secure file |
Use this clause to specify high-performance LOB. Scripting name: SecureFile |
LOB segment name |
Specify the name of the LOB data segment. You cannot use LOB_segname if you specify more than one LOB_item. Scripting name: LOBSegname |
LOB parameters |
Use this clause to specify various elements of LOB parameters. Scripting name: LOBParameters |
The following extensions are available on the Oracle tab:
Name |
Description |
---|---|
Size specification |
[v10g and higher] Specifies whether the tablespace is a bigfile or smallfile tablespace. This clause overrides any default tablespace type setting for the database. You can choose from the following settings: Scripting name: SizeSpecification |
Temporary tablespace |
Use this option to create a locally managed temporary tablespace, which is an allocation of space in the database that can contain transient data that persists only for the duration of a session. This transient data cannot be recovered after process or instance failure. Scripting name: Temporary |
Undo tablespace |
Use this option to create an undo tablespace. When you run the database in automatic undo management mode, Oracle Database manages undo space using the undo tablespace instead of rollback segments. This clause is useful if you are now running in automatic undo management mode but your database was not created in automatic undo management mode. Scripting name: Undo |
The following extensions are available on the General tab (for v9i and higher):
Name |
Description |
---|---|
Identification type |
Specifies how the user will be identified. You can choose between:
Scripting name: Identification |
Distinguished name |
[external or global identification types] Specifies the user's distinguished name (DN) in the directory or certificate. Scripting name: DistinguishedName |
Password |
[by identification type] Specifies the user password. Scripting name: ClearPassword |
The following extensions are available on the Options tab (for v9i and higher):
Name |
Description |
---|---|
Default tablespace |
Specifies the default tablespace for objects that the user creates. Scripting name: DefaultTablespace |
Temporary tablespace |
Specifies the tablespace or tablespace group for the user's temporary segments. Scripting name: TemporaryTablespace |
Quota definition |
Specifies the maximum amount of space the user can allocate in the tablespace. Scripting name: QuotaDefinition |
Profile |
Specifies the profile to assign to the user. Scripting name: Profile |
Password expire |
Specifies that the user's password will expire. Scripting name: PasswordExpire |
Account lock |
Select lock to lock the user's account and disable access or unlock to enable access to the account. Scripting name: AccountLock |
The following extensions are available on the Oracle tab:
Name |
Description |
---|---|
Super view object |
[v9i and higher] Used in the UNDER clause to specify the superview the current object view is based on. Scripting name: ExtObjSuperView |
Object view key |
[v8i and higher] Specifies the attributes of the object type that will be used as a key to identify each row in the object view. Scripting name: ExtObjOIDList |
Object view type |
[v8i and higher] Defines the type of the object view. Scripting name: ExtObjViewType |
Force |
When set to TRUE, allows you to create the view regardless of the existence of the base tables or the owner privileges on these tables. Scripting name: ExtViewForce |