Resolving deployment errors

The sections in this topic describe how to react to some common error and warning messages that can appear during i2 Analyze deployment.

"The results configuration file contains an invalid property type identifier"

The following message is displayed if there are any identifiers in your results configuration file that are not present in the i2 Analyze schema when you start i2 Analyze.

# [opal-services-is] OneOffStartupServiceInitializer encountered a problem communicating with the database that it cannot recover from.
# [opal-services-is] Exception during initialization. The application is in an unusable state.
# [opal-services-is] Errors occurred accessing system resources from ApplicationLifecycleManager:
# [opal-services-is] The results configuration file contains an invalid property type identifier: ADD1.

To resolve this issue, ensure that all of the identifiers in your results configuration file are present in the i2 Analyze schema. For more information, see Setting up search results filtering.

"Default security dimension values provider specifies dimension values that are not in the security schema" or "Default security dimension values provider specified no values for the dimensions with these IDs"

These messages can appear when the security dimension values that are specified in the security schema for the <DefaultSecurityDimensionValues> element are incorrect. For more information, see Setting default dimension values.

"Unable to determine the DB2 version as you do not have execute permission to db2level"

This message is displayed if the JDBC driver is not present, or the installation path to Db2 is specified incorrectly when you run the generateDefaults toolkit task.

There are two ways to resolve this issue:

  • Ensure that you provide the JDBC driver for your deployment. For more information, see Specifying the JDBC driver.

  • Ensure that the value for the db.installation.dir setting in the environment.properties file is correct. For more information, see environment.properties.

"Invalid attribute value for 'name' in element 'complexType'. Recorded reason: cvc-datatype-valid.1.2.1: 'Direcci├│nItemClass' is not a valid value for 'NCName'."

This message is displayed if you try to deploy with a highlight query configuration that contains an invalid character for the Db2 code page. After you install Db2, you specify the code page that the Db2 instance uses. For more information about the value that you must use for the code page, see the Post-install section of Installing IBM Db2 for i2 Analyze.

"Some item types have multiple property types with the same semantic type ID, which is not permitted."

This message appears if the server detects that the Information Store schema assigns the same semantic property type to more than one property type of the same item type. The message includes the types involved and the identifier of the semantic type. For example:

Property (ET9)
        Property Type (PRO2): guidc329f90d-3bf7-40c3-8d87-f6fe3cb8d5d4
        Document Type (PRO30): guidc329f90d-3bf7-40c3-8d87-f6fe3cb8d5d4

To resolve the problem, open the schema in Schema Designer and make one of the following changes:

  • Remove the semantic property type assignment from all but one of the indicated property types

  • Assign different semantic property types from the i2 Semantic Type Library to all but one of the indicated property types

  • Derive appropriate custom semantic property types from the duplicated type, and assign the derived types to the property types instead.

If the property types in question are semantically related, the second and third options provide the best analytical experience.

"<Permission> elements in the security schema have Level attributes ('NONE') that are not valid. Ensure that all permission levels are valid."

This message appears if the server detects that the security schema includes the NONE access level in a permission assignment. For example:

<SecurityPermissions>
  <GroupPermissions UserGroup="Analyst">
    <Permissions Dimension="SD-SC">
      <Permission DimensionValue="HI" Level="UPDATE"/>
      <Permission DimensionValue="OSI" Level="NONE"/>
    </Permissions>
  </GroupPermissions>
  ...

To resolve the problem, remove the NONE assignment , or replace it with a valid level (UPDATE or READ_ONLY).