7.0-dm_dump

DM_DUMP


ERROR: [DM_DUMP_F_INIT_FAILURE]

SEVERITY: FATAL
DESCRIPTION: S Initialization failure for %s.
CAUSE: Failure initializing a resource needed by dump and load.
ACTION: Check the error log for other error messages which should give more detail on the problem. Electronic Signature Errors ** Documentum DocuServer ** Confidential Property of Documentum, Inc. ** (c) Copyright Documentum, Inc., 1991-1998 ** All rights reserved. **
PARAMS: The name of the resource we failed to initialize.

ERROR: [DM_DUMP_E_CANT_CONTINUE]

SEVERITY: ERROR
DESCRIPTION: Cant continue dump — count of root sets has changed
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DUMP_E_NOT_SYS_ADMIN]

SEVERITY: ERROR
DESCRIPTION: S You must have sys admin privileges to perform a %s operation.
CAUSE: Not enough privilege
ACTION: Operation must be run as a privileged user.
PARAMS: %1 – description of the particular operation needing sysadmin priv

ERROR: [DM_DUMP_E_CANT_PROBE_OBJ]

SEVERITY: ERROR
DESCRIPTION: D Error checking existence of object to dump. Object id: %s. The server encountered an error while fetching an object from the docbase in order to write it to the dumpfile.
CAUSE: Error returned from the object manager.
ACTION: Check the error log for error messages logged by the object manager which may give more detail on the problem. Check the rdbms log for errors.
PARAMS: %1 – handle for object the server was attempting to fetch

ERROR: [DM_DUMP_E_OBJECT_SAVE_FAILED]

SEVERITY: ERROR
DESCRIPTION: S Save of dump object %s failed — dump terminated
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DUMP_E_DESTROY_DUMP_RECORD]

SEVERITY: ERROR
DESCRIPTION: An error occurred during cleanup from a Dump as part of a destroy request on the dm_dump_record object. The dump operation bookkeeping records (dmi_dump_object_record) have not been fully cleaned up. During a dump operation, the server creates bookkeeping records to keep track of what has been dumped (dmi_dump_object_record types). When the dump is complete, these records are cleaned up when the dump record itself is destroyed. The error is given when some problem occurs during the destroy of the dm_dump_record or the dmi_dump_object_records associated with it. The original dump operation which was done with the dm_dump_record is not affected by this error, only the cleanup of the bookkeeping objects is affected. NOTE: once a destroy has been started after a dump operation, the operation itself is committed. The dump can no longer be backed out via a revert. If a revert is done on a dump record following this error, then only part of the dumped data will be removed!
CAUSE: Possibly the underlying database system ran out of some resource, most likely logfile space.
ACTION: Review the error log for other errors indicating the destroy problem, then retry the destroy.
PARAMS:

ERROR: [DM_DUMP_E_CANT_OPEN_OLD_FILE]

SEVERITY: ERROR
DESCRIPTION: S Could not open old output dumpfile %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DUMP_E_NO_FILENAME]

SEVERITY: ERROR
DESCRIPTION: No file_name value given for the Dump Operation.
CAUSE: The file_name attribute of the dm_dump_record was not set.
ACTION: Set the file_name attribute and re-save the dump record.
PARAMS: None.

ERROR: [DM_DUMP_E_CANNOT_CREATE]

SEVERITY: ERROR
DESCRIPTION: S Cannot create dump file with the specified file name: %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DUMP_E_OPEN_TRANSACTION]

SEVERITY: ERROR
DESCRIPTION: The destroy Dump operation cannot be executed while inside of a user transaction. A dump operation needs to start its own internal transaction so that it can control when periodic commits are done to free database resources. It cannot be executed while a user transaction is in progress.
CAUSE: The user session which requested the destroy dump has a currently outstanding transaction open.
ACTION: Complete the current transaction before destroying the dump record.
PARAMS:

ERROR: [DM_DUMP_E_REPLICA_CATALOG]

SEVERITY: ERROR
DESCRIPTION: S Database error in accessing replica catalog: %s
CAUSE: A database error has occurred when the server checks on the replica catalog if an object has been previously dumped.
ACTION: Check with the database dba. If error persists, use other dump mode.
PARAMS: Database error message.

ERROR: [DM_DUMP_E_CANT_OPEN_NEW_FILE]

SEVERITY: ERROR
DESCRIPTION: S Could not open new output dumpfile %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DUMP_E_FILE_IO]

SEVERITY: ERROR
DESCRIPTION: S File Input / Output error. Operating System Error : %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DUMP_E_INIT_DUMP]

SEVERITY: ERROR
DESCRIPTION: II Version stamp %d was expected to be %d
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DUMP_E_MAP_BUILD]

