There is a oracle database on a windows machine (say machine A) on which a trigger is written to detect a change to a particular Oracle table. This trigger is then expected to invoke a SAS program on another windows server (say machine B). The SAS is installed only on machine B and therefore cannot be executed directly from the machine A.
![]()
The SAS task name is [STPX_LP ]
Segmentation Violation Traceback of the Exception: /sas/install/SASFoundation/9.4/sasexe/sas(+0x15aa6e) [0x7f8997290a6e] /sas/install/SASFoundation/9.4/sasexe/sas(+0x4cb0b) [0x7f8997182b0b] /sas/install/SASFoundation/9.4/sasexe/tkmk.so(bkt_signal_handler+0x144) [0x7f8995b4d3c4] /lib64/libpthread.so.0(+0xf7e0) [0x7f8996d057e0] /sas/install/SASFoundation/9.4/sasexe/tkmk.so(skm_unlink+0x21) [0x7f8995b608e1] /sas/install/SASFoundation/9.4/sasexe/tkmk.so(skmMemAlloc+0x19e) [0x7f8995b5e54e] /sas/install/SASFoundation/9.4/sasexe/tk4aarm4.so(arm4createSubbuffer+0x9b5) [0x7f8983035705] /sas/install/SASFoundation/9.4/sasexe/tk4aarm4.so(arm4start+0x24bd) [0x7f8983020b3d] /sas/install/SASFoundation/9.4/sasexe/tk4aarm4.so(+0x5a2b) [0x7f8983014a2b] /sas/install/SASFoundation/9.4/sasexe/tkl4sas.so(+0x31d55) [0x7f898d98ad55] /sas/install/SASFoundation/9.4/sasexe/tkl4sas.so(Log4SASCallAppenders+0x1c7) [0x7f898d964cd7] /sas/install/SASFoundation/9.4/sasexe/tkl4sas.so(Log4SASSpewEvent+0xba) [0x7f898d964a8a] /sas/install/SASFoundation/9.4/sasexe/tkl4sas.so(LoggerLogEventEDC+0x17d) [0x7f898d9854bd] /sas/install/SASFoundation/9.4/sasexe/tkl4sas.so(LoggerLogEvent+0x3a) [0x7f898d9847aa] /sas/install/SASFoundation/9.4/sasexe/tkarm.so(tka_start+0xc53) [0x7f898c4a80b3] /sas/install/SASFoundation/9.4/sasexe/uwutrans(txnstrt+0x276) [0x7f892d526736] /sas/install/SASFoundation/9.4/sasexe/sasxfnc(yfxfn+0x1ff) [0x7f895614a69f] /sas/install/SASFoundation/9.4/dbcs/sasexe/sasxmac(yjsysf+0xe74) [0x7f8960c68534] /sas/install/SASFoundation/9.4/dbcs/sasexe/sasxmac(yjoch+0x2c55) [0x7f8960c79635] /sas/install/SASFoundation/9.4/dbcs/sasexe/sasxshel(ytscan+0x2543) [0x7f8983b7b6e3] /sas/install/SASFoundation/9.4/dbcs/sasexe/sasxshel(yjdelta+0x33) [0x7f8983b61183] /sas/install/SASFoundation/9.4/dbcs/sasexe/sasxmac(+0x24530) [0x7f8960c65530] /sas/install/SASFoundation/9.4/dbcs/sasexe/sasxmac(yjintrp+0x2180) [0x7f8960c61380] /sas/install/SASFoundation/9.4/dbcs/sasexe/sasxshel(+0x50a82) [0x7f8983b7ca82]
A segmentation violation error and stored process failure might occur while processing the%apmrequestinit macro using the SAS ® Stored Process Server, pooled workspace server, or standard workspace server. The%apmrequestinit macro is part of the EMI framework that can be enabled for SAS ® Environment Manager monitoring. The segmentation violation occurs when the logon ID for the connecting user exceeds approximately 40 characters in length. The following traceback appears in the server log file. ERROR: Generic critical error.Currently the only circumvention is to disable the EMI framework for the stored process server, pooled workspace server, and workspace server:. On the service architecture framework machine, change to the SAS-configuration-directory/Lev1/Web/SASEnvironmentManager/emi-framework/bin directory. From a command line, issue the command./emiinit.sh -disable APM (UNIX) or emiinit.bat -disable APM (Windows) to disable only the APM ETL.
![]()
Issue the command./emiinit.sh -disable ALL (UNIX) or emiinit.bat -disable ALL (Windows) if you want to disable the APM, ACM, and solution kit ETLs.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
February 2023
Categories |