Workspace manager vs. shadow tables

Hi,
I have the requirement to track any changes (insert/update/delete) on db tables.
At the end the user should be able to view the change history of records in the GUI.
The two possible methods are (in my opinion):
a) workspace manger
b) manage shadow tables manually (with triggers)
Has anyone experience with workspace manager for this use case?
What are the pros and contras of the two methods?
Database is 10gR2
regards
Peter

We are using OWB to create OLAP because you have your metadata properly defined in the design repository of OWB from where you can deploy to different databases and schemas. We are also using OWB to create tables and other relational objects instead of using SQL Developer or Toad to do so.
Nevertheless there are some restrictions when using OWB: You cannot create programs with OWB (e.g. for limiting access to certain objects), not all aggregation operators are supported (e.g. the weighted aggregation operators like WSUM are not supported by OWB), you cannot create models, ...
If you come to these restrictions you could write "after-deployment scripts", i.e. you deploy your dimensions and cubes from OWB and let the scripts do what you could not model with OWB.
Hope this helps!

Similar Messages

Using Workspace Manager on Object tables

Is it possible to implement WM on object tables? I have tried to enable but with no success. See test below where I try to version enable an object table 'SAS_INSTANCE' in schema TEST.
TEST ==========>
Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.5.0 - Production
SQL> EXEC DBMS_WM.EnableVersioning('TEST.SAS_INSTANCE');
BEGIN DBMS_WM.EnableVersioning('TEST.SAS_INSTANCE'); END;
ERROR at line 1:
ORA-20129: table 'TEST.SAS_INSTANCE' does not exist
ORA-06512: at "SYS.WM_ERROR", line 288
ORA-06512: at "SYS.WM_ERROR", line 305
ORA-06512: at "SYS.LT", line 585
ORA-06512: at "SYS.LT", line 8031
ORA-06512: at line 1
<=========== END TEST
Regards
Mats Jansson

Hi Mats,
Workspace Manager does not yet support version enabling of object tables. We will fix WM to raise a better error message.
Thanks,
Ram

Workspace Manager and APEX

I was experimenting with using workspace manager (via DBMS_WM) to version a set of tables. Does everything I want, easily and quickly.
However, when I update versioned objects in APEX, and then look at the HIST table, the user name is APEXPUBLIC_USER.
I understand why this is, but does anyone know of any means of overriding the user saved in the _HIST table, using the APEX user instead.
I had a look at the IOT on the BASE object, but didnt see where it inserts into HIST.
Any help greatly appreciated.
Thanks, Rob

Hi Robert,
some time ago I created a german how to document on Workspace Manager and APEX - you'll find it here.
http://www.oracle.com/webfolder/technetwork/de/community/apex/tipps/wm/index.html
Be careful - in the following text a "workspace" is not an APEX workspace but a DBMS_WM workspace.
The "_HIST table" is not a table but a view. When version-enabling a table Workspace Manager renames the table, adds columns
for the versioning information and creates some views. The most important view is the view which "replaces" the original table. The
"_HIST" view is another view.
Workspace manager also creates an INSTEAD OF trigger which "catches" the DML done on the view (which now has the name
of the original object). That DML is being enriched with User and timestamp information and then placed into the original table
(which now has another name).
The user information is there because Workspace manager allows to grant privileges on "workspaces" to other users. So you ...
* first version-enable a table
* create a new workspace (CHANGES_1)
* do some DML
* grant access on your workspace to the other user say: HUGO
Now you and HUGO can access the workspace CHANGES_1 and review your DML. All other users can only see the
table status before your changes. So as long as you don't access the version enabled object from different database
schemas (i.e. different parsing schemas) and you don't use the DBMS_WM.GRANT.... procedures you don't have to care
about the APEX_PUBLIC_USER information in the HIST view. You can live with the APEXPUBLIC_USER information.
Does that help ...?
Best regards
-Carsten

Upgrading oracle workspace manager

