Resolving WebLogic Installation Script Execution Errors Due to Encoding Issues

When setting up a WebLogic server environment with all prerequisites fulfilled and installation packages uploaded, executing the install_wls1213.sh script resulted in multiple errors:

install_wls1213.sh: line 1: rectory: command not found
: command not found line 3: 
: command not found line 6: 
: command not found line 9: 
: command not found line 12: 
: command not found line 15: 
: command not found line 18: 
: command not found line 19: 
'nstall_wls1213.sh: line 24: syntax error near unexpected token `{
'nstall_wls1213.sh: line 24: `create_silent_install_files() {

Despite the script only generating two configuration files, syntax errors were reported. Recalling previous issues with Windows line endings conflicting with Linux environments, the problem was suspected to be encoding-related.

Resolution steps included:

  1. Removing the existing script file
  2. Creating a new file with identical name in the same directory
  3. Pasting UTF-8 encoded content directly into the new file via terminal editor
  4. Saving and executing the recreated script

The process was successful, completing WebLogic server installation:

weblogic@linux-velh:/home/weblogic/install> rm install_wls1213.sh 
weblogic@linux-velh:/home/weblogic/install> ls
weblogic@linux-velh:/home/weblogic/install> ls -al
total 8
drwxr-xr-x 2 weblogic weblogic 4096 Jun  6 22:22 .
drwxr-xr-x 5 weblogic weblogic 4096 Jun  6 22:22 ..
weblogic@linux-velh:/home/weblogic/install> vim install_wls1213.sh 
weblogic@linux-velh:/home/weblogic/install> ls -al
total 12
drwxr-xr-x 2 weblogic weblogic 4096 Jun  6 22:23 .
drwxr-xr-x 5 weblogic weblogic 4096 Jun  6 22:23 ..
-rw-r--r-- 1 weblogic weblogic 2493 Jun  6 22:23 install_wls1213.sh
weblogic@linux-velh:/home/weblogic/install> sh install_wls1213.sh 
CREATING SILENT INSTALL FILES
INSTALLING WEBLOGIC SERVER
Launcher log file is /tmp/OraInstall2019-06-06_10-23-25PM/launcher2019-06-06_10-23-25PM.log.
Extracting files...................................
Starting Oracle Universal Installer

Checking if CPU speed is above 300 MHz.   Actual 1796.690 MHz    Passed
Checking swap space: must be greater than 512 MB.   Actual 1123324 MB    Passed
Checking if this platform requires a 64-bit JVM.   Actual 64    Passed (64-bit not required)
Checking temp space: must be greater than 300 MB.   Actual 12192 MB    Passed


Preparing to launch the Oracle Universal Installer from /tmp/OraInstall2019-06-06_10-23-25PM
Log: /tmp/OraInstall2019-06-06_10-23-25PM/install2019-06-06_10-23-25PM.log
Copyright (c) 1996, 2014, Oracle and/or its affiliates. All rights reserved.
Reading response file..
Starting check : CertifiedVersions
Expected result: One of enterprise-4,enterprise-5,enterprise-6,redhat-6,redhat-4,redhat-5,SuSE-11
Actual Result: SuSE-11
Check complete. The overall result of this check is: Passed
CertifiedVersions Check: Success.
Starting check : CheckJDKVersion
Expected result: 1.7.0_15
Actual Result: 1.7.0_60
Check complete. The overall result of this check is: Passed
CheckJDKVersion Check: Success.
Validations are enabled for this session.
Verifying data......
Copying Files...
You can find the log of this install session at:
 /tmp/OraInstall2019-06-06_10-23-25PM/install2019-06-06_10-23-25PM.log
-----------20%----------40%----------60%----------80%--------100%

The installation of Oracle Fusion Middleware 12c WebLogic Server and Coherence 12.1.3.0.0 completed successfully.
Logs successfully copied to /home/weblogic/tmp/.inventory/logs.

This confirms that improper character encoding was the root cause of the execution failures.

Tags: WebLogic Shell Script Encoding Issues Linux Installation Troubleshooting

Posted on Wed, 17 Jun 2026 17:54:02 +0000 by Square1