Documentum Server 6.6 Errors « dm_misc: Miscellaneous Documentum Information. Tips: SQL Server Database Ownership for a Documentum Database « Word of Pie. Every now and then, I run into an instance where a database for Documentum has changed slightly, preventing an upgrade or even startup. There is nothing wrong with the database itself, just the way the database ownership is configured. There are several reasons why this could happen: The database was restored after a crashThe database was moved to a new serverA new user was created to own the database This is all fine and can be done properly. The Database dbo Account In SQL Server, every database has a built-in dbo user.
The dbo user should own every Table and View in the Documentum database. The account that Documentum uses to connect should be the assigned login for the dbo account. There are a few other options for this stored procedure, but that gets the job done. Changing the Database Login This is not as simple as it sounds. What if it is too late and the Repository (docbase) won’t start? Like this: Like Loading... Pie on Content Management: Tips: Installing Documentum 6.6 on SQL Server 2008 and 64-bit. –Cloning a repository « Content Bonson. Restoring a Docbase/Repository from the Database and File Store Backups: 1) Create a fresh docbase using Server Configuration Utility.
Ensure that you create the fresh docbase with same repository name, repository ID, database name, repository owner name and password as in the production repository. All the above details can be obtained from the server.ini file of the production repository. Eg: Repository name = prod_docbase Repository ID = 39351 Repository owner name = dmadmin Password = PASSWORD Obtain the docbase owner and password from the Content Server Administrator of the production repository. 2) As a consequence of the above step, we will have a file store created on the Content Server host (\data\ prod_docbase) and table space (prod_docbase) created on the database server (MSSQL 2000). 3) Connect to the Enterprise Manager on the SQL server machine and open the Databases folder. 4) Right Click the database (prod_docbase) corresponding to the repository created in the step 1. 8.
DCTM upgrade 5.3 SP6 to 6.7. Throughout this article 5.3 SP3 system will be called as Source and 6.7 system will be referred as Target Pre Migration Steps Checklist Target Content Server is installedTarget SQL Server instances are created with same collation as that in source environmentTarget Number of instances & there names are matching as that in source environmentTarget Number of DSN & there names are matching as that in source environmentSQL Server client is installed on Target Content ServerDSN’s are tested on Target Content Server Create new repository on Target server DSN’s are tested on Target Content ServerwNew repository must have Repository Name, Repository ID and Repository description same as Source version.Repository DSN must have same configuration & name as that in Source Database user name & password should be the same as that in Source DB build queries before migration Execute below database queries to fetch values from created repository in target environment to be used after migration Complete.
Documentum Repository Cloning / Copy Steps « DMoksha. August 27, 2009 Documentum administrator’s need to upgrade the content server and repositories to keep the installation updated with latest service packs and releases. This is one of the most critical tasks for a Documentum professional. Any thing goes wrong in upgrade could put the whole setup unusable. It is always wise to create a copy or clone of the existing repository and then test upgrades on the cloned environment. Repository copy or cloning steps are described in Content Server Installation Guide, Chapter 12 – Creating a repository copy to test an upgrade. I have prepared a summary of upgrade procedure: Shutdown production repositoryOn target host create a new Content Server installation & repository using the same version of installable.
Cloning of Documentum 6 repositories will need some more steps related with encryption and these steps are described in the EMC Support Notes esg74708 & esg96192. Like this: Like Loading...