Job de SAS Data Integration Studio - Error fetching Library

[SAS_LuisBolivar]

Good afternoon dear community.

I need your support to solve the following problem

I have several SAS Data Integration Studio Jobs that read data from Oracle.

When executing it does not generate an error, but when trying to open the table resulting from the EXTRACT it tells me the following:

If I try the execution again without closing the etl it works.

Only when opening it and running it the first time it fails.

Thanks.

[LinusH]

I can't tell why this is happening, but I think it has to do with that Extract is by default creating a view.

To do unit testing, you could switch to a target table instead, hopefully it would resolve your issue.

And before checking in your job, switch back to view.

[RacheLGomez123]

SAS statements like LIBNAME and PROC METALIB or DATA Step statements that require connecting back to the metadata server might fail with the following errors at execution time:

ERROR: Libname LIBREF is not assigned.
ERROR: Error in the LIBNAME statement.
ERROR 52-121: Invalid credentials
ERROR: Access denied.
ERROR: DBMS connection error: invalid username/password; logon denied.
ERROR: Error in the LIBNAME statement.
NOTE: Connecting to SAS Metadata Server produced: ERROR: Invalid credentials
NOTE: SAS application server not found; the local machine will be used.
NOTE: Connecting to SAS Metadata Server produced:
ERROR: Cannot locate the metadata for SAS Application Server "AppServer"
These errors occur when the following conditions are true:

The SAS Data Integration Studio job contains code that sets the SAS system option METASERVER.
The value specified on the METASERVER system option does not match the metadata server information that was established during trusted peer initialization.
The METASERVER system option is not required and should not be present in job code, but it is generated in the code when the SAS Data Integration Studio job option, Enable optional metadata macro variables, is set to Yes. In prior releases of SAS Data Integration Studio, it was necessary to set the METASERVER system option (along with METAPORT). However, trusted peer connectivity has removed that need.

The workaround for this issue is to select No for the Enable optional metadata macro variables job option in order to prevent the METASERVER system option from being set. Perform the following steps to modify the job option setting:

Open properties on the job.
Click the Options tab.
Select No for the option Enable optional metadata macro variables.
Click OK to save the change.
image label
The setting of the METASERVER and METAPORT system options will be removed from code generation in a future release of the product.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Regards,
Rachel Gomez