date +%z
-0500

I don't know about the server's clock but my guess would be it doesn't use
UTC.

Using the epoch time in the import file causes the imported date to be
correct.

I'm now importing data that looks like this:

Process,ProcessStatus, Started, Completed, Records Imported, Records
Failed,File to Attach
Load_SAP_Data,Success,1204301650,02/29/2008 11:15:00,0,1,/etc/testfile

The "1204301650" comes in as 2/29/2008 11:14:10 AM which is correct.
The "02/29/2008 11:15:00" comes in as 2/29/2008 6:15:00 AM which isn't.

Strange behavior, this.


J.T. Shyman
Column Technologies

 
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Misi Mladoniczky
Sent: Friday, February 29, 2008 9:16 AM
To: [email protected]
Subject: Re: arimport not importing dates properly

Hi,

The conversion is done within the arimportcmd-binary without any
connection to either database or AR Server. The ARDATE-environment
variable may be used by arimportcmds to parse the date, I think.

What does "date +%z" give you if you run it in the shell before you run
"arimportcmd"?

The "date +%s" will give you the current time in number of seconds since
1970. Run that in the shell. Import a file with a time corresponding to
the current time, and export the resulting record in arx-format. Compare
the resulting number with the one reported by "date +%s". Does it make
sence?

Have you tried to set your TZ-variable? For example to
"America/Whitehorse". I guess you will find the valid settings under the
directory /usr/share/zoneinfo/America/.

Does your servers clock use UTC-time or local-time?

        Best Regards - Misi, RRR AB, http://rrr.se

> Misi,
>
> Thanks for the reply. However, the timezone on my workstation is the same
> as the server, EST, and the import works fine if I run it from my
> workstation or if I try the exact same import on a windows/sql system. I'm
> wondering if the dbtimezone of the Oracle database, which is set to
> +00:00, and the sessiontimezone on the Oracle database, which is set to
> -05:00, is what is causing this behavior. The strange part is that would
> mean arimportcmd is ignoring the sessiontimezone and is only using the
> dbtimezone.
>
> J.T. Shyman
> Column Technologies
> 404-242-5407
> [EMAIL PROTECTED]
>
> ________________________________
>
> From: Action Request System discussion list(ARSList) on behalf of Misi
> Mladoniczky
> Sent: Fri 2/29/2008 5:19 AM
> To: [email protected]
> Subject: Re: arimport not importing dates properly
>
>
>
> Hi,
>
> The timezone on the server is not important.
>
> The important thing is the timezone on the "client" where you perform the
> import, and the "client" where you view the resulting date/time. Could
> there be a discrepancy between the timezones between these two "clients"?
>
>         Best Regards - Misi, RRR AB, http://www.rrr.se
>
> Products from RRR Scandinavia:
> * RRR|License - Not enough Remedy licenses? Save money by optimizing.
> * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
> * RRR|Translator - Manage and automate your language translations.
> Find these products, and many free tools and utilities, at http://rrr.se.
>
>> AR 7.0.1 Patch 005 on RedHat Linux
>>
>>
>>
>> We've got a script that uses arimport to import records into a form that
>> has
>> two date fields on it. We've tried to import the data several times and
>> the
>> dates keep coming in -5 hours from the time they are set for.
>>
>>
>>
>> For example, a data file that contains:
>>
>>
>>
>> Start_time, end_time
>>
>> 02/28/2008 16:00,02/28/2008 16:00
>>
>>
>>
>> Will import fine but show up in the form at: 2/28/2008 11:00
>>
>>
>>
>> We've tried various other formats including:
>>
>>
>>
>> "02/28/2008 16:00","02/28/2008 16:00"
>>
>> 02/28/2008 4:00 PM, 02/28/2008 4:00 PM
>>
>> "2/28/2008 4:00 PM","2/28/2008 4:00 PM"
>>
>>
>>
>> We've even tried pushing this data through character fields on a staging
>> form and then using push fields to get it into the desired form's date
>> fields with the same result.
>>
>>
>>
>> The strange part is that the records import as expected when we user
>> Remedy
>> Import from a windows client machine. Just not from the server.
>>
>>
>>
>> The time and time zone are set correctly on the server as is the "Server
>> Time Zone" in Remedy.
>>
>>
>>
>> I've duplicated this on another Linux server running 7.1 patch 1.
>> However,
>> this works as expected using arimportcmd on a windows server running AR
>> 7.0.1 Patch 5.
>>
>>
>>
>> --- J.T. Shyman
>>
>>
>>
>>
>>
>>
>>
____________________________________________________________________________
___
>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
>> Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
>>
>> --
>> This message was scanned by ESVA and is believed to be clean.
>>
>>
>
>
____________________________________________________________________________
___
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
>
>
>
>
____________________________________________________________________________
___
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
>
> --
> This message was scanned by ESVA and is believed to be clean.
>
>

____________________________________________________________________________
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Reply via email to