My Journey to the cloud…

In pursuit of excellence….


usdsop: exec failed during spawn

Y’day one of our PROD support team called up and asked that their ftp program is failing with the below error


/d05/applprod/11.5/xxzz/4.0.0/bin/ZZAAR1240F: No such file or directory usdsop: exec failed during spawn/d05/applprod/11.5/xxzz/4.0.0/bin/ZZAAR1240F Program exited with status 1

I first checked if the given shell script has the required permission to be executed by the application owner. and it was Ok – 755.

Then I opened the shell script on the server and tried to see if there is anything within the code that is causing the error. And there I saw the junk character (ctrl V + ctrl M). Looks like the file was edited in Windows and transferred to UNIX.

I removed all the junk character using the below command


:%s/(ctrl-v)(ctrl-m)//g
and press Enter key.

Then I asked the support team to run the program. program completed successfully and file got transferred.

-Anand



2 responses to “usdsop: exec failed during spawn”

  1. how did you see those characters? Were those visible? I am having same issue. But I don’t see any characters.

    1. Rahul
      In my case, it was the concurrent program was the host file and hence I looked into the corresponding shell script. Junk characters (ctrl V + ctrl M) were present over there.

Leave a comment

About Me

I’m a Hands-On Technical & Entrprise Solutions Architect based out of Houston, TX. I have been working on Oracle ERP, Oracle Database and Cloud technologies for over 20 years and still going strong for learning new things.

You can connect me on Linkedin and also reach out to me

I am certified for 8x AWS, OCP (Oracle Certified Professionals), PMP, ITTL and 6 Sigma.

Disclaimer

This is a personal blog. Any views or opinions represented in this blog are personal and belong solely to the blog owner and do not represent those of people, institutions or organizations that the owner may or may not be associated with in professional or personal capacity, unless explicitly stated.
All content provided on this blog is for informational purposes only. The owner of this blog makes no representations as to the accuracy or completeness of any information on this site or found by following any link on this site.

The owner will not be liable for any errors or omissions in this information nor for the availability of this information. The owner will not be liable for any losses, injuries, or damages from the display or use of this information. Any script available on the blog post MUST be tested before they are run against Production environment.

Newsletter