on 03-24-2012 7:54 AM
Hi gurus,
We are in a SolMan upgrade (to SolMan 7.1) and I can't advance from this phase, I don't find the correct settings.
SAPUP:
Checks after phase MAIN_NEWBAS/XPRAS_UPG were negative!
Last error code set: Unresolved requests in buffer SSM
> Check logfiles 'XPRASUPG.ELG' and 'G:\usr\sap\SSM\SOLMANUP\abap\log\SAPup.ECO'
SAPUP.ECO:
EXECUTING G:\usr\sap\SSM\DVEBMGS02\exe\tp.exe pf=G:\usr\sap\SSM\SOLMANUP\abap\bin\XPRASUPG.TPP put SSM
Environment: NLS_LANG=AMERICAN_AMERICA.UTF8
Environment: ORACLE_HOME=G:\oracle\SSM\102
Environment: ORACLE_SID=SSM
Environment: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.PSC1;.PSC1
Environment: Path=G:\oracle\SSM\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\WINDOWS\system32\WindowsPowerShell\v1.0;G:\usr\sap\SSM\DVEBMGS02\exe;G:\usr\sap\SSM\DVEBMGS00\exe;G:\usr\sap\SSM\SYS\exe\uc\NTI386
Environment: auth_shadow_upgrade=0
Environment: dbs_ora_schema=SAPSR3
Environment: dbs_ora_tnsname=SSM
This is G:\usr\sap\SSM\DVEBMGS02\exe\tp.exe version 380.03.41 (release 720, unicode enabled)
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter DBCONFPATH is no longer used.
Looking for effective putsteps ... ... ready (looking for putsteps)
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
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
tp=>sapparam(1c): No Profile used.
tp=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
Process with ID 5208 terminated with status 12
XPRASUPG.SAV:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR-1507RINSTPL.SSM
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "08163600")
Long text:
Cause
Program "&V#&", which was started in the background, was terminated
abnormally.
System Response
The system created a job log for the terminated program.
What to do
Proceed as follows:
Log onto the system in which the program was executed. The system is
specified at the beginning of the transport log.
Then call transaction SM37 to display the job log.
Enter "&V#&" as job name and "DDIC" as user name.
Restrict the starting date to the starting date specified in the
transport log.
For the other selection criteria, select only jobs with the status
"cancelled". Then press <LS>Execute</>.
A list of the jobs satisfying the selection criteria is displayed.
You can display the log by pressing <LS>Job log</>.
If the list contains several jobs, you can select the job with the ID "
&V#&" with <LS>Display</> -> <LS>Job details</> or define further
details for the selection criteria in the initial screen of transaction
SM37.
If the ABAP processor reports cancellation, double-clicking on the
corresponding message in the job log branches to the display of the
corresponding short dump.
1AEPU320 See job log"RDDEXECL""08163600""SSM"
1 ETP111 exit code : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
SAPR-1507RINSTPL.SSM:
4 EPU201XBEGIN OF SECTION BEING ANALYZED IN PHASE XPRAS_UPG
1 ETP199X######################################
1 ETP162 EXECUTION OF REPORTS AFTER PUT
1 ETP101 transport order : "SAPK-1507RINSTPL"
1 ETP102 system : "SSM"
1 ETP108 tp path : "G:\usr\sap\SSM\DVEBMGS02\exe\tp.exe"
1 ETP109 version and release : "380.03.41" "720"
1 ETP198
2 EPU126XPost-import methods for change/transport request: "SAPK-1507RINSTPL"
4 EPU111 on the application server: "<servername>"
2 EPU122XPost-import method "SDOK_FILE_TRANSFER_AFTER_IMP" started for "SI4P" "L", date and time: "20120315050114"
4 E1R456XStart of processing for request "SAPK-1507RINSTPL", time "05:01:14"
3 EPU123 Post-import method "SDOK_FILE_TRANSFER_AFTER_IMP" completed for "SI4P" "L", date and time: "20120315050144"
2 EPU122XPost-import method "SDOK_FILE_TRANSFER_AFTER_IMP" started for "SAPH" "L", date and time: "20120315050145"
4 E1R456XStart of processing for request "SAPK-1507RINSTPL", time "05:01:45"
3 EPU123 Post-import method "SDOK_FILE_TRANSFER_AFTER_IMP" completed for "SAPH" "L", date and time: "20120315050313"
2 EPU122XPost-import method "SMCI_AFTER_IMPORT" started for "SMCI" "L", date and time: "20120315050313"
1AETR012XProgram terminated (job: "RDDEXECL", no.: "05010500")
1AEPU320 See job log"RDDEXECL""05010500""SSM"
1 ETP162 EXECUTION OF REPORTS AFTER PUT
1 ETP110 end date and time : "20120315050411"
1 ETP111 exit code : "12"
1 ETP199 ######################################
Dump:
TSV_TNEW_PAGE_ALLOC_FAILED
Short text
No more storage space available for extending an internal table.
Error analysis
The internal table "\CLASS=CL_SM_BFR_CONTENT_TRANSPORT\METHOD=WRITE_BF_PV_MI\DA
TA=LT_DBTAB_BFUNCTION_PV_MI" could not be further extended. To enable
error handling, the table had to be delete before this log was written.
As a result, the table is displayed further down or, if you branch to
the ABAP Debugger, with 0 rows.
At the time of the termination, the following data was determined for
the relevant internal table:
Memory location: "Session memory"
Row width: 240
Number of rows: 1079612
Allocated rows: 1079612
Newly requested rows: 64 (in 1 blocks)
Last error logged in SAP kernel
Component............ "EM"
Place................ "SAP-Server <servername>_SSM_02 on host <servername> (wp 8)"
Version.............. 37
Error code........... 7
Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
Description.......... " "
System call.......... " "
Module............... "emxx.c"
Line................. 2232
The error reported by the operating system is:
Error number..... " "
Error text....... " "
How to correct the error
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 1711968
Extended memory (EM)........... 192345216
Assigned memory (HEAP)......... 220705888
Short area..................... " "
Paging area.................... 40960
Maximum address space.......... " "
System environment
SAP Release..... 702
SAP Basis Level. 0004
Application server... "<servername>"
Network address...... "10.74.50.6"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x Intel 801586"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 8
Shortdump setting.... "full"
Database server... "<servername>"
Database type..... "ORACLE"
Database name..... "SSM"
Database user ID.. "SAPSR3"
Terminal.......... " "
Char.set.... "C"
SAP kernel....... 720
created (date)... "Sep 20 2011 01:15:51"
create on........ "NT 5.2 3790 S x86 MS VC++ 14.00"
Database version. "OCI_10201_SHARE, 10.2.0.2.0 "
Patch level. 105
Patch text.. " "
Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"
SAP database version. 720
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0, Windows NT 6.1"
Memory consumption
Roll.... 1711968
EM...... 192345216
Heap.... 220705888
Page.... 40960
MM Used. 396623168
MM Free. 17755536
Instance Profile:
ztta/roll_first = 1
ztta/roll_area = 2000000
ztta/roll_extension = 20000000000
abap/heap_area_total = 18000000000
abap/heap_area_dia = 9000000000
abap/heap_area_nondia = 9000000000
abap/shared_objects_size_MB = 200
ztta/roll_first = 2000000
rsdb/ntab/entrycount = 40000
rsdb/ntab/ftabsize = 50000
rsdb/ntab/irbdsize = 8000
abap/buffersize = 300000
zcsa/presentation_buffer_area = 4400000
sap/bufdir_entries = 5000
zcsa/table_buffer_area = 50000000
zcsa/db_max_buftab = 7000
rtbb/buffer_length = 20000
rtbb/max_tables = 900
rsdb/obj/buffersize = 4096
rsdb/obj/max_objects = 3000
rsdb/obj/large_object_size = 8192
rsdb/otr/buffersize_kb = 4096
rsdb/otr/max_objects = 3000
rsdb/esm/buffersize_kb = 4096
rsdb/esm/max_objects = 3000
rsdb/esm/large_object_size = 8192
rsdb/ntab/sntabsize = 5000
zcsa/calendar_area = 500000
zcsa/calendar_ids = 200
em/blocksize_KB = 1024
em/address_space_MB = 512
em/max_size_MB = 20000
PHYS_MEMSIZE = 3967
em/initial_size_MB = 3967
rdisp/PG_MAXFS = 32768
Also, We have implemented SAP Note 1509252
Could you help me, please; we tried with several post, but no option has worked still
Hy,
I had a similar problem. ST22 includes the following message:
Runtime Errors | TSV_TNEW_PAGE_ALLOC_FAILED |
IF INTERMEDIATE-BF_PV_MI IS NOT INITIAL.
ASSIGN INTERMEDIATE-BF_PV_MI TO <lt_bfunction_pv_mi>.
read table <lt_bfunction_pv_mi> index 1 into bf_entry.
if ( bf_entry-productversion is initial ).
return.
endif.
SELECT * FROM SMBF_BF_PV_MI INTO CORRESPONDING FIELDS OF TABLE lt_dbtab_bfunction_pv
WHERE PRODUCTVERSION = bf_entry-productversion.
LOOP AT <lt_bfunction_pv_mi> ASSIGNING <wa_itab_bfunction_pv_mi>.
READ TABLE lt_dbtab_bfunction_pv_mi ASSIGNING <wa_dbtab_bfunction_pv_mi>
FROM <wa_itab_bfunction_pv_mi>.
The solution:
0001687122 Out of memory beim Importieren von ST-710 SP4.
I had implemented this note and it solved my problem.
best regards
Istvan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jansi,
I think those messages are not relevant (Note: 32785) Anyway, I have checked that DEFAULT.PFL and Instance Profile have that parameter set
SAPSYSTEMNAME = SSM
Hi Vikram,
I view those Notes, I import transport request and update lib_dbsl_<patch level>.sar (patch 120) but the error continue...
Hi Roland,
I check Note 88416; I change the parameters to standard value and extend Page File to 12 GB (Phical RAM = 4GB), I can only set the parameter /PAE, if I active /3G parameter the server crash. "Maximize Throughput for Network Application" is active. The new memory parameters in instance profile:
ztta/roll_first = 1
ztta/roll_area = 2000000
ztta/roll_extension = 2000000000
abap/heap_area_total = 2000000000
abap/heap_area_dia = 2000000000
abap/heap_area_nondia = 2000000000
abap/shared_objects_size_MB = 200
ztta/roll_first = 2000000
em/address_space_MB = 512
em/max_size_MB = 20000
PHYS_MEMSIZE = 3967
em/initial_size_MB = 3967
rdisp/PG_MAXFS = 32768
Any idea, please?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nicholas,
The server has 3,87GB RAM
I change PHYS_MEMSIZE and EM/initial_size_MB to 11264, with higher values SAP don't start.
Job Log:
- Job started
- Step 001 started (program RDDEXECL, variant , user ID DDIC)
- All DB buffers of application server <servername> were synchronized
- Internal session terminated with a runtime error (see ST22)
- Job cancelled
The dump is the same.... :'(
Hi,
You can't change phys_memsize and EM/initial_size_MB to value higher than your physical server memory.
Total physical memory - 3.87GB is too low.. as your solman is running on DUAL-STACK system + Database. Is there any way to addin more memory (to 6Gb or 8GB) and increase phys_memsize and em/initial_size_mb to at least 4196.
U can refer to Note 1299009 - Central Note: Upgrade Systems on SAP NetWeaver 7.0 EHP 2
It should wokr after that.
Thanks,
Nicholas Chang
hi,
you are getting TP error as
Javier Sahagun wrote:
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
tp=>sapparam(1c): No Profile used.
tp=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
Process with ID 5208 terminated with status 12
SYSTEMNAME not used in profile
can you check this, are you missing or using wrong command during upgrade/
Please cheCK
Thanks
Jansi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Please check below notes:
1572314
1292069
regards
vikram
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
95 | |
11 | |
11 | |
10 | |
9 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.