A termination occurs on a system due to insufficient available memory (address space). Common error messages that occur are 'STORAGE_PARAMETERS_WRONG_SET' or 'TSV_TNEW_PAGE_ALLOC_FAILED'.
The error can also occur after you set the '/3GB' option for NT Enterprise Edition or Windows 2000 Advanced Server this is due to Address space restriction on Windows NT / 2000.
If this error occurs on your system, first check to see whether you can use modified selection criteria to start the report/program that caused the termination.
A shorter time period, for example.
If you restrict the dataset, the existing address space may be sufficient to allow the program to finish without having to carry out further changes to the system.
The procedure described in this note will not necessarily provide a solution. It is quite possible that that available address space will still be insufficient even after the parameter change.
If this situation arises and you cannot restrict the selection criteria for this report/program any further, return the message to SAP so that the relevant department can analyze the program source code in greater detail.
An R/3 system started using the settings specified below is designed to execute memory-intensive programs only, not for work with users.
This means that you should test the settings below on the weekend or in the evening, for example, when no users have to work on the system.
1. Create a copy of the existing instance profile.
2. Add or change the following parameters in the 'new' instance profile:
abap/buffersize = 100000
rdisp/ROLL_SHM = 625
rdisp/PG_SHM = 0
3. Save the profile and start the R/3 system.
4. Start the required report/program.
If NT Enterprise Edition or Windows 2000 Advanced Server is installed on the system and the /3GB option is set (see Note 110172), these settings enable a process to allocate approximately 2.5GB of memory (EM + HEAP). If this parameter setting is used with NT Server or Windows 2000 Server, then approximately 1.5GB of address space is available. If you were able to execute the program with the above settings successfully, you should now consider the following questions: How often is the program executed? Daily, weekly..?
Depending on these factors, you must decide the following:
1. If NT Enterprise Edition or Windows 2000 Advanced Server is not yet installed, should I install it now?
2. Is it enough to start the system (central instance or application server) with the 'emergency' profile to execute the corresponding program?
3. Should I create another instance on one of the existing servers, which is then started using this profile and which is specifically configured to execute memory-intensive programs?
This instance must not be contained in logon groups and only serves to execute memory-intensive programs.