The problem of running processes and tasks on the schedule

[grudos20]

Hi guys

Faced with the problem of the work of processes and tasks on the schedule.

Reinstalled SAS 9.4M7 on new Linux servers.

Manual launches of campaigns from SAS CIS and manual launches of jobs from sas SAS DIS work out successfully. But if we schedule campaigns and jobs on the schedule, we get the following errors:

Campaign

----------

job 24 at Mon Apr 11 14:39:00 2022
ATJOBSubmitted
22/04/11 14:39:00 Flow _CAMP52138 starting, process ID 3144
job 25 at Tue Apr 12 14:39:00 2022
ATJOBSubmitted
22/04/11 14:39:00 Job _CAMP52138_A5VDU7VZ_C8000029 starting, process ID 3157
2022-04-11 14:39:02,022 FATAL [com.sas.svcs.environment.xml.XmlEnvironmentManager] - Unable to properly initialize EnvironmentManager (MalformedURLException) using the provided URL (prod-mid.ro-central1.internal:7980/ sas/sas-environment.xml)
java.net.MalformedURLException: unknown protocol: prod-mid.ro-central1.internal
at java.net.URL.<init>(URL.java:618)
at java.net.URL.<init>(URL.java:508)
at java.net.URL.<init>(URL.java:457)

----------

The link prod-mid.ro-central1.internal:7980/sas/sas-environment.xml opens successfully in the browser.

Scheduler Server: Operating System Services MA

Jobs the first lines of the batch log:

----------

NOTE: Libref SASDATA successfully assigned from logical server.
NOTE: Libref WRSDIST successfully assigned from logical server.
NOTE: Libref WRSTEMP successfully assigned from logical server.
NOTE: Libref MATABLES successfully assigned from logical server.
NOTE: Libref MASTATIC successfully assigned from logical server.
NOTE: Libref MAMOLIB successfully assigned from logical server.
NOTE: Libref STPSAMP successfully assigned from logical server.
NOTE: Libref SASSAMP successfully assigned from logical server.
NOTE: Libref SASSAMP refers to the same physical library as SASDATA.
ERROR: Libref CDM failed to assign from logical server.
ERROR: Unable to load oracle client (libclntsh.so)
ERROR: Libref CICOMMON failed to assign from logical server.
ERROR: Unable to load oracle client (libclntsh.so)
ERROR: Libref CMDM failed to assign from logical server.
ERROR: Unable to load oracle client (libclntsh.so)
ERROR: Libref EXCHANGE failed to assign from logical server.
ERROR: Unable to load oracle client (libclntsh.so)
ERROR: Libref ADM failed to assign from logical server.
ERROR: Unable to load oracle client (libclntsh.so)

----------

Batch Server : SAS Data Step Batch Server

I would be glad for ideas on solving the problem, why do tasks not work on the schedule?

Thanks

[gwootton]

For the campaign, the URL failure seems to be that it is complaining about a lack of protocol. In other words, there is no http:// or https:// in front of the URL.

For the Batch log error it seems the preassigned libraries can't be assigned because the shared object library libclntsh.so can't be found.

For the former, I think we need to add the protocol to the URL in the ini file for this application in SASHome.
For the latter, this is probably a matter of how the LD_LIBRARY_PATH is being updated to add the oracle libraries. Is this set in the sasenv_local file as described here?

Setting UNIX Environment Variables for SAS/ACCESS
https://go.documentation.sas.com/doc/en/bicdc/9.4/bidsag/p1w3v98qca3sfzn1rzty2tngrfyq.htm

[grudos20]

Hello gwootton
Thanks for the help.
I changed the file "/opt/sas/SASHome/sassw.config" to the command "SASENVIRONMENTSURL=" and added "http://" and my campaign ran successfully on the schedule. Did I do right?

Can't figure out the "LD_LIBRARY_PATH" command. The instruction is probably designed for experienced users.
On the server, I ran the command echo $ORACLE_HOME
Output: /opt/ora_client_19

In the directory I see the following files and folders:

The instructions recommend adding the command
LD_LIBRARY_PATH=/opt/drivers/odbc/lib:\
/opt/oracle/app/oracle/product/12.1.0/lib:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
Unfortunately, I do not find such links on my servers.

I am using the following setup to connect to Oracle DB:

Jobs are launched from SASAppMA (marketing automation) and SASAppEM (Enterprise Miner) servers. The Oracle client is deployed on all servers.

[gwootton · Accepted solution]

Glad to hear the correcting the URL resolve your campaign issue.

As far as the LD_LIBRARY_PATH setting, this needs to be set in your <SASHome>/SASFoundation/9.4/bin/sasenv_local to include the path to where your Oracle libraries are, which in your case seems to be /opt/ora_client_19/lib. So the lines you'd want to add to sasenv_local would probably be something like:

ORACLE_HOME=/opt/ora_client_19
export ORACLE_HOME
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib
export LD_LIBRARY_PATH

[grudos20]

Thank you very much, the problem is solved with your help