Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 66644 invoked from network); 10 Apr 2006 18:44:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 10 Apr 2006 18:44:21 -0000 Received: (qmail 50995 invoked by uid 500); 10 Apr 2006 18:44:19 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 50965 invoked by uid 500); 10 Apr 2006 18:44:19 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 50951 invoked by uid 99); 10 Apr 2006 18:44:19 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Apr 2006 11:44:19 -0700 X-ASF-Spam-Status: No, hits=0.6 required=10.0 tests=HTML_MESSAGE,UPPERCASE_50_75 X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [129.80.22.146] (HELO sherman.stortek.com) (129.80.22.146) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Apr 2006 11:44:16 -0700 Received: from sherman.stortek.com (localhost [127.0.0.1]) by sherman.stortek.com (8.13.6/8.13.6) with ESMTP id k3AIhr2O025610 for ; Mon, 10 Apr 2006 12:43:53 -0600 (MDT) Received: from hq-exchbh01.louisville.stortek.com (hq-exchbh01.louisville.stortek.com [129.80.18.139]) by sherman.stortek.com (8.13.6/8.13.6) with ESMTP id k3AIhrbN025606 for ; Mon, 10 Apr 2006 12:43:53 -0600 (MDT) Received: from louisville.stortek.com ([129.80.18.182]) by hq-exchbh01.louisville.stortek.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 10 Apr 2006 12:43:52 -0600 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C65CCE.B6AA0049" Subject: syscs_util.syscs_import_data error Date: Mon, 10 Apr 2006 12:43:51 -0600 Message-ID: <10CE3EBC5991E24DA62327882F27989A01DE8A12@EXCHVS1.louisville.stortek.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: syscs_util.syscs_import_data error Thread-Index: AcZczrYie/X+KrYWTv6XWCzAcRo/pw== From: "McColley, William S" To: X-OriginalArrivalTime: 10 Apr 2006 18:43:52.0898 (UTC) FILETIME=[B6F22A20:01C65CCE] X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N This is a multi-part message in MIME format. ------_=_NextPart_001_01C65CCE.B6AA0049 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Anyone experienced this before? =20 table definition is: ij> create table INDIGO.ATTRIBUTE (ATTRIBUTE_ID SMALLINT NOT NULL , ATTRIBUTE_PARENT_ENTITY_ID SMALLINT NOT NULL, ATTRIBUTE_INTERNAL_NAME VARCHAR(50), ATTRIBUTE_EXTERNAL_NAME VARCHAR(50), ATTRIBUTE_MAX_WIDTH SMALLINT, ATTRIBUTE_EDITABLE SMALLINT, ATTRIBUTE_HAS_SELECTIONS SMALLINT, ATTRIBUTE_GLOBAL_SETTINGS_ID SMALLINT, ATTRIBUTE_LIST_ALLOWED SMALLINT, ATTRIBUTE_ENTITY_ID SMALLINT, ATTRIBUTE_IDENTIFIES_ENTITY SMALLINT, ATTRIBUTE_TYPE_ID SMALLINT, FOREIGN KEY(ATTRIBUTE_PARENT_ENTITY_ID) REFERENCES INDIGO.ENTITY(ENTITY_ID), FOREIGN KEY(ATTRIBUTE_GLOBAL_SETTINGS_ID)REFERENCES INDIGO.GLOBAL_SETTINGS(GLOBAL_SETTINGS_ID), FOREIGN KEY(ATTRIBUTE_ENTITY_ID)REFERENCES INDIGO.ENTITY(ENTITY_ID), FOREIGN KEY(ATTRIBUTE_TYPE_ID)REFERENCES INDIGO.ATTRIBUTE_TYPE(ATTRIBUTE_TYPE_ID),PRIMARY KEY(ATTRIBUTE_ID)) =20 input file, 1 record: /export/wsm/work_area/extract/data/05_attribute.dat2 =20 2;2;'alternatereadsallowed';'alternatereadsallowed';0;0;0;NULL;0;NULL;0; 2 =20 ij> call syscs_util.syscs_import_data ('INDIGO','ATTRIBUTE',null, null,'/export/wsm/work_area/extract/data/05_attribute.dat2',';',null,nul l,1); ERROR 38000: The exception 'SQL Exception: Invalid character string format for type SMALLINT.' was thrown while evaluating an expression. ERROR 22018: Invalid character string format for type SMALLINT. ij> =20 If I take the same string and wrap an insert statement around it: =20 ij> insert into INDIGO.ATTRIBUTE values (2,2,'alternatereadsallowed','alternatereadsallowed',0,0,0,NULL,0,NULL,0 ,2); =20 1 row inserted/updated/deleted ij> =20 This is occurring on about 10% of the tables I try to import =20 I can't see a reason for this operation to error - the data is in fact valid. Any help would be greatly appreciated. Scott McColley ------_=_NextPart_001_01C65CCE.B6AA0049 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

