Parameter abap/unicode_check in 4.6c

Hi All.
I saw that 4.6C also has the parameter abap/unicode_check.
What is this parameter supposed to do in 4.6C which is not unicode enabled, actually?
Thanks in adv.

Hello Aishi,
check SAPnote # 1322715.According to this :
You can use the profile parameter abap/unicode_check to 'simulate' a Unicode system for the ABAP objects in a non-Unicode system. If you turn the profile parameter on, then all objects that do not have theunicode indicator set will not work in a non-Unicode system (normally these objects would still work fine in a non-Unicode system). You can set this parameter in the landscape (for releases
>= WAS 6.20 only) after the Unicode enabling is finished and automatically generated programs have been regenerated (see Unicode Conversion Guide). This ensures that you will detect missing Unicode
indicators before the actual Unicode conversion takes place. Please also have a look at the documentation of this parameter in transaction RZ11.
Regards
Niraj

Similar Messages

Help needed on memory parameter abap/buffersize

Hello Basis Gurus,
One of the programs in CRM system is failing with dump LOAD_PROGRAM_LOST.
I checked note "1798524 - Runtime error "LOAD_PROGRAM_LOST" when using Segmentation in CRM WEBUI" which seems to be relevant to our situation and found that the parameter 'abap/buffersize' is already on higher side i.e. > 3GB. Please let us know if we need to increase more and if yes then what is the dependency on any other memory parameters?
PS: I always have this question in general on memory parameters due to their sensitive nature (system may not start or adverse impact on other memory parameters). Functional/abap team asks to always increase it but how to check what is the impact and any possible dependency on other memory parameters...!!!
Thanks & Regards,
Kunal.

