6.6-dm_ft_index

DM_FT_INDEX


ERROR: [DM_FT_INDEX_F_UPDATE_R_IS_PUBLIC_FAILED]

SEVERITY: FATAL

DESCRIPTION: S Fulltext index sysobject upgrade failed on the type %s when updating r_is_public field.

CAUSE: Probable RDBMS failure.

ACTION: Examine system logs and try again.

PARAMS:

 

ERROR: [DM_FT_INDEX_F_UPGRADE_400_TYPE_DESTROY_FAILED]

SEVERITY: FATAL

DESCRIPTION: S The %s type could not be destroyed during upgrade.

CAUSE: Internal failure.

ACTION: Initially, disregard this error. It may cause no problem. If other problems show up, report this as well the others to your Documentum Site Representative.

PARAMS:

 

ERROR: [DM_FT_INDEX_F_UPGRADE_SYSOBJECT_400_PART2_FAILED]

SEVERITY: FATAL

DESCRIPTION: Part 2 of fulltext index sysobject upgrade failed

CAUSE: Probable RDBMS failure.

ACTION: Examine system logs and try again.

PARAMS:

 

ERROR: [DM_FT_INDEX_F_UPGRADE53_REMOVE_INDEX_OBJECT_FAILED]

SEVERITY: FATAL

DESCRIPTION: S Unable to expunge dm_fulltext_index object with id %s

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_F_UPGRADE_SYSOBJECT_400_PART1_FAILED]

SEVERITY: FATAL

DESCRIPTION: S Fulltext index sysobject upgrade failed on the type %s.

CAUSE: Probable RDBMS failure.

ACTION: Examine system logs and try again.

PARAMS:

 

ERROR: [DM_FT_INDEX_F_UPGRADE53_UNABLE_TO_GET_TEMP_CONNECTION]

SEVERITY: FATAL

DESCRIPTION: Unable to get temporary connection to the database to perform upgrade operations

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_F_UPGRADE53_UNABLE_TO_DROP_OBSOLETE_ATTRIBUTE]

SEVERITY: FATAL

DESCRIPTION: S Unable to drop attribute %s from dm_fulltext_index type

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_F_UPGRADE53_UNABLE_TO_ADD_ATTRIBUTE]

SEVERITY: FATAL

DESCRIPTION: S Unable to add attribute %s to the dm_fulltext_index type

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_F_UPGRADE53_BEGIN_TRANS_FAILED]

SEVERITY: FATAL

DESCRIPTION: Unable to begin transaction for upgrading fulltext types

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_F_UPGRADE53_COMMIT_TRANS_FAILED]

SEVERITY: FATAL

DESCRIPTION: Unable to commit the operations for fulltext upgrade

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_F_FULLTEXT_ENGINE_INIT_ERROR]

SEVERITY: FATAL

DESCRIPTION: S Query Plugin failed to successfully initialize: %s

CAUSE: The query plugin could not initialize its communication with the Index Server.

ACTION: The argument of the error message will indicate exact nature of the problem e.g. Index Server not reachable, mis-configured dm_ftengine_config object values etc. FullText Facility errors ** Documentum DocuServer ** Confidential Property of Documentum, Inc. ** (c) Copyright Documentum, Inc., 1993 ** All rights reserved. **

PARAMS:

 

ERROR: [DM_FT_INDEX_E_SAMPLE_OBJ_NOT_FOUND]

SEVERITY: ERROR

DESCRIPTION: S The sample object %s was not found in the docbase.

CAUSE: Sample object missing or bad.

ACTION: Choose a sample object that is marked for full-text and currently indexed and has a unique name.

PARAMS:

 

ERROR: [DM_FT_INDEX_E_NOT_SYS_ADMIN]

SEVERITY: ERROR

DESCRIPTION: S Cant perform operation %s on fulltext indices — not sys admin

CAUSE: The operation could not be performed because the user had insufficient privileges

ACTION: None.

PARAMS: The operation name

 

ERROR: [DM_FT_INDEX_E_NO_FULLTEXT_PLUGIN_LOADED]

SEVERITY: ERROR

DESCRIPTION: S The fulltext query plugin did not initialize with the fulltext search engine %s specified in the server config object. Please ensure that the search engine is functioning and is configured correctly.

CAUSE: This error occurs if the fulltext_location attribute in the server config does not refer to a valid fulltext search engine or if the search engine is incorrectly configured or not functioning.

ACTION: Set fulltext_location attribute of the server config object to a valid fulltext install location. Verify that valid fulltext installations are listed in the fulltext_install_locs attribute of the docbase config object. Verify that the fulltext search engine is functioning and correctly configured.

PARAMS:

 

ERROR: [DM_FT_INDEX_E_VERITY_LOC_CHANGED]

SEVERITY: ERROR

DESCRIPTION: SSS Not able to %s the fulltext index. The verity_location value of the server config (%s) does not match the install location of the fulltext library currently loaded (%s) in the server.

CAUSE: Performing this fulltext operation is not allowed when the install location of the currently loaded fulltext library does not match the verity_location of the server config.

ACTION: Restart the Content Server to load the fulltext library defined by the verity_location of the server config.

PARAMS: The index operation, the verity_location value, and the install location of the currently loaded fulltext implementation.

 

ERROR: [DM_FT_INDEX_E_CANNOT_USE_MAX_DOCS]

SEVERITY: ERROR

DESCRIPTION: Cannot run update_ftindex with date_cutoff and max_docs both specified.

CAUSE: Tried to run update_ftindex with date_cutoff and max_docs both specified.

ACTION: Retry update_ftindex with only one out of the two specified.

PARAMS:

 

ERROR: [DM_FT_INDEX_E_NOT_STANDBY]

SEVERITY: ERROR

DESCRIPTION: SS Operation %s requires a standby index. Index %s is not standby

CAUSE: Index named must be a standby index.

ACTION: Use a different index.

PARAMS: The name of the operation and the name of the index.

 

ERROR: [DM_FT_INDEX_E_BAD_LOCALE_SPECIFIED]

SEVERITY: ERROR

DESCRIPTION: SS The %s locale specified was not found in the fulltext configuration pointed by the %s fulltext install location. Please specify a valid locale. (Valid locales are identified in the dmfulltext.ini file, located $DOCUMENTUM/verity/ directory.

CAUSE: The locale specified is not supported by the fulltext configuration used by the index you are creating.

ACTION: Specify a locale recognized by this fulltext configuration.

PARAMS: The specified locale and fulltext install location

 

ERROR: [DM_FT_INDEX_E_CANT_UPDATE_SHADOW]

SEVERITY: ERROR

DESCRIPTION: S Cannot perform index update on shadow index %s

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_E_COLLECTION_NOT_FOUND]

SEVERITY: ERROR

DESCRIPTION: Couldnt find the collection for the sample object specified.

CAUSE: Possible internal error, or bad sample object.

ACTION: Check that this object is of an indexable type and format.

PARAMS:

 

ERROR: [DM_FT_INDEX_E_STYLE_BACKUP_NOT_FOUND]

SEVERITY: ERROR

DESCRIPTION: S Couldnt find the backup for the %s.

CAUSE: Probable operating system error or filesystem or disk problem.

ACTION: Check for OS error messages.

PARAMS:

 

ERROR: [DM_FT_INDEX_E_INDEX_CLOSED]

SEVERITY: ERROR

DESCRIPTION: S Cant rollover index %s — its already closed

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_E_CANT_COMMIT_TRANSACTION]

SEVERITY: ERROR

DESCRIPTION: SS Could not commit transaction for %s operation on fulltext index %s

CAUSE: The operation required a transaction which could not be committed

ACTION: None.

PARAMS: The operation name and the name of the fulltext index

 

ERROR: [DM_FT_INDEX_E_NO_FULLTEXT_CONFIG_FOUND]

SEVERITY: ERROR

DESCRIPTION: S A fulltext configuration was not found for the specified %s install location. Please specify a valid fulltext install location. (Valid install locations are defined in the fulltext_install_locs attribute of the docbase config object.)

CAUSE: An invalid install location not recognized by this server was specified, or the install loc refers to a location that wasnt successfully loaded by the server.

ACTION: Specify a valid install location on the next attempt

PARAMS: The specified fulltext install location.

 

ERROR: [DM_FT_INDEX_E_INVALID_OPTIMIZATION_FLAG]

SEVERITY: ERROR

DESCRIPTION: S The %s optimization flag is not valid.

CAUSE: The CLEAN_FTINDEX method aborted because an invalid flag was specified in the FLAGS argument.

ACTION: Make sure all optimization flags specified are valid and rerun the CLEAN_FTINDEX method. Multiple flags should be separated by hyphens.

PARAMS: The invalid optimization flag

 

ERROR: [DM_FT_INDEX_E_CANT_MAKE]

SEVERITY: ERROR

DESCRIPTION: SS Cant make index with name %s for storage of type %s

CAUSE: Fulltext indices cannot be created for the storage object

ACTION: None.

PARAMS: The name of the fulltext index and the name of the storage type

 

ERROR: [DM_FT_INDEX_E_BAD_INDEX_TYPE_SPECIFIED]

SEVERITY: ERROR

DESCRIPTION: II The specified index_type %d does not match the index_type of the fulltext configuration used by this index. Set the index_type to %d to match the fulltext configuration used.

CAUSE: The index_type specified does not match the index_type found in the fulltext configuration.

ACTION: Either do not explicitly specify an index_type or specify an index_type that matches the fulltext configuration used.

PARAMS: The specified index_type and the index_type of the fulltext configuration.

 

ERROR: [DM_FT_INDEX_E_UNABLE_TO_GENERATE_LOGIN_TICKET]

SEVERITY: ERROR

