Hello there!   I noticed StoredProcessServer writes a log real-time. If I turn on tracing of db requests: OPTIONS SASTRACE=',,,ds' sastraceloc=saslog nostsuffix sql_ip_trace=(note,source) msglevel=i fullstimer; I see what StoredProcessServer do right now. But BatchServer uses another way. It writes information only when data step have done fully. How to configure BatchServer for logging information in real-time? ... View more

Hello, experts!   I have a problem with executing scheduled job from Management console using LSF.   A .sh script is executed from LSF. It is a shell over the execution of the sas command. The required deployed stp (deployed job) and sas system options are passed to the .sh script as parameters.   The sas command inside .sh script looks as follows: /sas/SAS94/SASFoundation/9.4/sas -xcmd -noterminal -nosyntaxcheck -autoexec ./autoexec.sas -sysin ./scripts/$SCRIPT.sas -nolog -noprint -altlog $LOG_FILE   When the command crashes, there are no entries in altlog. When trying to redirect the error output stream to a file, we get a certain error: ERROR: Recursive Segmentation Violations - system exiting    This error appears every day with multiple jobs. The problem is that it is not related to any particular job. Today a job can work successfully, and tomorrow it will fall into an error. Some of the jobs (most of them) run successfully, some of them do not. In case of detecting a problem with the start of a job, restarting the job manually helps.   There are no problems with RAM utilization on the server. Could you please tell me what this problem may be related to? ... View more

Hello everyone! Does anyone have SAS and ClickHouse integration on projects? I am trying to establish a connection via SAS ACCESS TO ODBC with ClickHouse, but nothing is working. isql is working successfully, but it does not work through SAS.   I have two cases: 1) odbc.ini [ClickHouse] Description = connection to ClickHouse DNS = clickhouse ServerName = dwh-********* Driver = /sas/clickhouse-odbc-1.2.1-Linux/lib64/libclickhouseodbc.so database = default UID = *** PWD = *** Port = 8123   libname click ODBC DATAsrc=ClickHouse SCHEMA=default USER=*** PASSWORD=***; NOTE: Libref CLICK was successfully assigned as follows:            Engine: ODBC            Physical Name: ClickHouse    But there are no tables, and they are not registered in SAS MC. Without any obvious error in the log.   When I try to execute: proc sql; connect to odbc; execute( select 1) by click; quit;   As a result, I got an error: ERROR: CLI error trying to establish connection: [DataDirect] [ODBC lib] Driver Manager Message file not found. Please check for the value of InstallDir in your odbc.ini.   LD_LIBRARY_PATH contains /sas/clickhouse-odbc-1.2.1-Linux/lib64/   isql -v ClickHouse Connected! SQL> SELECT 1 [S1000]Connection refused [ISQL]ERROR: Could not SQLExecute   2) odbc.ini [ClickHouse] Description = connection to ClickHouse DNS = clickhouse Server = dwh-*********        Driver = /sas/clickhouse-odbc-1.2.1-Linux/lib64/libclickhouseodbc.so database = default UID = *** PWD = *** Port = 8123   libname click ODBC DATAsrc=ClickHouse SCHEMA=default USER=*** PASSWORD=***; ERROR: CLI error trying to establish connection: 523 650   isql -v ClickHouse Connected! SQL> SELECT 1 1 1 1 rows fetch   ... View more

Hello everyone! When I try to deploy/activate an RTDM diagram via the SAS CIS WEB interface, an error appears in the SASDecisionServicesAdministration6.4.log (full version in the file). If you try many times, sometimes it turns out to deploy/activate the diagram. If I do it through the SAS Management Console, then there are no errors. Small diagrams are activated successfully more often than large ones.   I tried to clean temporary files (work, logs, temp) and restart SASServer7_1, it helps for a while. I tried to increase the timeout in ./SASServer7_1/conf/server.xml , it didn't help. Synchronization of the Engine server cache is normal.   I also tried to raise the specified parameters for SASServer7_1 https://documentation.sas.com/doc/en/bicdc/9.4/appsrvtuning/n11d31ckagwavun102c8qtj5rm9r.htm   It seems to me that the performance of SASServe7_1 is not enough, but heap and cpu is normal.   ERROR com.sas.dcsv.admin.rest.controllers.DecisionFlowsController - An internal error occurred in the server while processing resource at /SASDecisionServicesAdministration/rest/decisionFlows with Http Method POST. Please contact your system administrator. More details may be available in the system log files. com.sas.analytics.ph.RTDMException: org.springframework.remoting.RemoteAccessException: Could not access HTTP invoker remote service at [p-host:8343/RTDM/Manager]; nested exception is java.net.SocketTimeoutException: Read timed out at com.sas.rtdm.EngineConnector$1.invoke(EngineConnector.java:122) at com.sun.proxy.$Proxy349.synchronizeCache(Unknown Source) at com.sas.dcsv.admin.DecisionServicesAdministration.synchronizeEngine(DecisionServicesAdministration.java:190) .... Caused by: org.springframework.remoting.RemoteAccessException: Could not access HTTP invoker remote service at [[p-host:8343/RTDM/Manager]; nested exception is java.net.SocketTimeoutException: Read timed out at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.convertHttpInvokerAccessException(HttpInvokerClientInterceptor.java:213) at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.invoke(HttpInvokerClientInterceptor.java:145) ... Caused by: java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) ... ... View more