[SOLVED] backup script not backing up Dynamic Fields values?

[blastik]

Hi,

I was doing a restore test of our OTRS 3.3.7 and everything went right. I couldn't get the Restore script to work so I ended up creating a new DB and restoring the dump. The only problem i found is that some the values of the Dynamic Fields were not backed up for some reason. That means the Dynamic Field and their properties are shown but when going inside I cant see the values.

How can I fix this?

Thanks!
David

[blastik]

Anybody please?

[crythias]

database backup should account for this. There's no ability to tell you what's the problem in your environment. Either the database backup has the values or it doesn't.

[blastik]

Thank for your answer. The values contain Scandinavian characters. Maybe is because of that?
I need to migrate OTRS to a new server. Do you recommend me to introduce the missing values manually using the OTRS GUI?

D.

[blastik]

I answer myself... other dynamic fields didn't have Scandinavian characters into the values and they were not restored...

[blastik]

Cyntias,

I've checked the database and the values are there. What could have happened?

[blastik]

FYI

Checking viewtopic.php?t=22410 and viewtopic.php?f=81&t=19169

[blastik]

Okay I found the problem.
For some reason the field name "config" in the "dynamic_field" table had the following format in the old system (MySQL version 5.1.73):

Code: Select all

PossibleValues:
  Key1: Value1
  Key2: Value2
  Key3: Value3
  ...
  

The new database (MySQL version 5.5.40) didn't like that, even though the collation was the same as the old. So I had to add ' as follows:

Code: Select all

PossibleValues:
  'Key1': 'Value1'
  'Key2': 'Value2'
  'Key3': 'Value3'
  ...
  

Then run the otrs.DeleteCache.pl script and voilá!

Also for the record, so it appears on future searches, the errors I was getting in the system logs were:

Code: Select all

YAML data was: "---
Loading the YAML string failed: YAML Error: Invalid element in map

[reneeb]

The reason for this is a newer version of the YAML module... Maybe this should reported as a bug...