SAP Basis is a niche IT skill. This is very demanding in IT companies. http://basissap.blogspot.

com

Basis consultant requirement is always high and there are very less numbers of good experience Basis consultants available in IT market. This make SAP Basis high paying job. Many times it is been asked how to become a Basis Consultant. There are many SAP training institutes which are providing BASIS training, but most of them doesnt have good infrastructure available with them to give live practical training. It is very important for Basis Consultant to have hands on experience on live servers. There are good Institutes are available like Siemens, Genovate and NIIT. This institutes are having good infrastructure to provide to work real scenarios.. As a fresher one can also go into SAP BASIS, many IT companies are there which recruit people from Campus provide them In house training in SAP BASIS. But most important for a Basis Consultant is to have hands on experience on Live Production Servers. Because every scenario could not be created in Training Environment or by Installing SAP at home. I have seen many people which show many year of experience but in actual they dont have proper knowledge.

Three most important things are required to be a good Basis consultant.

1. Good knowledge of OS (Unix, Linux and Windows). Having good knowledge of makes a consultant resolve issue very fast and he can do deep analysis on any problem which related to OS side. Unix experience is very advantage in Basis Side, because most company use Unix/Linux servers in there landscapes.

2. Any Database knowledge is very helpful to a consultant like Oracle, DB2 and Maxdb etc. It gives added advantage in anybody career. Because in day to day scenarios one can face mostly DB related issue.

3. Third important point is overall SAP knowledge, about its architecture, how its work?. How transaction works and etc There are many sites available in Internet where one get learn SAP Basis. Most important site is SAP SDN, where you can get latest information about SAP. There are many forums available and while paper available in SDN.

What is system refresh when and why it is done? The system refersh is nothing but the deletion of the client and replacing the data from other client. For example : you have clients 100, 200 and 300. Suppose when you want to refresh the client 100 you remove the client 100 and replace it with 200 0r 300 as per your requirement. Mostly the refresh of clients will be happen at the time of development stage. System Refresh is a simplified term to Client Copy. Client Copy means copying the production client on to the quality to test the real data. As recommend by SAP this need to carried out every 3 months. The process to carry out the same is as follows:

1. Create a client on quality system using txn scc4 2. Create a RFC between Production system and Quality System (need to create on quality system) 3. Login to the newly created client using sap* and pass as a password 4. Txn sccl to start the client copy. You can test the client copy by selecting the test run option. (test run will estimate the time taken for the activity. This is also called as local client copy.

How to change SDM password

Change SDM password 1. goto to the path /usr/sap/SID/CI/SDM/program at OS level stop SDM server first to reset the password

/.StopServer.sh

2. Then start SDM in standalone mode :sdzadm 65> ./sdm.sh jstartup "mode=standalone" Starting '/opt/IBMJava2-amd64-142/bin/java' '-Xmx512M' -jar '/usr/sap/SDZ/DVEBMGS35/SDM/program/bin/SDM.jar' jstartup 'sdmhome=/usr/sap/SDZ/DVEBMGS35/SDM/program' mode=standalone Starting SDM - Software Deployment Manager... tc/SL/SDM/SDM/sap.com/SAP AG/7.0106.20091119090254.0000 Initializing Network Manager (53517) Checking if another SDM is running on port 53518

Operationmode for JStartupFramework set to "standalone". Successfully executed. Return code: 0

3. Now change SDM password by below command

./sdm.sh changepassword newpassword=PASSWORD

4.After changing password change SDM mode to integrated mode

./sdm.sh jstartup "mode=integrated"

5. Now start SDM

./StartServer.sh

sap* user id unlock

How to unlock SAP* user id. As a Basis Consultant many times we require to unlock or rename SAP* user id in system. Providing few oracle sql command to rename or unlock the SAP* user id Rename SAP* user id update sapsr3.usr02 set bname='SAP*1' where bname='SAP*' and mandt='500'; and then try to login into client from SAP* user id. Default password is pass Unlock sap* user id. update sapsr3.usr02 set flag=0 where bname="ddic" and mandt='500'; or update sapsd1.usr02 set uflag=0 where bname='SAP*' and mandt='220'; To check the status of SAP* user id select status from sapr3e.usr02 where bname='SAP*' and mandt='220' Delete SAP* user id. delete from sapsr3.usr02 where bname='SAP*' and mandt='020';

What is authorization, authorization object, authorization profile, role?

Actions and the access to data are protected by authorization objects in the SAP system. Authorization objects allow complex checks that involve multiple conditions that allow a user to perform an action. The conditions are specified in authorization fields for the authorization objects and are AND linked for the check. Authorization objects and their fields have descriptive and technical names. An authorization is always associated with exactly one authorization object and contains the value for the fields for the authorization object. An authorization is a permission to perform a certain action in the SAP system. The action is defined on the basis of the values for the individual fields of an authorization object. A role is primarily a functional description The technical realization of the role, in the form of concrete authorizations is achieved through the authorization profile associated with the role.

What is a composite profile?

A set of profiles which are included under a single profile name is called as a composite profile (SU02) How can you find missing authorizations? How can you solve? By running the SU53 transaction. Identify the authorization object where the required filed value is to be given and the do the same thru SU01 or PFCG. to refresh the DEV client with PRD client. My requirement is the program version history should not loss in DEV system after the refresh? The client export/import with SAP_ALL only copies client dependent data hence it won't affect the version history. With client export/import the repository is untouched and so version history is unaffected. Also Support package level for QAS and PRD should be same for best results. For Client Import-export you need to check space on your QAS server if enough disk space is available or not. Check client size by running the report RSTABLESIZE & RSSPACECHECK. Please refer this SAP Note 118823 CC-ADMIN: Size of a client. Plan to perform a client refresh by using import/export method. 1.-Export client from PRD to transport directory 2.-Import client from transport directory to QAS

You have to first import the Transport on your target client then do the post processing on SCC7.

Once you are done with Phase 2 i.e. client import, you have to perform post client copy steps This could be done with SCC7 T-code.

What is a client copy?

A client copy does not "generate a new system". It is used to transfer information between clients within the same system or to another system atthe same release and db level.

Procedure to create: If it is a fresh installation, do this -1. SCC4 --> Create client no. and fill other details. 2. Logon to the newly created client with SAP* and PASS as password. 3. SCCL --> choose any profile (preferably SAP_ALL), source client 000 and target client .

4. Preferably do a test run initially to check if it can go well. 5. As a care check space in databases. You can do Client copies remotely or do an export/import of data. Please study the dependencies of client dependent/independent data rel. notes. Export: If you need to do a full client copy and database is more than 50 or 60gb, the import may tae little long time. Export of the full data can be done with SAP_ALLprofile in Source system. SCC4 >> Export the data with required profiles. It will create data and cofiles under os level. (usr/sap/trans/data, cofiles).The export may take of 8 to 20 hrs dependts on data.The import may take several days based on the size of the data. You need to set some parameters before you start the import. After the succefull import you need to do post processing for client copy with request in scc8. It depends upon what method you want to do client copy. If you say remote client copy, i will suggest you against it because it takes hell lot of time to do client copy and any break for a moment in network connection will cause failure in client copy.If you are exporting the client then as such there is no problem, just remember the sequence in which you import the three (or two) transport requests.AND, keep enough free space in Tablespaces of Target server Procedure : 1.Check Sufficeint space at OS level to keep extracted data from source client 2.Export the client using following path or scc8Tools (r) Administration (r) Administration (r) Client Admin. (r) Client Transport (r) Client Export. Select the data to be copied using a profile. (if u wnat client specific and cross client data use profile sap_expc). before importing ensure that all table spaces have enough sapce for this check source system table spaces and allocate table space accordingly) 3. Now create new client in target system 4. now import those requests in target client using stms or scc6 5. Now perform post processing Tools (r) Administration (r) Administration (r) Client administration (r) Client transport(r) Import editing

