eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

XDB.DBMS_XMLSTORAGE_MANAGE dependencies on XMLTYPE

Line 82: -- the constraints for both xmltype

78: clear Boolean default FALSE);
79:
80:
81: -- This procedure will be used to drop the indexes and disable
82: -- the constraints for both xmltype
83: -- table (no P_COL_NAME) and xmltype columns.
84: -- For xmltype tables, the user needs to pass the xmltype-table
85: -- name on which the bulk load operation is to be performed.
86: -- For xmltype columns, the user needs to pass

Line 83: -- table (no P_COL_NAME) and xmltype columns.

79:
80:
81: -- This procedure will be used to drop the indexes and disable
82: -- the constraints for both xmltype
83: -- table (no P_COL_NAME) and xmltype columns.
84: -- For xmltype tables, the user needs to pass the xmltype-table
85: -- name on which the bulk load operation is to be performed.
86: -- For xmltype columns, the user needs to pass
87: -- the relational table_name and the corresponding xmltype column name.

Line 84: -- For xmltype tables, the user needs to pass the xmltype-table

80:
81: -- This procedure will be used to drop the indexes and disable
82: -- the constraints for both xmltype
83: -- table (no P_COL_NAME) and xmltype columns.
84: -- For xmltype tables, the user needs to pass the xmltype-table
85: -- name on which the bulk load operation is to be performed.
86: -- For xmltype columns, the user needs to pass
87: -- the relational table_name and the corresponding xmltype column name.
88:

Line 86: -- For xmltype columns, the user needs to pass

82: -- the constraints for both xmltype
83: -- table (no P_COL_NAME) and xmltype columns.
84: -- For xmltype tables, the user needs to pass the xmltype-table
85: -- name on which the bulk load operation is to be performed.
86: -- For xmltype columns, the user needs to pass
87: -- the relational table_name and the corresponding xmltype column name.
88:
89: procedure enableIndexesAndConstraints(owner_name varchar2 default user,
90: table_name varchar2,

Line 87: -- the relational table_name and the corresponding xmltype column name.

83: -- table (no P_COL_NAME) and xmltype columns.
84: -- For xmltype tables, the user needs to pass the xmltype-table
85: -- name on which the bulk load operation is to be performed.
86: -- For xmltype columns, the user needs to pass
87: -- the relational table_name and the corresponding xmltype column name.
88:
89: procedure enableIndexesAndConstraints(owner_name varchar2 default user,
90: table_name varchar2,
91: column_name varchar2 default NULL);

Line 97: -- When P_COL_NAME is passed, it does the same for this xmltype column.

93:
94: -- This procedure will rebuild all indexes and enable the constraints
95: -- on the P_TABLE_NAME including its
96: -- child and out of line tables.
97: -- When P_COL_NAME is passed, it does the same for this xmltype column.
98:
99:
100: -- routine to disable constraints before exchange partition
101: procedure ExchangePreProc(owner_name varchar2 default user,

Line 112: namespaces IN VARCHAR2 default NULL) RETURN XMLTYPE;

108: function xpath2TabColMapping(owner_name VARCHAR2 default user,
109: table_name IN VARCHAR2,
110: column_name IN VARCHAR2 default NULL,
111: xpath IN VARCHAR2,
112: namespaces IN VARCHAR2 default NULL) RETURN XMLTYPE;
113:
114: function getSIDXDefFromView(viewName IN VARCHAR2) RETURN CLOB;
115:
116: --routine to get the type creation DDL for all CDB invalid types after PDB plugin