7.0-dm_upgrade_mgr

DM_UPGRADE_MGR


ERROR: [DM_UPGRADE_MGR_F_INTERNAL_ERROR]

SEVERITY: FATAL
DESCRIPTION: S The Upgrade Manager has encountered an internal error: %s.
CAUSE: An internal error has occurred in the Upgrade Manager
ACTION: Report this error to your Documentum Tech Support Representative.
PARAMS: Details of the internal error Id: dmuser.e,v 4.1 1996/11/22 12:19:28 roger Exp $ DmUser and dmGroup classes errors // // Documentum DocuServer // Confidential Property of Documentum, Inc. // (c) Copyright Documentum, Inc., 1992 – 1995 // All rights reserved.

ERROR: [DM_UPGRADE_MGR_F_INTERNAL_INDEX_VALIDATION_FAILURE]

SEVERITY: FATAL
DESCRIPTION: D Unable to validate dmi_index object with ID %s due to an internal error.
CAUSE: This is an internal error. The only reason we should ever get this is that our internal hard coded list of indices that we use to validate against is out of synch. Check the hard coded list in dmconv.cxx, dmUpgrade40 class.
ACTION: Report this error to a Documentum Adminstrator.
PARAMS: The first parameter is the object id of the dmi_index object that was being validated.

