Troubleshooting
Problem
First, we correctly deployed the example, and all was working well: setup -t deployExample
Then, we created a new personalized Schema by using IBM® i2 Analyze Schema Designer. We configured both the Schema and Charting Scheme correctly in "/opt/IBM/i2analyze/toolkit/configuration/fragments/common/WEB-INF/classes/ApolloServerSettingsMandatory.properties" file.
We dropped the example database and followed the steps to replace the schema. Then, we successfully redeployed, and confirmed the ISTORE database was created successfully.
However, when we tried to start the system, we received an error:
[root@localhost IBM]# /opt/IBM/i2EIA/toolkit/scripts/setup -t start
Validating configuration...
Validating configuration...
ZooKeeper (id 1) on port 9983: Started
Solr Node (id node1) on port 8983: Started
All shards are active on collection main_index.
All shards are active on collection match_index1.
All shards are active on collection match_index2.
All shards are active on collection highlight_index.
All shards are active on collection chart_index.
Starting server opal-server.
Server opal-server started with process ID 15603.
Monitoring /opt/IBM/i2analyze/deploy/wlp/usr/servers/opal-server/logs/console.log for application status.
Waiting for 'opal-services-is' application to start...
============================================================
# [opal-services-is] Application initializing...
# [opal-services-is] Checking configuration of Solr Collection 'main_index'.
# [opal-services-is] Configuration check passed for Solr Collection 'main_index'.
# [opal-services-is] Checking configuration of Solr Collection 'chart_index'.
# [opal-services-is] Configuration check passed for Solr Collection 'chart_index'.
# [opal-services-is] ZooKeeper Command Manager has started.
# [opal-services-is] SolrIndexScheduler for Solr Collection 'main_index' has started.
# [opal-services-is] SolrIndexScheduler for Solr Collection 'match_index1' has started.
# [opal-services-is] SolrIndexScheduler for Solr Collection 'match_index2' has started.
# [opal-services-is] SolrIndexScheduler for Solr Collection 'chart_index' has started.
# [opal-services-is] 'main_index', 'ALL_REPLICAS_ACTIVE', 'The Solr collection is healthy'.
# [opal-services-is] SolrHealthCheckScheduler has started for Solr Collection 'main_index'.
# [opal-services-is] SolrHealthCheckScheduler has started for Solr Collection 'match_index1'.
# [opal-services-is] SolrHealthCheckScheduler has started for Solr Collection 'match_index2'.
# [opal-services-is] SolrHealthCheckScheduler has started for Solr Collection 'chart_index'.
# [opal-services-is] 'match_index1', 'ALL_REPLICAS_ACTIVE', 'The Solr collection is healthy'.
# [opal-services-is] 'match_index2', 'ALL_REPLICAS_ACTIVE', 'The Solr collection is healthy'.
# [opal-services-is] 'chart_index', 'ALL_REPLICAS_ACTIVE', 'The Solr collection is healthy'.
# [opal-services-is] Creating deletion scheduler
# [opal-services-is] SavedVQDeletionScheduler started.
# [opal-services-is] Creating on-line InfoStore upgrade executor.
# [opal-services-is] Checking for pending upgrade tasks...
# [opal-services-is] No pending upgrade tasks.
# [opal-services-is] OneOffStartupServiceInitializer encountered a problem 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] Failed to load configuration file "highlight-queries-configuration.xml". Cause: "org.xml.sax.SAXParseException; lineNumber: 313; columnNumber: 48; s4s-att-invalid-value: Invalid attribute value for 'name' in element 'complexType'. Recorded reason: cvc-datatype-valid.1.2.1: 'Direcci├│nItemClassItemClass' is not a valid value for 'NCName'."
# [opal-services-is] Application stopping...
Server opal-server started with process ID 15603.
Monitoring /opt/IBM/i2analyze/deploy/wlp/usr/servers/opal-server/logs/console.log for application status.
Waiting for 'opal-services-is' application to start...
============================================================
# [opal-services-is] Application initializing...
# [opal-services-is] Checking configuration of Solr Collection 'main_index'.
# [opal-services-is] Configuration check passed for Solr Collection 'main_index'.
# [opal-services-is] Checking configuration of Solr Collection 'chart_index'.
# [opal-services-is] Configuration check passed for Solr Collection 'chart_index'.
# [opal-services-is] ZooKeeper Command Manager has started.
# [opal-services-is] SolrIndexScheduler for Solr Collection 'main_index' has started.
# [opal-services-is] SolrIndexScheduler for Solr Collection 'match_index1' has started.
# [opal-services-is] SolrIndexScheduler for Solr Collection 'match_index2' has started.
# [opal-services-is] SolrIndexScheduler for Solr Collection 'chart_index' has started.
# [opal-services-is] 'main_index', 'ALL_REPLICAS_ACTIVE', 'The Solr collection is healthy'.
# [opal-services-is] SolrHealthCheckScheduler has started for Solr Collection 'main_index'.
# [opal-services-is] SolrHealthCheckScheduler has started for Solr Collection 'match_index1'.
# [opal-services-is] SolrHealthCheckScheduler has started for Solr Collection 'match_index2'.
# [opal-services-is] SolrHealthCheckScheduler has started for Solr Collection 'chart_index'.
# [opal-services-is] 'match_index1', 'ALL_REPLICAS_ACTIVE', 'The Solr collection is healthy'.
# [opal-services-is] 'match_index2', 'ALL_REPLICAS_ACTIVE', 'The Solr collection is healthy'.
# [opal-services-is] 'chart_index', 'ALL_REPLICAS_ACTIVE', 'The Solr collection is healthy'.
# [opal-services-is] Creating deletion scheduler
# [opal-services-is] SavedVQDeletionScheduler started.
# [opal-services-is] Creating on-line InfoStore upgrade executor.
# [opal-services-is] Checking for pending upgrade tasks...
# [opal-services-is] No pending upgrade tasks.
# [opal-services-is] OneOffStartupServiceInitializer encountered a problem 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] Failed to load configuration file "highlight-queries-configuration.xml". Cause: "org.xml.sax.SAXParseException; lineNumber: 313; columnNumber: 48; s4s-att-invalid-value: Invalid attribute value for 'name' in element 'complexType'. Recorded reason: cvc-datatype-valid.1.2.1: 'Direcci├│nItemClassItemClass' is not a valid value for 'NCName'."
# [opal-services-is] Application stopping...
The following application(s) failed to start: opal-services-is.
Errors were reported by: opal-services-is.
============================================================
The requested operation on the Liberty server failed. See the output above and the log files in /opt/IBM/i2analyze/deploy/wlp/usr/servers/opal-server/logs for more details.
Errors were reported by: opal-services-is.
============================================================
The requested operation on the Liberty server failed. See the output above and the log files in /opt/IBM/i2analyze/deploy/wlp/usr/servers/opal-server/logs for more details.
Cause
If the newly created schema contained words with accentuated characters in the Display Name, then you can see this problem.
Here is an example schema entity definition that shows the problem:
<EntityType Id="ET1" SemanticTypeId="guidC6A2C76F-5637-43DC-92F8-8F3563226307" Description="Detalles de dirección" DisplayName="Dirección" Icon="House">
The DisplayName value is saved in the database, but the values are incorrect. They are appearing as "Direcci├│n" rather than "Dirección". The reason is that the database was not set for UTF-8 encoding (code page 1208).
After Db2® is installed, there are some postinstallation steps with instructions to ensure the database is created with the correct code set.
See the post-install steps
- Post-install
- After you install Db2® for the Information Store, you must enable the administrative task scheduler and set the code page on the Db2® installation:
- On the command line, navigate to the SQLLIB\bin directory of your Db2® installation. On Linux®, log in as db2inst1.
- To enable the administrative task scheduler, run the following command:
db2set DB2_ATS_ENABLE=YES
- To set the code page for UTF-8 encoding, run the following command:
db2set DB2CODEPAGE=1208
Resolving The Problem
Set the proper environment for your database creation. The instructions are for Linux®, but the issue also applies to Windows® system.
1. Add the LANG environment to the ".bash_profile" file for "db2inst1" user on Db2® database server. This example sets LANG for the Spanish language:
-
cd ~ echo "export LANG=es_ES.UTF-8" >>.bash_profile
2. Run the Post-install steps on the database Server with "db2inst1" user:
-
db2set DB2_ATS_ENABLE=YES db2set DB2CODEPAGE=1208
3. Update i2 Analyze Schema:
- Copy the i2 Analyze schema and charting scheme files to the /opt/IBM/i2analyze/toolkit/configuration/fragments/common/WEB-INF/classes directory of the deployment toolkit.
- Specify the i2 Analyze schema and charting scheme that the deployment uses in the ApolloServerSettingsMandatory.properties file in the same directory as the schema files.
- Set the values of the SchemaResource and ChartingSchemesResource properties to the names of your schema and charting scheme files.
- Save and close the file.
4. Copy a blank highlight query configuration file from the example configs to replace the example highlight query configuration, which correlates with the schema:
-
cp /opt/IBM/i2analyze/toolkit/examples/configurations/information-store-daod-opal/configuration/live/highlight-queries-configuration.xml /opt/IBM/i2analyze/toolkittoolkit/configuration/live
5. Update the /opt/IBM/i2analyze/toolkit/configuration/fragments/opal-services/WEB-INF/classes/DiscoServerSettingsCommon.properties file to clear out the example ResultsConfigurationResource property value, which also references the schema.
### Result configuration options ###
# The file that specifies what options are available to users when they view
# and filter results.
ResultsConfigurationResource=
6. Follow the steps of Replacing i2 Analyze Schema, which re-creates your database with the proper code set and the new schema. If your components are on separate systems, see the Replacing i2 Analyze Schema documentation for the instructions. If they are on the same system, you can use these commands:
-
./setup -t stop ./setup -t dropDatabases --hostname <hostname> ./setup -t deleteSolrCollections --hostname <hostname> --all ./setup -t deploy ./setup -t start
Replace <hostname> with the hostname of your system (as specified in the topology.xml file)
Windows® is a Registered Trade Mark of Microsoft® Corporation.
Related Information
Document Location
Worldwide
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSXVXZ","label":"IBM i2 Enterprise Insight Analysis"},"ARM Category":[{"code":"a8m0z000000CbpvAAC","label":"i2 Enterprise Insight Analysis->i2 Analyze->Configuration"}],"ARM Case Number":"TS004011104","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.3.x","Line of Business":{"code":"LOB24","label":"Security Software"}}]
Product Synonym
EIA; i2 Analyze; Opal server;
Was this topic helpful?
Document Information
Modified date:
08 September 2020
UID
ibm16321361