Format DELETE FILE_ELEMENT type-name [qualifier] ... element-name ,... .
1 – Parameters
1.1 – type-name
Specifies the type (MCS_BINARY or MCS_BINARY subtype) of the file element you are deleting. See the Oracle CDD/Repository Information Model Volume I for information on these types.
1.2 – element-name
Specifies the file element you are deleting. You can substitute an asterisk (*) wildcard character for this parameter.
2 – Qualifiers
2.1 /DESCENDANTS
Format options: /DESCENDANTS /NODESCENDANTS (default) Specifies whether CDO deletes children. When you specify the /DESCENDANTS qualifier, CDO deletes all children that are not also children of additional elements outside the area defined by your top collection.
2.2 /LOG
Format options: /LOG /NOLOG (default) Specifies whether CDO displays text confirming that the file element is deleted.
3 – Description
The DELETE FILE_ELEMENT command deletes a file element and, optionally, all children of the file element to the bottom of the collection hierarchy. Because a file element is a controlled element, CDO freezes all previous versions and allows you to delete only the highest visible version. CDO cannot delete the following versions in a branch line: o A version that is owned by a version in a different branch o A version that owns an intermediate version in a different branch See the Oracle CDD/Repository Architecture Manual for information on branch lines of descent.
4 – Examples
1.CDO> DELETE FILE_ELEMENT MCS_BINARY PARSER_TABLES. In this example, the DELETE FILE_ELEMENT command deletes a file element definition that is based on the MCS_BINARY type. 2.CDO> DELETE FILE_ELEMENT MCS_BINARY PARSER_TABLES(3). CDO> DELETE FILE_ELEMENT MCS_BINARY PARSER_TABLES(2:UPDATE_BRANCH:2). CDO> DELETE FILE_ELEMENT MCS_BINARY PARSER_TABLES(3:UPDATE_BRANCH:1). CDO> DELETE FILE_ELEMENT MCS_BINARY PARSER_TABLES(2). CDO> DELETE FILE_ELEMENT MCS_BINARY PARSER_TABLES(1). In this example, successive DELETE FILE_ELEMENT commands delete the main line and the branch line versions of a file element in sequence of ownership. The branch line originates from version 2 and merges back in version 3.