http://basissap.blogspot.com/2008/05/what-is-client-copy.html

Procedure for Client Export

http://basissap.blogspot.com/2012/06/client-export-logon-by-client-100-from.html

Client Export

Logon by the client 100 from where we have to do client export.

Enter Target system the same the system.

SAP_ALL Profile should be selected. The profile will differ according to the requirement.

The two files has to be given co file and data file. 2. & 3. one. In the above list.

Goto SCC3 transaction to see the status of the Client Export.

Click on processing. Again a screen will appear click on processing.

Here you will get the status.

What's the use of a domain controller and how to configure the same?
The transport domain contains all SAP systems whose transports are to be administrated jointly. One of these SAP systems is chosen as the transport domain controller. Since all activities relevant to the entire transport domain, such as configuring transport routes or RFC connections, can only be carried out on the domain controller, the SAP system selected to be the domain controller should have: High availability A high level of security A high level of maintenance

The domain controller is normally configured on a production system or a quality assurance system. Out of several reason you may choose to set up an SAP System dedicated to tasks that may be carried out CENTRALLY. This includes the task of the TMS domain controller. The system load on the SAP system that is chosen as the domain controller is low, and only increases for a short period when the TMS configuration is changed. Configuration:

To activate the TMS on an SAP system, run transaction STMS in client 000 with user authorization S_CTS_ADMIN. If the SAP system is already assigned to a transport domain, the TMS ini tial screen shows the systems status, either as a domain controller, or as a SAP system within a domain. If the SAP system is not yet assigned to a transport domain, the system tries to locate an existing transport domain within the current transport group by reading the file DOMAIN.CFG in the directory bin of the common transport directory. If no transport domain exists, a new transport domain is created, and the current SAP system is assigned as the transport domain controller. When a transport domain controller is first created, the TMS generates: A transport domain and a transport group User TMSADM The RFC destinations required for the TMS File DOMAIN.CFG in directory bin of the common transport directory, for storing the TMS configuration o The name of the transport domain may not contain blanks and may not be changed afterwards without reconfiguring the domain controller. By default, a transport domain will have the name DOMAIN_, where is the system ID of the domain controller. The name of the transport domain cannot be changed afterwards.

How will you configure a STMS, 3 system configuration?

To configure the TMS: Configure the transport domain Assign SAP systems to the transport domain, and specify one SAP system as the transport domain controller. Configure transport routes The transport routes are used to define both the target system in which you want to consolidate change requests, and the SAP systems to which change requests are delivered after verification and testing. Configure Quality Assurance (QA) Procedure Define a QA system, where the decision is made whether objects may be further transported to the production system. After setting up the TMS, use the TMS tools to check and monitor TMS configuration.

How many types of transport requests? Explain?

There are 3 types of requests: K type: The transport K type implements transports of DE objects from the integration system into the consolidation system. When you create a transport request using the workbench organizer, it always uses this transport type by default meaning that all the transportable change requests stored in the workbench organizer are allocate this transport type. For this transport type, the objects are transported to the consolidated systems without changing the obj ects system owner which means that the transported objects in the consolidated system become repair objects and no corrections are allowed for the imported objects. C type: With this transport type the objects change the system owner after they are transported which means that the source system of the object loses its ownership after the object is transported. So the target system in which the objects are transported becomes the original system. In other words objects are transported as original objects. So they can be corrected or modified in the target system too. That means that change authorization is also transported. In SAP terms, objects that are transported with C types are checked out of a system and checked into another system.

T type: This transport type is useful when you have to copy object between two systems in a group ie when a system(other than consolidation system) receives a copy of objects, the corresponding transport takes place with transport type T. Object including the object of transport type T do not change their system owner. So the original system remains same.

What is STMS? How do u configure it?

STMS is used for configuring routes / importing into relevent server after release of a request. STMS is being used to transport all your customization and workbench work from Development to QA and then to production.There are several steps need to follow for STMS configuration.1. Create Common mount point /usr/sap/trans. (Normally Development server file system need to be mount with Production system with nfs.)2. In all servers, to configure STMS follow the steps as mentioned below.i. Create Systemii. Select same domain for both the systems.iii. Again in Development server create Transport Route. (One Transport Layer for Standard objects and one layer for Customer Objects)iv. Activate the router in all the systems.3. Check the Status of all system of STMS after activation.

