IBM Support

How to fix '/usr/bin/ksh^M: bad interpreter' when using IBM Content Manager

Troubleshooting


Problem

How to fix '/usr/bin/ksh^M: bad interpreter' error when using IBM Content Manager

Symptom

After IBM Content Manager installation, I got '/usr/bin/ksh^M: bad interpreter : No such file or directory' error when issue the command cm_run_firststeps.sh and cmadmin.sh.

Cause

cm_run_firststeps.sh fileformat is DOS instead of Unix

Environment

Linux

Diagnosing The Problem

1. I checked the cm_run_firststeps.sh file, no ^M character existed.
2. ksh is installed.
3. After check the *.sh file format using 'vi' command, found that all the *.sh files belong to IBM Content Manager are in DOS format. The correct file format should be 'unix' in Linux OS.

Resolving The Problem

1. chmod a+x cm_run_firststeps.sh

2. vi cm_run_firststeps.sh
:set fileformat
:set fileformat=unix
:wq

[{"Product":{"code":"SSRS7Z","label":"IBM Content Manager Enterprise Edition"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Usage","Platform":[{"code":"PF016","label":"Linux"}],"Version":"8.4.3.3;8.4;8.4.0.1;8.4.1;8.4.1.1;8.4.2;8.4.2.1;8.4.2.2;8.4.2.3;8.4.3;8.4.3.1;8.4.3.2;6.1","Edition":"Enterprise","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 July 2019

UID

swg21634435

Page Feedback