Bookshelf Home | Contents | Index | Search | PDF

Siebel Marketing Guide > Troubleshooting in Siebel Marketing > Other Troubleshooting Issues in Siebel Marketing >

Mapping a Table Does Not Retrieve Fields in Fields View

---

When you step off a new table record in the Tables view of the Marketing Administration screen, a Data Dictionary server process retrieves field names and their data types for that table from the database server.

Mapping a table does not retrieve fields. Check the status of the Data Dictionary task in the My Component Requests view.

CAUTION:  Do not add field records manually and then map Measures to a table record that did not retrieve fields. Always wait for the data retrieval task to complete or measures on fields will not work.

Possible Cause 1

Data Dictionary task is in Error status.

How to diagnose 1. Check the status of the Data Dictionary task in the My Component Requests view. If its status is Error, perform the following tasks:

Verify that the schema name is prefixed to the table name. For example, SIEBEL.S_CONTACT, OLAP.W_PERSON_FACT. For information, see table name information in Table 19.
Verify that the table name is spelled correctly. Some databases are case sensitive to table names. For information, see Creating Server Definitions.
Verify that the correct Server is assigned to the table. For information, see Mapping to Tables from the Servers View Tab.
Verify that the database server is running. It is recommended to perform this task from the Siebel server machine using the ODBC test function. For assistance, see your system administrator.
Verify that the server DSN is the system DSN. For information, see Creating Server Definitions.
Verify that the correct ODBC driver was used to create a DSN. For example, ODBC drivers provided by Oracle and Microsoft for an Oracle database could be installed on the server for another application. They should not be used for Siebel Marketing. For information, see Creating Server Definitions.
Verify that the table actually exists in the database. For assistance, see your system administrator.
Verify that the user for this data source has read access to the table. It is recommended to run the ODBC test program, login as the user that you setup in the Servers view tab, and run a count(*) query on the table. For assistance, see your system administrator.
Verify that the task is run on the right Siebel server. Check the Server field in the My Components Requests view. For assistance, see your system administrator.

How to resolve 1. If you find errors when diagnosing the problem, correct the errors and create the table again.

Possible Cause 2

The Data Dictionary task is still in queue.

How to diagnose 2. Check the status of the Data Dictionary task in the My Component Requests view. For assistance, see your system administrator. If its status is Queued, perform the following tasks:

Verify that the Siebel server is running. If you map tables when Siebel server is down, the Data Dictionary task(s) will stay in queue till the Siebel server comes back up.
Verify that the Data Dictionary component and Marketing Server component group are enabled.
Verify that the Data Dictionary component is running.
Verify that the Request Server is running without errors.
Verify that the Siebel Server is configured properly (check the connect string and table owner in Siebel.cfg).

How to resolve 2. If you find errors when performing the diagnostic tasks, correct the errors and recheck the status of the Data Dictionary task in the My Component Requests View. If you have resolved the error, the Data Dictionary task should start running.

Possible Cause 3

The Data Dictionary completes successfully but does not retrieve fields.

How to diagnose 3. For assistance in performing the following tasks, see your system administrator:

Check the native data types for the table.
Check the ODBC driver documentation to see if SQLColumns is 3.x compliant.

How to resolve 3. If you find errors when performing the diagnostic tasks, correct the errors and create the table again.

Possible Cause 4

The Data Dictionary task errors out intermittently.

First, confirm that the problem is not a a result of other causes discussed in this topic.

How to diagnose 3. Check the Marketing Server log for errors.

If you find a Memory Allocation error, your system ran out of memory causing the task to fail.

How to resolve 4. You might need more available memory on the server.

Bookshelf Home | Contents | Index | Search | PDF