DESCRIPTION: S Unable to generate a login ticket to start Index Agent %s

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_E_NO_FULLTEXT_CONFIG_FOR_INDEX]

SEVERITY: ERROR

DESCRIPTION: SS Not able to %s the fulltext index. There is no fulltext configuration loaded for this fulltext indexs %s install_loc.

CAUSE: Performing this fulltext operation is not allowed when no fulltext configuration has been loaded corresponding to the install_loc of the fulltext index.

ACTION: Check the docbase config object to see if the fulltext_install_locs attribute contains the install_loc of the fulltext index. If so, reinit the server. If not, please add the install_loc into the docbase config and reinit the server.

PARAMS: The index operation, the install location of the fulltext index

 

ERROR: [DM_FT_INDEX_E_NO_FULLTEXT_IMPLEMENTATION_LOADED2]

SEVERITY: ERROR

DESCRIPTION: A fulltext library was not identified in the server config object. Please identify a valid fulltext installation in the fulltext_location attribute of the server config object.

CAUSE: This error occurs if the fulltext_location attribute in the server config is not set.

ACTION: Set fulltext_location attribute of the server config object to a valid fulltext install location. Valid fulltext installations are listed in the fulltext_install_locs attribute of the docbase config object.

PARAMS:

 

ERROR: [DM_FT_INDEX_E_NO_FULLTEXT_IMPLEMENTATION_LOADED]

SEVERITY: ERROR

DESCRIPTION: S Could not %s the fulltext index because a fulltext library is not loaded. A library was not loaded because verity_location in the server config object is not set or the fulltext plugin failed to load.

CAUSE: Content Server could not load the fulltext library because the verity_location attribute in the server config object is not set to a fulltext install location or the fulltext plugin failed to load.

ACTION: Set verity_location to a valid fulltext install location and reinit or restart the Content Server.

PARAMS: The fulltext index operation

 

ERROR: [DM_FT_INDEX_E_ILLEGAL_TIME_OUT]

SEVERITY: ERROR

DESCRIPTION: I The specified time-out interval (%d) does not make sense.

CAUSE: A time-out interval must be positive.

ACTION: Choose a positive value and retry the command.

PARAMS:

 

ERROR: [DM_FT_INDEX_E_INSTALL_LOC_NOT_VERITY_LOC]

SEVERITY: ERROR

DESCRIPTION: SS The %s fulltext install location specified does not match the verity_location of the server config: %s for a non-standby index. Non-standby indexes must use the verity_location of the server config.

CAUSE: A non-standby index must use the location defined in the verity_location of the server config. Any other value specified is not valid.

ACTION: Specify the value in the verity_location of the server config for non-standby indexes, or do not specify a value.

PARAMS: The specified install loc and the verity_location of the server config

 

ERROR: [DM_FT_INDEX_E_FAR_STORE]

SEVERITY: ERROR

DESCRIPTION: S Attempt to update fulltext index for far storage %s

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_E_QUERY_EXECUTION_FAILURE]

SEVERITY: ERROR

DESCRIPTION: SS An error occured while trying to execute the following query: %s. Database error was %s.

CAUSE: Query execution failed.

ACTION: Check the error message from the database in order to determine the cause of the query failure.

PARAMS: The first parameter is the query that was being executed. The second parameter is the resulting error from the database.

 

ERROR: [DM_FT_INDEX_E_DUPLICATE_NAME]

SEVERITY: ERROR

DESCRIPTION: SS Attempt to create new fulltext index failed — index %s already has name %s

CAUSE: Attempting to create a new fulltext index with a name that is being used by another fulltext index

ACTION: Choose a new name and retry the operation

PARAMS: The id of the existing fulltext index and the name

 

ERROR: [DM_FT_INDEX_E_STYLE_FILE_NOT_FOUND]

SEVERITY: ERROR

DESCRIPTION: S The internal copy of the %s was not found

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_E_CANT_COPY_FILE]

SEVERITY: ERROR

DESCRIPTION: SS Couldnt copy the %s at server path %s.

CAUSE: Probable operating system error or filesystem or disk problem.

ACTION: Check for OS error messages.

PARAMS:

 

ERROR: [DM_FT_INDEX_E_CANT_MODIFY_TDK_INDEX]

SEVERITY: ERROR

DESCRIPTION: There was a failure trying to modify a fulltext index object.

CAUSE: Internal error.

ACTION: Report this error to your Documentum Site Representative.

PARAMS:

 

ERROR: [DM_FT_INDEX_E_USER_STYLE_FILE_NOT_FOUND]

SEVERITY: ERROR

DESCRIPTION: SS The users %s was not found at server path %s

CAUSE: The path does not point to a file.

ACTION: Check the file name and try again.

PARAMS:

 

ERROR: [DM_FT_INDEX_E_SAMPLE_OBJ_BAD_ID]

SEVERITY: ERROR

DESCRIPTION: S The sample object %s has a bad id.

CAUSE: Sample object missing or bad.

