EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB10992: "ORA-01401: inserted value too large for column" error message appears when performing certain operations against a MicroStrategy metadata in Oracle.


Community Admin

• Strategy


This article describes an error "ORA-01401: inserted value too large for column" when performing certain operations against a MicroStrategy metadata in Oracle.

Users encounter the following error message when performing certain operations against a Strategy metadata in Oracle:
 
ORA-01401: inserted value too large for column
An example of such an operation is the copying of objects into a project in an Oracle metadata using Strategy Object Manager 7.x. Upon further investigation, it is found that the error occurs during an INSERT operation into the DEFINITION column of the DSSMDOBJDEFN table.
 
A likely reason is that the metadata was created using the Single-Byte Character Set (SBCS) script for Oracle while the character set encoding of the database is Unicode. The metadata creation scripts are located in the Common Files\Strategy folder. The SBCS script for Oracle is md7orcl.sql and the Unicode script is md7orclutf8.sql. The DEFINITION column is VARCHAR2(600) in the SBCS script while it is VARCHAR2(1800) in the Unicode script. The presence of certain characters (such as £ or €) may result in the data length being exceeded for the DEFINITION column as they would probably be counted as multi-byte characters on the database, thus resulting in this error message.
 
Users should check the character set encoding of the database where the metadata tables are stored. If it is Unicode, then the md7orclutf8.sql script should be used for metadata creation. By default, the Strategy configuration wizard uses the SBCS script.
 
Metadata Modification:
WARNING:
Manually editing values in the Strategy Metadata incorrectly may cause serious, project-wide problems that may make your project unusable. Since these are user-initiated changes, they are not covered by any Strategy warranty. Users are strongly encouraged to backup Metadata prior to any alteration.
 
Third Party Software Installation:
WARNING:
The third-party product(s) discussed in this technical note is manufactured by vendors independent of Strategy. Strategy makes no warranty, express, implied or otherwise, regarding this product, including its performance or reliability.
 


Comment

0 comments

Details

Knowledge Article

Published:

June 2, 2017

Last Updated:

June 2, 2017