Is it possible to version enable schema

hi
is it possible to version enable whole schema?. Because developers runs programs which will update severals tables
which he himself doesnt. I version enable schema, i can revert in case of issues
Regards

Hi,
It is not possible to version enable a set of tables by specifying the name of the schema. However, you should be able to pass all of the tables contained within the schema to dbms_wm.EnableVersioning.
Regards,
Ben

Similar Messages

Data transfer from version enabled schema to non-version enabled schema

Hi,
This is Kumar and I have two identical schemas on different databases. One which is version enabled and having data in it *(mainschema)* and other one is brand new schema which is not version enabled and empty *(newschema)*. I need to transfer data from mainschema to new schema and Im looking for best way to do this task.
Can anyone suggest me how to transfer data from version enabled schema on one database to non-version enabled schema on other database. Please let me know if further information is required.
Regards,
Kumar

Kumar , The FROMUSER and TOUSER capabilities of the Oracle Database import utility are also not supported with version-enabled databases.
Hope the following helps resolve your issue (3rd post).
Moving version enabled table between instances
Thanks

Spatial Query across schemas. one version enabled table another not -Hanged

Hi,
I am executing a PL/sql procedure where a Spatial query run across two schemas. One table(in x schema) is version enabled and second table(in y schema) is Unversioned. Add to that complexity I am running the procedure from third user logon. I think I have enough previleges, as I won't get any error message.
But, Procedure worked fine when there is no table is version enabled. It started giving problem when one table got version enabled.
I have tried by setting " DBMS_WM.Gotoworkspace('LIVE');" before running spatial query. But still no luck, process just hangs on the spatial query.
I tried by using physical name of the Table (table1_LT) which is making it to work. But, as per Workspace manager guide, applications, programs should NOT use, this physical tables(because it is not the correct way on versioned table).
1. How can I hint to my query, to use a table from only live version?
2. Why Query is hanging forever (even tried by leaving it over night....)
Normally it used to take one or two minutes(before versioning..)
I have posted it Workspace manager forum, But No Luck (people seems to be shy away after seeing "Spatial query" )
Any help is highly appriciated

Hi,
I will need to know more details about the specific query you are performing. So, please do the following:
1. list the actual query that you are using
2. generate an explain plan of the query both before and after the table was version enabled. use @?/rdbms/admin/utlxpls or anything that generates the predicate information.
3. also, give any pertinent details about the table(size of the table, number of rows expected to be returned, column types in the table, etc).
Based on that, I will see if I can suggest a possible hint that may be able to improve the performance of your query.
Regards,
Ben

Exporting Data from one Server to Another server w/ Version Enabled Tables

Hi,
I'm currently having a problem with regards to Exporting data to another server. This is the Scenario:
Source Server is Production Server with all of its Tables in the Schema are Version-Enabled.
Destination Server is a Test Server.
I exported data from Production Server using EXP command. Then in my Test Server I imported my data using IMP command (I already created tablespace and user for the Schema).
Import is successful in my Test server but when I execute my queries, There are no rows returned.
I checked my _LT tables and it contains my data. but when I query from the View created when version was enabled, no result is returned.
Am I missing something when I exported and imported my Schema? Should I have included the WMSYS schema when I created the .dump file?
Thanks in advance.

Hi Stefan,
we tried using Export and Import using Data Pump.
expdp system/password@orcl full=y directory=dmpdir2 dumpfile=FULL_DB.dmp
impdp system/password@orcl full=y table_exists_action=truncate directory=dmpdir2 dumpfile=FULL_DB.dmp
Still the same result as using exp and imp. _LT tables have data but when you query using the View, no results are found.

Problem with version enabling tables with ric.

Hello,
i have the a problem when i want to version enable tables having ref. int. constraits having delete rule cascade or set null.
Is it possible that i can't version enable the tables because of these constraints? How i could solve this problem if i want to keep the delete rule?
thanks,
Orsi Gyulai

Hi,
We are internally creating a <table_name>_g procedure that transfers privileges to the necessary users. If you have a table with that name, it would explain the error.
When using ignore_last_error, it will skip the statement that is selected from the all_wm_vt_errors view. Sometimes, the statement can be safely skipped, while in other cases it cannot be. This procedure will always eventually complete when it is repeatedly called with ignore_last_error set to true. However in doing so, some required objects or privileges may not exist or be in an invalid state.
In your case, you most likely had to skip the 3 or so statements that dealt with the <table_name>_g procedure. Typically, these statements should not be skipped, but you may or may not see a problem with it due to a number of factors.
The best course of action may be to drop the trigger in a beginDDL/commitDDL session, and then recreate it in a separate session. Of course, only do this after renaming the <table_name>_g table that you have. Unfortunately, there is currently no way of getting around this naming convention.
Thanks,
Ben

Is it possible to validate a schema defined date

Hi,
Is it possible to validate a schema defined date in xsd as of a null type.
     <xs:element name="ContractDt">
