Warnings...

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
Nagaraj
Premium Member
Premium Member
Posts: 383
Joined: Thu Nov 08, 2007 12:32 am
Location: Bangalore

Warnings...

Post by Nagaraj »

I am getting the below warnings, any idea what is this?

buffer(2),0: APT_BufferOperator warning: currentWriteTime <= lastWriteTime, 1254870770.10021 1254870770.47596
Nagaraj
Premium Member
Premium Member
Posts: 383
Joined: Thu Nov 08, 2007 12:32 am
Location: Bangalore

Post by Nagaraj »

Hint...: - The Job actually runs 12 hrs, which is correct according to the estimate.

Is this because of space issue?
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

"Hint"? It looks like the millisecond values aren't being returned correctly in this one case, or does this error refer to 2 entries spaced (just a bit more than) 12 hours apart?
Nagaraj
Premium Member
Premium Member
Posts: 383
Joined: Thu Nov 08, 2007 12:32 am
Location: Bangalore

Post by Nagaraj »

Actually you are right, the job actually took 14 Hrs, just now i checked.
Is there anything i can do to avoid this warning?
priyadarshikunal
Premium Member
Premium Member
Posts: 1735
Joined: Thu Mar 01, 2007 5:44 am
Location: Troy, MI

Post by priyadarshikunal »

What about this topic?

viewtopic.php?t=120901&highlight=currentWriteTime

have you tried it?
Priyadarshi Kunal

Genius may have its limitations, but stupidity is not thus handicapped. :wink:
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

After how long does this error message occur, before or after the first 12 hours?
Nagaraj
Premium Member
Premium Member
Posts: 383
Joined: Thu Nov 08, 2007 12:32 am
Location: Bangalore

Post by Nagaraj »

Actually this warning appears after 2 Hrs itself.(i.e from the moment you start the job)
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

So that would cancel out a problem with some 12-hour overflow occuring, it is just a timing event. The millisecond values retrieved from some UNIX variants aren't always that accurate, so it might just be a cross-process timing issue - which explains why this is a warning and not a fatal error. I see shades of Thiotimoline here.
Nagaraj
Premium Member
Premium Member
Posts: 383
Joined: Thu Nov 08, 2007 12:32 am
Location: Bangalore

Post by Nagaraj »

Hi priyadarshikunal

I didnt find this variable in DS GETTOD_ADJ_MONOTONIC,
Are you sure this env variable is going to solve the issue?

i have to remove these warnings....anyways.
priyadarshikunal
Premium Member
Premium Member
Posts: 1735
Joined: Thu Mar 01, 2007 5:44 am
Location: Troy, MI

Post by priyadarshikunal »

I don't know much about that as I never got this error but this is part of unix(AIX) and not related to DataStage. As it says the description is the man page of gettimeofday.

The two values in the warning are not related to execution time but they are current time of the server.
Priyadarshi Kunal

Genius may have its limitations, but stupidity is not thus handicapped. :wink:
Post Reply