Oracle Workspace Manager Component Description

 

1. Workspace Manager Component Description

 

Before the description, we first use the following SQL statement to check the components in the database:

SQL> Col comp_id for A15

SQL> Col version for A15

SQL> Col comp_name for A30

SQL> select comp_id, comp_name, versionfrom dba_registry;

 

Comp_id comp_name version

------------------------------------------------------------

XDB Oracle XML database 11.2.0.3.0

Amd olap catalog 11.2.0.3.0

Em Oracle Enterprise Manager 11.2.0.3.0

SDO spatial 11.2.0.3.0

Ordim Oracle multimedia 11.2.0.3.0

Context Oracle Text 11.2.0.3.0

ODM Oracle Data Mining 11.2.0.3.0

Exf Oracle Expression Filter 11.2.0.3.0

RUL Oracle Rules Manager 11.2.0.3.0

Owm Oracle Workspace Manager 11.2.0.3.0

Catalog Oracle Database catalog views 11.2.0.3.0

 

Comp_id comp_name version

------------------------------------------------------------

Catproc Oracle database packages and t11.2.0.3.0

Ypes

 

JavaVM jserver Java Virtual Machine 11.2.0.3.0

XML Oracle xdk 11.2.0.3.0

Catjava Oracle Database Java packages 11.2.0.3.0

Xoq Oracle olap api 11.2.0.3.0

Aps olap analytic workspace 11.2.0.3.0

 

17 rows selected.

 

Mos description:

Oracle 8i/9i/10g/11g component (components) Description

Http://blog.csdn.net/tianlesoftware/article/details/5937382

 

Oracle workspacemanager is a new feature of Oracle 9i that transparently and securely versionsrelational content in place with no changes to application SQL (DML), whilepermitting simultaneous read and write access to the same production data.

-- Oracle Workspace Manager is a new feature of Oracle9i, which makes it possible for applications to transparently and securely store relevant content without having to make any changes to the SQL (DML) of the application, it also allows read and write access to the same production data at the same time.

 

Applications usea pl/SQL stored procedure to set users in a workspace. once in a workspace, changes to data in version-enabled tables (using existing application SQL) Create new row versions (within the same tablespace) that are only visiblewithin the workspace until explicitly merged with production data. or, changescan be rolled back to a specific point in time through the use ofsavepoints.

-- The Application uses the PL/SQL stored procedure to set the user to the workspace. Once you change the data in a version-enabled table in a workspace (using an existing application SQL), a new row version (in the same tablespace) is created ), the new row version is only visible in the workspace until it is explicitly merged into the production data. Or you can use the save point to roll back the changes to the specified time point in time.

 

Users in aworkspace always see a transactionally consistent view of the entire database. this means they see the changes made in their workspace plus the rest of thedata in the database as it existed when their workspace was created or sincetheir workspace was last refreshed.
-- Users in the workspace always see the transaction consistency view of the entire database. This means that they can see the changes that have taken place in their workspace, and other data that already exists in the Database when a workspace is created or the last time the workspace is refreshed.

 

Use oracleenterprise manager or call the Workspace Manager PL/SQL API to version-enabletables and perform workspace operations, including create, Goto workspace, gotodate, merge, refresh, rollback, compare, resolve conflicts and removeworkspace, as well as manage workspace security and locking.

-- Use Oracle Enterprise Manager or call the Workspace Manager PL/SQL API to enable version tagging for tables and perform workspace operations, this includes creating, transferring to workspace, transferring to date, merging, refreshing, rollback, comparison, conflict resolution, and deleting workspace, as well as managing workspace security and locking.

 

Workspacemanager supports Oracle9i, Oracle8i, Oracle Spatial and other Oracle DBMS features, including referential integrity, locking, triggers, import and export.

-- Workspace Manager supports Oracle 9i, 8i, oraclespatial, and other DBMS features, including referential integrity, locking, triggers, import, and export.

 

Owm Component User:

Wmsys: It stores data dictionary for oracleworkspace Manager

 

