Upgrading the Content Server software

Use these instructions to upgrade Content Server software. The length of time needed to upgrade a

repository depends on the size of the repository. Allow sufficient time for backing up the repository

and performing the upgrade.

To upgrade the software installation:

1. Back up the repository.

2. If the repository contains customized repository formats (dm_format objects), back up the

customized formats.

Repository formats are upgraded by the dm_apply_formats.ebs script, which reads values from

the formats.csv file. If the attributes of a format in the repository do not match the format

descriptions in the formats.csv file, the script overwrites the existing values with the values

in the file.

3. Run the consistency checker.

The consistency checker is a script that looks for repository inconsistencies, such as users with

nonexistent groups, permissions sets with nonexistent users, and sysobjects that point to

nonexistent content files. Fixing inconsistencies in the repository improves the quality of the data

in the repository and results in a smoother upgrade. The syntax is:

dmbasic -fconsistency_checker.ebs -eEntry_Point -- repository_name

superuser password

        • repository_name is the name of the repository against which you are running the consistency

           checker.

         • superuser is the username of a repository superuser

         • password is the password for the superuser’s account.

The results of the consistency checker are directed to standard output.

4. Fix the inconsistencies reported by the consistency checker as errors.

The EMC Documentum Content Server Administration and Configuration Guide provides information

on the consistency checker.

5. Disable all jobs.

        • On UNIX and Linux, disable jobs in all repositories in the installation you are upgrading.

6. For the upgrade on a Windows host, shut down the repositories and connection brokers.

a. Click Start > Programs > Documentum > Server Manager.

b. Select the correct Content Server and click Stop.

c. Click the connection broker tab.

d. Select each connection broker.

e. Click Stop.

7. For the upgrade on a UNIX or Linux host, shut down the repositories and connection brokers.

EMC Documentum System Version 6.7 SP2 Upgrade and Migration Guide 51

Upgrading Content Server

a. For each repository, run the dm_shutdown_repository script, where repository is the name of

the Content Server to be stopped.

b. Stop each connection broker using the dm_stop_connection broker utility.

The EMC Documentum Content Server Administration and Configuration Guide contains

instructions.

8. Shut down the application server.

• To shut down the application server on Windows, stop the service called Documentum Java

method server. Ensure that the application server does not start automatically after a host

restart.

• To shut down the Java method server on UNIX or Linux, run the script

$DOCUMENTUM_SHARED/<application_server>/domains/DctDomain/stopMethodServer.sh.

9. Run the Content Server installation program. and contain the details.

10. Run the Content Server configuration program.

The Content Server configuration section in the installation chapter provides the procedure on

running the Content Server configuration program. Perform the procedure with the following

upgrade modification steps:

a. At step 6, select Custom configuration.

b. At step 8 (Configure a connection broker), select Upgrade an existing connection broker.

c. At step 9 (Configure a repository), select Upgrade an existing repository and skip to step 12.

The upgraded repository will use the same configuration settings as the existing repository.

If you are upgrading a repository on a Sybase platform, the upgrade procedure may hang

if the database transaction log is too small. When the repository is upgraded, it opens a

long-running transaction while the upgrade script is running. If the transaction log is too

small, the transaction hangs with locked system tables because the database server cannot

write information to the transaction log. To continue with the upgrade:

1.     Run the following command on the Sybase database:

sp_dboption db_name,'trun log on chkpt',true

2.     Run a checkpoint command to truncate the transaction log.

3. If steps 1 and 2 fail to resolve the issue and allow the upgrade to proceed, increase the

transaction log space.

11. If you upgraded from an installation using FAST fulltext indexing, and selected xPlore fulltext

indexing, you must restart Content Server again after you complete Content Server configuration.

12. After you complete the Content Server configuration, create a nonunique index on the

dm_sysobject.r_object_id and r_aspect_name properties by using the following MAKE_INDEX

command:

EXECUTE make_index WITH type_name='dm_sysobject',

attribute='r_aspect_name',use_id_col=true

The inclusion of the use_id_col argument set to true automatically causes Content Server to

include the r_object_id column in the index.

Note: Before you create the index, verify if it exists already. Check if dm_sysobject has an index on

r_aspect_name and r_object_id. If the index does not exist, then create it by using the above DQL.

13. If you are upgrading a repository in a distributed environment that uses a BOCS and

asynchronous write jobs, create an index on the dmr_content_s(i_parked_state, r_object_id)

properties. Use the following MAKE_INDEX command to do so:

EXECUTE make_index WITH type_name='dmr_content',

attribute='i_parked_state',use_id_col=true,id_in_front=false

14. For an upgrade from 6.5 SP2 to the current version:

After the upgrade is complete, for Windows, delete the directory <DctmUserDir>\bea9.2

(typically c:\documentum\bea9.2) as well as the directory <DctmUserDir>\bea9.2 (typically

c:\program files\documentum\bea9.2). For Unix, delete $DOCUMENTUM_SHARED/bea9.2.

15. Enable all jobs you previously disabled. In Documentum Administrator, navigate to

Administrator>Job Management>Jobs. For each of the previously disabled jobs, right-click the

job and select Properties. In the Properties window, set the State option to Active.

16. On a Windows upgrade, the Startup Type is set to Manual for the Documentum Docbase Service

repository name service. If you want the repository to automatically start after a server reboot,

navigate to Start>All Programs>Administrative Tools>Services, and set the Startup Type to

Automatic.