Format DELETE GENERIC type-name [qualifier] ... element-name ,... .
1 – Parameters
1.1 – type-name
Specifies the type of the generic element you are deleting. This type cannot be MCS_BINARY, an MCS_BINARY subtype, MCS_COLLECTION, MCS_CONTEXT, or MCS_PARTITION.
1.2 – element-name
Specifies the generic element you are deleting.
2 – Qualifiers
2.1 /DESCENDANTS
Format options: /DESCENDANTS /NODESCENDANTS (default) Specifies whether CDO deletes children. When you specify the /DESCENDANTS qualifier, and your generic element is controlled, CDO deletes all children that are not also children of additional elements outside the area defined by your top collection. If the generic element is uncontrolled, CDO deletes all children that are not also children of other elements.
2.2 /LOG
Format options: /LOG /NOLOG (default) Specifies whether CDO displays text confirming that the generic element is deleted.
3 – Description
The DELETE GENERIC command deletes a generic element. This element can be based on a type supplied by Oracle CDD/Repository or a user-supplied type. If a generic element is a controlled versioned element, CDO freezes previous versions and allows you to modify only the highest visible version. If a generic element is an uncontrolled versioned element, CDO deletes the highest version unless you specify another version number. If you use SQL (structured query language) to delete an Oracle Rdb database file, the corresponding CDD$DATABASE element may remain in Oracle CDD/Repository. You can use the DELETE GENERIC command to delete this element.
4 – Examples
1.CDO> DELETE GENERIC CDD$DATABASE DEPT1. In this example, the DELETE GENERIC command deletes the DEPT1 generic element from the repository. 2.CDO> DELETE GENERIC CDD$SOURCE_MODULE cont> /DESCENDANTS /LOG COBOL_SOURCE. In this example, the DELETE GENERIC command with the /LOG and /DESCENDANTS qualifiers confirms that CDO has deleted the COBOL_SOURCE generic element and children.