SAS Support Communities

gwootton

Yes, I think the only caveat I'd point out is the contents of rel and lod are going to change when you pull a new release.

gwootton

1. You are correct, the deployment operator pulls information from a remote location to get details on the deployment. 2. The documentation only covers the options (e.g. --repository-warehouse-location) and how to build the warehouse (mirrormgr doc for a air-gapped site) and not how to deploy an HTTP server to serve up this information. 3. Yes 4. No, we do not currently document how to set up a web server to serve up those files.

gwootton

You can use mirror manager to create the repository location: Create a Mirror Registry at an Air-Gapped Site https://go.documentation.sas.com/doc/en/itopscdc/v_063/dplyml0phy0dkr/n1f39x15xt82m4n13f7bu37l9qum.htm The documentation indicates you would then specify that local path when running the sas-orchestration tool. For the Deployment Operator, as you mentioned on your other post the viya4-warehouse project can also download the warehouse files without making use of mirror manager: https://github.com/sassoftware/viya4-warehouse If you serve that download path as the top level from a cluster-local web server you could specify that as the repository-warehouse-location. And the various deployment operator tasks should call that URL instead.

gwootton

This error is an import failure. When importing you first upload a package to the transfer service which would store the package as a large object, then import on that package ID. This error message is saying the package ID we are trying to import is associated with a large object that isn't in the database, so this is sort of the opposite of your initial concern, where we have a reference to the large object in the transfer schema table, but the large object itself isn't present.

gwootton

Are there any other messages indicating the details of the exception being encountered? Does the behavior change if you use JDBC driver version 94290? https://support.sas.com/downloads/package.htm?pid=2620

gwootton

The transfer service will call lo_unlink to the postgres database when you delete a package to delete the associated large object. If this call returns an error from postgres I would expect you to see an error in the transfer service log. The vacuumlo utility is the appropriate solution for removing those large objects that have been orphaned, so I would agree this is something that should be done periodically along with your other Postgres routine maintenance tasks like vacuuming and reindexing.

gwootton

That documentation indicates the virtual IP address would only be ping-able when at least two nodes in the HA pgpool-II cluster are running. Is that true in your case? If that is true and this is failing would suggest an issue with the virtual IP configuration.

gwootton

When you create a flow you select which deployed jobs you want to include in that flow. When you deploy a job, you select the location in Metadata where you wish to store that job. So the question is whether the deployed job has been deleted from Metadata, or simply removed from the flow. It sounds like one of those two things happened, so you may need to recover from a Metadata backup taken prior to the jobs being removed from the flow.

gwootton

It sounds like you're talking about accessing SAS data sets that have been stored on the compute tier of a grid deployment remotely from that environment and SAS, using the SAS ODBC driver. To do that, I think you would need a server to be running on that deployment to answer that ODBC connection (i.e. a SAS/SHARE server that has loaded a library with the datasets you want to read). So I think you'd need a SAS/SHARE server configured on your grid deployment to be able to access it using the SAS ODBC driver. Documentation on SAS/SHARE: https://go.documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/shrref/titlepage.htm Documentation on the SAS ODBC Driver: https://go.documentation.sas.com/doc/en/odbcdref/9.4/n0maisizj6qtffn1ps3ez8g09ge7.htm

gwootton

LTS 2025.03 is not yet available, but generally speaking you would apply it as a patch update if you were within the same version (e.g. 2025.03 > LTS 2025.03). Documentation on switching cadences can be found here: Update Paths When Switching Cadences https://go.documentation.sas.com/doc/en/sasadmincdc/v_063/itopsup/p1lam22gz8zj8gn1b51yczorenun.htm#p1hagvntwc2c57n1l459yj43xnqy The note for the entry for stable to LTS of the same version reads (in this case the example is moving from Stable 2024.09 to LTS 2024.09): 1 The update process is to apply a patch update to 2024.09 using the deployment assets for LTS 2024.09. Documentation on applying a patch update can be found here: Apply a Patch Update: https://go.documentation.sas.com/doc/en/sasadmincdc/v_063/k8sag/p0954mgxmsddrmn1klrphsbnqasm.htm

gwootton

You would want to review the AutoLoad log in <SASCONF>\Lev1\Applications\SASVisualAnalytics\VisualAnalyticsAdministrator\EVDMLA\Logs to see what it attempted to load and any failures that were encountered. Here's the relevant documentation on loading that table: https://go.documentation.sas.com/doc/en/bicdc/9.4/vaag/n0ztu074vadeuvn17a1hpspp4bd7.htm And autoloading in general: https://go.documentation.sas.com/doc/en/bicdc/9.4/vaag/n0nm6qjzfz4eban1237qqrcmxz0j.htm

gwootton

Remove the -V option from your kinit command, that option is not valid on Windows.

gwootton

You may wish to engage SAS Technical Support to confirm you are using the correct JRE for your 9.4 M6 installation.

gwootton

By default SAS would be using its private JRE (<SASHome>/SASPrivateJavaRuntimeEnvironment), not the one that is run when you run "java" from the command line. According to this page, 9.4 M6 included Java 8. Are you sure you are on version 9.4 M6 and not M5 or earlier? https://support.sas.com/en/documentation/third-party-software-reference/9-4/support-for-java.html I believe upgrading the SAS Private JRE would involve upgrading your SAS deployment to a newer release. The current release, 9.4 M8, ships with Java 11.

gwootton

The documentation on deploying SAS Web Parts for Microsoft Sharepoint can be found here: https://go.documentation.sas.com/doc/en/bicdc/9.4/biig/n11001intelplatform00install.htm