CRITICAL ERROR!!!!

karry450 · Post by **karry450** » Tue Jul 21, 2009 12:48 am

Hi There,

I have four jobs in a sequence and when I run the sequence all the jobs with in ran successfully but the sequence failed with the error shown below.

Job control process (pid 13007) has failed

From previous run
DataStage Job 202 Phantom 13007
Abnormal termination of DataStage.
Fault type is 8. Layer type is BASIC run machine.
Fault occurred in BASIC program DSD.Init at address 76.
Floating point exception
CRITICAL ERROR! Notify the system administrator.

Can anyone help me regarding this please.

Thanks
karthik

ray.wurlod · Post by **ray.wurlod** » Tue Jul 21, 2009 1:02 am

Floating point exceptions are very rare in the DataStage run machine. The fault type reported is actually the UNIX signal number (8 = SIGFPE, or floating point exception).

The problem may be in your code and its interaction with your data. For example an attempt to divide a floating point number by zero will cause a floating point exception. Check out this Wikipedia entry for more information about SIGFPE.

If you don't think it's in your code/data, you will need to involve your official support provider.

LavanyaRamesh007 · Post by **LavanyaRamesh007** » Tue Jul 21, 2009 1:03 am

karry450 wrote:Hi There,

I have four jobs in a sequence and when I run the sequence all the jobs with in ran successfully but the sequence failed with the error shown below.

Job control process (pid 13007) has failed

From previous run
DataStage Job 202 Phantom 13007
Abnormal termination of DataStage.
Fault type is 8. Layer type is BASIC run machine.
Fault occurred in BASIC program DSD.Init at address 76.
Floating point exception
CRITICAL ERROR! Notify the system administrator.

Can anyone help me regarding this please.

Thanks
karthik

Usually Phantom error is caused by any abnormalities in Datastage. When DS finds when the job you are running has anything unusual, abruptly the job aborts.
Reexamine everything job, check out partitioning, environmental parameters. It might help you to debug the job

karry450 · Post by **karry450** » Tue Jul 21, 2009 1:04 am

ray.wurlod wrote:Floating point exceptions are very rare in the DataStage run machine. The fault type reported is actually the UNIX signal number (8 = SIGFPE, or floating point exception).

The problem may be in yo ...

Can you please help me with full message I cant view I dont have the membership.

Thanks

chulett · Post by **chulett** » Tue Jul 21, 2009 5:22 am

Something that says "CRITICAL ERROR! Notify the system administrator" should be reported to your admin and then they in turn will need to contact your official support provider.

ray.wurlod · Post by **ray.wurlod** » Tue Jul 21, 2009 4:30 pm

karry450 wrote:Can you please help me with full message I cant view I dont have the membership.

No, because that would create a precedent of undermining a source of revenue that keeps DSXchange alive.

Premium membership is not expensive, at less than 30c (Rs12) per day.

If that's too much then, well, you ARE paying for support - why not demand some?

karry450 · Post by **karry450** » Wed Jul 22, 2009 4:35 am

ray.wurlod wrote:
karry450 wrote:Can you please help me with full message I cant view I dont have the membership.
No, because that would create a precedent of undermining a source of revenue that keeps DSXchange alive.

Premium membership is not expensive, at less than 30c (Rs12) per day.

If that's too much then, well, you ARE paying for support - why not demand some?

I would definitely buy one but it takes some time for me .

Thanks

CRITICAL ERROR!!!!

CRITICAL ERROR!!!!

Re: CRITICAL ERROR!!!!