Hi Kunal,
LOAD_PROGRAM_LOST can have multiple possible causes; a too-small program buffer is just one possibility. At 3 GB, yours does seem like it's probably big enough, but there's no way to tell that from the outside without a lot more information.
Does the same program always fail with this dump, or just sometimes? What else is going on in the system when the dump occurs? Are there transports going into the system around that time? Is it really busy at that time? What happens if you run the program by itself during a quiet time, with nothing else going on? Is this a PRD system? Or perhaps a DEV system?
What sort of statistics do you have on the program buffer when you look at it via ST02? Note that since it's practically impossible to buffer every program, you will inevitably have some swaps in this buffer. That's normal operation. What you might do is look at the history of swaps and get a sense of the average number per day. If you consistently get more than 1000 swaps per day (not 1000 swaps total -- that's not important), as an average, then you might want to consider increasing the size of the buffer. If you only occasionally get spikes higher than this, but typically the number of new swaps each day is less, then you probably don't need to increase the buffer.
The other thing you need to look at is available extended memory. Since the program buffer is quite large, you must make sure there is plenty of available memory for extending it, should you decide to do so. You can get a sense of this from various stats, like the ratio of MaxUse to In Mem for Extended Memory on the same ST02 page, and from OS07N (or ST06). Do you have plenty of free physical memory? Are you getting a lot of paging out? Things like that. If your free physical memory looks good, then you have room to expand.
But again, this may not even be the cause of your dumps.
Bear in mind, if you increase the parameter and have problems restarting the system, you can always fall back by decreasing it again, so other than the planned downtime for the restart you don't lose much by giving it a try. If you increase it and the system starts fine, you will need to keep an eye on those memory use statistics over the following days to ensure all is well, but likely if the system starts ok, then you'll be ok. The days of too-large program buffers causing startup problems were mostly associated with 32-bit systems.
Cheers,
Matt

Set parameter abap/fieldexit = YES

Hi guys! I'm practicing with FIELDEXIT, and when I try to test my field exit, it says: Set parameter abap/fieldexit = YES, but I don't know how to do that. Could you guys please help me with that?
Thanks!
Gabriela
Edited by: gpsoria on Nov 13, 2009 9:49 AM

The default value for this parameter is No (after installation of an SAP system).
Via RZ11 you can check the actual parameter value.
When it needs to be changed to Yes it should be done by your basis administrators via transaction RZ10.
This is not a dynamic parameter, this means that the complete SAP system you be restarted in order to activate the new parameter value.
Success.
Wim

Parameter abap/fieldexit not activated

Hi,
I have change "abap/fieldexit" in RZ10 to "YES" and restarted SAP.
But on checking RSPARAM (via SA38), it shows "NO" in the "user-defined value".
Has anyone encountered this before and how was it solved?
Thanks

Hi Sergo,
Both modified & activate time is the same.
Thanks for the link but unfortunately, I don't think we can do the same. We are not able to activate field exits via RSMODPRF (via SA38).
The system kept prompting the "abap/fieldexit" needs to be set to "YES". The parameter is already set to "YES" and SAP restarted.
When I contacted SAP, they did a check and tell me that in RSPARAM, abap/fieldexit is not set. I am puzzled.
Even when I look at the profile at OS level, the parameter is INDEED "YES".
So any idea what could have happened?
Thanks

Couldn't log into SAP System (message 00264) after SAP_BASIS update

Hello,
we performed SAP_BASIS update to SAPKB70023 and get a problem with logon into a SAP system with message 00264 (Status &2 of the user interface &1 missing).
We have a 64-bit non-Unicode system on Solaris/SPARC/Oracle and Kernel level 333.
We tried to import MENUSYST program from note 1285869, but nothing happened at all. The parameter abap/unicode_check we set to "on" but this didn't help us.
So after selecting system record in SAP Logon now we get the initial logon screen with no "new password" button and error 00264 (Status 0020 of the user interface SAPMSYST missing.) and couldn't log into the system.
We have no idea why correct and existing statuses are not working.
Please suggest us what to do to fix this problem.
Thanks in advance!

Check this,
http://forums.sdn.sap.com/thread.jspa?threadID=835278
it may be useful.
Regards,
Ravi

What is the functionality of unicode in 4.7

hi gurus
can anyone
inform me
what is the functionality of unicode in 4.7
thank u
regards
kals.

Before release 6.10, SAP supported different codes for representing characters of different fonts, for example ASCII, EBCDIC as single-byte code pages or double-bytecode pages:
ASCII (American Standard Code for Information Interchange) encodes every character with one byte. This means that a maximum of 256 characters can be displayed (strictly speaking, standard ASCII only encodes one character using 7 bit and can therefore only represent 128 characters. The extension to 8 bit is introduced with ISO-8859). Examples of common code pages are ISO-8859-1 for Western European, or ISO-8859-5 for Cyrillic fonts.
EBCDIC (Extended Binary Coded Decimal Interchange) also encodes each character using one byte, and can therefore also represent 256 characters. For example,EBCDIC 0697/0500 is an IBM format that has been used on the AS400 platform for Western European fonts.
Double byte code pages require between 1 and 2 bytes per character. This enables the representation of 65,536 characters, of which only 10,000 to 15,000 characters are normally used. For example, the code page SJIS is used for Japanese and BIG5 for traditional Chinese fonts.
Using these character sets, all languages can be handled individually in one ABAP-based SAP system. Difficulties arise if texts from different incompatible character sets are mixed in one central system. The exchange of data between systems with incompatible character sets can also lead to problems.
The solution to this problem is the use of a character set that includes all characters at once. This is realized by Unicode Unicode (ISO/IEC 10646) . A variety of Unicode character representations is possible for the Unicode character set, for example UTF, in which a character can occupy between one and four bytes.
From release 6.10, the SAP NetWeaver Application Server supports both Unicode and non-Unicode systems. Non-Unicode systems are conventional ABAP systems, in which one character is usually represented by one byte. Unicode systems are ABAP systems that are based on a Unicode character set and which have a corresponding underlying operating system, including a database.
Before release 6.10, many ABAP programming methods were based on the fact that one character corresponds to one byte. Before a system is converted to Unicode, ABAP programs must therefore be modified at all points where an explicit or implicit assumption is made about the internal length of a character.
ABAP supports this conversion using new syntax rules and new language constructs, whereby emphasis was placed on retaining as much of the existing source code as possible. As a preparation for the conversion to Unicode - but also independently of whether a system will actually be converted to Unicode - the checkbox Unicode checks active can be selected in the program properties. The transaction UCCHECK supports the activation of this check for existing programs. If this property is set, the program is identified as a Unicode program. In a Unicode program, an additional stricter syntax check is performed than in non-Unicode programs. In some cases, statements must also be enhanced by using new additions. A syntactically correct Unicode program will normally run with the same semantics and the same results in Unicode and non-Unicode systems. (Exceptions to this rule are low-level programs that query and evaluate the number of bytes per character). Programs that are required to run in both systems should therefore also be tested on both platforms.
In a Unicode system, only Unicode programs can be executed. Before converting to a Unicode system, the profile parameter abap/unicode_check should be set to "ON" so that only the execution of Unicode programs is permitted. Non-Unicode programs can only be executed in non-Unicode systems. All language constructs that have been introduced for Unicode programs can, however, also be used in non-Unicode programs.
It has been established that existing programs that have been programmed with no errors mostly fulfill the new Unicode rules and therefore require very little modification. Conversely, most programs that require significant changes are due to an error-prone and therefore questionable programming style. Even if you are not planning a conversion to a Unicode system, Unicode programs are preferable because they are more easily maintained and less prone to errors. Just as outdated and dangerous language constructs are declared obsolete and are no longer permitted for use in ABAP Objects, the rules for Unicode programs also offer increased security when programming, for example when working with character fields and mixed structures. This applies particularly for the storage of external data (for example using the file interface), which has been completely reviewed for use in Unicode programs. When creating a new program, SAP therefore recommends that you always identify the program as a Unicode program, and older programs can be converted to Unicode in stages.

Reg: Unicode- Coverage Analyzer- (SCOV)

Hi
Can any one tell me how we can use the Coverage Analyzer (Transaction SCOV)as a tool for Unicode enabling. What are the sequence of steps that are to be followed.
Any Information, Documentation, Links, or examples that elucidates the same are highly solicited.
Thank you in anticipation.
Regards,
Sravan.

Hi,
I haven't used SCOV much.
In SCOV, 'global view' gives you a set of figures and graphical representation of system performance data. One of these graphs show the unicode-percentange of all programs that are unicode-enabled(one axis is time (month) and other axis represents percentage of programs that are unicode enabled). This is just to see how many programs have been unicode-enabled in the system. As long as you are not 100%, there is work to be done.
To force unicode-enabling (there may be programs which are unicode compliant but have not been set to unicode), you can check the profile parameter abap/unicode_check to enforce unicode syntax checks. (This has nothing to do with SCOV per se).
Now, how best to use SCOV when an object is being unicode-enabled and you need to make sure it is working fine?
After unicode-enabling the program you need to test it to make sure it works. But after running one or more tests successfully, how do you know whether all lines of code in the program have been covered in the tests?
SCOV can give you information whether all blocks of the code has been tested or not. If all blocks of a program/object have been tested after unicode-enabling (as reported in SCOV) then you can assume your testing to be complete. If on the other hand some blocks (let us say cetain subroutines in the program) have not been executed, you can see this in the detailed view in SCOV, and accordingly run other tests to ensure that this code is tested.
I am sorry I can not give you a step by step for this, if you post your mail-id, I can probably mail you a document which talks about this in a little (not much) detail.
cheers,

Can i know some thing about unicode errors

can i know some thing about unicode errors

Hi,
UCCCHECK is to check if all your programs are UNICODE compatiable.
Now UNICODE means
Unicode - Overview
Before release 6.10, SAP supported different codes for representing characters of different fonts, for example ASCII, EBCDIC as single-byte code pages or double-bytecode pages:
ASCII (American Standard Code for Information Interchange) encodes every character with one byte. This means that a maximum of 256 characters can be displayed (strictly speaking, standard ASCII only encodes one character using 7 bit and can therefore only represent 128 characters. The extension to 8 bit is introduced with ISO-8859). Examples of common code pages are ISO-8859-1 for Western European, or ISO-8859-5 for Cyrillic fonts.
EBCDIC (Extended Binary Coded Decimal Interchange) also encodes each character using one byte, and can therefore also represent 256 characters. For example,EBCDIC 0697/0500 is an IBM format that has been used on the AS400 platform for Western European fonts.
Double byte code pages require between 1 and 2 bytes per character. This enables the representation of 65,536 characters, of which only 10,000 to 15,000 characters are normally used. For example, the code page SJIS is used for Japanese and BIG5 for traditional Chinese fonts.
Using these character sets, all languages can be handled individually in one ABAP-based SAP system. Difficulties arise if texts from different incompatible character sets are mixed in one central system. The exchange of data between systems with incompatible character sets can also lead to problems.
The solution to this problem is the use of a character set that includes all characters at once. This is realized by Unicode Unicode (ISO/IEC 10646) . A variety of Unicode character representations is possible for the Unicode character set, for example UTF, in which a character can occupy between one and four bytes.
From release 6.10, the SAP NetWeaver Application Server supports both Unicode and non-Unicode systems. Non-Unicode systems are conventional ABAP systems, in which one character is usually represented by one byte. Unicode systems are ABAP systems that are based on a Unicode character set and which have a corresponding underlying operating system, including a database.
Before release 6.10, many ABAP programming methods were based on the fact that one character corresponds to one byte. Before a system is converted to Unicode, ABAP programs must therefore be modified at all points where an explicit or implicit assumption is made about the internal length of a character.
ABAP supports this conversion using new syntax rules and new language constructs, whereby emphasis was placed on retaining as much of the existing source code as possible. As a preparation for the conversion to Unicode - but also independently of whether a system will actually be converted to Unicode - the checkbox Unicode checks active can be selected in the program properties. The transaction UCCHECK supports the activation of this check for existing programs. If this property is set, the program is identified as a Unicode program. In a Unicode program, an additional stricter syntax check is performed than in non-Unicode programs. In some cases, statements must also be enhanced by using new additions. A syntactically correct Unicode program will normally run with the same semantics and the same results in Unicode and non-Unicode systems. (Exceptions to this rule are low-level programs that query and evaluate the number of bytes per character). Programs that are required to run in both systems should therefore also be tested on both platforms.
In a Unicode system, only Unicode programs can be executed. Before converting to a Unicode system, the profile parameter abap/unicode_check should be set to "ON" so that only the execution of Unicode programs is permitted. Non-Unicode programs can only be executed in non-Unicode systems. All language constructs that have been introduced for Unicode programs can, however, also be used in non-Unicode programs.
It has been established that existing programs that have been programmed with no errors mostly fulfill the new Unicode rules and therefore require very little modification. Conversely, most programs that require significant changes are due to an error-prone and therefore questionable programming style. Even if you are not planning a conversion to a Unicode system, Unicode programs are preferable because they are more easily maintained and less prone to errors. Just as outdated and dangerous language constructs are declared obsolete and are no longer permitted for use in ABAP Objects, the rules for Unicode programs also offer increased security when programming, for example when working with character fields and mixed structures. This applies particularly for the storage of external data (for example using the file interface), which has been completely reviewed for use in Unicode programs. When creating a new program, SAP therefore recommends that you always identify the program as a Unicode program, and older programs can be converted to Unicode in stages.
Regards,
Shakir

Abap/SIGCHILD_default profile parameter

Hi All,
I tried to add the parameter abap/SIGCHILD_default in instance profile and it's value as 'on' but I recieve a message - 'Unknown parameter abap/SIGCHILD_default, a check cannot be performed', 'Parameter value not permitted'.
I already referred the Note 790017 - sy-subrc of CLOSE DATASET if FILTER addition used and our SAP release is 701 EhP4.
However, still I continued and now parameter is added into the profile and profile is activated after SAP restart.
Any idea why it says that parameter not permitted? And I think still this parameter has no relavance in our system because we recieved that particular message ?
Thanks and Regards
Subba Rao

Hi Juan,
Thanks for quick reply.
I found another note similar to what you said, for e.g. Note 903245 - VMC Profile Parameters are not known in RZ10/RZ11, however parameters are different.
This note suggests, 'You can add VMC parameters with RZ10, also if RZ10 doesn't know the parameter name. Important is, that the kernel knows it. If the kernel doesn't know the parameter too, it will be ignored.'
Please confirm, is it the similar case here with 'abap/SIGCHILD_default' ? In earlier note I pasted it was written - 'In the SAP Kernel 7.00, the profile parameter abap/SIGCHILD_default is available since Patch Level 0'. So I think for our SAP Release 701 this parameter is already available for our kernel and it will work fine despite that 'unknown parameter' message in RZ10 ?
In RZ11, I see the same messgae - 'The parameter name is not known'.
Thanks & Regards
Subba Rao

Abap/buffersize Parameter?

Dear Friends,
why we use system profile parameter abap/buffersize ? it will increase ? what about system performance ( Process speed wise)?
Regards
keshav

Check this [SAP.Help |http://help.sap.com/saphelp_nw04/helpdata/en/bc/4a813b680c250fe10000000a114084/frameset.htm]
abap/buffersize - is responsible for Program buffer.
why we use system profile parameter abap/buffersize ?
To adjust program buffer....
it will increase ?
It will increase Program buffer within specified limit... As per document Typical Size/Number of Entries = 240,000u2013400,000 KB
what about system performance ( Process speed wise)?
Check ... Procedure if Buffer Is Full or Swap Rate Is too High on same page, as it says...
Increase the size of the program buffer if the hit rate becomes too low, or the swaps become too frequent. Development systems require a larger program buffer than normal systems. It is, however, almost impossible to avoid swapping in a development system.

ABAP dump when running an ALV report in a portal

Hi,
I have an ABAP report created in SAP R/3 4.7. Am using the ALV function module REUSE_ALV_GRID_DISPLAY to display the output. The programs runs correctly when run in R/3 using the SAP GUI.
When the report is run in the portal, I get a runtime error 'MESSAGE_TYPE_X'.
Please let me know if anybody has faced such issues.
I checked the OSS note 702732 which talks about increasing the threshold value of the start parameter. But this is not agreed by the BASIS team.
Thanks,
Best regards,
Ajith
The ST22 error log is as follows:
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
Short text of error message:
Data volume (84.550.400 bytes) is too large. (abap/alvgrid/size_nodod_mb
Technical information about the message:
Diagnosis
     You tried to send a data record to the front-end that contains
     84.550.400 bytes. However, the data volume is restricted to
     52.428.800 bytes.
System Response
     The running application program was terminated with a runtime
     error.
Procedure
     Restrict the data selection if possible or contact your system
     administrator.
Procedure for System Administration
     You can set the maximum size of these data volumes using the kernel
     parameter 'abap/alvgrid/size_nodod_mb' (in megabytes).
Message classe...... "S>"
Number.............. 890
Variable 1.......... "84.550.400"
Variable 2.......... "52.428.800"
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"MESSAGE_TYPE_X" C
"SAPLAWRT" or "LAWRTU22"
"ITS_CHECK_ALV_DATA_SIZE"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
   To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
   To obtain this, call the system log with Transaction SM21
   and select the "Print" function to print out the relevant
   part.
3. If the programs are your own programs or modified SAP programs,
   supply the source code.
   To do this, you can either use the "PRINT" command in the editor or
   print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
   or which actions and input led to the error.
Information on where terminated
The termination occurred in the ABAP program "SAPLAWRT" in
"ITS_CHECK_ALV_DATA_SIZE".
The main program was "Z_BW_RECON_INV_RPT ".
The termination occurred in line 25 of the source code of the (Include)
program "LAWRTU22"
of the source code of program "LAWRTU22" (when calling the editor 250).
Source code extract
000010   FUNCTION ITS_CHECK_ALV_DATA_SIZE.
000020   *"
000030   ""Lokale Schnittstelle:
000040   *" IMPORTING
000050   *"     REFERENCE(DATA_TABLE) TYPE TABLE
000060   *"
000070
000080     data n type i.
000090     data currsize type i.
000100     statics maxsize type i.
000110     data par_value(56).
000120     if maxsize is initial.
000130       sy-subrc = 0.
000140       CALL 'C_SAPGPARAM' ID 'NAME' FIELD 'abap/alvgrid/size_nodod_MB'
000150                           id 'VALUE' field par_value.
000160       if sy-subrc ne 0.
000170         maxsize = 52428800.       " Default 50 MB
000180       else.
000190         maxsize = 1048576 * par_value.
000200       endif.
000210     endif.
000220     describe table data_table lines n.
000230     currsize = sy-tfill * sy-tleng.
000240     if currsize gt maxsize.
     >       message x890(s>) with currsize maxsize.
000260     endif.
000270   ENDFUNCTION.

HI,
This is a Memory problem.
System is allocated with a Max Memory of 50 MB,(see the dump code, in the last it is hardcoded in the std code)
The data of your report is coming around 83 MB.
Restrict your selection criteria of the Object and run the same report and see. it will work.
Regards,
Anji

ABAP/4 processor: SYSTEM_NO_TASK_STORAGE

Hi Experts,
I have tried to load one of the master datasource(ocrm_srv_ibase_attr) from crm(qa system) to bw system. the job is getting cancelled in the source system with below error message.
ABAP/4 processor: SYSTEM_NO_TASK_STORAGE
Job cancelled
I have tried to extract data this datasource by using rsa3 tcode and its going into short dump with time_out message.
Could any one faced this type of issue...Any clue...
Thanks in advance.
Regs,
Vachan
Points will be assigned.

Hi,
Normally this error happens due to insufficient memory to process the requests.
Make more "memory" available for the program xecution. To do so you must iterativly adjust the parameter mentioned in the shortdump.
It might be necessary to put more RAM or increase swap if these parameter have to be increased significantly. See also note 20527.
You also need to
check parameter abap/heap_area_dia and abap/heap_area_nondia
I hope this helps you to overcome the problem.
Regards,
Venu

How to change abap/buffersize

Hallo!
I would like to increase Profile parameter "abap/buffersize".
I tried to do this with TCode RZ11(Maintain Profile Parameter Attributes), where I couldn't change any parameter.
I tried to log on as DDIC and SAP* but no success.
Pleas help me.
Thank you in advance.
Best regards,
Mihail

This is Basis Work. If you are not a basis person, better talk to them before you change anything.
Goto RZ10
Click on the drop down button for Profile.
If you do not have any profile in that. Import the profile.
RZ10 --> Utilities --> Import Profiles --> Of active server
Then do the drop down on Profile again. This time pick the one with <sysid>_DVEBMGS<system number>_<hostname> which is an instance profile.
Choose Change.
In the next screen if you see ur parameter change it, otherwise, you can add one. Do not forget to save the changes.

Sol. Man. dump STORAGE_PARAMETERS_WRONG_SET

Sol. Man. dump STORAGE_PARAMETERS_WRONG_SET
Hi experts,
We are facing the following problem in our SM system - SM 7.0 with EhP1 SPS 06. When certain transactions are started a short dump is generated with error text STORAGE_PARAMETERS_WRONG_SET. This is a part of the dump text:
What happened?
    The current program had to be terminated because of an error when installing the R/3 System.
    The program had already requested 1 382 466 704 bytes from the operating system with 'malloc' when the operating system reported after a further memory request that there was no more memory space available.
Error analysis
    When the program was running, it was established that more memory was needed than the operating system is able safely to provide. To avoid a system crash, you must prevent this situation from occurring.
    Last error logged in SAP kernel
    Component............ "EM"
    Place................ "SAP-Server ... on host ... (wp 3)"
    Version.............. 37
    Error code........... 7
    Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
    Description.......... " "
    System call.......... " "
    Module............... "emxx.c"
    Line................. 1897
    The error reported by the operating system is:
    Error number..... " "
    Error text....... " "
System environment
    SAP-Release 701
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "2x Intel 80686"
    Character length.... 8 Bits
    Pointer length....... 32 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database type..... "ADABAS D"
    Char.set.... "English_United State"
    SAP kernel....... 701
    created (date)... "May 16 2010 22:55:15"
    create on........ "NT 5.2 3790 Service Pack 2 x86 MS VC++ 14.00"
    Database version. "SQLDBC 7.6.0.035 CL 139084 "
    Patch level. 93
    Patch text.. " "
    Database............. "MaxDB 7.6, MaxDB 7.7, MaxDB 7.8"
    SAP database version. 701
    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.... 2609360
    EM...... 382578336
    Heap.... 1382466704
    Page.... 57344
    MM Used. 1708544512
    MM Free. 54755528
Edited by: Petar Yordanov on May 28, 2010 11:47 AM

These are some of the profile parameters of the system:
Parameter Name                     System Default Value System Default Value(Unsubst. Form) User-Defined Value
EM/TOTAL_SIZE_MB                   262144                262144
PHYS_MEMSIZE                       3071                  3071                                 2048
abap/NTfmode                       t                     t
abap/aab_log_field_size_limit      1024                  1024
abap/atrasizequota                 30000                 30000
abap/buffersize                    300000                300000
abap/cache_area                    1000000               1000000
abap/heap_area_dia                 2000000000            2000000000
abap/heap_area_nondia              2000000000            2000000000
abap/heap_area_total               2000000000            2000000000
abap/heaplimit                     40000000              40000000
abap/programs                      100                   100
abap/pxa                           shared                shared
abap/pxaclients                    32                    32
abap/restricted_dset_open          yes                   yes
abap/rsyntextln                    180000                180000
abap/rtm_high_water                1038336               1038336
abap/rtm_memory1_size              25000                 25000
abap/rtm_memory2_size              25000                 25000
abap/rtm_memory3_entries           1000                  1000
abap/set_textenv/ignore_errors     0                     0
abap/set_textenv/skip_all          0                     0
abap/shared_objects_size_MB        20                    20
abap/slin_intcheck                 off                   off
abap/string_sharing                on                    on
abap/super                         open                  open
abap/swap_reserve                  20000000              20000000
abap/table_sharing                 on                    on
abap/timeout                       512                   512
abap/unicode_check                 off                   off
abap/use_max_bcd                   0                     0
abap/use_mm                        1                     1
abap/use_paging                    0                     0
abap/warn2error_release            700                   700
em/address_space_MB                512                   512
em/as4/max_free_list               -1                    -1
em/blocksize_KB                    1024                  1024
em/execute_protection              TRUE                  TRUE
em/global_area_MB                  128                   128
em/initial_size_MB                 2048                  2048
em/max_dump_lines                  6291456               6291456
em/max_size_MB                     20000                 20000
ztta/cua_area                      250000                250000
ztta/diag_area                     250000                250000
ztta/dynpro_area                   800000                800000
ztta/hold_data_area                2000                  2000
ztta/max_memreq_MB                 250                   250
ztta/parameter_area                16000                 16000
ztta/roll_area                     2000000               2000000                              3000000
ztta/roll_extension                2000000000            2000000000
ztta/roll_extension_dia            2000000000            $(ztta/roll_extension)               2000000000
ztta/roll_extension_nondia         2000000000            $(ztta/roll_extension)               2000000000
ztta/roll_first                    1                     1
ztta/short_area                    1600000               1600000

Performance Issue for BI system

Hello,
We are facing performance issues for BI System. Its a preproductive system and its performance is degrading badly everyday. I was checking system came to know program buffer hit ratio is increaasing everyday due to high Swaps. So asked to change the parameter abap/buffersize which was 300Mb to 500Mb. But still no major improvement is found in the system.
There is 16GB Ram available and Server is HP-UX and with Netweaver2004s with Oracle 10.2.0.4.0 installed in it.
The Main problem is while running a report or creating a query is taking way too long time.
Kindly help me.

Hello SIva,
Thanks for your reply but i have checked ST02 and ST03 and also SM50 and its normal
we are having 9 dialog processes, 3 Background , 2 Update and 1 spool.
No one is using the system currently but in ST02 i can see the swaps are in red.
Buffer                 HitRatio   % Alloc. KB Freesp. KB   % Free Sp.   Dir. Size FreeDirEnt   % Free Dir    Swaps    DB Accs
Nametab (NTAB)                                                                                0
   Table definition     99,60     6.798                                                   20.000                                            29.532    153.221
   Field definition     99,82      31.562        784                 2,61           20.000      6.222          31,11          17.246     41.248
   Short NTAB           99,94     3.625      2.446                81,53          5.000        2.801          56,02             0            2.254
   Initial records      73,95        6.625        998                 16,63          5.000        690             13,80             40.069     49.528
                                                                                0
boldprogram                97,66     300.000     1.074                 0,38           75.000     67.177        89,57           219.665    725.703bold
CUA                    99,75         3.000        875                   36,29          1.500      1.401          93,40            55.277      2.497
Screen                 99,80         4.297      1.365                 33,35          2.000      1.811          90,55              119         3.214
Calendar              100,00       488            361                  75,52            200         42              21,00               0            158
OTR                   100,00         4.096      3.313                  100,00        2.000      2.000          100,00              0
                                                                                0
Tables                                                                                0
   Generic Key          99,17    29.297      1.450                  5,23           5.000        350             7,00             2.219      3.085.633
   Single record        99,43    10.000      1.907                  19,41           500         344            68,80              39          467.978
                                                                                0
Export/import          82,75     4.096         43                      1,30            2.000        662          33,10            137.208
Exp./ Imp. SHM         89,83     4.096        438                    13,22         2.000      1.482          74,10               0
SAP Memory      Curr.Use %    CurUse[KB]    MaxUse[KB]    In Mem[KB]    OnDisk[KB]    SAPCurCach      HitRatio %
Roll area               2,22                5.832               22.856             131.072     131.072                   IDs           96,61
Page area              1,08              2.832                24.144               65.536    196.608              Statement     79,00
Extended memory     22,90       958.464           1.929.216          4.186.112          0                                         0,00
Heap memory                                    0                  0                    1.473.767          0                                         0,00
Call Stati             HitRatio %     ABAP/4 Req      ABAP Fails     DBTotCalls         AvTime[ms]      DBRowsAff.
Select single     88,59               63.073.369        5.817.659      4.322.263             0                         57.255.710
Select               72,68               284.080.387          0               13.718.442             0                        32.199.124
Insert                 0,00                  151.955             5.458             166.159               0                           323.725
Update               0,00                    378.161           97.884           395.814               0                            486.880
Delete                 0,00                    389.398          332.619          415.562              0                             244.495
Edited by: Srikanth Sunkara on May 12, 2011 11:50 AM

Parameter abap/unicode_check in 4.6c

Similar Messages

Maybe you are looking for