ACTION: Choose a sample object that is marked for full-text and currently indexed and has a unique name.

PARAMS:

 

ERROR: [DM_FT_INDEX_E_INDEX_NAME_TOO_LONG]

SEVERITY: ERROR

DESCRIPTION: SI Cant create index with name %s (%d chars is max).

CAUSE: Tried to create an index with a name too long.

ACTION: Retry with a shorter name.

PARAMS: The name that was too long and the maximum size.

 

ERROR: [DM_FT_INDEX_E_INVALID_FULLTEXT_ENGINE_ID]

SEVERITY: ERROR

DESCRIPTION: D %s is not a valid dm_ftengine_config object id

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_E_CANT_UPDATE_ATTRIBUTE]

SEVERITY: ERROR

DESCRIPTION: SS Attribute %s cannot be changed for dm_fulltext_index object %s

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_E_NO_STORAGE]

SEVERITY: ERROR

DESCRIPTION: SS Cannot perform operation %s — No storage is defined for fulltext index %s.

CAUSE: No storage is defined for this fulltext index object.

ACTION: Make sure that this fulltext index is associated with a storage area.

PARAMS: The name of the operation and the name of the index.

 

ERROR: [DM_FT_INDEX_E_INTERNAL_DATABASE_ERROR]

SEVERITY: ERROR

DESCRIPTION: SS A database error occured during the following operation: %s. Database error was %s.

CAUSE: Internal database error

ACTION: Check the error message from the database in order to determine the cause of the query failure.

PARAMS: The first parameter identifies the internal operation performed. The second parameter is the resulting error from the database.

 

ERROR: [DM_FT_INDEX_E_NO_LOCALE_SPECIFIED]

SEVERITY: ERROR

DESCRIPTION: Could not create the fulltext index because a locale was not specified. A locale must be specified.

CAUSE: Content Server requires you to identify the locale of a fulltext index when you create the index.

ACTION: Specify a valid locale on the next attempt to create the index. Valid locales are identified in the dmfulltext.ini file, located in $DOCUMENTUM/verity/ directory.

PARAMS:

 

ERROR: [DM_FT_INDEX_E_NO_NAME]

SEVERITY: ERROR

DESCRIPTION: Attempt to create new fulltext index without supplying a name

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_E_NO_LOCATION]

SEVERITY: ERROR

DESCRIPTION: SS Attempt to create new fulltext index with name %s failed — no location with name %s exists

CAUSE: Attempting to create a fulltext index for a storage object that doesnt exist

ACTION: Correct the problem and retry the operation

PARAMS: The name of the index and the name of the location object

 

ERROR: [DM_FT_INDEX_E_CANT_CREATE_FTINDEX_OBJECT_IN_NONSTANDBY_MODE]

SEVERITY: ERROR

DESCRIPTION: S Cannot create %s dm_fulltext_object with is_standby set to FALSE, because dm_fulltext_index object with is_standby set to FALSE already exists.

CAUSE: This error occurs when you attempt to create a dm_fulltext_index object with is_standby set to FALSE, when a dm_fulltext_index object with is_standby set to FALSE already exists in the docbase.

ACTION: You cannot have more than one dm_fulltext_index object in a docbase with is_standby set to FALSE. You can create any number of dm_fulltext_index object with is_standby set to TRUE.

PARAMS:

 

ERROR: [DM_FT_INDEX_E_SERVER_PATH_NOT_DIRECTORY]

SEVERITY: ERROR

DESCRIPTION: S The specified server_path (%s) is not a directory.

CAUSE: For topic trees, the server_path must be a directory, as created by the Verity mk_topic utility.

ACTION: Create such a directory and retry the command specifying it.

PARAMS:

 

ERROR: [DM_FT_INDEX_E_INVALID_DATE_CUTOFF]

SEVERITY: ERROR

DESCRIPTION: The specified cutoff date format is not valid or is later than the current time.

CAUSE: Tried to run update_ftindex with an invalid date format or date later than the current time.

ACTION: Retry update_ftindex with a valid date and format.

PARAMS:

 

ERROR: [DM_FT_INDEX_E_NO_INDEX_SPECIFIED]

SEVERITY: ERROR

DESCRIPTION: S Cannot perform operation %s — No index specified to search.

CAUSE: No index was specified to search.

ACTION: Rerun the operation with at least one valid index specified.

PARAMS: The name of the operation.

 

ERROR: [DM_FT_INDEX_E_STYLE_TYPE_NOT_ALLOWED]

SEVERITY: ERROR

DESCRIPTION: S The %s is not allowed

CAUSE: The style type specified was not one of the permitted ones.

ACTION: Check the Documentum manual for the list of styles, and retry the command.

PARAMS:

 

ERROR: [DM_FT_INDEX_E_UPGRADE_400_TCOLL_DESTROY_FAILED]

SEVERITY: ERROR

DESCRIPTION: S The dmi_topic_collection at %s could not be destroyed.

