Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
A user running dbimport on a different host (same IDS version) hit "1204 - Invalid year in date" and suspected an environment setting. The answer: the DBDATE environment variable must match the one used when the data was exported — export the correct DBDATE before running dbimport. The poster confirmed this solved it. Art Kagel also cautioned to check that the unload file doesn't contain a genuinely invalid date, since host languages (4GL, ESQL/C, Java) can store bad binary date values. The IIUG FAQ was suggested for similar common issues.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Hi everyone,
Using dbimport utility stops with this error:
*** put loadcur
1204 - Invalid year in date
The error seems to be related to something about checking settings of the TERM
environment variable correctly.
This happens when restoring in a different host (same IDS server version).
How to work arround this?
Thanks in advance,
Hernando.
↪ replying to HERNANDO DUQUE
Jack Parker — — source: IIUG Forums & Mailing Lists
Ensure that your $DBDATE setting is the same on both machines.
cheers
j.
On Apr 1, 2011, at 1:19 PM, HERNANDO DUQUE wrote:
> Hi everyone,=20
>=20
> Using dbimport utility stops with this error:=20
>=20
> *** put loadcur=20
> 1204 - Invalid year in date=20
>=20
> The error seems to be related to something about checking settings of =
the TERM=20
> environment variable correctly.=20
>=20
> This happens when restoring in a different host (same IDS server =
version).=20
>=20
> How to work arround this?=20
>=20
> Thanks in advance,=20
>=20
> Hernando.=20
>=20
>=20
> =
**************************************************************************=
*****=20
> Forum Note: Use "Reply" to post a response in the discussion forum.=20=
>=20
You should verify that the data file doesn't actually contain an invalid
date. With a DATE type column, it is possible using a host language like
4GL, Java, or ESQL/C to insert an invalid date if it is inserted as a binary
value.
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions and
do not reflect on my employer, Advanced DataTools, the IIUG, nor any other
organization with which I am associated either explicitly, implicitly, or by
inference. Neither do those opinions reflect those of other individuals
affiliated with any entity with which I am affiliated nor those of the
entities themselves.
On Fri, Apr 1, 2011 at 1:19 PM, HERNANDO DUQUE <hduquec@hotmail.com> wrote:
> Hi everyone,
>
> Using dbimport utility stops with this error:
>
> *** put loadcur
> 1204 - Invalid year in date
>
> The error seems to be related to something about checking settings of the
> TERM
> environment variable correctly.
>
> This happens when restoring in a different host (same IDS server version).
>
> How to work arround this?
>
> Thanks in advance,
>
> Hernando.
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--20cf307f3292eb7207049fdf03f5
jack,
Thank You. I did not think it was that easy. I wonder if there is some FAQ for
newbies where one can find solution for these common issues.
Hernando.
↪ replying to HERNANDO
Jack Parker — — source: IIUG Forums & Mailing Lists
There is an FAQ which you can download from www.iiug.org. But the nice =
people in this group (except for Obnoxio) will always be happy to answer =
questions. Of course half the time I get the answer wrong, but hey, =
it's the interweb.
j.
On Apr 1, 2011, at 1:57 PM, HERNANDO DUQUE wrote:
> jack,=20
>=20
> Thank You. I did not think it was that easy. I wonder if there is some =
FAQ for=20
> newbies where one can find solution for these common issues.=20
>=20
> Hernando.=20
>=20
>=20
> =
**************************************************************************=
*****=20
> Forum Note: Use "Reply" to post a response in the discussion forum.=20=
>=20
HI,
First, "export DBDATE=<whatever is your date format>", in your environment
from where you start the dbimport. After exporting the DBDATE environment,
then start the dbimport.
Neville.
On Fri, Apr 1, 2011 at 10:49 PM, HERNANDO DUQUE <hduquec@hotmail.com> wrote:
> Hi everyone,
>
> Using dbimport utility stops with this error:
>
> *** put loadcur
> 1204 - Invalid year in date
>
> The error seems to be related to something about checking settings of the
> TERM
> environment variable correctly.
>
> This happens when restoring in a different host (same IDS server version).
>
> How to work arround this?
>
> Thanks in advance,
>
> Hernando.
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--
Warm Regards,
Neville Monteiro.
--001517576e940516b004a0248cec
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.