When running an IMPORT/EXPORT Job, or sql Jobs such as FORECAST or HISTORY_PURGE, it Aborts with on the following errors:
Could not find Sql Loader executable
Error 6 initializing SQL*Plus
SP2-0667: Message file sp1<lang>.msb not found
SP2-0750: You may need to set ORACLE_HOME to your Oracle software directory
Could not login to sqlplus
Component : APPLICATIONS MANAGER
Sql Loader executable is not found in environment/path
Oracle Home value may have been overwritten with a new value
Correct the Oracle environment to stop it from being overwritten by '.oraenv'.
Enabling BODY debug, rerunning the Job, and reviewing the output file will provide additional information about the ORACLE environment. In many cases, the ORACLE environment is being overwritten when '.oraenv' is being called. This occurs in the BODY script when a parameter is missing in the scripting logic such as the net_connect value. Below is snippet of the BODY script that determines if '.oraenv' will be called or not.
if [ "$login_sid" != "" -a "$net_connect" = "" -a "$ORACLE_SID" != "$login_sid" ]; then
if [ "$db_type" = "ORACLE" -o "$db_type" = "OAE" ]; then
export ORACLE_SID ORAENV_ASK
. oraenv </dev/null