Type of Users in SAP system

1. Dialogue:For this kind of users:GUI login is possible. Initial password and expiration of passowrd are checked. Multi GUI logins are checked. Usage:- These are used for GUI logins. 2. System For this kind of users:GUI login is not possible. Initial password and expiration of passowrd are not checked. Usage:- These are used for internal use in system like background jobs. 3. Communication For this kind of users:GUI login is not possible. Users are allowed to change password through some software in middle tier. Usage:- These are used for login to system through external systems like web application 4. Service For this kind of users:GUI login is possible. Initial password and expiration of passowrd are not checked. Multiple logins are allowed. Users are not allowed to change the password. Only admin can change the password Usage:- These are used for anonymous users. This type of users should be given minimum authorization.

5. Reference For this kind of users:GUI login is not ible. Initial password and expiration of passowrd are not checked. Usage:- These are special kind of users which are used to give authorization to other users.

AIX command for Basis administrator

Simple commands
chgrp grp filelist : Change the group that the file(s) belong to. chmod 777 filelist : Change the rights of the file(s). 777: owner-world-user. 7: read-write-delete (=111) chown user filelist : Change the owner of the file(s) cp file1 file2 : Copy file1 to file2 cp /dev/null file : Clear all contents of file errpt : Hardware error-report (IBM-unix) ls ltr : Show filelist, parameters: l: show fileattributes , t: sort by time, r: reverse sortorder more

mv file1 file2 : Move command ps ef : Show all running processes, -e, -f vi : The famous vi-editor

2 A little more complex commands

kill : Kill a process as if it is cancelled. Child processes are killed as well. kill 1 : Kill a process as if the user is logging out. Child processes are killed as well. kill 9 : Kill a process as brutal as possible. Child-processes are not touched. kill USR2 : Increases TRACE by 1 kill USR1 : ecreases TRACE by 1. When TRACE = 0 all open trace files are closed and can be cleared using cp /dev/null filename. lslv : Show the logical volumes lsvg : Show the volumegroups sappfpar check pf= : Checks the profileparameter. Do they exist and do they have correct values. set VAR VAL : set environment variable VAR to value VAL printenv : prints the environementvariables ps ef grep xxx : Monitor processes with name containing xxx ps u : Monitor processes run by user

Importanat database command : BRTOOL and BRBACKUP

Querying tape Required : brbackup -q brarchive -q

Initialising tape: brbackup -c -i force -v / SCRATCH brarchive -c -i force -v / SCRATCH Backup: Database Backup brbackup -c -m all -t online -a -c -cds For Online Database brbackup -c -m all -t online_cons -a -c -cds For Online consistent backup (Database + Archive Logs) brbackup -c -m all -t offline -a -c -cds For Offline backup Archive Log Backup brarchive -c -cds Archive Log Backup with Copy ,delete & Save brarchive -c -sd Archive Log backup with Save & Delete

Queryng Tape No. present inside Tape Drive brbackup -i show Restoring Offline Backup from Tape brrestore c m all b <.aft file> *.aft file for that particular backup will be at path : oracle\SID\sapbackup\<.aft> Forcefully Ending the backup 1 Execute DB02 TCode 2 Go to Current Sizes 3 Read the Tablespace name whose backup status is 'ACTIVE' 4 Telnet of the Server / Take Dameware of server & goto command prompt 5 sqlplus /nolog 6 conn /as sysdba 7 Fire following command alter tablespace end backup;

How can you configure the printer? Explain the spool admin?
The configuration of the spool system is a system administration task. The central tool for this is transaction SPAD. To create an output device, choose Output Devices on the Devices / Servers tab page. If there is already a large number of devices in your system, you can restrict the output list in the field next to the button (for example .PR*.). Important information for a device: Output device Name, maximum of 30 characters long (case-sensitive).

 Short name For internal system purposes (can be automatically generated). Device type Printer model/family (more information about this below). The device type SWIN transfers the SAP system format to the Microsoft Windows printer driver. This is useful, for example, if various printers are used for front end printing in a Microsoft Windows environment. Spool server SAP application server with spool work processes or logical server. Location For example, building and room number (so that users can find their output). Message Used to temporarily override the location (such as .Is currently in maintenance.) Lock printer in SAP system Output requests for printers for which this indicator is selected are created but not transferred to the printer. The user receives the message ...no immediate printing. Host spool access method How does a spool work process contact the operating system spooler? Host printer Name of the printer at operating system level. Note that this name is case-sensitive. Under Microsoft Windows, there must not be a space in the printer name, and network printers are addressed using their UNC names (in the format \\R12345\P42). The specification __DEFAULT calls the defaultMicrosoftWindows printer (for example, for front end printing in a Microsoft Windows environment). Host Only for local printing, is calculated automatically from the spool server. Destination hosts Only for remote printing. Name of the host on which the operating system spooler (such as lpd or saplpd) is running.

Explain the client create, delete and copy?

We can create a client using the transaction SCC4. Mention the client name with the appropriate selection. Note that SAP delivers the software with standard clients 000 and 001. You may not work in client 000, but may use client 001. However, SAP recommends that you begin SAP System implementation by creating a new client as a copy of client 000. To Copy a client o A local client copy copies between clients within the same SAP System.

A remote client copy allows you to copy between clients in different SAP Systems.You can use a remote client copy to, for example, transport client-dependent as well client-independent Customizing data between SAP Systems.

o o o

A remote client copy proceeds in the same way as a local copy, but sends the data through a remote function call (RFC) connection to the target client. A remote client copy is easy to use, and does not require file system space on operating system level. The limitations of a remote client copy are as follows: A remote client copy does not create a file at operating system level, so there is no "hard copy" of the client to be copied. Therefore, the same, identical client copy cannot be duplicated at a later date.