Version-enabling tables)

The Workspace Manager can version one or more user tables in the database. A versionized unit is a row. If a table can be versioned, all rows in the table can support multiple versions of data. The versionized row is stored in the same table as the source row. All row version insertion, update, and deletion operations (DML) are performed in Oracle short transactions to ensure the integrity of version data. The basic structure of the version is invisible to database users. The Workspace Manager renames a version-based tableTablename_ Lt to implement this version. add columns to the renamed table to store versionized metadata, and use the source table name to create a view of the versionized table, define an instead of trigger for the view to facilitate SQL DML operations. If you no longer need a version-based table, you can make the version-based table invalid.

Official Website description:

Databaseapplication developer's Guide-Workspace Manager, 10g Release 2 (10.2)

 

 

2. Uninstall Workspace Manager

Mos:

Note.263428.1 howto de-install Oracle Workspace Manager

 

Note:

De-installingoracle Workspace Manager will remove any existing workspaces and the associatedmetadata.

Uninstalling Workspace Manager will remove any workspace and associated metadata.

 

The procedure is as follows:

1) Disable versioning on allversion-enabled tables in the database before de-installing Oracle workspacemanager.

 

2) To de-install login to SQL * plusas sysdba, invoke the de-installation script:
SQL> @ $ ORACLE_HOME/rdbms/admin/owmuinst. PLB

The install/upgrade/de-install process is discussed in the README defined in the kit. The readmeis supplied with Workspace Manager patch kits.

 

 

3. Install Workspace Manager

The link to the official document is as follows:

Howto install Workspace Manager with custom databases 11gr1
Installing workspacemanager with custom databases 11gr2

 

Workspacemanager is installed by default in the seed database and in all databasescreated by the database configuration Assistant (dbca ). however, in all otheroracle databases, such as those you create with a customized procedure, youmust install Workspace Manager before you can use its features.

-- By default, Workspace Manager is installed. If owm is not installed during custom installation, you need to install it manually.

 

To install workspacemanager in a custom database, do the following:

(1) At the system command prompt, change the current directory to the directory that contains workspace managerinstallation script and packages, as shown in the following example:

CD <ORACLE_HOME>/rdbms/admin

 

(2) connect as sys to theoracle instance with a command in the following format:

Sqlplus sys

Enter thepassword for the sys account when you are prompted.

 

(3) run the owminst. PLB script:

SQL> @ owminst. PLB

 

(4) Verify the installation ofworkspace manager by entering the following command while connected as anyvalid database user, and ensure that the output is as shown here:

SQL> select dbms_wm.getworkspace fromdual;

 

Getworkspace

----------------------------------------------------------------------------

Live

 

 

4. Other problems:

 

4.1 Workspace Manager version Problems

Note.341353.1 whydoes the Workspace Manager version differ from the current RDBMS patchsetversion

 

In v9.2.x tov10.2.x, the Oracle Workspace Manager updates are not integrated with thegeneric RDBMS patchsets, but are released seperately.

-- In Oracle 9i to 10g, owm updates are not associated with rdbmspatchsets and must be independently updated with owm.

 

You will need toobtain the latest available Workspace Manager patchset from Metalink:

-- To download owm from MOs, follow these steps:

 

Steps to find the patchset:

 

Go to http://support.oracle.com

Patches & updates
Advanced Search
Product or product family: Workspace Manager
Release: 9.2.0.x or 10.1.0.x or 10.2.0.x
Press <go>

Install thehighest available Workspace Manager patchset for your 9.2.0 or 10.1.0 or 10.2.0release. follow the instructions described in the readme.

 

From Oracle 11g onwards, the Oracle Workspace Manager updates are integrated with the generic rdbmspatchsets.

-- Note that after oracle11g, owm updates and rdbmspatchset do not need to be updated separately.

 

4.2 FAQs about Workspace Manager

Note.156963.1 frequentlyasked questions for Oracle Workspace Manager

4.2.1 how does Workspace Manager work?

