Page 1 of 1

Posted: Sun Feb 07, 2010 4:54 am
by Sainath.Srinivasan
Permission changes ?

Can you connect via SAP logon pad ?

Did anyone bounce datastage ?

Posted: Sun Feb 07, 2010 7:58 am
by chulett
So, this time they weren't run manually? Meaning, this error only happens when the job is scheduled? :?

Posted: Thu Mar 11, 2010 12:39 pm
by Elozm
Nothing has change in this environment, the connection via SAP doesn't have problems and yes, this problem has happened just when the job was running scheduled.

The error was generated in one ocassion, it is running ok, but we don't have any idea of what could generate it.

Any ideas?

Thanks for your help.

Posted: Thu Mar 11, 2010 3:11 pm
by ray.wurlod
Can you look in the job log (job starting event) to determine what parameter values are actually being passed? That's about the only place there might be difference if the job runs OK from the DataStage client.