To delete a client from within SAP System: o o Log on to the client to be deleted. Use the menu option use Transaction code SCC5 or from the SAP System initial screen choose Tools _ Administration _ Administration _ Client admin _ Special functions _ Delete client. o o Start the deletion of the client, preferably using background processing. When you delete a client entry from table T000 with client maintenance (Transaction SCC4), you can no longer log on to the client or update it using change requests. The deletion process, however, does not eliminate the data belong to the client. This means the client-dependent data remains in your SAP System, occupying space in the database. Therefore, to eliminate an SAP client entirely, that is, to delete both the client and the client-dependent data, use the client delete functionality (Transaction SCC5). o Deleting a client entry with client maintenance (Transaction SCC4) allows you to temporarily lock the client. The deletion procedure preserves the data for the client but prevents users from logging on to the client or accessing the data belonging to the client. To restore the client and allow logon, recreate the client entry using client maintenance. o The amount of time required for the deletion of a client can be reduced by performing the deletion using parallel processes.

The entire procedure for DRS switchover

PRODUCTION TO DRS SWITCHOVER

1. Take Offline backup of the PRD Database.

2. In SM02, Put message on the PRD system.

3. On PRD,

cmd>SVRMGR30 Connect Internal; Alter system switch logfile; Do switch log file 3-4 times.

4. In DRS, apply up to the last Archive Log created in PRD.

5. On PRD, Stop R/3, Shutdown Database And Stop SAP & Oracle Services.

6. On PRD, Backup Mirrlog A, Mirrlog B, Origlog A, Origlog B & Control file of PRD.

7. Shutdown DRS Database & Stop Oracle Services.

8. On DRS, Backup Mirrlog A, Mirrlog B, Origlog A, Origlog B & Control file of DRS.

9. Copy the redo log files & control files from PRD (production DB System) to DRS (DRS DB System). Copy the control file to all the locations on DRS (OriglogA, Saparch & Sapdata1 sub-folders).

10. Start the Oracle Services on DRS.

11. In DRS Start SVRMGR30 Connect Internal; Startup Mount; Recover Database; (Ensure the message Media Recovery Complete appears). Alter databases Open; (This opens in NORESETLOGS mode). Exit; 12. Start SAPOSCOL, SAP_00 services on DRS.

13. Start SAP R/3 application on DRS.

14. Logon to the DRS System through SAP Logon Pad.

15. Check the System Status & transactions like SM51, ST22, and SM21 Etc.

DRS TO PRODUCTION SWITCHOVER

16. On DRS, Stop R/3, Shutdown Database and Stop SAP & Oracle Services.

17. Copy the redo log files & control files from DRS (DRS DB System) to PRD (production DB System). Copy the control file to all the locations on PRD (OriglogA, Saparch & Sapdata1 sub-folders).

18. Start the Oracle services on the DRS.

19. Start the Oracle Services on PRD.

20. In PRD Start SVRMGR30 Connect Internal; Startup Mount; Recover Database; (Ensure the message Media Recovery Complete appears). Alter databases Open; (This opens in NORESETLOGS mode). Exit; 21. Start SAPOSCOL, SAP_00 services on PRD.

22. Start SAP R/3 application on PRD.

23. Logon to the PRD System through SAP Logon Pad.

24. Check the System Status & transactions like SM51, ST22, and SM21 Etc. Note: - DRS: DRS database server PRD: Production database server

SAP Test system refresh activity

SAP Test system refresh activity. Follow the below steps for SAP test system refresh activity from Production server backup.

1. Take the relevant screenshot of system STMS,SCC4,SM59,SAP standard jobs,DB13,SLICENSE,CCMS settings,SPAD 2. Import the SPAD settings 3. Take the offline backup of production system 4. Take the backup of backSID.log,*.aft and initSID.ora of production and test server

5. Lock users in Test system 6. Take offline backup of test system 7. Open client in test server : SCC4 8. Export the client for profile SAP_USER in test server. Keep test system as target server SCC8 9. Take the trace of control file on both the Test and production server 10. Stop the SAP instance and sap services 11. Note down the Schema users existing presently in the system. SQL> select user name from dba_users; 12. Shutdown the database 13. Copy last offline backup log file(*.aft) from production system to test server 14. edit the *.aft log file as per test server change SID from prdoduction to test server SID, check ORA-HOME directory 15. Now restore the backup brrestore c m full b XXX.aft 16. Connect to oracle as sqlplus /nolog, connect /as sysdba and type startup Nomount. 17. Edit the controlfile of Prod. Change all production SID to test SID and NORESETLOGS TO RESETLOGS. 17. Use the edited controlfile of Prod to recreate the control file of Test SQL> @Cntrl.sql SQL>shutdown immediate; 18. SQL> Alter database open RESETLOGS. 19. Create new OPS$ADM using the below command. I:\scripts>sqlplus /nolog @ORADBUSER.sql SAPSID NT DOMAIN SID (IF SIDADM is local user then give the host name in the place of Domain Name)

20. After this run the script sapdba_role to set proper right for OPS$ user IDs. >sqlplus /nolog @sapdba_role.sql 21. Check whether SAPSR3P (schema owner) account has been locked or not: select username,account_status from dba_users where username=SAPPCE; 22. If it is locked use this command to unlock it: alter user SAPPCE account unlock; 23. Start the SAP application. POST Processing Steps: 24. Update the license Logon to SAP with DDIC-client 000; update the license key through the transaction SLICENSE. 25. check the consistency Go to transaction SICK for checking the consistency of the system. 26. check the local host entry Go to transaction SE37 and execute BPT_LOCAL_HOSTNAME_CHECK to check for the hostname entry. 27. Change the STMS configuration and perform post installation activity Now go to transaction SE06 to perform post installation activities 28. Reconfiguring STMS 29. Login into DCE client 000 with DDIC , goto transaction STMS. 30. Schedule the standard jobs Go to transaction SM36 and click on the button Standard jobs to schedule the standard jobs defined for the system. 31. Import the user master of test server Goto the STMS and import the user master request 32. Close the client 33. Changing the client description.

34. Import profiles of active Server using RZ10. 35. Delete incorrect instances defined in RZ04, create correct instances and assign Operation modes for the same 36. Change the logical system name 37. Take an OFFLINE backup of the Test system and release the system to the users.

Oracle Bundle Patch