ERROR: [DM_UPGRADE_MGR_E_INDEXED_ATTRIBUTE_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: SSD The attribute %s of type %s, indexed by dmi_index object with ID %s does not exist.
CAUSE: The indexed attribute does not exist in the docbase.
ACTION: Verify that the attribute referenced by the dmi_index object exists. If it does not exist, remove the index and restart upgrade.
PARAMS: The first parameter is the name of the attribute. The second parameter is the name of the type. The third parameter is the id of the dmi_index object.

ERROR: [DM_UPGRADE_MGR_E_QUERY_EXECUTION_FAILURE]

SEVERITY: ERROR
DESCRIPTION: SS The Upgrade Manager failed to execute the following query: %s. The database error is %s.
CAUSE: Query execution failed.
ACTION: Check the error message from the database in order to determine the cause of the query failure.
PARAMS: The first parameter is the query that was being executed. The second parameter is the resulting error from the database.

ERROR: [DM_UPGRADE_MGR_E_UNABLE_TO_VALIDATE_INDEX]

SEVERITY: ERROR
DESCRIPTION: D Unable to validate dmi_index object with ID %s. The index either could not be validated or does not exist.
CAUSE: The upgrade code attempts to validate all Documentum indices due to a potential error during previous upgrades in which the dmi_index object was inconsistent with the actual indexed attribute. If this error occurs, either the index could not be properly validated, or it does not exist.
ACTION: Contact a Documentum Administrator with the information given in the error
PARAMS: The first parameter is the object id of the dmi_index object that was being validated.

ERROR: [DM_UPGRADE_MGR_E_UNABLE_TO_CREATE_INDEX]

SEVERITY: ERROR
DESCRIPTION: SS The Upgrade Manager failed to create an index on table %s. The error from the database was: %s
CAUSE: Index creation on a table failed. A database error has occurred.
ACTION: Contact a Documentum Administrator with the supplied database error.
PARAMS: The table the index was being created on. The error from the database.

ERROR: [DM_UPGRADE_MGR_W_UNABLE_TO_VALIDATE_USER_INDEX]

SEVERITY: WARNING
DESCRIPTION: DS Unable to validate the dmi_index object with ID %s. The index name is %s. Verify that the index refers to the correct attribute(s).
CAUSE: The upgrade code tried to validate all indices due to a potential error during previous upgrades in which the attribute field in dmi_index was not updated properly. As a result, some indices may point to the wrong attribute(s).
ACTION: Users should drop this index using the DROP_INDEX apply method and then recreate the index using the MAKE_INDEX apply method.
PARAMS: The first parameter is the object id of the dmi_index object. The second parameter is the index name of the dmi_index object.

ERROR: [DM_UPGRADE_MGR_I_SYBASE_ROW_LOCKING_COMPLETED]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager has completed verifying that row level locking is enabled for all tables.
CAUSE: This is an informational message generated during docbase upgrade.
ACTION: None.
PARAMS: None.

ERROR: [DM_UPGRADE_MGR_I_PREVENTING_PRE_40_SERVER_FROM_STARTING]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager has now reached a point where it cannot revert the docbase back to a pre-4.0 server.
CAUSE: This is an informational message generated at the point when the server cannot be reverted back to a pre-4.0 server.
ACTION: None
PARAMS: None.

ERROR: [DM_UPGRADE_MGR_I_DOCBASE_UPGRADE_COMPLETE]

SEVERITY: INFORMATION
DESCRIPTION: S The Upgrade Manager has successfully upgraded the docbase to version %s.
CAUSE: This is an informational message generated at the beginning of upgrade.
ACTION: None.
PARAMS: The version we are trying to upgrade to.

ERROR: [DM_UPGRADE_MGR_I_INDEX_VALIDATION_COMPLETED]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager has successfully completed validating Documentum indices.
CAUSE: This is an informational message generated at the completion of indice validation.
ACTION: None
PARAMS: None

ERROR: [DM_UPGRADE_MGR_I_INDEX_VALIDATION_STARTED]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager has started to validate Documentum indices. The Upgrade Manager will attempt to correct any incorrect indices
CAUSE: This is an informational message generated at the beginning of indice validation.
ACTION: None
PARAMS: None.

ERROR: [DM_UPGRADE_MGR_I_VALIDATING_INDEX]

SEVERITY: INFORMATION
DESCRIPTION: D The Upgrade Manager is validating index with ID %s.
CAUSE: This is an informational message generated during docbase upgrade.
ACTION: None.
PARAMS: The object id of the index object being validated.

ERROR: [DM_UPGRADE_MGR_I_DROPPING_INDEX_ON_DMI_OBJECT_TYPE]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager is dropping the index on the dmi_object_type table for enhanced upgrade performance
CAUSE: This is an informational message generated during docbase upgrade.
ACTION: None.
PARAMS: None.

ERROR: [DM_UPGRADE_MGR_I_RECREATING_INDEX_ON_DMI_OBJECT_TYPE]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager is re-creating the index on dmi_object_type table.
CAUSE: This is an informational message generated during docbase upgrade.
ACTION: None.
PARAMS: None.

ERROR: [DM_UPGRADE_MGR_I_OBJECT_TABLE_CONVERSION_STARTED]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager has started the object table conversion.
CAUSE: This is an informational message generated during docbase upgrade.
ACTION: None.
PARAMS: None.

ERROR: [DM_UPGRADE_MGR_I_DOCBASE_UPGRADE_STARTED]

SEVERITY: INFORMATION
DESCRIPTION: S The Upgrade Manager has started to upgrade the docbase to version %s.
CAUSE: This is an informational message generated at the start of upgrade.
ACTION: None.
PARAMS: The version we are trying to upgrade to.

ERROR: [DM_UPGRADE_MGR_I_INDEX_CREATION_FOR_UPGRADE_STARTED]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager has started to create the necessary indices for upgrade. This may take some time.
CAUSE: This is an informational message generated at the beginning of indices creation
ACTION: None.
PARAMS: None.

ERROR: [DM_UPGRADE_MGR_I_DOCBASE_UPGRADE_FAILED]

SEVERITY: INFORMATION
DESCRIPTION: S The Upgrade Manager was unable to upgrade the docbase to version %s. Customers are encouraged to turn on sql tracing as well as upgrade tracing and restart the upgrade. The additional tracing information will be helpful in determining the cause of upgrade failure.
CAUSE: The server upgrade process failed due to one or more errors. More detailed information regarding the error should have been reported earlier in the log.
ACTION: Gather up error information from the server log and determine the cause of the failure. If the cause can be fixed, the upgrade should be re-runnable.
PARAMS: The version we are trying to upgrade to.

ERROR: [DM_UPGRADE_MGR_I_UPGRADE_INFO]

SEVERITY: INFORMATION
DESCRIPTION: S %s.
CAUSE: This is an informational message generated when the document base is upgrading.
ACTION: None.
PARAMS:

ERROR: [DM_UPGRADE_MGR_I_INDEX_CREATION_FOR_UPGRADE_COMPLETED]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager has created the necessary indices for upgrade.
CAUSE: This is an informational message generated at the completion of indices creation
ACTION: None.
PARAMS: None.

ERROR: [DM_UPGRADE_MGR_I_SYBASE_ROW_LOCKING_STARTED]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager has started verifying that row level locking is enabled for all tables.
CAUSE: This is an informational message generated during docbase upgrade.
ACTION: None.
PARAMS: None.

ERROR: [DM_UPGRADE_MGR_I_INDEX_CREATION_FOR_UPGRADE_FAILED]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager was unable to create the necessary indices for upgrade.
CAUSE: This is an informational message generated upon failure of index creation. More detailed error messages should have been reported earlier.
ACTION: Look at the server log for additional error messages which may indicate the nature of the problem.
PARAMS: None.

ERROR: [DM_UPGRADE_MGR_I_OBJECT_TABLE_CONVERSION_COMPLETED]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager has completed the object table conversion.
CAUSE: This is an informational message generated during docbase upgrade.
ACTION: None.
PARAMS: None.

ERROR: [DM_UPGRADE_MGR_I_SYBASE_ROW_LOCKING_FAILED]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager has failed to set row locking on existing tables.
CAUSE: This is an informational message generated upon failure to set row level locking. More detailed error messages should have been reported earlier.
ACTION: Look at the server log for additional error messages which may indicate the nature of the problem.
PARAMS: None.

ERROR: [DM_UPGRADE_MGR_I_OBJECT_TABLE_CONVERSION_FAILED]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager has encountered a failure during object table conversion.
CAUSE: This is an informational message generated upon failure of object table conversion. More detailed error messages should have been reported earlier.
ACTION: Look at the server log for additional error messages which may indicate the nature of the problem.
PARAMS: None.

ERROR: [DM_UPGRADE_MGR_I_INDEX_VALIDATION_FAILED]

SEVERITY: INFORMATION
DESCRIPTION: The Upgrade Manager failed to validate Documentum indices.
CAUSE: This is an informational message generated upon failure of index validation. More detailed error messages should have been reported earlier.
ACTION: Look at the server log for additional error messages which may indicate the nature of the problem.
PARAMS: None.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: