Which has the higher priority in your organization: Deploying a new database or securing the ones you already have?
Looking for a website, and resources, dedicated solely to securing Oracle databases? Check out DBSecWorx.
Purpose
Undocumented but appears to relate to obtaining a safe System Change Number off the stack for use with DataPump.
AUTHID
CURRENT_USER
Dependencies
DBMS_INTERNAL_LOGSTDBY
KUPM$MCP
KUPW$WORKER
DBMS_STREAMS_DATAPUMP
Documented
No
First Available
Not known
Security Model
Owned by SYS with EXECUTE granted to the EXECUTE_CATALOG_ROLE and LOGSTDBY ADMINISTRATOR roles
dbms_internal_safe_scn.need_scn(
DBLINK IN VARCHAR2,
DBVERSION IN VARCHAR2,
COMPATIBILITY IN VARCHAR2,
INTEREST OUT BOOLEAN,
COOKIE IN OUT VARCHAR2);
-- a test seems to indicate that this must be run from within a datapump job
DECLARE
b BOOLEAN;
c VARCHAR2(200) := 'TEST';
BEGIN
dbms_internal_safe_scn.need_scn('','18.0.0.0','18.1.0', b, c);
dbms_output.put_line(c);
END;
/
DECLARE
*
ERROR at line 1:
ORA-31623: a job is not attached to this session via the specified handle
ORA-06512: at "SYS.DBMS_DATAPUMP", line 4747
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 79
ORA-06512: at "SYS.DBMS_DATAPUMP", line 4494
ORA-06512: at "SYS.DBMS_DATAPUMP", line 5973
ORA-06512: at "SYS.DBMS_STREAMS_DATAPUMP_UTIL", line 18
ORA-06512: at "SYS.DBMS_STREAMS_DATAPUMP_UTIL", line 80
ORA-06512: at "SYS.DBMS_STREAMS_DATAPUMP", line 219
ORA-06512: at "SYS.DBMS_INTERNAL_SAFE_SCN", line 44
ORA-06512: at line 5
dbms_internal_safe_scn.set_export_scn(
SCHEMA IN VARCHAR2,
NAME IN VARCHAR2,
TYPE IN VARCHAR2,
COOKIE IN VARCHAR2,
SCN IN NUMBER,
ORIGINAL_SCHEMA IN VARCHAR2,
ORIGINAL_NAME IN VARCHAR2);
Returns the next, safe, SCN based above the current SCN
dbms_internal_safe_scn.wait_for_safe_scn(
SCHEMA IN VARCHAR2,
TABLENAME IN VARCHAR2,
TIMEOUT IN VARCHAR2,
SCN IN NUMBER,
DBID IN NUMBER)
RETURN NUMBER;