How to Apply Oracle Bundle Patch Download the dump from SAP service market place to your system. 1.PRE INSTALLATION INSTRUCTIONS Copy the dumps of patch at below mentioned path. Drive/oracle/"SID"/"oracle version"/OPatch Stop SAP & DB along with all services of SAP & DB. Back up the current database that is installed, the %ORACLE_HOME% directory and Oracle inventory under c:\Program files\oracle directory. (This will help if there are problems applying the patch, and to restore the Inventory in case of an issue with the patch.) Now apply bundle patch. OPatch>opatch apply patch no Installation may be interrupted coz. of error in overwriting an existing .dll file giving following error file already in use. In case of above error dont rename the file and RETRY(It doesnt work) instead cancel the installation then and there rename the .dll file and start patch application again. 3. POST INSTALLATION INSTRUCTIONS Start all services of DB & DB

 Run script catcpu.sql sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> STARTUP SQL> @%ORACLE_HOME%\Bundle\Patch17\catcpu.sql SQL> QUIT If above script reports any error then Inspect the logfile %ORACLE_HOME%\Bundle\Patch17\Apply__.log for any errors. If catcpu.sql reports any Invalid Objects, compile the invalid objects as follows. sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> @%ORACLE_HOME%\rdbms\admin\utlprp.sql 0 Above script will compile the invalid objects. To check for any invalid objects still there or not, execute the following statement: SQL> SELECT OBJECT_NAME FROM DBA_OBJECTS WHERE STATUS = 'INVALID'; Recompiling Views in the Database To recompile the views for each database instance running out of the ORACLE_HOME being patched , follow these steps: Run the pre-check script, which reports the maximum number of views and objects that may be recompiled: sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> @%ORACLE_HOME%\Bundle\view_recompile\ recompile_precheck_jan2009cpu.sql

SQL> QUIT Run the view recompilation script. Note that this script is run with the database in upgrade mode, which restricts connections as SYSDBA. sqlplus /nolog SQL> SHUTDOWN SQL> CONNECT / AS SYSDBA SQL> STARTUP UPGRADE SQL>@%ORACLE_HOME%\Bundle\view_recompile\ view_recompile_jan2008cpu.sql SQL> SHUTDOWN; SQL> STARTUP; Check the log file for any errors. The log file is in the current directory and is named: vcomp__.log If any invalid objects were reported, run the utlrp.sql script as follows: sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> @%ORACLE_HOME%\rdbms\admin\utlrp.sql If still any invalid objects are there then recompile those manually. SQL> alter schemaname. compile; Verify that the view recompilation has been performed for the database, by executing the following statement: SELECT * FROM registry$history where ID = '6452863'; TO VIEW ALL PATCHES APPLIED ISSUE BELOW COMMAND:\ORACLE\"SID"\"oracle version"\OPATCH>OPATCH LSINVENTORY

Handy Oracle SQL commands

Here i am listing some Oracle Sql commands which are very useful useful many times.

1.Count no. of records in a table select count(*) from sapsr3.vbfs;

2. Count no. of sessions in db SELECT inst_id, count(*) "DB Sessions" FROM gv$session WHERE type = 'USER' GROUP BY inst_id;

3.Check status of file in recovery select FILE#,STATUS from v$datafile where status like '%REC%';

4. Check status of file in Offilne state select FILE#,STATUS from v$datafile where STATUS like 'OFFLINE';

5. Rebuild index online alter index "SAPSR3"."RSSTATMANREQMAP~PT" rebuild online;

6.Check last optimizer statiscs run select TABLE_NAME, STATUS, LAST_ANALYZED from DBA_TABLES where TABLE_NAME='VBFS';

7. Determine file name from file id. select FILE_NAME from dba_data_files where FILE_ID in (56,59,60,61,62,63,65,66,67,68);

GRMG configuration for TREX system

.Log on to the TREX host as root

<!--[if !supportLists]-->2. <!--[endif]-->Go to the directory . : /usr/sap/TPZ/TRX10

Set the environment variables required by TREX by executing the following scripts. . TREXSettings.sh

3. <!--[endif]-->Go to the directory /exe/CCMS, in which the script for installing the TREX monitoring functions is located

4.Execute the following command to configure monitoring of availability (heartbeat/GRMG): python ccms_config.py --grmg

Created GRMG upload file at location : /usr/sap/TPZ/TRX10/hostname/trace/grmg/GRMG_config.TPZ_10.hostname.xml

Uploading XML Customizing File by Transaction GRMG

1. Start transaction GRMGin the SAP system. 2. Choose Upload/Download. There are two ways to upload the TREX scenario: Choose Upload/Download Upload Scenario.

Choose the XML customizing file for the corresponding TREX instance and choose Open.

The window GRMG customizing file uploaded successfully appears.

Choose Upload/Download Poll agents for new scenarios.

This upload of the TREX scenario will only work if the SAPCCMSR agent is running and has been registered previously. In the list GRMG Scenarios for Availability Monitoring, choose the corresponding TREX scenario. Choose Start/Stop Start Scenarios. The window GRMG scenarios have started appears.

Shared memory issue while starting sapccmsr

SAPCCMSR not getting started

First try to clear shared memory by executing following command. sapccmsr -initshm pf=/sapmnt//profile/ Even if doesnt clear the shared memory from system for sapccmsr. Then check shared memory segment 4dc4 from user id sapadm. To identify shared memory segment execute following command ipcs -am | grep sapadm

If it is there then need to clear it Note : Only clear shared memory segment 4dc4. This is related to monitoring segment, until it doesnt get clear sapccmsr will not start. Once it is cleared sapccmsr will start on that host.

RMAN for SAP BRTOOLS

Important point needs to be consider while configuring RMAN for SAP BRTOOLS.

I had to configure RMAN for taking incremental backup of our SAP database by using RMAN. Here i have mentioned point which helped me to connect BRTOOLS to RMAN.

create following link first after installing TSM service at OS host

cd $ORACLE_HOME/rdbms/lib ln -s /usr/tivoli/tsm/tdp_r3/ora64/libtdp_r3. /usr/lib/libobk. ln -s /usr/lib/libobk.so $ORACLE_HOME/lib/libobk.so