hi,
I have upgraded recently 9.2.0.1 database to 9.2.0.6 db by applying patchset.
all the components have been brought up to 9.2.0.6 except
Oracle Workspace Manager
9.2.0.1.0
(select comp_name,version from dba_registry) this query returns all the components status valid with 9.2.0.6.0 version).
can Anyone tell me what I have to do to bring up oracle workspace manager to 9.2.0.6.0

Hi,
A full database import/export containing Workspace Manager version enabled tables and/or workspaces is only supported when both the source and target are the same version. So, obviously, you would not be able to export from 9.0.1.3 and import directly into a later version. Typically, this could only be accomplished via upgrade without using import/export as you described.
However, you should be able to install the 9.0.1.3 Workspace manager code on the target database, do the import, and then after that completes to upgrade Workspace Manager to the original version.
Regards,
Ben

Workspace manager to journal application tables?

Hi,
I know nothing about WSM. We need to provide a full audit
trail (journalling) for certain tables in a new application (Oracle 9i, Appl server 10g).
We were planning to generate this using API generator in Designer.
Question is - could WSM do this less painfully?.
If historical data is stored, can user reports be defined against it (Users may need to run queries against changes made to application data).
We would be grateful for any info.
Steve Edmeades
Cancer Research UK

Hi Steve,
I'm the Product Manager. Feel free to contact me directly at [email protected] to discuss your auditing requirements.
In general, yes, Workspace Manager can maintain a history of changes to a table.
It can make a timestamped copy of a row every time a change to it is committed. The GotoDate command allows the user to set session context to a particular point in time to see the database (including the changed rows) as it was at that time.
DML doesn't need to change (unless hints are needed to optimize performance). All historical copies of the rows are kept in the same table as the original row.
Best Regards,
Bill

Oracle11gR2 Workspace Manager and table consistency after merge

Hi folks,
     I'm working with Oracle Workspace Manager in order to get data inserted and validated into workpaces before they become available to the LIVE workspace.
     Doing some tests I found a problem about data consistency after I merge the data from a child workspace to the parent workspace.
     To be able to explain and reproduce the problem I create a simple test case:
--Create table TB_LINK
create table TB_LINK
CD_LINK NUMBER not null,
DS_LINK VARCHAR2(30)
--Create primary key
alter table TB_LINK add primary key (CD_LINK);
--Create table TB_GUD
create table TB_GUD
CD_GUD NUMBER not null,
DS_GUD VARCHAR2(30),
CD_LINK NUMBER
-- Create primary key
alter table TB_GUD add primary key (CD_GUD);
-- Create foreign key
alter table TB_GUD
add constraint FK_TB_LINK foreign key (CD_LINK)
references TB_LINK (CD_LINK);
-- Create sequences
create sequence SEQ_TB_GUD
minvalue 1
maxvalue 9999999999999999999999999999
start with 1
increment by 1
nocache;
create sequence SEQ_TB_LINK
minvalue 1
maxvalue 9999999999999999999999999999
start with 1
increment by 1
nocache;
--Create Triggers
create or replace trigger "INS_TB_GUD" before insert on TB_GUD for each row
Begin
select SEQ_TB_GUD.nextval into :new.CD_GUD from dual;
end;
create or replace trigger "INS_TB_LINK" before insert on TB_LINK for each row
Begin
select SEQ_TB_LINK.nextval into :new.CD_LINK from dual;
end;
--Enable version TB_LINK and TB_GUD
EXECUTE DBMS_WM.EnableVersioning('TB_GUD','VIEW_WO_OVERWRITE',FALSE,FALSE,'UNLIMITED');
EXECUTE DBMS_WM.EnableVersioning('TB_LINK','VIEW_WO_OVERWRITE',FALSE,FALSE,'UNLIMITED');
--Create a workspace
EXECUTE DBMS_WM.CreateWorkspace ('TEST_WKS');
--Goto workspace TEST_WKS
EXECUTE dbms_wm.gotoworkspace('TEST_WKS');
--Insert data into TB_LINK and TB_GUD
INSERT INTO TB_LINK(DS_LINK) VALUES ('DS1');
INSERT INTO TB_LINK(DS_LINK) VALUES ('DS2');
INSERT INTO TB_LINK(DS_LINK) VALUES ('DS3');
INSERT INTO TB_LINK(DS_LINK) VALUES ('DS4');
COMMIT;
INSERT INTO TB_GUD(DS_GUD,CD_LINK) VALUES ('GUD1',1);
INSERT INTO TB_GUD(DS_GUD,CD_LINK) VALUES ('GUD2',2);
INSERT INTO TB_GUD(DS_GUD,CD_LINK) VALUES ('GUD3',3);
INSERT INTO TB_GUD(DS_GUD,CD_LINK) VALUES ('GUD4',4);
COMMIT;
--Checking keys
select * from tb_link;
   CD_LINK      DS_LINK
         1           DS1
         2           DS2
         3           DS3
         4           DS4
