IT blok - Michal Šika

kutilovo živobytí

Documentum 6.6 – chybové zprávy – část 2.

V druhé části výčtu chybových hlášení systému Documentum verze 6.6 od EMC si ukážeme chyby DM_DOCBROKER – DM_INTERNAL v abecedním pořadí. Jedná se jak o ERROR tak i o WARNING chybová hlášení.
Doufám, že se vám podaří najít odpovídající řešení vašich problémů… Tento post navazuje na předchozí část.

DM_DOCBROKER DM_DOCUMENT DM_DUMP
DM_EVENT DM_EXCEPTION DM_EXPRESSION
DM_FILTER DM_FOLDER DM_FOREIGN
DM_FORMAT DM_FT_INDEX DM_FULLTEXT
DM_GROUP DM_IDITR DM_INBOX
DM_INFO DM_INTERNAL

DM_DOCBROKER

ERROR: [DM_DOCBROKER_E_LISTEN_FAIL]

SEVERITY: ERROR
DESCRIPTION: SS Failure to register the docbroker process on network address: (%s). Error: (%s)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_START_NETWISE]

SEVERITY: ERROR
DESCRIPTION: SS The docbroker failed to start due to an error returned by the Netwise networking subsystem. Failed API: %s. Error specifics: %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_DMCL_INI_MAC_MISSING]

SEVERITY: ERROR
DESCRIPTION: Failure to connect to a DocBroker (no dmcl.ini). The search rules are: 1) working path 2) preferences path 3) Documentum: 4) Documentum:config
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_NO_SERVERS_FOR_DOCBASE]

SEVERITY: ERROR
DESCRIPTION: SS The DocBroker running on host (%s) does not know of a server for the specified docbase (%s)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_BAD_NET_STREAM]

SEVERITY: ERROR
DESCRIPTION: Unable to process a request. The stream image was unparsable.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_DMCL_INI_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: Unable to connect to a DocBroker because your dmcl.ini file cannot be found. Please see your system administrator as this file is needed to specify the host name of your DocBroker.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_NO_DOCBASES]

SEVERITY: ERROR
DESCRIPTION: S There are not any Docbases registered with the DocBroker running on host (%s).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_DOCBASE_SYNTAX_ORDER]

SEVERITY: ERROR
DESCRIPTION: S Invalid syntax for the docbase connect string (%s). The docbase/server name separator, . must preceed the server name/host name separator @.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_DMCL_MISSING_HOST]

SEVERITY: ERROR
DESCRIPTION: S Unable to connect to a DocBroker because your dmcl.ini file (%s) does not specify a section DOCBROKER_PRIMARY with a value for host
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_DOCBASE_NAME_LENGTH]

SEVERITY: ERROR
DESCRIPTION: SII The connect string (%s) is too long at (%d) characters. Maximum length is restricted to (%d) characters
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_BAD_PROTOCOL]

SEVERITY: ERROR
DESCRIPTION: The DocBroker protocol you specified is invalid
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_NO_SERVERS_QUALIFY]

SEVERITY: ERROR
DESCRIPTION: SS The DocBroker running on host (%s) does not know of a local active server for the specified docbase (%s)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_UNKNOWN_DOCBROKER_MAP_NAME]

SEVERITY: ERROR
DESCRIPTION: S Unknown docbroker map name: %s
CAUSE: application specified a docbroker map name that was unknown
ACTION: Specify either mn_cs_map or mn_acs_map as the docbroker map name, or dont specify a docbroker map name as its optional.
PARAMS:

ERROR: [DM_DOCBROKER_E_DMCL_INI_WIN_MISSING]

SEVERITY: ERROR
DESCRIPTION: Failure to connect to a DocBroker (no dmcl.ini). The search rules are: 1) working directory 2) windows directory
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_NETWORK_ERROR]

SEVERITY: ERROR
DESCRIPTION: SS An error occured performing a network operation: (%s). Network specific error: (%s).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_DMCL_INI_WIN32_MISSING]

SEVERITY: ERROR
DESCRIPTION: DocBroker connection failed (no dmcl.ini). Search rules: 1) %%DMCL_CONFIG%% specifies a file 2) current directory 3) %%DOCUMENTUM%% specifies a directory with dmcl.ini 4) Windows dir.
CAUSE: dmcl is unable to determine which host has a running docbroker
ACTION: configure a valid dmcl.ini file
PARAMS:

ERROR: [DM_DOCBROKER_E_MAP_CACHE_OVERFLOW]

SEVERITY: ERROR
DESCRIPTION: S %s map cache overflow.
CAUSE: application access too many docbases/servers.
ACTION: Application has to wait and try to connect later when there are fewer connections.
PARAMS:

ERROR: [DM_DOCBROKER_E_SEND_LAUNCH]

SEVERITY: ERROR
DESCRIPTION: S Unable to send checkpoint to docbroker due to an operating system error: %s.
CAUSE: the operating system refused to launch the process/thread to perform the checkpoint
ACTION: Verify the operating system has enough resources
PARAMS:

ERROR: [DM_DOCBROKER_E_CONNECT_FAILED]

SEVERITY: ERROR
DESCRIPTION: S Unable to connect to DocBroker. Clients please check your dmcl.ini file for a correct host. Server please check your server.ini or target attributes in server config. Network address: (%s).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_INVALID_HOST]

SEVERITY: ERROR
DESCRIPTION: S Invalid host name (%s).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_REGISTER_IN_USE]

SEVERITY: ERROR
DESCRIPTION: IS Failure to start the docbroker process. Error indicates that there is already a docbroker process running on this host on port: (%d). Error Details: %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_NOT_IMPLEMENTED]

SEVERITY: ERROR
DESCRIPTION: S The Docbroker request you generated is not implemented in this release. (%s)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_REQUEST_FAILED]

SEVERITY: ERROR
DESCRIPTION: S The request to the Docbroker failed due to the following error: (%s).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_CHECKPOINT_NOT_SENT]

SEVERITY: ERROR
DESCRIPTION: S The docbroker checkpoint was not sent for the following reason: %s
CAUSE: There was an error fetching either the server config or docbase config when trying to send the checkpoint.
ACTION: Ensure that the database is running and restart the docbase if necessary.
PARAMS:

ERROR: [DM_DOCBROKER_E_EMPTY_NAME]

SEVERITY: ERROR
DESCRIPTION: S The docbase name is required and is not specified in the docbase connect string (%s)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_REQUEST_STATUS]

SEVERITY: ERROR
DESCRIPTION: SSS The docbroker on host (%s) returned a failed status for the request: (%s). Error message from docbroker: (%s).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_DOCBASE_SYNTAX_MULTI]

SEVERITY: ERROR
DESCRIPTION: S Invalid syntax for the docbase connect string (%s). The docbase/host name separator, @, and the docbase name/server name separator . can only appear once.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_REQUEST_FAILED_E]

SEVERITY: ERROR
DESCRIPTION: The Docbroker request failed.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_CONN_REJ_1]

SEVERITY: ERROR
DESCRIPTION: I Docbroker: Refusing service to client on connection %i — too many clients
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_INVALID_PORT]

SEVERITY: ERROR
DESCRIPTION: I Invalid port number (%d).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_MEMORY_EXHAUSTED]

SEVERITY: ERROR
DESCRIPTION: I Memory exhausted allocating %d bytes
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_NO_SERVERS_FOR_SPECIFIC]

SEVERITY: ERROR
DESCRIPTION: SS The DocBroker running on host (%s) indicates the specific server for the docbase (%s) you specified was not found.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_REQUEST_STREAM]

SEVERITY: ERROR
DESCRIPTION: S The request stream from the client could not be loaded. First 80 bytes: (%s).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_DMCL_INI_UNIX_MISSING]

SEVERITY: ERROR
DESCRIPTION: Failure to connect to DocBroker (no dmcl.ini). The search rules are: 1) $DMCL_CONFIG specifies a file 2) current directory 3) $DOCUMENTUM specifies a directory with dmcl.ini.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_REPLY_STREAM]

SEVERITY: ERROR
DESCRIPTION: S The reply stream from the DocBroker could not be loaded. First 80 bytes: (%s).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_REGISTER_FAIL]

SEVERITY: ERROR
DESCRIPTION: IS Failure to register the docbroker process on socket port: (%d). Error: %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_HOST_NAME]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_CONNECT_FAILED_EX]

SEVERITY: ERROR
DESCRIPTION: S Unable to connect to DocBroker. Clients please check your dfc.properties file for a correct host. Server please check your server.ini or target attributes in server config. Network address: (%s). the following errors are considered internal or not expected
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_E_OPEN_IFILE]

SEVERITY: ERROR
DESCRIPTION: SS Error opening initialization file: %s. %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_W_CHECKPOINT_RUNNING]

SEVERITY: WARNING
DESCRIPTION: I Docbroker Checkpoint was not sent. The previously launched Docbroker Checkpoint (pid = %d) is still running. Check your server log for additional messages.
CAUSE: The thread/process that was started at the previous checkpoint time is still running
ACTION: Check for errors, such as network timeouts, in your server log, also check to see whether the process is still in the system.
PARAMS:

ERROR: [DM_DOCBROKER_W_UNKNOWN_REQUEST]

SEVERITY: WARNING
DESCRIPTION: I Unknown request ordinal: %d
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_W_DBG_BYPASS_BY_SRV]

SEVERITY: WARNING
DESCRIPTION: SSSL Warning you are using a local override to specifiy the network address of your server for docbase (%s). Values used: host (%s), service (%s) and docbase ID (%d).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_W_REQUEST_STATUS]

SEVERITY: WARNING
DESCRIPTION: SSS The docbroker on host (%s) returned a failed status for the request: (%s). Error message from docbroker: (%s).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_W_FILE_CHECK]

SEVERITY: WARNING
DESCRIPTION: SS The file containing your docbroker password, %s, can be accessed by other users. The operating system error was %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_W_DBG_BYPASS_BY_RAW]

SEVERITY: WARNING
DESCRIPTION: SSIL Warning you are using a local override to specifiy the network address of your server for docbase (%s). Values used: host (%s), port (%d) and docbase ID (%d).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_W_CONNECT_FAILED]

SEVERITY: WARNING
DESCRIPTION: S Unable to make network connection to the DocBroker at network address (%s). Please check your dmcl.ini file for a correct host.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_W_FILE_PERMISSION]

SEVERITY: WARNING
DESCRIPTION: S The security of file containing your docbroker password: %s is readable by others.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_W_NO_LOCAL_SERVERS]

SEVERITY: WARNING
DESCRIPTION: SS The DocBroker running on host (%s) indicates the server map for docbase (%s), does not contain any servers with local proximity
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_W_NO_OPEN_SERVERS]

SEVERITY: WARNING
DESCRIPTION: SS The DocBroker running on host (%s) indicates the server map for docbase (%s), does not contain any servers with status Open
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_W_EXEC_POOL_FULL]

SEVERITY: WARNING
DESCRIPTION: The execution context pool is full.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_W_SHUTDOWN_REQ_REJ]

SEVERITY: WARNING
DESCRIPTION: SS A shutdown request from user (%s) on host (%s) was rejected due to an invalid password.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_I_SHUT_DOWN]

SEVERITY: INFORMATION
DESCRIPTION: The Docbroker is shutting down.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_I_REGISTERED_PORT]

SEVERITY: INFORMATION
DESCRIPTION: I The Docbroker registered using port (%d).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_I_REGISTERED]

SEVERITY: INFORMATION
DESCRIPTION: SI The Docbroker registered using service: (%s) with port: (%d).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_I_LISTENING]

SEVERITY: INFORMATION
DESCRIPTION: S The Docbroker is listening on network address: (%s)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_I_SECURITY_ENABLED]

SEVERITY: INFORMATION
DESCRIPTION: Shutdown security enabled via password.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_I_START]

SEVERITY: INFORMATION
DESCRIPTION: I Docbroker has started. Process id: %d
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_I_SHUTDOWN_REQUESTED]

SEVERITY: INFORMATION
DESCRIPTION: SS Shutdown has been requested from user: %s on host: %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_I_DMCL_INI_WIN32_SEARCH1]

SEVERITY: INFORMATION
DESCRIPTION: SSSS %%DMCL_CONFIG%%==(%s), current directory==(%s), %%DOCUMENTUM%%==(%s), Windows directory==(%s)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_DOCBROKER_I_PROJECTING]

SEVERITY: INFORMATION
DESCRIPTION: SIS Sending information to Docbroker located on host (%s) with port (%d). Information: (%s).
CAUSE:
ACTION:
PARAMS:

nahoru

DM_DOCUMENT

ERROR: [DM_DOCUMENT_F_INIT3]

SEVERITY: FATAL
DESCRIPTION: The type manager returned an error storing the dmDocument type.
CAUSE: Unknown.
ACTION: Look at the error logged by the type manager. Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_DOCUMENT_F_INIT1]

SEVERITY: FATAL
DESCRIPTION: The dmDocument type was found in the database without a version stamp.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_DOCUMENT_F_TYPE_CONVERSION]

SEVERITY: FATAL
DESCRIPTION: II Failed to convert type dm_document from version %d to version %d.
CAUSE: Type conversion failed.
ACTION: Report the problem. $Id: dmdoccnf.e,v 5.6 2003/03/07 18:55:21 zfan Exp $ dmDocbaseConfig class errors
PARAMS:

ERROR: [DM_DOCUMENT_F_INIT2]

SEVERITY: FATAL
DESCRIPTION: II Version stamp %d was expected to be %d.
CAUSE: The version stamp that the dmDocument object software expected was different from the actual version stamp in the database.
ACTION: You must upgrade your DocuServer database to conform to the software that you are running. If your software and data are consistent, then report a bug. Also, Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_DOCUMENT_E_NO_DESTROYER_PATH]

SEVERITY: ERROR
DESCRIPTION: S Unable to retrieve the file_system_path attribute of the dm_location named %s
CAUSE: The named dm_location does not contain a file system path
ACTION: Ammend the dm_location
PARAMS:

ERROR: [DM_DOCUMENT_E_NO_STAGE]

SEVERITY: ERROR
DESCRIPTION: SS Staging location named %s is not defined for %s document.
CAUSE: staging location is not defined
ACTION: Define staging location before saving staged document.
PARAMS:

ERROR: [DM_DOCUMENT_E_NO_STG_LOC_PATH]

SEVERITY: ERROR
DESCRIPTION: S Unable to retrieve the file_system_path attribute of the dm_location named %s
CAUSE: The named dm_location does not contain a file system path
ACTION: Ammend the dm_location
PARAMS:

ERROR: [DM_DOCUMENT_E_STG_DESTROY]

SEVERITY: ERROR
DESCRIPTION: IS Non-zero status returned from stage destroyer: %d. Command line was: %s.
CAUSE: A call to system() with the given command line returned a non-zero status.
ACTION: Check to ensure that the server config attribute, stage_destroyer_location, references a valid location and path. Check the file permissions of that path.
PARAMS:

nahoru

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:

nahoru

DM_EVENT

ERROR: [DM_EVENT_F_INIT9]

SEVERITY: FATAL
DESCRIPTION: SS Error renaming the table %s to %s
CAUSE: DB Error.
ACTION: check the RDBMS.
PARAMS:

ERROR: [DM_EVENT_F_INIT3]

SEVERITY: FATAL
DESCRIPTION: The type manager returned an error storing the dmEvent type.
CAUSE: Unknown.
ACTION: Look at the error logged by the type manager. Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_EVENT_F_INIT6]

SEVERITY: FATAL
DESCRIPTION: Could not access the registry data
CAUSE: DB Error
ACTION: Check the RDBMS
PARAMS:

ERROR: [DM_EVENT_F_INIT4]

SEVERITY: FATAL
DESCRIPTION: Could not remove the registry type
CAUSE: Unknown.
ACTION: Look at the error logged by the type manager. Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_EVENT_F_INIT1]

SEVERITY: FATAL
DESCRIPTION: The dmEvent type was found in the database without a version stamp.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_EVENT_F_INIT2]

SEVERITY: FATAL
DESCRIPTION: II Version stamp %d was expected to be %d.
CAUSE: The version stamp that the dmEvent object software expected was different from the actual version stamp in the database.
ACTION: You must upgrade your DocuServer database to conform to the software that you are running. If your software and data are consistent, then report a bug.
PARAMS:

ERROR: [DM_EVENT_F_INIT8]

SEVERITY: FATAL
DESCRIPTION: Error creating the temporary registry table
CAUSE: DB Error.
ACTION: check the RDBMS.
PARAMS:

ERROR: [DM_EVENT_F_INIT5]

SEVERITY: FATAL
DESCRIPTION: Could not create the new registry type
CAUSE: Unknown.
ACTION: Look at the error logged by the type manager. Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_EVENT_F_INIT7]

SEVERITY: FATAL
DESCRIPTION: Could not save the new registry entry
CAUSE: Unknown.
ACTION: check the RDBMS.
PARAMS:

ERROR: [DM_EVENT_E_MAIL_LAUNCH]

SEVERITY: ERROR
DESCRIPTION: S Please contact your system administrator. Unable to send mail during processing of your event. The dm_method named %s could not be launched.
CAUSE: The dm_method object encountered errors trying to launch the verb.
ACTION: Check the server log and server configuration.
PARAMS:

ERROR: [DM_EVENT_E_DIRECTORY_ACCESS_S]

SEVERITY: ERROR
DESCRIPTION: SSS Error accessing your event directory. The dm_location object named %s that defines your event directory (%s) is in error. Operating System error was: %s
CAUSE: Operating system returned a failed status when verifying the event directory
ACTION: Check for proper file system definition of your dm_location object
PARAMS:

ERROR: [DM_EVENT_E_CURSOR_FAIL]

SEVERITY: ERROR
DESCRIPTION: SS The following query %s generated the following database %s error
CAUSE: Used for internal purpose.
ACTION: Report to your sys admin.
PARAMS:

ERROR: [DM_EVENT_E_FLUSH_REGISTRY_CACHE_BAD_KEY]

SEVERITY: ERROR
DESCRIPTION: S A cache key (%s) was supplied to the flush registrycache API call that is not a legal type name.
CAUSE: The cache key you specified is not a legal type name.
ACTION: Supply a key that is the name of an object type.
PARAMS:

ERROR: [DM_EVENT_E_DBERROR]

SEVERITY: ERROR
DESCRIPTION: SSSS Event manager was unable to perform %s on %s for event %s.nDatabase error:n%s
CAUSE: Event manager was attempting a database operation which failed.
ACTION: Ensure that all is well with the underlying database tables. Check the dmi_registry_s table.
PARAMS:

ERROR: [DM_EVENT_E_INVALID_ID]

SEVERITY: ERROR
DESCRIPTION: DS Invalid handle (%s) for system event %s.
CAUSE: An invalid event name is specified.
ACTION: Retry the operation with valid event name.
PARAMS:

ERROR: [DM_EVENT_E_CANT_REGISTER_TYPE_EVENT]

SEVERITY: ERROR
DESCRIPTION: SS It is not permitted to register for event %s on type %s.
CAUSE: Only certain types and events can be registered. See the documentation
ACTION: Consult your system administrator.
PARAMS:

ERROR: [DM_EVENT_E_NEED_SU_OR_SYS_TO_UNREG]

SEVERITY: ERROR
DESCRIPTION: SS The current user (%s) needs to have superuser or sysadmin privilege to unregister %s user event.
CAUSE: Must have Superuser or SysAdmin privilege to perform this operation.
ACTION: Consult your system administrator.
PARAMS:

ERROR: [DM_EVENT_E_CANT_REGISTER_UNLESS_MATERIALIZED]

SEVERITY: ERROR
DESCRIPTION: SS Could not register the specified %s event for %s because it is an un-materialized lightweight object.
CAUSE: It is not allowed to register a lightweight object for event notification before it is materialized
ACTION: Materialize the lightweight object and try again.
PARAMS:

ERROR: [DM_EVENT_E_NOT_REGISTERED]

SEVERITY: ERROR
DESCRIPTION: SSS User %s has not registered event %s for sysobject named %s.
CAUSE: Specified event is not registered for this user.
ACTION: Check to see if either the event or the sysobj ID is invalid.
PARAMS:

ERROR: [DM_EVENT_E_SEND_LAUNCH]

SEVERITY: ERROR
DESCRIPTION: S Please contact your system administrator. Unable to send mail during processing of your event. The dm_method named %s could not be launched.
CAUSE: The dm_method object encountered errors trying to launch the verb.
ACTION: Check the server log and server configuration.
PARAMS:

ERROR: [DM_EVENT_E_EVENT_ALREADY_REGISTERED]

SEVERITY: ERROR
DESCRIPTION: SSS Event %s on object %s is already registered for user %s.
CAUSE: The object already has the requested event registered
ACTION: No need to register for the same event twice
PARAMS:

ERROR: [DM_EVENT_E_CANT_REGISTER]

SEVERITY: ERROR
DESCRIPTION: SS Could not register the specified %s event for %s document/object.
CAUSE: The specified event could not be registered. Most likely bad event name specified.
ACTION: Check the event name and try again.
PARAMS:

ERROR: [DM_EVENT_E_MAIL_RUN]

SEVERITY: ERROR
DESCRIPTION: SSS Please contact your system administrator. Unable to send mail during processing of your event. The dm_method named %s reported a non-zero status from the program: (%s) with arguments: (%s).
CAUSE: The dm_method object encountered errors trying to launch the verb.
ACTION: Check the server log and server configuration.
PARAMS:

ERROR: [DM_EVENT_E_DIRECTORY_ACCESS_M]

SEVERITY: ERROR
DESCRIPTION: SSSS Error accessing your event directory. The dm_location object named %s and/or the dm_mount_point object named %s that defines your event directory (%s) is in error. Operating System error was: %s
CAUSE: Operating system returned a failed status when verifying the event directory.
ACTION: Ensure that your NFS enabled capability is defined correctly. If your client does not have NFS access to the server disk defined by the mount point, you must have NFS enabled set to FALSE. Check for NFS enabled in your session config object, server config, and dmcl.ini file. If you do have NFS access, Check for proper file system definition in your dm_location object. If the location is defined correctly, check that the mount point is mounted on your client machine.
PARAMS:

ERROR: [DM_EVENT_E_CANT_UNREGISTER]

SEVERITY: ERROR
DESCRIPTION: SSS User %s could not unregister the specified %s event for %s document/object.
CAUSE: The specified event could not be unregistered. Most likely bad event name specified.
ACTION: Check the event name and try again. Could be that the specific user has not registered for this event.
PARAMS:

ERROR: [DM_EVENT_E_CANT_NOTIFY]

SEVERITY: ERROR
DESCRIPTION: SS Could not send notification for event %s for %s document/object.
CAUSE: The specified event could not be notified. Most likely bad event name specified or failed database operation.
ACTION: Check the event name and try again.
PARAMS:

ERROR: [DM_EVENT_E_NEED_SYS_TO_REG_TYPE]

SEVERITY: ERROR
DESCRIPTION: SSS The current user (%s) needs to have superuser or sysadmin privilege to register event %s on type %s.
CAUSE: Must have Superuser or SysAdmin privilege to perform this operation.
ACTION: Consult your system administrator.
PARAMS:

ERROR: [DM_EVENT_E_INVALID_EVENT]

SEVERITY: ERROR
DESCRIPTION: S Invalid system event %s.
CAUSE: An invalid event name is specified.
ACTION: Retry the operation with valid event name.
PARAMS:

ERROR: [DM_EVENT_E_CANT_FIND_OBJ]

SEVERITY: ERROR
DESCRIPTION: SS Could not find the object, name or event %s for id %s
CAUSE: The object identified by the id could not be found for that event.
ACTION: Check the id to make sure that it is a valid sysobject.
PARAMS:

ERROR: [DM_EVENT_E_SEND_RUN]

SEVERITY: ERROR
DESCRIPTION: SSS Please contact your system administrator. Unable to send mail during processing of your event. The dm_method named %s reported a non-zero status from the program: (%s) with arguments: (%s).
CAUSE: The dm_method object encountered errors trying to launch the verb.
ACTION: Check the server log and server configuration.
PARAMS:

ERROR: [DM_EVENT_W_MAIL_METHOD]

SEVERITY: WARNING
DESCRIPTION: S The method %s specified in the mail_method attribute of the server config object is not a valid method. The server will use the dm_event_sender method to send mail.
CAUSE: The mail_method attribute of the server config object is set to an invalid method.
ACTION: Set the mail_method attribute as appropriate.
PARAMS:

ERROR: [DM_EVENT_W_INIT10]

SEVERITY: WARNING
DESCRIPTION: S Error dropping the table %s
CAUSE: DB Error.
ACTION: manually remove table.
PARAMS:

ERROR: [DM_EVENT_W_SEND_LAUNCH]

SEVERITY: WARNING
DESCRIPTION: S Please contact your system administrator. Unable to send mail during processing of your event. The dm_method named %s could not be launched.
CAUSE: The dm_method object encountered errors trying to launch the verb.
ACTION: Check the server log and server configuration.
PARAMS:

ERROR: [DM_EVENT_W_SEND_RUN]

SEVERITY: WARNING
DESCRIPTION: SSS Please contact your system administrator. Unable to send mail during processing of your event. The dm_method named %s reported a non-zero status from the program: (%s) with arguments: (%s).
CAUSE: The dm_method object encountered errors trying to launch the verb.
ACTION: Check the server log and server configuration.
PARAMS:

nahoru

DM_EXCEPTION

ERROR: [DM_EXCEPTION_E_SYS_FATAL_ACCESS]

SEVERITY: ERROR
DESCRIPTION: SSSS A system exception (%s) occurred. Code address: (%s). Attempt to %s data at address %s.
CAUSE: a bug in the server, or an external dll
ACTION: if necessary re-start server
PARAMS:

ERROR: [DM_EXCEPTION_E_HEAP_TAG]

SEVERITY: ERROR
DESCRIPTION: IS Error during heap validation. Thread id: %d. Error: %s.
CAUSE: Internal memory corruption
ACTION: Monitor server log for failures – if too many failures occur restart server
PARAMS:

ERROR: [DM_EXCEPTION_E_MEMORY_EXHAUSTED]

SEVERITY: ERROR
DESCRIPTION: LL Unable to allocate %d bytes. Maximum heap capacity %d bytes
CAUSE: the heap is too small
ACTION: raise the size of the heap in server.ini
PARAMS:

ERROR: [DM_EXCEPTION_E_SYS_FATAL]

SEVERITY: ERROR
DESCRIPTION: SS A system exception (%s) occurred. Instruction: (%s)
CAUSE: a bug in the server, or an external dll
ACTION: if necessary re-start server
PARAMS:

ERROR: [DM_EXCEPTION_E_DOCU_FATAL]

SEVERITY: ERROR
DESCRIPTION: S A Documentum exception (%s) occurred.
CAUSE: a bug in the server, or an external dll
ACTION: if necessary re-start server
PARAMS:

ERROR: [DM_EXCEPTION_W_SHUTDOWN_SESSION]

SEVERITY: WARNING
DESCRIPTION: S A session showdown exception has occurred. Shutdown type: (%s)
CAUSE: a session showdown has requested. The session will be terminated.
ACTION:
PARAMS:

ERROR: [DM_EXCEPTION_W_SHUTDOWN_SERVER]

SEVERITY: WARNING
DESCRIPTION: A server showdown exception has occurred.
CAUSE: a server showdown has requested. The server will be terminated.
ACTION:
PARAMS:

nahoru

DM_EXPRESSION

ERROR: [DM_EXPRESSION_F_FUNC_EXPR_TYPE_INIT]

SEVERITY: FATAL
DESCRIPTION: S Failed to initialize type %s.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_EXPRESSION_F_EXPRESSION_MANAGER_INTERNAL]

SEVERITY: FATAL
DESCRIPTION: S Internal error (%s) in the Expression Manager.
CAUSE: This is an internal error.
ACTION: Report this error to Documentum sysadmins.
PARAMS: The first parameter is the internal error message.

ERROR: [DM_EXPRESSION_F_COND_ID_EXPR_TYPE_INIT]

SEVERITY: FATAL
DESCRIPTION: S Failed to initialize type %s.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_EXPRESSION_F_LITERAL_EXPR_TYPE_INIT]

SEVERITY: FATAL
DESCRIPTION: S Failed to initialize type %s.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_EXPRESSION_F_CANNOT_CLONE_EXPRESSION]

SEVERITY: FATAL
DESCRIPTION: D Cannot clone expression object with ID %s.
CAUSE: This is an internal error.
ACTION: Report this error to Documentum sysadmins.
PARAMS: The parameter is the object id of the expression object.