SEVERITY: ERROR
DESCRIPTION: D Error building map records in GetDumpMap operation for object %s. In replication processing, the server is sometimes called to generate a dump map which gives all the objects related to the one being replicated. This map is then used to determine what objects need to be replicated from the source docbase. If this error is given, then the server encountered an error attempting to build the map of object relationships.
CAUSE: The server could not build the relationship map. Could be an integrity problem or even a resource exhaustion.
ACTION: Check for errors in the sesssion log. Try Enabling tracing during the operation (trace,c,1,,DM_DUMP) and check the session log for further information.
PARAMS: %1 – handle for object for which map was requested

ERROR: [DM_DUMP_E_RECORDED_SIZE]

SEVERITY: ERROR
DESCRIPTION: SS The recorded size of %s in file (%s) is corrupted.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DUMP_E_TYPE_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: S Dump request error: type %s does not exist in this docbase.
CAUSE: One of the types requested in the type list of the dump object was not found in the docbase.
ACTION: Remove the non-existent types from the dump list and restart the dump operation.
PARAMS: The requested type name which could not be found.

ERROR: [DM_DUMP_E_PARAM]

SEVERITY: ERROR
DESCRIPTION: S Bad parameter for internal Dump Operation: %s
CAUSE: A valid parameter is missing.
ACTION: Check for the correct parameter value and re-save the dump record.
PARAMS: The invalid parameter string.

ERROR: [DM_DUMP_E_FILL_DUMPLOAD]

SEVERITY: ERROR
DESCRIPTION: Error in FILL_DUMPLOAD_TABLES operation. This error message is given on any failure in the FILL_DUMPLOAD_TABLES operation. It should be accompanied by a preceeding error message which will give a more detailed reason.
CAUSE: Failure in the FILL_DUMPLOAD_TABLES method.
ACTION: Check the error log for other error messages which should give more detail on the problem.
PARAMS: None

ERROR: [DM_DUMP_E_NON_RESTART]

SEVERITY: ERROR
DESCRIPTION: Dump operation is not restartable because user has set the restart flag to false.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DUMP_E_BAD_STREAM]

SEVERITY: ERROR
DESCRIPTION: A system error has occurred during a data stream formating operation.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DUMP_E_OBJECT_UPDATE_FAILED]

SEVERITY: ERROR
DESCRIPTION: S Update of dump object %s failed — dump terminated
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DUMP_E_CANT_FETCH_OBJ]

SEVERITY: ERROR
DESCRIPTION: D Error fetching object to dump. Object id: %s. The server encountered an error while fetching an object from the docbase in order to write it to the dumpfile.
CAUSE: Error returned from the object manager.
ACTION: Check the error log for error messages logged by the object manager which may give more detail on the problem. Check the rdbms log for errors.
PARAMS: %1 – handle for object the server was attempting to fetch

ERROR: [DM_DUMP_E_NOT_SUPERUSER]

SEVERITY: ERROR
DESCRIPTION: S The dump operation cannot be executed because the requesting user (%s) does not have superuser privilege. Superuser privilege is required to dump objects from a docbase.
CAUSE: The user does not have superuser privilege. Because DUMP bypasses permission checks, we require that the user executing the dump have superuser privilege.
ACTION: The current user cannot use the dump operation.
PARAMS: The name of the user executing the dump operation.

ERROR: [DM_DUMP_E_MAP_ARGS]

SEVERITY: ERROR
DESCRIPTION: DL Error in dmGetDumpMap call, bad parameters to operation. Handle: %s, argument ptr: %d. The server RPC dmGetDumpMap call was made with bad parameters from the DMCL.
CAUSE: Likely a bug in the DMCL.
ACTION: Check that the server and dmcl are compatible for the current operation.
PARAMS: %1 – handle for object for which map was requested %2 – the option argument object

ERROR: [DM_DUMP_E_CANT_READ_DUMP_RECS]

SEVERITY: ERROR
DESCRIPTION: Error reading dump records from dmi_dump_object_record. The server was attempting to query the dmi_dump_object_record table to determine which objects have already been dumped by this dump operation. The attempt to read from the table failed.
CAUSE: A query failed.
ACTION: Check the error log for error messages logged by the object manager which may give more detail on the problem. Check the rdbms log for errors.
PARAMS: None

ERROR: [DM_DUMP_E_INVALID_TYPE]

SEVERITY: ERROR
DESCRIPTION: S The type %s supplied by user is invalid.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DUMP_E_RECORD_SAVE_FAILED]

SEVERITY: ERROR
DESCRIPTION: S Save of dump record for object %s failed — dump terminated
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DUMP_E_ROOTSET_COLL]

