Results for DBMS_METADATA


1 to 20 of 103 results. Prev  Next
Results per page:   20  | 40 | 60


Packages and Types Reference, 10g Release 1 (10.1)

50 DBMS_METADATA

50 DBMS_METADATAThe DBMS_METADATA package provides a way for you to retrieve metadata from the database dictionary … following topics: Using DBMS_METADATA Overview Security Model Types Rules and Limits Organization of … of XML to the Database Summary of DBMS_METADATA Subprograms

Packages and Types Reference, 10g Release 1 (10.1)

50 DBMS_METADATA

Using DBMS_METADATAOverview Security Model Types Rules and Limits Organization of Subprograms

Packages and Types Reference, 10g Release 1 (10.1)

50 DBMS_METADATA

Summary of DBMS_METADATA SubprogramsTable 50-3  DBMS_METADATA Package Subprograms Subprogram Description ADD_TRANSFORM Function

Packages and Types Reference, 10g Release 1 (10.1)

50 DBMS_METADATA

OverviewYou can use the DBMS_METADATA package to retrieve metadata and also to submit XML. Retrieving Metadata Submitting XML

Packages and Types Reference, 10g Release 1 (10.1)

50 DBMS_METADATA

Return ValuesThe metadata for the objects or NULL if all objects have been returned.

Packages and Types Reference, 10g Release 1 (10.1)

50 DBMS_METADATA

SyntaxDBMS_METADATA.GET_XML ( object_type IN VARCHAR2, name IN VARCHAR2 DEFAULT NULL, 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 DEFAULT NULL, schema IN VARCHAR2 DEFAULT NULL, version IN VARCHAR2 DEFAULT 'COMPATIBLE', model

Packages and Types Reference, 10g Release 1 (10.1)

50 DBMS_METADATA

OPENW ProcedureThis procedure specifies the type of object to be submitted and the object model. The return value is an opaque context handle. See Also: For more information about related subprograms: Subprograms for Submission of XML to the Database

Packages and Types Reference, 10g Release 1 (10.1)

50 DBMS_METADATA

Usage NotesXSLT allows parameters to be passed to stylesheets. You call SET_TRANSFORM_PARAM or SET_REMAP_PARAM to specify the value of a parameter to be passed to the stylesheet identified by transform_handle. Normally, if you call SET_TRANSFORM_PARAMETER multiple times for the same parameter name, each call overrides the prior call. For example, the following sequence simply sets the STORAGE transform parameter

Packages and Types Reference, 10g Release 1 (10.1)

50 DBMS_METADATA

Rules and LimitsIn an Oracle Shared Server (OSS) environment, the DBMS_METADATA package must disable session

Packages and Types Reference, 10g Release 1 (10.1)

50 DBMS_METADATA

ExceptionsINVALID_ARGVAL. A NULL or invalid value was supplied for an input parameter. The error message text identifies the parameter. INVALID_OPERATION. ADD_TRANSFORM was called after the first call to FETCH_xxx for the OPEN context. After the first call to FETCH_xxx is made, no further calls to ADD_TRANSFORM for the current OPEN context are permitted. INCONSISTENT_ARGS. The arguments are inconsistent. Possible

Packages and Types Reference, 10g Release 1 (10.1)

50 DBMS_METADATA

SyntaxDBMS_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;

Packages and Types Reference, 10g Release 1 (10.1)

50 DBMS_METADATA

ExceptionsINVALID_ARGVAL. A NULL or invalid value was supplied for an input parameter. The error message text identifies the parameter. OBJECT_NOT_FOUND. The specified object was not found in the database.

Packages and Types Reference, 10g Release 1 (10.1)

50 DBMS_METADATA

ExceptionsINVALID_ARGVAL. A NULL or invalid value was supplied for an input parameter. The error message text identifies the parameter. INVALID_OPERATION. SET_PARSE_ITEM was called after the first call to FETCH_xxx for the OPEN context. After the first call to FETCH_xxx is made, no further calls to SET_PARSE_ITEM are permitted. INCONSISTENT_ARGS. The attribute name is not valid for the object type associated

Packages and Types Reference, 10g Release 1 (10.1)

50 DBMS_METADATA

The GET_xxx FunctionsThe following GET_xxx functions let you fetch metadata for objects with a single call: GET_XML GET_DDL GET_DEPENDENT_XML GET_DEPENDENT_DDL GET_GRANTED_XML GET_GRANTED_DDL See Also: For more information about related subprograms: Subprograms for Retrieval of Multiple Objects from the Database

Packages and Types Reference, 10g Release 1 (10.1)

50 DBMS_METADATA

ExamplesExample: Fetch the XML Representation of SCOTT.EMP To generate complete, uninterrupted output, set the PAGESIZE to 0 and set LONG to some large number, as shown, before executing your query. SET LONG 2000000 SET PAGESIZE 0 SELECT DBMS_METADATA.GET_XML('TABLE','EMP','SCOTT') FROM DUAL; Example: Fetch the DDL for all Complete Tables in the Current Schema, Filter Out Nested Tables and Overflow Segments

Packages and Types Reference, 10g Release 1 (10.1)

50 DBMS_METADATA

Parametersg, this value cannot be lower than 9.2.0. model Specifies which view to use. Only the Oracle proprietary (ORACLE) view is supported by DBMS_METADATA.

Packages and Types Reference, 10g Release 1 (10.1)

50 DBMS_METADATA

PUT FunctionThis function submits an XML document containing object metadata to the database to create the objects. See Also: For more information about related subprograms: Subprograms for Submission of XML to the Database

Packages and Types Reference, 10g Release 1 (10.1)

50 DBMS_METADATA

Organization of SubprogramsThe DBMS_METADATA subprograms are used to retrieve objects from, and submit XML to, a database … submission. Table 50-3 provides a summary of DBMS_METADATA subprograms used to retrieve multiple … objects from a database. Table 50-2 provides a summary of DBMS_METADATA subprograms used to submit XML metadata to a database.

Packages and Types Reference, 10g Release 1 (10.1)

50 DBMS_METADATA

Usage NotesEach call to SET_FILTER causes a WHERE condition to be added to the underlying query that fetches the set of objects. The WHERE conditions are ANDed together, so you can use multiple SET_FILTER calls to refine the set of objects to be returned. For example to specify that you want the object named EMP in schema SCOTT, do the following:SET_FILTER(handle,'SCHEMA','SCOTT'); SET_FILTER(handle,'NAME','EMP');

Packages and Types Reference, 10g Release 1 (10.1)

50 DBMS_METADATA

Usage NotesThese functions and procedures return metadata for objects meeting the criteria established by the call to OPEN that returned the handle, and subsequent calls to SET_FILTER, SET_COUNT, ADD_TRANSFORM, and so on. Each call to FETCH_xxx returns the number of objects specified by SET_COUNT (or less, if fewer objects remain in the underlying cursor) until all objects have been returned. After the last


Was this page helpful?