Mentione device type as for taking backup through RMAN backup_dev_type=rman_util

Set rman_parms to identify brtools for TSM parameters.

rman_parms="ENV=(XINT_PROFILE=/init.utl,PROLE_PORT=,&BR_INFO)"

Locate the appropriate ProLE port number in the /etc/services file. Look for port name tdpr3ora64

Below parameters also need to set in initsid.sap parameter file

saveset_members = 1 rman_channels = 6 : This parameter defines the number of parallel channels used by RMAN with an external backup library, that is, backup_dev_type = rman_util rman_filesperset = 8

Make sure /usr/lib is specified in the library path environment of your system.

System refresh using RMAN backup

Here i am providing steps for System refresh using RMAN backup.

1.Ensure db is shutdown Sqlplus / as sysdba Shutdown immediate

exit
2.Create a symbolic link on target server cd /oracle

ln s /oracle/ 3. Ftp to the following directory on Source server

/oracle//sapbackup

Copy to /oracle//sapbackup on the target server the required file for the restore. Note you will always need the .fnr (Level 0) backup

Also copy across the required .inr file, this should be the .inr backup closest to the point in time you are trying to recover to, but not later than.

Final file to copy is back.log

Once copied to target server, ensure permissions are correct 4. Ftp to the following directory on Source server
/oracle//102_64/dbs

Copy the following files to /oracle//102_64/dbs

Init.dba init.ora init.sap init.sap init.sap_rman_incr spfile.ora init.bki Again check permissions once copied

5. Set environment variables on target server Note Ensure you are logged in as ora SETENV DB_SID SETENV SAPDATA_HOME /ORACLE/ SETENV ORACLE_HOME /oracle//102_64

If your session times out, or you log off these environment variables will need to be set again

6. Restore the DB control files saved with the Level 1 backup (This is the .inr file)
brrestore -b <.inr file> -m 0 -d rman_util
Once complete you should then have the Source SID control files in the following locations

/oracle//sapdata1/cntrl /oracle//origlogA/cntrl /oracle//origlogB/cntrl

7. Mount the Database Sqlplus / as sysdba Startup mount Exit

8.Start the restore of the data files

brrestore -b <.fnr filename> -m all -d rman_util

Check log file for successful completion

9. Apply incremental backup once step 8 complete

brrestore -b <.inr filename> -m incr -d rman_util

Check log file for successful completion 10. Shutdown DB

Sqlplus / as sysdba Shutdown immediate

exit 11. Log off as ora to reset environment variables to original values 12.On target server remove the logical link created earlier
Cd /oracle

Rm 13. Change the SID of the database by running the control.sql file:
Run the control.sql script at the sqlplus command prompt: - logon to target system and type:su ora sqlplus /as sysdba sqlplus> @control.sql sqlplus> exit;

Follow Step mention in System Refresh Documentation to complete point in time recovery using log files.
14.

15. You can check the database has returned to its original SID and using the correct control files by issuing the
following commands Sqlplus / as sysdba Show parameter control_file;

The output should reference the target SID

select NAME from v$database;

This should show the target SID 16. Continue as per System Refresh activity. and follow remaining Post processing steps Safeguarding the version database during a refresh of the development system Introduction Developers and customizing consultants often need representative transaction data -- both in terms of quantity and quality -- in their development system. This is especially true in two-system SAP landscapes (SAP landscape with only a development and production system, no quality assurance). In almost every SAP environment, after several months or years, the discrepancy between the data in the development and

production system becomes problematic, as it makes ongoing development and customising difficult or nearly impossible. Two procedures exist to refresh transaction data in the development system: client copy or client transport and a database copy. Both of them have serious drawbacks: -- Client copy using remote function calls or client transport. Although this might be feasible in small environments, it has many disadvantages: * It can cause inconsistencies between client-dependent and client-independent data (or overwrites the client-independent data of the development system if client-independent customising was included). * Both the source and target clients are unavailable during the client copy. The source client is unavailable during the client export if client transport is used. * The process is too slow for copying large production clients. -- A database refresh in which the development system is completely overwritten with a backup of the productive system:

* SAP strongly recommends always retaining

Steps For SAP Client Copy / System Refresh

Before doing a client copy, you need to prepare the following :-

1. Find the source client space with the client size custom program which can be implemented using the rel. note: Find the space of the client - '0118823'. This will give you the size of the source client. 2. If your are on Unix OS, adjust all the file systems according to PRD file system to fit the PRD client in DEV client based on space requirements also. 3. You can do the client copy by remote or Export/Import Client. Remote method is not preferred if you are doing a large client copy. Do a client export/import. 4. To speed up the export/import, use R3trans export/import for the clustered tables. Please find the rel. notes related to performance improvements for cluster tables in OSS. 5. Do import and post processing. Note: Export may take 10 to 20 hr. for 50gb of data import may take 4 days and post import will take 8 to 15 hr. for 50gb of data. And it all depends on

your system performance. Please refer OSS rel. notes for the few RZ10 parameters which needs to be set for cluster tables to speed up the process. Note :If it is a fresh installation, do this -1. SCC4 --> Create client no. and fill other details. 2. Logon to the newly created client with SAP* and PASS as password. 3. SCCL --> choose any profile (preferably SAP_ALL), source client 000 and target client <as created just now>. 4. Preferably do a test run initially to check if it can go well. 5. As a care check space in databases.

What are step and procedure to create a client & to take a client copy from source to target.
By: Kavitha.G If you are copying from same system then flow the below steps: 1. Create the client in Tcode scc4. 2. Before that create a logical System in BD54. 3. Login in the newly created client with user Name : sap* and password : pass 4. Use the Tcode sccl to copy the client. If you are not familiar with the client copy. Try a test run and then schedule it in background. 5. You can select the needed profile. 6. To view the log files use the tcode scc3. If you are using different system then create a rfc connection in sm59. Test the connection and then continue from the 1st step. You can also import and export a client. Use scc7 for importing from the client and scc8 fro exporting from the source client

What is system refresh when and why it is done?

