Variabler size mismatch
Walter Lucas III
whl3@nwths.com
Mon, 16 Aug 1999 13:44:02 -0700
This is a multi-part message in MIME format.
------=_NextPart_000_0006_01BEE7ED.663705E0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hey guys,
This is Walter at NWTHS again. We now have Axiant running, the Oracle =
database in place and accessed, and are converting everything we can. =
Life is good.
"And now for something completely different..."
We've been pulling data off an HP mainframe in the form of portable =
subfiles and loaded our Oracle databases. This was working well until I =
started loading dates.
The error I get is "VARIABLE SIZE MISMATCH." It then list the column =
and the name of my field. Originally, I loaded the fields as strictly =
date using the default on the mainframe. Then I built new fields with =
the CENTURY INCLUDED option and passed those.
When neither of these worked, I handled the field builds on the Axiant =
size first setting the value to a zoned number, then a date, then a date =
with the century included. All had the same result.
I've read all the help and books on both systems. I don't know if this =
is a Cognos or Oracle issue. The data fields in Axiant are sized as 8. =
The Oracle database shows the field to be a date field, but gives no =
indication of size.
Have any of you seen this error? And if you have what did you have to =
do to fix it? More importantly, where did you find the information you =
needed to fix it? I'm having trouble finding in-depth documentation on =
a variety of problems.
Thank you,
Walter Lucas
Applications programmer
Northwest Texas Hospitals
Amarillo, Texas
------=_NextPart_000_0006_01BEE7ED.663705E0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
Hey guys,
This is Walter at NWTHS again. =
We now have=20
Axiant running, the Oracle database in place and accessed, and are =
converting=20
everything we can. Life is good.
"And now for something =
completely=20
different..."
We've been pulling data off an HP =
mainframe in=20
the form of portable subfiles and loaded our Oracle databases. =
This was=20
working well until I started loading dates.
The error I get is "VARIABLE =
SIZE=20
MISMATCH." It then list the column and the name of my =
field. =20
Originally, I loaded the fields as strictly date using the default on =
the=20
mainframe. Then I built new fields with the CENTURY INCLUDED =
option and=20
passed those.
When neither of these worked, I =
handled the=20
field builds on the Axiant size first setting the value to a zoned =
number, then=20
a date, then a date with the century included. All had the same=20
result.
I've read all the help and books on =
both=20
systems. I don't know if this is a Cognos or Oracle issue. =
The data=20
fields in Axiant are sized as 8. The Oracle database shows the =
field to be=20
a date field, but gives no indication of size.
Have any of you seen this =
error? And if=20
you have what did you have to do to fix it? More importantly, =
where did=20
you find the information you needed to fix it? I'm having trouble =
finding=20
in-depth documentation on a variety of problems.
Thank you,
Walter Lucas
Applications programmer
Northwest Texas =
Hospitals
Amarillo, =
Texas