CAUSE: Permission problem or disk problem.

ACTION: Look for the directory listed in the error message and delete it by other means.

PARAMS:

 

ERROR: [DM_FT_INDEX_E_BAD_CONFIG]

SEVERITY: ERROR

DESCRIPTION: S Attempt to update fulltext index object failed — invalid server config name %s

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_E_NO_FILE]

SEVERITY: ERROR

DESCRIPTION: S No file was specified for %s operation

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_E_RESULTS_NOT_FILTERED]

SEVERITY: ERROR

DESCRIPTION: SS Cannot perform operation %s — The matching results were not filtered to the specified type on fulltext index %s.

CAUSE: Verity failed to return the OBJTYPE of each result matching the query.

ACTION: Verify that Verity is working properly by checking if your environment is properly set up for Verity.

PARAMS: The name of the operation and the name of the index.

 

ERROR: [DM_FT_INDEX_E_CANT_RENAME_FILE]

SEVERITY: ERROR

DESCRIPTION: S Unable to rename the %s.

CAUSE: Probable operating system error or filesystem or disk problem.

ACTION: Check for OS error messages.

PARAMS:

 

ERROR: [DM_FT_INDEX_E_CANT_DESTROY_FILE]

SEVERITY: ERROR

DESCRIPTION: S Unable to destroy the %s.

CAUSE: Probable operating system error or filesystem or disk problem.

ACTION: Check for OS error messages.

PARAMS:

 

ERROR: [DM_FT_INDEX_E_FULLTEXT_CONFIG_NOT_LOADED]

SEVERITY: ERROR

DESCRIPTION: S A fulltext configuration was not found in the file_system_path defined by the fulltext install location %s object. Please check that the location object exists, that its file system_path points to a valid fulltext installation, and that the fulltext installation contains a valid dmfulltext.ini file.

CAUSE: Loading the fulltext configuration failed and returned a bad state.

ACTION: Make sure the dmfulltext.ini file is valid and that the fulltext install location is correctly defined. Information about the dmfulltext.ini files and the location objects is found in the Content Server Administrators Guide.

PARAMS: The fulltext install location

 

ERROR: [DM_FT_INDEX_E_CANT_MODIFY]

SEVERITY: ERROR

DESCRIPTION: S Cannot modify existing fulltext index %s

CAUSE: Fulltext indices cannot be modified once created

ACTION: None.

PARAMS: The name of the fulltext index

 

ERROR: [DM_FT_INDEX_E_BAD_FULLTEXT_INSTALL_LOCATION]

SEVERITY: ERROR

DESCRIPTION: S The %s fulltext install location is not valid or not found in the fulltext install locations identified in the docbase config object.

CAUSE: An invalid fulltext location was specified.

ACTION: Set the fulltext location object to point to one of the fulltext install locations defined in the docbase config object.

PARAMS: The specified fulltext install location

 

ERROR: [DM_FT_INDEX_E_NO_FTINDEX_PLUGIN]

SEVERITY: ERROR

DESCRIPTION: Cannot find fulltext index plugin library. PARAMETER: None.

CAUSE: The error message explains all.

ACTION: EXEC_XQUERY apply method cannot be executed without this.

PARAMS:

 

ERROR: [DM_FT_INDEX_E_CLOSE_FAILED]

SEVERITY: ERROR

DESCRIPTION: S Attempt to close fulltext index %s failed

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_E_CANT_BEGIN_TRANSACTION]

SEVERITY: ERROR

DESCRIPTION: SS Could not start transaction for %s operation on fulltext index %s

CAUSE: The operation required a transaction which could not be started

ACTION: None.

PARAMS: The operation name and the name of the fulltext index

 

ERROR: [DM_FT_INDEX_E_CANT_SAVE_TDK_INDEX]

SEVERITY: ERROR

DESCRIPTION: There was a failure trying to save a fulltext index object.

CAUSE: Internal error.

ACTION: Report this error to your Documentum Site Representative.

PARAMS:

 

ERROR: [DM_FT_INDEX_E_API_BAD_ARGS]

SEVERITY: ERROR

DESCRIPTION: SS The %s method failed because of bad arguments: %s

CAUSE: An apply or execute method failed because incorrect arguments were supplied.

ACTION: Check Documentum manuals for correct arguments and retry command.

PARAMS: %s – the api or execute method name %s – the incorrect argument supplied

 

ERROR: [DM_FT_INDEX_E_UNABLE_TO_FETCH_FTENGINE_CONFIG_TYPE]

SEVERITY: ERROR

DESCRIPTION: S Unable to fetch %s type

CAUSE: This error occurs when dm_ftengine_config type is not found in the docbase. This type is created when create_fulltext_objects.ebs script is executed by the Server Configuration program.

ACTION: Check if the type was created successfully during server configuration. If not, execute the script again to get the type created.

PARAMS:

 

ERROR: [DM_FT_INDEX_E_DUPLICATE_FOR_STORE]

