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

Similar Messages

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

Which Analytic Workspace Manager version should I use?

hi
Right now I am using DB 9.2.0.8 with OLAP Analytic Workspace and OLAP Catalog. Then which version of AWM should I use if I would like to create some demo cube on the instance?
this one?
http://otn.oracle.com/software/htdocs/devlic.html?http://download.oracle.com/otn/java/olap/awm920.zip
Thanks,
Scott

I recommend you check out Werner Puschitz's site, as it's the best source of information for installing Oracle on Redhat.
Cheers, APC

Workspace Manager and HTML DB

Hi Folks,
I was wondering if an HTML DB application can take advantage of
Workspace Manager features, I mean, work with versions inside the database.
The idea is, validate the user login and redirect it to an specific workspace ("version") of the database. Thus, I can control the data inserted by each application user, validated it and then promote it to the live database.
TIA,
Luis Paolini

Hi,
Yes you should be able to do this. The versioning of the table will be transparent to html db. When a table is versioned, the original table is renamed, and a view is created in its place with the original name. Any sql statements running against the original table, will also be able to be run against this new view.
The creation, merging, refreshing, etc of workspaces would need be handled in the same way as any other pl/sql statement being executed by html db.
You would also be able to create a logon trigger, which based on the user logging in, would be able to place the user in an appropriate workspace.
Regards,
Ben

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 and Streams

I wanted to know if workspace manager support streams.
If it supports, can Advanced replication and workspace manager co-exist in a database?
We currently have advanced replication between 2 database with workspace manager installed. The tables are version enabled and replicated. We are adding a new database that is going to use Streams for data movement instead of advanced replication. I would like to know if they can co-exist?
Thanks.

Hi,
There are a number of different modes in collecting data when using Streams. If the LCR records are being created using the redo log, then you would need to specify the LT table when adding support. Otherwise, if a custom application was creating its own LCRs (for example, via triggers) it would not have to use the LT table, but could create the records based on the column values in the trigger.
Also, I should note that it would not really be feasible to replicate the versioned tables completely using streams on top of Workspace Manager. The types of operations that I was referring to that could be performed would be moving data into a non-versioned table. For example, creating a rule so that only specified rows or a particular workspace are streamed into a table at a different database. The metadata would also need to be removed from the record, which would only be useful in a versioned environment. Aside, from these types of activities, advanced replication would need to be used.
Regards,
Ben

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 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 :-)

Analytic Workspace Manager 9.2.0.4

Hi
When I attempt to create a workspace in Analytic Workspace Manager an error message is displayed saying that the database I am using is not a 9.2.0.2 compatible database and the DBMS_AWM package cannot be found.
I have, however, patched my database to 9.2.0.5. Is Analytic Workspace Manager version 9.0.4 incompatible with Oracle DB version 9.2.0.5?
My environment setup is as follows:
Analytic Workspace Manager (9.2.0.4)
Oracle DB 9i Rel 2 (9.2.0.5)
Windows XP Professional SP 2.
Thanks
Ryan

AWM 9.2.0.4.1 is forward compatible on the 9.2 code stream. It works with the current 9.2.0.5.0 and 9.2.0.6 patch sets. My guess is that the Post Installation steps for the 9.2.0.5.0 patch set were not performed. For example, did the catpatch.sql script run? A lot of people overlook this required step in the readme.
In order to check to see if your patch set was installed correctly, perform the following query:
SQL> select comp_name, version, status from dba_registry;
You should see 9.2.0.5 and VALID for the OLAP components.

Does Analytic Workspace Manager 11.2.0.3.0A work with oracle database 12c?

hello,
i would like to know if AWM 11.2.0.3.0A works against with oracle database 12c in pdb mode or not .
regards
jm

I have attempted to connect 11g versions of AWM to 12c and get this error:
'This version of Analytic Workspace Manager is incompatible with the database instance. The Analytic Workspace Manager version is 11.2.0.3.0 and the database compatible version is 12.1.0.0.0'
So unfortunately it is not compatible, and there is currently no AWM for 12c
I also contacted Oracle support and they wont give me any information about a release date or any information on the xml template specification for 12c.
I guess we will just have to wait till they release a version of AWM that supports 12c...
Laszlo

Analytic Workspace Manager 11.2.0.3.0a and Oracle11g 11.2.0.4

Hello!
I'm trying to connect from Analytic Workspace Manager, version 11.2.0.3.0a (latest one), to Oracle server ver. 11.2.0.4. Connection fails with following message "This version of Analytic Workspace Manager is incompatible with the database instance.". Is there a way to make this work? The solution I'm aware of is to downgrade a server. Maybe someone knows other solutions?
Best regards
Bart

hello bart,
try with oracle client 12C Oracle Database 12c Release 1 for Microsoft Windows (x64)
Oracle client 12C contains awm 12C
regards
jean marc

BOBJ Metadata Management Version

Hello,
Is there BOBJ Metadata Management Version 3.1 available? I can only see BOBJ Metadata Management Version 3.0 in the service marketplace.
Regaards

Jørn Erik,
I just double checked about compatibility :
BOMM 12.0 FP1 (BOMM v12.0.0.1) supports BOE XI 3.1.
BOMM 12.0 (BOMM v12.0.0.0) does not support BOE XI 3.1.
So if you use the BOMM 12.0 FP1 version, you should not run not issues. If this is the case (fatal error) we should investigate this. Please open a case with support so that we can get the details.
Thanks,
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

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 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!

Can Designer 9i generate Workspace Manager versioned tables?

Similar Messages

Maybe you are looking for