Code running in DI Studio prior to the job, where is the code being called from?

_Dan_ — Thu, 08 Feb 2018 12:53:56 GMT

Hello all,

Colleagues have reported an influx of errors in their DI Studio jobs which point to LIBREFs not assigning properly. There's a specific caveat I must point out which I am hoping someone has come across before.

These error messages are being produced BEFORE the BatchServer Autoexec parses. This normally means I could find an %include or 'options insert' statement written in precode either in the individual transform, or the overlying DI Job. In this case, I can't find anything. Users have no control over their autoexec files, so they're not inserting anything there.

The error messages are:

ERROR: ORACLE connection error: ORA-12545: Connect failed because target host or object does not exist.
ERROR: ORACLE connection error: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor.

I don't "care" about the error message, that's a secondary issue. My concern is, where is this connection being attempted, because it's not in the config or autoexec files, and not a part of the user written code.

Finally, these error messages DO NOT cause Platform Process Manager jobs to exit as they are not deemed to be a part of the actual job. Even though the error message is in the log, they exist prior to the BatchServer actually doing anything, so PPM seems to ignore them. Like I say, this isn't the first time I have come across this issue, but I cannot for the life of me find where these assignments are stored. Maybe it's something in Management Console?

Thanks in advance,

Dan

Re: Code running in DI Studio prior to the job, where is the code being called from?

_Dan_ — Thu, 08 Feb 2018 13:04:52 GMT

For the benefit of anyone searching for a similar issue, the issue is due to two libraries being pre-assigned to this BatchServer which seem to have broken credentials. Check out the Data Library plugin in Management Console and have a look for libraries relevant to those you get an error for.

In my case I was lucky because they were the only two which began with a "P", but you may have difficulty if the LIBREF and Library Description don't match up properly.

topic Re: Code running in DI Studio prior to the job, where is the code being called from? in SAS Programming

Code running in DI Studio prior to the job, where is the code being called from?

Re: Code running in DI Studio prior to the job, where is the code being called from?