My Oracle Support Banner

During ADOP adrelinknew.sh fails in OEL8 'line 1: syntax error: unexpected end of file' (Doc ID 2939375.1)

Last updated on SEPTEMBER 26, 2023

Applies to:

Oracle Applications DBA - Version 12.2.5 and later
Information in this document applies to any platform.

Symptoms

NOTE: The nodatabaseportion is not supported unless specifically stated as step in official documentation like 2617787.1

$ adop phase=apply patches=# apply_mode=hotpatch options=nodatabaseportion

Fails with the following error log messages:

$ADOP_LOG_HOME/<session>/<date_time stamp>/apply/<hostname>/<timestamp>/log/adrelink.log

/bin/sh: switchml: line 1: syntax error: unexpected end of file
/bin/sh: error importing function definition for `switchml'
/bin/sh: ml: line 1: syntax error: unexpected end of file
/bin/sh: error importing function definition for `ml'
/bin/sh: _module_raw: line 1: syntax error: unexpected end of file
/bin/sh: error importing function definition for `_module_raw'
/bin/sh: module: line 1: syntax error: unexpected end of file
/bin/sh: error importing function definition for `module'
/bin/sh: switchml: line 1: syntax error: unexpected end of file
/bin/sh: error importing function definition for `switchml'
/bin/sh: switchml: line 1: syntax error: unexpected end of file
/bin/sh: error importing function definition for `switchml'
/bin/sh: ml: line 1: syntax error: unexpected end of file
/bin/sh: error importing function definition for `ml'
/bin/sh: _module_raw: line 1: syntax error: unexpected end of file
/bin/sh: error importing function definition for `_module_raw'
9:48

grep: Unmatched [, [^, [:, [., or [=
<APPL_TOP>/ad/12.0.0/bin/adrelinknew.sh: line 1078: unset: `[': not a valid identifier
<APPL_TOP>/ad/12.0.0/bin/adrelinknew.sh: line 1078: unset: `"${_mlIFS+x}"': not a valid identifier
<APPL_TOP>/ad/12.0.0/bin/adrelinknew.sh: line 1078: unset: `];': not a valid identifier

 


Changes

In this case the customer was following on a two node EBS system

(Doc ID 2617787.1) Business Continuity for Oracle E-Business Suite Release 12.2 on Oracle Database 19c Using Physical Host Names
*** Section 7: Maintaining Oracle E-Business Suite with a Standby Database
******7.3.2.3 Apply patches to standby using hotpatch mode with the nodatabaseportion option
*********4. Apply the patches using hotpatch in the order that they were applied on the primary.

Use options=nodatabaseportion so that the they are applied without updating the database:

adop phase=apply patches=# apply_mode=hotpatch options=nodatabaseportion

The patch applied to the primary Server and did not apply any patches to 2nd node.

NOTE: This is one example problem only. This solution can be used for the same errors for other AD/TXK scripts.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.