LSH Datatype Limits To Avoid Errors Like ORA-910 "specified length too long for its datatype"
(Doc ID 2197181.1)
Last updated on MARCH 22, 2019
Applies to:Oracle Life Sciences Data Hub - Version 2.4.6 and later
Information in this document applies to any platform.
The Datatypes in LSH depend on Database limits. If these are exceeded, you may hit errors like ORA-910 "specified length too long for its datatype".
The example below reproduces when Installing a Load Set where varchar2 column value is larger than the maximum of 4000:
Apply similar steps to Smoke Test "2.24 Create a SAS Load Set", but using a sas7bdat file where a table has a VARCHAR2 column length larger than 4000:
1. Go to LSH development Work Area
2. Create new Load Set with SAS Adapter Type and create Table Descriptor using sas7bdat file with a VARCHAR2 column length larger than 4000.
3. Create Table Instance from existing Table Descriptor. It will create a column DESCRIPTION as VARCHAR2 (4005)
4. Install the Load Set. LSH displays:
Error during Workarea Install : There are errors during OWB deployment. See install log for details.
a) Per OWB log:
2016/10/10-22:45:29-PDT [CDR_RTREPOS.CDR_RTREPOS] java.sql.SQLException: ORA-00910: specified length too long for its datatype
and then, as consequence, the table cannot be created and it displays:
2016/10/10-22:45:29-PDT [CDR_RTREPOS.CDR_RTREPOS] java.sql.SQLException: ORA-00942: table or view does not exist
In the example above, LSH tries to create a database table and then, hits the Database Datatype limits. Per <NOTE:18506.1> OERR: ORA-910 "specified length too long for its datatype"
Error: ORA-00910 specified length too long for its datatype
Cause: for datatypes CHAR and RAW, the length specified was > 2000; otherwise, the length specified was > 4000.
Action: use a shorter length or switch to a datatype permitting a longer length such as a VARCHAR2, LONG CHAR, or LONG RAW
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|