ERROR: [DM_EXPRESSION_F_COND_EXPR_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: II Type dm_cond_expr has a bad vstamp %d. The current vstamp for dm_cond_expr is supposed to be %d.
CAUSE: The RDBMS table has a bad vstamp.
ACTION: Report this error to Documentum sysadmins.
PARAMS:

ERROR: [DM_EXPRESSION_F_LITERAL_EXPR_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: II Type dm_literal_expr has a bad vstamp %d. The current vstamp for dm_literal_expr is supposed to be %d.
CAUSE: The RDBMS table has a bad vstamp.
ACTION: Report this error to Documentum sysadmins.
PARAMS:

ERROR: [DM_EXPRESSION_F_FUNC_EXPR_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: II Type dm_func_expr has a bad vstamp %d. The current vstamp for dm_func_expr is supposed to be %d.
CAUSE: The RDBMS table has a bad vstamp.
ACTION: Report this error to Documentum sysadmins.
PARAMS:

ERROR: [DM_EXPRESSION_F_EXPRESSION_TYPE_INIT]

SEVERITY: FATAL
DESCRIPTION: S Failed to initialize type %s.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_EXPRESSION_F_BUILTIN_EXPR_TYPE_INIT]

SEVERITY: FATAL
DESCRIPTION: S Failed to initialize type %s.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_EXPRESSION_F_NULL_CODE_OBJECT_ID_FOR_FUNC_EXPR]

SEVERITY: FATAL
DESCRIPTION: D A NULL object id was given for the code object for the dm_expression object with id %s.
CAUSE: This is an internal error.
ACTION: Report this error to Documentum sysadmins.
PARAMS: The parameter is the object id of the expression object. $Id: dmfilter.e,v 5.0 1998/01/10 02:07:42 sol_ora Exp $ Filter class errors

ERROR: [DM_EXPRESSION_F_COND_EXPR_TYPE_INIT]

SEVERITY: FATAL
DESCRIPTION: S Failed to initialize type %s.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_EXPRESSION_F_EXPRESSION_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: II Type dm_expression has a bad vstamp %d. The current vstamp for dm_expression is supposed to be %d.
CAUSE: The RDBMS table has a bad vstamp.
ACTION: Report this error to Documentum sysadmins.
PARAMS:

ERROR: [DM_EXPRESSION_F_BUILTIN_EXPR_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: II Type dm_builtin_expr has a bad vstamp %d. The current vstamp for dm_builtin_expr is supposed to be %d.
CAUSE: The RDBMS table has a bad vstamp.
ACTION: Report this error to Documentum sysadmins.
PARAMS:

ERROR: [DM_EXPRESSION_F_PARSER_INTERNAL_AT]

SEVERITY: FATAL
DESCRIPTION: SII Internal error (%s) at line %d, column %d of expression.
CAUSE: This is an internal error.
ACTION: Report this error to Documentum sysadmins.
PARAMS: The first parameter is the internal error message. The second parameter is the line number within the expression. The third parameter is the column number within the line.

ERROR: [DM_EXPRESSION_F_EXPRESSION_CANT_EXPUNGE]

SEVERITY: FATAL
DESCRIPTION: D Cannot expunge expression object with ID %s.
CAUSE: This is an internal error.
ACTION: Report this error to Documentum sysadmins.
PARAMS: The parameter is the object id of the expression object.

ERROR: [DM_EXPRESSION_F_COND_ID_EXPR_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: II Type dm_cond_id_expr has a bad vstamp %d. The current vstamp for dm_cond_id_expr is supposed to be %d.
CAUSE: The RDBMS table has a bad vstamp.
ACTION: Report this error to Documentum sysadmins.
PARAMS:

ERROR: [DM_EXPRESSION_E_COMPILATION]

SEVERITY: ERROR
DESCRIPTION: IIS The expression compilation attempt failed. Error Number is %d, Error Line is %d and Error Text is %s.
CAUSE: The expression compilation attempt failed.
ACTION: Correct the expression errors and retry compilation.
PARAMS: The first parameter is the error number. The second parameter is the error line. The third parameter is the error text.

ERROR: [DM_EXPRESSION_E_DOCBASIC_UNEXPECTED_RETURN_TYPE]

SEVERITY: ERROR
DESCRIPTION: I The Docbasic Engine has reported a return type of %d that is different than what is expected for the expression.
CAUSE: The resulting return value from executing a docbasic expression is not what was expected.
ACTION: Verify that the expression_text actually evaluates to the appropriate return data type.
PARAMS: The data type of the return value – mapped to the docbasic engines data type definitions.

ERROR: [DM_EXPRESSION_E_DOCBASIC_ENGINE]

SEVERITY: ERROR
DESCRIPTION: II An error has occurred in the docbasic engine in mode %d of type %d.
CAUSE: The docbasic engine has reported an engine error. Most likely this is a memory allocation issue. ACTION:Call Documentum Tech Support for assistence.
ACTION:
PARAMS: integer representation of the error mode and type.

ERROR: [DM_EXPRESSION_E_FUNC_EXPR_INVALID_ROUTINE_ID]

SEVERITY: ERROR
DESCRIPTION: The attribute routine_id is not a valid object id.
CAUSE: The routine_id does not reference a valid sysobject.
ACTION: Use a valid sysobject id.
PARAMS: None.

ERROR: [DM_EXPRESSION_E_PARSER_MALFORMED_NUMBER_AT]

SEVERITY: ERROR
DESCRIPTION: II Malformed numeric literal at line %d, column %d.
CAUSE: The expression contains an illegal numeric literal.
ACTION: Correct the numeric literal at the indicated location.
PARAMS: The first parameter is the line number within the expression. The second parameter is the column number within the line.

ERROR: [DM_EXPRESSION_E_UNABLE_TO_COMPILE]

SEVERITY: ERROR
DESCRIPTION: DDI The Expression Manager encountered a compilation error for expression with id %s. Check the source code stored in routine id %s, page %d.
CAUSE: The expression compilation attempt failed.
ACTION: Look at the source code for the expression to try and understand the compilation error information.
PARAMS: The first parameter is the object id of the expression object. The second parameter is the object id of the sysobject that contains the source code. The third parameter is the source page where the source code is located.

ERROR: [DM_EXPRESSION_E_EXECUTION_INVALID_OBJECT_ID]

SEVERITY: ERROR
DESCRIPTION: SSI The Expression Manager found an invalid object_id of %s of type %s at position %d.
CAUSE: An invalid object id has been specified during expression evaluation.
ACTION: Verify that the object id that is being supplied for expression execution is valid.
PARAMS: The first parameter is the invalid object id (in string form) that was supplied. The second parameter is the type that the object id is supposed to correspond to. The third parameter is the position of the object id in the object list.

ERROR: [DM_EXPRESSION_E_INVALID_DATA_TYPE]

SEVERITY: ERROR
DESCRIPTION: I An invalid data type %d has been specified.
CAUSE: An invalid data type has been specified.
ACTION: Make sure that only valid data types are being used.
PARAMS: The integer representation of the data type – maps to dmPrimitives.

ERROR: [DM_EXPRESSION_E_BUILTIN_EXPR_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch – Invalid object ID %s.
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS:

ERROR: [DM_EXPRESSION_E_PARSER_UNEXPECTED_CHAR_AT]

SEVERITY: ERROR
DESCRIPTION: SII Unexpected character (%s) at line %d, column %d of expression.
CAUSE: The expression string contains an illegal character.
ACTION: Remove the illegal character at the indicated location.
PARAMS: The first parameter is the illegal character. The second parameter is the line number within the expression. The third parameter is the column number within the line.

ERROR: [DM_EXPRESSION_E_COND_EXPR_INVALID_SUBEXPR_ID]

SEVERITY: ERROR
DESCRIPTION: D Invalid Subexpression id %s in expression_list.
CAUSE: The subexpression id does not reference a valid dm_func_expr object
ACTION: Use a valid subexpression id in the expression list.
PARAMS: Invalid ID

ERROR: [DM_EXPRESSION_E_GENERATED_SOURCE_FILE_IO]

SEVERITY: ERROR
DESCRIPTION: DS The following IO Error occurred while accessing the source code for expression %s: %s.
CAUSE: An error occured during IO on the generated expression source file.
ACTION: Check the error string to determine an appropriate action.
PARAMS: The first parameter is the id of the expression object. The second parameter is the IO Error reported by the operating system.

ERROR: [DM_EXPRESSION_E_EXECUTION_UNABLE_TO_RETRIEVE_STORE_INFO]

SEVERITY: ERROR
DESCRIPTION: DS The Expression Manager was unable to retrieve store information for store %s with name %s.
CAUSE: The Expression Manager was not able to retrieve information from the store needed for pcode execution.
ACTION: Check that the storage object is valid.
PARAMS: The first parameter is the object id of the storage object. The second parameter is the name of the store.

ERROR: [DM_EXPRESSION_E_EXECUTION_UNABLE_TO_RETRIEVE_PCODE]

SEVERITY: ERROR
DESCRIPTION: DD The Expression Manager was unable to retrieve pcode for expression with id %s which is stored in sysobject with it %s.
CAUSE: The Expression Manager was not able to retrieve pcode from the sysobject specified by routine_id attribute of the expression object.
ACTION: Verify that the sysobject exists and that the pcode is indeed stored there.
PARAMS: The first parameter is the object id of the expression object. The second parameters is the object id of the sysobject pointed to by routine_id.

ERROR: [DM_EXPRESSION_E_SOURCE_PAGE_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: SS Expression objects must have the same source_pages in order for source code to be stored together. The expression object with object ids %s and %s have different source_pages. CAUSE:An attempt has been made to store source code for multiple expression together, but the expressions have different source_pages.
CAUSE:
ACTION: Make sure that expressions that are going to have source code stored together have the same source_pages.
PARAMS: The first parameter is the object id of the first expression object. The second parameter is the object id of the second expression object.

ERROR: [DM_EXPRESSION_E_ROUTINE_ID_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: SS Expression objects must have the same routine_ids in order for source code to be stored together. The expression objects with object ids %s and %s have different routine_ids.
CAUSE: An attempt has been made to store source code for multiple expression together, but the expressions have different routine_ids.
ACTION: Make sure that expressions that are going to have source code stored together have the same routine_ids.
PARAMS: The first parameter is the object id of the first expression object. The second parameter is the object id of the second expression object.

ERROR: [DM_EXPRESSION_E_FUNC_EXPR_INVALID_SOURCE_PAGE]

SEVERITY: ERROR
DESCRIPTION: The attribute source_page must be 0.
CAUSE: The source page must be 0 for Piper.
ACTION: Make sure the source page is set to 0.
PARAMS: None.

ERROR: [DM_EXPRESSION_E_INCREASE_LENGTH]

SEVERITY: ERROR
DESCRIPTION: SII Failed to increase the size of %s from %d to %d. PARAMTERS: S – attribute name I – original size of the attribute I – new size of the attribute
CAUSE: For an unknown reason, type conversion failed.
ACTION: Check if there are any database errors or problems. Report the problem to Documentum Support.
PARAMS:

ERROR: [DM_EXPRESSION_E_PARSER_UNKNOWN_IDENTIFIER_AT]

SEVERITY: ERROR
DESCRIPTION: SII The parser encountered an unknown identifier %s at line %d, column %d is illegal.
CAUSE: The expression contains an unknown identifier.
ACTION: Correct the identifier in the expression at the indicated location.
PARAMS: The first parameter is the unknown identifier. The second parameter is the line number within the expression. The third parameter is the column number within the line.

ERROR: [DM_EXPRESSION_E_UNABLE_TO_EXECUTE]

SEVERITY: ERROR
DESCRIPTION: DDI The Expression Manager encountered an execution error for expression with id %s. Check the source code stored in routine id %s, page %d.
CAUSE: The expression execution attempt failed.
ACTION: Look at the source code for the expression to try and understand the execution error information.
PARAMS: The first parameter is the object id of the expression object. The second parameter is the object id of the sysobject that contains the source code. The third parameter is the source page where the source code is located.

ERROR: [DM_EXPRESSION_E_PARSER_SYNTAX_EXPECTED_AT]

SEVERITY: ERROR
DESCRIPTION: SSII Expected %s, found %s at line %d, column %d.
CAUSE: The expression contains a syntax error.
ACTION: Correct the expression to use legal syntax.
PARAMS: The first parameter is the expected token. The second parameter is the actual token found. The third parameter is the line number within the expression. The fourth parameter is the column number within the line.

ERROR: [DM_EXPRESSION_E_COMPILATION_UNABLE_TO_RETRIEVE_SOURCE_CODE]

SEVERITY: ERROR
DESCRIPTION: DD The Expression Manager was unable to retrieve the source code for expression %s from sysobject %s.
CAUSE: The Expression Manager was not able to retrieve the source code from the sysobject pointed to by routine_id.
ACTION: Verify that the sysobject pointed to by routine_id is valid and that the source code is stored there.
PARAMS: The first parameter is the object id of the expression object. The second parameter is the object id of the sysobject that is supposed to hold the source code.

ERROR: [DM_EXPRESSION_E_SUBSCRIPT_BAD_OPERATOR_AT]

SEVERITY: ERROR
DESCRIPTION: SII The array subscript operation %s at line %d, column %d is illegal.
CAUSE: The expression contains an illegal array operation. Repeating attribute comparisons can only use (>,<,<>,=,<=,>=)
ACTION: Use a valid operator for array comparisons.
PARAMS: The first parameter is the invalid operator that was used. The second parameter is the line number within the expression. The third parameter is the column number within the line.

ERROR: [DM_EXPRESSION_E_COND_EXPR_LANGUAGE_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: The cond_expr contains a subexpression that is in a different expression language.
CAUSE: All subexpressions must be in the same expression language.
ACTION: Only add subexpressions of the same language.
PARAMS:

ERROR: [DM_EXPRESSION_E_INVALID_EXPRESSION_TYPE]

SEVERITY: ERROR
DESCRIPTION: The expression_type for a dm_expression is invalid.
CAUSE: An attempt was made to create a dm_expression with an invalid expression_type attribute.
ACTION: Supply an expression_type of DM_BOOLEAN for dm_func_expr, DM_INTEGER for dm_cond_expr, or DM_STRING for dm_cond_id_expr.
PARAMS: None.

ERROR: [DM_EXPRESSION_E_FUNC_EXPR_INVALID_ALIAS_INFO]

SEVERITY: ERROR
DESCRIPTION: The object_alias information is not complete.
CAUSE: An attempt was made to create a dm_func_expr with an incomplete object_alias list.
ACTION: Make sure each type_name entry has a corresponding object_alias entry.
PARAMS: None.

ERROR: [DM_EXPRESSION_E_FUNC_EXPR_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch – Invalid object ID %s.
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS:

ERROR: [DM_EXPRESSION_E_FUNC_EXPR_INVALID_CODE_PAGE]

SEVERITY: ERROR
DESCRIPTION: The attribute code_page must be 1.
CAUSE: The code page must be 1 for Piper.
ACTION: Make sure the code page is set to 1.
PARAMS: None.

ERROR: [DM_EXPRESSION_E_COMPILATION_UNABLE_TO_STORE_PCODE]

SEVERITY: ERROR
DESCRIPTION: DD The Expression Manager was unable to store the pcode for expression object %s in sysobject with id %s.
CAUSE: The Expression Manager encountered an error trying to store pcode for an expression.
ACTION: Verify that the sysobject exists.
PARAMS: The first parameter is the object id of the expression object. The second parameters is the object id of the sysobject pointed to by routine_id.

ERROR: [DM_EXPRESSION_E_EXECUTION_OBJECT_ID_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: II The Expression Manager expected %d object ids but was given %d object_ids.
CAUSE: An invalid number of object ids was supplied to the expression manager during execution.
ACTION: Make sure the correct number of object ids are being passed for expression execution.
PARAMS: The first parameter is the number of expected object ids. The second parameter is the number of object ids passed for execution.

ERROR: [DM_EXPRESSION_E_PARSER_TOKEN_TOO_LONG_AT]

SEVERITY: ERROR
DESCRIPTION: III The token at line %d, column %d exceeds the maximum token length of %d.
CAUSE: The expression contains a token that is too long.
ACTION: Correct the token to be within the limit given.
PARAMS: The first parameter is the line number within the expression. The second parameter is the column number within the line. The third parameter is the maximum allowed token length.

ERROR: [DM_EXPRESSION_E_UNABLE_TO_FETCH_ATTRIBUTE_VALUE]

SEVERITY: ERROR
DESCRIPTION: SSIS The Expression Handler was unable to fetch attribute %s of type %s at index %d for object %s.
CAUSE: The Expression Handler was unable to fetch a value of an attribute for a specified object.
ACTION: Verify that the object ids given to the expression handler are valid.
PARAMS: Attribute, Type, Index, Object ID

ERROR: [DM_EXPRESSION_E_COND_ID_EXPR_INVALID_ID_LIST]

SEVERITY: ERROR
DESCRIPTION: The expression_list and id_list attributes are not in synch.
CAUSE: Each expression_list entry must have a corresponding id_list entry.
ACTION: Make sure each expression_list entry has a id_list entry.
PARAMS: None.

ERROR: [DM_EXPRESSION_E_COND_ID_EXPR_MISSING_DEFAULT_ID]

SEVERITY: ERROR
DESCRIPTION: The default_id attribute must be set.
CAUSE: The default_id attribute is not set.
ACTION: Set the default id.
PARAMS: None.

ERROR: [DM_EXPRESSION_E_PARSER_MALFORMED_STRING_AT]

SEVERITY: ERROR
DESCRIPTION: II Malformed string literal at line %d, column %d.
CAUSE: The expression contains an illegal string literal.
ACTION: Correct the string literal at the indicated location.
PARAMS: The first parameter is the line number within the expression. The second parameter is the column number within the line.

ERROR: [DM_EXPRESSION_E_CODE_PAGE_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: SS Expression objects must have the same code_pages in order for source code to be stored together. The expression object with object ids %s and %s have different code_pages. CAUSE:An attempt has been made to store source code for multiple expression together, but the expressions have different code_pages.
CAUSE:
ACTION: Make sure that expressions that are going to have source code stored together have the same code_pages.
PARAMS: The first parameter is the object id of the first expression object. The second parameter is the object id of the second expression object.

ERROR: [DM_EXPRESSION_E_PARSER_MALFORMED_DATE_AT]

SEVERITY: ERROR
DESCRIPTION: II Malformed date literal at line %d, column %d.
CAUSE: The expression contains an illegal date literal.
ACTION: Correct the date literal at the indicated location.
PARAMS: The first parameter is the line number within the expression. The second parameter is the column number within the line.

ERROR: [DM_EXPRESSION_E_INVALID_ATTRIBUTE_INDEX]

SEVERITY: ERROR
DESCRIPTION: SSI The attribute %s of type %s references an invalid index %d.
CAUSE: An invalid index has been specified for the attribute.
ACTION: Check the index and make sure it is valid.
PARAMS: type_name, attribute_name, index

ERROR: [DM_EXPRESSION_E_INVALID_EXPRESSION_SYNTAX]

SEVERITY: ERROR
DESCRIPTION: The syntax of the expression_text attribute is invalid.
CAUSE: There is a syntax error in the expression text attribute.
ACTION: Fix the syntax error in the expression.
PARAMS: None.

ERROR: [DM_EXPRESSION_E_INVALID_EXPRESSION_OBJECT]

SEVERITY: ERROR
DESCRIPTION: An invalid operation on an expression object was attempted.
CAUSE: The expression manager cannot perform certain operations on certain forms of expressions. (i.e. dm_func_expr, dm_cond_expr, dm_cond_id_expr)
ACTION: Make sure that the desired operation is indeed valid for the expression object being used.
PARAMS: None.

ERROR: [DM_EXPRESSION_E_FUNC_EXPR_USER_FUNCTION_NULL_ROUTINE_NAME]

SEVERITY: ERROR
DESCRIPTION: The routine name for a user function must be set.
CAUSE: A dm_func_expr object of kind DM_EXPR_USER_FUNCTION must have the routine_name attribute set.
ACTION: Make sure a valid routine_name has been specified for the expression.
PARAMS: None.

ERROR: [DM_EXPRESSION_E_FUNC_EXPR_INVALID_EXPRESSION_KIND]

SEVERITY: ERROR
DESCRIPTION: The expression_kind for a dm_func_expr must be DM_EXPR_NORMAL or DM_EXPR_USER_ROUTINE.
CAUSE: An attempt was made to create a dm_func_expr with an invalid expression_kind.
ACTION: Supply an expression_kind of DM_EXPR_NORMAL or DM_EXPR_USER_ROUTINE
PARAMS: None.

ERROR: [DM_EXPRESSION_E_FUNC_EXPR_INVALID_ATTRIBUTE_INFO]

SEVERITY: ERROR
DESCRIPTION: The attribute information could not be validated.
CAUSE: Either an attribute_name, type_name, repeat_index or attr_object_index entry is invalid.
ACTION: Make sure attribute information is correct and that indices are valid.
PARAMS: None.

ERROR: [DM_EXPRESSION_E_NULL_TEXT]

SEVERITY: ERROR
DESCRIPTION: The expression_text for a dm_expression cannot be empty.
CAUSE: An attempt was made to create a dm_expression with an empty expression_text attribute.
ACTION: Supply expression_text when creating a dm_expression.
PARAMS: None.

ERROR: [DM_EXPRESSION_E_INVALID_ATTRIBUTE]

SEVERITY: ERROR
DESCRIPTION: SSI The attribute %s of type %s at index %d is invalid.
CAUSE: An invalid attribute was referenced by an expression.
ACTION: Make sure that the attribute referenced is valid for the associated type.
PARAMS: attribute_name

ERROR: [DM_EXPRESSION_E_LITERAL_EXPR_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch – Invalid object ID %s.
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS:

ERROR: [DM_EXPRESSION_E_COND_ID_EXPR_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch – Invalid object ID %s.
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS:

ERROR: [DM_EXPRESSION_E_PARSER_ILLEGAL_SUBSCRIPT_AT]

SEVERITY: ERROR
DESCRIPTION: II The array subscript operation at line %d, column %d is illegal.
CAUSE: The expression contains an illegal array subscript operation.
ACTION: Correct the subscript operation at the indicated location.
PARAMS: The first parameter is the line number within the expression. The second parameter is the column number within the line.

ERROR: [DM_EXPRESSION_E_INVALID_TYPE]

SEVERITY: ERROR
DESCRIPTION: S The type %s is an invalid type.
CAUSE: An invalid type was referenced by an expression.
ACTION: Make sure that the type referenced does exist.
PARAMS: type_name

ERROR: [DM_EXPRESSION_E_COND_EXPR_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch – Invalid object ID %s.
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS:

ERROR: [DM_EXPRESSION_E_UNKNOWN_ERROR]

SEVERITY: ERROR
DESCRIPTION: I An unknown error with code %d has occurred within the expression manager.
CAUSE: An error has occurred within the expression manager and the error code has no mapping.
ACTION: This is an internal error that should not happen, but if it does, please report it.
PARAMS: error_code.

ERROR: [DM_EXPRESSION_E_COND_EXPR_INVALID_SUBEXPR_KIND]

SEVERITY: ERROR
DESCRIPTION: Subexpressions cannot be User Routines.
CAUSE: The subexpression is a User Routine.
ACTION: Make sure you do not use User Routines as subexpressions.
PARAMS: None.

ERROR: [DM_EXPRESSION_E_RUNTIME]

SEVERITY: ERROR
DESCRIPTION: IIS The expression execution attempt failed. Error Number is %d, Error Line is %d and Error Text is %s.
CAUSE: The expression execution attempt failed.
ACTION: Correct the expression errors and retry execution.
PARAMS: The first parameter is the error number. The second parameter is the error line. The third parameter is the error text.

ERROR: [DM_EXPRESSION_E_FUNC_EXPR_MISSING_TYPE_NAME_INFO]

SEVERITY: ERROR
DESCRIPTION: The type_name attribute must have at least one type specified.
CAUSE: An attempt was made to create a dm_func_expr without a type_name entry.
ACTION: Specify at least one type for the dm_func_expr object.
PARAMS: None.

ERROR: [DM_EXPRESSION_E_FUNC_EXPR_INVALID_EXPRESSION_LANG]

SEVERITY: ERROR
DESCRIPTION: The expression_lang for a dm_func_expr must be DM_EXPR_LANG_DOCBASIC.
CAUSE: An attempt was made to create a dm_func_expr with an invalid expression_lang attribute.
ACTION: Supply an expression_lang of DM_EXPR_LANG_DOCBASIC.
PARAMS: None.

ERROR: [DM_EXPRESSION_E_EXPRESSION_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch – Invalid object ID %s.
CAUSE: Could not fetch an object with the given id.
ACTION: This is probably caused by a bad ID. Or, possibly, a connection to the Documentum server could not be established.
PARAMS:

ERROR: [DM_EXPRESSION_E_CANNOT_GENERATE_USER_ROUTINES]

SEVERITY: ERROR
DESCRIPTION: Cannot generate a User Routine.
CAUSE: Only Expressions can be generated.
ACTION: Dont generate User Routines.
PARAMS: None.

ERROR: [DM_EXPRESSION_E_COND_EXPR_INVALID_SUBEXPRESSION]

SEVERITY: ERROR
DESCRIPTION: The subexpression of the conditional expression object is invalid.
CAUSE: There is some inconsistency between the parent expression object and the subexpression
ACTION: Verify that the subexpression is consistent with the parent expression object.
PARAMS: None.

ERROR: [DM_EXPRESSION_W_EXECUTION_PCODE_MISSING]

SEVERITY: WARNING
DESCRIPTION: DDI Expression Manager could not find the pcode for expression with ID %s. The pcode should be stored in the sysobject with ID %s at page %d
CAUSE: The pcode file for the expression was either missing or out of synch with the source code. This suggests that the source code has been manually changed and the corresponding pcode was not regenerated or the pcode was actually deleted.
ACTION: Although expression execution should have completed successfully, it is costly from a performance standpoint to cause the expression manager to recompile the source code each time it is executed. We recommend that you regenerate the expression pcode and store it in the expression sysobject pointed to by the routine_id attribute of the expression object.
PARAMS:

ERROR: [DM_EXPRESSION_W_EXPUNGE_COND_ID_EXPR_CANT_FETCH]

SEVERITY: WARNING
DESCRIPTION: D Could not fetch the dm_cond_id_expr object with ID %s during an expunge operation.
CAUSE: Could not fetch an object with the given id.
ACTION: None necessary, the expunge operation continued.
PARAMS: The parameter is the object id.

ERROR: [DM_EXPRESSION_W_EXPUNGE_EXPRESSION_CANT_FETCH]

SEVERITY: WARNING
DESCRIPTION: D Could not fetch the expression object with ID %s during an expunge operation.
CAUSE: Could not fetch an object with the given id.
ACTION: None necessary, the expunge operation continued.
PARAMS: The parameter is the object id.

ERROR: [DM_EXPRESSION_W_COMPILATION_UNABLE_TO_REMOVE_TEMP_FILE]

SEVERITY: WARNING
DESCRIPTION: DSS The Expression Manager was unable to remove a temporary file used during the compilation of expression with id %s. Removal of the temporary file %s failed due to IO Error: %s.
CAUSE: The Expression Manager was not able to remove a temporary file created during expression compilation.
ACTION: Manually delete the specified temporary file.
PARAMS: The first parameter is the object id of the expression object that was being compiled. The second parameter is the name of the temporary file which could not be removed. The third parameter is the IO Error reported by the operating system.

ERROR: [DM_EXPRESSION_W_UNABLE_TO_REMOVE_PCODE_FILE]

SEVERITY: WARNING
DESCRIPTION: DDI The Docbasic Engine was unable to remove the pcode file for expression with id %s after generating new source code. The pcode is stored in sysobject %s at page %d. It should be removed prior to evaluating the expression.
CAUSE: The expression handler was not able to delete the pcode rendition stored in the sysobject.
ACTION: As long as the expression is compiled prior to execution there should be no problem. The only danger is that if you dont compile the expression, the pcode and source could be out of synch.
PARAMS: The first parameter is the object id of the expression object. The second parameter is the object id of the sysobject where the pcode is stored. The third parameter is the page at which the pcode is stored.

ERROR: [DM_EXPRESSION_W_GENERATION_UNABLE_TO_REMOVE_TEMP_FILE]

SEVERITY: WARNING
DESCRIPTION: DSS The Expression Manager was unable to remove a temporary file used during source code generation of expression with id %s. Removal of the temporary file %s failed due to IO Error: %s.
CAUSE: The Expression Manager was not able to remove a temporary file created during expression generation.
ACTION: Manually delete the specified temporary file.
PARAMS: The first parameter is the object id of the expression object that was being compiled. The second parameter is the name of the temporary file which could not be removed. The third parameter is the IO error reported by the operating system.

nahoru

DM_FILTER

ERROR: [DM_FILTER_E_DUMPOUT_TYPE]

SEVERITY: ERROR
DESCRIPTION: S Error writing type description for %s to the dump output file.
CAUSE: The filter program received an error on an attempt to write out a type description to the output dumpfile.
ACTION: Check previous error messages for further information. Check consistency of type in the dump input file.
PARAMS: 1%s – the name of the type on which the error occurred.

ERROR: [DM_FILTER_E_USER_ARG]

SEVERITY: ERROR
DESCRIPTION: SS Argument Error: the user specified in the %s argument does not exist. User name: <%s>.
CAUSE: A replication request gives a new user to own documents. The filter program verifies that the specified user exists. This verification failed.
ACTION: Correct the command line arguments.
PARAMS: 1%s – the flag name for the new user 2%s – the specified user name

ERROR: [DM_FILTER_E_SYNTAX_NEWVALUE]

SEVERITY: ERROR
DESCRIPTION: S Error in argument syntax for -new_value flag. Parameter value %s is incorrect. The correct format is -new_value type.attribute value.
CAUSE: The argument given to a -new_value option was not of the correct format. The format required is: type_name.attribute_name attribute_value
ACTION: Fix command options.
PARAMS: 1%s – the callers parameter value

ERROR: [DM_FILTER_E_NO_DUMP_INPUT]

SEVERITY: ERROR
DESCRIPTION: SS Cannot locate dump input file: %s. Operating System Status %s.
CAUSE: The filter program could not find the dump input file.
ACTION: Make sure the specified dump input file exists. Check permissions of the filter program (which normally runs as the docbase owner) to access the specified input file.
PARAMS: 1%s – the dump input file 2%s – the os error status

ERROR: [DM_FILTER_E_FOLDER_ARG]

SEVERITY: ERROR
DESCRIPTION: SS Argument Error: the folder specified in the %s argument does not exist. Folder name: <%s>.
CAUSE: A replication request gives a new folder in which to place documents. The filter program verifies that the specified folder exists. This verification failed.
ACTION: Correct the command line arguments.
PARAMS: 1%s – the flag name for the new folder 2%s – the specified folder name

ERROR: [DM_FILTER_E_TYPE_UNKNOWN]

SEVERITY: ERROR
DESCRIPTION: SS An internal error was detected in the filter program. An attribute contained an unknown or unsupported type. Attribute: %s.%s
CAUSE: During processing in the filter, an attribute which was to be replaced was found to be of an unknown type.
ACTION: Check for previous error messages and report to Documentum support.
PARAMS: 1%s – the name of the type. 2%s – the name of the attribute.

ERROR: [DM_FILTER_E_DUMPIN_INIT]

SEVERITY: ERROR
DESCRIPTION: S Error opening/initializing dump input file: %s.
CAUSE: The filter program was returned an error from the dumpfile open call.
ACTION: Check previous error messages for further information.
PARAMS: 1%s – the dump input file

ERROR: [DM_FILTER_E_STORAGE_ARG]

SEVERITY: ERROR
DESCRIPTION: SS Argument Error: the storage area specified in the %s argument does not exist. Storage Area name: <%s>.
CAUSE: A replication request gives a new storage area to place documents. The filter program verifies that the specified area exists. This verification failed.
ACTION: Correct the command line arguments.
PARAMS: 1%s – the flag name for the new storage area 2%s – the specified storage area name

ERROR: [DM_FILTER_E_SYNTAX_NOOPT]

SEVERITY: ERROR
DESCRIPTION: S The required parameter %s was not specified.
CAUSE: A required input parameter was not given to the filter program. This could be a parameter required for all filter actions or the parameter could be needed because of other command line options which were specified.
ACTION: Fix command options.
PARAMS: 1%s – the name of the option.

ERROR: [DM_FILTER_E_DUMPOUT_EXISTS]

SEVERITY: ERROR
DESCRIPTION: SS Cannot remove existing dump output file: %s. Operating System Status %s.
CAUSE: The filter program found that the specified dump output file already existed. It tried to remove the existing file but could not.
ACTION: Remove the existing dump output file.
PARAMS: 1%s – the dump output file 2%s – the os error status

ERROR: [DM_FILTER_E_OBJECT_FILTER]

SEVERITY: ERROR
DESCRIPTION: SS Error processing object %s (type %s) in filter program.
CAUSE: An error was encountered while applying the filter actions to an object of the dumpfile. The object could not be altered correctly.
ACTION: Check previous error messages for further information.
PARAMS: 1%s – the id of the object on which the error occurred. 2%s – the typename of the object

ERROR: [DM_FILTER_E_STORE_NOT_INDEXABLE]

SEVERITY: ERROR
DESCRIPTION: Warning: the storage area specified has no fulltext index defined on it, but the filter arguments do not disable fulltext indexing. Objects filtered will have their fulltext index attributes set to False.
CAUSE: Since the storage area being loaded to does not have a fulltext index defined on it, the loaded objects must be marked non indexable.
ACTION: Create a fulltext index on the storage area if desired
PARAMS: none

ERROR: [DM_FILTER_E_ACL_ARG]

SEVERITY: ERROR
DESCRIPTION: SSS Argument Error: the acl specified in the %s argument does not exist. Acl name: <%s.%s>.
CAUSE: A replication request gives a new acl setting to documents. The filter program verifies that the specified acl exists. This verification failed.
ACTION: Correct the command line arguments.
PARAMS: 1%s – the flag name for the new acl 2%s – the specified acl domain name 3%s – the specified acl name

ERROR: [DM_FILTER_E_DUMPOUT_OBJECT]

SEVERITY: ERROR
DESCRIPTION: SS Error writing description for object %s (type %s) to the dump output file.
CAUSE: The filter program received an error on an attempt to write out an object description to the output dumpfile.
ACTION: Check previous error messages for further information.
PARAMS: 1%s – the id of the object on which the error occurred. 2%s – the typename of the object

ERROR: [DM_FILTER_E_DUMMY1_MESSAGE]

SEVERITY: ERROR
DESCRIPTION: This is here to keep the error numbers from shifting.
CAUSE: This is a dummy message that is never used. Do not ever remove it.
ACTION:
PARAMS:

ERROR: [DM_FILTER_E_ARG_MISSING]

SEVERITY: ERROR
DESCRIPTION: S Argument Error: missing required argument %s.
CAUSE: An argument that is required for the filter program was not specified. An argument may be required for all calls (such as the dump file name) or the argument may be required due to the presence of one of the other specified arguments.
ACTION: Correct the command line arguments.
PARAMS: 1%s – the missing argument

ERROR: [DM_FILTER_E_API_ERROR0]

SEVERITY: ERROR
DESCRIPTION: S An error was returned from an API call in an attempt to execute the command: <%s>.
CAUSE: An API call that was made to lookup docbase information to use in the filter program returned with an error indication.
ACTION: Check the status of the specified docbase to ensure it is active. Check any previously reported error messages for clues to the problem.
PARAMS: 1%s – the command string

ERROR: [DM_FILTER_E_API_ERROR]

SEVERITY: ERROR
DESCRIPTION: SS An error was returned from an API call in an attempt to execute the command: <%s>. The error reason was: <%s>.
CAUSE: An API call that was made to lookup docbase information to use in the filter program returned with an error indication.
ACTION: Check the status of the specified docbase to ensure it is active. Check any previously reported error messages for clues to the problem.
PARAMS: 1%s – the command string 2%s – the error message returned by getmessage

ERROR: [DM_FILTER_E_DUMPIN_HEADER]

SEVERITY: ERROR
DESCRIPTION: S Error reading header information in the dump input file: %s. Cannot build list of type version stamps.
CAUSE: The filter program received an error from the dump routines process the dumpfile header information.
ACTION: Check previous error messages for further information. Check the dumpfile version/date for compatibility with the current system.
PARAMS: 1%s – the dump input file

ERROR: [DM_FILTER_E_SYNTAX_ARGCOUNT]

SEVERITY: ERROR
DESCRIPTION: S Insufficient number of arguments for parameter %s.
CAUSE: The command line string did not contain enough arguments to fulfill the given flag.
ACTION: Fix command options.
PARAMS: 1%s – the name of the option.

ERROR: [DM_FILTER_E_DUMPOUT_INIT]

SEVERITY: ERROR
DESCRIPTION: S Error opening/initializing the dump output file: %s.
CAUSE: The filter program was returned an error from the dumpfile open call.
ACTION: Check previous error messages for further information. Check permissions to create the specified file. Check that the specified directory exists and is accessible. Check for available diskspace.
PARAMS: 1%s – the dump output file

ERROR: [DM_FILTER_E_STATE_ERROR]

SEVERITY: ERROR
DESCRIPTION: An internal error was detected in the filter program. The program arguments were not correctly processed.
CAUSE: The program state built from the arguments is not consistent.
ACTION: Check for previous error messages and report to Documentum support.
PARAMS:

ERROR: [DM_FILTER_E_SYNTAX_BADPARM]

SEVERITY: ERROR
DESCRIPTION: S The parameter %s is not a valid filter option.
CAUSE: An unrecognized option was given to the filter program.
ACTION: Fix command options.
PARAMS: 1%s – the name of the option.

ERROR: [DM_FILTER_E_BOOLEAN_VAL]

SEVERITY: ERROR
DESCRIPTION: SS Argument Error: the value (%s) for argument (%s) is not a legal boolean value. The value must be T(rue) or F(alse)
CAUSE: A value was given to a boolean flag that did not begin with T or F (case is important).
ACTION: Correct the command line arguments.
PARAMS: 1%s – the specified boolean value 2%s – the argument flag name

ERROR: [DM_FILTER_E_DUMPOUT_CONTENT]

SEVERITY: ERROR
DESCRIPTION: SS Error writing content data for object %s (type %s) to the dump output file.
CAUSE: The filter program received an error on an attempt to write out the content data for an object to the output dumpfile. When an object with content data is encountered during filter processing, the program just reads the content data from the input file and writes in out to the output file. This error could indicate a problem reading the input or in writing the output.
ACTION: Check previous error messages for further information.
PARAMS: 1%s – the id of the object on which the error occurred. 2%s – the typename of the object

ERROR: [DM_FILTER_I_STARTUP]

SEVERITY: INFORMATION
DESCRIPTION: SSS Starting program %s on dumpfile %s. Output to %s.
CAUSE: Trace message given at filter startup. Trace level 1.
ACTION:
PARAMS: 1%s – the program name (dmrepfilter) 2%s – the dump input file 3%s – the dump output file

ERROR: [DM_FILTER_I_COMPLETE]

SEVERITY: INFORMATION
DESCRIPTION: IIII Program completed with status %d.n %d objects processed from input file.n %d objects written to output file.n %d types written to output file.
CAUSE: Trace message given at filter exit. Trace level 1.
ACTION:
PARAMS: 1%d – the program exit status 2%d – the number of objects in the dump input file 3%d – the number of objects written to the dump output file 4%d – the number of types written to the dump output file

nahoru

DM_FOLDER

ERROR: [DM_FOLDER_F_INIT3]

SEVERITY: FATAL
DESCRIPTION: The type manager returned an error storing the dm_folder type.
CAUSE: Unknown.
ACTION: Look at the error logged by the type manager. Report this message and any parameters to your Documentum Site Representative. $Id: dmforgn.e,v 5.12 1999/06/14 09:42:47 rogert Exp $ dmDocbaseIdMap class and foreign/replicated object errors
PARAMS:

ERROR: [DM_FOLDER_F_INIT1]

SEVERITY: FATAL
DESCRIPTION: The dm_folder type was found in the database without a version stamp.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_FOLDER_F_INIT2]

SEVERITY: FATAL
DESCRIPTION: II Version stamp %d was expected to be %d.
CAUSE: The version stamp that the dm_folder object software expected was different from the actual version stamp in the database.
ACTION: You must upgrade your DocuServer database to conform to the software that you are running. If your software and data are consistent, then report this message and any parameters to your Documentum Site Representative.
PARAMS:

ERROR: [DM_FOLDER_E_UNIQUENESS_CHECK_FAILED]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: During the Check to see if a folder with the same name exists or not, we encountered an error.
ACTION: This can lead to creation of 2 folders with the same name under certain conditions, please check the system and delete or rename one of them.
PARAMS:

ERROR: [DM_FOLDER_E_LONG_PATH1]

SEVERITY: ERROR
DESCRIPTION: SL Folder path for folder named %s is too long (%ld).
CAUSE: User tried to define a folder path that is wider than the current supported size.
ACTION: Use folder path that is size of the r_folder_path limit.
PARAMS:

ERROR: [DM_FOLDER_E_MERGE_FOLDER_IDS]

SEVERITY: ERROR
DESCRIPTION: D Error in load of folder object %s. Error processing i_folder_id values.
CAUSE: An error was encountered in a load operation while attempting to merge the folder links of an incoming folder with an existing docbase folder. The error was encountered inside the generic i_folder_id merging routine for the dm_sysobject type. Previous error messages logged by that routine should give more detail on the problem. This operation is normally done as part of replication processing and this error will likely terminate the replication run.
ACTION: Check previous error messages for more information on the problem. If this error was encountered during replication processing, then the replication job must be rerun after the error is corrected.
PARAMS:

ERROR: [DM_FOLDER_E_PATH_EXISTS]

SEVERITY: ERROR
DESCRIPTION: SS Cannot save (or link) %s folder with path name %s because one already exists.
CAUSE: Object_names of all contained folders within the same folder must be unique.
ACTION: Remove the linkage that caused this problem.
PARAMS:

ERROR: [DM_FOLDER_E_CANT_COMPUTE_DESC]

SEVERITY: ERROR
DESCRIPTION: S Cannot compute child folders for %s folder.
CAUSE: Most likely security violation. ACTION:consult the previous error messages.
ACTION:
PARAMS:

ERROR: [DM_FOLDER_E_CANT_SAVE_NO_LINK]

SEVERITY: ERROR
DESCRIPTION: S Cannot save folder with object_name %s – folders must be linked.
CAUSE: You tried to save a folder without any linkages. Your default folder or folder that your tried to link may be bad.
ACTION: All folders must have one linkage. Link this folder to another folder and try again.
PARAMS:

ERROR: [DM_FOLDER_E_NOT_A_FOLDER_ID]

SEVERITY: ERROR
DESCRIPTION: SS You have specified an ID (%s) in the %s command that is not a valid ID value for a folder or cabinet.
CAUSE: The ID value in the specific command does not identify a folder or cabinet.
ACTION: Make sure the given ID is a valid ID value for folder of cabinet.
PARAMS: The ID value given in the command and the Name of the command.

ERROR: [DM_FOLDER_E_TRAILING_SPACE_IN_NAME]

SEVERITY: ERROR
DESCRIPTION: S The folder name %s contains trailing space(s), which is not allowed.
CAUSE: The folder name contains trailing space(s).
ACTION: Change the folder name and retry.
PARAMS:

ERROR: [DM_FOLDER_E_CANT_ADD_LINK1]

SEVERITY: ERROR
DESCRIPTION: SD Cannot add sysobject named %s to folder with ID %s.
CAUSE: Your linkage between the sysobject and folder that has failed.
ACTION: No action is required. The requested link operation is denied.
PARAMS:

ERROR: [DM_FOLDER_E_MERGE_FOLDER_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Error in load folder merging. Could not fetch folder object %s.
CAUSE: An error was encountered in a load operation while attempting to merge the folder links of an incoming folder with an existing docbase folder. The error was encountered while attempting to propagate the changes to the folders children and was the result of an error trying to fetch one of these child folders. A previous error message logged by the fetch routine should give more detail on the problem.
ACTION: Check previous error messages for more information on the problem. If this error was encountered during replication processing, then the replication job must be rerun after the error is corrected.
PARAMS:

ERROR: [DM_FOLDER_E_LONG_PATH]

SEVERITY: ERROR
DESCRIPTION: SSL Folder path %s in folder named %s is too long (%ld).
CAUSE: User tried to define a folder path that is wider than the current supported size.
ACTION: Use folder path that is size of the r_folder_path limit.
PARAMS:

ERROR: [DM_FOLDER_E_MERGE_PROPSAVE]

SEVERITY: ERROR
DESCRIPTION: D Error in folder load merging. Error saving the folder object %s.
CAUSE: An error was encountered in a load operation while attempting to merge the folder links of an incoming folder with an existing docbase folder. The error was encountered while attempting to propagate the changes to the folders children and was the result of an error while trying to save changes to one of those child folders. Previous error messages logged by the server should give more detail on the problem. This operation is normally done as part of replication processing and this error will likely terminate the replication run.
ACTION: Check previous error messages for more information on the problem. If this error was encountered during replication processing, then the replication job must be rerun after the error is corrected.
PARAMS:

ERROR: [DM_FOLDER_E_ILLEGAL_NAME]

SEVERITY: ERROR
DESCRIPTION: SS The folder name %s is illegal due to the character %s.
CAUSE: The folder name contains an illegal character.
ACTION: Change the folder name and retry.
PARAMS:

ERROR: [DM_FOLDER_E_CANT_CHANGED]

SEVERITY: ERROR
DESCRIPTION: SS Cannot change name of folder %s name since could not modify descendant named %s.
CAUSE: Descendant folder could not be changed to propogate the folder name changes.
ACTION: See the previous error message for more detail.
PARAMS:

ERROR: [DM_FOLDER_E_ALREADY_LINKED]

SEVERITY: ERROR
DESCRIPTION: SD The %s sysobject is already linked to folder with ID %s.
CAUSE: You just linked a folder that has been linked before. Most likely the sysobject in question is erroneous.
ACTION: No action is required. The requested link operation was denied.
PARAMS:

ERROR: [DM_FOLDER_E_RENAMED_FOLDER_INTERNALLY]

SEVERITY: ERROR
DESCRIPTION: SDSS Multiple sessions tried to save a folder with name ( %s ) simultaneously.Folder(%s) with path (%s) was renamed to (%s) at the same location.
CAUSE: In a multithreaded environment, multiple sessions tried to save a folder with the same name simultaneously. During this situation the server renames the last commited folder to dm_fix_me__ at the same folder level.
ACTION: Please move the contents of the second folder to the first one and delete the second folder or rename this folder to have a unique name.
PARAMS:

ERROR: [DM_FOLDER_E_MERGE_PROPAGATE]

SEVERITY: ERROR
DESCRIPTION: D Error in load of folder object %s. Error propagating folder link changes to subfolders.
CAUSE: An error was encountered in a load operation while attempting to merge the folder links of an incoming folder with an existing docbase folder. The error was encountered while attempting to propagate the changes to this folders children. Previous error messages logged should give more detail on the exact cause of the problem. This operation is normally done as part of replication processing and this error will likely terminate the replication run.
ACTION: Check previous error messages for more information on the problem. If this error was encountered during replication processing, then the replication job must be rerun after the error is corrected.
PARAMS:

ERROR: [DM_FOLDER_E_CIRC_LINK]

SEVERITY: ERROR
DESCRIPTION: S Cannot create circular links for folder with path name %s.
CAUSE: New linkages in this folder have caused circularity of folder containment.
ACTION: Remove the unwanted links and try again.
PARAMS:

ERROR: [DM_FOLDER_E_CANT_DESTROY]

SEVERITY: ERROR
DESCRIPTION: S Cannot destroy folder with path name %s since it is not empty.
CAUSE: You tried to destroy a non-empty folder.
ACTION: A folder must be empty before destruction.
PARAMS:

ERROR: [DM_FOLDER_E_MERGE_PROPQUERY]

SEVERITY: ERROR
DESCRIPTION: D Error in folder load merging. Error querying for subfolders of the folder object %s.
CAUSE: An error was encountered in a load operation while attempting to merge the folder links of an incoming folder with an existing docbase folder. The error was encountered while attempting to propagate the changes to the folders children and was the result of a query error while trying to find these child folders. Previous error messages logged by the query facility should give more detail on the problem. This operation is normally done as part of replication processing and this error will likely terminate the replication run.
ACTION: Check previous error messages for more information on the problem. If this error was encountered during replication processing, then the replication job must be rerun after the error is corrected.
PARAMS:

ERROR: [DM_FOLDER_E_CANT_FETCH_BY_PATH]

SEVERITY: ERROR
DESCRIPTION: S Cannot fetch folder with path name %s.
CAUSE: You tried to fetch a folder with a non-existent path name.
ACTION: Retry the operation with correct path name.
PARAMS:

ERROR: [DM_FOLDER_E_INVALID_PATH]

SEVERITY: ERROR
DESCRIPTION: SS An Invalid path %s is encountered in folder named %s.
CAUSE: User tried to change a folder name and system encountered an invalid folder path.
ACTION: See your system admin. This should not happen under normal circumstances.
PARAMS:

ERROR: [DM_FOLDER_E_NAME_MAPPING]

SEVERITY: ERROR
DESCRIPTION: SS Failed to map the given folder path %s to the folders handle due to database errors. The message from the database is: %s
CAUSE: Failed to execute the query that gets the object id with the given unique folder path.
ACTION: Fixed the database problem as reported in the error message and try again.
PARAMS:

ERROR: [DM_FOLDER_E_CANT_CHANGE_NAME]

SEVERITY: ERROR
DESCRIPTION: Cannot change a folder name.
CAUSE: You tried to change the object_name of an existing folder. This is not supported at this time.
ACTION: No action is required. The requested save operation is not carried out.
PARAMS:

ERROR: [DM_FOLDER_E_PATH_WIDEN_FAILED]

SEVERITY: ERROR
DESCRIPTION: II The type manager returned an error when widening the r_folder_path attribute from %d to %d.
CAUSE: Unknown.
ACTION: None needed if you can work with the current path width. If you need wider paths, look at the error logged by the type manager. Report this message and any parameters to your Documentum Site Representative.
PARAMS:

ERROR: [DM_FOLDER_E_CANT_DELETE_LINK]

SEVERITY: ERROR
DESCRIPTION: SS Cannot delete sysobject named %s from folder with path name %s.
CAUSE: Your unlink operation between the sysobject and folder that has failed. Most likely the sysobject in question is erroneous.
ACTION: No action is required. The requested link operation is denied.
PARAMS:

ERROR: [DM_FOLDER_E_CANT_ADD_LINK]

SEVERITY: ERROR
DESCRIPTION: SS Cannot add sysobject named %s to folder with path name %s.
CAUSE: Your linkage between the sysobject and folder that has failed.
ACTION: No action is required. The requested link operation is denied.
PARAMS:

ERROR: [DM_FOLDER_E_CANT_ADD_LINK2]

SEVERITY: ERROR
DESCRIPTION: SS Failed to recompute the folder paths of the folder %s, which is a descendent of the folder %s.
CAUSE: Failed to recomupte the folder paths of the first folder, while adding a new link to the second folder.
ACTION: Validate the folder of the specified path and find out why its folder paths can not be recomputed.
PARAMS:

ERROR: [DM_FOLDER_E_MERGE_ANCESTORS]

SEVERITY: ERROR
DESCRIPTION: D Error in load of folder object %s. Error processing i_ancestor_id values.
CAUSE: An error was encountered in a load operation while attempting to merge the folder links of an incoming folder with an existing docbase folder. The error was encountered while attempting to calculate i_ancestor_id values for the updated folder object. Previous error messages logged by that routine should give more detail on the problem. This operation is normally done as part of replication processing and this error will likely terminate the replication run.
ACTION: Check previous error messages for more information on the problem. If this error was encountered during replication processing, then the replication job must be rerun after the error is corrected.
PARAMS:

ERROR: [DM_FOLDER_E_CANT_DROP_LINK]

SEVERITY: ERROR
DESCRIPTION: SD No link established between folder with path name %s and sysobject with ID %s.
CAUSE: You tried to drop a non-existent linkage.
ACTION: No action is required. The requested unlink operation is denied.
PARAMS:

ERROR: [DM_FOLDER_E_MUST_HAVE_NAME]

SEVERITY: ERROR
DESCRIPTION: A new folder/cabinet must have an object_name.
CAUSE: All folders must have an object_name during creation.
ACTION: Set the object_name and try to save again.
PARAMS:

ERROR: [DM_FOLDER_E_MERGE_PROPRECURS]

SEVERITY: ERROR
DESCRIPTION: D Error in folder load merging. Error propagating folder link changes to subfolder %s.
CAUSE: An error was encountered in a load operation while attempting to merge the folder links of an incoming folder with an existing docbase folder. The error was encountered while attempting to propagate the changes to this folders children. Previous error messages logged should give more detail on the exact cause of the problem. This operation is normally done as part of replication processing and this error will likely terminate the replication run.
ACTION: Check previous error messages for more information on the problem. If this error was encountered during replication processing, then the replication job must be rerun after the error is corrected.
PARAMS:

ERROR: [DM_FOLDER_W_MERGE_ANCESTR_FETCH]

SEVERITY: WARNING
DESCRIPTION: DDS Unable to fetch parent link %s for folder %s (%s). Parent folder object may not exist. This inconsistent link should be resolved later in the load process.
CAUSE: An error was encountered in a load operation while attempting to merge the folder links of an incoming folder with an existing docbase folder. The error was encountered while attempting to fetch a folders parent folders in order to set the proper ancestor_id values for this target docbase. The specific cause was that the parent folder object did not appear to exist. This could be caused by the deletion of the parent folder at the source site or due to a local object with phantom links left from a previous failed replication attempt. The folder will be loaded but the ancestors for this uknown folder cannot be added at this time. It is probable that this folder will be encountered again later in the load and that the phantom links will will be resolved automatically at that time.
ACTION: Check that the source and target docbases are both running the same version of the eContent Server. This warning could be the result of incompatible rules for dumping and loading folder objects. The folder referenced in this error message should be checked at the end of the replication run to see if it is properly linked into its parent folders.
PARAMS:

ERROR: [DM_FOLDER_W_MERGE_ANCESTOR_ID]

SEVERITY: WARNING
DESCRIPTION: DDS Unable to resolve local id for folder link %s in folder %s. Parent links in folder %s may not have been properly loaded.
CAUSE: An error was encountered in a load operation while attempting to merge the folder links of an incoming folder with an existing docbase folder. The error was encountered while attempting to fetch a folders parent folders in order to set the proper ancestor_id values for this target docbase. The specific cause was that there was no known replica of the parent folder value in the local docbase – the folder contained an i_folder_id value which could not be mapped to a local id. The folder will be loaded but the ancestors for this uknown folder cannot be added at this time. It is possible that the unknown folder will be added later in the replication process and this inconsistency will be resolved automatically at that time.
ACTION: Check that the source and target docbases are both running the same version of the eContent Server. This warning could be the result of incompatible rules for dumping and loading folder objects. The folder referenced in this error message should be checked at the end of the replication run to see if it is properly linked into its parent folders.
PARAMS:

ERROR: [DM_FOLDER_T_MERGE_PROP9]

SEVERITY: TRACE
DESCRIPTION: D Completed folder path changes to subfolders of %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FOLDER_T_MERGE_PROP7]

SEVERITY: TRACE
DESCRIPTION: S Propagating folder path changes: appending path %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FOLDER_T_MERGE_PROP4]

SEVERITY: TRACE
DESCRIPTION: S Propagating folder path changes: checking deleted path: %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FOLDER_T_MERGE_ADD]

SEVERITY: TRACE
DESCRIPTION: SD Adding folder path %s to folder object %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FOLDER_T_MERGE_CHECK_NEW]

SEVERITY: TRACE
DESCRIPTION: DS Checking local folder path for folder %s, folder_path=%s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FOLDER_T_MERGE_PROP1]

SEVERITY: TRACE
DESCRIPTION: D Propagating folder path changes to subfolders of %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FOLDER_T_MERGE_PROP3]

SEVERITY: TRACE
DESCRIPTION: D Propagating folder path changes: checking subfolder %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FOLDER_T_MERGE_PROP6]

SEVERITY: TRACE
DESCRIPTION: S Propagating folder path changes: checking added path: %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FOLDER_T_MERGE_CHECK_OLD]

SEVERITY: TRACE
DESCRIPTION: DSS Checking local folder path for folder %s, folder_path=%s, tgt_path=%s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FOLDER_T_MERGE_PROP2]

SEVERITY: TRACE
DESCRIPTION: D Propagating folder path changes: subfolder %s skipped.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FOLDER_T_MERGE_DELETE]

SEVERITY: TRACE
DESCRIPTION: SD Removing folder path %s from folder object %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FOLDER_T_MERGE_PROP5]

SEVERITY: TRACE
DESCRIPTION: SI Propagating folder path changes: deleting path %s at index %d.
CAUSE:
ACTION:
PARAMS:

nahoru

DM_FOREIGN

ERROR: [DM_FOREIGN_F_TYPE_INIT]

SEVERITY: FATAL
DESCRIPTION: Could not create dm_reference type. The type manager returned an error from the Store operation. During docbase initialization, the server could not create the type for dm_reference. Since the server was attempting to create the type, the server must be attempting to create a new docbase or to upgrade a docbase from a pre-4.0 version.
CAUSE: The type manager returned a failure from the attempt to create the new type.
ACTION: Look at the error logged by the type manager. Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_FOREIGN_F_MAP_INIT1]

SEVERITY: FATAL
DESCRIPTION: Could not create dm_docbaseid_map type. The type manager returned an error from the Store operation. During docbase initialization, the server could not create the type for dm_docbaseid_map. Since the server was attempting to create the type, the docbase must be being created or must be being upgraded from a pre-3.0 version. If neither of these are true then this may be the source of the problem.
CAUSE: The type manager returned a failure from the attempt to create the new type.
ACTION: Look at the error logged by the type manager. Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_FOREIGN_F_BAD_VSTAMP]

SEVERITY: FATAL
DESCRIPTION: LL The version stamp for the dm_reference type was %d but was expected to be %d. You may be running a version of the Documentum server which is incompatible with the Docbase. During docbase initialization, the version stamp for the dm_reference type was found to be at an unexpected state. The version stamp is stored in the dmi_vstamp table with i_application = dm_reference.
CAUSE: Could be running an incompatible version of the Documentum server.
ACTION: Check the version of the server you are attempting to run to be sure it is compatible with the docbase. If they are consistent, report this message and any parameters to your Documentum site representative.
PARAMS: %d – the type version stamp %d – the version stamp expected by the server executable

ERROR: [DM_FOREIGN_F_TYPE_CONVERSION]

SEVERITY: FATAL
DESCRIPTION: I Failed to convert type dm_reference to version %d. During docbase initialization, the version stamp for the dm_reference type indicated that it needed to be upgraded to match the current server version. This upgrade procedure failed.
CAUSE: Type conversion failed.
ACTION: Check the version of the server to make sure it is compatible with the current version of the docbase. Check previous errors in the server log file and for additional error information (if any) in the database error log files.
PARAMS: %d – the type version stamp

ERROR: [DM_FOREIGN_F_MAP_INIT2]

SEVERITY: FATAL
DESCRIPTION: LL The version stamp for the dm_docbaseid_map type was %d but was expected to be %d. During docbase initialization, the version stamp for the dm_docbaseid_map type was found to be at an unexpected state. The version stamp is stored in the dmi_vstamp table with i_application = dm_docbaseid_map.
CAUSE: Could be running an incompatible version of the Documentum server.
ACTION: Check the version of the server you are attempting to run to be sure it is compatible with the docbase. If they are consistent, report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_FOREIGN_E_INTERNAL_ERROR]

