The APEX_INSTANCE_ADMIN package provides utilities for managing an Oracle Application Express runtime environment. You use the APEX_INSTANCE_ADMIN package to get and set email settings, Oracle Wallet settings, report printing settings and to manage schema to workspace mappings. APEX_INSTANCE_ADMIN can be executed by the SYS, SYSTEM, and APEX_050000 database users and any database user granted the role APEX_ADMINISTRATOR_ROLE.
Table 11-1 lists all the available parameter values you can set within the APEX_INSTANCE_ADMIN package, including parameters for email, wallet, and reporting printing.
Table 11-1 Available Parameters
| Parameter Name | Description |
|---|---|
|
|
The maximum number of days an end-user account password may be used before the account is expired. |
|
|
If set to |
|
|
If set, users can only navigate to an application if the URL's hostname part contains this value. Instance administrators can configure more specific values at workspace level. |
|
|
If set to |
|
|
This parameter is only supported if running Oracle Database 12c. If set to |
|
|
If set to |
|
|
Controls the authentication scheme for the internal builder applications. Valid parameter values include:
|
|
|
Controls the URI path prefix used to access built-in RESTful Services exposed by Application Express. For example, built-in RESTful Service for referencing static application files using |
|
|
Controls instance wide setting of application activity log ([A]lways, [N]ever, [U]se application settings) |
|
|
The largest possible ID for a websheet or database application. |
|
|
The smallest possible ID for a websheet or database application. |
|
|
If set to |
|
|
If set to |
|
|
Defines the algorithm that is used to create one way hashes for URL checksums.Valid values are MD5 (deprecated), SH1 (SHA-1), SH256 (SHA-2, 256 bit), SH384 (SHA-2, 384 bit), SH512 (SHA-2, 512 bit) and null. The SHA-2 algorithms are only available on Oracle Database Release 12g and later. A null value evaluates to the most secure algorithm available and is the default. |
|
|
If set to N, the check for Oracle Application Express and Oracle REST Data Services product updates is disabled for the entire instance, regardless of preferences specified by individual developers. The default is Y. |
|
|
Uploaded files like application export files, websheet export files, spreadsheet data load files are automatically deleted after this number of days. Default is |
|
|
If set to |
|
|
If set to |
|
|
If set to |
|
|
Specifies the full URL to the images directory of Application Express instance, including the trailing slash after the images directory. For example: This setting is used for Oracle Application Express system-generated emails. |
|
|
Specifies the URL to Oracle Application Express instance, including the trailing slash after the Database Access Descriptor. For example: This setting used for Oracle Application Express system-generated emails. |
|
|
If set to |
|
|
If set to |
|
|
If set to |
|
|
Used in conjunction with the If set to |
|
|
List of http response headers, separated by newline (chr(10)). Application Express writes these headers on each request, before rendering the page. The substitution string |
|
|
|
|
|
Comma-separated list of IP addresses for proxy servers through which requests come in. |
|
|
The flag which determines the time increase in seconds after failed logins. |
|
|
The methods to count failed logins. Colon-separated list of |
|
|
The number of seconds an internal application may be idle. |
|
|
The number of seconds an internal application may be idle. |
|
|
The number of seconds an internal application session may exist. |
|
|
The number of seconds an internal application session may exist. |
|
|
The alphabetic characters used for password complexity rules. Default list of alphabetic characters include the following:
|
|
|
Defines the algorithm that is used to create one way hashes for workspace user passwords. Valid values are MD5 (deprecated), SH1 (SHA-1), SH256 (SHA-2, 256 bit), SH384 (SHA-2, 384 bit), SH512 (SHA-2, 512 bit) and null. The SHA-2 algorithms are only available on Oracle Database Release 12g and later. A null value evaluates to the most secure algorithm available and is the default. |
|
|
Defines the number of iterations for the |
|
|
Defines the maximum number of days a developer or administrator account password may be used before the account expires. The default value is 45 days. |
|
|
The punctuation characters used for password complexity rules. Default list of punctuation characters include the following: !"#$%&()``*+,-/:;<=>?_ |
|
|
If set to |
|
|
Specify either standard support or advanced support. Advanced support requires an Oracle BI Publisher license. Valid values include:
|
|
|
Specifies the host address of the print server converting engine, for example, |
|
|
Defines the port of the print server engine, for example |
|
|
Valid values include:
|
|
|
Defines the script that is the print server engine, for example: /xmlpserver/convert |
|
|
Number of seconds that an active old session can live, when |
|
|
Number of allowed concurrent requests to one session associated with this workspace. |
|
|
Number of allowed concurrent requests to sessions in this workspace. |
|
|
If set to |
|
|
Set to |
|
|
Set to |
|
|
If set to |
|
|
If set to |
|
|
If set, this is the resource manager consumer group to be used for all page events. A more specific group can be configured at workspace level. |
|
|
Determines default provisioning mode. Default is |
|
|
If set to |
|
|
Defines the "from" address for administrative tasks that generate email, such as approving a provision request or resetting a password. Enter a valid email address, for example:
|
|
|
Defines the server address of the SMTP server. If you are using another server as an SMTP relay, change this parameter to that server's address. Default setting: localhost |
|
|
Defines the port the SMTP server listens to for mail requests. Default setting: 25 |
|
|
Defines the password Application Express takes to authenticate itself against the SMTP server, with the parameter |
|
|
Defines whether Application Express opens an encrypted connection to the SMTP server. Encryption is only supported on database versions 11.2.0.2 and later. On earlier database versions, the connection is not encrypted. If set to If set to If |
|
|
Defines the username Application Express takes to authenticate itself against the SMTP server (default is null). Starting with database version 11.2.0.2, Application Express uses |
|
|
The maximum allowable size for an individual script result. Default is |
|
|
Defines the URL Application Express redirects to in order to trigger a logout from the Single Sign-On server. Application Express automatically appends Example: |
|
|
If set to |
|
|
Location of the help and documentation accessed from the Help link within the development environment. Default is |
|
|
If set to If set to |
|
|
The regular expression used to validate a username if the Builder authentication scheme is not APEX. Default is as follows: ^[[:alnum:]._%-]+@[[:alnum:].-]+\.[[:alpha:]]{2,4}$ |
|
|
The path to the wallet on the file system, for example:
file:/home/<username>/wallets
|
|
|
The password associated with the wallet. |
|
|
If set to |
|
|
Maximum number of emails allowed to be sent by using APEX_MAIL per workspace in a 24 hour period. Default is |
|
|
The maximum number of bytes for uploaded files for a workspace. A setting at the workspace-level overrides the instance-level setting. |
|
|
The maximum space allocated for script results. Default is |
|
|
If set to |
|
|
If set to |
The ADD_SCHEMA procedure adds a schema to a workspace to schema mapping.
APEX_INSTANCE_ADMIN.ADD_SCHEMA(
p_workspace IN VARCHAR2,
p_schema IN VARCHAR2);
Table 11-2 describes the parameters available in the ADD_SCHEMA procedure.
Table 11-2 ADD_SCHEMA Parameters
| Parameter | Description |
|---|---|
|
|
The name of the workspace to which the schema mapping is added. |
|
|
The schema to add to the schema to workspace mapping. |
The following example demonstrates how to use the ADD_SCHEMA procedure to map a schema mapped to a workspace.
BEGIN
APEX_INSTANCE_ADMIN.ADD_SCHEMA('MY_WORKSPACE','FRANK');
END;
The ADD_WORKSPACE procedure adds a workspace to an Application Express Instance.
APEX_INSTANCE_ADMIN.ADD_WORKSPACE(
p_workspace_id IN NUMBER DEFAULT NULL,
p_workspace IN VARCHAR2,
p_source_identifier IN VARCHAR2 DEFAULT NULL,
p_primary_schema IN VARCHAR2,
p_additional_schemas IN VARCHAR2,
p_rm_consumer_group IN VARCHAR2 DEFAULT NULL );
Table 11-3 describes the parameters available in the ADD_WORKSPACE procedure.
Table 11-3 ADD_WORKSPACE Parameters
| Parameter | Description |
|---|---|
|
|
The ID to uniquely identify the workspace in an Application Express instance. This may be left null and a new unique ID is assigned. |
|
|
The name of the workspace to be added. |
|
|
A short identifier for the workspace used when synchronizing feedback between different instances. |
|
|
The primary database schema to associate with the new workspace. |
|
|
A colon delimited list of additional schemas to associate with this workspace. |
|
|
Resource Manager consumer group which is used when executing applications of this workspace. |
The following example demonstrates how to use the ADD_WORKSPACE procedure to add a new workspace named MY_WORKSPACE using the primary schema, SCOTT, along with additional schema mappings for HR and OE.
BEGIN
APEX_INSTANCE_ADMIN.ADD_WORKSPACE (
p_workspace_id => 8675309,
p_workspace => 'MY_WORKSPACE',
p_primary_schema => 'SCOTT',
p_additional_schemas => 'HR:OE' );
END;
This procedure creates an exception which allows assignment of a restricted schema to a specific workspace.
APEX_INSTANCE_ADMIN.CREATE_SCHEMA_EXCEPTION (
p_schema in varchar2,
p_workspace in varchar2 );
Table 11-4 describes the parameters available for CREATE_SCHEMA_EXCEPTION procedure.
Table 11-4 CREATE_SCHEMA_EXCPETION Parameters
| Parameter | Description |
|---|---|
|
p_schema |
The schema. |
|
|
The workspace. |
This example allows the assignment of restricted schema HR to workspace HR_WORKSPACE.
begin
apex_instance_admin.create_schema_exception (
p_schema => 'HR',
p_workspace => 'HR_WORKSPACE' );
commit;
end;
This procedure removes the reservation of application IDs for a given workspace ID. Use this procedure to undo a reservation, when the reservation is not necessary anymore because it happened by mistake or the workspace no longer exists. To reserve application IDs for a given workspace, see "RESERVE_WORKSPACE_APP_IDS Procedure."
APEX_INSTANCE_ADMIN.FREE_WORKSPACE_APP_IDS (
p_workspace_id IN NUMBER );
Table 11-5 describes the parameters available in the FREE_WORKSPACE_APP_IDS procedure.
Table 11-5 FREE_WORKSPACE_APP_IDS Parameters
| Parameter | Description |
|---|---|
|
|
The unique ID of the workspace. |
This example illustrates how to undo the reservation of application IDS that belong to a workspace with an ID of 1234567890.
begin
apex_instance_admin.free_workspace_app_ids(1234567890);
end;
The GET_PARAMETER function retrieves the value of a parameter used in administering a runtime environment.
APEX_INSTANCE_ADMIN.GET_PARAMETER(
p_parameter IN VARCHAR2)
RETURN VARCHAR2;
Table 11-6 describes the parameters available in the GET_PARAMETER function.
Table 11-6 GET_PARAMETER Parameters
| Parameter | Description |
|---|---|
|
|
The instance parameter to be retrieved. |
The following example demonstrates how to use the GET_PARAMETER function to retrieve the SMTP_HOST_ADDRESS parameter currently defined for an Oracle Application Express instance.
DECLARE
L_VAL VARCHAR2(4000);
BEGIN
L_VAL :=APEX_INSTANCE_ADMIN.GET_PARAMETER('SMTP_HOST_ADDRESS');
DBMS_OUTPUT.PUT_LINE('The SMTP Host Setting Is: '||L_VAL);
END;
The GET_SCHEMAS function retrieves a comma-delimited list of schemas that are mapped to a given workspace.
APEX_INSTANCE_ADMIN.GET_SCHEMAS(
p_workspace IN VARCHAR2)
RETURN VARCHAR2;
Table 11-7 describes the parameters available in the GET_SCHEMAS function.
Table 11-7 GET_SCHEMAS Parameters
| Parameter | Description |
|---|---|
|
|
The name of the workspace from which to retrieve the schema list. |
The following example demonstrates how to use the GET_SCHEMA function to retrieve the underlying schemas mapped to a workspace.
DECLARE
L_VAL VARCHAR2(4000);
BEGIN
L_VAL :=APEX_INSTANCE_ADMIN.GET_SCHEMAS('MY_WORKSPACE');
DBMS_OUTPUT.PUT_LINE('The schemas for my workspace: '||L_VAL);
END;
The GET_WORKSPACE_PARAMETER procedure gets the workspace parameter.
get_workspace_parameter(
p_workspace IN VARCHAR2,
p_parameter IN VARCHAR2,
Table 11-8 describes the parameters available in GET_WORKSPACE_PARAMETER procedure.
Table 11-8 GET_WORKSPACE_PARAMETER Parameters
| Parameter | Description |
|---|---|
|
|
The name of the workspace to which you are getting the workspace parameter. |
|
|
The parameter name that overrides the instance parameter value of the same name for this workspace. Parameter names include:
|
The following example prints the value of ALLOW_HOSTNAMES for the HR workspace.
BEGIN
DBMS_OUTPUT.PUT_LINE (
APEX_INSTANCE_ADMIN.GET_WORKSPACE_PARAMETER (
p_workspace => 'HR',
p_parameter => 'ALLOW_HOSTNAMES' ));
END;
The REMOVE_APPLICATION procedure removes the application specified from the Application Express instance.
APEX_INSTANCE_ADMIN.REMOVE_APPLICATION (
p_application_id IN NUMBER);
Table 11-9 describes the REMOVE_APPLICATION procedure parameters.
Table 11-9 REMOVE_APPLICATION Parameters
| Parameter | Description |
|---|---|
|
|
The ID of the application to remove. |
The following example demonstrates how to use the REMOVE_APPLICATION procedure to remove an application with an ID of 100 from an Application Express instance.
BEGIN
APEX_INSTANCE_ADMIN.REMOVE_APPLICATION(100);
END;
The REMOVE_SAVED_REPORT procedure removes a specific user's saved interactive report settings for a particular application.
APEX_INSTANCE_ADMIN.REMOVE_SAVED_REPORT(
p_application_id IN NUMBER,
p_report_id IN NUMBER);
Table 11-10 describes the parameters available in the REMOVE_SAVED_REPORT procedure.
Table 11-10 REMOVE_SAVED_REPORT Parameters
| Parameter | Description |
|---|---|
|
|
The ID of the application for which to remove user saved interactive report information. |
|
p_report_id |
The ID of the saved user interactive report to be removed. |
The following example demonstrates how to use the REMOVE_SAVED_REPORT procedure to remove user saved interactive report with the ID 123 for the application with an ID of 100.
BEGIN
APEX_INSTANCE_ADMIN.REMOVE_SAVED_REPORT(100,123);
END;
The REMOVE_SAVED_REPORTS procedure removes all user saved interactive report settings for a particular application or for the entire instance.
APEX_INSTANCE_ADMIN.REMOVE_SAVED_REPORTS(
p_application_id IN NUMBER DEFAULT NULL);
Table 11-11 describes the parameters available in the REMOVE_SAVED_REPORTS procedure.
Table 11-11 REMOVE_SAVED_REPORTS Parameters
| Parameter | Description |
|---|---|
|
|
The ID of the application for which to remove user saved interactive report information. If this parameter is left null, all user saved interactive reports for the entire instance is removed. |
The following example demonstrates how to use the REMOVE_SAVED_REPORTS procedure to remove user saved interactive report information for the application with an ID of 100.
BEGIN
APEX_INSTANCE_ADMIN.REMOVE_SAVED_REPORTS(100);
END;
This REMOVE_SCHEMA procedure removes a workspace to schema mapping.
APEX_INSTANCE_ADMIN.REMOVE_SCHEMA(
p_workspace IN VARCHAR2,
p_schema IN VARCHAR2);
Table 11-12 describes the parameters available in the REMOVE_SCHEMA procedure.
Table 11-12 REMOVE_SCHEMA Parameters
| Parameter | Description |
|---|---|
|
|
The name of the workspace from which the schema mapping is removed. |
|
|
The schema to remove from the schema to workspace mapping. |
The following example demonstrates how to use the REMOVE_SCHEMA procedure to remove the schema named Frank from the MY_WORKSPACE workspace to schema mapping.
BEGIN
APEX_INSTANCE_ADMIN.REMOVE_SCHEMA('MY_WORKSPACE','FRANK');
END;
This procedure removes an exception that allows the assignment of a restricted schema to a given workspace.
APEX_INSTANCE_ADMIN.REMOVE_SCHEMA_EXCEPTION (
p_schema in varchar2,
p_workspace in varchar2 );
Table 11-13 describes the parameters available for REMOVE_SCHEMA_EXCEPTION procedure.
Table 11-13 REMOVE_SCHEMA_EXCEPTION Parameters
| Parameter | Description |
|---|---|
|
|
The schema. |
|
|
The workspace. |
This example removes the exception that allows the assignment of schema HR to workspace HR_WORKSPACE.
begin
apex_instance_admin.remove_schema_exception (
p_schema => 'HR',
p_workspace => 'HR_WORKSPACE' );
commit;
end;
This procedure removes all exceptions that allow the assignment of a given schema to workspaces.
APEX_INSTANCE_ADMIN.REMOVE_SCHEMA_EXCEPTIONS (
p_schema in varchar2 );
Table 11-14 describes the parameters available for REMOVE_SCHEMA_EXCEPTIONS procedure.
This example removes all exceptions that allow the assignment of the HR schema to workspaces.
begin
apex_instance_admin.remove_schema_exceptions (
p_schema => 'HR' );
commit;
end;
The REMOVE_SUBSCRIPTION procedure removes a specific interactive report subscription.
APEX_INSTANCE_ADMIN.REMOVE_SUBSCRIPTION(
p_subscription_id IN NUMBER);
Table 11-15 describes the parameters available for the REMOVE_SUBSCRIPTION procedure.
Table 11-15 REMOVE_SUBSCRIPTION Procedure Parameters
| Parameter | Description |
|---|---|
|
p_subscription_id |
The ID of the interactive report subscription to be removed. |
The following example demonstrates how to use the REMOVE_SUBSCRIPTION procedure to remove interactive report subscription with the ID 12345. Use of APEX_APPLICATION_PAGE_IR_SUB view can help identifying the subscription ID to remove.
BEGIN
APEX_INSTANCE_ADMIN.REMOVE_SUBSCRIPTION (
p_subscription_id => 12345);
END;
The REMOVE_WORKSPACE procedure removes a workspace from an Application Express instance.
APEX_INSTANCE_ADMIN.REMOVE_WORKSPACE(
p_workspace IN VARCHAR2,
p_drop_users IN VARCHAR2 DEFAULT 'N',
p_drop_tablespaces IN VARCHAR2 DEFAULT 'N' );
Table 11-16 describes the parameters available in the REMOVE_WORKSPACE procedure.
Table 11-16 REMOVE_WORKSPACE Parameters
| Parameter | Description |
|---|---|
|
|
The name of the workspace to be removed. |
|
|
|
|
|
'Y' to drop the tablespace associated with the database user associated with the workspace. The default is |
The following example demonstrates how to use the REMOVE_WORKSPACE procedure to remove an existing workspace named MY_WORKSPACE, along with the associated database users and tablespace.
BEGIN
APEX_INSTANCE_ADMIN.REMOVE_WORKSPACE('MY_WORKSPACE','Y','Y');
END;
This procedure removes all exceptions that allow the assignment of restricted schemas to given workspace.
APEX_INSTANCE_ADMIN.REMOVE_WORKSPACE_EXCEPTIONS ( p_workspace in varchar2 );
Table 11-14 describes the parameters available for REMOVE_WORKSPACE_EXCEPTIONS procedure.
This example removes all exceptions that allow the assignment of restricted schemas to HR_WORKSPACE.
begin apex_instance_admin.remove_schema_exceptions ( p_workspace => 'HR_WORKSPACE' ); commit;end;
This procedure permanently reserves the IDs of websheet and database applications in a given workspace. Even if the workspace and its applications get removed, developers can not create other applications with one of these IDs. To undo a reservation, see "FREE_WORKSPACE_APP_IDS Procedure."
APEX_INSTANCE_ADMIN.RESERVE_WORKSPACE_APP_IDS (
p_workspace_id IN NUMBER );
Table 11-18 describes the parameters available in the RESERVE_WORKSPACE_APP_IDS procedure.
Table 11-18 RESERVE_WORKSPACE_APP_IDS Parameters
| Parameter | Description |
|---|---|
|
|
The unique ID of the workspace. |
This example demonstrates setting up two separate Application Express instances where the application IDs are limited to within a specific range. At a later point, a workspace and all of it's applications are moved from instance 1 to instance 2. For the workspace that is moved, the developer reserves all of its application IDs to ensure that no applications with the same IDs are created on instance 1.
After setting up Application Express instance 1, ensure that application IDs are between 100000 and 199999.
begin
apex_instance_admin.set_parameter('APPLICATION_ID_MIN', 100000);
apex_instance_admin.set_parameter('APPLICATION_ID_MAX', 199999);
end;
After setting up Application Express instance 2, ensure that application IDs are between 200000 and 299999.
begin
apex_instance_admin.set_parameter('APPLICATION_ID_MIN', 200000);
apex_instance_admin.set_parameter('APPLICATION_ID_MAX', 299999);
end;
Later, the operations team decides that workspace MY_WORKSPACE with ID 1234567890 should be moved from instance 1 to instance 2. The required steps are:
Export the workspace, applications and data on instance 1 (not shown here).
Ensure that no other application on instance 1 can reuse application IDs of this workspace.
begin
apex_instance_admin.reserve_workspace_app_ids(1234567890);
end;
Drop workspace, accompanying data and users on instance 1.
begin
apex_instance_admin.remove_workspace('MY_WORKSPACE');
end;
Import the workspace, applications and data on instance 2 (not shown here).
This procedure revokes the privilege to assign a schema to workspaces.
APEX_INSTANCE_ADMIN.RESTRICT_SCHEMA (
p_schema in varchar2 );
Table 11-19 describes the parameters available for RESTRICT_SCHEMA procedure.
This example revokes the privilege to assign schema HR to workspaces.
begin
apex_instance_admin.restrict_schema(p_schema => 'HR');
commit;
end;
Set the log switch interval for each of the logs maintained by Application Express.
APEX_INSTANCE_ADMIN.SET_LOG_SWITCH_INTERVAL(
p_log_name IN VARCHAR2,
p_log_switch_after_days IN NUMBER );
Table 11-20 describes the parameters available in the SET_LOG_SWITCH_INTERVAL procedure.
Table 11-20 SET_LOG_SWITCH_INTERVAL Parameters
| Parameters | Description |
|---|---|
|
|
Specifies the name of the log. Valid values include |
|
|
This interval must be a positive integer between 1 and 180. |
This example sets the log switch interval for the ACTIVITY log to 30 days.
begin
apex_instance_admin.set_log_switch_interval( p_log_name in 'ACTIVITY', p_log_switch_after_days => 30 );
commit;
end;
The SET_WORKSPACE_PARAMETER procedure sets the designated workspace parameter.
SET_WORKSPACE_PARAMETER(
p_workspace IN VARCHAR2,
p_parameter IN VARCHAR2,
p_value IN VARCHAR2 );
Table 11-21 describes the parameters available in SET_WORKSPACE_PARAMETER procedure.
Table 11-21 SET_WORKSPACE_PARAMETER Parameters
| Parameter | Description |
|---|---|
|
|
The name of the workspace to which you are setting the workspace parameter. |
|
|
The parameter name which overrides the instance parameter value of the same for this workspace. Parameter names include:
|
|
|
The parameter value. |
The following example demonstrates how to use the set_workspace_parameter procedure to restrict URLs for accessing applications in the HR workspace that have hr.example.com in the hostname or domain name.
BEGIN
apex_instance_admin.set_workspace_parameter (
p_workspace => 'HR',
p_parameter => 'ALLOW_HOSTNAMES' ));
p_value => 'hr.example.com' );
END;
The SET_PARAMETER procedure sets a parameter used in administering a runtime environment. You must issue a commit for the parameter change to take affect.
APEX_INSTANCE_ADMIN.SET_PARAMETER(
p_parameter IN VARCHAR2,
p_value IN VARCHAR2 DEFAULT 'N');
Table 11-22 describes the parameters available in the SET_PARAMETER procedure.
Table 11-22 SET_PARAMETER Parameters
| Parameter | Description |
|---|---|
|
|
The instance parameter to be set. |
|
|
The value of the parameter. |
The following example demonstrates how to use the SET_PARAMETER procedure to set the SMTP_HOST_ADDRESS parameter for an Oracle Application Express instance.
BEGIN
APEX_INSTANCE_ADMIN.SET_PARAMETER('SMTP_HOST_ADDRESS', 'mail.example.com');
COMMIT;
END;
The SET_WORKSPACE_CONSUMER_GROUP procedure sets a Resource Manager Consumer Group to a workspace.
set_workspace_consumer_group(
p_workspace in varchar2,
p_rm_consumer_group in varchar2 );
Table 11-23 describes the parameters available for the SET_WORKSPACE_CONSUMER_GROUP procedure.
Table 11-23 SET_WORKSPACE_CONSUMER_GROUP Parameters
| Parameters | Description |
|---|---|
|
p_workspace |
This is the name of the workspace for which the resource consumer group is to be set. |
|
p_rm_consumer_group |
The parameter If the value of |
The following example sets the workspace to the Resource Manager consumer group "CUSTOM_GROUP1":
begin
apex_instance_admin.set_workspace_consumer_group(
p_workspace => 'MY_WORKSPACE',
p_rm_consumer_group => 'CUSTOM_GROUP1' );
commit;
end;
/
The TRUNCATE_LOG procedure truncates the log entries specified by the input parameter.
APEX_INSTANCE_ADMIN.TRUNCATE_LOG(
p_log IN VARCHAR2);
Table 11-24 describes the parameters available in the TRUNCATE_LOG procedure.
Table 11-24 TRUNCATE_LOG Parameters
| Parameter | Description |
|---|---|
|
|
This parameter can have one of the following values:
|
The following example demonstrates how to use the TRUNCATE_LOG procedure to remove all log entries that record access to Application Express application pages.
BEGIN
APEX_INSTANCE_ADMIN.TRUNCATE_LOG('ACTIVITY');
END;
This procedure re-grants the privilege to assign a schema to workspaces, if it has been revoked before.
APEX_INSTANCE_ADMIN.UNRESTRICT_SCHEMA (
p_schema in varchar2 );
Table 11-25 describes the parameters available for UNRESTRICT_SCHEMA procedure.
This example re-grants the privilege to assign schema HR to workspaces.
begin
apex_instance_admin.unrestrict_schema(p_schema => 'HR');
commit;
end;