SEVERITY: ERROR

DESCRIPTION: SS Attempt to create new fulltext index with name %s duplicates an existing index on the same store (storage name is %s)

CAUSE: Attempting to create a new fulltext index for a storage object that already has a fulltext index defined

ACTION: None.

PARAMS: The name of the index and the name of the storage object

 

ERROR: [DM_FT_INDEX_E_NO_STORE]

SEVERITY: ERROR

DESCRIPTION: SS Attempt to create new fulltext index with name %s failed — no store with name %s exists

CAUSE: Attempting to create a fulltext index for a storage object that doesnt exist

ACTION: Correct the problem and retry the operation

PARAMS: The name of the index and the name of the storage object

 

ERROR: [DM_FT_INDEX_E_NO_FTINDEX_AGENT_CONFIG_OBJECTS_FOUND]

SEVERITY: ERROR

DESCRIPTION: There were no dm_ftindex_agent_config object(s) found for the specified arguments

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_E_CANT_OPEN_NON_TDK_INDEX]

SEVERITY: ERROR

DESCRIPTION: SI The index, %s, you tried to open is with a wrong type %d.

CAUSE: A non-TDK fulltext index is detected while constructing a fulltext object.

ACTION: Make sure the i_implementation_type of the dm_fulltext_index object has a value 2 (i.e. TDK).

PARAMS:

 

ERROR: [DM_FT_INDEX_E_UNABLE_TO_GET_ATTR_POSITION]

SEVERITY: ERROR

DESCRIPTION: SS Unable to find %s attribute in type %s

CAUSE: could not find an attribute in the specified type.

ACTION: This is an internal error. Contact Technical Support.

PARAMS:

 

ERROR: [DM_FT_INDEX_E_ILLEGAL_ARG_VALUE]

SEVERITY: ERROR

DESCRIPTION: SI The %s argument was specified with an invalid value. Value was %d.

CAUSE: The argument value specified is not valid for this method.

ACTION: Rerun the method with a valid value.

PARAMS: The name of the argument and the value specified.

 

ERROR: [DM_FT_INDEX_E_METHOD_NOT_ENABLED]

SEVERITY: ERROR

DESCRIPTION: S Cannot perform operation %s — The method is not enabled for usage. Contact your superuser for information.

CAUSE: The method is not enabled because the superuser did not set the use_estimate_search parameter to T in the server.ini file.

ACTION: If the superuser decides to enable the method, rerun the operation.

PARAMS: The name of the operation.

 

ERROR: [DM_FT_INDEX_E_NO_FULLTEXT_INDEX]

SEVERITY: ERROR

DESCRIPTION: SS Cannot perform operation %s — fulltext index %s is not defined.

CAUSE: The fulltext index object is not defined or does not exist.

ACTION: Verify that the fulltext index does exist or create a new one to associate with the storage area.

PARAMS: The name of the operation and the name of the index.

 

ERROR: [DM_FT_INDEX_E_BAD_CODEPAGE_SPECIFIED]

SEVERITY: ERROR

DESCRIPTION: SSS The %s codepage specified is not valid for the %s locale. Please specify codepage %s for this locale.

CAUSE: The codepage specified is not valid for the locale.

ACTION: Specify a codepage that is compatible with the locale.

PARAMS: The specified codepage and locale

 

ERROR: [DM_FT_INDEX_E_INTERNAL_LOGIC_ERROR]

SEVERITY: ERROR

DESCRIPTION: S An internal error occured during the following operation: %s.

CAUSE: Internal error

ACTION: Contact Tech Support.

PARAMS: The internal operation being performed.

 

ERROR: [DM_FT_INDEX_E_SAMPLE_OBJ_NO_GOOD]

SEVERITY: ERROR

DESCRIPTION: S The sample object %s specified must be unique and indexed.

CAUSE: Sample object incorrectly specified

ACTION: Choose a sample object that is marked for full-text and currently indexed and has a unique name

PARAMS:

 

ERROR: [DM_FT_INDEX_E_UNABLE_TO_FETCH_FTINDEX_AGENT_CONFIG_TYPE]

SEVERITY: ERROR

DESCRIPTION: S Unable to fetch %s type

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_E_NO_INDEX]

SEVERITY: ERROR

DESCRIPTION: S Cant perform operation %s — fulltext index not found

CAUSE: The operation could not be performed because the fulltext index did not exist

ACTION: None.

PARAMS: The operation name

 

ERROR: [DM_FT_INDEX_E_API_ARG_MISSING]

SEVERITY: ERROR

DESCRIPTION: SS The %s method failed because of the argument %s was missing

CAUSE: An apply or execute method failed because a required argument was not supplied.

ACTION: Check Documentum manuals for correct arguments and retry command.

PARAMS: %s – the api or execute method name %s – the missing argument

 

ERROR: [DM_FT_INDEX_W_UPGRADE_400_TCOLL_NOT_FOUND]