select * from tb_gud;
   CD_GUD      DS_GUD     CD_LINK
         1           GUD1              1
         2           GUD2              2
         3           GUD3              3
         4           GUD4              4
--Merge Workspace
EXECUTE DBMS_WM.MergeWorkspace ('TEST_WKS');
--Checking keys
EXECUTE dbms_wm.gotoworkspace('LIVE');
select * from tb_link;
   CD_LINK      DS_LINK
         5           DS4
         6           DS3
         7           DS1
         8           DS2
We can see that the CD_LINK got new values after merge and that was not expected.
select * from tb_gud;
   CD_GUD      DS_GUD                  CD_LINK
         6           GUD3                       3
         7           GUD1                       1
         8           GUD2                       2
         5           GUD4                       4
We can see that the CD_GUD got new values after merge and that was not expected.
Now, the values for the CD_LINK column does not have corresponding records at the TB_LINK table, as the foreign key does not exist anymore.
Could you please help me understand what is going on?
Thanks,
Luis

Hi Luis,
The reason for the difference is that the trigger is being run during the MergeWorkspace operation. The inserts into the child workspace(TEST_WKS) translates into an insert into the LIVE workspace during merge as the rows do not yet exist. As a result, the trigger is fired and the sequence is evaluated. Ideally, we should not allow the PK to be modified by a sequence in this case.
You have 2 options:
(1) Check for :new.CD_GUD being null prior to using the sequence. Any dml coming from a merge/refresh operation will have a non-null value.
(2) Turn off the trigger during dbms_wm procedures. This can be done using dbms_wm.SetTriggerEvents. I would assume you would only want this trigger being run for DML events.
Let me know if you have any questions.
Regards,
Ben

Can Designer 9i generate Workspace Manager versioned tables?

All,
I am exploring the use of the Oracle 9i feature Workspace Manager.
Can Designer 9i generate versioned tables for a Workspace Manager enabled instance. I know that the tables could be generated to scripts and then edited to properly alter versioned tables. However manually editing each script is not a long term solution. I have read through the application help, newsgroups, and this discussion group and did not find any information.
I welcome any input you have to offer,
Doug

Hi Steve,
I'm the Product Manager. Feel free to contact me directly at [email protected] to discuss your auditing requirements.
In general, yes, Workspace Manager can maintain a history of changes to a table.
It can make a timestamped copy of a row every time a change to it is committed. The GotoDate command allows the user to set session context to a particular point in time to see the database (including the changed rows) as it was at that time.
DML doesn't need to change (unless hints are needed to optimize performance). All historical copies of the rows are kept in the same table as the original row.
Best Regards,
Bill

Upgrading from 9.0.1.3 to 11.2.0.4 with Oracle Workspace Manager

