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.
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
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.
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).
5. Uninstall Dimensions using Windows Add/Remove programs. You are just going to uninstall the Dimensions application server - not the database or libraries.
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
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
