/scripts/ahub.form.attachments.js
0

System shutdown during online backup

May 31, 2017 at 07:49 PM

181

avatar image

Hi SAP experts.

Our PRD system has running and stable for about two years, but two nights ago it began to shutdown itself. Checking Syslog and developer logs, I realized that a "DISPATCHER EMERGENCY SHUTDOWN" message appeared. The last action before the shutdown was the daily online backup that runs at 22:00. Could the backup job been affecting system's performance?

PS: This issue lay on PRD system so I'd have to initialice sap system manually in the morning until I find a solution.

PS2: We're running our PRD system on Windows server 2012R, MaxDB Database 7.8.09, 48Gb physical memory and 48,8 GB Page File Space.

PS3: Thank you in advance for your insights about tihs issue.

PS4: Here are the instance profile parameters:

icm/server_port_1 = PROT=SMTP,PORT=25000,T login/password_expiration_time = 90 FN_AUDIT = ++++++++_######.AUD rsau/max_diskspace/per_file = 500M rsau/enable = 1 DIR_AUDIT = H:\Audit_log abap/heaplimit = 160000000 abap/heap_area_total = 8000000000 abap/heap_area_nondia = 8000000000 abap/heap_area_dia = 8000000000 ztta/roll_extension = 8000000000 em/address_space_MB = 16384 em/blocksize_KB = 16384 rdisp/PG_LOCAL = 600 rdisp/PG_SHM = 131072 rdisp/ROLL_SHM = 131072 rdisp/ROLL_MAXFS = 131072 ztta/roll_area = 26000000 zcsa/calendar_ids = 800 zcsa/calendar_area = 2000000 rsdb/ntab/sntabsize = 60000 rsdb/esm/large_object_size = 32768 rsdb/esm/max_objects = 8000 rsdb/esm/buffersize_kb = 16384 rsdb/otr/max_objects = 8000 rsdb/otr/buffersize_kb = 16384 rtbb/max_tables = 4000 zcsa/db_max_buftab = 80000 rsau/max_diskspace/local = 200M rsau/selection_slots = 2 rsau/local/file = H:\Audit_log login/password_max_idle_initial = 14 login/min_password_letters = 2 login/min_password_specials = 1 login/min_password_uppercase = 2 login/min_password_lowercase = 3 login/min_password_digits = 2 icm/host_name_full = impsrvvm-isp.datacent rdisp/PG_MAXFS = 196608 rdisp/keepalive_timeout = 1800 SAPSYSTEMNAME = ISP SAPGLOBALHOST = impsrvvm-isp SAPSYSTEM = 00 INSTANCE_NAME = DVEBMGS00 enque/table_size = 65536 DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE) DIR_EXECUTABLE = $(DIR_INSTANCE)\exe sec/libsapsecu = $(ssl/ssl_lib) ssf/ssfapi_lib = $(ssl/ssl_lib) rdisp/wp_no_dia = 20 rdisp/wp_no_btc = 10 rdisp/max_wprun_time = 3600 # SAP parameters are set in the Old System zcsa/table_buffer_area = 480000000 rtbb/buffer_length = 80000 rsdb/obj/large_object_size = 8192000 zcsa/presentation_buffer_area = 70400000 # *** PERMANENT 731 CHANGE *** #ztta/short_area = 4000000 rsdb/obj/max_objects = 32000 icm/server_port_0 = PROT=HTTP,PORT=8000,TI login/min_password_lng = 8 rsdb/obj/buffersize = 131072 sap/bufdir_entries = 32000 rsdb/cua/buffersize = 48000 abap/buffersize = 2400000 rsdb/ntab/irbdsize = 240000 rsdb/ntab/ftabsize = 1000000 rdisp/max_comm_entries = 2000 #---------------------------------sapgui-- # SAP Message Server parameters are set in em/initial_size_MB = 49152 #ms/server_port_0 = PROT=HTTP,PORT=81$ ms/server_port_0 = PROT=HTTP,PORT=81$ rdisp/wp_no_enq = 1 rdisp/wp_no_vb = 10 rdisp/wp_no_vb2 = 3 rdisp/wp_no_spo = 10 rdisp/wp_no_spo_Fro_max = 4 dbs/ada/schema = SAPISP ssl/ssl_lib = $(DIR_EXECUTABLE)$(DIR_SEP)$ zcsa/system_language = S zcsa/second_language = E zcsa/installed_languages = DES login/system_client = 400 login/no_automatic_user_sapstar = 1 login/disable_multi_gui_login = 1 rsdb/ntab/entrycount = 800000 #abap/buffersize = 1200000 rdisp/tm_max_no = 1000 rdisp/max_alt_modes = 4 sapgui/user_scripting = TRUE
10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

4 Answers

Karl-Heinz Hochmuth
Jun 02, 2017 at 11:36 AM
0

Hi David,

usually, I would expect that Dispatcher will also write the reason to dev_disp log, why it shutdown itself ...?

One reason I remember is a too large time drift between local application server instance and database time.

Please provide the dispatcher log ... what are the last entries before the

"DISPATCHER EMERGENCY SHUTDOWN" message?

Best regards,

Kalle

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Hello David,

If possible, please provide the complete "dev_disp.old" trace (or at least the last 500 lines) so we can see the reason for the shutdown.

Regards,

Isaías

0
Raquel Gomez
Jun 07, 2017 at 09:04 AM
0

Hi David,

Where did you find "DISPATCHER EMERGENCY SHUTDOWN" message?

Please provide dispatcher trace file (dev_disp) so we can check error information before this emergency shutdown. This file should be located on work folder from affected application server.

Regards,
Raquel

Share
10 |10000 characters needed characters left characters exceeded
David Montoya Jul 06, 2017 at 02:59 PM
0

Please accept my apologies for my late feedback.

Thank you for your kind answers and suggestion. Issue was resolved by applying parameter modification recommended by Zero Administration Memory Management for Windows.

Regards,

David

Share
10 |10000 characters needed characters left characters exceeded
David Montoya Jul 06, 2017 at 02:59 PM
0

Please accept my apologies for my late feedback.

Thank you for your kind answers and suggestion. Issue was resolved by applying parameter modification recommended by Zero Administration Memory Management for Windows.

Regards,

David

Share
10 |10000 characters needed characters left characters exceeded
Skip to Content