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.
dbms_sqadm_syscalls.kwsa_3gl_addCSub(
q_schema IN VARCHAR2,
q_name IN VARCHAR2,
sub_name IN VARCHAR2,
sub_id IN NUMBER,
pos_bmap OUT NUMBER,
create_time IN TIMESTAMP WITH TIME ZONE,
flags OUT NUMBER,
parent_id OUT NUMBER,
parent IN VARCHAR2);
dbms_sqadm_syscalls.kwsa_3gl_addDSub(
q_schema IN VARCHAR2,
q_name IN VARCHAR2,
sub_name IN VARCHAR2,
sub_addr IN VARCHAR2,
sub_prot IN NUMBER,
sub_id IN NUMBER,
pos_bmapP OUT NUMBER,
rule_name IN VARCHAR2,
trans_sch IN VARCHAR2,
trans_name IN VARCHAR2,
create_time IN TIMESTAMP WITH TIME ZONE,
flags IN NUMBER);
dbms_sqadm_syscalls.kwsa_3gl_alterDSub(
q_schema IN VARCHAR2,
q_name IN VARCHAR2,
sub_name IN VARCHAR2,
rule_name IN VARCHAR2,
trans_sch IN VARCHAR2,
trans_name IN VARCHAR2,
updrule IN BOOLEAN,
updtrans IN BOOLEAN);
dbms_sqadm_syscalls.kwsa_3gl_drpCSub(
q_schema IN VARCHAR2,
q_name IN VARCHAR2,
sub_name IN VARCHAR2,
sub_addr IN VARCHAR2,
sub_prot IN NUMBER,
sub_id IN NUMBER,
qid IN NUMBER,
par_name IN VARCHAR2);
dbms_sqadm_syscalls.kwsa_3gl_drpDSub(
q_schema IN VARCHAR2,
q_name IN VARCHAR2,
sub_name IN VARCHAR2,
sub_addr IN VARCHAR2,
sub_prot IN NUMBER,
sub_id IN NUMBER,
qid IN NUMBER);