SEVERITY: WARNING

DESCRIPTION: SS The dmi_topic_collection at %s for object %s was not found.

CAUSE: This may be a second invocation of this upgrade.

ACTION: None needed.

PARAMS:

 

ERROR: [DM_FT_INDEX_W_NO_FULLTEXT_LOCS_DEFINED]

SEVERITY: WARNING

DESCRIPTION: No fulltext install locations are defined in the fulltext_install_locs attribute of the docbase config. This is expected on the first startup of a upgraded or new docbase. If this warning occurs on subsequent startups, follow the instructions in ACTION.

CAUSE: The fulltext_install_locs attribute is empty when an upgraded or new Docbase is first started because the attribute is populated by the headstart.ebs script, which runs after the startup.

ACTION: Generally no action is required if headstart.ebs runs successfully. However, if headstart.ebs does not run successfully or the attribute remains unset, set it manually to verity271 and verity451.

PARAMS:

 

ERROR: [DM_FT_INDEX_W_VERITY_LOCATION_NOT_DEFINED]

SEVERITY: WARNING

DESCRIPTION: No fulltext install location was specified in the verity location. No fulltext library will be loaded when the Content Server is rebooted.

CAUSE: The verity location was set to a blank value.

ACTION: If it is the users intent to not load a fulltext implementation when the Content Server is rebooted, then nothing needs to be done. Otherwise, please specify a valid fulltext install location.

PARAMS:

 

ERROR: [DM_FT_INDEX_W_FULLTEXT_IMPLEMENTATION_NOT_LOADED_AIX]

SEVERITY: WARNING

DESCRIPTION: A fulltext library is not loaded. Changes made to load a new fulltext library cannot take effect until Content Server is restarted.

CAUSE: An attempt was made to load a new fulltext library without restarting Content Server. This error is AIX specific.

ACTION: Restart Content Server.

PARAMS:

 

ERROR: [DM_FT_INDEX_W_FULLTEXT_SERVER_METHOD_DEPRECATED]

SEVERITY: WARNING

DESCRIPTION: S The Fulltext subsystem related Server method %s has been deprecated.

CAUSE: The fulltext subsystem related Server method has been deprecated.

ACTION: The reported server method is not required for the fulltext subsystem architecture starting Content Server version 5.3.

PARAMS:

 

ERROR: [DM_FT_INDEX_W_FULLTEXT_LOCATION_NOT_DEFINED]

SEVERITY: WARNING

DESCRIPTION: No fulltext install location was specified in the fulltext location. No fulltext library will be loaded when the Content Server is rebooted.

CAUSE: The fulltext location was set to a blank value.

ACTION: If it is the users intent to not load a fulltext implementation when the Content Server is rebooted, then nothing needs to be done. Otherwise, please specify a valid fulltext install location.

PARAMS:

 

ERROR: [DM_FT_INDEX_W_NO_FULLTEXT_LOC_DEFINED]

SEVERITY: WARNING

DESCRIPTION: No fulltext install location is defined in the install_location attribute of the server config. This is expected on the first startup of an upgraded or new docbase. If this warning occurs on subsequent startups, please ensure that a location is defined correctly.

CAUSE: The install_location attribute is empty when an upgraded or new Docbase is first started because the attribute is populated by the headstart.ebs script, which runs after the startup.

ACTION: Generally no action is required if headstart.ebs runs successfully. After ensuring that headstart.ebs ran successfully, check the server config object to verify that the install_location attribute is populated with the object_name of a valid dm_location object.

PARAMS:

 

ERROR: [DM_FT_INDEX_W_STYLE_FILE_NOT_FOUND]

SEVERITY: WARNING

DESCRIPTION: S The %s was not found

CAUSE: The style file specified was not one of the permitted ones.

ACTION: Check the Documentum manual for the list of style files, and retry the command.

PARAMS:

 

ERROR: [DM_FT_INDEX_W_UPGRADE_400_TCOLL_TYPE_NOT_FOUND]

SEVERITY: WARNING

DESCRIPTION: The dmi_topic_collection type was not found during upgrade. Skipping.

CAUSE: This may be a second invocation of this upgrade.

ACTION: None needed.

PARAMS:

 

ERROR: [DM_FT_INDEX_W_DOCUMENTS_NOT_INDEXED]

SEVERITY: WARNING

DESCRIPTION: II %i documents were not indexed in this update — their update_count attributes were set to %i

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_W_NO_FULLTEXT_IMPLEMENTATION_LOADED]

SEVERITY: WARNING

DESCRIPTION: A fulltext library was not identified in the server config object. Please identify a valid fulltext installation in the verity_location attribute of the server config object.

CAUSE: This error occurs if the verity_location attribute in the server config is not set.

ACTION: Set verity_location attribute of the server config object to a valid fulltext install location. Valid fulltext installations are listed in the fulltext_install_locs attribute of the docbase config object.

PARAMS:

 

