Error in Scheduling

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

Sakthi_Sst
Participant
Posts: 36
Joined: Wed Aug 09, 2006 12:18 am
Location: Chennai

Error in Scheduling

Post by Sakthi_Sst »

Hi All,

I have a problem in schedulng my jobs.

Issue:
1.When i try to schedule a job "test11" in a proj called "BI_1A",it throws me an error
"Error adding to schedule: at: 0481-166 The auditproc function failed with errno 1.(Command was: at -s 11:25 today )
(Data was: /db2tmp1p101/ds/Ascential/DataStage/Projects/BI_1A/dsr_sched.sh /db2tmp1p101/ds/Ascential/DataStage/Projects/BI_1A /software/ds/Ascential/DataStage/DSEngine test11 0/50/1/0/0 1 >/dev/null 2>&1) "

2.I have tried scheduling with a different project in the same server even it throws me a similar error.

3.I have also copied the "dsr_sched.sh" file from a different server where iam able to schedule the jobs to this server and still i get the error.

Has anyone come across this issue?
Help me come out of this issue?

Regards,
Sakthi
kumar_s
Charter Member
Charter Member
Posts: 5245
Joined: Thu Jun 16, 2005 11:00 pm

Post by kumar_s »

Have you ever tried scheduling any jobs via datastage/ outside of datastage?
Try to schedule the same using command prompt in the AT.
Else you may need to check the permission for your user id.
Check .allow and .deny file has the entry of your user id.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
Sakthi_Sst
Participant
Posts: 36
Joined: Wed Aug 09, 2006 12:18 am
Location: Chennai

Post by Sakthi_Sst »

Hi Kumar,


1.I am able to schedule jobs in a different unix server(say server 141) in datastage,but not with this unix server(say server 142) alone.
2.I have not scheduled any jobs outside datastage.
3.I am sure my user id has all permissions,
sorry for my illiteracy where do i find the .allow and .deny file in unix server.

Regards,
Sakthi
kumar_s
Charter Member
Charter Member
Posts: 5245
Joined: Thu Jun 16, 2005 11:00 pm

Post by kumar_s »

Its at.allow / at.deny or cron.allow / cron.deny if its cron.
In your cron directory like /var/adm/cron/
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

And you'll need to talk to your SA to effect any change there - you won't be able to directly.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Sakthi_Sst
Participant
Posts: 36
Joined: Wed Aug 09, 2006 12:18 am
Location: Chennai

Post by Sakthi_Sst »

Hi All,


I was unable to check that since i didnot have permissions in CRON.

I have spoke to my SA and he has confirmed that my UserId has all the permissions to schedule the job.

He has also compared the settings and permissions of my UserId with another one Userid which is working,they both are the same.

Any other workarounds or soluntions??????

Regards,
Sakthi
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Check again. Get your SA to show you your entry in cron.allow or at.allow.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
kumar_s
Charter Member
Charter Member
Posts: 5245
Joined: Thu Jun 16, 2005 11:00 pm

Post by kumar_s »

Ask him (our you) to schedule a job or any script using your user id, from command prompt. If that succeeds, it proves, your user id has permission.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
Sakthi_Sst
Participant
Posts: 36
Joined: Wed Aug 09, 2006 12:18 am
Location: Chennai

Post by Sakthi_Sst »

Hi All,

Thanks everyone for your inputs.

I worked with my SA and scheduled a script on the same unix server by myself.
I am able to schedule the script with my UserId and it successfully ran at the scheduled time using the CRONTAB command.

But, still Iam unable to do that through Datastage.

Any other inputs?

Regards,
Sakthi
kumar_s
Charter Member
Charter Member
Posts: 5245
Joined: Thu Jun 16, 2005 11:00 pm

Post by kumar_s »

If you schedule from Datastage, are you able to see any entry in CRONTAB file?
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
Sakthi_Sst
Participant
Posts: 36
Joined: Wed Aug 09, 2006 12:18 am
Location: Chennai

Post by Sakthi_Sst »

Kumar,

No.It actually takes the scheduled time,parameter for the job and then throws an error before scheduling.

No entry in the CRONTAB file.


Regards,
Sakthi
kumar_s
Charter Member
Charter Member
Posts: 5245
Joined: Thu Jun 16, 2005 11:00 pm

Post by kumar_s »

Have you gone through the section that given under the Adminstrator Guide for Troubleshooting. There is a seperate section for Scheduling jobs.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
Sakthi_Sst
Participant
Posts: 36
Joined: Wed Aug 09, 2006 12:18 am
Location: Chennai

Post by Sakthi_Sst »

Hi Kumar,

I went through the pdf it states that, something got to do with the AT or CRONTAB command.

Can you confirm whether Datastage uses CRONTAB or AT command to schedule the jobs through the Unix Server?

Which is the underlying process to schedule jobs CRONTAB or AT thru unix?

So that I can work with my SA to schedule it.


Regards,
Sakthi
kumar_s
Charter Member
Charter Member
Posts: 5245
Joined: Thu Jun 16, 2005 11:00 pm

Post by kumar_s »

CRONTAB for unix.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
Sakthi_Sst
Participant
Posts: 36
Joined: Wed Aug 09, 2006 12:18 am
Location: Chennai

Post by Sakthi_Sst »

Hi All,


The issue is resolved at last ,my userid did not have execute permissions in " AT " utility.

Datastage uses a utility called "AT" in unix server to schedule jobs,whenever it is scheduled through DS Director.


Thanks for all your inputs.


Regards,
Sakthi
Post Reply