<xs:restriction base="xs:date"/>
</xs:element>
In xml file if i want to keep date null and still should be valid......how do i do it
For eg: <ContractDt></ContractDt>
<ContractDt>1990-12-12</ContractDt>
Both the above should be valid.............and any other thing should be invalid. I know we can use patterns and ennumeration to achive this but...............all the other validations that come along schema defined datatype date are required........
Any help.
Regards,
Aru

Hi,
I meant this...........
<xs:element name="ContractDt" nillable="true">
          <xs:simpleType>
               <xs:union>
                    <xs:simpleType>
                         <xs:restriction base="xs:date"/>
                    </xs:simpleType>
                    <xs:simpleType>
                         <xs:restriction base="xs:string">
                              <xs:enumeration value=""/>
                         </xs:restriction>
                    </xs:simpleType>
               </xs:union>
          </xs:simpleType>
     </xs:element>
Hope my requirement is clear...
Aru

Performance issues with version enable partitioned tables?

Hi all,
Are there any known performance issues with version enable partitioned tables?
Ive been doing some performance testes with a large version enable partitioned table and it seems that OCB optimiser is choosing very expensive plans during merge operations.
Tanks in advance,
Vitor
Example:
     Object Name     Rows     Bytes     Cost     Object Node     In/Out     PStart     PStop
UPDATE STATEMENT Optimizer Mode=CHOOSE          1          249
UPDATE     SIG.SIG_QUA_IMG_LT
NESTED LOOPS SEMI          1     266     249
PARTITION RANGE ALL                                   1     9
TABLE ACCESS FULL     SIG.SIG_QUA_IMG_LT     1     259     2               1     9
VIEW     SYS.VW_NSO_1     1     7     247
NESTED LOOPS          1     739     247
NESTED LOOPS          1     677     247
NESTED LOOPS          1     412     246
NESTED LOOPS          1     114     244
INDEX RANGE SCAN     WMSYS.MODIFIED_TABLES_PK     1     62     2
INDEX RANGE SCAN     SIG.QIM_PK     1     52     243
TABLE ACCESS BY GLOBAL INDEX ROWID     SIG.SIG_QUA_IMG_LT     1     298     2               ROWID     ROW L
INDEX RANGE SCAN     SIG.SIG_QUA_IMG_PKI$     1          1
INDEX RANGE SCAN     WMSYS.WM$NEXTVER_TABLE_NV_INDX     1     265     1
INDEX UNIQUE SCAN     WMSYS.MODIFIED_TABLES_PK     1     62
/* Formatted on 2004/04/19 18:57 (Formatter Plus v4.8.0) */
UPDATE /*+ USE_NL(Z1) ROWID(Z1) */sig.sig_qua_img_lt z1
SET z1.nextver =
SYS.ltutil.subsversion
(z1.nextver,
SYS.ltutil.getcontainedverinrange (z1.nextver,
'SIG.SIG_QUA_IMG',
'NpCyPCX3dkOAHSuBMjGioQ==',
4574,
4575
4574
WHERE z1.ROWID IN (
(SELECT /*+ ORDERED USE_NL(T1) USE_NL(T2) USE_NL(J2) USE_NL(J3)
INDEX(T1 QIM_PK) INDEX(T2 SIG_QUA_IMG_PKI$)
INDEX(J2 WM$NEXTVER_TABLE_NV_INDX) INDEX(J3 MODIFIED_TABLES_PK) */
t2.ROWID
FROM (SELECT /*+ INDEX(WM$MODIFIED_TABLES MODIFIED_TABLES_PK) */
UNIQUE VERSION
FROM wmsys.wm$modified_tables
WHERE table_name = 'SIG.SIG_QUA_IMG'
AND workspace = 'NpCyPCX3dkOAHSuBMjGioQ=='
AND VERSION > 4574
AND VERSION <= 4575) j1,
sig.sig_qua_img_lt t1,
sig.sig_qua_img_lt t2,
wmsys.wm$nextver_table j2,
(SELECT /*+ INDEX(WM$MODIFIED_TABLES MODIFIED_TABLES_PK) */
UNIQUE VERSION
FROM wmsys.wm$modified_tables
WHERE table_name = 'SIG.SIG_QUA_IMG'
AND workspace = 'NpCyPCX3dkOAHSuBMjGioQ=='
AND VERSION > 4574
AND VERSION <= 4575) j3
WHERE t1.VERSION = j1.VERSION
AND t1.ima_id = t2.ima_id
AND t1.qim_inf_esq_x_tile = t2.qim_inf_esq_x_tile
AND t1.qim_inf_esq_y_tile = t2.qim_inf_esq_y_tile
AND t2.nextver != '-1'
AND t2.nextver = j2.next_vers
AND j2.VERSION = j3.VERSION))

Hello Vitor,
There are currently no known issues with version enabled tables that are partitioned. The merge operation may need to access all of the partitions of a table depending on the data that needs to be moved/copied from the child to the parent. This is the reason for the 'Partition Range All' step in the plan that you provided. The majority of the remaining steps are due to the hints that have been added, since this plan has provided the best performance for us in the past for this particular statement. If this is not the case for you, and you feel that another plan would yield better performance, then please let me know and I will take a look at it.
One suggestion would be to make sure that the table was been recently analyzed so that the optimizer has the most current data about the table.
Performance issues are very hard to fix without a reproducible test case, so it may be advisable to file a TAR if you continue to have significant performance issues with the mergeWorkspace operation.
Thank You,
Ben

Unable to drop foreign key on a version-enabled table

Hi,
We're using Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit and I'm trying to delete a foreign key from a version-enabled table.
The constraint shows in ALL_WM_RIC_INFO view. I run exec dbms_wm.beginddl('tablename'), when I inspect the generated <tablename>_LTS I don't see any referential integrity constraints generated on that table ? The constraint i'm trying to delete is from a version-enabled table to a non-version enabled table if that makes a difference.
From what I understand the referential integrity constraint would be generated and I would be able to run something like:
ALTER TABLE <tablename>_LTS DROP CONSTRAINT <constraintname>.
I tried running the above statement using the RIC_NAME from ALL_WM_RIC_INFO view but it fails predictably with:
ORA-02443: Cannot drop constraint - nonexistent constraint
Cause: alter table drop constraint <constraint_name>
Action: make sure you supply correct constraint name.

as I ran into this today as well I feel like answering this question, as I suppose that the thread opener did the same mistake as I did, and maybe
some others do it as well :)
of course you need to open a DDL session on the parent table as well in order to drop foreign key constraints, just as you do when you add them.
so the correct order to make it work would be:
EXECUTE DBMS_WM.BeginDDL('PARENT_TABLE');
EXECUTE DBMS_WM.BeginDDL('CHILD_TABLE');
ALTER TABLE CHILD_TABLE_LTS
DROP CONSTRAINT FOREIGN_KEY_NAME
EXECUTE DBMS_WM.CommitDDL('CHILD_TABLE');
EXECUTE DBMS_WM.CommitDDL('PARENT_TABLE');I felt kind of stupid that it took me 1 hour to figure this out ;)
regards,
Andreas