SEVERITY: ERROR
DESCRIPTION: I Internal error (%d) in Reference Object operation. Similar to an assertion check, this error is generated by an unexpected occurrence in Reference Object handling.
CAUSE: Internal error.
ACTION: Check for previous errors which could give more detail on the cause of the problem. Also check the server and session logs for any errors which could have led to the problem.
PARAMS: %1d – marker to which operation produced the error.

ERROR: [DM_FOREIGN_E_SERVER_SECURITY]

SEVERITY: ERROR
DESCRIPTION: S Distributed Features are not accessible on docbase %s because it uses an incompatible security mode. Docbases must use ACL mode security to participate in distributed operations. An attempt to create a distributed relationship or to move data between docbases was attempted, but could not be satisfied because one of the docbases was not using ACL mode security. The action cannot be performed unless the docbase is converted to use ACL mode security.
CAUSE: The docbase does not support the requested operation.
ACTION: The action cannot be performed unless the docbase is upgraded to use ACL mode security.
PARAMS: %1s – the incompatible docbases name.

ERROR: [DM_FOREIGN_E_REPLICA_FETCH]

SEVERITY: ERROR
DESCRIPTION: DSS Error in Distributed Operation due to the inibility to fetch/create the replica object with id %s. Type Name: %s. Create Flag: %s. An error occurred during replica operation because of the failure to fetch the indicated object from the database. If the above create flag is True, then the attempt was to create a new object with the specified id.
CAUSE: Failure to fetch replica object.
ACTION: Check for previous error messages which give more detail on problem.
PARAMS: %s – The replica object id %s – The type name %s – T if creating a new object, F otherwise

ERROR: [DM_FOREIGN_E_REF_CREATE]

SEVERITY: ERROR
DESCRIPTION: SS Error creating reference to object %s. Could not save the local dm_reference object (%s). The creation of a reference object failed because of an error saving the local dm_reference object.
CAUSE: The server could not create the local object.
ACTION: Check for previous errors which should give more detail on the cause of the problem.
PARAMS: %1s – the reference object id. %2s – the local object which could not be saved.

ERROR: [DM_FOREIGN_E_CURSOR_FAIL]

SEVERITY: ERROR
DESCRIPTION: SSS In operation %s an attempt to execute cursor failed query was: %s error from database system was: %s During an attempt to execute a database cursor, a failure occurred. The error message gives the reference operation that was being performed, the query on which the failure occurred, and the database error string.
CAUSE: The cursor is executed and failed because of possible db errors.
ACTION: Check for previous errors which should give more detail on the cause of the problem.
PARAMS: %1s – the referenced operation %2s – the cursor query %3s – the database error string

ERROR: [DM_FOREIGN_E_INDEX_CREATE]

SEVERITY: ERROR
DESCRIPTION: SS Error during type initialization. Could not create index on %s.%s. The call to create a database index on the dm_reference type failed.
CAUSE: The create index command failed
ACTION: Check for additional logged errors for more information – especially for any database errors. Check the database server logs for database index creation errors.
PARAMS: %1s – The type name (dm_reference) %2s – The first column specified in the index create request

ERROR: [DM_FOREIGN_E_SOURCE_AMBIGUOUS]

SEVERITY: ERROR
DESCRIPTION: SS The requested source object (%s) does not specify a unique object in docbase %s. The creation of a reference object failed because the requested object name matched more than one object in the source docbase.
CAUSE: The requested object name was ambiguous.
ACTION: Create the object reference by id to get the desired object.
PARAMS: %1s – the requested object name and path %2s – the referenced docbase name

ERROR: [DM_FOREIGN_E_REFRESH_NOJOB]

SEVERITY: ERROR
DESCRIPTION: DD Could not fetch the dm_job object which defines the replication parameters for replica %s. Job id from dm_reference: %s. The replica refresh operation must fetch the dm_job object which originally caused the replication in order to obtain the replication options. This error indicates that the job object could not be fetched.
CAUSE: The replica may no longer have a valid parent job. Or the dm_reference for the replica may not indicate the proper job id.
ACTION: Check the existence of the parent dm_job for the replication task.
PARAMS: %s – The replica object on which the error was encountered. %s – The object id of the job as obtained from the dm_reference

ERROR: [DM_FOREIGN_E_RENDITION_DELETE]