Our client has a (very old) 9.0.1.3 database on Windows 2000
This database (and other products – but that’s not the main concern right now) needs to be upgraded to 11.2.0.4 in Windows2008R2 (64 bit).
A complicating factor might be the use of Oracle Workspace Manager – a lot of tables are Workspace Managed.
We can do it the long way, by upgrading it via 9.1.0.4, 10.2.0.1, 10.2.0.4 -> Export and then, on the new environment, import on 10.2.0.4 en subsequently upgrade it to 10.2.0.5 and then 11.2 (and maybe some more patching afterwards).
But that takes way too long (downtime).
So would it be possible to do it the “easy way”:
Full Database Export of 9.0.1.3, import it into a brand new empty 11.2.0.4 and then upgrade Workspace Manager to 11.2 as well?
Or should we upgrade OWM to 11.2 in the old environment - and is that possible at all?
(FYI: Snippet from the OWM manuals : Workspace Manager supports the import and export of version-enabled tables in one of the following two ways: a full database import and export, and a workspace-level import and export through Workspace Manager procedures. No other export modes, such as schema, table, or partition level, are currently supported).
(On purpose cross-posted in the "Workspace Manager" Forum : Upgrading from 9.0.1.3 to 11.2.0.4 with Oracle Workspace Manager

The database is not that big (in fact there are two, both around 130Gb).
Affordable downtime is one weekend. The long way (with all patching and upgrading) takes around 100 hours...
We did raise an SR, but the answer was ... take the long way home ;-)
(But, FYI, I didn't raise the SR, so I don't know what question has been asked... If the original question was "how to upgrade", you get the official statement. If you don't ask for other options, you don't get them - so I ask it here...)
And I've seen that presentation... Thanks anyway.

Shadow tables in owb 10.2.0.2.8

Hi all,
I have a problem with creating shadow tables in patch set 10.2.0.2.8. If I recalled correctly, I did manage to create them with no issues in another version of owb: 10.2.0.3. Can I just verify that this current patchset 10.2.0.2.8 does not support the creation of shadow tables automatiicaly? I looked at the script generated and I didnt see any "logerrors into error_table..." statement.

Hi
Prior to OWB 10.2.0.3 you can use the DML error logging features only for the mappings which runs
in ROW based mode.
But from OWB 10.2.0.3 onwards DML error logging features can be used for SET based mappings also.
Cheers
Nawneet

Triggers in Workspace Manager

I've got some problems with the workspace manager and triggers in 10g:
If you have a trigger defined on a table and you version this table, ORACLE will create 3 "instead of"-triggers on the view representing the table.
The "content" of the trigger will be created in a wm$ procedure.
My question is: How can I change my trigger without unversioning the table?
As an example, consider the following two tables:
-- Create Data Table
CREATE TABLE MY_TABLE
     X_ID NUMBER(28) NOT NULL,
     V_TEXT VARCHAR2(200),
     V_COMMENT VARCHAR2(4000)
-- The Table's PK
ALTER TABLE MY_TABLE ADD CONSTRAINT PK_MY_TABLE
     PRIMARY KEY (X_ID)
USING INDEX;
-- Create Registry Table
CREATE TABLE MY_REGISTRY_TABLE
     X_ID NUMBER(28) NOT NULL,
     V_OLD_TEXT VARCHAR2(200),
     V_OLD_COMMENT VARCHAR2(4000),
     V_NEW_TEXT VARCHAR2(200),
     V_NEW_COMMENT VARCHAR2(4000),
     D_WHEN DATE NOT NULL
