Troubleshooting
Problem
During the migration of webMethods API Gateway from version 10.15 to 11.1, the core data migration to Elasticsearch fails. The issue is observed in environments where the tenant ID contains underscores, leading to improper staged index creation and reindexing failures.
Symptom
The migration of core data to Elasticsearch failed with below error:
Migration log Error: Total document count is less than created + updated document count. Reindexing has failed
Elasticsearch log: "caused_by":{"type":"illegal_argument_exception","reason":"Limit of total fields [1000] has been exceeded while adding new fields [21]"}},"status":400}
Cause
The issue is for the tenant IDs having underscore.
gateway_default_policy is an index in source 10.15
gateway_defaultmigrated_policy is a staged index created in target 11.1
From the staged index gateway_defaultmigrated_policy, it is reindexed to gateway_default_assets index in 11.1
However, if the tenant ID has underscore in it, the staged index is created in wrong format and it leads to migration failure.
Diagnosing The Problem
- Inspect server logs from the 11.1 instance for migration errors.
- Collect Elasticsearch logs to identify potential issues related to index configuration or data migration.
- Verify the tenant ID configuration in both 10.15 and 11.1 instances to ensure consistency.
- Apply the workaround of using 'default' as the tenant ID in both 10.15 and 11.1 to resolve issues related to tenant ID formatting.
- Perform a clean migration after addressing the identified issues and verify the resolution.
Resolving The Problem
The issue was caused by the 'Limit of total fields [1000] has been exceeded' error during the migration from 10.15 to 11.1 due to improper index naming because of the tenant ID containing underscores. To resolve: Install 11.1 Fix 7
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
29 November 2025
UID
ibm17252598