cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
John_Wick
‎04-25-2024
  • 31 Posts
  • 6 Likes Given
  • 6 Solutions
  • 5 Likes Received

Re: Problem with SASMerchIntelGridSvr5.41

by Obsidian | Level 7 in Administration and Deployment
‎04-10-2024 08:54 AM
‎04-10-2024 08:54 AM
It was the problem with value RPO_PLAN_MEMBER_SK in the table DI_DM.RPO_PLAN_MEMBER. Id has become more than MAX_VALUE of int in the C language. So it was an overflow problem.   ... View more

Problem with SASMerchIntelGridSvr5.41

by Obsidian | Level 7 in Administration and Deployment
‎04-07-2024 01:37 PM
‎04-07-2024 01:37 PM
Hi all!  I'm facing a problem with SASMerchIntelGridSvr5.41. If you run plan optimization in Regular Price Plans in SAS Merchandise Intelligence, an error appears in the interface: ERROR: A fatal error was encountered while processing the STP request.   An error appears in the SASMerchIntelGridSvr5.41 log:   2024-04-05 18:54:53,131 [http-bio-5191-exec-8-0509] DEBUG com.sas.solutions.di.server.invoke - <- com.sun.proxy.$Proxy13.getRequestStatus took 3 ms. 2024-04-05 18:55:00,994 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - TKMI LOG: sk-sas-grid: rpo_optimize.2.log (LOCAL) 2024-04-05 18:55:00,994 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - <U+FEFF>20240405:18.54.45.93: running command: run='rpo_optimize' 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - 20240405:18.54.45.97: Loading Dim for partition_id=1 gps=0 sk=244810 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - 20240405:18.54.57.34: Completed Loading Dim for partition_id=1 gps=0 sk=244810 in 11 second s (dim -> 162 MB/s, io adapter -> ~0.0 MB/s) 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - 20240405:18.54.58.70: ERROR: consumer thread 'c_(null)' encountered a fatal error 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - 20240405:18.54.58.70: 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - ERROR: TKTException code = 10 (Domain exception) 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - from /sas/SASHome/SASFoundation/9.4/sasexe/tkmi.so 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - #4 0x00007fede1e00c46 in tkmi_exception_handler () 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - from /sas/SASHome/SASFoundation/9.4/sasexe/tkmi.so 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - #5 0x00007fedf000d3f2 in bktExcept () 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - from /sas/SASHome/SASFoundation/9.4/sasexe/tkmk.so 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - #6 0x00007fedf0011d0d in bkt_fpe () 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - from /sas/SASHome/SASFoundation/9.4/sasexe/tkmk.so 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - #7 0x00007fedf000da44 in bkt_signal_handler () 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - from /sas/SASHome/SASFoundation/9.4/sasexe/tkmk.so 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - #8 <signal handler called> 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - #9 0x00007fede1dfc153 in io_get_int () 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - from /sas/SASHome/SASFoundation/9.4/sasexe/tkmi.so 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - #10 0x00007fede20a538e in rpo_plan_member_cb () 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - from /sas/SASHome/SASFoundation/9.4/sasexe/tkmi.so 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - #11 0x00007fede1df7834 in process_rows () 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - from /sas/SASHome/SASFoundation/9.4/sasexe/tkmi.so 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - #12 0x00007fedf000b494 in sktMain () 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - from /sas/SASHome/SASFoundation/9.4/sasexe/tkmk.so 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - #13 0x00007fedf000d231 in bktMain () 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - from /sas/SASHome/SASFoundation/9.4/sasexe/tkmk.so 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - #14 0x00007fedf1418ea5 in 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - 20240405:18.54.58.70: start_thread () from /lib64/libpthread.so.0 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - #15 0x00007fedf0a04b0d in clone () from /lib64/libc.so.6 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - 2 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - 20240405:18.54.58.70: ERROR: Assertion failed: ! this->pc_error, file /sas/wky/mva-m1ro541/di/src/input_adapter.c, line 726 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - 20240405:18.54.58.70: Error while reading table '(null)' (see previous error message(s)) 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - 20240405:18.54.59.83: 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - ERROR: TKTException code = 6 (Access violation) 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - from /sas/SASHome/SASFoundation/9.4/sasexe/tkmi.so 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - #4 0x00007fede1e00c46 in tkmi_exception_handler () 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - from /sas/SASHome/SASFoundation/9.4/sasexe/tkmi.so 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - #5 0x00007fedf000d3f2 in bktExcept () 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - from /sas/SASHome/SASFoundation/9.4/sasexe/tkmk.so 2024-04-05 18:55:00,995 [RequestThread-359077] DEBUG com.sas.solutions.di.tkmiserver.dispatcher.TKMI - #6 0x00007fedf000da44 in bkt_signal_handler () 2024-   ... View more

"Naming Conventions" error when trying to select data from oracle data...

