SYMPTOM
The data load does not complete, and the following error is seen in the DSSErrors (on the Strategy Intelligence Server) when running a data load from Strategy Enterprise Manager 10.x.
2017-09-13 17:46:59.150-03:00 [HOST:XXXX2][SERVER:CastorServer][PID:15044][THR:4908][Database Classes][Error] OdbcParameterizedQuery::ExecQuery failed.
Error type: Odbc error. Odbc operation attempted: SQLExecute. [22001:0: on SQLHANDLE] [Strategy][ODBC Oracle Wire Protocol driver]String data, right truncated. Error in parameter 3. Connection String: DSN=BDWP001;UID=EM_MD;SRVR=SIEONLINE;. SQL Statement: INSERT INTO STG_IS_PROJ (IS_PROJ_NAME,IS_PROJ_ABBREV,IS_PROJ_DESC,IS_PROJ_LOC,EM_ACCESS_ID,IS_REPOSITORY_GUID,EM_CREATE_DATE,IS_PROJ_GUID,EM_MODIF_DATE,EM_HIDDEN_ID,EM_OWNER_GUID,IS_PROJ_VER,EM_DELETION_DATE) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?).
For this sample error, the parameter 3 is related to the column IS_PROJ_DESC from the STG_IS_PROJ table. This column is limited to 255 characters as per the table definition. Also, the Project description field in Strategy Developer is restricted to allow only 255 characters.
CAUSEIf the project description (or any field referred to in the error message) occupies 255 characters (or a length as defined for that field) or close to 255 characters but contains special characters (non-English characters), it is possible for the character to take up more than 1 byte to store it on the database and exceed the limit if the NLS_LENGTH_SEMANTICS is set to use BYTE instead of CHAR. Refer to
this link for more information regarding this setting.
ACTIONIf it is an option to change the NLS_LENGTH_SEMANTICS on the database to CHAR instead of BYTE, this can be altered. With this change, even though there are Unicode characters, they would be counted as 1 character (as opposed to multiple bytes). Alternately, use fewer characters in the description considering the conversion to Unicode or avoid the use of special characters. KB439235