SEVERITY: ERROR
DESCRIPTION: DD Error returned from server DESTROY_CONTENT call to destroy local rendition of object %s. Local object id is %s.
CAUSE: The server destroy call failed.
ACTION: Check the session log for the error message logged by the server which should further describe the problem.
PARAMS: %s – The global object id. %s – The object id of the local replica.

ERROR: [DM_FOREIGN_E_SOURCE_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: DS The requested source object was not found. Could not fetch object (%s) from docbase %s. The creation or refresh of a reference object failed because the requested object could not be found in the referenced docbase.
CAUSE: The requested object was not found.
ACTION: Check to make sure the remote docbase is available and accessible. Verify the object id specified and make sure that it exists. Check for other messages that may indicate an error during the fetch operation.
PARAMS: %1s – the requested object id %2s – the referenced docbase name

ERROR: [DM_FOREIGN_E_SRC_FOR_UPDATE]

SEVERITY: ERROR
DESCRIPTION: DSD Could not fetch master object %s from docbase %s. Unable to update replica object %s. The save of the specified object failed because of the inability to fetch the replicas source object. The error could have been caused by an internal error or by the non-existence of the master object.
CAUSE: Object could not be fetched.
ACTION: Check for previous error message which may give more detail on the problem. Check for the existence of the master object.
PARAMS: %s – The object id of the source object. %s – The source docbase. %s – The local replica object id.

ERROR: [DM_FOREIGN_E_ACL_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: SSSS Error processing reference object – could not find acl %s.%s in docbase %s for sysobject (%s). A create or update operation on a reference/replica failed due to the inability to find the named acl object associated with a referenced object.
CAUSE: An attempt to query for the acl by name failed.
ACTION: Check if the ACL exists for the specified object. If not then this object is not consistent and cannot be referenced or replicated. Check other error messages which should give a more detailed explanation of the error. Also check the server session logs for errors.
PARAMS: %1s – the acl domain %2s – the acl name %3s – the docbase where the acl should have been %4s – the object id of the sysobject which points to the acl

ERROR: [DM_FOREIGN_E_REF_IMMUTABLE]

SEVERITY: ERROR
DESCRIPTION: S Attempt to modify an immutable field (%s) of a dm_reference object. The update operation on a dm_reference object attempted to modify an immutable field. Some fields of the dm_reference object cannot be changed once they are set at object creation time. Refer to the Documentation on distributed objects for more information on these fields.
CAUSE: This field cannot be changed in an existing dm_reference object.
ACTION: Do not attempt to update this field.
PARAMS: %s – the modified field name

ERROR: [DM_FOREIGN_E_REFERENCE_NONE]

SEVERITY: ERROR
DESCRIPTION: SSSS Error dereferencing the object (%s) – the referenced object was not found in docbase %s. Remote object id was (%s) and version label requested was %s. Referencing through a reference/replica object found no match at the remote docbase. Either the referenced object has been deleted or the user requested a version label for which there is no matching version of the remote object.
CAUSE: Likely either the referenced object has been deleted or the user requested a version label for which there is no matching version of the remote object.
ACTION: Query the remote docbase to verify the existence/non-existence of the referenced object. If it has been deleted the user may want to consider removing the reference to the object.
PARAMS: %1s – The object id of the local object. %2s – The remote docbase name. %3s – The referenced object. %4s – The version label binding applied.

ERROR: [DM_FOREIGN_E_ALLOC_ID]

SEVERITY: ERROR
DESCRIPTION: ID Could not allocate new object id for tag %d in replication of object %s. During a replication action, the system attempted to pre-allocate a local object id for the replica of the indicated object. The call to create the id failed.
CAUSE: Could be a server failure of some kind. Unlikely, but could indicate an exhaustion of available ids for the indicated tag.
ACTION: Check server/session log for error messages. Test to see if you can directly create a new object of the specified type.
PARAMS: %s – the tag for which the id was requested. %s – the object being replicated.

ERROR: [DM_FOREIGN_E_DIST_REFRESHACL]

SEVERITY: ERROR
DESCRIPTION: S Error in refresh security operation for object (%s). An error occurred during a distributed object refresh. The local replica or reference link could not be updated with the current acl copy from the master docbase. The session log (at the local server) should give more information on why the action failed.
CAUSE: The local server refused the refresh request.
ACTION: Check for previous error messages and check the server session log.
PARAMS: %1s – The object id of the local object.

ERROR: [DM_FOREIGN_E_MODIFIED_MASTER]

SEVERITY: ERROR
DESCRIPTION: DD Could not update replica %s because its master object %s is already modified in the users cache. Either save or revert the changes to the master object first. The save of the specified replica object failed because the master object was found to be modified in the users client-side cache. During the distributed save operation, changes made to the replica object are moved over to the master docbase. If the master object is fetched and found to be modified, the operation cannot safely copy the replica changes into the object of unknown state.
CAUSE: Object was modified.
ACTION: Revert the master object specified in the error message and retry the operation.
PARAMS: %s – The local replica object id. %s – The object id of the source object.

ERROR: [DM_FOREIGN_E_REFRESH_DEEP]

SEVERITY: ERROR
DESCRIPTION: D A simple refresh operation on object %s could not be done because the object had relationships which were changed and also needed refreshing. A deep refresh is required on this object. The attempt to refresh a replica or reference object failed because the object had relationships (usually VDM children) which were modified and would need refreshing as well. A refresh operation can be run in two modes: – deep refresh: – the object is refreshed and all objects related to it are also refreshed then all objects related to those are refreshed, etc. – shallow refresh: – an attempt is made to refresh only the specified objects and not follow all its relationships. If a shallow refresh is requested but the objects relationships are found to have changed, then a deep refresh is required.
CAUSE: The object had modified relationships.
ACTION: Request a full refresh of the object (default in refresh api).
PARAMS: %1s – The object id of the local object.

ERROR: [DM_FOREIGN_E_REFERENCE_GLOBAL]

SEVERITY: ERROR
DESCRIPTION: SS Attempt to locally modify a global attribute of a reference object. Attribute %s cannot be updated on reference object %s. Reference objects are pointers to other documents commonly on outside docbases. The global attributes of the reference objects meta-data mirror the source document and cannot be changed directly. Only local attributes of reference objects can be locally modified. Global attribute changes can only be made at the source document. The source document can be updated through the reference indirect syntax: set,session,@object_id,attribute_name save,session,@object_id
CAUSE: Object is a reference and cannot be directly updated.
ACTION: Check update statement to see if update is really desired on this object and alter statement if appropriate. If the referenced object must be updated, the update can be made by query at the master docbase or by indirect api operations (@object_id syntax).
PARAMS: %1s – name of global attribute to which change was attempted %2s – object id of reference object

ERROR: [DM_FOREIGN_E_MAP_COLLECTION]

SEVERITY: ERROR
DESCRIPTION: Error building collection of existing dm_docbaseid_map objects. During server startup, the server builds a cache of the existing docbaseid map objects, storing the ids of the docbases from which objects have been replicated and the internal_id offsets for thoses docbases. To do this, the server runs a query to build a collection of the existing map objects. This error is given when that query fails.
CAUSE: Collection operation failed.
ACTION: Check for previous error messages, especially those from the type the type manager or database manager. Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_FOREIGN_E_REFINFO_NOT_SYSOBJ]

SEVERITY: ERROR
DESCRIPTION: S ReferenceFetchInfo Operation failed because caller requested acl information on a non-sysobject (%s). Server call to get replica or reference refresh information failed because the caller (dmcl) requested improper information for a non-sysobject based object.
CAUSE: The requested object was not of a sysobject-based type.
ACTION: Report error to Document Technical Support.
PARAMS: %1s – the requested object id

ERROR: [DM_FOREIGN_E_VERSION_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: DDLL Replica object %s is out of date with its master object %s. Master Vstamp: %d, Replica Vstamp: %d. You must refresh the local replica before applying updates to it. The save of the specified replica object failed because the replica was not up-to-date with its source object.
CAUSE: Object out-of-date
ACTION: Refresh the replica object specified in the error message and retry the operation.
PARAMS: %s – The local replica object id. %s – The object id of the source object. %d – The master version stamp. %d – The replica version stamp.

ERROR: [DM_FOREIGN_E_REF_INCOMPATIBLE]

SEVERITY: ERROR
DESCRIPTION: SSS The local object (%s) references an object in an incompatible docbase (%s). This object cannot be dereferenced until the remote docbase is upgraded. The remote docbase version is currently %s. A reference or replica object points to an object in a docbase that is not compatible with the local docbase. The object cannot be dereferenced until the remote docbase is upgraded.
CAUSE: Remote docbase is not compatible with the local docbase.
ACTION: Until the remote docbase is upgraded, the local object cannot be dereferenced. To access the remote object you must go directly to that docbase and fetch the referenced object explicitly.
PARAMS: %1s – The object id of the local object. %2s – The remote docbase name. %3s – The version of the remote docbase.

ERROR: [DM_FOREIGN_E_REF_FETCH_INFO]

SEVERITY: ERROR
DESCRIPTION: SSS Error fetching information for the object referenced by local object (%s). Remote docbase is %s and remote object id is (%s). In order to dereference a local reference or replica object, the dmcl sends a special ReferenceFetchInfo apply call to the server to compute the remote object to which the reference points and to determine if the remote object is out-of-date with the local mirror object. This error indicates that the apply call has failed.
CAUSE: The remote docbase may be inaccessible.
ACTION: Check for previous errors giving more specific information. Check that the referenced docbase is reachable and available.
PARAMS: %1s – The object id of the local object. %2s – The remote docbase name. %3s – The referenced object.

ERROR: [DM_FOREIGN_E_PROCESSREPLICA]

SEVERITY: ERROR
DESCRIPTION: SDD Error processing replica object %s. Global object id: %s. Source id: %s. An error occurred during replica refresh as the replica object was being built from a copy of the source object. The error may have occurred in copying the object values from the source (which may indicate some sort of type inconsistency between the docbases) or in applying replication filter/remapping options. Previous errors in the log should indicate more about the nature of the problem.
CAUSE: Failure to build new version of replica object.
ACTION: Check for previous error messages which give more detail on problem.
PARAMS: %s – The replica object id (NEW_OBJECT if new object). %s – The global object id. %s – The source object id (commonly the same as the global id).

ERROR: [DM_FOREIGN_E_REF_UPDATE]

SEVERITY: ERROR
DESCRIPTION: SS Error updating reference object %s. Could not save the local dm_reference object (%s). The update of reference object information failed because of an error saving the local dm_reference object.
CAUSE: The server could not save the local object.
ACTION: Check for previous errors which should give more detail on the cause of the problem.
PARAMS: %1s – the referenced objects id. %2s – the local object which could not be saved.

ERROR: [DM_FOREIGN_E_OBJECT_REFRESH]

SEVERITY: ERROR
DESCRIPTION: DD Error returned from server ReplicaRefresh call on attempt to save local replica of object %s. Local object id is %s.
CAUSE: The server refresh call failed.
ACTION: Check the session log for the error message logged by the server which should further describe the problem.
PARAMS: %s – The global object id. %s – The object id of the local replica.

ERROR: [DM_FOREIGN_E_REFRESH_SAVE]

SEVERITY: ERROR
DESCRIPTION: The server ReferenceRefresh operation failed. The refresh request failed due to an error saving the updated local object.
CAUSE: The failure occurred on the server request to update the local object.
ACTION: Check other error messages which should give a more detailed explanation of the error. Since the error likely occurred on the server check the local server session log. It should give more information on the error.
PARAMS: none

ERROR: [DM_FOREIGN_E_UPDATE_NOLOCALUPD]

SEVERITY: ERROR
DESCRIPTION: S A distributed update to object %s was partially completed. The updates to the master object were saved correctly but an error prevented the saving of local attribute changes. The save of a replica or reference object succeeded only partially. The remote updates were performed and committed, but the local updates could not be applied. The user should attempt a manual refresh of the object (refresh api) to bring it up-to-date with the remote changes.
CAUSE: Object could not be refreshed following update.
ACTION: Check for previous error message which may give more detail on the problem. Re-try the refresh by using the refresh operation. If that still fails try enabling tracing during the refresh call.
PARAMS: %s – The object id of the local object.

ERROR: [DM_FOREIGN_E_COULD_NOT_CONNECT]

SEVERITY: ERROR
DESCRIPTION: S Distributed Operation failed because a connection could not be established to docbase %s. An attempt to establish a connection to another docbase failed. The current command could not be processed.
CAUSE: The docbase could be unknown or unavailable at this time. Or the login attempt could have been denied.
ACTION: Check the error log for previous errors that may indicate the exact reason for the connection failure. Attempt to login directly to the desired docbase as a diagnostic step.
PARAMS: %2s – the referenced docbase name

ERROR: [DM_FOREIGN_E_NEW_REPLICA]

SEVERITY: ERROR
DESCRIPTION: D Error during Distributed Update operation. The local changes to replica object %s could not be applied due to the inability to refetch the replica object following the remote update. When a replica object is updated and the update includes both global and local changes, the remote changes are applied first, the replica object is refreshed, and then the local changes are applied. This save of the specified replica object failed because the replica could not be fetched following the refresh. Note that when this error is received, the master object has been updated – only the local attribute changes have failed. This state will be described by later warning messages.
CAUSE: Error in attribute copy.
ACTION: Check for previous error message which may give more detail on the problem.
PARAMS: %s – The local replica object id.

ERROR: [DM_FOREIGN_E_REP_BADCOPY]

SEVERITY: ERROR
DESCRIPTION: DD Error during Distributed Update operation. The attributes of replica object %s could not be copied to master object %s. The save of the specified replica object failed because the copy of changes from the replica to the master did not succeed.
CAUSE: Error in attribute copy.
ACTION: Check for previous error message which may give more detail on the problem.
PARAMS: %s – The local replica object id. %s – The object id of the source object.

ERROR: [DM_FOREIGN_E_PURGE_MIRROR]

SEVERITY: ERROR
DESCRIPTION: SS Cannot purge the replica objects for the job (%s) because %s.
CAUSE: See reason.
ACTION:
PARAMS: %s – replication job id %s – reason

ERROR: [DM_FOREIGN_E_REF_DIRECT_DELETE]

SEVERITY: ERROR
DESCRIPTION: You cannot delete this dm_reference object directly. To properly remove a reference link delete the mirror object, which will cause the associated dm_reference object to be deleted as well. The attempt to explicitly delete a dm_reference object failed. The proper way to remove a reference link is not to delete the dm_reference object but to delete the associated mirror object. This will also trigger the delete of the dm_reference entry. The mirror object can be found via the dm_reference.r_mirror_object_id field. This check can be bypassed with system admin privilege.
CAUSE: Incorrect protocol for deleting a reference object.
ACTION: Delete the associated mirror object instead.
PARAMS: None

ERROR: [DM_FOREIGN_E_PARM]

SEVERITY: ERROR
DESCRIPTION: SS Error in distributed operation. Bad parameter: %s = %s. An error occurred due to a bad operational parameter. This may indicate a protocol error between the client and server, possibly an incompatibility between the server and client versions.
CAUSE: Bad parameter.
ACTION: Check for previous error message which may give more detail on the problem. Check the server and client versions.
PARAMS: %s – The parameter name. %s – The parameter value.

ERROR: [DM_FOREIGN_E_PURGE_REF_OBJ]

SEVERITY: ERROR
DESCRIPTION: S Cannot purge the replica objects because %s.
CAUSE: See reason.
ACTION:
PARAMS: %s – reason

ERROR: [DM_FOREIGN_E_REPLICA_GLOBAL]

SEVERITY: ERROR
DESCRIPTION: SSS Attempt to locally modify a global attribute of a foreign object. Attribute %s.%s cannot be updated on replica object %s. Replica objects are copies of objects from other docbases imported locally for document sharing. They are managed internally by documentum replication services. Only local attributes of replica objects can be locally modified. Global attribute changes can only be made at the source object. To update the object you must connect directly to the master docbase and update the master copy, then replicate the changes back to your local docbase.
CAUSE: Object is a replica and cannot be updated.
ACTION: Check update statement to see if update is really desired on this object and alter statement if appropriate. If foreign object must be updated, the update can be made at the master docbase. If a local-only update is necessary, consider making a local copy of the object (see SAVEASNEW method).
PARAMS: %1s – type name of replica object %2s – name of global attribute to which change was attempted %3s – object id of replica object

ERROR: [DM_FOREIGN_E_REFRESH_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: SLLSS Refresh operation on object (%s) failed because the object fetched from the master docbase was inconsistent with the local object. Global vstamp: %d, Refresh vstamp: %d Master id: %s, Refresh id: %s. The refresh request was refused by the local server because the information with which to refresh did not appear consistent. It either came from the wrong object or had a version stamp that was prior to the latest local copy.
CAUSE: This may be caused by an inconsistency in the local copy of the object.
ACTION: If the object cannot be refreshed on repeated attempts, delete the copy and recreate the reference/replica.
PARAMS: %1s – The object id of the local object. %2d – The Global Vstamp as recorded locally. %3d – The vstamp of the refresh object. %4s – The master object id as recorded locally. %5s – The object id of the refresh object.

ERROR: [DM_FOREIGN_E_REF_MIRROR_CREATE]

SEVERITY: ERROR
DESCRIPTION: SS Error creating reference to object %s. Could not save the local mirror object (%s). The creation of a reference object failed because of an error creating a new object to hold the copy of the referenced objects meta-data.
CAUSE: The server could not create the local sysobject reference.
ACTION: Check for previous errors which should give more detail on the cause of the problem.
PARAMS: %1s – the referenced objects id. %2s – the local object which could not be saved.

ERROR: [DM_FOREIGN_E_NO_OBJECT_GIVEN]

SEVERITY: ERROR
DESCRIPTION: The reference cannot be created because no object to reference was specified. Either the reference_by_id or the reference_by_name attribute must be set. The save request of a dm_reference object failed because one of the required attributes – reference_by_id or reference_by_name – was not specified.
CAUSE: One of – reference_by_id or reference_by_name – must be set.
ACTION: Set the required field and resave the object.
PARAMS: None

ERROR: [DM_FOREIGN_E_NOT_DISTRIBUTED]

SEVERITY: ERROR
DESCRIPTION: Distributed operation requested on an object which is neither a replica nor a reference link. Distributed operations seek to refresh, update or lookup information through a pointer to a remote object. This type of operation can be done with a replica or a reference object. This error was caused by an attempt to execute a distributed operation on a local non-distributed object.
CAUSE: The operation is not legal.
ACTION: Correct the request.
PARAMS: None

ERROR: [DM_FOREIGN_E_PURGE_DANG_REF]

SEVERITY: ERROR
DESCRIPTION: SS Cannot purge the dangling reference objects for the job (%s) because %s.
CAUSE: See reason.
ACTION:
PARAMS: %s – replication job id %s – reason

ERROR: [DM_FOREIGN_E_AMBIGUOUS_REQUEST]

SEVERITY: ERROR
DESCRIPTION: The reference cannot be created because both the object to reference was specified both by name and by id. Only one of the reference_by_id and reference_by_name fields can be set. The save request of a dm_reference object failed because values were specified for both of the mutually-exclusive fields: reference_by_id and reference_by_name.
CAUSE: Values were specified for both of the mutually-exclusive fields: reference_by_id and reference_by_name.
ACTION: Choose one option and set that field only, then resave the object.
PARAMS: None

ERROR: [DM_FOREIGN_E_EXACT_ID_NAME]

SEVERITY: ERROR
DESCRIPTION: The reference cannot be created because an invalid binding condition was specified. When referencing a document by Name, VERSION_LABEL binding must be used. The save request of a dm_reference object failed because the value given for one of the attributes was not valid for that field. The field was the binding_condition attribute which specifies to bind by Version-label or by Exact-Id. The Exact-Id binding type can only be used when the remote document is referenced by ID, not by name.
CAUSE: The value given for one of the attributes was not valid.
ACTION: Correct the specified attribute and resave the object.
PARAMS: None

ERROR: [DM_FOREIGN_E_REF_NOT_ALLOWED]

SEVERITY: ERROR
DESCRIPTION: S Illegal operation invoked on a reference object. This operation (%s) should be directed to the source object rather than the reference. An update operation was requested on a reference object which was not appropriate for a reference. The request (eg. checkout) needs to be performed on the source object rather than the reference object. This can be easily done through the dereference syntax: checkout,c,@ref_obj <- applies operation to source object
CAUSE: Operation was not appropriate for a reference object.
ACTION: Check the request to see if it is an attempt to modify the source object: if so, modify the request to direct the update there if not, check that the update does not attempt to modify globally managed attributes of the local reference.
PARAMS: %1s – the operation type

ERROR: [DM_FOREIGN_E_REPLICA_DELETE]

SEVERITY: ERROR
DESCRIPTION: DD Error returned from server DESTROY_REPLICA call to destroy local replica of object %s. Local object id is %s.
CAUSE: The server delete call failed.
ACTION: Check the session log for the error message logged by the server which should further describe the problem.
PARAMS: %s – The global object id. %s – The object id of the local replica.

ERROR: [DM_FOREIGN_E_REP_BADCOPY2]

SEVERITY: ERROR
DESCRIPTION: D Error during Distributed Update operation. The modified attributes of replica object %s could not be copied to temporary object prior to save to source docbase. The save of the specified replica object failed because the copy of changes from the replica to the master did not succeed.
CAUSE: Error in attribute copy.
ACTION: Check for previous error message which may give more detail on the problem.
PARAMS: %s – The local replica object id.

ERROR: [DM_FOREIGN_E_REF_UPDATE_PRIV]

SEVERITY: ERROR
DESCRIPTION: S You do not have privilege to %s this object. The update operation on a dm_reference object failed due to insufficient privilege.
CAUSE: Insufficient privilege to perform the requested update.
ACTION: Check for privileges on the specified object.
PARAMS: %s – the type of update operation

ERROR: [DM_FOREIGN_E_MERGEREPMAP]

SEVERITY: ERROR
DESCRIPTION: Error building map of related object in replica refresh operation. The replica refresh operation must compute the set of all related objects and determine the state of those objects at the source and local sites. This error message is given when a failure is encountered during the building of that map. Previous error messages should give more detail on the error.
CAUSE: Failure to compute related object set.
ACTION: Check for previous error messages which give more detail on problem.
PARAMS: None

ERROR: [DM_FOREIGN_E_FOLDER_MERGE]

SEVERITY: ERROR
DESCRIPTION: D A Replication error during computation of the new folders links for replica object %s in its target docbase. An error occurred in replication during the folder-merge processing of a replica object. The error could either be in the creation of a new replica or the refreshing of an existing one. Folder merging determines which folders the replica object should be linked into in the target docbase. It involves merging the attributes from the new replica object with any existing links in the local copy.
CAUSE: Could be a bad folder id or an inability to fetch a referenced folder.
ACTION: Check for previous error message which may give more detail on the problem. Enable replication tracing to collect more information.
PARAMS: %s – The replica object id.

ERROR: [DM_FOREIGN_E_BUILDREPMAP]

SEVERITY: ERROR
DESCRIPTION: Error building map of related object in replica refresh operation. The replica refresh operation must compute the set of all related objects and determine the state of those objects at the source and local sites. This error message is given when a failure is encountered during the building of that map. Previous error messages should give more detail on the error.
CAUSE: Failure to compute related object set.
ACTION: Check for previous error messages which give more detail on problem.
PARAMS: None

ERROR: [DM_FOREIGN_E_REPLICA_UPDATE]

SEVERITY: ERROR
DESCRIPTION: SS Attempt to update a foreign object. The object %s of type %s cannot be updated because it is a replica. Replica objects are copies of objects from other docbases imported locally for document sharing. They are imported via non-relocate Load operations as part of a replicated docbase setup. Replica objects cannot be updated. To update the document you must connect directly to the master docbase and update the master copy, then replicate the changes back to your local docbase. The master docbase can be found using the object id of the foreign object.
CAUSE: Object is a replica and cannot be updated.
ACTION: Check update statement to see if update is really desired on this object and alter statement if appropriate. If foreign object must be updated, the update can be made at the master docbase. If a local-only update is necessary, consider making a local copy of the object (see SAVEASNEW method).
PARAMS: %s – object id of replica %s – type name of replica object

ERROR: [DM_FOREIGN_E_REFRESHACL_SAVE]

SEVERITY: ERROR
DESCRIPTION: The server ReferenceRefreshAcl operation failed. The refresh request failed due to an error saving the updated local object security.
CAUSE: The failure occurred on the server request to update the local object.
ACTION: Check other error messages which should give a more detailed explanation of the error. Since the error likely occurred on the server check the local server session log. It should give more information on the error.
PARAMS: none

ERROR: [DM_FOREIGN_E_REFRESH_SECURITY]

SEVERITY: ERROR
DESCRIPTION: SD The user (%s) does not have permission to refresh object %s. The attempt to refresh a replica or reference object failed because the current user does not have permission to fetch all of the required data from the source docbase(s).
CAUSE: The user did not have permission to fetch the source object.
ACTION: Ask the docbase aministrator to refresh the object and/or check the ability of the local server to access the data at the source.
PARAMS: %s – The current user. %s – The object id of the local object.

ERROR: [DM_FOREIGN_E_NOT_SYSADMIN]

SEVERITY: ERROR
DESCRIPTION: Cannot update foreign objects without at least System Admin privilege. Replica objects are normally read-only. They cannot be set to updatable without system admin privilege.
CAUSE: Insufficient privilege for the current command.
ACTION: Check for replica update requirements. In general, replicas should not be directly updated as it may affect operation of replication processing.
PARAMS:

ERROR: [DM_FOREIGN_E_DEREFERENCE_ERROR]

SEVERITY: ERROR
DESCRIPTION: D Error referencing through object (%s). An error was encountered while dereferencing a Reference Object link. On commands such as fetch,c,@obj_id the action is redirected to the docbase/object pointed to by the local reference object obj_id. This involves looking up the local reference information (in the dm_reference table), connecting to the remote docbase, and determining which version of the referenced object the command should apply to.
CAUSE: The error could be caused by a number of things – most likely the inability to reach the remotely referenced docbase. Previous errors in the error stream should give a better indication of the specific problem.
ACTION: Check for previous errors giving more specific information. Check that the referenced docbase is reachable and available.
PARAMS: %1s – The object id of the local object.

ERROR: [DM_FOREIGN_E_OPEN_TRANSACTION]

SEVERITY: ERROR
DESCRIPTION: The reference object operation cannot be executed while inside of a user transaction. A purge replica mirror or reference cleanup 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 reference object operation has a currently outstanding transaction open.
ACTION: Complete the current transaction and retry.
PARAMS:

ERROR: [DM_FOREIGN_E_REF_CLIENT_VERSION]

SEVERITY: ERROR
DESCRIPTION: DMCL version must be 4.0 or higher to create a distributed reference. The request to create a new reference was rejected because the dmcl version was not 4.0 or higher.
CAUSE: The DMCL is too old.
ACTION: The user must upgrade to a new dmcl to create reference objects.
PARAMS: None

ERROR: [DM_FOREIGN_E_LOAD_NEW_MAP]

SEVERITY: ERROR
DESCRIPTION: L Error creating new dm_docbaseid_map object for docbase %d. During a load operation an object from a foreign docbase was encountered that had not previously had objects replicated to this docbase. The object could not be loaded due to a failure creating a new docbaseid map for this docbase.
CAUSE: Save operation failed on new dm_docbaseid_map object.
ACTION: Check for previous error messages, especially those from the object manager or database manager. Report this message and any parameters to your Documentum site representative. If solution cant be foudn
PARAMS: %d – docbase id from which objects are being imported

ERROR: [DM_FOREIGN_E_REFRESH_WRONGACL]

SEVERITY: ERROR
DESCRIPTION: SSSSS Reference security refresh failed: ACL object passed by dmcl did not match the reference mirror object. Reference id %s. ACL object name: %s, domain: %s. Mirror object name: %s, domain: %s. The refresh request failed because the acl object passed down by the client for the refresh did not match the mirror object in the local docbase. The object does not appear to be the acl object from the reference source.
CAUSE: The source objects acl may be inconsistent, or an undetected failure in the refresh operation made the two look inconsistent.
ACTION: Check the source object for consistency and retry the refresh action. Check the local server session log for more information. information on the error. If the object cannot be refreshed on repeated attempts, delete the copy and recreate the reference/replica.
PARAMS: %1s – The object id of the local object. %2s – The acl name from the refresh acl argument. %3s – The acl domain from the refresh acl argument. %4s – The acl name in the local mirror object. %5s – The acl domain in the local mirror object.

ERROR: [DM_FOREIGN_E_INVALID_VALUE]

SEVERITY: ERROR
DESCRIPTION: S The reference cannot be created because an invalid value was specified for the attribute: %s. The save request of a dm_reference object failed because the value given for one of the attributes was not valid for that field.
CAUSE: The value given for one of the attributes was not valid.
ACTION: Correct the specified attribute and resave the object.
PARAMS: %1s – the name of the attribute with the invalid value.

ERROR: [DM_FOREIGN_E_MAP_UPDATE_PRIV]

SEVERITY: ERROR
DESCRIPTION: S No privilege to %s dm_docbaseid_map object. You must have at least SYSADMIN privilege. PARAMS: The type of update operation (save, delete).
CAUSE: The user does not have privilege to update the specified type. Sysadmin (or higher) privilege is required.
ACTION: Find system admin user to make required updates.
PARAMS:

ERROR: [DM_FOREIGN_E_DMREF_MISSING]

SEVERITY: ERROR
DESCRIPTION: D Error: no dm_reference record found for object (%s). An error was encountered while dereferencing a Reference Object link. No dm_reference entry was found for the specified object, even though the object indicated it was a replica (i_is_replica = True) or a reference link (i_is_reference = True). This should never be the case. Each reference or replica object in a docbase has a corresponding entry in dm_reference. The dm_reference record points back to the local object by its r_mirror_object_id attribute.
CAUSE: There could be an inconsistency in the docbase.
ACTION: Check for previous error messages and check the session log to see if there was just a query error that made it look like there was no corresponding dm_reference object. Query the docbase to look for a dm_reference object with an r_mirror_object_id equal to the specified object id. Verify that the object indicated by the specified id is indeed a replica or reference link. If the local object is indeed a reference or replica, the best solution may be to delete it and recreate it.
PARAMS: %1s – The object id of the local object.

ERROR: [DM_FOREIGN_E_DIST_REFRESH]

SEVERITY: ERROR
DESCRIPTION: S Error in refresh operation for object (%s). An error occurred during a distributed object refresh. The local replica or reference link could not be updated with the current copy from the master docbase. The session log (at the local server) should give more information on why the action failed.
CAUSE: The local server refused the refresh request.
ACTION: Check for previous error messages and check the server session log.
PARAMS: %1s – The object id of the local object.

ERROR: [DM_FOREIGN_E_PRESAVE]

SEVERITY: ERROR
DESCRIPTION: D Error preparing object %s for Distributed Save operation. The save of the specified object failed. A distribute save operation is one in which multiple docbases must be updated. Examples: updating a replica linking a document to remote folder creating a foreign relationship (eg vdm) between documents. This error message is given when an error occurs while attempting to determine the update requirements for the distributed save.
CAUSE: Object update requirements could not be determined.
ACTION: Check for previous error message which may give more detail on the problem.
PARAMS: %s – The object id of the local object being saved.

ERROR: [DM_FOREIGN_E_DUMPMAP_SRV]

SEVERITY: ERROR
DESCRIPTION: D The source server was unable to properly determine the replication data for object %s. The replica refresh operation involves building a relationship map of all the objects related to the one being refreshed. During the building of this map we encountered an error that prevents the indicated object from being properly replicated.
CAUSE: The source data may not be consistent.
ACTION: Check the source object for consistency.
PARAMS: %s – The object on which the error was encountered.

ERROR: [DM_FOREIGN_E_MAP_CREATE]

SEVERITY: ERROR
DESCRIPTION: Error creating server dm_docbaseid_map cache. During server startup, the server builds a cache of the existing docbaseid map objects, storing the ids of the docbases from which objects have been replicated and the internal_id offsets for thoses docbases. This error is given when the cache creation fails.
CAUSE: Probably the docbaseid_map collection operation failed.
ACTION: Check for previous error messages, especially those from the type the type manager or database manager. Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_FOREIGN_E_COULD_NOT_REFRESH]

SEVERITY: ERROR
DESCRIPTION: SDSD Unable to dynamically refresh %s object (%s) from its source object. The local object may not be an up-to-date copy. Master docbase is %s. Master object is (%s). The attempt to refresh a replica or reference object from its soure object failed for some reason. Previous error messages should give more detail on why the failure occurred. Local docbase operations will continue with the currently cached copy of the object, which may be out-of-date. This refresh could have been requested explicitly by the user or could have been triggered by an update. Note that if this error occurs following an update, the update will have been made successfully, but the update will not be reflected in the local copy.
CAUSE: Could be a number of reasons: – inability to connect to the source docbase – source object no longer exists – inconsistencies in reference/replica catalogs
ACTION: Check other error messages which should give a more detailed explanation of the error. Also check the server session logs.
PARAMS: %1s – indicator of replica or reference refresh %2s – The object id of the local object. %3s – The docbase where the master object resides. %4s – The object id of the master object.

ERROR: [DM_FOREIGN_E_REP_BADCOPY3]

SEVERITY: ERROR
DESCRIPTION: D Error during Distributed Update operation. The local changes to replica object %s could not be reapplied following the distributed save and refresh of the local object. When a replica object is updated and the update includes both global and local changes, the local changes are saved in a temporary copy object while the master object is updated with the global changes. Following the master object, the local changes are re-applied to the replica and the replica object is saved. This save of the specified replica object failed because the copy of changes from a saved copy back to the local replica failed. Note that when this error is received, the master object has been updated – only the local attribute changes have failed. This state will be described by later warning messages.
CAUSE: Error in attribute copy.
ACTION: Check for previous error message which may give more detail on the problem.
PARAMS: %s – The local replica object id.

ERROR: [DM_FOREIGN_E_SOURCE_NOT_SYSOBJ]

SEVERITY: ERROR
DESCRIPTION: D The reference cannot be created because object %s is not a dm_sysobject or dm_sysobject subtype. Only dm_sysobject based objects can be referenced. The creation of a reference object failed because the requested object was not legal to reference.
CAUSE: The requested object was not of a sysobject-based type.
ACTION: This object cannot be referenced.
PARAMS: %1s – the requested object id

ERROR: [DM_FOREIGN_E_REF_TRAN]

SEVERITY: ERROR
DESCRIPTION: DS Error creating reference to object %s. Could not %s transaction to create the local reference object. The creation of a reference object failed because of an error returned from the transaction system.
CAUSE: The server could not begin/commit the transaction.
ACTION: Check for previous errors which should give more detail on the cause of the problem. Check the RDBMS error logs for further indication.
PARAMS: %1s – the referenced object id. %2s – indicates error on transaction begin or commit.

ERROR: [DM_FOREIGN_E_REFRESH_TRAN]

SEVERITY: ERROR
DESCRIPTION: DS Error refreshing reference object %s. Could not %s transaction to update the local reference object. The refresh of a reference object failed because of an error returned from the transaction system.
CAUSE: The server could not begin/commit the transaction.
ACTION: Check for previous errors which should give more detail on the cause of the problem. Check the RDBMS error logs for further indication.
PARAMS: %1s – the reference object id. %2s – indicates error on transaction begin or commit.

ERROR: [DM_FOREIGN_E_REFINFO_NO_ACL]

SEVERITY: ERROR
DESCRIPTION: S ReferenceFetchInfo Operation could not find requested ACL information for object (%s). Server call to get replica or reference refresh information failed because the server could not find the acl for the requested object.
CAUSE: Could not find acl for requested object.
ACTION: Check the object identified by id to see if the ACL indicated by the objects acl_name/acl_domain fields exists. Check the session log for errors which may give further information the the cause of the error.
PARAMS: %1s – the requested object id

ERROR: [DM_FOREIGN_E_OBJECT_VSTAMP]

SEVERITY: ERROR
DESCRIPTION: SLL Cannot load object %s because its version stamp value (i_vstamp = %d) exceeds the maximum allowable distributed version stamp of %d. Currently the system uses to the object version stamp for two purposes with distributed objects. It tracks the version stamp of the local object and the version stamp of the original object from which it was replicated. This imposes a version limit of 64k on each replicated object.
CAUSE: The object being loaded had a version stamp greater than 64k.
ACTION: The object cannot be imported into this docbase unless the version stamp at the master docbase is altered. The easiest way to do this may be to create a new copy of the object (saveasnew) at the master docbase which will start with a new version stamp and then discard the old object.
PARAMS: %s – the object id %d – the object version stamp %d – the maximum allowable version stamp

ERROR: [DM_FOREIGN_E_BAD_FOLDER_LINK]

SEVERITY: ERROR
DESCRIPTION: SS The reference cannot be created because %s is not valid for %s. You must specify an existing folder or cabinet of the local docbase, either by ID (eg. 0b0015b480001b4f) or by Name (eg. /cabinet/subfolder). The save request of a dm_reference object failed because the value given for one of the attributes was not valid for that field. The field was the local_folder_link attribute – which specifies a local folder/cabinet into which to link the resulting reference object. The local_folder_link must specify an existing folder or cabinet. The local_folder_link can be specified by id or by name. In the latter case the full path to the folder must be specified.
CAUSE: The value given for one of the attributes was not valid.
ACTION: Correct the specified attribute and resave the object.
PARAMS: %1s – the invalid attribute value. %2s – the name of the attribute with the invalid value.

ERROR: [DM_FOREIGN_E_REF_MIRROR_UPDATE]

SEVERITY: ERROR
DESCRIPTION: S Error updating reference object %s. Could not save the local mirror object. The update of reference object information failed because of an error saving the updating mirror object – which holds the copy of the referenced objects meta-data.
CAUSE: The server could not save the local sysobject reference.
ACTION: Check for previous errors which should give more detail on the cause of the problem.
PARAMS: %1s – the reference object id.

ERROR: [DM_FOREIGN_E_NOT_IMPLEMENTED]

SEVERITY: ERROR
DESCRIPTION: S Distributed operation (%s) not supported. Operation not yet supported.
CAUSE: Not implemented yet.
ACTION: none
PARAMS: %1s – the operation type

ERROR: [DM_FOREIGN_E_DESTROY_REPLICA]

SEVERITY: ERROR
DESCRIPTION: SS Cannot destroy the replica object (%s) because %s.
CAUSE: See reason.
ACTION:
PARAMS: %s – replica object id %s – reason

ERROR: [DM_FOREIGN_E_CHECKPOINT_ERROR]

SEVERITY: ERROR
DESCRIPTION: An error occurred attempting to commit the work completed so far during a set of reference objects operation. Either the outstanding transaction could not be committed or a new transaction could not be started. During a purge replica mirror or dangling reference objects cleanup operation, the work performed is committed periodically to reduce the database resources and to allow the operation to be continued from where it left off should a failure occur half-way through. This error is given when a that commit action fails. The failure may be caused by an error in the commit or the inability to start a new transaction following the commit.
CAUSE: Possibly the underlying database system ran out of some resource.
ACTION: Review the error log for other errors.
PARAMS:

ERROR: [DM_FOREIGN_E_DMREF_LOOKUP]

SEVERITY: ERROR
DESCRIPTION: D Error fetching dm_reference object for (%s). An error was encountered while looking up or fetching the dm_reference entry for a reference or replica object. Each reference or replica object in a docbase has a corresponding entry in dm_reference. The dm_reference record points back to the local object by its r_mirror_object_id attribute. The error could have occurred while querying for a dm_reference object with the an r_mirror_object_id value matching the specified object id, or while fetching the qualifying dm_reference. Other errors in the error stream should indicate which one and give more information on the specific error. Note that the non-existence of a qualifying dm_reference object will NOT be treated as an error.
CAUSE: The error could have been caused by a query error with the server or by an object fetching error.
ACTION: Check for previous errors giving more specific information.
PARAMS: %1s – The object id of the local object.

ERROR: [DM_FOREIGN_E_UPDATE_NULL_REF]

SEVERITY: ERROR
DESCRIPTION: SS Unable to update reference/replica (%s) to show that the object it points to does not exist. Could not update i_null_ref_flag in object %s. The attempt to update a reference object to show that the object it points to does not exist anymore failed for some reason. Previous error messages should give more detail on why the failure occurred. The local reference object will remain usable, but will not reflect the null-reference property.
CAUSE: Transaction or object update error. Other error messages should have been logged giving a more precise reason for the failure.
ACTION: Check other error messages which should give a more detailed explanation of the error. Also check the server session logs for errors.
PARAMS: %1s – object id of reference/replica object %2s – object id of the dm_reference catalog object

ERROR: [DM_FOREIGN_E_OBJECT_COPY]

SEVERITY: ERROR
DESCRIPTION: DS Error creating copy of object %s in order to save to local server in a refresh operation. The remote object type is %s. Check that the type definitions in the local and remote docbases are consistent. The replica refresh operation must take each modified/new object and copy it from the domain of the source server to the local domain. This involves converting it to the local type (typically just copying the attributes over). This error is triggered by a failure in this copy.
CAUSE: The failure may be due to a remote type being unknown in the local system or having a different incompatible type definition.
ACTION: Check the consistencies of the named type in the two docbases.
PARAMS: %s – The replica object on which the error was encountered. %s – The type name of the source object.

ERROR: [DM_FOREIGN_E_DUMPMAP_ALLOC]

SEVERITY: ERROR
DESCRIPTION: SL The %s could not allocate a new entry for the refresh map. Current map size is %ld. The replica refresh operation involves building a relationship map of all the objects related to the one being refreshed. During the building of this map we were unable to allocate a new map entry. This likely represents a memory exhaustion.
CAUSE: Likely running out of memory.
ACTION: Check memory/swap limits.
PARAMS: %s – Indicator for DMCL or Server. %s – The number of entries in the map before the error occurred.

ERROR: [DM_FOREIGN_E_SERVER_VERSION]

SEVERITY: ERROR
DESCRIPTION: SSS Distributed Features are not accessible on docbase %s because it is of an incompatible version (server version %s). Docbases must be at least version %s to participate in distributed operations. An attempt to create a distributed relationship or to move data between docbases was attempted, but could not be satisfied because one of the docbases was not running at the correct server version. The action cannot be performed unless the docbase is upgraded to the specified version.
CAUSE: The docbase does not support the requested operation.
ACTION: The action cannot be performed unless the docbase is upgraded to the specified version.
PARAMS: %1s – the incompatible docbases name. %2s – the server version of the above docbase. %3s – the required version for distributed features.

ERROR: [DM_FOREIGN_E_REFERENCE_TYPE]

SEVERITY: ERROR
DESCRIPTION: S Cannot create a reference to an object of type %s. The request to create a new reference was rejected because the referenced object was of a type that cannot be referenced.
CAUSE: The referenced type is not supported in a create reference operation.
ACTION: Modify reference request.
PARAMS: %1s – the type of the referenced object.

ERROR: [DM_FOREIGN_E_MAP_CANT_CHANGE]

SEVERITY: ERROR
DESCRIPTION: Cannot change r_docbase_id or r_id_offset fields of an existing dm_docbaseid_map.
CAUSE: The user does not have privilege to update the specified type. The docbase_id and r_id_offset fields should never be changed in an existing map object as doing so will leaving existing objects orphaned.
ACTION: Verify the intended operation. Changing docbaseid_map objects incorrectly will leave the docbase corrupted. If needed, the object can be changed by dropping it and creating a new one with the intended data.
PARAMS:

ERROR: [DM_FOREIGN_E_NOMAP]

SEVERITY: ERROR
DESCRIPTION: DSD No mapping found for object id %s in %s object %s. A replication operation that relies on finding a local mapping for a remote object failed. No local object could be found which maps to the given object id. During replication, remote objects have their id fields remapped to local values. When no local mapping is found, then generally the fields are left as-is. However, some operations are sensitive to finding a valid mapping. For example content transfer relies on having a local storage area and format object in order to store content locally.
CAUSE: Could not find local mapping for id.
ACTION: Check for existence of replica for given object. Try running batch-mode replication to bring over appropriate related objects.
PARAMS: %s – The object id which could not be mapped. %s – The type name of the object which had the id pointer. %s – The object id of the object which had the id pointer.

ERROR: [DM_FOREIGN_E_SOURCE_NOTFOUND]

SEVERITY: ERROR
DESCRIPTION: SSSS The requested source object was not found. No object matching the %s (%s) with version label (%s) was found in docbase %s. The creation of a reference object failed because the requested object could not be found in the referenced docbase.
CAUSE: The requested object was not found.
ACTION: Check to make sure the remote docbase is available and accessible. Verify the object name specified and make sure that the full path to the object is included (eg. /Cabinet/folder/subfolder/object_name).
PARAMS: %1s – indicates by name or id search %2s – the requested object name and path %3s – the version label requested %4s – the referenced docbase name

ERROR: [DM_FOREIGN_E_TYPE_INCOMPATIBLE]

SEVERITY: ERROR
DESCRIPTION: SS The reference cannot be created because the %s type from docbase %s is not compatible with the local docbase. The creation of a reference object failed because the requested object was of a type that could not be imported into the local docbase.
CAUSE: The requested objects type was incompatible with the local docbase.
ACTION: The object cannot be referenced unless the base types are made to be compatible.
PARAMS: %1s – the requested objects type %2s – the referenced docbase

ERROR: [DM_FOREIGN_E_DMREF_ALLOC]

SEVERITY: ERROR
DESCRIPTION: Error creating new dm_reference object. The creation of a reference object failed because of an error creating a new dm_reference object.
CAUSE: The server could not allocate a new dm_reference object
ACTION: Check for previous errors which should give more detail on the cause of the problem. Check for resource usage (memory).
PARAMS: none

ERROR: [DM_FOREIGN_E_NEW_SYSOBJECT]

SEVERITY: ERROR
DESCRIPTION: S Error creating a new object of type %s during the creation of a reference link. The creation of a reference object failed because of an error creating a new object to hold the copy of the referenced objects meta-data.
CAUSE: The server could not create an object of the requested type.
ACTION: Check for previous errors which should give more detail on the cause of the problem.
PARAMS: %1s – the local objects type

ERROR: [DM_FOREIGN_E_NO_DOCBASE_NAME]

SEVERITY: ERROR
DESCRIPTION: The reference cannot be created because no docbase name was specified. The reference_docbase_name attribute must be set. The save request of a dm_reference object failed because the required attribute – reference_docbase_name – was not specified.
CAUSE: The required attribute – reference_docbase_name – was not specified.
ACTION: Set the required field and resave the object.
PARAMS: None

ERROR: [DM_FOREIGN_E_OBJECT_IDMAP]

SEVERITY: ERROR
DESCRIPTION: Error in Distributed Id Mapping during object replication action. An error occurred during replica refresh as the replica object was being built from a copy of the source object. The error occurred during the actions to remap source id ptrs in the object to the appriopriate local object id values.
CAUSE: Failure to build new version of replica object.
ACTION: Check for previous error messages which give more detail on problem.
PARAMS: None

ERROR: [DM_FOREIGN_W_UPDATE_NOREFRESH]

SEVERITY: WARNING
DESCRIPTION: SSD An update to a %s object was performed successfully, but the local information could not be properly refreshed to reflect the new object state. Local %s object %s is likely not up-to-date. The save of a replica or reference object succeeded. But the local info could not be refreshed to reflect the new changes. The local replica/reference was left out-of-date by the update operation. This could lead to confusion by the user (the object may still appear locked following a checkin) and later errors if further updates are attempted on the object (updates are not allowed using an out-of-date replica). The user should attempt a manual refresh of the object (refresh api) to bring it up-to-date.
CAUSE: Object could not be refreshed following update.
ACTION: Check for previous error message which may give more detail on the problem. Re-try the refresh by using the refresh operation. If that still fails try enabling tracing during the refresh call.
PARAMS: %s – replica/reference indicator %s – The object id of the local object. %s – replica/reference indicator

ERROR: [DM_FOREIGN_W_MULTI_SOURCE]

SEVERITY: WARNING
DESCRIPTION: DD Not Yet Supported: Refresh operation encountered a replica object (%s) from a docbase different than the original object being refreshed (%s). This multi-docbase replica relationship must be refreshed via the Replication Job. The refresh operation also refreshes related objects. The operation does not currently support refreshing related objects that are mastered in another docbase.
CAUSE: Multi-source replica relationship not yet supported.
ACTION: Try running batch-mode replication to bring over appropriate related objects.
PARAMS: %s – The object id which fell outside the base source. %s – The source replica id.

ERROR: [DM_FOREIGN_W_MAPINCOMPLETE]

SEVERITY: WARNING
DESCRIPTION: D Object could not be refreshed due to a problem computing the set of related objects needed in the refresh action. The state of object %s was unexpectedly unknown. The replica refresh operation must compute the set of all related objects and determine the state of those objects at the source and local sites. This error is given when the algorithm fails somehow leaving an object state unknown.
CAUSE: A bug in the refresh map algorithm.
ACTION: If the object being refreshed has child objects (annotations or VDM children) try refreshing the sub-objects first. Otherwise the object may have to be refreshed by the batch replica refresh job.
PARAMS: %s – The object on which the error was encountered.

ERROR: [DM_FOREIGN_W_SOURCE_REFRESH]

SEVERITY: WARNING
DESCRIPTION: D After a successful refresh of a replica or reference object, could not update the source object (%s) to show the refresh completion. This may cause the source to later needlessly re-execute the refresh. After a refresh, the save of the information on the source to show that the refresh occurred did not work.
CAUSE: The source object could not be updated.
ACTION: No action necessary.
PARAMS: %1s – the source object

ERROR: [DM_FOREIGN_W_LOAD_NO_IDMAP]

SEVERITY: WARNING
DESCRIPTION: Cannot lookup object_id mapping for foreign object because the server has not initialized its object_id map cache. During a non-relocate load operation a foreign object was found but could not be loaded due to there being no docbaseid map cache in the server.
CAUSE: The server has apparently not initialized its docbaseid map cache.
ACTION: Check for other errors in the error log. Report this message and any others to your Documentum site representative.
PARAMS:

ERROR: [DM_FOREIGN_W_TOO_MANY_MAPS]

SEVERITY: WARNING
DESCRIPTION: LL Cannot add new replica objects from docbase id %d because the limit has already been reached of %d docbases participating in a replicated enterprise. During a load operation an object from a foreign docbase was encountered that had not previously had objects replicated to this docbase. The object could not be loaded because the hard limit of the maximum number of different docbases from which data can be replicated had already been reached.
CAUSE: The docbase has exceeded the limit on the number of docbases that can participate in a replicated environment.
ACTION: Check docbase replication setup and docbase objects to see what docbases have had data replicated here. Look for extraneous data which may be removed.
PARAMS: %d – docbase id from which objects are being imported %d – limit of number of docbases in a distributed setup

ERROR: [DM_FOREIGN_T_FOLDERMERGE_CHECK]

SEVERITY: TRACE
DESCRIPTION: S Checking Folder %s as part of distributed operation. Trace message during distributed replication or refresh operation. Tracing the checking to determine if the specified folder should be included in a replicated object.
CAUSE:
ACTION:
PARAMS: %s – The folder name Basic object warning codes.

nahoru

DM_FORMAT

ERROR: [DM_FORMAT_F_TYPE_CONVERSION]

SEVERITY: FATAL
DESCRIPTION: I Failed to convert type dm_format to version %d.
CAUSE: Type conversion failed.
ACTION: Report this message and any parameters to your Documentum site representative. Fulltext Index Management Facility errors
PARAMS:

ERROR: [DM_FORMAT_E_INCR_LENGTH_FAILED]

SEVERITY: ERROR
DESCRIPTION: SL The attribute %s increase length failed for version %d. The database could not widen the attribute
CAUSE: The database server may have problems widening the column length
ACTION: Check database server log or use sql script(under dba) to upgrade.
PARAMS:

ERROR: [DM_FORMAT_E_INCR_LENGTH_NONEXISTANT_ATTR]

SEVERITY: ERROR
DESCRIPTION: SL The attribute %s increase length failed for version %d because the attribute did not exist
CAUSE: Attributes for which the length is being increased should already be in existence before they are lengthened. A previous upgrade step may have failed.
ACTION: Contact your Documentum Site Representative.
PARAMS:

ERROR: [DM_FORMAT_E_BAD_TOPIC_FORMAT]

SEVERITY: ERROR
DESCRIPTION: S Topic format %s either doesnt exist or is not indexable
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FORMAT_E_INCR_LENGTH_TOO_LONG]

SEVERITY: ERROR
DESCRIPTION: SL The attribute %s increase length failed for version %d because the attribute was too long
CAUSE: The IncreaseLength function was called on an attribute which was too long. A previous upgrade step may have failed.
ACTION: Contact your Documentum Site Representative.
PARAMS:

ERROR: [DM_FORMAT_E_NO_NAME]

SEVERITY: ERROR
DESCRIPTION: Failed to save format object — no name was supplied
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FORMAT_E_CANT_UPDATE_FTINDICES]