The workspacemanager API is implemented as PL/SQL packages, automatically installed withoracle9i. using the API or the version enabled tables folder in oracleenterprise manager, one can selectively version-enable some or all tables in anexisting or new database. there can be a hierarchy of workspaces in thedatabase. by default, when a workspace is created, it is created from thetopmost, or live, database workspace.

 

All changes madein a workspace are made by conventional short transactions. creating anexplicit savepoint causes a new version of a row to be created the next timethe row is updated. changes made in one or more workspaces to the sameproduction data are captured automatically as new versions of the data. storageexpansion and row proliferation is minimized by versioning only changed rowsand by placing the new versions in the same tablespace.

 

Conflicts aredetected automatically before changes are merged into the live workspaceand can be resolved by the user with Oracle Enterprise Manager orprogrammatically through the API.

 

 

4.2.2 Summary of Enterprise Manager integration:

While connectedto a database, you will see a folder called workspace management that can beexpanded to see two sub-folders: Version enabled tables and workspaces.

(1) The OEM version enabled tablessub-Folder allows you to view table status and set tables as version-enabled.

(2) The OEM workspaces folderallows you:

1) Create and view workspace hierarchies and attributes, including:

2) Set and view workspace access modes. The user access modes for aworkspace are:

A) no access, is the default

B) read only

C) single writer, allowing allother users to read

D) Workspace operations only, suchas merge and rollback

3) set and view savepoints

A) Implicit savepoint created bythe system when child workspace is created

B) Explain It savepoint created by auser

4) rollback changes since last explicit savepoint

5) Resolve differences between any two workspaces or between twosavepoints in a workspace

6) Refresh an entire workspace, a table, or rows with data from theparent workspace. Refreshing a workspace may not succeed if there are conflicts

7) Merge all changes made in the workspace or changes made to aspecific table.

8) set privileges to access, create, delete, rollback and mergeworkspaces

 

4.2.3 Summary of Workspace Manager metadata views:

Workspacemanager creates and maintains metadata views to hold information that helps tomanage the workspace environment and diagnose problems. These views areread-only to users. Views that span the whole workspace environment are:

(1) user_wm_versioned_tables and all_wm_versioned_tables

(2) user_wm_modified_tables and all_wm_modified_tables

(3) user_workspaces and all_workspaces containinformation on The workspaces User owns or can access

(4) user_workspace_savepoints and all_workspace_savepoints

(5) user_workspace_privs and all_workspace_privs includesall users 'privileges

(6) user_wm_privs includesprivileges the current user has in each Workspace

(7) role_wm_privs

(8) user_wm_locked_tables and all_wm_locked_tables

(9) dba_workspace_users containsuser info for workspaces other than live

(10) user_wm_ric_info and all_wm_ric_info containreferential integrity constraints

(11) user_wm_tab_triggers and all_wm_tab_triggers

(12) all_version_hview is a workspace hierarchy

 

Views created for eachworkspace enabled table are:

(1) Conflict View

(2) Difference View

(3) Lock View

(4) History View

(5) multiworkspace View

 

 

 

 

 

 

Bytes -------------------------------------------------------------------------------------------------------

All rights reserved. reprinted articles are allowed, but source addresses must be indicated by links. Otherwise, the documents will be held legally responsible!

Skype: tianlesoftware

Email: tianlesoftware@gmail.com

Blog: http://www.tianlesoftware.com

WEAVER: http://weibo.com/tianlesoftware

Twitter: http://twitter.com/tianlesoftware

Facebook: http://www.facebook.com/tianlesoftware

LinkedIn: http://cn.linkedin.com/in/tianlesoftware

 

 

------- Add a group to describe the relationship between Oracle tablespace and data files in the remarks section. Otherwise, reject the application ----

Dba1 group: 62697716 (full); dba2 group: 62697977 (full) dba3 group: 62697850 (full)

Super DBA group: 63306533 (full); dba4 group: 83829929 dba5 group: 142216823

Dba6 group: 158654907 dba7 group: 172855474 DBA group: 104207940