Hi all,
I am applying EHP6 for ERP. During ACT_UPG phase I tried to stop shadow instance and incress some profile parameters and rester shadow agian and repeat the ACT_UPG phase again.
I have selected as Batch process 3 and maximum uptime process 1 and R3trans process 3
There is no error in TCO st22 or sm21.
I can see the batch job
RDDMASGL is active and form job log I have this massage:
Job started
Step 001 started (program RDDMASGL, variant IMPACTMRG, user ID DDIC)
Start of mass activation 08:47:41
And I have just one batch job runing in SM50.
BGD 14939 Running Yes 6826 RADMASDSC 000 DDIC
And non og logs, tmp or data logs in /abap/ in shoadow get update.
My question is should I restar sap server after changing profile parameter for shadow or it is enough with restart shadow instance?
---------------------------------------------------------------------------
I have this log from last part of SAPup.ECO from shadow.
### Phase MAIN_SHDRUN/ACT_UPG:
SAPup> Starting subprocess with PID 15031 in phase 'ACT_UPG' at 20130911084738
ENV: DIR_LIBRARY=/r3d/mnt/R3U/start/SUM/abap/exe
ENV: JAVA_HOME=/opt/java1.5/jre
ENV: LD_LIBRARY_PATH=/r3d/mnt/R3U/start/SUM/abap/exe:/r3d/mnt/R3U/start/SUM/jvm/jre/lib/ia64/server:/r3d/mnt/R3U/start/SUM/jvm/jre/lib/ia64:/r3d/mnt/R3U/start/SUM/jvm/jre/../lib/ia64
ENV: NLS_LANG=AMERICAN_AMERICA.UTF8
ENV: ORACLE_BASE=/oracle
ENV: ORACLE_HOME=/oracle/R3U/112_64
ENV: ORACLE_SID=R3U
ENV: PATH=/r3d/mnt/R3U/start/SUM/abap/exe:/oracle/R3U/112_64/bin:/opt/java1.5/jre/bin:.:/home/r3uadm:/usr/sap/R3U/SYS/exe/run:/usr/bin:/usr/ccs/bin:/usr/contrib/bin:/usr/contrib/Q4/bin:/opt/perl/bin:/opt/gvsd/bin:/opt/ipf/bin:/opt/nettladm/bin:/opt/fcms/bin:/opt/wbem/bin:/opt/wbem/sbin:/opt/sas/bin:/opt/graphics/common/bin:/opt/atok/bin:/usr/bin/X11:/usr/contrib/bin/X11:/opt/sec_mgmt/bastille/bin:/opt/caliper/bin:/opt/drd/bin:/opt/dsau/bin:/opt/dsau/sbin:/opt/resmon/bin:/opt/firefox:/opt/gnome/bin:/opt/perf/bin:/opt/propplus/bin:/usr/contrib/kwdb/bin:/opt/perl_32/bin:/opt/perl_64/bin:/opt/prm/bin:/opt/sfm/bin:/opt/swm/bin:/opt/sec_mgmt/spc/bin:/opt/ssh/bin:/opt/swa/bin:/opt/hpsmh/bin:/opt/thunderbird:/opt/sentinel/bin:/opt/langtools/bin:/opt/wlm/bin:/opt/gwlm/bin:/opt/hpnpl//bin
ENV: SAPDATA_HOME=/oracle/R3U
ENV: SAPSYSTEMNAME=R3U
ENV: auth_shadow_upgrade=1
ENV: dbms_type=ORA
ENV: dbs_ora_schema=SAPR3
ENV: dbs_ora_tnsname=R3U
EXECUTING /r3d/mnt/R3U/start/SUM/abap/exe/tp pf=/r3d/mnt/R3U/start/SUM/abap/var/ACTUPG.TPP put R3U
This is tp version 380.08.41 (release 720, unicode enabled)
Looking for effective putsteps ... ... ready (looking for putsteps
Any advice if this phase is working?
Thanks
Request clarification before answering.
Hello
Were the parameter modifications and the restart done in the shadow system ?
Connect to the shadow system and perform a check status of the running job.
Tx SM37 - RDDMASGL - Job - Check status
Regards
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello ,
Thanks for all your replys.
I have change parameter just in shadow instance befor I get memory error. And restart just shadow instance as note 1387739.
RDDMASGL DDIC Active 11.09.2013 08:47:41 13.832 0
TCO SM37 - job RDDMASGL status shows aktiv:
Job started
Step 001 started (program RDDMASGL, variant IMPACTMRG, user ID DDIC)
Start of mass activation 08:47:41
And nothing more.
Thanks
Here are few things which you can check.
1 - Check the start time of the job and the time when you restarted the SAP shadow system.
2 - Check the shadow system work process trace file for this job.
3 - Check Tx SM50 for this work process whether the status, report name and other parts are getting changed.
Be aware that this is one of the longest phases in the entire upgrade process.
Regards
RB
Hello,
No need to start complete server. Restarting only the shadow instance is okay for the parameters to take effect.
Also ACT_UPG is a very long running phase and sometimes there might not be any update in the logs for some time. Please make sure that DB stats are updated as it might influence the runtime of this phase. Parallisation do not work during this phase so important thing will be your DB performance and memory settings.
Regards,
Gaurav
Hello,
RDDMASGL batch Job stopet with:
Internal session terminated with runtime error SYSTEM_NO_TASK_STORAGE.
I had allready increased parameters:
abap/heap_area_dia 900000000
abap/heap_area_total 49000000000
abap/heap_area_nondia 49000000000
ztta/roll_extension 12000000000
ztta/roll_area 500000000
Have I miss some thing?
Thanks for any advice.
Hello
According to the SAP Note 1387739 - Out of memory errors during shadow system operation
SAP recommendation :
abap/heap_area_total = 10000000000
abap/heap_area_nondia = 10000000000
ztta/roll_area = 20000000
You implemented :
abap/heap_area_dia = 900000000
abap/heap_area_total = 49000000000
abap/heap_area_nondia = 49000000000
ztta/roll_extension = 12000000000
ztta/roll_area = 500000000
Please correct the parameters and restart the shadow system.
Regards
RB
Hello,
Thanks for any help for this problem
The RDDMASGL batch Job stopet again after 5 houre with:
Internal session terminated with runtime error SYSTEM_NO_TASK_STORAGE.
I had allready increased parameters:
SAP recommendation :
abap/heap_area_total = 10000000000
abap/heap_area_nondia = 10000000000
ztta/roll_area = 20000000
ANy idea?
Thanks
Hi,
Please check the below note .
Note 1275873 - Memory bottleneck during DDIC activation during EHP import
Thanks
Rishi abrol
Hi,
Thanks for help,
Here is some part of log files:
From SAPUP.ECO
-------------------
### Phase MAIN_SHDRUN/ACT_UPG:
SAPup> Starting subprocess with PID 12208 in phase 'ACT_UPG' at 20130911214104
ENV: DIR_LIBRARY=/r3d/mnt/R3U/start/SUM/abap/exe
ENV: JAVA_HOME=/opt/java1.5/jre
ENV: LD_LIBRARY_PATH=/r3d/mnt/R3U/start/SUM/abap/exe:/r3d/mnt/R3U/start/SUM/jvm/jre/lib/ia64/server:/r3d/mnt/R3U/start/SUM/jvm/jre/lib/ia64:/r3d/mnt/R3U/start/SUM/jvm/jre/../lib/ia64
ENV: NLS_LANG=AMERICAN_AMERICA.UTF8
ENV: ORACLE_BASE=/oracle
ENV: ORACLE_HOME=/oracle/R3U/112_64
ENV: ORACLE_SID=R3U
.
.
ENV: ngtools/bin:/opt/wlm/bin:/opt/gwlm/bin:/opt/hpnpl//bin
ENV: SAPDATA_HOME=/oracle/R3U
ENV: SAPSYSTEMNAME=R3U
ENV: auth_shadow_upgrade=1
ENV: dbms_type=ORA
ENV: dbs_ora_schema=SAPR3
ENV: dbs_ora_tnsname=R3U
EXECUTING /r3d/mnt/R3U/start/SUM/abap/exe/tp pf=/r3d/mnt/R3U/start/SUM/abap/var/ACTUPG.TPP put R3U
This is tp version 380.08.41 (release 720, unicode enabled)
Looking for effective putsteps ... ... ready (looking for putsteps)
ERROR: stopping on error 12 during DD ACTIVATION
stopping on error 12 during DD ACTIVATION
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
SAPup> Process with PID 12208 terminated with status 12 at 20130912030834!
From ACTUPG.ELG
------------------
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPA-603DDINEAAPPL.R3U
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDMASGL", no.: "21410600")
1AEPU320 See job log"RDDMASGL""21410600""R3U"
1 ETP111 exit code : "12"
From ST22
---------------Runtime Errors SYSTEM_NO_TASK_STORAGE
Date and Time 12.09.2013 03:07:26
Short Text
Unable to fulfil request for 1701536 bytes of storage space.
Hi
Here is value of some parameters.
.
.
.
rdisp/max_wprun_time = 0
abap/apg_settings = off
zcsa/presentation_buffer_area = 2000000
zcsa/table_buffer_area = 10000000
zcsa/db_max_buftab = 10000
rtbb/buffer_length = 5000
rtbb/max_tables = 500
# *** CHANGE for the shadow instance ***
#ipc/shm_psize_10 = 40000000
ipc/shm_psize_10 = 128000000
# *** CHANGE for the shadow instance ***
#ipc/shm_psize_40 = 68000000
ipc/shm_psize_40 = 112000000
abap/heap_area_dia = 900000000
abap/heap_area_total = 12000000000
abap/heap_area_nondia = 12000000000
ztta/roll_extension = 12000000000
ztta/roll_area = 20000000
rdisp/autoabaptime = 0
zcsa/system_language = E
dbs/ora/schema = SAPR3
# *** CHANGE for the shadow instance ***
rdisp/accept_remote_trace_level = 0
transport/during_upgrade = ON
rdisp/system_needs_spool = false
snc/enable = 0
rdisp/j2ee_start = 0
rdisp/start_icman = false
vmcj/enable = off
abap/package_check = off
rdisp/dynamic_wp_check = false
Thanks
Hi,
How much physical memory you have allocated for this server..
Can u allocate more memory EM/initial_size_MB
ztta/roll_area = 6500000
ztta/roll_extension = 2000683008
ztta/roll_extension_dia = 2000683008
ztta/roll_extension_nondia = 2000683008
abap/heap_area_dia = 30000000000
abap/heap_area_nondia = 30000000000
abap/heap_area_total = 30000000000
abap/buffersize = (ceil($(em/initial_size_MB)*1024*0.15/4096) * 4096)
abap/shared_objects_size_MB = ($(em/initial_size_MB)*0.02)
em/global_area_MB = ($(em/initial_size_MB) * 0.05)
em/initial_size_MB = ($(PHYS_MEMSIZE) * 0.7)
em/max_size_MB = ($(em/initial_size_MB))
zcsa/table_buffer_area = (max(30000000,($(em/initial_size_MB) * 1024 * 1024 * 0.05)))
Take the backup.
Dont forget to run sappfpar check pf=profile
Hope you system can be started after that..
Thanks
Rishi abrol
Hi ,
as mentioned earlier please take copy of the existing profile.
Stop the shadow system
Once you have taken the copy vi the instance profile and change the value that you can find in the instance profile.
save it and then do sappfpar check for the instance profile.
adjust the ipc parameters.
Hope system comes up.
Thanks
Rishi abrol
Dear Reagan,
I have changed the parameters according to the Note 1387739
than stop and start shadow instance and got succeeded.
my question is the parameter abap/heap_area_dia was not mentioned in the note and it was there in the file i have change that parameter same as nodia parameter value.What about area_total value is ok?
Upgrade is successfully done.
Thanks
The ulimit values for all users are stored in this file.
Check the contents of this file
Regards
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello
Try with a different kernel
Regards
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am tring to download kernel version 300 now. I had stop alle sap installation on this server for try one more time. If not works I will change kernel and try again.
I am In perprocessing Phase. I think It is possible to reset this upgrade and start again.
But must intresting is to know what is the problem.
Is any test I can du in shadow system to see if there is some error?
Thanks again a lot for this help.
Reza
Hello
Make sure there is sufficient memory available on the machine.
Secondly set these parameters in the instance profile of the shadow system.
ztta/roll_extension = 64000000000
abap/heap_area_total = 5000000000
abap/heap_area_nondia = 5000000000
ztta/roll_area = 10000000
abap/buffersize = 400000
If possible restart the main system and the shadow system after cleaning the shared memory segments from the OS level.
Check the ulimits of the sidadm user. Set them to unlimited and restart the system.
Regards
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
su - sidadm
ulimit -a
Refer this link
Regards
RB
Hello,
I did set there parameter values in shadow system:
ipc/shm_psize_10 = 128000000
# *** CHANGE for the shadow instance ***
#ipc/shm_psize_40 = 68000000
ipc/shm_psize_40 = 112000000
abap/heap_area_dia = 5000000000
abap/heap_area_total = 5000000000
abap/heap_area_nondia = 10000000000
ztta/roll_extension = 64000000000
ztta/roll_area = 10000000
I will try with
abap/heap_area_total = 10000000000
abap/heap_area_nondia = 10000000000
this too.
Thanks
Hi Rishi,
Here is screen shot of st06
Can I have some explanation for:
You can run glance on the server and i needed the st02 of the shadow system .?
screen shot is from shadow instance.
Please attach the os level instance file.? Where can I find this fil?
The screen shot of shadow system should have 7 gb of extended memory but this one has 4.?
You mean I should add 3 more gb extended memory in shadow instance. Or incress the profile parameter?
Thanks again
Hi,
What else is running on the server. this has 64 gb of memory and out of which only 5.4 gb is free when the upgrade job is not running. I think that you need to get more memory free on the server or stop any extra app running on this server that is not used and re run the phase.
If i see your swap is three times of the actual memory so should be 192 GB but is 155GB. I dont think it should impact .
you can see the memory usage when you run glance at os level.
I want the instance profile file of the shadow system.
But changing the profile parameters will not help if you don't have free memory on the server.
Thanks
Rishi Abrol
Hi,
Yes Please stop all the application and the database that you can stop.
As you have configured the below parameters to 10 gb so you need to have at-least close to 20 to 25gb free
abap/heap_area_dia = 10000000000
abap/heap_area_total = 10000000000
abap/heap_area_nondia = 10000000000
Please try to stop all the servers and also set the set the em/initial_size_MB in 15 gb.
em/initial_size_MB = 15000
Then try to start the system.
Se how it goes..
Thanks
Rishi Abrol
Hi,
Please also check the the command at os level.
1904979 - Different output of comand 'ulimit -a' between OS levle and R/3 level
Thanks
Rishi Abrol
Hi
Here is result:
sapux1:r3uadm 32> memlimits -v off
SAP R/3 address space configuration test tool V3.2 (98/01/14)
=========================================================================
Verbose mode off
Check the maximum data size per process (malloc)
Check the available swap space (malloc in several processes)
Process 21475 all ... Size = 2048MB Total: 2048MB
Upper size limit 4096 reached. Finish checking
Total available swap space = 4096MB
Check the maximum size of mapped file (mmap anonymous,dev/zero)
Check protection operations on this area (protect)
Upper size limit 4096 reached. Finish checking
Maximum mapped file size: 4096MB
Maximum mprotect size: 4096MB
Check the maximum address space per process usable
both by process local memory and mapped file
Maximum address space ( mmap(4096 MB)+ malloc(1636MB) 😞 5732MB
+-------------------------------------------------------+
| Result |
+-------------------------------------------------------+
Maximum heap size per process........: 2048 MB
Maximum mapped file size (mmap)......: 4096 MB
measurement limited to 4096 MB
Maximum protectable size (mprotect)..: 4096 MB
measurement limited to 4096 MB
em/initial_size_MB > 4096 MB will not work
Maximum address space per process....: 5732 MB
Total available swap space...........: 4096 MB
measurement limited to 4096 MB
main memory size x 3 recommended , minimum 1 GB
sapux1:r3uadm 33>
Hello,
I have greate a massage with sap I am waiting for respons.
Her is result:
sapux1:r3uadm 35> bdf | grep r3u
/dev/sanvg01/lvol1 8388575232 8369096744 19326344 100% /r3u
sapux1:r3uadm 36>
I had stop alle installation on this server and try one more time. I am not sure the problem is memory.
Is it any thing I can du to see there is some problem in shadow instance. Becuse upgrade allwas stop in the same plads?
Thanks very much for helping me.
Reza
I would like to change the data in ulimit but I donot know how can I do that. there is nobody here to help me with this.
Thanks
I had tried this command again:
sapux1:r3uadm 36>
sapux1:r3uadm 36> memlimits -v off
SAP R/3 address space configuration test tool V3.2 (98/01/14)
=========================================================================
Verbose mode off
Check the maximum data size per process (malloc)
Check the available swap space (malloc in several processes)
Process 18185 all ... Size = 2048MB Total: 2048MB
Upper size limit 4096 reached. Finish checking
Total available swap space = 4096MB
Check the maximum size of mapped file (mmap anonymous,dev/zero)
Check protection operations on this area (protect)
Upper size limit 4096 reached. Finish checking
Maximum mapped file size: 4096MB
Maximum mprotect size: 4096MB
Check the maximum address space per process usable
both by process local memory and mapped file
Maximum address space ( mmap(4096 MB)+ malloc(1636MB) 😞 5732MB
+-------------------------------------------------------+
| Result |
+-------------------------------------------------------+
Maximum heap size per process........: 2048 MB
Maximum mapped file size (mmap)......: 4096 MB
measurement limited to 4096 MB
Maximum protectable size (mprotect)..: 4096 MB
measurement limited to 4096 MB
em/initial_size_MB > 4096 MB will not work
Maximum address space per process....: 5732 MB
Total available swap space...........: 4096 MB
measurement limited to 4096 MB
main memory size x 3 recommended , minimum 1 GB
sapux1:r3uadm 37>
Hi,
Please read the below note how to set ulimit.
Note 323816 - User limits on AIX
For all users associated with R/3 - the <sid>adm, sid, etc. - the
limits should be set to the following:
Soft CPU = -1
Soft CORE file size = 2097151 (this is the default)
Soft FILE size = -1
Soft DATA segment size = -1
Soft STACK size = -1
This can be done in one of two ways:
1. Using smit - enter the command "smitty". Select: Security & Users,
-> Users -> Change/Show Characteristics of a User.
2. Edit the /etc/security/limits directly using a normal editor
like vi. You can change the default values, but if values are also
defined for the users, you must remove them or change them also. For DB2 32bit Installations, please read related note 365314 which describes special settings for db2 environments.
If this fails we would go with higher disp+work and tp and r3trans tools.
Thanks
Rishi Abrol
Hi,
I have modified this file and i want to use this instance profile.
Please do sappfpar check when you use this profile.
Please also take the copy of the old profile.
#.******************************************************************************************************************************
#.* *
#.* Instance profile R3U_DVEBMGS07_SAPUX1 *
#.* *
#.* Version = 000007 *
#.* Generated by user = DDIC *
#.* Generated on = 12.09.2013 , 08:43:11 *
#.* *
#.******************************************************************************************************************************
#parameter created by: DDIC 11.09.2013 21:37:59
abap/buffersize = 400000
#parameter created by: DDIC 11.09.2013 21:14:15
em/initial_size_MB = 15000
em/max_size_MB = 22500
em/address_space_MB = 4096
ztta/roll_first = 1
# Instance profile for shadow system 731
rdisp/mshost = sapux1
rdisp/wp_no_dia = 5
rdisp/wp_no_vb = 1
rdisp/wp_no_vb2 = 0
# Entries for configuring a stand-alone enqueue. Integrated enqueue is no longer supported for kernel 802 and higher.
#rdisp/wp_no_enq = 1
rdisp/wp_no_btc = 4
rdisp/wp_no_spo = 1
rdisp/max_wprun_time = 0
abap/apg_settings = off
#old_value: 2000000 changed: DDIC 12.09.2013 08:42:55
zcsa/presentation_buffer_area = 4400000
zcsa/table_buffer_area = 80000000
zcsa/db_max_buftab = 10000
rtbb/buffer_length = 70000
rtbb/max_tables = 500
# *** CHANGE for the shadow instance ***
#ipc/shm_psize_10 = 40000000
ipc/shm_psize_10 = 128000000
# *** CHANGE for the shadow instance ***
#ipc/shm_psize_40 = 68000000
ipc/shm_psize_40 = 112000000
abap/heap_area_dia = 10000000000
abap/heap_area_total = 16106127360
abap/heap_area_nondia = 10000000000
ztta/roll_extension = 64000000000
ztta/roll_area = 20000000
rdisp/ROLL_MAXFS = 250000
rdisp/ROLL_SHM = 163840
rdisp/PG_MAXFS = 458752
rdisp/autoabaptime = 0
zcsa/system_language = E
dbs/ora/schema = SAPR3
# *** CHANGE for the shadow instance ***
rdisp/accept_remote_trace_level = 0
transport/during_upgrade = ON
rdisp/system_needs_spool = false
snc/enable = 0
rdisp/j2ee_start = 0
rdisp/start_icman = false
vmcj/enable = off
abap/package_check = off
rdisp/dynamic_wp_check = false
# Adaptions for shadow system 731
SAPSYSTEMNAME = R3U
SAPSYSTEM = 07
INSTANCE_NAME = DVEBMGS07
SAPGLOBALHOST = sapux1
SAPLOCALHOST = sapux1
SAPLOCALHOSTFULL = sapux1
DIR_INSTANCE = /r3d/mnt/R3U/start/SUM/abap$(DIR_SEP)R3U$(DIR_SEP)$(INSTANCE_NAME)
DIR_PROFILE = /r3d/mnt/R3U/start/SUM/abap$(DIR_SEP)R3U$(DIR_SEP)SYS$(DIR_SEP)profile
DIR_EXECUTABLE = /r3d/mnt/R3U/start/SUM/abap/exe
DIR_CT_RUN = /r3d/mnt/R3U/start/SUM/abap/exe
DIR_GLOBAL = /r3d/mnt/R3U/start/SUM/abap$(DIR_SEP)R3U$(DIR_SEP)SYS$(DIR_SEP)global
auth/shadow_upgrade = 1
Highlighted are the changes
Thanks
Rishi Abrol
Hi,
Can you please try this.
em/initial_size_MB = 10000
em/max_size_MB = 15000
em/address_space_MB = 4096
ztta/roll_first = 1
ztta/roll_area = 3000000
ztta/roll_extension = 2000000000
abap/heap_area_dia = 10000000000
abap/heap_area_nondia = 10000000000
abap/heap_area_total = 16106127360
rdisp/ROLL_MAXFS = 150000
rdisp/ROLL_SHM = 163840
rdisp/PG_MAXFS = 32768
rdisp/PG_SHM = 106608
Thanks
Rishi Abrol
Hi,
In which profile file the old one or the new one you gave me? The shadow will not start by old profile too.
I have tried to use new profile parameter on new one you gave me but still the same.
14.09.2013 06:49:48
StartWait
FAIL: process disp+work Dispatcher not running
SAPup> Process with PID 2200 terminated with status 2 at 20130914064948!
Thanks
Reza
Hi,
I did treid this:
sapux1:r3uadm 67> cleanipc 07 remove
Show/Cleanup SAP-IPC-Objects V2.3, 94/01/20
===========================================
Running SAP-Systems (Nr)...:
----------------------------------------------------------
---- Clear IPC-Objects of Sap-System 7 ------------------
----------------------------------------------------------
Number of IPC-Objects...........: 0
Number of removed IPC-Objects...: 0
Number of SAP_ES files found:.............: 0
Number of SAP_ES files removed:...........: 0
sapux1:r3uadm 68> SAPup startshd
Starting shadow system ...
Starting service ...
FATAL ERROR: Process /r3d/mnt/R3U/start/SUM/abap/exe/sapcontrol exited with 2, see '/r3d/mnt/R3U/start/SUM/abap/log/SAPup.ECO' for details
sapux1:r3uadm 69>
I had treid with old one and the new one profile you gave me . Shadow did not come up.
Thanks
Hi,
Please use this profile.
#.******************************************************************************************************************************
#.* *
#.* Instance profile R3U_DVEBMGS07_SAPUX1 *
#.* *
#.* Version = 000007 *
#.* Generated by user = DDIC *
#.* Generated on = 12.09.2013 , 08:43:11 *
#.* *
#.******************************************************************************************************************************
#parameter created by: DDIC 11.09.2013 21:37:59
abap/buffersize = 400000
#parameter created by: DDIC 11.09.2013 21:14:15
#em/initial_size_MB = 15000
#em/max_size_MB = 22500
#em/address_space_MB = 4096
#ztta/roll_first = 1
# Instance profile for shadow system 731
rdisp/mshost = sapux1
rdisp/wp_no_dia = 5
rdisp/wp_no_vb = 1
rdisp/wp_no_vb2 = 0
# Entries for configuring a stand-alone enqueue. Integrated enqueue is no longer supported for kernel 802 and higher.
#rdisp/wp_no_enq = 1
rdisp/wp_no_btc = 4
rdisp/wp_no_spo = 1
rdisp/max_wprun_time = 0
abap/apg_settings = off
#old_value: 2000000 changed: DDIC 12.09.2013 08:42:55
PHYS_MEMSIZE = 30%
zcsa/presentation_buffer_area = 4400000
zcsa/table_buffer_area = 80000000
zcsa/db_max_buftab = 10000
rtbb/buffer_length = 70000
rtbb/max_tables = 500
# *** CHANGE for the shadow instance ***
#ipc/shm_psize_10 = 40000000
ipc/shm_psize_10 = 128000000
# *** CHANGE for the shadow instance ***
#ipc/shm_psize_40 = 68000000
ipc/shm_psize_40 = 112000000
#abap/heap_area_dia = 10000000000
#abap/heap_area_total = 16106127360
#abap/heap_area_nondia = 10000000000
#ztta/roll_extension = 64000000000
#ztta/roll_area = 20000000
#rdisp/ROLL_MAXFS = 250000
#rdisp/ROLL_SHM = 163840
#rdisp/PG_MAXFS = 458752
rdisp/autoabaptime = 0
zcsa/system_language = E
dbs/ora/schema = SAPR3
# *** CHANGE for the shadow instance ***
rdisp/accept_remote_trace_level = 0
transport/during_upgrade = ON
rdisp/system_needs_spool = false
snc/enable = 0
rdisp/j2ee_start = 0
rdisp/start_icman = false
vmcj/enable = off
abap/package_check = off
rdisp/dynamic_wp_check = false
# Adaptions for shadow system 731
SAPSYSTEMNAME = R3U
SAPSYSTEM = 07
INSTANCE_NAME = DVEBMGS07
SAPGLOBALHOST = sapux1
SAPLOCALHOST = sapux1
SAPLOCALHOSTFULL = sapux1
DIR_INSTANCE = /r3d/mnt/R3U/start/SUM/abap$(DIR_SEP)R3U$(DIR_SEP)$(INSTANCE_NAME)
DIR_PROFILE = /r3d/mnt/R3U/start/SUM/abap$(DIR_SEP)R3U$(DIR_SEP)SYS$(DIR_SEP)profile
DIR_EXECUTABLE = /r3d/mnt/R3U/start/SUM/abap/exe
DIR_CT_RUN = /r3d/mnt/R3U/start/SUM/abap/exe
DIR_GLOBAL = /r3d/mnt/R3U/start/SUM/abap$(DIR_SEP)R3U$(DIR_SEP)SYS$(DIR_SEP)global
auth/shadow_upgrade = 1
How did you make the changes in the profile.
When you do below commad you should not see any ^M in end of the line.
more R3U_DVEBMGS07_SAPUX1
Always use vi command if you are changing the profile if you are changing at os level.
Thanks
Rishi Abrol
Hi,
Hope you have checked this note .
Note 1387739 - Out of memory errors during shadow system operation
You only need to restart the shadow instance after changing the profile.
did you get memory error before you change the parameters.
Thanks
Rishi Abrol
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I hope you have changed the parameters in shadow instance profile. If that is the case then you need not to restart the main instance. Restart of shadow instance will suffice.
Thanks
Sunny
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 5 | |
| 4 | |
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.