Hello everyone,
I'm installing SAS 9.4 on linux redhat 8.2 server.
I have installed meta , compute and mid-tier server . all the solution works fine but I have encountred a problem during the deploying of SAS Risk Stratum content .
I'm using rqscdt.v12.2022 and rqsrsc.v12.2022
the is the command I run to deploy sas risk stratum content :
./cdt_unix.sh -metaserver sas-metadata.int -metaport 8561 -metarepository Foundation -metauser rgfadmin -metapass {SAS002}A44B192F215FDFGG1817BBF5559AB269 -lev_path /app/sas/sasconfig/Lev1 -content_path /app/sas/sasconfig/Lev1/AppData/SASIRM/fa.rmc.2022.12 -actions_xlsx actions.xlsx -log_path /tmp/rgf/risk/log -load_sample YESthis is the output I got :
-----------------------------------------------
Content Deployment Tool
-----------------------------------------------
Checking input parameters..
-> Option -user has not been specified. Using the provided -metauser value
-> Option -password has not been specified. Using the provided -metapass value
START TIME :: Thu Jul 13 13:25:28 CET 2023
SAS exited with : 2. Log file: /tmp/rgf/risk/log/cr_tool.log.
END TIME :: Thu Jul 13 13:25:31 CET 2023
Checking errors...
1 The SAS System Thursday, July 13, 2023 01:25:00 PM
Looking for SAS errors .... /tmp/rgf/risk/log/cr_tool.log
Error Found :: Line Number:774::ERROR: error loading module 'envluamap' from file '/tmp/rgf/risk/log/envluamap.lua':
Error Found :: Line Number:780::ERROR: There was an error submitting the provided code
Error Found :: Line Number:809::ERROR 180-322: Statement is not valid or it is used out of proper order.
Error Found :: Line Number:819::ERROR 180-322: Statement is not valid or it is used out of proper order.
Error Found :: Line Number:832::ERROR: Invalid physical name.
Error Found :: Line Number:833::ERROR: Error in the FILENAME statement.
Error Found :: Line Number:862::ERROR 180-322: Statement is not valid or it is used out of proper order.
Error Found :: Line Number:867::ERROR 180-322: Statement is not valid or it is used out of proper order.
Error Found :: Line Number:872::ERROR 180-322: Statement is not valid or it is used out of proper order.
Error Found :: Line Number:909::ERROR 180-322: Statement is not valid or it is used out of proper order.
Error Found :: Line Number:929::ERROR 180-322: Statement is not valid or it is used out of proper order.
Error Found :: Line Number:935::ERROR 180-322: Statement is not valid or it is used out of proper order.
Error Found :: Line Number:953::ERROR 180-322: Statement is not valid or it is used out of proper order.
Error Found :: Line Number:1025::ERROR 180-322: Statement is not valid or it is used out of proper order.
Error Found :: Line Number:1031::ERROR 180-322: Statement is not valid or it is used out of proper order.
Error Found :: Line Number:1138::ERROR 180-322: Statement is not valid or it is used out of proper order.
Error Found :: Line Number:1178::ERROR 180-322: Statement is not valid or it is used out of proper order.
Error Found :: Line Number:1185::ERROR 180-322: Statement is not valid or it is used out of proper order.
Error Found :: Line Number:1192::ERROR 180-322: Statement is not valid or it is used out of proper order.
Error Found :: Line Number:1324::ERROR 180-322: Statement is not valid or it is used out of proper order.
Error Found :: Line Number:1335::ERROR: Errors printed on pages 10,11,12,13,14,16,17,18,19.
Looking for Dataload errors .... /tmp/rgf/risk/log/cr_tool.log
No Errors Foundlog from crt_tool :
#######RUNNING LOAD_PROPERTIES#######
{ "items" : [ {"name" : "RMCDR_USER" , "value" : "rmcdr" } , {"name" : "RMCDR_PASSWORD" , "value" : "rmcdr" } ] }
INFO:: RMCDR_USER=rmcdr
INFO:: RMCDR_PASSWORD=rmcdr
NOTE: The import data set has 29 observations and 3 variables.
INFO:Loading Global Config Table.
ERROR: error loading module 'envluamap' from file '/tmp/rgf/risk/log/envluamap.lua':
/tmp/rgf/risk/log/envluamap.lua:58: invalid escape sequence near '\['
stack traceback:
[C]: in ?
[C]: in function 'require'
SUBMIT block:153: in main chunk
ERROR: There was an error submitting the provided code
NOTE: The SAS System stopped processing this step because of errors.
NOTE: Due to ERROR(s) above, SAS set option OBS=0, enabling syntax check mode.
This prevents execution of subsequent data modification statements.
NOTE: PROCEDURE LUA used (Total process time):
real time 0.39 seconds
cpu time 0.23 seconds