SEVERITY: ERROR
DESCRIPTION: Error dumping result collection.
CAUSE: Failure in dump processing
ACTION: Check the error log for other error messages which should give more detail on the problem. If the error appears transient (dbms or resource problem) the dump can be continued by resaving the same dump record.
PARAMS: None

ERROR: [DM_DUMP_E_FILE_EXISTS]

SEVERITY: ERROR
DESCRIPTION: S Could not open new output dumpfile. File %s already exists. Dump will not overwrite an existing file.
CAUSE: Dump command was called with a file_name that already existed. Dump will not overwrite an existing file.
ACTION: Move or remove the existing file and re-execute the dump operation.
PARAMS: The name of the dumpfile.

ERROR: [DM_DUMP_E_DUMP_OBJECT]

SEVERITY: ERROR
DESCRIPTION: S An Error occurred dumping object with id: %s.
CAUSE: Failure in dump processing
ACTION: Check the error log for other error messages which should give more detail on the problem. If the error appears transient (dbms or resource problem) the dump can be continued by resaving the same dump record.
PARAMS: %1 – id of object being dumped when the error was encountered

ERROR: [DM_DUMP_E_DUMP_RELATED_OBJECT]

SEVERITY: ERROR
DESCRIPTION: S Error dumping objects related to %s. This error message is given on some failures encountered in a dump while trying to dump objects related to one just written to the dump file. It should be accompanied by a preceeding error message which will give a more detailed reason.
CAUSE: Some internal error.
ACTION: Check the error log for other error messages which should give more detail on the problem.
PARAMS: %1 – The object id of the object which triggered the dump of related objects.

ERROR: [DM_DUMP_E_CANT_COUNT_ROOT_SET]

SEVERITY: ERROR
DESCRIPTION: S Query to count objects to be dumped failed. \nQuery was: %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DUMP_W_UNABLE_TO_FETCH_TYPE]

SEVERITY: WARNING
DESCRIPTION: S Could not fetch type %s
CAUSE: A dm_type object could not be fetched.
ACTION: Verify if the type definition is consistent in the repository by fetching the type.
PARAMS:

ERROR: [DM_DUMP_W_FORCEPLAN_FAILED]

SEVERITY: WARNING
DESCRIPTION: S Could not turn on FORCEPLAN. %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DUMP_W_UNFORCEPLAN_FAILED]

SEVERITY: WARNING
DESCRIPTION: S Could not turn off FORCEPLAN. %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DUMP_W_OBJ_NOT_EXIST]

SEVERITY: WARNING
DESCRIPTION: D Skipping reference to object %s. Object does not exist. The dump operation followed an object id pointer to an object that does not exist. The dump operation will continue, but that object cannot be dumped.
CAUSE: Referenced object does not exist.
ACTION: Look for references to this object in the docbase. Ensure that if data is loaded, the objects which refer to this nonexistent object can be used properly.
PARAMS: %1 – handle for object the server was attempting to dump.

ERROR: [DM_DUMP_T_DUMPMAP_ADDEXCEPTION]

SEVERITY: TRACE
DESCRIPTION: DD Add %s as an exception object for object %s.
CAUSE: Informational message. Written in GetDumpMap operation as objects are added to the map if trace level for DM_DUMP_FACILITY is >= 1.
ACTION:
PARAMS: %1 – handle for object being added to map %2 – handle for object which triggered the addition of this new object

ERROR: [DM_DUMP_T_QUERY]

SEVERITY: TRACE
DESCRIPTION: S Executing query statement: %s Will show up at level 5
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DUMP_T_REPL_4]

SEVERITY: TRACE
DESCRIPTION: SL Skipping object ID=%s, i_vstamp=%ld
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DUMP_T_REPL_1]

SEVERITY: TRACE
DESCRIPTION: LFF Number of objects looked up=%ld, total lookup time=%lf ms, avg time=%lf ms
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DUMP_T_DUMPMAP_ADDBEFORE]

SEVERITY: TRACE
DESCRIPTION: DD Add %s, before object %s.
CAUSE: Informational message. Written in GetDumpMap operation as objects are added to the map if trace level for DM_DUMP_FACILITY is >= 1.
ACTION:
PARAMS: %1 – handle for object being added to map %2 – handle for object which triggered the addition of this new object

ERROR: [DM_DUMP_T_RELATE]

SEVERITY: TRACE
DESCRIPTION: S Dumping the objects referenced by the following object: %s Will show up at level 1
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DUMP_T_DUMPMAP_ADD]

