Page 1 of 1

Getting: 9389 Bus error

Posted: Tue Mar 01, 2005 8:11 am
by memrinal
Hi All,
I have a job which uses a before job ExecSH Subroutine where a shell script is called and 17 job level parameters(most of them pathnames) are passed to it.

The script runs fine when run independently but when i try to run the job with before job ExecSH the job aborts and the director shows the following entry as the reason for abort
when executing command: ksh mysh1.ksh BR Brazil 20050301 /ascential/projects/COMETSTND_DEV/Test/LOG /ascential/projects/COMETSTND_DEV/Test/ERROR /ascential/projects/COMETSTND_DEV/Test/STAGE /ascential/projects/COMETSTND_DEV/Test/SCRIPTS /ascential/projects/COMETSTND_DEV/Test/LOOKUP /ascential/projects/COMETSTND_DEV/Test/ARCH /ascential/projects/COMETSTND_DEV/Test/ORCH /ascential/projects/COMETSTND_DEV/Test/INPUT /ascential/projects/COMETSTND_DEV/Test/OUTPUT /ftp/inbound/COMETBR ftpserver ftpuser ftp123 Mrinal_Kumar01@infosys.com
*** Output from command was: ***
SH: 9389 Bus error(coredump)
Job stopped - before-job routine returned error: Error 1 returned from BEFORE routine DSU.ExecSH
Please let me know why this is happening and how i can overcome this.
TIA
Mrinal

Posted: Tue Mar 01, 2005 8:23 am
by Sainath.Srinivasan
Login to Unix as dsadm and load your dsenv before running the command from Unix. That may simulate the working as in with DataStage.

Apply few 'echo' within the shell script to identify the location that has the problems.

Posted: Tue Mar 01, 2005 9:19 am
by chulett
Operating system? HP/UX by chance?

Posted: Tue Mar 01, 2005 10:39 am
by Sainath.Srinivasan
One guess is your usage of '@' symbol as a parameter value. Unix considers '@' to be a kill character. Try to enclose within double quotes.

Posted: Tue Mar 01, 2005 10:12 pm
by memrinal
Hi Chulett,
Yes the OS is HP/UX. Is this problem due to OS?

Sai i tried enclosing the email id within "'s but still i am getting error. this time the log says
SH: 17306 Bus error(coredump)
Is there anyway i can overcome this.
the same script runs fine when run directly from the shell.

Sai, one more query. how do i load dsenv. i can login as dsadm, but dont know how to load dsenv.

Thanks
Mrinal

Posted: Tue Mar 01, 2005 10:20 pm
by chulett
memrinal wrote:Yes the OS is HP/UX. Is this problem due to OS?
Yes, this is why I asked. Several others (including myself) have had the same problem with Korn shell scripts core dumping on HP/UX - only from DataStage. This post may help shed some light on the issue and documents what we have done that corrected the problem. :wink:

Posted: Tue Mar 01, 2005 11:30 pm
by memrinal
Thanks Chulett. I am also working on HP/UX 11.11 and the LD_PRELOAD is set.
I wanted to try commenting it out, but it will take some time since i am working on the production server and several clearances are required before making any changes to dsenv.
Thanks a lot for your timely help, else i would have been scratching my hair, thinking why the script is not running.
Mrinal

Posted: Mon Jun 30, 2008 8:58 am
by abhishekachrekar
Hi guys,

I am also facing similar error. I am working on HP-UX 11.11.
In some other thread I saw that this reason for this error was the usage of korn script. I removed the ksh command from the script calls in all the jobs.
It worked fine for some jobs but didnt for others.

In this particular job we are calling a script in After-job sub routine.
The script in DS aborts giving the error "SH: 20427 Bus error(coredump)".
But when the script is run on unix it works fine.
For debugging, I added set -xv command in the script and loaded the dsenv on unix (as suggested by Sainath). But then the script aborted on unix prompt with Bus error.

I tried to go through all the posts but couldn't find any resolution.
Kindly help me in resolving this issue.

Posted: Mon Jun 30, 2008 9:01 am
by chulett
If you have $LD_PRELOAD set, try unsetting it.

Posted: Mon Jun 30, 2008 9:20 am
by abhishekachrekar
Thanks chulett,

The parameter LD_PRELOAD is set as follows in dsenv.
LD_PRELOAD=$DSHOME/java/jre/lib/PA_RISC2.0/hotspot/libjvm.sl

I guess commenting this command will resolve the issue.
But what impact does it have on other processes/application.
I mean whats the significance of this parameter?

Actually my only concern is not to harm any other applications on that server.

Regards,
Abhishek

Posted: Mon Jun 30, 2008 9:28 am
by chulett
Commenting it out of the dsenv won't affect any other applications, just DataStage. You'd need to talk to an SA about what exactly it does other than cause core dumps.

Posted: Mon Jun 30, 2008 9:45 am
by abhishekachrekar
Thanks a lot :)