After moving Oracle Client or Server versions, FORECAST and HISTORY_PURGE aborts with the below error, seen in the output file:
starting sqlp Fri Mar 11 07:24:27 EST 2022
sqlplus -s @/app/uc4/master/sql/forecast A20011098.lis
ERROR:
ORA-12154: TNS:could not resolve the connect identifier specified
SP2-0306: Invalid option.
Usage: CONN[ECT] [{logon|/|proxy} [AS {SYSDBA|SYSOPER|SYSASM|SYSBACKUP|SYSDG|SYSKM|SYSRAC}] [edition=value]]
where <logon> ::= <username>[/<password>][@<connect_identifier>]
<proxy> ::= <proxyuser>[<username>][/<password>][@<connect_identifier>]
SP2-0306: Invalid option.
Usage: CONN[ECT] [{logon|/|proxy} [AS {SYSDBA|SYSOPER|SYSASM|SYSBACKUP|SYSDG|SYSKM|SYSRAC}] [edition=value]]
where <logon> ::= <username>[/<password>][@<connect_identifier>]
<proxy> ::= <proxyuser>[<username>][/<password>][@<connect_identifier>]
SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus
Could not login to sqlplus
no output from FORECAST
exiting sqlp Fri Mar 11 07:24:27 EST 2022
Release : 9.x
Component : Applications Manager
missing or misconfiguration of Oracle environment
The error can be caused by a number of reasons. Please refer to your DBA for further review and recommendation.
One specific cause of this error is to ensure that EZCONNECT is specified by the NAMES.DIRECTORY_PATH parameter in the sqlnet.ora file.