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_XDB_REPOS dependencies on DBMS_XDB

Line 1: PACKAGE dbms_xdb_repos AUTHID CURRENT_USER IS

1: PACKAGE dbms_xdb_repos AUTHID CURRENT_USER IS
2:
3: ------------
4: -- CONSTANTS
5: --

Line 339: -- DBMS_XDB.LINK_TYPE_HARD (default)

335: -- Name of the new link.
336: -- linktype
337: -- Type of link to be created.
338: -- One of the following:
339: -- DBMS_XDB.LINK_TYPE_HARD (default)
340: -- DBMS_XDB.LINK_TYPE_WEAK
341: -- DBMS_XDB.LINK_TYPE_SYMBOLIC
342: ---------------------------------------------
343: PROCEDURE Link(srcpath IN VARCHAR2, linkfolder IN VARCHAR2,

Line 340: -- DBMS_XDB.LINK_TYPE_WEAK

336: -- linktype
337: -- Type of link to be created.
338: -- One of the following:
339: -- DBMS_XDB.LINK_TYPE_HARD (default)
340: -- DBMS_XDB.LINK_TYPE_WEAK
341: -- DBMS_XDB.LINK_TYPE_SYMBOLIC
342: ---------------------------------------------
343: PROCEDURE Link(srcpath IN VARCHAR2, linkfolder IN VARCHAR2,
344: linkname IN VARCHAR2,

Line 341: -- DBMS_XDB.LINK_TYPE_SYMBOLIC

337: -- Type of link to be created.
338: -- One of the following:
339: -- DBMS_XDB.LINK_TYPE_HARD (default)
340: -- DBMS_XDB.LINK_TYPE_WEAK
341: -- DBMS_XDB.LINK_TYPE_SYMBOLIC
342: ---------------------------------------------
343: PROCEDURE Link(srcpath IN VARCHAR2, linkfolder IN VARCHAR2,
344: linkname IN VARCHAR2,
345: linktype IN PLS_INTEGER := DBMS_XDB.LINK_TYPE_HARD);

Line 345: linktype IN PLS_INTEGER := DBMS_XDB.LINK_TYPE_HARD);

341: -- DBMS_XDB.LINK_TYPE_SYMBOLIC
342: ---------------------------------------------
343: PROCEDURE Link(srcpath IN VARCHAR2, linkfolder IN VARCHAR2,
344: linkname IN VARCHAR2,
345: linktype IN PLS_INTEGER := DBMS_XDB.LINK_TYPE_HARD);
346:
347: ---------------------------------------------
348: -- PROCEDURE - Rename
349: -- Renames a XDB resource

Line 686: FUNCTION getResource(abspath IN VARCHAR2) return dbms_xdbresource.XDBResource;

682: -- abspath - absolute path in the repository
683: -- RETURNS -
684: -- The XDBResource.
685: ---------------------------------------------
686: FUNCTION getResource(abspath IN VARCHAR2) return dbms_xdbresource.XDBResource;
687:
688: -----------------------------------------------------------
689: -- PROCEDURE - refreshContentSize
690: -- Recompute the content size of the specified resource,

Line 897: -- NOTE: Currently used by DBMS_XDBT, which is AUTHID CURRENT_USER

893: -- Returns the current tablespace of xdb, on the assumption
894: -- that that is the tablespace of XDB.XDB$RESOURCE.
895: -- PARAMETERS - None.
896: --
897: -- NOTE: Currently used by DBMS_XDBT, which is AUTHID CURRENT_USER
898: -- package, so this API will not be moved to DBMS_XDB_ADMIN.
899: -- This API is useful if we envision having XDB's objects
900: -- span multiple tablespaces. Otherwise, DBA_USERS can be queried.
901: ---------------------------------------------

Line 898: -- package, so this API will not be moved to DBMS_XDB_ADMIN.

894: -- that that is the tablespace of XDB.XDB$RESOURCE.
895: -- PARAMETERS - None.
896: --
897: -- NOTE: Currently used by DBMS_XDBT, which is AUTHID CURRENT_USER
898: -- package, so this API will not be moved to DBMS_XDB_ADMIN.
899: -- This API is useful if we envision having XDB's objects
900: -- span multiple tablespaces. Otherwise, DBA_USERS can be queried.
901: ---------------------------------------------
902: FUNCTION getxdb_tablespace RETURN VARCHAR2;

Line 904: end dbms_xdb_repos;

900: -- span multiple tablespaces. Otherwise, DBA_USERS can be queried.
901: ---------------------------------------------
902: FUNCTION getxdb_tablespace RETURN VARCHAR2;
903:
904: end dbms_xdb_repos;