Now, we create a trigger that automatically registers the changes made on MY_TABLE:
-- Create Trigger
CREATE OR REPLACE TRIGGER TR_MY_TABLE
AFTER INSERT OR UPDATE OR DELETE ON MY_TABLE
FOR EACH ROW
BEGIN
     INSERT INTO MY_REGISTRY_TABLE(
          X_ID
          ,V_OLD_TEXT
          ,V_OLD_COMMENT
          ,V_NEW_TEXT
          ,V_NEW_COMMENT
          ,D_WHEN
     VALUES (
          NVL(:old.X_ID, :new.X_ID)
          ,:old.V_TEXT
          ,:old.V_COMMENT
          ,:new.V_TEXT
          ,:new.V_COMMENT
          ,sysdate
END TR_MY_TABLE;
Now, we decide to version MY_TABLE.
exec dbms_wm.enableversioning('MY_TABLE');
This turns MY_TABLE into 2 data tables and a collection of views.
The trigger has changed as well. The original trigger has disappeared, and there are 3 "INSTEAD OF"-triggers on the view MY_TABLE:
OVM_Delete_102
OVM_Insert_102
OVM_Update_102
These three triggers in the end call a system generated procedure:
wm$proc_udt_187
If I try to change this procedure, the system won't let me do that.
So, my question is, how can I change my trigger on MY_TABLE without unversioning the table?

Hi,
The 3 instead of triggers are created regardless of whether the table contained a user defined trigger or not. They are primarily used to implement the DML, but are used for other things as well as you noted. To change the definition of the trigger, you would need to use the Workspace Manager DDL procedure. See section 1.8 of the user guide. Essentially, you execute dbms_wm.beginDDL on the table, update the trigger on the <table_name>LTS table that is created (the trigger will have the original name that you gave it), then execute dbmswm.commitDDL.
Regards,
Ben

Performance of workspace manager

I have created versioned tables in Oracle 9.2. It sits in DEC Unix OS. I have experienced performance degredation after versioning the tables. The largest table has about 20 million rows. Do I need to analyze the base table generated by versioning the tables?
Help!
Ashley

Ashley
Analyzing the base table should definitely help performance. Also, if you think it will help, feel free to send me mail with your phone and we can have a conference call to help you with the performance issues.
regards
Arun Gopalan
Director, Workspace Manager Engg.
Oracle Corporation
[email protected]

Workspace manager performance

Hi
I'm a Java developper trying to act as a DBA so don't fire !
I'm trying to use the workspace manager on a 21M record DB
on Oracle 10g/Windows.
I'm bulkloading using sqlloader into it. The load phase is done
with good performance (or at least it seems to me), in
about 30 minutes, which is consistent to numbers I get when
I load in a non-version enabled table.
When I do the commitbulkloading though, it takes about 55 minutes
to complete. I realized 2 things:
1- it takes quite a lot of time creating and populating the discards table
with the entire content of the original table (!) - which looks like a bug
to me
2- it spends tremendous amount of time doing:
SELECT count(*)
FROM listings_lt t1, listings_lt t2
WHERE t1.listing_id = t2.listing_id
AND t1.delstatus IS NULL
AND t1.version = 0
AND t2.delstatus IS NOT NULL
where listings_id is my PK on the listings_lt table.
I solved 1 by simply creating the discards table before calling commit -
then it does not create or populate it. But 2 puzzles me. I
specified check_for_duplicates=FALSE in the CommitBulkLoading
API but it did not change anything.
Any ideas to speed things up ?
/zog

Hi,
Yes, #1 does indeed look like a bug. The current workaround to this is to create the discards table before calling commitBulkLoading as you indicated. This will be fixed.
The query in #2 is not used to check for duplicates. It is used to determine if all the keys that are being inserted are unique. There is currently no way to avoid this select, as it is needed internally by the commitbulkloading procedure. To increase its performance, I would recommend to analyze the table using dbms_stats before calling commitbulkloading. However, please note that when bulk loading 21M records into an empty table, this query will require a full table scan.
If that does not help, then post the execution plan for the statement. From that I may be able to determine if something else needs to be done.
Regards,
Ben

Creating a DWMQY DIMENSION using Analytic Workspace Manager

Hi everyone,
I need some help creating a "time aware" (DAY, WEEK, MONTH, QUARTER, and YEAR) dimension using Analytic Workspace Manager.
Let me give you some background. I'm coming from a traditional "Oracle Express" OLAP background where all our data is stored in cubes and these are defined, populated and operated on using OLAP DML, there is no SQL or traditional relational tables involved.
I now want to pull data from relational tables into some OLAP cubes and am using Analytic Workspace Manager to do this (maybe this is not the best way?)
Let me explain what I'm trying to achieve. In OLAP worksheet I can type the following DML commands:
DEFINE MY_DAY DIMENSION DAY
MAINTAIN MY_DAY ADD TODAY '01JAN2011'
What this will do is create a "day dimension" and will populate it with values for each and every day between 1st Jan 2011 and today. It will be fully "time aware" and thus you can use date functions such as DAYOF to limit the MY_DAY dimension to all the Fridays etc. Similarly if I define a "month dimension" there will be an automatic implicit relationship between these two dimensions, this relationship and time aware cleverness is built into Oracle.
However, a dimension defined using DML commands (and indeed all objects created using DML language) is not visible in Analytic Workspace Manager (as there is no metadata for them?) and for the life of me I cannot work out how to create such a dimension using AWM. If I create a "Time Dimension" then, as far as I can tell, this is not a proper time dimension but merely a text dimension and I, presume, I have to teach it time awareness.
Can anyone help me? I have no issues creating, and populating cubes from relational tables using Analytic Workspace Manager, the only issue I have is creating a "proper" time aware dimension.
Many thanks in anticipation.
Ian.

When a dimension is of type "TIME" in AWM, then for each member of that dimension, you need END_DATE and TIMESPAN attributes in addition to the key column and description column.
So in your case, if there are 5 levels: DAY->WEEK->MONTH->QTR->YEAR
then you will need atleast 15 columns in your source sql table/view
or 20 columns if you have separate column for description.
For example the columns in your source table/view could be:
DAY_ID,
DAY_DESC,
DAY_END_DATE, (which will be that day's date)
DAY_TIMESPAN, (which will be 1)
WEEK_ID,
WEEK_DESC,
WEEK_END_DATE,
WEEK_TIMESPAN,
MONTH_ID,
MONTH_DESC,
MONTH_END_DATE,
MONTH_TIMESPAN,
QTR_ID,
QTR_DESC,
QTR_END_DATE,
QTR_TIMESPAN,
YEAR_ID,
YEAR_DESC,
YEAR_END_DATE,
YEAR_TIMESPAN
Just "map" this table/view to the 5-level time dimension in AWM.
NOTE that behind-the-scenes lot of useful structures are automatically defined to support time-series measures,
and there are lot of calculation templates available also.
Since you came from Express background, I have to say that try to use new OLAP Expression Syntax when creating calculated measures instead of OLAP DML.
Its very rare these days that we need OLAP DML.
Edited by: Nasar on Nov 22, 2012 12:11 PM

Import Log shows Incompatible version of Workspace Manager Installed

Hi,
I did an export of my DB using oracle 10.2.0.3 in Windows 2003 R2, I am trying to import the DB in Oracle 10.2.0.4 on Windows 2008 Server.
Question 1
I am getting the following error message
IMP-00003: ORACLE error 20000 encountered
ORA-20000: Incompatible version of Workspace Manager Installed
Is it safe to continue the import? Do I need to do any post import configuration to solve the above error message.
Question 2
I have few notes in the log which states, is it because of the above error message or can I ignore these notes
Note: table contains ROWID column, values may be obsolete 0 rows imported
Thank you

Pl see if these MOS Docs help
730373.1 - ORA-39083 ORA-20000 Incompatible Version of Workspace Manager Installed
743097.1 - IMP-00017 ORA-20000 Importing older version of OWM into a higher version
HTH
Srini

Workspace Manager and tabular forms

Does anyone know whether it is possible to use Workspace Manager with tabular forms using APEX's multi row processes?
I tried creating a process that runs before the multi-row processes that uses gotoWorkspace() to switch to a different workspace and another process afterwards that switches back to the LIVE workspace. However, the changes go into the LIVE workspace rather than the desired workspace.
Rodney

Turns out my application did indeed need to be debugged. I had an explicit condition written to limit the process to certain buttons, but I also managed to add an unintended constraint that the process only run when the Add button was used. The result was that the process ran, creating a workspace, when one added a row, but didn't switch back to that workspace when one saved the new row.
Sorry for the false alarm.
At least I can confirm for anyone considering this option that APEX does work with Workspace Manager as long as you can enable the versioning on the tables through another means.
Rodney

Workspace manager vs. shadow tables

Similar Messages

Maybe you are looking for