Anyone experienced this = before?

 

table definition is:

ij> create table = INDIGO.ATTRIBUTE

(ATTRIBUTE_ID SMALLINT NOT NULL = ,

ATTRIBUTE_PARENT_ENTITY_ID SMALLINT NOT = NULL,

ATTRIBUTE_INTERNAL_NAME = VARCHAR(50),

ATTRIBUTE_EXTERNAL_NAME = VARCHAR(50),

ATTRIBUTE_MAX_WIDTH = SMALLINT,

ATTRIBUTE_EDITABLE = SMALLINT,

ATTRIBUTE_HAS_SELECTIONS = SMALLINT,

ATTRIBUTE_GLOBAL_SETTINGS_ID = SMALLINT,

ATTRIBUTE_LIST_ALLOWED = SMALLINT,

ATTRIBUTE_ENTITY_ID = SMALLINT,

ATTRIBUTE_IDENTIFIES_ENTITY = SMALLINT,

ATTRIBUTE_TYPE_ID = SMALLINT,

FOREIGN KEY(ATTRIBUTE_PARENT_ENTITY_ID) REFERENCES INDIGO.ENTITY(ENTITY_ID),

FOREIGN KEY(ATTRIBUTE_GLOBAL_SETTINGS_ID)REFERENCES INDIGO.GLOBAL_SETTINGS(GLOBAL_SETTINGS_ID),

FOREIGN KEY(ATTRIBUTE_ENTITY_ID)REFERENCES INDIGO.ENTITY(ENTITY_ID),

FOREIGN KEY(ATTRIBUTE_TYPE_ID)REFERENCES = INDIGO.ATTRIBUTE_TYPE(ATTRIBUTE_TYPE_ID),PRIMARY KEY(ATTRIBUTE_ID))

 

input file, 1 record: = /export/wsm/work_area/extract/data/05_attribute.dat2

 

2;2;'alternatereadsallowed';'alternatereadsallowed';0;= 0;0;NULL;0;NULL;0;2

 

ij> call syscs_util.syscs_import_data ('INDIGO','ATTRIBUTE',null, null,'/export/wsm/work_area/extract/data/05_attribute.dat2',';',null,null= ,1);

ERROR 38000: The exception 'SQL Exception: Invalid = character string format for type SMALLINT.' was thrown while evaluating an = expression.

ERROR 22018: Invalid character string format for type SMALLINT.

ij>

 

If I take the same string and wrap an insert = statement around it:

 

ij> insert into INDIGO.ATTRIBUTE values (2,2,'alternatereadsallowed','alternatereadsallowed',0,0,0,NULL,0,NULL,0,= 2);

 

1 row = inserted/updated/deleted

ij>

 

This is occurring on about 10% of the tables I try to = import

 

I can’t see a reason for this operation to = error – the data is in fact valid.

Any help would be greatly = appreciated.

Scott McColley

------_=_NextPart_001_01C65CCE.B6AA0049--