Checks When SAP R3 is Very
Slow
I'm using SAP R3 4.6C MS SQL 2000. I have 190 users. I notice when users are log in during peak hours 9am -6pm SAP R3 is very very slow. I lately increase my DIA and BGD process but still same issue.
Check if there are long running jobs in the background during the peak times (SM50) or if users are running long running
transactions/big lists.
System performance cannot improve if Dia and Bck workprocess increased. In fact those itself will bring down the performance of the system.
* Do not allocate more the 2 bck process in peak hours
* Check if your hardWARE is adequately sized for these many users.
* Check for any jobs consuming more than 60% of you resource.
( STO6-DETAIL ANALYSIS-TOP CPU)
* Check if there is any NETWORK COLLISION AT SERVER AND USER END.
* Rate of ARCHIEVE LOG SWITCH OVER .
* All USERS use SAME SERVER AT A TIME
* Even USER with ALL SUPER USER AUTHORISATIION can bring DOWN SYSTEM PERFORMANCE AT TIMES
* TRANSPORTS, providing AUTHORISATION and EXECUTING RESOURCE CONSUMING REPORTS TO BE AVOIDED at PRIME TIME.
What is the difference between unicode and nonunicode. For what purpose it is used.
Unicode is a character encoding system similiar to ASCII. You can see the definiton for Unicode by Unicode consortium below.
Unicode is the universal character encoding, maintained by the Unicode Consortium.
This encoding standard provides the basis for processing, storage and interchange of text data in any language in all modern software and information technology protocols". Unicode covers all the characters for all the writing systems of the world, modern and ancient. It also includes technical symbols, punctuations, and many other characters used in writing text.
The Unicode Standard is intended to support the needs of all types of users, whether in business or academia, using mainstream or minority scripts.
Most of the SAP implementations are done on Unicode system as it support all kind of languages, which is good for a company to expend their business. Another things is Unicode system requires 70% more storage area and processing speed to run the system perfectly.
There are systems like XI, which can work only on Unicode so it is always advisable to go for unicode then to non-unicode.
Regular Job to Purge
Transactions Logs
You should re-organize (note 16083) the following
data at regular intervals. When doing so, use the following job names as they
can be used to check if the jobs have already been active in your system:
Administration Data for Background Jobs - Program: RSBTCDEL
- Re-organized tables: BTC*
- Path for accessing files: /usr/sap/SID/SYS/global/<client>JOBLG
- Job scheduling: Daily (with variants)
- Recommended job name: SAP_REORG_JOBS
Spool Data and Administration Data
for Spool Jobs
- Program: RSPO0041
- Re-organized tables: TSP*
- Path for accessing files: /usr/sap/SID/<instance>/data
- Job scheduling: Daily (with variants)
- Recommended job name: SAP_REORG_SPOOL
Administration Data for Batch
Input
- Program: RSBDCREO
- Re-organized tables: BDC* and APQ*
- Path for accessing files: /usr/sap/SID/SYS/global
- Job scheduling: Daily (with variants)
- Recommended job name: SAP_REORG_BATCHINPUT
Runtime Statistics for Background
Jobs
- Program: RSBPSTDE
- Re-organized tables: BTCJSTAT*
- Path for accessing files: Not specified
- Job scheduling: Weekly (with variants)
- Recommended job name: SAP_REORG_JOBSTATISTIC
Question about Go Live
Check
What's Go-Live Check?
Who's responsible for Go-Live Check?
What should we prepare before Go-Live Check?
How many times for Go-Live Check?(I mean that Go-
Live Check seperate into how many steps/types such as 3 times for 1 Month before Go-Live, 2 Weeks before Go-Live
and 2 Weeks after Go-Live etc.) What's recommend schedule for each time?
How can we proceed Go-Live Check?
You have to open a message in component XX-SER-TCC to find out if your installation is scheduled for a Go-Live check which is conducted by SAP and it’s partners.
Go-Live Functional Upgrade Analysis – ideally 6 months before Golive – basically checks your hardware requirement , will it be able to accommodate the increase in the functionalities caused by the Go-Live, also some parameter recommendations to fine-tune your system.
Go-Live Functional Upgrade Verification – This is normally 2 months after the Go-live which is to see e’thing is fine after the upgrade.
Then you have normal Earlywatch session , each installation is entitled for 2 free earlywatch session in a year, in this performance tuning is done for your system, hardware,memory, I/0 bottlenecks are identified.
Reports of all these sessions carried out by SAP is then sent to you in form a MS-Word document and you can follow the guidelines mentioned and call up SAP or mail the person who has done the session for you for any clarifications.
Usually once a session is scheduled.
SAP will contact you to open the connections for them, so that they can prepare the system before the actual session takes place , in which they see , if SDCC version is good enough so that they can download the data from your system into their internal system on which they carry out the analysis, see if SAPOSCOL is running and enough history data is there in ST03n for them to carry out reasonable analysis. If e’thing is set a download is scheduled on your system using SDCC for a day prior to the actual session , and on the day of the session you open the connections for them again and provide them with userid and password normally it is earlywatch in 066 client.
Perform a Consistency Check
and Clean Temse Directory
I'm having problems with the STMS on the Development Box, from the look of things I need to clean the temse directory. What sought of routine can I perform as clean up routine regarding the same.
----------------------------------------------------
This is the procedure clear and tests the consistency of temse objects in case of 3.1I.
So first execute SPAD, where click on the consistency check button.
- this will display a list of objects. check to see the whether objects other than current day is displayed.
- then go SP12, here click on temse database button, where there is again consistency check.
- after the consistency checks are over, click on temsedatabase button, select reorganisation,
- here select the radio button that shows "delete all objects older than". Here enter the value and click on tick mark.
- this will display the number of objects. then delete it.
That's all the procedure.
