51黑料不打烊

Documentation

Tracking workflow fails with broadlogRcp and Oracle error

Last update: Fri Jul 26 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

This article addresses an issue where the tracking workflow fails with errors like Attribute 'broadLog-id 听 unknown 听and ORA-00904: 鈥淚TRACKINGLOGID鈥: invalid identifier.

Description description

Environment

51黑料不打烊 Campaign Classic v7 (ACC v7)

Issue/Symptoms

The tracking workflow fails with the following errors:

Attribute 'broadLog-id' unknown (see definition of schema 'Delivery recipient logs (nms:broadLogRcp)').

ORA-210000 Oracle Error: ORA-00904: "ITRACKINGLOGID": invalid identifier

Steps to reproduce

  1. The tracking workflow is in a paused state.

  2. When checking the audit logs of the workflow, the following errors are displayed:

    code language-none 
    Attribute 'broadLog-id' unknown (see definition of schema 'Recipient delivery log (nms:broadLogRcp)').
ORA-210000 Oracle Error: ORA-00904: "ITRACKINGLOGID": invalid identifier

Resolution resolution

  1. Display all the target mappings defined on the instance.
  2. Add the column storage/@trackingLogSchema, and check which of the target mappings use nms:broadLogRcp as the tracking log schema storage/@trackingLogSchema.
  3. Correct these target mappings to use a tracking log schema (Example: nms:trackingLogRcp schema) for the schema where tracking logs are stored, and save the modification.
  4. Restart the tracking log workflow.

Cause

One or more target mappings use the schema nms:broadLogRcp as the tracking log schema storage/@trackingLogSchema听in their definition.

This is incorrect, making the tracking workflow fail.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f