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.
Purpose
Internal support utilities for Data Guard Logical Standby Databases
exec dbms_internal_logstdby.capture_scn;
BEGIN dbms_internal_logstdby.capture_scn; END;
*
ERROR at line 1:
ORA-16287: operation not permitted due to active apply state
ORA-06512: at "SYS.DBMS_INTERNAL_LOGSTDBY", line 373
ORA-06512: at line 1
dbms_internal_logstdby.enable_logical_replication(repl_state IN BOOLEAN);
DECLARE
retVal BOOLEAN := dbms_internal_logstdby.disable_logical_replication;
BEGIN
IF retVal THEN
dbms_output.put_line('TRUE');
ELSE
dbms_output.put_line('FALSE');
END IF;
END;
/
DECLARE
retVal BOOLEAN := dbms_internal_logstdby.disable_logical_replication;
BEGIN
IF retVal THEN
dbms_output.put_line('TRUE');
ELSE
dbms_output.put_line('FALSE');
END IF;
END;
/
DECLARE
retVal BOOLEAN := dbms_internal_logstdby.disable_logical_replication;
BEGIN
IF retVal THEN
dbms_output.put_line('TRUE');
ELSE
dbms_output.put_line('FALSE');
END IF;
END;
/
dbms_internal_logstdby.is_eds_maintained(
owner IN VARCHAR2,
table_name IN VARCHAR2)
RETURN BOOLEAN;
SQL> BEGIN
2 IF dbms_internal_logstdby.is_eds_maintained(USER, 'OBJ$') THEN
3 dbms_output.put_line('Extended Data Type Supportable');
4 ELSE
5 dbms_output.put_line('Not Extended Data Type Supportable');
6 END IF;
7 END;
8 /
Not Extended Data Type Supportable
dbms_internal_logstdby.is_eds_supportable(
owner IN VARCHAR2,
table_name IN VARCHAR2)
RETURN BOOLEAN;
SQL> BEGIN
2 IF dbms_internal_logstdby.is_eds_supportable(USER, 'OBJ$') THEN
3 dbms_output.put_line('Extended Data Type Supportable');
4 ELSE
5 dbms_output.put_line('Not Extended Data Type Supportable');
6 END IF;
7 END;
8 /
Not Extended Data Type Supportable
dbms_internal_logstdby.is_lsdby_supportable(
owner IN VARCHAR2,
table_name IN VARCHAR2)
RETURN BOOLEAN;
BEGIN
IF dbms_internal_logstdby.is_lsby_supportable(USER, 'OBJ$') THEN
dbms_output.put_line('Logical Standby Supportable');
ELSE
dbms_output.put_line('Not Logical Standby Supportable');
END IF;
END;
/
BEGIN
IF dbms_internal_logstdby.is_pdb_root THEN
dbms_output.put_line('Current container is CDB$ROOT');
ELSE
dbms_output.put_line('Current container is ' || SYS_CONTEXT('USERENV','CON_NAME'));
END IF;
END;
/
alter session set container = 'PDBDEV';
BEGIN
IF dbms_internal_logstdby.is_pdb_root THEN
dbms_output.put_line('Current container is CDB$ROOT');
ELSE
dbms_output.put_line('Current container is ' || SYS_CONTEXT('USERENV','CON_NAME'));
END IF;
END;
/
-- unfortunately an other example of Oracle doing EXCEPTION WHEN OTHERS THEN NULL
SQL> SELECT dbms_internal_logstdby.upcase(12a3.4)
2 FROM dual;
SELECT dbms_internal_logstdby.upcase(12a3.4)
*
ERROR at line 1:
ORA-00907: missing right parenthesis
-- all exactly the same behaviour as the UPPER function in STANDARD
SQL> exec dbms_internal_logstdby.verify_session;
BEGIN dbms_internal_logstdby.verify_session; END;
*
ERROR at line 1:
ORA-16100: not a valid Logical Standby database
ORA-06512: at "SYS.DBMS_INTERNAL_LOGSTDBY", line 919
ORA-06512: at line 1
