Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

AXimport AXexport usage. Tons of Zeros added to "range start" field

Updated: 21 May 2010 | 1 comment
Greg Zielinski's picture
0 0 Votes
Login to vote

I've exported jobs from one DS and imported into a new one. All my jobs that contain "modify configuration" tasks have had over 64 zero's added to the prefix.



Fixed text = WCHI

range start = 1000

(imported version of job… range start = “tons of zeros”1000)

results wchi1000...wchi1009



After the import on the new system, I get the error "Please enter no more than 64 characters”

I look and on the imported job, range start = 0000000000000000000000…(some seemingly infinite number of zeros)0001000.



The end of the range still has 1000. I look in the “config_set” table in EXPRESS and the “cname_addl” field shows the value of 1000 as I would expect.

If I copy the entire DS job, or just copy the task within the job, the pasted results also share this error.

However, if I create a new “modify configuration” task, the setting I enter remain correct.



Comparing the items in the “config_set” table, I see a field called “cname_addl_padlength”

The working job has “4” and the failed jobs/tasks have “NULL”.



Any idea how to track this down. A problem with the export or with the import?

Comments

Greg Zielinski's picture
14
Nov
2008
0 Votes 0
Login to vote

This quick fix seems to have made the problem go away.



SQL query

update config_set

set cname_addl_padlength = len(cname_addl)





This replaced the NULL values in cname_addl_padlength with what appears to be the correct value.



Still not sure if it was a bad export or bad import. Also not sure this is the correct or safe fix.