System refresh and client copy can be the same thing. Normally when you want to refresh a system this normally means refreshing the clients using a client copy like SCCL or SCC8. A system "copy" is very different as this is far more involved than a simple "client refresh" Imagine you have a DEV and a PRD system and after 6 months the data in DEV is very old so you would perform a client copy SCC8 from PRD to DEV using a profile that copies the

application data from PRD to DEV - it actually deletes the data and replaces it with data from PRD. If however your DEV system died and needed to be completely rebuilt, you would use "Homogeneous System Copy" - you install the OS, Database and SAP and then process the system copy - which makes a complete copy of PRD (all clients) Client copy - a single client refresh from PRD to DEV - can be just application data, or user data, or configuration or any combination you choose system copy - all clients 100% copied PRD to DEV The system refersh is nothing but the deletion of the client and replacing the data from other client. For example : you have clients 100, 200 and 300. Suppose when you want to refresh the client 100 you remove the client 100 and replace it with 200 0r 300 as per your reqiurement. Mostly the refresh of clients will be happen at the time of development stage. System Refresh is a simplified term to Client Copy. Client Copy means copying the production client on to the quality to test the real data. As recommend by SAP this need to carried out every 3 months. The process to carry out the same is as follows: 1. Create a client on quality system using txn scc4 2. Create a RFC between Production system and Quality System (need to create on quality system) 3. Login to the newly created client using sap* and pass as a password 4. Txn sccl to start the client copy. You can test the client copy by selecting the test run option. (test run will estimate the time taken for the activity).

SAP Best Practices Client Copy and Before Copying

What are some of the activities that we must to do before a SAP system copy?
By: Andrew These are what you can do: 1. Export the users, roles and authorisations with Tx SCC8 using profile SAP_USER. 2. RFCDES RFCATTRIB and RFCDOC a. Create file export_sm59.r3t contents: Export file 'C:\exp\EXPORT_SM59.DMP'

delete from rfcattrib select * from rfcattrib delete from rfcdes select * from rfcdes delete from rfcdoc select * from rfcdoc b. Create file import_sm59.r3t contents: import file = 'C:\exp\EXPORT_SM59.DMP' c. Run an export on source: R3trans -w c:\exp\EXPORTSM59.log c:\exp\export_sm59.r3t d. When ready, import on destination: R3trans -w c:\exp\IMPORTSM59.log c:\exp\import_sm59.r3t e. Reset the secure Store with Tx SECSTORE 3. You will have to copy the Background jobs and recreate them afterwards. For your information, it's possible to copy the tables of all background Jobs. To do this I created a file export_jobs.r3t with the following contents and I tested it and it worked well (please test it as not all system are alike). Export file 'C:\jobs\JOBS.DMP' delete from TBTCA select * from TBTCA delete from TBTCB select * from TBTCB

delete from TBTCCNTXT select * from TBTCCNTXT delete from TBTCCTXTT select * from TBTCCTXTT delete from TBTCCTXTTP select * from TBTCCTXTTP delete from TBTCI select * from TBTCI delete from TBTCJSTEP select * from TBTCJSTEP delete from TBTCO select * from TBTCO delete from TBTCP select * from TBTCP delete from TBTCR select * from TBTCR delete from TBTCS select * from TBTCS 4. It is not considered good/best practice to perform a system copy into the development system. However, if there is no other way you can keep the version management with SAP note 130906. Points to note: It is NOT a best practice to copy Production data into the Development system. It is best practice for the Development and Configuration to be consistent across the landscape

but not necessarily in terms of data. You should not have production data in the Development system because: 1. Data protection reasons. The developers and Configuration team do not need actual data. They should create their own sample data. the Project team has more access in the Development / Customising client. 2. Volume of data. If your development system has production data, it can take longer to perform the development.

Copy Users from DEV to PRD

How can I copy users created in development to production? 1. Login to the client in your DEV system from where you want to copy. 2. Execute SCC8. Select the profile sap_user. Specify the target system. Click on 'schedule as background job'. 3. Specify the background server name i.e. the server name where your DEV system is available. 4. Click on 'schedule job' button. Verify the things and click on 'continue' button. 5. You will have options to specify the start time. Specify to suit your convenience. You can see the log in SCC3. 6. Login to the destination client and execute SCC6. Specify the request number which was created during SCC8. You need to specify only one request number. Other(s) will be taken automatically. Click on 'Prepare import'. 7. Specify the target client and click on 'Import'. Log can be checked in SCC3. Additional:

Can we do a copy of sap_user from SAP version 4.6C to ECC 6.0? The answer is : NO You can find the answer in the SAP note. Note 552711 - FAQ: Client copy Point 4. Notes: Options when you do a client export / import or local client copy. SAP_UCSV Customizing, User Master Records and User Variants. SAP_UCUS Customizing and User Master Records. SAP_UONL User Without Authorization Profiles and Roles. SAP_USER User Master Records and Authorization Profiles. If you are just looking for only the user master records then you just can use SAP_UCUS.

Client Copy Using Client Export and Import

How to do client copy using client export and import? By Henry Today I am going to view about Client Copy using Client Export and Client Import procedure. Its easy and safe way than direct client copy. Client Export Steps: 1. Run SCC8 2. Select Profile for desired copy type (Usually All SAP_ALL or user master only SAP_USER. You will need direction from the requester as to the correct selection here. Use Profile -> Display Profile to display profile details.) 3. Select target System (or group) 4. De- Select Test Run (If selected) 5. Run Export - Up to 3 requests are created, depending on the data selected and available:

1. SIDKO00353" for transporting client-independent data, if you have selected this 2. SIDKT00353" for transporting client-specific data 3. SIDKX00353" for transporting client-specific texts, provided texts are available in this client 6.Monitor TP logs for errors and export files for growth Client Import Steps: 1. Create client (scc4) 2. Login to client (sap* pass) 3. Manually add O transport then X then T to TMS buffer 4. Highlight #1 and use Request -> Import to launch import tool 5. Monitor I file in OS /usr/sap/trans/tmp dir for progress info 6. After Import is complete perform post processing steps from client tool (SCC7) So, if you have 3 transport requests and the data has been exported successfully then go for an import in quality system. This would help you to refresh QA server with PRD server data and settings. Note: About client copy from PRD to QAS through export-import, is it possible to do it in office hour (while all users are still active) and do I have to lock them first? Right now I have 164 GBs of data in the database, how long does it take. I use SUSE Ent v10 as the OS, what command should I use to increase the FS just in case the space is not enough. Answer: You need un-peak hour to do client copy since this process would take most of your server resource. I didnt know how long it going to take time since it depend on your server hardware specification and your SAP config. If you are using LVM and using ext3 or reiserfs than this would be simple step. Steps when using reiserfs : #lvextend -L +size /dev/volume_group/logical_volume #resize_reiserfs -L +size /dev/volume_group/logical_volume Steps when using ext2/ext3 : #lvextend -L +size /dev/volume_group/logical_volume #resize2fs /dev/volume_group/logical_volume Just make sure you would contact your OS and hardware vendor before resizing of fs.

What is SAP BODS? Sap Business Objects Data Services is an ETL Tool. Extract, transform, load tools are software packages that facilitate the performing of ETL tasks. The old name of Data Services was Data Integrator. (BODI).

SAP R/3 How to perform Kernel Upgrade

Matrix BI Software Version Patch CRM 620 674 CRM 4.0 CRM 5.0 EP 5, EP6 CRM2007 EP 7.0 EP

BI3.1 4.7EE

BI3.5 ECC 5.0 640 BI 7.0 ECC 6.0 700

To know the current version run c:\> disp+work.exe

Or run TCODE SM51 and look for the release notes.

Goto System/Status

Hardware OS Database

32bit or 64bit Windows 2003, Linux, Solaris AIX 5.3 AIX6.1 OS390 AIX400 Oracle 8, Oracle 9i, Oracle 10G, DB2 8x, 9x, DB4 8x,9x, DB6, SQL Server 2000,2005,2008 Max Db 9.0X, 8.0X

Unicode/Non Unicode

4.7 is Non Unicode, ECC6 SR3 is Unicode, All other versions (ECC 5.0 etc) are available in Unicode and non Unicode versions

Goto service.sap.com/PAM to see the product availability matrix. It will tell you what needs to be applied to go from one version to another. Also download the kernel upgrade dump (3 files). SAPEXE.SAR SAPEXEDB.SAR DBATOOLS.SAR SAPCAR.EXE First two files are needed to patch the kernel. All three are needed to upgrade the kernel. Procedure 1. Shutdown SAP Server, stop all SAP and Oracle services 2. Copy D:\usr\sap\DEV\SYS\exe\run to D:\usr\sap\DEV\SYS\exe\run_old 3. Create D:\usr\sap\DEV\SYS\exe\run_new directory and copy all the above files into the run_new directory 4.Rename SAPCAR.EXE in run_new to OLDSAPCAR.EXE 4. Change to run_new directory and Run d:> OLDSAPCAR.EXE xvf SARFile one file at a time. Need to execute this command three times, one for each SAR file. 5. Copy/Overwrite all files except the above 4 files from run_new to run directory 6. Restart the services a.TnsListner b.Oracle<SID> c.SAP<SID>_IN#> Central Instance d.SAPOSCOL e.SAP<SID>_<IN#> Dialog Instances 7. Start SAP CI, DIs 9.If any problems arise check the instance profiles 10.Verify the installation using TCODE SICK

n the below screen you will see the SAP System Kernel information. In this screen you will see 1. Kernel information 2. Database information 3. System information.

SAP Release Information from Server. In this screen SAP Release Information SAP R/3 kernel information SAP R/3 Kernel Database Client Library

SAP How to exclude a table in client copy

If you want to exclude a table x from copying in client copy run report RSCCEXPT Goto transaction SA38 , enter the report name and execute. You will see the output screen as

Enter the table you want to exclude and save it

SAP Remote Client Copy (Transaction Code: SCC9)

The client copy sheld between two different databases or two different servers (R/3 systems) is known as Remote Client copy. Remote Client copy requires RFC Connections. Create RFCUSER with SAP_ALL and SAP_NEW profiles on source system (DR1) Run su01 and create new user RFCUSER and copy from ddic Make sure the user type is SYSTEM.

Lock all users on source Send system message to all users SM02 Wait for one hour and kill any remaining users Run SU10 to mass user lock Stop all background jobs Display all background jobs using sm37 Run BTCTRANS1 to de schedule all jobs Run BTCTRANS2 to re schedule all jobs Make sure enough space is available for TableSpaces in target Create RFC Connection from target to source (TCODE SM59) Connection type should be R3 connection Connecting two applications running on two different servers to enable the data communication is called as RFC connection. Using RFC connection the communication obtained between source and target systems with the help of gateway work process which enables data communication between them. RFC connections will be created using SM59 transaction code Types of RFC connections Connecting application server with same database Connecting with R/2 system database

Connecting with R/3 system database connecting type 3 stands for creating a connection between R/3 to R/3 technology servers. SAP R/3 to SAP R/3 SAP R/3 to SAP BIW (vice versa) SAP R/3 to SAP CRM (vice versa) SAP R/3 to SAP SRM (vice versa) If SAP R/3 to SAP R/3 connection obtained the data communication held between those two systems as per its technical and configuration Steps in creation of RFC destination Go to SM59 in target client

Create Give RFC destination Name (SIDCLNT) Connection type (3) for R/3 connection

Choose Description and Enter

 Now additional tabs will be opened Give CI host name of Source client and Instance number in the tab Technical Settings: Go to Logon/Security tab, mention source client number, give user information using which source RFC to be logged on to target then save and Test connection. User info in RFC In RFC administration, screen logon details required to be given for the source system of RFC to be logged in to the target system RFC. This user type should be system or service which ever part of target system database. Once RFC is created source to target system the data extraction can be done from target system to source system

Test

Go back and run SM59 and you will see the newly created connection.

Run Remote Client Copy (TCODE SCC9) Remote client copy will be done using SCC9 transaction code using the same steps as done in local client copy.

Only difference is for the source client, instead of giving the client number of a local client you will need to provide the RFC connection for the system containing the source client, which is defined in step 1.