3.15.3 Deleting a Workspace
Deleting a workspace does not remove any of the associated database objects. To remove the associated schemas, a database administrator (DBA) must use a standard database administration tool, such as Oracle Enterprise Manager or SQL*Plus.
- Identifying and Deleting Inactive Workspaces
Learn how to identify and delete inactive workspaces. - Deleting Workspaces in a Full Development Environment
Delete workspaces in a full development environment. - Deleting Workspaces in a Runtime Development Environment
Delete workspaces in a runtime development environment.
See Also:
"Viewing the Workspace Details Report" and "Creating Workspaces in Administration Services"
Parent topic: Managing Existing Workspaces
3.15.3.1 Identifying and Deleting Inactive Workspaces
Learn how to identify and delete inactive workspaces.
- How to Identify Inactive Workspaces
- Identifying Inactive Workspaces By Checking Recent Updates
- Viewing Workspaces with Only a Sample Application
- Removing the Resources Associated with Inactive Workspaces
- Deleting Inactive Workspaces
Parent topic: Deleting a Workspace
3.15.3.1.1 How to Identify Inactive Workspaces
If you are managing a large hosted Oracle Application Express instance, manually deleting inactive workspaces can free up resources for other users. The process of manually deleting inactive workspaces consists of the following steps:
-
Step 1: Identify inactive workspaces. See "Identifying Inactive Workspaces By Checking Recent Updates" and "Viewing Workspaces with Only a Sample Application."
-
Step 2: Remove the resources (that is, the database schemas, tablespaces, and data files) associated with each inactive workspace. See "Removing the Resources Associated with Inactive Workspaces."
-
Step 3: Drop the inactive workspaces from Oracle Application Express. See "Deleting Inactive Workspaces."
Tip:
To systematically purge inactive workspaces you must configure Workspace Purge settings. See "Purging Inactive Workspaces."
Parent topic: Identifying and Deleting Inactive Workspaces
3.15.3.1.2 Identifying Inactive Workspaces By Checking Recent Updates
The first step in determining if a workspace is inactive is to establish some basic rules. A common approach is to base the rules on the Oracle Application Express activity records found in the current Application Express engine schema.
The following DDL (data definition language) creates a table of all workspaces requested before June 28, 2004 but that have been inactive since June 10, 2004. In this example, inactivity is determined by checking a key within the Application Express engine schema for the most recent updates by each workspace.
ALTER SESSION SET CURRENT_SCHEMA = APEX_18100; CREATE TABLE ws_to_purge AS SELECT c.security_group_id, c.company_name, c.admin_email, c.request_date, SYSDATE last_updated_on, 'Y' ok_to_delete FROM wwv_flow_provision_company c WHERE c.request_date <= to_date('20040628','YYYYMMDD') AND ( not exists (SELECT NULL /* Activity Log */ FROM wwv_flow_activity_log l WHERE l.security_group_id = c.security_group_id AND l.time_stamp > to_date('20040610','YYYYMMDD')) ) AND NOT EXISTS (SELECT NULL /* workspace applications */ FROM wwv_flows f WHERE f.security_group_id = c.security_group_id AND f.last_updated_on > to_date('20040610','YYYYMMDD')) AND NOT EXISTS (SELECT NULL /* Pages */ FROM wwv_flow_steps s WHERE s.security_group_id = c.security_group_id AND s.last_updated_on > to_date('20040610','YYYYMMDD')) AND NOT EXISTS (SELECT NULL /* Regions */ FROM wwv_flow_page_plugs p WHERE p.security_group_id = c.security_group_id AND p.last_updated_on > to_date('20040610','YYYYMMDD')) AND NOT EXISTS (SELECT NULL /* Items */ FROM wwv_flow_step_items i WHERE i.security_group_id = c.security_group_id AND i.last_updated_on > to_date('20040610','YYYYMMDD')) AND NOT EXISTS (SELECT NULL /* Templates */ FROM wwv_flow_templates t WHERE t.security_group_id = c.security_group_id AND t.last_updated_on > to_date('20040610','YYYYMMDD')) AND NOT EXISTS (SELECT NULL /* Files uploaded */ FROM wwv_flow_file_objects$ o WHERE o.security_group_id = c.security_group_id AND o.created_on > to_date('20040610','YYYYMMDD')) AND NOT EXISTS (SELECT NULL /* SQL Workshop history */ FROM wwv_flow_sw_sql_cmds s WHERE s.security_group_id = c.security_group_id AND s.created_on > to_date('20040610','YYYYMMDD'));
Parent topic: Identifying and Deleting Inactive Workspaces
3.15.3.1.3 Viewing Workspaces with Only a Sample Application
Another way to identify potentially inactive workspaces is to view the Workspaces with Only Sample Application report.
To view a report or workspaces only containing only a sample application:
Parent topic: Identifying and Deleting Inactive Workspaces
3.15.3.1.4 Removing the Resources Associated with Inactive Workspaces
After you have identified inactive workspaces in a single table, the next step is to remove them.
Note:
Before removing the schemas, tablespaces, or data files associated with inactive workspaces, make sure these resources are not being used in any other workspace or application.
To remove the resources associated with inactive workspaces:
Parent topic: Identifying and Deleting Inactive Workspaces
3.15.3.1.5 Deleting Inactive Workspaces
Once you remove the resources associated with an inactive workspace, you can delete the workspace. You can delete inactive workspaces manually using the Oracle Application Express Administration Services application. Or, you can delete them programmatically as shown in the following PL/SQL example.
BEGIN FOR c1 IN (SELECT security_group_id FROM ws_to_purge WHERE ok_to_delete = 'Y') LOOP WWV_FLOW_PROVISIONING.TERMINATE_SERVICE_BY_SGID(c1.security_group_id); END LOOP; END;
Parent topic: Identifying and Deleting Inactive Workspaces
3.15.3.2 Deleting Workspaces in a Full Development Environment
Delete workspaces in a full development environment.
To delete a workspace:
Parent topic: Deleting a Workspace
3.15.3.3 Deleting Workspaces in a Runtime Development Environment
Delete workspaces in a runtime development environment.
To delete a workspace in a runtime development environment:
Parent topic: Deleting a Workspace