by Obsidian | Level 7 in SAS Enterprise Guide
‎03-19-2024 06:07 AM
‎03-19-2024 06:07 AM
Hello, experts! We have two SAS clusters that are deployed on different servers. Let it be SERVER 1 and SERVER 2.   We have a problem with selecting data from oracle database table on SEVER 1. Part of log with query and error looks like this: ------------------SERVER 1 LOG--------------------------- LIBNAME DWH_R ORACLE PRESERVE_COL_NAMES=YES PRESERVE_TAB_NAMES=YES DBMAX_TEXT=32767 READBUFF=7500 INSERTBUFF=7500 PATH=*** SCHEMA=*** USER=*** PASSWORD=*** NOTE: Libref DWH_R was successfully assigned as follows: Engine: ORACLE Physical Name: *** options validvarname=any; options sastrace=',,,ds' sastraceloc=saslog nostsuffix sql_ip_trace=(note, source) msglevel=i fullstimer; proc sql dquote=ansi; select * from dwh_r.'S0208$KBS_CHAT_BOT_SUGGEST'n;   ORACLE_4: Prepared: on connection 21 SELECT * FROM "DWH_STAGE2"."S0208$KBS_CHAT BOT_SUGGEST"   Summary Statistics for ORACLE are: Total SQL prepare seconds were: 0.000822 Total seconds used by the ORACLE ACCESS engine were 0.002057   ERROR: This DBMS table or view cannot be accessed by the SAS System because it contains column names that are normalized (uppercased) compare is performed. See "Naming Conventions" in the SAS/ACCESS documentation. not unique ------------------SERVER 1 LOG---------------------------   We think, that the problem is due to certain long names of table fields, which after being cut off (SAS accepts field names of no more than 30 characters) become the same like this two fields with long labels:   But in SAS, there is a special VALIDVARNAME option, which in any case will change the name to a unique one by adding an index to the end of the name, as shown in "Name" field in the picture above. This is what happens on our SERVER 2 (part of log with query): ------------------SERVER 2 LOG--------------------------- LIBNAME DWH_R ORACLE PRESERVE_COL_NAMES=YES PRESERVE_TAB_NAMES=YES DBMAX_TEXT=32767 READBUFF=7500 INSERTBUFF=7500 PATH=*** SCHEMA=*** USER=*** PASSWORD=*** NOTE: Libref DWH_R was successfully assigned as follows: Engine: ORACLE Physical Name: *** options validvarname=any; options sastrace=',,,ds' sastraceloc=saslog nostsuffix sql_ip_trace=(note, source) msglevel=i fullstimer; proc sql dquote=ansi outobs=10; select * from dwh_r.'S0208$KBS_CHAT_BOT_SUGGEST'n;   ORACLE_5: Prepared: on connection 6 SELECT * FROM "DWH_R"."S0208$KBS_CHAT BOT_SUGGEST"   SQL_IP_TRACE: None of the SQL was directly passed to the DBMS.   ORACLE_6: Executed: on connection 6 SELECT statement  ORACLE_5   WARNING: Statement terminated early due to OUTOBS=10 option.   Summary Statistics for ORACLE are: Total row fetch seconds were: 0.336985 Total SQL execution seconds were: 0.031686 Total SQL prepare seconds were: 0.001000 Total seconds used by the ORACLE ACCESS engine were 1.934726   NOTE: Procedure SQL used (Total process time): ------------------SERVER 2 LOG---------------------------   What points have been checked already? different combination of validvarname and validmemname options (this did not help) output comparison of proc options command on both workspace server's (this did not help) Attempt to reproduce the error on SERVER 2 (this step was unsuccessful) Both servers use SAS 9.4:  SERVER 1 - 9.4 (TS1M3) SERVER 2 - 9.4 (TS1M7) There is a feeling that SAS on SERVER 1 does not respond to the VALIDVARNAME option. Can version of SAS affect this? We also found SAS note for this error - 16835 - An error occurs when DBMS tables do not have unique column names and you try to reference a specific table in SAS® code. It suggests creating a VIEW of this table, but we want to avoid this, because on SERVER 2, select to the table works perfectly without creating a VIEW.    I will be grateful for any useful information and any thoughts on this matter! ... View more

SAS Server 6 stops returning information to the scheduler about comple...

by Obsidian | Level 7 in Administration and Deployment
‎01-25-2024 09:40 AM
‎01-25-2024 09:40 AM
Hello, experts! Periodically, we encounter a problem when a queue of unfulfilled campaigns that have been scheduled begins to accumulate in the LSF scheduler. At the same time, in the SASCICore logs of the 6th server, we see that the campaigns have been completed, but for some reason SASServer6 does not send a response about the execution to the scheduler. There are no errors in the logs. Restarting SASServer6 solves this problem and everything returns to normal. We believe that the reason is caused by an overflow of HEAP memory on the 6th server, since we saw peak values in the Garbage Collector logs and at this point a problem could occur. Has anyone else encountered a similar problem? Are there any ways to solve it? ... View more

Re: Setting logging of BatchServer to real-time

by Obsidian | Level 7 in Administration and Deployment
‎11-27-2023 05:02 AM
1 Like
‎11-27-2023 05:02 AM
1 Like
Thanks you! Need to change in Scheduler manager a param in execute command of job from -logparm "rollover=session" to -logparm "rollover=session write=IMMEDIATE" ... View more

