Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd
Upload
186 views

Sap On db2 Commands: S.no Command Description

The document lists various commands and transactions used to check the status and performance of SAP systems running on Oracle and DB2 databases. Some key commands include db2cmd to open a DB2 command line, db2level to check the DB2 version, db2start and db2stop to start and stop the DB2 instance, and brbackup and brrestore for backups using BRtools. Important transactions listed are SM66 to check long running jobs, SM50 for long running work processes, SM51 to check application server status, and SM21 to check database errors in the system log.

Uploaded by

Raghavendhar Reddy
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
186 views

Sap On db2 Commands: S.no Command Description

The document lists various commands and transactions used to check the status and performance of SAP systems running on Oracle and DB2 databases. Some key commands include db2cmd to open a DB2 command line, db2level to check the DB2 version, db2start and db2stop to start and stop the DB2 instance, and brbackup and brrestore for backups using BRtools. Important transactions listed are SM66 to check long running jobs, SM50 for long running work processes, SM51 to check application server status, and SM21 to check database errors in the system log.

Uploaded by

Raghavendhar Reddy
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Sap on db2 commands

s.no Command Description


1 Db2cmd To open a db2 command line
2 Db2level To know the current version
3 Db2start To start the db2 instance
4 Db2stop To stop the db2 instance
5 Db2admin stop Stops db2 admin server instance
6 Db2admin start Starts db2 admin server instance
7 Db2 list applications Shows current applications
8 Db2 list directory Shows available directories
9 Db2 connect to <dbname> Connects to db ( dbname)
10 Db2 connect reset Close the db connection held by that
user
11 Db2 upsadte db cfg for To update db parameter with new
<dbname>using<param><new value
string>
12 Db2 backup db <dbname> to Db backup command dbname is
<bkup dir> db2sid
13 Db2 backup db <dbname>use Offline backup using tivoli tool,first
tsm stop sap and then start db<db2start>
14 Db2 backup db Online backup using tsm
<dbname>online use tsm
15 Db2 list history backup List history for backups
16 Db2 restore db <db2sid> from This put the db in rollforward state
taken at<timestamp>
17 Db2 backup db <sid>online to Db backup to specific path
<path>
18 Restore db <sid>from<bacup Restore to backup dir
Dir>
19 Db2 connect to Connect to database
<sid>user<myuser>using<myp
ass>
20 Db2 list utilities show details See backup progress

Sap on oracle commands

oracle Login with sidadm or orasid


1 Stop sap To stop sap and db
2 Start sap To satrt sap and db
3 Stop sapr3 Stop only r3 system
4 Start sapr3 Start only r3 system
sql>startup nomount Oracle instance started
Sql>alter database mount Database altered
Sql>alter database open Database altered

brtools
login as orasid
brtools or brconnect to connect to brtools

Brbackup –m full –b <file name> m is mode (online,offline,full,whole,incrimental) type is t (online


offline)
Brrestore –m full –b <file name>

Db check
1 Run/Review Database Check job via Run brtools
BR tools 1 = Database system check,
2 Check Database backup and Redo Check the status of the BR backups/ BR Connect and view
log backups via BR tools the log if required.
Logon as orasid user to the DB server
Run brtools
8 - Additional functions
1 = Show profiles and logs
Select either
3 - BRBACKUP logs
4 - BRARCHIVE logs

3 Check Table space Free space via Br Check the free space left in the table spaces:
tools Logon as orasid user to the DB server
Run Br tools
2 - Space management
7 - Additional space functions
1 = Show table spaces
Continue
Continue

T_Code Description
SM66 1. Check Long running job. (Job running
for more than 12 hours
2. Check the status for all work processes.
SM50 Check for the long running work process
SM51 1. Check if all application servers are
running. Double click on each application
server and check whether you are able to
login
SM21 1. Check for Database errors, Oracle error,
System Errors etc.
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
day old)
SM13 1. Check for " Update is active "
2. Check for Update failures.
ST02 1. Ensure Hit ratio for each buffer is more
than 95 %.
3. Ensure extended memory should not
cross more than 80% use.
ST03N 1. Check and note the following
parameters.
Dia. Response time
DB Response Time
ST06 Check for following utilization in all
instances
1. CPU Utilization. Ideally 60 % should be
free.
ST22 1. Check for the dump which is appearing
more than 20 times
2. Check for dumps appearing more than
100 times.
ST04 Check following settings for all instances
1. Check for Data Buffer quality. It should
be above 95 %.
2. Check for DD Cache quality . It should
be above 97 %.
3. Check for Read/User Calls. It should be
below 30.
DB01 1. Oracle Lock Monitor. There should not
be any entry
DB02 1.Check the free size of the tablespace

DB12 1. Check the Last successful backup


2.Archive directory status(Free space).
SM37 1. Check long running active jobs(Check
for last one week)
2. Check for repetitive cancelled jobs
3. Check if standard house keeping jobs
are running
AL08 1. Use this transaction if you want to find
out user across the application servers

You might also like