{"id":8904,"date":"2015-09-24T20:50:32","date_gmt":"2015-09-24T23:50:32","guid":{"rendered":"http:\/\/www.orabr.com\/oracle-dbms_metadata-recuperar-metadados-do-dicionario-banco-de-dados-como-xml-ou-criacao-ddl-e-submeter-o-xml-para-recriar-o-objeto\/"},"modified":"2015-09-24T20:58:38","modified_gmt":"2015-09-24T23:58:38","slug":"ORACLE-DBMS_METADATA-RECUPERAR-METADADOS-DO-DICIONARIO-BANCO-DE-DADOS-COMO-XML-OU-CRIACAO-DDL-E-SUBMETER-O-XML-PARA-RECRIAR-O-OBJETO","status":"publish","type":"post","link":"https:\/\/orabr.virttus.com\/?p=8904","title":{"rendered":"ORACLE DBMS_METADATA – recuperar metadados do dicion\u00e1rio banco de dados como XML ou cria\u00e7\u00e3o DDL e submeter o XML para recriar o objeto"},"content":{"rendered":"

O pacote DBMS_METADATA fornece uma maneira para que voc\u00ea possa recuperar metadados do dicion\u00e1rio banco de dados como XML ou cria\u00e7\u00e3o DDL e submeter o XML para recriar o objeto.<\/a><\/p>\n

————————————————————————–<\/p>\n

57\u00a0DBMS_METADATA<\/a><\/p>\n
The\u00a0DBMS_METADATA\u00a0package provides a way for you to retrieve metadata from the database dictionary as XML or creation DDL and to submit the XML to re-create the object.<\/a><\/p><\/blockquote>\n
<\/p>\n
\n\n\n\n
See Also:<\/p>\n
Oracle Database Utilities<\/a><\/span>\u00a0for more information and for examples of using the Metadata API<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
This chapter contains the following topics:<\/h6>\n
\n
\n
Using DBMS_METADATA<\/a><\/h6>\n
\n
\n
Overview<\/h6>\n<\/li>\n
\n
Security Model<\/h6>\n<\/li>\n
\n
Rules and Limits<\/h6>\n<\/li>\n<\/ul>\n<\/li>\n
\n
Data Structures – Object and Table Types<\/a><\/h6>\n<\/li>\n
\n
Subprogram Groupings<\/a><\/h6>\n
\n
\n
Subprograms for Retrieving Multiple Objects From the Database<\/h6>\n<\/li>\n
\n
Subprograms for Submitting XML to the Database<\/h6>\n<\/li>\n<\/ul>\n<\/li>\n
\n
Summary of All DBMS_METADATA Subprograms<\/a><\/h6>\n<\/li>\n<\/ul>\n
\n
<\/a>Using DBMS_METADATA<\/h2>\n
This section contains topics which relate to using the\u00a0DBMS_METADATA<\/code>\u00a0package.<\/p>\n
\nOverview<\/a><\/li>\n Security Model<\/a><\/li>\n Rules and Limits<\/a><\/li>\n<\/ul>\n<\/a><\/p>\n \nOverview<\/h3>\nYou can use the\u00a0DBMS_METADATA<\/code>\u00a0package to retrieve metadata and also to submit XML.<\/p>\n\nRetrieving Metadata<\/a><\/li>\n Submitting XML<\/a><\/li>\n<\/ul>\n<\/a><\/p>\n Retrieving Metadata<\/h4>\nIf you are retrieving metadata, you can specify:<\/p>\n\nThe kind of object to be retrieved. This can be either a particular object type (such as a table, index, or procedure) or a heterogeneous collection of object types that form a logical unit (such as a database export or schema export).<\/li>\n Optional selection criteria, such as owner or name.<\/li>\n Parse items (attributes of the returned objects to be parsed and returned separately).<\/li>\nOptional transformations on the output, implemented by XSLT (Extensible Stylesheet Language Transformation) scripts. By default the output is represented in XML, but you can specify transformations (into SQL DDL, for example), which are implemented by XSLT stylesheets stored in the database or externally.<\/li>\n<\/ul>\nDBMS_METADATA<\/code>\u00a0provides the following retrieval interfaces:<\/p>\n\nFor programmatic use:\u00a0OPEN,<\/code>\u00a0SET_FILTER,<\/code>\u00a0SET_COUNT,<\/code>\u00a0GET_QUERY,<\/code>\u00a0SET_PARSE_ITEM,<\/code>\u00a0ADD_TRANSFORM,<\/code>\u00a0SET_TRANSFORM_PARAM,SET_REMAP_PARAM,<\/code>\u00a0FETCH_xxx,<\/code>\u00a0and\u00a0CLOSE<\/code>\u00a0retrieve multiple objects.<\/li>\nFor use in SQL queries and for browsing:\u00a0GET_XML<\/code>\u00a0and\u00a0GET_DDL<\/code>\u00a0return metadata for a single named object. The\u00a0GET_DEPENDENT_XML<\/code>,\u00a0GET_DEPENDENT_DDL<\/code>,\u00a0GET_GRANTED_XML<\/code>, and\u00a0GET_GRANTED_DDL<\/code>\u00a0interfaces return metadata for one or more dependent or granted objects. These procedures do not support heterogeneous object types.<\/li>\n<\/ul>\n<\/a><\/p>\n Submitting XML<\/h4>\nIf you are submitting XML, you specify:<\/p>\n\nThe type of object<\/li>\n Optional transform parameters to modify the object (for example, changing the object’s owner)<\/li>\n Parse items (attributes of the submitted objects to be parsed and submitted separately)<\/li>\nWhether to execute the operation or simply return the generated DDL<\/li>\n<\/ul>\nDBMS_METADATA<\/code>\u00a0provides a programmatic interface for submission of XML. It is comprised of the following procedures:\u00a0OPENW<\/code>,\u00a0ADD_TRANSFORM<\/code>,\u00a0SET_TRANSFORM_PARAM<\/code>,\u00a0SET_REMAP_PARAM<\/code>,\u00a0SET_PARSE_ITEM<\/code>,\u00a0CONVERT<\/code>,\u00a0PUT<\/code>, and\u00a0CLOSE<\/code>.<\/p>\n<\/a><\/p>\n \nSecurity Model<\/h3>\nThe object views of the Oracle metadata model implement security<\/a>\u00a0as follows:<\/p>\n \nNonprivileged users can see the metadata of only their own objects.<\/li>\n SYS<\/code>\u00a0and users with\u00a0SELECT_CATALOG_ROLE<\/code>\u00a0can see all objects.<\/li>\n Nonprivileged users can also retrieve public synonyms, system privileges granted to them, and object privileges granted to them or by them to others. This also includes privileges granted to\u00a0PUBLIC<\/code>.<\/li>\n If callers request objects they are not privileged to retrieve, no exception is raised; the object is simply not retrieved.<\/li>\n If nonprivileged users are granted some form of access to an object in someone else’s schema, they will be able to retrieve the grant specification through the Metadata API, but not the object’s actual metadata.<\/li>\nIn stored procedures, functions, and definers-rights packages, roles (such as\u00a0SELECT_CATALOG_ROLE<\/code>) are disabled. Therefore, such a PL\/SQL program can only fetch metadata for objects in its own schema. If you want to write a PL\/SQL program that fetches metadata for objects in a different schema (based on the invoker’s possession of\u00a0SELECT_CATALOG_ROLE<\/code>), you must make the program invokers-rights.<\/li>\n<\/ul>\n<\/a><\/p>\n \nRules and Limits<\/h3>\nIn an Oracle Shared Server (OSS) environment, the\u00a0DBMS_METADATA<\/code>\u00a0package must disable session migration and connection pooling. This results in any shared server process that is serving a session running the package to effectively become a default, dedicated server for the life of the session. You should ensure that sufficient shared servers are configured when the package is used and that the number of servers is not artificially limited by too small a value for the\u00a0MAX_SHARED_SERVERS<\/code>\u00a0initialization parameter.<\/p>\n \nData Structures – Object and Table Types<\/h2>\nThe\u00a0DBMS_METADATA<\/code>\u00a0package defines, in the\u00a0SYS<\/code>\u00a0schema, the following\u00a0OBJECT<\/code>\u00a0and\u00a0TABLE<\/code>\u00a0types.<\/p>\nCREATE TYPE sys.ku$_parsed_item AS OBJECT (\r\n item VARCHAR2(30),\r\n value VARCHAR2(4000),\r\n object_row NUMBER )\r\n\/\r\n\r\nCREATE PUBLIC SYNONYM ku$_parsed_item FOR sys.ku$_parsed_item;\r\n\r\nCREATE TYPE sys.ku$_parsed_items IS TABLE OF sys.ku$_parsed_item\r\n\/\r\n\r\nCREATE PUBLIC SYNONYM ku$_parsed_items FOR sys.ku$_parsed_items;\r\n\r\nCREATE TYPE sys.ku$_ddl AS OBJECT (\r\n ddlText CLOB,\r\nparsedItem sys.ku$_parsed_items )\r\n\/\r\n\r\nCREATE PUBLIC SYNONYM ku$_ddl FOR sys.ku$_ddl;\r\n\r\nCREATE TYPE sys.ku$_ddls IS TABLE OF sys.ku$_ddl\r\n\/\r\n\r\nCREATE PUBLIC SYNONYM ku$_ddls FOR sys.ku$_ddls;\r\n\r\nCREATE TYPE sys.ku$_multi_ddl AS OBJECT (\r\n object_row NUMBER,\r\n ddls sys.ku$_ddls )\r\n\/\r\n\r\nCREATE OR REPLACE PUBLIC SYNONYM ku$_multi_ddl FOR sys.ku$_multi_ddl;\r\n\r\nCREATE TYPE sys.ku$_multi_ddls IS TABLE OF sys.ku$_multi_ddl;\r\n\/\r\n\r\nCREATE OR REPLACE PUBLIC SYNONYM ku$_multi_ddls FOR\r\n sys.ku$_multi_ddls;\r\n\r\nCREATE TYPE sys.ku$_ErrorLine IS OBJECT (\r\n errorNumber NUMBER,\r\n errorText VARCHAR2(2000) )\r\n\/\r\n\r\nCREATE PUBLIC SYNONYM ku$_ErrorLine FOR sys.ku$_ErrorLine;\r\n\r\nCREATE TYPE sys.ku$_ErrorLines IS TABLE OF sys.ku$_ErrorLine\r\n\/\r\nCREATE PUBLIC SYNONYM ku$ErrorLines FOR sys.ku$_ErrorLines;\r\n\r\nCREATE TYPE sys.ku$_SubmitResult AS OBJECT (\r\n ddl sys.ku$_ddl,\r\n errorLines sys.ku$_ErrorLines );\r\n\/\r\n\r\nCREATE TYPE sys.ku$_SubmitResults IS TABLE OF sys.ku$_SubmitResult\r\n\/\r\n\r\nCREATE PUBLIC SYNONYM ku$_SubmitResults FOR sys.ku$_SubmitResults;\r\n<\/pre>\n \nSubprogram Groupings<\/h2>\nThe\u00a0DBMS_METADATA<\/code>\u00a0subprograms are used to retrieve objects from, and submit XML to, a database. Some subprograms are used for both activities, while others are used only for retrieval or only for submission.<\/p>\n\nTable 57-1<\/a>\u00a0provides a summary, in alphabetical order, of\u00a0DBMS_METADATA<\/code>\u00a0subprograms used to retrieve multiple objects from a database.<\/li>\n Table 57-2<\/a>\u00a0provides a summary, in alphabetical order, of\u00a0DBMS_METADATA<\/code>\u00a0subprograms used to submit XML metadata to a database.<\/li>\n<\/ul>\n<\/a><\/p>\n \nSubprograms for Retrieving Multiple Objects From the Database<\/h3>\nTable 57-1<\/a>\u00a0lists the subprograms used for retrieving multiple objects from the database.<\/p>\n \n<\/a><\/a><\/p>\n Table 57-1 DBMS_METADATA Subprograms for Retrieving Multiple Objects<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nSubprogram<\/th>\n Description<\/th>\n<\/tr>\n<\/thead>\n \nADD_TRANSFORM Function<\/a><\/p>\n<\/td>\n \nSpecifies a transform that\u00a0FETCH_xxx<\/code>\u00a0applies to the XML representation of the retrieved objects<\/p>\n<\/td>\n<\/tr>\n \nCLOSE Procedure<\/a>2<\/a><\/p>\n<\/td>\n \nInvalidates the handle returned by\u00a0OPEN<\/code>\u00a0and cleans up the associated state<\/p>\n<\/td>\n<\/tr>\n \nFETCH_xxx Functions and Procedures<\/a><\/p>\n<\/td>\n \nReturns metadata for objects meeting the criteria established by\u00a0OPEN<\/code>,\u00a0SET_FILTER<\/code>,\u00a0SET_COUNT<\/code>,\u00a0ADD_TRANSFORM<\/code>, and so on<\/p>\n<\/td>\n<\/tr>\n \nGET_QUERY Function<\/a><\/p>\n<\/td>\n \nReturns the text of the queries that are used by\u00a0FETCH_xxx<\/code><\/p>\n<\/td>\n<\/tr>\n \nGET_xxx Functions<\/a><\/p>\n<\/td>\n \nFetches the metadata for a specified object as XML or DDL, using only a single call<\/p>\n<\/td>\n<\/tr>\n \nOPEN Function<\/a><\/p>\n<\/td>\n \nSpecifies the type of object to be retrieved, the version of its metadata, and the object model<\/p>\n<\/td>\n<\/tr>\n \nSET_COUNT Procedure<\/a><\/p>\n<\/td>\n \nSpecifies the maximum number of objects to be retrieved in a single\u00a0FETCH_xxx<\/code>\u00a0call<\/p>\n<\/td>\n<\/tr>\n \nSET_FILTER Procedure<\/a><\/p>\n<\/td>\n \nSpecifies restrictions on the objects to be retrieved, for example, the object name or schema<\/p>\n<\/td>\n<\/tr>\n \nSET_PARSE_ITEM Procedure<\/a><\/p>\n<\/td>\n \nEnables output parsing by specifying an object attribute to be parsed and returned<\/p>\n<\/td>\n<\/tr>\n \nSET_TRANSFORM_PARAM and SET_REMAP_PARAM Procedures<\/a><\/p>\n<\/td>\n \nSpecifies parameters to the XSLT stylesheets identified by\u00a0transform_handle<\/code><\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n <\/a><\/p>\n \nSubprograms for Submitting XML to the Database<\/h3>\nTable 57-2<\/a>\u00a0lists the subprograms used for submitting XML to the database.<\/p>\n \n<\/a><\/a><\/p>\n Table 57-2 DBMS_METADATA Subprograms for Submitting XML<\/p>\n\n\n\n\n\n\n\n\n\n\n\nSubprogram<\/th>\n Description<\/th>\n<\/tr>\n<\/thead>\n \nADD_TRANSFORM Function<\/a><\/p>\n<\/td>\n \nSpecifies a transform for the XML documents<\/p>\n<\/td>\n<\/tr>\n \nCLOSE Procedure<\/a>2<\/a><\/p>\n<\/td>\n \nCloses the context opened with\u00a0OPENW<\/code><\/p>\n<\/td>\n<\/tr>\n \nCONVERT Functions and Procedures<\/a><\/p>\n<\/td>\n \nConverts an XML document to DDL<\/p>\n<\/td>\n<\/tr>\n \nOPENW Function<\/a><\/p>\n<\/td>\n \nOpens a write context<\/p>\n<\/td>\n<\/tr>\n \nPUT Function<\/a><\/p>\n<\/td>\n \nSubmits an XML document to the database<\/p>\n<\/td>\n<\/tr>\n \nSET_PARSE_ITEM Procedure<\/a><\/p>\n<\/td>\n \nSpecifies an object attribute to be parsed<\/p>\n<\/td>\n<\/tr>\n \nSET_TRANSFORM_PARAM and SET_REMAP_PARAM Procedures<\/a><\/p>\n<\/td>\n \nSET_TRANSFORM_PARAM<\/code>\u00a0specifies a parameter to a transform<\/p>\n SET_REMAP_PARAM<\/code>\u00a0specifies a remapping for a transform<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n \n<\/a><\/a><\/a><\/a><\/h6>\n\n<\/a>Summary of All DBMS_METADATA Subprograms<\/h6>\n<\/a><\/a><\/h6>\nTable 57-3 DBMS_METADATA Package Subprograms<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nSubprogram<\/th>\n Description<\/th>\n<\/tr>\n<\/thead>\n \nADD_TRANSFORM Function<\/a><\/p>\n<\/td>\n \nSpecifies a transform that\u00a0FETCH_xxx<\/code>\u00a0applies to the XML representation of the retrieved objects<\/p>\n<\/td>\n<\/tr>\n \nCLOSE Procedure<\/a>2<\/a><\/p>\n<\/td>\n \nInvalidates the handle returned by\u00a0OPEN<\/code>\u00a0and cleans up the associated state<\/p>\n<\/td>\n<\/tr>\n \nCONVERT Functions and Procedures<\/a><\/p>\n<\/td>\n \nConverts an XML document to DDL.<\/p>\n<\/td>\n<\/tr>\n \nFETCH_xxx Functions and Procedures<\/a><\/p>\n<\/td>\n \nReturns metadata for objects meeting the criteria established by\u00a0OPEN<\/code>,\u00a0SET_FILTER<\/code>,\u00a0SET_COUNT<\/code>,\u00a0ADD_TRANSFORM<\/code>, and so on<\/p>\n<\/td>\n<\/tr>\n \nGET_xxx Functions<\/a><\/p>\n<\/td>\n \nFetches the metadata for a specified object as XML or DDL, using only a single call<\/p>\n<\/td>\n<\/tr>\n \nGET_QUERY Function<\/a><\/p>\n<\/td>\n \nReturns the text of the queries that are used by\u00a0FETCH_xxx<\/code><\/p>\n<\/td>\n<\/tr>\n \nOPEN Function<\/a><\/p>\n<\/td>\n \nSpecifies the type of object to be retrieved, the version of its metadata, and the object model<\/p>\n<\/td>\n<\/tr>\n \nOPENW Function<\/a><\/p>\n<\/td>\n \nOpens a write context<\/p>\n<\/td>\n<\/tr>\n \nPUT Function<\/a><\/p>\n<\/td>\n \nSubmits an XML document to the database<\/p>\n<\/td>\n<\/tr>\n \nSET_COUNT Procedure<\/a><\/p>\n<\/td>\n \nSpecifies the maximum number of objects to be retrieved in a single\u00a0FETCH_xxx<\/code>\u00a0call<\/p>\n<\/td>\n<\/tr>\n \nSET_FILTER Procedure<\/a><\/p>\n<\/td>\n \nSpecifies restrictions on the objects to be retrieved, for example, the object name or schema<\/p>\n<\/td>\n<\/tr>\n \nSET_PARSE_ITEM Procedure<\/a><\/p>\n<\/td>\n \nEnables output parsing by specifying an object attribute to be parsed and returned<\/p>\n<\/td>\n<\/tr>\n \nSET_TRANSFORM_PARAM and SET_REMAP_PARAM Procedures<\/a><\/p>\n<\/td>\n \nSpecifies parameters to the XSLT stylesheets identified by\u00a0transform_handle<\/code><\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n <\/a><\/h6>\n \nADD_TRANSFORM Function<\/a><\/h6>\nThis function is used for both retrieval and submission:<\/h6>\n\n\nWhen this procedure is used to retrieve objects, it specifies a transform that\u00a0FETCH_xxx<\/code>\u00a0applies to the XML representation of the retrieved objects.<\/h6>\n<\/li>\n\nWhen used to submit objects, it specifies a transform that\u00a0CONVERT<\/code>\u00a0or\u00a0PUT<\/code>\u00a0applies to the XML representation of the submitted objects. It is possible to add more than one transform.<\/h6>\n\n\n\n\nSee Also:<\/p>\n For more information about related subprograms:<\/p>\n \n\nSubprograms for Retrieving Multiple Objects From the Database<\/a><\/p>\n<\/li>\n \nSubprograms for Submitting XML to the Database<\/a><\/p>\n<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/li>\n<\/ul>\n <\/a><\/h6>\nSyntax<\/h6>\n DBMS_METADATA.ADD_TRANSFORM ( handle IN NUMBER, name IN VARCHAR2, encoding IN VARCHAR2 DEFAULT NULL, object_type IN VARCHAR2 DEFAULT NULL) RETURN NUMBER;<\/h6>\n<\/a><\/h6>\nParameters<\/h6>\n<\/a><\/a><\/h6>\nTable 57-4 ADD_TRANSFORM Function Parameters<\/p>\n\n\n\n\n\n\n\n\nParameters<\/th>\n Description<\/th>\n<\/tr>\n<\/thead>\n \nhandle<\/code><\/p>\n<\/td>\n \nThe handle returned from\u00a0OPEN<\/code>\u00a0when this transform is used to retrieve objects. Or the handle returned from\u00a0OPENW<\/code>\u00a0when this transform is used in the submission of XML metadata.<\/p>\n<\/td>\n<\/tr>\n \nname<\/code><\/p>\n<\/td>\n \nThe name of the transform. If name contains a period, colon, or forward slash, it is interpreted as the URL of a user-supplied XSLT script. See\u00a0Oracle XML DB Developer’s Guide<\/a>.<\/span><\/p>\n Otherwise, name designates a transform implemented by this project. The following transforms are defined:<\/p>\n \n\nDDL – the document is transformed to DDL that creates the object. The output of this transform is\u00a0not<\/span>\u00a0an XML document.<\/p>\n<\/li>\n \nMODIFY – The document is modified as directed by transform and remap parameters. The output of this transform is an XML document. If no transform or remap parameters are specified, the document is unchanged.<\/p>\n<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n \nencoding<\/code><\/p>\n<\/td>\n \nThe name of the Globalization Support character set in which the stylesheet pointed to by name is encoded. This is only valid if name is a URL. If left NULL and the URL is external to the database, UTF-8 encoding is assumed. If left NULL and the URL is internal to the database (that is, it begins with \/oradb\/), then the encoding is assumed to be the database character set.<\/p>\n<\/td>\n<\/tr>\n \nobject_type<\/code><\/p>\n<\/td>\n \nThe definition of this parameter depends upon whether you are retrieving objects or submitting XML metadata.<\/p>\n \n\nWhen you use\u00a0ADD_TRANFORM<\/code>\u00a0to retrieve objects, the following definition of object_type applies:<\/p>\n<\/li>\n<\/ol>\n Designates the object type to which the transform applies. (Note that this is an object type name, not a path name.) By default the transform applies to the object type of the\u00a0OPEN<\/code>\u00a0handle. When the\u00a0OPEN<\/code>\u00a0handle designates a heterogeneous object type, the following behavior can occur:<\/p>\n \n\nif\u00a0object_type<\/code>\u00a0is omitted, the transform applies to all object types within the heterogeneous collection<\/p>\n<\/li>\n \nif\u00a0object_type<\/code>\u00a0is specified, the transform only applies to that specific object type within the collection<\/p>\n If you omit this parameter you can add the DDL transform to all objects in a heterogeneous collection with a single call. If you supply this parameter, you can add a transform for a specific object type.<\/p>\n<\/li>\n<\/ul>\n \n\nWhen you use\u00a0ADD_TRANSFORM<\/code>\u00a0in the submission of XML metadata, this parameter is the object type to which the transform applies. By default, it is the object type of the\u00a0OPENW<\/code>\u00a0handle. Because the\u00a0OPENW<\/code>\u00a0handle cannot designate a heterogeneous object type, the caller would normally leave this parameter NULL in the\u00a0ADD_TRANSFORM<\/code>\u00a0calls.<\/p>\n<\/li>\n<\/ol>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n <\/a><\/h6>\nReturn Values<\/h6>\nThe opaque handle that is returned is used as input to\u00a0SET_TRANSFORM_PARAM<\/code>\u00a0and\u00a0SET_REMAP_PARAM<\/code>. Note that this handle is different from the handle returned by\u00a0OPEN<\/code>\u00a0or\u00a0OPENW<\/code>; it refers to the transform, not the set of objects to be retrieved.<\/h6>\n<\/a><\/h6>\nUsage Notes<\/h6>\n\n\nWith no transforms added, objects are returned by default as XML documents. You call\u00a0ADD_TRANSFORM<\/code>\u00a0to specify the XSLT stylesheets to be used to transform the returned XML documents.<\/h6>\n<\/li>\n\nYou can call\u00a0ADD_TRANSFORM<\/code>\u00a0more than once to apply multiple transforms to XML documents.\u00a0T<\/code>ransforms are applied in the order in which they were specified, the output of the first transform being used as input to the second, and so on.<\/h6>\n<\/li>\n\nThe output of the DDL transform is\u00a0not<\/span>\u00a0an XML document. Therefore, no transform should be added after the DDL transform.<\/h6>\n<\/li>\n<\/ul>\n<\/a><\/h6>\nExceptions<\/h6>\n\n\nINVALID_ARGVAL<\/code>. A\u00a0NULL<\/code>\u00a0or invalid value was supplied for an input parameter. The error message text identifies the parameter.<\/h6>\n<\/li>\n\nINVALID_OPERATION<\/code>.\u00a0ADD_TRANSFORM<\/code>\u00a0was called after the first call to\u00a0FETCH_xxx<\/code>\u00a0for the\u00a0OPEN<\/code>\u00a0context. After the first call to\u00a0FETCH_xxx<\/code>\u00a0is made, no further calls to\u00a0ADD_TRANSFORM<\/code>\u00a0for the current\u00a0OPEN<\/code>\u00a0context are permitted.<\/h6>\n<\/li>\n\nINCONSISTENT_ARGS<\/code>. The arguments are inconsistent. Possible inconsistencies include the following:<\/h6>\n\n\nencoding<\/code>\u00a0is specified even though name is not a URL<\/h6>\n<\/li>\n\nobject_type<\/code>\u00a0is not part of the collection designated by handle<\/h6>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/a><\/h6>\n \nCLOSE Procedure<\/a><\/h6>\nThis procedure is used for both retrieval and submission. This procedure invalidates the handle returned by\u00a0OPEN<\/code>\u00a0(or\u00a0OPENW<\/code>) and cleans up the associated state.<\/h6>\n\n\n\n\n\nSee Also:<\/p>\n For more information about related subprograms:<\/p>\n \n\nSubprograms for Retrieving Multiple Objects From the Database<\/a><\/p>\n<\/li>\n \nSubprograms for Submitting XML to the Database<\/a><\/p>\n<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n <\/a><\/h6>\nSyntax<\/h6>\n DBMS_METADATA.CLOSE ( handle IN NUMBER);<\/h6>\n<\/a><\/h6>\nParameters<\/h6>\n<\/a><\/a><\/h6>\nTable 57-5 CLOSE Procedure Parameters<\/p>\n\n\n\n\n\nParameter<\/th>\n Description<\/th>\n<\/tr>\n<\/thead>\n \nhandle<\/code><\/p>\n<\/td>\n \nThe handle returned from\u00a0OPEN<\/code>\u00a0(or\u00a0OPENW<\/code>).<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n <\/a><\/h6>\nUsage Notes<\/h6>\n\n\n\n\n\nNote:<\/p>\n The following notes apply only to object retrieval<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n You can prematurely terminate the stream of objects established by\u00a0OPEN<\/code>\u00a0or (OPENW)<\/code>.<\/h6>\n\n\nIf a call to\u00a0FETCH_xxx<\/code>\u00a0returns\u00a0NULL,<\/code>\u00a0indicating no more objects, a call to\u00a0CLOSE<\/code>\u00a0is made transparently. In this case, you can still call\u00a0CLOSE<\/code>\u00a0on the handle and not get an exception. (The call to\u00a0CLOSE<\/code>\u00a0is not required.)<\/h6>\n<\/li>\n\nIf you know that only one specific object will be returned, you should explicitly call\u00a0CLOSE<\/code>\u00a0after the single\u00a0FETCH_xxx<\/code>\u00a0call to free resources held by the handle.<\/h6>\n<\/li>\n<\/ul>\n<\/a><\/h6>\nExceptions<\/h6>\n\n\nINVALID_ARGVAL<\/code>. The value for the\u00a0handle<\/code>\u00a0parameter is\u00a0NULL<\/code>\u00a0or invalid.<\/h6>\n<\/li>\n<\/ul>\n<\/a><\/h6>\n \nCONVERT Functions and Procedures<\/a><\/h6>\nThe\u00a0CONVERT<\/code>\u00a0functions and procedures transform input XML documents. The\u00a0CONVERT<\/code>\u00a0functions return creation DDL. The\u00a0CONVERT<\/code>\u00a0procedures return either XML or DDL, depending on the specified transforms.<\/h6>\n\n\n\n\n\nSee Also:<\/p>\n For more information about related subprograms:<\/p>\n \n\nSubprograms for Submitting XML to the Database<\/a><\/p>\n<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n <\/a><\/h6>\nSyntax<\/h6>\nThe\u00a0CONVERT<\/code>\u00a0functions are as follows:<\/h6>\nDBMS_METADATA.CONVERT ( handle IN NUMBER, document IN sys.XMLType) RETURN sys.ku$_multi_ddls; DBMS_METADATA.CONVERT ( handle IN NUMBER, document IN CLOB) RETURN sys.ku$_multi_ddls;<\/h6>\nThe\u00a0CONVERT<\/code>\u00a0procedures are as follows:<\/h6>\nDBMS_METADATA.CONVERT ( handle IN NUMBER, document IN sys.XMLType, result IN OUT NOCOPY CLOB); DBMS_METADATA.CONVERT ( handle IN NUMBER, document IN CLOB, result IN OUT NOCOPY CLOB);<\/h6>\n<\/a><\/h6>\nParameters<\/h6>\n<\/a><\/a><\/h6>\nTable 57-6 CONVERT Subprogram Parameters<\/p>\n\n\n\n\n\n\n\nParameter<\/th>\n Description<\/th>\n<\/tr>\n<\/thead>\n \nhandle<\/code><\/p>\n<\/td>\n \nThe handle returned from\u00a0OPENW<\/code>.<\/p>\n<\/td>\n<\/tr>\n \ndocument<\/code><\/p>\n<\/td>\n \nThe XML document containing object metadata of the type of the\u00a0OPENW<\/code>\u00a0handle.<\/p>\n<\/td>\n<\/tr>\n \nresult<\/p>\n<\/td>\n \nThe converted document.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n <\/a><\/h6>\nReturn Values<\/h6>\n DDL to create the object(s).<\/h6>\n<\/a><\/h6>\nUsage Notes<\/h6>\nYou can think of\u00a0CONVERT<\/code>\u00a0as the second half of\u00a0FETCH_xxx<\/code>, either\u00a0FETCH_DDL<\/code>\u00a0(for the function variants) or\u00a0FETCH_CLOB<\/code>\u00a0(for the procedure variants). There are two differences:<\/h6>\n\n\nFETCH_xxx<\/code>\u00a0gets its XML document from the database, but\u00a0CONVERT<\/code>\u00a0gets its XML document from the caller<\/h6>\n<\/li>\n\nFETCH_DDL returns its results in a sys.ku$_ddls nested table, but CONVERT returns a sys.ku$_multi_ddls nested table<\/h6>\n<\/li>\n<\/ul>\nThe transforms specified with\u00a0ADD_TRANSFORM<\/code>\u00a0are applied in turn, and the result is returned to the caller. For the function variants, the DDL transform must be specified. If parse items were specified, they are returned in the\u00a0parsedItems<\/code>\u00a0column. Parse items are ignored by the procedure variants.<\/h6>\nThe encoding of the XML document is embedded in its CLOB or XMLType representation. The version of the metadata is embedded in the XML. The generated DDL is valid for the database version specified in\u00a0OPENW<\/code>.<\/h6>\n<\/a><\/h6>\nExceptions<\/h6>\n\n\nINVALID_ARGVAL<\/code>. A NULL or invalid value was supplied for an input parameter. The error message text identifies the parameter.<\/h6>\n<\/li>\n\nINCONSISTENT_OPERATION<\/code>. No transform was specified. The DDL transform was not specified (function variants only).<\/h6>\n<\/li>\n\nINCOMPATIBLE_DOCUMENT<\/code>. The version of the XML document is not compatible with this version of the software.<\/h6>\n<\/li>\n<\/ul>\n<\/a><\/h6>\n \nFETCH_xxx Functions and Procedures<\/h6>\nThese functions and procedures return metadata for objects meeting the criteria established by\u00a0OPEN<\/code>,\u00a0SET_FILTER<\/code>,\u00a0SET_COUNT<\/code>,\u00a0ADD_TRANSFORM<\/code>, and so on. See\u00a0“Usage Notes”<\/a>\u00a0for the variants.<\/h6>\n\n\n\n\n\nSee Also:<\/p>\n For more information about related subprograms:<\/p>\n \n\nSubprograms for Retrieving Multiple Objects From the Database<\/a><\/p>\n<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n <\/a><\/h6>\nSyntax<\/h6>\n The\u00a0FETCH<\/code>\u00a0functions are as follows:<\/h6>\nDBMS_METADATA.FETCH_XML ( handle IN NUMBER) RETURN sys.XMLType;<\/h6>\n\n\n\n\n\nSee Also:<\/p>\n Oracle XML DB Developer’s Guide<\/span><\/a>\u00a0for a description of\u00a0XMLType<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n DBMS_METADATA.FETCH_DDL ( handle IN NUMBER) RETURN sys.ku$_ddls; DBMS_METADATA.FETCH_CLOB ( handle IN NUMBER, cache_lob IN BOOLEAN DEFAULT TRUE, lob_duration IN PLS INTEGER DEFAULT DBMS_LOB.SESSION) RETURN CLOB;<\/h6>\nThe\u00a0FETCH<\/code>\u00a0procedures are as follows:<\/h6>\nDBMS_METADATA.FETCH_CLOB ( handle IN NUMBER, doc IN OUT NOCOPY CLOB); DBMS_METADATA.FETCH_XML_CLOB ( handle IN NUMBER, doc IN OUT NOCOPY CLOB, parsed_items OUT sys.ku$_parsed_items, object_type_path OUT VARCHAR2);<\/h6>\n<\/a><\/h6>\nParameters<\/h6>\n<\/a><\/a><\/h6>\nTable 57-7 FETCH_xxx Function Parameters<\/p>\n\n\n\n\n\n\n\n\n\n\nParameters<\/th>\n Description<\/th>\n<\/tr>\n<\/thead>\n \nhandle<\/code><\/p>\n<\/td>\n \nThe handle returned from\u00a0OPEN<\/code>.<\/p>\n<\/td>\n<\/tr>\n \ncache_lob<\/code><\/p>\n<\/td>\n \nTRUE<\/code>=read LOB into buffer cache<\/p>\n<\/td>\n<\/tr>\n \nlob_duration<\/code><\/p>\n<\/td>\n \nThe duration for the temporary LOB created by\u00a0FETCH_CLOB<\/code>, either\u00a0DBMS_LOB.SESSION<\/code>\u00a0(the default) or\u00a0DBMS_LOB.CALL<\/code>.<\/p>\n<\/td>\n<\/tr>\n \ndoc<\/code><\/p>\n<\/td>\n \nThe metadata for the objects, or\u00a0NULL<\/code>\u00a0if all objects have been returned.<\/p>\n<\/td>\n<\/tr>\n \nparsed_items<\/code><\/p>\n<\/td>\n \nA nested table containing the items specified by\u00a0SET_PARSE_ITEM<\/code>. If\u00a0SET_PARSE_ITEM<\/code>\u00a0was not called, a NULL is returned.<\/p>\n<\/td>\n<\/tr>\n \nobject_type_path<\/code><\/p>\n<\/td>\n \nFor heterogeneous object types, this is the full path name of the object type for the objects returned by the call to\u00a0FETCH_XXX<\/code>. If\u00a0handle<\/code>\u00a0designates a homogeneous object type, a NULL is returned.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n <\/a><\/h6>\nReturn Values<\/h6>\nThe metadata for the objects or\u00a0NULL<\/code>\u00a0if all objects have been returned.<\/h6>\n<\/a><\/h6>\nUsage Notes<\/h6>\nThese functions and procedures return metadata for objects meeting the criteria established by the call to\u00a0OPEN<\/code>\u00a0that returned the handle, and subsequent calls to\u00a0SET_FILTER<\/code>,\u00a0SET_COUNT<\/code>,\u00a0ADD_TRANSFORM<\/code>, and so on. Each call to\u00a0FETCH_xxx<\/code>\u00a0returns the number of objects specified by\u00a0SET_COUNT<\/code>\u00a0(or less, if fewer objects remain in the underlying cursor) until all objects have been returned. After the last object is returned, subsequent calls to\u00a0FETCH_xxx<\/code>\u00a0return\u00a0NULL<\/code>\u00a0and cause the stream created by\u00a0OPEN<\/code>\u00a0to be transparently closed.<\/h6>\nThere are several different\u00a0FETCH_xxx<\/code>\u00a0functions and procedures:<\/h6>\n\n\nThe\u00a0FETCH_XML<\/code>\u00a0function returns the XML metadata for an object as an\u00a0XMLType<\/code>. It assumes that if any transform has been specified, that transform will produce an XML document. In particular, it assumes that the DDL transform has not been specified.<\/h6>\n<\/li>\n\nThe\u00a0FETCH_DDL<\/code>\u00a0function returns the DDL (to create the object) in a\u00a0sys.ku$_ddls<\/code>\u00a0nested table. It assumes that the DDL transform has been specified. Each row of the\u00a0sys.ku$_ddls<\/code>\u00a0nested table contains a single DDL statement in the\u00a0ddlText<\/code>\u00a0column; if requested, parsed items for the DDL statement will be returned in the\u00a0parsedItems<\/code>\u00a0column. Multiple DDL statements may be returned under the following circumstances:<\/h6>\n\n\nWhen you call\u00a0SET_COUNT<\/code>\u00a0to specify a count greater than\u00a01<\/code><\/h6>\n<\/li>\n\nWhen an object is transformed into multiple DDL statements. For example, A\u00a0TYPE<\/code>\u00a0object that has a DDL transform applied to it can be transformed into both\u00a0CREATE TYPE<\/code>\u00a0and\u00a0CREATE TYPE BODY<\/code>\u00a0statements. A\u00a0TABLE<\/code>\u00a0object can be transformed into a\u00a0CREATE TABLE<\/code>, and one or more\u00a0ALTER TABLE<\/code>\u00a0statements<\/h6>\n<\/li>\n<\/ul>\n<\/li>\n\nThe\u00a0FETCH_CLOB<\/code>\u00a0function simply returns the object, transformed or not, as a CLOB. By default, the CLOB is read into the buffer cache and has session duration, but these defaults can be overridden with the\u00a0cache_lob<\/code>\u00a0and\u00a0lob_duration<\/code>\u00a0parameters.<\/h6>\n<\/li>\n\nThe\u00a0FETCH_CLOB<\/code>\u00a0procedure returns the objects by reference in an\u00a0IN<\/code>\u00a0OUT<\/code>\u00a0NOCOPY<\/code>\u00a0parameter. This is faster than the function variant, which returns LOBs by value, a practice that involves an expensive LOB copy.<\/h6>\n<\/li>\n\nThe\u00a0FETCH_XML_CLOB<\/code>\u00a0procedure returns the XML metadata for the objects as a CLOB in an\u00a0IN<\/code>\u00a0OUT<\/code>\u00a0NOCOPY<\/code>\u00a0parameter. This helps to avoid LOB copies, which can consume a lot of resources. It also returns a nested table of parse items and the full path name of the object type of the returned objects.<\/h6>\n<\/li>\n\nAll LOBs returned by\u00a0FETCH_xxx<\/code>\u00a0are temporary LOBs. You must free the LOB. If the LOB is supplied as an\u00a0IN<\/code>\u00a0OUT<\/code>\u00a0NOCOPY<\/code>\u00a0parameter, you must also create the LOB.<\/h6>\n<\/li>\n\nIf\u00a0SET_PARSE_ITEM<\/code>\u00a0was called,\u00a0FETCH_DDL<\/code>\u00a0and\u00a0FETCH_XML_CLOB<\/code>\u00a0return attributes of the object’s metadata (or the DDL statement) in a\u00a0sys.ku$_parsed_items<\/code>\u00a0nested table. For\u00a0FETCH_XML_CLOB<\/code>, the nested table is an\u00a0OUT<\/code>\u00a0parameter. For\u00a0FETCH_DDL<\/code>, it is a column in the returned\u00a0sys.ku$_ddls<\/code>\u00a0nested table. Each row of the nested table corresponds to an item specified by\u00a0SET_PARSE_ITEM<\/code>\u00a0and contains the following columns:<\/h6>\n\n\nitem<\/code>\u2014the name of the attribute as specified in the\u00a0name<\/code>\u00a0parameter to\u00a0SET_PARSE_ITEM.<\/code><\/h6>\n<\/li>\n\nvalue\u2014the attribute value, or\u00a0NULL<\/code>\u00a0if the attribute is not present in the DDL statement.<\/h6>\n<\/li>\n\nobject-row<\/code>\u2014a positive integer indicating the object to which the parse item applies. If multiple objects are returned by\u00a0FETCH_xxx<\/code>, (because\u00a0SET_COUNT<\/code>\u00a0specified a count greater than 1) then\u00a0object_row<\/code>=1<\/code>\u00a0for all items for the first object,\u00a02<\/code>\u00a0for the second, and so on.<\/h6>\n<\/li>\n<\/ul>\n<\/li>\n\nThe rows of the\u00a0sys.ku$_parsed_items<\/code>\u00a0nested table are ordered by ascending\u00a0object_row<\/code>, but otherwise the row order is undetermined. To find a particular parse item within an object row the caller must search the table for a match on\u00a0item<\/code>.<\/h6>\n<\/li>\n\nIn general there is no guarantee that a requested parse item will be returned. For example, the parse item may not apply to the object type or to the particular line of DDL, or the item’s value may be\u00a0NULL<\/code>.<\/h6>\n<\/li>\n\nIf\u00a0SET_PARSE_ITEM<\/code>\u00a0was not called,\u00a0NULL<\/code>\u00a0is returned as the value of the parsed items nested table.<\/h6>\n<\/li>\n\nIt is expected that the same variant of\u00a0FETCH_xxx<\/code>\u00a0will be called for all objects selected by\u00a0OPEN<\/code>. That is, programs will not intermix calls to\u00a0FETCH_XML<\/code>,\u00a0FETCH_DDL<\/code>,\u00a0FETCH_CLOB<\/code>, and so on using the same\u00a0OPEN<\/code>\u00a0handle. The effect of calling different variants is undefined; it might do what you expect, but there are no guarantees.<\/h6>\n<\/li>\n\nEvery object fetched will be internally consistent with respect to on-going DDL (and the subsequent recursive DML) operations against the dictionary. In some cases, multiple queries may be issued, either because the object type is heterogeneous or for performance reasons (for example, one query for heap tables, one for index-organized tables). Consequently the\u00a0FETCH_xxx<\/code>\u00a0calls may in fact be fetches from different underlying cursors (meaning that read consistency is not guaranteed).<\/h6>\n<\/li>\n<\/ul>\n<\/a><\/h6>\nExceptions<\/h6>\nMost exceptions raised during execution of the query are propagated to the caller. Also, the following exceptions may be raised:<\/h6>\n\n\nINVALID_ARGVAL<\/code>. A\u00a0NULL<\/code>\u00a0or invalid value was supplied for an input parameter. The error message text identifies the parameter.<\/h6>\n<\/li>\n\nINCONSISTENT_OPERATION<\/code>. Either\u00a0FETCH_XML<\/code>\u00a0was called when the DDL transform had been specified, or\u00a0FETCH_DD<\/code>L was called when the DDL transform had\u00a0not<\/span>\u00a0been specified.<\/h6>\n<\/li>\n<\/ul>\n<\/a><\/h6>\n \nGET_xxx Functions<\/a><\/a><\/h6>\nThe following\u00a0GET_xxx<\/code>\u00a0functions let you fetch metadata for objects with a single call:<\/h6>\n\n\nGET_XML<\/code><\/h6>\n<\/li>\n\nGET_DDL<\/code><\/h6>\n<\/li>\n\nGET_DEPENDENT_XML<\/code><\/h6>\n<\/li>\n\nGET_DEPENDENT_DDL<\/code><\/h6>\n<\/li>\n\nGET_GRANTED_XML<\/code><\/h6>\n<\/li>\n\nGET_GRANTED_DDL<\/code><\/h6>\n\n\n\n\nSee Also:<\/p>\n For more information about related subprograms:<\/p>\n \n\nSubprograms for Retrieving Multiple Objects From the Database<\/a><\/p>\n<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/li>\n<\/ul>\n <\/a><\/h6>\nSyntax<\/h6>\n DBMS_METADATA.GET_XML ( object_type IN VARCHAR2, name IN VARCHAR2, schema IN VARCHAR2 DEFAULT NULL, version IN VARCHAR2 DEFAULT ‘COMPATIBLE’, model IN VARCHAR2 DEFAULT ‘ORACLE’, transform IN VARCHAR2 DEFAULT NULL) RETURN CLOB; DBMS_METADATA.GET_DDL ( object_type IN VARCHAR2, name IN VARCHAR2, schema IN VARCHAR2 DEFAULT NULL, version IN VARCHAR2 DEFAULT ‘COMPATIBLE’, model IN VARCHAR2 DEFAULT ‘ORACLE’, transform IN VARCHAR2 DEFAULT ‘DDL’) RETURN CLOB; DBMS_METADATA.GET_DEPENDENT_XML ( object_type IN VARCHAR2, base_object_name IN VARCHAR2, base_object_schema IN VARCHAR2 DEFAULT NULL, version IN VARCHAR2 DEFAULT ‘COMPATIBLE’, model IN VARCHAR2 DEFAULT ‘ORACLE’, transform IN VARCHAR2 DEFAULT NULL, object_count IN NUMBER DEFAULT 10000) RETURN CLOB; DBMS_METADATA.GET_DEPENDENT_DDL ( object_type IN VARCHAR2, base_object_name IN VARCHAR2, base_object_schema IN VARCHAR2 DEFAULT NULL, version IN VARCHAR2 DEFAULT ‘COMPATIBLE’, model IN VARCHAR2 DEFAULT ‘ORACLE’, transform IN VARCHAR2 DEFAULT ‘DDL’, object_count IN NUMBER DEFAULT 10000) RETURN CLOB; DBMS_METADATA.GET_GRANTED_XML ( object_type IN VARCHAR2, grantee IN VARCHAR2 DEFAULT NULL, version IN VARCHAR2 DEFAULT ‘COMPATIBLE’, model IN VARCHAR2 DEFAULT ‘ORACLE’, transform IN VARCHAR2 DEFAULT NULL, object_count IN NUMBER DEFAULT 10000) RETURN CLOB; DBMS_METADATA.GET_GRANTED_DDL ( object_type IN VARCHAR2, grantee IN VARCHAR2 DEFAULT NULL, version IN VARCHAR2 DEFAULT ‘COMPATIBLE’, model IN VARCHAR2 DEFAULT ‘ORACLE’, transform IN VARCHAR2 DEFAULT ‘DDL’, object_count IN NUMBER DEFAULT 10000) RETURN CLOB;<\/h6>\n<\/a><\/h6>\nParameters<\/h6>\n<\/a><\/a><\/h6>\nTable 57-8 GET_xxx Function Parameters<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nParameter<\/th>\n Description<\/th>\n<\/tr>\n<\/thead>\n \nobject_type<\/code><\/p>\n<\/td>\n \nThe type of object to be retrieved. This parameter takes the same values as the\u00a0OPEN object_type<\/code>\u00a0parameter, except that it cannot be a heterogeneous object type. The attributes of the object type must be appropriate to the function. That is, for\u00a0GET_xxx<\/code>\u00a0it must be a named object.<\/p>\n<\/td>\n<\/tr>\n \nname<\/code><\/p>\n<\/td>\n \nThe object name. It is used internally in a\u00a0NAME<\/code>\u00a0filter. (If the name is longer than 30 characters, it will be used in a\u00a0LONGNAME<\/code>\u00a0filter.) If this parameter is NULL, then no\u00a0NAME<\/code>\u00a0or\u00a0LONGNAME<\/code>\u00a0filter is specifiedSee\u00a0Table 57-17<\/a>\u00a0for a list of filters.<\/p>\n<\/td>\n<\/tr>\n \nschema<\/code><\/p>\n<\/td>\n \nThe object schema. It is used internally in a\u00a0SCHEMA<\/code>\u00a0filter. The default is the current user.<\/p>\n<\/td>\n<\/tr>\n \nversion<\/code><\/p>\n<\/td>\n \nThe version of metadata to be extracted. This parameter takes the same values as the\u00a0OPEN<\/code>\u00a0version parameter.<\/p>\n<\/td>\n<\/tr>\n \nmodel<\/code><\/p>\n<\/td>\n \nThe object model to use. This parameter takes the same values as the\u00a0OPEN<\/code>\u00a0model parameter.<\/p>\n<\/td>\n<\/tr>\n \ntransform<\/code><\/p>\n<\/td>\n \nThe name of a transformation on the output. This parameter takes the same values as the\u00a0ADD_TRANSFORM<\/code>\u00a0name<\/code>\u00a0parameter. For\u00a0GET_XML<\/code>\u00a0this must not be\u00a0DDL<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nbase_object_name<\/code><\/p>\n<\/td>\n \nThe base object name. It is used internally in a\u00a0BASE_OBJECT_NAME<\/code>\u00a0filter.<\/p>\n<\/td>\n<\/tr>\n \nbase_object_schema<\/code><\/p>\n<\/td>\n \nThe base object schema. It is used internally in a\u00a0BASE_OBJECT_SCHEMA<\/code>\u00a0filter. The default is the current user.<\/p>\n<\/td>\n<\/tr>\n \ngrantee<\/code><\/p>\n<\/td>\n \nThe grantee. It is used internally in a\u00a0GRANTEE<\/code>\u00a0filter. The default is the current user.<\/p>\n<\/td>\n<\/tr>\n \nobject_count<\/code><\/p>\n<\/td>\n \nThe maximum number of objects to return. See\u00a0SET_COUNT Procedure<\/a>\u00a0.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n <\/a><\/h6>\nReturn Values<\/h6>\n The metadata for the specified object as XML or DDL.<\/h6>\n<\/a><\/h6>\nUsage Notes<\/h6>\n\n\nThese functions allow you to fetch metadata for objects with a single call. They encapsulate calls to\u00a0OPEN<\/code>,\u00a0SET_FILTER<\/code>, and so on. The function you use depends on the characteristics of the object type and on whether you want XML or DDL.<\/h6>\n\n\nGET_xxx<\/code>\u00a0is used to fetch named objects, especially schema objects (tables, views).<\/h6>\n<\/li>\n\nGET_DEPENDENT_xxx<\/code>\u00a0is used to fetch dependent objects (audits, object grants).<\/h6>\n<\/li>\n\nGET_GRANTED_xxx<\/code>\u00a0is used to fetch granted objects (system grants, role grants).<\/h6>\n<\/li>\n<\/ul>\n<\/li>\n\nFor some object types you can use more than one function. For example, you can use\u00a0GET_xxx<\/code>\u00a0to fetch an index by name, or\u00a0GET_DEPENDENT_xxx<\/code>\u00a0to fetch the same index by specifying the table on which it is defined.<\/h6>\n<\/li>\n\nGET_xxx<\/code>\u00a0only returns a single named object.<\/h6>\n<\/li>\n\nFor\u00a0GET_DEPENDENT_xxx<\/code>\u00a0and\u00a0GET_GRANTED_xxx,<\/code>\u00a0an arbitrary number of dependent or granted objects can match the input criteria. You can specify an object count when fetching these objects. (The default count of 10000 should be adequate in most cases.)<\/h6>\n<\/li>\n\nIf the DDL transform is specified, session-level transform parameters are inherited.<\/h6>\n<\/li>\n\nIf you invoke these functions from SQL*Plus, you should set the\u00a0PAGESIZE<\/code>\u00a0to 0 and set\u00a0LONG<\/code>\u00a0to some large number to get complete, uninterrupted output.<\/h6>\n<\/li>\n<\/ul>\n<\/a><\/h6>\nExceptions<\/h6>\n\n\nINVALID_ARGVAL<\/code>. A\u00a0NULL<\/code>\u00a0or invalid value was supplied for an input parameter. The error message text identifies the parameter.<\/h6>\n<\/li>\n\nOBJECT_NOT_FOUND<\/code>. The specified object was not found in the database.<\/h6>\n<\/li>\n<\/ul>\n<\/a><\/h6>\nExamples<\/h6>\n<\/a><\/h6>\nExample: Fetch the XML Representation of SCOTT.EMP<\/h6>\nTo generate complete, uninterrupted output, set the\u00a0PAGESIZE<\/code>\u00a0to 0 and set\u00a0LONG<\/code>\u00a0to some large number, as shown, before executing your query.<\/h6>\nSET LONG 2000000 SET PAGESIZE 0 SELECT DBMS_METADATA.GET_XML(‘TABLE’,’EMP’,’SCOTT’) FROM DUAL;<\/h6>\n<\/a><\/h6>\nExample: Fetch the DDL for all Complete Tables in the Current Schema, Filter Out Nested Tables and Overflow Segments<\/h6>\nThis example fetches the DDL for all “complete” tables in the current schema, filtering out nested tables and overflow segments. The example uses\u00a0SET_TRANSFORM_PARAM<\/code>\u00a0(with the handle value =\u00a0DBMS_METADATA.SESSION_TRANSFORM<\/code>\u00a0meaning “for the current session”) to specify that storage clauses are not to be returned in the SQL DDL. Afterwards, the example resets the session-level parameters to their defaults.<\/h6>\nTo generate complete, uninterrupted output, set the\u00a0PAGESIZE<\/code>\u00a0to 0 and set\u00a0LONG<\/code>\u00a0to some large number, as shown, before executing your query.<\/h6>\nSET LONG 2000000 SET PAGESIZE 0 EXECUTE DBMS_METADATA.SET_TRANSFORM_PARAM(DBMS_METADATA.SESSION_TRANSFORM,’STORAGE’,false); SELECT DBMS_METADATA.GET_DDL(‘TABLE’,u.table_name) FROM USER_ALL_TABLES u WHERE u.nested=’NO’ AND (u.iot_type is null or u.iot_type=’IOT’); EXECUTE DBMS_METADATA.SET_TRANSFORM_PARAM(DBMS_METADATA.SESSION_TRANSFORM,’DEFAULT’);<\/h6>\n<\/a><\/h6>\nExample: Fetch the DDL For All Object Grants On HR.EMPLOYEES<\/h6>\n SELECT DBMS_METADATA.GET_DEPENDENT_DDL(‘OBJECT_GRANT’, ‘EMPLOYEES’,’HR’) FROM DUAL;<\/h6>\n<\/a><\/h6>\nExample: Fetch the DDL For All System Grants Granted To SCOTT<\/h6>\n SELECT DBMS_METADATA.GET_GRANTED_DDL(‘SYSTEM_GRANT’,’SCOTT’) FROM DUAL;<\/h6>\n<\/a><\/h6>\n \nGET_QUERY Function<\/a><\/h6>\nThis function returns the text of the queries that are used by\u00a0FETCH_xxx<\/code>. This function assists in debugging.<\/h6>\n\n\n\n\n\nSee Also:<\/p>\n For more information about related subprograms:<\/p>\n \n\nSubprograms for Retrieving Multiple Objects From the Database<\/a><\/p>\n<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n <\/a><\/h6>\nSyntax<\/h6>\n DBMS_METADATA.GET_QUERY ( handle IN NUMBER) RETURN VARCHAR2;<\/h6>\n<\/a><\/h6>\nParameters<\/h6>\n<\/a><\/a><\/h6>\nTable 57-9 GET_QUERY Function Parameters<\/p>\n\n\n\n\n\nParameter<\/th>\n Description<\/th>\n<\/tr>\n<\/thead>\n \nhandle<\/code><\/p>\n<\/td>\n \nThe handle returned from\u00a0OPEN<\/code>. It cannot be the handle for a heterogeneous object type.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n <\/a><\/h6>\nReturn Values<\/h6>\nThe text of the queries that will be used by\u00a0FETCH_xxx.<\/code><\/h6>\n<\/a><\/h6>\nExceptions<\/h6>\n\n\nINVALID_ARGVAL<\/code>. A\u00a0NULL<\/code>\u00a0or invalid value was supplied for the\u00a0handle<\/code>\u00a0parameter.<\/h6>\n<\/li>\n<\/ul>\n<\/a><\/h6>\n \nOPEN Function<\/a><\/h6>\nThis function specifies the type of object to be retrieved, the version of its metadata, and the object model. The return value is an opaque context handle for the set of objects to be used in subsequent calls.<\/h6>\n\n\n\n\n\nSee Also:<\/p>\n For more information about related subprograms:<\/p>\n \n\nSubprograms for Retrieving Multiple Objects From the Database<\/a><\/p>\n<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n <\/a><\/h6>\nSyntax<\/h6>\n DBMS_METADATA.OPEN ( object_type IN VARCHAR2, version IN VARCHAR2 DEFAULT ‘COMPATIBLE’, model IN VARCHAR2 DEFAULT ‘ORACLE’, network_link IN VARCHAR2 DEFAULT NULL) RETURN NUMBER;<\/h6>\n<\/a><\/h6>\nParameters<\/h6>\n<\/a><\/a><\/h6>\nTable 57-10 Open Function Parameters<\/p>\n\n\n\n\n\n\n\n\nParameter<\/th>\n Description<\/th>\n<\/tr>\n<\/thead>\n \nobject_type<\/code><\/p>\n<\/td>\n \nThe type of object to be retrieved.\u00a0Table 57-11<\/a>\u00a0lists the valid type names and their meanings. These object types will be supported for the ORACLE model of metadata (see\u00a0model<\/code><\/a>\u00a0in this table).<\/p>\n The Attributes column in\u00a0Table 57-11<\/a>\u00a0specifies some object type attributes:<\/p>\n \n\nSchema objects, such as tables, belong to schemas.<\/p>\n<\/li>\n \nNamed objects have unique names (if they are schema objects, the name is unique to the schema).<\/p>\n<\/li>\n \nDependent objects, such as indexes, are defined with reference to a base schema object.<\/p>\n<\/li>\n \nGranted objects are granted or assigned to a user or role and therefore have a named grantee.<\/p>\n<\/li>\n\nHeterogeneous object types denote a collection of related objects of different types. See\u00a0Table 57-12<\/a>\u00a0for a listing of object types returned for the heterogeneous object type.<\/p>\n<\/li>\n<\/ul>\n These attributes are relevant when choosing object selection criteria. See\u00a0“SET_FILTER Procedure”<\/a>\u00a0for more information.<\/p>\n<\/td>\n<\/tr>\n \nversion<\/code><\/p>\n<\/td>\n \nThe version of metadata to be extracted. Database objects or attributes that are incompatible with the version will not be extracted. Legal values for this parameter are as follows:<\/p>\n COMPATIBLE<\/code>\u00a0(default)\u2014the version of the metadata corresponds to the database compatibility level.<\/p>\n LATEST<\/code>\u2014the version of the metadata corresponds to the database version.<\/p>\n A specific database version, for example, 9.2.0. As of Oracle Database 10g<\/span>, this value cannot be lower than 9.2.0.<\/p>\n<\/td>\n<\/tr>\n <\/a><\/p>\nmodel<\/code><\/p>\n<\/td>\n \nSpecifies which view to use, because the API can support multiple views on the metadata. Only the ORACLE model is supported as of Oracle Database 10g<\/span>.<\/p>\n<\/td>\n<\/tr>\n \nnetwork_link<\/code><\/p>\n<\/td>\n \nReserved.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Table 57-11<\/a>\u00a0provides the name, meaning, attributes, and notes for the\u00a0DBMS_METADATA<\/code>\u00a0package object types. In the attributes column,\u00a0S<\/code>\u00a0represents a schema object,\u00a0N<\/code>\u00a0represents a named object,\u00a0D<\/code>\u00a0represents a dependent object,\u00a0G<\/code>\u00a0represents a granted object, and\u00a0H<\/code>\u00a0represents a heterogeneous object.<\/h6>\n<\/a><\/a><\/h6>\nTable 57-11 DBMS_METADATA: Object Types<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nType Name<\/th>\n Meaning<\/th>\n Attributes<\/th>\n Notes<\/th>\n<\/tr>\n<\/thead>\n \nAQ_QUEUE<\/code><\/p>\n<\/td>\n \nqueues<\/p>\n<\/td>\n \nSND<\/code><\/p>\n<\/td>\n \nDependent on table<\/p>\n<\/td>\n<\/tr>\n \nAQ_QUEUE_TABLE<\/code><\/p>\n<\/td>\n \nadditional metadata for queue tables<\/p>\n<\/td>\n \nND<\/code><\/p>\n<\/td>\n \nDependent on table<\/p>\n<\/td>\n<\/tr>\n \nAQ_TRANSFORM<\/code><\/p>\n<\/td>\n \ntransforms<\/p>\n<\/td>\n \nSN<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nASSOCIATION<\/code><\/p>\n<\/td>\n \nassociate statistics<\/p>\n<\/td>\n \nD<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nAUDIT<\/code><\/p>\n<\/td>\n \naudits of SQL statements<\/p>\n<\/td>\n \nDG<\/code><\/p>\n<\/td>\n \nModeled as dependent, granted object. The base object name is the statement audit option name (for example,\u00a0ALTER<\/code>\u00a0SYSTEM<\/code>). There is no base object schema. The grantee is the user or proxy whose statements are audited.<\/p>\n<\/td>\n<\/tr>\n \nAUDIT_OBJ<\/code><\/p>\n<\/td>\n \naudits of schema objects<\/p>\n<\/td>\n \nD<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nCLUSTER<\/code><\/p>\n<\/td>\n \nclusters<\/p>\n<\/td>\n \nSN<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nCOMMENT<\/code><\/p>\n<\/td>\n \ncomments<\/p>\n<\/td>\n \nD<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nCONSTRAINT<\/code><\/p>\n<\/td>\n \nconstraints<\/p>\n<\/td>\n \nSND<\/code><\/p>\n<\/td>\n \nDoes not include:<\/p>\n \n\nprimary key constraint for IOT<\/p>\n<\/li>\n \ncolumn\u00a0NOT<\/code>\u00a0NULL<\/code>\u00a0constraints<\/p>\n<\/li>\n \ncertain\u00a0REF<\/code>\u00a0SCOPE<\/code>\u00a0and\u00a0WITH<\/code>\u00a0ROWID<\/code>\u00a0constraints for tables with\u00a0REF<\/code>\u00a0columns<\/p>\n<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n \nCONTEXT<\/code><\/p>\n<\/td>\n \napplication contexts<\/p>\n<\/td>\n \nN<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nall metadata objects in a database<\/p>\n<\/td>\n \nH<\/code><\/p>\n<\/td>\n \nCorresponds to a full database export<\/p>\n<\/td>\n<\/tr>\n \nDB_LINK<\/code><\/p>\n<\/td>\n \ndatabase links<\/p>\n<\/td>\n \nSN<\/code><\/p>\n<\/td>\n \nModeled as schema objects because they have owners. For public links, the owner is PUBLIC. For private links, the creator is the owner.<\/p>\n<\/td>\n<\/tr>\n \nDEFAULT_ROLE<\/code><\/p>\n<\/td>\n \ndefault roles<\/p>\n<\/td>\n \nG<\/code><\/p>\n<\/td>\n \nGranted to a user by\u00a0ALTER<\/code>\u00a0USER<\/code><\/p>\n<\/td>\n<\/tr>\n \nDIMENSION<\/code><\/p>\n<\/td>\n \ndimensions<\/p>\n<\/td>\n \nSN<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nDIRECTORY<\/code><\/p>\n<\/td>\n \ndirectories<\/p>\n<\/td>\n \nN<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nFGA_POLICY<\/code><\/p>\n<\/td>\n \nfine-grained audit policies<\/p>\n<\/td>\n \nD<\/code><\/p>\n<\/td>\n \nNot modeled as named object because policy names are not unique.<\/p>\n<\/td>\n<\/tr>\n \nFUNCTION<\/code><\/p>\n<\/td>\n \nstored functions<\/p>\n<\/td>\n \nSN<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nINDEX_STATISTICS<\/code><\/p>\n<\/td>\n \nprecomputed statistics on indexes<\/p>\n<\/td>\n \nD<\/code><\/p>\n<\/td>\n \nThe base object is the index’s table.<\/p>\n<\/td>\n<\/tr>\n \nINDEX<\/code><\/p>\n<\/td>\n \nindexes<\/p>\n<\/td>\n \nSND<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nINDEXTYPE<\/code><\/p>\n<\/td>\n \nindextypes<\/p>\n<\/td>\n \nSN<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nJAVA_SOURCE<\/code><\/p>\n<\/td>\n \nJava sources<\/p>\n<\/td>\n \nSN<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nJOB<\/code><\/p>\n<\/td>\n \njobs<\/p>\n<\/td>\n \nS<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nLIBRARY<\/code><\/p>\n<\/td>\n \nexternal procedure libraries<\/p>\n<\/td>\n \nSN<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nMATERIALIZED_VIEW<\/code><\/p>\n<\/td>\n \nmaterialized views<\/p>\n<\/td>\n \nSN<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nMATERIALIZED_VIEW_LOG<\/code><\/p>\n<\/td>\n \nmaterialized view logs<\/p>\n<\/td>\n \nD<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nOBJECT_GRANT<\/code><\/p>\n<\/td>\n \nobject grants<\/p>\n<\/td>\n \nDG<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nOPERATOR<\/code><\/p>\n<\/td>\n \noperators<\/p>\n<\/td>\n \nSN<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nOUTLINE<\/code><\/p>\n<\/td>\n \nstored outlines<\/p>\n<\/td>\n \nN<\/code><\/p>\n<\/td>\n \nThis type is being deprecated.<\/p>\n<\/td>\n<\/tr>\n \nPACKAGE<\/code><\/p>\n<\/td>\n \nstored packages<\/p>\n<\/td>\n \nSN<\/code><\/p>\n<\/td>\n \nBy default, both package specification and package body are retrieved. See\u00a0“SET_FILTER Procedure”<\/a>.<\/p>\n<\/td>\n<\/tr>\n \nPACKAGE_SPEC<\/code><\/p>\n<\/td>\n \npackage specifications<\/p>\n<\/td>\n \nSN<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nPACKAGE_BODY<\/code><\/p>\n<\/td>\n \npackage bodies<\/p>\n<\/td>\n \nSN<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nPROCEDURE<\/code><\/p>\n<\/td>\n \nstored procedures<\/p>\n<\/td>\n \nSN<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nPROFILE<\/code><\/p>\n<\/td>\n \nprofiles<\/p>\n<\/td>\n \nN<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nPROXY<\/code><\/p>\n<\/td>\n \nproxy authentications<\/p>\n<\/td>\n \nG<\/code><\/p>\n<\/td>\n \nGranted to a user by\u00a0ALTER<\/code>\u00a0USER<\/code><\/p>\n<\/td>\n<\/tr>\n \nREF_CONSTRAINT<\/code><\/p>\n<\/td>\n \nreferential constraint<\/p>\n<\/td>\n \nSND<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nREFRESH_GROUP<\/code><\/p>\n<\/td>\n \nrefresh groups<\/p>\n<\/td>\n \nSN<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nRESOURCE_COST<\/code><\/p>\n<\/td>\n \nresource cost info<\/p>\n<\/td>\n <\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nRLS_CONTEXT<\/code><\/p>\n<\/td>\n \ndriving contexts for enforcement of fine-grained access-control policies<\/p>\n<\/td>\n \nD<\/code><\/p>\n<\/td>\n \nCorresponds to the DBMS_RLS.ADD_POLICY_CONTENT procedure<\/p>\n<\/td>\n<\/tr>\n \nRLS_GROUP<\/code><\/p>\n<\/td>\n \nfine-grained access-control policy groups<\/p>\n<\/td>\n \nD<\/code><\/p>\n<\/td>\n \nCorresponds to the DBMS_RLS.CREATE_GROUP procedure<\/p>\n<\/td>\n<\/tr>\n \nRLS_POLICY<\/code><\/p>\n<\/td>\n \nfine-grained access-control policies<\/p>\n<\/td>\n \nD<\/code><\/p>\n<\/td>\n \nCorresponds to DBMS_RLS.ADD_GROUPED_POLICY. Not modeled as named objects because policy names are not unique.<\/p>\n<\/td>\n<\/tr>\n \nRMGR_CONSUMER_GROUP<\/code><\/p>\n<\/td>\n \nresource consumer groups<\/p>\n<\/td>\n \nSN<\/code><\/p>\n<\/td>\n \nData Pump does not use these object types. Instead, it exports resource manager objects as procedural objects.<\/p>\n<\/td>\n<\/tr>\n \nRMGR_INTITIAL_CONSUMER_GROUP<\/code><\/p>\n<\/td>\n \nassign initial consumer groups to users<\/p>\n<\/td>\n \nG<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nRMGR_PLAN<\/code><\/p>\n<\/td>\n \nresource plans<\/p>\n<\/td>\n \nSN<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nRMGR_PLAN_DIRECTIVE<\/code><\/p>\n<\/td>\n \nresource plan directives<\/p>\n<\/td>\n \nD<\/code><\/p>\n<\/td>\n \nDependent on resource plan<\/p>\n<\/td>\n<\/tr>\n \nROLE<\/code><\/p>\n<\/td>\n \nroles<\/p>\n<\/td>\n \nN<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nROLE_GRANT<\/code><\/p>\n<\/td>\n \nrole grants<\/p>\n<\/td>\n \nG<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nROLLBACK_SEGMENT<\/code><\/p>\n<\/td>\n \nrollback segments<\/p>\n<\/td>\n \nN<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nall metadata objects in a schema<\/p>\n<\/td>\n \nH<\/code><\/p>\n<\/td>\n \nCorresponds to user-mode export.<\/p>\n<\/td>\n<\/tr>\n \nSEQUENCE<\/code><\/p>\n<\/td>\n \nsequences<\/p>\n<\/td>\n \nSN<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nSYNONYM<\/code><\/p>\n<\/td>\n \nsynonyms<\/p>\n<\/td>\n \nSee notes<\/code><\/p>\n<\/td>\n \nPrivate synonyms are schema objects. Public synonyms are not, but for the purposes of this API, their schema name is\u00a0PUBLIC<\/code>. The name of a synonym is considered to be the synonym itself. For example, in\u00a0CREATE PUBLIC SYNONYM FOO FOR BAR<\/code>, the resultant object is considered to have name\u00a0FOO<\/code>\u00a0and schema\u00a0PUBLIC<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nSYSTEM_GRANT<\/code><\/p>\n<\/td>\n \nsystem privilege grants<\/p>\n<\/td>\n \nG<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nTABLE<\/code><\/p>\n<\/td>\n \ntables<\/p>\n<\/td>\n \nSN<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nTABLE_DATA<\/code><\/p>\n<\/td>\n \nmetadata describing row data for a table, nested table, or partition<\/p>\n<\/td>\n \nSND<\/code><\/p>\n<\/td>\n \nFor partitions, the object name is the partition name.<\/p>\n For nested tables, the object name is the storage table name. The base object is the top-level table to which the table data belongs. For nested tables and partitioning, this is the top-level table (not<\/span>\u00a0the parent table or partition). For nonpartitioned tables and non-nested tables this is the table itself.<\/p>\n<\/td>\n<\/tr>\n \nTABLE_EXPORT<\/code><\/p>\n<\/td>\n \nmetadata for a table and its associated objects<\/p>\n<\/td>\n \nH<\/code><\/p>\n<\/td>\n \nCorresponds to table-mode export<\/p>\n<\/td>\n<\/tr>\n \nTABLE_STATISTICS<\/code><\/p>\n<\/td>\n \nprecomputed statistics on tables<\/p>\n<\/td>\n \nD<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nTABLESPACE<\/code><\/p>\n<\/td>\n \ntablespaces<\/p>\n<\/td>\n \nN<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nTABLESPACE_QUOTA<\/code><\/p>\n<\/td>\n \ntablespace quotas<\/p>\n<\/td>\n \nG<\/code><\/p>\n<\/td>\n \nGranted with\u00a0ALTER<\/code>\u00a0USER<\/code><\/p>\n<\/td>\n<\/tr>\n \nTRANSPORTABLE_EXPORT<\/code><\/p>\n<\/td>\n \nmetadata for objects in a transportable tablespace set<\/p>\n<\/td>\n \nH<\/code><\/p>\n<\/td>\n \nCorresponds to transportable tablespace export<\/p>\n<\/td>\n<\/tr>\n \nTRIGGER<\/code><\/p>\n<\/td>\n \ntriggers<\/p>\n<\/td>\n \nSND<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nTRUSTED_DB_LINK<\/code><\/p>\n<\/td>\n \ntrusted links<\/p>\n<\/td>\n \nN<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nTYPE<\/code><\/p>\n<\/td>\n \nuser-defined types<\/p>\n<\/td>\n \nSN<\/code><\/p>\n<\/td>\n \nBy default, both type and type body are retrieved. See\u00a0“SET_FILTER Procedure”<\/a>.<\/p>\n<\/td>\n<\/tr>\n \nTYPE_SPEC<\/code><\/p>\n<\/td>\n \ntype specifications<\/p>\n<\/td>\n \nSN<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nTYPE_BODY<\/code><\/p>\n<\/td>\n \ntype bodies<\/p>\n<\/td>\n \nSN<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nUSER<\/code><\/p>\n<\/td>\n \nusers<\/p>\n<\/td>\n \nN<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nVIEW<\/code><\/p>\n<\/td>\n \nviews<\/p>\n<\/td>\n \nSN<\/code><\/p>\n<\/td>\n \nNone<\/p>\n<\/td>\n<\/tr>\n \nXMLSCHEMA<\/code><\/p>\n<\/td>\n \nXML schema<\/p>\n<\/td>\n \nSN<\/code><\/p>\n<\/td>\n \nThe object’s name is its URL (which may be longer than 30 characters). Its schema is the user who registered it.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Table 57-12<\/a>\u00a0lists the types of objects returned for the major heterogeneous object types. For\u00a0SCHEMA_EXPORT<\/code>, certain object types are only returned if the\u00a0INCLUDE_USER<\/code>\u00a0filter is specified at\u00a0TRUE<\/code>. In the table, such object types are marked\u00a0INCLUDE_USER<\/code>.<\/h6>\n<\/a><\/a><\/h6>\nTable 57-12 Object Types Returned for the Heterogeneous Object Type<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nObject Type<\/th>\n DATABASE_EXPORT<\/th>\n SCHEMA_EXPORT<\/th>\n TABLE_EXPORT<\/th>\n TRANSPORTABLE_EXPORT<\/th>\n<\/tr>\n<\/thead>\n \nASSOCIATION<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nAUDIT<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nAUDIT_OBJ<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n<\/tr>\n \nCLUSTER<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n<\/tr>\n \nCOMMENT<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n<\/tr>\n \nCONSTRAINT<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n<\/tr>\n \nCONTEXT<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nDB_LINK<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nDEFAULT_ROLE<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nINCLUDE_USER<\/code><\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nDIMENSION<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nDIRECTORY<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nFGA_POLICY<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n<\/tr>\n \nFUNCTION<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nINDEX_STATISTICS<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n<\/tr>\n \nINDEX<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n<\/tr>\n \nINDEXTYPE<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nJAVA_SOURCE<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nJOB<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nLIBRARY<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nMATERIALIED_VIEW<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nMATERIALIZED_VIEW_LOG<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nOBJECT_GRANT<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n<\/tr>\n \nOPERATOR<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nOUTLINE<\/code><\/p>\n<\/td>\n \nIf\u00a0OUTLN<\/code>\u00a0user’s objects are returned<\/p>\n<\/td>\n \nif user is\u00a0OUTLN<\/code><\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nPACKAGE<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nPACKAGE_SPEC<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nPACKAGE_BODY<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nPASSWORD_HISTORY<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nINCLUDE_USER<\/code><\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nPASSWORD_VERIFY_FUNCTION<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nPROCEDURE<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nPROFILE<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nPROXY<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nREF_CONSTRAINT<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n<\/tr>\n \nREFRESH_GROUP<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nRESOURCE_COST<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nRLS_CONTEXT<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n<\/tr>\n \nRLS_GROUP<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n<\/tr>\n \nRLS_POLICY<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nTable data is retrieved according to policy<\/p>\n<\/td>\n \nTable data is retrieved according to policy<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n<\/tr>\n \nROLE<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nROLE_GRANT<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nROLLBACK_SEGMENT<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nSEQUENCE<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nSYNONYM<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nSYSTEM_GRANT<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nINCLUDE_USER<\/code><\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nTABLE<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n<\/tr>\n \nTABLE_DATA<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n<\/tr>\n \nTABLE_STATISTICS<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n<\/tr>\n \nTABLESPACE<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nTABLESPACE_QUOTA<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nINCLUDE_USER<\/code><\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nTRIGGER<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n<\/tr>\n \nTRUSTED_DB_LINK<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nTYPE<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nYes, if the types are used by tables in the transportable set<\/p>\n<\/td>\n<\/tr>\n \nTYPE_SPEC<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nYes, if the types are used by tables in the transportable set<\/p>\n<\/td>\n<\/tr>\n \nTYPE_BODY<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nYes, if the types are used by tables in the transportable set<\/p>\n<\/td>\n<\/tr>\n \nUSER<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nINCLUDE_USER<\/code><\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nVIEW<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n \nXMLSCHEMA<\/code><\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nYes<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n \nNo<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n <\/a><\/h6>\nReturn Values<\/h6>\nAn opaque handle to the class of objects. This handle is used as input to\u00a0SET_FILTER<\/code>,\u00a0SET_COUNT,<\/code>\u00a0ADD_TRANSFORM<\/code>,\u00a0GET_QUERY,<\/code>\u00a0SET_PARSE_ITEM,<\/code>\u00a0FETCH_xxx,<\/code>\u00a0and\u00a0CLOSE<\/code>.<\/h6>\n<\/a><\/h6>\nExceptions<\/h6>\n\n\nINVALID_ARGVAL<\/code>. A\u00a0NULL<\/code>\u00a0or invalid value was supplied for an input parameter. The error message text identifies the parameter.<\/h6>\n<\/li>\n\nINVALID_OBJECT_PARAM<\/code>. The\u00a0version<\/code>\u00a0or\u00a0model<\/code>\u00a0parameter was not valid for the\u00a0object_type<\/code>.<\/h6>\n<\/li>\n<\/ul>\n<\/a><\/h6>\n \nOPENW Function<\/a><\/h6>\nThis function specifies the type of object to be submitted and the object model. The return value is an opaque context handle.<\/h6>\n\n\n\n\n\nSee Also:<\/p>\n For more information about related subprograms:<\/p>\n \n\nSubprograms for Submitting XML to the Database<\/a><\/p>\n<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n <\/a><\/h6>\nSyntax<\/h6>\n DBMS_METADATA.OPENW (object_type IN VARCHAR2, version IN VARCHAR2 DEFAULT ‘COMPATIBLE’, model IN VARCHAR2 DEFAULT ‘ORACLE’) RETURN NUMBER;<\/h6>\n<\/a><\/h6>\nParameters<\/h6>\n<\/a><\/a><\/h6>\nTable 57-13 OPENW Function Parameters<\/p>\n\n\n\n\n\n\n\nParameter<\/th>\n Description<\/th>\n<\/tr>\n<\/thead>\n \nobject_type<\/code><\/p>\n<\/td>\n \nThe type of object to be submitted. Valid types names and their meanings are listed in\u00a0Table 57-11<\/a>. The type cannot be a heterogeneous object type.<\/p>\n<\/td>\n<\/tr>\n \nversion<\/code><\/p>\n<\/td>\n \nThe version of DDL to be generated by the\u00a0CONVERT<\/code>\u00a0function. DDL clauses that are incompatible with the version will not be generated. The legal values for this parameter are as follows:<\/p>\n \n\nCOMPATIBLE<\/code>\u00a0– This is the default. The version of the DDL corresponds to the database compatibility level. Database compatibility must be set to 9.2.0 or higher.<\/p>\n<\/li>\n \nLATEST<\/code>\u00a0– The version of the DDL corresponds to the database version.<\/p>\n<\/li>\n \nA specific database version. As of Oracle Database 10g<\/span>, this value cannot be lower than 9.2.0.<\/p>\n<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n \nmodel<\/code><\/p>\n<\/td>\n \nSpecifies which view to use. Only the Oracle proprietary (ORACLE) view is supported by\u00a0DBMS_METADATA<\/code>.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n <\/a><\/h6>\nReturn Values<\/h6>\nAn opaque handle to write context. This handle is used as input to the\u00a0ADD_TRANSFORM<\/code>,\u00a0CONVERT<\/code>,\u00a0PUT<\/code>, and\u00a0CLOSE<\/code>\u00a0procedures.<\/h6>\n<\/a><\/h6>\nExceptions<\/h6>\n\n\nINVALID_ARGVAL<\/code>. A NULL or invalid value was supplied for an input parameter. The error message text identifies the parameter.<\/h6>\n<\/li>\n\nINVALID_OBJECT_PARAM<\/code>. The\u00a0model<\/code>\u00a0parameter was not valid for the\u00a0object_type<\/code>.<\/h6>\n<\/li>\n<\/ul>\n<\/a><\/h6>\n \nPUT Function<\/a><\/h6>\nThis function submits an XML document containing object metadata to the database to create the object.<\/h6>\n\n\n\n\n\nSee Also:<\/p>\n For more information about related subprograms:<\/p>\n \n\nSubprograms for Submitting XML to the Database<\/a><\/p>\n<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n <\/a><\/h6>\nSyntax<\/h6>\n DBMS_METADATA.PUT ( handle IN NUMBER, document IN sys.XMLType, flags IN NUMBER, results IN OUT NOCOPY sys.ku$_SubmitResults) RETURN BOOLEAN; DBMS_METADATA.PUT ( handle IN NUMBER, document IN CLOB, flags IN NUMBER, results IN OUT NOCOPY sys.ku$_SubmitResults) RETURN BOOLEAN;<\/h6>\n<\/a><\/h6>\nParameters<\/h6>\n<\/a><\/a><\/h6>\nTable 57-14 PUT Function Parameters<\/p>\n\n\n\n\n\n\n\n\nParameter<\/th>\n Description<\/th>\n<\/tr>\n<\/thead>\n \nhandle<\/code><\/p>\n<\/td>\n \nThe handle returned from\u00a0OPENW<\/code>.<\/p>\n<\/td>\n<\/tr>\n \ndocument<\/code><\/p>\n<\/td>\n \nThe XML document containing object metadata for the type of the\u00a0OPENW<\/code>\u00a0handle.<\/p>\n<\/td>\n<\/tr>\n \nflags<\/code><\/p>\n<\/td>\n \nReserved for future use<\/p>\n<\/td>\n<\/tr>\n \nresults<\/code><\/p>\n<\/td>\n \nDetailed results of the operation.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n <\/a><\/h6>\nReturn Values<\/h6>\nTRUE<\/code>\u00a0if all SQL operations succeeded;\u00a0FALSE<\/code>\u00a0if there were any errors.<\/h6>\n<\/a><\/h6>\nUsage Notes<\/h6>\nThe\u00a0PUT<\/code>\u00a0function converts the XML document to DDL just as\u00a0CONVERT<\/code>\u00a0does (applying the specified transforms in turn) and then submits each resultant DDL statement to the database. As with\u00a0CONVERT<\/code>, the DDL transform must be specified. The DDL statements and associated parse items are returned in the\u00a0sys<\/code>.ku$_SubmitResults<\/code>\u00a0nested table. With each DDL statement is a nested table of error lines containing any errors or exceptions raised by the statement.<\/h6>\nThe encoding of the XML document is embedded in its CLOB or XMLType representation. The version of the metadata is embedded in the XML. The generated DDL is valid for the database version specified in\u00a0OPENW<\/code>.<\/h6>\n<\/a><\/h6>\nExceptions<\/h6>\n\n\nINVALID_ARGVAL<\/code>. A NULL or invalid value was supplied for an input parameter. The error message text identifies the parameter.<\/h6>\n<\/li>\n\nINCONSISTENT_OPERATION<\/code>. The DDL transform was not specified.<\/h6>\n<\/li>\n\nINCOMPATIBLE_DOCUMENT<\/code>. The version of the XML document is not compatible with this version of the software.<\/h6>\n<\/li>\n<\/ul>\n<\/a><\/h6>\n \nSET_COUNT Procedure<\/a><\/h6>\nThis procedure specifies the maximum number of objects to be retrieved in a single\u00a0FETCH_xxx<\/code>\u00a0call. By default, each call to\u00a0FETCH_xxx<\/code>\u00a0returns one object. You can use the\u00a0SET_COUNT<\/code>\u00a0procedure to override this default. If\u00a0FETCH_xxx<\/code>\u00a0is called from a client, specifying a count value greater than 1 can result in fewer server round trips and, therefore, improved performance.<\/h6>\nFor heterogeneous object types, a single\u00a0FETCH_xxx<\/code>\u00a0operation only returns objects of a single object type.<\/h6>\n\n\n\n\n\nSee Also:<\/p>\n For more information about related subprograms:<\/p>\n \n\nSubprograms for Retrieving Multiple Objects From the Database<\/a><\/p>\n<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n <\/a><\/h6>\nSyntax<\/h6>\n DBMS_METADATA.SET_COUNT ( handle IN NUMBER, value IN NUMBER, object_type_path IN VARCHAR2 DEFAULT NULL);<\/h6>\n<\/a><\/h6>\nParameters<\/h6>\n<\/a><\/a><\/h6>\nTable 57-15 SET_COUNT Procedure Parameters<\/p>\n\n\n\n\n\n\n\nParameter<\/th>\n Description<\/th>\n<\/tr>\n<\/thead>\n \nhandle<\/code><\/p>\n<\/td>\n \nThe handle returned from\u00a0OPEN<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nvalue<\/code><\/p>\n<\/td>\n \nThe maximum number of objects to retrieve.<\/p>\n<\/td>\n<\/tr>\n \nobject_type_path<\/code><\/p>\n<\/td>\n \nA path name designating the object types to which the count value applies. By default, the count value applies to the object type of the\u00a0OPEN<\/code>\u00a0handle. When the\u00a0OPEN<\/code>\u00a0handle designates a heterogeneous object type, behavior can be either of the following:<\/p>\n \n\nif\u00a0object_type_path<\/code>\u00a0is omitted, the count applies to all object types within the heterogeneous collection<\/p>\n<\/li>\n \nif\u00a0object_type_path<\/code>\u00a0is specified, the count only applies to the specific node (or set of nodes) within the tree of object types forming the heterogeneous collection<\/p>\n<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n <\/a><\/h6>\nExceptions<\/h6>\n\n\nINVALID_ARGVAL<\/code>. A\u00a0NULL<\/code>\u00a0or invalid value was supplied for an input parameter. The error message text identifies the parameter.<\/h6>\n<\/li>\n\nINVALID_OPERATION<\/code>.\u00a0SET_COUNT<\/code>\u00a0was called after the first call to\u00a0FETCH_xxx<\/code>\u00a0for the\u00a0OPEN<\/code>\u00a0context. After the first call to\u00a0FETCH_xxx<\/code>\u00a0is made, no further calls to\u00a0SET_COUNT<\/code>\u00a0for the current\u00a0OPEN<\/code>\u00a0context are permitted.<\/h6>\n<\/li>\n\nINCONSISTENT_ARGS<\/code>.\u00a0object_type<\/code>\u00a0parameter is not consistent with handle.<\/h6>\n<\/li>\n<\/ul>\n<\/a><\/h6>\n \nSET_FILTER Procedure<\/a><\/h6>\nThis procedure specifies restrictions on the objects to be retrieved, for example, the object name or schema.<\/h6>\n\n\n\n\n\nSee Also:<\/p>\n For more information about related subprograms:<\/p>\n \n\nSubprograms for Retrieving Multiple Objects From the Database<\/a><\/p>\n<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n <\/a><\/h6>\nSyntax<\/h6>\n DBMS_METADATA.SET_FILTER ( handle IN NUMBER, name IN VARCHAR2, value IN VARCHAR2, object_type_path IN VARCHAR2 DEFAULT NULL); DBMS_METADATA.SET_FILTER ( handle IN NUMBER, name IN VARCHAR2, value IN BOOLEAN DEFAULT TRUE, object_type_path IN VARCHAR2 DEFAULT NULL); DBMS_METADATA.SET_FILTER ( handle IN NUMBER, name IN VARCHAR2, value IN NUMBER, object_type_path IN VARCHAR2 DEFAULT NULL);<\/h6>\n<\/a><\/h6>\nParameters<\/h6>\n<\/a><\/a><\/h6>\nTable 57-16 SET_FILTER Procedure Parameters<\/p>\n\n\n\n\n\n\n\n\nParameter<\/th>\n Description<\/th>\n<\/tr>\n<\/thead>\n \nhandle<\/code><\/p>\n<\/td>\n \nThe handle returned from\u00a0OPEN<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nname<\/code><\/p>\n<\/td>\n \nThe name of the filter. For each filter,\u00a0Table 57-17<\/a>\u00a0lists the\u00a0object_type<\/code>\u00a0it applies to, its name, its datatype (text or Boolean) and its meaning or effect (including its default value, if any).<\/p>\n The Datatype column of\u00a0Table 57-17<\/a>\u00a0also indicates whether a text filter is an expression filter. An expression filter is the right-hand side of a SQL comparison (that is, a SQL comparison operator (=, !=, and so on.)) and the value compared against. The value must contain parentheses and quotation marks where appropriate. Note that in PL\/SQL and SQL*Plus, two single quotes (not<\/span>\u00a0a double quote) are needed to represent an apostrophe. For example, an example of a\u00a0NAME_EXPR<\/code>\u00a0filter in PL\/SQL is as follows:<\/p>\n 'IN (''DEPT'',''EMP'')'<\/code><\/p>\n The filter value is combined with a particular object attribute to produce a\u00a0WHERE<\/code>\u00a0condition in the query that fetches the objects. In the preceding example, the filter is combined with the attribute corresponding to an object name; objects named ‘DEPT'<\/code>\u00a0and ‘EMP'<\/code>\u00a0are selected.<\/p>\n<\/td>\n<\/tr>\n \nvalue<\/code><\/p>\n<\/td>\n \nThe value of the filter. Text, Boolean, and Numeric filters are supported.<\/p>\n<\/td>\n<\/tr>\n \nobject_type_path<\/code><\/p>\n<\/td>\n \nA path name designating the object types to which the filter applies. By default, the filter applies to the object type of the\u00a0OPEN<\/code>\u00a0handle. When the\u00a0OPEN<\/code>\u00a0handle designates a heterogeneous object type, you can use this parameter to specify a filter for a specific node or set of nodes within the tree of object types that form the heterogeneous collection. See\u00a0Table 57-18<\/a>\u00a0for a listing of some of the values for this parameter.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Table 57-17<\/a>\u00a0describes the object type, name, datatype, and meaning of the filters available with the\u00a0SET_FILTER<\/code>\u00a0procedure.<\/h6>\n<\/a><\/a><\/h6>\nTable 57-17 SET_FILTER: Filters<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nObject Type<\/th>\n Name<\/th>\n Datatype<\/th>\n Meaning<\/th>\n<\/tr>\n<\/thead>\n \nNamed objects<\/p>\n<\/td>\n \nNAME<\/code><\/p>\n<\/td>\n \ntext<\/p>\n<\/td>\n \nObjects with this exact name are selected.<\/p>\n<\/td>\n<\/tr>\n \nNamed objects<\/p>\n<\/td>\n \nNAME_EXPR<\/code><\/p>\n<\/td>\n \ntext expression<\/p>\n<\/td>\n \nThe filter value is combined with the object attribute corresponding to the object name to produce a\u00a0WHERE<\/code>\u00a0condition in the query that fetches the objects.<\/p>\n By default, all named objects of\u00a0object_type<\/code>\u00a0are selected.<\/p>\n<\/td>\n<\/tr>\n \nNamed objects<\/p>\n<\/td>\n \nEXCLUDE_NAME_EXPR<\/code><\/p>\n<\/td>\n \ntext expression<\/p>\n<\/td>\n \nThe filter value is combined with the attribute corresponding to the object name to specify objects that are to be excluded from the set of objects fetched.<\/p>\n By default, all named objects of the object type are selected.<\/p>\n<\/td>\n<\/tr>\n \nSchema objects<\/p>\n<\/td>\n \nSCHEMA<\/code><\/p>\n<\/td>\n \ntext<\/p>\n<\/td>\n \nObjects in this schema are selected. If the object type is SYNONYM, specify PUBLIC to select public synonyms.<\/p>\n<\/td>\n<\/tr>\n \nSchema objects<\/p>\n<\/td>\n \nSCHEMA_EXPR<\/code><\/p>\n<\/td>\n \ntext expression<\/p>\n<\/td>\n \nThe filter value is combined with the attribute corresponding to the object’s schema.<\/p>\n The default is determined as follows:<\/p>\n – if\u00a0BASE_OBJECT_SCHEMA<\/code>\u00a0is specified, then objects in that schema are selected;<\/p>\n – otherwise, objects in the current schema are selected.<\/p>\n<\/td>\n<\/tr>\n \nPACKAGE, TYPE<\/code><\/p>\n<\/td>\n \nSPECIFICATION<\/code><\/p>\n<\/td>\n \nBoolean<\/p>\n<\/td>\n \nIf\u00a0TRUE<\/code>, retrieve the package or type specification. Defaults to TRUE<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nPACKAGE, TYPE<\/code><\/p>\n<\/td>\n \nBODY<\/code><\/p>\n<\/td>\n \nBoolean<\/p>\n<\/td>\n \nIf\u00a0TRUE<\/code>, retrieve the package or type body. Defaults to\u00a0TRUE<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nTABLE, CLUSTER, INDEX, TABLE_DATA, TABLE_EXPORT, TRANSPORTABLE_EXPORT<\/code><\/p>\n<\/td>\n \nTABLESPACE<\/code><\/p>\n<\/td>\n \ntext<\/p>\n<\/td>\n \nObjects in this tablespace (or having a partition in this tablespace) are selected.<\/p>\n<\/td>\n<\/tr>\n \nTABLE, CLUSTER, INDEX,TABLE_DATA, TABLE_EXPORT, TRANSPORTABLE_EXPORT<\/code><\/p>\n<\/td>\n \nTABLESPACE_EXPR<\/code><\/p>\n<\/td>\n \ntext expression<\/p>\n<\/td>\n \nThe filter value is combined with the attribute corresponding to the object’s tablespace (or in the case of a partitioned table or index, the partition’s tablespaces). By default, objects in all tablespaces are selected.<\/p>\n<\/td>\n<\/tr>\n \nTABLE<\/code>, objects dependent on tables<\/p>\n<\/td>\n \nPRIMARY<\/code><\/p>\n<\/td>\n \nBoolean<\/p>\n<\/td>\n \nIf\u00a0TRUE<\/code>, retrieve primary tables (that is, tables for which the secondary object bit in\u00a0obj$<\/code>\u00a0is clear.<\/p>\n Defaults to\u00a0TRUE<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nTABLE<\/code>, objects dependent on tables<\/p>\n<\/td>\n \nSECONDARY<\/code><\/p>\n<\/td>\n \nBoolean<\/p>\n<\/td>\n \nIf\u00a0TRUE<\/code>, retrieve secondary tables (that is, tables for which the secondary object bit in\u00a0obj$<\/code>\u00a0is set).<\/p>\n Defaults to\u00a0TRUE<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nDependent Objects<\/p>\n<\/td>\n \nBASE_OBJECT_NAME<\/code><\/p>\n<\/td>\n \ntext<\/p>\n<\/td>\n \nObjects are selected that are defined or granted on objects with this name. Specify\u00a0SCHEMA<\/code>\u00a0for triggers on schemas. Specify\u00a0DATABASE<\/code>\u00a0for database triggers. Column-level comments cannot be selected by column name; the base object name must be the name of the table, view, or materialized view containing the column.<\/p>\n<\/td>\n<\/tr>\n \nDependent Objects<\/p>\n<\/td>\n \nBASE_OBJECT_SCHEMA<\/code><\/p>\n<\/td>\n \ntext<\/p>\n<\/td>\n \nObjects are selected that are defined or granted on objects in this schema. If\u00a0BASE_OBJECT_NAME<\/code>\u00a0is specified with a value other than\u00a0SCHEMA<\/code>\u00a0or\u00a0DATABASE<\/code>, this defaults to the current schema.<\/p>\n<\/td>\n<\/tr>\n \nDependent Objects<\/p>\n<\/td>\n \nBASE_OBJECT_NAME_EXPR<\/code><\/p>\n<\/td>\n \ntext expression<\/p>\n<\/td>\n \nThe filter value is combined with the attribute corresponding to the name of the base object.<\/p>\n Not valid for schema and database triggers.<\/p>\n<\/td>\n<\/tr>\n \nDependent Objects<\/p>\n<\/td>\n \nEXCLUDE_BASE_OBJECT_NAME_EXPR<\/code><\/p>\n<\/td>\n \ntext expression<\/p>\n<\/td>\n \nThe filter value is combined with the attribute corresponding to the name of the base object to specify objects that are to be excluded from the set of objects fetched.<\/p>\n Not valid for schema and database triggers.<\/p>\n<\/td>\n<\/tr>\n \nDependent Objects<\/p>\n<\/td>\n \nBASE_OBJECT_SCHEMA_EXPR<\/code><\/p>\n<\/td>\n \ntext expression<\/p>\n<\/td>\n \nThe filter value is combined with the attribute corresponding to the schema of the base object.<\/p>\n<\/td>\n<\/tr>\n \nDependent Objects<\/p>\n<\/td>\n \nBASE_OBJECT_TYPE<\/code><\/p>\n<\/td>\n \ntext<\/p>\n<\/td>\n \nThe object type of the base object.<\/p>\n<\/td>\n<\/tr>\n \nDependent Objects<\/p>\n<\/td>\n \nBASE_OBJECT_TYPE_EXPR<\/code><\/p>\n<\/td>\n \ntext expression<\/p>\n<\/td>\n \nThe filter value is combined with the attribute corresponding to the object type of the base object.<\/p>\n By default no filtering is done on object type.<\/p>\n<\/td>\n<\/tr>\n \nDependent Objects<\/p>\n<\/td>\n \nBASE_OBJECT_TABLESPACE<\/code><\/p>\n<\/td>\n \ntext<\/p>\n<\/td>\n \nThe tablespace of the base object.<\/p>\n<\/td>\n<\/tr>\n \nDependent Objects<\/p>\n<\/td>\n \nBASE_OBJECT_TABLESPACE_EXPR<\/code><\/p>\n<\/td>\n \ntext expression<\/p>\n<\/td>\n \nThe filter value is combined with the attribute corresponding to the tablespaces of the base object. By default, no filtering is done on the tablespace.<\/p>\n<\/td>\n<\/tr>\n \nINDEX, TRIGGER<\/code><\/p>\n<\/td>\n \nSYSTEM_GENERATED<\/code><\/p>\n<\/td>\n \nBoolean<\/p>\n<\/td>\n \nIf\u00a0TRUE<\/code>, select indexes or triggers even if they are system-generated. If\u00a0FALSE<\/code>, omit system-generated indexes or triggers. Defaults to\u00a0TRUE<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nGranted Objects<\/p>\n<\/td>\n \nGRANTEE<\/code><\/p>\n<\/td>\n \ntext<\/p>\n<\/td>\n \nObjects are selected that are granted to this user or role. Specify\u00a0PUBLIC<\/code>\u00a0for grants to\u00a0PUBLIC<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nGranted Objects<\/p>\n<\/td>\n \nPRIVNAME<\/code><\/p>\n<\/td>\n \ntext<\/p>\n<\/td>\n \nThe name of the privilege or role to be granted. For TABLESPACE_QUOTA, only UNLIMITED can be specified.<\/p>\n<\/td>\n<\/tr>\n \nGranted Objects<\/p>\n<\/td>\n \nPRIVNAME_EXPR<\/code><\/p>\n<\/td>\n \ntext expression<\/p>\n<\/td>\n \nThe filter value is combined with the attribute corresponding to the privilege or role name. By default, all privileges\/roles are returned.<\/p>\n<\/td>\n<\/tr>\n \nGranted Objects<\/p>\n<\/td>\n \nGRANTEE_EXPR<\/code><\/p>\n<\/td>\n \ntext expression<\/p>\n<\/td>\n \nThe filter value is combined with the attribute corresponding to the grantee name.<\/p>\n<\/td>\n<\/tr>\n \nGranted Objects<\/p>\n<\/td>\n \nEXCLUDE_GRANTEE_EXPR<\/code><\/p>\n<\/td>\n \ntext expression<\/p>\n<\/td>\n \nThe filter value is combined with the attribute corresponding to the grantee name to specify objects that are to be excluded from the set of objects fetched.<\/p>\n<\/td>\n<\/tr>\n \nOBJECT_GRANT<\/code><\/p>\n<\/td>\n \nGRANTOR<\/code><\/p>\n<\/td>\n \ntext<\/p>\n<\/td>\n \nObject grants are selected that are granted by this user.<\/p>\n<\/td>\n<\/tr>\n \nSYNONYM, JAVA_SOURCE, XMLSCHEMA<\/code><\/p>\n<\/td>\n \nLONGNAME<\/code><\/p>\n<\/td>\n \ntext<\/p>\n<\/td>\n \nA name longer than 30 characters. Objects with this exact name are selected. If the object name is 30 characters or less, the\u00a0NAME<\/code>\u00a0filter must be used.<\/p>\n<\/td>\n<\/tr>\n \nSYNONYM, JAVA_SOURCE, XMLSCHEMA<\/code><\/p>\n<\/td>\n \nLONGNAME_EXPR<\/code><\/p>\n<\/td>\n \ntext<\/p>\n<\/td>\n \nThe filter value is combined with the attribute corresponding to the object’s long name. By default, no filtering is done on the long name of an object.<\/p>\n<\/td>\n<\/tr>\n \nAll objects<\/p>\n<\/td>\n \nCUSTOM_FILTER<\/code><\/p>\n<\/td>\n \ntext<\/code><\/p>\n<\/td>\n \nThe text of a\u00a0WHERE<\/code>\u00a0condition. The condition is appended to the query that fetches the objects. By default, no custom filter is used.<\/p>\n The other filters are intended to meet the needs of the majority of users. Use\u00a0CUSTOM_FILTER<\/code>\u00a0when no defined filters exists for your purpose. Of necessity such a filter depends on the detailed structure of the UDTs and views used in the query. Because filters may change from version to version, upward compatibility is not guaranteed.<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nSCHEMA<\/code><\/p>\n<\/td>\n \ntext<\/code><\/p>\n<\/td>\n \nThe schema whose objects are selected.<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nSCHEMA_EXPR<\/code><\/p>\n<\/td>\n \ntext expression<\/code><\/p>\n<\/td>\n \nThe filter value is either:<\/p>\n combined with the attribute corresponding to a schema name to produce a\u00a0WHERE<\/code>\u00a0condition in the query that fetches schema objects,<\/p>\n combined with the attribute corresponding to a base schema name to produce a\u00a0WHERE<\/code>\u00a0condition in the query that fetches dependent objects.<\/p>\n By default the current user’s objects are selected.<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nINCLUDE_USER<\/code><\/p>\n<\/td>\n \nBoolean<\/code><\/p>\n<\/td>\n \nIf\u00a0TRUE<\/code>, retrieve objects containing privileged information about the user. For example,\u00a0USER<\/code>,\u00a0PASSWORD_HISTORY<\/code>,\u00a0TABLESPACE_QUOTA<\/code>.<\/p>\n Defaults to\u00a0FALSE<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nTABLE_EXPORT<\/code><\/p>\n<\/td>\n \nSCHEMA<\/code><\/p>\n<\/td>\n \ntext<\/code><\/p>\n<\/td>\n \nObjects (tables and their dependent objects) in this schema are selected.<\/p>\n<\/td>\n<\/tr>\n \nTABLE_EXPORT<\/code><\/p>\n<\/td>\n \nSCHEMA_EXPR<\/code><\/p>\n<\/td>\n \ntext expression<\/code><\/p>\n<\/td>\n \nThe filter value is either:<\/p>\n combined with the attribute corresponding to a schema name to produce a\u00a0WHERE<\/code>\u00a0condition in the query that fetches the tables,<\/p>\n combined with the attribute corresponding to a base schema name to produce a\u00a0WHERE<\/code>\u00a0condition in the query that fetches the tables’ dependent objects.<\/p>\n By default the current user’s objects are selected.<\/p>\n<\/td>\n<\/tr>\n \nTABLE_EXPORT<\/code><\/p>\n<\/td>\n \nNAME<\/code><\/p>\n<\/td>\n \ntext<\/code><\/p>\n<\/td>\n \nThe table with this exact name is selected along with its dependent objects.<\/p>\n<\/td>\n<\/tr>\n \nTABLE_EXPORT<\/code><\/p>\n<\/td>\n \nNAME_EXPR<\/code><\/p>\n<\/td>\n \ntext expression<\/p>\n<\/td>\n \nThe filter value is combined with the attribute corresponding to a table name in the queries that fetch tables and their dependent objects.<\/p>\n By default all tables in the selected schemas are selected, along with their dependent objects.<\/p>\n<\/td>\n<\/tr>\n \nHeterogeneous objects<\/p>\n<\/td>\n \nBEGIN_WITH<\/code><\/p>\n<\/td>\n \ntext<\/p>\n<\/td>\n \nThe fully qualified path name of the first object type in the heterogeneous collection to be retrieved. Objects normally fetched prior to this object type will not be retrieved.<\/p>\n<\/td>\n<\/tr>\n \nHeterogeneous objects<\/p>\n<\/td>\n \nBEGIN_AFTER<\/code><\/p>\n<\/td>\n \ntext<\/p>\n<\/td>\n \nThe fully qualified path name of an object type after which the heterogeneous retrieval should begin. Objects of this type will not be retrieved, nor will objects normally fetched prior to this object type.<\/p>\n<\/td>\n<\/tr>\n \nHeterogeneous objects<\/p>\n<\/td>\n \nEND_BEFORE<\/code><\/p>\n<\/td>\n \ntext<\/p>\n<\/td>\n \nThe fully qualified path name of an object type where the heterogeneous retrieval should end. Objects of this type will not be retrieved, nor will objects normally fetched after this object type.<\/p>\n<\/td>\n<\/tr>\n \nHeterogeneous objects<\/p>\n<\/td>\n \nEND_WITH<\/code><\/p>\n<\/td>\n \ntext<\/p>\n<\/td>\n \nThe fully qualified path name of the last object type in the heterogeneous collection to be retrieved. Objects normally fetched after this object type will not be retrieved.<\/p>\n<\/td>\n<\/tr>\n \nHeterogeneous objects<\/p>\n<\/td>\n \nINCLUDE_PATH_EXPR, EXCLUDE_PATH_EXPR<\/code><\/p>\n<\/td>\n \ntext expression<\/p>\n<\/td>\n \nFor these two filters, the filter value is combined with the attribute corresponding to an object type path name to produce a\u00a0WHERE<\/code>\u00a0condition in the query that fetches the object types belonging to the heterogeneous collection. Objects of types satisfying this condition are included (INCLUDE_PATH_EXPR<\/code>) or excluded (EXCLUDE_PATH_EXPR<\/code>) from the set of object types fetched. Path names in the filter value do not have to be fully qualified. See\u00a0Table 57-18<\/a>\u00a0for valid path names that can be used with these filters.<\/p>\n BEGIN_WITH<\/code>,\u00a0BEGIN_AFTER<\/code>,\u00a0END_BEFORE<\/code>,\u00a0END_WITH<\/code>,\u00a0INCLUDE_PATH_EXPR<\/code>, and\u00a0EXCLUDE_PATH_EXPR<\/code>\u00a0all restrict the set of object types in the heterogeneous collection. By default, objects of all object types in the heterogeneous collection are retrieved.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n <\/a><\/h6>\nUsage Notes<\/h6>\n\n\nEach call to\u00a0SET_FILTER<\/code>\u00a0causes a\u00a0WHERE<\/code>\u00a0condition to be added to the underlying query that fetches the set of objects. The\u00a0WHERE<\/code>\u00a0conditions are ANDed together, so you can use multiple\u00a0SET_FILTER<\/code>\u00a0calls to refine the set of objects to be returned. For example to specify that you want the object named\u00a0EMP<\/code>\u00a0in schema\u00a0SCOTT<\/code>, do the following:<\/h6>\nSET_FILTER(handle,’SCHEMA’,’SCOTT’); SET_FILTER(handle,’NAME’,’EMP’);<\/h6>\n<\/li>\n\nYou can use the same text expression filter multiple times with different values. All the filter conditions will be applied to the query. For example, to get objects with names between Felix and Oscar, do the following:<\/h6>\nSET_FILTER(handle,’NAME_EXPR’,’>=”FELIX”’); SET_FILTER(handle,’NAME_EXPR’,'<=”OSCAR”’);<\/h6>\n<\/li>\n\nWith SET_FILTER,<\/code>\u00a0you can specify the schema of objects to be retrieved, but security considerations may override this specification. If the caller is\u00a0SYS<\/code>\u00a0or has\u00a0SELECT_CATALOG_ROLE<\/code>, then any object can be retrieved; otherwise, only the following can be retrieved:<\/h6>\n\n\nSchema objects owned by the current user<\/h6>\n<\/li>\n\nPublic synonyms<\/h6>\n<\/li>\n\nSystem privileges granted to the current user or to\u00a0PUBLIC<\/code><\/h6>\n<\/li>\n\nGrants on objects for which the current user is owner, grantor, or grantee (either explicitly or as\u00a0PUBLIC<\/code>).<\/h6>\n<\/li>\n\nSCHEMA_EXPORT<\/code>\u00a0where the\u00a0name<\/code>\u00a0is the current user<\/h6>\n<\/li>\n\nTABLE_EXPORT<\/code>\u00a0where\u00a0SCHEMA<\/code>\u00a0is the current user<\/h6>\n<\/li>\n<\/ul>\nIf you request objects that you are not privileged to retrieve, no exception is raised; the object is not retrieved, as if it did not exist.<\/h6>\n In stored procedures, functions, and definers-rights packages, roles (such as\u00a0SELECT_CATALOG_ROLE<\/code>) are disabled. Therefore, such a PL\/SQL program can only fetch metadata for objects in its own schema. If you want to write a PL\/SQL program that fetches metadata for objects in a different schema (based on the invoker’s possession of\u00a0SELECT_CATALOG_ROLE<\/code>), you must make the program invokers-rights.<\/h6>\n<\/li>\n\nFor heterogeneous object types, the\u00a0BEGIN_WITH<\/code>\u00a0and\u00a0BEGIN_AFTER<\/code>\u00a0filters allow restart on an object type boundary. Appropriate filter values are returned by the\u00a0FETCH_XML_CLOB<\/code>\u00a0procedure.<\/h6>\nFilters on heterogeneous objects provide default values for filters on object types within the collection. You can override this default for a particular object type by specifying the appropriate filter for the specific object type path. For example, for\u00a0SCHEMA_EXPORT<\/code>\u00a0the\u00a0NAME<\/code>\u00a0filter specifies the schema to be fetched including all the tables in the schema, but you can further restrict this set of tables by supplying a\u00a0NAME_EXPR<\/code>\u00a0filter explicitly for the TABLE object type path.\u00a0Table 57-18<\/a>\u00a0lists valid object type path names for the major heterogeneous object types along with an explanation of the scope of each path name. (The same information is available in the following catalog views:\u00a0DATABASE_EXPORT_OBJECTS<\/code>,\u00a0SCHEMA_EXPORT_OBJECTS<\/code>, and\u00a0TABLE_EXPORT_OBJECTS<\/code>.) See\u00a0Table 57-17<\/a>\u00a0for filters defined for each path name. These path names are valid in the\u00a0INCLUDE_PATH_EXPR<\/code>\u00a0and\u00a0EXCLUDE_PATH_EXPR<\/code>\u00a0filters. Path names marked with an asterisk (*) are\u00a0only<\/span>\u00a0valid in those filters; they cannot be used as values of the\u00a0SET_FILTER<\/code>\u00a0object_type_path<\/code>\u00a0parameter.<\/h6>\n<\/li>\n<\/ul>\n<\/a><\/a><\/h6>\nTable 57-18 Object Type Path Names for Heterogeneous Object Types<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nHeterogeneous Type<\/th>\n Path Name (*=valid only in xxx_PATH_EXPR)<\/th>\n Scope<\/th>\n<\/tr>\n<\/thead>\n \nTABLE_EXPORT<\/code><\/p>\n<\/td>\n \nAUDIT_OBJ<\/code><\/p>\n<\/td>\n \nObject audits on the selected tables<\/p>\n<\/td>\n<\/tr>\n \nTABLE_EXPORT<\/code><\/p>\n<\/td>\n \nCOMMENT<\/code><\/p>\n<\/td>\n \nTable and column comments for the selected tables<\/p>\n<\/td>\n<\/tr>\n \nTABLE_EXPORT<\/code><\/p>\n<\/td>\n \nCONSTRAINT<\/code><\/p>\n<\/td>\n \nConstraints (including referential constraints) on the selected tables<\/p>\n<\/td>\n<\/tr>\n \nTABLE_EXPORT<\/code><\/p>\n<\/td>\n \n*GRANT<\/code><\/p>\n<\/td>\n \nObject grants on the selected tables<\/p>\n<\/td>\n<\/tr>\n \nTABLE_EXPORT<\/code><\/p>\n<\/td>\n \nINDEX<\/code><\/p>\n<\/td>\n \nIndexes (including domain indexes) on the selected tables<\/p>\n<\/td>\n<\/tr>\n \nTABLE_EXPORT<\/code><\/p>\n<\/td>\n \nOBJECT_GRANT<\/code><\/p>\n<\/td>\n \nObject grants on the selected tables<\/p>\n<\/td>\n<\/tr>\n \nTABLE_EXPORT<\/code><\/p>\n<\/td>\n \nREF_CONSTRAINT<\/code><\/p>\n<\/td>\n \nReferential (foreign key) constraints on the selected tables<\/p>\n<\/td>\n<\/tr>\n \nTABLE_EXPORT<\/code><\/p>\n<\/td>\n \nSTATISTICS<\/code><\/p>\n<\/td>\n \nStatistics on the selected tables<\/p>\n<\/td>\n<\/tr>\n \nTABLE_EXPORT<\/code><\/p>\n<\/td>\n \nTABLE_DATA<\/code><\/p>\n<\/td>\n \nRow data for the selected tables<\/p>\n<\/td>\n<\/tr>\n \nTABLE_EXPORT<\/code><\/p>\n<\/td>\n \nTRIGGER<\/code><\/p>\n<\/td>\n \nTriggers on the selected tables<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nASSOCIATION<\/code><\/p>\n<\/td>\n \nStatistics type associations for objects in the selected schemas<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nAUDIT_OBJ<\/code><\/p>\n<\/td>\n \nAudits on all objects in the selected schemas<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nCLUSTER<\/code><\/p>\n<\/td>\n \nClusters in the selected schemas and their indexes<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nCOMMENT<\/code><\/p>\n<\/td>\n \nComments on all objects in the selected schemas<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nCONSTRAINT<\/code><\/p>\n<\/td>\n \nConstraints (including referential constraints) on all objects in the selected schemas<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nDB_LINK<\/code><\/p>\n<\/td>\n \nPrivate database links in the selected schemas<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nDEFAULT_ROLE<\/code><\/p>\n<\/td>\n \nDefault roles granted to users associated with the selected schemas<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nDIMENSION<\/code><\/p>\n<\/td>\n \nDimensions in the selected schemas<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nFUNCTION<\/code><\/p>\n<\/td>\n \nFunctions in the selected schemas and their dependent grants and audits<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \n*GRANT<\/code><\/p>\n<\/td>\n \nGrants on objects in the selected schemas<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nINDEX<\/code><\/p>\n<\/td>\n \nIndexes (including domain indexes) on tables and clusters in the selected schemas<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nINDEXTYPE<\/code><\/p>\n<\/td>\n \nIndextypes in the selected schemas and their dependent grants and audits<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nJAVA_SOURCE<\/code><\/p>\n<\/td>\n \nJava sources in the selected schemas and their dependent grants and audits<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nJOB<\/code><\/p>\n<\/td>\n \nJobs in the selected schemas<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nLIBRARY<\/code><\/p>\n<\/td>\n \nExternal procedure libraries in the selected schemas<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nMATERIALIZED_VIEW<\/code><\/p>\n<\/td>\n \nMaterialized views in the selected schemas<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nMATERIALIZED_VIEW_LOG<\/code><\/p>\n<\/td>\n \nMaterialized view logs on tables in the selected schemas<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nOBJECT_GRANT<\/code><\/p>\n<\/td>\n \nGrants on objects in the selected schemas<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nOPERATOR<\/code><\/p>\n<\/td>\n \nOperators in the selected schemas and their dependent grants and audits<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nPACKAGE<\/code><\/p>\n<\/td>\n \nPackages (both specification and body) in the selected schemas, and their dependent grants and audits<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nPACKAGE_BODY<\/code><\/p>\n<\/td>\n \nPackage bodies in the selected schemas<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nPACKAGE_SPEC<\/code><\/p>\n<\/td>\n \nPackage specifications in the selected schemas<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nPASSWORD_HISTORY<\/code><\/p>\n<\/td>\n \nThe password history for users associated with the selected schemas<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nPROCEDURE<\/code><\/p>\n<\/td>\n \nProcedures in the selected schemas and their dependent grants and audits<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nREF_CONSTRAINT<\/code><\/p>\n<\/td>\n \nReferential (foreign key) constraints on tables in the selected schemas<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nREFRESH_GROUP<\/code><\/p>\n<\/td>\n \nRefresh groups in the selected schemas<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nSEQUENCE<\/code><\/p>\n<\/td>\n \nSequences in the selected schemas and their dependent grants and audits<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nSTATISTICS<\/code><\/p>\n<\/td>\n \nStatistics on tables and indexes in the selected schemas<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nSYNONYM<\/code><\/p>\n<\/td>\n \nPrivate synonyms in the selected schemas<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nTABLE<\/code><\/p>\n<\/td>\n \nTables in the selected schemas and their dependent objects (indexes, constraints, triggers, grants, audits, comments, table data, and so on)<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nTABLE_DATA<\/code><\/p>\n<\/td>\n \nRow data for tables in the selected schemas<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nTABLESPACE_QUOTA<\/code><\/p>\n<\/td>\n \nTablespace quota granted to users associated with the selected schemas<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nTRIGGER<\/code><\/p>\n<\/td>\n \nTriggers on tables in the selected schemas<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nTYPE<\/code><\/p>\n<\/td>\n \nTypes (both specification and body) in the selected schemas, and their dependent grants and audits<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nTYPE_BODY<\/code><\/p>\n<\/td>\n \nType bodies in the selected schemas<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nTYPE_SPEC<\/code><\/p>\n<\/td>\n \nType specifications in the selected schemas<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nUSER<\/code><\/p>\n<\/td>\n \nUser definitions for users associated with the selected schemas<\/p>\n<\/td>\n<\/tr>\n \nSCHEMA_EXPORT<\/code><\/p>\n<\/td>\n \nVIEW<\/code><\/p>\n<\/td>\n \nViews in the selected schemas and their dependent objects (grants, constraints, comments, audits)<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nASSOCIATION<\/code><\/p>\n<\/td>\n \nStatistics type associations for objects in the database<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nAUDIT<\/code><\/p>\n<\/td>\n \nAudits of SQL statements<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nAUDIT_OBJ<\/code><\/p>\n<\/td>\n \nAudits on all objects in the database<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nCLUSTER<\/code><\/p>\n<\/td>\n \nClusters and their indexes<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nCOMMENT<\/code><\/p>\n<\/td>\n \nComments on all objects<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nCONSTRAINT<\/code><\/p>\n<\/td>\n \nConstraints (including referential constraints)<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nCONTEXT<\/code><\/p>\n<\/td>\n \nApplication contexts<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nDB_LINK<\/code><\/p>\n<\/td>\n \nPrivate and public database links<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nDEFAULT_ROLE<\/code><\/p>\n<\/td>\n \nDefault roles granted to users in the database<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nDIMENSION<\/code><\/p>\n<\/td>\n \nDimensions in the database<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nDIRECTORY<\/code><\/p>\n<\/td>\n \nDirectory objects in the database<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nFGA_POLICY<\/code><\/p>\n<\/td>\n \nFine-grained audit policies<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nFUNCTION<\/code><\/p>\n<\/td>\n \nFunctions<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \n* GRANT<\/code><\/p>\n<\/td>\n \nObject and system grants<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nINDEX<\/code><\/p>\n<\/td>\n \nIndexes (including domain indexes) on tables and clusters<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nINDEXTYPE<\/code><\/p>\n<\/td>\n \nIndextypes and their dependent grants and audits<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nJAVA_SOURCE<\/code><\/p>\n<\/td>\n \nJava sources and their dependent grants and audits<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nJOB<\/code><\/p>\n<\/td>\n \nJobs<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nLIBRARY<\/code><\/p>\n<\/td>\n \nExternal procedure libraries<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nMATERIALIZED_VIEW<\/code><\/p>\n<\/td>\n \nMaterialized views<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nMATERIALIZED_VIEW_LOG<\/code><\/p>\n<\/td>\n \nMaterialized view logs<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nOBJECT_GRANT<\/code><\/p>\n<\/td>\n \nAll object grants in the database<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nOPERATOR<\/code><\/p>\n<\/td>\n \nOperators and their dependent grants and audits<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nPACKAGE<\/code><\/p>\n<\/td>\n \nPackages (both specification and body) and their dependent grants and audits<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nPACKAGE_BODY<\/code><\/p>\n<\/td>\n \nPackage bodies<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nPACKAGE_SPEC<\/code><\/p>\n<\/td>\n \nPackage specifications<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nPASSWORD_HISTORY<\/code><\/p>\n<\/td>\n \nPassword histories for database users<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \n*PASSWORD_VERIFY_FUNCTION<\/code><\/p>\n<\/td>\n \nThe password complexity verification function<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nPROCEDURE<\/code><\/p>\n<\/td>\n \nProcedures and their dependent grants and objects<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nPROFILE<\/code><\/p>\n<\/td>\n \nProfiles<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nPROXY<\/code><\/p>\n<\/td>\n \nProxy authentications<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nREF_CONSTRAINT<\/code><\/p>\n<\/td>\n \nReferential (foreign key) constraints on tables in the database<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nREFRESH_GROUP<\/code><\/p>\n<\/td>\n \nRefresh groups<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \n*RESOURCE_ COST<\/code><\/p>\n<\/td>\n \nResource cost information<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nRLS_CONTEXT<\/code><\/p>\n<\/td>\n \nFine-grained access-control driving contexts<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nRLS_GROUP<\/code><\/p>\n<\/td>\n \nFine-grained access-control policy groups<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nRLS_POLICY<\/code><\/p>\n<\/td>\n \nFine-grained access-control policies<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nROLE<\/code><\/p>\n<\/td>\n \nRoles<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nROLE_GRANT<\/code><\/p>\n<\/td>\n \nRole grants to users in the database<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nROLLBACK_SEGMENT<\/code><\/p>\n<\/td>\n \nRollback segments<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \n*SCHEMA (named object)<\/code><\/p>\n<\/td>\n \nDatabase schemas including for each schema all related and dependent objects: user definitions and their attributes (default roles, role grants, tablespace quotas, and so on), objects in the schema (tables, view, packages, types, and so on), and their dependent objects (grants, audits, indexes, constraints, and so on). The\u00a0NAME<\/code>\u00a0and\u00a0NAME_EXPR<\/code>\u00a0filters can be used with this object type path name to designate the database schemas to be fetched.<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nSEQUENCE<\/code><\/p>\n<\/td>\n \nSequences<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nSTATISTICS<\/code><\/p>\n<\/td>\n \nStatistics on tables and indexes<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nSYNONYM<\/code><\/p>\n<\/td>\n \nPublic and private synonyms<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nSYSTEM_GRANT<\/code><\/p>\n<\/td>\n \nSystem privilege grants<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nTABLE<\/code><\/p>\n<\/td>\n \nTables and their dependent objects (indexes, constraints, triggers, grants, audits, comments, table data, and so on)<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nTABLE_DATA<\/code><\/p>\n<\/td>\n \nRow data for all tables<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nTABLESPACE<\/code><\/p>\n<\/td>\n \nTablespace definitions<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nTABLESPACE_QUOTA<\/code><\/p>\n<\/td>\n \nTablespace quota granted to users in the database<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nTRIGGER<\/code><\/p>\n<\/td>\n \nTriggers on the database, on schemas, and on schema objects<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nTRUSTED_DB_LINK<\/code><\/p>\n<\/td>\n \nTrusted links<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nTYPE<\/code><\/p>\n<\/td>\n \nTypes (both specification and body) and their dependent grants and audits<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nTYPE_BODY<\/code><\/p>\n<\/td>\n \nType bodies<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nTYPE_SPEC<\/code><\/p>\n<\/td>\n \nType specifications<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nUSER<\/code><\/p>\n<\/td>\n \nUser definitions<\/p>\n<\/td>\n<\/tr>\n \nDATABASE_EXPORT<\/code><\/p>\n<\/td>\n \nVIEW<\/code><\/p>\n<\/td>\n \nViews<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n <\/a><\/h6>\nExceptions<\/h6>\n\n\nINVALID_ARGVAL<\/code>. A\u00a0NULL<\/code>\u00a0or invalid value was supplied for an input parameter. The error message text identifies the parameter.<\/h6>\n<\/li>\n\nINVALID_OPERATION<\/code>.\u00a0SET_FILTER<\/code>\u00a0was called after the first call to\u00a0FETCH_xxx<\/code>\u00a0for the\u00a0OPEN<\/code>\u00a0context. After the first call to\u00a0FETCH_xxx<\/code>\u00a0is made, no further calls to\u00a0SET_FILTER<\/code>\u00a0are permitted.<\/h6>\n<\/li>\n\nINCONSISTENT_ARGS<\/code>. The arguments are inconsistent. Possible inconsistencies include the following:<\/h6>\n\n\nfilter name not valid for the object type associated with the\u00a0OPEN<\/code>\u00a0context<\/h6>\n<\/li>\n\nfilter\u00a0name<\/code>\u00a0not valid for the\u00a0object_type_path<\/code><\/h6>\n<\/li>\n\nobject_type_path<\/code>\u00a0not part of the collection designated by\u00a0handle<\/code><\/h6>\n<\/li>\n\nfilter\u00a0value<\/code>\u00a0is the wrong datatype<\/h6>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/a><\/h6>\n \nSET_PARSE_ITEM Procedure<\/a><\/h6>\nThis procedure is used for both retrieval and submission. This procedure enables output parsing and specifies an object attribute to be parsed and returned.<\/h6>\n\n\n\n\n\nSee Also:<\/p>\n For more information about related subprograms:<\/p>\n \n\nSubprograms for Retrieving Multiple Objects From the Database<\/a><\/p>\n<\/li>\n \nSubprograms for Submitting XML to the Database<\/a><\/p>\n<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n <\/a><\/h6>\nSyntax<\/h6>\nThe following syntax applies when\u00a0SET_PARSE_ITEM<\/code>\u00a0is used for object retrieval:<\/h6>\nDBMS_METADATA.SET_PARSE_ITEM ( handle IN NUMBER, name IN VARCHAR2, object_type IN VARCHAR2 DEFAULT NULL);<\/h6>\nThe following syntax applies when\u00a0SET_PARSE_ITEM<\/code>\u00a0is used for XML submission:<\/h6>\nDBMS_METADATA.SET_PARSE_ITEM ( handle IN NUMBER, name IN VARCHAR2);<\/h6>\n<\/a><\/h6>\nParameters<\/h6>\n<\/a><\/a><\/h6>\nTable 57-19 SET_PARSE_ITEM Procedure Parameters<\/p>\n\n\n\n\n\n\n\nParameter<\/th>\n Description<\/th>\n<\/tr>\n<\/thead>\n \nhandle<\/code><\/p>\n<\/td>\n \nThe handle returned from\u00a0OPEN<\/code>\u00a0(or\u00a0OPENW<\/code>).<\/p>\n<\/td>\n<\/tr>\n \nname<\/code><\/p>\n<\/td>\n \nThe name of the object attribute to be parsed and returned. See\u00a0Table 57-20<\/a>\u00a0for the attribute object type, name, and meaning.<\/p>\n<\/td>\n<\/tr>\n \nobject_type<\/code><\/p>\n<\/td>\n \nDesignates the object type to which the parse item applies (this is an object type name, not a path name). By default, the parse item applies to the object type of the OPEN handle. When the\u00a0OPEN<\/code>\u00a0handle designates a heterogeneous object type, behavior can be either of the following:<\/p>\n \n\nif object_type is omitted, the parse item applies to all object types within the heterogeneous collection<\/p>\n<\/li>\n \nif object_type is specified, the parse item only applies to that specific object type within the collection<\/p>\n<\/li>\n<\/ul>\n This parameter only applies when\u00a0SET_PARSE_ITEM<\/code>\u00a0is used for object retrieval.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Table 57-20<\/a>\u00a0describes the object type, name, and meaning of the items available in the\u00a0SET_PARSE_ITEM<\/code>\u00a0procedure.<\/h6>\n<\/a><\/a><\/h6>\nTable 57-20 SET_PARSE_ITEM: Parse Items<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nObject Type<\/th>\n Name<\/th>\n Meaning<\/th>\n<\/tr>\n<\/thead>\n \nAll objects<\/p>\n<\/td>\n \nVERB<\/code><\/p>\n<\/td>\n \nIf\u00a0FETCH_XML_CLOB<\/code>\u00a0is called, no value is returned.<\/p>\n If\u00a0FETCH_DDL<\/code>\u00a0is called, then for every row in the\u00a0sys.ku$_ddls<\/code>\u00a0nested table returned by\u00a0FETCH_DDL<\/code>\u00a0the verb in the corresponding\u00a0ddlText<\/code>\u00a0is returned. If the\u00a0ddlText<\/code>\u00a0is a SQL DDL statement, then the SQL verb (for example,\u00a0CREATE<\/code>,\u00a0GRANT<\/code>,\u00a0AUDIT<\/code>) is returned. If the\u00a0ddlText<\/code>\u00a0is a procedure call (for example,\u00a0DBMS_AQADM<\/code>.CREATE_QUEUE_TABLE())<\/code>\u00a0then the package.procedure-name is returned.<\/p>\n<\/td>\n<\/tr>\n \nAll objects<\/p>\n<\/td>\n \nOBJECT_TYPE<\/code><\/p>\n<\/td>\n \nIf\u00a0FETCH_XML_CLOB<\/code>\u00a0is called, an object type name from\u00a0Table 57-11<\/a>\u00a0is returned.<\/p>\n If\u00a0FETCH_DDL<\/code>\u00a0is called and the\u00a0ddlText<\/code>\u00a0is a SQL DDL statement whose verb is\u00a0CREATE<\/code>\u00a0or\u00a0ALTER<\/code>, the object type as used in the DDL statement is returned (for example,\u00a0TABLE<\/code>,\u00a0PACKAGE<\/code>_BODY<\/code>, and so on). Otherwise, an object type name from\u00a0Table 57-11<\/a>\u00a0is returned.<\/p>\n<\/td>\n<\/tr>\n \nSchema objects<\/p>\n<\/td>\n \nSCHEMA<\/code><\/p>\n<\/td>\n \nThe object schema is returned. If the object is not a schema object, no value is returned.<\/p>\n<\/td>\n<\/tr>\n \nNamed objects<\/p>\n<\/td>\n \nNAME<\/code><\/p>\n<\/td>\n \nThe object name is returned. If the object is not a named object, no value is returned.<\/p>\n<\/td>\n<\/tr>\n \nTABLE, TABLE_DATA, INDEX<\/code><\/p>\n<\/td>\n \nTABLESPACE<\/code><\/p>\n<\/td>\n \nThe name of the object’s tablespace or, if the object is a partitioned table, the default tablespace is returned. For a TABLE_DATA object, this is always the tablespace where the rows are stored.<\/p>\n<\/td>\n<\/tr>\n \nTRIGGER<\/code><\/p>\n<\/td>\n \nENABLE<\/code><\/p>\n<\/td>\n \nIf the trigger is enabled,\u00a0ENABLE<\/code>\u00a0is returned. If the trigger is disabled,\u00a0DISABLE<\/code>\u00a0is returned.<\/p>\n<\/td>\n<\/tr>\n \nOBJECT_GRANT, TABLESPACE_QUOTA<\/code><\/p>\n<\/td>\n \nGRANTOR<\/code><\/p>\n<\/td>\n \nThe grantor is returned.<\/p>\n<\/td>\n<\/tr>\n \nDependent objects (including domain index secondary tables)<\/p>\n<\/td>\n \nBASE_OBJECT_NAME<\/code><\/p>\n<\/td>\n \nThe name of the base object is returned. If the object is not a dependent object, no value is returned.<\/p>\n<\/td>\n<\/tr>\n \nDependent objects (including domain index secondary tables)<\/p>\n<\/td>\n \nBASE_OBJECT_SCHEMA<\/code><\/p>\n<\/td>\n \nThe schema of the base object is returned. If the object is not a dependent object, no value is returned.<\/p>\n<\/td>\n<\/tr>\n \nDependent objects (including domain index secondary tables)<\/p>\n<\/td>\n \nBASE_OBJECT_TYPE<\/code><\/p>\n<\/td>\n \nThe object type of the base object is returned. If the object is not a dependent object, no value is returned.<\/p>\n<\/td>\n<\/tr>\n \nGranted objects<\/p>\n<\/td>\n \nGRANTEE<\/code><\/p>\n<\/td>\n \nThe grantee is returned. If the object is not a granted object, no value is returned.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n <\/a><\/h6>\nUsage Notes<\/h6>\n These notes apply when using SET_PARSE_ITEM to retrieve objects.<\/h6>\n By default, the\u00a0FETCH_xxx<\/code>\u00a0routines return an object’s metadata as XML or creation DDL. By calling\u00a0SET_PARSE_ITEM<\/code>\u00a0you can request that individual attributes of the object be returned as well.<\/h6>\nYou can call\u00a0SET_PARSE_ITEM<\/code>\u00a0multiple times to ask for multiple items to be parsed and returned. Parsed items are returned in the\u00a0sys<\/code>.ku$_parsed_items<\/code>\u00a0nested table.<\/h6>\nFor\u00a0TABLE_DATA<\/code>\u00a0objects, the following parse item return values are of interest:<\/h6>\n\n\n\n\n\n\n\nIf Object Is<\/span><\/th>\n NAME, SCHEMA<\/th>\n BASE_OBJECT_NAME, BASE_OBJECT_SCHEMA<\/th>\n<\/tr>\n<\/thead>\n nonpartitioned table<\/td>\n table name, schema<\/td>\n table name, schema<\/td>\n<\/tr>\n table partition<\/td>\n partition name, schema<\/td>\n table name, schema<\/td>\n<\/tr>\n nested table<\/td>\n storage table name, schema<\/td>\n name and schema of top-level table (not<\/span>\u00a0the parent nested table)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nTables are not usually thought of as dependent objects. However, secondary tables for domain indexes are dependent on the domain indexes. Consequently, the\u00a0BASE_OBJECT_NAME<\/code>,\u00a0BASE_OBJECT_SCHEMA<\/code>\u00a0and\u00a0BASE_OBJECT_TYPE<\/code>\u00a0parse items for secondary\u00a0TABLE<\/code>\u00a0objects return the name, schema, and type of the domain index.<\/h6>\n\n\n\n\n\nSee Also:<\/p>\n \n\n“FETCH_xxx Functions and Procedures”<\/a><\/p>\n<\/li>\n \nOracle Database Utilities<\/a><\/span>\u00a0for information about using the Metadata API<\/p>\n<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n By default, the\u00a0CONVERT<\/code>\u00a0and\u00a0PUT<\/code>\u00a0procedures simply transform an object’s XML metadata to DDL. By calling\u00a0SET_PARSE_ITEM<\/code>\u00a0you can request that individual attributes of the object be returned as well.<\/h6>\n<\/a><\/h6>\nExceptions<\/h6>\n\n\nINVALID_ARGVAL<\/code>. A\u00a0NULL<\/code>\u00a0or invalid value was supplied for an input parameter. The error message text identifies the parameter.<\/h6>\n<\/li>\n\nINVALID_OPERATION<\/code>.\u00a0SET_PARSE_ITEM<\/code>\u00a0was called after the first call to\u00a0FETCH_xxx<\/code>\u00a0for the\u00a0OPEN<\/code>\u00a0context. After the first call to\u00a0FETCH_xxx<\/code>\u00a0is made, no further calls to\u00a0SET_PARSE_ITEM<\/code>\u00a0are permitted.<\/h6>\n<\/li>\n\nINCONSISTENT_ARGS<\/code>. The attribute\u00a0name<\/code>\u00a0is not valid for the object type associated with the\u00a0OPEN<\/code>\u00a0context.<\/h6>\n<\/li>\n<\/ul>\n<\/a><\/h6>\n \nSET_TRANSFORM_PARAM and SET_REMAP_PARAM<\/a>\u00a0Procedure<\/a>s<\/h6>\nThese procedures are used for both retrieval and submission.\u00a0SET_TRANSFORM_PARAM<\/code>\u00a0and\u00a0SET_REMAP_PARAM<\/code>\u00a0specify parameters to the XSLT stylesheet identified by\u00a0transform_handle.<\/code>Use them to modify or customize the output of the transform.<\/h6>\n\n\n\n\n\nSee Also:<\/p>\n For more information about related subprograms:<\/p>\n \n\nSubprograms for Retrieving Multiple Objects From the Database<\/a><\/p>\n<\/li>\n \nSubprograms for Submitting XML to the Database<\/a><\/p>\n<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n <\/a><\/h6>\nSyntax<\/h6>\n DBMS_METADATA.SET_TRANSFORM_PARAM ( transform_handle IN NUMBER, name IN VARCHAR2, value IN VARCHAR2, object_type IN VARCHAR2 DEFAULT NULL); DBMS_METADATA.SET_TRANSFORM_PARAM ( transform_handle IN NUMBER, name IN VARCHAR2, value IN BOOLEAN DEFAULT TRUE, object_type IN VARCHAR2 DEFAULT NULL); DBMS_METADATA.SET_TRANSFORM_PARAM ( transform_handle IN NUMBER, name IN VARCHAR2, value IN NUMBER, object_type IN VARCHAR2 DEFAULT NULL); DBMS_METADATA.SET_REMAP_PARAM ( transform_handle IN NUMBER, name IN VARCHAR2, old_value IN VARCHAR2, new_value IN VARCHAR2, object_type IN VARCHAR2 DEFAULT NULL);<\/h6>\n<\/a><\/h6>\nParameters<\/h6>\nTable 57-21<\/a>\u00a0describes the parameters for the\u00a0SET_TRANSFORM_PARAM<\/code>\u00a0and\u00a0SET_REMAP_PARAM<\/code>\u00a0procedures.<\/h6>\n<\/a><\/a><\/h6>\nTable 57-21 SET_TRANSFORM_PARAM and SET_REMAP_PARAM Parameters<\/p>\n\n\n\n\n\n\n\n\n\n\nParameters<\/th>\n Description<\/th>\n<\/tr>\n<\/thead>\n \ntransform_handle<\/code><\/p>\n<\/td>\n \nEither (1) the handle returned from\u00a0ADD_TRANSFORM<\/code>, or (2) the enumerated constant\u00a0SESSION_TRANSFORM<\/code>\u00a0that designates the DDL transform for the whole session.<\/p>\n Note that the handle returned by\u00a0OPEN<\/code>\u00a0is not a valid transform handle.<\/p>\n For\u00a0SET_REMAP_PARAM<\/code>, the transform handle must designate the MODIFY transform.<\/p>\n<\/td>\n<\/tr>\n \nname<\/code><\/p>\n<\/td>\n \nThe name of the parameter.<\/p>\n Table 57-22<\/a>\u00a0lists the transform parameters defined for the DDL transform, specifying the\u00a0object_type<\/code>\u00a0it applies to, its datatype, and its meaning or effect. This includes its default value, if any, and whether the parameter is additive.<\/p>\n Table 57-23<\/a>\u00a0describes the parameters for the MODIFY transform in the\u00a0SET_TRANSFORM_PARAM<\/code>\u00a0procedure.<\/p>\n Table 57-24<\/a>\u00a0describes the parameters for the MODIFY transform in the\u00a0SET_REMAP_PARAM<\/code>\u00a0procedure.<\/p>\n<\/td>\n<\/tr>\n \nvalue<\/code><\/p>\n<\/td>\n \nThe value of the transform. This parameter is valid only for\u00a0SET_TRANSFORM_PARAM<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nold_value<\/code><\/p>\n<\/td>\n \nThe old value for the remapping. This parameter is valid only for\u00a0SET_REMAP_PARAM<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nnew_value<\/code><\/p>\n<\/td>\n \nThe new value for the remapping. This parameter is valid only for\u00a0SET_REMAP_PARAM<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nobject_type<\/code><\/p>\n<\/td>\n \nDesignates the object type to which the transform or remap parameter applies. By default, it applies to the same object type as the transform. In cases where the transform applies to all object types within a heterogeneous collection, the following apply:<\/p>\n \n\nIf\u00a0object_type<\/code>\u00a0is omitted, the parameter applies to all applicable object types within the heterogeneous collection.<\/p>\n<\/li>\n \nIf\u00a0object_type<\/code>\u00a0is specified, the parameter only applies to that object type.<\/p>\n<\/li>\n<\/ul>\n This allows a caller who has added a transform to a heterogeneous collection to specify different transform parameters for different object types within the collection.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Table 57-22<\/a>\u00a0describes the object type, name, datatype, and meaning of the parameters for the DDL transform in the\u00a0SET_TRANSFORM_PARAM<\/code>\u00a0procedure.<\/h6>\n<\/a><\/a><\/h6>\nTable 57-22 SET_TRANSFORM_PARAM: Transform Parameters for the DDL Transform<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nObject Type<\/th>\n Name<\/th>\n Datatype<\/th>\n Meaning<\/th>\n<\/tr>\n<\/thead>\n \nAll objects<\/code><\/p>\n<\/td>\n \nPRETTY<\/code><\/p>\n<\/td>\n \nBOOLEAN<\/code><\/p>\n<\/td>\n \nIf\u00a0TRUE<\/code>, format the output with indentation and line feeds. Defaults to\u00a0TRUE<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nAll objects<\/code><\/p>\n<\/td>\n \nSQLTERMINATOR<\/code><\/p>\n<\/td>\n \nBOOLEAN<\/code><\/p>\n<\/td>\n \nIf\u00a0TRUE<\/code>, append a SQL terminator (;<\/code>\u00a0or\u00a0\/<\/code>) to each DDL statement. Defaults to\u00a0FALSE<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nTABLE<\/code><\/p>\n<\/td>\n \nSEGMENT_ATTRIBUTES<\/code><\/p>\n<\/td>\n \nBOOLEAN<\/code><\/p>\n<\/td>\n \nIf\u00a0TRUE<\/code>, emit segment attributes (physical attributes, storage attributes, tablespace, logging). Defaults to\u00a0TRUE<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nTABLE<\/code><\/p>\n<\/td>\n \nSTORAGE<\/code><\/p>\n<\/td>\n \nBOOLEAN<\/code><\/p>\n<\/td>\n \nIf\u00a0TRUE<\/code>, emit storage clause. (Ignored if\u00a0SEGMENT_ATTRIBUTES<\/code>\u00a0is\u00a0FALSE<\/code>.) Defaults to\u00a0TRUE.<\/code><\/p>\n<\/td>\n<\/tr>\n \nTABLE<\/code><\/p>\n<\/td>\n \nTABLESPACE<\/code><\/p>\n<\/td>\n \nBOOLEAN<\/code><\/p>\n<\/td>\n \nIf\u00a0TRUE<\/code>, emit tablespace. (Ignored if\u00a0SEGMENT_ATTRIBUTES<\/code>\u00a0is\u00a0FALSE<\/code>.) Defaults to\u00a0TRUE<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nTABLE<\/code><\/p>\n<\/td>\n \nCONSTRAINTS<\/code><\/p>\n<\/td>\n \nBOOLEAN<\/code><\/p>\n<\/td>\n \nIf\u00a0TRUE<\/code>, emit all non-referential table constraints. Defaults to\u00a0TRUE<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nTABLE<\/code><\/p>\n<\/td>\n \nREF_CONSTRAINTS<\/code><\/p>\n<\/td>\n \nBOOLEAN<\/code><\/p>\n<\/td>\n \nIf\u00a0TRUE<\/code>, emit all referential constraints (foreign keys). Defaults to\u00a0TRUE<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nTABLE<\/code><\/p>\n<\/td>\n \nCONSTRAINTS_AS_ALTER<\/code><\/p>\n<\/td>\n \nBOOLEAN<\/code><\/p>\n<\/td>\n \nIf\u00a0TRUE<\/code>, emit table constraints as separate\u00a0ALTER TABLE<\/code>\u00a0(and, if necessary,\u00a0CREATE INDEX<\/code>) statements. If\u00a0FALSE<\/code>, specify table constraints as part of the\u00a0CREATE TABLE<\/code>\u00a0statement. Defaults to\u00a0FALSE<\/code>. Requires that\u00a0CONSTRAINTS be TRUE.<\/code><\/p>\n<\/td>\n<\/tr>\n \nTABLE<\/code><\/p>\n<\/td>\n \nOID<\/code><\/p>\n<\/td>\n \nBOOLEAN<\/code><\/p>\n<\/td>\n \nIf\u00a0TRUE<\/code>, emit the OID clause for object tables. Defaults to\u00a0FALSE<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nTABLE<\/code><\/p>\n<\/td>\n \nSIZE_BYTE_KEYWORD<\/code><\/p>\n<\/td>\n \nBOOLEAN<\/code><\/p>\n<\/td>\n \nIf\u00a0TRUE<\/code>, emit the\u00a0BYTE<\/code>\u00a0keyword as part of the size specification of\u00a0CHAR<\/code>\u00a0and\u00a0VARCHAR2<\/code>\u00a0columns that use byte semantics. If\u00a0FALSE<\/code>, omit the keyword. Defaults to\u00a0FALSE.<\/code><\/p>\n<\/td>\n<\/tr>\n \nINDEX<\/code>,\u00a0CONSTRAINT<\/code>,\u00a0ROLLBACK_SEGMENT<\/code>,\u00a0CLUSTER<\/code>,\u00a0TABLESPACE<\/code><\/p>\n<\/td>\n \nSEGMENT_ATTRIBUTES<\/code><\/p>\n<\/td>\n \nBOOLEAN<\/code><\/p>\n<\/td>\n \nIf\u00a0TRUE<\/code>, emit segment attributes (physical attributes, storage attributes, tablespace, logging). Defaults to\u00a0TRUE<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nINDEX<\/code>,\u00a0CONSTRAINT<\/code>,\u00a0ROLLBACK_SEGMENT<\/code>,\u00a0CLUSTER<\/code><\/p>\n<\/td>\n \nSTORAGE<\/code><\/p>\n<\/td>\n \nBOOLEAN<\/code><\/p>\n<\/td>\n \nIf\u00a0TRUE<\/code>, emit storage clause. (Ignored if\u00a0SEGMENT_ATTRIBUTES<\/code>\u00a0is\u00a0FALSE<\/code>.) Defaults to\u00a0TRUE<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nINDEX<\/code>,\u00a0CONSTRAINT<\/code>,\u00a0ROLLBACK_SEGMENT<\/code>,\u00a0CLUSTER<\/code><\/p>\n<\/td>\n \nTABLESPACE<\/code><\/p>\n<\/td>\n \nBOOLEAN<\/code><\/p>\n<\/td>\n \nIf\u00a0TRUE<\/code>, emit tablespace. (Ignored if\u00a0SEGMENT_ATTRIBUTES<\/code>\u00a0is\u00a0FALSE<\/code>.) Defaults to\u00a0TRUE<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nTYPE<\/code><\/p>\n<\/td>\n \nSPECIFICATION<\/code><\/p>\n<\/td>\n \nBOOLEAN<\/code><\/p>\n<\/td>\n \nIf\u00a0TRUE<\/code>, emit the type specification. Defaults to\u00a0TRUE<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nTYPE<\/code><\/p>\n<\/td>\n \nBODY<\/code><\/p>\n<\/td>\n \nBOOLEAN<\/code><\/p>\n<\/td>\n \nIf\u00a0TRUE<\/code>, emit the type body. Defaults to\u00a0TRUE<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nTYPE<\/code><\/p>\n<\/td>\n \nOID<\/code><\/p>\n<\/td>\n \nBOOLEAN<\/code><\/p>\n<\/td>\n \nIf\u00a0TRUE<\/code>, emit the OID clause. Defaults to\u00a0FALSE<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nPACKAGE<\/code><\/p>\n<\/td>\n \nSPECIFICATION<\/code><\/p>\n<\/td>\n \nBOOLEAN<\/code><\/p>\n<\/td>\n \nIf\u00a0TRUE<\/code>, emit the package specification. Defaults to\u00a0TRUE<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nPACKAGE<\/code><\/p>\n<\/td>\n \nBODY<\/code><\/p>\n<\/td>\n \nBOOLEAN<\/code><\/p>\n<\/td>\n \nIf\u00a0TRUE<\/code>, emit the package body. Defaults to\u00a0TRUE<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nVIEW<\/code><\/p>\n<\/td>\n \nFORCE<\/code><\/p>\n<\/td>\n \nBOOLEAN<\/code><\/p>\n<\/td>\n \nIf\u00a0TRUE<\/code>, use the\u00a0FORCE<\/code>\u00a0keyword in the\u00a0CREATE VIEW<\/code>\u00a0statement. Defaults to\u00a0TRUE<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nOUTLINE<\/code><\/p>\n<\/td>\n \nINSERT<\/code><\/p>\n<\/td>\n \nBOOLEAN<\/code><\/p>\n<\/td>\n \nIf\u00a0TRUE<\/code>, emit the\u00a0INSERT<\/code>\u00a0statements into the OL$ dictionary tables that will create the outline and its hints. If\u00a0FALSE<\/code>, emit a\u00a0CREATE<\/code>\u00a0OUTLINE<\/code>\u00a0statement. Defaults to\u00a0FALSE<\/code>.<\/p>\n Note: This object type is being deprecated.<\/p>\n<\/td>\n<\/tr>\n \nAll objects<\/code><\/p>\n<\/td>\n \nDEFAULT<\/code><\/p>\n<\/td>\n \nBOOLEAN<\/code><\/p>\n<\/td>\n \nCalling\u00a0SET_TRANSFORM_PARAM<\/code>\u00a0with this parameter set to\u00a0TRUE<\/code>\u00a0has the effect of resetting all parameters for the transform to their default values. Setting this\u00a0FALSE<\/code>\u00a0has no effect. There is no default.<\/p>\n<\/td>\n<\/tr>\n \nAll objects<\/code><\/p>\n<\/td>\n \nINHERIT<\/code><\/p>\n<\/td>\n \nBOOLEAN<\/code><\/p>\n<\/td>\n \nIf\u00a0TRUE<\/code>, inherits session-level parameters. Defaults to\u00a0FALSE<\/code>. If an application calls\u00a0ADD_TRANSFORM<\/code>\u00a0to add the DDL transform, then by default the only transform parameters that apply are those explicitly set for that transform handle. This has no effect if the transform handle is the session transform handle.<\/p>\n<\/td>\n<\/tr>\n \nROLE<\/code><\/p>\n<\/td>\n \nREVOKE_FROM<\/code><\/p>\n<\/td>\n \nText<\/code><\/p>\n<\/td>\n \nThe name of a user from whom the role must be revoked. If this is a non-null string and if the\u00a0CREATE<\/code>\u00a0ROLE<\/code>\u00a0statement grants you the role, a\u00a0REVOKE<\/code>\u00a0statement is emitted after the\u00a0CREATE<\/code>\u00a0ROLE<\/code>.<\/p>\n Note: When you issue a\u00a0CREATE<\/code>\u00a0ROLE<\/code>\u00a0statement, Oracle may grant you the role. You can use this transform parameter to undo the grant.<\/p>\n Defaults to null string.<\/p>\n<\/td>\n<\/tr>\n \nTABLESPACE<\/code><\/p>\n<\/td>\n \nREUSE<\/code><\/p>\n<\/td>\n \nBOOLEAN<\/code><\/p>\n<\/td>\n \nIf\u00a0TRUE<\/code>, include the\u00a0REUSE<\/code>\u00a0parameter for datafiles in a tablespace to indicate that existing files can be reused.<\/p>\n Defaults to\u00a0FALSE<\/code>.<\/p>\n<\/td>\n<\/tr>\n \nCLUSTER<\/code>,\u00a0INDEX<\/code>,\u00a0ROLLBACK_SEGMENT<\/code>,\u00a0TABLE<\/code>,\u00a0TABLESPACE<\/code><\/p>\n<\/td>\n \nPCTSPACE<\/code><\/p>\n<\/td>\n \nNUMBER<\/code><\/p>\n<\/td>\n \nA number representing the percentage by which space allocation for the object type is to be modified. The value is the number of one-hundreths of the current allocation. For example, 100 means 100%.<\/p>\n If the object type is\u00a0TABLESPACE<\/code>, the following size values are affected:<\/p>\n – in file specifications, the value of\u00a0SIZE<\/code><\/p>\n –\u00a0MINIMUM<\/code>\u00a0EXTENT<\/code><\/p>\n –\u00a0EXTENT<\/code>\u00a0MANAGEMENT<\/code>\u00a0LOCAL<\/code>\u00a0UNIFORM<\/code>\u00a0SIZE<\/code><\/p>\n For other object types,\u00a0INITIAL<\/code>\u00a0and\u00a0NEXT<\/code>\u00a0are affected.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Table 57-23<\/a>\u00a0describes the object type, name, datatype, and meaning of the parameters for the MODIFY transform in the\u00a0SET_TRANSFORM_PARAM<\/code>\u00a0procedure.<\/h6>\n<\/a><\/a><\/h6>\nTable 57-23 SET_TRANSFORM_PARAM: Transform Parameters for the MODIFY Transform<\/p>\n\n\n\n\n\nObject Type<\/th>\n Name<\/th>\n Datatype<\/th>\n Meaning<\/th>\n<\/tr>\n<\/thead>\n \nAll objects<\/code><\/p>\n<\/td>\n \nOBJECT_ROW<\/code><\/p>\n<\/td>\n \nNUMBER<\/code><\/p>\n<\/td>\n \nA number designating the object row for an object. The object in the document that corresponds to this number will be copied to the output document.<\/p>\n This parameter is additive.<\/p>\n By default, all objects are copied to the output document.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Table 57-24<\/a>\u00a0describes the object type, name, datatype, and meaning of the parameters for the MODIFY transform in the\u00a0SET_REMAP_PARAM<\/code>\u00a0procedure.<\/h6>\n<\/a><\/a><\/h6>\nTable 57-24 SET_REMAP_PARAM: Transform Parameters for the MODIFY Transform<\/p>\n\n\n\n\n\n\n\nObject Type<\/th>\n Name<\/th>\n Datatype<\/th>\n Meaning<\/th>\n<\/tr>\n<\/thead>\n \nLIBRARY, TABLESPACE, DIRECTORY<\/code><\/p>\n<\/td>\n \nREMAP_DATAFILE<\/code><\/p>\n<\/td>\n \nText<\/code><\/p>\n<\/td>\n \nObjects in the document will have their filespecs renamed as follows: any filespec matching\u00a0old_value<\/code>\u00a0will be changed to\u00a0new_value<\/code>. Filespecs should\u00a0not<\/span>\u00a0be enclosed in quotes.<\/p>\n This parameter is additive.<\/p>\n By default, filespecs are not renamed.<\/p>\n<\/td>\n<\/tr>\n \nSchema Objects, Dependent Objects, Granted Objects, USER<\/code><\/p>\n<\/td>\n \nREMAP_SCHEMA<\/code><\/p>\n<\/td>\n \nText<\/code><\/p>\n<\/td>\n \nAny schema object in the document whose name matches\u00a0old_value<\/code>\u00a0will have its schema name changed to\u00a0new_value<\/code>.<\/p>\n Any dependent object whose base object schema name matches\u00a0old_value<\/code>\u00a0will have its base object schema name changed to\u00a0new_value<\/code>.<\/p>\n Any granted object whose grantee name matches\u00a0old_value<\/code>\u00a0will have its grantee name changed to\u00a0new_value<\/code>.<\/p>\n Any user whose name matches\u00a0old_value<\/code>\u00a0will have its name changed to\u00a0new_value<\/code>.<\/p>\n This parameter is additive.<\/p>\n By default, schemas are not remapped.<\/p>\n<\/td>\n<\/tr>\n \nTABLE, CLUSTER, CONSTRAINT, INDEX, ROLLBACK_SEGMENT, MATERIALIZED_VIEW, MATERIALIZED_VIEW_LOG, TABLESPACE_QUOTA<\/code><\/p>\n<\/td>\n \nREMAP_TABLESPACE<\/code><\/p>\n<\/td>\n \nText<\/code><\/p>\n<\/td>\n \nObjects in the document will have their tablespaces renamed as follows: any tablespace name matching\u00a0old_value<\/code>\u00a0will be changed to\u00a0new_value<\/code>.<\/p>\n This parameter is additive.<\/p>\n By default, tablespaces are not remapped.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n <\/a><\/h6>\nExceptions<\/h6>\n\n\nINVALID_ARGVAL.<\/code>\u00a0A\u00a0NULL<\/code>\u00a0or invalid value was supplied for an input parameter. The error message text identifies the parameter.<\/h6>\n<\/li>\n\nINVALID_OPERATION.<\/code>\u00a0Either\u00a0SET_TRANSFORM_PARAM<\/code>\u00a0or\u00a0SET_REMAP_PARAM<\/code>\u00a0was called after the first call to\u00a0FETCH_xxx<\/code>\u00a0for the\u00a0OPEN<\/code>\u00a0context. After the first call to\u00a0FETCH_xxx<\/code>\u00a0is made, no further calls to\u00a0SET_TRANSFORM_PARAM<\/code>\u00a0or\u00a0SET_REMAP_PARAM<\/code>\u00a0are permitted.<\/h6>\n<\/li>\n\nINCONSISTENT_ARGS<\/code>. The arguments are inconsistent. This can mean the following:<\/h6>\n\n\nThe transform parameter\u00a0name<\/code>\u00a0is not valid for the object type associated with the\u00a0OPEN<\/code>\u00a0context or for the transform associated with the transform handle.<\/h6>\n<\/li>\n\nThe transform applies to all object types in a heterogeneous collection, but\u00a0object_type<\/code>\u00a0is not part of the collection.<\/h6>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/a><\/h6>\nUsage Notes<\/h6>\n XSLT allows parameters to be passed to stylesheets. You call\u00a0SET_TRANSFORM_PARAM<\/code>\u00a0or\u00a0SET_REMAP_PARAM<\/code>\u00a0to specify the value of a parameter to be passed to the stylesheet identified by\u00a0transform_handle<\/code>.<\/h6>\nNormally, if you call\u00a0SET_TRANSFORM_PARAMETER<\/code>\u00a0multiple times for the same parameter name, each call overrides the prior call. For example, the following sequence simply sets the\u00a0STORAGE<\/code>\u00a0transform parameter to\u00a0TRUE<\/code>.<\/h6>\nSET_TRANSFORM_PARAM(tr_handle,’STORAGE’,false); SET_TRANSFORM_PARAM(tr_handle,’STORAGE’,true);<\/h6>\n However, some transform parameters are additive which means that all specified parameter values are applied to the document, not just the last one. For example, the\u00a0OBJECT_ROW<\/code>\u00a0parameter to the\u00a0MODIFY<\/code>\u00a0transform is additive. If you specify the following, then both specified rows are copied to the output document.<\/h6>\nSET_TRANSFORM_PARAM(tr_handle,’OBJECT_ROW’,5); SET_TRANSFORM_PARAM(tr_handle,’OBJECT_ROW’,8);<\/h6>\n The\u00a0REMAP_TABLESPACE<\/code>\u00a0parameter is also additive. If you specify the following, then tablespaces TBS1 and TBS3 are changed to TBS2 and TBS4, respectively.<\/h6>\nSET_REMAP_PARAM(tr_handle,’REMAP_TABLESPACE’,’TBS1′,’TBS2′); SET_REMAP_PARAM(tr_handle,’REMAP_TABLESPACE’,’TBS3′,’TBS4′);<\/h6>\n The order in which the transformations are performed is undefined. For example, if you specify the following, the result is undefined.<\/h6>\n SET_REMAP_PARAM(tr_handle,’REMAP_TABLESPACE’,’TBS1′,’TBS2′); SET_REMAP_PARAM(tr_handle,’REMAP_TABLESPACE’,’TBS2′,’TBS3′);<\/h6>\n<\/div>\n<\/HTML><\/HTML><\/p>\n","protected":false},"excerpt":{"rendered":" O pacote DBMS_METADATA fornece uma maneira para que voc\u00ea possa recuperar metadados do dicion\u00e1rio banco de dados como XML ou cria\u00e7\u00e3o DDL e submeter o… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29,124,126,110],"tags":[],"class_list":["post-8904","post","type-post","status-publish","format-standard","hentry","category-base-de-conhecimentos","category-database","category-developer-tools","category-estudo-e-pesquisa"],"_links":{"self":[{"href":"https:\/\/orabr.virttus.com\/index.php?rest_route=\/wp\/v2\/posts\/8904","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/orabr.virttus.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/orabr.virttus.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/orabr.virttus.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/orabr.virttus.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=8904"}],"version-history":[{"count":5,"href":"https:\/\/orabr.virttus.com\/index.php?rest_route=\/wp\/v2\/posts\/8904\/revisions"}],"predecessor-version":[{"id":8909,"href":"https:\/\/orabr.virttus.com\/index.php?rest_route=\/wp\/v2\/posts\/8904\/revisions\/8909"}],"wp:attachment":[{"href":"https:\/\/orabr.virttus.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=8904"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/orabr.virttus.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=8904"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/orabr.virttus.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=8904"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}