Subject | |
---|---|
Author | Edwin A. Epstein, III |
Post date | 2005-02-23T16:57:34Z |
Arithmatic exception, numeric overflow, or string truncation. One of my
favorites.
This was working, and still is working in another database. I made a meta
data backup and copied it to another linux sever. Now the after insert
trigger which does an insert on a table generates this error.
The 2 servers running side by side with the same code do not act the same
way. Both are identical hardware, identical operating systems, Firebird
1.5, and running the same database, just different data pumped in from a
previous database.
I am inserting 5 values into a table:
INSERT INTO TRACKING(TRACKING_TYPE_ID,T1,T2,T3)
VALUES(3,NEW.H_ABBREV,NEW.H_DESCRIPTION,NEW.PARENT_ID);
This is the DDL for that table:
RECREATE TABLE TRACKING
(
TRID INTEGER NOT NULL,
TRACKING_DATE TIMESTAMP DEFAULT
CURRENT_TIMESTAMP,
TRACKING_NOTES BLOB SUB_TYPE 1 SEGMENT
SIZE 80 CHARACTER SET ASCII,
TRACKING_TYPE_ID INTEGER,
T1 VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
T2 VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
T3 VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
T4 VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
T5 VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
T6 VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
T7 VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
T8 VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
T9 VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
T10 VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
T11 VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
T12 VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
T13 VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
T14 VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
T15 BLOB SUB_TYPE 1 SEGMENT
SIZE 80 CHARACTER SET ASCII,
FILE_NAME VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
FILE_MD5 VARCHAR( 32) CHARACTER SET
ASCII COLLATE ASCII,
FILE_LIB_ID INTEGER,
REC_AMOUNT INTEGER,
TAG_ID_1 INTEGER,
TAG_ID_2 INTEGER,
H_ABBREV VARCHAR( 3) CHARACTER SET
ASCII COLLATE ASCII,
LEAD_TRACKING_ID VARCHAR( 10) CHARACTER SET
ASCII COLLATE ASCII,
UPDATED SMALLINT DEFAULT 0,
USER_NAME VARCHAR( 50) CHARACTER SET
ASCII DEFAULT USER COLLATE ASCII
);
update rdb$relations set rdb$description = ' ' where rdb$relation_name =
'TRACKING';
Now inserting the values (3,'XXX','XTest',0) generates an error. I have
tried different values of course, all integers, all varchars, no success.
Any Ideas?
favorites.
This was working, and still is working in another database. I made a meta
data backup and copied it to another linux sever. Now the after insert
trigger which does an insert on a table generates this error.
The 2 servers running side by side with the same code do not act the same
way. Both are identical hardware, identical operating systems, Firebird
1.5, and running the same database, just different data pumped in from a
previous database.
I am inserting 5 values into a table:
INSERT INTO TRACKING(TRACKING_TYPE_ID,T1,T2,T3)
VALUES(3,NEW.H_ABBREV,NEW.H_DESCRIPTION,NEW.PARENT_ID);
This is the DDL for that table:
RECREATE TABLE TRACKING
(
TRID INTEGER NOT NULL,
TRACKING_DATE TIMESTAMP DEFAULT
CURRENT_TIMESTAMP,
TRACKING_NOTES BLOB SUB_TYPE 1 SEGMENT
SIZE 80 CHARACTER SET ASCII,
TRACKING_TYPE_ID INTEGER,
T1 VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
T2 VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
T3 VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
T4 VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
T5 VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
T6 VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
T7 VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
T8 VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
T9 VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
T10 VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
T11 VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
T12 VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
T13 VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
T14 VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
T15 BLOB SUB_TYPE 1 SEGMENT
SIZE 80 CHARACTER SET ASCII,
FILE_NAME VARCHAR( 255) CHARACTER SET
ASCII COLLATE ASCII,
FILE_MD5 VARCHAR( 32) CHARACTER SET
ASCII COLLATE ASCII,
FILE_LIB_ID INTEGER,
REC_AMOUNT INTEGER,
TAG_ID_1 INTEGER,
TAG_ID_2 INTEGER,
H_ABBREV VARCHAR( 3) CHARACTER SET
ASCII COLLATE ASCII,
LEAD_TRACKING_ID VARCHAR( 10) CHARACTER SET
ASCII COLLATE ASCII,
UPDATED SMALLINT DEFAULT 0,
USER_NAME VARCHAR( 50) CHARACTER SET
ASCII DEFAULT USER COLLATE ASCII
);
update rdb$relations set rdb$description = ' ' where rdb$relation_name =
'TRACKING';
Now inserting the values (3,'XXX','XTest',0) generates an error. I have
tried different values of course, all integers, all varchars, no success.
Any Ideas?