Search for successful or failed metadata generation in SAS® Customer Intelligence 360


This SAS KB article describes how to determine whether the generation of metadata for SAS Customer Intelligence 360 is successful.

Locate Information in the onprem_direct.log

Below are some tips about how to search for successful or failed metadata generation in the onprem_direct.log.

  1. Search for the metadata generation start using CommandController - handleMetadataRequest.

    2026-03-24T12:43:34,800 INFO  [http-nio-10080-exec-10] SID[] USER[] CC[] [] cs.crm.rest.controller.CommandController - handleMetadataRequest {"maxConcurrent":2,"generateMetadata":true,"genMethod":"SQL",^
    "maxNominalValues":1000,"itemIds":["root.GENDER"],"clearCache":true,"type":^
    "metadata","bcName":"your BC Name"}

    2026-03-24T12:43:34,800 INFO  [http-nio-10080-exec-10] SID[] USER[] CC[] [] cs.crm.rest.controller.CommandController - handleMetadataRequest {"maxConcurrent":2,"generateMetadata":true,"genMethod":"SQL",^
    "maxNominalValues":1000,"itemIds":["root.GENDER"],"clearCache":true,"type":^
    "metadata","bcName":^"your BC Name"}

  2. Search for a successful metadata generation:

    DirectMarketingMetadataService - generate metadata successful

    2026-03-24T12:43:38,126 INFO  [http-nio-10080-exec-10] SID[] USER[] CC[] [] t.service.DirectMarketingMetadataService - generate metadata successful

  3. If metadata generation fails, the following message is displayed: 

2026-03-24T11:58:23,493 INFO  [http-nio-10080-exec-10] SID[] USER[] CC[] [] t.service.DirectMarketingMetadataService - process - error processing metadata request: Problem running metadata generation

Note: The [http-nio-10080-exec-10] session needs to match the start session.

Troubleshooting Tips

  1. Find the data items that require metadata generation. The Task # contains the data item ID, which is easily recognizable because of the 'root.' In addition, the subject level is listed for the data item.

    Search for the Task #:

    2026-03-24T12:43:35,591 INFO  [CIAsyncExec-7] SID[] USER[ciprem] CC[] [] apattern.metadata.GenerationRunnableImpl - Task # 0, TaskID: DCDEIFIABNF5WJDS, Node Name root.GENDER:SUBJECT_ID_CUSTOMER

    2026-03-24T12:43:35,594 INFO  [CIAsyncExec-7] SID[] USER[ciprem] CC[] [] apattern.metadata.GenerationRunnableImpl - Task # 1, TaskID: FAGGNBF33NBMV4C1, Node Name root.GENDER:SUBJECT_ID_HOUSEHOLD

    2026-03-24T12:43:35,594 INFO  [CIAsyncExec-7] SID[] USER[ciprem] CC[] [] apattern.metadata.GenerationRunnableImpl - Task # 2, TaskID: BBBHWB0CRBGLWHYY/Norminal

    2026-03-24T12:43:35,595 INFO  [CIAsyncExec-7] SID[] USER[ciprem] CC[] [] apattern.metadata.GenerationRunnableImpl - Task # 3, TaskID: ABHGJ54ZSVDJQQS0/UpdateMetadata


  2. As a quick method, search for Exception running metadata query.

    If you cannot tell which data item causes the problem, try to regenerate the metadata using --maxconcurrent 1, as shown in the following example:

    ./dm.sh gmd --bcName "My Business Context" --method SQL -maxconcurrent 1 --uploadallitems --clearcache

  3. In the editor (for example, TextPad), search for, mark all, and copy to text the following:

    Running job:
    Completed job:
    ERROR (case sensitive)

    Here is an example:

    2025-02-24 15:14:13,576 DEBUG [CIExec-14] SID[] USER[] CC[] [] .crm.task.queue.EvenDistributionJobQueue - TID[DFEAJGYYNBGFWS11] Running job: DFEAJGYYNBGFWS11 for node root.Segment Cd:null in request with id [not set]

    2025-02-24 15:14:13,624 ERROR [CIAsyncExec-2] SID[5ac09315d09bde05:41d0b6c0:195374e7cb4:-7a7c] USER[Customer Intelligence User] CC[] [] tics.crm.custdata.datapattern.MADataItem - Date Of Transaction: Level= is not a valid level.  Forcing Metadata to None and Level to Nominal.

    2025-02-24 15:14:13,643 DEBUG [CIExec-11] SID[] USER[] CC[] [] .crm.task.queue.EvenDistributionJobQueue - TID[DCDAS35FX3GFWA1D] Completed job: DCDAS35FX3GFWA1D for node root.Type Description:null in request with id [not set] in 0.796 seconds

    2025-02-24 15:14:13,644 DEBUG [CIExec-11] SID[] USER[] CC[] [] .crm.task.queue.EvenDistributionJobQueue - TID[EAGBCD5XENBJXTN4] Running job: EAGBCD5XENBJXTN4 for node root.Prefix Desc_4:null in request with id [not set]

    2025-02-24 15:14:13,852 ERROR [CIExec-14] SID[5ac09315d09bde05:41d0b6c0:195374e7cb4:-7a7c] USER[Customer Intelligence User] CC[] [] taSQLValuesGenerator$ValueQueryGenerator - TID[DFEAJGYYNBGFWS11] Exception running metadata query:

    ERROR: File CDM.CDM_SEGMENT_DETAIL.DATA does not exist.

    ERROR: File CDM.CDM_SEGMENT_DETAIL.DATA does not exist.

    2025-02-24 15:14:13,852 ERROR [CIExec-14] SID[5ac09315d09bde05:41d0b6c0:195374e7cb4:-7a7c] USER[Customer Intelligence User] CC[] [] tern.metadata.MetadataSQLValuesGenerator - TID[DFEAJGYYNBGFWS11] com.sas.analytics.crm.error.client.ApplicationException: Error while submitting SAS code

    ERROR: File CDM.CDM_SEGMENT_DETAIL.DATA does not exist.

    2025-02-24 15:14:13,853 DEBUG [CIExec-14] SID[] USER[] CC[] [] .crm.task.queue.EvenDistributionJobQueue - TID[DFEAJGYYNBGFWS11] Completed job: DFEAJGYYNBGFWS11 for node root.Segment Cd:null in request with id [not set] in 0.277 seconds


  4. If an immediate error occurs, a previous metadata generation likely started but did not complete.

If you are not able to determine why a metadata generation fails, contact SAS Technical Support and provide the onprem_direct.log.