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

Similar Messages

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!

Create key mapping using import manager for lookup table FROM EXCEL file

hello,
i would like create key mapping while importing the values via excel file.
the source file containing the key, but how do i map it to the lookup table?
the properties of the table has enable the creation of mapping key. but during the mapping in import manager, i cant find any way to map the key mapping..
eg
lookup table contains:
Material Group
Code
excel file contain
MatGroup1 Code System
Thanks!
Shanti

Hi Shanti,
Assuming you have already defined below listed points
1) Key Mapping "Yes" to your lookup table in MDM Console
2) Created a New Remote System in MDM console
3) proper rights for your account for updating the remote key values in to data manager through import manager.
Your sample file can have Material Group and Code alone which can be exported from Data Manager by File-> Export To -> Excel, if you have data already in Data Manager.
Open your sample file through Import Manager by selecting the remote system for which you want to import the Key mapping.
(Do Not select MDM as Remote System, which do not allows you to maintain key mapping values) and also the file type as Excel
Now select your Soruce and Destination tables, under the destination fields you will be seeing a new field called [Remote Key]
Map you source and destination fields correspondingly and Clone your source field code by right clicking on code in the source hierarchy and map it to Remote Key if you want the code to be in the remote key values.
And in the matching criteria select destination field code as a Matching field and change the default import action to Update NULL fields or UPDATED MAPPED FIELDS as required,
After sucessfull import you can check the Remote Key values in Data Manager.
Hope this helps
Thanks
Sowseel

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

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

Oracle10g with Workspace Manager

Has anyone used Workspace Manager in 10g? I'm trying to draw the line between workspaces and version tables. Can someone please shed some light on this.
Thanks,
Bobby

TopLink does not have a formal integration with Workspace manager but I have worked with at least one customer using them together. For basic version usage you need to ensure you force the same connection to be used and execute the appropriate stored procedures.
I do see an opportunity for a more seamless integration to allow TopLink to automatically invoke the stored procs and to facilitate conflict resolution.
Can you describe how you want to use workspace manager and maybe we can work out an example that meets your needs.
Doug

Workspace-Manager Error-numbers

Hi everybody,
i have an oracle forms-application using Workspace-manager-enabled table. My problem is that i can not handle the WM-errors directly as Exceptions for they are all treated as ORA-06510-exceptions in forms. So i have to go with the error-numbers of the exceptions to cast them to a "meaningful" text. Does anybody know of a list where also the number is listed next to the Exception WM_ERROR_xxx ?
Thanks for your help.

Found the answer by testing:
Raised an DBMS_WM.WM_ERROR_1 and checked sqlcode (-20001) and DBMS_WM.WM_ERROR_282 (-20282) and "guessed" the rest :-)

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 & Slowly Changin Dimension in Data Warehouse

Has anyone used Workspace Manager in a Slowly Changing Dimension to keep history in a Data Warehouse.
What issues have you come across?
What are advantages?
What are disadvantages?
Thanks
Uli

Hi Ben,
thanks for getting back on this and sorry for not updating earlier.
I had a brief scan through the documentation and Workspace Manager seems to be quite powerful. When I was reading through the docs originally I had the idea that this might be useful to reduce coding and improve performance in a Slowly Changing Dimension (type 2) DW scenario. I would hope for a performance improvement in both loading and querying data. So I thought before I get my hands dirty and do some tests I would check with the community to see if this is something that has been done before.
To answer your specific questions: I would like to keep every change. I would not need the primary workspace functionality for merging and version control etc. It would just be to keep history.
Again thanks for your efforts.
Uli

Does Toplink work with Workspace Manager ?

Hi all,
as the subject heading specified, is it possible to use Toplink with Workspace Manager ?
thank you for any response

TopLink does not have a formal integration with Workspace manager but I have worked with at least one customer using them together. For basic version usage you need to ensure you force the same connection to be used and execute the appropriate stored procedures.
I do see an opportunity for a more seamless integration to allow TopLink to automatically invoke the stored procs and to facilitate conflict resolution.
Can you describe how you want to use workspace manager and maybe we can work out an example that meets your needs.
Doug

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

Creating Dimension using template in Analytical workspace manager

Hi,
I am rajan, I am working with Oracle's Analytical workspace manager Release 2.
I am trying to create the dimension using the templates from the file. it throws the following error,
The following errors have occurred when loading contents:
Closed Connection
Note : I am referring the tutorial in the following URL,
http://st-curriculum.oracle.com/obe/db/10g/r2/prod/bidw/awm/awm_otn.htm and also i have downloaded the awm.zip file from the same URL and imported into my desktop.
Right now, I am working based on this tutorial only.
Kindly,help me to resolve this issue.
Thanks
Rajan

Francisco,
Query DBA_REGISTRY to verify the status of "OLAP Analytic Workspace" component.
Also, wait for the script to finish and check the status of the objects then.
Thanks,
Hussein

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

Using workspaces with large tables

Hello
I've got a few large tables (6-10GB+) that will have around 500k new rows added on a daily basis as part of an overnight batch job. No rows are ever updated, only inserted or deleted and then re-inserted. I want to stop the process that adds the new rows from being an overnight batch to being a near real time process i.e. a queue will be populated with requests to rebuild the content of these tables for specific parent ids, and a process will consume those requests throughout the day rather than going through the whole list in one go.
I need to provide views of the data asof a point in time i.e. what was the content of the tables at close of business yesterday, and for this I am considering using workspaces.
I need to keep at least 10 days worth of data and I was planning to partition the table and drop one partition every day. If I use workspaces, I can see that oracle creates a view in place of the original table and creates a versioned table with the LT suffix - this is the table name returned by DBMSMW.GetPhysicalTableName. Would it be considered bad practice to drop partitions from this physical table as I would do with a non version enabled table? If so, what would be the best method for dropping off old data?
Thanks in advance
David

I've just spotted the workspace manager forum, I'll post there. :-)

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

Using Workspace Manager on Object tables

Similar Messages

Maybe you are looking for