About AnandVyas

AnandVyas · ‎10-07-2020

Hi @sathya66 Can you please share application logs for these apps located under <sas-config>/Lev1/Web/Logs/SASServer2_1?

AnandVyas · ‎10-07-2020

Hi @helpme88 In order to make connection from SAS to any database you will have to use a libname statement. For the connection to work, you will have to configure a related SAS/Access engine to that database. In your case you have SAS/Access to ODBC installed at your site so you will have to check if the related configuration is also made or not in order to connect to Oracle. If not, you will have to make those changes. Also, just to let you know SAS also has a native SAS/Access interface to Oracle engine. For setup related to ODBC, you will need to have the ODBC driver manager and the Oracle driver for ODBC installed in your platform. I would suggest you to go through this documentation link to understand more on how it: Introduction to SAS/ACCESS Interface to ODBC Here is a good SAS Communities article on How-to-configure-SAS-ACCESS-Interface-to-ODBC-on-UNIX-Platforms Once you have the setup correctly configured you can use a libname statement to make connection to DB and work with data. Link to documentation here for libname statement here .

AnandVyas · ‎10-07-2020

Hi @vinpres The error clearly states that connection failed as it wasn't able to connect to oracle host. Do you have the correct oracle environment variables defined for each user to properly resolve host address or are these set for a single user only?

AnandVyas · ‎10-07-2020

Hi @pmaturi83 You can override the locale using the system option if you wish. Link to the details about this option: LOCALE System Option . It can be done platform level or user can also do it at their session level. While SAS will automatically detect the change of native encoding and do the processing it will output in the log a note as below: NOTE: Data file HEALTH.OXYGEN.DATA is in a format that is native to another host, or the file encoding does not match the session encoding. Cross Environment Data Access will be used, which might require additional CPU resources and might reduce performance. It's better to migrate SAS data and content to native Linux encoding. I believe you can use proc migrate to do that or if a new dataset created will be in native encoding. There is a RedHat performance brief available to Optimizing SAS on Red Hat Enterprise Linux (RHEL) 6 & 7 . I think it's a good read to understand optimize the system based on your analytics requirements.

AnandVyas · ‎10-07-2020

Hi @sasprofile To answer it simple, If you have changed your sasadm@saspw password, you will have to launch SDM on every host in your environment and update it. In SAS all the internal accounts ending with '@saspw' , internal DB accounts and service accounts are also called 'Managed Password' Update a Managed Password

AnandVyas · ‎10-07-2020

If it's a managed password, then you will have to update it on every machine using SDM. Some examples accounts include: SAS Administrator (sasadm@saspw) SAS Trusted User (sastrust@saspw) SAS General Servers (sassrv) SAS Environment Manager User (sasevs@saspw) accounts for the SAS Web Infrastructure Platform Data Server and databases

AnandVyas · ‎10-06-2020

sasadm@saspw is only in metadata and if you change it once then should be enough. If you have no other admin account you can use the steps below: If there is no other administrator available and you have the necessary host access, you can use this approach as a last resort: Edit the metadata server's adminUsers.txt file to create an unrestricted user. Navigate to your equivalent of SAS/Lev1/SASMeta/MetadataServer/adminUsers.txt. Open the file with a text editor. Add a user ID for an account that is known to the metadata server's host. Include a preceding asterisk (for example, *WIN\winID or *unixID). Stop and restart the metadata server to make the change take effect. CAUTION Stopping the metadata server stops other components. Log on to SAS Management Console using the user ID that you added to the adminUsers.txt file. On the status bar at the bottom of the application window, notice that you are unrestricted. Unlock the locked account. See the preceding instruction list for more information. To verify that the account is unlocked, log on to SAS Management Console using the account. Open the adminUsers.txt file, remove the entry that you added, and stop and restart the metadata server. Here are some additional tips: If you choose to change the password for the original SAS Administrator, you might need to update the deployment. You can customize the account lockout policy. We recommend that you establish individual metadata administrators rather than sharing the predefined SAS Administrator account. https://documentation.sas.com/?cdcId=bicdc&cdcVersion=9.4&docsetId=bisecag&docsetTarget=p135ufuc50p223n1ve02cy1a69u3.htm&locale=en

AnandVyas · ‎10-06-2020

Hi @sathya66 Can you share the complete error details? If you are thinking of reverting it back it should be from the cold backup you might have taken before applying the hot-fix not the files inside the sas_webapps directory.

AnandVyas · ‎10-05-2020

Very interesting ask! Would like to know what is making you do this. Also first thing to check would be if you have any SAS objects that are downgrade compatible or you have to rebuild them. For Ex: EG projects

AnandVyas · ‎10-05-2020

In my experience usually if the SAS servers are part of VM farm then there are available technologies that can sync everything from existing VM to DR VM automatically. It is usually scheduled from the VM support team managing the infra. Since there is a requirement of hostnames should be same for SAS if that cannot be achieved seamlessly then you can use DNS or alias name and do a switch while moving to DR. If this installation is on physical machines then you have storage replication technologies that can perform the job. You should talk to your Infra team on how are they doing it for other applications. If you choose for a hot-hot approach I believe you will have to pay license fees for both the SAS environments. Again It's a good discussion to have with your account manager.

AnandVyas · ‎10-04-2020

You can enable guest access to give read only access for users to view reports in VA. https://documentation.sas.com/?docsetId=calauthmdl&docsetTarget=n067qoyrgu1yohn19nq4ehy8o0b3.htm&docsetVersion=3.5&locale=en

AnandVyas · ‎09-29-2020

Hi @MG18 In addition to steps shared by @rabindrakumar1 also check object spawner logs for errors and see if you can enable workspace server logs for extra logging.

AnandVyas · ‎09-28-2020

Is this the full log? Are there any firewalls which is dropping the connection to the port? "Connection failed" is a very generic error. See if you can add some debug options for more detailed logging.

AnandVyas · ‎09-28-2020

That is right! Usually I have had such scenarios where every user had their own DB ID so by adding the user and the auth under the user identity it should work. Usually it works for group as well, not sure why it's prompting for credentials. Did you try to clear the credential cache and see?

AnandVyas · ‎09-28-2020

If you are talking about SAS IQ and OQ in SAS9 platform there aren't such utilities for Viya. If you have done complete validation and there weren't any errors or issues I think you are good. 🙂