Hi @JuanS_OCS ,   Both servers are the same, Solaris. For testing purpose, the folder with special characters is empty, so the test is save a table on it.    We are working with SAS Technical Support and SAS Professional Services (all installation was made by SAS) but we don't have any progress with them. I share the problem with the community hoping someone had a similar problem on the past.    Regards,  ... View more

Hi @JuanS_OCS ,   Yes, it's related to other post. We have 2 new servers, one for production and one for UAT. In both, SAS is in LATIN1 with en_US encoding.   ENCODING=LATIN1 Specifies the default character-set encoding for the SAS session. LOCALE=EN_US Specifies a set of attributes in a SAS session that reflect the language, local conventions, and culture for a geographical region.   Our OS is in UTF-8. Which output of OS for locale do you prefer? On the production servers, we don't have problem, the problem occurs on UAT.   We know that is not recommend but for many reasons we have some files/folders with these characteristics and we need to work with these situation.    As comment, the performance problems occurs in both servers.    Thanks,         ... View more

Is Intel(R) Xeon(R) CPU E5-2690 v2.   Regards, ... View more

Hi @MargaretC ,   We already convert all SAS tables to Solaris, so we don't use CEDA.   Our Solaris server is SPARC M6.   Regards, ... View more

Hi folks,   You have the solution for this issue? We have the same problem on our new environment.   Regards, ... View more

Hi @MargaretC ,   Follows the complete SAS Notes: NOTE: Variable YYYYYY is uninitialized. WARNING: Multiple lengths were specified for the variable YYYYY by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable YYYY by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable YYYYY by input data set(s). This can cause truncation of data. WARNING: Multiple lengths were specified for the variable YYYYYY by input data set(s). This can cause truncation of data. NOTE: There were 5820616 observations read from the data set XXXX. NOTE: There were 4569248 observations read from the data set XXXX. NOTE: There were 4509959 observations read from the data set XXXX. NOTE: There were 4518362 observations read from the data set XXXX. NOTE: There were 4546455 observations read from the data set XXXX. NOTE: There were 4423525 observations read from the data set XXXX. NOTE: There were 4254636 observations read from the data set XXXX. NOTE: There were 4359365 observations read from the data set XXXX. NOTE: There were 4353605 observations read from the data set XXXX. NOTE: There were 4554579 observations read from the data set XXXX. NOTE: There were 4267877 observations read from the data set XXXX. NOTE: There were 4262071 observations read from the data set XXXX. NOTE: There were 4694086 observations read from the data set XXXX. NOTE: There were 4789203 observations read from the data set XXXX. NOTE: There were 4072292 observations read from the data set XXXX. NOTE: There were 4567131 observations read from the data set XXXX. NOTE: There were 4538530 observations read from the data set XXXX. NOTE: There were 4475507 observations read from the data set XXXX. NOTE: There were 4411171 observations read from the data set XXXX. NOTE: There were 4359381 observations read from the data set XXXX. NOTE: There were 4324500 observations read from the data set XXXX. NOTE: There were 4228892 observations read from the data set XXXX. NOTE: There were 4190545 observations read from the data set XXXX. NOTE: There were 4185068 observations read from the data set XXXX. NOTE: There were 4167472 observations read from the data set XXXX. NOTE: There were 4141983 observations read from the data set XXXX. NOTE: There were 4041356 observations read from the data set XXXX. NOTE: There were 3920099 observations read from the data set XXXX. NOTE: There were 3788828 observations read from the data set XXXX. NOTE: There were 3636657 observations read from the data set XXXX. NOTE: There were 3536831 observations read from the data set XXXX. NOTE: There were 3340947 observations read from the data set XXXX. NOTE: There were 3106852 observations read from the data set XXXX. NOTE: There were 4505524 observations read from the data set XXXX. NOTE: There were 4490082 observations read from the data set XXXX. NOTE: There were 4776326 observations read from the data set XXXX. NOTE: There were 4687402 observations read from the data set XXXX. NOTE: There were 4704937 observations read from the data set XXXX. NOTE: There were 4699015 observations read from the data set XXXX. NOTE: There were 4667477 observations read from the data set XXXX. NOTE: There were 4628155 observations read from the data set XXXX. NOTE: There were 4534338 observations read from the data set XXXX. NOTE: There were 4547107 observations read from the data set XXXX. NOTE: There were 4528159 observations read from the data set XXXX. NOTE: There were 4537420 observations read from the data set XXXX. NOTE: There were 4384072 observations read from the data set XXXX. NOTE: There were 4256290 observations read from the data set XXXX. NOTE: There were 4301934 observations read from the data set XXXX. NOTE: There were 4262408 observations read from the data set XXXX. NOTE: There were 4229829 observations read from the data set XXXX. NOTE: There were 4103216 observations read from the data set XXXX. NOTE: There were 3573311 observations read from the data set XXXX. NOTE: There were 3378687 observations read from the data set XXXX. NOTE: There were 3208889 observations read from the data set XXXX. NOTE: There were 3027670 observations read from the data set XXXX. NOTE: There were 4159768 observations read from the data set XXXX. NOTE: There were 4110686 observations read from the data set XXXX. NOTE: There were 4052798 observations read from the data set XXXX. NOTE: There were 4100190 observations read from the data set XXXX. NOTE: There were 4101430 observations read from the data set XXXX. NOTE: There were 4096104 observations read from the data set XXXX. NOTE: There were 4155598 observations read from the data set XXXX. NOTE: There were 4150791 observations read from the data set XXXX. NOTE: There were 4148467 observations read from the data set XXXX. NOTE: There were 4133380 observations read from the data set XXXX. NOTE: There were 4125579 observations read from the data set XXXX. NOTE: There were 4106291 observations read from the data set XXXX. NOTE: There were 4103442 observations read from the data set XXXX. NOTE: There were 4100431 observations read from the data set XXXX. NOTE: There were 4090390 observations read from the data set XXXX. NOTE: There were 4081835 observations read from the data set XXXX. NOTE: There were 4065041 observations read from the data set XXXX. NOTE: There were 4086124 observations read from the data set XXXX. NOTE: There were 4079646 observations read from the data set XXXX. NOTE: There were 4072297 observations read from the data set XXXX. NOTE: There were 4032759 observations read from the data set XXXX. NOTE: There were 4017684 observations read from the data set XXXX. NOTE: There were 4026204 observations read from the data set XXXX. NOTE: The data set WORK.FINAL has 329186812 observations and 25 variables. NOTE: DATA statement used (Total process time): real time 26:46.93 user cpu time 17:45.94 system cpu time 8:01.01 memory 70107.87k OS Memory 116408.00k Timestamp 09/28/2020 05:35:16 PM Step Count 3 Switch Count 2456 Page Faults 0 Page Reclaims 78 Page Swaps 4 Voluntary Context Switches 46739 Involuntary Context Switches 8595 Block Input Operations 4 Block Output Operations 0 The same occurs when we create a table from an external database (for example SQL Server). The same query takes 3 to 4 times. Same happens with proc sort, etc.    Regards,  ... View more

For now, happens only for one user. Until last week, the user has not problem.   Regards, ... View more

Thanks, @andreas_lds  The stored process has steam and package as result capabilities.    Regards, ... View more

Thanks @JuanS_OCS . Our SAS is 9.4M6 and DFLANG is setting to English. Sybase database are en WLATIN1.We use SAS EG. We have SAS/ACCESS Interface to SAP ASE. The same occurs when we access DB2 or Sybase IQ.    Regards,  ... View more