ODrive Edit in Place PDF Document Manual Versioning enabled Error

Hi,
Any one has tried or able to do edit in place with ODrive and PDF Document type?
I have manual versioning enable. When I am doing edit in place from ODrive for PDF Document getting following error.
I have manually check out the document before doing Edit from ODrive.
Need help to resolve this issue.
Thanks,
Jigar
Error logs
07/05/31 15:45:07 content: [oracle.ifs.ecm.util.FolderUtilities] [24] 99117 publicuser1 INFO: resolveLegacyPath targetPath =
07/05/31 15:46:29 content: [oracle.ifs.protocols.dav.ecm.EcmDavServlet] [23] 99117 publicuser1 WARNING: no mapping found for ORACLE.FDK.ItemNotCheckedOut
07/05/31 15:46:29 content: [oracle.ifs.protocols.dav.ecm.EcmDavServlet] [23] 99117 publicuser1 WARNING: unmapped exception: oracle.ifs.fdk.FdkException:
ErrorCode = ORACLE.FDK.AggregateError; DetailedErrorCode = ORACLE.FDK.AggregateError; Cause = IFS-90244: Cannot update all of the specified
items; ServerStackTraceId = ; Info = null; Entries = 1
Main Exception Stack Trace:
ORACLE.FDK.AggregateError:ORACLE.FDK.AggregateError
at oracle.ifs.fdk.FdkException.getInstance(FdkException.java:181)
at oracle.ifs.fdk.FdkException.getInstance(FdkException.java:74)
at oracle.ifs.fdk.impl.FileManagerImpl.updateDocuments(FileManagerImpl.java:1661)
at oracle.ifs.fdk.impl.FileManagerImpl.updateDocument(FileManagerImpl.java:1511)
at oracle.ifs.protocols.dav.ecm.EcmDavServlet.doPut(EcmDavServlet.java:1688)
at oracle.ifs.protocols.dav.DavServlet.doPut(DavServlet.java:1929)
at oracle.ifs.protocols.dav.DavServlet.processRequest(DavServlet.java:2622)
at oracle.ifs.protocols.dav.ecm.EcmDavServlet.processRequest(EcmDavServlet.java:3616)
at oracle.ifs.protocols.dav.DavServlet.processRequest(DavServlet.java:2396)
at oracle.ifs.protocols.dav.DavServlet.service(DavServlet.java:2361)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(Unknown Source)
at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:16)
at oracle.ifs.fdk.http.HttpServerManager.doFilter(HttpServerManager.java:103)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:659)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:224)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:133)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
at java.lang.Thread.run(Thread.java:534)
Caused by: oracle.ifs.common.IfsException: IFS-90244: Cannot update all of the specified items
at oracle.ifs.ecm.util.BulkUtilities.ecmUpdate(BulkUtilities.java:369)
at oracle.ifs.fdk.impl.FileManagerImpl.updateDocuments(FileManagerImpl.java:1653)
... 19 more
FdkException Details: oracle.ifs.fdk.FdkException: ErrorCode = ORACLE.FDK.AggregateError; DetailedErrorCode = ORACLE.FDK.AggregateError;
Cause = IFS-90244: Cannot update all of the specified items; ServerStackTraceId = ; Info = null; Entries = 1
Entry[0] = oracle.ifs.fdk.FdkExceptionEntry: ErrorCode = ORACLE.FDK.OperationError; DetailedErrorCode = ORACLE.FDK.ItemNotCheckedOut;
ItemID = 99150; Cause = IFS-90301: Cannot update a Document under version control that is not checked out; Info = null
Cause Exception Stack Trace:
oracle.ifs.common.IfsException: IFS-90301: Cannot update a Document under version control that is not checked out
at oracle.ifs.ecm.beans.EcmDocument.lowLevelUpdate(EcmDocument.java:938)
at oracle.ifs.ecm.beans.EcmDocument.ecmUpdate(EcmDocument.java:618)
at oracle.ifs.ecm.util.BulkUtilities.ecmUpdate(BulkUtilities.java:345)
at oracle.ifs.fdk.impl.FileManagerImpl.updateDocuments(FileManagerImpl.java:1653)
at oracle.ifs.fdk.impl.FileManagerImpl.updateDocument(FileManagerImpl.java:1511)
at oracle.ifs.protocols.dav.ecm.EcmDavServlet.doPut(EcmDavServlet.java:1688)
at oracle.ifs.protocols.dav.DavServlet.doPut(DavServlet.java:1929)
at oracle.ifs.protocols.dav.DavServlet.processRequest(DavServlet.java:2622)
at oracle.ifs.protocols.dav.ecm.EcmDavServlet.processRequest(EcmDavServlet.java:3616)
at oracle.ifs.protocols.dav.DavServlet.processRequest(DavServlet.java:2396)
at oracle.ifs.protocols.dav.DavServlet.service(DavServlet.java:2361)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(Unknown Source)
at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:16)
at oracle.ifs.fdk.http.HttpServerManager.doFilter(HttpServerManager.java:103)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:659)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:224)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:133)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
at java.lang.Thread.run(Thread.java:534)
Entry[0] = oracle.ifs.fdk.FdkExceptionEntry: ErrorCode = ORACLE.FDK.OperationError; DetailedErrorCode = ORACLE.FDK.ItemNotCheckedOut;
ItemID = 99150; Cause = IFS-90301: Cannot update a Document under version control that is not checked out; Info = null
Cause Exception Stack Trace:
oracle.ifs.common.IfsException: IFS-90301: Cannot update a Document under version control that is not checked out
at oracle.ifs.ecm.beans.EcmDocument.lowLevelUpdate(EcmDocument.java:938)
at oracle.ifs.ecm.beans.EcmDocument.ecmUpdate(EcmDocument.java:618)
at oracle.ifs.ecm.util.BulkUtilities.ecmUpdate(BulkUtilities.java:345)
at oracle.ifs.fdk.impl.FileManagerImpl.updateDocuments(FileManagerImpl.java:1653)
at oracle.ifs.fdk.impl.FileManagerImpl.updateDocument(FileManagerImpl.java:1511)
at oracle.ifs.protocols.dav.ecm.EcmDavServlet.doPut(EcmDavServlet.java:1688)
at oracle.ifs.protocols.dav.DavServlet.doPut(DavServlet.java:1929)
at oracle.ifs.protocols.dav.DavServlet.processRequest(DavServlet.java:2622)
at oracle.ifs.protocols.dav.ecm.EcmDavServlet.processRequest(EcmDavServlet.java:3616)
at oracle.ifs.protocols.dav.DavServlet.processRequest(DavServlet.java:2396)
at oracle.ifs.protocols.dav.DavServlet.service(DavServlet.java:2361)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(Unknown Source)
at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:16)
at oracle.ifs.fdk.http.HttpServerManager.doFilter(HttpServerManager.java:103)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:659)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:224)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:133)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
at java.lang.Thread.run(Thread.java:534)
07/05/31 15:46:29 content: Servlet error
ORACLE.FDK.AggregateError:ORACLE.FDK.AggregateError
at oracle.ifs.fdk.FdkException.getInstance(FdkException.java:181)
at oracle.ifs.fdk.FdkException.getInstance(FdkException.java:74)
at oracle.ifs.fdk.impl.FileManagerImpl.updateDocuments(FileManagerImpl.java:1661)
at oracle.ifs.fdk.impl.FileManagerImpl.updateDocument(FileManagerImpl.java:1511)
at oracle.ifs.protocols.dav.ecm.EcmDavServlet.doPut(EcmDavServlet.java:1688)
at oracle.ifs.protocols.dav.DavServlet.doPut(DavServlet.java:1929)
at oracle.ifs.protocols.dav.DavServlet.processRequest(DavServlet.java:2622)
at oracle.ifs.protocols.dav.ecm.EcmDavServlet.processRequest(EcmDavServlet.java:3616)
at oracle.ifs.protocols.dav.DavServlet.processRequest(DavServlet.java:2396)
at oracle.ifs.protocols.dav.DavServlet.service(DavServlet.java:2361)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(Unknown Source)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:16)
at oracle.ifs.fdk.http.HttpServerManager.doFilter(HttpServerManager.java:103)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:659)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.AJPRequestHandler.run(AJPRequestHandler.java:224)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.AJPRequestHandler.run(AJPRequestHandler.java:133)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
at java.lang.Thread.run(Thread.java:534)
Caused by: oracle.ifs.common.IfsException: IFS-90244: Cannot update all of the specified items
at oracle.ifs.ecm.util.BulkUtilities.ecmUpdate(BulkUtilities.java:369)
at oracle.ifs.fdk.impl.FileManagerImpl.updateDocuments(FileManagerImpl.java:1653)
... 19 more
FdkException Details: oracle.ifs.fdk.FdkException: ErrorCode = ORACLE.FDK.AggregateError; DetailedErrorCode = ORACLE.FDK.AggregateError;
Cause = IFS-90244: Cannot update all of the specified items; ServerStackTraceId = ; Info = null; Entries = 1
Entry[0] = oracle.ifs.fdk.FdkExceptionEntry: ErrorCode = ORACLE.FDK.OperationError; DetailedErrorCode = ORACLE.FDK.ItemNotCheckedOut;
ItemID = 99150; Cause = IFS-90301: Cannot update a Document under version control that is not checked out; Info = null
Cause Exception Stack Trace:
oracle.ifs.common.IfsException: IFS-90301: Cannot update a Document under version control that is not checked out
at oracle.ifs.ecm.beans.EcmDocument.lowLevelUpdate(EcmDocument.java:938)
at oracle.ifs.ecm.beans.EcmDocument.ecmUpdate(EcmDocument.java:618)
at oracle.ifs.ecm.util.BulkUtilities.ecmUpdate(BulkUtilities.java:345)
at oracle.ifs.fdk.impl.FileManagerImpl.updateDocuments(FileManagerImpl.java:1653)
at oracle.ifs.fdk.impl.FileManagerImpl.updateDocument(FileManagerImpl.java:1511)
at oracle.ifs.protocols.dav.ecm.EcmDavServlet.doPut(EcmDavServlet.java:1688)
at oracle.ifs.protocols.dav.DavServlet.doPut(DavServlet.java:1929)
at oracle.ifs.protocols.dav.DavServlet.processRequest(DavServlet.java:2622)
at oracle.ifs.protocols.dav.ecm.EcmDavServlet.processRequest(EcmDavServlet.java:3616)
at oracle.ifs.protocols.dav.DavServlet.processRequest(DavServlet.java:2396)
at oracle.ifs.protocols.dav.DavServlet.service(DavServlet.java:2361)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(Unknown Source)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:16)
at oracle.ifs.fdk.http.HttpServerManager.doFilter(HttpServerManager.java:103)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:659)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.AJPRequestHandler.run(AJPRequestHandler.java:224)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.AJPRequestHandler.run(AJPRequestHandler.java:133)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
at java.lang.Thread.run(Thread.java:534)

Hi Matt,
Thank you for your very useful reply.
I have non blocking serial approval workflow.
In my workflow I have attachment as PDF document to be signed. URI of that document is from Odrive. Foe example O:\sjrwmd\DMSFAContainer\DMSFALibrary\36397\P041282\978599\Invoice_with_2_blank_sig_OD_2.pdf
When task has been assign to any user, from task detail page of the worklist application user click / open that pdf file and sign the document. When user save this document Odrive should save that to Contentdb.
Just wanted to know that why it is not ODrive bug?
I was able to do following test It works only in Acrobat 6.0.
Steps I did,
1) Upload pdf file to folder with manual versioning enable.
2) Manually checked out file from web ui.
3) Login to ODrive using same user
4) Created html file with link (Please replace href portion to your url of the file)
<HTML>
<BODY>
Testing Link <BR>
<a class="blue" href="O:/sjrwmd/DMSFAContainer/DMSFALibrary/36397/P041282/978599/Invoice_102_wit
h_blank_sig_OD.pdf" target="_blank">Invoice_101CD.pdf</a> <BR>
<a class="blue" href="O:/sjrwmd/DMSFAContainer/DMSFALibrary/16966/P040577/246361/ST_Memo.doc"
target="_blank">ST_Memo.doc</a>
</BODY>
</HTML>
5) Open html in browser
6) Click on document link
7) Will open pdf files in browser
8) Sign the document
9) Click on save a copy button.
10) In the save a copy dialog , file name place paste your file url of o drive for example in my
case
O:/sjrwmd/DMSFAContainer/DMSFALibrary/36397/P041282/978599/Invoice_102_with_blank_sig_OD.pdf
click save
11) This should save updated file
12) Checked in document
I will look into programmatically way to achive this.
Regards,
Jigar