Setting logging of BatchServer to real-time

by Obsidian | Level 7 in Administration and Deployment
‎11-23-2023 08:20 AM
‎11-23-2023 08:20 AM
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

Re: Recursive Segmentation Violations - system exiting error while ex...

by Obsidian | Level 7 in Administration and Deployment
‎10-27-2023 08:47 AM
2 Likes
‎10-27-2023 08:47 AM
2 Likes
The cause of this error could not be found. But we managed to use the following workaround:   Using bhist -all, determine the error status in LSF with which the jobs are falling (in our case Exit code=102. Also with SIGSEGV, Exit code=139 is possible) Define the queue in which the jobs are executed (in our case QUEUEUE_NAME=normal. The queue name is also specified when using bhist -all) In the file <LSF-root-directory>/conf/lsbatch/sas_cluster/configdir/lsb.queues Add the REQUEUE_EXIT_VALUES and MAX_JOB_REQUEUE parameters: ... Begin Queue QUEUEUE_NAME=normal ... REQUEUE_EXIT_VALUES=139 102 MAX_JOB_REQUEUE=3 ... End Queue ... Save the changes This will allow LSF to restart jobs in case of errors 139 and 102. The number of restarts is adjusted in MAX_JOB_REQUEUE. In our case it is 3 times. ... View more

Re: Recursive Segmentation Violations - system exiting error while ex...

by Obsidian | Level 7 in Administration and Deployment
‎10-26-2023 11:44 AM
‎10-26-2023 11:44 AM
The problem is that the error occurs at the stage of running the command itself, which I specified in the problem description. ... View more

Re: Recursive Segmentation Violations - system exiting error while ex...

by Obsidian | Level 7 in Administration and Deployment
‎10-26-2023 09:50 AM
‎10-26-2023 09:50 AM
1) Yes, we have multiple machines. SEGVs happen on a specific machine 2) This happens for user "lsfadmin", because the scheduled job is running under that user 3) No, it may happen for different sas programs 4) It most often occurs in a specific time frame that is fairly spread out over a period of time ... View more

Recursive Segmentation Violations - system exiting error while execut...

by Obsidian | Level 7 in Administration and Deployment
‎10-26-2023 06:29 AM
‎10-26-2023 06:29 AM
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

Up the performance of deploying RTDM diagrams

by Obsidian | Level 7 in Administration and Deployment
‎06-19-2023 10:49 AM
‎06-19-2023 10:49 AM
Hello!  Faced with the problem of a long deployment of RTDM diagrams on the engine server. Approximately 10 minutes each. Tell me, please, what to pay attention to, what can be the limiting stage?   Previously, there was a problem with ReadTimedOut during deployment. I increased ReadTimedOut, but I would like to speed up the process. ... View more

Selecting the desired SASApp from several for the system SAS MA

by Obsidian | Level 7 in Administration and Deployment
‎06-12-2023 07:25 AM
‎06-12-2023 07:25 AM
Hello experts!   We have installed the SAS MA system in the classical architectural scheme: meta+mid+compute. Now, as always, SAS MA requests from SELECT nodes work on the PWS servers of the SASApp compute server.   There was a need to deploy an additional compute server with its own SASApp2 to the existing architecture, on which it is planned to run ETL-processes using the same libraries as SASApp from the initial configuration.   Question: What setting is responsible for selecting the required SASApp to run regular SAS MA diagram nodes (for example, select)? If for stored processes you can still choose your own SASApp for calculation (via SAS MC), then for such regular nodes we have not yet been able to find such a setting. We would like to avoid the situation when calculations can be made from SAS MA both on SASApp and on SASApp2. ... View more

Re: SAS Access to ODBC for ClickHouse

by Obsidian | Level 7 in Administration and Deployment
‎06-02-2023 11:16 AM
2 Likes
‎06-02-2023 11:16 AM
2 Likes
To change ODBC Driver Manager from DataDirect to unixODBC, you should set unixODBC libraries in LD_LIBRARY_PATH first.   For example: in <SASHome>/SASFoundation/9.4/bin/sasenv_local LD_LIBRARY_PATH=/usr/local/unixODBC/lib:$LD_LIBRARY_PATH export LD_LIBRARY_PATH   ... View more

Re: SAS Access to ODBC for ClickHouse

by Obsidian | Level 7 in Administration and Deployment
‎06-01-2023 05:46 AM
‎06-01-2023 05:46 AM
The problem was in the confict with the ODBC DataDirect driver for PostgreSQL. Because DataDirect appears in the error, although the ClickHouse driver is not DataDirect. The connection on the other server was successful. ... View more

SAS Access to ODBC for ClickHouse

by Obsidian | Level 7 in Administration and Deployment
‎05-26-2023 08:59 AM
‎05-26-2023 08:59 AM
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
Contact Me
Online Status
Offline
Date Last Visited
‎04-25-2024 08:52 AM
Likes given to
Likes from
Quick links