SEVERITY: ERROR
DESCRIPTION: Failed to save format objects — could not update
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FORMAT_E_FORMAT_IN_USE]

SEVERITY: ERROR
DESCRIPTION: SI Cant expunge format %s — %i content objects exist with this format
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FORMAT_E_NOT_SYSADMIN]

SEVERITY: ERROR
DESCRIPTION: S Cant perform %s operation — user does not have sysadmin privileges
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FORMAT_E_DUPLICATE_NAME]

SEVERITY: ERROR
DESCRIPTION: S Failed to save format object — format with name %s already exists
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FORMAT_E_BAD_ATTR_SPEC]

SEVERITY: ERROR
DESCRIPTION: S Format string has illegal specification for attribute %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FORMAT_E_ILLEGAL_NAME]

SEVERITY: ERROR
DESCRIPTION: S The format name %s is invalid
CAUSE: The format name must be all alphanumeric
ACTION: Try to save the format with a different name
PARAMS:

ERROR: [DM_FORMAT_E_NOT_ATTR]

SEVERITY: ERROR
DESCRIPTION: S Format string has specification for non-existent attribute %s
CAUSE:
ACTION:
PARAMS:

nahoru

DM_FT_INDEX

ERROR: [DM_FT_INDEX_F_UPDATE_R_IS_PUBLIC_FAILED]

SEVERITY: FATAL
DESCRIPTION: S Fulltext index sysobject upgrade failed on the type %s when updating r_is_public field.
CAUSE: Probable RDBMS failure.
ACTION: Examine system logs and try again.
PARAMS:

ERROR: [DM_FT_INDEX_F_UPGRADE_400_TYPE_DESTROY_FAILED]

SEVERITY: FATAL
DESCRIPTION: S The %s type could not be destroyed during upgrade.
CAUSE: Internal failure.
ACTION: Initially, disregard this error. It may cause no problem. If other problems show up, report this as well the others to your Documentum Site Representative.
PARAMS:

ERROR: [DM_FT_INDEX_F_UPGRADE_SYSOBJECT_400_PART2_FAILED]

SEVERITY: FATAL
DESCRIPTION: Part 2 of fulltext index sysobject upgrade failed
CAUSE: Probable RDBMS failure.
ACTION: Examine system logs and try again.
PARAMS:

ERROR: [DM_FT_INDEX_F_UPGRADE53_REMOVE_INDEX_OBJECT_FAILED]

SEVERITY: FATAL
DESCRIPTION: S Unable to expunge dm_fulltext_index object with id %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_F_UPGRADE_SYSOBJECT_400_PART1_FAILED]

SEVERITY: FATAL
DESCRIPTION: S Fulltext index sysobject upgrade failed on the type %s.
CAUSE: Probable RDBMS failure.
ACTION: Examine system logs and try again.
PARAMS:

ERROR: [DM_FT_INDEX_F_UPGRADE53_UNABLE_TO_GET_TEMP_CONNECTION]

SEVERITY: FATAL
DESCRIPTION: Unable to get temporary connection to the database to perform upgrade operations
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_F_UPGRADE53_UNABLE_TO_DROP_OBSOLETE_ATTRIBUTE]

SEVERITY: FATAL
DESCRIPTION: S Unable to drop attribute %s from dm_fulltext_index type
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_F_UPGRADE53_UNABLE_TO_ADD_ATTRIBUTE]

SEVERITY: FATAL
DESCRIPTION: S Unable to add attribute %s to the dm_fulltext_index type
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_F_UPGRADE53_BEGIN_TRANS_FAILED]

SEVERITY: FATAL
DESCRIPTION: Unable to begin transaction for upgrading fulltext types
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_F_UPGRADE53_COMMIT_TRANS_FAILED]

SEVERITY: FATAL
DESCRIPTION: Unable to commit the operations for fulltext upgrade
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_F_FULLTEXT_ENGINE_INIT_ERROR]

SEVERITY: FATAL
DESCRIPTION: S Query Plugin failed to successfully initialize: %s
CAUSE: The query plugin could not initialize its communication with the Index Server.
ACTION: The argument of the error message will indicate exact nature of the problem e.g. Index Server not reachable, mis-configured dm_ftengine_config object values etc. FullText Facility errors ** Documentum DocuServer ** Confidential Property of Documentum, Inc. ** (c) Copyright Documentum, Inc., 1993 ** All rights reserved. **
PARAMS:

ERROR: [DM_FT_INDEX_E_SAMPLE_OBJ_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: S The sample object %s was not found in the docbase.
CAUSE: Sample object missing or bad.
ACTION: Choose a sample object that is marked for full-text and currently indexed and has a unique name.
PARAMS:

ERROR: [DM_FT_INDEX_E_NOT_SYS_ADMIN]

SEVERITY: ERROR
DESCRIPTION: S Cant perform operation %s on fulltext indices — not sys admin
CAUSE: The operation could not be performed because the user had insufficient privileges
ACTION: None.
PARAMS: The operation name

ERROR: [DM_FT_INDEX_E_NO_FULLTEXT_PLUGIN_LOADED]

SEVERITY: ERROR
DESCRIPTION: S The fulltext query plugin did not initialize with the fulltext search engine %s specified in the server config object. Please ensure that the search engine is functioning and is configured correctly.
CAUSE: This error occurs if the fulltext_location attribute in the server config does not refer to a valid fulltext search engine or if the search engine is incorrectly configured or not functioning.
ACTION: Set fulltext_location attribute of the server config object to a valid fulltext install location. Verify that valid fulltext installations are listed in the fulltext_install_locs attribute of the docbase config object. Verify that the fulltext search engine is functioning and correctly configured.
PARAMS:

ERROR: [DM_FT_INDEX_E_VERITY_LOC_CHANGED]

SEVERITY: ERROR
DESCRIPTION: SSS Not able to %s the fulltext index. The verity_location value of the server config (%s) does not match the install location of the fulltext library currently loaded (%s) in the server.
CAUSE: Performing this fulltext operation is not allowed when the install location of the currently loaded fulltext library does not match the verity_location of the server config.
ACTION: Restart the Content Server to load the fulltext library defined by the verity_location of the server config.
PARAMS: The index operation, the verity_location value, and the install location of the currently loaded fulltext implementation.

ERROR: [DM_FT_INDEX_E_CANNOT_USE_MAX_DOCS]

SEVERITY: ERROR
DESCRIPTION: Cannot run update_ftindex with date_cutoff and max_docs both specified.
CAUSE: Tried to run update_ftindex with date_cutoff and max_docs both specified.
ACTION: Retry update_ftindex with only one out of the two specified.
PARAMS:

ERROR: [DM_FT_INDEX_E_NOT_STANDBY]

SEVERITY: ERROR
DESCRIPTION: SS Operation %s requires a standby index. Index %s is not standby
CAUSE: Index named must be a standby index.
ACTION: Use a different index.
PARAMS: The name of the operation and the name of the index.

ERROR: [DM_FT_INDEX_E_BAD_LOCALE_SPECIFIED]

SEVERITY: ERROR
DESCRIPTION: SS The %s locale specified was not found in the fulltext configuration pointed by the %s fulltext install location. Please specify a valid locale. (Valid locales are identified in the dmfulltext.ini file, located $DOCUMENTUM/verity/ directory.
CAUSE: The locale specified is not supported by the fulltext configuration used by the index you are creating.
ACTION: Specify a locale recognized by this fulltext configuration.
PARAMS: The specified locale and fulltext install location

ERROR: [DM_FT_INDEX_E_CANT_UPDATE_SHADOW]

SEVERITY: ERROR
DESCRIPTION: S Cannot perform index update on shadow index %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_E_COLLECTION_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: Couldnt find the collection for the sample object specified.
CAUSE: Possible internal error, or bad sample object.
ACTION: Check that this object is of an indexable type and format.
PARAMS:

ERROR: [DM_FT_INDEX_E_STYLE_BACKUP_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: S Couldnt find the backup for the %s.
CAUSE: Probable operating system error or filesystem or disk problem.
ACTION: Check for OS error messages.
PARAMS:

ERROR: [DM_FT_INDEX_E_INDEX_CLOSED]

SEVERITY: ERROR
DESCRIPTION: S Cant rollover index %s — its already closed
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_E_CANT_COMMIT_TRANSACTION]

SEVERITY: ERROR
DESCRIPTION: SS Could not commit transaction for %s operation on fulltext index %s
CAUSE: The operation required a transaction which could not be committed
ACTION: None.
PARAMS: The operation name and the name of the fulltext index

ERROR: [DM_FT_INDEX_E_NO_FULLTEXT_CONFIG_FOUND]

SEVERITY: ERROR
DESCRIPTION: S A fulltext configuration was not found for the specified %s install location. Please specify a valid fulltext install location. (Valid install locations are defined in the fulltext_install_locs attribute of the docbase config object.)
CAUSE: An invalid install location not recognized by this server was specified, or the install loc refers to a location that wasnt successfully loaded by the server.
ACTION: Specify a valid install location on the next attempt
PARAMS: The specified fulltext install location.

ERROR: [DM_FT_INDEX_E_INVALID_OPTIMIZATION_FLAG]

SEVERITY: ERROR
DESCRIPTION: S The %s optimization flag is not valid.
CAUSE: The CLEAN_FTINDEX method aborted because an invalid flag was specified in the FLAGS argument.
ACTION: Make sure all optimization flags specified are valid and rerun the CLEAN_FTINDEX method. Multiple flags should be separated by hyphens.
PARAMS: The invalid optimization flag

ERROR: [DM_FT_INDEX_E_CANT_MAKE]

SEVERITY: ERROR
DESCRIPTION: SS Cant make index with name %s for storage of type %s
CAUSE: Fulltext indices cannot be created for the storage object
ACTION: None.
PARAMS: The name of the fulltext index and the name of the storage type

ERROR: [DM_FT_INDEX_E_BAD_INDEX_TYPE_SPECIFIED]

SEVERITY: ERROR
DESCRIPTION: II The specified index_type %d does not match the index_type of the fulltext configuration used by this index. Set the index_type to %d to match the fulltext configuration used.
CAUSE: The index_type specified does not match the index_type found in the fulltext configuration.
ACTION: Either do not explicitly specify an index_type or specify an index_type that matches the fulltext configuration used.
PARAMS: The specified index_type and the index_type of the fulltext configuration.

ERROR: [DM_FT_INDEX_E_UNABLE_TO_GENERATE_LOGIN_TICKET]

SEVERITY: ERROR
DESCRIPTION: S Unable to generate a login ticket to start Index Agent %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_E_NO_FULLTEXT_CONFIG_FOR_INDEX]

SEVERITY: ERROR
DESCRIPTION: SS Not able to %s the fulltext index. There is no fulltext configuration loaded for this fulltext indexs %s install_loc.
CAUSE: Performing this fulltext operation is not allowed when no fulltext configuration has been loaded corresponding to the install_loc of the fulltext index.
ACTION: Check the docbase config object to see if the fulltext_install_locs attribute contains the install_loc of the fulltext index. If so, reinit the server. If not, please add the install_loc into the docbase config and reinit the server.
PARAMS: The index operation, the install location of the fulltext index

ERROR: [DM_FT_INDEX_E_NO_FULLTEXT_IMPLEMENTATION_LOADED2]

SEVERITY: ERROR
DESCRIPTION: A fulltext library was not identified in the server config object. Please identify a valid fulltext installation in the fulltext_location attribute of the server config object.
CAUSE: This error occurs if the fulltext_location attribute in the server config is not set.
ACTION: Set fulltext_location attribute of the server config object to a valid fulltext install location. Valid fulltext installations are listed in the fulltext_install_locs attribute of the docbase config object.
PARAMS:

ERROR: [DM_FT_INDEX_E_NO_FULLTEXT_IMPLEMENTATION_LOADED]

SEVERITY: ERROR
DESCRIPTION: S Could not %s the fulltext index because a fulltext library is not loaded. A library was not loaded because verity_location in the server config object is not set or the fulltext plugin failed to load.
CAUSE: Content Server could not load the fulltext library because the verity_location attribute in the server config object is not set to a fulltext install location or the fulltext plugin failed to load.
ACTION: Set verity_location to a valid fulltext install location and reinit or restart the Content Server.
PARAMS: The fulltext index operation

ERROR: [DM_FT_INDEX_E_ILLEGAL_TIME_OUT]

SEVERITY: ERROR
DESCRIPTION: I The specified time-out interval (%d) does not make sense.
CAUSE: A time-out interval must be positive.
ACTION: Choose a positive value and retry the command.
PARAMS:

ERROR: [DM_FT_INDEX_E_INSTALL_LOC_NOT_VERITY_LOC]

SEVERITY: ERROR
DESCRIPTION: SS The %s fulltext install location specified does not match the verity_location of the server config: %s for a non-standby index. Non-standby indexes must use the verity_location of the server config.
CAUSE: A non-standby index must use the location defined in the verity_location of the server config. Any other value specified is not valid.
ACTION: Specify the value in the verity_location of the server config for non-standby indexes, or do not specify a value.
PARAMS: The specified install loc and the verity_location of the server config

ERROR: [DM_FT_INDEX_E_FAR_STORE]

SEVERITY: ERROR
DESCRIPTION: S Attempt to update fulltext index for far storage %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_E_QUERY_EXECUTION_FAILURE]