Can't install Adobe Flashplayer 11. Uninstalled old version. enabled Java. Allowed cookies. Install button grey.

Can anyone help me with this problem of installing Adobe Flashdrive 11, the latest version ? I'm bashing my head against the wall. Started when iPhoto would not load to Facebook and was advised it could be Flashplayer update after troubleshooting other options including deleting extraneous iPhoto files. I uninstalled older version, enabled Java, allowed cookies, downloaded installer but when I try to download it, the install button is grey and won't work. (This is, coindcidentally the same problem that suddenly began today with iPhoto which always worked fine before....grey button for "publish") It is ALWAYS a problem installing Adobe anything, and usually this same problem. All my software updates are current. Now I have NO Flashplayer and can't use YouTube at all, much less iPhoto.

Also, sounds like others are having this problem. Read other posts, didn't find an answer. OBVIOUSLY did not solve my problem. No delete ? First time here, sorry.

Row locking issue with version enabled tables

I've been testing the effect of locking in version enabled tables in order to assess workspace manager restrictions when updating records in different workspaces and I have encountered a locking problem where I can't seem to update different records of the same table in different sessions if these same records have been previously updated & committed in another workspace.
I'm running the tests on 11.2.0.3. I have ROW_LEVEL_LOCKING set to ON.
Here's a simple test case (I have many other test cases which fail as well but understanding why this one causes a locking problem will help me understand the results from my other test cases):
--Change tablespace names as required
create table t1 (id varchar2(36) not null, name varchar2(50) not null) tablespace XXX;
alter table t1 add constraint t1_pk primary key (id) using index tablespace XXX;
exec dbms_wm.gotoworkspace('LIVE');
insert into t1 values ('1', 'name1');
insert into t1 values ('2', 'name2');
insert into t1 values ('3', 'name3');
commit;
exec dbms_wm.enableversioning('t1');
exec dbms_wm.gotoworkspace('LIVE');
exec dbms_wm.createworkspace('TESTWSM1');
exec dbms_wm.gotoworkspace('TESTWSM1');
--update 2 records in a non-LIVE workspace in preparation for updating in different workspaces later
update t1 set name = name||'changed' where id in ('1', '2');
commit;
quit;
--Now in a separate session (called session 1 for this example) run the following without committing the changes:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
--Now in another session (session 2) update a different record from the same table. The below update will hang waiting on the transaction in session 1 to complete (via commit/rollback):
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
I'm surprised records of different ids can't be updated in different sessions i.e. why does session 1 lock the update of record 2 which is not being updated anywhere else. I've tried this using different non-LIVE workspaces with similar results. I've tried changing table properties e.g. initrans with and still get a lock. The changes to table properties are successfully propagated to the _LT tables but not all the related workspace manager tables created for table T1 above. I'm not sure if this is the issue.
Note an example of the background workspace manager query that may create the lock is something like:
UPDATE TESTWSM.T1_LT SET LTLOCK = WMSYS.LT_CTX_PKG.CHECKNGETLOCK(:B6 , LTLOCK, NEXTVER, :B3 , 0,'UPDATE', VERSION, DELSTATUS, :B5 ), NEXTVER = WMSYS.LT_CTX_PKG.GETNEXTVER(NEXTVER,:B4 ,VERSION,:B3 ,:B2 ,683) WHERE ROWID = :B1
Any help with this will be appreciated. Thanks in advance.

Hi Ben,
Thanks for your quick response.
I've tested your suggestion and it does work with 2 workspaces but the same problem is enountered when additional workspaces are created.
It seems if multiple workspaces are used in a multi user environment, locks will be inevitable which will degrade performance especially if a long transaction is used.
Deadlocks can also be encountered where eventually one of the sessions is rolled back by the database.
Is there a way of avoiding this e.g. by controlling the creation of workspaces and table updates?
I've updated my test case below to demonstrate the extra workspace locking issue.
--change tablespace name as required
create table t1 (id varchar2(36) not null, name varchar2(50) not null) tablespace XXX;
alter table t1 add constraint t1_pk primary key (id) using index tablespace XXX;
exec dbms_wm.gotoworkspace('LIVE');
insert into t1 values ('1', 'name1');
insert into t1 values ('2', 'name2');
insert into t1 values ('3', 'name3');
commit;
exec dbms_wm.enableversioning('t1');
exec dbms_wm.gotoworkspace('LIVE');
exec dbms_wm.createworkspace('TESTWSM1');
exec dbms_wm.gotoworkspace('TESTWSM1');
update t1 set name = name||'changed' where id in ('1', '2');
commit;
Session 1:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
session 2:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
--end of original test case, start of additional workspace locking issue:
Session 1:
rollback;
Session 2:
rollback;
--update record in both workspaces
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '3';
commit;
exec dbms_wm.gotoworkspace('TESTWSM1');
update t1 set name = 'changed' where id = '3';
commit;
Session 1:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
session 2:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
Session 1:
rollback;
Session 2:
rollback;
exec dbms_wm.gotoworkspace('LIVE');
exec dbms_wm.createworkspace('TESTWSM2');
exec dbms_wm.gotoworkspace('TESTWSM2');
update t1 set name = name||'changed2' where id in ('1', '2');
commit;
Session 1:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
--this now gets locked out by session 1
session 2:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
Session 1:
rollback;
Session 2:
rollback;
--update record 3 in TESTWSM2
exec dbms_wm.gotoworkspace('TESTWSM2');
update t1 set name = 'changed' where id = '3';
commit;
Session 1:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
--this is still locked out by session 1
session 2:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
Session 1:
rollback;
Session 2:
rollback;
--try updating LIVE
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '3';
commit;
Session 1:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
--this is still locked out by session 1
session 2:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
Session 1:
rollback;
Session 2:
rollback;
--try updating TESTWSM1 workspace too - so all have been updated since TESTWSM2 was created
exec dbms_wm.gotoworkspace('TESTWSM1');
update t1 set name = 'changed' where id = '3';
commit;
Session 1:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
--this is still locked out by session 1
session 2:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
Session 1:
rollback;
Session 2:
rollback;
--try updating every workspace afresh
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changedA' where id = '3';
commit;
exec dbms_wm.gotoworkspace('TESTWSM1');
update t1 set name = 'changedB' where id = '3';
commit;
exec dbms_wm.gotoworkspace('TESTWSM2');
update t1 set name = 'changedC' where id = '3';
commit;
Session 1:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '1';
--this is still locked out by session 1
session 2:
exec dbms_wm.gotoworkspace('LIVE');
update t1 set name = 'changed' where id = '2';
Session 1:
rollback;
Session 2:
rollback;

Can Oracle 9i enable schema/table creation to be transacted?

If anyone can help with this, that would be much appreciated.
So - the server has disabled autocommit and commits/rollbacks are handled by the application. Even though this is the case, Oracle 9i is not rolling back changes that have (i) created schemas/users and/or (ii) tables.
Worse still, it seems to be performing a partial rollback - some tables in a schema are left with data and others are not.
Now, this may be caused by our server creating tables for indexing while adding data to some existing tables - that is the table definitions have auto-committed the transaction to date, also committing the table insertions/updates.
After some delving, the JDBC driver has the following method: dataDefinitionCausesTransactionCommit - for Pointbase and other databases, this returns false - for Oracle it returns true.
The questions are therefore:
1) Is there a solution with Oracle 9i that enables schema and table creation to be transacted?
2) Does Oracle 10g allow definition clauses to be transacted?

Actually I believe there is a limited way to make DDL statements transaction based via the CREATE SCHEMA command.
From the 9.2 SQL manaul >>
Use the CREATE SCHEMA to create multiple tables and views and perform multiple grants in a single transaction.
To execute a CREATE SCHEMA statement, Oracle executes each included statement. If all statements execute successfully, Oracle commits the transaction. If any statement results in an error, Oracle rolls back all the statements.
<<
This may be of some limited use to you, but your process should probably be changed to track of the DDL and to undo (drop) any created objects if a rollback is issued.
HTH -- Mark D Powel --

How To version a Schema in SQL Developer?

How To version a Schema in SQL Developer? Is there any open source tool for windows? I used a trial version of Source Control for Oracle by Red Gate. But i am looking for a free tool or way around? Like we do versioning in Jdeveloper?Any help in this regard would be much appreciated.

SQL Developer supports e.g. Subversion out of the box.
Open Sql Developer Help and search for "Versioning"
Using Versioning
SQL Developer provides integrated support for the Subversion and Git versioning and source control systems, and you can add support for other such systems as extensions by clicking Help, then Check for Updates. Available extensions include CVS (Concurrent Versions System) and Perforce.
This is the part about support for versioning. The next step would be how you organize your workflow so every source is available in your repository.
Maybe an online tutorial can help you: Using Source Code Control in Oracle SQL Developer 3.0
Regards
Marcus

Unique constraint violation on version enabled table

hi!
we're facing a strange problem with a version enabled table that has an unique constraint on one column. if we rename an object stored in the table (the name-attribute of the object is the one that has a unique constraint on the respective column) and rename it back to the old name again, we get an ORA-00001 unique constraint violation on the execution of an update trigger.
if the constraint is simply applied as before to the now version enabled table, I understand that this happens, but shouldn't workspace manager take care of something like that when a table with unique constraints is version enabled? (the documentation also says that) because taking versioning into account it's not that we try to insert another object with the same name, it's the same object at another point in time now getting back it's old name.
we somewhat assume that to be a pretty standard scenario when using versioned data.
is this some kind of bug or do we just miss something important here?
more information:
- versioning is enabled on all tables with VIEW_WO_OVERWRITE and no valid time support
- database version is 10.2.0.1.0
- wm installation output:
ALLOW_CAPTURE_EVENTS OFF
ALLOW_MULTI_PARENT_WORKSPACES OFF
ALLOW_NESTED_TABLE_COLUMNS OFF
CR_WORKSPACE_MODE OPTIMISTIC_LOCKING
FIRE_TRIGGERS_FOR_NONDML_EVENTS ON
NONCR_WORKSPACE_MODE OPTIMISTIC_LOCKING
NUMBER_OF_COMPRESS_BATCHES 50
OWM_VERSION 10.2.0.1.0
UNDO_SPACE UNLIMITED
USE_TIMESTAMP_TYPE_FOR_HISTORY ON
- all operations are done on LIVE workspace
any help is appreciated.
EDIT: we found out the following: the table we are talking about is the only table where the unique constraint is left. so there must have been a problem during version enabling. on another oracle installation we did everything the same way and the unique constraint wasn't left there, so everything works fine.
regards,
Andreas Schilling
Message was edited by:
aschilling

hi!
we're facing a strange problem with a version enabled table that has an unique constraint on one column. if we rename an object stored in the table (the name-attribute of the object is the one that has a unique constraint on the respective column) and rename it back to the old name again, we get an ORA-00001 unique constraint violation on the execution of an update trigger.
if the constraint is simply applied as before to the now version enabled table, I understand that this happens, but shouldn't workspace manager take care of something like that when a table with unique constraints is version enabled? (the documentation also says that) because taking versioning into account it's not that we try to insert another object with the same name, it's the same object at another point in time now getting back it's old name.
we somewhat assume that to be a pretty standard scenario when using versioned data.
is this some kind of bug or do we just miss something important here?
more information:
- versioning is enabled on all tables with VIEW_WO_OVERWRITE and no valid time support
- database version is 10.2.0.1.0
- wm installation output:
ALLOW_CAPTURE_EVENTS OFF
ALLOW_MULTI_PARENT_WORKSPACES OFF
ALLOW_NESTED_TABLE_COLUMNS OFF
CR_WORKSPACE_MODE OPTIMISTIC_LOCKING
FIRE_TRIGGERS_FOR_NONDML_EVENTS ON
NONCR_WORKSPACE_MODE OPTIMISTIC_LOCKING
NUMBER_OF_COMPRESS_BATCHES 50
OWM_VERSION 10.2.0.1.0
UNDO_SPACE UNLIMITED
USE_TIMESTAMP_TYPE_FOR_HISTORY ON
- all operations are done on LIVE workspace
any help is appreciated.
EDIT: we found out the following: the table we are talking about is the only table where the unique constraint is left. so there must have been a problem during version enabling. on another oracle installation we did everything the same way and the unique constraint wasn't left there, so everything works fine.
regards,
Andreas Schilling
Message was edited by:
aschilling

Problem by adding one spatial column to the version-enabled table

Hello, I'm trying to modify one version-enabled table T1 like this:
--table definition
create table T1
(ID NUMBER NOT NULL PRIMARY KEY,
NAME VARCHAR2 (256),
FUNCTION VARCHAR2 (256));
--enable versioning
EXECUTE DBMS_WM.EnableVersioning('T1','VIEW_WO_OVERWRITE');
I'd like to add one spatial column to this table by:
-- modify metada view for spatial indexing
INSERT INTO USER_SDO_GEOM_METADATA (TABLE_NAME, COLUMN_NAME, DIMINFO, SRID)
VALUES ('T1_LT', 'ANCHOR',
MDSYS.SDO_DIM_ARRAY
(MDSYS.SDO_DIM_ELEMENT('X', 0.000, 100000.000, 0.0005),
MDSYS.SDO_DIM_ELEMENT('Y', 0.000, 100000.000, 0.0005),
MDSYS.SDO_DIM_ELEMENT('Z', -100, 1000, 0.0005)) , 81989002);
-- table modification - add a column and create a spatial index
EXECUTE DBMS_WM.BeginDDL('T1');
ALTER TABLE T1_LTS ADD ("ANCHOR" MDSYS.SDO_GEOMETRY);
CREATE INDEX T1_SPX on T1_LTS(ANCHOR) INDEXTYPE is MDSYS.SPATIAL_INDEX;
EXECUTE DBMS_WM.CommitDDL('T1');
By finishing of the DDL operation with EXECUTE DBMS_WM.CommitDDL('T1') I get an error message:
"SQL> EXECUTE DBMS_WM.CommitDDL('T1');
BEGIN DBMS_WM.CommitDDL('T1'); END;
ERROR at line 1:
ORA-20171: WM error: 'CREATE TABLE' and 'CREATE SEQUENCE' privileges needed.
ORA-06512: at "SYS.WM_ERROR", line 342
ORA-06512: at "SYS.WM_ERROR", line 359
ORA-06512: at "SYS.LTUTIL", line 8016
ORA-06512: at "SYS.LT", line 11925
ORA-06512: at line 1
What is wrong here? The Oracle 10g DB is installed on Windows 2003 Server, OWM_VERSION - 10.2.0.1.0.
Regards,
Viktor

Hi,
You need to explicitly grant the create table and create sequence privileges to the user owning the table. It is not enough for these to be granted by using a role. This restriction is documented in the user guide.
Also, you should add the entry in the user_sdo_geom_metadata view on the t1_lts table, which is the table to which you are actually adding the geometry column, after calling beginDDL. CommitDDL will make the necessary changes, which in this case would be to add an entry for both t1 and t1_lt.
Regards,
Ben

Is it possible to version enable schema

Similar Messages

Maybe you are looking for