ERROR: [DM_FT_INDEX_W_NO_VERITY_CODEPAGE_SPECIFIED]

SEVERITY: WARNING

DESCRIPTION: SS The verity_default_codepage flag was not specified in the server.ini for the %s locale. The server will set %s as the codepage for all existing dm_fulltext_index objects.

CAUSE: A verity locale was specified in the server.ini file but not a verity default codepage.

ACTION: The server has set an appropriate codepage based on the verity locale in the server.ini. No user action is required.

PARAMS:

 

ERROR: [DM_FT_INDEX_W_UPGRADE_400_TPART_TYPE_NOT_FOUND]

SEVERITY: WARNING

DESCRIPTION: The dmi_topic_partition type was not found during upgrade. Skipping.

CAUSE: This may be a second invocation of this upgrade.

ACTION: None needed.

PARAMS:

 

ERROR: [DM_FT_INDEX_W_FULLTEXT_IMPLEMENTATION_NOT_LOADED]

SEVERITY: WARNING

DESCRIPTION: A fulltext library is currently loaded. Changes made to load a new fulltext library cannot take effect until Content Server is restarted.

CAUSE: An attempt was made to load a new fulltext library without restarting Content Server.

ACTION: Restart Content Server after making the necessary changes.

PARAMS:

 

ERROR: [DM_FT_INDEX_T_INIT_INDEX_AGENT_UNABLE_TO_START]

SEVERITY: TRACE

DESCRIPTION: D Unable to start Index Agent %s

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_T_INIT_INDEX_AGENT_STARTED]

SEVERITY: TRACE

DESCRIPTION: D Index Agent %s started.

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_T_UPGRADE53_OBSOLETE_ATTRIBUTE_DROPPED]

SEVERITY: TRACE

DESCRIPTION: S Attribute %s dropped from dm_fulltext_index successfully.

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_T_UPGRADE53_REMOVE_INDEX_OBJECT]

SEVERITY: TRACE

DESCRIPTION: S The dm_fulltext_index object with %s is removed successfully

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_T_FTMETHOD_TIMEOUT]

SEVERITY: TRACE

DESCRIPTION: Timing out of %s method

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_T_UPGRADE_TOPIC_400D_DONE]

SEVERITY: TRACE

DESCRIPTION: Fulltext index topic to tdk upgrade succeeded

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_T_UPGRADE_SYSOBJECT_400_PART1_DONE]

SEVERITY: TRACE

DESCRIPTION: Part 1 of fulltext index sysobject upgrade succeeded

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_T_INIT_INDEX_AGENT_NO_FTINDEX_AGENT_FOUND]

SEVERITY: TRACE

DESCRIPTION: S There were no dm_ftindex_agent_config object(s) found for dm_fulltext_index object with name %s

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_T_UPGRADE53_ATTRIBUTE_ADDED]

SEVERITY: TRACE

DESCRIPTION: S Added attribute %s to the dm_fulltext_index type

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_T_UPGRADE53_REMOVE_INDEX_IMPLEMENTATION_OBJECT]

SEVERITY: TRACE

DESCRIPTION: SS Removal of dmi_tdk_index object with id %s %s

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_T_INIT_INDEX_AGENT_MSG]

SEVERITY: TRACE

DESCRIPTION: S %s

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_T_INIT_INDEX_AGENT_INVALID_FTINDEX_AGENT_CONFIG]

SEVERITY: TRACE

DESCRIPTION: D dm_ftindex_agent_config object %s is invalid.

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_T_UPGRADE_SYSOBJECT_400_PART2_DONE]

SEVERITY: TRACE

DESCRIPTION: Part 2 of fulltext index sysobject upgrade succeeded

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_T_UPGRADE53_OBSOLETE_INDEX_LOCATION]

SEVERITY: TRACE

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

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_T_UPGRADE_SYSOBJECT_400_DONE]

SEVERITY: TRACE

DESCRIPTION: Fulltext index sysobject upgrade succeeded

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_T_INIT_INDEX_AGENT_INVALID_FTINDEX]

SEVERITY: TRACE

DESCRIPTION: D dm_fulltext_index (%s) is invalid

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_T_UPGRADE53_REMOVE_COLLECTION_OBJECT]

SEVERITY: TRACE

DESCRIPTION: SS Removal of dmi_tdk_collect object with id %s %s

CAUSE:

ACTION:

PARAMS:

 

ERROR: [DM_FT_INDEX_I_IN_PROGRESS]

SEVERITY: INFORMATION

DESCRIPTION: SS Cannot perform operation %s — Fulltext index %s is currently in progress.

CAUSE: An attempt to perform an operation while another operation is in progress on the same index.

ACTION: Wait for the other operation to finish and try again.

PARAMS: The name of the operation, the name of the index

 

Advertisements

Leave a Reply

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

WordPress.com Logo

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

Twitter picture

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

Facebook photo

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

Google+ photo

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

Connecting to %s

%d bloggers like this: