This action might not be possible to undo. Are you sure you want to continue?
Central instance have message server and dialog, update, spool, enque, gateway, background work processes. Application server has only Dialog, update, spool, gateway and Background workprocess. Note: SAP server has only one message server and Enque server.
Q. What is difference between consolidated & delivery routs. Ans. In a 3 system landscape, transports from development and quality is called Consolidation Route (this can have target groups & CTC). Transports route from Quality to production is called delivery route.
Q. What are the prerequisites for applying a support pack? What is the Procedure for applying support packs? Download the Support Patches from market place. Login through 000 client with user DDIC. Go to Transaction SAPM. From the menu support packages - > load package -> from Front End.. Then Select display button in the screen and select the patch and gives import. Import the Package queue. Take care that no users are in online while u upload the support packages.
Q. Auto Start SAP on Windows Instance
Use transaction RZ10 to edit your startup profile. Add the following entry: * Autostart = 1 Then save the profile. Next time your server reboots, your SAP instance will come up automatically!
Q. What is the procedure for applying sap notes to sap system?
Goto Tcode SNOTE. GOTO Menu -> Download SAPNote. Give the Note No. After downloading check the status. If it shows that it can be implemented. Then Select that Note goto Menu SAPNote -> implement Note. Q. How to lock SAP Client? Is there any Tcode to lock the particular Client…? Execute Transaction code SE37. Enter the Functional Module SCCR_LOCK_CLIENT. Execute this and enter the client u need to lock. Q. Change the default Support Pack Path
It is because the path is defined in the parameter DIR_EPS_ROOT.
Q. SAP ECC6.0 Installation Steps
1. Once the Linux OS is over u configure the network card and change the Host name . 2. Install JDK and saplocales. 3. Then add the java home in profile file. 4. Modify the parameters in sysctl.conf. 5. Before install oracle u have to change the parameters in limits.conf. (Installation guide for oracle in linux is available from oracle site) 6. Install SAP by executing sapinst. 7. In the 3rd phase it will ask u to create user for oracle (user should be ora<ianstancename>). Suppose if u r going to install oracle in middle of sapinstallation only. Rest SAP will handle own its own. Q. STAT, STAD and ST03N tcode is showing error “RFC error, No performance data collected”.
Start SAP standard job SAP_COLLECTOR_FOR_PERFMONITOR(program RSCOLL00).
Q. What is the difference between client 000 & 001? Why we use client 000 for client copy, why don’t 001?
000 client is standard client and contain client independent setting. 000 client contain simple organizational structure of test company and include all parameter for application, standard setting
001 client is copy of 000 client. It is reserve for the activity for preparing the system for production system.
Q. Which are the default SAP background jobs run for Basis data?
SAP_REORG_JOBS SAP_REORG_SPOOL SAP_REORG_BATCHINPUT SAP_REORG_ABAPDUMPS SAP_COLLECTOR_FOR_JOBSTATISTIC SAP_COLLECTOR_FOR_PERFMONITOR RSPO1043
Q. What are Homogenous system copy and Heterogeneous system copy and how you will do that?
Homogenous- Same OS +Same DB Heterogeneous- Different OS+ Different DB or Same DB.
Q. What is SAPS?
BI: It is an OLAP (on line analytical processing). Q. What is difference between these? 1. SAP XI. SAP -XI: Exchange Infrastructure is used to establish a cross system connections between system by different vendors and versions 5. based on your installation choices during software installation. Web AS: Web Application Server is the platform for ABAP and J2EE stacks in Netweaver.Netweaver is a web based technology includes java. 2. gets filled frequently and we add datafile to that? PSAPBTABD/I. Q. which provides a plate form to collect the data and user extract the data from BI or BW (older version) to analyze it 3. It includes BI/XI/EP and different level of it’s configuration. PSCAPLUCD etc. services and information. PSAPSTABD/I. What is SAP NETWEAVER. SAP BIW. you can log in to EP using host name:port#/ <service name> and user name and password 4. Which table space. . SAP WAS and SAP BI.The SAP Application Performance Standard (SAPS) is a hardware-independent unit that describes the performance of a system configuration in the SAP environment. EP: Enterprise portal provides web based secure access to all the application. SAPNW .
it should deactivated it in normal operation. * ST03: → Select a server → Today’s Workload: What are the response times? In the case of poor response times. ST02: Check the buffering quality. Also refer to SAP Note 121625 in this context. Any signs of general problems in the System Log . Places to look: * SM50: → Process → Trace → Components – is there a Trace level set? Is it greater than 1? What is the utilization of the work processes? Click the white clock pictureicon. the corresponding parameter should be increased. If paging occurs in a buffer. To which extent are the hardware resources utilized? CallST06 at times with poor system performance.1. where is most of the time needed? Button ‘Top Time’: Are there a lot of different transactions with poor response times or are there only a few? Is a certain transaction always slow or only sometimes? * ST06: → Detail analysis menu → Hardware Info. What is the utilization of the disks? How high is the paging in the base pool? .SM21? 3. What is the CPU utilization? → Goto → Current Data → Snapshot → Top CPU processes and display the main CPU consumers. Is the total CPU for the last dialog process > 10 minutes? * ST04: Is the database monitor activated? If yes. What has changed since the performance is poor? * o System Parameter Changes (RZ10)? o Increase in the number of users? o Kernel patch? o Support Packages? o Linux and Oracle patches? o Hardware Changes? 2.
DB02 → Space Statistics button Press Enter on the Tables and Indexes popup History → All objects off/on Click the Months button 5. Click on the first number under the Rows – Chg/Month header and click the Sort button. What is considered “normal” response time? Performance Standards: Response time – 1 second (dialog). The sorted results shows the top tables when it comes to rows changes per month. 6. 1. 3. Look for tables that have experienced unusual monthly growth. ST03: Display the corresponding performance records. 5. 2. < 1 second (update) . 6. you should additionally note the following points: 1. ST05: If the database times are high. 4. Check whether modifications were made in the affected or related transactions. 3. These tables are your “database hogs”. 2. If only few transactions are affected by the performance problem. 4. SE30: Carry out a runtime analysis for the affected transactions. you should generate an SQL trace of the affected transactions to find out whether the database access is carried out in a useful way.4.
If your installaion was never able to . or an old one. you know that the instance itself must be viable. If this is a brand new SAP instance.CPU time Wait time Load time – approx 40% of average response time – < 1% of average response time – < 10% of average response time DB request time — approx 40% of average response time Database Standards: Direct reads – < 10 ms Sequential reads– < 40 ms Changes – < 25 ms High Value Indications: DB request time –. and the installation completed 100% successfully. there are some very specific places to look for information.Database or index problems Load time Wait time – Buffer problems – Not enough work processes Locked tasks Long running transactions Whether you are trying to start a brand new SAP instance.
the issue is probably due to lack of resources.complete due to the instance not being able to start up. dev_rfcx. Sort them with “ls – ltr” is see the list sorted in descending order for the ease of viewing. dev_ms. look for “error” in all files with the suffix “. · · · have you changed any instance paramters? did you do a kernel replacement for some reason? have there been SAP Support Packages applied that might necessitate a kernel replacement? · · · · have there been OS patches? is the database archiver stuck or hosed? has a crucial directory run out of space? has a semaphore or ipc segment gotten stuck from a previous run? · is your memory so fragmented that it can’t get enough primary space to start the instance? · has someone changes the directory privileges? To investigate an unsuccessful start up. go to the /usr/sap/<SID>/DVEBMGS00/work directory and do the same thing in this directory. and stderrx files. . The most useful information can be found in the dev_wx. Use the sapinst directory to search the installation logs and find your problem.log”. Sort them with “ls – ltr” is see the list sorted in descending order for the ease of viewing. look at the logs in the /home/<sid>adm directory. If nothing obvious is found. then something has probably changed that makes it not come up. If your SAP instance has been up and running fine for a good while. dev_disp. If you have a test searching tool.
If you searched for “Panic! Panic! Panic!” and got no hits. kernel. and the OS. open a problem with SAP.42 BR602W No valid SAP license found . you could try “warning message no object header”. and anything else you might think useful.10 (80) BR055I Start of database backup: bdmsqjbi. Normally a very specific query will get you the results you need. and if you had no luck.05. you could make your next search a little less specifc. Lets use this error message as an example: ”BR051I BRBACKUP 6. patch level for SAP support packages.anf 2004-02-27 00.”? And how often have you gone to SAP Marketplace and done a search yourself and found a hit? If we only had a had a nickle… Searching SAP Notes (formerly known as OSS notes) is a science as well as an art. If you didn’t find a note that matched the problem. you are applying support packages and get an import error with the following message “Panic! Panic! Panic! there’s no object header”. First you could search for the phrase. you should read the SAP Note even if it didn’t look as if it pertained 100%. And if that produced nothing tangible. If you get at least one hit. Since we speak English and we realize that the SAP product was designed and implemented in Germany. like “brbackup No valid SAP license found”. you could make it even less specific as in “brbackup SAP license error” or “SAP license error”. and attach the zipped file to it. and search accordingly. But sometimes things get lost in translation. you could search for all words. For example. Moral of the story? Realize that some things just don’t translate correctly from language to language.If all else fails. Why? Because it might contain information leading to other notes that did pertain. or give you new ideas for more search terms to help narrow the scope of my query. you should search the specific error message “BR602W No valid SAP license found”. we have to guess that the English word “Panic!” somehow was translated from the German word “Warning!” and that we can temporarily delay a panick attack until we can research the error. The Delicate Art of SAP Note Search How often have you seen a posted message saying “I have searched through SAP Notes and can find nothing related to this matter. . zip the contains of the /usr/sap/<SID>/DVEBMGS00/work directory.please contact SAP” First. Also provide them with the answers to the above questions as well as your current hardware and database platforms.
several things need to be checked: · Is the operating system on the user’s workstation patched to the level recommended by SAP? · · · · · · Is the user using a version of SAPGui that is too old for his workstation? Is the user using a version of SAPGui that is not certified for his operating system? Is the user’s workstation having resource problems? Is the user’s workstation connected to the LAN? Can a different user reproduce the same error on the same workstation? Are there any SAPGui patches that have not been applied? Most SAPGui problems can be solved by either a) deleting and reinstalling SAPGui on the workstation. read and become familiar with your SAP Notes. If a user seems to be experiencing SAPGui errors. There are certain notes that you pull over and over again due to some task that needs fresh.Last. current and precise information. or b) deleting and installing a newer version of SAPGui. add these three lines to the bottom of your \Windows\system32\drivers\etc\services file: . known problems with applying patches. etc. These are mostly lists of supported printer devices. and not least. Make sure that these lines were added to the services file on the user’s workstation: After you have successfully configured your SAPGui.
. on port 3200: Connect failed” error message right under the command you entered. If you have never tested connectivity to a SAP instance on the workstation having the connection problem. Let’s say your user us trying to connect to System ID (SID) DEV.11… Could not open connection to the host. first you need to make sure that the workstation can connect to the SAP server in some non-SAPGui way.10. you will have to add their equivalents to the services file as well. Also. Either the password or the user type for RFC_USER was changed. resource. If your window never goes completely blank and you set a “Connecting To 10.11 3200¬ If the screen rolls and goes totally blank then your dispatcher is reachable. or the SM59 RFC connection to was changed and is no longer working. and hardware requirements for running SAPGui.sapdp00 sapmsR3I # 3200/tcp 3600/tcp If you have SAP Instances using System Numbers other than 00. something in the RFC setup has changed. Open a DOSWindows and type this: telnet 10. For information regarding operating system. see SAP Note 26417 -SAP GUI Resources: Hardware and software. the dispatcher is not reachable. make sure the \Windows\system32\drivers\etc\hosts file on the workstation is correct.1.10.11. You can close the DOS session. Also. and IP address 10. System Number 00. the CUA Parent Client If CUA stops sending changes from DEV to QAS or PRD. be sure that your Insert Key is set so that you can type your password in properly – you can delete whatever is in the password field in order to enter your password.1. And.10.1. check if you are having connection problems due to firewall restrictions.
If they work (ie nothing seems to happen after you click the remote logon button) everything should now be fixed. 1. change the password in the sm59 screen to the same password you changed RFC_USER to in DEV and QAS. ii.SCCL----------------------------Step by Step Procedure to create a copy of a client locally in the same SAP server. assign client number & description as per request Logoff from current client. reset the RFC_USER password in DEV. If it still doesn’t go to QAS. And make sure that the user type is Communication and not dialog. and PRD. This does not mean that YOU are not authorized. Look for the user you tried to transport but could not. 5. 2. 3. Local Client Copy . You might see “You are not authorized to change users in group” or “No authorization for group users in role”. If you get a logon screen for QAS. Logon to SAP server Use Transaction Code SCC4 Go to change mode Create a new client. 4. First. Retry your user change. 6. maybe the QAS system is hosed and down. QAS.Use SCUL in DEV in your DEV CUA parent to list the errors that are occurring. Client Number User Id Password : Newly created one : SAP* : PASS . it means that the RFC_USER doing the ALE communication between the SAP systems is not authorized. Now go to sm59 and do remote logins using the QAS RFC connections. iii. Login to newly created client using the following credentials : i.
0 are the only proper tool to be use to keep multiple systems in sync by transporting development and customizing changes to another instance. The transport system and the transport management system of 4. It is always better to schedule the client copy job in the background for the night run when normal work is not taking place. 9. 8. Application data (transactional and master) should not be copied without copying configuration data. Golden rules for CLIENT Copies 1. Make sure that the client exists in T000 table and you can logon to that client. 10. Use Transaction Code SCCL for local client copy Give reference client for copy and profile as per the request Use SCC3 Transaction code to monitor progress of Client Copy.7. 5. Client copy requires a valid client as the destination client. . This program will give information about the missing definitions from the data dictionary in the target. 3. A remote test client copy also can be executed to know the differences between source client and target client. We recommend the users to read all the OSS notes regarding client copy that applies to their SAP release. you can use SE11 to compare and adjust the table structure in both the system before the client copy. When you copy a client from one system to another. 2. After executing this program and getting successful results you can ensure that the client copy will have no problems. 7. 9. 6. client-independent tables should only be copied if they are not yet modified in the target system. To avoid data inconsistencies all the users working in the source and target clients should logoff from the system. If you are not in release 2. 4.2 then do not use R3trans to copy a client. 8. Always check the database space before performing a client copy. Master data can not be copied without copying transactional data and transactional data can not be copied without copying master data. RSCLICHK program should be run in the target system remotely before doing a client export. In case some tables are different.
Go to transaction SM50. If this does not kill the process. If this does not kill the session. you can go to transaction SM04 and kill the user’s session. open a Task Manager session. You may now leave the SM50 transaction. If this does not kill the process. there is an .Kill the Work process-------------------------- Stopping Run-Away or “Bad” Work Processes 1. Place a √ in the □ to the left of the process number to be stopped by pressing Space. find the process which must be stopped. 3. and End the Process. click the Process → Cancel without core. 5. 4. On the top-most menu bar. Log on to any client in the appropriate SAP system. 2. you can log on to the server. On the Process Overview screen. Click the blue arrow circle picture-icon to refresh the Process Overview screen until the stopped process has cleared from the display.
executable in the RUN directory on the server called sapntkill. Click SAVE 8. Give IP address/Host name and system number for destination server in Technical Settings tab 9. 1. If none of the above work. On the new screen. give RFC destination name – Name by which the connection would be identified 5. Click SAVE 10. Creating RFC Connection This procedure should allow the Basis team to create a RFC connection in any SAP server. you have no choice but to “bounce” the SAP instance and/or possibly the serve. 2. 11. give user credentials in “Logon/Security” tab . If Trusted RFC connection is required. Logon to SAP server Use Transaction Code SM59 On SM59 screen click on “Create” button 4. 3. Use “Test Connection” to check RFC.exe. Give Description for the RFC Connection – Generally the purpose of the connection is mentioned here 7. Give Connection Type ( 3 for any SAP to SAP communication ) F4 Help will list down all possible types of connections 6. Run it providing the process ID number.
After the process starts. Before the client export starts. You can watch the export process in client copy log using transaction SCC3. For example DEVKX0001 The data export is performed automatically.DEV For client independent customizing data: /usr/sap/trans/data/RO00001. if you chose the client independent data then three transports are created in /usr/sap/trans/cofiles or there will be two transports: <sid>KO<no> for the client-independent data ( if selected). For example DEVKT0001 <sid>KX<no> for the SAPscript objects as Texts and forms. <sid>KT<no> for the client-specific data. In the client transport screen you can select a copy profile that matches your requirements and the target system in your CTS pipeline. The following data files will be created in/usr/sap/trans/data directory using the same example given above: For client dependent data: /usr/sap/trans/data/RT00001.DEV /usr/sap/trans/data/DX00001. The output of the export includes the name of the COMMFILE that has to be imported.DEV Tips: Make sure that all the cofiles and the datafiles exist in the data and cofile directories before starting the import phase. For example if the client export is done from development client 100 then the file will look like DEVKO0001. Then add all the command files to the buffer by using the TP command in /usr/sap/trans/bin directory as following: tp addtobuffer <cofile name> <target sid name> Using the above example cofile: tp addtobuffer devkt00001 qas (if qas is our target system) . After the client export procedure is completed. go to System Administration then choose Tools -> Administration -> Client admin->Client transport -> Client export or transaction SCC8.Transporting a Client: ---------- Procedure: To transport clients from one system to another.DEV For SAPscript data of a client: /usr/sap/trans/data/SX00011. a popup screen shows all the information about the command files that will be created after the client export is done. Then you can execute the client export in the background or online.
0 In 4. You can also use SCC2 to execute the same process as in transaction SCC7. choose Tools -> Administration. Using the transport procedure in 4. According to the above example devkx00001. To execute post-processing. The tp command is used to do the import as we have seen before and the RSCLIIMP program is executed for the post-processing activities and the consistency of data.>Client admin ->Client transport->client import or transaction SCC7. the following transport files are created. If there are inconsistencies. you need to repeat the import after checking the log. Then you can continue to execute the program and it will successfully complete the import of SAPscript objects to the target client.tp addtobuffer devko00001 qas tp addtobuffer devkx00001 qas Then logon as <sid>adm to the target system and then use then import the transports as following: tp import devkt00001 qas client100 u148 – For the client dependent data tp import devko00001 qas client100 u148 – For client independent data (In the above example QAS is the target system and 100 is the target client) After you import a client from another system. In this screen you can enter the transport request for the SAPscript object.DEV (using the above example) You can choose the import option from the “mode” option. RSCLIEXP program can be used to create the command files. Up to release 3. <sid>KO<no>: For the client-independent data (if the copy profile selected includes client independent data: . Please check the transport number and if every thing is according to the order then press enter and that will take care of the post processing activities. Transaction SCC7 will take you to the client import post-processing screen . you must perform post-processing. the SAPscript texts are imported and application reports are generated. activities in order to adapt the runtime environment to the current state of the data. In the second line you need to enter the path for the SAPscript data file as following: /usr/sap/trans/data/<data file for the SAPscript objects> /usr/sap/trans/SX00001. If you get any problem importing the SAPscript objects then use the RSTXR3TR program in the target client to import those. During this process.0 after the client is exported from the source system using transaction SCC8 as we have seen in the client export section. In that screen the transport from the last tp import is proposed.0.
Local Client Copy . we recommend doing table compare between the source client and the target client to check all the client dependent and independent tables for consistency. When all the above transports get released from the source system. you should perform the post-processing activities by using the following path: Tools ->Administration->Client admin->Client transport->Post-process import. 3. After the post processing is done. <sid>KX<no>: For the Texts and forms. Then you can start the import into the target system as shown in the following UNIX example: tp import <target-sys-id> client<target-client> from /usr/sap/trans/bin directory After the “tp import” process completes successfully. This process imports all the SAPscript objects and generates all the programs. assign client number & description as per request . The cofiles are also created in the /usr/sap/trans/cofiles directory. Then the command files need to be added to the buffer for the import using the format from the cofiles as following: * Logon to the target system as <sid>adm * cd /usr/sap/trans/bin . the data is exported to the data files of /usr/sap/trans/data directory automatically. 2.SCCL-------------------Step by Step Procedure to create a copy of a client locally in the same SAP server. After the client is imported successfully. 4.Change to the transport directory * tp addtobuffer <command file-name> <target-sys-id> . 1.<sid>KR<no>: For the client-specific data. Logon to SAP server Use Transaction Code SCC4 Go to change mode Create a new client. start transaction SCC2 and then execute the import into the target client.Adds to the buffer If you are transporting to a new client then the new client should be created in the target system.
7. 5. When you copy a client from one system to another. 3. 4. Always check the database space before performing a client copy. Client Number User Id Password : Newly created one : SAP* : PASS 7. Logoff from current client. It is always better to schedule the client copy job in the background for the night run when normal work is not taking place. Use Transaction Code SCCL for local client copy Give reference client for copy and profile as per the request Use SCC3 Transaction code to monitor progress of Client Copy. Login to newly created client using the following credentials : i.0 are the only proper tool to be use to keep multiple systems in sync by transporting development and customizing changes to another instance. Application data (transactional and master) should not be copied without copying configuration data. iii. ii.5. 8. To avoid data inconsistencies all the users working in the source and target clients should logoff from the system. Master data can not be copied without copying transactional data and transactional data can not be copied without copying master data. client-independent tables should only be copied if they are not yet modified in the target system. Make sure that the client exists in T000 table and you can logon to that client. . 8. We recommend the users to read all the OSS notes regarding client copy that applies to their SAP release. Client copy requires a valid client as the destination client. Golden rules for CLIENT Copies 1. 6. 6. 2. 9. The transport system and the transport management system of 4.
If you are not in release 2. assign client number & description as per request * Logoff from current client. A remote test client copy also can be executed to know the differences between source client and target client. After executing this program and getting successful results you can ensure that the client copy will have no problems.2 then do not use R3trans to copy a client.9. In case some tables are different. ii iii Client Number User Id Password : Newly created one : SAP* : PASS * Use Transaction Code SM59 to create a RFC Connection for client copy if does not exist already. you can use SE11 to compare and adjust the table structure in both the system before the client copy. * Login to newly created client in destination SAP server using the following credentials : i. * RFC Connection should have Target Server as Destination and the test results should say “Connection test OK” . Creating Remote Client Copy SCC9--------------- Step by Step Procedure to copy a Client to the Remote SAP Server. 10. RSCLICHK program should be run in the target system remotely before doing a client export. This program will give information about the missing definitions from the data dictionary in the target. * Logon to destination SAP server * Use Transaction Code SCC4 * Go to change mode * Create a new client.
When you copy a client from one system to another. Master data can not be copied without copying transactional data and transactional data can not be copied without copying master data. After executing this program and getting successful results you can ensure that the client copy will have no problems. 8. Client copy requires a valid client as the destination client. The transport system and the transport management system of 4. To avoid data inconsistencies all the users working in the source and target clients should logoff from the system. 7. Make sure that the client exists in T000 table and you can logon to that client. client-independent tables should only be copied if they are not yet modified in the target system. you can use SE11 to compare and adjust the table structure in both the system before the client copy. . * Give profile as per the request. A remote test client copy also can be executed to know the differences between source client and target client. RSCLICHK program should be run in the target system remotely before doing a client export. 6.0 are the only proper tool to be use to keep multiple systems in sync by transporting development and customizing changes to another instance. Always check the database space before performing a client copy. 4. Application data (transactional and master) should not be copied without copying configuration data.* Use SCC9 Transaction code to go to client copy screen. 9. This program will give information about the missing definitions from the data dictionary in the target. It is always better to schedule the client copy job in the background for the night run when normal work is not taking place. 3. 5. * Select RFC destination created for the purpose for the source client to client copy * Use Transaction code SCC3 for monitoring the progress of client copy ___________________________________________________________________ Golden rules for CLIENT Copies 1. In case some tables are different. We recommend the users to read all the OSS notes regarding client copy that applies to their SAP release. 2.
Run the following command on source system. i. Above command will generate a . Login as adm b. If you are not in release 2.2 then do not use R3trans to copy a client.10.. a.) and paste it in to any new .. Edit the reuse database command with the set database command . alter database backup controlfile to trace. connect internal d. f. h. svrmgrl c. Verify the backup is successfully done. Steps for SAP System Copy------------------------------- 1. j. g. e.sql or controlfile. Edit the file and replace the entire source SID to target SID.trc file in /oracle/P01/saptrance/usertrace directory. Take offline backup of both the server (source and target servers) 2.sql file. exit. 3. Copy the text from CREATE CONTROLFILE until the (.sql to target system. Copy the controlfile.
sql (file name of the control file contains the CREATE CONTROLFILE statement) n. After the run the above command it should give the “Statement Processed) . k. run the following command m. Change all the source to target . c. From this onwards all the command on the target system only. Once the database is restored login as orasid and run the i. Copy the above aft file name line from the source back. It will take some time to restore. run the brtools c. select Select backup type f.4. a. Select the offline backup which you want to restore. svrmgrl j. 6.log file. h. select Restore/Recovery d. @controlfile. g. 5.log to target. Only don’t change the backup volume name it must be target system . Shutdown the target server instance. startup nomount (if the database is already mounted shutdown it using the shutdown command) l. b. (/oracle//sapbackup) a. Login as Orasid b. connect internal. Copy the generated during the backup file from the source system to target system. select Full restore and recovery e.
jpg. Replace SAP Splash Logo: Change default SAP Logo on front screen. But convert it to jpg since that is the smallest available picture type. Look to the far right of the Data Browser: Table MIMETYPES Select Entries screen.gif. shutdown q.gif. bmp. After this you have to reconfigure the STMS. 9. On the SAP Web Repository: Object display screen.then you need to add it. If you want to change the Client number then use the local copy tool and remove the original client after successful import to new client. 4. and click the Find icon or press F8. 3. back out to SAP Web Repository: Object display screen. 10. Click Settings -> Maintain MIME types. Reconfigure all the printers.o. click “on” the radio button for Binary data for WebRFC applications. This picture can be in any valid picture format . . Identify a picture to replace the existing SAP logo. alter database open resetlogs p. Store the picture somewhere on your workstation. 1. Go to transaction SMW0. and if you don’t see your file type . bmp . 8. Once you at done. first make sure that the mime extension exists for your picture type. On the SAP Web Repository: Objection selection screen. jpg. 2. All the jobs also you have to reconfigure and reschedule. Start the database and SAP services using startup. click the Execute icon or press F8. 7. On the SAP Web Repository: Initial Screen.
SAR files is Stack 42.sap.SAR”. unCAR the files with SAPCAR command “sapcar -xvf “SAPEXE*. Now you can upload your picture.I use one called /usr/sap/trans/NewKernel. Download the two necessary archives . log on to the UNIX server as <sid>adm and copy them up to a directory on the UNIX server . Then press the Save icon. if your SAP instance is on Basis level 39 and the description of one of the SAPEXE. stop the SAP instance.com/patches.SAR and SAPEXEDB. For example. Be careful that your Basis level is high enough to use the patch level of the files you download. Go to transaction SM30. Fill in the name of your picture and a brief description and click the Import icon. 7.SAR from SAP MarketPlace. As <sid>adm. you need to download a SAPEXE. Once both files have been downloaded.5. You have replaced the SAP splash screen picture. Then provide the location of your picture and load it in. 6. 3. Click the Create icon or press F5. and log on as root and stop saposcol.SAR of a lower level.SAPEXE. On the Change View “Set Values for the Session Manager / Profile Generator” screen. There files can be found at http://service. Log on as ora<sid> and stop the TNS listener. Log off and back on to view your work! UNIX Kernel Patch: UNIX Kernel Replacement--------- 1. . click New Entries and add an entry called START_IMAGE and set the value to the name of your picture created in step #5. 2. Fill in the table name SSM_CUST and click Maintain.
3. Start saposcol. the TNS listeners.not the subtasks contained in the list and click Ctrl+F11. and the SAP instance.4. High-light the main transport in the list . . rename the directories /usr/sap/<SID>/SYS/exe/run to /usr/sap/<SID>/SYS/exe/bad_run and /usr/sap/<SID>/SYS/exe/backup_run to /usr/sap/<SID>/SYS/exe/run to restore your old kernel. sapdba & all br* files to ora<sid>. You have patched your UNIX SAP kernel. 8. Change the owner of saposcol to root. If prompted. Add an Object to a Transport----------------------------- To add an object to a existing unreleased transport. 6. 2. Copy all the files unCARed in step 2 to /usr/sap/<SID>/SYS/exe/run. stop everything. Go to transaction se10 and pull up a list containing the main transport. Log on to the client in which the main transport was created. I usually create a /usr/sap/<SID>/SYS/exe/backup_run and copy all the files in /usr/sap/<SID>/SYS/exe/run to it. you must do the following: 1. 7. and all the rest to <sid>adm. Make a backup of your run directory before patching. If you run into any problems starting your SAP instances. 5. overwrite all.
106.4.129 * P 10.1. Now you can release your transport and let it move to QAS! How to set-up and open a REMOTE SERVICE CONNECTION WITH SAP----------------------- 1.ZPROGRAM in our case.1. Set-up a remote network connection to SAP. Check “on” the check box on the appropriate line. Install SAPCRYPTOLIB on the same machine. 5. You will see a confirmation message in the status bar at the bottom of the screen.117. 6.1. turn “on” the “Selected Objects in the Selection by type and name” section. 3. 7.1. Click the Execute button or press F8.117. Turn “on” the radio button “Freely selected objects” that appears in the popup and press Enter or click the Copy button. 2. In the “Include objects in request” screen.130 * . On the “Include objects in request” screen.106. click the “Include Request” button or press F9. Check the saprouttab file : a) you should have only one in your system and b) it should look like this: P 10.* 194. 4.* 194. and enter the name of the object to be added to the transport . Install SAP router on a Windows machine.
19. and enter the saprouter’s NETBIOS name. install Service Connector from SAP’s site. Click on the edit icon. 6. Under System tab.sap.1. The Service Connection-System ID page opens.129 10. To set-up the maximum time for SAP connection. 15. . Go to http://service. Click on Systemdata – next to Logbook 14. scroll down to SAP-router. If you have a system that has the db server and the application server running on it. When you are done installing then. Under Appl. along with the local IP address. 16.com/system-data. Go to the Connecting to SAP tab. and under Service-port enter 3299. and the LOP. 18. On a workstation (Windows XP) that has the SAP GUI.106. Click on “Display all systems” 11. 8. Unless you have two saprouters. 17.P 194.After less than a minute. 9. Test you connection to SAP by DOS cd: ping sapserv1. Click on Maintain Connections 10.61 3200 5. run first SAPServiceConnector. and look for an edit icon to the right. do not enter anything under Additional SAP-Router field. 13. Double click on your system ID 12. Go to the Problem Solving tab.117. Under DB server tab click on the change icon and enter the NETBIOS name of the server. 7. then the IP address will be the same. you can check on the SAP website if the connection is open.1. click on Semi-Automatic Opening and enter the number of days for connecting to SAP. Install on the same machine LOP (Line Opener program).Server tab do the same thing.
exe). EventViewer can provide useful information and it may help you pinpoint where the problem resides. Windows Task Manager (TASKMGR. Dispatcher Monitor (DPMON. Example: \usr\sap\TST\DVEBMGS00\work. For a central SAP instance to start successfully.exe). Things you need to get familiar with: Developer Traces: – dev_disp Dispatcher developer trace – dev_ms Message Server developer trace – dev_wp0 Work process 0 developer trace The “services” file. yellow or red lights). users cannot log in to the system. This plain-text configuration file is located under %winnt %/system32/drivers/etc. which is located under \usr\sap\<SID>\sys\exe\run.SAP Startup Problems in Windows-----------------------Troubleshooting SAP Startup Problems in Windows----There’s probably nothing worse than not being able to start your SAP system … Especially the production system! Aside from the operating system and the database server you must pay close attention to certain places in SAP to find out what caused the problem and how to solve it. If one of them or both fail to start. both the message server and the dispatcher need to start. EventViewer (EVENTVWR. Here are the two places you will definitely need to check: EventViewer (Application and System logs) and the SAP Management Console (MMC). The SAP MMC gives you the ability to visually see the system status (green. The following scenarios will illustrate possible causes of why an SAP instance might not start and the reason of the message: “*** DISPATCHER EMERGENCY SHUTDOWN ***”.exe). Database logs. TROUBLESHOOTING SAP STARTUP PROBLEMS . view the work processes status and view the developer traces. which contains TCP and UDP services and their respective port numbers. which are stored in the “work” directory.
You can use the following OS command to help you resolve port conflicts: netstat -p TCP There are also utilities on the Internet that can help you list all the TCP and UDP ports a system is using. Errors found in “dev_disp”: ***LOG Q0I=> NiPBind: bind (10048: WSAEADDRINUSE: Address already in use) [ninti.Scenario 1: Dispatcher does not start due to a port conflict Symptoms No work processes (disp+work.c 1488] *** ERROR => NiIBind: service sapdp00 in use [nixxi. Due to the conflict. the dispatcher shuts down. If there is no firewall client at all.c 7326] *** DP_FATAL_ERROR => DpSapEnvInit: DpCommInit *** DISPATCHER EMERGENCY SHUTDOWN *** Problem Analysis Possible causes for error messages above: Address already in use Service sapdp00 in use The TCP port number assigned in the “services” file is being occupied by another application.exe) exist in Task Manager.c 3505] *** ERROR => DpCommInit: NiDgBind [dpxxdisp. disable it and attempt to start the SAP instance again. or if disabling it did not resolve the problem. edit the “services” file and check what port the appropriate “sapdp” is using. If the instance number is 00. Solution If your server has a firewall client. look for sapdp00. Dispatcher shows status “stopped” in the SAP MMC. If the instance starts successfully you can enable the client firewall back again. . If the instance number is 01 look for sapdp01 and so on.c 3936] *** ERROR => NiIDgBind: NiBind (rc=-4) [nixxi.
pfl system profile (under \usr\sap\<SID>\sys\profile).c 8437] *** ERROR => W0 (pid 2460) died [dpxxdisp. This parameter needs to be set in the DEFAULT. th_errno 13. If the system is based on Basis <= 4. But. No work processes. SAP MMC -> WP Table shows all processes as “ended”.7 the database owner should be “dbo”.x the database . db_connect (DB-Connect 000256) [thxxhead.c 11651] my types changed after wp death/restart 0xbf –> 0×80 *** DP_FATAL_ERROR => DpEnvCheck: no more work processes *** DISPATCHER EMERGENCY SHUTDOWN *** DpModState: change server state from STARTING to SHUTDOWN Problem Analysis A connection to the database could not be established because either the SQL login specified in parameter “dbs/mss/schema” is set incorrectly or the SQL login was deleted from the database server.c 11651] *** ERROR => W1 (pid 2468) died [dpxxdisp.6 or if the system was upgraded from 4.x to 4.Scenario 2: Dispatcher dies due to a database connection problem Symptoms No database connections.. if the system was installed from scratch and it’s based on the Web AS 6..c 11651] *** ERROR => W2 (pid 2476) died [dpxxdisp. Solution Set the entry to the appropriate database owner. action 3. In the messages above.c 11651] *** ERROR => W12 (pid 2592) died [dpxxdisp. we see that the SQL login ‘tst’ is expected but it does not exist at the database level. Errors found in “dev_disp”: C setuser ‘tst’ failed — connect terminated C failed to establish conn.c 11651] . 0 M ***LOG R19=> tskh_init.c 1102] M in_ThErrHandle: 1 M *** ERROR => tskh_init: db_connect (step 1. level 1) [thxxhead. *** ERROR => W11 (pid 2552) died [dpxxdisp.
exe) shows status “stopped”. If it doesn’t. Instead. The dev_ms file reports these errors: [Thr 2548] *** ERROR => MsCommInit: NiBufListen(sapmsTST) (rc=NIESERV_UNKNOWN) [msxxserv. Solution Re-create the “saploc” and “sapmnt” network shares. create it and give it database ownership to the <SID>.owner should match the SID name in lower case.c 8163] [Thr 2548] *** ERROR => MsSInit: MsSCommInit [msxxserv. No new developer traces written to disk (under the “work” directory.c 5023] .pfl profile check at the database level if the SQL login exists. they get this error: No logon possible (no hw ID received by mssg server). If the parameter is set correctly in the DEFAULT. Scenario 3: SAP does not start at all: no message server and no dispatcher Symptoms The message server and the dispatcher do not start at all in the SAP MMC. the message server (msg_server. In the SAP MMC.) Problem Analysis The network shares “saploc” and “sapmnt” do not exist. Scenario 4: Users get ‘No logon possible’ messages when they attempt to log in Symptoms Work processes start but no logins are possible. Both need to be created on the \usr\sap directory.c 1561] [Thr 2548] *** ERROR => main: MsSInit [msxxserv. That explains the “network path not found” message when attempting to view the developer traces within the SAP MMC. Example: if the SID is TST then the database owner should be “tst”. Users get the login screen but the system does not log them in. The following error when trying to view the developer traces within the SAP MMC: The network path was not found.
.c 5078] Problem Analysis Work processes were able to start but the message server was not. service_unknown (sapdp00) [nixxi. Example: sapdp00 3200/tcp Solution Add the necessary entry in the “services” file. The reason is because the “services” file is missing the SAP System Message Port entry. Then. Example: SAPmsTST 3600/tcp Solution Edit the “services” file and add the entry. 3600) for the message server. MSStop (Msg Server 2900) [msxxserv. re-start the instance. re-start the instance.g.c 7326] *** DP_FATAL_ERROR => DpSapEnvInit: DpCommInit *** DISPATCHER EMERGENCY SHUTDOWN *** Problem Analysis The keyword in the messages above is “service unknown” followed by the entry name “sapdp00″. The “dev_disp” file shows these errors: ***LOG Q0A=> NiIServToNo. Make sure you specify the appropriate TCP port (e. Scenario 5: The message server starts but the dispatcher doesn’t Symptoms The dispatcher shows status “stopped” in the SAP MMC. The dispatcher entry “sapdp00″ is missing in the “services” file. Scenario 6: Work processes die soon after they start Symptoms All work processes die right after the instance is started.c 2580] *** ERROR => DpCommInit: NiDgBind [dpxxdisp. Example: sapdp00 3200/tcp Then.[Thr 2548] ***LOG Q02=> MsSHalt.
An ABAP dump saying “PXA_NO_SHARED_MEMORY” is generated as soon as a user logs in. When you have your entry. Also. Solution Edit the instance system profile at the OS level under \usr\sap\<SID>\sys\profile and lower the value assigned to “abap/buffersize”. the system should start once the adequate memory allocation has been set to the the “abap/buffersize” parameter. The SAP MMC Syslog shows the following error multiple times: “SAP-Basis System: Shared Memory for PXA buffer not available”. Display the entry (or entries) you want to modify. Most likely the “abap/buffersize” instance profile parameter is set to high. enter your table Name (ex: USR02).The SAP MMC shows work processes with status “ended”. Change Data In Table Without Authorization Using Transaction se16-------------------------------------- There is a way to change entries of a table with SE16 even if you don’t have the authorization: Go in SE16. Cross the line you want to modify and press F7 (display function). Only one work process shows status “wait”. . Here. If not. Problem Analysis The instance profile contains misconfigured memory-related parameters. restart the instance. you are in the code… Press F7 again to skip some code… Now you should see the code: Refresh Exclude_Tab. If Code = ‘SHOW’. it’s important to find out if any other memory parameter were changed. Set Titlebar ‘TAB’ With Name ‘anzeigen’(100). Then. write ‘/h’ to go in debug mode.
click the Save picture-icon. Go to transaction SM19. You may now leave the SM19 transaction. click Change FLD Contents. On the Create new profile popup. Once you have entered all your trace information. From the top-most menu bar on the Security Audit: Administer Audit Profile screen. 6. 4. it is not yet active. Log on to any client in the appropriate SAP system. Please note that while the user trace profile has been saved.Elseif Code = ‘EDIT’. 3. . click the radio button to the left of the level of auditing you need. and don’t forget to save! Trace a User’s Activity-----------------------Creating a User Audit Profile 1. To activate the user trace. On the Filter 1 tab of the Security Audit: Administer Audit Profile screen. 5. You will receive an Audit profile saved in the status bar at the bottom of the screen. In the Selection criteria section. … Change the value from SHOW to EDIT. click Profile -> Create. In the Audit classes section. 7. click “on” all the auditing functions you need for this profile. 2. see the next section Activating a User Audit Profile. In the Events section. and press F8… Here we are… You can change the value to what you want. type in a new Profile name and click the green √ picture-icon. click the □ to the left of Filter active to place a √ in the box. click Change FLD Contents. select the Clients and User names to be traced. and press F8… or to delete an entry Change the value from SHOW to DELE.
Log on to any client in the appropriate SAP system. 2. 4. be sure to include that user’s ID. You may now leave the SM20 transaction. 5. and Events to select sections of the Security Audit Log: Local Analysis screen. 2. Log on to any client in the appropriate SAP system. This list can be printed using the usual methods. 4. You may now leave the SM19 transaction. The audit will not begin until after the SAP instance has been recycled. 3. Click the lit match picture-icon to activate it. The resulting list is displayed. You will receive an Audit profile activated for next system start in the status bar at the bottom of the screen. provide your information to filter the audit information. If you need to trace the activities of a specific user. On the Security Audit: Administer Audit Profile screen. In the Selection.Activating a User Audit Profile 1. Working with saprouter-----------------------Working with saprouter Starting saprouter (OSS Link) . Viewing the Audit Analysis Report 1. Go to transaction SM19. select the audit profile to be activated from the Profile dropdown. 3. Go to transaction SM20. Click the Re-read audit log button. Audit classes.
Click Start → Administrative Tools → Services to open a Services window. Look at the SAPROUTER service. Right-click on the SAPROUTER service and click Start. Log on to the appropriate server as <sid>adm. your saprouter configuration has been incorrectly changed (also very rare). If is not started.1. right-click & Stop the service and then right-click & Start the service. 1. 4. 4. or your saprouter is not running (happens all the time). 2. there can only be three reasons for a “broken” SAPNet connection to SAP: the SAP VPN is down (which rarely happens). Verifying the Status of saprouter If you have previously successfully established SAPNet (OSS) communications with SAP via saprouter in the past. You may now log off the server. 3. 1. 2. This should “bounce” your saprouter instance. Click Start → Administrative Tools → Services to open a Services window. 2. . You may now log off the server. If it is started. right-click to start the service. Log on to the appropriate server as <sid>adm. You may now log off the server. 3. Log on to the appropriate server as <sid>adm. Click Start → Administrative Tools → Services to open a Services window. 3. 4. Right-click on the SAPROUTER service and click Stop.
On the Service Connections – Overview screen. 2. click the Service Connections button. In the Enter Data for the system’s semi-automatic opening popup. 3. You can do the same thing using SAP. Please LOPInstalltion. hours. and that a Security Audit Trace has been activated for the SAPAG ID.exe on your saprouter server before trying to add and open any Service Connections. Creating a Local Frontend Printer or Desktop Printer-----------------------Local or frontend printing is sometimes confusing in concept but actually very easy to understand. scroll down the page and find the SAP instance you want to open. set the days. be sure that the SAPAG client has been added to the appropriate SAP system and Client.com/serviceconnection. the saprouter must run the LOP – Line Opener Program – to initiate the mode of SAP connection. Go to transaction SPAD. Click the Continue button.Opening a Service Connection for SAP Support------------------Before opening a service connection for SAP. As a rule. Click on the red X in that instance’s line.sap. Log on to the SAP Marketplace using an OSS ID with Administration rights – http://service. 2. and minutes you want the service connection to stay open. 1. Before a Service Connection to a SAP server via your saprouter can be created. 4. etc without thinking about it. local printer is simply another way of saying that the user is going to print to the default printer designated on his/her workstation. Log on to any client in the appropriate SAP system. . On the Service Connections screen. 1. You probably do this all the time with Windows to printerspreadsheets. Word documents.
3. Use the following DeviceAttributes fields: Device type = SWIN Device Class = standard printer And the following Access Method fields: Host spool access method = F: Printing on frontend computer Host printer = __DEFAULT. 5. Using this printer will cause print to go to SAPLPD which will use the default printer of the current workstation. You may now leave the SPAD transaction. click the Change button and then the Create button. 6. SAP R/3 dispatcher and work processes--------------------------Types of work processes: . On the Spool Administration: Create Output Device screen. That is _ _ D E F A U L T Save the printer. On the Spool Administration: List of Output Devices screen.I normally use a short name of “DESK” for “Desktop Printing” but alot of people use a Short name “SWIN” or “LOCL” as well. fill in the Output Name and Short name . click the Output Devices button. On the Spool Administration: Initial Screen screen. 4.
anyone can log into the system using the client 066. If it is true. and password PASS. Used for interactive online processing. * Gateway : Used for transport of bigger amount of data between application servers as well as external (non SAP) systems that communicate with SAP Some Usefull Tips------------------- * Logging on without being authorized Client 066 usually exists in a SAP system because of EarlyWatch services. * Enqueue : Single “Central Lock Management Service” that controls the locking mechanism between the different application servers and the database. * Batch : For Background jobs. Often this client does not have master users. * Dispatcher : Redirect the request from GUI client to free process.* Message : Coordinates the communication between different instances of a single SAP R/3 system. * Locking the whole system Using the command tp locksys «SysID» only the user SAP* will be allowed to login. Used for Logon purpose and load balancing. * Update : Responsible for consistency in asynchronous data changes. user SAP*. * Dialog : Interpreting the ABAP code and execute the business logic. . Enjoy yourself. The commandtp unlocksys «SysID» cancels the lock.
impst. and expst. * SQL code help Run the command oerr ora «error number» under user ora«SysID». a job previously defined within R/3 will be released. * Direct input logs The transaction BMV0 (direct input logs) shows all direct input logs. . Thus.* Connection between SAP R/3 and operating system : Release SAP Job from OS The command sapevt can be used to trigger an event from the operation system. * Oracle import and export explanations Run the command imp help=yes under user ora«SysID». This format can also be used with exp.
* Long messages on footer Click on the message and hold the mouse button. * Setting up module FI/CO without using IMG Almost all parameters can be set using the transactions ORFA (Asset Accounting).tif on PC files) into .* Table analyses between two systems The contents of a table between two systems can be checked through the transaction OY19. and ORKS (Cost Center Accounting). After moving the mouse to the left side. * Graphics on SAPscript The program RSTXLDMC can be used to upload graphics (file extension . ORFB (Financial Accounting).
The current date is automaticly set. It reports the last objects verified and also the respective values. * Filling up an empty date field quickly Strike the key F4 (or click on matchcode symbol) and press ESCAPE. * Displaying check object when not authorized Soon after the lock try to access the transaction SU53.individual standard text. * Correction and transport system . * Deleting cost elements and cost centers Since they have no postings you can use the transaction KA04 for deleting cost elements and KS04 for deleting cost centers.
You have to choose the desired patch and click on delete entry. * Helpful reports RSCLTCOP Copy tables across clients RSAVGL00 Table adjustment across clients RSINCL00 Extended program list RSBDCSUB Release batch-input sessions automaticly RSTXSCRP Transport SAPscript files across systems RSORAREL Get the Oracle Release RGUGBR00 Substitution/Validation utility RSPARAM Display all instance parameters RSUSR003 Check the passwords of users SAP* and DDIC in all clients RSUSR006 List users last login * Reapplying hot packages If you accidently applied hot packages out of sequence for instance.The transaction SE10 provides the easiest way to manage any request/transport and corrections. . Use the transaction SM31 to modify table PAT03.
* Scheduling of system maintenance jobs RSBTCDEL Clean the old background job records RSDBCREO Clean batch input session log RSPO0041 Removing old spooling objects RSSNAPDL Clean the old ABAP error dumps UNIX commands used for SAP administration:----------------------------1. -name filename -print for checking the file in the present directory 5. dpmon pf= <Instance profile path>. bdf for checking all file system usages. 11. find . for individual file usages 7.. jcmon pf=<instance profile path> 6. Cdpro for checking the profiles path SAPMNT/<SID>/profile 3. stopsap/startsap for stopping/starting SAP+ DB. h for listing previous used commands. Ps -ef is to check the how many running process and Kill any running process . bdf. df -k. 9. Cdexe for checking the kernel folder 4. du -a | sort -k 1n. df -k . rm < file> for removing file. gzip <file> for zipping the file. stopsap r3/startsap r3 for stopping/starting R3 2. 10. ls -lrt for listing of files according to the date modified 8.1 for sorting the files in a recursive manner.
Make command to effect any coading content 17. make clean to clean the effect of make command 18.sap. pwd check the current directory Important SAP Marketplace Links----------------- Inbox http://service.sap.com/licensekey Request New Permanent .com/instguides http://service.12. gunzip to unzip file 13.sap. tar -xvzf file name to run the zip folder of file content 14. mv mo from one path to another 15. Rf remove forcifully any file 16.com/inbox Read messages from SAP to you Download SAP Installation Guides product installation guides License Keys License Key http://service. cp coppy from one location to another 19.
sap.sap.com/sscr Register Developers and made against SAP objects User Administration http://service.Messages to SAP QuickLinks Page Oracle DBA Page Material OSS Notes Database Patches patches Remote Connection connection and http://service.com/message http://service.com/serviceconnection Open a Service Connection for SAP to access your SAP landscape Software Distribution http://service.com/patches Open problems with SAP An index of SAP links Page for Oracle DBA Search the SAP Notes Download SAP software http://service.com/user-admin user information Add/Change OSS ID .sap.sap.sap.com/remoteconnection Learn about the OSS order it from SAP Service Connection http://service.sap.sap.sap.com/swdc Download new images of Installation CDs & DVDs SSCR Changes http://service.sap.sap.com/dbaora http://service.com/notes http://service.com/quicklinks http://service.