SEVERITY: ERROR
DESCRIPTION: SS An error occured while trying to execute the following query: %s. Database error was %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_FT_INDEX_E_DUPLICATE_NAME]

SEVERITY: ERROR
DESCRIPTION: SS Attempt to create new fulltext index failed — index %s already has name %s
CAUSE: Attempting to create a new fulltext index with a name that is being used by another fulltext index
ACTION: Choose a new name and retry the operation
PARAMS: The id of the existing fulltext index and the name

ERROR: [DM_FT_INDEX_E_STYLE_FILE_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: S The internal copy of the %s was not found
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_E_CANT_COPY_FILE]

SEVERITY: ERROR
DESCRIPTION: SS Couldnt copy the %s at server path %s.
CAUSE: Probable operating system error or filesystem or disk problem.
ACTION: Check for OS error messages.
PARAMS:

ERROR: [DM_FT_INDEX_E_CANT_MODIFY_TDK_INDEX]

SEVERITY: ERROR
DESCRIPTION: There was a failure trying to modify a fulltext index object.
CAUSE: Internal error.
ACTION: Report this error to your Documentum Site Representative.
PARAMS:

ERROR: [DM_FT_INDEX_E_USER_STYLE_FILE_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: SS The users %s was not found at server path %s
CAUSE: The path does not point to a file.
ACTION: Check the file name and try again.
PARAMS:

ERROR: [DM_FT_INDEX_E_SAMPLE_OBJ_BAD_ID]

SEVERITY: ERROR
DESCRIPTION: S The sample object %s has a bad id.
CAUSE: Sample object missing or bad.
ACTION: Choose a sample object that is marked for full-text and currently indexed and has a unique name.
PARAMS:

ERROR: [DM_FT_INDEX_E_INDEX_NAME_TOO_LONG]

SEVERITY: ERROR
DESCRIPTION: SI Cant create index with name %s (%d chars is max).
CAUSE: Tried to create an index with a name too long.
ACTION: Retry with a shorter name.
PARAMS: The name that was too long and the maximum size.

ERROR: [DM_FT_INDEX_E_INVALID_FULLTEXT_ENGINE_ID]

SEVERITY: ERROR
DESCRIPTION: D %s is not a valid dm_ftengine_config object id
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_E_CANT_UPDATE_ATTRIBUTE]

SEVERITY: ERROR
DESCRIPTION: SS Attribute %s cannot be changed for dm_fulltext_index object %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_E_NO_STORAGE]

SEVERITY: ERROR
DESCRIPTION: SS Cannot perform operation %s — No storage is defined for fulltext index %s.
CAUSE: No storage is defined for this fulltext index object.
ACTION: Make sure that this fulltext index is associated with a storage area.
PARAMS: The name of the operation and the name of the index.

ERROR: [DM_FT_INDEX_E_INTERNAL_DATABASE_ERROR]

SEVERITY: ERROR
DESCRIPTION: SS A database error occured during the following operation: %s. Database error was %s.
CAUSE: Internal database error
ACTION: Check the error message from the database in order to determine the cause of the query failure.
PARAMS: The first parameter identifies the internal operation performed. The second parameter is the resulting error from the database.

ERROR: [DM_FT_INDEX_E_NO_LOCALE_SPECIFIED]

SEVERITY: ERROR
DESCRIPTION: Could not create the fulltext index because a locale was not specified. A locale must be specified.
CAUSE: Content Server requires you to identify the locale of a fulltext index when you create the index.
ACTION: Specify a valid locale on the next attempt to create the index. Valid locales are identified in the dmfulltext.ini file, located in $DOCUMENTUM/verity/ directory.
PARAMS:

ERROR: [DM_FT_INDEX_E_NO_NAME]

SEVERITY: ERROR
DESCRIPTION: Attempt to create new fulltext index without supplying a name
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_E_NO_LOCATION]

SEVERITY: ERROR
DESCRIPTION: SS Attempt to create new fulltext index with name %s failed — no location with name %s exists
CAUSE: Attempting to create a fulltext index for a storage object that doesnt exist
ACTION: Correct the problem and retry the operation
PARAMS: The name of the index and the name of the location object

ERROR: [DM_FT_INDEX_E_CANT_CREATE_FTINDEX_OBJECT_IN_NONSTANDBY_MODE]

SEVERITY: ERROR
DESCRIPTION: S Cannot create %s dm_fulltext_object with is_standby set to FALSE, because dm_fulltext_index object with is_standby set to FALSE already exists.
CAUSE: This error occurs when you attempt to create a dm_fulltext_index object with is_standby set to FALSE, when a dm_fulltext_index object with is_standby set to FALSE already exists in the docbase.
ACTION: You cannot have more than one dm_fulltext_index object in a docbase with is_standby set to FALSE. You can create any number of dm_fulltext_index object with is_standby set to TRUE.
PARAMS:

ERROR: [DM_FT_INDEX_E_SERVER_PATH_NOT_DIRECTORY]

SEVERITY: ERROR
DESCRIPTION: S The specified server_path (%s) is not a directory.
CAUSE: For topic trees, the server_path must be a directory, as created by the Verity mk_topic utility.
ACTION: Create such a directory and retry the command specifying it.
PARAMS:

ERROR: [DM_FT_INDEX_E_INVALID_DATE_CUTOFF]

SEVERITY: ERROR
DESCRIPTION: The specified cutoff date format is not valid or is later than the current time.
CAUSE: Tried to run update_ftindex with an invalid date format or date later than the current time.
ACTION: Retry update_ftindex with a valid date and format.
PARAMS:

ERROR: [DM_FT_INDEX_E_NO_INDEX_SPECIFIED]

SEVERITY: ERROR
DESCRIPTION: S Cannot perform operation %s — No index specified to search.
CAUSE: No index was specified to search.
ACTION: Rerun the operation with at least one valid index specified.
PARAMS: The name of the operation.

ERROR: [DM_FT_INDEX_E_STYLE_TYPE_NOT_ALLOWED]

SEVERITY: ERROR
DESCRIPTION: S The %s is not allowed
CAUSE: The style type specified was not one of the permitted ones.
ACTION: Check the Documentum manual for the list of styles, and retry the command.
PARAMS:

ERROR: [DM_FT_INDEX_E_UPGRADE_400_TCOLL_DESTROY_FAILED]

SEVERITY: ERROR
DESCRIPTION: S The dmi_topic_collection at %s could not be destroyed.
CAUSE: Permission problem or disk problem.
ACTION: Look for the directory listed in the error message and delete it by other means.
PARAMS:

ERROR: [DM_FT_INDEX_E_BAD_CONFIG]

SEVERITY: ERROR
DESCRIPTION: S Attempt to update fulltext index object failed — invalid server config name %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_E_NO_FILE]

SEVERITY: ERROR
DESCRIPTION: S No file was specified for %s operation
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_E_RESULTS_NOT_FILTERED]

SEVERITY: ERROR
DESCRIPTION: SS Cannot perform operation %s — The matching results were not filtered to the specified type on fulltext index %s.
CAUSE: Verity failed to return the OBJTYPE of each result matching the query.
ACTION: Verify that Verity is working properly by checking if your environment is properly set up for Verity.
PARAMS: The name of the operation and the name of the index.

ERROR: [DM_FT_INDEX_E_CANT_RENAME_FILE]

SEVERITY: ERROR
DESCRIPTION: S Unable to rename the %s.
CAUSE: Probable operating system error or filesystem or disk problem.
ACTION: Check for OS error messages.
PARAMS:

ERROR: [DM_FT_INDEX_E_CANT_DESTROY_FILE]

SEVERITY: ERROR
DESCRIPTION: S Unable to destroy the %s.
CAUSE: Probable operating system error or filesystem or disk problem.
ACTION: Check for OS error messages.
PARAMS:

ERROR: [DM_FT_INDEX_E_FULLTEXT_CONFIG_NOT_LOADED]

SEVERITY: ERROR
DESCRIPTION: S A fulltext configuration was not found in the file_system_path defined by the fulltext install location %s object. Please check that the location object exists, that its file system_path points to a valid fulltext installation, and that the fulltext installation contains a valid dmfulltext.ini file.
CAUSE: Loading the fulltext configuration failed and returned a bad state.
ACTION: Make sure the dmfulltext.ini file is valid and that the fulltext install location is correctly defined. Information about the dmfulltext.ini files and the location objects is found in the Content Server Administrators Guide.
PARAMS: The fulltext install location

ERROR: [DM_FT_INDEX_E_CANT_MODIFY]

SEVERITY: ERROR
DESCRIPTION: S Cannot modify existing fulltext index %s
CAUSE: Fulltext indices cannot be modified once created
ACTION: None.
PARAMS: The name of the fulltext index

ERROR: [DM_FT_INDEX_E_BAD_FULLTEXT_INSTALL_LOCATION]

SEVERITY: ERROR
DESCRIPTION: S The %s fulltext install location is not valid or not found in the fulltext install locations identified in the docbase config object.
CAUSE: An invalid fulltext location was specified.
ACTION: Set the fulltext location object to point to one of the fulltext install locations defined in the docbase config object.
PARAMS: The specified fulltext install location

ERROR: [DM_FT_INDEX_E_NO_FTINDEX_PLUGIN]

SEVERITY: ERROR
DESCRIPTION: Cannot find fulltext index plugin library. PARAMETER: None.
CAUSE: The error message explains all.
ACTION: EXEC_XQUERY apply method cannot be executed without this.
PARAMS:

ERROR: [DM_FT_INDEX_E_CLOSE_FAILED]

SEVERITY: ERROR
DESCRIPTION: S Attempt to close fulltext index %s failed
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_E_CANT_BEGIN_TRANSACTION]

SEVERITY: ERROR
DESCRIPTION: SS Could not start transaction for %s operation on fulltext index %s
CAUSE: The operation required a transaction which could not be started
ACTION: None.
PARAMS: The operation name and the name of the fulltext index

ERROR: [DM_FT_INDEX_E_CANT_SAVE_TDK_INDEX]

SEVERITY: ERROR
DESCRIPTION: There was a failure trying to save a fulltext index object.
CAUSE: Internal error.
ACTION: Report this error to your Documentum Site Representative.
PARAMS:

ERROR: [DM_FT_INDEX_E_API_BAD_ARGS]

SEVERITY: ERROR
DESCRIPTION: SS The %s method failed because of bad arguments: %s
CAUSE: An apply or execute method failed because incorrect arguments were supplied.
ACTION: Check Documentum manuals for correct arguments and retry command.
PARAMS: %s – the api or execute method name %s – the incorrect argument supplied

ERROR: [DM_FT_INDEX_E_UNABLE_TO_FETCH_FTENGINE_CONFIG_TYPE]

SEVERITY: ERROR
DESCRIPTION: S Unable to fetch %s type
CAUSE: This error occurs when dm_ftengine_config type is not found in the docbase. This type is created when create_fulltext_objects.ebs script is executed by the Server Configuration program.
ACTION: Check if the type was created successfully during server configuration. If not, execute the script again to get the type created.
PARAMS:

ERROR: [DM_FT_INDEX_E_DUPLICATE_FOR_STORE]

SEVERITY: ERROR
DESCRIPTION: SS Attempt to create new fulltext index with name %s duplicates an existing index on the same store (storage name is %s)
CAUSE: Attempting to create a new fulltext index for a storage object that already has a fulltext index defined
ACTION: None.
PARAMS: The name of the index and the name of the storage object

ERROR: [DM_FT_INDEX_E_NO_STORE]

SEVERITY: ERROR
DESCRIPTION: SS Attempt to create new fulltext index with name %s failed — no store with name %s exists
CAUSE: Attempting to create a fulltext index for a storage object that doesnt exist
ACTION: Correct the problem and retry the operation
PARAMS: The name of the index and the name of the storage object

ERROR: [DM_FT_INDEX_E_NO_FTINDEX_AGENT_CONFIG_OBJECTS_FOUND]

SEVERITY: ERROR
DESCRIPTION: There were no dm_ftindex_agent_config object(s) found for the specified arguments
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_E_CANT_OPEN_NON_TDK_INDEX]

SEVERITY: ERROR
DESCRIPTION: SI The index, %s, you tried to open is with a wrong type %d.
CAUSE: A non-TDK fulltext index is detected while constructing a fulltext object.
ACTION: Make sure the i_implementation_type of the dm_fulltext_index object has a value 2 (i.e. TDK).
PARAMS:

ERROR: [DM_FT_INDEX_E_UNABLE_TO_GET_ATTR_POSITION]

SEVERITY: ERROR
DESCRIPTION: SS Unable to find %s attribute in type %s
CAUSE: could not find an attribute in the specified type.
ACTION: This is an internal error. Contact Technical Support.
PARAMS:

ERROR: [DM_FT_INDEX_E_ILLEGAL_ARG_VALUE]

SEVERITY: ERROR
DESCRIPTION: SI The %s argument was specified with an invalid value. Value was %d.
CAUSE: The argument value specified is not valid for this method.
ACTION: Rerun the method with a valid value.
PARAMS: The name of the argument and the value specified.

ERROR: [DM_FT_INDEX_E_METHOD_NOT_ENABLED]

SEVERITY: ERROR
DESCRIPTION: S Cannot perform operation %s — The method is not enabled for usage. Contact your superuser for information.
CAUSE: The method is not enabled because the superuser did not set the use_estimate_search parameter to T in the server.ini file.
ACTION: If the superuser decides to enable the method, rerun the operation.
PARAMS: The name of the operation.

ERROR: [DM_FT_INDEX_E_NO_FULLTEXT_INDEX]

SEVERITY: ERROR
DESCRIPTION: SS Cannot perform operation %s — fulltext index %s is not defined.
CAUSE: The fulltext index object is not defined or does not exist.
ACTION: Verify that the fulltext index does exist or create a new one to associate with the storage area.
PARAMS: The name of the operation and the name of the index.

ERROR: [DM_FT_INDEX_E_BAD_CODEPAGE_SPECIFIED]

SEVERITY: ERROR
DESCRIPTION: SSS The %s codepage specified is not valid for the %s locale. Please specify codepage %s for this locale.
CAUSE: The codepage specified is not valid for the locale.
ACTION: Specify a codepage that is compatible with the locale.
PARAMS: The specified codepage and locale

ERROR: [DM_FT_INDEX_E_INTERNAL_LOGIC_ERROR]

SEVERITY: ERROR
DESCRIPTION: S An internal error occured during the following operation: %s.
CAUSE: Internal error
ACTION: Contact Tech Support.
PARAMS: The internal operation being performed.

ERROR: [DM_FT_INDEX_E_SAMPLE_OBJ_NO_GOOD]

SEVERITY: ERROR
DESCRIPTION: S The sample object %s specified must be unique and indexed.
CAUSE: Sample object incorrectly specified
ACTION: Choose a sample object that is marked for full-text and currently indexed and has a unique name
PARAMS:

ERROR: [DM_FT_INDEX_E_UNABLE_TO_FETCH_FTINDEX_AGENT_CONFIG_TYPE]

SEVERITY: ERROR
DESCRIPTION: S Unable to fetch %s type
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_E_NO_INDEX]

SEVERITY: ERROR
DESCRIPTION: S Cant perform operation %s — fulltext index not found
CAUSE: The operation could not be performed because the fulltext index did not exist
ACTION: None.
PARAMS: The operation name

ERROR: [DM_FT_INDEX_E_API_ARG_MISSING]

SEVERITY: ERROR
DESCRIPTION: SS The %s method failed because of the argument %s was missing
CAUSE: An apply or execute method failed because a required argument was not supplied.
ACTION: Check Documentum manuals for correct arguments and retry command.
PARAMS: %s – the api or execute method name %s – the missing argument

ERROR: [DM_FT_INDEX_W_UPGRADE_400_TCOLL_NOT_FOUND]

SEVERITY: WARNING
DESCRIPTION: SS The dmi_topic_collection at %s for object %s was not found.
CAUSE: This may be a second invocation of this upgrade.
ACTION: None needed.
PARAMS:

ERROR: [DM_FT_INDEX_W_NO_FULLTEXT_LOCS_DEFINED]

SEVERITY: WARNING
DESCRIPTION: No fulltext install locations are defined in the fulltext_install_locs attribute of the docbase config. This is expected on the first startup of a upgraded or new docbase. If this warning occurs on subsequent startups, follow the instructions in ACTION.
CAUSE: The fulltext_install_locs attribute is empty when an upgraded or new Docbase is first started because the attribute is populated by the headstart.ebs script, which runs after the startup.
ACTION: Generally no action is required if headstart.ebs runs successfully. However, if headstart.ebs does not run successfully or the attribute remains unset, set it manually to verity271 and verity451.
PARAMS:

ERROR: [DM_FT_INDEX_W_VERITY_LOCATION_NOT_DEFINED]

SEVERITY: WARNING
DESCRIPTION: No fulltext install location was specified in the verity location. No fulltext library will be loaded when the Content Server is rebooted.
CAUSE: The verity location was set to a blank value.
ACTION: If it is the users intent to not load a fulltext implementation when the Content Server is rebooted, then nothing needs to be done. Otherwise, please specify a valid fulltext install location.
PARAMS:

ERROR: [DM_FT_INDEX_W_FULLTEXT_IMPLEMENTATION_NOT_LOADED_AIX]

SEVERITY: WARNING
DESCRIPTION: A fulltext library is not loaded. Changes made to load a new fulltext library cannot take effect until Content Server is restarted.
CAUSE: An attempt was made to load a new fulltext library without restarting Content Server. This error is AIX specific.
ACTION: Restart Content Server.
PARAMS:

ERROR: [DM_FT_INDEX_W_FULLTEXT_SERVER_METHOD_DEPRECATED]

SEVERITY: WARNING
DESCRIPTION: S The Fulltext subsystem related Server method %s has been deprecated.
CAUSE: The fulltext subsystem related Server method has been deprecated.
ACTION: The reported server method is not required for the fulltext subsystem architecture starting Content Server version 5.3.
PARAMS:

ERROR: [DM_FT_INDEX_W_FULLTEXT_LOCATION_NOT_DEFINED]

SEVERITY: WARNING
DESCRIPTION: No fulltext install location was specified in the fulltext location. No fulltext library will be loaded when the Content Server is rebooted.
CAUSE: The fulltext location was set to a blank value.
ACTION: If it is the users intent to not load a fulltext implementation when the Content Server is rebooted, then nothing needs to be done. Otherwise, please specify a valid fulltext install location.
PARAMS:

ERROR: [DM_FT_INDEX_W_NO_FULLTEXT_LOC_DEFINED]

SEVERITY: WARNING
DESCRIPTION: No fulltext install location is defined in the install_location attribute of the server config. This is expected on the first startup of an upgraded or new docbase. If this warning occurs on subsequent startups, please ensure that a location is defined correctly.
CAUSE: The install_location attribute is empty when an upgraded or new Docbase is first started because the attribute is populated by the headstart.ebs script, which runs after the startup.
ACTION: Generally no action is required if headstart.ebs runs successfully. After ensuring that headstart.ebs ran successfully, check the server config object to verify that the install_location attribute is populated with the object_name of a valid dm_location object.
PARAMS:

ERROR: [DM_FT_INDEX_W_STYLE_FILE_NOT_FOUND]

SEVERITY: WARNING
DESCRIPTION: S The %s was not found
CAUSE: The style file specified was not one of the permitted ones.
ACTION: Check the Documentum manual for the list of style files, and retry the command.
PARAMS:

ERROR: [DM_FT_INDEX_W_UPGRADE_400_TCOLL_TYPE_NOT_FOUND]

SEVERITY: WARNING
DESCRIPTION: The dmi_topic_collection type was not found during upgrade. Skipping.
CAUSE: This may be a second invocation of this upgrade.
ACTION: None needed.
PARAMS:

ERROR: [DM_FT_INDEX_W_DOCUMENTS_NOT_INDEXED]

SEVERITY: WARNING
DESCRIPTION: II %i documents were not indexed in this update — their update_count attributes were set to %i
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_W_NO_FULLTEXT_IMPLEMENTATION_LOADED]

SEVERITY: WARNING
DESCRIPTION: A fulltext library was not identified in the server config object. Please identify a valid fulltext installation in the verity_location attribute of the server config object.
CAUSE: This error occurs if the verity_location attribute in the server config is not set.
ACTION: Set verity_location attribute of the server config object to a valid fulltext install location. Valid fulltext installations are listed in the fulltext_install_locs attribute of the docbase config object.
PARAMS:

ERROR: [DM_FT_INDEX_W_NO_VERITY_CODEPAGE_SPECIFIED]

SEVERITY: WARNING
DESCRIPTION: SS The verity_default_codepage flag was not specified in the server.ini for the %s locale. The server will set %s as the codepage for all existing dm_fulltext_index objects.
CAUSE: A verity locale was specified in the server.ini file but not a verity default codepage.
ACTION: The server has set an appropriate codepage based on the verity locale in the server.ini. No user action is required.
PARAMS:

ERROR: [DM_FT_INDEX_W_UPGRADE_400_TPART_TYPE_NOT_FOUND]

SEVERITY: WARNING
DESCRIPTION: The dmi_topic_partition type was not found during upgrade. Skipping.
CAUSE: This may be a second invocation of this upgrade.
ACTION: None needed.
PARAMS:

ERROR: [DM_FT_INDEX_W_FULLTEXT_IMPLEMENTATION_NOT_LOADED]

SEVERITY: WARNING
DESCRIPTION: A fulltext library is currently loaded. Changes made to load a new fulltext library cannot take effect until Content Server is restarted.
CAUSE: An attempt was made to load a new fulltext library without restarting Content Server.
ACTION: Restart Content Server after making the necessary changes.
PARAMS:

ERROR: [DM_FT_INDEX_T_INIT_INDEX_AGENT_UNABLE_TO_START]

SEVERITY: TRACE
DESCRIPTION: D Unable to start Index Agent %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_T_INIT_INDEX_AGENT_STARTED]

SEVERITY: TRACE
DESCRIPTION: D Index Agent %s started.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_T_UPGRADE53_OBSOLETE_ATTRIBUTE_DROPPED]

SEVERITY: TRACE
DESCRIPTION: S Attribute %s dropped from dm_fulltext_index successfully.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_T_UPGRADE53_REMOVE_INDEX_OBJECT]

SEVERITY: TRACE
DESCRIPTION: S The dm_fulltext_index object with %s is removed successfully
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_T_FTMETHOD_TIMEOUT]

SEVERITY: TRACE
DESCRIPTION: Timing out of %s method
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_T_UPGRADE_TOPIC_400D_DONE]

SEVERITY: TRACE
DESCRIPTION: Fulltext index topic to tdk upgrade succeeded
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_T_UPGRADE_SYSOBJECT_400_PART1_DONE]

SEVERITY: TRACE
DESCRIPTION: Part 1 of fulltext index sysobject upgrade succeeded
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_T_INIT_INDEX_AGENT_NO_FTINDEX_AGENT_FOUND]

SEVERITY: TRACE
DESCRIPTION: S There were no dm_ftindex_agent_config object(s) found for dm_fulltext_index object with name %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_T_UPGRADE53_ATTRIBUTE_ADDED]

SEVERITY: TRACE
DESCRIPTION: S Added attribute %s to the dm_fulltext_index type
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_T_UPGRADE53_REMOVE_INDEX_IMPLEMENTATION_OBJECT]

SEVERITY: TRACE
DESCRIPTION: SS Removal of dmi_tdk_index object with id %s %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_T_INIT_INDEX_AGENT_MSG]

SEVERITY: TRACE
DESCRIPTION: S %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_T_INIT_INDEX_AGENT_INVALID_FTINDEX_AGENT_CONFIG]

SEVERITY: TRACE
DESCRIPTION: D dm_ftindex_agent_config object %s is invalid.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_T_UPGRADE_SYSOBJECT_400_PART2_DONE]

SEVERITY: TRACE
DESCRIPTION: Part 2 of fulltext index sysobject upgrade succeeded
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_T_UPGRADE53_OBSOLETE_INDEX_LOCATION]

SEVERITY: TRACE
DESCRIPTION: S The Verity sub-directory under the directory indicated by the file_system_path attribute of the following dm_location objects are not used for fulltext indexing: %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_T_UPGRADE_SYSOBJECT_400_DONE]

SEVERITY: TRACE
DESCRIPTION: Fulltext index sysobject upgrade succeeded
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_T_INIT_INDEX_AGENT_INVALID_FTINDEX]

SEVERITY: TRACE
DESCRIPTION: D dm_fulltext_index (%s) is invalid
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_T_UPGRADE53_REMOVE_COLLECTION_OBJECT]

SEVERITY: TRACE
DESCRIPTION: SS Removal of dmi_tdk_collect object with id %s %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FT_INDEX_I_IN_PROGRESS]

SEVERITY: INFORMATION
DESCRIPTION: SS Cannot perform operation %s — Fulltext index %s is currently in progress.
CAUSE: An attempt to perform an operation while another operation is in progress on the same index.
ACTION: Wait for the other operation to finish and try again.
PARAMS: The name of the operation, the name of the index

nahoru

DM_FULLTEXT

ERROR: [DM_FULLTEXT_F_FTDQL_OBJECT_MERGE_FAIL]

SEVERITY: FATAL
DESCRIPTION: Unable to perform object merge
CAUSE: this is an internal error while processing a FASDQL compliant query.
ACTION: Note other error messages and server log and contact system administrator. $Id: dmgroup.e,v 5.5 2003/03/10 21:59:12 swei Exp $ dmGroup class errors
PARAMS:

ERROR: [DM_FULLTEXT_F_ZERO_CHILDREN]

SEVERITY: FATAL
DESCRIPTION: An internal inconsistency has been encountered.
CAUSE: An internal Verity call has returned no children (matched documents), however an earlier call to get information about the retrieval indicated that there were matched documents.
ACTION: This is an internal inconsistency. Contact your Documentum Site Representative.
PARAMS: None.

ERROR: [DM_FULLTEXT_F_VERITY_ENV]

SEVERITY: FATAL
DESCRIPTION: Unable to initialize the Verity API environment.
CAUSE: An error occurred during the Verity API environment setup, causing your statement to fail.
ACTION: There should be another error message on the message queue which will contain additional information about the cause of the Verity failure. Take whatever steps are appropriate to resolve the Verity problem, and retry your query.
PARAMS: None.

ERROR: [DM_FULLTEXT_F_BAD_CONTENT]

SEVERITY: FATAL
DESCRIPTION: S The content id retrieved from Verity is an invalid Documentum dmID value: %s.
CAUSE: The Documentum dmID for indexed content objects are stored with the Verity index. An id retrieved for a matched content object during this Verity retrieval is not a valid dmID.
ACTION: Contact your Documentum Site Representative.
PARAMS: The invalid id value, as returned by Verity.

