Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML KM-Dim9: Reported Defect DEF85428: Issue Fixed in Dimensions 9.1.3: Users still get ...Error: cannot overwrite file
During mass check in / upload operations occasionally DB2 gets into deadlock state. When this happens the transactions are rolled back . However, at that point the item library files have already been created, and they are not removed.
CMS-XML KM-Dim7: Error: ORA-01562, 00000, "failed to extend rollback segment (id = %s)"
Rollback Segments store transactions that are in progress. They are used to back out transactions which were applied to the database due to lack of space in the database buffer cache in memory but are not committed. They are also extremely sensitive to storage space problems in instances that process large transactions
CMS-XML During workflow transition, investement is deleted after error "Get error "Unable to cast object of type 'PacificEdgeSotware.Common.Command.MergeObjectAndTemplateCommand'...."
[Expected Results] The workflow process should be done as a transaction on the database side. Then, if it fails for any reason, the transaction will be rolled back . This should prevent the original investment from being lost.
CMS-XML MCLG: "Check out failed, Unable to check out asset. SQLException:ASA Error -193: Primary key for table 'AssetVersion' is not unique SQLState: 23W01 errorCode: 2601" when trying to check out an asset.
Inf 2003/06/09 09:11:53 PDT-- Request: Request.leave: Because of mismatching connection transaction levels an active transaction was rolled back
CMS-XML KM-Dim9: Can you switch between using Rollback Segments and Automatic Undo Management?
rollback segment for performing system transactions . There is only one
CMS-XML KM-Dim9: ORA-01562: failed to extend rollback segment number 1, ORA-01628: max number of extents 20 reached for rollback segment RO
Use the following to take that rollback segment offline, forcing Oracle to use other rollback segments for transactions . sqlplus system/<password> SQL> alter rollback segment R0 offline;
PDF Upgrading from Dimensions 6.0 to 7.0
Oracle will not wait for connected users, but will rollback current transactions . Any recovery on subsequent startup is automatic.
PDF Database Administrator’s Guide
 IMMEDIATE Dimensions will not wait for connected users, but will rollback current transactions . Any recovery on subsequent startup is automatic.
PDF Administrator’s Guide
* IMMEDIATE Oracle will not wait for connected users, but will rollback current transactions . Any recovery on subsequent startup is automatic. IMMEDIATE is recommended if the machine is going to be shut down, or if the database is malfunctioning.
CMS-XML KM-Dim7: Backup software will timeout while waiting for PVCS Dimensions complete pcms_shutdown script.
Instead of issuing blanket PCMS_SHUTDOWN, issue PCMS_SHUTDOWN IMMEDIATE. This will cause Dimensions to not wait for users to disconnect, but will rollback current transactions . Any recovery on subsequent startup is automatic.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Rolling Back Requests (demonstration)
This demonstration shows you how to roll back to the previous version of a deployment area in Dimensions CM. A rollback puts back the files that were previously deployed to the area, not just the latest revisions of the files at that stage.

Additional Assistance

  • Submit a Case Online
  • FAQs