Sap Basis Notes Keylabs Training 141104032535 Conversion Gate02 PDF
Sap Basis Notes Keylabs Training 141104032535 Conversion Gate02 PDF
Sap Basis Notes Keylabs Training 141104032535 Conversion Gate02 PDF
Work process
A. All the process which handles by the use task based on the type of the user
request.
B. Types of work process
1) Dialog work process
2) Background work process
3) Update work process
4) Message server
5) Enqueue server
6) Gateway
7) Spool
C. What are the different types of work process in R/3?
Dialog (D), Update (V), Enqueue (E), Background (B) and Spool(S)
rdisp\max_wp_run_timeout=600 to 1800
J. One dialog work process maximum up to 32 users are we can create
K. One application server maximum up to 100 work process are we can create
L. Work process statuses are
1) Waiting
2) Running
3) Error
4) Stopped
5) Private mode: Dedicated to the particular user
6) Sleep: Work process is running but not responding
Why: Waiting for resources
M. In sap level work process overview SM50
N. In sap level global work process overview SM66
O. In O.S level work process overview dpmon
Dpmon: when the user could not login to the sap system
P. In sap level display a list of application server SM51
Q. In sm51 transaction to identify the Release note, the R/3 kernel, D/B kernel, O.S.
Kernel and support packages information
R. In sap level version statuses are system ---> status
S. In O.S level version we can see disp+work
How to user request flow?
User request ---> dispatcher ---> work process ---> dialog work process --->
update the tables
Background jobs are programs, printing specification and interactively can be run
automatically by the background processing system
B. Background work process parameter name is rdisp\wp_no_btc=2
C. During the installation minimum of 2 background work process
One is defining and another one is executing
D. Scheduling the background job is SM36
Job name should start either z or y.
Maximum 32 characters are allowed in the name.
E. Start conditions
1) Immediate
2) Date/time
3) After job
4) After event
5) At operation mode
F. Background job steps
1) ABAP program: It is a standard program (or) customized program which
will execute by variant.
Variant: It is a program selection criterion to provide the inputs
during the runtime (or) execution of the program.
Variants are stored in the table is TVARV
We can create the variant from SE38
2) External command: It is used for pre defined input by system
administrator.
External commands are defined in SM49 (or) SM69
External commands & external program are executed by SAPXG
program
3) External program: It is used for direct command input by system
administrator
A. It is used to update the database by reading from the temporary tables. It cant
communicate with user directly
B. There are 2 types of update work process. They are v1 and v2
V1 update is used for critical jobs and V2 update is used for non critical jobs
C. We need at least one update work process per sap system and we have more than
per dispatcher
D. The update profile parameter name is rdisp\wp_no_vb, rdisp\wp_no_vb2
E. Update monitoring is SM13
Here we can check critical and non critical updates. We can specify date and time
F. Update program administration SM14
This transaction code is used for active to deactivate & deactivates to activate
update request and you configure the update servers, update groups and display &
monitoring update parameters.
G. Update temporary table is VB*
1) Vbmod update function module
2) Vbdata update data
3) Vberror update error information
4) Vbhdr update header
5) Vbwrk work list for mass processing at a time have update
H. Update status are
1) Init the status will be initial.
2) Run update is started in main database.
3) Error update is thrown into error.
4) Auto update is thrown into error due to problem in database space.
I. Update tables are stored in TBLOD
SAPMV45A: which update work process is going on?
J. Update parameters
1) rdisp\vb_stop_acive: Set to 0 so that update can be deactivated. If the
value is set to be 1 update can be activated.
2) rdisp\vbdelete: This parameter is used to delete the old update requests
based on the no. of days. It will delete default 50 days.
3) rdisp\vbmail: It is used to send an email. It update thrown an error which
can be viewed in SBWP (sap business workplace) based on your user
(set to 0 or 1).
4) rdisp\vbname : Name of the server running where update are processed
5) rdisp\vbreorg: It is used to delete the incomplete update request.
1=delete, 0=no, we can also schedule a background job RSM13002 but it
will delete the update request which are in completed it will be deleted after
restarting.
6) rdisp\vb_delete_after_execution: It is used to delete the update request
soon after the execute of the update. Set it to1 to delete the record (or)
2 to the record will not be deleted. If it is set to 1 the background job
RSM13002 is not required. If not schedule periodically daily during off
peak hours.
Spool (S)
D. Dialog work process (or) background work process are creates a spool request. i.e.
to print the documents
E. In O.S level spool request are stored in global directory usr\sap\<Sid>\sys\global
F. The storage location specific parameter name is rdisp\store_location
G. This parameter has 2 values they are global_G and database_DB.
H. G means it stored in global directory DB means it stored in database tables are
TST01 and TST03
I. The spool request is also referred as TEMSE
Temse is used for temporary sequential objects
J. Access method: It is connection to spool server to O.S spool.
Access methods are 3 types
1) Local access method: the spool process and the spool host (printer spool)
reside on the same system. Access method type L is used for UNIX O.S
and C is used for windows O.S
2) Remote access method: the spool process and the spool host reside on two
different systems. Access method type U is used for UNIX O.S and S is
used for windows O.S
3) Front end method: access method p is the printers are connected to end
users desktop do not configured to many front and printers F and G
K. We can see all the clients and users spool request T_Code is SP01
L. We can see specific client and user spool request T_Code is SP02
M. Spool administration is - SPAD
N. Default printers are SWIN, SAPWIN
A. RFC is using connect to the one sap system to another sap system.
B. Sap gate way is using of RFC
C. RFC connections are 4 types
Operation mode
Profile
Administration data
Basic maintenance
Extended maintenance
Where you can see the Profiles?
Sap level transaction code is RZ10 & RZ11
OS level usr\sap\<Sid>\sys\profile
DB level PAH1, TPFYPROFTY, TPFET, TPFHR
USERS:
During the sap installation for windows O.S default users are <Sid>adm,
sap service<Sid>.
During the sap installation for UNIX default users are <Sid>adm, sap
service<Sid>, ora<Sid>.
1) <Sid>adm: It owns the sap system and start and stop done by <Sid>adm.
2) Sap service<Sid>: It is used to start and stop the services.
Ex: [sap<Sid>_00, sap<Sid>_01..]
3) Ora<Sid>: It is used to owner to work on database
SAP GUI default users are DDIC & sap*
After installation database users are sys, system
Database schema users are: Abap level SAPSR3, java level
SAPSR3DB
Communication user is SAP JSF
Default users are: DDIC is 06071992, Sap* is 19920706
J. Default services are
a. Sap OS Col: sap OS Col collector which is used to collect the O.S
resources that are required to start the installation.
b. Ora TNS Listener: Ora TNS listener service should be started on the
specified port number is [1521 1529].
c. Oracle service<Sid>: This is required for the database.
strcpe.exe
strdbs.cmd
msgserver.exe
Disp+work.exe
igswd.exe ---------> IGS means internet graphical service
V. DB
Start C.I stop
D.I
2. The transport objects are divided into 2 types they are Export & Import
DEV QAS PRO
Export Import
Go to STMS --->overview ----> system ----> double click system (Ex: dev) ---> go
to transport tool tab ----> insert row ----> N0_IMPORT ALL = 1 this is used to
disable the fully loaded truck
31. How to create the STMS?
Login to the system with DDIC in client 000
Go to the T_Code STMS ---->configured ---->standard configured ----> single
system, development system, three system in group
(Or)
Go to the T_Code STMS ---->overview ----> systems ----> sap systems ---->
external system ----> then we have to give the system name, <Sid>
32. How to create the transport route?
Overview ---> transport route ---> change button ---> click the DEV, QAS & PRO
---> here click the add transport route tab ---> then we have to give the <Sid>,
transport layer, system name.
33. How to create the change request?
Using the transaction codes are SE01, SE09 and SE10
34. How to import the change request?
Go to STMS --->overview ---> import (or) import overview button
35. How many types of change request?
Four they are
1) Customizing request: customizing request containing client specific object
2) Workbench request: workbench request containing cross client objects &
repository objects
3) Transport of copies: transport of copies is used for more the tables for user
date. This is used for DB refresh & Client refresh
4) Relocation: relocation object is used for changing the location of object
from one system to another system
35. What are the steps for importing at command level?
<Sod>k9<5 digits>
Version of SAP
What is the difference between Net weaver and ECC (or) ERP?
Clients
To disable multiple users login within the same client implementation this
parameter in the instance profile login\disable\_multi_gui_login = 1
25. Exception login?
In case you are wondering how to allow multiple login for certain key users you
can implement parameter login\multi_login_users =
Login\system_client it is used for when the open the screen we will get this
client number whatever we set in the default profile parameter
26. How to delete the client deletion?
1) Login in the client which you want to delete
2) Using the transaction code SCC5
3) Check delete entry from T000 option & click delete in background job
button
4) Double click on server name
5) Check immediately option & click on schedule job button click on continue
button
6) Go to the transaction code SCC3 to see log analysis
7) After taking some time status become success fully completed
27. Tell the steps for a local client copy?
1) Login with sap* & password pass in newly create client
2) Using the transaction code is SCCL
3) Target is displayed
4) Select the profile which you want to you copy
5) Selected source client
6) Select on start immediately button (or) schedule as background job
7) Click on continue button to continue the client copy
28. Tell the steps for remote client copy?
1) Using the transaction code in target client
2) Target client is displayed
Support packages
A. Patches: To fix the bugs, to get the functional enhancement and To upgrade the
system to next level
WWW.KEYLABSTRAINING.COM USA: 908-366-7933 India: +91-9550645679 37
SAP BASIS Notes by Keylabs Training
J. With solution manager can I apply support packages in C.I & D.I?
Yes, I can
How?
We can install the C.I & D.I on the host and on the same <Sid> can apply support
packages.
K. Usr\sap\trans\eps\in:
This directory stores uncar patches which are download from the service market
place
L. Table TPFET is used for store the parameter values along with patches
Kernel patch latest number: 156/291
Support package highest level: 26
Patch: Group of NOTES is called patches
Packages: Group of patches is called packages
Stacks: Group of packages is called stacks
M. How to uncar .car/.sar files in UNIX single shot?
# $for I in *, SAR: do SAPCAR XVF $I: done
We cant able to see uncar files in EPS directory then what will you do?
May be file corrupted
Sap car may old version
N. Can you apply the support packages in Java system?
Yes, through SDM and JSPM
O. Why we required 2 background work process in support packages?
Support package is the time taking process in this process due to some problems.
If one job is failed another one job is take the backup.
The Support Package Manager runs through a series of phases when it imports
Support Packages. If you want to know which phases were performed for which
scenario (test scenario or standard scenario), execute program RSSPAM10.
The following list provides an overview of all the modules and phases and list
them in the order in which they are executed by the Support Package Manager:
Module: Preparation
1. PROLOGUE
This phase checks if you are authorized to import Support Packages.
2. CHECK_REQUIREMENTS
This phase checks various prerequisites for importing Support Packages such as
the tp logon to your system.
3. DISASSEMBLE
This phase disassembles, or unpacks, the data files from the relevant EPS parcels
and copies them to the transport directory.
4. ADD_TO_BUFFER
This phase copies the queue to the transport buffer of your system.
5. MODIFY_BUFFER
In this phase, the transport buffer is prepared for correct processing of the
following import phases.
6. IMPORT_OBJECT_LIST
This phase imports the object lists of the Support Packages in the queue into the
system.
7. TEST_IMPORT
This phase performs a test import for the current queue using tp. It checks if there
are objects that are in open repairs and will be overwritten during the import, or if
any other circumstances are preventing an object from being imported
successfully.
8. OBJECTS_LOCKED_?
This phase checks if there are objects that will be overwritten by the Support
Package, and that are still in requests that have not yet been released.
9. ADDON_CONFLICTS_?
This phase checks if there are conflicts between the objects in the queue and the
installed add-ons.
10. SCHEDULE_RDDIMPDP
This phase schedules the transport daemon (program RDDIMPDP).
Module Import 1
11. CREATE_VERS_BEFORE
This phase generates versions of the objects in the Support Packages that are in the
queue.
12. SPDD_SPAU_CHECK
This phase checks if a modification adjustment is necessary (Transactions
SPDD/SPAU).
13. DDIC_IMPORT
This phase imports all ABAP Dictionary objects in the queue.
14. AUTO_MOD_SPDD
This phase checks if modifications to ABAP Dictionary objects can be adjusted
automatically.
15. RUN_SPDD_?
This phase prompts you to adjust your modifications to ABAP Dictionary objects
with Transaction SPDD.
16. LOCK_EU (For Import Mode Downtime-Minimized Only)
This phase locks the development environment.
17. INACTIVE_IMPORT (For Import Mode Downtime-Minimized Only)
This phase imports program code and program texts in an inactive state.
18. DDIC_ACTIVATION
This phase activates the imported Data Dictionary objects.
19. IMPORT_PROPER
This phase imports all Repository objects and table entries, provided they have not
already been imported during the phase INACTIVE_IMPORT. This is preceded
by actions such as table conversion and activation of the name tabs.
20. PREPARE_XPRA
This phase prepares the XPRAs and after-import methods to be executed.
21. UNLOCK_EU (For Import Mode Downtime-Minimized Only)
This phase unlocks the development environment.
22. AUTO_MOD_SPAU
This phase checks whether modifications can be adjusted automatically.
23. XPRA_EXECUTION
This step executes the XPRAs and the post-import methods.
24. ABAP_GENERATION
This phase generates runtime objects for the imported Repository objects (ABAP
source texts and screens).
25. RUN_SPAU_?
This phase prompts you to adjust your modifications to Repository objects with
transaction SPAU.
26. CLEAR_OLD_REPORTS (For Import Mode Downtime-Minimized Only)
This phase deletes obsolete versions of the program code and program texts in the
database.
27. EPILOGUE
This phase completes the import of the Support Package. It also checks if the
queue was processed completely.
A. More than one instance we can configured the in that time we can use logon load
balancing
B. Decreasing the load balancing on the C.I
C. Effective utilization of buffers
11. Table space issues (or) space issues at O.S level [then increase the table space
issues (or) increase O.S level spaces]
12. Dispatcher is not coming up in that time we have to check the listener
Cmd: lsnctl (enter)
Listener :> status (to check whether it is started or not
Listener :> start [to start the listener]
Listeners :> stop [to stop the listener]
13. If system is not coming up then change in instance profile that is rdisp\trace = 0,
1,2,3,4 then start sap again it will writes the logs into work directory (after starting
sap system we need to change the trace level = 0)
[Trace = 0 no trace is written to files]
[Trace =1 write error messages in the trace file]
[Trace = 2 write the full trace]
[Trace = 3 write the full trace including data blocks]
Performance
NOTE: OScol brings the OS information into ST06. If OS call not stared
ST06 will be blank
We can check top CPU utilization for the current last 24 hours
7. ST07 application monitoring
Here we can see how many users are log, number of servers, clients & work
process
it is used to identify whether the system is optimally designed or not, this is
also used to identify the buffer utilization & response TIME
8. ST11 it is used to display the developer traces of work directory
\usr\sap\<Sid>\sys\work
How to delete the statistics of file R/3?
Sometimes deleted manually
Using ST03 or ST03N
OS level: DVEBMGS/data file
2. User administration
By using this we can create the portal users assign the portal roles to
particular users and export import of the roles, users
3. System administration
By using this we can configure the SSO and key store administration &
UWL [universal work list configuration]
I. How to start the java system?
Start
DB, SCS, C.I, D.I
Stop
J. Work process overview JCMON
Config tool
A. To logon the config tool database should be up but their java is not mandatory
B. Without user ID & password we can log in the config tool
C. If you change this config tool then we can restart the sap system
1. Ume.saperadmin.active
Ume.superadmin.password
2. Ume.logon.logon_help
Key store --->default log on tickets)
1) In the config tool we can updated the LDAP Data server information if we
are using active directory for the user connection
LDAP ---> LIGHT WEIHT DATA ACCESS PROTOCOL
2) To fetched the data from active servers using LDAP Data
3) Services:
1. Licensing service
2. Locking service
3. Log viewer service
4. Log configure service
5. JCO RFC service
6. Security service
7. SLD service
8. SSL service
4) Manager:
1. Configuration manager: it process the configuration data from
relationship of database
2. Cluster manager: it manage the communication b/w J2EE engine
cluster elements
3. Service manager: it provides runtime elements of the J2EE engine
4. Thread manager:
5. Port manager: it manages the process of pooling java object.
6. Long manager: it manages process of logging system
5. System
K. Key store services: these are the services we can to create the sap logon tickets.
These log on tickets used for authorization and security for java system.
5)Make sure that Binary is selected as the File format. Click on green
check mark.
6)Click on Add to Certificate List button, Notice that the Portal Certificate
is now added to the list of certificates.
7)Click on Add to ACL button. When prompted, fill in the WPS System
with the SID of Portal and WPS Client to 002.
8)Login to portal click on system administrator ---> system configuration --
->portal content->ERP folder-> System right click on connection test
DATABASE
This is also called read in consistency error. This is called snapshot too old create some
more roll back segments to avoid this error.
Error codes:
DB calendar (DB14)
Login as <Sid>adm
#r3trance d
Should returns you 0000 return codes if it is 0012, then look for trans/log file for detail
error.
BRTOOLS
BRCONNECT:
It is used to connect the database and perform the various administrative tasks
# Brconnect f check: to check the database and writes the logs into sap check directory
# brconnect f stats: it is used to run the database statistics. It identifies the tables whose
statistics are out based and update them.
# Brconnect f cleanup: it is used to clean the old log files from sap trace & sap check
directory
Db optimizer: all the tables & indexes will be stored known as a DB optimizer
Br backup: it is used to take the take the backup of the database. These are 2 types
Offline backup: the database is down during backup & no transaction is allowed
Online backup: the database is up & running without effecting the user transaction
Complete backup: take the full backup of system without catalog information
Incremental: for incremental backup, first take the full backup system [Ex: 1 2 3 4,
add the 5 6 then incremental]
Parameters:
Backup_mode = all
Br archive: it is used to backup the offline redo log file to tape (or) disk from ora arch
directory to tape (or) disk
---> when online redo logs are full then ora arch writes contents to ora arch (offline redo
logs) the content of ora arch is reference of off line redo logs
There is a mediator is called DB client with the help of DB client. It becomes as database
independent
WWW.KEYLABSTRAINING.COM USA: 908-366-7933 India: +91-9550645679 59
SAP BASIS Notes by Keylabs Training
Database client is used to convert the open SQL statement into native SQL statement and
vice versa
LISTNER will provide the connectivity between the sap system and database during
startup of sap system
During the starting of sap system LISTNER will create shadow process in the ratio of 1:1
to connect to database
LISTNER: create the shadow process which are going to connect the database table
SAPUSER by using ops$ mechanism
Ops$ mechanism contain the one table in database, that table is SAPUSER this table
contains schema owner name & password. Shadow work process get the scheme owner
name & pass word, disconnect (choose connection database) the database.
Shadow process again connects to database by using schema owner name & password.
The user who is authorized at o.s level is automatically authenticared at Database level.
That means no user ID & password is required to login to Database
OS_authent_prefix = ops$
Remote_OS_authent = true
Which performing the client copy PSAPUNDO table space will be increase
NOTE: If there is no space in space in PSAPUNDO table space SNAPSHOT too old
dump is thrown into ST22 then we need to lock after the PSAPUNDO table space
DATABASE:
What is database?
Advantages:
Consistency
Availability
Reliability
Uniqueness
Redundancy
Indexing
BRBACKUP: Backup of data files, control files and online redo log files
BRRESTORE: Restore the data files, control files, online redo log files & offline redo
log files
Symbol:
- : control choice list you can choose (or) execute this now
No: not used skips the following actions to narmal program steps;it is recorded is
IR06761 in the detail log
=: control choose list this is the initial default choice with yellow background
#: control I/P you cant 1. Execute this action 2. Change this parameter
Option 4 choice
If Lot of achieve Logs are getting generated in minutes then what will do?
Re org jobs: table contains the information of the standard background jobs
Oracle listener: it is used to connecting the R/3 work process and shadow process
Tnsnames.ora
SQLnet.ora
Listener.ora
Restore from the database backup recover from the redo log files, alter database backup
from control file to trace
Brconnect f check
Brconnect f status
Brconnect f next
Brconnect f cleanup
# SQL :> delete from sapar3.usr02 where bname = sap* and mandt = client number
Roll in: the process of copying the user related information in to work process handler
The work process continues to process the user request and response back to the user
Roll out: the process of copying the user related information into user context
SAP USER: sap user is the table which contains database scheme user ID & password
The user complaints that he could not log into the system in our glass mode?
Archive struck
The user could not update any record and result in our glass mode
For every 100 request the 2 request goes to database and remaining should be form the
buffers
R/3 buffers: [memory accessible for all users] programs, table and field definition,
customizing tables.
User context: [memory attached individual users] variables, lists, internal tables,
administration data (authorizations)
Local memory: local memory is associated with individual work process, local memory
is executables, data, stack, buffer for data transfer, local roll area, local paging area.
Shared memory: shared memory is associated with all the process of one instance R/3
buffer contains global objects for all users and work process such as programs and
customizing tables.
Heap memory: it contains user context, when extended memory is full. It is called and
released on demand.
WWW.KEYLABSTRAINING.COM USA: 908-366-7933 India: +91-9550645679 65
SAP BASIS Notes by Keylabs Training
Buffers, extended memory, heap memory, roll memory, R/3 paging memory, local work
process memory.
Roll area: user context data is store of that is an authorization, set/get parameters, internal
tables and report lists.
Paging area: which stores application program data that corresponding to specific Abap
commands?
Parameters:
Ztta/roll_first define first port of the roll area set to 1.17kb to 4.6
Abap/heap_area_dia limit for the amount of local memory allocated to dialog work
process
Abap/heaplimits maximum heap limit if it is reached the work process is flogged for
restart
Heap memory is released after use. After ending the transaction the heap memory is
automatically released and the work process restarted to release the swap memory.
Oracle startup options: startup no mounts: oracle is not operational and oracle
background process is not started. It will used to create the control file.
Startup mount: oracle is not open and not operational. Oracle background process is
started. SGA is created [SGA means shared global area]
Abort
Immediate
Transactional
Normal
Abort: here we forcefully shutdown the database without intimating any users. The total
cache information in the lost and SMON can recover the information from online redo
log files whenever system is restarts
Immediate: the committed transactions are updated in to the database. the database open
transactions are rolled back
Normal: no connections are allowed exist user can perform transaction till complete the
task
Oracle sid sap trace background trace alter_<Sid>.trace [it contain all profile in
formation about oracle]
Oravle sid orig log A [online redo log files & control files]
Oravle sid orig log B [online redo log files & control files]
Control file: it contains the oracle structure. It is a binary file. It can be updated only
oracle. We cant edit manually.
If lot of achieve logs are getting generated in minutes then what do we do?
Table space utilization, space critical objects and table space growth
Go to DB02, click on space critical objects, then note down the objects, go to SAPDBA,
go to reorganization (option d), then use option b ---> show extent ---> resize the extent
(take the recommended value)
Go to oracle/<Sid>/sap backup
# Tail back<Sid>.log
DB calendar (DB13)
Init<Sid>.sap
We do daily on line backup on all servers and weekly offline backup on DEV and Quality
system
Why mapping?
The user IDs are particular system & back end system are different then we need to
perform the user mapping
DB02: this transaction is used for checking the database table space
Psapsr3700
Paspsr3usr
Psapremp
Psapsr3db
Data base log & BRTOOLS logs transaction code is DB14 & DB24
Init<Sid>.ora
Init<Sid>.sap
P file is the static file, it is a test file and we can edit manually by using notepad.
Sp file is server parameter file. It is a binary file and we cant edit the manually. It can
modified with the ALTER SYSTEM SET command
Log_archive_start = true ---> indicates to automatically start the archive process when
the database is start
Shared_pool_size ---> specifies in bytes the amount of space that SGA reserved to cashed
& SQL start
To test the object or changes which are made to system like production environment. We
need to restore the production data to QAS data.
What are homogeneous system copy & heterogeneous system copy and how you will do
that?
A system copy without a change in the database type and the OS is called a homogeneous
system copy.
A system copy with a change in the database type and the operating system is called a
heterogeneous system copy
What is db refresh?
It is the process of refreshing the data of one system by another system [OS, DB & R3]
remains the same but only database is refreshed
Create the transport of copies by using SE01 and specify the following tables are USR01,
USR02, RFCDES and TBDLS. Then we need to release the transport of copies.
Take the screen shots of SM59, BD54, DB13, SM37, AL11, SMLG, RZ12, RZ04, SCC4
& SPAM
And then we need to delete all the datafiles related to QAS system. Data1, Data2 ---- ext
first we need to stop the oracle services, the structure should remain same
Mirrorloga
Mirror log b
Orig log a
Orig log b
Copy the sap back up folder from PRD, along with the control.sql file pasted on the desk
top to QAS (\oracle\QAS\sap backup)
Open the .afd/.and backup file (ex: bdjvujux.afd) present in sap directory. Replace the
PRD with the QAS and save it
Start ---> run ---> cmd goes to the location \oracle\QAS\sap backup and type
Check the present of the paths for the creation of the control file oracle
\Oracle\Qas\sapdata1\cntrl
Oracle<Qas102>SQL* plus
Oracle<Qas102>TNSLISTNER
Login to SQL from the location where the control SQL file is located.
Click start ---> run ---> type ---> BRTOOLS and click ok
1. Instance management
2. Space management
3. Segment management
7. Database statistics
8. Additional functions
9. Exit program
Database backup
Archivelog backup
database copy
Database copy
The above window denotes that the backup has stored and being saved in the location
D:\oracle\PRD\sap back up
If shows down the database instance as we are taking on offline backup (then backup has
been completed success fully)
Exit from the BRTOOLS by selecting option S and then select the option y
Click start ---> run ---> type ---> sqlplus as sysdba and click ok
SQL: > alter database backup control file to trace; [then database alerted]
You can find the trace file in the following location d:\oracle\<Sid> (PRD)\sap
trace\user trace [then check the latest file that is generated]
Copy that file and paste it onto the desktop and rename it with control.sql
Remove the lines present above startupnomount and below charactersetutfs and save
the file
STATUS
MOUNTED
STATUS
OPEN
USER NAME
You can view the PRD op$ users in the above screen
USERNAME:
User dropped
User dropped
Below screen displays the list of users available after dropping PRD users
USERNAME:
Provide permissions to the following QAS users as mentioned in the bellow screen
STATUS
OPEN
Install the license for QAS system and remove the PRD system license
Sap license show (display the license of both QAS and PRD system)
SICK
SEO6 and select database copy or database migration option click perform post
installation action ---> yes ---> accept the source system ---> yes accept --->\yes ---> yes
---> yes
Note: here we are considering the system as (NAG) domain controller. If it is a child
system, including that system in to the domain controller as per bellow screen that system
in to domain controller as bellow per screen
Profile ---> delete ---> all versions ---> of a profile ---> click yes ---> no ---> click on
continue ---> similarly delete start profile & delete profile as shown screen
After deleting all profile of the PRD system then import profile of NAG system by using
bellow path go to utilities ---> import profile ---> of active servers
Standard installation
In one client all the users are locked. How you can login the particular client?
Listener path:
Oracle\<Sid>\instancenumber>\<NETWORK\ADMIN\listner.ora
startup pf = d:\oracle\dev\102\database\initdev.ora
Using the SQL: > create sp file from p file; [then file is created]
Using the SQL: > create p file from sp file; [then file is created]
In BRTOOLS
Go to BRTOOLS --> option 2 --> option 1 --> option 3 --> PASPSR3 --> c --> c
DBREFRESH:
Intermediate buffers: Frequently accessed content to reduce the load on the data base
server
Where you have to check the java software status and java version?
# Java c
# Java version
Interview question
A: 400 users
A: Four Servers
5) How can you confirm the patch level for SAP GUI?
A: Log in to sap GUI, and hit alt f12 -> about patch level information.
A:Instance where message server and enqueue server is present that is called central
instance
Which doesnt contain message server and enqueue server that is called dialog instance
A: SAPJSF
A: DIAG Protocol
A: Windows 2003
These 3 are used to administrative users massively [deletion, modification and creation
whatever]
A: Using PFGH transaction code ---> enter a role ---> change ---> go to user tab ---> past
the users ---> click on comparison ---> complete comparison ---> save the role.
Sap*: sap* does not contain any user master records. It will be adjusted at kernel level. If
you delete sap* then it will be automatically with password PASS
DDIC: DDIC is the data dictionary in charge it will contains the all authorization &
profiles
The system logs of SAP application at OS level can be checked at sap MMC ---> sap
system ---> <Sid> ---> sys log
ST22 SM21
Illegal time
<Project name>ECCSAPC.I
Unicode means it will support for all the languages and code pages
Non fUnicode it will not supported the all the language except English & germen
Typical: typical is nothing but the system will take automatically the installation drivers
Custom: Custom is nothing but it will ask for the installation drovers
we dont install ECC system and net weaver is one system. If any problems accurse
we have to restart the system. At that time along net weaver system and ECC system will
also turn of then business will lose
Software component is which including the all applications is called software component
---> Before going to the sap installation, first install operating system and database
---> Hard ware sizing based on the end users using QUICK SIZE TOOL
A: The sap basis consultant should decided the hard ware capacity on the end users this
concept is Known as Sizing. It will done by quick size tool
Single GUI to access all the sap application [ERP, CRM, SCM, XI, PI, BI & SRM]
Instance type:
Central instance
Dialog instance
Database instance
Installation logs:
---> create local groups and global groups and assigns them to users
I) System logs at OS level ---> MMC ---> SAP system ---> <Sid> ---> sys log
UNIX command:
Cat <filename> ---> to open the file & read the files
Ri <file name> ---> if you want modify any file it is use full
Su <filename> <target location> ---> to move the other directory or rename the file
UNIX commands:
ST06 OS Monitor:
1- Click on 'Detailed Analysis menu'
2- Click on 'CPU' in 'Previous Hours' Group
3- Check if at any past hours is > %80
4- Notify Team if there is any such case
The Following are the transaction codes used for the System Monitoring:
SM12:
This Traction is used for Check for Lock Entries. There may be old locks still in place from
transactions that did not release, or from when the user was cut off from the Network. If any lock
entries are exist then we have to check since how long this lock existing. If, this lock existing
from more than one day then we should check that particular User is available or not (By using
the Transaction Code AL08). If he is not available then delete that lock. Otherwise we should
wait 1 or 2 Days.
SM13:
This Transaction is used for Check for any Errors in Update Records. A failed or Update
Terminate is an update to the failed database. These failed Updates occur when a user entry or
transaction is not entered or Updated in database. And we should check Whether Update is
ACTIVE or not. And also we should check any Update Records are terminated.
SM21:
This Transaction is used to check System Logs. After hitting the traction we should go to System
log--> Choose All Remote System logs, and set Date and time to before the Last log review. And
we should check whether any Errors, Warnings, Security Messages, Database, Abends, Any
other different Events are there. The log is important because unexpected or unknown warnings
and errors could indicate a serious problem.
SM51:
This Transaction is used to check that all Application Servers are UP. And also this transaction is
a central transaction from which you can select the instance to be monitor.
SM50:
This Transaction is used to check Work Process Overview and for Systems with out Servers.
Here all work processes with a Running or Waiting State. If Batch Jobs are not running, if
all the work processes are in use, this transaction provides a hint of this problem.
ST01:
This Transaction is used for System Trace. By this transaction we can trace that what are the
operations performed on particular file by particular user on which dates.
ST02:
This transaction is used for Buffer tuning or Buffer Statistics. And it is used to tune Buffer
parameters of R/3. The Buffer is important because significant buffer swapping reduces
performance. Look under Swaps for Red Entries. Regularly check these entries to establish
trends and get a feel of the Buffer behavior. And in this transaction we should Maintain Hit
Ratio is in between 90 100% for all , and Heap Memory allocated should be 0 , and
Swaps is 0.
ST03:
This Transaction is used to Check Work Load Analysis of. Workload Analysis is used to
determine System performance. Check Statistics and Record Trends to get a feel for the
Systems Behavior and Performance. Understanding the System when it is running well helps us
to determine what changes may need to be made when it is not.
ST04:
This Transaction is used for Database Performance Analysis. This transaction provides the
ability to Monitor the Database in related to 1) In Shared Pool SQL Area Get Ratio should be
90 95% 2) In Log Buffer Allocation Retries / Entries <1% 3) In Data Buffer Quality should
be in 90 95% 4) In Sorts Disk / Memory <1% 5) In Table Scan & Fetches Long Table Scans
should maintain as minimum as possible. And we should check Detailed Analysis then we
should hit Detailed Analysis menu Button in this screen. In that we can check Database
Overview like Exclusive Lock Waits , Wait Events, Buffer Busy Waits, File System
Request, Database Message logs, SQL Requests, Summery Report for all activities, etc
ST22 :
This Transaction is used to Analyses ABAP Dumps or Short Dumps. This transaction is also
used for Analyses and Determine why the errors occurred and take corrective action. It looks for
an excessive number of dumps, and also dumps of an unusual nature. A ABAP dump is
generated when a report or transaction terminates as a result of a serious error. The system
records in the System Log (SM21) and writes a snapshot of the program terminate to a special
table.
DB02:
This transaction is used to check all table Spaces and Indexes. Here we should check table spaces
sizes. If any table used space is =>99 then we should increase add the space for particular table
space. And this transaction is provides a way to examine database allocation. And this
transaction is allows us to monitor items such as: a) DB Space History b) DB Analysis By this
transaction we can view Database history by Dates and Times.
DB12:
This Transaction is used to check database Backups. And in this we should we see successful
Backups and Unsuccessful Backups list
AL08:
This transaction is used to check the users on the System. This transaction displays User Ids and
Terminal Names who are currently logged on the system.
SM37:
This transaction is used for Monitoring Background Jobs. Background is batch jobs scheduled to
run at specific time during the day. Here we should check for cancelled jobs. Here If we want to
check particular job then, we should enter the Job Name and enter User name in User name field
or * and hit execute Button. And verify that all critical jobs are successful.
2. Check the status for all work processes. 2. For dialog work process in PRIV mode for
There should not be lot of dialog work more than 12 hrs contact the user and take
processes in PRIV mode. confirmation and kill the sessions.
SM50 Check for the long running work process If you find any anomalies, Contact the user and
check whether we can kill the process. Once
user gives the confirmation, kill the WP without
core.
SM51 1. Check if all application servers are 1. If you find problems in logging to application
running. Double click on each application
servers, login to OS level of the app server and
server and check whether you are able to
login check the wps using dpmon.
SM21 1. Check for Database errors, Oracle error, 1. Analyses & take appropriate action
System Errors etc.
2. Refer to "Sys log Codes" Sheet for
errors
Note: Please check the system log starting
from yesterday 00:00:00 till Current time.
This should help to see the errors which
occurred yesterday
SM12 1. Check for old lock entries (Generally 1 1. Check if there is any active job running for
day old) that user using SM66. If not then write email to
user and take the confirmation for clearing old
lock entries after confirmation from user.
2. Note down the actual utile value. This value
should be <= 80% of
SM13 1. Check for " Update is active " 1. Note down the number of V1 and V2 update
2. Check for Update failures. failures
ST02 1. Ensure Hit ratio for each buffer is more 1) Note down the buffer and value if hit ratio is
than 95 %. <95%
2. Sometimes if hit ratio is below 95 % & 2) No action to be taken if sometimes hit ratio is
no Swaps you can ignore it. <95%,
3. Ensure extended memory should not
cross more than 80% use.
4. Please check the following thresholds
for SWAPS for individual
ST03N 1. Check and note the following 1. Note down the values for all application
parameters. servers (yesterday's value) and analyze. If the
Explorer http://s49cam.corp.wrgrace.com:51600/nwa
Monitoring -> Java System reports
Database Checks
1 Run/Review Database Check job via BR Run the database check job. This will highlight
tools any errors that have turned up in the oracle
alert logs, table space problems, statistics etc.
Logon as oraepp user to the DB server
Run brtools
6 - Check and verification, continue
1 = Database system check,
2 Check Database backup and Redo log Check the status of the BR backups/ BR
backups via BR tools Connect and view the log if required.
Logon as oraepp user to the DB server
Run brtools
8 - Additional functions
1 = Show profiles and logs
Select either
3 - BRBACKUP logs
4 - BRARCHIVE logs
Check Table space Free space via Br tools Check the free space left in the table spaces:
Logon as oraepp user to the DB server
Run Br tools
2 - Space management
7 - Additional space functions
1 = Show table spaces
Continue
Continue