Bookshelf Home | Contents | Index | Search | PDF

Siebel Marketing Guide > Troubleshooting in Siebel Marketing > Error Messages in Siebel Marketing >

Invalid Join Path

---

Invalid join path errors are caused when the application server cannot access one or more tables that are needed for data synchronization (data retrieval) or snapshot generation. When trying to synchronize data (data retrieval) or generate a snapshot, the following error appears:

Invalid Join Path

Possible Cause 1

No start point join has been created.

Make sure that there is a start point join on a table being retrieved.

How to diagnose 1. Verify that you have set up at least one start point join. When you receive this error during data retrieval, verify that there is a start point join on the table being retrieved.

How to resolve 1. Create appropriate start point joins. For additional information, see Joining Tables and Fields.

Possible Cause 2

Joins are not set up correctly.

How to diagnose 2. Use the following methods to verify that joins are set up correctly:

Verify the content of the snapshot to make sure joins are properly set up to extract data elements needed for the snapshot. Use the Screens > Programs > Snapshots view to see the contents of the snapshot.
Query the control table to obtain a list of tables and fields required for the snapshot build.

CAUTION:  It is recommended that you contact Siebel Technical Support engineers before you perform this task because it involves querying the Siebel database.

Siebel Marketing Server creates a temporary table called the control table that captures all the necessary definitions of a snapshot, including the list of tables and fields needed to build the snapshot. By querying this table, you can identify the tables needed to build the snapshot.

The Marketing Server log file reports the ROWID for the snapshot task and every stage has a unique task ROWID. The table name is the task ROWID without any special characters and containing a prefix of C_. So a task with ROWID 1-GXJ2 creates a control table C_1GXJ2. Use the following query to troubleshoot:

Select distinct labels, db_table, db_name from <table name>

NOTE:  The Labels column determines the Siebel object (list measure, bound measure, and so on) that is mapped to the table (db_table) and field (db_field).

How to resolve 2. Correct the setup for any joins that are set up incorrectly. For additional information, see the topics about joins in External Data Mapping.

Bookshelf Home | Contents | Index | Search | PDF