Configuration IBM DB2 Valid Tokens Error

Problem

You have received an error in regards to a Database Migration set to an IBM Database and get the following message:

Error
Batch: 20130903.145348 (Exceptions)

Migration: Database

Error: Error adding index record: SQL0104: Token PRINTED was not valid. Valid tokens: ) ,.

Cause . . . . . : A syntax error was detected at token PRINTED. Token PRINTED is not a valid token. A partial list of valid tokens is ) ,. This list assumes that the statement is correct up to the token. The error may be earlier in the statement, but the syntax of the statement appears to be valid up to this point. Recovery . . . : Do one or more of the following and try the request again: – Verify the SQL statement in the area of the token PRINTED. Correct the statement. The error could be a missing comma or quotation mark, it could be a misspelled word, or it could be related to the order of clauses. – If the error token is <END-OF-STATEMENT>, correct the SQL statement because it does not end with a valid clause.

Solution

There are a lot of things to look at with this error. It most likely means the mapping is incorrect and the system fields are not properly being filled out. In order for the database to accept our migration all fields must be correctly mapped and no field can be empty.

There are 8 system database fields that must be filled out in order for the migration to work. IBM2 Databases do not accept NULL insert or empty strings. All fields within PSIcapture must be filled out in order for migration to work.

Below I have listed the system fields that need to be mapped and their general properties.

  • IVWSPLN= 6 characters/vchar
  • IVWSPLF= 10 characters/vchar
  • IVWUSER= 10 characters/vchar
  • IVWJOBN= 6 characters/numeric
  • IVWDATE= 10 characters/ Must follow specific format yyyy-mm-dd
  • IVWTIME= 8 characters/ Must follow specific format hh.mm.ss
  • IVWJOB= 10 characters/vchar
  • IFSFILE= set to 2048 characters/vchar/image file output by PSIcapture must match this system field within database.

If you are still experiencing difficulties, please contact our Support team by:


Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.