(17388575) Import fails with translations when encountering enumerated values.
When importing data, CIM assumes that the system locale is the same as used when exporting the data. When the system encounters an enumeration code value that is not in the same locale, the import fails.

Workaround: You can force the imports to used the same locale as the export locale by updating the /CIM/plugins/Base/ant/cim-ant.xml file. Update the call to the startSQLRepository executable file to include the locale environment variables and set them to the specific language.

The following example shows the addition of the LANG and LC_ALL values to the start.sqlrepository call for non-Windows environments:

<target name="start.sqlrepository.nonwindows">
  <exec executable="${cim.dynamo.root}home/bin/startSQLRepository"
      dir="${cim.dynamo.root}home/bin" failonerror="true">
    <arg line="${cim.sqlrepository.arg}"/>
    <env key="DYNAMO_HOME" value="${cim.dynamo.root}/home"/>
    <env key="CLASSPATH" value="${cim.classpath}"/>
    <env key="CONFIGPATH" value=""/>
    <env key="ATG_CHECK_DEPLOY_TARGETS" value="false"/>
    <env key="LANG" value="en_US.UTF-8"/>
    <env key="LC_ALL" value="en_US.UTF-8"/>
  </exec>
</target>

(13294564) The Import Initial Data step in CIM configuration fails if the DISPLAY variable in the AIX profile is enabled.

Workaround: Disable the DISPLAY variable.

(13282091) CIM does not configure properties files necessary for DB2 databases on the staging server.

Workaround: Configure the properties manually on your staging server as described:

In the /atg/dynamo/messaging/SqlJmsProvider component, configure the following:

parameterizedSelect=false
useSetBinaryStream=false

In the <ATG11dir>/home/localconfig/GLOBAL.properties file configure the following:

handleRangesInMemory=true
(17739178localTransactionModeInitialization=false