SEVERITY: TRACE
DESCRIPTION: D Add object %s.
CAUSE: Informational message. Written in GetDumpMap operation as objects are added to the map if trace level for DM_DUMP_FACILITY is >= 1.
ACTION:
PARAMS: %1 – handle for object being added to map

ERROR: [DM_DUMP_T_OBJECT_START]

SEVERITY: TRACE
DESCRIPTION: S Start object dump, id = %s#[[[
CAUSE: Informational message. Written before dumping an object.
ACTION:
PARAMS: %1 – handle for object being processed

ERROR: [DM_DUMP_T_DUMPMAP_ADDAFTER]

SEVERITY: TRACE
DESCRIPTION: DD Add %s, after object %s.
CAUSE: Informational message. Written in GetDumpMap operation as objects are added to the map if trace level for DM_DUMP_FACILITY is >= 1.
ACTION:
PARAMS: %1 – handle for object being added to map %2 – handle for object which triggered the addition of this new object

ERROR: [DM_DUMP_T_REPL_2]

SEVERITY: TRACE
DESCRIPTION: LFF Number of objects inserted=%ld, total insert time=%lf ms, avg time=%lf ms
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DUMP_T_TYPE_END]

SEVERITY: TRACE
DESCRIPTION: S End type dump, name = %s#]]]
CAUSE: Informational message. Written after dumping a type.
ACTION:
PARAMS: %1 – name for a type being dumped

ERROR: [DM_DUMP_T_TYPE_START]

SEVERITY: TRACE
DESCRIPTION: S Start type dump, name = %s#[[[
CAUSE: Informational message. Written before dumping a type.
ACTION:
PARAMS: %1 – name for a type being dumped

ERROR: [DM_DUMP_T_DUMPMAP_PROCESS]

SEVERITY: TRACE
DESCRIPTION: D Processing Object %s.
CAUSE: Informational message. Written in GetDumpMap operation as the server begins to search for objects related to the the logged one. Written if trace level for DM_DUMP_FACILITY is >= 1.
ACTION:
PARAMS: %1 – handle for object being processed

ERROR: [DM_DUMP_T_REPL_3]

SEVERITY: TRACE
DESCRIPTION: S Executing SQL stmt: %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DUMP_T_TYPE_NAME]

SEVERITY: TRACE
DESCRIPTION: S Dumping type, name = %s Will show up at level 8
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DUMP_T_OBJECT_END]

SEVERITY: TRACE
DESCRIPTION: S End object dump, id = %s#]]] %1 – handle for object being processed
CAUSE: Informational message. Written after dumping an object.
ACTION:
PARAMS:

ERROR: [DM_DUMP_T_DUMPMAP_DUPLICATE]

SEVERITY: TRACE
DESCRIPTION: D Object %s already exists in map.
CAUSE: Informational message. Written in GetDumpMap operation when an object is encountered for a second time if trace level for DM_DUMP_FACILITY is >= 1.
ACTION:
PARAMS: %1 – handle for object being added to map

ERROR: [DM_DUMP_T_LOG_TYPE]

SEVERITY: TRACE
DESCRIPTION: Writing type information into the dump file. Will show up at level 1
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DUMP_T_REPL_5]

SEVERITY: TRACE
DESCRIPTION: SI Starting dump: mode=%s, object count=%d
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DUMP_T_DUMPMAP_ADDPRIMARY]

SEVERITY: TRACE
DESCRIPTION: DD Add %s as a primary object for object %s.
CAUSE: Informational message. Written in GetDumpMap operation as objects are added to the map if trace level for DM_DUMP_FACILITY is >= 1.
ACTION:
PARAMS: %1 – handle for object being added to map %2 – handle for object which triggered the addition of this new object

ERROR: [DM_DUMP_T_DUMPMAP]

SEVERITY: TRACE
DESCRIPTION: DS Starting GetDumpMap operation on object %s. Option parameters (%s).
CAUSE: Informational message. Written at start of GetDumpMap if trace level for DM_DUMP_FACILITY is >= 1.
ACTION:
PARAMS: %1 – handle for object for which map was requested %2 – parameters to operation

ERROR: [DM_DUMP_T_DUMPMAP_ADDPEER]

SEVERITY: TRACE
DESCRIPTION: DD Add %s, peer of object %s.
CAUSE: Informational message. Written in GetDumpMap operation as objects are added to the map if trace level for DM_DUMP_FACILITY is >= 1.
ACTION:
PARAMS: %1 – handle for object being added to map %2 – handle for object which triggered the addition of this new object

ERROR: [DM_DUMP_T_OBJ_ID]

SEVERITY: TRACE
DESCRIPTION: S Dumping object, id = %s Will show up at level 8
CAUSE:
ACTION:
PARAMS:

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: