Note:

• This tutorial requires access to Oracle Cloud. To sign up for a free account, see Get started with Oracle Cloud Infrastructure Free Tier.
• It uses example values for Oracle Cloud Infrastructure credentials, tenancy, and compartments. When completing your lab, substitute these values with ones specific to your cloud environment.

Use Oracle Workspace Manager on Autonomous Database

Introduction

Oracle Workspace Manager provides an infrastructure that enables applications to create workspaces and group different versions of table row values in different workspaces. Oracle Workspace Manager is a feature of Oracle Database that provides the infrastructure for developers to create workspaces to maintain multiple versions of a set of tables. Developers can work on a copy of the data within a workspace that is visible only to them and not visible to other users of the database accessing production data. Changes they make to the data are isolated to the workspace. When a developer has finished working on data in a workspace, they can merge it with production data.

About Using Oracle Workspace Manager on Autonomous Database

Use Oracle Workspace Manager to version-enable one or more user tables in the database. When a table is version-enabled, all rows in the table can support multiple versions of the data.

Applications that can benefit from Oracle Workspace Manager typically do one or more of the following operations:

• Manage a collection of updates and insertions as a unit before incorporating them into production data.
• Support a collaborative development effort.
• Use a common data set to create multiple scenarios for what-if analyses or multiple editions of data for publication.
• Keep a history of changes to data.

Objectives

Outline the steps for using Oracle Workspace Manager on Autonomous Database to connect and execute.

Prerequisites

• Connect to autonomous database.
• Check the view dba_cloud_config.
• Enable Oracle Workspace Manager on Autonomous Database.

Task 1: Enable Oracle Workspace Manager on Autonomous Database

Oracle Workspace Manager must be enabled to be used on Autonomous Database. You can migrate existing data that has enabled Oracle Workspace Manager.

1. Check the dba_cloud_config view whether Oracle Workspace Manager is enabled.

   SQL> SELECT param_name, param_value FROM dba_cloud_config;
   
   |PARAM_NAME                 | PARAM_VALUE                              |
   | ------------------------- | ---------------------------------------- |
   | latest_timezone_version   | 42                                       |
   | aws_user_arn              | arn:aws:iam::213420752344:user/oraclearn |
   

   

2. As the ADMIN user, run DBMS_CLOUD_ADMIN.ENABLE_FEATURE to enable Oracle Workspace Manager.

   Workspace manager is enabled using the procedure DBMS_CLOUD_ADMIN.ENABLE_FEATURE.

   SQL> BEGIN    DBMS_CLOUD_ADMIN.ENABLE_FEATURE(        feature_name => 'OWM');
     2  end;
     3* /
   
   PL/SQL procedure successfully completed.
   

   

3. Query dba_cloud_config to verify that Oracle Workspace Manager is enabled.

   SQL> SELECT param_name, param_value FROM dba_cloud_config WHERE       LOWER(param_name) = 'owm';
   
   | PARAM_NAME   | PARAM_VALUE |
   | ------------ | ----------- |
   | owm          | enabled     |
   

   

   

4. (Optional) If you have existing data using Oracle Workspace Manager on another database that you want to migrate to Autonomous Database, Oracle Workspace Manager provides import and export procedures that enable you to migrate the data.

   For additional information, See Export Schemas and Import Schemas.

Task 2: Disable Oracle Workspace Manager on Autonomous Database (If requires)

Use the following steps to disable Oracle Workspace Manager on Autonomous Database.

1. As the ADMIN user, run DBMS_CLOUD_ADMIN.DISABLE_FEATURE to disable Oracle Workspace Manager.

   Workspace manager is disabled using the procedure DBMS_CLOUD_ADMIN. DISABLE_FEATURE.

   Disable Oracle Workspace Manage :

   SQL> BEGIN    DBMS_CLOUD_ADMIN.DISABLE_FEATURE(        feature_name => 'OWM');
     2  end;
     3* /
   
   PL/SQL procedure successfully completed.
   

   

2. Query dba_cloud_config to verify that Oracle Workspace Manager is disabled.

   SQL> SELECT param_name, param_value FROM dba_cloud_config WHERE       LOWER(param_name) = 'owm';
   
   no rows selected
   

   

Related Links

• Use Oracle Workspace Manager on Autonomous Database

Acknowledgments

• Author - Aditya Kumar Srivastawa (Principal Cloud Architect)

More Learning Resources

Explore other labs on docs.oracle.com/learn or access more free learning content on the Oracle Learning YouTube channel. Additionally, visit education.oracle.com/learning-explorer to become an Oracle Learning Explorer.

For product documentation, visit Oracle Help Center.

---

Title and Copyright Information

Use Oracle Workspace Manager on Autonomous Database

F87957-01

October 2023

Copyright © 2023, Oracle and/or its affiliates.