For how many years have you been working
with physical servers that are starving your database of the memory
necessary to deploy important new performance features such as the Result
Cache, Memoptimize Pool, In-Memory Aggregation, In-Memory Column Store, and
Full Database Caching? Too long? Contact me to learn how to improve all
queries ... not just some queries.
The DBMS_XDB package supports the following features:
Resource Management subprograms which complement Resource Views
The Access Control List (ACL)-based Security Mechanism
Configuration Session Management
Creation of the XDB username
The DBMS_XDB package subprograms and constants are deprecated with Oracle Database 12c but still present in 18c.
While all features continue to be supported for backward compatibility, Oracle recommends that you use the alternative procedures provided in each case as identified below.
Constant number for 1st argument of setListenerEndPoint
Constant number for 4th argument of setListenerEndPoint
Retrieves the parameters of a listener end point corresponding to the XML DB HTTP server. The parameters of both HTTP and HTTP2 end points can be retrieved by invoking this procedure.
In 12c this proc is deprecated and replaced by DBMS_XDB_CONFIG.GETLISTENERENDPOINT.
endpoint IN NUMBER,
host OUT VARCHAR2,
port OUT NUMBER,
protocol OUT NUMBER);
Sets the parameters of a listener end point corresponding to the XML DB HTTP server. Both HTTP and HTTP2 end points can be set by invoking this procedure.
In 12c this proc is deprecated and replaced by DBMS_XDB_CONFIG.SETLISTENERENDPOINT.
endpoint IN NUMBER,
host IN VARCHAR2,
port IN NUMBER,
protocol IN NUMBER);
Restricts listener end points of the XML DB HTTP server to listen only on the localhost interface if TRUE or to all listener end points if FALSE.
In 12c this proc is deprecated and replaced by DBMS_XDB_CONFIG.SETLISTENERLOCALACCESS.
dbms_xdb.setListenerLocalAccess(l_access IN BOOLEAN);