Dbimport date import problem
A user moving a database from Informix SE 7.25 on SCO to IDS 9.21 on Windows 2000 hit "invalid month in date" during dbimport; the exported dates are in DD/MM/YYYY form and DBDATE was set to DMY4/ via setnet32, yet importing the same files into SE 7.25 on Windows worked. Suggestions included temporarily using MDY4, ensuring DBDATE is set before the engine starts, checking that DBDATE matches on both the export and import sides, and setting DBDATE in the Windows shell/system environment rather than setnet32. None of the tried suggestions worked and no resolution is recorded in the thread.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Hi,
Sorry for this basic question.
I'm importing a db into IDS 9.21 on Windows 2000. The dbexport was
originally done on SCO from Informix SE 7.25.
I get "error invalid month in date " when doing the dbimport (dbimport mydb
-d mydbspace)
DBDATE is set to DMY4/ in setnet32 and the dates are of form the 23/12/2003.
Importing the same dbexport into SE 7.25 on Windows works OK. What am I
doing wrong?
Any pointers gratefully received. Thanks.
Michael
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.543 / Virus Database: 337 - Release Date: 21/11/2003
Henry,
Tried this - still the same. It's as if IDS is simply not seeing the DBDATE
variable.
-----Original Message-----
From: Ardila, Henry (EDS Operations (AdSC))
[mailto:henry.ardila-eds@eds.com]
Sent: 24 November 2003 22:33
To: 'Michael Mayne'
Subject: RE: Dbimport date import problem [2233]
Set Dbdate MDY4 and after you finish the import change to DMY4, dates are
stored in Informix as a Julian date, it means as a number the dbdate is the
displaying format.
Try to see if this work.
Reg,
Henry Ardila
EDS - DBA Support
( Phone:61-8-84641609)
henry.ardila-eds@eds.com
-----Original Message-----
From: forum.subscriber@iiug.org [mailto:forum.subscriber@iiug.org] On Behalf
Of Michael Mayne
Sent: Tuesday, 25 November 2003 12:33 AM
To: ids@iiug.org
Subject: Dbimport date import problem [2233]
Hi,
Sorry for this basic question.
I'm importing a db into IDS 9.21 on Windows 2000. The dbexport was
originally done on SCO from Informix SE 7.25.
I get "error invalid month in date " when doing the dbimport (dbimport mydb
-d mydbspace) DBDATE is set to DMY4/ in setnet32 and the dates are of form
the 23/12/2003.
Importing the same dbexport into SE 7.25 on Windows works OK. What am I
doing wrong? Any pointers gratefully received. Thanks.
Michael
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.543 / Virus Database: 337 - Release Date: 21/11/2003
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.543 / Virus Database: 337 - Release Date: 21/11/2003
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.543 / Virus Database: 337 - Release Date: 21/11/2003
Hi, I'd really appreciate it someone could just point me in the right direction: I'm sure I'm just making a simple mistake somewhere. Thanks Michael
Not sure about windows, but on UNIX, DBDATE needs to be set when the
engine starts up.
> -----Original Message-----
> From: forum.subscriber@iiug.org
> [mailto:forum.subscriber@iiug.org] On Behalf Of Michael Mayne
> Sent: 25 November 2003 06:23
> To: ids@iiug.org
> Subject: RE: Dbimport date import problem [2243]
>
>
> Henry,
> Tried this - still the same. It's as if IDS is simply not
> seeing the DBDATE variable.
>
> -----Original Message-----
> From: Ardila, Henry (EDS Operations (AdSC))
> [mailto:henry.ardila-eds@eds.com]
> Sent: 24 November 2003 22:33
> To: 'Michael Mayne'
> Subject: RE: Dbimport date import problem [2233]
>
>
> Set Dbdate MDY4 and after you finish the import change to
> DMY4, dates are stored in Informix as a Julian date, it means
> as a number the dbdate is the displaying format.
>
> Try to see if this work.
>
> Reg,
>
>
> Henry Ardila
> EDS - DBA Support
>
> ( Phone:61-8-84641609)
> henry.ardila-eds@eds.com
>
>
>
> -----Original Message-----
> From: forum.subscriber@iiug.org
> [mailto:forum.subscriber@iiug.org] On Behalf > Of Michael Mayne
>
> Sent: Tuesday, 25 November 2003 12:33 AM
> To: ids@iiug.org
> Subject: Dbimport date import problem [2233]
>
>
> Hi,
> Sorry for this basic question.
> I'm importing a db into IDS 9.21 on Windows 2000. The
> dbexport was originally done on SCO from Informix SE 7.25.
>
> I get "error invalid month in date " when doing the dbimport
> (dbimport mydb -d mydbspace) DBDATE is set to DMY4/ in
> setnet32 and the dates are of form the 23/12/2003.
>
> Importing the same dbexport into SE 7.25 on Windows works OK.
> What am I doing wrong? Any pointers gratefully received. Thanks.
>
> Michael
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.543 / Virus Database: 337 - Release Date: 21/11/2003
>
>
>
>
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.543 / Virus Database: 337 - Release Date: 21/11/2003
>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.543 / Virus Database: 337 - Release Date: 21/11/2003
>
>
>
>
>--------------------------------------------------------
Eurolife Assurance Group plc, Eurolife House, 16 St John Street, London, EC1M
4NT
Tel: 020-7454 1151 Fax: 020-7454 1277
www.eurolife.co.uk
Registered in England, number 2471313
This message (and any associated files) is intended only for the use of the
individual or entity to which it is addressed and may contain information that
is confidential, subject to copyright or constitutes a trade secret. If you
are not the intended recipient you are hereby notified that any dissemination,
copying or distribution of this message, or files associated with this
message, is strictly prohibited. If you have received this message in error,
please notify us immediately by replying to the message and deleting it from
your computer. Messages sent to and from us may be monitored.
Internet communications cannot be guaranteed to be secure or error-free as
information could be intercepted, corrupted, lost, destroyed, arrive late or
incomplete, or contain viruses. Therefore, we do not accept responsibility for
any errors or omissions that are present in this message, or any attachment,
that have arisen as a result of e-mail transmission. If verification is
required, please request a hard-copy version. Any views or opinions presented
are solely those of the author and do not necessarily represent those of the
company.
Scott,
It is; still doesn't seem to make any difference.
-----Original Message-----
From: Scott O'Rourke [mailto:SORourke@eurolife.co.uk]
Sent: 25 November 2003 09:12
To: Michael Mayne; ids@iiug.org
Subject: RE: Dbimport date import problem [2243]
Not sure about windows, but on UNIX, DBDATE needs to be set when the
engine starts up.
> -----Original Message-----
> From: forum.subscriber@iiug.org
> [mailto:forum.subscriber@iiug.org] On Behalf Of Michael Mayne
> Sent: 25 November 2003 06:23
> To: ids@iiug.org
> Subject: RE: Dbimport date import problem [2243]
>
>
> Henry,
> Tried this - still the same. It's as if IDS is simply not
> seeing the DBDATE variable.
>
> -----Original Message-----
> From: Ardila, Henry (EDS Operations (AdSC))
> [mailto:henry.ardila-eds@eds.com]
> Sent: 24 November 2003 22:33
> To: 'Michael Mayne'
> Subject: RE: Dbimport date import problem [2233]
>
>
> Set Dbdate MDY4 and after you finish the import change to
> DMY4, dates are stored in Informix as a Julian date, it means
> as a number the dbdate is the displaying format.
>
> Try to see if this work.
>
> Reg,
>
>
> Henry Ardila
> EDS - DBA Support
>
> ( Phone:61-8-84641609)
> henry.ardila-eds@eds.com
>
>
>
> -----Original Message-----
> From: forum.subscriber@iiug.org
> [mailto:forum.subscriber@iiug.org] On Behalf > Of Michael Mayne
>
> Sent: Tuesday, 25 November 2003 12:33 AM
> To: ids@iiug.org
> Subject: Dbimport date import problem [2233]
>
>
> Hi,
> Sorry for this basic question.
> I'm importing a db into IDS 9.21 on Windows 2000. The
> dbexport was originally done on SCO from Informix SE 7.25.
>
> I get "error invalid month in date " when doing the dbimport
> (dbimport mydb -d mydbspace) DBDATE is set to DMY4/ in
> setnet32 and the dates are of form the 23/12/2003.
>
> Importing the same dbexport into SE 7.25 on Windows works OK.
> What am I doing wrong? Any pointers gratefully received. Thanks.
>
> Michael
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.543 / Virus Database: 337 - Release Date: 21/11/2003
>
>
>
>
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.543 / Virus Database: 337 - Release Date: 21/11/2003
>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.543 / Virus Database: 337 - Release Date: 21/11/2003
>
>
>
>
>--------------------------------------------------------
Eurolife Assurance Group plc, Eurolife House, 16 St John Street, London,
EC1M 4NT
Tel: 020-7454 1151 Fax: 020-7454 1277
www.eurolife.co.uk
Registered in England, number 2471313
This message (and any associated files) is intended only for the use of the
individual or entity to which it is addressed and may contain information
that is confidential, subject to copyright or constitutes a trade secret. If
you are not the intended recipient you are hereby notified that any
dissemination, copying or distribution of this message, or files associated
with this message, is strictly prohibited. If you have received this message
in error, please notify us immediately by replying to the message and
deleting it from your computer. Messages sent to and from us may be
monitored.
Internet communications cannot be guaranteed to be secure or error-free as
information could be intercepted, corrupted, lost, destroyed, arrive late or
incomplete, or contain viruses. Therefore, we do not accept responsibility
for any errors or omissions that are present in this message, or any
attachment, that have arisen as a result of e-mail transmission. If
verification is required, please request a hard-copy version. Any views or
opinions presented are solely those of the author and do not necessarily
represent those of the company.
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.543 / Virus Database: 337 - Release Date: 21/11/2003
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.543 / Virus Database: 337 - Release Date: 21/11/2003
Michael,
Is DBDATE set with the same value on the both servers, on SCO (before
starting dbexport) & WIN (before starting dbimport) ?
Please show us how is DBDATE set on both machines.
Elena
"Michael Mayne"
<michael@jadegrou To: ids@iiug.org
p.co.uk> cc:
Sent by: Subject: RE: Dbimport date import problem [2246]
forum.subscriber@
iiug.org
11/25/03 12:25 PM
Scott,
It is; still doesn't seem to make any difference.
-----Original Message-----
From: Scott O'Rourke [mailto:SORourke@eurolife.co.uk]
Sent: 25 November 2003 09:12
To: Michael Mayne; ids@iiug.org
Subject: RE: Dbimport date import problem [2243]
Not sure about windows, but on UNIX, DBDATE needs to be set when the
engine starts up.
> -----Original Message-----
> From: forum.subscriber@iiug.org
> [mailto:forum.subscriber@iiug.org] On Behalf Of Michael Mayne
> Sent: 25 November 2003 06:23
> To: ids@iiug.org
> Subject: RE: Dbimport date import problem [2243]
>
>
> Henry,
> Tried this - still the same. It's as if IDS is simply not
> seeing the DBDATE variable.
>
> -----Original Message-----
> From: Ardila, Henry (EDS Operations (AdSC))
> [mailto:henry.ardila-eds@eds.com]
> Sent: 24 November 2003 22:33
> To: 'Michael Mayne'
> Subject: RE: Dbimport date import problem [2233]
>
>
> Set Dbdate MDY4 and after you finish the import change to
> DMY4, dates are stored in Informix as a Julian date, it means
> as a number the dbdate is the displaying format.
>
> Try to see if this work.
>
> Reg,
>
>
> Henry Ardila
> EDS - DBA Support
>
> ( Phone:61-8-84641609)
> henry.ardila-eds@eds.com
>
>
>
> -----Original Message-----
> From: forum.subscriber@iiug.org
> [mailto:forum.subscriber@iiug.org] On Behalf > Of Michael Mayne
>
> Sent: Tuesday, 25 November 2003 12:33 AM
> To: ids@iiug.org
> Subject: Dbimport date import problem [2233]
>
>
> Hi,
> Sorry for this basic question.
> I'm importing a db into IDS 9.21 on Windows 2000. The
> dbexport was originally done on SCO from Informix SE 7.25.
>
> I get "error invalid month in date " when doing the dbimport
> (dbimport mydb -d mydbspace) DBDATE is set to DMY4/ in
> setnet32 and the dates are of form the 23/12/2003.
>
> Importing the same dbexport into SE 7.25 on Windows works OK.
> What am I doing wrong? Any pointers gratefully received. Thanks.
>
> Michael
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.543 / Virus Database: 337 - Release Date: 21/11/2003
>
>
>
>
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.543 / Virus Database: 337 - Release Date: 21/11/2003
>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.543 / Virus Database: 337 - Release Date: 21/11/2003
>
>
>
>
>--------------------------------------------------------
Eurolife Assurance Group plc, Eurolife House, 16 St John Street, London,
EC1M 4NT
Tel: 020-7454 1151 Fax: 020-7454 1277
www.eurolife.co.uk
Registered in England, number 2471313
This message (and any associated files) is intended only for the use of the
individual or entity to which it is addressed and may contain information
that is confidential, subject to copyright or constitutes a trade secret.
If
you are not the intended recipient you are hereby notified that any
dissemination, copying or distribution of this message, or files associated
with this message, is strictly prohibited. If you have received this
message
in error, please notify us immediately by replying to the message and
deleting it from your computer. Messages sent to and from us may be
monitored.
Internet communications cannot be guaranteed to be secure or error-free as
information could be intercepted, corrupted, lost, destroyed, arrive late
or
incomplete, or contain viruses. Therefore, we do not accept responsibility
for any errors or omissions that are present in this message, or any
attachment, that have arisen as a result of e-mail transmission. If
verification is required, please request a hard-copy version. Any views or
opinions presented are solely those of the author and do not necessarily
represent those of the company.
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.543 / Virus Database: 337 - Release Date: 21/11/2003
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.543 / Virus Database: 337 - Release Date: 21/11/2003
Not necessary. You can set DBDATE for client and make use of it without
having to start the server.
As for Windows, I would suggest again to set the DBDATE in the shell or the
system environment settings, instead of setnet32.
set DBDATE=dmy4/
It should work with setnet32 also, try higher versions.
Thanks and Regards,
Gaurav
"Scott O'Rourke"
<SORourke@eurolif To: ids@iiug.org
e.co.uk> cc:
Sent by: Subject: RE: Dbimport date import problem [2245]
forum.subscriber@
iiug.org
11/25/03 03:15 AM
Not sure about windows, but on UNIX, DBDATE needs to be set when the
engine starts up.
> -----Original Message-----
> From: forum.subscriber@iiug.org
> [mailto:forum.subscriber@iiug.org] On Behalf Of Michael Mayne
> Sent: 25 November 2003 06:23
> To: ids@iiug.org
> Subject: RE: Dbimport date import problem [2243]
>
>
> Henry,
> Tried this - still the same. It's as if IDS is simply not
> seeing the DBDATE variable.
>
> -----Original Message-----
> From: Ardila, Henry (EDS Operations (AdSC))
> [mailto:henry.ardila-eds@eds.com]
> Sent: 24 November 2003 22:33
> To: 'Michael Mayne'
> Subject: RE: Dbimport date import problem [2233]
>
>
> Set Dbdate MDY4 and after you finish the import change to
> DMY4, dates are stored in Informix as a Julian date, it means
> as a number the dbdate is the displaying format.
>
> Try to see if this work.
>
> Reg,
>
>
> Henry Ardila
> EDS - DBA Support
>
> ( Phone:61-8-84641609)
> henry.ardila-eds@eds.com
>
>
>
> -----Original Message-----
> From: forum.subscriber@iiug.org
> [mailto:forum.subscriber@iiug.org] On Behalf > Of Michael Mayne
>
> Sent: Tuesday, 25 November 2003 12:33 AM
> To: ids@iiug.org
> Subject: Dbimport date import problem [2233]
>
>
> Hi,
> Sorry for this basic question.
> I'm importing a db into IDS 9.21 on Windows 2000. The
> dbexport was originally done on SCO from Informix SE 7.25.
>
> I get "error invalid month in date " when doing the dbimport
> (dbimport mydb -d mydbspace) DBDATE is set to DMY4/ in
> setnet32 and the dates are of form the 23/12/2003.
>
> Importing the same dbexport into SE 7.25 on Windows works OK.
> What am I doing wrong? Any pointers gratefully received. Thanks.
>
> Michael
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.543 / Virus Database: 337 - Release Date: 21/11/2003
>
>
>
>
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.543 / Virus Database: 337 - Release Date: 21/11/2003
>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.543 / Virus Database: 337 - Release Date: 21/11/2003
>
>
>
>
>--------------------------------------------------------
Eurolife Assurance Group plc, Eurolife House, 16 St John Street, London,
EC1M 4NT
Tel: 020-7454 1151 Fax: 020-7454 1277
www.eurolife.co.uk
Registered in England, number 2471313
This message (and any associated files) is intended only for the use of the
individual or entity to which it is addressed and may contain information
that is confidential, subject to copyright or constitutes a trade secret.
If you are not the intended recipient you are hereby notified that any
dissemination, copying or distribution of this message, or files associated
with this message, is strictly prohibited. If you have received this
message in error, please notify us immediately by replying to the message
and deleting it from your computer. Messages sent to and from us may be
monitored.
Internet communications cannot be guaranteed to be secure or error-free as
information could be intercepted, corrupted, lost, destroyed, arrive late
or incomplete, or contain viruses. Therefore, we do not accept
responsibility for any errors or omissions that are present in this
message, or any attachment, that have arisen as a result of e-mail
transmission. If verification is required, please request a hard-copy
version. Any views or opinions presented are solely those of the author and
do not necessarily represent those of the company.