Thank you Jaap for all the suggestions and insights. I selected just the above three hot fixes since the issue we were facing was being catered for in one of these and the other two were a pre-req for installing the former one. Also, since we have a miration plan in place already (from 9.1.3 to 9.2) thus i didnot want to go for 'install all available fixes' approach and was more surgical and only selected the ones which catered the issue being faced. I actually went ahaed with the hot-fix installation which went smoothly and resolved the issue. I basically only followed the guidelines/notes which comes with the hot-fix bunlde file.The installation was performed in the following steps: - took a backup of Metada (the installation guide didnot say that , i took it just to be on the safe side) - Shut down all sas services, spwaners, user sessions and sas exes from task manager. - the hot-fix bundles where self extracting executables , executed in form of simple step by step wizards. - the bundles were executed on all machines which had SAS Base installaed on them (since the hot fixes were for SAS Base, in our case the webapp server is installed on a separate machine which didnot have sas base installed on it and hence no need to run the hot-fixes on that machine) - Started the services back up and the issue was resloved. A lilttle about the issue faced: Our production dwh is Teradata; when a PROC SQL was executed , certain column names were assigned wrong aliases while query generation at SAS end (I got to know that the issue was actually with the aliases by running the PROC SQL in SASBase with adding the following before the LIBNAME: options Locale=en_US; option sastrace=',,,d' sastraceloc=saslog no$stsuffix; and using PROC SQL_method instead of PROC SQL ) the above showed the step by step queries as generated by SAS and thrown on TD and the resulting errors.
... View more