ERROR: [DM_FULLTEXT_F_VERITY_FATAL]

SEVERITY: FATAL
DESCRIPTION: SIS A fatal error has been encountered in Verity: (%s) code = %d, text = %s
CAUSE: The Verity fulltext system has generated a fatal error.
ACTION: The Verity error message is contained in this message. Take whatever action is appropriate based on the Verity error message to correct the problem. You may need assistance from your Verity site representative to resolve this problem.
PARAMS: The Verity error message string.

ERROR: [DM_FULLTEXT_F_DATABASE_ERROR]

SEVERITY: FATAL
DESCRIPTION: S An unexpected database error has occurred (%s), causing your statement to fail.
CAUSE: The RDBMS has encountered an error which has caused further processing of your query to be impossible.
ACTION: The error message string from the RDBMS is contained in the message. Take whatever action is appropriate based on the RDBMS message to correct the problem. This type of error sometimes occurs if a system limit of the RDBMS has been exceeded, or the RDBMS has failed. You may require assistance from your RDBMS System Administrator to resolve this problem.
PARAMS: The first parameter is the name of the DocuServer function in which the error occurred. The second parameter contains the error message from the RDBMS.

ERROR: [DM_FULLTEXT_F_NO_FULLTEXT]

SEVERITY: FATAL
DESCRIPTION: Unable to create a fulltext object.
CAUSE: This is an internal error. It is probably caused by insufficient memory.
ACTION: Contact your Documentum system administrator.
PARAMS:

ERROR: [DM_FULLTEXT_F_VERITY_DOCV]

SEVERITY: FATAL
DESCRIPTION: Unable to create a Verity document view.
CAUSE: An unexpected error occurred during the Verity API docview creation, causing your statement to fail.
ACTION: There will be another error message on the message queue which will contain additional information about the cause of the Verity failure. Take whatever steps are appropriate to resolve the Verity problem, and retry your query.
PARAMS: None.

ERROR: [DM_FULLTEXT_F_FTDQL_INIT_QUERY_DATA_FAIL]

SEVERITY: FATAL
DESCRIPTION: S Failed to initialize the data structures for FTDQL. Reason: %s
CAUSE: This is an internal error in the processing of a FTDQL compliant query.
ACTION: Contact your Documentum system administrator.
PARAMS:

ERROR: [DM_FULLTEXT_F_NO_DBCONN]

SEVERITY: FATAL
DESCRIPTION: Unable to establish a database connection.
CAUSE: The Documentum server was unable to establish a database connection on which to create a table to hold fulltext results.
ACTION: Check with your Documentum system administrator or your Oracle system administrator. It may be that your Oracle installation has a limit on the number of connections that is too low.
PARAMS:

ERROR: [DM_FULLTEXT_F_VERITY_UNEXPECTED]

SEVERITY: FATAL
DESCRIPTION: ISS An unexpected Verity error, error code = %d, has been encountered during: %s, %s
CAUSE: An unexpected error occurred during Verity processing, causing your statement to fail.
ACTION: There will be another error message on the message queue which will contain additional information about the cause of the Verity failure. Take whatever steps are appropriate to resolve the Verity problem. If it is necessary to contact your Documentum site Representative, please have this message, and its parameters, available.
PARAMS: The first parameter is the name of the Verity function that failed. The second parameter is information describing which particular call to that function it was that failed. The third parameter is usually 0 (zero), but in some instances the value contains additional information about the error. The first two parameters may be useful to Verity technical support, if it becomes involved in the problem resolution. Those, in addition to the third parameter, may be useful to Documentum technical support, if it becomes involved in the problem resolution.

ERROR: [DM_FULLTEXT_E_STRING_MALFORMED]

SEVERITY: ERROR
DESCRIPTION: IS Attempt to assign malformed value of encoding %d to attribute %s.
CAUSE: Program executed a Set operation supplying a string value that was not a legal string in the specified encoding
ACTION: No action.
PARAMS:

ERROR: [DM_FULLTEXT_E_SEARCH_FT_ENGINE_GENERAL_ERROR]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: A generic error occured in the underlying fulltext engine while executing a search.
ACTION: Refer to the FT Engine trouble shooting guide.
PARAMS:

ERROR: [DM_FULLTEXT_E_SEARCH_STATUS_FAIL]

SEVERITY: ERROR
DESCRIPTION: SI dmFTSearchStatus failed with error: %s, error code: %d
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FULLTEXT_E_SEARCH_FT_ENGINE_UNABLE_TO_SEND_DOC_SUMMARY_REQUEST]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: Content Server is unable to send a request to the Index Server to retrieve the document summary.
ACTION: Refer to the FT Engine trouble shooting guide.
PARAMS:

ERROR: [DM_FULLTEXT_E_SEARCH_FT_ENGINE_FETCH_DOC_SUMMARY_TIMEOUT]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: A timeout error occured when retrieving the document summary from the Index Server.
ACTION: Refer to the FT Engine trouble shooting guide.
PARAMS:

ERROR: [DM_FULLTEXT_E_SEARCH_GET_ROW_FAIL]

SEVERITY: ERROR
DESCRIPTION: SI dmFTSearchGetRow failed with error: %s, error code: %d
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FULLTEXT_E_BAD_SDC_PHRASE]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: This is error from SDC parser.
ACTION: Refer to the FT Engine trouble shooting guide or contact your administrator.
PARAMS:

ERROR: [DM_FULLTEXT_E_SEARCH_FT_ENGINE_SEARCH_PARTITIONS_UNAVAILABLE]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: The fulltext engine could not execute a search because index files are unavailable.
ACTION: Refer to the FT Engine trouble shooting guide.
PARAMS:

ERROR: [DM_FULLTEXT_E_CANT_OPEN_SESSION]

SEVERITY: ERROR
DESCRIPTION: SI Unable to open a session with fulltext engine: %s, Error Code: %d
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FULLTEXT_E_SEARCH_FT_ENGINE_INVALID_QUERY_STATE]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: This is an internal error reported by the Index Server.
ACTION: Refer to the FT engine trouble shooting guide.
PARAMS:

ERROR: [DM_FULLTEXT_E_FTDQL_UNABLE_TO_BUILD_ACL_LIST]

SEVERITY: ERROR
DESCRIPTION: Unable to build ACL list
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FULLTEXT_E_SEARCH_FT_ENGINE_CONNECTION_FAILURE_DURING_SEARCH]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: A connection failure occured during search between Content Server and the Index Server.
ACTION: Contact your repository administrator.
PARAMS:

ERROR: [DM_FULLTEXT_E_SEARCH_FT_ENGINE_INTERNAL_ERROR]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: The fulltext engine encountered an internal error while executing a search.
ACTION: Refer to the FT Engine trouble shooting guide.
PARAMS:

ERROR: [DM_FULLTEXT_E_FTDQL_UNABLE_TO_FETCH_USER_GROUP_LIST]

SEVERITY: ERROR
DESCRIPTION: Unable to obtain user group list
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FULLTEXT_E_SEARCH_FT_ENGINE_PARTIAL_SEARCH_RESULT]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: This is an internal error from the Index Server.
ACTION: Refer to the FT Engine trouble shooting guide or contact your administrator.
PARAMS:

ERROR: [DM_FULLTEXT_E_FTDQL_UNABLE_TO_EXECUTE_FULLTEXT_QUERY]

SEVERITY: ERROR
DESCRIPTION: Unable to execute the full text query in FTDQL Mode.
CAUSE: An error occured while setting up the underlying fulltext query engine to run a full text query.
ACTION: Look for additional error messages that indicate the nature of the problem.
PARAMS:

ERROR: [DM_FULLTEXT_E_CANT_FETCH_TOPIC_INDEX]

SEVERITY: ERROR
DESCRIPTION: D You have tried to fetch a Topic index with ID %s.
CAUSE: Topic 4.00d indexes are no longer supported.
ACTION: Make sure the i_implementation_type of the dm_fulltext_index object has a value 2 (i.e. TDK).
PARAMS:

ERROR: [DM_FULLTEXT_E_SEARCH_FT_ENGINE_NO_QUERY_STATE]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: This is an internal error reported by the fulltext engine while executing a query.
ACTION: Refer to the FT Engine trouble shooting guide.
PARAMS:

ERROR: [DM_FULLTEXT_E_FETCH_UNKNOWN_INDEX_TYPE]

SEVERITY: ERROR
DESCRIPTION: ID You tried to fetch an unknown fulltext type, %d, object with ID %s.
CAUSE: An unknown index type is supplied while making a new fulltext object.
ACTION: Make sure the i_implementation_type of the dm_fulltext_index object has a value 2 (i.e. TDK).
PARAMS:

ERROR: [DM_FULLTEXT_E_SEARCH_FT_ENGINE_NO_SEARCH_CHANNEL]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: A communication failure occured between the Content Server host and the host on which the Index Server is running.
ACTION: Resolve communication/connectivity problems by contacting the Administrator.
PARAMS:

ERROR: [DM_FULLTEXT_E_SEARCH_FT_ENGINE_SYSTEM_OVERLOAD]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: The fulltext engine could not execute a search because its been overloaded.
ACTION: Refer to the FT Engine trouble shooting guide.
PARAMS:

ERROR: [DM_FULLTEXT_E_COULD_NOT_OPEN_FILE_FOR_WRITE]

SEVERITY: ERROR
DESCRIPTION: S The file- %s could not be opened for writing
CAUSE: The directory to write the file probably does not exist.
ACTION: Make sure that the directory to write the file exists.
PARAMS:

ERROR: [DM_FULLTEXT_E_VERITY_NOT_AVAILABLE]

SEVERITY: ERROR
DESCRIPTION: You have specified a SEARCH clause in your query, but no fulltext system is available.
CAUSE: Either Verity is not installed, or the Verity installation is not available.
ACTION: Make sure that the installation procedures for setting up Verity to run with DocuServer are followed.
PARAMS: None.

ERROR: [DM_FULLTEXT_E_SEARCH_FT_ENGINE_QUERY_SERVER_GENERIC_ERROR_CODE]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: This is an internal error from the Query Server configured to be captured in the dm_ftengine_config.
ACTION: Refer to the FT Engine trouble shooting guide or contact your administrator.
PARAMS:

ERROR: [DM_FULLTEXT_E_FTDQL_UNABLE_TO_EXECUTE_QUERY_FOR_SELECT_LIST]

SEVERITY: ERROR
DESCRIPTION: Unable to execute a database query to fetch data for select list for a FTDQL compliant query
CAUSE: A database error.
ACTION: Look for other messages and contact your system administrator.
PARAMS:

ERROR: [DM_FULLTEXT_E_SEARCH_FT_ENGINE_MEMORY_ALLOCATION_FAILURE]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: This is an internal error from the Index Server.
ACTION: Refer to the FT Engine trouble shooting guide or contact your administrator.
PARAMS:

ERROR: [DM_FULLTEXT_E_SEARCH_FT_ENGINE_QUERY_TIMEOUT]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: The search submitted to the Index Server has timedout.
ACTION: Contact your administrator.
PARAMS:

ERROR: [DM_FULLTEXT_E_BAD_XQUERY_STREAM]

SEVERITY: ERROR
DESCRIPTION: I Invalid xquery result stream: 0%xp. PARAMETER: The stream source address.
CAUSE: The xquery result stream source is invalid, might have been close.
ACTION: Retry without closing the stream source.
PARAMS:

ERROR: [DM_FULLTEXT_E_VERITY_RETRIEVE]

SEVERITY: ERROR
DESCRIPTION: S An error has occurred during the processing of the Verity query: %s
CAUSE: Verity was unable to process the Verity query. This could be an expected error, such as that the query was not a valid Verity boolean plus query. Or, it could be an unexpected Verity failure.
ACTION: There will be another error message on your message queue which contains the Verity error message. Take whatever action is appropriate to correct the problem.
PARAMS: The Verity boolean plus query that was not successfully processed.

ERROR: [DM_FULLTEXT_E_INCORRECT_STORE_TYPE_FOR_RENDITION]

SEVERITY: ERROR
DESCRIPTION: SS Primary Content object %s uses a CA Store but the indexable rendition object %s uses a non-CA storage type.
CAUSE: This error occurs during full-text indexing of content in a CA Store and the primary content is of non-indexable format and an indexable rendition for the content is not using a CA Store.
ACTION: Destroy the rendition in the non-CA Store and create a rendition in the same CA store as the primary content.
PARAMS:

ERROR: [DM_FULLTEXT_E_SEARCH_FT_ENGINE_UNABLE_TO_SEND_QUERY]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: A communication error occured while submitting a search, between the Content Server host and the Index Server host.
ACTION: Contact your repository Administrator.
PARAMS:

ERROR: [DM_FULLTEXT_E_FEATURE_NOT_AVAILABLE]

SEVERITY: ERROR
DESCRIPTION: S Feature %s is not available.
CAUSE: The feature is not implemented in the fulltext engine.
ACTION: None
PARAMS:

ERROR: [DM_FULLTEXT_E_FTDQL_OBJECT_MERGE_FAIL]

SEVERITY: ERROR
DESCRIPTION: Unable to process fulltext results for a FTDQL compliant query.
CAUSE: A database error occured while processing the fulltext results in conjunction with processing of select list.
ACTION: Contact your system administrator.
PARAMS:

ERROR: [DM_FULLTEXT_E_BAD_PULLER_HANDLE]

SEVERITY: ERROR
DESCRIPTION: I Cannot find puller with handle: %ld. PARAMETER: Puller handle
CAUSE: The puller has not been created or already been removed.
ACTION: None.
PARAMS:

ERROR: [DM_FULLTEXT_E_SEARCH_FT_ENGINE_UNABLE_TO_STORE_DOC_SUMMARY]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: This is an internal error from the Index Server.
ACTION: Refer to the FT Engine trouble shooting guide or contact your administrator.
PARAMS:

ERROR: [DM_FULLTEXT_E_FTDQL_DUPLICATE_ITEM_IN_ACL_CACHE]

SEVERITY: ERROR
DESCRIPTION: Unable to add an duplicate item to ACL cache
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FULLTEXT_E_SEARCH_FT_ENGINE_QUERY_RESOURCE_LIMIT_EXCEEDED]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: This is an internal error from the Index Server.
ACTION: Refer to the FT Engine trouble shooting guide or contact your administrator.
PARAMS:

ERROR: [DM_FULLTEXT_E_SEARCH_FT_ENGINE_INVALID_RESPONSE_FOR_DOC_SUMMARY]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: This is an internal error from the Index Server.
ACTION: Refer to the FT Engine trouble shooting guide or contact your administrator.
PARAMS:

ERROR: [DM_FULLTEXT_E_MAKE_UNKNOWN_INDEX_TYPE]

SEVERITY: ERROR
DESCRIPTION: IS You tried to create an unknown fulltext type, %d, object on location %s.
CAUSE: An unknown index type is supplied while making a new fulltext object.
ACTION: Make sure the i_implementation_type of the dm_fulltext_index object has a value 2 (i.e. TDK).
PARAMS:

ERROR: [DM_FULLTEXT_E_CANT_MAKE_TOPIC_INDEX]

SEVERITY: ERROR
DESCRIPTION: S You have tried to create a Topic index on location %s.
CAUSE: Topic 4.00d indexes are no longer supported.
ACTION: Make sure the i_implementation_type of the dm_fulltext_index object has a value 2 (i.e. TDK).
PARAMS:

ERROR: [DM_FULLTEXT_E_SEARCH_FT_ENGINE_QUERY_NOT_ALLOWED]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: The fulltext engine has been configured to not allow the kind of search being executed.
ACTION: You cannot execute search you have submitted.
PARAMS:

ERROR: [DM_FULLTEXT_E_FTDQL_PERMIT_CHECK_FAIL]

SEVERITY: ERROR
DESCRIPTION: Unable to run the permit check on a result set.
CAUSE: This error is returned when the Content Server is unable to perform the permit check on objects to be returned., most likely due to a database error.
ACTION: contact your system administrator.
PARAMS:

ERROR: [DM_FULLTEXT_E_SEARCH_FT_ENGINE_QUERY_WILDCARD_TERM_COUNT_THRESHOLD_EXCEEDED]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: This is an internal error from the Index Server.
ACTION: Refer to the FT Engine trouble shooting guide or contact your administrator.
PARAMS:

ERROR: [DM_FULLTEXT_E_HIGHLIGHT_READ_FAIL]

SEVERITY: ERROR
DESCRIPTION: SI dmFTHighlightRead failed with error: %s, error code: %d
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FULLTEXT_E_INCORRECT_STORE_TYPE_FOR_RENDITION2]

SEVERITY: ERROR
DESCRIPTION: SSSS Primary Content Object %s uses CA Store %s, whereas the indexable rendition %s uses CA Store %s
CAUSE: This error occurs when the primary content to be indexed and its indexable rendition are on two different CA Stores.
ACTION: Create the rendition object in the same CA Store as the primary content and destroy the rendition object in the other CA Store.
PARAMS:

ERROR: [DM_FULLTEXT_E_FTDQL_UNABLE_TO_EXECUTE_SQL_FOR_ACL_CHECK]

SEVERITY: ERROR
DESCRIPTION: SS Unable to execute SQL to perform ACL check. SQL Statement was: %s, Error from database: %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FULLTEXT_E_SEARCH_FT_ENGINE_FEATURE_NOT_IMPLEMENTED]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: The search submitted to the fulltext engine is not supported by the FT engine.
ACTION: Contact Technical Support
PARAMS:

ERROR: [DM_FULLTEXT_E_FTDQL_UNABLE_TO_FETCH_SELECT_LIST_DATA]

SEVERITY: ERROR
DESCRIPTION: A database error occured while processing the select list for a FTDQL compliant query
CAUSE: A database error occured.
ACTION: Contact your system administrator
PARAMS:

ERROR: [DM_FULLTEXT_E_SEARCH_NEW_FAIL]

SEVERITY: ERROR
DESCRIPTION: SI dmFTSearchNew failed with error: %s, error code: %d
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FULLTEXT_E_EXEC_XQUERY_FAIL]

SEVERITY: ERROR
DESCRIPTION: SI EXEC_XQUERY failed with error: %s, error code: %d
CAUSE: Failed to execute the xquery statement.
ACTION: Check the error message returned from query plugin and correct the xquery statement.
PARAMS:

ERROR: [DM_FULLTEXT_E_SEARCH_FT_ENGINE_QUERY_PARSE_ERROR]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: A parsing error occured in the query submitted to the fulltext engine.
ACTION: Contact EMC Technical Support.
PARAMS:

ERROR: [DM_FULLTEXT_E_SEARCH_FT_ENGINE_INVALID_QUERY_RESPONSE]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: A communication error occured while processing a search between the Content Server host and the Index Server host.
ACTION: Contact your repository administrator.
PARAMS:

ERROR: [DM_FULLTEXT_E_FTDQL_INVALID_SECURITY_MODE]

SEVERITY: ERROR
DESCRIPTION: Invalid value for security_mode in dm_ftengine_config object. The valid options are BROWSE,READ or SUMMARY_BASED
CAUSE: This error is returned when a non-allowed value in set for security_mode in dm_ftengine_config object.
ACTION: Set security_mode to one of the valid options ( READ, BROWSE or SUMMARY_BASED ) or contact your system administrator.
PARAMS:

ERROR: [DM_FULLTEXT_E_SEARCH_FT_ENGINE_CONNECTION_ERROR_DURING_DOC_SUMMARY_FETCH]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: A connection error occured while retrieving the document summary from the Index Server.
ACTION: Refer to the FT Engine trouble shooting guide or contact your administrator.
PARAMS:

ERROR: [DM_FULLTEXT_W_BAD_SYSOBJ_ID]

SEVERITY: WARNING
DESCRIPTION: SI Bad sysobj id (%s) at child node %d.
CAUSE: This is an internal error caused by a Verity bug. If you get this warning (it should never occur, but in case it does) it means that there was a document match that you are not going to see.
ACTION: The rest of your matched documents are returned to you. Report this error to your Documentum Site Representative.
PARAMS: The first parameter will probably be blank. The second parameter is Verity-related information that may be useful in determining the problem, especially if you get more than one of these messages for a single query. Report these parameters to your Documentum Site Representative.

ERROR: [DM_FULLTEXT_W_INDEX_IGNORED]

SEVERITY: WARNING
DESCRIPTION: S Fulltext index %s not accessible — index ignored
CAUSE: A fulltext index that was to be searched could not be accessed. A likely cause is that the fulltext index was destroyed by another user or the index was reset or cleaned while the search was being done.
ACTION: The rest of your matched documents are returned to you.
PARAMS: The name of the fulltext index

ERROR: [DM_FULLTEXT_W_IGNORED]

SEVERITY: WARNING
DESCRIPTION: I Could not read %i files during hit processing — content ignored
CAUSE: To return position or hit information, the file that was indexed needs to be read — for some reason, one or more files could not be read. Likely causes include migrating the content to some other storage area or destorying the content.
ACTION: The rest of your matched documents are returned to you.
PARAMS: The number of files ignored

ERROR: [DM_FULLTEXT_W_VERITY_WARN]

SEVERITY: WARNING
DESCRIPTION: SIS A message is generated from Verity: (%s) code = %d, text = %s
CAUSE: The Verity fulltext system has generated a message.
ACTION: The Verity message is contained in this message. Take whatever action is appropriate based on the Verity message to correct the problem. You may need assistance from your Verity site representative to resolve this problem.
PARAMS: The Verity message code and string.

ERROR: [DM_FULLTEXT_W_BAD_CONTENT_ID]

SEVERITY: WARNING
DESCRIPTION: SI Bad content id (%s) at child node %d.
CAUSE: This is an internal error caused by a Verity bug. If you get this warning (it should never occur, but in case it does) it means that there was a document match that you are not going to see.
ACTION: The rest of your matched documents are returned to you. Report this error to your Documentum Site Representative.
PARAMS: The first parameter will probably be blank. The second parameter is Verity-related information that may be useful in determining the problem, especially if you get more than one of these messages for a single query. Report these parameters to your Documentum Site Representative.

ERROR: [DM_FULLTEXT_T_QUERY_PLUGIN_VERSION]

SEVERITY: TRACE
DESCRIPTION: S Loaded FT Query Plugin: %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FULLTEXT_T_NUM_CHILDREN]

SEVERITY: TRACE
DESCRIPTION: I GetFTResults: Number of children of the rootnode of the docview: %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FULLTEXT_T_BEGIN_VERITY_RETRIEVAL]

SEVERITY: TRACE
DESCRIPTION: Verity retrieval is beginning.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FULLTEXT_T_VERITY_RETRIEVAL_COMPLETE]

SEVERITY: TRACE
DESCRIPTION: Verity retrieval has completed.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FULLTEXT_T_FULLTEXT_QUERY]

SEVERITY: TRACE
DESCRIPTION: S Fulltext Query: %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FULLTEXT_T_NUM_POSITIONS]

SEVERITY: TRACE
DESCRIPTION: I GetFTResults: Number of positions (hits within a document): %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FULLTEXT_T_FTDQL_DATA]

SEVERITY: TRACE
DESCRIPTION: ISSS FTDQL Execution. ft_convertible = %d, converted_ft_query = %s, search phrase = %s, ft_search_type = %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_FULLTEXT_T_NUM_MATCHES]

SEVERITY: TRACE
DESCRIPTION: I RunFTQuery: Number of documents matched by the fulltext query was %d.
CAUSE:
ACTION:
PARAMS:

nahoru

DM_GROUP

ERROR: [DM_GROUP_F_INIT3]

SEVERITY: FATAL
DESCRIPTION: The type manager returned an error storing the dm_group type.
CAUSE: Unknown.
ACTION: Look at the error logged by the type manager. Report this message and any parameters to your Documentum Site Representative.
PARAMS:

ERROR: [DM_GROUP_F_INIT4]

SEVERITY: FATAL
DESCRIPTION: I The dm_group type could not be converted %d.
CAUSE: Failure to convert dm_group type. Unable to add attributes to dm_group type.
ACTION: Report this message to your EMC Documentum Site representative.
PARAMS:

ERROR: [DM_GROUP_F_INIT1]

SEVERITY: FATAL
DESCRIPTION: The dm_group type was found in the database without a version stamp.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum Site Representive.
PARAMS:

ERROR: [DM_GROUP_F_INIT2]

SEVERITY: FATAL
DESCRIPTION: II Version stamp %d was expected to be %d.
CAUSE: The version stamp that the dm_group object software expected was different from the actual version stamp in the database.
ACTION: You must upgrade your DocuServer database to conform to the software that you are running. If your software and data are consistent, then report this message and any parameters to your Documentum Site Representive.
PARAMS:

ERROR: [DM_GROUP_F_INT1]

SEVERITY: FATAL
DESCRIPTION: S The following database query %s could not be executed.
CAUSE: Inconsistency between the server and the group type.
ACTION: Look at the error logged by the database. Report this message and any parameters to your Documentum Site Representative.
PARAMS:

ERROR: [DM_GROUP_F_UPGRADE_NONDYN]

SEVERITY: FATAL
DESCRIPTION: Unable to upgrade the i_nondyn_supergroups_names attributes.
CAUSE: Failure to populate the i_nondyn_supergroups_names attributes during an upgrade operation.
ACTION: Report this message to your EMC Documentum Site representative. $Id: dmiditr.e,v 5.4 2000/11/15 05:12:22 ghwang Exp $ SQL DMID Iterator error ** Documentum DocuServer ** Confidential Property of Documentum, Inc. ** (c) Copyright Documentum, Inc., 1991-1998 ** All rights reserved. **
PARAMS:

ERROR: [DM_GROUP_E_CANT_FETCH_INVALID_ID]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch a group – Invalid object ID %s.
CAUSE: Cannot fetch the group with the given object id.
ACTION: Try again with the correct id.
PARAMS:

ERROR: [DM_GROUP_E_ATTR_PRIV]

SEVERITY: ERROR
DESCRIPTION: SS Insufficient privilege to set the %s attribute of group %s. ARGUMENTS: %s – the attribute the user did not have permission to set/modify. %s – the name of the group object
CAUSE: The user did not have privilege to set/change the specified field.
ACTION: See your sites superuser about changing the desired field.
PARAMS:

ERROR: [DM_GROUP_E_DROP_NONMEMBER_USER]

SEVERITY: ERROR
DESCRIPTION: SS Cannot drop a non-member user %s from the %s group.
CAUSE: Tried to drop a user that is not in this group.
ACTION: Try with a valid user name.
PARAMS:

ERROR: [DM_GROUP_E_CANT_FIND_GROUP]

SEVERITY: ERROR
DESCRIPTION: S Cannot find %s group.
CAUSE: Cannot find the group with the given name. This may happen when fetching a group by name during save, destroy, or group inclusion, exclusion.
ACTION: Try again with the correct name.
PARAMS:

ERROR: [DM_GROUP_E_NOT_DYNAMIC_MEMBER]

SEVERITY: ERROR
DESCRIPTION: S User is not a potential dynamic member of group %s.
CAUSE: The requested dynamic group does not exist, is not dynamic, or the requesting user is not a potential member of the group.
ACTION: Check the group name and the users permission to include it.
PARAMS:

ERROR: [DM_GROUP_E_MISSING_PARAMETERS]

SEVERITY: ERROR
DESCRIPTION: S You must supply parameters to the apply method (%s)
CAUSE: Caller did not supply any arguments to the apply method
ACTION: The application or user is in error. Make sure to supply the required USER argument and optionally the DOMAIN argument.
PARAMS:

ERROR: [DM_GROUP_E_PROTECTED_ROLE_UNKNOWN_CLIENT]

SEVERITY: ERROR
DESCRIPTION: S The requested role (%s) is marked protected and the requesting application was either not known in this docbases dm_client_rights table or its credentials did not match those in the dm_client_rights table.
CAUSE: An attempt was made to add a protected dynamic role or group to the session, but the client application has not been authenticated.
ACTION: Check that the requesting client application is registered and granted privileged to use the requested role.
PARAMS:

ERROR: [DM_GROUP_E_CANT_SAVE]

SEVERITY: ERROR
DESCRIPTION: S Cannot save %s group
CAUSE: Couldnt save the group.
ACTION: Previous error message should provide the answer.
PARAMS:

ERROR: [DM_GROUP_E_NEED_SU_OR_SYS_PRIV]

SEVERITY: ERROR
DESCRIPTION: S The current user (%s) needs to have superuser or sysadmin privilege.
CAUSE: Must have Superuser or SysAdmin privilege to perform this operation.
ACTION: Consult your Documentum Administrator.
PARAMS:

ERROR: [DM_GROUP_E_CANT_CREATE_EXISTING_GROUP]

SEVERITY: ERROR
DESCRIPTION: S Cannot create the %s group since it already exists.
CAUSE: Tried to create a group that already exists. All group names are unique. Also a group is treated as a user and its name must be unique in the user name space as well.
ACTION: Try again with a different group name.
PARAMS:

ERROR: [DM_GROUP_E_DYNAMIC_SUBGROUP]

SEVERITY: ERROR
DESCRIPTION: S Cannot add dynamic group %s as a subgroup of a regular group.
CAUSE: Normal groups cannot contain dynamic subgroups. Only dynamic groups can contain dynamic subgroups.
ACTION: The dynamic subgroups must be removed before saving this group.
PARAMS:

ERROR: [DM_GROUP_E_CANT_CHANGE_DYNAMIC]

SEVERITY: ERROR
DESCRIPTION: S Cannot change group %s to be a dynamic group while it is contained in other groups.
CAUSE: A group that is already a subgroup of other groups cannot be changed to be a dynamic group.
ACTION: Check previous error messages for more information on the error.
PARAMS:

ERROR: [DM_GROUP_E_CANT_GET_ROLES]

SEVERITY: ERROR
DESCRIPTION: S The ROLES_FOR_USER method failed because of the following: %s.
CAUSE: ROLES_FOR_USER failed because of the specified database failure.
ACTION: Talk to your System Administrator about correcting the database operation.
PARAMS:

ERROR: [DM_GROUP_E_DUPLICATE_DISPLAY_NAME]

SEVERITY: ERROR
DESCRIPTION: SSD Cannot save group %s because its display name (%s) and native room id (%s) together is not unique
CAUSE: The display name together with the native room id in a repository needs to be unique.
ACTION: Choose a different display name for the group.
PARAMS:

ERROR: [DM_GROUP_E_MODULE_ROLE_STATEFUL_REQUEST]

SEVERITY: ERROR
DESCRIPTION: S Module Role cannot be added through AddDynamicGroup interface. A call was made to add a role (%s) to the session in a stateful mode. This is not allowed when the is_module_only attribute is set.
CAUSE: An attempt was made to add a dynamic role or group to the session in a stateful manner – probably through the AddDynamicGroup interface – but the role definition (is_module_only) disallows this use. The role /group can only be used through the doPrivileged dfc interfaces.
ACTION: Change the calling application or change the is_module_only settings to allow the current request.
PARAMS:

ERROR: [DM_GROUP_E_CANT_ADD_GROUP_TWICE]

SEVERITY: ERROR
DESCRIPTION: SS Cannot add group %s to the %s group more than once.
CAUSE: A group can be contained within another group list just once.
ACTION: Server side object is not affected. Remove the problem group.
PARAMS:

ERROR: [DM_GROUP_E_DEFAULT_DYNAMIC_SETTING]

SEVERITY: ERROR
DESCRIPTION: S Default dynamic group %s can not be protected nor module only.
CAUSE: A default dynamic group may not be set to protected mode nor to module only mode.
ACTION: Check the groups settings and either set default to false or do not set protected or module only to true.
PARAMS:

ERROR: [DM_GROUP_E_INSUFFICIENT_PRIVILEGE]

SEVERITY: ERROR
DESCRIPTION: SS The current user (%s) has insufficient privileges to save or destroy the %s group object.
CAUSE: A user with insufficient privileges tried to save or destroy a group object.
ACTION: You must have create group, sysadmin, or superuser privilege to create a group. You must be the creator of the group, or have superuser privilege to modify or destroy the group. See your system administrator if you think you should have create group privilege.
PARAMS:

ERROR: [DM_GROUP_E_CANT_ADD_GROUP_TO_USER]

SEVERITY: ERROR
DESCRIPTION: SS Cannot add group %s to the users_names of %s group.
CAUSE: You can only add users, not groups, to the column users_names of a group object.
ACTION: Server side object is not affected. Either change the attribute to groups_names or select a user for users_names.
PARAMS:

ERROR: [DM_GROUP_E_PROTECTED_ROLE_PRIV]

SEVERITY: ERROR
DESCRIPTION: S The requesting application is not privileged to use role (%s).
CAUSE: An attempt was made to add a protected dynamic role or group to the session, but the client application has not been configured as privileged.
ACTION: Check that the requesting client application is registered and granted privileged to use the requested role.
PARAMS:

ERROR: [DM_GROUP_E_ERROR_UPDATING_SUBGROUPS]

SEVERITY: ERROR
DESCRIPTION: S Error updating subgroups of group %s to reflect changes in the group heirarchy.
CAUSE: An internal error occurred as part of a group update operation.
ACTION: Check previous error messages for more information.
PARAMS:

ERROR: [DM_GROUP_E_PROCESS_GROUP_QUERY]

SEVERITY: ERROR
DESCRIPTION: S Error executing query to discover group membership for user %s.
CAUSE: A error occurred while running a database query to find the set of groups that the current user is a member of.
ACTION: Remove the group from its parent groups before setting it dynamic. Note that after being made dynamic, the group can be added back to the parent groups only if they are also dynamic.
PARAMS:

ERROR: [DM_GROUP_E_NEED_NAME_OR_EMAIL]

SEVERITY: ERROR
DESCRIPTION: Need to specify name and eMail for a group before save.
CAUSE: All group definitions must have a group name and e-mail address before save.
ACTION: Try again with both group_name and group_address.
PARAMS:

ERROR: [DM_GROUP_E_NONDYN_SUPERGROUP_QUERY]

SEVERITY: ERROR
DESCRIPTION: SS Error querying for nondynamic_supergroups of the parent groups of the group named %s. Query: %s
CAUSE: An internal error occurred as part of a group update operation.
ACTION: Check previous error messages for more information.
PARAMS:

ERROR: [DM_GROUP_E_NEED_SUPER_USER_PRIV]

SEVERITY: ERROR
DESCRIPTION: S The current user (%s) needs to have superuser privilege to save the group object.
CAUSE: Must have superuser privilege to save the group object. The user tried to change the following attributes without superuser privilege: . group_name . group_directory_id
ACTION: Consult your Documentum Administrator.
PARAMS:

ERROR: [DM_GROUP_E_GETINFO_DB]

SEVERITY: ERROR
DESCRIPTION: SS Error processing database cursor for group %s. (%s) An Internal error occurred while checking information on a given group name. The error may have been triggered by a problem with a database query. Previous error messages should give more detail on the failure.
CAUSE: An internal error occurred while looking up a group name.
ACTION: Check previous error messages for more information.
PARAMS:

ERROR: [DM_GROUP_E_CANT_DESTROY]

SEVERITY: ERROR
DESCRIPTION: S Cannot destroy the %s group
CAUSE: Could not destroy the group.
ACTION: Previous error message should provide the answer.
PARAMS:

ERROR: [DM_GROUP_E_INSUFFICIENT_PRIV_OWNER]

SEVERITY: ERROR
DESCRIPTION: S Cannot change the owner name of the %s group.
CAUSE: You must have superuser privilege to change the owner of a group.
ACTION: Set your sites superuser about changing the owner of the group.
PARAMS:

ERROR: [DM_GROUP_E_GETINFO]

SEVERITY: ERROR
DESCRIPTION: S Error getting information for group %s. An Internal error occurred while checking information on a given group name. The error may have been triggered by a problem with the group or group name, or could have been the result of a database error. Previous error messages should give more detail on the failure.
CAUSE: An internal error occurred while looking up a group name.
ACTION: Check previous error messages for more information.
PARAMS:

ERROR: [DM_GROUP_E_DIR_MAPPED_ATTR_CHANGED]

SEVERITY: ERROR
DESCRIPTION: SS Cannot save the directory group %s because at least one directory-mapped attribute (%s) has been changed
CAUSE: For directory groups, non-superuser is not allowed to change any directory-mapped attribute.
ACTION: Do not change any directory-mapped attributes. You need to either reset or revert the object in order to save other changes.
PARAMS:

ERROR: [DM_GROUP_E_INSUFFICIENT_PRIV_ADMIN]

SEVERITY: ERROR
DESCRIPTION: S Cannot change the group administrator of the %s group.
CAUSE: You must have superuser privilege or be the owner of a group in order to change the group administrator.
ACTION: See your sites superuser about changing the group administrator.
PARAMS:

ERROR: [DM_GROUP_E_CANT_CHANGE_NAME]

SEVERITY: ERROR
DESCRIPTION: S Cannot change name of the %s group.
CAUSE: Cannot change the group_name attribute of an existing group.
ACTION: None.
PARAMS:

ERROR: [DM_GROUP_E_CANT_ADD_USER_TWICE]

SEVERITY: ERROR
DESCRIPTION: SS Cannot add user %s to the %s group more than once.
CAUSE: A user can be contained within a group just once.
ACTION: Server side object is not affected. Remove the problem user.
PARAMS:

ERROR: [DM_GROUP_E_UNABLE_TO_SAVE_EXISTING]

SEVERITY: ERROR
DESCRIPTION: S Cannot save group %s because a user already exists with the same name
CAUSE: Users and groups share the same namespace and therefore groups cannot be created that have the same name as an existing user.
ACTION: Choose a different name for the group.
PARAMS:

ERROR: [DM_GROUP_E_DROP_NONMEMBER_GROUP]

SEVERITY: ERROR
DESCRIPTION: SS Cannot drop non-member %s group from the %s group.
CAUSE: Tried to drop a group that is not in this group.
ACTION: Try again with a valid group name.
PARAMS:

ERROR: [DM_GROUP_E_ILLEGAL_DIR_ID]

SEVERITY: ERROR
DESCRIPTION: SD Cannot save a directory group %s because its group_directory_id (%s) is illegal
CAUSE: For directory groups, the group_directory_id must be a legal directory config id.
ACTION: Make sure to provide a legal directory config id for the group.
PARAMS:

ERROR: [DM_GROUP_E_DEFAULT_NONDYNAMIC]

SEVERITY: ERROR
DESCRIPTION: S Non-dynamic group %s can not be set to default dynamic mode.
CAUSE: A non-dynamic group may not be set to default dynamic mode.
ACTION: Do not set the is_default_dynamic attribute of non-dynamic groups to true.
PARAMS:

ERROR: [DM_GROUP_E_CANT_FIND_USER]

SEVERITY: ERROR
DESCRIPTION: S Cannot find user %s.
CAUSE: Tried to insert or remove a nonexistent user.
ACTION: Try again with the correct name.
PARAMS:

ERROR: [DM_GROUP_E_UNABLE_TO_SAVE]

SEVERITY: ERROR
DESCRIPTION: S An error occurred during a save operation on the %s group.
CAUSE: An error occurred while saving this group.
ACTION: Check the following errors on the error stack for more details on the cause of this failure.
PARAMS:

ERROR: [DM_GROUP_E_NO_CYCLES_IN_GROUPS]

SEVERITY: ERROR
DESCRIPTION: SS Two groups cannot be contained in each other: Group %s forms a cycle with group %s.
CAUSE: Two groups can not be contained in each other.
ACTION: Reevaluate your group containment strategy, remove any groups that are out of place.
PARAMS:

ERROR: [DM_GROUP_E_ADD_AS_GROUP]

SEVERITY: ERROR
DESCRIPTION: S Group %s cannot be added as users.
CAUSE: Tried to add a group in the user list.
ACTION: Remove the group from the user list and add it to the groups_names.
PARAMS:

ERROR: [DM_GROUP_E_CANT_UNREGISTER]

SEVERITY: ERROR
DESCRIPTION: SS Could not unregister the specified %s event for %s object.
CAUSE: The specified event could not be unregistered. Most likely bad event name specified.
ACTION: Correct the event name and try again.
PARAMS:

ERROR: [DM_GROUP_E_INTERNAL_DEFAULT_DYNAMIC]

SEVERITY: ERROR
DESCRIPTION: S Default dynamic group %s can not be added to the session dynamic group list.
CAUSE: An internal error occurred preventing the group from being added to the session cache.
ACTION: Check previous error messages for more information.
PARAMS:

ERROR: [DM_GROUP_W_UPGRADE_I_POSITION]

SEVERITY: WARNING
DESCRIPTION: S Could not upgrade the i_position attribute. Database error was: %s
CAUSE: Failed to upgrade i_position from DB_ShortInt to DB_LongInt.
ACTION: This warning in most cases is O.K. since most groups do not have more than 64K direct users. If you do have, you can move some direct users to become indirect users. That is, you can create some group hierarchy to work around the problem.
PARAMS:

nahoru

DM_CHARTRANS

ERROR: [DM_CHARTRANS_F_NO_TRANSLATOR]

SEVERITY: FATAL
DESCRIPTION: S Unable to instantiate any translators in directory (%s) $Id: dmcntain.e,v 5.2 2001/06/01 22:08:16 ghwang Exp $ dmContainment class errors
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_CHARTRANS_E_OS_TRANSLATION_TO_OS_CODEPAGE]

SEVERITY: ERROR
DESCRIPTION: SSS Error translating %s to OS codepage %s from codepage %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_CHARTRANS_E_PROC_LOAD_FAIL]

SEVERITY: ERROR
DESCRIPTION: SSS Error processing Library %s: unable to load procedure: %s due to: %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_CHARTRANS_E_SESSION_TRANSLATION]

SEVERITY: ERROR
DESCRIPTION: SS Error translating %s to session codepage %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_CHARTRANS_E_SCAN_ADVANCE]

SEVERITY: ERROR
DESCRIPTION: SS Error during scan of directory (%s). Operating System Error: (%s)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_CHARTRANS_E_DATABASE_CONFIGURATION]

SEVERITY: ERROR
DESCRIPTION: Unable to verify that database is compatible with UTF-8 codepage.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_CHARTRANS_E_VERITY_NO_TRANSLATOR]

SEVERITY: ERROR
DESCRIPTION: S Unable to find character translator for Verity codepage %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_CHARTRANS_E_MEMORY_EXHAUSTED]

SEVERITY: ERROR
DESCRIPTION: I Memory exhausted allocating %d bytes
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_CHARTRANS_E_CLIENT_TRANSLATION_TO_CLIENT_CODEPAGE]

SEVERITY: ERROR
DESCRIPTION: SSS Error in DMCL translating %s from server codepage %s to client codepage %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_CHARTRANS_E_OS_TRANSLATION_FROM_OS_CODEPAGE]

SEVERITY: ERROR
DESCRIPTION: SSS Error translating %s from OS codepage %s to codepage %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_CHARTRANS_E_SERVER_PLATFORM_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: SSS Library, %s, does not provide translation for server host platform. Server platform :(%s), Library translation server platform: (%s).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_CHARTRANS_E_INVALID_DIRECTORY]

SEVERITY: ERROR
DESCRIPTION: SSS Unable to validate existence of directory for (%s)=(%s). Operating System Error: (%s)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_CHARTRANS_E_SERVER_TRANSLATION]

SEVERITY: ERROR
DESCRIPTION: SSS %s function: %s value: %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_CHARTRANS_E_SERVER_TRANSLATION_TO_SERVER_CODEPAGE]

SEVERITY: ERROR
DESCRIPTION: SSS Error in server translating %s from client codepage %s to server codepage %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_CHARTRANS_E_SERVER_LOCALE]

SEVERITY: ERROR
DESCRIPTION: S Error processing Library %s: unable to create locale object
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_CHARTRANS_E_CLIENT_TRANSLATION_FROM_CLIENT_CODEPAGE]

SEVERITY: ERROR
DESCRIPTION: SSS Error in DMCL translating %s from client codepage %s to server codepage %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_CHARTRANS_E_NO_OS_TRANSLATOR]

SEVERITY: ERROR
DESCRIPTION: S Unable to create character translator for Operating System codepage %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_CHARTRANS_E_SHARED_LIB_OPEN]

SEVERITY: ERROR
DESCRIPTION: SS Unable to open character translator shared library: (%s). Operating System Error: (%s)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_CHARTRANS_E_SCAN_OPEN]

SEVERITY: ERROR
DESCRIPTION: SS Error opening directory scan for directory: (%s), %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_CHARTRANS_E_VERITY_TRANSLATION]

SEVERITY: ERROR
DESCRIPTION: S Error translating %s to Verity codepage.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_CHARTRANS_E_SERVER_TRANSLATION_FROM_SERVER_CODEPAGE]

SEVERITY: ERROR
DESCRIPTION: SSS Error in server translating %s from server codepage %s to client codepage %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_CHARTRANS_W_SERVER_CODEPAGE]

SEVERITY: WARNING
DESCRIPTION: S The server is NOT certified with an internal codepage of %s, only UTF-8! Using the server with this codepage setting is likely to lead to corruption of data!
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_CHARTRANS_W_TRANSLATOR_SKIPPED]

SEVERITY: WARNING
DESCRIPTION: SS Translator in directory (%s) was skipped because it failed initialization. Translator specifics: (%s)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_CHARTRANS_W_CHANGE_PASSWORD_TRANSLATION]

SEVERITY: WARNING
DESCRIPTION: User password was successfully changed but an internal error occurred in returning the user credentials.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_CHARTRANS_W_NLS_LOCACTION_ACCESS]

SEVERITY: WARNING
DESCRIPTION: SSS The location specified by your server configuration for the NLS directory is (%s) specifies a directory (%s) which cannot be accessesed. Operating system error was (%s).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_CHARTRANS_I_TRANSLATOR_OPENED]

SEVERITY: INFORMATION
DESCRIPTION: SS Translator in directory (%s) was added succesfully initialized. Translator specifics: (%s)
CAUSE:
ACTION:
PARAMS:

nahoru

DM_IDITR

ERROR: [DM_IDITR_F_SQL_ITER_UPDATE_FAILED]

SEVERITY: FATAL
DESCRIPTION: S Update failed during large database update database error message was %s.
CAUSE: A database failure.
ACTION: Check system logs for other messages. Retry. $Id: dminbox.e,v 5.4 2002/06/01 02:51:45 xtang Exp $ dmInbox class errors
PARAMS:

ERROR: [DM_IDITR_F_SQL_ITER_FETCH_FAILED]

SEVERITY: FATAL
DESCRIPTION: S Fetch failed during large database update database error message was %s.
CAUSE: A database failure.
ACTION: Check system logs for other messages. Retry.
PARAMS:

ERROR: [DM_IDITR_F_SQL_ITER_ACCESS_FAILED]

SEVERITY: FATAL
DESCRIPTION: S Cursor access failed during large database update database error message was %s.
CAUSE: A database failure.
ACTION: Check system logs for other messages. Retry.
PARAMS:

ERROR: [DM_IDITR_E_CURSOR]

SEVERITY: ERROR
DESCRIPTION: SS The cursor %s fails. The error message from the database server is: %s.
CAUSE: An internal cursor failure occurrs.
ACTION: Re-try the operation. If the problem persists, please see your local system administrative.
PARAMS: S – the query S – the database error message

ERROR: [DM_IDITR_T_SQL_ITER_PROGRESS]

SEVERITY: TRACE
DESCRIPTION: I Large database update %d percent done.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_IDITR_T_SQL_ITER_DONE]

SEVERITY: TRACE
DESCRIPTION: Large database update complete.
CAUSE:
ACTION:
PARAMS:

nahoru

DM_INBOX

ERROR: [DM_INBOX_F_PINIT9]

SEVERITY: FATAL
DESCRIPTION: SS Error renaming the table %s to %s
CAUSE: DB Error.
ACTION: check the RDBMS. Information Facility errors
PARAMS:

ERROR: [DM_INBOX_F_PINIT6]

SEVERITY: FATAL
DESCRIPTION: Could not access the registry data
CAUSE: DB Error
ACTION: Check the RDBMS
PARAMS:

ERROR: [DM_INBOX_F_INIT3]

SEVERITY: FATAL
DESCRIPTION: The type manager returned an error storing the dmi_queue_item type.
CAUSE: Unknown.
ACTION: Look at the error logged by the type manager. Report this message and any parameters to your Documentum Site representative.
PARAMS:

ERROR: [DM_INBOX_F_INIT6]

SEVERITY: FATAL
DESCRIPTION: I The dmi_queue_item type could not be converted %d.
CAUSE: Failure to convert dmi_queue_item cookie generator.
ACTION: Report this message to your Documentum Site representative.
PARAMS:

ERROR: [DM_INBOX_F_INIT2]

SEVERITY: FATAL
DESCRIPTION: II Version stamp %d was expected to be %d.
CAUSE: The version stamp that the dmi_queue_item object software expected was different than the actual version stamp in the database.
ACTION: You must upgrade your DocuServer database to conform to the software that you are running. If your software and data are consistent, then report this error, and other recent errors on your session, to your Documentum Site Representative.
PARAMS:

ERROR: [DM_INBOX_F_INT1]

SEVERITY: FATAL
DESCRIPTION: S The following database query %s could not be executed.
CAUSE: Inconsistency between the server and the sysobject type.
ACTION: Look at the error logged by the database. Report this message and any parameters to your Documentum Site Representative.
PARAMS:

ERROR: [DM_INBOX_F_INIT8]

SEVERITY: FATAL
DESCRIPTION: L The dmi_queue_item type could not be converted to version %d. The type initialization steps for the dmi_queue_item type failed because the type could not be upgraded to the current server version.
CAUSE: It is likely that a type/table alter command failed.
ACTION: Check for other related errors in the server log. Also check the RDBMS error logs for database errors. Report this message to your Documentum Site representative.
PARAMS: %1d – The version the server was attempting to upgrade to.

ERROR: [DM_INBOX_F_PINIT5]

SEVERITY: FATAL
DESCRIPTION: Could not create the new registry type
CAUSE: Unknown.
ACTION: Look at the error logged by the type manager. Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_INBOX_F_INIT7]

SEVERITY: FATAL
DESCRIPTION: The dmi_queue_item type could not be altered.
CAUSE: Failure to alter dmi_queue_item type.
ACTION: Report this message to your Documentum Site representative.
PARAMS:

ERROR: [DM_INBOX_F_INIT1]

SEVERITY: FATAL
DESCRIPTION: The dmi_queue_item type was found in the database without a version stamp.
CAUSE: Unknown.
ACTION: Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_INBOX_F_INIT4]

SEVERITY: FATAL
DESCRIPTION: S Unable to validate or create the event log location as specified using directory (%s). This error message is obsolete (see TroyO)
CAUSE: Failed to create the event log directory, during the initialization.
ACTION: Examine the docbase directory structure and look for possible security access problems.
PARAMS:

ERROR: [DM_INBOX_F_PINIT4]

SEVERITY: FATAL
DESCRIPTION: Could not remove the registry type
CAUSE: Unknown.
ACTION: Look at the error logged by the type manager. Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_INBOX_F_PINIT7]

SEVERITY: FATAL
DESCRIPTION: Could not save the new registry entry
CAUSE: Unknown.
ACTION: check the RDBMS.
PARAMS:

ERROR: [DM_INBOX_F_PINIT8]

SEVERITY: FATAL
DESCRIPTION: Error creating the temporary registry table
CAUSE: DB Error.
ACTION: check the RDBMS.
PARAMS:

ERROR: [DM_INBOX_F_INIT5]

SEVERITY: FATAL
DESCRIPTION: SS Failure to create view %s: database error was: %s
CAUSE: Failure to create a database view for queues
ACTION: Report this message to your Documentum Site representative
PARAMS:

ERROR: [DM_INBOX_E_CANT_GETEVENTS1]

SEVERITY: ERROR
DESCRIPTION: S GetEvents failed because of the following: %s.
CAUSE: GetEvents failed because of the specified database failure.
ACTION: Correct the database operation or talk to your System Administrator.
PARAMS:

ERROR: [DM_INBOX_E_ONLY_SYSADMIN_SU]

SEVERITY: ERROR
DESCRIPTION: SS Only a sysadmin or super user can perform %s operation on %s inbox item.
CAUSE: An non-privileged user tried to destroy any inbox item or save another user inbox item.
ACTION: None.
PARAMS:

ERROR: [DM_INBOX_E_QUERY_EXECUTION_FAILURE]

SEVERITY: ERROR
DESCRIPTION: SS The dmi_queue_item object upgrade encountered an error while trying to execute the following query: %s. Database error was %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_INBOX_E_INIT4]

SEVERITY: ERROR
DESCRIPTION: SS Unable to validate or create the event log location as specified using directory (%s). Operating System Error: (%s)
CAUSE: Failed to create the event log directory, during the initialization.
ACTION: Examine the docbase directory structure and look for possible security access problems.
PARAMS:

ERROR: [DM_INBOX_E_NOEVENTS]

SEVERITY: ERROR
DESCRIPTION: An error was encountered initializing the server shared Events area which prevents registering inbox events to any session clients.
CAUSE: An attempt was made to use the events area (presumably to post an event to a client), but the server was unable to initialize the events subsystem. Previous error messages should indicate the specific reason for the failure.
ACTION: Have the sysadmin resolve the events problem and restart the server.
PARAMS:

ERROR: [DM_INBOX_E_CANT_GETINBOX]

SEVERITY: ERROR
DESCRIPTION: S GET_INBOX failed because of the following: %s.
CAUSE: GET_INBOX failed because of the specified database failure.
ACTION: Correct the database operation or talk to your System Administrator.
PARAMS:

ERROR: [DM_INBOX_E_EVENT_FILE_CREATE]

SEVERITY: ERROR
DESCRIPTION: SS Error creating the event notification file (%s) used to indicate to a session that an inbox event has occurred. Operating system error (%s).
CAUSE: The file used for event notification could not be created.
ACTION: Check for existence of the events location directory and for check permissions in it.
PARAMS:

ERROR: [DM_INBOX_E_CANT_FIND_OBJ]

SEVERITY: ERROR
DESCRIPTION: SS Could not find the object to queue the event %s for id %s
CAUSE: The object identified by the id could not be found for that event.
ACTION: Check the id to make sure that it is a valid sysobject.
PARAMS:

ERROR: [DM_INBOX_W_EVENT_LOC]

SEVERITY: WARNING
DESCRIPTION: SS Unable to validate or create the event log location as specified using directory (%s). Operating System Error: (%s)
CAUSE: Failed to create the event log directory, during the initialization.
ACTION: Examine the docbase directory structure and look for possible security access problems.
PARAMS:

ERROR: [DM_INBOX_W_NO_ROWS]

SEVERITY: WARNING
DESCRIPTION: No results were returned from the GetEvents statement.
CAUSE: Your GetEvents method has returned an empty result set.
ACTION: No action is required.
PARAMS:

ERROR: [DM_INBOX_W_EVENT_NOLOC]

SEVERITY: WARNING
DESCRIPTION: S The server events location is currently undefined. There is no location object for the events area (%s).
CAUSE: An attempt was made to use the events area (presumably to post an event to a client), but the server was unable to initialize the events subsystem due to there being no definition for the server events location. There should be a dm_location object in the docbase with an object_name which matches the value of the server config object events_location attribute. Until this location object is defined events cannot be used.
ACTION: Have the sysadmin define an events location.
PARAMS:

ERROR: [DM_INBOX_W_PINIT10]

SEVERITY: WARNING
DESCRIPTION: S Error dropping the table %s
CAUSE: DB Error.
ACTION: manually remove table
PARAMS:

nahoru

DM_INFO

ERROR: [DM_INFO_F_NODB]

SEVERITY: FATAL
DESCRIPTION: S Cannot find docbase %s.
CAUSE: The specified docbase was not found.
ACTION: Ensure that your dminfo.sys file is configured correctly. If it is, and your docbase is correctly defined in it, then report this error, along with a copy of the dminfo.sys file, to your Documentum site representative.
PARAMS: The docbase name or id.

ERROR: [DM_INFO_F_INTERNAL]

SEVERITY: FATAL
DESCRIPTION: SS An internal error occurred: %s %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_INFO_F_OWNERSHIP]

SEVERITY: FATAL
DESCRIPTION: SS Database password file %s should be owned by the dmdba user not %s.
CAUSE: The database file must be owned by whomever is doing the installation. This user should be dmdba.
ACTION: Ensure that the database file is owned by docuserv. Log in as docuserv to complete the installation.
PARAMS: The name of the database file.

ERROR: [DM_INFO_F_OPENERM]

SEVERITY: FATAL
DESCRIPTION: S Cannot open error message file %s. Terminating…
CAUSE: The error message files are mandatory for initial startup of the system. If one is missing or corrupted, the program will abort execution.
ACTION: Make sure that the environment variable DM_DIR is set to the correct directory and that the error message file are in a sub directory called error Internal errors
PARAMS:

ERROR: [DM_INFO_F_OPENDBFILE]

SEVERITY: FATAL
DESCRIPTION: S Cannot open database file %s.
CAUSE: The database file could not be opened.
ACTION: Ensure that the database file has its permissions set such that this user can access it. If it appears correct, report this problem to your Documentum site representative.
PARAMS: None.

ERROR: [DM_INFO_F_NODBUSER]

SEVERITY: FATAL
DESCRIPTION: Cannot find database user for your docbase.
CAUSE: The docbase definition in the system information file is incorrect.
ACTION: Ensure that the docbase definition is complete and correct. If it is okay, report this error to your Documentum site representative.
PARAMS: None.

ERROR: [DM_INFO_F_OPENINFO]

SEVERITY: FATAL
DESCRIPTION: S Cannot open system information file %s.
CAUSE: The system information file was not successfully opened.
ACTION: Ensure that the system information file exists, and is readable. If everything checks out, report this problem to your Documentum site representative.
PARAMS: The name of the system information file.

ERROR: [DM_INFO_F_DBFILE]

SEVERITY: FATAL
DESCRIPTION: S Could not find database file for database user %s.
CAUSE: The database file could not be found.
ACTION: Ensure that the database file exists, and is in the expected location. If it is, report this message to your Documentum site representative.
PARAMS: The user name corresponding to the database file.

ERROR: [DM_INFO_F_READABLE]

SEVERITY: FATAL
DESCRIPTION: S Database file %s is readable by others.
CAUSE: The password file is universally readable. It must be protected against access by others.
ACTION: Ensure that the password files are all protected against others (world) access.
PARAMS: The name of the database file.

ERROR: [DM_INFO_E_INVALID_PATH]

SEVERITY: ERROR
DESCRIPTION: SSS The path, %s (for %s), is not a valid pathname: Operating System Error: (%s).
CAUSE: A pathname specified in your dminfo.sys, or a docbase-specific info file is invalid.
ACTION: See your Documentum System Administrator about correcting the pathname in the information file.
PARAMS: The incorrect pathname, and the location (i.e, common) or info attribute (i.e, DM_FULLTEXT_DIR) that it corresponds to.

ERROR: [DM_INFO_E_PREV]

SEVERITY: ERROR
DESCRIPTION: A previous error has left this object invalid.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_INFO_E_NOPATH]

SEVERITY: ERROR
DESCRIPTION: S There is no pathname defined for location %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_INFO_E_NOT_SET]

SEVERITY: ERROR
DESCRIPTION: The operation failed.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_INFO_E_NOFMT]

SEVERITY: ERROR
DESCRIPTION: S Cannot find format %s.
CAUSE: The specified content format was not found.
ACTION: Ensure that your dminfo.sys file is configured correctly.
PARAMS:

ERROR: [DM_INFO_E_BADPATH]

SEVERITY: ERROR
DESCRIPTION: SS The path, %s (for %s), is not a valid pathname.
CAUSE: A pathname specified in your dminfo.sys, or a docbase-specific info file is invalid.
ACTION: See your Documentum System Administrator about correcting the pathname in the information file.
PARAMS: The incorrect pathname, and the location (i.e, common) or info attribute (i.e, DM_FULLTEXT_DIR) that it corresponds to.

ERROR: [DM_INFO_W_OWNED]

SEVERITY: WARNING
DESCRIPTION: SS Database password file %s should be owned by the dmdba user not %s.
CAUSE: The database file should be owned by whomever is doing the installation. This user should be dmdba.
ACTION: Ensure that the database file is owned by dmdba. Log in as docuserv to complete the installation.
PARAMS: The name of the database file.

ERROR: [DM_INFO_W_READIT]

SEVERITY: WARNING
DESCRIPTION: S Database file %s is readable by others.
CAUSE: The password file is universally readable. It should be protected against access by others.
ACTION: Ensure that the password files are all protected against others (world) access.
PARAMS: The name of the database file.

nahoru

DM_INTERNAL

ERROR: [DM_INTERNAL_E_INVALID_ERROR_NO]

SEVERITY: ERROR
DESCRIPTION: I Invalid Error no from error (%d)n $Id: dmload.e,v 5.9 2002/05/09 20:57:20 roger Exp $ dmLoad class errors
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_INTERNAL_E_INVALID_FACILITY]

SEVERITY: ERROR
DESCRIPTION: I Invalid Facility from error (%d)n
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_INTERNAL_W_ERROR_LIST_OVERFLOW]

SEVERITY: WARNING
DESCRIPTION: I Error list has overflowed: beyond %d messages. See server log for remaining messages.
CAUSE: This can happen when the error list has overflown during a batch process that a large list of errors are generated. When the error list is flushed, server side errors are recorded in the session log file, client side errors are dropped.
ACTION: None.
PARAMS:

Konec druhé části…

Michal Šika

One Response to Documentum 6.6 – chybové zprávy – část 2.

  1. Pingback: Documentum 6.6 – chybové zprávy – část 3. » IT notes © Michal Šika