IT blok - Michal Šika

kutilovo živobytí

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

Ve třetí části výčtu chybových hlášení systému Documentum verze 6.6 od EMC si ukážeme chyby DM_LOAD – DM_RELATION 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_LOAD DM_LOCALE DM_LOCATION
DM_METHOD DM_MIGRATE_LIGHT DM_MTPT
DM_NOTE DM_OBJECT DM_OBJ_MGR
DM_OUTPUTDEVICE DM_PLATFORM DM_POLICY
DM_QUERY DM_QUERY2 DM_RECOVERY
DM_RELATION

DM_LOAD

ERROR: [DM_LOAD_E_IGNORE_CHECK_ERROR]

SEVERITY: ERROR
DESCRIPTION: D Error checking if object %s should be loaded or skipped. This error message is given when an error occurs during a call to a dump-ignore procedure to determine if an object from the dumpfile should be loaded or skipped. The error likely caused the object to be not loaded.
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 being checked.

ERROR: [DM_LOAD_E_MISSING_PARAMETER]

SEVERITY: ERROR
DESCRIPTION: S The load_parameter (%s) is missing
CAUSE: A required load_parameter is missing
ACTION: set the load_parameter and resave the load record.
PARAMS: The name of the load parameter that is missing

ERROR: [DM_LOAD_E_TYPE_DEF_NOTFOUND]

SEVERITY: ERROR
DESCRIPTION: S Error during Load operation – definition for type %s not found in the loadfile type cache. During a load operation as objects are read from the loadfile type definitions are found and saved in a type cache in case an object of that type needs to be loaded. Since all objects are preceded in the dumpfile by their type definition there should always be one cached when such a typed object needs to be loaded.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOAD_E_OBJECT_SAVE_FAILED]

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

ERROR: [DM_LOAD_E_CHECKPOINT_ERROR]

SEVERITY: ERROR
DESCRIPTION: An error occurred attempting to commit the work completed so far during a load operation. Either the outstanding transaction could not be committed or a new transaction could not be started. During a load 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 indicating the load problem.
PARAMS:

ERROR: [DM_LOAD_E_PHASE2_INCOMPLETE2]

SEVERITY: ERROR
DESCRIPTION: I S S S S Error in Phase 2.An error occurred during processing of this object. Load Order No (%i), Old Id (%s), New Id (%s), old_exists (%s), update_done (%s). This error message is useful to extract more diagnostic information, which will help track problems during load phase
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOAD_E_FILE_SIZE_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: SS The actual file size %s does not match the size recorded %s .
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOAD_E_REVERT_ERROR]

SEVERITY: ERROR
DESCRIPTION: An error occurred during the rollback of a load operation. The loaded objects were not all successfully removed. Please remedy the indicated problem and restart the REVERT operation. When a load operation is performed to import data into a docbase, records are kept of all objects added in the load. Until the dm_load_record which was created for the load is destroyed, the load operation can be rolled back by issuing a Revert request. The revert removes each new object added by the load. This error is given when a Revert request encounters an error. Since the load has been partially reverted, this error will normally indicate that the docbase is inconsistent, having some but not all of the objects loaded into it. This error should always be handled by fixing the problem which led to the revert failure and retrying the revert.
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 revert. Do not destroy the dm_load_record as this will make it impossible to rollback the partially completed load.
PARAMS:

ERROR: [DM_LOAD_E_BAD_STREAM]

SEVERITY: ERROR
DESCRIPTION: An error occur during formating of information.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOAD_E_OBJECT_UPDATE_FAILED]

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

ERROR: [DM_LOAD_E_IDS_OUT_OF_RANGE]

SEVERITY: ERROR
DESCRIPTION: I Ids in dumpfile extend beyond docbase range for tag %i
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOAD_E_TYPE_CREATION_FAILED]

SEVERITY: ERROR
DESCRIPTION: S Could not create type %s in docbase
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOAD_E_OPEN_TRANSACTION]

SEVERITY: ERROR
DESCRIPTION: The Load operation cannot be executed while inside of a user transaction. A load 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 load has a currently outstanding transaction open.
ACTION: Complete the current transaction before starting the load.
PARAMS:

ERROR: [DM_LOAD_E_NOT_SUPERUSER]

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

ERROR: [DM_LOAD_E_PHASE2_INCOMPLETE]

SEVERITY: ERROR
DESCRIPTION: I Error in Phase 2. No rows returned from dmi_load_object_record indicating no work to do to complete the load, but the load object count (%i) indicates that there should have been. Check database temp table space. During the second phase of a load operation, the system updates each of the objects added during the load to link them properly into the new docbase. To facilitate this, a dmi_load_object_record entry is created for each object loaded during the first phase. This error occurs when no dmi_load_object_record entries are found in the second phase even though we know that there were objects loaded in the first phase. It usually indicates that a database error caused the dmi_load_object_record query to fail and return no rows. Most commonly, this error is caused by exhaustion of database temp space required to sort the rows in the query.
CAUSE: Usually caused by a database query error, most likely related to temporary or sort space.
ACTION: Check the server error log for other error messages indicating the cause of the error. Also check the database error log for relevant messages and check for low database resources. Consider increasing the space your database reserves for sort operations (temp space).
PARAMS:

ERROR: [DM_LOAD_E_NO_DMREF_OBJ]

SEVERITY: ERROR
DESCRIPTION: DS Object %s fetched during load operation indicates it is a %s but the server could find not corresponding dm_reference object. Internal error attempting to refresh an existing docbase object during a load operation. A docbase object has i_is_reference or i_is_replica set to True but apparently with no dm_reference object.
CAUSE: Docbase object may not be consistent.
ACTION: Check for other error messages which may give more detail. If the load is part of a replication task, try destroying the replica and retrying the operation.
PARAMS: %1 – The object id we were updating. %s – String indicating reference or replica.

ERROR: [DM_LOAD_E_FILE_IO]

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

ERROR: [DM_LOAD_E_RECORD_SAVE_FAILED]

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

ERROR: [DM_LOAD_E_INIT_LOAD]

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

ERROR: [DM_LOAD_E_OBJECT_DBID_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: S Error executing non-relocate Load operation. Cannot load object with id (%s) because it was dumped from a different docbase than the one being loaded. The docbase id in the object_id does not match. In order to use non-relocate load, the objects being loaded must have object ids that match the current docbase. Ideally it means that the objects were dumped from the same docbase and that no existing objects are going to overlap with IDs in the dumpfile. Technically it just means that the docbase being loaded must have the same docbase_id as the one which was dumped.
CAUSE: The dumpfile was created from a docbase with a different docbase id than the one on which the load is being attempted.
ACTION: Review load strategy to determine if this dumpfile can be loaded into the current docbase. If attempting to recreate an old docbase, be sure that the new one has the same docbase id as the old one.
PARAMS:

ERROR: [DM_LOAD_E_DESTROY_LOAD_RECORD]

SEVERITY: ERROR
DESCRIPTION: An error occurred during cleanup from a Load as part of a destroy request on the dm_load_record object. The load operation bookkeeping records (dmi_load_object_record) have not been fully cleaned up. During a load operation, the server creates bookkeeping records to keep track of what has been loaded (dmi_load_object_record types). When the load is complete, these records are cleaned up when the load record itself is destroyed. The error is given when some problem occurs during the destroy of the dm_load_record or the dmi_load_object_records associated with it. The original load operation which was done with the dm_load_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 load operation, the operation itself is committed. The load can no longer be backed out via a revert. If a revert is done on a load record following this error, then only part of the loaded 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_LOAD_E_CORRUPTION]

SEVERITY: ERROR
DESCRIPTION: S Unreasonable Object / Type size: %s (bytes). Possible corruption of dump file.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOAD_E_CANT_REPLICATE]

SEVERITY: ERROR
DESCRIPTION: L The load operation specifies a dumpfile that was created on a foreign docbase (docbase id %d). Use of the non-relocate flag with foreign dumpfiles should be used in the context of Replication operations only.
CAUSE: The user is attempting to non-relocate load a dumpfile from an outside source (a foreign docbase). This is used by replication and will create replica objects. To prevent accidental creation of replicas when the user really intends to do normal (relocate) load, this operation is disallowed unless the user has the replication package installed. The check for this uses the server_config agent_launcher field to determine if replication is in use.
ACTION: Use relocate-load for loading data into the docbase from an outside source. If creation of replica records is really intended, then check the server setup (server_config) to ensure that the agent_launcher field is properly defined.
PARAMS: The docbase id where the dumpfile was created.

ERROR: [DM_LOAD_E_RELOCATE_PREDICATE]

SEVERITY: ERROR
DESCRIPTION: Request error. The type and predicate fields which subset the load operation may only be used on a non-relocate load (the relocate field must be False). The type and predicate attributes of the dm_load_record modify the load operation so that only the objects which match the queries are loaded. Since the queries are run against the existing docbase the behavior only makes sense when a non-relocate load (in which the objects to update already exist in the docbase) is done.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOAD_E_CANT_CREATE_REF]

SEVERITY: ERROR
DESCRIPTION: S Failed to create a dm_reference object during load operation. The id of the object from the dump file is (%s). PARARMETERS: The id of the object from the dump file.
CAUSE: Unexpected error.
ACTION: Retry the load operation again.
PARAMS:

ERROR: [DM_LOAD_E_VERSION_TOO_OLD]

SEVERITY: ERROR
DESCRIPTION: SII Version stamp for type %s in dumpfile is too old — n is %i should be at least %i
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOAD_E_OLDER_VERSION]

SEVERITY: ERROR
DESCRIPTION: S Object with %s not updated — version in dumpfile older than version in docbase
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOAD_E_CANT_OPEN_FILE]

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

ERROR: [DM_LOAD_E_LOAD_RECORD_LOOKUP]

SEVERITY: ERROR
DESCRIPTION: D Error looking up dmi_load_object_record for id %s. Internal error attempting to find a dmi_load_object record for a particular object. The query to look in the dmi_load_object_record table failed.
CAUSE: Most likely caused by a resource error of some kind. Possibly due to rollback segment size.
ACTION: Review the error log for other errors indicating the exact problem. Attempt to continue the load operation by resaving the same load record.
PARAMS: %1 – The object id we were searching for information on.

ERROR: [DM_LOAD_E_STORE_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: S Could not find storage object with name %s in docbase. The docbase being loaded must have a synonym for each storage object referenced in the load file. During a load operation storage objects are not recreated. Each storage object listed in the loadfile must have a synonym in the docbase being loaded, otherwise objects from that storage object cannot be loaded.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOAD_W_FORCEPLAN_FAILED]

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

ERROR: [DM_LOAD_W_OBJECT_NOT_LOADED]

SEVERITY: WARNING
DESCRIPTION: D Object %s could not be loaded. The load operation is proceeding without loading it. The load operation skipped an object that could not be loaded.
CAUSE: Internal error or unexpected condition.
ACTION: Check the error log for further messages. Check for references in other loaded objects to this object. Those references may be left as dangling pointers.
PARAMS: %1 – handle for object from the dump file.

ERROR: [DM_LOAD_W_FOREIGN_ID]

SEVERITY: WARNING
DESCRIPTION: SS The load operation specifies a dumpfile that contains objects (%s) foreign to the source docbase (%s). The object will be ignored.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOAD_W_INCOMPLETE_LOAD]

SEVERITY: WARNING
DESCRIPTION: S Loading of object %s failed to finish properly — some attributes may be incorrect
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOAD_W_UNFORCEPLAN_FAILED]

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

ERROR: [DM_LOAD_W_UPDATE_STATISTICS]

SEVERITY: WARNING
DESCRIPTION: S Failed to update statistics. %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOAD_I_TYPE_MATCH]

SEVERITY: INFORMATION
DESCRIPTION: S Type %s matches definition in docbase. display when trace level = 8
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOAD_I_SKIP_OBJ]

SEVERITY: INFORMATION
DESCRIPTION: LL Object skipped — version in dumpfile (%ld) older than version in docbase (%ld). display when trace level = 8
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOAD_I_PHASE_2_COMPLETE]

SEVERITY: INFORMATION
DESCRIPTION: S Phase 2 of loading finished for load object %s display when trace level = 1
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOAD_I_PHASE_1_COMPLETE]

SEVERITY: INFORMATION
DESCRIPTION: S Phase 1 of loading finished for load object %s display when trace level = 1
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOAD_I_UNMAPPED_OBJ]

SEVERITY: INFORMATION
DESCRIPTION: DD Local object %s contains a foreign id pointer (%s). Object being refreshed from the dumpfile copy to ensure consistency. During a replication load operation, an object was encountered with an ID field containing a foreign id. We consider that this is most likely caused by an object which was only half-loaded in a previous load and we will reload it even if the version stamps indicate that the local object is up-to-date.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOAD_I_SKIP_LOCAL]

SEVERITY: INFORMATION
DESCRIPTION: D Object skipped — object in dumpfile is replica of a local object (%s). During a replication load operation, an object was encountered with a global_id matching the local docbase. This object is not applied locally as we do not want to overwrite a local master object with data from a replica.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOAD_I_PROGRESS]

SEVERITY: INFORMATION
DESCRIPTION: SIIIS For load object %s in phase %i, processed %i of %i objects last object processed was %s display when trace leve = 10
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOAD_I_BUILD_OBJ]

SEVERITY: INFORMATION
DESCRIPTION: LL Object being loaded — version in dumpfile (%ld) is current or later than version in docbase (%ld). display when trace level = 8
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOAD_I_LOAD_TYPE]

SEVERITY: INFORMATION
DESCRIPTION: S Loading type: %s display when trace level = 8
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOAD_I_TYPE_SKIP]

SEVERITY: INFORMATION
DESCRIPTION: S Type %s mismatches definition in docbase. Skipping type. During a load operation, a type with an identical name but different attribute types was found. The server will skip it. display when trace level = 8
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOAD_I_MERGE_1]

SEVERITY: INFORMATION
DESCRIPTION: LFF Number of objects merged=%ld, total time=%lf ms, avg time=%lf ms display when trace level = 5
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOAD_I_LOAD_OBJ]

SEVERITY: INFORMATION
DESCRIPTION: DD Loading object: %s, old object id: %s display when trace level = 8
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOAD_I_TYPE_CREATE]

SEVERITY: INFORMATION
DESCRIPTION: S Creating type %s. display when trace level = 8
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOAD_I_SYNONYM]

SEVERITY: INFORMATION
DESCRIPTION: S Synonym %s found. display when trace level = 8
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOAD_I_MERGE_2]

SEVERITY: INFORMATION
DESCRIPTION: S Merging object ID=%s display when trace level = 5
CAUSE:
ACTION:
PARAMS:

nahoru

DM_LOCALE

ERROR: [DM_LOCALE_F_UNEXPECTED_OS_FAILURE]

SEVERITY: FATAL
DESCRIPTION: SS An error was returned from the Operating System API (%s) and was unexpected. Operating System Error: (%s).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOCALE_E_SERVER_FAILURE]

SEVERITY: ERROR
DESCRIPTION: An failed status was returned by the server during processing of your client locale. Please check the server log for details.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOCALE_E_UNKNOWN_CODEPAGE_NAME]

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

ERROR: [DM_LOCALE_E_MEMORY_EXHAUSTED]

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

ERROR: [DM_LOCALE_E_UNKNOWN_LOCALE_NAME]

SEVERITY: ERROR
DESCRIPTION: S Unknown locale name %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOCALE_E_UNABLE_TO_MODIFY_OS_LOCAL]

SEVERITY: ERROR
DESCRIPTION: S Unable to modify the locale using the following API call: (%s).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOCALE_E_UNKNOWN_CHAR_SET]

SEVERITY: ERROR
DESCRIPTION: I Unknown character set, ordinal =%d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOCALE_W_DEFAULT_DATE_MAC]

SEVERITY: WARNING
DESCRIPTION: S Unable to get local date format from Macintosh environment. Reason code %s.
CAUSE: Your short date format is determined from the Macintosh Date/Time control panel. An error has been encountered. Your session will assume the default short date format: MM/DD/YYYY hh:mm:ss
ACTION: The reason code parameter indicates where the error was encountered. Check your Mac environment. PARAMETER: Reason code. 1 — The date order was incorrect in the internationalization resource. 2 — The specification for 24 hour clock was incorrect.
PARAMS:

ERROR: [DM_LOCALE_W_DEFAULT_DATE_WIN]

SEVERITY: WARNING
DESCRIPTION: S Unable to get local date format from Windows environment. Reason code %s.
CAUSE: Your short date format is determined from the Windows International control panel. An error has been encountered. Your session will assume the default short date format: MM/DD/YYYY hh:mm:ss
ACTION: The reason code parameter indicates where the error was encountered. Check your windows environment. PARAMETER: Reason code. 1 — The intl profile string could not be retrieved. 2 — An invalid iDate variable value was encountered. 3 — An invalid iTime variable value was encountered. 4 — The 24 or 12 hour clock indicator was invalid. 5 — The AM or PM string was invalid. 6 — The date separator was invalid. 7 — The time separator was invalid. 8 — The short date format string was too long. 9 — The short date format string was invalid. Value preceding the first date separator did not exist. 10 — The short date format string was invalid. Value following the first date separator did not exist. 11 — The short date format string was invalid. Value following the second date separator did not exist.
PARAMS:

ERROR: [DM_LOCALE_W_DEFAULT_DATE_SYSV]

SEVERITY: WARNING
DESCRIPTION: S Unable to get local date format from your Unix environment. Reason code %s.
CAUSE: Your short date format is determined from the international short date format of your Unix machine. An error has been encountered. Your session will assume the default short date format: MM/DD/YYYY hh:mm:ss
ACTION: The reason code parameter indicates where the error was encountered. Check your Unix environment. PARAMETER: Reason code. 1 — The short date format returned by strftime %x %X was unexpected. 2 — The date separator or time separator (or both) were more than one character long. 3 — The short date format could not be parsed.
PARAMS:

ERROR: [DM_LOCALE_W_ILLEGAL_DATE_FORMAT]

SEVERITY: WARNING
DESCRIPTION: S Illegal syntax found in the date format %s. The default localized short date format will be used.
CAUSE: You have provided an illegal date format in either a DATE or a datetostring function.
ACTION: The default short date format that was used is mm/dd/yy hh:mi:ss. If this is not acceptable correct your date format pattern and re-run the query. PARAMETER: The user-specified date format pattern.
PARAMS:

nahoru

DM_LOCATION

ERROR: [DM_LOCATION_F_COPY_DIRECTORY]

SEVERITY: FATAL
DESCRIPTION: Sorry, the save operator is not implemented at this time
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOCATION_F_INIT3]

SEVERITY: FATAL
DESCRIPTION: The dm_location object subsystem could not be initialized. A failure was detected attempting to store the dm_location type.
CAUSE: Possible database failure.
ACTION: Examine error log for other errors.
PARAMS:

ERROR: [DM_LOCATION_F_INIT1]

SEVERITY: FATAL
DESCRIPTION: The dm_location object subsystem failed initialization. The version stamp for the dm_location object exists, but the corresponding type could not be fetched.
CAUSE: Possible database corruption
ACTION: Consult documentation.
PARAMS:

ERROR: [DM_LOCATION_F_INIT2]

SEVERITY: FATAL
DESCRIPTION: LL The dm_location object subsystem could not be initialized. The version stamp for the dm_location type (%i) does not match the expected stamp (%i).
CAUSE: Possible database corruption. Perhaps an older server is being run against a newer docbase
ACTION: Consult documentation.
PARAMS:

ERROR: [DM_LOCATION_F_MOVE_DIRECTORY]

SEVERITY: FATAL
DESCRIPTION: Sorry, the save operator is not implemented at this time $Id: dmmethod.e,v 5.10 2003/05/02 00:36:26 roger Exp $ dmNote class errors
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOCATION_E_RESETPERM_MAXERR]

SEVERITY: ERROR
DESCRIPTION: SS Failed to reset permission on path %s of location %s
CAUSE: An internal error occurred while re-setting permission on the directory of the said location object.
ACTION: Consult your system administrator.
PARAMS:

ERROR: [DM_LOCATION_E_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Cant fetch, object identified by id (%s). Invalid id.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOCATION_E_NOT_A_LOCATION]

SEVERITY: ERROR
DESCRIPTION: S The object identified by (%s) is not a dm_location.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOCATION_E_CANT_DESTROY]

SEVERITY: ERROR
DESCRIPTION: Cannot destroy
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOCATION_E_FULL_PATH_REQUIRED]

SEVERITY: ERROR
DESCRIPTION: S The attribute, file_system_path, must be a full path name when the attribute mount_point_name is not specifie. file_system_path is currently: %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOCATION_E_NAMED_LOOKUP]

SEVERITY: ERROR
DESCRIPTION: S Unable to fetch the dmLocation named (%s) by name.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOCATION_E_CREATE_DIRECTORY]

SEVERITY: ERROR
DESCRIPTION: SSS Creation of file system directory for DM_LOCATION (%s) failed. Operating System failed to create directory (%s). Operating System error was (%s)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOCATION_E_MEMORY_EXHAUSTED]

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

ERROR: [DM_LOCATION_E_UNIQUE_CHECK]

SEVERITY: ERROR
DESCRIPTION: An error occurred attempting to validate the file_system_path attribute of a dm_location object.
CAUSE: An internal error occurred during the lookups to ensure that the file_system_path attribute of a dm_location object was valid during a save of that object.
ACTION: Consult your system administrator.
PARAMS:

ERROR: [DM_LOCATION_E_NON_UNIQUE_PATH]

SEVERITY: ERROR
DESCRIPTION: SS The attribute, file_system_path, must be unique among all existing dm_location objects. Path = (%s). Matching dm_location id = (%s).
CAUSE: Must have Superuser or SysAdmin privilege to save/destroy location objects.
ACTION: Consult your system administrator.
PARAMS:

ERROR: [DM_LOCATION_E_ATTRIBUTE_UNKNOWN]

SEVERITY: ERROR
DESCRIPTION: SSS Save of DM_LOCATION (%s) failed due to unrecognized value in attribute (%s). Value is (%s)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOCATION_E_NEED_PRIV_FOR_CHANGE]

SEVERITY: ERROR
DESCRIPTION: SS The current user (%s) needs to have superuser or sysadmin privilege to save or destroy %s location object.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOCATION_E_FILE_EXISTENCE]

SEVERITY: ERROR
DESCRIPTION: SSS File System file specified in DM_LOCATION (%s) does not exist. Operating System failed to validate existence of the file (%s). Operating System error was (%s)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOCATION_E_DESTROY]

SEVERITY: ERROR
DESCRIPTION: SSS Destroy with delete option of DM_LOCATION (%s) failed. Operating System failed to delete directory (%s). Operating System error was (%s)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOCATION_E_SAVE]

SEVERITY: ERROR
DESCRIPTION: S Save of DM_LOCATION (%s) failed.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOCATION_E_WALK_DIRECTORY]

SEVERITY: ERROR
DESCRIPTION: SS Failed to access directory %s, OS error: %s
CAUSE: An internal error occurred while walking through the said directory.
ACTION: Consult your system administrator.
PARAMS:

ERROR: [DM_LOCATION_E_VALIDATE]

SEVERITY: ERROR
DESCRIPTION: SSS Validation of DM_LOCATION (%s) failed. Operating System failed to validate directory (%s). Operating System error was (%s)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOCATION_E_DIRECTORY_EXISTENCE]

SEVERITY: ERROR
DESCRIPTION: SSS File System directory specified in DM_LOCATION (%s) is does not exist. Operating System failed to validate existence of the directory (%s). Operating System error was (%s)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOCATION_E_INVALID_MOUNT_POINT]

SEVERITY: ERROR
DESCRIPTION: SS Unable to get file system path for location (%s)n, because of failure accessing associatedndm_mount_point (%s).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOCATION_E_INVALID_DESTROY_OPTION]

SEVERITY: ERROR
DESCRIPTION: S The destroy option (%s) is not a valid option.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_LOCATION_E_SAVE_REQUIRES_ATTRIBUTE]

SEVERITY: ERROR
DESCRIPTION: S Cannot save object due to empty attribute (%s)
CAUSE:
ACTION:
PARAMS:

nahoru

DM_METHOD

ERROR: [DM_METHOD_F_INIT3]

SEVERITY: FATAL
DESCRIPTION: The type manager returned an error storing the dmMethod type.
CAUSE: Unknown.
ACTION: Look at the error logged by the type manager. Report this message and any parameters to your Documentum site representative. Migrate to Lightweight Facility errors ** Documentum Content Server ** Confidential Property of EMC Corporation ** (c) Copyright Documentum, Inc., 2007 – 2010 ** All rights reserved. **
PARAMS:

ERROR: [DM_METHOD_F_INIT1]

SEVERITY: FATAL
DESCRIPTION: The dmMethod 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_METHOD_F_INIT2]

SEVERITY: FATAL
DESCRIPTION: II Version stamp %d was expected to be %d.
CAUSE: The version stamp that the dmMethod 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_METHOD_E_HTTP_POST_APP_SERVER_NAME_NOTFOUND]

SEVERITY: ERROR
DESCRIPTION: The app_server_name was not specified.
CAUSE: The app_server_name cannot be null.
ACTION: Provide a valid app_server_name, which corresponds to an app_server_uri configured in the dm_server_config.
PARAMS:

ERROR: [DM_METHOD_E_CANT_FETCH_INVALID_ID]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch a dm_method – 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_METHOD_E_HTTP_POST_INSUFFICIENT_PRIVILEGES]

SEVERITY: ERROR
DESCRIPTION: S The user %s must have at least sysadmin privileges to execute HTTP_POST. Params %1 the user of the current session
CAUSE: User does not have at least sysadmin privileges, this is a requirement for HTTP_POST execution.
ACTION: Run HTTP_POST as a user that has at least sysadmin privileges.
PARAMS:

ERROR: [DM_METHOD_E_HTTP_POST_ILLEGAL_APP_SERVER_NAME]

SEVERITY: ERROR
DESCRIPTION: S The app_server_name %s is reserved for DO_METHOD.
CAUSE: The app_server_name specified is not allowed for HTTP_POST.
ACTION: Provide a different app_server_name, which corresponds to an app_server_uri configured in the dm_server_config.
PARAMS:

ERROR: [DM_METHOD_E_BAD_CONTENT]

SEVERITY: ERROR
DESCRIPTION: S Your method name (%s) content could not be fetched.
CAUSE: The specified method content could not be fetched during launch.
ACTION: Examine other messages to determine cause.
PARAMS:

ERROR: [DM_METHOD_E_NEED_PRIV_TO_RUN]

SEVERITY: ERROR
DESCRIPTION: SS The current user (%s) does not have enough privilege to run %s dm_method object.
CAUSE: Must have EXECUTE_PROC privilege to run dm_method objects.
ACTION: Consult your system administrator.
PARAMS:

ERROR: [DM_METHOD_E_CANT_SAVE]

SEVERITY: ERROR
DESCRIPTION: S Cannot save %s dm_method object.
CAUSE: One or more operations has failed during this save. Consult the following error message(s) for more help.
ACTION: Try again after fixing previous problems.
PARAMS:

ERROR: [DM_METHOD_E_HTTP_POST_INVALID_SAVE_RESPONSE]

SEVERITY: ERROR
DESCRIPTION: I The save_response field must be 0, 1, or -1 instead of: %d.
CAUSE: The value specified for save_response is not valid.
ACTION: Specify one of the following for save_response: 0 never save response of post 1 always save response from post -1 save response only on error
PARAMS:

ERROR: [DM_METHOD_E_NO_CONTENT]

SEVERITY: ERROR
DESCRIPTION: S Your method name (%s) has no content to launch.
CAUSE: The method specified has not content to be used during launch.
ACTION: specify a content that will point to a user defined script.
PARAMS:

ERROR: [DM_METHOD_E_SEND_PARAM]

SEVERITY: ERROR
DESCRIPTION: Error message not implemented
CAUSE: Obsolete error
ACTION: Obsolete error
PARAMS:

ERROR: [DM_METHOD_E_VERB_NOT_DEFINED]

SEVERITY: ERROR
DESCRIPTION: S The dm_method named (%s) does not have a verb defined
CAUSE: You cannot save a method that does not have a verb
ACTION: Define a verb
PARAMS:

ERROR: [DM_METHOD_E_INVALID_TIMEOUTP]

SEVERITY: ERROR
DESCRIPTION: SLS The %s value is = %d, must be a positive number for %s dm_method object.
CAUSE: the specified time out field must be a positive number.
ACTION: Respecify the number.
PARAMS:

ERROR: [DM_METHOD_E_BAD_CONTENT1]

SEVERITY: ERROR
DESCRIPTION: S Your method name (%s) content could not be fetched.
CAUSE: The specified method content could not be fetched during launch.
ACTION: Examine other messages to determine cause.
PARAMS:

ERROR: [DM_METHOD_E_ASSUME_USER_UV]

SEVERITY: ERROR
DESCRIPTION: SLS Your method named (%s) failed to execute because the assume user process could not validation your user credentials. Assume User Process returned (%d=%s).
CAUSE: The method specified run_as_server==False, this means the assume user process should be used to launch the method. The assume user process returned an unexpected error
ACTION:
PARAMS:

ERROR: [DM_METHOD_E_CACHECONFIG_CHECK]

SEVERITY: ERROR
DESCRIPTION: SD The CHECK_CACHE_CONFIG call for the config object %s (%s) failed. Params %1 the name of the cache config object being used (if requested by name) %2 the object id of the cache config object
CAUSE: This error is given for all failures in the CHECK_CACHE_CONFIG apply call. It should be preceeded by another error message giving further details. CHECK_CACHE_CONFIG calls are made automatically when accessing objects or queries in an application while using the client_persisent_cache features of the Documentum client.
ACTION: Check preceeding error message for more detail. The error can be bypassed by disabling the client_persistent_cache feature through the dmcl.ini.
PARAMS:

ERROR: [DM_METHOD_E_CACHECONFIG_NOMATCH]

SEVERITY: ERROR
DESCRIPTION: S No dm_cache_config object exists with the name %s. Params %1 the name of the cache config object being used
CAUSE: The CHECK_CACHE_CONFIG apply call was made and specified a config object that did not exist. CHECK_CACHE_CONFIG calls are made automatically when accessing objects or queries in an application while using the client_persisent_cache features of the Documentum client.
ACTION: Check the name or id of the config object being requested.
PARAMS:

ERROR: [DM_METHOD_E_NEED_VERB]

SEVERITY: ERROR
DESCRIPTION: S The verb for %s dm_method object must be specified.
CAUSE: User did not specify a method verb.
ACTION: Specify a method verb.
PARAMS:

ERROR: [DM_METHOD_E_RUN_AS_SERVER]

SEVERITY: ERROR
DESCRIPTION: The dm_method must have RUN_AS_SERVER set to TRUE.
CAUSE: The dm_method did not have RUN_AS_SERVER set to TRUE.
ACTION: Specify RUN_AS_SERVER in the dm_method object, or override it in the arguments to DO_METHOD with a user session that has at least system administrator privileges.
PARAMS:

ERROR: [DM_METHOD_E_MISSING_ARG]

SEVERITY: ERROR
DESCRIPTION: SS The method %s is missing argument for %s.
CAUSE: Argument is missing for the method.
ACTION: Make sure that all required arguments are correctly specified.
PARAMS: S – name of the method. S – name of the missing argument.

ERROR: [DM_METHOD_E_NO_JMS_AVAILABLE2]

SEVERITY: ERROR
DESCRIPTION: No Java Method Server available to serve the request.
CAUSE: All Java Method Servers configured for this content server might be down.
ACTION: None.
PARAMS:

ERROR: [DM_METHOD_E_CHECK_SECURITY_INVALID_ARGUMENT]

SEVERITY: ERROR
DESCRIPTION: S Invalid value for argument: %s.
CAUSE: The value given for the specified argument is not valid.
ACTION: Check the value given for the arugment.
PARAMS:

ERROR: [DM_METHOD_E_INCOMPAT_OPTIONS_1]

SEVERITY: ERROR
DESCRIPTION: The dm_method apply option RUN_AS_SERVER = F is only allowed if LAUNCH_DIRECT equals F.
CAUSE: The command line options and/or the dm_method attributes are in conflict
ACTION: Change the dm_method arguments and/or dm_method attributes to not conflict
PARAMS:

ERROR: [DM_METHOD_E_CACHECONFIG_MTHD]

SEVERITY: ERROR
DESCRIPTION: S Failure to execute the server method %s. Params %1 the name of the server method
CAUSE: The CHECK_CACHE_CONFIG call failed due to an error invoking the server method to check the cache state.
ACTION: Check the server log file for any messages logged by the server method. The problem can be further debugged by running the method directly (as a superuser), including the -method_trace_level flag and the SAVE_RESULTS option to gather more information.
PARAMS:

ERROR: [DM_METHOD_E_CHECK_SECURITY_ILLEGAL_USER]

SEVERITY: ERROR
DESCRIPTION: S The session user does not have super user privileges: %s.
CAUSE: The apply method check_security can only be run by a super user.
ACTION: Run this method in a super user session.
PARAMS:

ERROR: [DM_METHOD_E_WEBCACHE_ILLEGAL]

SEVERITY: ERROR
DESCRIPTION: S Invalid argument to webcache publish method: %s.
CAUSE: The specified argument is not allowed.
ACTION: The publish cannot be executed as requested.
PARAMS:

ERROR: [DM_METHOD_E_ASSUME_USER_OS]

SEVERITY: ERROR
DESCRIPTION: S Your method named (%s) could not be executed because the assume user feature is not supported in the current OS platform.
CAUSE: The assume user feature is not supported on some OS platforms.
ACTION:
PARAMS:

ERROR: [DM_METHOD_E_ASSUME_USER_UE]

SEVERITY: ERROR
DESCRIPTION: SLS Your method named (%s) failed to execute because the assume user process was unable to satisfy the request. Assume User Process returned (%d=%s).
CAUSE: The method specified run_as_server==False, this means the assume user process should be used to launch the method. The assume user process returned an unexpected error
ACTION:
PARAMS:

ERROR: [DM_METHOD_E_ASSUME_USER_FAIL]

SEVERITY: ERROR
DESCRIPTION: I Your method failed to run due to an error during communication with the assume_user process. Error: (%d).
CAUSE: Check the meaning of the Error in /usr/include/sys/errno.h
ACTION: Proceed according to error.
PARAMS:

ERROR: [DM_METHOD_E_CACHECONFIG_OWNER]

SEVERITY: ERROR
DESCRIPTION: SS Cache config object %s is owned by a non-superuser: %s. Config objects must be owned by a valid superuser. Params %1 the config object being refreshed %2 the owner of the cache config object
CAUSE: The CHECK_CACHE_CONFIG call failed because the config object was not owned by a superuser.
ACTION: Create the desired config object as a superuser-owned object
PARAMS:

ERROR: [DM_METHOD_E_WEBCACHE_CNF_OWNER]

SEVERITY: ERROR
DESCRIPTION: The webcache publish method must specify a superuser-owned dm_webc_config object.
CAUSE: Because the webcache publish operation runs with privileges, its use must be tightly controlled. The webcache publish method can only be run on a dm_webc_config object that was created by a super-user.
ACTION: The publish cannot be executed as requested.
PARAMS:

ERROR: [DM_METHOD_E_ACTION]

SEVERITY: ERROR
DESCRIPTION: Re-execute the method with run_as_server set to True. Or upgrade your OS to a supported version.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_METHOD_E_NO_FOLDER]

SEVERITY: ERROR
DESCRIPTION: SS Unable to find the default folder named (%s) to store your resulting document. This error occurred while processing the dm_method named (%s).
CAUSE: The default folder could not be found
ACTION: Define, create, the named folder
PARAMS:

ERROR: [DM_METHOD_E_HTTP_POST_FAILED]

SEVERITY: ERROR
DESCRIPTION: SS Failed to send HTTP Post to app_server_uri:%s Error:%s
CAUSE: Failed to send post. ACTION:Enable tracing for more information and check the Application Server.
ACTION:
PARAMS:

ERROR: [DM_METHOD_E_ASSUME_USER_FILE]

SEVERITY: ERROR
DESCRIPTION: SSS Unable to verify existence of program file for assume_user during processing of the dm_method named (%s). Program file : (%s). Operating System Error : (%s).
CAUSE: Check the Operating System Error.
ACTION: Dependent on the Operating System Error.
PARAMS:

ERROR: [DM_METHOD_E_WEBCACHE_NOTFOUND]

SEVERITY: ERROR
DESCRIPTION: S The requested dm_webc_config object (%s) does not exist or is not accessible by the current user.
CAUSE: The specified webcache config was not accessible by the current user.
ACTION: The publish cannot be executed as requested.
PARAMS:

ERROR: [DM_METHOD_E_UNKNOWN_METHOD]

SEVERITY: ERROR
DESCRIPTION: S The dm_method named (%s) is not defined. Please check the name of the method.
CAUSE: A method was invoked by name – the named method does not exist
ACTION: Define the method
PARAMS:

ERROR: [DM_METHOD_E_WEBCACHE_UNKNOWN]

SEVERITY: ERROR
DESCRIPTION: The requested webcache publish returned an unknown status.
CAUSE: The operation returned an unrecognized return-value and the server was unable to determine if it succeeded or failed.
ACTION: Check the publish operation log to determine the publish status.
PARAMS:

ERROR: [DM_METHOD_E_ASSUME_USER_SE]

SEVERITY: ERROR
DESCRIPTION: SLS Your method named (%s) failed to execute because the assume user process encountered an error processing the method. Assume User Process returned (%d=%s).
CAUSE: The method specified run_as_server==False, this means the assume user process should be used to launch the method. The assume user process returned an unexpected error
ACTION:
PARAMS:

ERROR: [DM_METHOD_E_ASSUME_USER_LE]

SEVERITY: ERROR
DESCRIPTION: S Your method named (%s) failed to execute because the assume user process was unable to launch.
CAUSE: The method specified run_as_server==False, this means the assume user process should be used to launch the method. The assume user process was unable to launch.
ACTION:
PARAMS:

ERROR: [DM_METHOD_E_CACHECONFIG_PRIV]

SEVERITY: ERROR
DESCRIPTION: SS The user %s does not have privilege to force a recheck of the cache config object %s. Execute privilege is required for this operation. Params %1 the user requesting the call %2 the name of the cache config object being used
CAUSE: The caller has made a CHECK_CACHE_CONFIG call and has specified the FORCE_CHECK option but does not have sufficient privilege. This call requires that the user have execute privilege on the config object, be the owner of the object, or be a superuser.
ACTION: Remove the FORCE_CHECK flag from the call. If a force must be done, contact the owner of the object to make the call or to grant privilege.
PARAMS:

ERROR: [DM_METHOD_E_HTTP_POST_FILE_ACCESS]

SEVERITY: ERROR
DESCRIPTION: SS Unable to access file (%s) used to save response. Operating system error (%s).
CAUSE: Failed to access file created to save HTTP response. ACTION:Check that the session user can create and modify files.
ACTION:
PARAMS:

ERROR: [DM_METHOD_E_JMS_APP_SERVER_NAME_NOTFOUND]

SEVERITY: ERROR
DESCRIPTION: S The app_server_name/servlet_name %s is not specified in dm_server_config/dm_jms_config.
CAUSE: The app_server_name/servlet_name and corresponding app_server_uri/base_uri must be configured.
ACTION: Configure the default app_server_name/servlet_name and corresponding app_server_uri/servlet_uri in the dm_server_config/dm_jms_config.
PARAMS:

ERROR: [DM_METHOD_E_HTTP_POST_NO_FOLDER]

SEVERITY: ERROR
DESCRIPTION: S Unable to find the default folder named (%s) to store the HTTP response.
CAUSE: The default folder could not be found
ACTION: Define, create, the named folder
PARAMS:

ERROR: [DM_METHOD_E_APP_SERVER_NAME_NOTFOUND]

SEVERITY: ERROR
DESCRIPTION: S The app_server_name %s is not specified in dm_server_config.
CAUSE: The app_server_name and corresponding app_server_uri must be configured.
ACTION: Configure the default app_server_name and corresponding app_server_uri in the dm_server_config.
PARAMS:

ERROR: [DM_METHOD_E_HTTP_POST_APP_SERVER_NAME_INVALID]

SEVERITY: ERROR
DESCRIPTION: S The app_server_name %s was not specified in dm_server_config.
CAUSE: The app_server_name must correspond to an an attribute in the dm_server_config.
ACTION: Provide a valid app_server_name, which corresponds to an app_server_uri configured in the dm_server_config.
PARAMS:

ERROR: [DM_METHOD_E_TEMP_CREATE]

SEVERITY: ERROR
DESCRIPTION: S Failure attempting to create document to store save results during the processing of the dm_method (%s).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_METHOD_E_HTTP_POST_APP_SERVER_URI_INVALID]

SEVERITY: ERROR
DESCRIPTION: S The app_server_uri used was not a valid uri: %s.
CAUSE: The app_server_uri must be of the form http://:.
ACTION: Provide an app_server_name, which corresponds to a valid app_server_uri configured in the dm_server_config. The app_server_uri must be of the form http://:.
PARAMS:

ERROR: [DM_METHOD_E_FILE_ACCESS]

SEVERITY: ERROR
DESCRIPTION: SSS Unable to access file (%s) used to save results. Operating System Error: (%s). This occurred during the processing of the dm_method (%s).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_METHOD_E_NEED_PRIV_FOR_CHANGE]

SEVERITY: ERROR
DESCRIPTION: SS The current user (%s) needs to have superuser or sysadmin privilege to save or destroy %s dm_method object.
CAUSE: Must have Superuser or SysAdmin privilege to save/destroy dm_method objects.
ACTION: Consult your system administrator.
PARAMS:

ERROR: [DM_METHOD_E_CACHECONFIG_REFRESH]

SEVERITY: ERROR
DESCRIPTION: D Failure to refresh the cache config object %s. Params %1 the object id of the config object being refreshed
CAUSE: The CHECK_CACHE_CONFIG call failed due to an error refreshing the cache config object. On some calls to CHECK_CACHE_CONFIG the server will need to call its dm_CheckCacheConfig method to recalculate the state of the cache. Since this call may modify the config object, the object is refreshed following the method call. This error indicates that the refresh has failed. It should be preceeded by another error message giving further details.
ACTION: Check preceeding error message for more detail.
PARAMS:

ERROR: [DM_METHOD_E_INVALID_TIMEOUTR]

SEVERITY: ERROR
DESCRIPTION: SLSLS The %s = %d must be less than or equal to the %s = %d for %s dm_method object.
CAUSE: TimeoutMin <= TimeoutMax and TimeoutMin <= TimeoutDefault <= TimeoutMax. See the actual error for what fields are the wrong values.
ACTION: Respecify the number.
PARAMS:

ERROR: [DM_METHOD_E_HTTP_COMMUNICATION]

SEVERITY: ERROR
DESCRIPTION: S %s
CAUSE: An HTTP protocol or socket error occurred communicating with the Application Server. ACTION:Enable tracing for more information and check the Application Server.
ACTION:
PARAMS:

ERROR: [DM_METHOD_E_INVALID_MTHD_VERB]

SEVERITY: ERROR
DESCRIPTION: SS The dm_method named (%s) of type dmbasic has invalid method_verb (%s).
CAUSE: Method of type dmbasic must contain dmbasic in its method verb.
ACTION: Reset the method verb
PARAMS:

ERROR: [DM_METHOD_E_WEBCACHE_FAILED]

SEVERITY: ERROR
DESCRIPTION: The requested webcache publish operation was not successful.
CAUSE: The method either could not be properly invoked or failed during execution.
ACTION: Check the returned collection object to see if the method was or was not invoked. The method return value also gives further information. More information will be included in the webcache log or might be obtained by running the method with the SAVE_RESULTS flag asserted.
PARAMS:

ERROR: [DM_METHOD_E_HTTP_POST_TEMP_CREATE]

SEVERITY: ERROR
DESCRIPTION: Failure attempting to create document to store saved HTTP response.
CAUSE: Failed to create a temporary document to store HTTP response. ACTION:Ensure that there is enough free space, and that dm_document objects can be created.
ACTION:
PARAMS:

ERROR: [DM_METHOD_W_RETURNTO_START_DIR]

SEVERITY: WARNING
DESCRIPTION: SSS Prior to launch of method named (%s) the attempt to change directory to start-up directory (%s) failed. Operating System error: %s.
CAUSE: Could not change directory to the specified directory
ACTION: Ensure that the permissions and accesibility of the specified directory is correct for the server.
PARAMS:

ERROR: [DM_METHOD_W_ASSUME_USER_LOCATION]

SEVERITY: WARNING
DESCRIPTION: S The method named (%s) was executed on the servers behalf even though run_as_server was set to FALSE. The dm_server_config attribute assume_user_location has not been defined.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_METHOD_W_WEBCACHE_WARN]

SEVERITY: WARNING
DESCRIPTION: The webcache publish operation completed with warnings.
CAUSE: The method finished but logged warning messages.
ACTION: Check the webcache result log for more details.
PARAMS:

ERROR: [DM_METHOD_I_NO_JMS_AVAILABLE]

SEVERITY: INFORMATION
DESCRIPTION: No Java Method Server available to serve the request.
CAUSE: All Java Method Servers configured for this content server might be down.
ACTION: None.
PARAMS:

ERROR: [DM_METHOD_I_JMS_DISABLED]

SEVERITY: INFORMATION
DESCRIPTION: S Connect to the Java Method Server (%s) failed, therefore it is marked DEAD.
CAUSE: Connect to the Java Method Server resulted in a DM_METHOD_E_HTTP_POST_FAILED or DM_METHOD_E_HTTP_COMMUNICATION error. Therefore, the corresponding dm_jms_config object is marked DEAD.
ACTION: None.
PARAMS:

nahoru

DM_MIGRATE_LIGHT

ERROR: [DM_MIGRATE_LIGHT_E_WRONG_SHARED_PARENT_IN_RECOVERY_MODE]

SEVERITY: ERROR
DESCRIPTION: SS The type (%s) specified in SHARED_PARENT_TYPE is not the right shareable parent type of type (%s).
CAUSE: SHARED_PARENT_TYPE argument supplied in MIGRATE_TO_LITE rpc call is not a right shareable type for the type specified in SOURCE_TYPE. One of the following can be the cause of this error: 1. It is not a shareable type. 2. It is not a direct supertype of SOURCE_TYPE. 3. The user is neither the owner of the type nor has superuser privilege.
ACTION: Either supply a proper SHARED_PARENT_TYPE or make sure the session user has the proper privilege. PARAMETER: the name supplied in SHARED_PARENT_TYPE and the name supplied in SOURCE_TYPE.
PARAMS:

ERROR: [DM_MIGRATE_LIGHT_E_NOT_LIGHT]

SEVERITY: ERROR
DESCRIPTION: S Interim type %s is not lightweight.
CAUSE: Interim type for LIGHTWEIGHT_TYPE is not lightweight.
ACTION: Execute MIGRATE_TO_LITE with RECOVERY_MODE asserted PARAMETER: name of interim type
PARAMS:

ERROR: [DM_MIGRATE_LIGHT_E_INTERIM_TYPE_CANNOT_EXIST]

SEVERITY: ERROR
DESCRIPTION: S The interim type (%s) can not be an existent type before migration unless under recovery mode.
CAUSE: The interim type can not exist before the migration unless under recovery mode.
ACTION: Set the RECOVERY_MODE flag to true and try again. PARAMETER: The name of an interim type during the type conversion.
PARAMS:

ERROR: [DM_MIGRATE_LIGHT_E_BAD_DEFAULT_ID]

SEVERITY: ERROR
DESCRIPTION: D DEFAULT_PARENT_ID %s is invalid.
CAUSE: The DEFAULT_PARENT_ID is either not present in SHARED_PARENT_TYPE or is present in LIGHTWEIGHT_TYPE.
ACTION: DEFAULT_PARENT_ID must only be present in SHARED_PARENT_TYPE PARAMETER: The DEFAULT_PARENT_ID specified in rpc call
PARAMS:

ERROR: [DM_MIGRATE_LIGHT_E_SQL_CANCEL]

SEVERITY: ERROR
DESCRIPTION: Failed to generate SQL to cancel migration.
CAUSE:
ACTION: PARAMETER:
PARAMS:

ERROR: [DM_MIGRATE_LIGHT_E_TYPES_REQUIRED]

SEVERITY: ERROR
DESCRIPTION: the specified rpc requires SHARED_PARENT_TYPE and LIGHTWEIGHT_TYPE to be specified
CAUSE: One or both of SHARED_PARENT_TYPE and LIGHTWEIGHT_TYPE arugments are missing from the rpc call when both a required.
ACTION: specify both arguments in rpc call.
PARAMS:

ERROR: [DM_MIGRATE_LIGHT_E_REP_CHILD_ATTRS_WRONG_CNT]

SEVERITY: ERROR
DESCRIPTION: III Either the number of values in parameter REPLACE_ORIG_CHILD_ATTRS (%d) is different than that in REPLACE_WITH_CHILD_ATTRS (%d) or they exceed the limit (%d).
CAUSE: Either the number of values supplied in the parameter REPLACE_ORIG_CHILD_ATTRS is different than the number of values in REPLACE_WITH_CHILD_ATTRS or any one of them exceeds the maximum limit. These two parameters need to have the same amount of values (i.e., child attributes) so that the child attributes specified in REPLACE_ORIG_CHILD_ATTRS can be dropped and replaced with the corresponding ones specified in REPLACE_WITH_CHILD_ATTRS. Currently, we only allow the following child attributes to be swapped: . object_name . r_page_cnt . i_vstamp . i_folder_id
ACTION: Correct the above problem and submit the RPC again.
PARAMS: The number of values in the corresponding parameters REPLACE_ORIG_CHILD_ATTRS and REPLACE_WITH_CHILD_ATTRS. The last number is the maximum number of values allowed.

ERROR: [DM_MIGRATE_LIGHT_E_NOT_PARENT_TYPE]

SEVERITY: ERROR
DESCRIPTION: DS object %s is not of type %s
CAUSE: The given object id is not an instance of the given type.
ACTION: Supply PARENT_ID or DEFAULT_PARENT_ID object id values that are of the parent type.
PARAMS: The invalid parent id and the parent type.

ERROR: [DM_MIGRATE_LIGHT_E_LIGHTWEIGHT_REQUIRED]

SEVERITY: ERROR
DESCRIPTION: LIGHTWEIGHT_TYPE is required when SHARED_PARENT_TYPE is a sharable type.
CAUSE: LIGHTWEIGHT_TYPE argument not supplied when SHARED_PARENT_TYPE argument specifies a shareable type.
ACTION: Specify a value for the LIGHTWEIGHT_TYPE when making this call. PARAMETER: none.
PARAMS:

ERROR: [DM_MIGRATE_LIGHT_E_SQL_TRAILER]

SEVERITY: ERROR
DESCRIPTION: Failed to generate SQL trailer for migration.
CAUSE:
ACTION: PARAMETER:
PARAMS:

ERROR: [DM_MIGRATE_LIGHT_E_NO_INSTRINSIC]

SEVERITY: ERROR
DESCRIPTION: S SHARED_PARENT_TYPE %s cannot be an intrinsic type.
CAUSE: Type specified by SHARED_PARENT_TYPE is in intrinsic type.
ACTION: Specify a subtype of dm_sysobject as the value for SHARED_PARENT_TYPE. PARAMETER: name of type.
PARAMS:

ERROR: [DM_MIGRATE_LIGHT_E_NO_SYSOBJECT]

SEVERITY: ERROR
DESCRIPTION: S SOURCE_TYPE %s cannot be dm_sysobject.
CAUSE: Type specified by SOURCE_TYPE is dm_sysobject.
ACTION: Specify a subtype of dm_sysobject as the value for SOURCE_TYPE. PARAMETER: name of type.
PARAMS:

ERROR: [DM_MIGRATE_LIGHT_E_SHARED_PARENT_CANNOT_EXIST]

SEVERITY: ERROR
DESCRIPTION: S The type (%s) specified in SHARED_PARENT_TYPE can not be an existent type when splitting a type.
CAUSE: SHARED_PARENT_TYPE argument supplied in MIGRATE_TO_LITE rpc call is an existent type when splitting the type.
ACTION: Specify a non-existent type for the SHARED_PARENT_TYPE when making this call. PARAMETER: the name supplied in SHARED_PARENT_TYPE.
PARAMS:

ERROR: [DM_MIGRATE_LIGHT_E_CANNOT_FINALIZE]

SEVERITY: ERROR
DESCRIPTION: S Cannot Finalize type %s. Try EXECUTION_MODE of Run without Finalize or Split without Finalize first
CAUSE: Attempt to finalize a migration that has not been started.
ACTION: Run the RPC with EXECUTION_MODE set to Run without Finalize or Split without Finalize
PARAMS: the parent and child type names

ERROR: [DM_MIGRATE_LIGHT_E_SQL_FINALIZE]

SEVERITY: ERROR
DESCRIPTION: S Failed to generate the SQL to finalize the type %s.
CAUSE:
ACTION: PARAMETER:
PARAMS:

ERROR: [DM_MIGRATE_LIGHT_E_SQL_SHARED]

SEVERITY: ERROR
DESCRIPTION: S Failed to generate SQL to create interim shared parent type %s.
CAUSE:
ACTION: PARAMETER:
PARAMS:

ERROR: [DM_MIGRATE_LIGHT_E_NO_PARENT_ID]

SEVERITY: ERROR
DESCRIPTION: DS %s is not an object of type %s.
CAUSE: The object is not of the given type.
ACTION: PARENT_ID must only be present in SHARED_PARENT_TYPE PARAMETER: The PARENT_ID specified in rpc call and parent type name.
PARAMS:

ERROR: [DM_MIGRATE_LIGHT_E_BAD_PARENT_CHILD]

SEVERITY: ERROR
DESCRIPTION: DS object %s is materialized object of type %s.
CAUSE: The PARENT_ID refers to an object of LIGHTWEIGHT_TYPE.
ACTION: PARENT_ID must only be present in SHARED_PARENT_TYPE PARAMETER: The PARENT_ID specified in rpc call and lightweight type.
PARAMS:

ERROR: [DM_MIGRATE_LIGHT_E_BAD_PARENT_ID]

SEVERITY: ERROR
DESCRIPTION: DS object %s is already sharing type %s.
CAUSE: The PARENT_ID is already sharing another lightweight type.
ACTION: PARENT_ID must either be shared by this child lightweight type or not sharinny lightweight type. PARAMETER: The PARENT_ID specified in rpc call and the lightweight type name sharing it.
PARAMS:

ERROR: [DM_MIGRATE_LIGHT_E_REP_CHILD_ATTRS_WRONG_WITH_ATTR]

SEVERITY: ERROR
DESCRIPTION: SS The attribute %s specified in REPLACE_WITH_CHILD_ATTRS needs to be a direct attribute of type %s.
CAUSE: The specified attribute name in REPLACE_WITH_CHILD_ATTRS can only be a direct attribute of the child type.
ACTION: Correct the above problem and submit the RPC again.
PARAMS: The name of the specified attribute in parameter REPLACE_WITH_CHILD_ATTRS and the name of the child type.

ERROR: [DM_MIGRATE_LIGHT_E_SQL_EXEC]

SEVERITY: ERROR
DESCRIPTION: S Execution of the SQL failed with error: %s.
CAUSE: Database error
ACTION: PARAMETER: Database error message
PARAMS:

ERROR: [DM_MIGRATE_LIGHT_E_NOT_SYSOBJ]

SEVERITY: ERROR
DESCRIPTION: S SHARED_PARENT_TYPE %s is not a subtype of dm_sysobject.
CAUSE: Type specified by SHARED_PARENT_TYPE is not a subtype of dm_sysobject.
ACTION: Specify a subtype of dm_sysobject as the value for SHARED_PARENT_TYPE. PARAMETER: name of type.
PARAMS:

ERROR: [DM_MIGRATE_LIGHT_E_PARAMETER_REQUIRED_WHEN_SPLIT]

SEVERITY: ERROR
DESCRIPTION: S The parameter (%s) is a required parameter when the execution_mode is either Split and Finalize or Split without Finalize.
CAUSE: SOURCE_TYPE argument not supplied in MIGRATE_TO_LITE rpc call when splitting a type into a shareable type and its lightweight type.
ACTION: Specify a value for the SOURCE_TYPE when making this call. PARAMETER: none.
PARAMS:

ERROR: [DM_MIGRATE_LIGHT_E_SHAREABLE]

SEVERITY: ERROR
DESCRIPTION: S LIGHTWEIGHT_TYPE (%s) cannot be a shareable type.
CAUSE: The type specified in the LIGHTWEIGHT_TYPE is a shareable type.
ACTION: Specify a non-shareable type for value of LIGHTWEIGHT_TYPE. PARAMETER: name of type.
PARAMS:

ERROR: [DM_MIGRATE_LIGHT_E_SHARED_PARENT_REQUIRED]

SEVERITY: ERROR
DESCRIPTION: SHARED_PARENT_TYPE is a required parameter.
CAUSE: SHARED_PARENT_TYPE argument not supplied in MIGRATE_TO_LITE rpc call.
ACTION: Specify a value for the SHARED_PARENT_TYPE when making this call. PARAMETER: none.
PARAMS:

ERROR: [DM_MIGRATE_LIGHT_E_DQL_EXEC]

SEVERITY: ERROR
DESCRIPTION: S Execution of DQL to create %s failed.
CAUSE:
ACTION: PARAMETER:
PARAMS:

ERROR: [DM_MIGRATE_LIGHT_E_DIRECT_SUBTYPE]

SEVERITY: ERROR
DESCRIPTION: SS Type %s is not a direct subtype of %s.
CAUSE: LIGHTWEIGHT_TYPE must be a direct subtype of SHARED_PARENT_TYPE.
ACTION: Specify direct subtype of SHARED_PARENT_TYPE for LIGHTWEIGHT_TYPE.
PARAMS: names of types.

ERROR: [DM_MIGRATE_LIGHT_E_ILLEGAL_ATTRIBUTE]

SEVERITY: ERROR
DESCRIPTION: SS You have specified an invalid attribute name (%s) for type (%s).
CAUSE: The attribute name specified in the list is not an attribute of the specified type.
ACTION: Correct the name and retry the RPC. Use DESCRIBE to find out the valid attributes for the type[s] you are migrating.
PARAMS: The invalid attribute name and the migrated type name.

ERROR: [DM_MIGRATE_LIGHT_E_SQL_LIGHT]

SEVERITY: ERROR
DESCRIPTION: S Failed to generate SQL to create interim lightweight child type %s.
CAUSE:
ACTION: PARAMETER:
PARAMS:

ERROR: [DM_MIGRATE_LIGHT_E_CANCEL]

SEVERITY: ERROR
DESCRIPTION: S Execution of SQL to cancel migration failed with error: %s.
CAUSE: Database error
ACTION: PARAMETER: Database error message
PARAMS:

ERROR: [DM_MIGRATE_LIGHT_E_ALREADY_LIGHTWEIGHT]

SEVERITY: ERROR
DESCRIPTION: S Migration type (%s) is already a lightweight type.
CAUSE: The type specified in the LIGHTWEIGHT_TYPE is already a lightweight type.
ACTION: Specify a non-lightweight type for value of LIGHTWEIGHT_TYPE. PARAMETER: name of type.
PARAMS:

ERROR: [DM_MIGRATE_LIGHT_E_REP_CHILD_ATTRS_WRONG_ORIG_ATTR]

SEVERITY: ERROR
DESCRIPTION: S The attribute %s specified in REPLACE_ORIG_CHILD_ATTRS is not allowed.
CAUSE: The specified attribute name in REPLACE_ORIG_CHILD_ATTRS can only be one of the following: . object_name . r_page_cnt . i_vstamp
ACTION: Correct the above problem and submit the RPC again.
PARAMS: The name of the specified attribute in parameter REPLACE_ORIG_CHILD_ATTRS.

ERROR: [DM_MIGRATE_LIGHT_E_SQL_HEADER]

SEVERITY: ERROR
DESCRIPTION: Failed to generate SQL header for migration.
CAUSE:
ACTION: PARAMETER:
PARAMS:

ERROR: [DM_MIGRATE_LIGHT_W_ADD_FT_ATTR]

SEVERITY: WARNING
DESCRIPTION: s Could not add fulltext index support to type %s.
CAUSE: fulltext index support could not be added to the given type
ACTION:
PARAMS: The name of the lightweight type

nahoru

DM_MTPT

ERROR: [DM_MTPT_F_INIT3]

SEVERITY: FATAL
DESCRIPTION: The dm_mount_point object subsystem could not be initialized. A failure was detected attempting to store the dm_mount_point type.
CAUSE: Possible database failure.
ACTION: Examine error log for other errors. $Id: dmnote.e,v 5.0 1998/01/10 02:07:59 sol_ora Exp $ dmNote class errors
PARAMS:

ERROR: [DM_MTPT_F_INIT1]

SEVERITY: FATAL
DESCRIPTION: The dm_mount_point object subsystem failed initialization. The version stamp for the dm_mount_point object exists, but the corresponding type could not be fetched.
CAUSE: Possible database corruption
ACTION: Consult documentation.
PARAMS:

ERROR: [DM_MTPT_F_INIT2]

SEVERITY: FATAL
DESCRIPTION: LL The dm_mount_point object subsystem could not be initialized. The version stamp for the dm_mount_point type (%i) does not match the expected stamp (%i).
CAUSE: Possible database corruption. Perhaps an older server is being run against a newer docbase
ACTION: Consult documentation.
PARAMS:

ERROR: [DM_MTPT_E_NO_ALIAS_FOR_MAC]

SEVERITY: ERROR
DESCRIPTION: S The dm_mount_point object named (%s) does not have a alias for the Macintosh platform
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_MTPT_E_NOT_A_MOUNTPOINT]

SEVERITY: ERROR
DESCRIPTION: S The object identified by (%s) is not a dm_mount_point.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_MTPT_E_CANT_FETCH]

SEVERITY: ERROR
DESCRIPTION: D Cant fetch, object identified by id (%s). Invalid id.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_MTPT_E_CANT_DESTROY]

SEVERITY: ERROR
DESCRIPTION: Cannot destroy
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_MTPT_E_NO_ALIAS_FOR_WINDOWS]

SEVERITY: ERROR
DESCRIPTION: S The dm_mount_point object named (%s) does not have a alias for the Windows platform
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_MTPT_E_NAMED_LOOKUP]

SEVERITY: ERROR
DESCRIPTION: S Unable to fetch the dm_mount_point named (%s) by name.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_MTPT_E_CREATE_DIRECTORY]

SEVERITY: ERROR
DESCRIPTION: SSS Creation of file system directory for DM_MOUNT_POINT (%s) failed. Operating System failed to create directory (%s). Operating System error was (%s)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_MTPT_E_ATTRIBUTE_UNKNOWN]

SEVERITY: ERROR
DESCRIPTION: SSS Save of DM_MOUNT_POINT (%s) failed due to unrecognized value in attribute (%s). Value is (%s)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_MTPT_E_NEED_PRIV_FOR_CHANGE]

SEVERITY: ERROR
DESCRIPTION: SS The current user (%s) needs to have superuser or sysadmin privilege to save or destroy %s dm_mount_point object.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_MTPT_E_REFERENCES_EXIST]

SEVERITY: ERROR
DESCRIPTION: SI The dm_mount_point object named (%s) can not be destroyed because there are (%d) dm_location objects referencing it
CAUSE: Must have Superuser or SysAdmin privilege to save/destroy mount_point objects.
ACTION: Consult your system administrator.
PARAMS:

ERROR: [DM_MTPT_E_FILE_EXISTENCE]

SEVERITY: ERROR
DESCRIPTION: SSS File System file specified in DM_MOUNT_POINT (%s) is does not exist. Operating System failed to validate existence of the file (%s). Operating System error was (%s)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_MTPT_E_DESTROY]

SEVERITY: ERROR
DESCRIPTION: SSS Destroy with delete option of DM_MOUNT_POINT (%s) failed. Operating System failed to delete directory (%s). Operating System error was (%s)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_MTPT_E_SAVE]

SEVERITY: ERROR
DESCRIPTION: S Save of DM_MOUNT_POINT (%s) failed.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_MTPT_E_DIRECTORY_EXISTENCE]

SEVERITY: ERROR
DESCRIPTION: SSS File System directory specified in DM_MOUNT_POINT (%s) is does not exist. Operating System failed to validate existence of the directory (%s). Operating System error was (%s)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_MTPT_E_VALIDATE]

SEVERITY: ERROR
DESCRIPTION: SSS Validation of DM_MOUNT_POINT (%s) failed. Operating System failed to validate directory (%s). Operating System error was (%s)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_MTPT_E_INVALID_DESTROY_OPTION]

SEVERITY: ERROR
DESCRIPTION: S The destroy option (%s) is not a valid option.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_MTPT_E_SAVE_REQUIRES_ATTRIBUTE]

SEVERITY: ERROR
DESCRIPTION: S Cannot save object due to empty attribute (%s)
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_MTPT_E_NO_ALIAS_FOR_UNIX]

SEVERITY: ERROR
DESCRIPTION: S The dm_mount_point object named (%s) does not have a alias for the UNIX platform
CAUSE:
ACTION:
PARAMS:

nahoru

DM_NOTE

ERROR: [DM_NOTE_F_INIT3]

SEVERITY: FATAL
DESCRIPTION: The type manager returned an error storing the dmNote 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: dmobject.e,v 5.5 2002/06/20 00:19:48 ziff Exp $ dmObject class errors
PARAMS:

ERROR: [DM_NOTE_F_INIT1]

SEVERITY: FATAL
DESCRIPTION: The dmNote 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_NOTE_F_INIT2]

SEVERITY: FATAL
DESCRIPTION: II Version stamp %d was expected to be %d.
CAUSE: The version stamp that the dmNote 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_NOTE_E_CANT_ADDNOTE2]

SEVERITY: ERROR
DESCRIPTION: SS Can not relate %s sysobject to %s note object.
CAUSE: Could not build a relation object to establish annote relationship.
ACTION: See the previous error messages.
PARAMS:

ERROR: [DM_NOTE_E_CANT_FETCH_INVALID_ID]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch a note – 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_NOTE_E_CANT_ADDNOTE1]

SEVERITY: ERROR
DESCRIPTION: SS Can not relate %s sysobject to %s note object.
CAUSE: The sysobject and note object are part of the same version tree.
ACTION: None.
PARAMS:

ERROR: [DM_NOTE_E_CANT_CLEAN_UNUSED]

SEVERITY: ERROR
DESCRIPTION: S Could not complete the cleanup of unused note objects for %s docbase.
CAUSE: Previous operations have forced the server to stop the clean up operations.
ACTION: See the previous errors messages for the specific reasons.
PARAMS:

ERROR: [DM_NOTE_E_CANT_SAVE]

SEVERITY: ERROR
DESCRIPTION: S Cannot save %s sysobject.
CAUSE: One or more operations has failed during this save. Consult the following error message(s) for more help.
ACTION: Try again after fixing previous problems.
PARAMS:

ERROR: [DM_NOTE_E_ALREADY_ANNOTATED]

SEVERITY: ERROR
DESCRIPTION: SS The %s Sysobject is already annotated by %s note object.
CAUSE: The given sysobject is already related to the current note object.
ACTION: None.
PARAMS:

ERROR: [DM_NOTE_E_NO_ANNOTATION]

SEVERITY: ERROR
DESCRIPTION: SS No annotation relationship exists between %s note and %s sysobject.
CAUSE: No annotation relation exists between note object an given sysobject.
ACTION: None.
PARAMS:

nahoru

DM_OBJ_MGR

ERROR: [DM_OBJ_MGR_E_UNABLE_TO_FETCH_CONSISTENT_OBJECT_SNAPSHOT]

SEVERITY: ERROR
DESCRIPTION: D Unable to fetch object %s alongwith its aspect attributes with consistency
CAUSE: This error occurs when a client fetches an object that has aspect attributes, and that either the normal or aspect attributes have changed perhaps by a different session while Content Server was fetching the aspect attributes after fetching the normal attributes from the database.
ACTION: Application should refetch the object.
PARAMS:

ERROR: [DM_OBJ_MGR_E_UPDATE_FAIL]

SEVERITY: ERROR
DESCRIPTION: SSS attempt to update attributes of objects of type %s in table %s failed: error from database system was %s
CAUSE: The Update of objects of a given type failed because the attribute values could not be changed due to a database error.
ACTION: None: internal programming error.
PARAMS: The name of the type being updated, the name of the internal table being changed, and the error string reported by the database.

ERROR: [DM_OBJ_MGR_E_DIRECT_EXPUNGE_ASPECT_ATTRIBUTE_OBJECT_NOT_ALLOWED]

SEVERITY: ERROR
DESCRIPTION: D Cannot expunge aspect attribute side object with handle (%s) directly
CAUSE: A direct expunge attempt of the aspect attribute object using the EXPUNGE RPC call.
ACTION: Direct expunge of the aspect attribute object is not allowed. You must expunge the main object to which the aspect has been attached using the standard DFC API.
PARAMS:

ERROR: [DM_OBJ_MGR_E_CURSOR_FETCH_FAIL]

SEVERITY: ERROR
DESCRIPTION: S A failure occurred during a fetch through a cursor: database error message was %s
CAUSE: During a fetch in a database cursor, the operation failed. The operation is terminated.
ACTION: The database system error message may indicate how to repair the error.
PARAMS:

ERROR: [DM_OBJ_MGR_E_CURSOR_FAIL]

SEVERITY: ERROR
DESCRIPTION: SSS In operation %s an attempt to create cursor failed query was: %s error from database system was: %s
CAUSE: During an attempt to create a database cursor, a failure occurred. The error message gives the type manager operation that was being performed, the query on which the failure occurred, and the database error string.
ACTION: The database system error may indicate how to repair the error.
PARAMS:

ERROR: [DM_OBJ_MGR_E_DIRECT_SAVE_ASPECT_ATTRIBUTE_OBJECT_NOT_ALLOWED]

SEVERITY: ERROR
DESCRIPTION: D Cannot save aspect attribute side object with handle (%s) directly
CAUSE: A direct save attempt of the aspect attribute object using the SAVE RPC call.
ACTION: Direct save of the aspect attribute is not allowed. Use the DFC Save method to save the main object to which the aspect with the attributes has been attached.
PARAMS:

ERROR: [DM_OBJ_MGR_E_CANT_DELETE_RELATION_EXISTS]

SEVERITY: ERROR
DESCRIPTION: SS Cannot delete object %s since dm_relation object(s) %s exists with integrity_kind set to 1.
CAUSE: Cannot delete an object referenced by a dm_relation object with integrity kind set to 1.
ACTION: Delete the dm_relation object that references this object, and try again.
PARAMS:

ERROR: [DM_OBJ_MGR_E_DB_CONN]

SEVERITY: ERROR
DESCRIPTION: A failure occurred during an attempt to establish a connection to the database. The operation failed.
CAUSE: During (re)establishment of a database connection there was an error.
ACTION:
PARAMS:

ERROR: [DM_OBJ_MGR_E_DELETE_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: SI version mismatch on delete of object %s: version supplied was %d
CAUSE: The delete of an object failed because the version stamp supplied did not match the current version stamp in the database. (The caller had an old copy of the object.)
ACTION: Refetch the object to check that it should be deleted.
PARAMS: The identifier for the object and the version stamp that was supplied.

ERROR: [DM_OBJ_MGR_E_DELETE_NOTFOUND]

SEVERITY: ERROR
DESCRIPTION: SS no entry for the object with identifier %s could be found in the database table %s
CAUSE: During the deletion of an object, no entry for it could be found in the given internal database table. At least one entry must always exist.
ACTION: None: report to Documentum technical support.
PARAMS:

ERROR: [DM_OBJ_MGR_E_INVALID_ASPECT_ATTRIBUTE_OBJECT]

SEVERITY: ERROR
DESCRIPTION: DS An error occured when instantiating a persistent object for aspect attributes for %s, for aspect %s
CAUSE: An error occured when a persistent object is instantiated to store the aspect attributes.
ACTION: Refer to the accompanying error message(s).
PARAMS:

ERROR: [DM_OBJ_MGR_E_FETCH_FAIL]

SEVERITY: ERROR
DESCRIPTION: S attempt to fetch object with handle %s failed
CAUSE: The program attempted to fetch an object with a non-existent identifier.
ACTION: None: internal programming error.
PARAMS: The identifier of the object that was being fetched.

ERROR: [DM_OBJ_MGR_E_FETCH_BAD_TYPE]

SEVERITY: ERROR
DESCRIPTION: S attempt to create object of type %s failed because type did not exist
CAUSE: The program attempted to fetch an object trying to fetch an object of a type that does not exist.
ACTION: None: internal programming error.
PARAMS: The name of the type.

ERROR: [DM_OBJ_MGR_E_SAVE_FAIL]

SEVERITY: ERROR
DESCRIPTION: SSSS save failed for object with handle %s of type %s: table on which save failed was %s error from database system was %s
CAUSE: The save of an object failed because of a database error.
ACTION: None: internal programming error.
PARAMS: The identifier of the object, the name of its type, the name of the database table on which the save failed and the error string reported by the database system.

ERROR: [DM_OBJ_MGR_E_UNABLE_TO_APPLY_ASPECT_ATTR_CHANGES]

SEVERITY: ERROR
DESCRIPTION: DS Unable to apply aspect attribute changes defined by aspect %s for object %s
CAUSE: An (internal) error occured when attempting to apply aspect attribute changes defined by an aspect attached to the reported object.
ACTION: Refer to accompanying messages.
PARAMS:

ERROR: [DM_OBJ_MGR_E_UNABLE_TO_VALIDATE_ASPECT_ATTRIBUTE_TYPE]

SEVERITY: ERROR
DESCRIPTION: SS A database error occured while attempting to validate attributes for aspect (%s). Database error is (%s)
CAUSE: A database error occured when Content Server attempted to check if an aspect had attribute definition.
ACTION: Refer to the database error and take corrective action.
PARAMS:

ERROR: [DM_OBJ_MGR_E_SAVE_FAILED_UNAVAILABLE_TYPE]

SEVERITY: ERROR
DESCRIPTION: S Your client is older than your server, and you have attempted to create an object of a type (%s) that is not available to your client version.
CAUSE: A type that is available in your docbase was created by an e-Content Server that is newer than the Documentum Client Library (dmcl) of the client you are using. You cannot create an object of that type unless the dmcl matches. You would not get a correct ID, nor proper save semantics if this were allowed.
ACTION:
PARAMS:

ERROR: [DM_OBJ_MGR_E_ACTION]

SEVERITY: ERROR
DESCRIPTION: Diagnois and remedy the database error.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_OBJ_MGR_E_VERSION_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: SSL save of object %s of type %s failed because of version mismatch: old version was %d
CAUSE: The save of an object failed because the version stamp in the object was inconsistent with the version stamp currently stored in the database.
ACTION: Refetch the object, make the necessary changes and save it again.
PARAMS: The identifier of the object, the type of the object and the old value of the version stamp.

ERROR: [DM_OBJ_MGR_E_ASPECT_ATTR_EXISTS_CHECK_FAILED]

SEVERITY: ERROR
DESCRIPTION: DSS A database error occured when checking if object %s has attributes defined through aspect %s: %s
CAUSE: A database error occured when CS attempted to check if specified object has attributes defined through specified aspect
ACTION: Refer to the database error and take the database server specific corrective action.
PARAMS:

ERROR: [DM_OBJ_MGR_E_UNABLE_TO_CLONE_ASPECT_ATTRIBUTES]

SEVERITY: ERROR
DESCRIPTION: DDS An error occured while cloning the aspect attributes from %s to %s for aspect %s
CAUSE: An error occured while cloning the aspect attributes of a persistent object.
ACTION: Refer to accompanying error messages
PARAMS:

ERROR: [DM_OBJ_MGR_E_LOCK_FAIL]

SEVERITY: ERROR
DESCRIPTION: SSSS lock failed for object with handle %s of type %s: table on which lock failed was %s error from database system was %s
CAUSE: The lock of an object failed because of a database error.
ACTION: None internal programming error.
PARAMS: The identifier of the object, the name of its type, the name of the database table on which the save failed and the error string reported by the database system.

ERROR: [DM_OBJ_MGR_E_DIRECT_FETCH_ASPECT_ATTRIBUTE_OBJECT_NOT_ALLOWED]

SEVERITY: ERROR
DESCRIPTION: D Cannot fetch aspect attribute side object with handle (%s) directly
CAUSE: A direct fetch attempt of the aspect attribute object using the FETCH RPC call.
ACTION: Direct fetch of the aspect attribute object is not allowed. You must access the aspect attributes using standard DFC API.
PARAMS:

ERROR: [DM_OBJ_MGR_E_SAVE_ASPECT_NQA]

SEVERITY: ERROR
DESCRIPTION: S Could not save nonqualifiable aspect attribute to object %s without property bag .
CAUSE: Main object doesnt have property bag.
ACTION: Add property bag to main object or redefine the attribute as regular qualified attribute.
PARAMS:

ERROR: [DM_OBJ_MGR_E_UP_OUT_OF_RANGE]

SEVERITY: ERROR
DESCRIPTION: SI Unable to set attribute %s because the value (%d) being assigned is out of range
CAUSE: Attempt to assign a value to an attribute which is out of range of the attributes datatype. For example, assigning a value to an integer attribute larger than the largest allowable integer.
ACTION: Either scale the values being assigned to such an attribute, or increase the range of the attribute to allow such values. For example, turn an attribute of type integer into type double.
PARAMS: The first parameter is the attribute name $Id: dmptm.e,v 5.15 2002/02/05 19:21:21 aamir Exp $ dmTypeManager class errors

ERROR: [DM_OBJ_MGR_E_LOCK_INVALIDDB]

SEVERITY: ERROR
DESCRIPTION: SS lock of object %s of type %s failed because of invalid database connection.
CAUSE: The lock of an object failed because the database connection is not alive.
ACTION: make a valid connection to database and relock this object.
PARAMS: The identifier of the object, the type of the object.

ERROR: [DM_OBJ_MGR_E_SET_NULL_TYPE]

SEVERITY: ERROR
DESCRIPTION: attempt to set persistent object type to NULL
CAUSE: The program called SetType with a NULL type.
ACTION: None: internal programming error.
PARAMS: None.

ERROR: [DM_OBJ_MGR_E_LOCK_NEWOBJ]

SEVERITY: ERROR
DESCRIPTION: SS lock of object %s of type %s failed because this object has not been created.
CAUSE: The lock of an object failed because this object does not exist in database.
ACTION: None internal programming error.
PARAMS: The identifier of the object, the type of the object.

ERROR: [DM_OBJ_MGR_E_UNABLE_TO_FETCH_ASPECT_ATTRS]

SEVERITY: ERROR
DESCRIPTION: DS Unable to fetch aspect attributes defined by aspect %s for object %s
CAUSE: An error occured when attempting to fetch the attributes defined by an aspect attached to the reported object.
ACTION: Refer to accompanying error messages
PARAMS:

ERROR: [DM_OBJ_MGR_E_SET_BAD_TYPE]

SEVERITY: ERROR
DESCRIPTION: S attempt to set persistent object type to non-persistent type %s
CAUSE: The program called SetType to set the type of a persistent object to a non-persistent type.
ACTION: None: internal programming error.
PARAMS: The name of the type.

ERROR: [DM_OBJ_MGR_E_INVALID_ASPECT_ATTR_TYPE]

SEVERITY: ERROR
DESCRIPTION: SS Attribute definition by aspect (%s) is invalid. Internal type (%s) is not found in the repository
CAUSE: This error occurs when Content Server attempts to save or fetch aspect attributes for a persistent object, and the internal type created for attribute definition is not valid.
ACTION: Verify if the type object referenced in i_attr_def attribute of the Aspect object is valid. If not valid, use alter aspect DQL statement to define attributes.
PARAMS:

ERROR: [DM_OBJ_MGR_E_DELETE_FAIL]

SEVERITY: ERROR
DESCRIPTION: SSS attempt to delete attributes of object %s in table %s failed: error from database system was %s
CAUSE: The destroy of an object failed because the attribute values could not be deleted due to a database error.
ACTION: None: internal programming error.
PARAMS: The identifier of the object, the name of the internal table being updated, and the error string reported by the database system.

ERROR: [DM_OBJ_MGR_E_DUPLICATE_ASPECTS_FOUND]

SEVERITY: ERROR
DESCRIPTION: SD Aspect (%s) has been attached more than once for object (%s)
CAUSE: An aspect has been attached more than once for an object.
ACTION: Cant attach the same aspect more than once for an object. Remove the duplicates and retry the operation.
PARAMS:

ERROR: [DM_OBJ_MGR_W_ENUM_DATABASE_CLOSED]

SEVERITY: WARNING
DESCRIPTION: attempt to begin enumeration of type with closed database
CAUSE: Program called EnumerateForType after the database had been closed.
ACTION: None:nternal programming error.
PARAMS: None

ERROR: [DM_OBJ_MGR_W_LOAD_PROPERTY_BAG]

SEVERITY: WARNING
DESCRIPTION: S Could not deserialize property bag for %s.
CAUSE: Serialization format error
ACTION: No recovery possible.
PARAMS:

ERROR: [DM_OBJ_MGR_W_UPDATE_TYPE_NULL]

SEVERITY: WARNING
DESCRIPTION: attempt to update NULL type
CAUSE: Program called Update passing in a NULL type.
ACTION: None: internal programming error.
PARAMS: None.

ERROR: [DM_OBJ_MGR_W_MATCH_BAD_ATTR]

SEVERITY: WARNING
DESCRIPTION: IS match field attribute %d in type %s is erroneous
CAUSE: Program called MatchField or MatchForIds to match an attribute that was erroneous (was not defined, or had an erroneous type).
ACTION: None: internal programming error.
PARAMS: The number of the attribute and the name of the type being matched.

ERROR: [DM_OBJ_MGR_W_ENUM_BAD_ATTR]

SEVERITY: WARNING
DESCRIPTION: SS order_by attribute %s in enumeration is not part of type %s
CAUSE: Program called EnumerateForType, specifying an attribute name to order the result that is not part of the type.
ACTION: None: internal programming error.
PARAMS: The name of the attribute and the name of the type.

ERROR: [DM_OBJ_MGR_W_ENUM_TYPE_BOGUS]

SEVERITY: WARNING
DESCRIPTION: S attempt to enumerate non-persistent type %s
CAUSE: Program called EnumerateForType with a type that is not in the database.
ACTION: None: internal programming error.
PARAMS: The name of the type.

ERROR: [DM_OBJ_MGR_W_MATCH_BAD_ORDER_BY]

SEVERITY: WARNING
DESCRIPTION: SS match field order_by attribute %s is not attribute of type %s
CAUSE: Program called MatchField specifying an attribute to order the result that is not a part of the type being enumerated.
ACTION: None: internal programming error.
PARAMS: The name of the order by attribute and the name of the type.

ERROR: [DM_OBJ_MGR_W_UPDATE_TYPE_BOGUS]

SEVERITY: WARNING
DESCRIPTION: S attempt to perform update with non-persistent type %s
CAUSE: Program called Update passing in a type that does not exist in the database.
ACTION: None: internal programming error.
PARAMS: The name of the type.

ERROR: [DM_OBJ_MGR_W_ENUM_TYPE_NULL]

SEVERITY: WARNING
DESCRIPTION: attempt to enumerate NULL type
CAUSE: Program called EnumerateForType will a NULL type value.
ACTION: None: internal programming error.
PARAMS: None

ERROR: [DM_OBJ_MGR_W_ENUM_BAD_MATCH_TYPE]

SEVERITY: WARNING
DESCRIPTION: SS match_type %s in enumeration is not subtype of type %s
CAUSE: Program called EnumerateForType, specifying a match type that is not a subtype of the type being enumerated.
ACTION: None: internal programming error.
PARAMS: The name of the match type and the type being enumerated.

ERROR: [DM_OBJ_MGR_W_MATCH_TYPE_NULL]

SEVERITY: WARNING
DESCRIPTION: attempt to perform match field with NULL type
CAUSE: Program called MatchField or MatchForIds with a NULL type value.
ACTION: None: internal programming error.
PARAMS: None.

ERROR: [DM_OBJ_MGR_W_MATCH_BAD_POS]

SEVERITY: WARNING
DESCRIPTION: match position specification invalid
CAUSE: Program called MatchField or MatchForIds with position specification but no repeating attributes were being matched
ACTION: None.
PARAMS: None.

ERROR: [DM_OBJ_MGR_W_UPDATE_NO_UPDATES]

SEVERITY: WARNING
DESCRIPTION: attempt to update with no updates
CAUSE: Program called Update but passed no attribute values to be changed.
ACTION: None: internal programming error.
PARAMS: None.

ERROR: [DM_OBJ_MGR_W_UPDATE_OVERLAP_ATTR]

SEVERITY: WARNING
DESCRIPTION: IS attempt to use attribute %d as both match field and update field of type %s
CAUSE: Program called Update to change attribute that is also being used to match objects to be changed. (The set of attributes to be changed must be disjoint from the set of attributes used to match.)
ACTION: None: internal programming error.
PARAMS: The number of the attribute and the name of the type.

ERROR: [DM_OBJ_MGR_W_UPDATE_BAD_ATTR]

SEVERITY: WARNING
DESCRIPTION: IS attribute %d of type %s has undefined type in update
CAUSE: Program called Update to update an attribute that has an undefined type.
ACTION: None: internal programming error.
PARAMS: The number of the attribute and the name of the type.

ERROR: [DM_OBJ_MGR_W_MATCH_BAD_MATCH_TYPE]

SEVERITY: WARNING
DESCRIPTION: SS match_type %s in match field is not subtype of type %s
CAUSE: Program called MatchField with a match type that is not of subtype of the type being enumerated.
ACTION: None: internal programming error.
PARAMS: The name of the match type and the name of the type being enumerated.

ERROR: [DM_OBJ_MGR_W_VERSION_MISMATCH]

SEVERITY: WARNING
DESCRIPTION: SSI save of object %s of type %s failed because of version mismatch: old version was %d
CAUSE: The save of an object failed because the version stamp in the object was inconsistent with the version stamp currently stored in the database.
ACTION: Refetch the object, make the necessary changes and save it again.
PARAMS: The identifier of the object, the type of the object and the old value of the version stamp.

ERROR: [DM_OBJ_MGR_W_MATCH_TYPE_BOGUS]

SEVERITY: WARNING
DESCRIPTION: S attempt to perform match field with non-persistent type %s
CAUSE: Program called MatchField or MatchForIds with a type that is not in the database.
ACTION: None: internal programming error.
PARAMS: The name of the type.

ERROR: [DM_OBJ_MGR_W_UPDATE_BAD_MATCH_TYPE]

SEVERITY: WARNING
DESCRIPTION: SS match_type %s in update is not subtype of type %s
CAUSE: Program called Update with a match type that is not a subtype of the type on which the update is being performed.
ACTION: None: internal programming error.
PARAMS: The name of the match type and the name of the type being updated.

nahoru

DM_OBJECT

ERROR: [DM_OBJECT_E_OBJECT_ID_LOOKUP]

SEVERITY: ERROR
DESCRIPTION: D Error looking up object %s.
CAUSE: Internal error occurred while processing or evaluating object.
ACTION: Check the error log for further messages that might give more detail. Check that the specified object is valid.
PARAMS: %1 – handle for object we failed on.

ERROR: [DM_OBJECT_E_FETCH_FAILURE]

SEVERITY: ERROR
DESCRIPTION: error fetching object attributes
CAUSE: The client could not fetch an objects attributes
ACTION: Probable server failure.
PARAMS:

ERROR: [DM_OBJECT_E_INVALID_TYPE]

SEVERITY: ERROR
DESCRIPTION: SD Invalid type %s for object %s.
CAUSE: Could not find the type for an object we were processing
ACTION: Check the error log for further messages that might give more detail. Check that the specified object is valid.
PARAMS: %1 – type name we were looking for %2 – handle for object we failed on.

ERROR: [DM_OBJECT_E_LOAD_MEMORY_EXHAUSTED]

SEVERITY: ERROR
DESCRIPTION: I Error loading object: failed to allocate %d bytes
CAUSE: During an attempt to read an object from an input stream, an attempt to allocate memory failed. The object could not be loaded.
ACTION: No recovery possible.
PARAMS: The number of bytes which the process attempted to allocate. Output Device Facility errors

ERROR: [DM_OBJECT_E_COULD_NOT_FETCH_DD_ATTR_OBJECT]

SEVERITY: ERROR
DESCRIPTION: SS Could not fetch the Data Dictionary object for type %s, attribute %s.
CAUSE: This is an internal error.
ACTION: No recovery possible.
PARAMS:

ERROR: [DM_OBJECT_E_BAD_DD_ATTR_HANDLE]

SEVERITY: ERROR
DESCRIPTION: SSI Could not parse Data Dictionary handle for type %s, attribute %s. Error code = %d.
CAUSE: This is an internal error.
ACTION: No recovery possible.
PARAMS:

ERROR: [DM_OBJECT_E_LOAD_COUNT_ERROR]

SEVERITY: ERROR
DESCRIPTION: SII error loading object — wrong object count for object of type %s found %d attributes, but type says there should be %d
CAUSE: When reading an input stream containing an object, the count of attribute values in the stream and the count of attributes in the type differed.
ACTION: No recovery possible.
PARAMS: The name of the type, the count of attributes in the stream, the count of attributes in the type.

ERROR: [DM_OBJECT_E_LOAD_TYPE_VERSION_ERROR]

SEVERITY: ERROR
DESCRIPTION: SII error loading object — wrong type version for object of type %s loaded object has version %d, but current type has version %d
CAUSE: When reading an input stream containing an object, the type version of the serialized type and type version of the server type differed.
ACTION: Reload the object and reapply changes.
PARAMS: The name of the type, serialized type version, type system type version.

ERROR: [DM_OBJECT_E_LOAD_TYPE_ERROR]

SEVERITY: ERROR
DESCRIPTION: S error loading object — cant find type %s
CAUSE: When reading an input stream containing an object, the type name was given as the type of the object in the stream the type is unknown and cant be found on the server.
ACTION: No recovery possible.
PARAMS: The name of the type that could not be found.

ERROR: [DM_OBJECT_E_OBJECT_TOO_BIG]

SEVERITY: ERROR
DESCRIPTION: attempt to return object that exceeds the network buffer size
CAUSE: The object being returned from an RPC exceeds the size of the network buffer (64K).
ACTION: No recovery possible.
PARAMS:

ERROR: [DM_OBJECT_E_LOAD_KEYWORD_ERROR]

SEVERITY: ERROR
DESCRIPTION: error loading object — stream should begin with OBJ
CAUSE: An attempt was made to read an object from an input stream the stream did not begin with the keyword OBJ used to indicate the start of an object dump.
ACTION: No recovery possible.
PARAMS: None

ERROR: [DM_OBJECT_E_BAD_DD_HANDLE]

SEVERITY: ERROR
DESCRIPTION: SI Could not parse Data Dictionary handle for type %s. Error code = %d.
CAUSE: This is an internal error.
ACTION: No recovery possible.
PARAMS:

ERROR: [DM_OBJECT_E_LOAD_INVALID_STRING_LEN]

SEVERITY: ERROR
DESCRIPTION: I Error loading object: invalid string length %d found in input stream
CAUSE: During an attempt to read an object from an input stream an invalid sting length was found. The object could not be loaded.
ACTION: No recovery possible.
PARAMS: The length of the string that was read.

ERROR: [DM_OBJECT_E_COULD_NOT_FETCH_DD_OBJECT]

SEVERITY: ERROR
DESCRIPTION: S Could not fetch the Data Dictionary object for type %s.
CAUSE: This is an internal error.
ACTION: No recovery possible.
PARAMS:

ERROR: [DM_OBJECT_W_GET_ATTR_KIND_ERROR]

SEVERITY: WARNING
DESCRIPTION: S attempt to fetch from non-zero position in single-valued attribute %s
CAUSE: Program executed a Get operation with a non-zero position argument, when the attribute contained only a single-value/
ACTION: No action.
PARAMS: The name of the attribute.

ERROR: [DM_OBJECT_W_DELETE_ATTR_LEN_ERROR]

SEVERITY: WARNING
DESCRIPTION: II attempt to delete at non-existent position %d in attribute %d
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_OBJECT_W_APPEND_ATTR_TYPE_ERROR]

SEVERITY: WARNING
DESCRIPTION: I attempt to append value of wrong type to attribute %d
CAUSE: Program executed an Append operation to append a value of a type different from the type of the attribute.
ACTION: No action.
PARAMS: The number of the attribute.

ERROR: [DM_OBJECT_W_INSERT_ATTR_TYPE_MISMATCH]

SEVERITY: WARNING
DESCRIPTION: S attempt to insert value of wrong type in attribute %s
CAUSE: Program executed an InsertAttr with a value of a type different from the type of the attribute.
ACTION: No action.
PARAMS: The name of the attribute.

ERROR: [DM_OBJECT_W_SET_ATTR_TYPE_ERROR]

SEVERITY: WARNING
DESCRIPTION: I attempt to assign value of wrong type to attribute %d
CAUSE: Program executed a Set operation to change the value of an attribute to a value of the wrong type (a type inconsistent with the type of the attribute).
ACTION: No action.
PARAMS: The number of the attribute being set.

ERROR: [DM_OBJECT_W_APPEND_ATTR_TYPE_ERROR_NAME]

SEVERITY: WARNING
DESCRIPTION: IS attempt to append value of wrong type to attribute %d (name %s)
CAUSE: Program executed an Append operation to append a value of a type different from the type of the attribute.
ACTION: No action.
PARAMS: The number and name of the attribute.

ERROR: [DM_OBJECT_W_SET_ATTR_STRING_MALFORMED_NAME]

SEVERITY: WARNING
DESCRIPTION: IISS attempt to assign malformed value of encoding %d to attribute %d (name %s). Value:%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: The encoding number, number and name of the attribute, and atribute value

ERROR: [DM_OBJECT_W_ADD_ATTR_DUPLICATE_ERROR]

SEVERITY: WARNING
DESCRIPTION: S attempt to add duplicate attribute %s
CAUSE: Program executed an AddAttr operation to add an attribute that already exists in the object.
ACTION: No action.
PARAMS: The name of the attribute.

ERROR: [DM_OBJECT_W_SET_ATTR_POSITION_ERROR]

SEVERITY: WARNING
DESCRIPTION: I attempt to set non-existent attribute %d
CAUSE: Program executed a Set operation on a non-existent attribute.
ACTION: No action.
PARAMS: The number of the attribute being set.

ERROR: [DM_OBJECT_W_INSERT_ATTR_KIND_ERROR]

SEVERITY: WARNING
DESCRIPTION: I attempt to insert into non-repeating attribute %d
CAUSE: Program executed an Insert operation to add a new value into a single-valued attribute.
ACTION: No action.
PARAMS: The number of the attribute.

ERROR: [DM_OBJECT_W_APPEND_ATTR_STRING_LENGTH_ERROR]

SEVERITY: WARNING
DESCRIPTION: I attempt to append string of excessive length to attribute %i
CAUSE: Program attempted to Append a string value with a length that exceeded the maximum length allowed for the attribute.
ACTION: No action.
PARAMS: The number of the attribute.

ERROR: [DM_OBJECT_W_GET_ATTR_TYPE_MISMATCH]

SEVERITY: WARNING
DESCRIPTION: S attempt to read value of wrong type from attribute %s
CAUSE: Program executed a Get operation with a result type different from the type of the attribute (e.g., using GetLongAttrByName on a string-valued attribute).
ACTION: No action.
PARAMS: The name of the attribute.

ERROR: [DM_OBJECT_W_DELETE_ATTR_POSITION_ERROR]

SEVERITY: WARNING
DESCRIPTION: I attempt to delete non-existent attribute %d
CAUSE: Program executed a DeleteAttr operation that specified an non-existent attribute position (either a negative number or a number larger than the number of attributes in the object).
ACTION: No action.
PARAMS: The number of the attribute.

ERROR: [DM_OBJECT_W_FIND_ATTR_NAME_ERROR]

SEVERITY: WARNING
DESCRIPTION: S attempt to find value in non-existent attribute %s
CAUSE: Program executed a FindAttrValue operation naming a non-existent attribute.
ACTION: No action.
PARAMS: The name of the attribute.

ERROR: [DM_OBJECT_W_SET_ATTR_STRING_LENGTH]

SEVERITY: WARNING
DESCRIPTION: S attempt to assign string of excessive length to attribute %s
CAUSE: Program executed a SetAttr of a string-valued attribute. The length of the string being assigned to the attribute was longer than the length property of the attribute.
ACTION: No action.
PARAMS: The name of the attribute.

ERROR: [DM_OBJECT_W_GET_ATTR_POSITION_ERROR]

SEVERITY: WARNING
DESCRIPTION: I attempt to fetch non-existent attribute %d
CAUSE: Program executed a Get operation to fetch an attribute that did not exist (the attribute number that was passed was either negative or larger than the number of attributes in the object).
ACTION: No action.
PARAMS: The number of the attribute.

ERROR: [DM_OBJECT_W_GET_ATTR_NAME_ERROR]

SEVERITY: WARNING
DESCRIPTION: S attempt to get non-existent attribute %s
CAUSE: Program executed a Get operation on a non-existent attribute.
ACTION: No action.
PARAMS: The name of the attribute.

ERROR: [DM_OBJECT_W_DELETE_ATTR_LEN_MISMATCH]

SEVERITY: WARNING
DESCRIPTION: S attempt to delete non-existing item in attribute %s
CAUSE: Program executed an InsertAttr naming a non-existent attribute.
ACTION: No action.
PARAMS: The name of the attribute.

ERROR: [DM_OBJECT_W_DROP_ATTR_POSITION_ERROR]

SEVERITY: WARNING
DESCRIPTION: I attempt to drop value from non-existent attribute %d
CAUSE: Program executed a DropAttr operation that specified an non-existent attribute position (either a negative number or a number larger than the number of attributes in the object).
ACTION: No action.
PARAMS: The number of the attribute.

ERROR: [DM_OBJECT_W_APPEND_ATTR_TYPE_MISMATCH]

SEVERITY: WARNING
DESCRIPTION: S attempt to append value of wrong type to attribute %s
CAUSE: Program executed an AppendAttr with a value of a type different from the type of the attribute.
ACTION: No action.
PARAMS: The name of the attribute.

ERROR: [DM_OBJECT_W_SET_ATTR_TYPE_ERROR_NAME]

SEVERITY: WARNING
DESCRIPTION: IS attempt to assign value of wrong type to attribute %d (name %s)
CAUSE: Program executed a Set operation to change the value of an attribute to a value of the wrong type (a type inconsistent with the type of the attribute).
ACTION: No action.
PARAMS: The number and name of the attribute being set.

ERROR: [DM_OBJECT_W_INSERT_ATTR_LEN_MISMATCH]

SEVERITY: WARNING
DESCRIPTION: S attempt to insert value beyond current length of attribute %s
CAUSE: Program executed an InsertAttr at a position beyond the current length of the list of values in the attribute.
ACTION: No action.
PARAMS: The name of the attribute.

ERROR: [DM_OBJECT_W_SET_ATTR_KIND_MISMATCH]

SEVERITY: WARNING
DESCRIPTION: S attempt to set to non-zero position in single-valued attribute %s
CAUSE: Program executed a SetAttr with a non-zero position (trying to change a multi-valued attribute) the attribute only had a single value.
ACTION: No action.
PARAMS: The name of the attribute.

ERROR: [DM_OBJECT_W_SET_ATTR_LENGTH_ERROR]

SEVERITY: WARNING
DESCRIPTION: I attempt to set non-existent attribute value of attribute %d
CAUSE: Program executed a Set operation with a non-zero position argument that was beyond the current number of values in the attribute.
ACTION: No action.
PARAMS: The number of the attribute being set.

ERROR: [DM_OBJECT_W_GET_ATTR_TYPE_ERROR_NAME]

SEVERITY: WARNING
DESCRIPTION: IS attempt to read value of wrong type from attribute %d (name %s)
CAUSE: Program executed a Get operation with a result type different from the type of the attribute (e.g., using GetLongAttr on a string-valued attribute).
ACTION: No action.
PARAMS: The number and name of the attribute.

ERROR: [DM_OBJECT_W_APPEND_ATTR_POSITION_ERROR]

SEVERITY: WARNING
DESCRIPTION: I attempt to append to non-existent attribute %d
CAUSE: Program executed an Append operation to append a value to a non-existent attribute.
ACTION: No action.
PARAMS: The number of the attribute.

ERROR: [DM_OBJECT_W_GET_ATTR_LENGTH_ERROR]

SEVERITY: WARNING
DESCRIPTION: IIS attempt to read from non-existent position %d in attribute %d, type %s
CAUSE: Program executed Get operation on a non-existent attribute (i.e., the attribute position specified was negative or beyond the last attribute of the object).
ACTION: No action.
PARAMS: The position of the attribute.

ERROR: [DM_OBJECT_W_INSERT_ATTR_NAME_ERROR]

SEVERITY: WARNING
DESCRIPTION: S attempt to insert into non-existent attribute %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_OBJECT_W_GET_ATTR_TYPE_ERROR]

SEVERITY: WARNING
DESCRIPTION: I attempt to read value of wrong type from attribute %d
CAUSE: Program executed a Get operation with a result type different from the type of the attribute (e.g., using GetLongAttr on a string-valued attribute).
ACTION: No action.
PARAMS: The number of the attribute.

ERROR: [DM_OBJECT_W_DROP_ATTR_NAME_ERROR]

SEVERITY: WARNING
DESCRIPTION: S attempt to drop value from non-existent attribute %s
CAUSE: Program executed a DropAttr that specified an non-existent attribute name.
ACTION: No action.
PARAMS: The name of the attribute.

ERROR: [DM_OBJECT_W_INSERT_ATTR_LEN_ERROR]

SEVERITY: WARNING
DESCRIPTION: II attempt to insert at invalid position %d in attribute %d
CAUSE: Program executed an Insert operation to add a value at an invalid position (i.e., the position specified was negative or beyond the current list of values in the attribute).
ACTION: No action.
PARAMS: The number of the attribute.

ERROR: [DM_OBJECT_W_SET_ATTR_BY_NAME_LENGTH_MISMATCH]

SEVERITY: WARNING
DESCRIPTION: S attempt to set attribute %s beyond current length
CAUSE: Program executed a SetAttr with a position beyond the current length of the value list for the attribute.
ACTION: No action.
PARAMS: The name of the attribute.

ERROR: [DM_OBJECT_W_SET_ATTR_LENGTH_MISMATCH]

SEVERITY: WARNING
DESCRIPTION: I attempt to set attribute %d beyond current length
CAUSE: Program executed a SetAttr with a position beyond the current length of the value list for the attribute.
ACTION: No action.
PARAMS: The name of the attribute.

ERROR: [DM_OBJECT_W_SET_ATTR_STRING_TOO_LONG]

SEVERITY: WARNING
DESCRIPTION: I attempt to assign string of excessive length to attribute %i
CAUSE: Program executed a Set operation to assign a string that is longer than the maximum size allowed for the attribute.
ACTION: No action.
PARAMS: The number of the attribute being set.

ERROR: [DM_OBJECT_W_TYPE_VERSION_MISMATCH]

SEVERITY: WARNING
DESCRIPTION: SII wrong type version for object of type %s object has version %d, but server type has version %d
CAUSE: When processing an object, the type version of the serialized type and type version of the server type differed.
ACTION: If errors result, refresh object, and reapply changes.
PARAMS: The name of the type, serialized type version, type system type version.

ERROR: [DM_OBJECT_W_SET_TYPE_WITH_NULL_TYPE]

SEVERITY: WARNING
DESCRIPTION: attempt to set type of persistent object with NULL type
CAUSE: Program executed a SetType operation using a NULL type.
ACTION: No action.
PARAMS: None.

ERROR: [DM_OBJECT_W_DELETE_ATTR_NAME_ERROR]

SEVERITY: WARNING
DESCRIPTION: S attempt to delete non-existent attribute %s
CAUSE: Program executed a DeleteAttr operation that specified a non-existent value in the attribute (the position either was negative or greater than the current number of values in the attribute).
ACTION: No action.
PARAMS: The number of the attribute.

ERROR: [DM_OBJECT_W_DROP_ATTR_LENGTH_ERROR]

SEVERITY: WARNING
DESCRIPTION: I attempt to drop non-existent value from attribute %d
CAUSE: Program executed a DropAttr that specified a non-existent value in the attribute (the position either was negative or greater than the current number of values in the attribute).
ACTION: No action.
PARAMS: The number of the attribute.

ERROR: [DM_OBJECT_W_APPEND_ATTR_KIND_ERROR]

SEVERITY: WARNING
DESCRIPTION: I attempt to append to non-repeating attribute %d
CAUSE: Program attempted to Append a value to a single-valued attribute.
ACTION: No action.
PARAMS: The number of the attribute.

ERROR: [DM_OBJECT_W_INSERT_ATTR_POSITION_ERROR]

SEVERITY: WARNING
DESCRIPTION: I attempt to insert in non-existent attribute %d
CAUSE: Program executed an Insert operation to insert a value in a non-existent attribute.
ACTION: No action.
PARAMS: The number of the attribute.

ERROR: [DM_OBJECT_W_SET_ATTR_TYPE_MISMATCH]

SEVERITY: WARNING
DESCRIPTION: S attempt to assign value of wrong type to attribute %s
CAUSE: Program executed a SetAttr with a value of a type different from the type of the attribute.
ACTION: No action.
PARAMS: The name of the attribute.

nahoru

DM_OUTPUTDEVICE

ERROR: [DM_OUTPUTDEVICE_E_INIT3]

SEVERITY: ERROR
DESCRIPTION: The type manager returned an error storing the dmOutputDevice type.
CAUSE: Unknown.
ACTION: Look at the error logged by the type manager.
PARAMS:

ERROR: [DM_OUTPUTDEVICE_E_NOOSNAME]

SEVERITY: ERROR
DESCRIPTION: S The output device %s was not found in the system.
CAUSE: 1. The caller spelled the output device name incorrectly. 2. A dm_outputdevice is not defined with the specified name.
ACTION: 1. Correct the spelling of the device name and retry the operation. 2. Define and Save a dmOutputDevice before retrying this operation.
PARAMS:

ERROR: [DM_OUTPUTDEVICE_E_CANT_FIND_METHOD]

SEVERITY: ERROR
DESCRIPTION: S Can not find the method named : %s.
CAUSE: Server could not find a method with the supplied name.
ACTION: Check dm_method objects for a method of this name and report it to your sysadmin
PARAMS:

ERROR: [DM_OUTPUTDEVICE_E_UNEXPECTEDERROR]

SEVERITY: ERROR
DESCRIPTION: Unexpected Error.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_OUTPUTDEVICE_E_TICKET_FAILED]

SEVERITY: ERROR
DESCRIPTION: S Ticket generation failed for user %s.
CAUSE: Server failed to generate a ticket for the specified user
ACTION: Report the error to the sysadmin, check user credentials
PARAMS:

ERROR: [DM_OUTPUTDEVICE_E_SCANF1]

SEVERITY: ERROR
DESCRIPTION: S Internal error. The lp subsystem returned a string that sscanf was not expecting. String:%s
CAUSE: Unknown.
ACTION: Carefully record this error message and any parameters and contact your Documentum Site Administrator.
PARAMS:

ERROR: [DM_OUTPUTDEVICE_E_FETCH_FAILED]

SEVERITY: ERROR
DESCRIPTION: Unable to complete the print request due to an error fetching the content
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_OUTPUTDEVICE_E_APPLY1]

SEVERITY: ERROR
DESCRIPTION: ApplyForInt unexpectedly returned invalid.
CAUSE: Unknown.
ACTION: Carefully record this error message and any parameters and contact your Documentum Site Administrator.
PARAMS:

ERROR: [DM_OUTPUTDEVICE_E_INIT4]

SEVERITY: ERROR
DESCRIPTION: The dm_outputdevice type cannot be stored because the dm_sysobject type could not be fetched from the database.
CAUSE: The dm_sysobject type does not exist in the database.
ACTION: Unknown. It would be a good idea to check the database permissions for docuserv.
PARAMS:

ERROR: [DM_OUTPUTDEVICE_E_REMOVE]

SEVERITY: ERROR
DESCRIPTION: IS A system error %d was encountered while attempting to remove the temporary print file %s.
CAUSE: Unknown.
ACTION: Check the permission of the print file. Check the permissions of all directories leading to the print file.
PARAMS:

ERROR: [DM_OUTPUTDEVICE_E_CANT_RUN_METHOD]

SEVERITY: ERROR
DESCRIPTION: SL The server was unable to run method %s, error return was %d.
CAUSE: Server failed to generate a ticket for the specified user
ACTION: Report the error to the sysadmin, check user credentials
PARAMS:

ERROR: [DM_OUTPUTDEVICE_E_ASSUME_USER_PF]

SEVERITY: ERROR
DESCRIPTION: SS Unable to access the assume user program file. Error returned from Operating System: (%s). Program file: (%s).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_OUTPUTDEVICE_E_SAVE1]

SEVERITY: ERROR
DESCRIPTION: This Output Devices operating system device name has not been set.
CAUSE: The device name attribute is not set.
ACTION: Contact your Documentum Site Administrator about verifying the correct definition of the output device that you are trying to use.
PARAMS:

ERROR: [DM_OUTPUTDEVICE_E_APPLY3]

SEVERITY: ERROR
DESCRIPTION: Apply(SEARCH) unexpectedly returned NULL.
CAUSE: Unknown.
ACTION: Carefully record this error message and any parameters and contact your Documentum Site Administrator.
PARAMS:

ERROR: [DM_OUTPUTDEVICE_E_NEED_PRIV_FOR_CHANGE]

SEVERITY: ERROR
DESCRIPTION: SS The current user (%s) needs to have superuser or sysadmin privilege to save or destroy %s server_config object.
CAUSE: Must have Superuser or SysAdmin privilege to save/destroy outputdevice objects.
ACTION: Consult your system administrator.
PARAMS:

ERROR: [DM_OUTPUTDEVICE_E_OPEN_PRINTER]

SEVERITY: ERROR
DESCRIPTION: SS Unable to open the output device due to error: %s. The command used was: (%s)
CAUSE: Unknown: it is a function of the command given
ACTION: Check your configuration and/or operating system.
PARAMS:

ERROR: [DM_OUTPUTDEVICE_E_INIT2]

SEVERITY: ERROR
DESCRIPTION: II Version stamp %d was expected to be %d.
CAUSE: The version stamp that the dmOutputDevice 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_OUTPUTDEVICE_E_FORMAT_NOT_SUPPORTED]

SEVERITY: ERROR
DESCRIPTION: S The document format %s is not support.
CAUSE: Server failed to generate a ticket for the specified user
ACTION: Report the error to the sysadmin, check user credentials
PARAMS:

ERROR: [DM_OUTPUTDEVICE_E_APPLY2]

SEVERITY: ERROR
DESCRIPTION: ApplyForString unexpectedly returned invalid.
CAUSE: Unknown.
ACTION: Carefully record this error message and any parameters and contact your Documentum Site Administrator.
PARAMS:

ERROR: [DM_OUTPUTDEVICE_E_ASSUME_USR_RET]

SEVERITY: ERROR
DESCRIPTION: I Unable to complete the print request an error was returned from the assume user process: %d
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_OUTPUTDEVICE_E_PCLOSE]

SEVERITY: ERROR
DESCRIPTION: I An unexpected system error %d occurred during pclose.
CAUSE: Unknown.
ACTION: Carefully record this error message and any parameters and contact your Documentum Site Administrator.
PARAMS:

ERROR: [DM_OUTPUTDEVICE_E_NONEXISTENT]

SEVERITY: ERROR
DESCRIPTION: S Outputdevice with %s object_name does not exist.
CAUSE: User specified an invalid output device.
ACTION: Specify a valid output device object_name.
PARAMS:

ERROR: [DM_OUTPUTDEVICE_E_INIT1]

SEVERITY: ERROR
DESCRIPTION: The dmOutputDevice type was found in the database without a version stamp.
CAUSE: Unknown.
ACTION: Carefully record this error message and any parameters and contact your Documentum Site Administrator.
PARAMS:

ERROR: [DM_OUTPUTDEVICE_E_COPY_TO_COMMON]

SEVERITY: ERROR
DESCRIPTION: Unable to complete the print request due to an error during the file copy to the common area
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_OUTPUTDEVICE_E_OS_ERROR]

SEVERITY: ERROR
DESCRIPTION: SS An error was returned by the operating system during the processing of the request. OS API: %s returned error: %s
CAUSE: Unknown: it is a function of the command given
ACTION: Check your configuration and/or operating system.
PARAMS:

ERROR: [DM_OUTPUTDEVICE_W_ACTION_UNSUPPORTED]

SEVERITY: WARNING
DESCRIPTION: SS The specified action %s is not supported on this platform %s.
CAUSE: The specified action has no meaning or support on the given platform
ACTION: Refer to documentation to see if this is a supported action
PARAMS:

ERROR: [DM_OUTPUTDEVICE_W_SUB1]

SEVERITY: WARNING
DESCRIPTION: An error occurred attempting to transform and save the content rendition in postscript.
CAUSE: Unknown.
ACTION: Refer to the next error message in the message queue for a description of why the transformation failed.
PARAMS:

nahoru

DM_PLATFORM

ERROR: [DM_PLATFORM_E_INTEGER_CONVERSION_ERROR]

SEVERITY: ERROR
DESCRIPTION: S The server was unable to convert the following string (%s) to an integer or long.
CAUSE: It may be that the string was not in the range of valid integers of -2147483647 and 2147483647
ACTION: If the integer is out of range, you may need to use a double datatype if possible. Otherwise you should try a smaller integer value.
PARAMS:

ERROR: [DM_PLATFORM_E_SYSTEM_INFO]

SEVERITY: ERROR
DESCRIPTION: S An error occured when calling the Operating System: %s
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_PLATFORM_E_STACK_OPERATION_INCONSISTENCE]

SEVERITY: ERROR
DESCRIPTION: SI Stack operation inconsistency found in File %s, line %d.
CAUSE: Internal error.
ACTION: Contact technical support. dmPolicy class errors
PARAMS:

ERROR: [DM_PLATFORM_E_MEMORY_EXHAUSTED]

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

nahoru

DM_POLICY

ERROR: [DM_POLICY_F_INIT3]

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

ERROR: [DM_POLICY_F_INIT2]

SEVERITY: FATAL
DESCRIPTION: II Version stamp %d was expected to be %d.
CAUSE: The version stamp that the dm_policy 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_POLICY_F_INT1]

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

ERROR: [DM_POLICY_F_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_POLICY_F_AS_INIT2]

SEVERITY: FATAL
DESCRIPTION: II Version stamp %d was expected to be %d.
CAUSE: The version stamp that the dm_alias_set 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_POLICY_F_INIT1]

SEVERITY: FATAL
DESCRIPTION: The dm_policy 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_POLICY_F_AS_INIT1]

SEVERITY: FATAL
DESCRIPTION: The dm_alias_set 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_POLICY_F_AS_INIT3]

SEVERITY: FATAL
DESCRIPTION: The type manager returned an error storing the dm_alias_set 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_POLICY_F_TYPE_CONVERSION]

SEVERITY: FATAL
DESCRIPTION: I Failed to convert type dm_policy to version %d.
CAUSE: Type conversion failed.
ACTION: Report this message and any parameters to your Documentum Site Representative.
PARAMS: The first parameter is the version stamp we are trying to upgrade to.

ERROR: [DM_POLICY_F_TYPE_CONVERSION_QUERY_FAILURE]

SEVERITY: FATAL
DESCRIPTION: SI The following database error occurred:%s. Attempt to upgrade dm_policy type to version %d failed.
CAUSE: A query failed during an attempt to upgrade dm_policy.
ACTION: Report this message along with the error from the database to your Documentum Site Representative.
PARAMS: The first parameter is the database error. The second parameter is the dm_policy version stamp we were trying to upgrade to. $Id: dmpom.e,v 5.4 2001/01/23 20:28:18 xtang Exp $ dmObjectManager class errors

ERROR: [DM_POLICY_E_AS_ALIAS_NAME_NOT_UNIQUE]

SEVERITY: ERROR
DESCRIPTION: SSII The alias name %s in alias set %s is defined at positions %d and %d.
CAUSE: Tried to create an alias that already exists in the same alias set.
ACTION: Try again with a different alias name.
PARAMS:

ERROR: [DM_POLICY_E_AS_EMPTY_NAME]

SEVERITY: ERROR
DESCRIPTION: The alias set has no name.
CAUSE: You have provided an alias set without a name.
ACTION: Supply a name for the alias set.
PARAMS:

ERROR: [DM_POLICY_E_ERROR_1013]

SEVERITY: ERROR
DESCRIPTION: SS Unable to set the objects ACL to %s. Details:%s
CAUSE: The Internal Action Proc failed to set the objects ACL.
ACTION: Check the details.
PARAMS:

ERROR: [DM_POLICY_E_NO_EXCP_STATE]

SEVERITY: ERROR
DESCRIPTION: DS The dm_policy object identified by %s does not have an exception state defined for state %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_POLICY_E_AS_EMPTY_ALIAS_NAME]

SEVERITY: ERROR
DESCRIPTION: SI Cannot assign an empty alias name to alias set %s at position %d.
CAUSE: You have provided an empty alias name.
ACTION: Supply a name at the specified position.
PARAMS:

ERROR: [DM_POLICY_E_BAD_STATE_CHAIN]

SEVERITY: ERROR
DESCRIPTION: D The policy object identified by %s has loops.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_POLICY_E_INVALID_ALIAS_SET_NAME]

SEVERITY: ERROR
DESCRIPTION: SD Invalid alias set name %s of policy %s specified.
CAUSE: You tried to use an invalid alias set name.
ACTION: Retry with a valid alias set name.
PARAMS:

ERROR: [DM_POLICY_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_POLICY_E_MUST_SAVE]

SEVERITY: ERROR
DESCRIPTION: D Changes to the sysobject (%s) must be saved or reverted first.
CAUSE: This error occured when user is doing promote, demote, attach, suspend, or resume on a new or modified object.
ACTION: User has to save or revert the change before doing any of the action described above.
PARAMS:

ERROR: [DM_POLICY_E_BAD_USERPOSTPROC_TYPE]

SEVERITY: ERROR
DESCRIPTION: DSDS The policy identified by %s has an invalid user-defined post-processing object %s:%s specified for state %s.
CAUSE: The object is of wrong type.
ACTION:
PARAMS:

ERROR: [DM_POLICY_E_ERROR_1015]

SEVERITY: ERROR
DESCRIPTION: SSS Unable to post a request to render the document in %s format using Autorender for %s. Details:%s
CAUSE: The Internal Action Proc failed to invoke Autorender for creating a new rendition for a document.
ACTION: Check the details.
PARAMS:

ERROR: [DM_POLICY_E_ERROR_1007]

SEVERITY: ERROR
DESCRIPTION: SS Unable to add symbolic label:%s. Details:%s
CAUSE: The Internal Action Proc failed to add symbolic label.
ACTION: Check the details.
PARAMS:

ERROR: [DM_POLICY_E_METHOD_TIMEOUT]

SEVERITY: ERROR
DESCRIPTION: SI The method (%s) timeout before the action procedure could finish. The method timeout is currently set to %d.
CAUSE: This error occured when the action procedure takes longer time to finish. If the time exceeds the method timeout length, this error will occur.
ACTION: Set the timeout_default attribute of the method to a greater value. If timeout_default is set to more than 5 minutes, you may need to set client_session_timeout in server.ini accordingly.
PARAMS:

ERROR: [DM_POLICY_E_ERROR_1010]

SEVERITY: ERROR
DESCRIPTION: SS Unable to link object to location:%s. Details:%s
CAUSE: The Internal Action Proc failed to link object to location.
ACTION: Check the details.
PARAMS:

ERROR: [DM_POLICY_E_BAD_RESULT_ID]

SEVERITY: ERROR
DESCRIPTION: D The dm_bp_transition returns an invalid ID %s.
CAUSE: Internal error.
ACTION:
PARAMS:

ERROR: [DM_POLICY_E_FAILED_CREATE_STATE_EXT_OBJ]

SEVERITY: ERROR
DESCRIPTION: D Failed to create new dm_state_extension object for the document lifecycle (%s).
CAUSE: Problem with dm_relation or dm_state_extension type.
ACTION: Contact Documentum Tech Support.
PARAMS:

ERROR: [DM_POLICY_E_ERROR_1005]

SEVERITY: ERROR
DESCRIPTION: SSSS Unable to add value:%s to attribute:%s at position %s. Details:%s
CAUSE: The Internal Action Proc failed to add value to attribute.
ACTION: Check the details.
PARAMS:

ERROR: [DM_POLICY_E_BAD_USERACTION_TYPE]

SEVERITY: ERROR
DESCRIPTION: DSDS The policy identified by %s has an invalid user-defined action object %s:%s specified for state %s.
CAUSE: The object is of wrong type.
ACTION:
PARAMS:

ERROR: [DM_POLICY_E_BAD_TYPE_ATTRC]

SEVERITY: ERROR
DESCRIPTION: SSII In policy named %s, count of %s: %d does not match the count of included_type: %d.
CAUSE: Tried to save a policy with inconsistent number of included_type and include_subtypes.
ACTION: NONE.
PARAMS:

ERROR: [DM_POLICY_E_CANT_FIND_PROC_OBJ]

SEVERITY: ERROR
DESCRIPTION: SDS Cant find the %s procedure with id (%s) and version (%s).
CAUSE: No object can be found with the matching version label.
ACTION: Make sure that version has the correct value and id points to the chronicle id.
PARAMS:

ERROR: [DM_POLICY_E_CURSOR_ERROR]

SEVERITY: ERROR
DESCRIPTION: S A database error has occurred during the creation of a cursor (%s).
CAUSE: A SQL statement that queries the Documentum schema has failed. This error message indicates that a failure occurred during the parsing of the generated SQL statement by the underlying RDBMS.
ACTION: The error message from the RDBMS is shown in the message. Use that error message to figure out what has happened.
PARAMS:

ERROR: [DM_POLICY_E_ERROR_1002]

SEVERITY: ERROR
DESCRIPTION: SSSS Unable to set attribute:%s to value:%s at position %s. Deatils:%s
CAUSE: The Internal Action Proc failed to set value to attribute.
ACTION: Check the details.
PARAMS:

ERROR: [DM_POLICY_E_BAD_RESULT_CONTENT]

SEVERITY: ERROR
DESCRIPTION: DS The dm_bp_transition returns a document (ID=%s) either without content or bad content (%s).
CAUSE: Internal error.
ACTION:
PARAMS:

ERROR: [DM_POLICY_E_INVALID_MOVE_POS]

SEVERITY: ERROR
DESCRIPTION: III In movestate API, the old/new position (%d/%d) needs to be positive and less than (or equal to) the number of states (%d).
CAUSE: User has specified either an invalid old position or an invalid new position.
ACTION: Make sure both the old and new positions are in the right range.
PARAMS:

ERROR: [DM_POLICY_E_NO_NORMAL_STATE]

SEVERITY: ERROR
DESCRIPTION: D The policy identified by %s has no normal state. CASUE: A valid policy must have at least one normal state.
CAUSE:
ACTION: Add a normal state to this policy.
PARAMS:

ERROR: [DM_POLICY_E_BAD_RESULT_STATUS]

SEVERITY: ERROR
DESCRIPTION: DS Document %s has no content, but the status is bad (%s).
CAUSE: The dm_bp_transition encounters errors while processing the criteria and actions. However, the error message does not get stored in the content of the result document.
ACTION: Check the $DM_HOME/bin/dm_bp_transition.out for detailed error message.
PARAMS:

ERROR: [DM_POLICY_E_ERROR_1001]

SEVERITY: ERROR
DESCRIPTION: SSS Unable to set attribute:%s to value:%s. Details:%s
CAUSE: The Internal Action Proc failed to set value to attribute.
ACTION: Check the details.
PARAMS:

ERROR: [DM_POLICY_E_INVALID_STATE_NAME]

SEVERITY: ERROR
DESCRIPTION: SD Invalid state name %s of policy %s specified.
CAUSE: You tried to use an invalid state name.
ACTION: Retry with a valid state name.
PARAMS:

ERROR: [DM_POLICY_E_AS_PRIVILEGES_OWNER]

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

ERROR: [DM_POLICY_E_INVALID_ATCH_TYPE]

SEVERITY: ERROR
DESCRIPTION: S The attached type %s is not a valid docbase type.
CAUSE: The specified type does not exist in docbase.
ACTION: Make sure the specified type exists in docbase.
PARAMS:

ERROR: [DM_POLICY_E_NO_ATTACH_STATE]

SEVERITY: ERROR
DESCRIPTION: D The policy identified by %s does not have any attachable state.
CAUSE: A valid policy must have at least one attachable state, normal or exception.
ACTION: Add an attachable state to this policy.
PARAMS:

ERROR: [DM_POLICY_E_BAD_RESULT_ERROR_2]

SEVERITY: ERROR
DESCRIPTION: SSSSSS The BP Logfile (%s) has illegal error format ([ErrorCode]=%s,[Parameter]=%s,[Parameter]=%s,[Parameter]=%s,[ServerError]=%s.
CAUSE: Error reported by dm_bp_transition needs to follow the following format: [ErrorCode] [Parameter] [Parameter] [Parameter] [ServerError] The number of parameters may vary depending on the error code. The keywords within the square bracket are case-sensitive. The legal range of is between 1000 and 1015.
ACTION: Make sure the error follow the format.
PARAMS:

ERROR: [DM_POLICY_E_REMOVE_NO_STATE]

SEVERITY: ERROR
DESCRIPTION: D Policy object %s has no state to be removed.
CAUSE: You tried to remove a state from an empty policy object.
ACTION: N/A
PARAMS:

ERROR: [DM_POLICY_E_SET_OVERR_BAD_STATE]

SEVERITY: ERROR
DESCRIPTION: DS You cannot set the type_override attribute because dm_polict %s does not have a state named %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_POLICY_E_DEFAULT_POLICY_ID]

SEVERITY: ERROR
DESCRIPTION: DS The policy object with id %s is the default_policy_id for type %s. In order to destroy the policy, you must first modify the data dictionary for type and set the default_policy_id to another valid policy object or NULL.
CAUSE: An attempt has been to expunge a policy object even though it is still linked to the specified type as the default_policy_id
ACTION: You must first modify the data dictionary for the specified type and set the default_policy_id to a valid policy object or NULL.
PARAMS:

ERROR: [DM_POLICY_E_BAD_USERPOSTPROC]

SEVERITY: ERROR
DESCRIPTION: DDS The policy identified by %s has an invalid user-defined post-processing object id %s specified for state %s.
CAUSE: The object does not exist.
ACTION:
PARAMS:

ERROR: [DM_POLICY_E_AS_INVALID_ID]

SEVERITY: ERROR
DESCRIPTION: DS Invalid alias set object ID %s found for %s.
CAUSE: Cannot fetch the alias set with the given object id.
ACTION: Try again with the correct id.
PARAMS:

ERROR: [DM_POLICY_E_INVALID_EXCP_NAME]

SEVERITY: ERROR
DESCRIPTION: SDS The state %s defined for dm_policy %s has an invalid exception state %s.
CAUSE: The exception state defined for the normal state does not exist.
ACTION: Add the execption state to the policy object.
PARAMS:

ERROR: [DM_POLICY_E_BAD_USERPOSTPROCSERVICE]

SEVERITY: ERROR
DESCRIPTION: DSS The policy identified by %s has an invalid user-defined post-processing service %s specified for state %s.
CAUSE: The object does not exist.
ACTION:
PARAMS:

ERROR: [DM_POLICY_E_ERROR_1600]

SEVERITY: ERROR
DESCRIPTION: S The User Actions Proc failed. Details:%s
CAUSE: The User Actions Proc failed due to the error described in Details.
ACTION: Check the details.
PARAMS:

ERROR: [DM_POLICY_E_BAD_OVERRIDE]

SEVERITY: ERROR
DESCRIPTION: DDS The policy identified by %s has an invalid type_overwide %s specified for state %s.
CAUSE: NONE
ACTION:
PARAMS:

ERROR: [DM_POLICY_E_ERROR_1012]

SEVERITY: ERROR
DESCRIPTION: SS Unable to move object to location:%s. Details:%s
CAUSE: The Internal Action Proc failed to move object to location.
ACTION: Check the details.
PARAMS:

ERROR: [DM_POLICY_E_CANT_DESTROY]

SEVERITY: ERROR
DESCRIPTION: D Cannot destroy policy identified by %s since its state is installed or currently referenced by some sysobject. CASUE: You cannot destroy a policy if the definition state is INSTALLED. You must unistall the policy first. If the definition state is not INSTALLED, but the policy is referenced by some sysobject, you must be superuser and use force_flag = T to detroy this policy.
CAUSE:
ACTION: You may need to unistall the policy and set force_flag to True.
PARAMS:

ERROR: [DM_POLICY_E_BAD_OVERRIDE_TYPE]

SEVERITY: ERROR
DESCRIPTION: DSDS The policy identified by %s has an invalid type_overwide object %s:%s specified for state %s.
CAUSE: NONE
ACTION:
PARAMS:

ERROR: [DM_POLICY_E_BAD_USERACTIONSERVICE]

SEVERITY: ERROR
DESCRIPTION: DSS The policy identified by %s has an invalid user-defined action service %s specified for state %s.
CAUSE: The object does not exist.
ACTION:
PARAMS:

ERROR: [DM_POLICY_E_OPEN_LOG_FAILURE]

SEVERITY: ERROR
DESCRIPTION: SS Error opening file (%s). Operating System error: (%s).
CAUSE: Attempt to open the named file failed. The operating system error should give a better indication of the actual problem.
ACTION: Check if the indicated file exists check permissions to open or create the file.
PARAMS:

ERROR: [DM_POLICY_E_ERROR_1800]

SEVERITY: ERROR
DESCRIPTION: S The Action failed. Details:%s
CAUSE: The System Actions Proc failed due to the error described in Details.
ACTION: Check the details.
PARAMS:

ERROR: [DM_POLICY_E_ERROR_0001]

SEVERITY: ERROR
DESCRIPTION: S Dmbasic error. Details:%s
CAUSE: There exists some dmbasic error in users script.
ACTION: Check the details.
PARAMS:

ERROR: [DM_POLICY_E_INCONSISTENT_JAVA_DOCBASIC]

SEVERITY: ERROR
DESCRIPTION: DSSS The policy identified by %s cannot define a value for attribute %s for state %s when java_methods is set to %s.
CAUSE: The attribute java_methods is set to F and one of the atttributes user_entry_service, user_action_service, or user_postprocessing_service has a defined value. Or, the attribute java_methods is set T and one of the atttributes user_criteria_id, user_action_id, or user_postproc_id has a defined value.
ACTION: If the policy is using java services, java_methods must be set to T. A policy must use only docbasic procedures or java services but not both.
PARAMS:

ERROR: [DM_POLICY_E_INVALID_ALIAS_SET_INDEX]

SEVERITY: ERROR
DESCRIPTION: SD Invalid alias set index %s of policy %s specified.
CAUSE: You tried to use an invalid alias set index.
ACTION: Retry with a valid alias set index.
PARAMS:

ERROR: [DM_POLICY_E_BAD_STATE_ATTRC]

SEVERITY: ERROR
DESCRIPTION: SSII In policy named %s, count of %s: %d does not match the count of state number: %d.
CAUSE: Tried to save a policy with invalid state attribute count.
ACTION: Most likely the user tried to manipulate state attributes with append or insert or remove methods instead of appendstate, insertstate or removestate
PARAMS:

ERROR: [DM_POLICY_E_FAILED_TICKET]

SEVERITY: ERROR
DESCRIPTION: SSD Failed to generate a ticket for %s to execute %s operation on object %s
CAUSE: A ticket has failed to be generated for executing the user-specified operation on the object.
ACTION:
PARAMS:

ERROR: [DM_POLICY_E_NOT_VALIDATED]

SEVERITY: ERROR
DESCRIPTION: D Cannot install a business %s which is not validated.
CAUSE: User tried to install a dm_policy object which has not been validated.
ACTION: Run validate API to validate the object, then re-run install.
PARAMS:

ERROR: [DM_POLICY_E_NEED_PRIMARY_TYPE]

SEVERITY: ERROR
DESCRIPTION: You must set the primary type (i.e. included_type[0]) for this policy object.
CAUSE: Every business policy object must associate with at least a type. The included_type[0] stores the primary type. Other values represents the subtypes of the primary type.
ACTION: set included_type[0] to a valid type name.
PARAMS:

ERROR: [DM_POLICY_E_BAD_ACTION]

SEVERITY: ERROR
DESCRIPTION: DDS The policy identified by %s has an invalid action object id %s specified for state %s.
CAUSE: The object does not exist.
ACTION:
PARAMS:

ERROR: [DM_POLICY_E_NO_INSTALLED_SAVE]

SEVERITY: ERROR
DESCRIPTION: You cannot save an INSTALLED policy object with changes related to policy definition.
CAUSE: User tried to save one of the following changes to an installed policy object: (1) policy-specific attributes excluding state_description, allow_attach, allow_schedule, and return_to_base, (2) position of a state within the policy, (3) adding new states, and (4) deleting existing states.
ACTION: Uninstall the policy object first.
PARAMS:

ERROR: [DM_POLICY_E_BAD_STATE]

SEVERITY: ERROR
DESCRIPTION: DS The dm_policy object identified by %s does not have a state named %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_POLICY_E_ERROR_1011]

SEVERITY: ERROR
DESCRIPTION: SS Unable to unlink object from location:%s. Details:%s
CAUSE: The Internal Action Proc failed to unlink object from location.
ACTION: Check the details.
PARAMS:

ERROR: [DM_POLICY_E_BAD_USERENTRY]

SEVERITY: ERROR
DESCRIPTION: DDS The policy identified by %s has an invalid user-defined entry criteria id %s specified for state %s.
CAUSE: The object does not exist.
ACTION:
PARAMS:

ERROR: [DM_POLICY_E_NO_ROUTER_BP]

SEVERITY: ERROR
DESCRIPTION: S The attached type %s can not be dm_router, dm_policy, or their subtypes.
CAUSE: Types dm_router and dm_policy, and their subtypes are not allowed to be in the included_type.
ACTION: Make sure the specified type is not dm_router, dm_policy, or their subtype.
PARAMS:

ERROR: [DM_POLICY_E_PRIVILEGES]

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

ERROR: [DM_POLICY_E_INVALID_ATCH_SUBTYPE]

SEVERITY: ERROR
DESCRIPTION: SS The attached type %s is not a subtype of %s.
CAUSE: The specified subtype is not a subtype of the primary type.
ACTION: Only specify subtypes of the primary type in positions greater than zero.
PARAMS:

ERROR: [DM_POLICY_E_BP_OWNER_BATCH_PROMTE]

SEVERITY: ERROR
DESCRIPTION: It is not allowed to specify lifecycle_owner (in a_bpaction_run_as of docbase_config) to run the lifecycle actions.
CAUSE: a_bpaction_run_as of docbase_config is set to lifecycle_owner.
ACTION: Set a_bpaction_run_as to a differnt value.
PARAMS:

ERROR: [DM_POLICY_E_LAUNCH_BAD_STATE]

SEVERITY: ERROR
DESCRIPTION: DS Cannot evaluate the entry_criteria/action of dm_policy %s because the state %s does not exist.
CAUSE: The state name does not exist in the policy.
ACTION: Internal error.
PARAMS:

ERROR: [DM_POLICY_E_BAD_USERACTION]

SEVERITY: ERROR
DESCRIPTION: DDS The policy identified by %s has an invalid user-defined action object id %s specified for state %s.
CAUSE: The object does not exist.
ACTION:
PARAMS:

ERROR: [DM_POLICY_E_BAD_STATE_NAME]

SEVERITY: ERROR
DESCRIPTION: S The specified state name %s either is empty, or does not start with letter, or contains :, ., or ,.
CAUSE: User does not follow the naming convention for a state name.
ACTION: Change the state name so that the following rules are satisfied: (1) It starts with a letter. (2) It does not contain :, ., or ,.
PARAMS:

ERROR: [DM_POLICY_E_GET_OVERR_BAD_STATE]

SEVERITY: ERROR
DESCRIPTION: DS You cannot get the type_override value due to that dm_policy %s does not have a state named %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_POLICY_E_BAD_USERENTRYSERVICE]

SEVERITY: ERROR
DESCRIPTION: DSS The policy identified by %s has an invalid user-defined entry criteria service %s specified for state %s.
CAUSE: The object does not exist.
ACTION:
PARAMS:

ERROR: [DM_POLICY_E_BAD_ENTRY_TYPE]

SEVERITY: ERROR
DESCRIPTION: DSDS The policy identified by %s has an invalid entry criteria %s:%s specified for state %s.
CAUSE: The object type is not DM_EXPRESSION.
ACTION:
PARAMS:

ERROR: [DM_POLICY_E_AS_REF_INSTALLED_BP]

SEVERITY: ERROR
DESCRIPTION: SI The alias set %s is referenced by %d installed Business Policy objects.
CAUSE: An alias set object is not changeable if it is referenced by installed Business Policy objects.
ACTION: Uninstall those Business Policy objects.
PARAMS:

ERROR: [DM_POLICY_E_EXIST_NO_BP_LOG]

SEVERITY: ERROR
DESCRIPTION: S BP Log (%s) was not created.
CAUSE: Its either script error or system error that causes this problem.
ACTION: Make sure that the hard disk is not full. Also look into server log for error messages that result from scripting error.
PARAMS:

ERROR: [DM_POLICY_E_BAD_ACTION_TYPE]

SEVERITY: ERROR
DESCRIPTION: DSDS The policy identified by %s has an invalid action object %s:%s specified for state %s.
CAUSE: The object type is not DM_PROCEDURE.
ACTION:
PARAMS:

ERROR: [DM_POLICY_E_NO_POLICY_METHOD]

SEVERITY: ERROR
DESCRIPTION: S Cannot find the method %s, which is needed to evaluate an entry criteria and/or to execute an action of a business policy.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_POLICY_E_AS_ILLEGAL_NAME]

SEVERITY: ERROR
DESCRIPTION: S The alias set contains illegal symbols in the name (%s).
CAUSE: You have provided an alias set with illegal symbols like . in the name.
ACTION: Remove the illegal symbols.
PARAMS:

ERROR: [DM_POLICY_E_INVALID_EXCP_TYPE]

SEVERITY: ERROR
DESCRIPTION: SSD The exception state %s of %s for dm_policy %s is a normal state.
CAUSE: The exception state defined is identified as a normal state in its state_class.
ACTION: Change the state_class value of the exception state to 1.
PARAMS:

ERROR: [DM_POLICY_E_ERROR_0010]

SEVERITY: ERROR
DESCRIPTION: S BP transition script error. Details:%s
CAUSE: There exists some error in the BP transition script.
ACTION: Check the details.
PARAMS:

ERROR: [DM_POLICY_E_BAD_LABEL]

SEVERITY: ERROR
DESCRIPTION: DS There is no policy object with chronincle ID %s and version label %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_POLICY_E_BAD_USERENTRY_TYPE]

SEVERITY: ERROR
DESCRIPTION: DSDS The policy identified by %s has an invalid user-defined entry criteria %s:%s specified for state %s.
CAUSE: The object is of wrong type.
ACTION:
PARAMS:

ERROR: [DM_POLICY_E_NON_ATTACH_STATE]

SEVERITY: ERROR
DESCRIPTION: SD The state %s you tried to attach is not an attachable state of policy %s. CASUE: The is_attachable attribute is not set to T for this policy state.
CAUSE:
ACTION: Try to attach to other states.
PARAMS:

ERROR: [DM_POLICY_E_ERROR_1000]

SEVERITY: ERROR
DESCRIPTION: SS Unable to load the procedure:%s. Details:%s
CAUSE: The Internal Action Proc failed to load the specified procedure.
ACTION: Check the details.
PARAMS:

ERROR: [DM_POLICY_E_INVALID_STATE_INDEX]

SEVERITY: ERROR
DESCRIPTION: SD Invalid state index %s of policy %s specified.
CAUSE: You tried to use an invalid state index.
ACTION: Retry with a valid state index.
PARAMS:

ERROR: [DM_POLICY_E_AS_NAME_NOT_UNIQUE]

SEVERITY: ERROR
DESCRIPTION: S Cannot create the %s alias set since it already exists.
CAUSE: Tried to create an alias set that already exists. All alias set names are unique.
ACTION: Try again with a different alias set name.
PARAMS:

ERROR: [DM_POLICY_E_AS_NO_ALIAS_SET_POLICY]

SEVERITY: ERROR
DESCRIPTION: SSD No default alias set found for user %s under policy %s (ID = %s).
CAUSE: Tried to find a default alias set for a user under a specified policy.
ACTION: Make sure a default alias set is specified in one of the following: (1) sessionconfig, (2) the session users dm_user object, (3) dm_server_config, and (4) the specified policy object.
PARAMS:

ERROR: [DM_POLICY_E_NOT_INCLUDED_TYPE]

SEVERITY: ERROR
DESCRIPTION: DS dm_policy object identified by %s does not have %s as one of its valid attachable type.
CAUSE: included_type[] does not contain the object type which has tried to attach to this policy.
ACTION: the policy designer must add the type to included_type[], and try again
PARAMS:

ERROR: [DM_POLICY_E_ERROR_1003]

SEVERITY: ERROR
DESCRIPTION: SSS Unable to remove value:%s from attribute:%s. Details:%s
CAUSE: The Internal Action Proc failed to remove value from attribute.
ACTION: Check the details.
PARAMS:

ERROR: [DM_POLICY_E_ERROR_2100]

SEVERITY: ERROR
DESCRIPTION: S Validation procedure detected error in the lifecycle. Details: %s
CAUSE: The dm_bp_validation method detected error.
ACTION: Check the details in the error message.
PARAMS:

ERROR: [DM_POLICY_E_ERROR_2000]

SEVERITY: ERROR
DESCRIPTION: S Unable to set application_code to dm_all_applications. Details: %s
CAUSE: The business policy method was unable to set the application_code to dm_all_applications
ACTION: Check the details in the error message.
PARAMS:

ERROR: [DM_POLICY_E_UNIQUE_STATE_NAME]

SEVERITY: ERROR
DESCRIPTION: SD The state name %s within dm_policy %s must be unique.
CAUSE: the state name is not unique within a dm_policy.
ACTION: rename the duplicate one.
PARAMS:

ERROR: [DM_POLICY_E_OPER_FROM_EXCEPTION]

SEVERITY: ERROR
DESCRIPTION: SSD It is not allowed to %s on the document %s(%s) from the exception state.
CAUSE: The object is in an exception state. It is not allowed to promote or demote from this state.
ACTION: Perform resume operation on the object to bring it back to a normal state.
PARAMS:

ERROR: [DM_POLICY_E_AS_NO_ALIAS_SET]

SEVERITY: ERROR
DESCRIPTION: SS No value is found in alias set (%s) for resolving alias %s.
CAUSE: Tried to resolve an alias which does not exist in the specified alias set.
ACTION: Try to define at least one alias set which consists of the aliase in question in dm_alias_set and set up the session alias set, user alias set, system alias set appropriately.
PARAMS:

ERROR: [DM_POLICY_E_AS_PRIVILEGES]

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

ERROR: [DM_POLICY_E_AS_NAME_VALUE_NOT_MATCHED]

SEVERITY: ERROR
DESCRIPTION: IIS The alias_name count (%d) and alias_value count (%d) of alias set %s are not matched.
CAUSE: The alias set object has a mis-matched alias name and alias value.
ACTION: Make sure the numbers of alias_name and alias_value are equivalent.
PARAMS:

ERROR: [DM_POLICY_E_INVALID_ARG]

SEVERITY: ERROR
DESCRIPTION: SSS The method %s has invalid value (%s) for argument %s.
CAUSE: Argument has invalid value.
ACTION: Make sure that all required arguments are correctly specified.
PARAMS: S – name of the method. S – value of the arguemnt. S – name of the argument.

ERROR: [DM_POLICY_E_NOT_A_POLICY]

SEVERITY: ERROR
DESCRIPTION: D The policy identified by %s is not a dm_policy object.
CAUSE:
ACTION: NONE.
PARAMS:

ERROR: [DM_POLICY_E_READ_LOG_FAILURE]

SEVERITY: ERROR
DESCRIPTION: SS Error reading file (%s). Operating System error: (%s).
CAUSE: A failure occurred while reading content from an open content file. The operating system error should give a better indication of the actual problem.
ACTION: Check if the indicated file exists check permissions to open or create the file.
PARAMS:

ERROR: [DM_POLICY_E_BAD_RESULT_ERROR]

SEVERITY: ERROR
DESCRIPTION: DSSSSS Document %s has illegal error format ([ErrorCode]=%s,[Parameter]=%s,[Parameter]=%s,[Parameter]=%s,[ServerError]=%s.
CAUSE: Error reported by dm_bp_transition needs to follow the following format: [ErrorCode] [Parameter] [Parameter] [Parameter] [ServerError] The number of parameters may vary depending on the error code. The keywords within the square bracket are case-sensitive. The legal range of is between 1000 and 1015.
ACTION: Make sure the error follow the format.
PARAMS:

ERROR: [DM_POLICY_E_ERROR_1008]

SEVERITY: ERROR
DESCRIPTION: SS Unable to remove symbolic label:%s. Details:%s
CAUSE: The Internal Action Proc failed to remove symbolic label.
ACTION: Check the details.
PARAMS:

ERROR: [DM_POLICY_E_AS_NO_ALIAS_SET_USER]

SEVERITY: ERROR
DESCRIPTION: S No default alias set found for user %s. The following alias sets were searched: sessionconfig, user, users default group, server config, and policy (if applicable)
CAUSE: Tried to find a default alias set for a user.
ACTION: Make sure a default alias set is specified in one of the following: (1) sessionconfig, (2) the session users dm_user object, (3) the session users default group, (4) dm_server_config. (5) the first alias set defined in the policy, if exists. Note that if policy is involved, then the alias set found between 1 and 4 must be in the policys alias_set_ids attribute as well.
PARAMS:

ERROR: [DM_POLICY_E_AS_INVALID_NAME]

SEVERITY: ERROR
DESCRIPTION: SS Cannot find %s alias set for %s.
CAUSE: Cannot find the alias set with the given name. This may happen when fetching an alias set group by name during save, or destroy.
ACTION: Try again with the correct name.
PARAMS:

ERROR: [DM_POLICY_E_ERROR_1400]

SEVERITY: ERROR
DESCRIPTION: S The BP transition script failed due to deadlock. Details:%s
CAUSE: The BP transition script failed due to deadlock described in Details.
ACTION: Retry the action.
PARAMS:

ERROR: [DM_POLICY_E_AS_ILLEGAL_CATEGORY]

SEVERITY: ERROR
DESCRIPTION: I The alias set contains an illegal alias_category (%d).
CAUSE: You have provided an illegal alias_category. The following are legal categories: 0 (Unknown) 1 (User) 2 (Group) 3 (User or Group) 4 (Cabinet Path) 5 (Folder Path) 6 (ACL)
ACTION: Provide a legal category.
PARAMS:

ERROR: [DM_POLICY_E_BAD_USERVALIDATIONSERVICE]

SEVERITY: ERROR
DESCRIPTION: DS The policy identified by %s has an invalid user-defined validation service %s.
CAUSE: The object does not exist.
ACTION:
PARAMS:

ERROR: [DM_POLICY_E_ERROR_1004]

SEVERITY: ERROR
DESCRIPTION: SS Unable to remove all values from attribute:%s. Details:%s
CAUSE: The Internal Action Proc failed to remove all values from attribute.
ACTION: Check the details.
PARAMS:

ERROR: [DM_POLICY_E_ERROR_1900]

SEVERITY: ERROR
DESCRIPTION: S Batch Promote failed. Details:%s
CAUSE: The Batch Promote method failed when it tries to gather bp information, i.e getting procedure ids.
ACTION: Check the details.
PARAMS:

ERROR: [DM_POLICY_E_AS_NO_DEFAULT_ALIAS_SET]

SEVERITY: ERROR
DESCRIPTION: S No default alias set is allowed for resolving alias %s since the sysobject is attached to a policy without alias set.
CAUSE: Tried to resolve an alias on a sysobject attached to a policy without alias set.
ACTION: Try to provide an alias set in the alias or re-attach the sysobject to a policy with alias set.
PARAMS:

ERROR: [DM_POLICY_E_CONNECTION_ERROR]

SEVERITY: ERROR
DESCRIPTION: S Error connecting to docbase as user %s.
CAUSE: Invalid user name is used to connect to the docbase.
ACTION: Make sure that the user is a valid documentum user.
PARAMS:

ERROR: [DM_POLICY_E_ERROR_1006]

SEVERITY: ERROR
DESCRIPTION: SSS Unable to append value:%s to attribute:%s. Details:%s
CAUSE: The Internal Action Proc failed to append value to attribute.
ACTION: Check the details.
PARAMS:

ERROR: [DM_POLICY_E_ERROR_1500]

SEVERITY: ERROR
DESCRIPTION: S The User Entry Criteria Proc failed. Details:%s
CAUSE: The User Entry Criteria Proc failed due to the error described in Details.
ACTION: Check the details.
PARAMS:

ERROR: [DM_POLICY_E_BAD_ENTRY]

SEVERITY: ERROR
DESCRIPTION: DDS The policy identified by %s has an invalid entry criteria id %s specified for state %s.
CAUSE: The object does not exist.
ACTION:
PARAMS:

ERROR: [DM_POLICY_E_ERROR_1014]

SEVERITY: ERROR
DESCRIPTION: SS Unable to set %s as the owner of the object. Details:%s
CAUSE: The Internal Action Proc failed to set owner of an object.
ACTION: Check the details.
PARAMS:

ERROR: [DM_POLICY_I_ALREADY_IN_NORMAL]

SEVERITY: INFO
DESCRIPTION: S No need to resume the object since its current state %s is a normal state.
CAUSE:
ACTION: NONE.
PARAMS:

ERROR: [DM_POLICY_I_ALREADY_VALIDATED]

SEVERITY: INFO
DESCRIPTION: D The policy identified by %s is already in VALIDATED state.
CAUSE: This policy has not been modified since last validation.
ACTION: No need to validate this policy again until being modified.
PARAMS:

ERROR: [DM_POLICY_I_ALREADY_IN_EXCEP]

SEVERITY: INFO
DESCRIPTION: S No need to suspend the object since its current state %s is an exception state.
CAUSE:
ACTION: NONE.
PARAMS:

ERROR: [DM_POLICY_I_ALREADY_INSTALLED]

SEVERITY: INFO
DESCRIPTION: D The policy identified by %s has already been installed. No need to install again.
CAUSE:
ACTION: NONE.
PARAMS:

ERROR: [DM_POLICY_I_ALREADY_UNINSTALLED]

SEVERITY: INFO
DESCRIPTION: D The policy identified by %s is not installed. No need to uninstall again.
CAUSE:
ACTION: NONE.
PARAMS:

ERROR: [DM_POLICY_I_VALIDATE_INSTALLED]

SEVERITY: INFO
DESCRIPTION: D The policy identified by %s is in INSTALLED state. No need to validate it.
CAUSE: The policy has been validated and installed.
ACTION: There is no need to validate an INSTALLED policy.
PARAMS:

ERROR: [DM_POLICY_W_ACTION]

SEVERITY: WARNING
DESCRIPTION: null.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_POLICY_W_CAUSE]

SEVERITY: WARNING
DESCRIPTION: unknown.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_POLICY_W_WARN1]

SEVERITY: WARNING
DESCRIPTION: II This is a warning %d, %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_POLICY_W_REMOVE_REF]

SEVERITY: WARNING
DESCRIPTION: SD State-related changes have applied to %s (ID = %s) when there exist referencing sysobjects.
CAUSE: Some state-related changes have applied to a policy object when it has some referencing sysobjects.
ACTION: Check all the referencing sysobjects to see if they need to be re-attached.
PARAMS:

ERROR: [DM_POLICY_W_EMPTY_RESULT_CONTENT]

SEVERITY: WARNING
DESCRIPTION: DS The dm_bp_transition returns an empty document (%s) with status %s.
CAUSE: Internal error. However, the method seems to be launched O.K.
ACTION:
PARAMS:

ERROR: [DM_POLICY_W_ERROR_1700]

SEVERITY: WARNING
DESCRIPTION: S The User Post Processing Proc failed. Details:%s
CAUSE: The User Post Processing Proc failed due to the error described in Details.
ACTION: Check the details.
PARAMS:

nahoru

DM_QUERY

ERROR: [DM_QUERY_F_COMMIT_FAILED]

SEVERITY: FATAL
DESCRIPTION: S %s: An attempt to commit your statements changes to the database has failed, causing your statement to fail.
CAUSE: Another error message on the error queue will explain the exact clause of the failure. Your statement failed.
ACTION: Take whatever action is necessary according to the explanation in the other error message.
PARAMS: The parameter specifies the statement type that the error occurred in.

ERROR: [DM_QUERY_F_RESULT_NOT_SET_INT]

SEVERITY: FATAL
DESCRIPTION: I Unable to set the integer return value for this query: %d.
CAUSE: Another error message will have been set for this query. The other message, or messages, will contain information about the cause of this error.
ACTION: Examine the other error messages for this query, and take the appropriate action based upon those messages.
PARAMS:

ERROR: [DM_QUERY_F_NO_REG]

SEVERITY: FATAL
DESCRIPTION: SS %s: An unexpected error has occurred during a %s operation, causing your statement to fail.
CAUSE: Your statement has failed due to an error in a facility which the query facility called.
ACTION: There is another message on the error queue which describes the cause of the failure. Follow whatever instructions are contained in that message to correct the failure, and retry your query.
PARAMS: The first parameter contains the statement type of the query that failed. The second parameter gives the name of the called function in which the failure occurred.

ERROR: [DM_QUERY_F_TRAN_COMMIT_FAILED]

SEVERITY: FATAL
DESCRIPTION: COMMIT: Your commit transaction statement failed.
CAUSE: Unknown. There may be another message on the queue that sheds light on the reason for the failure. The most likely reason is that an RDBMS error has occurred.
ACTION: Examine any other error messages for your session, and do whatever they suggest. If all else fails, retry the commit. If that fails, abort the transaction.
PARAMS:

ERROR: [DM_QUERY_F_CURSOR_CREATE]

SEVERITY: FATAL
DESCRIPTION: SELECT: Unable to create the SQL cursor to represent this DQL query.
CAUSE: An attempt to create the SQL cursor representing your query failed. This is an unexpected condition, and there will not be an accompanying error message to explain the reason. The most probably reason for this type of error is lack of memory.
ACTION: Try the query again. If it continues to fail, a call to Documentum tech support may be required.
PARAMS: None.

ERROR: [DM_QUERY_F_SET_FAILED_SS]

SEVERITY: FATAL
DESCRIPTION: SSSS %s: Unable to set this attribute (%s) with this value (%s %s).
CAUSE: This is an internal error.
ACTION: Collect all the error messages that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the function in which the error occurred. The second parameter is the name of an attribute which could not be set. The third and fourth parameters are the string value which could not be set.

ERROR: [DM_QUERY_F_DATABASE_ERROR]

SEVERITY: FATAL
DESCRIPTION: SS %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 Documentum function in which the error occurred. The second parameter contains the error message from the RDBMS.

ERROR: [DM_QUERY_F_CHANGE_CONTENT_SAVE]

SEVERITY: FATAL
DESCRIPTION: S CHANGE: An unexpected save error has occurred on content object (%s). Please check for any accompanying error messages.
CAUSE: An unexpected error occurred during the content save step.
ACTION: There will be additional error messages with this one. Look at the actions required for those messages and try to correct the problem.
PARAMS: The IDs of the content and its parent.

ERROR: [DM_QUERY_F_NO_CONTEXT]

SEVERITY: FATAL
DESCRIPTION: Unable to create a query context block.
CAUSE: This is an internal error. An internally used control block was not created, probably due to lack of sufficient memory.
ACTION: Retry your query, and if it continues to fail, gather up all error messages for your session and contact your Documentum site representative.
PARAMS: None.

ERROR: [DM_QUERY_F_UP_DESTROY]

SEVERITY: FATAL
DESCRIPTION: DELETE: An error has occurred during a destroy operation.
CAUSE: Another error message will have been set for this query. The other message, or messages, will contain information about the cause of this error.
ACTION: Examine the other error messages for this query, and take the appropriate action based upon those messages.
PARAMS:

ERROR: [DM_QUERY_F_NO_QUERY]

SEVERITY: FATAL
DESCRIPTION: The query string was not found.
CAUSE: There was no query string passed to the query parser. This is an internal error.
ACTION: Gather up information about the invocation of the query (the actions leading up to the execution of the query), and all error messages on your session, and contact your Documentum site representative.
PARAMS: None.

ERROR: [DM_QUERY_F_TYPE_FAIL]

SEVERITY: FATAL
DESCRIPTION: SI An error occurred adding attribute %s (with datatype, %d) to the query results type.
CAUSE: This is an internal error.
ACTION: Collect all the error messages that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter contains an attribute name the second parameter contains a datatype code. This information could be useful if your site representative contacts Documentum technical support.

ERROR: [DM_QUERY_F_UP_SAVE]

SEVERITY: FATAL
DESCRIPTION: UPDATE: An error has occurred during a save operation.
CAUSE: Another error message will have been set for this query. The other message, or messages, will contain information about the cause of this error.
ACTION: Examine the other error messages for this query, and take the appropriate action based upon those messages.
PARAMS:

ERROR: [DM_QUERY_F_TRAN_ABORT_FAILED]

SEVERITY: FATAL
DESCRIPTION: ABORT: Your abort transaction statement failed.
CAUSE: Unknown. There may be other error messages on the queue that explain the reason for the failure. The most likely reason is that an RDBMS error has occurred.
ACTION: Examine any other error messages for your session, and do whatever they suggest. If all else fails, retry the abort. If you cannot get abort to complete successfully, your docbase may be inconsistent. Consult your Documentum Site Representative, or your RDBMS DBA for assistance.
PARAMS:

ERROR: [DM_QUERY_F_NO_OWNER]

SEVERITY: FATAL
DESCRIPTION: Unable retrieve the docbase owner from initialization file.
CAUSE: This is an internal error. An internally used control block was not reliable.
ACTION: Report this error to your Documentum site representative.
PARAMS: None.

ERROR: [DM_QUERY_F_SET_FAILED_I]

SEVERITY: FATAL
DESCRIPTION: SSI %s: Unable to set this attribute (%s) with this value (%d).
CAUSE: This is an internal error.
ACTION: Collect all the error messages that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the function in which the error occurred. The second parameter is the name of an attribute which could not be set. The third parameter is the numeric value which could not be set.

ERROR: [DM_QUERY_F_ALTER_FAILED]

SEVERITY: FATAL
DESCRIPTION: ALTER TYPE statement failed.
CAUSE: Your statement has failed due to an internal error.
ACTION: There are additional error messages on your error message queue which will explain the failure, and give possible actions to correct it. You may need to check the error message log for your session. If the statement was re-tried (there will be a warning message, if so), error messages prior to the re-try will have been purged from your queue, but they will still be present in the error message log.
PARAMS: None.

ERROR: [DM_QUERY_F_NO_COLL]

SEVERITY: FATAL
DESCRIPTION: Unable to create the dmQueryResults collection.
CAUSE: This is an internal error, probably caused by lack of memory.
ACTION: Retry your query, and if it continues to fail, gather up all error messages for your session and contact your Documentum site representative.
PARAMS: None.

ERROR: [DM_QUERY_F_ALTER_STORE_FAILED]

SEVERITY: FATAL
DESCRIPTION: S ALTER TYPE: An unexpected error has occurred while storing the changes to the type %s.
CAUSE: Another error message on the error queue will explain the exact cause of the failure. Your statement failed.
ACTION: Take whatever action is necessary according to the explanation in the other error message.
PARAMS: The parameter gives the typename of the type which was not altered.

ERROR: [DM_QUERY_F_COMPOUND_INT]

SEVERITY: FATAL
DESCRIPTION: SS An internal inconsistency has been encountered while recursively processing %s for %s.
CAUSE: This is an internal error. The cause is not readily known. This happens if a SysObject was retrieved during recursive processing that was supposed to have descendents or an assembly, but an attempt to fetch those contained objects yielded nothing.
ACTION: Probably an assembly is corrupted, or there is other erroneous information in the docbase. The first parameter contains either assembly or descendents. The second parameter contains the integer form of the object id for the SysObject being processed. Examine the docbase information about this SysObject. (Integer IDs are found in the _i columns associated with ID attributes.) If you cannot figure out what is wrong with the docbase, give this message and associated information to your Documentum Site Representative.
PARAMS: Explained above.

ERROR: [DM_QUERY_F_INTERNAL_P]

SEVERITY: FATAL
DESCRIPTION: SS An internal problem has occurred in function %s: %s.
CAUSE: This is an internal error.
ACTION: Record the information in this message, and the query that caused it, and contact your Documentum site representative.
PARAMS: The first parameter gives the name of the function in which the error occurred. The second parameter contains a phrase which describes the nature of the error.

ERROR: [DM_QUERY_F_TRAN_BEGIN_FAILED]

SEVERITY: FATAL
DESCRIPTION: BEGIN TRANSACTION: Your begin transaction statement failed.
CAUSE: Unknown. There may be other error messages on the queue that explain the reason for the failure. The most likely reason is that an RDBMS error has occurred.
ACTION: Examine any other error messages for your session, and do whatever they suggest.
PARAMS:

ERROR: [DM_QUERY_F_CHANGE_DESTROY]

SEVERITY: FATAL
DESCRIPTION: S CHANGE: An unexpected destroy error has occurred for object %s.
CAUSE: CHANGE is a two-step operation. The object is first destroyed from its old type, then it is saved as the new type. An unexpected error occurred during the destroy step.
ACTION: There will be additional error messages with this one. Look at the actions required for those messages and try to correct the problem.
PARAMS: The ID of the object that caused your statement to fail.

ERROR: [DM_QUERY_F_INVALID_GROUP]

SEVERITY: FATAL
DESCRIPTION: SS %s: The group specified (%s) was not properly fetched.
CAUSE: This is an internal inconsistency. The group exists, but could not be fetched.
ACTION: Contact your Documentum site representative.
PARAMS: The statement type, and the name of the group.

ERROR: [DM_QUERY_F_NO_TYPE]

SEVERITY: FATAL
DESCRIPTION: Unable to create the `type of the query results object.
CAUSE: A call to the type constructor failed during the attempt to create a query results type describing your querys results.
ACTION: This is most likely caused by an out of memory condition. Retry your query and if it continues to fail, contact your Documentum site representative.
PARAMS: None.

ERROR: [DM_QUERY_F_INTERNAL]

SEVERITY: FATAL
DESCRIPTION: SIS An internal inconsistency has occurred in function %s. %d %s.
CAUSE: This is an internal error.
ACTION: Record the information in this message, and the query that caused it, and contact your Documentum site representative.
PARAMS: The first parameter gives the name of the Documentum function in which this error occurred. The second parameter gives a numeric code. The third parameter contains a phrase which describes the nature of the error. All of this information, plus the query which caused it, should be provided to your Documentum site representative.

ERROR: [DM_QUERY_F_SET_FAILED_S]

SEVERITY: FATAL
DESCRIPTION: SSS %s: Unable to set this attribute (%s) with this value (%s).
CAUSE: This is an internal error.
ACTION: Collect all the error messages that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the function in which the error occurred. The second parameter is the name of an attribute which could not be set. The third parameter is the string value which could not be set.

ERROR: [DM_QUERY_F_CHANGE_CONTENT_BAD]

SEVERITY: FATAL
DESCRIPTION: S CHANGE: The status for content object (%s) is bad. Please check for any accompanying error messages and examine the file.
CAUSE: The status for the content object is bad.
ACTION: There will be additional error messages with this one. Look at the actions required for those messages and try to correct the problem.
PARAMS: The IDs of the content and its parent. Query Facility errors (continued due to limit of 256 messages per severity per facility) ** Documentum DocuServer ** Confidential Property of Documentum, Inc. ** (c) Copyright Documentum, Inc., 1991-2002 ** All rights reserved. **

ERROR: [DM_QUERY_F_SYSOBJ_NOT_FOUND]

SEVERITY: FATAL
DESCRIPTION: S Unable to find the SysObject matching ID %s.
CAUSE: This is an internal error. There should be additional error message(s) that explain the cause of this failure.
ACTION: Examine the other error messages for this query. If you cannot figure out how to correct this problem, consult your Documentum System Administrator.
PARAMS: The ID is the object ID that corresponds to the version label specified in your IN DOCUMENT clause.

ERROR: [DM_QUERY_F_CHANGE_SAVE]

SEVERITY: FATAL
DESCRIPTION: S CHANGE: An unexpected save error has occurred for object %s.
CAUSE: CHANGE is a two-step operation. The object is first destroyed from its old type, then it is saved as the new type. An unexpected error occurred during the save step.
ACTION: There will be additional error messages with this one. Look at the actions required for those messages and try to correct the problem.
PARAMS: The ID of the object that caused your statement to fail.

ERROR: [DM_QUERY_F_NO_INFO_OBJECT]

SEVERITY: FATAL
DESCRIPTION: Unable access the dmInfoObject.
CAUSE: This is an internal error. An internally used control block was not accessible.
ACTION: Retired.
PARAMS:

ERROR: [DM_QUERY_F_NO_CONNECTION]

SEVERITY: FATAL
DESCRIPTION: Unable to create a database connection.
CAUSE: Your query required a separate database connection, which could not be created. The types of things that cause queries to require separate database connections are, your query is a read-for-update query, or your query has a SEARCH clause.
ACTION: Check the next messages on the message queue and follow the instructions for recovery in them. This error is usually caused by some error in the RDBMS that Documentum is running with. Some RDBMSs will reject connection attempts if certain thresholds are exceeded. You may require assistance from the Database Administrator if a threshold must be set higher. Sometimes all that is required is to wait until activity against the RDBMS is lower, if that is an option.
PARAMS: None.

ERROR: [DM_QUERY_F_CREATE_UNABLE]

SEVERITY: FATAL
DESCRIPTION: S CREATE OBJECT: An unexpected error has caused your creation of %s object to fail.
CAUSE: An error has prevented your object from being created.
ACTION: It could be that objects of this type cannot be created directly. Create the object by using the appropriate api method instead.
PARAMS: The object type specified in your statement.

ERROR: [DM_QUERY_F_ROLLBACK_FAILED]

SEVERITY: FATAL
DESCRIPTION: An attempt to rollback your statements changes to the database has failed.
CAUSE: Your statement failed, causing an attempt to rollback the database. The rollback failed.
ACTION: Check the rest of the messages in the error queue. There should be a message describing the rollback failure, and giving the error message from the database system which caused it. Take whatever action is required to resolve the database system problem. This may require action by your database system administrator.
PARAMS: None.

ERROR: [DM_QUERY_F_NO_RESULT]

SEVERITY: FATAL
DESCRIPTION: Unable to create the `result object for the query results.
CAUSE: A call to dm_CreateTypedObject failed during the attempt to create the result object for query results.
ACTION: There is another message on the error queue which describes the cause of the failure. Follow whatever instructions are contained in that message to correct the failure, and retry your query.
PARAMS: None.

ERROR: [DM_QUERY_F_RESULT_NOT_SET_ID]

SEVERITY: FATAL
DESCRIPTION: S Unable to set the ID return value for this query: %s.
CAUSE: Another error message will have been set for this query. The other message, or messages, will contain information about the cause of this error.
ACTION: Examine the other error messages for this query, and take the appropriate action based upon those messages.
PARAMS:

ERROR: [DM_QUERY_E_UPDATE_LINK_CAB]

SEVERITY: ERROR
DESCRIPTION: S You have specified %s for a cabinet object.
CAUSE: Your statement has a LINK, MOVE, or UNLINK clause, but these operations are not valid on cabinets.
ACTION: If your statement is a CREATE OBJECT statement, do not attempt to link, move, or unlink in this statement. If your statement is an UPDATE OBJECTS statement, modify your WHERE clause so that no cabinets will be qualified for updating.
PARAMS:

ERROR: [DM_QUERY_E_UPDATE_USER_P]

SEVERITY: ERROR
DESCRIPTION: You must have SYSADMIN or SUPERUSER privilege to update or create users.
CAUSE: You have attempted to update or create objects of the dm_user type, or a subtype of dm_user, with insufficient privilege to do so.
ACTION: None.
PARAMS:

ERROR: [DM_QUERY_E_NOT_GROUP]

SEVERITY: ERROR
DESCRIPTION: SS %s: The group specified (%s) does not exist.
CAUSE: The group is not a Documentum group. The can happen in an ALTER TYPE statement, if the DEFAULT GROUP setting is wrong, or in an ALTER or DROP GROUP statement.
ACTION: Find the correct name of the intended group, or talk to a System Administrator or SuperUser about creating a new group.
PARAMS: The first parameter gives the statement type that the error occurred in. The second parameter contains the invalid group name.

ERROR: [DM_QUERY_E_CONFLICT_HINTS]

SEVERITY: ERROR
DESCRIPTION: SS The DQL hints %s and %s are not compatible.
CAUSE: You have specified two conflict DQL hints in the same query.
ACTION: Make sure that you only use one of those two hints.
PARAMS: Name of the hints.

ERROR: [DM_QUERY_E_WITHIN_NOT_SUPPORTED]

SEVERITY: ERROR
DESCRIPTION: You have specified a WITHIN predicate in your SEARCH clause.
CAUSE: The WITHIN predicate is not supported for the fulltext system that you are using.
ACTION: If you cannot formulate SEARCH clause with a CONTAINS condition that fits your requirements, try formulating the fulltext query directly in your fulltext systems query language, and use the passthrough mechanism of the SEARCH clause.
PARAMS: None.

ERROR: [DM_QUERY_E_INDEX_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: S The specified index, %s, in the search clause is not found.
CAUSE: You have specified a non-existent index in the search clause.
ACTION: Make sure all index names in the search clause exist in the docbase.
PARAMS:

ERROR: [DM_QUERY_E_REPEATING_USED]

SEVERITY: ERROR
DESCRIPTION: S You have specified a repeating attribute (%s) where it is not allowed.
CAUSE: Repeating attributes may only appear in the select list, a repeating attribute predicate (ANY), a group by clause, or an order by clause.
ACTION: Correct the query.
PARAMS: The name of the repeating attribute that is in the wrong place.

ERROR: [DM_QUERY_E_BAD_QUAL]

SEVERITY: ERROR
DESCRIPTION: SS The attribute qualifier, %s, for attribute %s, is not a valid qualifier.
CAUSE: A construct such as qualifier.attribute_name has appeared in your query, but the qualifier is not a valid qualifier in this query.
ACTION: The valid qualifiers are 1) the queried type name, 2) a registered table name, 3) a correlation variable. Furthermore, if a correlation variable is specified, it masks the type name or table name that it represents. In other words, types which have correlation variables are not valid qualifiers.
PARAMS: The two parameters are, respectively, the bad qualifier, and the attribute that it qualifies.

ERROR: [DM_QUERY_E_CURRENT_NOT_IN_SL]

SEVERITY: ERROR
DESCRIPTION: The special keyword ISCURRENT must appear in the select list.
CAUSE: It is a restriction that if the special keyword ISCURRENT appears in a where clause, it must also appear in the select list. This is a current limitation due to implementation considerations.
ACTION: Add ISCURRENT to your select list.
PARAMS:

ERROR: [DM_QUERY_E_MSCORE_USED]

SEVERITY: ERROR
DESCRIPTION: You have specified the MSCORE keyword where it is not allowed.
CAUSE: The MSCORE keyword may only be specified in a select list, or an order by clause.
ACTION: Correct your statement so that MSCORE does not appear anywhere other than the select list or order by clause. PARAMTERS: None.
PARAMS:

ERROR: [DM_QUERY_E_DROP_FAILED2]

SEVERITY: ERROR
DESCRIPTION: S DROP GROUP statement failed for group: %s.
CAUSE: An error has occurred dropping the specified group.
ACTION: There will be another error message describing the specific reason for the failure. Follow the directions in that message to correct the problem.
PARAMS: The parameter specifies the group which was not dropped.

ERROR: [DM_QUERY_E_COMPOSITE_2]

SEVERITY: ERROR
DESCRIPTION: ORDER keyword illegally used in SELECT statement.
CAUSE: You have specified the ORDER keyword in an illegal place in your SELECT statement. The ORDER keyword may only be specified in the ORDER BY clause, and in the SELECT list. Furthermore, since the ORDER keyword expands into multiple column specifications, it cannot appear in the select list of a subselect.
ACTION: Composites are a deprecated feature. The ORDER keyword is no longer supported.
PARAMS: None.

ERROR: [DM_QUERY_E_COMPOUND_ID_NO]

SEVERITY: ERROR
DESCRIPTION: S Compound document clause has an ID specification (%s) that does not identify an existing SysObject.
CAUSE: The ID specified in your IN DOCUMENT or IN ASSEMBLY clause does not identify an existing SysObject.
ACTION: Correct the ID specification in your query and retry.
PARAMS: The invalid ID.

ERROR: [DM_QUERY_E_UP_NOT_TYPE]

SEVERITY: ERROR
DESCRIPTION: S You have specified an invalid type name (%s).
CAUSE: The name that you specified in your statement is not a type.
ACTION: Correct the type name.
PARAMS: The name you specified in your update, change, delete, or create object statement.

ERROR: [DM_QUERY_E_MFILE_URL_NOT_IN_SL]

SEVERITY: ERROR
DESCRIPTION: The special keyword MFILE_URL must appear in the outermost select list.
CAUSE: It is a restriction that the special keyword MFILE_URL must appear in the outermost select list. This is a current limitation due to implementation considerations.
ACTION: Add MFILE_URL to your outermost select list.
PARAMS:

ERROR: [DM_QUERY_E_DROP_BASE_TYPE]

SEVERITY: ERROR
DESCRIPTION: S DROP TYPE: You have attempted to drop a Documentum base type, %s.
CAUSE: The specified type is a Documentum base type and cannot be dropped.
ACTION: None. The type cannot be dropped.
PARAMS: The type specified in this statement.

ERROR: [DM_QUERY_E_EXEC_NO_LIST]

SEVERITY: ERROR
DESCRIPTION: S EXECUTE: You have specified a value list for the argument %s.
CAUSE: This argument may only have one value.
ACTION: Correct the query and retry.
PARAMS:

ERROR: [DM_QUERY_E_MIXED_UNION]

SEVERITY: ERROR
DESCRIPTION: UNION ALL clause is combined with UNION.
CAUSE: You cannot mix UNION and UNION ALL clauses in the same query qualification list.
ACTION: Either use UNION or UNION ALL clause in a query qualification list. Do not mix them together.
PARAMS:

ERROR: [DM_QUERY_E_TYPE_PREDICATE]

SEVERITY: ERROR
DESCRIPTION: S You have specified a type predicate (%s), but no type was specified in the FROM clause of this query.
CAUSE: There are DQL predicates that only pertain to Documentum types. You have specified one of them in a query which only names registered tables in the FROM clause.
ACTION: Reformulate the query without this predicate.
PARAMS: The parameter names the specific predicate that is in error.

ERROR: [DM_QUERY_E_CURSOR_ERROR]

SEVERITY: ERROR
DESCRIPTION: S A database error has occurred during the creation of a cursor (%s).
CAUSE: A DQL SELECT statement is turned into an SQL SELECT statement that queries the Documentum schema for the information requested. This error message indicates that a failure occurred during the parsing of the generated SQL statement by the underlying RDBMS.
ACTION: The error message from the RDBMS is shown in the message. Use that error message to figure out what has happened, and correct your DQL statement accordingly.
PARAMS: The parameter contains the text of the error message generated by the RDBMS.

ERROR: [DM_QUERY_E_CHG_NOT_LINKABLE]

SEVERITY: ERROR
DESCRIPTION: You cannot move/link/unlink objects in a CHANGE statement.
CAUSE: You have tried to move/link/unlink an object while changing its type.
ACTION: You have to change the type first, then use UPDATE statement to move/link/unlink the object.
PARAMS:

ERROR: [DM_QUERY_E_NOT_ATTRIBUTE]

SEVERITY: ERROR
DESCRIPTION: S You have specified an invalid attribute name (%s).
CAUSE: The attribute name specified in the query is not an attribute of the queried type.
ACTION: Correct the name and retry the query. Use DESCRIBE to find out the valid attributes for the type[s] you are querying. Note that if you are joining multiple types, you should also disambiguate all attribute references.
PARAMS: The invalid attribute name.

ERROR: [DM_QUERY_E_COMPOUND_PARENT_ND]

SEVERITY: ERROR
DESCRIPTION: You have specified PARENT in a query that does not have an IN DOCUMENT or IN ASSEMBLY clause.
CAUSE: The PARENT special keyword may only appear in a query that has an IN DOCUMENT or IN ASSEMBLY clause.
ACTION: Either remove PARENT from your select list, or add an in document clause.
PARAMS:

ERROR: [DM_QUERY_E_SEARCH_NOT_AVAILABLE]

SEVERITY: ERROR
DESCRIPTION: You have specified a SEARCH clause, but no fulltext system is available.
CAUSE: You must have a fulltext system installed in order to specify a search clause.
ACTION: If you do have a fulltext system installed, check to make sure it is defined in your server config object.
PARAMS: None.

ERROR: [DM_QUERY_E_HITS_NOT_IN_SL]

SEVERITY: ERROR
DESCRIPTION: The special keyword HITS must appear in the select list.
CAUSE: It is a restriction that if the special keyword HITS appears in a where clause, it must also appear in the select list. This is a current limitation due to implementation considerations.
ACTION: Add HITS to your select list.
PARAMS:

ERROR: [DM_QUERY_E_COMPOUND_INS]

SEVERITY: ERROR
DESCRIPTION: IN DOCUMENT clause appears in an INSERT statement.
CAUSE: You have specified an IN DOCUMENT clause within an INSERT statement. This is not allowed unless there is a rootnode assembly that will be used.
ACTION: None.
PARAMS:

ERROR: [DM_QUERY_E_COMPOUND_ORDER]

SEVERITY: ERROR
DESCRIPTION: IN DOCUMENT or IN ASSEMBLY clause is combined with ORDER BY.
CAUSE: You cannot specify ORDER BY in the same query as IN DOCUMENT or IN ASSEMBLY. This is because the compound document clause dictates the ordering and it cannot be overridden.
ACTION: Remove the ORDER BY clause, and retry your query.
PARAMS:

ERROR: [DM_QUERY_E_MODIFY_SPACEOPTIMIZE_MISMATCH_TYPE]

SEVERITY: ERROR
DESCRIPTION: SSS ALTER TYPE: The attribute %s has a data type %s different than the one (%s) specified in the query.
CAUSE: You have specified an attribute in the MODIFY clause of an ALTER TYPE statement for enabling spaceoptimize that has a different data type. Note that for enabling spaceoptimize in ALTER TYPE, the attribute must be the same data type as specified in the query.
ACTION: Correct the attribute data type in your MODIFY clause.
PARAMS: The attribute name and attribute data type as they appear in your statement plus the real data type of the attribute.

ERROR: [DM_QUERY_E_NO_SUPERTYPE]

SEVERITY: ERROR
DESCRIPTION: S CREATE TYPE: Supertype, %s, not found.
CAUSE: The supertype specified in your querys WITH SUPERTYPE clause is not a valid Documentum type.
ACTION: Correct the supertype specification. To get a list of the names of all types defined in Documentum, you may run the DQL query: select name from dm_type
PARAMS: The parameter specifies the invalid type name.

ERROR: [DM_QUERY_E_STRING_LENGTH]

SEVERITY: ERROR
DESCRIPTION: ISI CREATE or ALTER TYPE: Length specification (%d) for attribute %s exceeds allowable maximum (%d).
CAUSE: You have attempted to create a type with an invalid attribute. The maximum allowable length for string attributes is given in the message. The type was not created.
ACTION: Shorten your length specification for the named attribute.
PARAMS: The first parameter gives the invalid length you have specified. The second parameter gives the attribute. The third parameter gives the maximum allowable length for a string attribute.

ERROR: [DM_QUERY_E_EXEC_BAD_BOOL]

SEVERITY: ERROR
DESCRIPTION: IS EXECUTE: You have specified an integer value (%d) for a boolean argument (%s).
CAUSE: An integer may be specified for a boolean argument as long as it is 0 or 1.
ACTION: Correct the value and retry.
PARAMS:

ERROR: [DM_QUERY_E_COMPOUND_POS]

SEVERITY: ERROR
DESCRIPTION: You have specified POSITION or TAG in the select list of a query with an IN DOCUMENT clause.
CAUSE: POSITION and TAG are not allowed in queries with IN DOCUMENT.
ACTION: Reconstruct your query. You could assemble the compound document, and then use the IN ASSEMBLY clause.
PARAMS:

ERROR: [DM_QUERY_E_COMPOUND_NODE_ID_NO]

SEVERITY: ERROR
DESCRIPTION: S Your NODE phrase has an ID specification (%s) that does not identify an existing SysObject.
CAUSE: The ID specified in your ASSEMBLY clauses NODE phrase does not identify an existing SysObject.
ACTION: Correct the ID specification in your query and retry.
PARAMS: The invalid ID.

ERROR: [DM_QUERY_E_SCORE_NOT_IN_SL]

SEVERITY: ERROR
DESCRIPTION: The special keyword SCORE must appear in the select list.
CAUSE: It is a restriction that if the special keyword SCORE appears in a where clause, it must also appear in the select list. This is a current limitation due to implementation considerations.
ACTION: Add SCORE to your select list.
PARAMS:

ERROR: [DM_QUERY_E_MCONTENTID_USED]

SEVERITY: ERROR
DESCRIPTION: You have specified the MCONTENTID keyword where it is not allowed.
CAUSE: The MCONTENTID keyword may only be specified in a select list, or an order by clause.
ACTION: Correct your statement so that MCONTENTID does not appear anywhere other than the select list or order by clause. PARAMTERS: None.
PARAMS:

ERROR: [DM_QUERY_E_REG_TABLE_UPDATE]

SEVERITY: ERROR
DESCRIPTION: You have attempted to update the table_name or table_owner of a registered table.
CAUSE: This is not permitted.
ACTION: To change the table_name or table_owner attribute of a registered table, you must unregister the table, and reregister it under its new name or owner.
PARAMS:

ERROR: [DM_QUERY_E_NOT_YET]

SEVERITY: ERROR
DESCRIPTION: S %s is not supported at this time.
CAUSE: You have attempted to use a feature of the query language which is not yet supported.
ACTION: Try to get along without this feature until support for it is supplied.
PARAMS: The parameter is a string that describes the unsupported feature.

ERROR: [DM_QUERY_E_LIKE_INVALID_OP]

SEVERITY: ERROR
DESCRIPTION: You have specified an invalid operand to the LIKE predicate.
CAUSE: Only a column specification or a scalar function specification (upper or lower) may be specified as the operand for LIKE.
ACTION: Correct the LIKE predicate and retry.
PARAMS:

ERROR: [DM_QUERY_E_INSERT_BAD_VALUE]

SEVERITY: ERROR
DESCRIPTION: You have specified an invalid value in the VALUES clause of an INSERT statement.
CAUSE: Only the keyword USER, a date function, a substring function or a literal value, are legal in this context.
ACTION: Correct the statement and retry.
PARAMS:

ERROR: [DM_QUERY_E_REG_TABLE_PERMIT_I]

SEVERITY: ERROR
DESCRIPTION: SI You have attempted to set an invalid %s table permission: %d.
CAUSE: The table permission specified is not valid. Table permissions must be a positive integer less than 16.
ACTION: Correct the table permission.
PARAMS: The first parameter indicates whether it was the owner, group, or world table permission. The second parameter is the invalid value.

ERROR: [DM_QUERY_E_NO_GROUP_PRIV]

SEVERITY: ERROR
DESCRIPTION: You have insufficient privilege to create, alter, or drop a group.
CAUSE: You must have SYSADMIN or CREATE GROUP privilege to do group operations.
ACTION: Ask your system administrator about doing the operation for you, or granting you CREATE GROUP privilege.
PARAMS: None.

ERROR: [DM_QUERY_E_TEXT_NOT_IN_SL]

SEVERITY: ERROR
DESCRIPTION: The special keyword TEXT must appear in the select list.
CAUSE: It is a restriction that if the special keyword TEXT appears in a where clause, it must also appear in the select list. This is a current limitation due to implementation considerations.
ACTION: Add TEXT to your select list.
PARAMS:

ERROR: [DM_QUERY_E_NOT_REG]

SEVERITY: ERROR
DESCRIPTION: SS UNREGISTER: The table, %s.%s, was not registered.
CAUSE: You have attempted to unregister a table that was not registered.
ACTION: No action required. The table is not registered.
PARAMS: The parameters specify the two-part tablename of the table (owner.table).

ERROR: [DM_QUERY_E_NO_THUMBNAIL_STORE]

SEVERITY: ERROR
DESCRIPTION: There is no storage area whose media type is thumbnail (1).
CAUSE: It is required to have at least one storage area with media type equal to thumbnail when the keyword THUMBNAIL_URL is specified in the select list.
ACTION: Make sure you have at least one storage area with media type equal to thumbnail.
PARAMS:

ERROR: [DM_QUERY_E_UP_VALUE]

SEVERITY: ERROR
DESCRIPTION: You have specified an illegal value specification.
CAUSE: The value in an update clause may not contain any of an expression, a set function, a date arithmetic function, or the special keywords (order, tag, position, score).
ACTION: Correct the update clause in your update or create object statement, and retry.
PARAMS:

ERROR: [DM_QUERY_E_NOT_CABINET_PATH]

SEVERITY: ERROR
DESCRIPTION: S You have specified a path value ( %s ) that is not a valid cabinet path.
CAUSE: The CABINET predicate must specify a cabinet path, not a folder path. The path you have specified may or may not be a valid folder path, but it is not the path of a cabinet.
ACTION: Correct the path specification.
PARAMS: The path value as specified in your CABINET predicate.

ERROR: [DM_QUERY_E_COMPOUND_COL_S]

SEVERITY: ERROR
DESCRIPTION: IN DOCUMENT or IN ASSEMBLY clause has a column specification but is not in a subselect.
CAUSE: If you specify the ID of the root node in a compound document clause as a column specification, the IN DOCUMENT or IN ASSEMBLY clause must be in a subselect.
ACTION: Reformulate your query.
PARAMS:

ERROR: [DM_QUERY_E_ALTER_BASE_TYPE]

SEVERITY: ERROR
DESCRIPTION: S ALTER TYPE: You have insufficient privilege to ADD or DROP attributes from a Documentum base type (%s).
CAUSE: Your alter type statement specified a Documentum base type. Only a superuser may alter the base types, and then only if requested to do so as part of a Documentum release script. Any type which has a name beginning with the letters dm is a Documentum base type.
ACTION: None.
PARAMS: The typename as specified in the alter type statement.

ERROR: [DM_QUERY_E_TH_URL_NOT_IN_SL]

SEVERITY: ERROR
DESCRIPTION: The special keyword THUMBNAIL_URL must appear in the outermost select list.
CAUSE: It is a restriction that the special keyword THUMBNAIL_URL must appear in the outermost select list. This is a current limitation due to implementation considerations.
ACTION: Add THUMBNAIL_URL to your outermost select list.
PARAMS:

ERROR: [DM_QUERY_E_COMPOSITE_4]

SEVERITY: ERROR
DESCRIPTION: IN COMPOSITE clause used without a dm_sysobject type.
CAUSE: You have specified an IN COMPOSITE clause in your query, but the FROM clause does not specify dm_sysobject or a subtype of dm_sysobject.
ACTION: Only SysObjects are contained in composites, so a query must specify dm_sysobject or one of its subtypes if the IN COMPOSITE clause is used. Modify your query as appropriate and retry.
PARAMS: None.

ERROR: [DM_QUERY_E_SYNTAX]

SEVERITY: ERROR
DESCRIPTION: SS A Parser Error (%s) has occurred in the vicinity of: %s
CAUSE: The DQL syntax parser has failed to parse your query. The first parameter is an error message from YACC (the compiler compiler), which explains the cause of the failure. This is nearly always going to be syntax error. The second parameter contains a portion of your query, up to the point at which the parser failure occurred. Thus, the last word in the partial query string is the token on which the parser failed.
ACTION: If the error is anything besides syntax error you have probably exceeded some sort of YACC processing limit. That could possibly require a call to Documentum tech support to figure out, in the unlikely event that this should happen. In the very likely event that the error is syntax error, examine your query in the vicinity of the final few tokens processed to determine the cause of the syntax error. Correct your query accordingly and resubmit it. Note that if no string appears in the second parameter, that indicates that an empty string, or a string containing all unprintable characters and blanks, was submitted as a query.
PARAMS: Described above. If your query is exceptionally long, the second parameter may be cut down to fit within an error message. In this case, not all of the beginning of the query may be present, but the rule still holds that the last word in the second parameter is the token that caused the query to fail.

ERROR: [DM_QUERY_E_BAD_GROUP_SAVE]

SEVERITY: ERROR
DESCRIPTION: CREATE or ALTER GROUP: Unable to save the group.
CAUSE: An error has occurred which prevented your group from being saved in the database. Your create or alter statement failed.
ACTION: There will be a message from the Save() method which will explain the reason for this error. Follow the directions in that message to correct the problem.
PARAMS: None.

ERROR: [DM_QUERY_E_NOT_CLASS]

SEVERITY: ERROR
DESCRIPTION: S SELECT: The type (%s) specified in the FROM clause is either not a valid Documentum type, or not a queryable Documentum type.
CAUSE: The queryable types are dm_user, dm_group, dm_type, dm_sysobject, and all system- or user-defined subtypes of these queryable types.
ACTION: Reformulate the query specifying a queryable type.
PARAMS: The parameter specifies the typename of the non-queryable type.

ERROR: [DM_QUERY_E_CREATE_INTERNAL_ATT]

SEVERITY: ERROR
DESCRIPTION: CREATE TYPE: You have attempted to create a type with internal or readonly attribute(s).
CAUSE: Internal and readonly attributes (those with names beginning with `i_ or `r_) can only be added by a superuser, and then only if requested to do so as part of a Documentum release script.
ACTION: None.
PARAMS: None.

ERROR: [DM_QUERY_E_COMPOUND_SUB]

SEVERITY: ERROR
DESCRIPTION: IN DOCUMENT clause appears within a subquery.
CAUSE: You have specified an IN DOCUMENT clause within a subquery. IN DOCUMENT may only appear in the outermost SELECT, unless there is a rootnode assembly that will be used, or the IN DOCUMENT clause is not descending.
ACTION: None.
PARAMS:

ERROR: [DM_QUERY_E_NOT_SUPPORTED]

SEVERITY: ERROR
DESCRIPTION: SS %s: The subquery form of this query is not supported in your environment, because your RDBMS (%s) does not have the required functionality.
CAUSE: Self explanatory.
ACTION: Use the list form of this query instead of the subquery form.
PARAMS: The first parameter specifies the statement type that the error occurred in. The second parameter contains the name of the RDBMS that Documentum is connected to.

ERROR: [DM_QUERY_E_COMPOUND_UPDATE]

SEVERITY: ERROR
DESCRIPTION: You have specified an IN DOCUMENT clause in an UPDATE statement.
CAUSE: This is not supported.
ACTION: IN ASSEMBLY is supported in an UPDATE statement. You could create an assembly for your compound document and retry your update statement using the IN ASSEMBLY clause.
PARAMS:

ERROR: [DM_QUERY_E_COMPOUND_CONTID_SL]

SEVERITY: ERROR
DESCRIPTION: You have specified CONTAIN_ID somewhere in your query besides the select list.
CAUSE: The PARENT special keyword may only appear in the select list.
ACTION: Reword your query, removing the CONTAIN_ID keyword from all parts of the query besides the select list.
PARAMS:

ERROR: [DM_QUERY_E_COMPOUND_PARENT_SL]

SEVERITY: ERROR
DESCRIPTION: You have specified PARENT somewhere in your query besides the select list.
CAUSE: The PARENT special keyword may only appear in the select list.
ACTION: Reword your query, removing the PARENT keyword from all parts of the query besides the select list.
PARAMS:

ERROR: [DM_QUERY_E_MODIFY_SPACEOPTIMIZE_WRONG_STRING_LENGTH]

SEVERITY: ERROR
DESCRIPTION: SI ALTER TYPE: The string attribute %s can not have a non-zero length (%d) while enabling spaceoptimize.
CAUSE: You have specified a string attribute in the MODIFY clause of an ALTER TYPE statement for enabling spaceoptimize that has a non-zero string length. Note that for enabling spaceoptimize in ALTER TYPE, the string attribute must have a zero length in the query.
ACTION: Correct the attribute data length in your MODIFY clause.
PARAMS: The attribute name and attribute data length as they appear in your statement.

ERROR: [DM_QUERY_E_BAD_STORAGE_CLASS]

SEVERITY: ERROR
DESCRIPTION: S ALTER TYPE: You have specified an invalid storage class (%s).
CAUSE: Your DQL ALTER TYPE statement specified a SET DEFAULT STORAGE clause with an unknown storage class.
ACTION: Correct the storage class and try again. The valid storage classes can be found in the name attribute of the dm_store type.
PARAMS: The invalid storage class.

ERROR: [DM_QUERY_E_UP_TYPES]

SEVERITY: ERROR
DESCRIPTION: You have specified a list of types or tables in your statement.
CAUSE: Exactly one type name may be specified in an update, delete, or create object statement. One type may be specified for each of the from and to types in a change statement.
ACTION: Correct the statement. Only one type (not a list) may be specified. If information from another type or a registered table must be used, that information can be specified in a subselect.
PARAMS:

ERROR: [DM_QUERY_E_CHANGE_CANNOT_SETFILE]

SEVERITY: ERROR
DESCRIPTION: You can not use Setfile in a CHANGE OBJECT statement.
CAUSE: You can not use a Setfile clause in a CHANGE OBJECT statement.
ACTION: Use either an UPDATE OBJECT or CREATE OBJECT statement to Setfile.
PARAMS:

ERROR: [DM_QUERY_E_UP_BAD_ATTR]

SEVERITY: ERROR
DESCRIPTION: S The attribute %s is not updateable.
CAUSE: The attribute you are attempting to set is not an updateable attribute.
ACTION: Internal and readonly attributes are not updateable. The owner_name attribute is also not updateable. Remove the reference(s) to attribute(s) beginning with i_ or _r, or owner_name, from your update or create object statement.
PARAMS: The attribute name.

ERROR: [DM_QUERY_E_IS_REPLICA_SL]

SEVERITY: ERROR
DESCRIPTION: You have specified ISREPLICA somewhere in your query besides the select list.
CAUSE: The ISREPLICA special keyword may only appear in the select list.
ACTION: Reword your query, removing the ISREPLICA keyword from all parts of the query besides the select list.
PARAMS:

ERROR: [DM_QUERY_E_CHANGE_TYPES3]

SEVERITY: ERROR
DESCRIPTION: CHANGE: You have specified types that are not in a subtype/supertype relationship.
CAUSE: Objects may be changed from one type to another only if one of the types is a supertype (either direct or indirect) of the other. For example, you cannot change objects from one subtype of dm_document into another subtype of dm_document.
ACTION: You may be able to make the change in two steps. For example, you could change documents from a subtype of dm_document into dm_document objects, and then change them into another subtype of dm_document.
PARAMS:

ERROR: [DM_QUERY_E_REG_TABLE_PERMIT_IN]

SEVERITY: ERROR
DESCRIPTION: SSS You have insufficient privilege to %s the %s.%s table.
CAUSE: You have attempted to access a registered table in a way that you have no permission for.
ACTION: If you require the given permission, contact the table owner or a Documentum superuser about assigning you the permission. PARAMTERES: The first parameter shows the requested level of permission (select, update, insert, delete). The following paramters show the qualified name of the table.
PARAMS:

ERROR: [DM_QUERY_E_CANT_ALTER_BASE_TYPE]

SEVERITY: ERROR
DESCRIPTION: S ALTER TYPE: You cannot ADD, DROP or MODIFY attributes from a Documentum base type (%s).
CAUSE: You have attempted to alter a Documentum base type. This is no longer supported.
ACTION: Only attempt allowed actions on Documentum base types. You may not ADD an attribute, DROP an attribute, or MODIFY the length of an attribute of a Documentum base type.
PARAMS:

ERROR: [DM_QUERY_E_NOT_ACL]

SEVERITY: ERROR
DESCRIPTION: SSS %s: The ACL specified (%s %s) does not exist.
CAUSE: The ACL is not a Documentum ACL. This can happen in an ALTER TYPE statement, if the name specified in DEFAULT ACL is wrong.
ACTION: Find the correct name of the intended ACL, or talk to a System Administrator or SuperUser about creating a new ACL.
PARAMS: The first parameter gives the statement type that the error occurred in. The second parameter contains the ACL name and the third one contains the ACL domain.

ERROR: [DM_QUERY_E_UPDATE_SUB_CONV1]

SEVERITY: ERROR
DESCRIPTION: UPDATE: Your subquery returned an unconvertable value.
CAUSE: The subquery in an update clause returned a value that is not convertable to the datatype of the updated attribute.
ACTION:
PARAMS:

ERROR: [DM_QUERY_E_FOLDERS_TOO_MANY]

SEVERITY: ERROR
DESCRIPTION: You have specified too many folders in a FOLDER predicate.
CAUSE: The folder predicate only accepts up to 10 folders in the list form.
ACTION: If you must search more than 10 folders, you may specify the overflow in a separate folder predicate ORd with first folder predicate.
PARAMS:

ERROR: [DM_QUERY_E_POS_NOT_IN_SL]

SEVERITY: ERROR
DESCRIPTION: The special keyword POSITION must appear in the select list.
CAUSE: It is a restriction that if the special keyword POSITION appears in a where clause, it must also appear in the select list. This is a current limitation due to implementation considerations.
ACTION: Add POSITION to your select list.
PARAMS:

ERROR: [DM_QUERY_E_TRAN_NOT_BEGUN]

SEVERITY: ERROR
DESCRIPTION: S %s: An attempt to begin a transaction failed. This query must be run within a transaction.
CAUSE: Queries such as this that process lists must be run within a transaction in order to ensure all-or-nothing semantics. The query processor was unable to begin a transaction.
ACTION: There will be another error message which explains the reason the the transaction could not be begun. Take whatever action is appropriate based on the explanation in that message.
PARAMS: The parameter gives the statement on which this error occurred.

ERROR: [DM_QUERY_E_EXEC_BAD_VALUE]

SEVERITY: ERROR
DESCRIPTION: S EXECUTE: You have specified a value that is not a valid datatype for argument %s.
CAUSE: Argument values may be integers, booleans (TRUE or FALSE), or character string literals only.
ACTION: Correct the value specification and retry.
PARAMS:

ERROR: [DM_QUERY_E_EXEC_REQD]

SEVERITY: ERROR
DESCRIPTION: S EXECUTE: A required argument (%s) was omitted.
CAUSE: The argument is required.
ACTION: Specify a value for this argument.
PARAMS:

ERROR: [DM_QUERY_E_ATTR_NOT_ACC]

SEVERITY: ERROR
DESCRIPTION: S The attribute %s is not an accessible attribute.
CAUSE: The attribute is not accessible via DQL.
ACTION: Remove the attribute from your DQL statement.
PARAMS: The attribute name as it appears in your statement.

ERROR: [DM_QUERY_E_COMPOUND_NO_ASSEM]

SEVERITY: ERROR
DESCRIPTION: Your IN ASSEMBLY clause specifies a document with no assembly.
CAUSE: The ID specified must be a document that has been assembled.
ACTION: Either create an assembly for the document, or use the IN DOCUMENT clause to retrieve the components of this document.
PARAMS:

ERROR: [DM_QUERY_E_UPDATE_SUB_CONVB]

SEVERITY: ERROR
DESCRIPTION: UPDATE: Your subquery returned an unconvertable value.
CAUSE: The subquery in an update clause returned a value that is not convertable to the datatype of the updated attribute. Or, the attribute is boolean and the value is integer, but the value is not a convertable value (0 or 1).
ACTION:
PARAMS:

ERROR: [DM_QUERY_E_TWICE]

SEVERITY: ERROR
DESCRIPTION: S ALTER TYPE: You have attempted to set the %s attribute more than once in this query.
CAUSE: You have specified a SET CLAUSE attribute more than once, causing your query to fail.
ACTION: Reformulate the query such that each attribute you want set is only referred to once.
PARAMS: The parameter contains the attribute that has been set more than once.

ERROR: [DM_QUERY_E_ATTR_NOT_VIEWABLE]

SEVERITY: ERROR
DESCRIPTION: SSS User (%s) does not have enough privilege to view the column (%s) in the type (%s).
CAUSE: The user does not have enough privilege to view the column in the type that you specified in your select statement. Currently, there are some attributes that are only viewable to users who are either superusers or have the VIEW AUDIT privilege.
ACTION: Remove the attribute from the select statement.
PARAMS: The name you specified in your select statement.

ERROR: [DM_QUERY_E_INSERT_ERROR]

SEVERITY: ERROR
DESCRIPTION: S A database error has occurred during the execution of your insert statement (%s).
CAUSE: A DQL INSERT statement is turned into an SQL INSERT statement that performs the insert on the specified registered table. This error message indicates that a failure occurred during the processing of the generated SQL INSERT statement by the underlying RDBMS.
ACTION: The error message from the RDBMS is shown in the message. Use that error message to figure out what has happened, and correct your DQL statement accordingly.
PARAMS: The parameter contains the text of the error message generated by the RDBMS.

ERROR: [DM_QUERY_E_UP_INDEX]

SEVERITY: ERROR
DESCRIPTION: S You have specified a non-zero index for attribute %s.
CAUSE: The attribute is a single-valued attribute, which can only have an index value of zero.
ACTION: Correct either the attribute name or the index value specified.
PARAMS: The attribute name.

ERROR: [DM_QUERY_E_UPDATE_GROUP_P]

SEVERITY: ERROR
DESCRIPTION: UPDATE: You must have CREATE GROUP, SYSADMIN, or SUPERUSER privilege to update groups.
CAUSE: You have attempted update objects of the dm_group type, or a subtype of dm_group,y with insufficient privilege to do so.
ACTION: None.
PARAMS:

ERROR: [DM_QUERY_E_UP_NOT_UPDATEABLE]

SEVERITY: ERROR
DESCRIPTION: S You have specified a non updateable type name (%s).
CAUSE: The name that you specified in your update, change, or create statement is not an updateable type. Internal types, and the dm_type type are not updateable.
ACTION: None.
PARAMS: The name you specified in your update statement.

ERROR: [DM_QUERY_E_REG_ATTR]

SEVERITY: ERROR
DESCRIPTION: REGISTER: An error has occurred which caused your statement to fail.
CAUSE: An error occurred while defining the Documentum object which represents a registered table.
ACTION: There will be another error message following this one (possibly more than one) which describes the reason for the failure. The most probable cause of this error is that a name (column, table, or owner name) was too long. Correct the problem and resubmit the query.
PARAMS: None.

ERROR: [DM_QUERY_E_UP_NOT_ATTR]

SEVERITY: ERROR
DESCRIPTION: S The attribute %s is not an attribute of the specified type.
CAUSE: The attribute you are attempting to set, or the attribute you are using to set another value, is not an attribute of the type specified in your update or create object statement.
ACTION: Either correct the attribute name, or correct the type name.
PARAMS: The attribute name.

ERROR: [DM_QUERY_E_ALTER_ERROR]

SEVERITY: ERROR
DESCRIPTION: ALTER TYPE: statement failure. Check the following messages for more information.
CAUSE: Your alter type statement failed due to incorrect specification.
ACTION: There are additional error messages on the queue from the type manager which explain the exact cause of the failure, and the actions you can take to correct it.
PARAMS: None.

ERROR: [DM_QUERY_E_COMPOSITE_5]

SEVERITY: ERROR
DESCRIPTION: A correlated reference appears in a non-nested SELECT.
CAUSE: You have specified a column specification in an IN COMPOSITE clause. Column specifications are only valid if they are correlated references to a column in an outer SELECT. Your SELECT is not nested.
ACTION: Use an ID specification to refer to the composite in your IN COMPOSITE clause.
PARAMS: None.

ERROR: [DM_QUERY_E_OFFSET_NOT_IN_SL]

SEVERITY: ERROR
DESCRIPTION: The special keyword OFFSET must appear in the select list.
CAUSE: It is a restriction that if the special keyword OFFSET appears in a where clause, it must also appear in the select list. This is a current limitation due to implementation considerations.
ACTION: Add OFFSET to your select list.
PARAMS:

ERROR: [DM_QUERY_E_UP_PERMIT]

SEVERITY: ERROR
DESCRIPTION: SI UPDATE: The permit (%s) cannot be updated with an integer value (%d) less than 1 or greater than 7.
CAUSE: You have attempted to assign an invalid integer value to a permit attribute.
ACTION: Correct your update statement and retry.
PARAMS: The first parameter is the attribute that is being updated, and the second parameter is the integer value that was specified.

ERROR: [DM_QUERY_E_COMPOUND_ID]

SEVERITY: ERROR
DESCRIPTION: S IN DOCUMENT or IN ASSEMBLY clause has an invalid ID specification (%s).
CAUSE: The ID specified in your compound document clause is not a valid ID.
ACTION: Correct the ID specification in your query and retry.
PARAMS: The invalid ID.

ERROR: [DM_QUERY_E_MODIFY_ATTR_NOT]

SEVERITY: ERROR
DESCRIPTION: SS ALTER TYPE: The attribute %s is not an attribute of the type %s.
CAUSE: You have specified an attribute in the MODIFY clause of an ALTER TYPE statement that does not exist in the specified type. Note that for ALTER TYPE, the attribute must be a defined attribute of the type, not an inherited attribute. To modify an inherited attribute of this type, you must alter the supertype for which the attribute was defined.
ACTION: Correct the attribute in your MODIFY clause.
PARAMS: The attribute name and type name as they appear in your statement.

ERROR: [DM_QUERY_E_DOC_PRED]

SEVERITY: ERROR
DESCRIPTION: S You have specified a SysObject predicate (%s), but a dm_sysobject subtype was not specified as the first type in the FROM clause in this select or subselect.
CAUSE: Some of the DQL predicates are only valid for SysObjects. The parameter indicated one of those predicates. When more than one type is joined in a query, this predicate will be applied only to the first (left to right) type encountered in the FROM clause.
ACTION: Remove the SysObject predicate from your query.
PARAMS: The parameter specifies the predicate.

ERROR: [DM_QUERY_E_WHITESPACE]

SEVERITY: ERROR
DESCRIPTION: S You have specified a word (%s) containing whitespace.
CAUSE: Whitespace (spaces, tabs, etc.) are not allowed within words in a contains condition.
ACTION: Reformulate your query and retry.
PARAMS: The word containing whitespace.

ERROR: [DM_QUERY_E_TABLE_NO_ACCESS]

SEVERITY: ERROR
DESCRIPTION: SS The table, %s.%s, is not registered or you do not have access to it.
CAUSE: You have specified a table in your query which is either not a registered table, or is a registered table which you do not have access to.
ACTION: If the table is registered, check with the owner of the registered table, or a Documentum superuser, about giving you access to the table. You will need at least a BROWSE permit on the registered table object in order to access it. If the table has not yet been registered, check with the tables owner about registering it. Note that you must have READ access to the dm_registered object for this table in order to access it in any way (SELECT, INSERT, UPDATE, DELETE). In addition, your access to the actual table is checked to be sure you have the appropriate permission on it.
PARAMS: The two parameters specify the two-part table name (owner.table). Note that if you specified the special dm_dbo document base owner, the first parameter will hold the actual name of the document base owner.

ERROR: [DM_QUERY_E_KEYWORD_NEEDED]

SEVERITY: ERROR
DESCRIPTION: S You have specified one of the special fulltext keywords (%s)in the ORDER BY clause.
CAUSE: You have specified one of the special fulltext keywords in the ORDER BY clause, but the same keyword does not appear in the select list for your select statement or subselect.
ACTION: It is required that elements specified in the order by clause must also appear in the select list. Add the keyword(s) to the select list to correspond to the order by clause.
PARAMS: The keyword specified.

ERROR: [DM_QUERY_E_COMPOUND_UPD]

SEVERITY: ERROR
DESCRIPTION: IN ASSEMBLY clause with NODE appears in an UPDATE OBJECT statement.
CAUSE: You have specified an IN ASSEMBLY clause within an UPDATE OBJECT statement. This is not allowed if there is also a NODE phrase specified.
ACTION: You could make an assembly for the node, and then specify it directly in the IN ASSEMBLY clause.
PARAMS:

ERROR: [DM_QUERY_E_NOT_REPEATING]

SEVERITY: ERROR
DESCRIPTION: S You have specified a non-repeating attribute (%s) in a repeating attribute predicate.
CAUSE: The ANY repeating attribute predicates must have a repeating attribute as an argument. The attribute you have specified is a non-repeating attribute. Note that if you are joining multiple types together, you should disambiguate attribute references in order to ensure that this check is being made against the correct type.
ACTION: Correct the query.
PARAMS: The name of the invalid attribute.

ERROR: [DM_QUERY_E_COMPOUND_CONTID_2]

SEVERITY: ERROR
DESCRIPTION: You have specified CONTAIN_ID more than once in a single select list.
CAUSE: The CONTAIN_ID special keyword may only appear once in a select list.
ACTION: Remove the second and any subsequent occurrences of CONTAIN_ID from your select list and retry the query.
PARAMS:

ERROR: [DM_QUERY_E_UNION_ORDER]

SEVERITY: ERROR
DESCRIPTION: You have specified a non-integer token in an ORDER BY clause with UNION.
CAUSE: When select blocks are unioned together, the order by clause must specify an integer, signifying the ordinal position within the select list of the attribute to be sorted on.
ACTION: Respecify your query using an integer in the order by clause.
PARAMS:

ERROR: [DM_QUERY_E_NO_SYSCAB]

SEVERITY: ERROR
DESCRIPTION: REGISTER: Unable to link the table to the System cabinet.
CAUSE: The System cabinet was not found. All registered tables are linked into the System cabinet. Your register statement failed.
ACTION: See your Documentum system administrator about making sure that the System cabinet exists. The System cabinet is created during Documentum installation, so either it has been inadvertently dropped by a superuser, or an internal problem is causing Documentum to be unable to find it. If the System cabinet does exist, contact your Documentum site representative.
PARAMS: None.

ERROR: [DM_QUERY_E_DATE_FORMAT]

SEVERITY: ERROR
DESCRIPTION: S The specified date literal (%s) is not in a recognized format, or is out of the valid date range.
CAUSE: You have incorrectly specified a date literal.
ACTION: Correct your date literal to be in one of the valid date forms. Note that all four digits of the year must be specified. Examples: 2/14/1992, 02/14/1991, February 14, 1992 Note that a legal date needs to be in the following range: (1) year: (1753, 4712), inclusively. (2) month: (1, 12), inclusively. (3) day: (1, n), inclusively, where n is 31 for January, March, May, July, August, October, December. 28 for February (29 if leap year). 30 for other months. (4) hour: (0, 24), inclusively. (5) minute: (0, 60), inclusively. (6) second: (0, 60), inclusively.
PARAMS: The parameter contains the incorrectly specified date.

ERROR: [DM_QUERY_E_ALTER_INTERNAL_DROP]

SEVERITY: ERROR
DESCRIPTION: ALTER TYPE: You have attempted to DROP an internal or readonly attribute.
CAUSE: Internal and readonly attributes (those with names beginning with `i_ or `r_) cannot be dropped.
ACTION: None.
PARAMS: None.

ERROR: [DM_QUERY_E_UP_CHAR]

SEVERITY: ERROR
DESCRIPTION: SS UPDATE: You have attempted to set a non-string attribute (%s) with a string value (%s).
CAUSE: No type conversion is done between a character string literal and a non-string attribute. ACTUON: Correct your update statement and retry.
ACTION:
PARAMS: The attribute name, and the specified character string value.

ERROR: [DM_QUERY_E_CHG_BAD_ATTR]

SEVERITY: ERROR
DESCRIPTION: S The attribute %s cannot be set in a CHANGE statement.
CAUSE: You have tried to set the value of one of the following attributes in a CHANGE statement: (a) a_full_text, (b) a_storage_type, and (c) a_content_type
ACTION: You have to CHANGE the type first, then use UPDATE statement to set the required value.
PARAMS:

ERROR: [DM_QUERY_E_MODIFY_ATTR_NO_MOD]

SEVERITY: ERROR
DESCRIPTION: SS ALTER TYPE: The attribute %s is not an accessible attribute of the type %s.
CAUSE: You have specified an attribute in the MODIFY clause of an ALTER TYPE statement that is not accessible through DQL.
ACTION: Remove the attribute from your MODIFY clause.
PARAMS: The attribute name and type name as they appear in your statement.

ERROR: [DM_QUERY_E_CHANGE_NON_SYSOBJECT]

SEVERITY: ERROR
DESCRIPTION: The CHANGE OBJECT statement can only be used on dm_sysobject or its subtypes.
CAUSE: The type specified in a CHANGE … OBJECT statement is not a dm_sysobject or a subtype of dm_sysobject.
ACTION: Specify a type that is a dm_sysobject or one of its subtypes.
PARAMS:

ERROR: [DM_QUERY_E_EXEC_VALUE_LIST_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: S EXECUTE: You have specified a value list with values of differing datatypes for argument %s.
CAUSE: Argument values may be integers, booleans (TRUE or FALSE), or character string literals only, and in a value list the datatypes must all be identical.
ACTION: Correct the value list specification and retry.
PARAMS:

ERROR: [DM_QUERY_E_COMPOUND_CYCLE]

SEVERITY: ERROR
DESCRIPTION: I IN DOCUMENT recursion has encountered a cycle at depth %d.
CAUSE: The compound document hierarchy your query is traversing contains a cycle.
ACTION: Locate the cycle and remove the document that is causing it. The last result returned by the query is the document node immediately before the node causing the cycle. The depth number may help you determine the location. For additional assistance determining the location of the cycle, turn tracing on.
PARAMS: The depth at which the node causing the cycle was encountered.

ERROR: [DM_QUERY_E_BAD_ID]

SEVERITY: ERROR
DESCRIPTION: S The string specified for an ID value (%s) was not a valid Documentum dmID.
CAUSE: The string does not properly represent an ID value.
ACTION: The strings representing an ID must conform to a very rigid, internal format. ID strings should only be used in queries if they are copied directly from the dmID value of an existing Documentum object. Check the specified ID string against the dmID of the object you were attempting to query, and correct it as appropriate.
PARAMS: The parameter specifies the incorrect ID string.

ERROR: [DM_QUERY_E_NOT_OWNER]

SEVERITY: ERROR
DESCRIPTION: S %s: You have attempted to register or unregister a table that is not owned by you.
CAUSE: You may only register or unregister a table if you are its owner, or if you are a Documentum SuperUser.
ACTION: Check with the tables owner or a SuperUser about registering it.
PARAMS: The parameter gives the specific statement that the error occurred in.

ERROR: [DM_QUERY_E_ESCAPE_LENGTH]

SEVERITY: ERROR
DESCRIPTION: S The ESCAPE character in your LIKE predicate is not one character long (%s).
CAUSE: The escape character must be exactly one character.
ACTION: Reformulate your LIKE predicate, using one character for the escape.
PARAMS: The parameter holds the string that you specified.

ERROR: [DM_QUERY_E_IS_REPLICA_SUB]

SEVERITY: ERROR
DESCRIPTION: You have specified ISREPLICA in a select list that is not the outermost select list.
CAUSE: The ISREPLICA special keyword may only appear in the outermost select list.
ACTION: Reword your query, removing the ISREPLICA keyword from all parts of the query besides the outermost select list.
PARAMS:

ERROR: [DM_QUERY_E_BAD_SUBQUERY]

SEVERITY: ERROR
DESCRIPTION: SS %s: An invalid attribute (%s) was returned by the subquery. Your statement was not executed.
CAUSE: The subquery in this statement returned an attribute that is not valid in this context.
ACTION: Check the value of the parameter for the reason the attribute was invalid, and reformulate the query.
PARAMS: The parameter is a string containing the reason for the failure. The two possible reasons are: string too long: The subquery returned a string valued attribute with a length that is too long to represent a valid user name. not a string datatype: The subquery returned an attribute that was not a string.

ERROR: [DM_QUERY_E_EXEC_NO_REPEAT]

SEVERITY: ERROR
DESCRIPTION: S EXECUTE: You have specified an argument (%s) twice, but it is not a repeatable argument.
CAUSE: The argument may only be specified once.
ACTION: Correct the query and retry.
PARAMS:

ERROR: [DM_QUERY_E_UP_NOT_SYSOBJ]

SEVERITY: ERROR
DESCRIPTION: You have specified LINK or MOVE TO for a non-SysObject type.
CAUSE: Only SysObjects may be linked or moved to a folder.
ACTION:
PARAMS:

ERROR: [DM_QUERY_E_BAD_USER_SAVE]

SEVERITY: ERROR
DESCRIPTION: S GRANT or REVOKE: Unable to save the user (%s).
CAUSE: An error has occurred which prevented a user from being saved in the database. Your grant or revoke statement failed.
ACTION: There will be a message from the Save() method which will explain the reason for this error. Follow the directions in that message to correct the problem.
PARAMS: The parameter specifies the name of the user for which the Save() failed. However, since grant and revoke have all-or-nothing semantics, none of the users specified in your statement have been changed by this statement.

ERROR: [DM_QUERY_E_QUERY_IS_NOT_FTDQL]

SEVERITY: ERROR
DESCRIPTION: You specified ENABLE(FTDQL) hint for a SELECT statement that does not conform to the rules of FTDQL
CAUSE: User specified ENABLE(FTDQL) hint for a query which does not conform to the rules of FTDQL.
ACTION: Remove the FTDQL hint from the list of hints specified in the query. If no other hints are present in the query, remove the ENABLE clause from the query.
PARAMS:

ERROR: [DM_QUERY_E_NO_SET_FUNC]

SEVERITY: ERROR
DESCRIPTION: Set Functions are not permitted in WHERE or WITH clauses.
CAUSE: You have specified a set function (max, min, count, sum, avg) in a WHERE or WITH clause. This is not allowed. Set functions may be specified in a HAVING clause.
ACTION: Reformulate your query using HAVING.
PARAMS: None.

ERROR: [DM_QUERY_E_UP_BOOL]

SEVERITY: ERROR
DESCRIPTION: SI UPDATE: You have attempted to set a boolean attribute (%s) with a non-boolean integer value (%d).
CAUSE: The value specified for updating a boolean attribute must be either 0 or 1 (denoted in DQL by the special keywords FALSE and TRUE, respectively). ACTUON: Correct your update statement and retry.
ACTION:
PARAMS: The attribute name, and the incorrect integer value.

ERROR: [DM_QUERY_E_REPEATING_REQUIRED]

SEVERITY: ERROR
DESCRIPTION: S You have specified a single-valued attribute (%s) where a repeating attribute is required.
CAUSE: In the search conditions specified within an ANY() or ONLY() predicate, repeating attributes are required.
ACTION: Reconstruct your query, moving search conditions referencing single-valued attributes outside the ANY or ONLY predicate.
PARAMS: The parameter is the single-valued attribute name.

ERROR: [DM_QUERY_E_NO_PRIV_PRIV]

SEVERITY: ERROR
DESCRIPTION: You have insufficient privilege to GRANT or REVOKE user privileges.
CAUSE: You must have SYSADMIN privilege to do privilege operations.
ACTION: Ask your system administrator about doing the operation for you.
PARAMS: None.

ERROR: [DM_QUERY_E_COMPOSITE_3]

SEVERITY: ERROR
DESCRIPTION: ORDER keyword used without IN COMPOSITE clause.
CAUSE: If the ORDER keyword is specified in a query, the IN COMPOSITE clause is required.
ACTION: Composites are a deprecated feature. The ORDER keyword is no longer supported.
PARAMS: None.

ERROR: [DM_QUERY_E_COMPOUND_VL]

SEVERITY: ERROR
DESCRIPTION: SS IN DOCUMENT or IN ASSEMBLY version label (%s) does not have a match in the version branch containing %s.
CAUSE: You have specified a version label that does not exist for any object in the version branch containing the SysObject you specified by ID for the root of your document search.
ACTION: Correct your query and retry.
PARAMS: The version label and ID as specified in your query.

ERROR: [DM_QUERY_E_OWNER_PERMIT]

SEVERITY: ERROR
DESCRIPTION: ALTER TYPE: You may not set the default owner permit to a permit level less than VERSION.
CAUSE: A set clause in your ALTER TYPE statement has attempted to set the default owner permit to NONE, BROWSE, READ, or NOTE. Owners of objects need to have permits at these levels in order to manage their objects. An owner may explicitly deny himself or herself access to an object, but a type may not overly restrict owners of created objects by default. The ALTER TYPE statement failed.
ACTION: Correct the permit level for the OWNER PERMIT setting in the SET clause and resubmit the entire ALTER TYPE statement.
PARAMS: None.

ERROR: [DM_QUERY_E_NO_CREATE_PRIV]

SEVERITY: ERROR
DESCRIPTION: CREATE TYPE: You have insufficient privilege to create a type.
CAUSE: You do not have superuser, sysadmin, or create type privilege.
ACTION: Ask your system administrator about either granting you create type privilege, or creating the type for you.
PARAMS: None.

ERROR: [DM_QUERY_E_STAR_WITHOUT_TYPE]

SEVERITY: ERROR
DESCRIPTION: You have incorrectly specified a star (*) in the select list of a select statement.
CAUSE: A star is not valid in the select list unless a type is specified in the from clause.
ACTION: Correct the query to specify all of the select list items explicitly.
PARAMS: None.

ERROR: [DM_QUERY_E_COMPOUND_NS_SUB]

SEVERITY: ERROR
DESCRIPTION: IN DOCUMENT clause contains NODESORT within a subquery.
CAUSE: You have specified an IN DOCUMENT clause containing a NODESORT specification within a subquery. NODESORT may only appear in the outermost SELECT. This is because the ultimate usage of NODESORT, which is to identify which of competing versions of a document at a particular node is to be chosen, is only performed at the outermost SELECT level.
ACTION: None.
PARAMS:

ERROR: [DM_QUERY_E_COMPOUND_NCCS]

SEVERITY: ERROR
DESCRIPTION: A non-correlated column specification appears in an IN DOCUMENT or IN ASSEMBLY clause.
CAUSE: You have specified a column reference for the rootnode id of a compound document clause, but the column is not qualified. The column reference in an IN DOCUMENT or IN ASSEMBLY clause must be qualified, and it must be a correlated reference to a column in an outer SELECT.
ACTION: Qualify your column name with a correlation variable referring to an outer SELECT.
PARAMS: None.

ERROR: [DM_QUERY_E_COMPOUND_COL_N]

SEVERITY: ERROR
DESCRIPTION: Your IN ASSEMBLY clause has both a column specification and a NODE.
CAUSE: If you specify the ID of the root node in an IN ASSEMBLY clause as a column specification, you may not also specify the NODE phrase.
ACTION: Reformulate your query.
PARAMS:

ERROR: [DM_QUERY_E_BAD_ATTRIBUTE]

SEVERITY: ERROR
DESCRIPTION: SS The attribute name, %s, is not an attribute of the queried type, %s.
CAUSE: You have specified an attribute that does not exist in the type that you are querying.
ACTION: Check to be sure that all the attributes specified in the query are attributes of the type which is specified in the FROM clause. Only attributes of the queried type may be specified. (Attributes of subtypes of the queried type may not be specified in the query.)
PARAMS: The first parameter is the attribute that does not exist in the type (second parameter).

ERROR: [DM_QUERY_E_PUBLIC_NOT_IN_SL]

SEVERITY: ERROR
DESCRIPTION: The special keyword ISPUBLIC must appear in the select list.
CAUSE: It is a restriction that if the special keyword ISPUBLIC appears in a where clause, it must also appear in the select list. This is a current limitation due to implementation considerations.
ACTION: Add ISPUBLIC to your select list.
PARAMS:

ERROR: [DM_QUERY_E_REG_TABLE_PERMIT_U]

SEVERITY: ERROR
DESCRIPTION: You have attempted to set a table permission attribute of the registered table.
CAUSE: Only the owner of the registered table or a superuser may update the table permission attributes of a registered table.
ACTION: Contact the owner or a superuser and ask them to make the change for you.
PARAMS:

ERROR: [DM_QUERY_E_ALTER_INTERNAL_ADD]

SEVERITY: ERROR
DESCRIPTION: ALTER TYPE: You have attempted to ADD internal or readonly attribute.
CAUSE: Internal and readonly attributes (those with names beginning with `i_ or `r_) can only be added by a superuser, and even then should only be done if requested as part of a Documentum release script.
ACTION: None.
PARAMS: None.

ERROR: [DM_QUERY_E_CHANGE_TYPES2]

SEVERITY: ERROR
DESCRIPTION: CHANGE: You have specified types that have a base type between them.
CAUSE: You cannot change objects from one type to another if the two types are separated by a Documentum base type. For example, from a subtype of dm_document to dm_sysobject.
ACTION: None.
PARAMS:

ERROR: [DM_QUERY_E_NOT_CABINET_ID]

SEVERITY: ERROR
DESCRIPTION: S You have specified an ID value ( %s ) that is not a valid cabinet ID.
CAUSE: The CABINET predicate must specify a cabinet ID. The ID you have specified may be a valid object ID, but it is not the ID of a cabinet.
ACTION: Correct the ID specification.
PARAMS: The ID value as specified in your CABINET predicate.

ERROR: [DM_QUERY_E_UPDATE_SUB]

SEVERITY: ERROR
DESCRIPTION: S UPDATE: An error occurred during the processing of a subquery for attribute %s.
CAUSE: A subquery in one of the set, append, or insert clauses of your update statement returned no values, returned invalid values, or some other error occurred during its processing. There will be another error message which explains the cause of the failure.
ACTION: Follow the suggested action in the other error message(s).
PARAMS:

ERROR: [DM_QUERY_E_DOC_ALL]

SEVERITY: ERROR
DESCRIPTION: You have specified (ALL) in the FROM clause, but the type specified is not a dm_sysobject subtype.
CAUSE: Your query contains a select or subselect with the (ALL) modifier in the from clause. (ALL) is only valid for versioned types. dm_sysobject and subtypes of dm_sysobject are the only versioned types.
ACTION: Check to make sure you have correctly specified the type. If it is not a versioned type, leave the (ALL) modifier off of the from clause.
PARAMS: None.

ERROR: [DM_QUERY_E_NO_SUPER_PRIV]

SEVERITY: ERROR
DESCRIPTION: S You have insufficient privilege to GRANT or REVOKE %s privilege.
CAUSE: You must have SUPERUSER privilege to GRANT or REVOKE SUPERUSER or SYSADMIN privilege.
ACTION: None.
PARAMS: The privilege you attempted to GRANT or REVOKE.

ERROR: [DM_QUERY_E_EXEC_BAD_DATATYPE]

SEVERITY: ERROR
DESCRIPTION: SS EXECUTE: You have specified a value that is not the same datatype as the argument %s (%s)
CAUSE: Argument values must match the predefined datatype of the argument.
ACTION: Correct the value specification and retry.
PARAMS: The argument name, and the expected datatype name.

ERROR: [DM_QUERY_E_COMPOUND_UNION]

SEVERITY: ERROR
DESCRIPTION: IN DOCUMENT clause is combined with UNION.
CAUSE: You cannot UNION together SELECTs if any of them require recursion. Your IN DOCUMENT clause requires recursion.
ACTION: Run the SELECTs separately. Alternatively, you could create an assembly on the root node specified in your IN DOCUMENT clause, and then formulate your query with USING ASSEMBLIES. This would avoid the need for the query to be processed recursively, and it could then be UNIONed.
PARAMS:

ERROR: [DM_QUERY_E_ID_NOT_VALID]

SEVERITY: ERROR
DESCRIPTION: The ID datatype is not valid in REGISTER statements.
CAUSE: The ID datatype is an internal datatype that is meaningful only for Documentum types.
ACTION: Check the datatypes in the table you are registering, and use datatype names that corresponds to the database datatypes.
PARAMS: None.

ERROR: [DM_QUERY_E_REPEAT_POS]

SEVERITY: ERROR
DESCRIPTION: You have specified repeating attribute(s) and TAG or POSITION in the same select.
CAUSE: Repeating attributes may not be selected in the same select statement or subselect as TAG and/or POSITION.
ACTION: Correct and retry the query.
PARAMS: None.

ERROR: [DM_QUERY_E_SEARCH_NEEDED]

SEVERITY: ERROR
DESCRIPTION: You have specified one of the special fulltext keywords without a SEARCH clause.
CAUSE: You have specified TAG, SCORE, or POSITION in your select list or order by clause, but have not specified a SEARCH clause in your select statement or subselect. These special keywords have no meaning without a fulltext search.
ACTION: Remove the keyword(s) from your query, or specify a SEARCH clause.
PARAMS: None.

ERROR: [DM_QUERY_E_IS_REPLICA_2]

SEVERITY: ERROR
DESCRIPTION: You have specified ISREPLICA more than once in the select list.
CAUSE: The ISREPLICA special keyword may only appear once in the select list.
ACTION: Reword your query, removing the extra ISREPLICA keywords from the select list.
PARAMS:

ERROR: [DM_QUERY_E_CREATE_FAILED2]

SEVERITY: ERROR
DESCRIPTION: S CREATE TYPE statement failed because attribute %s could not be added.
CAUSE: There should be another message on your message queue which explains the reason for this failure. If there is no additional message, the cause of this failure is that the attribute specified already exists in one of the types supertypes.
ACTION: Check the other messages for this query and take the action described therein to correct this problem. Then retry your query.
PARAMS: The parameter specifies the attribute name.

ERROR: [DM_QUERY_E_GROUP_BY_STAR]

SEVERITY: ERROR
DESCRIPTION: A star (*) may not be specified in the select list if GROUP BY is also specified for this query.
CAUSE: If a GROUP BY clause is specified, the attributes in the select list must be explicitly named.
ACTION: Replace the * in the select list with a list of attributes.
PARAMS: None.

ERROR: [DM_QUERY_E_UNION_NOT]

SEVERITY: ERROR
DESCRIPTION: S UNION is not supported by your RDBMS (%s).
CAUSE: You have specified a UNION, but this is not supported by your rdbms.
ACTION: Recompose your queries without union.
PARAMS: The name of your rdbms.

ERROR: [DM_QUERY_E_MODIFY_ATTR_LEN]

SEVERITY: ERROR
DESCRIPTION: SII ALTER TYPE: The attribute %s is longer (%d) than the specified length %d.
CAUSE: Your MODIFY clause would shorten a string attribute. That is not allowed. The only modification allowed is lengthening strings.
ACTION: None.
PARAMS: The attribute name, its current length, and the length the ALTER TYPE statement specified.

ERROR: [DM_QUERY_E_UP_USER]

SEVERITY: ERROR
DESCRIPTION: S You have attempted to assign the USER special value to a non-string attribute (%s).
CAUSE: The USER value may only be assigned to string-typed attributes.
ACTION: Correct the query and retry.
PARAMS: The non-string attribute.

ERROR: [DM_QUERY_E_DOC_CLAUSE]

SEVERITY: ERROR
DESCRIPTION: You have specified a SEARCH clause or fulltext keyword, but a dm_sysobject type was not specified in this select or subselect.
CAUSE: Only dm_sysobject and its subtypes are subject to fulltext searching. You have specified a fulltext search (by specifying the SEARCH clause or including a fulltext keyword) on a non-sysobject type.
ACTION: Remove the SEARCH clause or fulltext keyword, or specify a type which is a dm_sysobject type in the FROM clause.
PARAMS: None.

ERROR: [DM_QUERY_E_REG_ALREADY]

SEVERITY: ERROR
DESCRIPTION: S REGISTER: Table %s was already registered.
CAUSE: You have attempted to register a table that is already registered.
ACTION: No action is required. The table is already registered. If your intent was to revise the description of the registered table (change the column description or add a key, for instance), you must first UNREGISTER the table, and then REGISTER it again.
PARAMS: The parameter specifies the registered table name.

ERROR: [DM_QUERY_E_COMPOSITE_1]

SEVERITY: ERROR
DESCRIPTION: ORDER keyword used in ORDER BY clause, but not in select list.
CAUSE: You have attempted to order your query results by specifying the order keyword in the order by clause, but have not also specified the order keyword in the select list.
ACTION: Composites are a deprecated feature. The ORDER keyword is no longer supported.
PARAMS: None.

ERROR: [DM_QUERY_E_COMPOUND_NODE_ID]

SEVERITY: ERROR
DESCRIPTION: S Your NODE phrase has an invalid ID specification (%s).
CAUSE: The ID specified in your ASSEMBLY clauses NODE phrase is not a valid ID.
ACTION: Correct the ID specification in your query and retry.
PARAMS: The invalid ID.

ERROR: [DM_QUERY_E_UP_SUB_MORE]

SEVERITY: ERROR
DESCRIPTION: UPDATE: A subquery in your update statement has returned more than one row.
CAUSE: Subqueries used for setting a value in an update statement must return exactly one row. Only APPENDs may set more than one value.
ACTION:
PARAMS:

ERROR: [DM_QUERY_E_DROP_TYPE_TYPE]

SEVERITY: ERROR
DESCRIPTION: DROP TYPE: You have attempted to drop the dm_type type.
CAUSE: The DROP TYPE statement specified dm_type. It is illegal to drop the dm_type type.
ACTION: None. The dm_type type cannot be dropped.
PARAMS: None.

ERROR: [DM_QUERY_E_UP_BAD_ATTR_SPEC]

SEVERITY: ERROR
DESCRIPTION: S The attribute specification for attribute %s is in error.
CAUSE: Attribute specifications may be one or two part names (correlation.attribute). You have specified a three part name.
ACTION: Correct the query and retry.
PARAMS: The name of the attribute that is incorrectly specified.

ERROR: [DM_QUERY_E_PAGE_NO_NOT_IN_SL]

SEVERITY: ERROR
DESCRIPTION: The special keyword PAGE_NO must appear in the select list.
CAUSE: It is a restriction that if the special keyword PAGE_NO appears in a where clause, it must also appear in the select list. This is a current limitation due to implementation considerations.
ACTION: Add PAGE_NO to your select list.
PARAMS:

ERROR: [DM_QUERY_E_TYPE_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: S ALTER or DROP TYPE: The type, %s, was not found. A type of this name does not exist.
CAUSE: The type specified is not a valid type.
ACTION: In the case of DROP TYPE, the type has apparently already been dropped, so no further action is required. In the case of ALTER TYPE, check to make sure the name is spelled correctly. The type may have to be recreated.
PARAMS: The parameter specifies the type name as it appeared in the query.

ERROR: [DM_QUERY_E_BAD_SUPERTYPE]

SEVERITY: ERROR
DESCRIPTION: CREATE TYPE: A non-subtypeable type was specified as supertype.
CAUSE: You have specified a supertype which cannot be subtyped. Only dm_sysobject and dm_user, and their subtypes, may be subtyped.
ACTION: Correct the query and retry.
PARAMS: None.

ERROR: [DM_QUERY_E_UP_CURSOR]

SEVERITY: ERROR
DESCRIPTION: S A database error has occurred during the creation of a cursor for %s.
CAUSE: A DQL UPDATE statement is turned into an SQL SELECT statement that identifies the Documentum objects that will be updated. This error message indicates that a failure occurred during the parsing of the generated SQL statement by the underlying RDBMS.
ACTION: The error message from the RDBMS is shown in the following message. Use that error message to figure out what has happened. Typically, it will be evident that an error in the formulation of your UPDATE statement has been translated into an error in the SQL select statement. Correct your DQL UPDATE statement accordingly.
PARAMS: The parameter contains the SQL SELECT statement that was produced to select Documentum objects.

ERROR: [DM_QUERY_E_ID_LENGTH]

SEVERITY: ERROR
DESCRIPTION: SI The identifier, %s, exceeds the maximum identifier length allowed (%d).
CAUSE: You have specified an identifier which is too long.
ACTION: Shorten the identifier. If the identifier is the name of a table in the database, then see if there is a mechanism for defining a shorter synonym for the table name in the database.
PARAMS: The first parameter specifies the identifier which is too long. The second parameter gives the maximum allowable length for an identifier of this type.

ERROR: [DM_QUERY_E_UPDATE_SUB_EMPTY]

SEVERITY: ERROR
DESCRIPTION: UPDATE: Your update subquery returned no values.
CAUSE: A subquery in one of the set, append, or insert clauses of your update statement returned no values.
ACTION: Reformulate your update statement without the empty subquery, or reformulate the subquery so that it will return a value.
PARAMS: None.

ERROR: [DM_QUERY_E_NOT_RESTRICTED_FOLDER_PATH]

SEVERITY: ERROR
DESCRIPTION: S You have specified a folder path ( %s ) that is not a folder (or subfolder of a folder) in the users restricted_folder_ids.
CAUSE: If restricted_folder_ids is specified, the FOLDER predicate must specify a folder path either in the restricted_folder_ids or a subfolder in the list. The path you have specified may be a valid path, but it is not in the users restricted_folder_ids list.
ACTION: Correct the path specification.
PARAMS: The path value as specified in your FOLDER predicate.

ERROR: [DM_QUERY_E_NOT_RESTRICTED_FOLDER_ID]

SEVERITY: ERROR
DESCRIPTION: D You have specified an ID value ( %s ) that is not a folder (or subfolder of a folder) in the users restricted_folder_ids.
CAUSE: If restricted_folder_ids is specified, the FOLDER predicate must specify a folder ID either in the restricted_folder_ids or a subfolder in the list. The ID you have specified may be a valid object ID, but it is not in the users restricted_folder_ids list.
ACTION: Correct the ID specification.
PARAMS: The ID value as specified in your FOLDER predicate.

ERROR: [DM_QUERY_E_UP_IMMUTABLE]

SEVERITY: ERROR
DESCRIPTION: Your UPDATE or CHANGE statement has tried to update an immutable object.
CAUSE: You cannot update or change an immutable object.
ACTION: Add a clause to your WHERE clause that restricts the UPDATE or CHANGE statement to non-immutable objects: where r_immutable_flag = false
PARAMS:

ERROR: [DM_QUERY_E_UP_MAX_APPEND]

SEVERITY: ERROR
DESCRIPTION: You have specified an invalid maximum append value.
CAUSE: Zero is not a valid number for the maximum number of appends allowed from a subselect in an update or create object statement.
ACTION: Correct your query and retry.
PARAMS:

ERROR: [DM_QUERY_E_UPDATE_INDEX]

SEVERITY: ERROR
DESCRIPTION: SSI UPDATE: Unable to %s the attribute %s at index %d.
CAUSE: The index value is probably erroneous.
ACTION: Correct the index value and retry.
PARAMS:

ERROR: [DM_QUERY_E_CREATE_BASE_TYPE]

SEVERITY: ERROR
DESCRIPTION: CREATE TYPE: You must be a superuser to create a Documentum base type.
CAUSE: You have attempted to create a type with a name beginning with dm which denotes a Documentum base type. Only superusers may create base types, and then only if an install script for a new release of the product directs them to do so.
ACTION: Give your type a name that is not reserved by Documentum.
PARAMS: None.

ERROR: [DM_QUERY_E_IS_GROUP]

SEVERITY: ERROR
DESCRIPTION: S CREATE GROUP: The group specified (%s) already exists.
CAUSE: You have attempted to create a group with a name that already exists.
ACTION: Change the group name and resubmit your query.
PARAMS: The parameter specifies the name of the existing group.

ERROR: [DM_QUERY_E_STRINGLIST_NOT_SUPPORTED]

SEVERITY: ERROR
DESCRIPTION: You have specified a string list in your SEARCH clause where only a single string is valid.
CAUSE: The string list is not supported for the fulltext system that you are using.
ACTION: Reformulate the SEARCH clause with ORs instead of using the string list.
PARAMS: None.

ERROR: [DM_QUERY_E_DATE_FORMAT_EX]

SEVERITY: ERROR
DESCRIPTION: S The specified date literal (%s) is not in a recognized format, or the UTC of the specified date is out of the valid date range.
CAUSE: You have incorrectly specified a date literal or the UTC of the converted date is out of the supported range of the database.
ACTION: Correct your date literal to be in one of the valid date forms. Note that all four digits of the year must be specified. Examples: 2/14/1992, 02/14/1991, February 14, 1992 Note that a legal date needs to be in the following range: (1) year: (1753, 4712), inclusively. (2) month: (1, 12), inclusively. (3) day: (1, n), inclusively, where n is 31 for January, March, May, July, August, October, December. 28 for February (29 if leap year). 30 for other months. (4) hour: (0, 24), inclusively. (5) minute: (0, 60), inclusively. (6) second: (0, 60), inclusively. or the UTC conversion of the specified date is out of the supported range of the database 1753 – 9999.
PARAMS: The parameter contains the incorrectly specified date.

ERROR: [DM_QUERY_E_TOO_MANY_FOLDERS_FOR_FTDQL]

SEVERITY: ERROR
DESCRIPTION: IS The folder predicate in the query exceeds the maximum number of supported folders (%d). Conversion error message from the query plug-in: %s
CAUSE: A query with FOLDER() predicate with DESCEND keyword, and with a SEARCH clause was executed. The total number of descendents exceeds the maximum allowed folders.
ACTION: Cannot execute the query with SEARCH clause in this case, its a limitation.
PARAMS:

ERROR: [DM_QUERY_E_COMPOUND_DEPTH_SL]

SEVERITY: ERROR
DESCRIPTION: You have specified DEPTH somewhere in your query besides the select list.
CAUSE: The DEPTH special keyword may only appear in the select list.
ACTION: Reword your query, removing the DEPTH keyword from all parts of the query besides the select list.
PARAMS:

ERROR: [DM_QUERY_E_COMPOUND_COL_D]

SEVERITY: ERROR
DESCRIPTION: IN DOCUMENT clause has both a column specification and a DESCEND.
CAUSE: If you specify the ID of the root node in an IN DOCUMENT clause as a column specification, you may not also specify DESCEND.
ACTION: Reformulate your query.
PARAMS:

ERROR: [DM_QUERY_E_COMPOUND_NODE_SUB]

SEVERITY: ERROR
DESCRIPTION: Your IN ASSEMBLY clause contains NODE phrase within a subquery.
CAUSE: You have specified an IN ASSEMBLY clause containing a NODE specification within a subquery. NODE may only appear in the outermost SELECT. This is because the query post-processing that is required to deliver the NODE phrase semantics.
ACTION: You could assemble document specified in your NODE phrase separately, and then query it directly in your subquery.
PARAMS:

ERROR: [DM_QUERY_E_INVALID_SETFILE_STMT]

SEVERITY: ERROR
DESCRIPTION: You have used an invalid setfile statement. Verify that you are using the correct form of the setfile statement.
CAUSE: 1) You cannot set content files for subsequent pages of an object without first setting the first content file and specifying its format. 2) You have attempted to replace the first page using the Setfile with content_format = statement. You cannot use this statement to replace the first page.
ACTION: 1) Use the Setfile statement Setfile with content_format = to set the first content file before setting subsequent content files. 2) Use the setfile statement Setfile with page_no = to replace the first page.
PARAMS:

ERROR: [DM_QUERY_E_MODIFY_ATTR_TYPE]

SEVERITY: ERROR
DESCRIPTION: ALTER TYPE: You have specified an invalid datatype in the MODIFY clause.
CAUSE: The only attribute datatype that may be specified in the MODIFY clause of an ALTER TYPE statement is STRING or CHARACTER. Starting from 6.6, we allow an attribute of any datatype to be changed to spaceoptimize.
ACTION: None. You cannot MODIFY attributes except to set a string attribute to a longer string.
PARAMS:

ERROR: [DM_QUERY_E_COMPOUND_TYPE]

SEVERITY: ERROR
DESCRIPTION: IN DOCUMENT or IN ASSEMBLY clause was used without a dm_sysobject type.
CAUSE: You have specified an IN DOCUMENT clause in your query, but the FROM clause does not specify dm_sysobject or a subtype of dm_sysobject.
ACTION: Only SysObjects are contained in compound documents, so a query must specify dm_sysobject or one of its subtypes if the IN DOCUMENT clause is used. Modify your query as appropriate and retry.
PARAMS: None.

ERROR: [DM_QUERY_E_COLUMN_QUAL]

SEVERITY: ERROR
DESCRIPTION: S The column or attribute name %s must be qualified.
CAUSE: In a SELECT statement, if a type is specified in the from clause and registered tables are also specified, then all attribute and column names must be qualified.
ACTION: Qualify all column and attribute references with typename, tablename, or correlation variable qualifiers.
PARAMS: The parameter specifies the particular column or attribute name that was not qualified.

ERROR: [DM_QUERY_E_CONT_ID_NOT_IN_SL]

SEVERITY: ERROR
DESCRIPTION: The special keyword CONTENTID must appear in the select list.
CAUSE: It is a restriction that if the special keyword CONTENTID appears in a where clause, it must also appear in the select list. This is a current limitation due to implementation considerations.
ACTION: Add CONTENTID to your select list.
PARAMS:

ERROR: [DM_QUERY_E_ALTER_TYPE_TOO]

SEVERITY: ERROR
DESCRIPTION: I ALTER TYPE: You have specified too many attributes. The maximum allowed is %d.
CAUSE: You have listed too many attributes.
ACTION: Break your ALTER TYPE statement up into multiple statements so that none of them exceeds the maximum number of attributes allowed in one query.
PARAMS: The maximum number of attributes allowed.

ERROR: [DM_QUERY_E_DEFAULT_NOT_CABINET]

SEVERITY: ERROR
DESCRIPTION: You have specified CABINET(DEFAULT) but your default folder is not a cabinet.
CAUSE: The DEFAULT parameter to the FOLDER or CABINET predicate causes your default folder to be used. If your default folder is not also a cabinet, it is not valid to specify the CABINET predicate.
ACTION: If you want to search your default folder, use the FOLDER(DEFAULT) predicate.
PARAMS: None.

ERROR: [DM_QUERY_E_ACL_TRAN]

SEVERITY: ERROR
DESCRIPTION: ALTER TYPE: You cannot change the default acl when a multi-statement transaction is open.
CAUSE: You have attempted to set the default acl for this type while a multi-statement transaction is in progress. This is not allowed.
ACTION: Change the logic of your application so that the ALTER TYPE statement does not happen within a transaction. (Commit or rollback the in-progress transaction.)
PARAMS:

ERROR: [DM_QUERY_E_ALTER_TYPE_TYPE]

SEVERITY: ERROR
DESCRIPTION: ALTER TYPE: You have attempted to alter the dm_type type.
CAUSE: The ALTER TYPE statement specified dm_type. It is illegal to alter the dm_type type.
ACTION: None. The dm_type type cannot be altered.
PARAMS: None.

ERROR: [DM_QUERY_E_REG_TABLE_QUAL]

SEVERITY: ERROR
DESCRIPTION: S You must provide a table owner name qualification on your reference to table %s.
CAUSE: If you reference a registered table in a query, if you do not provide a fully-qualified name (owner_name.table_name), the owner_name defaults to your database login name. However, you do not have a database login (user_db_name) defined in your Documentum user definition.
ACTION: Fully qualify references to registered tables.
PARAMS:

ERROR: [DM_QUERY_E_REPEAT_REG]

SEVERITY: ERROR
DESCRIPTION: You have specified repeating attribute(s) and columns from a registered table in the same select list.
CAUSE: Repeating attributes may not be selected in the same select statement as columns from registered tables.
ACTION: Correct and retry the query.
PARAMS: None.

ERROR: [DM_QUERY_E_INSERT_ORDER_BY]

SEVERITY: ERROR
DESCRIPTION: The ORDER BY clause in the INSERT statement is only supported for Sybase platform.
CAUSE: You cannot use ORDER BY clause in an INSERT statement for non-Sybase RDBMS.
ACTION: Remove the ORDER BY clause from the INSERT statement.
PARAMS:

ERROR: [DM_QUERY_E_TAG_NOT_IN_SL]

SEVERITY: ERROR
DESCRIPTION: The special keyword TAG must appear in the select list.
CAUSE: It is a restriction that if the special keyword TAG appears in a where clause, it must also appear in the select list. This is a current limitation due to implementation considerations.
ACTION: Add TAG to your select list.
PARAMS:

ERROR: [DM_QUERY_E_NO_CURSOR]

SEVERITY: ERROR
DESCRIPTION: GRANT, REVOKE, or CREATE GROUP: An error occurred during the processing of the subquery. Your statement was not executed.
CAUSE: There will be another error message which explains the cause of the failure of the subquery processing.
ACTION: Follow the suggested action in the other error message.
PARAMS: None.

ERROR: [DM_QUERY_E_UP_BAD_ATTR_TYPES]

SEVERITY: ERROR
DESCRIPTION: SS UPDATE: The attributes %s and %s do not have the same datatype.
CAUSE: When attribute assignment is done in an update statement, the attributes datatypes must be the same.
ACTION: Find another way to assign the desired value to the updated attribute.
PARAMS: The first parameter is the updated attribute the second parameter is the assigned attribute.

ERROR: [DM_QUERY_E_NO_REPEAT]

SEVERITY: ERROR
DESCRIPTION: REGISTER: The REPEATING column attribute is not supported in the register table statement.
CAUSE: You have specified the REPEATING attribute on the description of a column in a table. Repeating attributes are only meaningful in Documentum objects, not in registered tables.
ACTION: Describe the table without REPEATING.
PARAMS: None.

ERROR: [DM_QUERY_E_REPEAT_ORDER]

SEVERITY: ERROR
DESCRIPTION: You have specified repeating attribute(s) and the composite ORDER keyword in the same select.
CAUSE: Repeating attributes may not be selected in the same select statement as ORDER.
ACTION: Composites are a deprecated feature. The ORDER keyword is no longer supported.
PARAMS: None.

ERROR: [DM_QUERY_E_COMPOSITE_6]

SEVERITY: ERROR
DESCRIPTION: A non-correlated column specification appears in an IN COMPOSITE clause.
CAUSE: You have specified a column reference in an IN COMPOSITE clause, but the column is not qualified. The column reference in an IN COMPOSITE clause must be qualified, and it must be a correlated reference to a column in an outer SELECT.
ACTION: Composites are a deprecated feature.
PARAMS: None.

ERROR: [DM_QUERY_E_NULLDATE]

SEVERITY: ERROR
DESCRIPTION: NULLDATE is not valid in this context.
CAUSE: NULLDATE is not recognized as an argument to the DATE function.
ACTION: If you are trying to do a compare, use the IS NULLDATE predicate.
PARAMS: None.

ERROR: [DM_QUERY_E_UPDATE_ERROR]

SEVERITY: ERROR
DESCRIPTION: S A database error has occurred during the execution of your update statement (%s).
CAUSE: A DQL UPDATE registered table statement is turned into an SQL UPDATE statement that performs the update on the specified registered table. This error message indicates that a failure occurred during the processing of the generated SQL UPDATE statement by the underlying RDBMS.
ACTION: The error message from the RDBMS is shown in the message. Use that error message to figure out what has happened, and correct your DQL statement accordingly.
PARAMS: The parameter contains the text of the error message generated by the RDBMS.

ERROR: [DM_QUERY_E_COMPOUND_CONTID_ND]

SEVERITY: ERROR
DESCRIPTION: You have specified CONTAIN_ID in a query that does not have an IN DOCUMENT or IN ASSEMBLY clause.
CAUSE: The CONTAIN_ID special keyword may only appear in a query that has an IN DOCUMENT or IN ASSEMBLY clause.
ACTION: Either remove CONTAIN_ID from your select list, or add a compound document clause.
PARAMS:

ERROR: [DM_QUERY_E_NOT_USER]

SEVERITY: ERROR
DESCRIPTION: SS %s: The username %s is not a valid Documentum user.
CAUSE: You have attempted to add a non-existent user to a group, or to grant a privilege to a non-existent user.
ACTION: Correct your statement so that it does not specify any invalid users. If you are generating usernames from a subquery, correct the subquery so that only valid user names are produced. Note that usernames and groupnames share the same namespace. If your query was attempting to add a group into another group, you can get this message if the name shown is neither a username nor a group name.
PARAMS: The first parameter specifies the statement type that the error occurred in. The second parameter gives the name of the invalid user. However, since these statements have all-or-nothing semantics, none of the users you have specified in this query have been affected.

ERROR: [DM_QUERY_E_UP_INT]

SEVERITY: ERROR
DESCRIPTION: SI UPDATE: The attribute (%s) cannot be updated with an integer value (%d).
CAUSE: You have attempted to assign an integer value to a non-numeric attribute.
ACTION: Correct your update statement and retry.
PARAMS: The first parameter is the attribute that is being updated, and the second parameter is the integer value that was specified. Note that the special keywords TRUE and FALSE are translated internally into the integer values 1 and 0, respectively.

ERROR: [DM_QUERY_E_COMPOUND_DEPTH_2]

SEVERITY: ERROR
DESCRIPTION: You have specified DEPTH more than once in a single select list.
CAUSE: The DEPTH special keyword may only appear once in a select list.
ACTION: Remove the second and any subsequent occurrences of DEPTH from your select list and retry the query.
PARAMS:

ERROR: [DM_QUERY_E_MODIFY_NOT_STR]

SEVERITY: ERROR
DESCRIPTION: S ALTER TYPE: The attribute %s is not a string type.
CAUSE: Only string attributes may be modified. Note that character and char are synonyms for string.
ACTION: Remove the non-string attributes from the MODIFY clause.
PARAMS: The non-string attribute name.

ERROR: [DM_QUERY_E_BAD_TYPE]

SEVERITY: ERROR
DESCRIPTION: SS %s: The datatype %s is not valid in this statement.
CAUSE: You have specified a datatype that is not a valid datatype in this context.
ACTION: Chose another datatype to represent the attribute.
PARAMS: The first parameter is the statement (for example, create type) that the error occurred in. The second parameter is the datatype that was specified in error.

ERROR: [DM_QUERY_E_COMPOUND_FUNC]

SEVERITY: ERROR
DESCRIPTION: IN DOCUMENT clause and a set function appear in the same SELECT.
CAUSE: You may not specify IN DOCUMENT with a DESCEND in the same query with a set function in the select list unless the IN DOCUMENT clause does not require recursion.
ACTION: Create an assembly on the compound document you are expanding, then try the query again with USING ASSEMBLIES or the IN ASSEMBLY clause.
PARAMS:

ERROR: [DM_QUERY_E_UPDATE_SUB_CONV2]

SEVERITY: ERROR
DESCRIPTION: UPDATE: Your subquery returned an unconvertable value.
CAUSE: The subquery in an update clause returned a value that is not convertable to the datatype of the updated attribute.
ACTION:
PARAMS:

ERROR: [DM_QUERY_E_COMPOUND_DEPTH_ND]

SEVERITY: ERROR
DESCRIPTION: You have specified DEPTH in a query that does not have a DESCENDing IN DOCUMENT clause.
CAUSE: None. This is no longer an error.
ACTION:
PARAMS:

ERROR: [DM_QUERY_E_COMPOUND_NS_KW]

SEVERITY: ERROR
DESCRIPTION: A NODESORT clause specifies an unsupported special keyword.
CAUSE: The NODESORT specification may only contain a column, an integer, or the SCORE or HITS special keyword. ORDER, TAG, and POSITION are not allowed in NODESORT. Nor are MSCORE, MHITS, or MCONTENTID.
ACTION: Correct the query and retry.
PARAMS:

ERROR: [DM_QUERY_E_UP_DOUBLE]

SEVERITY: ERROR
DESCRIPTION: SSS UPDATE: You have attempted to set a non-double attribute (%s) with a floating point literal value (%s%s).
CAUSE: No type conversion is done between a floating point literal and a non-double attribute. ACTUON: Correct your update statement and retry.
ACTION:
PARAMS: The attribute name, and the specified character string value.

ERROR: [DM_QUERY_E_MHITS_USED]

SEVERITY: ERROR
DESCRIPTION: You have specified the MHITS keyword where it is not allowed.
CAUSE: The MHITS keyword may only be specified in a select list, or an order by clause.
ACTION: Correct your statement so that POSITION does not appear anywhere other than the select list or order by clause. PARAMTERS: None.
PARAMS:

ERROR: [DM_QUERY_E_KEY_NO_MATCH]

SEVERITY: ERROR
DESCRIPTION: S REGISTER: Column %s specified in KEY clause has no match in column definitions.
CAUSE: You have listed a column in the KEY clause that was not listed in the column list.
ACTION: Add the column to the column list, or remove it from the KEY clause, as appropriate.
PARAMS: The parameter gives the name of the referenced column.

ERROR: [DM_QUERY_E_POSITION_USED]

SEVERITY: ERROR
DESCRIPTION: You have specified the POSITION keyword where it is not allowed.
CAUSE: The POSITION keyword may only be specified in a select list, or an order by clause.
ACTION: Correct your statement so that POSITION does not appear anywhere other than the select list or order by clause. PARAMTERS: None.
PARAMS:

ERROR: [DM_QUERY_E_COMPOUND_CURSOR]

SEVERITY: ERROR
DESCRIPTION: S A database error has occurred during the creation of a cursor (%s).
CAUSE: A recursive DQL SELECT statement (one containing IN DOCUMENT DESCEND, with no root assembly being used) is turned into an SQL SELECT statement that is bound to various object ID values as the document hierarchy is recursively searched. This error occurred during one of the recursive executions of this SQL statement. It could be that too many cursors must be opened simultaneously to process your documents hierarchy for the RDBMS to handle.
ACTION: The error message from the RDBMS is shown in the message. Use that error message to figure out what has happened, and correct your DQL statement accordingly.
PARAMS: The parameter contains the text of the error message generated by the RDBMS.

ERROR: [DM_QUERY_E_QUERY_HAS_OBSOLETE_KEYWORDS_IN_SELECT_LIST]

SEVERITY: ERROR
DESCRIPTION: S The query statement contains the following obsolete keywords in the select list: %s
CAUSE: the DQL select statement contains at least one keyword in the select list thats obsolete.
ACTION: Remove the obsolete keywords from the select list and rerun the query. Refer to the DQL Reference manual for more information.
PARAMS:

ERROR: [DM_QUERY_E_SYS_ID_NOT_IN_SL]

SEVERITY: ERROR
DESCRIPTION: The special keyword SYSOBJ_ID must appear in the select list.
CAUSE: It is a restriction that if the special keyword SYSOBJ_ID appears in a where clause, it must also appear in the select list. This is a current limitation due to implementation considerations.
ACTION: Add SYSOBJ_ID to your select list.
PARAMS:

ERROR: [DM_QUERY_E_EXEC_NOID]

SEVERITY: ERROR
DESCRIPTION: S EXECUTE: The argument %s is required unless an ID is specified.
CAUSE: You must specify either an ID in the FOR clause, or the argument in the WITH clause.
ACTION: Correct the query and retry.
PARAMS:

ERROR: [DM_QUERY_E_STAR_IN_SUBQUERY]

SEVERITY: ERROR
DESCRIPTION: Subquery: You may not specify a * in the select list of non-exists subquery.
CAUSE: Self explanatory.
ACTION: Reformulate your query such that a single column is specified in the select list of the subquery.
PARAMS: None.

ERROR: [DM_QUERY_E_REG_NO_DB_NAME]

SEVERITY: ERROR
DESCRIPTION: You cannot register a table because your database login is not defined.
CAUSE: You must have a user_db_name value defined in your Documentum user definition before you can register a database table.
ACTION: See your Documentum System Administrator about updating your user definition to contain your database login name.
PARAMS:

ERROR: [DM_QUERY_E_TYPE_NOT_OWNER]

SEVERITY: ERROR
DESCRIPTION: You have attempted to DROP or ALTER a type which does not belong to you.
CAUSE: Only the owner (creator) of a type, or a superuser, may ALTER or DROP the type.
ACTION: Check with the owner of the type about doing the ALTER or DROP for you.
PARAMS: None.

ERROR: [DM_QUERY_E_DROP_FAILED]

SEVERITY: ERROR
DESCRIPTION: S DROP TYPE statement failed for type: %s.
CAUSE: The cause of this failure will be explained in another message.
ACTION: Examine the other error messages generated during query processing. The message immediately following this one should be the one which explains the reason for the DROP TYPE failure. Possible reasons include, the type has dependents which must be dropped first, or you do not have sufficient privilege to drop this type.
PARAMS: The parameter specifies the type which was not dropped.

ERROR: [DM_QUERY_E_UP_SINGLE]

SEVERITY: ERROR
DESCRIPTION: S The attribute %s is a single-valued attribute.
CAUSE: You have attempted to remove, truncate, append, or insert into a single-valued attribute. Single-valued attributes may only be SET.
ACTION: Correct the update clause for this attribute and retry your update or create object statement.
PARAMS: The single-valued attribute name.

ERROR: [DM_QUERY_E_UPDATE_SUB_DT]

SEVERITY: ERROR
DESCRIPTION: S UPDATE: Your subquery returned a value with an invalid datatype (%s).
CAUSE: The subquery returned a value that could not be handled.
ACTION: Check your subquery and make sure that it returns values of database datatypes: date, character, integer, shortint, or double.
PARAMS: The parameter contains an attempt to identify the database type that was returned.

ERROR: [DM_QUERY_E_MORE_REPEATING]

SEVERITY: ERROR
DESCRIPTION: You have specified too many repeating attributes.
CAUSE: Repeating attributes may appear in at most 100 select list elements.
ACTION: Correct the query to have no more than 100 select list elements containing repeating attributes.
PARAMS: None.

ERROR: [DM_QUERY_E_TEXTPAGE_NOT_IN_SL]

SEVERITY: ERROR
DESCRIPTION: The special keyword TEXTPAGE must appear in the select list.
CAUSE: It is a restriction that if the special keyword TEXTPAGE appears in a where clause, it must also appear in the select list. This is a current limitation due to implementation considerations.
ACTION: Add TEXTPAGE to your select list. **Note: do not add any more ERROR messages to this file. Use the QUERY2.e file instead.
PARAMS:

ERROR: [DM_QUERY_E_ALTER_BASE_TYPE_DROP]

SEVERITY: ERROR
DESCRIPTION: S ALTER TYPE: You have attempted to drop or modify an attribute from a Documentum base type (%s).
CAUSE: It is illegal to drop or modify attributes from Documentum base types. Any type which has a name beginning with the letters dm is a Documentum base type.
ACTION: None.
PARAMS: The typename as specified in the alter type statement.

ERROR: [DM_QUERY_E_REG_TABLE_GROUP]

SEVERITY: ERROR
DESCRIPTION: SSS The registered table you are trying to access (%s.%s) has an invalid default group: %s.
CAUSE: The specified group name appears in the group_name attribute of the registered table object that describes the named relational table. It is not a valid group. This groupname is used to validate table access permissions.
ACTION: You do not have sufficient privilege to access the table in the manner that your statement requires. Owner and world permissions were checked. Since the group name in the object was in error, it was not possible to check group permissions. You could contact the owner of the registered table or the superuser and notify them of this error.
PARAMS: The registered table name and the invalid group name.

ERROR: [DM_QUERY_E_IS_GROUP2]

SEVERITY: ERROR
DESCRIPTION: S GRANT or REVOKE: The specified grantee or revokee (%s) is a group.
CAUSE: You have specified a group name in your list of users. Groups are not subject to permits. No permits have been affected by this query.
ACTION: Remove the group name from your list of users, or reformulate the subquery which is materializing users such that groups will be excluded.
PARAMS: The parameter specifies the group name.

ERROR: [DM_QUERY_E_CREATE_FAILED]

SEVERITY: ERROR
DESCRIPTION: S CREATE TYPE statement failed for type: %s.
CAUSE: Your attempt to create a type has failed.
ACTION: There will be an error message from the type manager that will explain the reason for this failure. Check any other messages on your session and follow the actions specified for them. An example of one common cause of failure is that you may have named an attribute with an RDBMS reserved word. This will be indicated by an error message from the type manager containing the Oracle error: ORA-00904: invalid column name
PARAMS: The parameter specifies the typename for the type which could not be created.

ERROR: [DM_QUERY_E_NULL_SUPERTYPE]

SEVERITY: ERROR
DESCRIPTION: CREATE TYPE: You are not authorized to create a type with no supertype.
CAUSE: Only a superuser may specify NULL in the SUPERTYPE clause of a create type statement.
ACTION: Correct the supertype specification and create your type as a subtype of one of the subtypeable Documentum types (dm_user, dm_sysobject, and all subtypes of dm_sysobject).
PARAMS: None.

ERROR: [DM_QUERY_E_NOT_VIEWABLE]

SEVERITY: ERROR
DESCRIPTION: S You do not have enough privilege to view the specified type (%s).
CAUSE: You do not have enough privilege to view the type that you specified in your select statement. Currently, dmi_audittrail_attrs type is only viewable to users who are either superusers or have the VIEW AUDIT privilege.
ACTION: None.
PARAMS: The name you specified in your select statement.

ERROR: [DM_QUERY_E_ID_NOT_ALLOWED_IN_OUTER_SELECT]

SEVERITY: ERROR
DESCRIPTION: You cannot include the ID function in the selected values.
CAUSE: You have specified ID() in the outermost select list. This is a deprecated feature.
ACTION: select r_object_id instead of ID().
PARAMS:

ERROR: [DM_QUERY_E_COMPOUND_PARENT_2]

SEVERITY: ERROR
DESCRIPTION: You have specified PARENT more than once in a single select list.
CAUSE: The PARENT special keyword may only appear once in a select list.
ACTION: Remove the second and any subsequent occurrences of PARENT from your select list and retry the query.
PARAMS:

ERROR: [DM_QUERY_E_COMPOUND_REPEATING]

SEVERITY: ERROR
DESCRIPTION: You have selected repeating attribute(s) in an IN DOCUMENT query.
CAUSE: You cannot select repeating attributes in the same query with the IN DOCUMENT clause.
ACTION: This error message is no longer true. Now, repeating attributes are supported in an IN DOCUMENT query.
PARAMS:

ERROR: [DM_QUERY_E_UP_BAD_ATTR_CORR]

SEVERITY: ERROR
DESCRIPTION: SSS The correlation variable (%s) for attribute %s does not match the updated types correlation variable (%s).
CAUSE: You have specified an invalid correlation variable on one of your updated attributes.
ACTION: Correct the query and retry.
PARAMS: The first parameter is the correlation variable that is in error. The attribute name and the expected correlation variable are in the next two parameters.

ERROR: [DM_QUERY_E_CHANGE_TYPES1]

SEVERITY: ERROR
DESCRIPTION: CHANGE: You have specified two base types.
CAUSE: You cannot change objects from one Documentum base type to another.
ACTION: None.
PARAMS:

ERROR: [DM_QUERY_E_COMPOUND_NS_NOT]

SEVERITY: ERROR
DESCRIPTION: IN DOCUMENT clause contains NODESORT within a non-select statement.
CAUSE: You have specified an IN DOCUMENT clause containing a NODESORT specification somewhere other than the outermost SELECT of a SELECT statement. NODESORT may only appear in the outermost SELECT. This is because the ultimate usage of NODESORT, which is to identify which of competing versions of a document at a particular node is to be chosen, is only performed at the outermost SELECT level.
ACTION: None.
PARAMS:

ERROR: [DM_QUERY_E_EXEC_NOT_VALID]

SEVERITY: ERROR
DESCRIPTION: S EXECUTE: The function you are trying to execute (%s) is not a valid function.
CAUSE: The specified function is not a function that can be executed.
ACTION: Check the spelling of the function name against the documentation. Only functions that are documented with the APPLY method are available for execution.
PARAMS: The invalid function name.

ERROR: [DM_QUERY_E_TWO_TYPES]

SEVERITY: ERROR
DESCRIPTION: SS You have specified more than one type (%s and %s) in your FROM clause.
CAUSE: The FROM clause can have only one type specified.
ACTION: If you are trying to query two types, reformulate the query to reference only one type at a time. If the two types are both subtypes of a common supertype, you could query the supertype, and then restrict the results to the two types you want by using the TYPE predicate. If one of the names shown above is supposed to be a tablename, it is also a typename, and an ambiguous reference. You can disambiguate it by appending the tables owner to the tablename in the FROM clause: FROM ownername.tablename
PARAMS: The two types that were found in the FROM clause.

ERROR: [DM_QUERY_E_STAR_EXPRESSIONS]

SEVERITY: ERROR
DESCRIPTION: You have specified an expression list along with * in the select list.
CAUSE: You may only specify expressions in addition to the * in a select list if you are selecting from a type.
ACTION: * gets all columns in the table(s) you are selecting from. If You require an expression (such as columna + columnb) you must specify that along with all other column names you want to select.
PARAMS:

ERROR: [DM_QUERY_E_OBJTYPE_NOT_IN_SL]

SEVERITY: ERROR
DESCRIPTION: The special keyword OBJTYPE must appear in the select list.
CAUSE: It is a restriction that if the special keyword OBJTYPE appears in a where clause, it must also appear in the select list. This is a current limitation due to implementation considerations.
ACTION: Add OBJTYPE to your select list.
PARAMS:

ERROR: [DM_QUERY_E_ESCAPE_NOT]

SEVERITY: ERROR
DESCRIPTION: The ESCAPE clause is not supported in your RDBMS.
CAUSE: The RDBMS you are running with does not support the ESCAPE clause in the LIKE predicate, so DQL does not.
ACTION: Reformulate you query so that you do not use an ESCAPE clause. If you are running Oracle 6, be aware that Oracle 7 does support ESCAPE.
PARAMS:

ERROR: [DM_QUERY_E_UP_BAD_FOLDER]

SEVERITY: ERROR
DESCRIPTION: S You have specified an invalid folder path, %s, in your LINK or MOVE TO clause.
CAUSE: The folder specified is not a valid folder path name.
ACTION: Correct the path name and retry your update or create object statement.
PARAMS:

ERROR: [DM_QUERY_E_MODIFY_SPACEOPTIMIZE_LOCAL_ONLY]

SEVERITY: ERROR
DESCRIPTION: SS ALTER TYPE: The attribute %s is not a local attribute of the type %s.
CAUSE: You have specified an attribute in the MODIFY clause of an ALTER TYPE statement that is not a local attribute of the specified type. Note that for ALTER TYPE, the attribute must be a defined attribute of the type, not an inherited attribute. To modify an inherited attribute of this type, you must alter the supertype for which the attribute was defined.
ACTION: Correct the attribute in your MODIFY clause.
PARAMS: The attribute name and type name as they appear in your statement.

ERROR: [DM_QUERY_E_CANT_USE_CONTENT_ATTS_WITH_LITE_OBJ]

SEVERITY: ERROR
DESCRIPTION: DQL does not support using the i_contents_id, r_content_size or r_full_content_size attributes with Lightweight Objects
CAUSE: A query with a lightweight type in the from clauses uses i_contents_id, r_content_size and/or r_full_content_size attributes on the lightweight type. This is not supported
ACTION: Rewrite the query to join to the dmr_content type.
PARAMS:

ERROR: [DM_QUERY_E_DELETE_ERROR]

SEVERITY: ERROR
DESCRIPTION: S A database error has occurred during the execution of your delete statement (%s).
CAUSE: A DQL DELETE registered table statement is turned into an SQL DELETE statement that performs the deletion on the specified registered table. This error message indicates that a failure occurred during the processing of the generated SQL DELETE statement by the underlying RDBMS.
ACTION: The error message from the RDBMS is shown in the message. Use that error message to figure out what has happened, and correct your DQL statement accordingly.
PARAMS: The parameter contains the text of the error message generated by the RDBMS.

ERROR: [DM_QUERY_E_SUMMARY_NOT_IN_SL]

SEVERITY: ERROR
DESCRIPTION: The special keyword SUMMARY must appear in the select list.
CAUSE: It is a restriction that if the special keyword SUMMARY appears in a where clause, it must also appear in the select list. This is a current limitation due to implementation considerations.
ACTION: Add SUMMARY to your select list.
PARAMS:

ERROR: [DM_QUERY_W_ALTER_TYPE_OBSOLETE_SYNTAX]

SEVERITY: WARNING
DESCRIPTION: S %s is obsolete starting Release 5.3 of Content Server
CAUSE: This warning occurs when either ADD_FTINDEX or DROP_FTINDEX is specifed in an ALTER statement.
ACTION: None. You need not execute ADD_FTINDEX or DROP_FTINDEX at all. The Content Server by default indexes all indexable metadata.
PARAMS:

ERROR: [DM_QUERY_W_NO_USERS2]

SEVERITY: WARNING
DESCRIPTION: CREATE or ALTER GROUP: No users were returned by the subquery. No privileges were affected.
CAUSE: Your statement specified a subquery which returned no results.
ACTION: No action is required. No users were added to the specified group.
PARAMS: None.

ERROR: [DM_QUERY_W_TRAN_ALREADY]

SEVERITY: WARNING
DESCRIPTION: BEGIN TRANSACTION: There is already a transaction open.
CAUSE: You have issued a begin transaction statement, but a transaction was already in progress. No action has been taken by the Documentum server.
ACTION: None required. However, you might want to understand what actions have already occurred under the existing transaction before you take any action to end (commit or abort) it.
PARAMS:

ERROR: [DM_QUERY_W_NOT_FOLDER_ALL]

SEVERITY: WARNING
DESCRIPTION: You have specified a not folder(all) predicate.
CAUSE: The folder(all) predicate means that all folders will be searched. Your folder(all) predicates has been NOTed, meaning that no folders will be searched, so no results are possible.
ACTION: Correct your WHERE clause so that the folder(all) predicate is not modified by a NOT.
PARAMS: None.

ERROR: [DM_QUERY_W_UPNOTSUPP]

SEVERITY: WARNING
DESCRIPTION: Read-For-Update mode is not supported.
CAUSE: You have specified read for update mode on a select statement, either by setting the flag on the execquery method, or by using the query method. Read for update mode is not supported on Sybase.
ACTION: Your query will be run in read-only mode. If you want read for update semantics, you can start a multi-operation transaction by using the begintran method, or the BEGIN TRAN statement.
PARAMS:

ERROR: [DM_QUERY_W_COMPOSITE_TWICE]

SEVERITY: WARNING
DESCRIPTION: You have specified the ORDER keyword more than once in your ORDER BY clause.
CAUSE: The special order keyword appears more than once in the order by clause.
ACTION: Composites are a deprecated feature. The ORDER keyword is no longer supported.
PARAMS: None.

ERROR: [DM_QUERY_W_COMPOUND_LATE]

SEVERITY: WARNING
DESCRIPTION: You have specified USING ASSEMBLIES and WITH in the same IN DOCUMENT clause.
CAUSE: This is not an error.
ACTION: None required. Simply be aware that the late binding condition specified in a WITH clause does not apply to any nodes that are reached via assemblies.
PARAMS:

ERROR: [DM_QUERY_W_QUERIES_CLOSED]

SEVERITY: WARNING
DESCRIPTION: A transaction operation has caused a query or queries to be closed.
CAUSE: DQL select statements are represented by database SQL cursors. In most RDBMSs, a transaction close (commit or rollback) causes all SQL cursors to be invalidated. Thus, a Documentum transaction operation, which translates into a database commit or rollback, will cause DQL select queries to be closed.
ACTION: If you need for your query to transcend transaction operations, you may invoke the query in read_for_update mode. This causes the query to be run in a separate database connection which is not affected by Documentum transactions. Note, however, that on some RDBMSs (notably Oracle) setting up and maintaining multiple transactions is very time consuming.
PARAMS: None.

ERROR: [DM_QUERY_W_NOT_A_FOLDER_ID]

SEVERITY: WARNING
DESCRIPTION: S You have specified an ID (%s) in a FOLDER or CABINET predicate that is not a valid ID value for a folder or cabinet.
CAUSE: The ID value in your FOLDER predicate does not identify a folder or cabinet. The query processing continues, but be aware that unless your query contained other predicates that were ORed with this FOLDER or CABINET predicate, your query will return no rows.
ACTION: Make sure the pathname is the one you intended.
PARAMS: The parameter is the ID value that is in error.

ERROR: [DM_QUERY_W_ALTER_SOME]

SEVERITY: WARNING
DESCRIPTION: ALTER TYPE: Your attempt to modify the lengths of attributes was only partially successful.
CAUSE: At least one of the attributes you wanted to modify has failed. There will be additional error messages indicating the reasons for this failure.
ACTION: Do a describe on the type you are modifying to see which attributes were changed and which were not. Then submit another ALTER TYPE statement to modify the rest.
PARAMS:

ERROR: [DM_QUERY_W_NO_USERS]

SEVERITY: WARNING
DESCRIPTION: GRANT or REVOKE: No users were returned by the subquery. No privileges were affected.
CAUSE: Your statement specified a subquery which returned no results.
ACTION: No action is required. No users were affected by the GRANT or REVOKE statement.
PARAMS: None.

ERROR: [DM_QUERY_W_BAD_DATE_FMT]

SEVERITY: WARNING
DESCRIPTION: S The date format %s is either un-recognizable or not supported on the RDBMS. Use default date format mm/dd/yyyy hh:mi:ss.
CAUSE: You have specified an illegal or an unsupported date format in the datetostring function.
ACTION: Check documentation and choose a legal date format pattern for your query. Note that (1) month is not supported on Sybase platform, (2) month, mon, and yy are not supported on Informix platform.
PARAMS:

ERROR: [DM_QUERY_W_COMPOSITE_INTEGERS]

SEVERITY: WARNING
DESCRIPTION: You have specified an integer in the ORDER BY clause of a query containing ORDER in the select list.
CAUSE: The composite ORDER keyword expands into many column specifications. The integer you have specified in your ORDER BY clause might not correspond to the column you expect if the ORDER keyword preceded it in the select list.
ACTION: Composites are a deprecated feature. The ORDER keyword is no longer supported.
PARAMS: None.

ERROR: [DM_QUERY_W_GROUPS_UNKNOWN]

SEVERITY: WARNING
DESCRIPTION: An error occurred processing your groups.
CAUSE: The groups that you are a member of are used in determining which objects you may SELECT. An unexpected error has occurred during the determination of your groups.
ACTION: None required. However, your query results may have been restricted by the fact that your group memberships were unknown. To determine the cause of the error, look at the other error messages generated during the processing of this query.
PARAMS: None.

ERROR: [DM_QUERY_W_TRAN_NOT]

SEVERITY: WARNING
DESCRIPTION: S %s: There is no open transaction.
CAUSE: You have attempted to commit or abort a transaction, but there is no transaction open to commit or abort. No action has been taken by the Documentum server.
ACTION: None required.
PARAMS:

ERROR: [DM_QUERY_W_STAR_INTEGERS]

SEVERITY: WARNING
DESCRIPTION: You have specified an integer in the ORDER BY or NODESORT clause of a query containing * in the select list.
CAUSE: A * in the select list expands into many column specifications. The integer you have specified in your ORDER BY or NODESORT clause might not correspond to the column you expect.
ACTION: Make sure that any integers in the ORDER BY or NODESORT clause correctly reflect the expansion of the * in the select list.
PARAMS: None.

ERROR: [DM_QUERY_W_NOT_A_FOLDER_PATH]

SEVERITY: WARNING
DESCRIPTION: S You have specified a pathname (%s) in a FOLDER or CABINET predicate that is not a valid pathname.
CAUSE: The pathname in your FOLDER predicate is not a pathname known to Documentum. The query processing continues, but be aware that unless your query contained other predicates that were ORed with this FOLDER or CABINET predicate, your query will return no rows.
ACTION: Make sure the pathname is the one you intended.
PARAMS: The parameter is the pathname that is in error.

ERROR: [DM_QUERY_W_RETRY_ALTER]

SEVERITY: WARNING
DESCRIPTION: ALTER TYPE is being re-tried.
CAUSE: Your alter type statement has not completed due to an internal problem, possibly an error from the database management system. Error messages in the log prior to this one may shed more light on the exact cause of the failure. Your statement is being re-tried, in case the failure was transient.
ACTION: If your statement succeeds on the retry, you may ignore this message. If it fails, check the error message log for this session. There will be additional messages there which explain the cause of the failure.
PARAMS: None.

ERROR: [DM_QUERY_T_GROUP_BAD_VIEW]

SEVERITY: TRACE
DESCRIPTION: S build_group_temp: View creation failed for temporary view %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_QUERY_T_STMT]

SEVERITY: TRACE
DESCRIPTION: S Your DQL statement is: %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_QUERY_T_CYCLE]

SEVERITY: TRACE
DESCRIPTION: I A compound document cycle has been found at object %d.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_QUERY_T_DROP_BEGIN]

SEVERITY: TRACE
DESCRIPTION: S Begin drop temporary fulltext table(s) (%s).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_QUERY_T_CLOSE_BEGIN]

SEVERITY: TRACE
DESCRIPTION: S Begin database cursor close (%s).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_QUERY_T_SYNTAX_BEGIN]

SEVERITY: TRACE
DESCRIPTION: Begin syntactic parse (call yacc).
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_QUERY_T_STMT_BEGIN]

SEVERITY: TRACE
DESCRIPTION: S Begin %s statement.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_QUERY_T_CONTAIN_TABLE_DROP]

SEVERITY: TRACE
DESCRIPTION: S drop_temp_tables: Temporary fulltext table dropped: %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_QUERY_T_SQL_DELETE]

SEVERITY: TRACE
DESCRIPTION: S DELETE statement generated by the query is: %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_QUERY_T_SELECT_BEGIN]

SEVERITY: TRACE
DESCRIPTION: Begin SELECT statement.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_QUERY_T_GROUP_VIEW]

SEVERITY: TRACE
DESCRIPTION: S build_group_temp: Temporary group view created: %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_QUERY_T_SUBSELECT]

SEVERITY: TRACE
DESCRIPTION: S SQL select statement produced from the subselect or update or delete statement is: %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_QUERY_T_CONTAIN_TABLE]

SEVERITY: TRACE
DESCRIPTION: S make_fulltext_temp: Temporary fulltext table created: %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_QUERY_T_STMT_COMPLETE]

SEVERITY: TRACE
DESCRIPTION: S %s statement has completed.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_QUERY_T_SQL_PARTIAL]

SEVERITY: TRACE
DESCRIPTION: S Partial SELECT statement generated by the query is: %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_QUERY_T_SYNTAX_COMPLETE]

SEVERITY: TRACE
DESCRIPTION: Syntactic parse is complete.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_QUERY_T_CONTAIN_BAD_TABLE]

SEVERITY: TRACE
DESCRIPTION: S make_fulltext_temp: Table creation failed for temporary table %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_QUERY_T_SQL_SELECT]

SEVERITY: TRACE
DESCRIPTION: S SELECT statement generated by the query is: %s. Begin Database processing.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_QUERY_T_CLOSE_COMPLETE]

SEVERITY: TRACE
DESCRIPTION: Database cursor close is complete.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_QUERY_T_DROP_COMPLETE]

SEVERITY: TRACE
DESCRIPTION: Drop temporary fulltext table(s) is complete.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_QUERY_T_SELECT_COMPLETE]

SEVERITY: TRACE
DESCRIPTION: SELECT statement semantic checking and setup is complete.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_QUERY_T_SQL_INSERT]

SEVERITY: TRACE
DESCRIPTION: S INSERT statement generated by the query is: %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_QUERY_T_SQL_UPDATE]

SEVERITY: TRACE
DESCRIPTION: S UPDATE statement generated by the query is: %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_QUERY_T_GROUP_VIEW_DROP]

SEVERITY: TRACE
DESCRIPTION: S drop_temp_tables: Temporary group view dropped: %s.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_QUERY_I_DISTINCT_COMPOUND]

SEVERITY: INFORMATION
DESCRIPTION: DISTINCT was ignored in this query.
CAUSE: When you specify DISTINCT along with one of the compound document clauses (IN DOCUMENT or IN ASSEMBLY), it is ignored. It is not possible to remove duplicate objects from the result set, because each object is made unique by its position within the compound document hierarchy. Thus, if the same document appears twice within a compound document hierarchy, it will appear twice in the result set. In your query, DISTINCT was requested either explicitly, or by default from the distinct query results server installation setting.
ACTION: None required. This messages is informational only.
PARAMS:

ERROR: [DM_QUERY_I_QUERY_CLOSED]

SEVERITY: INFORMATION
DESCRIPTION: S A cursor was closed and the dmQueryResults object for it invalidated: %s
CAUSE: A transaction operation has caused this querys database cursor to be closed.
ACTION: No further action on the query results (Next(), for example) will be accepted, except Close(). It is advisable to close the corresponding query.
PARAMS: The text of the DQL select statement that was invalidated.

ERROR: [DM_QUERY_I_UP_MAX_APPEND_EX]

SEVERITY: INFORMATION
DESCRIPTION: IS Your UPDATE statement exceeded the maximum append value (%d) for attribute %s.
CAUSE: Your UPDATE statement had a maximum append-from-subselect value that was exceded by the subselect. This message is informational only. It means that the subselect returned more values than were appended to your object.
ACTION:
PARAMS:

ERROR: [DM_QUERY_I_NUM_UPDATE]

SEVERITY: INFORMATION
DESCRIPTION: IS %d objects were affected by your %s statement.
CAUSE: A successful update or delete statement has affected the specified number of objects.
ACTION: No action is required.
PARAMS: The number of objects affected, and the statement used.

ERROR: [DM_QUERY_I_DEADLOCK_INFO]

SEVERITY: INFORMATION
DESCRIPTION: A database deadlock occurred.
CAUSE: Database deadlock occurred.
ACTION: No action is needed if application is running a docserver method query . However, if application is running a user transaction, i,e, user use explicit begintran to start a transaction, then user has to rerun the transaction as it has been rolled back after becoming a deadlock victim.
PARAMS:

ERROR: [DM_QUERY_I_MODIFY_ATTR_NO]

SEVERITY: INFORMATION
DESCRIPTION: S ALTER TYPE: No action is required for attribute %s.
CAUSE: You have specified a length for the attribute that is identical to the current length of the attribute. Starting from 6.6, you may try to enable spaceoptimize on an attribute which is already spaceoptimized. No action is required.
ACTION: None. This is informational only.
PARAMS: The attribute that remains unchanged.

nahoru

DM_QUERY2

ERROR: [DM_QUERY2_F_ALTER_SET_OVERRIDE_FAILED]

SEVERITY: FATAL
DESCRIPTION: S ALTER TYPE: Unable to set the type_override attribute in the dmi_type_info object for type %s.
CAUSE: This is an internal error.
ACTION: Collect all the error messages that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the name of the type being altered.

ERROR: [DM_QUERY2_F_BAD_UPDATE_MODIFIER_TYPE]

SEVERITY: FATAL
DESCRIPTION: I Unknown update modifier (%d).
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representitive.
PARAMS: The parameter is the internal update modifier type code.

ERROR: [DM_QUERY2_F_CANNOT_EXPUNGE_AGGR_DOMAIN]

SEVERITY: FATAL
DESCRIPTION: DS DROP TYPE could not expunge the dm_aggr_domain object with id %s when dropping type %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representitive.
PARAMS: The first parameter is the object id of the dm_aggr_domain object. The second parameter is the name of the type being dropped.

ERROR: [DM_QUERY2_F_BAD_MODIFIER_TYPE]

SEVERITY: FATAL
DESCRIPTION: IS ALTER/CREATE TYPE: Unknown modifier type (%d) for type %s.
CAUSE: This is an internal error.
ACTION: Collect all the error messages that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the internal modifier type code. The second parameter is the name of the type being created/altered.

ERROR: [DM_QUERY2_F_CANNOT_FETCH_AGGR_DOMAIN]

SEVERITY: FATAL
DESCRIPTION: DS DROP TYPE could not fetch the dm_aggr_domain object with id %s when dropping type %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representitive.
PARAMS: The first parameter is the object id of the dm_aggr_domain object. The second parameter is the name of the type being dropped.

ERROR: [DM_QUERY2_F_BAD_BUSINESS_POLICY_MODIFIER_TYPE]

SEVERITY: FATAL
DESCRIPTION: I Unknown business policy modifier type (%d).
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representitive.
PARAMS: The parameter is the internal business policy modifier type code.

ERROR: [DM_QUERY2_F_BAD_UPDATE_VALUE_TYPE]

SEVERITY: FATAL
DESCRIPTION: I Unknown update value type (%d).
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representitive.
PARAMS: The parameter is the internal update value type code.

ERROR: [DM_QUERY2_F_BAD_DEFAULT_ELEMENT_TYPE]

SEVERITY: FATAL
DESCRIPTION: I Unknown default element type (%d).
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representitive.
PARAMS: The parameter is the internal default element type code.

ERROR: [DM_QUERY2_F_MARK_FOR_RESYNC_FAILED]

SEVERITY: FATAL
DESCRIPTION: S Failure attempting to mark subtypes of type %s for Data Dictionary re-synchronization.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representitive.
PARAMS: The parameter is the internal default element type code.

ERROR: [DM_QUERY2_F_BAD_CONSTRAINT_TYPE]

SEVERITY: FATAL
DESCRIPTION: IS ALTER/CREATE TYPE: Unknown constraint type (%d) for type %s.
CAUSE: This is an internal error.
ACTION: Collect all the error messages that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the internal constraint type code. The second parameter is the name of the type being created/altered.

ERROR: [DM_QUERY2_F_BAD_EXPRESSION_LANGUAGE]

SEVERITY: FATAL
DESCRIPTION: IS ALTER/CREATE TYPE: Unknown expression language (%d) for type %s.
CAUSE: This is an internal error.
ACTION: Collect all the error messages that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the internal expression language code. The second parameter is the name of the type being created/altered.

ERROR: [DM_QUERY2_F_INTERNAL_ERROR_IN_ATTR_MODIFIER]

SEVERITY: FATAL
DESCRIPTION: SSS ALTER/CREATE TYPE: An internal error occurred while processing a Data Dictionary modifier for type %s, attribute %s: (%s).
CAUSE: This is an internal error.
ACTION: Collect all the error messages that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the name of the type being created/altered. The second parameter is the name of the attribute of the type. The third parameter describes the internal error.

ERROR: [DM_QUERY2_F_ALTER_STORE_OVERRIDE_FAILED]

SEVERITY: FATAL
DESCRIPTION: S ALTER TYPE: Unable to store the updated type_override in the dmi_type_info object for type %s.
CAUSE: This is an internal error.
ACTION: Collect all the error messages that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the name of the type being altered.

ERROR: [DM_QUERY2_F_BAD_EXPRESSION_TYPE]

SEVERITY: FATAL
DESCRIPTION: IS ALTER/CREATE TYPE: Unknown expression type (%d) for type %s.
CAUSE: This is an internal error.
ACTION: Collect all the error messages that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the internal expression type code. The second parameter is the name of the type being created/altered.

ERROR: [DM_QUERY2_F_INTERNAL_ERROR_IN_MODIFIER]

SEVERITY: FATAL
DESCRIPTION: SS ALTER/CREATE TYPE: An internal error occurred while processing a Data Dictionary modifier for type %s: (%s).
CAUSE: This is an internal error.
ACTION: Collect all the error messages that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the name of the type being created/altered. The second parameter describes the internal error.

ERROR: [DM_QUERY2_F_CREATE_SET_OVERRIDE_FAILED]

SEVERITY: FATAL
DESCRIPTION: S CREATE TYPE: Unable to set the type_override attribute in the dmi_type_info object for type %s.
CAUSE: This is an internal error.
ACTION: Collect all the error messages that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the name of the type being created.

ERROR: [DM_QUERY2_F_BAD_LITERAL_TYPE]

SEVERITY: FATAL
DESCRIPTION: IS ALTER/CREATE TYPE: Unknown literal type (%d) for type %s.
CAUSE: This is an internal error.
ACTION: Collect all the error messages that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the internal literal type code. The second parameter is the name of the type being created/altered.

ERROR: [DM_QUERY2_F_DROP_DMI_DD_INFO_FOR_TYPE]

SEVERITY: FATAL
DESCRIPTION: S Unable to drop Data dictionary information stored in the dmi_dd_common_info/dmi_dd_type_info/dmi_dd_attr_info tables about type %s
CAUSE: This is an internal error. It may be related to the database.
ACTION: Collect all the error messages that have been set for this session, and contact your Documentum site representative. Check the database tables to see if the type is listed.
PARAMS: The parameter is the name of the type being dropped. $Id: dmrecov.e,v 5.2 1998/03/05 23:10:25 ziff Exp $ Recovery subsystem error ** Documentum DocuServer ** Confidential Property of Documentum, Inc. ** (c) Copyright Documentum, Inc., 1991-1998 ** All rights reserved. **

ERROR: [DM_QUERY2_F_BAD_UPDATE_TYPE]

SEVERITY: FATAL
DESCRIPTION: IS ALTER/CREATE TYPE: Unknown update type (%d) for type %s.
CAUSE: This is an internal error.
ACTION: Collect all the error messages that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the internal update type code. The second parameter is the name of the type being created/altered.

ERROR: [DM_QUERY2_F_BAD_VALUE_ASSISTANCE_TYPE]

SEVERITY: FATAL
DESCRIPTION: IS ALTER/CREATE TYPE: Unknown value assistance type (%d) for type %s.
CAUSE: This is an internal error.
ACTION: Collect all the error messages that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the internal value assistance code. The second parameter is the name of the type being created/altered.

ERROR: [DM_QUERY2_F_BAD_VA_OPTION_TYPE]

SEVERITY: FATAL
DESCRIPTION: I ALTER/CREATE TYPE: Unknown value assistance option (%d).
CAUSE: This is an internal error.
ACTION: Collect all the error messages that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the internal value assistance option type code.

ERROR: [DM_QUERY2_F_CREATE_STORE_OVERRIDE_FAILED]

SEVERITY: FATAL
DESCRIPTION: S CREATE TYPE: Unable to store the updated type_override in the dmi_type_info object for type %s.
CAUSE: This is an internal error.
ACTION: Collect all the error messages that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the name of the type being created.

ERROR: [DM_QUERY2_F_INVALIDATE_DD_CACHE_FAILED]

SEVERITY: FATAL
DESCRIPTION: S ALTER TYPE: Unable to flush the Data Dictionary cache for type %s.
CAUSE: This is an internal error.
ACTION: Collect all the error messages that have been set for this session, and contact your Documentum site representative.
PARAMS: The parameter is the name of the type being altered.

ERROR: [DM_QUERY2_F_BAD_KEY_TYPE]

SEVERITY: FATAL
DESCRIPTION: IS ALTER/CREATE TYPE: Unknown key type (%d) for type %s.
CAUSE: This is an internal error.
ACTION: Collect all the error messages that have been set for this session, and contact your Documentum site representative.
PARAMS: The first parameter is the internal key type code. The second parameter is the name of the type being created/altered.

ERROR: [DM_QUERY2_F_DROP_TYPE_COMMIT_FAILURE]

SEVERITY: FATAL
DESCRIPTION: S Commit failed for expunge of Data Dictionary information when dropping type %s.
CAUSE: This is an internal error.
ACTION: Collect all the errors that have been set for this session, and contact your Documentum site representitive.
PARAMS: The parameter is the internal default element type code.

ERROR: [DM_QUERY2_E_ALLOW_ASPECTS_MUST_BE_SUPERMOST_TYPE]

SEVERITY: ERROR
DESCRIPTION: SS ALTER TYPE statement to ALLOW ASPECTS can be executed on a type with no super types only. Type (%s) has a super type (%s)
CAUSE: The alter type .. allow aspects statement was executed on a type thats not the super most type.
ACTION: This statement cannot be executed on a type with a super-type. You must specify the super-most type in a type hierarchy in the statement.
PARAMS:

ERROR: [DM_QUERY2_E_QUERY_VA_STAR_SELECT_LIST]

SEVERITY: ERROR
DESCRIPTION: The QRY form of value assistance cannot use * in the select list.
CAUSE: The query_string specified for QRY value assistance uses SELECT *.
ACTION: Change the select list to reference specific attributes, rather than *.
PARAMS: None.

ERROR: [DM_QUERY2_E_MISSING_OBJECTID_IN_SELECT_LIST]

SEVERITY: ERROR
DESCRIPTION: The DQL statement has non-qualifiable attribute(s) or repeating attribute(s) from lightweight type or repeating aspect attribute(s) in the select list, r_object_id is required in the select list.
CAUSE: r_object_id is not in the select list while a repeating lightweight or aspect attribute is in the select list.
ACTION: Add r_object_id into the DQL select list.
PARAMS:

ERROR: [DM_QUERY2_E_DUPLICATE_DROP_CHECK]

SEVERITY: ERROR
DESCRIPTION: Duplicate DROP CHECK clause.
CAUSE: A duplicate DROP CHECK clause was found.
ACTION: Remove the duplicate clause.
PARAMS: None.

ERROR: [DM_QUERY2_E_DUPLICATE_DEFAULT_POLICY]

SEVERITY: ERROR
DESCRIPTION: Duplicate DEFAULT BUSINESS POLICY clause.
CAUSE: A duplicate DEFAULT BUSINESS POLICY clause was found.
ACTION: Remove the duplicate clause.
PARAMS: None.

ERROR: [DM_QUERY2_E_UNKNOWN_XQUERY_TARGET]

SEVERITY: ERROR
DESCRIPTION: S Unknown XQuery target: %s PARAMETER: taget type.
CAUSE: Currently, content server only supports two types of XQuery target, XMLStore and FULLTEXT.
ACTION: You should execute the XQuery statement against either XML Store or FULLTEXT.
PARAMS:

ERROR: [DM_QUERY2_E_NO_ARCHIVE_SERVICE_LICENSE]

SEVERITY: ERROR
DESCRIPTION: An Archive Services license is required to create a lightweight or shareable type
CAUSE: User tried to create a lightweight or shareable type, but there is no valid AS license configured for the respository.
ACTION: Contact EMC Technical support to purchase a AS license.
PARAMS:

ERROR: [DM_QUERY2_E_ILLEGAL_ATTR_LEVEL_PRIMARY_KEY]

SEVERITY: ERROR
DESCRIPTION: SS The primary key specified at the attribute level for attribute %s references another attribute (%s).
CAUSE: You have attempted to define a primary key at the attribute level involving another attribute.
ACTION: Move this primary key specification to the type level.
PARAMS: The first parameter is the name of the attribute on which the primary key is defined. The second parameter is the name of the offending attribute.

ERROR: [DM_QUERY2_E_ALLOW_ASPECTS_NOT_SUPERUSER]

SEVERITY: ERROR
DESCRIPTION: S You do not have super-user privileges to alter (%s) type to allow aspects
CAUSE: You do not have super user privileges to alter a type to allow aspects.
ACTION: Login as a user with super-user privileges and re-issue the statement
PARAMS:

ERROR: [DM_QUERY2_E_DD_FILE_NOT_FOUND_IN_DOCBASE]

SEVERITY: ERROR
DESCRIPTION: SS The object with the path %s and version %s is not found in the docbase.
CAUSE: The user has specified an incorrect path and version to a sysobject.
ACTION: Correct the path and version number to the sysobject. Try not specifying the version number
PARAMS: The first parameter is the path of the sysobject, which consists of the folder path and object name The second parameter is the version of the sysobject.

ERROR: [DM_QUERY2_E_PARTITION_NOT_SUPPORTED]

SEVERITY: ERROR
DESCRIPTION: Data partitioning is not supported.
CAUSE: You attempted to run some functionalities related to data partitioning feature which is not supported for the database vendor that content server is running on.
ACTION: None.
PARAMS:

ERROR: [DM_QUERY2_E_LITERAL_EXPR_STRING_TOO_LONG]

SEVERITY: ERROR
DESCRIPTION: SII The the length of literal expression %s (%d) exceeds the maximum allowed for a literal (%d).
CAUSE: You have specified a literal value that is too long.
ACTION: Use a shorter literal value.
PARAMS: The first parameter is the literal. The second parameter is the length of the literal. The third parameter is the maximum allowed length.

ERROR: [DM_QUERY2_E_LITERAL_REQUIRED]

SEVERITY: ERROR
DESCRIPTION: Only literal values are allowed here.
CAUSE: An expression, or some other form of value was used where a literal value is required.
ACTION: Use a literal value instead of an expression.
PARAMS: None.

ERROR: [DM_QUERY2_E_REPEATING_ASPECT_ATTR_IN_SUBQUERY]

SEVERITY: ERROR
DESCRIPTION: You cannot specify a repeating aspect attribute(s) in the select list of a subquery.
CAUSE: This is the limitation of DQL query with repeating aspect attributes.
ACTION: revise the query, dont put repeating aspect arribute in the select list of a subquery.
PARAMS:

ERROR: [DM_QUERY2_E_JOIN_SEARCH]

SEVERITY: ERROR
DESCRIPTION: Your query specifies both a fulltext query and a multi-type join.
CAUSE: Only one type may be specified in the FROM clause when fulltext querying is done.
ACTION: Correct the query and retry.
PARAMS:

ERROR: [DM_QUERY2_E_NO_CHILD_COLUMNS_FOR_TYPE_LEVEL_FOREIGN_KEY]

SEVERITY: ERROR
DESCRIPTION: A Foreign Key specified at the type level must contain a child attribute list.
CAUSE: The child attribute list was omitted from a foriegn key specification at the type level.
ACTION: Specify a child attribute list.
PARAMS: The parameter is the name of the type.

ERROR: [DM_QUERY2_E_ALTER_ASPECT_ATTR_DEF_MISMATCH]

SEVERITY: ERROR
DESCRIPTION: Invalid data type or nature of i_attr_def attribute
CAUSE: The data type or the nature of the i_attr_def attribute in the dmc_aspect_type type does not match the expectation of the Content Server.
ACTION: This is a server intrinsic type and is created/altered by a script that runs during server configuration or upgrade. Check if there was any failure while configuring the repository and address them.
PARAMS:

ERROR: [DM_QUERY2_E_DUPLICATE_VALUE_ESTIMATE]

SEVERITY: ERROR
DESCRIPTION: Duplicate VALUE ESTIMATE clause for value assistance.
CAUSE: The VALUE ESTIMATE clause was specified more than once in value assistance.
ACTION: Remove the extra clauses.
PARAMS: None.

ERROR: [DM_QUERY2_E_MISS_LIGHTWEIGHT_OR_SHARES]

SEVERITY: ERROR
DESCRIPTION: lightweight and shares keywords must co-exist to create a lightweight type.
CAUSE: You attempted to create a lightweight type without specifying either lightweight or shares keyword.
ACTION: Change the create statement so that it has both lightweight and shares keywords to create a lightweight type.
PARAMS:

ERROR: [DM_QUERY2_E_DATA_TYPE_NOT_SUPPORTED]

SEVERITY: ERROR
DESCRIPTION: SSS The data type, %s, declared for attribute, %s, is not supported in %s database platform.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_QUERY2_E_NOT_SHAREABLE_TYPE]

SEVERITY: ERROR
DESCRIPTION: S Shared parent type (%s) is not a shareable type.
CAUSE: When you create a lightweight type, the shared parent type must be a shareable type.
ACTION: Use a shareable type as shared parent.
PARAMS: The type name.

ERROR: [DM_QUERY2_E_VALUE_LIST_WRONG_TYPE]

SEVERITY: ERROR
DESCRIPTION: SSSS A literal in the value assistance list for type %s, attribute %s is the wrong type. Expected %s, found %s.
CAUSE: One of the literal values in a value assistance list is not the same data type as the attribute that the value assistance belongs to.
ACTION: Change the literal to one of the correct type.
PARAMS: The first parameter is the name of the type. The second parameter is the name of the attribute. The third parameter is the data type of the attribute. The fourth parameter is the data type of the value found.

ERROR: [DM_QUERY2_E_QUERY_VA_NOT_SELECT]

SEVERITY: ERROR
DESCRIPTION: The QRY form of value assistance must use a SELECT statement.
CAUSE: The query_string specified for QRY value assistance is not a SELECT statement.
ACTION: Only use a SELECT statement for QRY value assistance.
PARAMS: None.

ERROR: [DM_QUERY2_E_VA_QUERY_SYNTAX]

SEVERITY: ERROR
DESCRIPTION: SS For the query string used in QRY value assistance, a parser error (%s) has occurred in the vicinity of: %s
CAUSE: and ACTION for the error SYNTAX above.
ACTION: Correct the syntax error.
PARAMS: See the PARAMETERS for the error SYNTAX above.

ERROR: [DM_QUERY2_E_DUPLICATE_FOREIGN_KEY]

SEVERITY: ERROR
DESCRIPTION: You cannot supply two foreign keys with the same child attributes.
CAUSE: Two foreign keys were supplied for the same type or attribute that have the same child attributes.
ACTION: Remove all but one of the duplicates.
PARAMS: None.

ERROR: [DM_QUERY2_E_CANNOT_GENERATE_FOREIGN_KEY_NAME]

SEVERITY: ERROR
DESCRIPTION: SS Cannot generate a foreign key name for type %s attribute %s.
CAUSE: There are too many foreign keys on the same type/attribute combination.
ACTION: Remove any unneeded foreign keys.
PARAMS: The first parameter is the type name. The second parameter is the attribute name.

ERROR: [DM_QUERY2_E_UNRECOGNIZED_HINT]

SEVERITY: ERROR
DESCRIPTION: S %s is an unknown hint or is being used incorrectly.
CAUSE: Either the query was passed in with a DQL hint that is not recognized by the server, or the syntax used for the hint was incorrect.
ACTION: Please see the documentation for recognized database hints. Try running the query without hints.
PARAMS: The first parameter is the unrecognized hint.

ERROR: [DM_QUERY2_E_DUPLICATE_ALLOW_CACHING]

SEVERITY: ERROR
DESCRIPTION: Duplicate ALLOW CACHING clause for value assistance.
CAUSE: The ALLOW CACHING clause was specified more than once in value assistance.
ACTION: Remove the extra clauses.
PARAMS: None.

ERROR: [DM_QUERY2_E_DATA_DICTIONARY_PUBLISH_SYNTAX]

SEVERITY: ERROR
DESCRIPTION: S The alter/create statement should either have the word PUBLISH, or be left blank. %s is an invalid argument.
CAUSE: There is a syntax error in the alter/create type statement.
ACTION: The word PUBLISH should be spelled correctly, or not be appended to the dql statement. Try leaving the word publish off.
PARAMS: The parameter is the syntax token that is unrecognized.

ERROR: [DM_QUERY2_E_DEFAULT_FOR_ADDED_ATTRIBUTE]

SEVERITY: ERROR
DESCRIPTION: You cannot supply a DEFAULT value when adding an attribute.
CAUSE: You supplied a DEFAULT value in the same ALTER TYPE statement that you added the attribute.
ACTION: ADD the attribute without a DEFAULT value, then ALTER the type in a separate ALTER TYPE statement to add the DEFAULT value.
PARAMS: None.

ERROR: [DM_QUERY2_E_PARTITION_API_INVALID_ARG2]

SEVERITY: ERROR
DESCRIPTION: DEFAULT_PARTITION and DEFAULT_TABLESPACE need to co-exist if you specify any of them in the GENERATE_PARTITION_SCHEME_SQL apply method.
CAUSE: You have specified either DEFAULT_PARTITION or DEFAULT_TABLESPACE, but not both in the GENERATE_PARTITION_SCHEME_SQL apply method.
ACTION: You can specify both or neither of them.
PARAMS:

ERROR: [DM_QUERY2_E_DROP_FTATTRS_FAILED]

SEVERITY: ERROR
DESCRIPTION: S An attempt to drop an indexed attribute(s) failed because there are existing indexed objects of type %s in the docbase.
CAUSE: An attempt was made to drop an indexed attribute from a type with existing indexed objects.
ACTION: Drop and recreate or reset the fulltext index before dropping indexed attributes.
PARAMS: The type name

ERROR: [DM_QUERY2_E_NO_UNIQUE_KEY]

SEVERITY: ERROR
DESCRIPTION: No unique key matching the one specified exists to DROP.
CAUSE: An attempt was made to drop a unique key that does not exist.
ACTION: Verify that the type or attribute you specified has a unique key with the combination of key attributes that you specified.
PARAMS: None.

ERROR: [DM_QUERY2_E_DATA_DICT_ERROR_FOR_TYPE_A_C]

SEVERITY: ERROR
DESCRIPTION: S The following error(s) occurred processing an ALTER/CREATE statement for type %s.
CAUSE: This message is providing additional information about the error message(s) that follow involving constructs applied to the specified type.
ACTION: Correct the errors indicated by the following message(s).
PARAMS: The parameter is the type name.

ERROR: [DM_QUERY2_E_ADD_ATTRIBUTES_FOR_POLICY_OVERRIDE]

SEVERITY: ERROR
DESCRIPTION: You cannot ADD type attributes for a business policy state.
CAUSE: An ADD attribute clause was specified in an ALTER TYPE statement for a business policy state.
ACTION: Remove the ADD attribute clause.
PARAMS: None.

ERROR: [DM_QUERY2_E_ADD_FULLTEXT_FOR_POLICY_OVERRIDE]

SEVERITY: ERROR
DESCRIPTION: You cannot specify an ADD_FTINDEX clause for a business policy state.
CAUSE: An ADD_FTINDEX clause was specified in an ALTER TYPE statement for a business policy state.
ACTION: Remove the ADD_FTINDEX clause.
PARAMS: None.

ERROR: [DM_QUERY2_E_ALTER_ASPECT_CANNOT_TOGGLE_OPTIMIZEFETCH]

SEVERITY: ERROR
DESCRIPTION: S Optimization options for aspect attributes OPTIMIZEFETCH or NO OPTIMIZEFETCH specified does not match the current setting for aspect (%s)
CAUSE: An ALTER ASPECT statement was executed with OPTIMIZEFETCH or NO OPTIMIZEFETCH for an aspect to which attributes have been previously defined, and the optimization option differs from what was specified the first time attributes were added to the aspect.
ACTION: optimization options for aspect attributes specified in the ALTER ASPECT statement the first time it was executed for an aspect cannot be changed when adding additional attributes to the same aspect. Execute the statement without specifying any optimization options.
PARAMS:

ERROR: [DM_QUERY2_E_BAD_VALUE_SEPARATOR]

SEVERITY: ERROR
DESCRIPTION: S The string %s specified in the SEPARATOR clause is not length 1.
CAUSE: The SEPARATOR clause specified an invalid string.
ACTION: Use a single-character string.
PARAMS: The parameter is the string specified.

ERROR: [DM_QUERY2_E_MIXED_TYPE_REPEATING_ATTRS]

SEVERITY: ERROR
DESCRIPTION: Repeating attributes from shared parent type and repeating attributes from lightweight type, or repeating attribute and single attributes cannot be referenced in an expression in a select list item when querying a lightweight type.
CAUSE: You atempted to combine repeating attributes from shared parent type and repeating attributes from lightweight type in a select list item.
ACTION: You need to modify the select statement to separate repeating attributes from shared parent type and repeating attributes from lightweight type.
PARAMS:

ERROR: [DM_QUERY2_E_BAD_UPDATE_CLAUSE_IN_MODIFIER]

SEVERITY: ERROR
DESCRIPTION: S The %s form of the update clause is not allowed in a type/attribute modifier.
CAUSE: A form of the update clause was used that is not supported for type/attribute modifiers.
ACTION: Remove the unsupported form of update.
PARAMS: The parameter is the name of the update construct used.

ERROR: [DM_QUERY2_E_BAD_ATTR_FOR_TYPE]

SEVERITY: ERROR
DESCRIPTION: SS Attribute %s does not exist for type %s.
CAUSE: The attribute does not exist in the given type.
ACTION: Specify a legal attribute.
PARAMS: The first parameter is the attribute name. The second parameter is the type name.

ERROR: [DM_QUERY2_E_DUPLICATE_IS_COMPLETE]

SEVERITY: ERROR
DESCRIPTION: Duplicate IS COMPLETE clause for value assistance.
CAUSE: The IS COMPLETE clause was specified more than once in value assistance.
ACTION: Remove the extra clauses.
PARAMS: None.

ERROR: [DM_QUERY2_E_MIXED_TYPE_REPEATING_ASPECT_ATTRS]

SEVERITY: ERROR
DESCRIPTION: Repeating attributes from different aspects cannot be referenced in an expression in a select list item.
CAUSE: You attemped to combine repeating attributes from different aspects in a select list item.
ACTION: You need to modify the select statement to separate repeating attributes from different aspects.
PARAMS:

ERROR: [DM_QUERY2_E_ALTER_ASPECT_CANT_GET_TEMP_DATABASE_CONNECTION]

SEVERITY: ERROR
DESCRIPTION: Unable to get a temporary database connection to perform the alter aspect operation
CAUSE: A database error occured when attempting to obtain a database connection.
ACTION: See the accompanying error message(s).
PARAMS:

ERROR: [DM_QUERY2_E_DUPLICATE_DROP_COMPONENTS]

SEVERITY: ERROR
DESCRIPTION: Duplicate DROP COMPONENTS clause.
CAUSE: A duplicate DROP COMPONENTS clause was found.
ACTION: Remove the duplicate clause.
PARAMS: None.

ERROR: [DM_QUERY2_E_QUERY_VA_ATTR_WRONG_TYPE]

SEVERITY: ERROR
DESCRIPTION: SSSSS The type of the query attribute (%s) from QRY value assistance does not match the type of attribute %s in type %s. Expected %s, found %s.
CAUSE: The result attribute for QRY value assistance is the wrong data type.
ACTION: The result attribute must match the type of the attribute for which the value assistance is defined.
PARAMS: The first parameter is the result attribute for QRY value assistance. The second parameter is the name of the attribute for which the value assistance is being defined. The third parameter is the name of the type. The fourth parameter is the expected data type. The fifth parameter is the actual data type.

ERROR: [DM_QUERY2_E_DATA_DICT_ERROR_FOR_ATTR_A_C]

SEVERITY: ERROR
DESCRIPTION: SS The following error(s) occurred processing an ALTER/CREATE statement for type %s, attribute %s.
CAUSE: This message is providing additional information about the error message(s) that follow involving constructs applied to the specified attribute of the specified type.
ACTION: Correct the errors indicated by the previous message.
PARAMS: The first parameter is the type name. The second parameter is the attribute name.

ERROR: [DM_QUERY2_E_NO_PRIMARY_KEY]

SEVERITY: ERROR
DESCRIPTION: No primary key exists to DROP.
CAUSE: An attempt was made to drop a primary key that does not exist.
ACTION: Verify that the type or attribute you specified has a primary key.
PARAMS: None.

ERROR: [DM_QUERY2_E_DUPLICATE_DROP_COMPUTED_FROM]

SEVERITY: ERROR
DESCRIPTION: Duplicate DROP COMPUTED FROM clause.
CAUSE: A duplicate DROP COMPUTED FROM clause was found.
ACTION: Remove the duplicate clause.
PARAMS: None.

ERROR: [DM_QUERY2_E_NO_SHAREABLE_SUBTYPES]

SEVERITY: ERROR
DESCRIPTION: S Cannot make type %s shareable as it has shareable subtypes
CAUSE: You are trying to make a type shareable when it already has subtypes that are shareable
ACTION: Create a new shareable subtype instead. PARAMETER: The parameter is the name of the type that cannot be made shareable.
PARAMS:

ERROR: [DM_QUERY2_E_ALLOW_ASPECTS_CANT_ALLOW]

SEVERITY: ERROR
DESCRIPTION: S Type %s cannot be altered to allow aspects because the type or a sub-type in the type hierarchy has an attribute named r_aspect_name
CAUSE: The type being altered to allow aspects has the r_aspect_name attribute or a sub-type (direct or indirect) of the type being altered has an attribute named r_aspect_name.
ACTION: Drop the r_aspect_name attribute from the type or its sub-type and then execute the statement on the type.
PARAMS:

ERROR: [DM_QUERY2_E_DUPLICATE_DEFAULT]

SEVERITY: ERROR
DESCRIPTION: Duplicate DEFAULT value clause.
CAUSE: A duplicate DEFAULT value clause was found.
ACTION: Remove the duplicate clause.
PARAMS: None.

ERROR: [DM_QUERY2_E_DUPLICATE_COMPUTED]

SEVERITY: ERROR
DESCRIPTION: Duplicate COMPUTED FROM clause.
CAUSE: A duplicate COMPUTED FROM clause was found.
ACTION: Remove the duplicate clause.
PARAMS: None.

ERROR: [DM_QUERY2_E_INCORRECT_GROUPBY_FOR_LIGHTWEIGHT_AGGREGATE]

SEVERITY: ERROR
DESCRIPTION: The DQL statement has an aggregate function on a lightweight repeating attribute, the group by clause can only have r_object_id.
CAUSE: This is the limitation with aggregate function and lightweight repeating attribute in the same DQL statement.
ACTION: Correct the DQL statement by adding r_object_id in the select list and group by clause.
PARAMS:

ERROR: [DM_QUERY2_E_DUPLICATE_VALUE_SEPARATOR]

SEVERITY: ERROR
DESCRIPTION: Duplicate SEPARATOR clause for value assistance.
CAUSE: The SEPARATOR clause was specified more than once in value assistance.
ACTION: Remove the extra clauses.
PARAMS: None.

ERROR: [DM_QUERY2_E_ALTER_ASPECT_UNABLE_TO_FETCH_TYPE]

SEVERITY: ERROR
DESCRIPTION: S Unable to fetch type (%s)
CAUSE: The type mentioned in the error message is not found in the repository.
ACTION: This is a server intrinsic type and is created by a script that runs during server configuration or upgrade. Check if there was any failure while configuring the repository and address them.
PARAMS:

ERROR: [DM_QUERY2_E_DEFAULT_ASPECTS_TYPE_NOT_ALLOWED]

SEVERITY: ERROR
DESCRIPTION: S The type (%s) specified in the ALTER TYPE statement is not enabled for default aspects.
CAUSE: The type specified in the ALTER TYPE [SET|ADD|REMOVE] statement is either a lightweight type or is not aspects enabled. You cannot define default aspects for lightweight object types, nor for non-lightweight object types that do not allow aspects.
ACTION: If the type is not a lightweight type, issue an ALTER TYPE ALLOW ASPECTS on the specified types supermost type before re-issuing this statement again. Note that you cannot issue an ALTER TYPE to allow aspects on lightweight object type.
PARAMS:

ERROR: [DM_QUERY2_E_DEFAULT_PERMIT_FOR_POLICY_OVERRIDE]

SEVERITY: ERROR
DESCRIPTION: You cannot specify a (default) PERMIT clause for a business policy state.
CAUSE: A PERMIT clause was specified in an ALTER TYPE statement for a business policy state.
ACTION: Remove the PERMIT clause.
PARAMS: None.

ERROR: [DM_QUERY2_E_ALTER_NOT_PRIMARY_TYPE_FOR_POLICY]

SEVERITY: ERROR
DESCRIPTION: SSD The type being altered (%s) is not the primary type (%s) for the busines policy with object id %s.
CAUSE: An attempt was made to alter a type for a specific business policy state, but the type altered is not the primary type for the business policy.
ACTION: Alter the primary type.
PARAMS: The first parameter is the name of the type being altered. The second parameter is the the primary type for the business policy. The third parameter is the object id of the business policy.

ERROR: [DM_QUERY2_E_TYPE_ALREADY_PARTITIONED]

SEVERITY: ERROR
DESCRIPTION: S Type (%s) is already partitioned.
CAUSE: You attempted to enable partition for a type which is already partitioned.
ACTION: None.
PARAMS:

ERROR: [DM_QUERY2_E_NQA_IN_SUBQUERY]

SEVERITY: ERROR
DESCRIPTION: You cannot specify a nonqualifiable attribute in the select list of a subquery.
CAUSE: This is the limitation of DQL query with nonqualifiable attributes.
ACTION: revise the query, dont put nonqualifiable arribute in the select list of a subquery.
PARAMS:

ERROR: [DM_QUERY2_E_ALREADY_SHAREABLE]

SEVERITY: ERROR
DESCRIPTION: S Type (%s) is already a shareable type.
CAUSE: You attempted to alter a shareable type to shareable.
ACTION: Correct your query by specifying a currently non-shareable type. The type must be dm_sysobject or a dm_sysobject subtype. PARAMETER: None
PARAMS:

ERROR: [DM_QUERY2_E_DATE_LITERAL_IN_UPDATE_MODIFIER]

SEVERITY: ERROR
DESCRIPTION: Date literals are not supported in the update form of a type/attribute modifier.
CAUSE: A value was specified that was not a date literal for an update modifier.
ACTION: There are no modifiers of type date, so specify the correct type of literal.
PARAMS: None.

ERROR: [DM_QUERY2_E_BAD_FUNCTION_LOCATION_ID]

SEVERITY: ERROR
DESCRIPTION: SD The location id for user function %s is invalid (%s).
CAUSE: The user function specification has a bad object id given as the location.
ACTION: Correct the location object id information to the user function.
PARAMS: The first parameter is the name of the user function. The second parameter is the invalid location object id.

ERROR: [DM_QUERY2_E_PIPER_NOT_SUPPORTED_YET_TYPE_A_C]

SEVERITY: ERROR
DESCRIPTION: SS ALTER/CREATE for type %s: Feature (%s) is not yet supported in Piper.
CAUSE: This message should only be seen during Piper development. You have attempted an operation on a type that requires Data Dictionary support that has not yet been added to Piper.
ACTION: Remove the indicated construct until it is supported.
PARAMS: The first parameter is the type name. The second parameter describes the un-implemented feature.

ERROR: [DM_QUERY2_E_DROP_FULLTEXT_FOR_POLICY_OVERRIDE]

SEVERITY: ERROR
DESCRIPTION: You cannot specify a DROP_FTINDEX clause for a business policy state.
CAUSE: A DROP_FTINDEX clause was specified in an ALTER TYPE statement for a business policy state.
ACTION: Remove the DROP_FTINDEX clause.
PARAMS: None.

ERROR: [DM_QUERY2_E_ALTER_ASPECT_MULTIPLE_ASPECTS_FOUND]

SEVERITY: ERROR
DESCRIPTION: S Multiple aspects with the name (%s) was found in the repository
CAUSE: More than one aspect with the same name was found in the repository.
ACTION: Aspects must be uniquely named.
PARAMS:

ERROR: [DM_QUERY2_E_DUPLICATE_PRIMARY_KEY]

SEVERITY: ERROR
DESCRIPTION: You cannot supply two primary keys for the same type.
CAUSE: Two primary keys were supplied for the same type.
ACTION: Remove all but one of the duplicates.
PARAMS: None.

ERROR: [DM_QUERY2_E_MAPPING_TABLE_FOR_WHOLE_TYPE]

SEVERITY: ERROR
DESCRIPTION: S A mapping table was specified for type %s. It is only allowed on individual attributes.
CAUSE: A mapping table clause was specified for the entire type, rather than for an individual attribute.
ACTION: Remove the mapping table clause, or move it to apply to an attribute.
PARAMS: The parameter is the name of the type.

ERROR: [DM_QUERY2_E_DUPLICATE_DROP_VALUE_ASSIST]

SEVERITY: ERROR
DESCRIPTION: Duplicate DROP VALUE ASSISTANCE clause.
CAUSE: A duplicate DROP VALUE ASSISTANCE clause was found.
ACTION: Remove the duplicate clause.
PARAMS: None.

ERROR: [DM_QUERY2_E_SHAREABLE_NOT_LITETYPE]

SEVERITY: ERROR
DESCRIPTION: Shareable object types cannot be set to lightweight
CAUSE: You tried to alter a shareable type to make it lightweight. Shareable object types cannot be lightweight.
ACTION: Specify a non-shareable type. You can only alter a regular dm_sysobject type or a subtype as lightweight. PARAMETER: none.
PARAMS:

ERROR: [DM_QUERY2_E_UPDATE_ATTRIBUTE_NOT_REPEATING]

SEVERITY: ERROR
DESCRIPTION: S The Data Dictionary attribute %s is not repeating.
CAUSE: You attempted to APPEND or INSERT into a Data Dictionary attribute that is not repeating.
ACTION: Remove the update clause for the named attribute or use a repeating attribute.
PARAMS: The parameter is the name of the Data Dictionary attribute.

ERROR: [DM_QUERY2_E_REPEATING_ASPECT_ATTR_IN_INVALID_CLAUSE]

SEVERITY: ERROR
DESCRIPTION: S You cannot specify a repeating aspect attribute(s) in %s clause.
CAUSE: This is the limitation of DQL query with repeating aspect attributes.
ACTION: revise the query, dont put repeating aspect arribute in the specified clause.
PARAMS:

ERROR: [DM_QUERY2_E_DUPLICATE_DROP_DEFAULT]

SEVERITY: ERROR
DESCRIPTION: Duplicate DROP DEFAULT clause.
CAUSE: A duplicate DROP DEFAULT clause was found.
ACTION: Remove the duplicate clause.
PARAMS: None.

ERROR: [DM_QUERY2_E_DATA_DICTIONARY_PUBLISH_FAILURE]

SEVERITY: ERROR
DESCRIPTION: S While trying to publish Data dictionary information (dmi_dd_common/type/attr info) for object defined by %s, an error occured.
CAUSE: There may be an error in the dmi_dd_common/dmi_dd_type/dmi_dd_attr s and r tables.
ACTION: Try repeating the statement without an explicit PUBLISH command, or try repeating the statement. Contact Documentum.
PARAMS: The first parameter is the name of the type being published, the attribute name, business policy and state name

ERROR: [DM_QUERY2_E_BAD_VALUE_ESTIMATE]

SEVERITY: ERROR
DESCRIPTION: I VALUE ESTIMATE (%d) must be greater than zero.
CAUSE: The VALUE ESTIMATE specified was not greater than zero.
ACTION: Specify a value greater than zero.
PARAMS: The parameter is the value estimate.

ERROR: [DM_QUERY2_E_DEFAULT_STORAGE_FOR_POLICY_OVERRIDE]

SEVERITY: ERROR
DESCRIPTION: You cannot specify a DEFAULT STORAGE clause for a business policy state.
CAUSE: A DEFAULT STORAGE clause was specified in an ALTER TYPE statement for a business policy state.
ACTION: Remove the DEFAULT STORAGE clause.
PARAMS: None.

ERROR: [DM_QUERY2_E_ALTER_BAD_STATE_NAME]

SEVERITY: ERROR
DESCRIPTION: DS The business policy with object id %s does not have a state named %s.
CAUSE: The state specified does not exist in the business policy.
ACTION: Use a valid state name.
PARAMS: The first parameter is the business policy object id specified. The second parameter is the business policy state name.

ERROR: [DM_QUERY2_E_DUPLICATE_VALUE_ASSIST]

SEVERITY: ERROR
DESCRIPTION: Duplicate VALUE ASSISTANCE clause.
CAUSE: A duplicate VALUE ASSISTANCE clause was found.
ACTION: Remove the duplicate clause.
PARAMS: None.

ERROR: [DM_QUERY2_E_LITETYPE_NOT_SHAREABLE]

SEVERITY: ERROR
DESCRIPTION: Lightweight object types cannot be set to shareable
CAUSE: You tried to alter a lightweight type to make it shareable. Lightweight object types cannot be shareable.
ACTION: Change the type name in the statement to a valid type name. You can only alter a regular dm_sysobject type or a subtype as shareable. PARAMETER: none.
PARAMS:

ERROR: [DM_QUERY2_E_NON_PARTITIONABLE_TYPE]

SEVERITY: ERROR
DESCRIPTION: S Internal type %s cannot be partitioned.
CAUSE: You attempted to alter a nonpartition-able internal type to a partitioned type.
ACTION: Dont do this.
PARAMS:

ERROR: [DM_QUERY2_E_DROP_ATTRIBUTES_FOR_POLICY_OVERRIDE]

SEVERITY: ERROR
DESCRIPTION: You cannot DROP type attributes for a business policy state.
CAUSE: A DROP attribute clause was specified in an ALTER TYPE statement for a business policy state.
ACTION: Remove the DROP attribute clause.
PARAMS: None.

ERROR: [DM_QUERY2_E_BAD_COMPONENT_ID]

SEVERITY: ERROR
DESCRIPTION: SS Bad object id %s for component classifier %s.
CAUSE: The object id of the component specified for the indicated component classifier is invalid.
ACTION: Specify a legal object id.
PARAMS: The first parameter is the object id. The second parameter is the component classifier.

ERROR: [DM_QUERY2_E_DEFAULT_ASPECTS_NOT_SUPERUSER]

SEVERITY: ERROR
DESCRIPTION: S You do not have Superuser privileges to alter the (%s) type to set/add/remove default aspects
CAUSE: You do not have Superuser privileges to alter a type to set/add/remove default aspects.
ACTION: Login as a user with Superuser privileges and re-issue the statement
PARAMS:

ERROR: [DM_QUERY2_E_DUPLICATE_QRY_ATTR]

SEVERITY: ERROR
DESCRIPTION: Duplicate QRY ATTR clause for value assistance.
CAUSE: The QRY ATTR clause was specified more than once in value assistance.
ACTION: Remove the extra clauses.
PARAMS: None.

ERROR: [DM_QUERY2_E_COLLECTION_FAIL]

SEVERITY: ERROR
DESCRIPTION: S Error executing query the query collection terminated abnormally. Query was: %s
CAUSE: The query was started properly but an error occurred while iterating through the results. Typically this error is triggered by an error on the underlying database cursor. The system should have logged a previous error giving a more detailed reason for the error.
ACTION: Check error log for previous error giving more detail on the problem. Look for errors in the database logs.
PARAMS: %1 Query text that was being executed.

ERROR: [DM_QUERY2_E_QUERY_VA_AS_NAME]

SEVERITY: ERROR
DESCRIPTION: S The QRY form of value assistance cannot use an AS name (%s) in the select list.
CAUSE: The query_string specified for QRY value assistance uses an as name.
ACTION: Change the select list to not use an as name.
PARAMS: The parameter is the as name.

ERROR: [DM_QUERY2_E_WRONG_PRIVILEGE_FOR_LITE_KEYWORD]

SEVERITY: ERROR
DESCRIPTION: The query with LITE keyword was issued by user without enough privilege, only superuser, or member of dm_read_all (or dm_browse_all) can issue such kind of query.
CAUSE: User without enough privilege issues query with LITE keyword.
ACTION: Make sure that only superuser, or member of dm_read_all (or dm_browse_all) issues such kind of query.
PARAMS:

ERROR: [DM_QUERY2_E_BAD_VALUE_LIST_ELEMENT]

SEVERITY: ERROR
DESCRIPTION: Only literal values are allowed in a value assistance list.
CAUSE: An expression, or some other form of value was used in the value list for the list form of value assistance.
ACTION: Use a literal value instead of an expression.
PARAMS: None.

ERROR: [DM_QUERY2_E_LITERAL_VALUE_WRONG_TYPE]

SEVERITY: ERROR
DESCRIPTION: SSSS A literal supplied for type %s, attribute %s is the wrong type. Expected %s, found %s.
CAUSE: A literal value is not the same data type as the attribute that the value was supplied to.
ACTION: Change the literal to one of the correct type.
PARAMS: The first parameter is the name of the type. The second parameter is the name of the attribute. The third parameter is the data type of the attribute. The fourth parameter is the data type of the value found.

ERROR: [DM_QUERY2_E_ALTER_ASPECT_INVALID_ASPECT]

SEVERITY: ERROR
DESCRIPTION: S Aspect (%s) is invalid and is not found in the repository
CAUSE: There is no aspect in the repository with the specified name.
ACTION: Specify a valid aspect name in the command/DQL statement.
PARAMS:

ERROR: [DM_QUERY2_E_MAPPING_TABLE_WRONG_TYPE]

SEVERITY: ERROR
DESCRIPTION: SSSS A literal in the mapping table value list for type %s, attribute %s is the wrong type. Expected %s, found %s.
CAUSE: One of the literal values in a mapping table value list is not the same data type as the attribute that the mapping table value list belongs to.
ACTION: Change the literal to one of the correct type.
PARAMS: The first parameter is the name of the type. The second parameter is the name of the attribute. The third parameter is the data type of the attribute. The fourth parameter is the data type of the value found.

ERROR: [DM_QUERY2_E_BAD_QRY_ATTR]

SEVERITY: ERROR
DESCRIPTION: S The attribute %s specified in the QRY ATTR clause does not exist in the type.
CAUSE: The QRY ATTR clause specified an invalid attribute.
ACTION: Use a valid attribute name.
PARAMS: The parameter is the attribute name specified.

ERROR: [DM_QUERY2_E_QUERY_VA_QUERY_ATTR_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: S The attribute specified in the QRY ATTR clause (%s) was not found in the select list for the QRY value assistance query.
CAUSE: If QRY ATTR is specified, the attribute must be present in the select list.
ACTION: Add the QRY ATTR to the select list.
PARAMS: The parameter is the attribute name from the QRY ATTR clause.

ERROR: [DM_QUERY2_E_DROP_TYPE_COMMIT_EXTERNAL_TRANSACTION]

SEVERITY: ERROR
DESCRIPTION: S DROP TYPE for %s is not allowed inside an explicit transaction if Data Dictionary information is present.
CAUSE: An attempt was made to drop a type that has Data Dictionary information specified while an explicit user transaction was open.
ACTION: Move the drop type outside of the explicit transaction.
PARAMS: The parameter is the name of the type.

ERROR: [DM_QUERY2_E_DEFAULT_ACL_FOR_POLICY_OVERRIDE]

SEVERITY: ERROR
DESCRIPTION: You cannot specify a DEFAULT ACL clause for a business policy state.
CAUSE: A DEFAULT ACL clause was specified in an ALTER TYPE statement for a business policy state.
ACTION: Remove the DEFAULT ACL clause.
PARAMS: None.

ERROR: [DM_QUERY2_E_LIGHTWEIGHT_REPEATING_IN_SUBQUERY]

SEVERITY: ERROR
DESCRIPTION: You cannot specify lightweight repeating attribute(s) in the select list of a subquery.
CAUSE: This is the limitation of DQL query with lightweight repeating attributes.
ACTION: revise the query, dont query lightweight repeating in subquery.
PARAMS:

ERROR: [DM_QUERY2_E_DUPLICATE_COMPONENTS]

SEVERITY: ERROR
DESCRIPTION: Duplicate COMPONENTS clause.
CAUSE: A duplicate COMPONENTS clause was found.
ACTION: Remove the duplicate clause.
PARAMS: None.

ERROR: [DM_QUERY2_E_NO_ADD_FOREIGN_KEY_PRIV]

SEVERITY: ERROR
DESCRIPTION: You have insufficient privilege to add a foreign key.
CAUSE: You do not have at least sysadmin privilege.
ACTION: Ask your system administrator about creating the foreign key for you.
PARAMS: None.

ERROR: [DM_QUERY2_E_DATA_DICTIONARY_LOGGING_FAILURE]

SEVERITY: ERROR
DESCRIPTION: S While trying to log Data dictionary information (in dd_publish_log) for object defined by %s, an error occured.
CAUSE: There may be an error in the dd_publish_log table.
ACTION: Try repeating the statement without an explicit PUBLISH command, or try repeating the statement. Contact Documentum.
PARAMS: The first parameter is the name of the type being published, the attribute name, business policy and state name

ERROR: [DM_QUERY2_E_BAD_VA_FOR_VALUE_SEPARATOR]

SEVERITY: ERROR
DESCRIPTION: The SEPARATOR clause can only be specified for FUNCTION value assistance.
CAUSE: The SEPARATOR clause was specified for value assistance that is not FUNCTION.
ACTION: Only use the SEPARATOR clause for FUNCTION value assistance.
PARAMS: None.

ERROR: [DM_QUERY2_E_UNSUPPORTED_DD_DATE_FUNCTION]

SEVERITY: ERROR
DESCRIPTION: Only date(now), date(today), date(tomorrow), and date(yesterday) are allowed here.
CAUSE: A date function was used that is not supported for default values or value assistance lists.
ACTION: Change the unsupported date function to one of those listed.
PARAMS: None.

ERROR: [DM_QUERY2_E_DUPLICATE_UNIQUE_KEY]

SEVERITY: ERROR
DESCRIPTION: You cannot supply two unique keys with the same attributes.
CAUSE: Two identical unique keys were supplied for the same type or attribute.
ACTION: Remove all but one of the duplicates.
PARAMS: None.

ERROR: [DM_QUERY2_E_ALTER_CANNOT_FETCH_POLICY]

SEVERITY: ERROR
DESCRIPTION: D Could not fetch the business policy id (%s) specified in ALTER TYPE.
CAUSE: The policy object specified in the FOR POLICY clause of ALTER TYPE does not exist.
ACTION: Use a valid business policy object id.
PARAMS: The parameter is the business policy object id specified.

ERROR: [DM_QUERY2_E_NOT_DMSYSOBJECT_TYPE]

SEVERITY: ERROR
DESCRIPTION: S Type (%s) is not dm_sysobject or a dm_sysobject subtype.
CAUSE: You attempted to create a lightweight type with a non dm_sysobject type as the shared parent. A shared parent type must be dm_sysobject or a dm_sysobject subtype.
ACTION: Dont use a non dm_sysobject type as shared parent. PARAMETER: The type name.
PARAMS:

ERROR: [DM_QUERY2_E_NO_COLUMNS_FOR_TYPE_LEVEL_UNIQUE_KEY]

SEVERITY: ERROR
DESCRIPTION: A Unique constraint specified at the type level must contain an attribute list.
CAUSE: The attribute list was omitted from a unique constraint specification at the type level.
ACTION: Specify an attribute list.
PARAMS: The parameter is the name of the type.

ERROR: [DM_QUERY2_E_NOT_ENOUGH_PRIVILEGE_FOR_USER_FUNCTION]

SEVERITY: ERROR
DESCRIPTION: S To invoke code in a user-provided function (%s) you must have at least sysadmin privilege.
CAUSE: An attempt was made to specify a user-written function as an expression but the user did not have at least sysadmin privilege.
ACTION: Use a simple expression, or have an administrator add the user-written function.
PARAMS: The parameter is the name of the user-written function.

ERROR: [DM_QUERY2_E_UP_OUT_OF_RANGE]

SEVERITY: ERROR
DESCRIPTION: S Unable to set attribute %s because the value being assigned is out of range
CAUSE: Attempt to assign a value to an attribute which is out of range of the attributes datatype. For example, assigning a value to an integer attribute larger than the largest allowable integer.
ACTION: Either scale the values being assigned to such an attribute, or increase the range of the attribute to allow such values. For example, turn an attribute of type integer into type double.
PARAMS: The first parameter is the attribute name

ERROR: [DM_QUERY2_E_TOO_MANY_FOLDERS_FOR_FTDQL]

SEVERITY: ERROR
DESCRIPTION: I The folder predicate in the query exceeds the maximum number of supported folders (%d).
CAUSE: A query with FOLDER() predicate with DESCEND keyword, and with a SEARCH clause was executed. The total number of descendents exceeds the maximum allowed folders.
ACTION: Cannot execute the query with SEARCH clause in this case, its a limitation.
PARAMS:

ERROR: [DM_QUERY2_E_ALTER_ASPECT_NOT_SUPER_USER]

SEVERITY: ERROR
DESCRIPTION: You must be a super user to execute an alter aspect statement
CAUSE: You dont have super-user permission to alter an aspect.
ACTION: You must login as super-user or a user with super-user privileges and re-execute the statement.
PARAMS:

ERROR: [DM_QUERY2_E_ALTER_ASPECT_FAILED]

SEVERITY: ERROR
DESCRIPTION: Alter aspect statement failed.
CAUSE: Alter aspect statement failed.
ACTION: Refer to other error messages in the session.
PARAMS:

ERROR: [DM_QUERY2_E_NO_FUNCTION_LOCATION]

SEVERITY: ERROR
DESCRIPTION: S User function %s must specify a location by object id or folder path.
CAUSE: The user function specification has no location information.
ACTION: Add the location information to the user function.
PARAMS: The parameter is the name of the user function.

ERROR: [DM_QUERY2_E_ANY_PREDICATE_TYPES]

SEVERITY: ERROR
DESCRIPTION: You have specified attributes from more than one type in your ANY predicate.
CAUSE: The repeating attributes specified in the search condition of an ANY predicate must all be from the same type.
ACTION: Either correct the specification error, or reformulate your query, as needed.
PARAMS: None.

ERROR: [DM_QUERY2_E_ALLOW_ASPECTS_SYSOBJECT_TYPE_NOT_ALLOWED]

SEVERITY: ERROR
DESCRIPTION: S ALTER TYPE statement to ALLOW ASPECTS cannot be executed on a sysobject sub-type. Type (%s) is a sysobject sub-type
CAUSE: The ALTER TYPE .. ALLOW ASPECTS statement was executed on a sysobject sub-type.
ACTION: No need to alter a sysobject sub-type to have aspects. dm_sysobject and their sub-types are aspect enabled out of the box.
PARAMS:

ERROR: [DM_QUERY2_E_NO_DROP_FOREIGN_KEY_PRIV]

SEVERITY: ERROR
DESCRIPTION: You have insufficient privilege to drop a foreign key.
CAUSE: You do not have at least sysadmin privilege.
ACTION: Ask your system administrator about dropping the foreign key for you.
PARAMS: None.

ERROR: [DM_QUERY2_E_INCORRECT_GROUPBY_FOR_ASPECT_AGGREGATE]

SEVERITY: ERROR
DESCRIPTION: The DQL statement has an aggregate function on a repeating aspect attribute, the group by clause can only have r_object_id.
CAUSE: This is the limitation with aggregate function and repeating aspect attribute in the same DQL statement.
ACTION: You need to modify the DQL statement by adding r_object_id in the select list and group by clause.
PARAMS:

ERROR: [DM_QUERY2_E_NQA_IN_FUNCTION]

SEVERITY: ERROR
DESCRIPTION: S You cannot specify nonqualifiable attributes (%s) in the functions or expressions.
CAUSE: Nonqualifiable attributes cannot be passed to SQL functions and expressions.
ACTION: revise the query, dont put nonqualifiable arribute in SQL functions and expression.
PARAMS:

ERROR: [DM_QUERY2_E_BAD_DEFAULT_FOR_REPEATING]

SEVERITY: ERROR
DESCRIPTION: SS Attribute %s of type %s is repeating, so the list form of the DEFAULT value clause must be used.
CAUSE: The single value form of the DEFAULT value was used where the list form is required.
ACTION: Use a parenthesized list of comma separated values.
PARAMS: The first parameter is the name of the attribute. The second parameter is the name of the type.

ERROR: [DM_QUERY2_E_VALUE_ASSIST_FOR_WHOLE_TYPE]

SEVERITY: ERROR
DESCRIPTION: S Value assistance was specified for type %s. It is only allowed on individual attributes.
CAUSE: A value assistance clause was specified for the entire type, rather than for an individual attribute.
ACTION: Remove the value assistance clause, or move it to apply to an attribute.
PARAMS: The parameter is the name of the type.

ERROR: [DM_QUERY2_E_DEFAULT_FOR_WHOLE_TYPE]

SEVERITY: ERROR
DESCRIPTION: S A default value was specified for type %s. A default value is only allowed on individual attributes.
CAUSE: A DEFAULT value clause was specified for the entire type, rather than for an individual attribute.
ACTION: Remove the DEFAULT value clause, or move it to apply to an attribute.
PARAMS: The parameter is the name of the type.

ERROR: [DM_QUERY2_E_QUERY_VA_BAD_FIRST_VALUE]

SEVERITY: ERROR
DESCRIPTION: The first value in the select list for QRY value assistance is not a simple attribute name.
CAUSE: If no QRY ATTR is specified, the first element of the select list must be a simple attribute name.
ACTION: Change the select list to have a simple attribute name first, or use the QRY ATTR clause to specify a different attribute.
PARAMS: None.

ERROR: [DM_QUERY2_E_NO_COLUMNS_FOR_TYPE_LEVEL_PRIMARY_KEY]

SEVERITY: ERROR
DESCRIPTION: A Primary Key specified at the type level must contain an attribute list.
CAUSE: The attribute list was omitted from a primary key specification at the type level.
ACTION: Specify an attribute list.
PARAMS: The parameter is the name of the type.

ERROR: [DM_QUERY2_E_SYSOBJECT_FOR_FILE_NOT_FOUND_IN_DOCBASE]

SEVERITY: ERROR
DESCRIPTION: SSS The sysobject with object id: %s for the path %s and version %s is not found in the docbase.
CAUSE: The sysobject with the given r_object_id could not be fetched.
ACTION: Try seeing if the sysobject exists in the docbase. Try querying in the database for objects corresponding to the given r_object_id. Try not specifying the version number
PARAMS: The first parameter is the r_object_id of the sysobject which is being fetched. The second parameter is the path of the sysobject, which consists of the folder path and object name The third parameter is the version of the sysobject.

ERROR: [DM_QUERY2_E_FTDQL_LITE_TYPE_FAIL]

SEVERITY: ERROR
DESCRIPTION: S Cannot execute FTDQL for lightweight type %s that does not have fulltext support. PARAMETER: Type name
CAUSE: You have attempted to execute an FTDQL against a lightweight type that does not support fulltext.
ACTION: Just execute regular DQL query against the same type.
PARAMS:

ERROR: [DM_QUERY2_E_DUPLICATE_DROP_MAPPING_TABLE]

SEVERITY: ERROR
DESCRIPTION: Duplicate DROP MAPPING TABLE clause.
CAUSE: A duplicate DROP MAPPING TABLE clause was found.
ACTION: Remove the duplicate clause.
PARAMS: None.

ERROR: [DM_QUERY2_E_TOO_MANY_TYPES_IN_JOIN]

SEVERITY: ERROR
DESCRIPTION: Your query has too many types in the FROM clause.
CAUSE: There is a maximum number of types allowed in a FROM clause (currently 10). You will get this message for each type over the allowed maximum that you have in your FROM clause.
ACTION: Reformulate your query so fewer joins can be used (use subselects, if possible, or do multiple queries.
PARAMS:

ERROR: [DM_QUERY2_E_NO_HIGH_VOLUME_SERVER_LICENSE]

SEVERITY: ERROR
DESCRIPTION: A High-Volume Server license is required to create a lightweight or shareable type
CAUSE: User tried to create a lightweight or shareable type, but there is no valid HVS license configured for the respository.
ACTION: Contact EMC Technical support to purchase a HVS license.
PARAMS:

ERROR: [DM_QUERY2_E_UNSUPPORTED_DD_VALUE_SPECIFICATION]

SEVERITY: ERROR
DESCRIPTION: Only literals, NULL, USER, date(now), date(today), date(tomorrow), and date(yesterday) are allowed here.
CAUSE: A form of value specification was used that is not supported for default values or value assistance lists.
ACTION: Change the unsupported value specification to one of those listed.
PARAMS: None.

ERROR: [DM_QUERY2_E_ALTER_ASPECT_INVALID_OPERATION]

SEVERITY: ERROR
DESCRIPTION: SSS Cannot perform (%s) action on aspect (%s) because %s
CAUSE: An invalid operation is specified in the alter aspect statement for an aspect whose state is not inconsistent with attempted operation.
ACTION: Refer to the reason as part of the error message.
PARAMS:

ERROR: [DM_QUERY2_E_ALTER_ASPECT_UNABLE_TO_FETCH_ASPECT]

SEVERITY: ERROR
DESCRIPTION: SD Unable to fetch the aspect with name (%s) id (%s)
CAUSE: A database error occured while fetching an aspect object.
ACTION: Check associated error messages that contain database error.
PARAMS:

ERROR: [DM_QUERY2_E_INVALID_LOCALE_SETTING]

SEVERITY: ERROR
DESCRIPTION: SS ALTER/CREATE TYPE: The session_locale setting of %s in the sessionconfig object is not a valid locale in the docbase. The ALTER/CREATE is disallowed because it contains locale sensitive information for an invalid locale. Please either set the session_locale to a valid dd_locales value (%s), or add a new locale entry to dd_locales (dm_docbase_config).
CAUSE: The session_locale setting in the sessionconfig does not match any of the dd_locales values that are specified in the dm_docbase_config object. As a result, any language sensitive information that may be affected by the ALTER/CREATE is ambiguous.
ACTION: To remedy this problem, the session_locale setting in the sessionconfig object should be changed to a valid dd_locales (dm_docbase_config) value. If you want to add a new locale to the Data Dictionary, you can modify the dd_locales parameter in the dm_docbase_config object. However, the user should be careful and ensure that they actually want to add another language to the Data Dictionary before modifying the dd_locales attribute.
PARAMS:

ERROR: [DM_QUERY2_E_NOT_LITETYPE]

SEVERITY: ERROR
DESCRIPTION: S %s is not a lightweight type.
CAUSE:
ACTION:
PARAMS:

ERROR: [DM_QUERY2_E_NON_ACL]

SEVERITY: ERROR
DESCRIPTION: Non-ACL Permissions are no longer supported.
CAUSE: ACL permissions are the only permissions system supported. ACTUON: Convert your docbase to ACL permissions.
ACTION:
PARAMS:

ERROR: [DM_QUERY2_E_INVALID_TYPE_CORRELATION_FOR_ASPECT_ATTR]

SEVERITY: ERROR
DESCRIPTION: S Invalid type or correlation qualifier specified for aspect attribute %s
CAUSE: An invalid type or correlation was specified for an aspect attribute in the select list or where clause of a query. The type name or the correlation is not found in the from clause of the statement.
ACTION: Specify a valid type name or correlation for the aspect attribute.
PARAMS:

ERROR: [DM_QUERY2_E_PARTITION_API_INVALID_ARG]

SEVERITY: ERROR
DESCRIPTION: You specified arguments incorrectly for the GENERATE_PARTITION_SCHEME_SQL apply method.
CAUSE: You did not specify a value for PARTITION or RANGE repeating arguments. Or the number of values you have specified for PARTITION and RANGE arguments do not match.
ACTION: correct the command you issued.
PARAMS:

ERROR: [DM_QUERY2_E_SAVE_AGGR_DOMAIN_FAILED]

SEVERITY: ERROR
DESCRIPTION: S Save of type/attribute modifiers failed for type %s.
CAUSE: One or more type/attribute modifiers contained errors. See these error messages for details.
ACTION: Correct the individual errors and try again.
PARAMS: The parameter is the name of the type.

ERROR: [DM_QUERY2_E_DD_DO_NOT_HAVE_READ_PERMISSION]

SEVERITY: ERROR
DESCRIPTION: SS You do not have permission to read the sysobject with the path %s and version %s.
CAUSE: The user does not have permission to read the sysobject specified by the given path and version.
ACTION: The user has to obtain permission to at least read the sysobject.
PARAMS: The first parameter is the path of the sysobject, which consists of the folder path and object name The second parameter is the version of the sysobject.

ERROR: [DM_QUERY2_E_REPEAT_TYPE_JOIN]

SEVERITY: ERROR
DESCRIPTION: Your query is selecting repeating attributes and joining types.
CAUSE: It is a restriction that when you join multiple types together, you may not also select repeating attributes in the select list.
ACTION: Reformulate your query without the repeating attributes, or without the type join.
PARAMS:

ERROR: [DM_QUERY2_E_TABLE_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: S The database table or view was not found in the database. Error from the database was: %s
CAUSE: The table or view specified in the query does not exist in the database.
ACTION: Correct the name of the table in the database and reissue the query.
PARAMS: The first parameter is the error message from the database.

ERROR: [DM_QUERY2_E_ALTER_ASPECT_INVALID_TYPE_OBJECT]

SEVERITY: ERROR
DESCRIPTION: SS The internal type (%s) referenced by aspect (%s) for aspect attributes is invalid
CAUSE: The internal dm_type object referenced by the specified aspect for which the alter aspect statement was executed is invalid. The type does not exist in the repository.
ACTION: Set the i_attr_def attribute of the dmc_aspect_type object with the reported aspect name to an empty string and retry the alter aspect statement.
PARAMS:

ERROR: [DM_QUERY2_E_INCONSISTENT_UNION]

SEVERITY: ERROR
DESCRIPTION: SS Incompatible select list items (%s) and (%s) have been specified in the union clauses.
CAUSE: You have specified incompatible select list items (e.g. lightweight repeating attributes, etc.) in a union.
ACTION: If you have select list items that require post processing in a union, you should have the same item in every union clause.
PARAMS: The incompatible select list items.

ERROR: [DM_QUERY2_E_BAD_UPDATE_VALUE_IN_MODIFIER]

SEVERITY: ERROR
DESCRIPTION: Only literals are allowed in the update form of a type/attribute modifier.
CAUSE: A value was specified that was not a literal for an update modifier.
ACTION: Change the update to use a literal.
PARAMS: None.

ERROR: [DM_QUERY2_E_BAD_DEFAULT_FOR_NON_REPEATING]

SEVERITY: ERROR
DESCRIPTION: SS Attribute %s of type %s is not repeating, so the single value form of the DEFAULT value clause must be used.
CAUSE: The list form of the DEFAULT value was used where the single value form is required.
ACTION: Use a single DEFAULT value.
PARAMS: The first parameter is the name of the attribute. The second parameter is the name of the type.

ERROR: [DM_QUERY2_E_NQA_IN_WHERE_CLAUSE]

SEVERITY: ERROR
DESCRIPTION: S You cannot specify nonqualifiable attributes (%s) in where, order by and group by clause.
CAUSE: This is the unsearchable aspect of nonqualifiable attributes.
ACTION: revise the query, dont put nonqualifiable arribute in where clause.
PARAMS:

ERROR: [DM_QUERY2_E_DUPLICATE_MAPPING_TABLE]

SEVERITY: ERROR
DESCRIPTION: Duplicate MAPPING TABLE clause.
CAUSE: A duplicate MAPPING TABLE clause was found.
ACTION: Remove the duplicate clause.
PARAMS: None.

ERROR: [DM_QUERY2_E_NO_FOREIGN_KEY]

SEVERITY: ERROR
DESCRIPTION: No foreign key matching the one specified exists to DROP.
CAUSE: An attempt was made to drop a foreign key that does not exist.
ACTION: Verify that the type or attribute you specified has a foreign key with the combination of key attributes that you specified. Keep in mind that the child type, child attributes, parent type, and parent attributes must all match.
PARAMS: None.

ERROR: [DM_QUERY2_E_CHANGE_ATTRIBUTE_LENGTH_FOR_POLICY_OVERRIDE]

SEVERITY: ERROR
DESCRIPTION: S You cannot modify the length of an attribute (%s) for a business policy state.
CAUSE: A MODIFY attribute length clause was specified in an ALTER TYPE statement for a business policy state.
ACTION: Remove the MODIFY attribute length clause.
PARAMS: None.

ERROR: [DM_QUERY2_E_BAD_VA_FOR_QRY_ATTR]

SEVERITY: ERROR
DESCRIPTION: The QRY ATTR clause can only be specified for QRY value assistance.
CAUSE: The QRY ATTR clause was specified for value assistance that is not QRY.
ACTION: Only use the QRY ATTR clause for QRY value assistance.
PARAMS: None.

ERROR: [DM_QUERY2_E_OP_DISALLOW_DATATYPE]

SEVERITY: ERROR
DESCRIPTION: SS Operation %s does not support datatype %s PARAMETER: Operation name & datatype name
CAUSE: You have tries to apply an operation to an disallowed datatype.
ACTION: You must apply the operation to allowed datatype.
PARAMS:

ERROR: [DM_QUERY2_E_OWNERNAME_QUAL]

SEVERITY: ERROR
DESCRIPTION: S You have qualified a typename or correlation (%s) name with an ownername qualifier.
CAUSE: Only a tablename may be qualified with an ownername.
ACTION: Correct the query and retry.
PARAMS:

ERROR: [DM_QUERY2_E_DEFAULT_GROUP_FOR_POLICY_OVERRIDE]

SEVERITY: ERROR
DESCRIPTION: You cannot specify a DEFAULT GROUP clause for a business policy state.
CAUSE: A DEFAULT GROUP clause was specified in an ALTER TYPE statement for a business policy state.
ACTION: Remove the DEFAULT GROUP clause.
PARAMS: None.

ERROR: [DM_QUERY2_E_INVALID_ASPECT_ATTRIBUTE]

SEVERITY: ERROR
DESCRIPTION: SS Aspect (%s) does not have a attribute named (%s)
CAUSE: An aspect attribute referenced in the select list or where clause of a DQL statement is invalid.
ACTION: Specify a valid aspect attribute in the statement or add the attribute to the aspect first.
PARAMS:

ERROR: [DM_QUERY2_E_ILLEGAL_ATTR_LEVEL_UNIQUE_KEY]

SEVERITY: ERROR
DESCRIPTION: SS The unique key specified at the attribute level for attribute %s references another attribute (%s).
CAUSE: You have attempted to define a unique key at the attribute level involving another attribute.
ACTION: Move this unique key specification to the type level.
PARAMS: The first parameter is the name of the attribute on which the unique key is defined. The second parameter is the name of the offending attribute.

ERROR: [DM_QUERY2_E_ALTER_BAD_POLICY_ID]

SEVERITY: ERROR
DESCRIPTION: S The business policy id (%s) specified in ALTER TYPE is not valid.
CAUSE: The object id specified in the FOR POLICY clause of ALTER TYPE is not valid.
ACTION: Use a valid business policy object id.
PARAMS: The parameter is the business policy object id specified.

ERROR: [DM_QUERY2_E_ALTER_ASPECT_MISSING_ATTRIBUTE]

SEVERITY: ERROR
DESCRIPTION: SS Type (%s) does not have the attribute (%s)
CAUSE: An expected attribute of the specified type is not defined in that type.
ACTION: This is a server intrinsic type and is created/altered by a script that runs during server configuration or upgrade. Check if there was any failure while configuring the repository and address them.
PARAMS:

ERROR: [DM_QUERY2_E_QUERY_VA_ATTR_NOT_FOUND]

SEVERITY: ERROR
DESCRIPTION: SS The query attribute from QRY value assistance (%s) does not exist in type %s.
CAUSE: The result attribute for QRY value assistance does not exist in the named type.
ACTION: Use a legal attribute name from the type.
PARAMS: The first parameter is the result attribute for QRY value assistance. The second parameter is the name of the type.

ERROR: [DM_QUERY2_E_CREATE_ALTER_TYPE_FAILURE]

SEVERITY: ERROR
DESCRIPTION: SS An error was encountered during a CREATE/ALTER statement for type %s. Failed query was: %s
CAUSE: The CREATE/ALTER type statement failed
ACTION: Additional error messages should be reported that indicate the cause of the error.
PARAMS: The first parameter is the name of the type. The second parameter is the query that failed.

ERROR: [DM_QUERY2_E_TYPE_NOT_ASPECTS_ENABLED]

SEVERITY: ERROR
DESCRIPTION: SS Type (%s) specified in the from clause is not enabled for aspects. Cannot reference aspect attribute(s) in the %s of the query
CAUSE: An aspect attribute was specified in the select list or where clause of the query. But the type specified in the from clause of the query is not aspects enabled.
ACTION: Cannot specify aspect attributes in the query if the type referenced in the from clause is not enabled for aspects.
PARAMS:

ERROR: [DM_QUERY2_E_BAD_UPDATE_WITH_NULL]

SEVERITY: ERROR
DESCRIPTION: NULL cannot be used with APPEND, INSERT, REMOVE, or TRUNCATE.
CAUSE: The value specified for APPEND, INSERT, REMOVE, or TRUNCATE was the keyword NULL.
ACTION: Remove the keyword NULL, or use SET.
PARAMS: None.

ERROR: [DM_QUERY2_E_AMBIGUOUS_ASPECT_ATTR_USAGE]

SEVERITY: ERROR
DESCRIPTION: SS Query has multiple types in the from clause. Could not resolve ambiguity of association of the aspect attribute %s in the %s of the query
CAUSE: A query contained multiple types in the from clause and an aspect attribute is specified in the select list or where clause of the query. Because of multiple types in the from clause, server cannot resolve to which type the aspect attributes are to be associated.
ACTION: Qualify the aspect attribute in the form of typename.aspect_name.attr_name
PARAMS:

ERROR: [DM_QUERY2_E_DUPLICATE_DROP_NOT_NULL]

SEVERITY: ERROR
DESCRIPTION: Duplicate DROP NOT NULL clause.
CAUSE: A duplicate DROP NOT NULL clause was found.
ACTION: Remove the duplicate clause.
PARAMS: None.

ERROR: [DM_QUERY2_E_DD_NOT_YET_SUPPORTED_ATTR_A_C]

SEVERITY: ERROR
DESCRIPTION: SSS ALTER/CREATE for type %s, attribute %s: Feature (%s) is not yet supported in Documentum 4i Server.
CAUSE: You have attempted an operation on a type that requires Data Dictionary support that has not yet been added to Documentum 4i Server.
ACTION: Remove the indicated construct until it is supported.
PARAMS: The first parameter is the type name. The second parameter is the attribute name. The third parameter describes the un-implemented feature.

ERROR: [DM_QUERY2_E_ALREADY_LIGHTWEIGHT]

SEVERITY: ERROR
DESCRIPTION: S Type (%s) is already a lightweight type.
CAUSE: You attempted to alter a lightweight type to lightweight.
ACTION: Specify a currently non-lightweight type. The type must be dm_sysobject or a dm_sysobject subtype. PARAMETER: None
PARAMS:

ERROR: [DM_QUERY2_E_NULL_BUSINESS_POLICY_ID]

SEVERITY: ERROR
DESCRIPTION: The object id specified for the DEFAULT BUSINESS POLICY is NULL.
CAUSE: The object id specified for the DEFAULT BUSINESS POLICY is the null object id.
ACTION: Specify a valid object id, or use one of the keywords NULL or NONE.
PARAMS: None.

ERROR: [DM_QUERY2_E_CANNOT_PARTITION]

SEVERITY: ERROR
DESCRIPTION: You need to run the data partitioning script generated by the GENERATE_PARTITION_SCHEME_SQL apply method against the database server before you can enable partitioning for any type.
CAUSE: You have attempted to use alter type to set a type partitionable without properly upgrading your docbase using the GENERATE_PARTITION_SCHEME_SQL apply method and the script it generates.
ACTION: Issue the GENERATE_PARTITION_SCHEME_SQL apply method against your docbase and then run the script the apply method generates against your database server.
PARAMS:

ERROR: [DM_QUERY2_E_BAD_VA_FOR_ALLOW_CACHING]

SEVERITY: ERROR
DESCRIPTION: The ALLOW CACHING clause can only be specified for QRY value assistance.
CAUSE: The ALLOW CACHING clause was specified for value assistance that is not QRY.
ACTION: Only use the ALLOW CACHING clause for QRY value assistance.
PARAMS: None.

ERROR: [DM_QUERY2_E_ALTER_TYPE_LIGHTWEIGHT_ONLY]

SEVERITY: ERROR
DESCRIPTION: SS The ALTER TYPE clause, %s, can not be applied to type, %s, because it is not a lightweight type
CAUSE: Use specified an ALTER TYPE option which only applies to lightweight types.
ACTION: Correct the DQL ALTER TYPE syntax to supply a lightweight type.
PARAMS: The first parameter is the ALTER TYPE option and the second one is the type name.

ERROR: [DM_QUERY2_W_ATTRS_NOT_ALTERED_FTINDEX]

SEVERITY: WARNING
DESCRIPTION: S String-valued attributes are not marked for fulltext indexing because index objects of type %s already exist. Please see the documentation for more information.
CAUSE: An attempt was made to mark string-valued attributes for indexing after indexed objects of the type already exist.
ACTION: Since this happened during the alter type add operation, this warning notifies that the attributes are not automatically marked for fulltext indexing. Please see the Server Reference Manual for more information.
PARAMS: The type name.

ERROR: [DM_QUERY2_W_CONVERSION_ERROR]

SEVERITY: WARNING
DESCRIPTION: S Conversion error message from the query plug-in: %s
CAUSE: Query plug-in fails to translate the DQL to Search Engines query.
ACTION: None. Content Server will execute the DQL constraint via DB.
PARAMS:

ERROR: [DM_QUERY2_W_DATA_DICTIONARY_PUBLISH_FAILURE_A_C]

SEVERITY: WARNING
DESCRIPTION: S ALTER/CREATE for type %s: The Data Dictionary encountered a failure while trying to publish Data Dictionary information. The ALTER/CREATE has succeeded, but the user should manually try to publish the Data Dictionary information for this type using the publish_dd API. More detailed error messages should follow.
CAUSE: While processing an ALTER/CREATE statement the explicit publish that was requested encountered an error. The ALTER/CREATE succeeded, however, Data Dictionary information was not published. Additional error messages should accompany this warning with more specific details regarding the cause of the error.
ACTION: The user must manually publish the Data Dictionary information by using the publish_dd API. Otherwise, if the Data Dictionary Publisher Job is active, that should take care of publishing the Data Dictionary changes.
PARAMS: The first parameter is the name of the type involved

ERROR: [DM_QUERY2_W_NO_PRIMARY_KEY]

SEVERITY: WARNING
DESCRIPTION: No primary key exists to DROP. DROP clause ignored.
CAUSE: An attempt was made to drop a primary key that does not exist.
ACTION: Verify that the type or attribute you specified has a primary key. This is merely a warning. The DROP clause was ignored.
PARAMS: None.

ERROR: [DM_QUERY2_W_DROP_TYPE_CANNOT_FETCH_AGGR_DOMAIN]

SEVERITY: WARNING
DESCRIPTION: DS Cannot fetch the dm_aggr_domain object with ID %s while dropping type %s. Proceeding with drop type operation.
CAUSE: The type referenced a dm_aggr_domain object that does not exist.
ACTION: No action necessary since the type is being dropped.
PARAMS: The first parameter is the object id of the dm_aggr_domain object. The second parameter is the name of the type being dropped.

ERROR: [DM_QUERY2_W_NO_FOREIGN_KEY]

SEVERITY: WARNING
DESCRIPTION: No foreign key matching the one specified exists to DROP. DROP clause ignored.
CAUSE: An attempt was made to drop a foreign key that does not exist.
ACTION: Verify that the type or attribute you specified has a foreign key with the combination of key attributes that you specified. Keep in mind that the child type, child attributes, parent type, and parent attributes must all match. This is merely a warning. The DROP clause was ignored.
PARAMS: None.

ERROR: [DM_QUERY2_W_NO_UNIQUE_KEY]

SEVERITY: WARNING
DESCRIPTION: No unique key matching the one specified exists to DROP. DROP clause ignored.
CAUSE: An attempt was made to drop a unique key that does not exist.
ACTION: Verify that the type or attribute you specified has a unique key with the combination of key attributes that you specified. This is merely a warning. The DROP clause was ignored.
PARAMS: None.

nahoru

DM_RECOVERY

ERROR: [DM_RECOVERY_F_NO_CONNECTION]

SEVERITY: FATAL
DESCRIPTION: Unable to get a database connection to create a recovery object.
CAUSE: Probable database connectivity or resource problem.
ACTION: Check system logs.
PARAMS:

ERROR: [DM_RECOVERY_F_REG_TOOMANY]

SEVERITY: FATAL
DESCRIPTION: Too many recovery procedures have been registered.
CAUSE: There is an internal maximum size for the table of registered recovery procedures.
ACTION: Increase the size of the internal table (TABLE_SIZE_LIMIT in dmrecov.cxx).
PARAMS:

ERROR: [DM_RECOVERY_F_SAVE_FAILED]

SEVERITY: FATAL
DESCRIPTION: Unable to save recovery object.
CAUSE: Probable database connectivity or resource problem.
ACTION: Check system logs.
PARAMS:

ERROR: [DM_RECOVERY_F_CANT_COMMIT]

SEVERITY: FATAL
DESCRIPTION: Unable to commit save of recovery object.
CAUSE: Probable database connectivity or resource problem.
ACTION: Check system logs.
PARAMS:

ERROR: [DM_RECOVERY_F_CANT_DESTROY]

SEVERITY: FATAL
DESCRIPTION: S Unable to desrtoy recovery object %s.
CAUSE: Probable database connectivity or resource problem.
ACTION: Check system logs. $Id: dmrelate.e,v 5.4 2000/09/19 19:40:01 yasoja Exp $ dmrelation class errors
PARAMS:

ERROR: [DM_RECOVERY_F_REG_DUPDEFN]

SEVERITY: FATAL
DESCRIPTION: S The function (%s) has already been registered as a recovery procedure.
CAUSE: This function is already registered.
ACTION: Find out where it is registered, and decide which registration is valid.
PARAMS:

ERROR: [DM_RECOVERY_F_NOT_FOUND]

SEVERITY: FATAL
DESCRIPTION: A recovery procedure was requested but not found in the table.
CAUSE: The function was never registered.
ACTION: Find out where it ought to be registered, and register it.
PARAMS:

ERROR: [DM_RECOVERY_E_ARG_WRONG_TYPE]

SEVERITY: ERROR
DESCRIPTION: The parameter to RUN_RECOVERY_PROCS was not a recovery object.
CAUSE: For the RUN_RECOVERY_PROCS apply method, a parameter was supplied that was not of the required type.
ACTION: Supply a parameter that is a recovery object, or supply NULL, and all recovery objects will be run.
PARAMS:

ERROR: [DM_RECOVERY_E_NOT_SYS_ADMIN]

SEVERITY: ERROR
DESCRIPTION: Only the system administrator may run recovery procedures.
CAUSE: Someone other than the system administrator attempted to use the RUN_RECOVERY_PROCS apply method.
ACTION: Run the method as system administrator.
PARAMS:

ERROR: [DM_RECOVERY_E_BAD_ARG]

SEVERITY: ERROR
DESCRIPTION: The parameter to RUN_RECOVERY_PROCS was bad, may have been deleted.
CAUSE: For the RUN_RECOVERY_PROCS apply method, a parameter was supplied that was not fetchable or bad.
ACTION: The parameter may have been deleted or mistyped. Make sure it exists, then try again.
PARAMS:

nahoru

DM_RELATION

ERROR: [DM_RELATION_F_INIT3]

SEVERITY: FATAL
DESCRIPTION: The type manager returned an error storing the dmRelation 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_RELATION_F_INIT1]

SEVERITY: FATAL
DESCRIPTION: The dmRelation 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_RELATION_F_TYPE_CONVERSION]

SEVERITY: FATAL
DESCRIPTION: I Failed to convert type dm_relation_type to version %d.
CAUSE: Type conversion failed.
ACTION: Look at the error logged by the type manager. Report this message and any parameters to your Documentum site representative.
PARAMS:

ERROR: [DM_RELATION_F_INIT2]

SEVERITY: FATAL
DESCRIPTION: II Version stamp %d was expected to be %d.
CAUSE: The version stamp that the dmRelation 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_RELATION_F_RELATION_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. $Id: dmrelatp.e,v 5.0 1998/01/10 02:08:10 sol_ora Exp $ dmrelation_type class errors
PARAMS:

ERROR: [DM_RELATION_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_RELATION_E_INCR_LENGTH_FAILED]

SEVERITY: ERROR
DESCRIPTION: L While upgrading to version %d: The upgrade failed on widening dm_relations attribute lengths.
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_RELATION_E_INCR_LENGTH_NONEXISTANT_ATTR]

SEVERITY: ERROR
DESCRIPTION: L While upgrading to version %d: Failed while trying to increase the length of a non-existant attribute in dm_relation.
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_RELATION_E_INCR_LENGTH_TOO_LONG]

SEVERITY: ERROR
DESCRIPTION: L While upgrading to version %d: Failed when trying to increase the length of a dm_relation attribute because the attribute is 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_RELATION_E_NEED_PRIV]

SEVERITY: ERROR
DESCRIPTION: SS The current user %s has insufficient privileges to save or destroy %s relation.
CAUSE: A user with insufficient privileges tried to save or destroy a relation object.
ACTION: See your sysadmin.
PARAMS:

ERROR: [DM_RELATION_E_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_RELATION_E_CANNOT_CREATE_RELATION_FOR_FOREIGN_KEY]

SEVERITY: ERROR
DESCRIPTION: S You cannot create an explicit dm_relation object for a dm_foreign_key relation type (%s).
CAUSE: You cannot create dm_relation objects using the dm_foreign_key subtype of dm_relation_type.
ACTION:
PARAMS:

ERROR: [DM_RELATION_E_CANT_SAVE]

SEVERITY: ERROR
DESCRIPTION: S Could not save the %s relation object.
CAUSE: Previous errors have caused the save to abort.
ACTION: Remedy the previous problem before retrying.
PARAMS:

ERROR: [DM_RELATION_E_CANT_DESTROY]

SEVERITY: ERROR
DESCRIPTION: SI Cannot destroy relation objects for %s object %d.
CAUSE: DocuServer could not destroy relation objects.
ACTION: See the followings messages for more detail.
PARAMS:

ERROR: [DM_RELATION_E_CANT_CASCADE_DESTROY_OBJECT]

SEVERITY: ERROR
DESCRIPTION: SS Cannot cascade delete related object %s for object %s.
CAUSE: DocuServer could not cascade-destroy relation objects.
ACTION: Objects specified to be cascade-deleted may need to be manually removed.
PARAMS:

ERROR: [DM_RELATION_E_NO_RELATE_PERMIT]

SEVERITY: ERROR
DESCRIPTION: SSS No relate permit for relation %s since %s %s is protected.
CAUSE: No relate permit because the security sysobject says so.
ACTION:
PARAMS:

ERROR: [DM_RELATION_E_TYPE_FETCH_FAILED]

SEVERITY: ERROR
DESCRIPTION: S Failed to fetch type (%s)
CAUSE: Failed to fetch a type object during a relation operation.
ACTION: Try again. This is likely due to a temporary database issue.
PARAMS:

ERROR: [DM_RELATION_E_BAD_LABEL]

SEVERITY: ERROR
DESCRIPTION: SD Non-existent %s child_label associated %s child of with relation.
CAUSE: Invalid child_label specified with the relation definition.
ACTION: Try again with an valid version_label in the specified child object.
PARAMS:

ERROR: [DM_RELATION_E_INVALID_NAME]

SEVERITY: ERROR
DESCRIPTION: S Invalid relation_name = %s, Must be a valid dm_relation_type name.
CAUSE: A user specified an invalid relation_name.
ACTION: Try again with a valid dm_relation_type name.
PARAMS:

Konec třetí části…

Michal Šika

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

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