KB484359: Oracle metadata objects are partially crawlered during initial crawl for quick search and sent to Kafka during initial load trigger for Platform Analytics

Product Owner, Principal • MicroStrategy

This article addresses the issue in which Oracle metadata objects are partially crawlered and sent to Kafka. This article also provides a workaround to avoid this behavior.

Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.

Description

Platform Analytics

Partial Object Change Journal logs are sent to Kafka during the initial load trigger. Around half of the objects remain "Unknown" in the Platform Analytics dossier, as shown below.

MetadataObjectTelemetry.log

You can look in the

MetadataObjectTelemetry.log

to troubleshoot. You can see that the object count that was sent is around half of the total object count, as shown below.


2020-05-28 16:29:41.092+02:00 [HOST:env-216144laiouse1][SERVER:CastorServer][PID:116693][THR:140598332135168][MetadataObjectTelemetry][Info][UID:54F3D26011D2896560009A8E67019608][SID:B66745255788072F092E2E32FEA5885F][OID:0] [ObjectTelemetryID:9EFF335211EAA0EFFFFF0080EF55A398] Project 'Platform Analytics' object telemetry in progress. 2601 objects are sent to Kafka successfully, 0 objects failed to send to Kafka. A total of about 4882 objects need to be sent.
2020-05-28 16:29:41.122+02:00 [HOST:env-216144laiouse1][SERVER:CastorServer][PID:116693][THR:140598332135168][MetadataObjectTelemetry][Info][UID:54F3D26011D2896560009A8E67019608][SID:B66745255788072F092E2E32FEA5885F][OID:0] [ObjectTelemetryID:9EFF335211EAA0EFFFFF0080EF55A398] Project 'Platform Analytics' object telemetry in progress. 2618 objects are sent to Kafka successfully, 0 objects failed to send to Kafka. A total of about 4882 objects need to be sent.
2020-05-28 16:29:41.122+02:00 [HOST:env-216144laiouse1][SERVER:CastorServer][PID:116693][THR:140598332135168][MetadataObjectTelemetry][Info][UID:54F3D26011D2896560009A8E67019608][SID:B66745255788072F092E2E32FEA5885F][OID:0] [ObjectTelemetryID:9EFF335211EAA0EFFFFF0080EF55A398] Project 'Platform Analytics' object telemetry finish. 2618 objects were sent in total.

Quick Search

Many objects cannot be searched for via Quick Search in Strategy Web or Workstation. Although the index status of Quick Search is "complete," the percentage is not 100%.

Why is this happening?

This issue seems to only occur for the Oracle metadata. This is caused by the inconsistent setting for

NLS_SORT

and

NLS_COMP

in the Oracle database server. The sort order in

SPANISH

A-F0-9

while the sort order in

BINARY

0-9A-F

Run the following SQL to get the Oracle metadata database configurations:
```
select * from nls_session_parameters
```
Check the
```
NLS_SORT
```
and
```
NLS_COMP
```
value.

Workaround

Set the Oracle metadata database

NLS_SORT

and

NLS_COMP

settings the same at the Database Instance Level. Both are

SPANISH

or both are set to

BINARY

.
Note: This problem occurs in the Oracle metadata and the impacted customers are usually from the following countries:


Arabic, Czech, Danish, Dutch, Finnish, French, German, German_DIN,
    Greek, Hebrew, Hungarian, Italian, Latin, Lithuanian, Norwegian,
    Russian, Slovak, Spanish, Swedish, Turkish, West_European

For customers from the above countries, the

NLS_SORT

in Oracle database setting follows the

NLS_LANGUAGE

settings, and the sort order is letters before numbers, i.e.

A-Z0-9

. At the same time, the default value of

NLS_COMP

in the Oracle database is

BINARY

References

Setting Up a Globalization Support Environment
Order by: numbers after letters?

Comment

0 comments

Details

Knowledge Article

Published:

June 22, 2020

Last Updated:

March 21, 2024