Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML KM-Dim7: Moving Database Indexes to a separate Tablespace
Instructions for moving the Indexes This document explains how to accomplish this process on a Dimensions system where the database server is on a Windows/NT platform.
CMS-XML KM-Dim10: Issues with moving a Dim Database that uses Replication
Moving a replication basedb to another SID / hostname For each basedb in the database the following needs to be done (make sure the database is backed up before beginning) 1. Ensure the imported basedb is registered against the correct server using Net Admin in Admin console
CMS-XML KM-Dim7: How to move Oracle database files from existing server to another and separate them into multiple file systems.
The first is to place the files in their new location then create a new controlfile. The second is to use the ALTER DATABASE RENAME command for each of the tablespaces. The second method is preferred as it is the easiest and is less problematic when returning the database to open status for use.
CMS-XML KM-Dim9: Moving products across base databases
Is it possible to copy a product from one base database to an existing base database ?
CMS-XML Dim cm: after moving Dimensions server and item library to a new machine, browse item no longer works for delta library storage
After moving Dimensions server, database and Item librairies from one server to an other, items of a specific product are no longer accessible. Indeed, when browsing one item of this product, getting this error: Browse item - FSY0004611E Error: Cannot open file demo-01.txt-169910766X12761X1.1 - No such file or directory (error=2).
CMS-XML DIM10: How to move Dimensions installation to different directory
5. Uninstall Dimensions using Windows Add/Remove programs. You are just going to uninstall the Dimensions application server - not the database or libraries.
CMS-XML Dim12.2.2: Correcting the Wrong Database System Identifier.
After moving server to another host, email messages can have the wrong Database System Identifier.
CMS-XML KM-Dim9: How to move item libraries to new server
For Dimensions 7.2 Use the Network Admin tool on the new server/ database to add the new machine to the list of defined nodes if using DFS Use the Process Modeller to change the Item Library locations on the new machine
CMS-XML KM-Dim9: SQL Solution: ora-00001 constraint error on sec_cm_attr_upd_hist1 trying to move change docs to secondary catalogue
User gets the following error when trying to move change docs to secondary catalogue: 1019-DBIO: Database I/O error occurred. SQL-0304(18008) ORA-00001: unique constraint (SEC_CM_ATTR_UPD_HIST1) violated
CMS-XML KM-Dim9:1348-SUCCEEDED_TO_ARCHIVE Moved %s from main catalogue into secondary catalogue successfully
The Database platform and version being used The exact list of steps to recreate the error message A detailed control plan report
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs