question & answers

1.What is the difference between System Trace, Developer Trace and System Log?
Ans: ST01 - System Trace which will be required when you want to record trace for system
        ST05- Performance Trace (Developer Trace) which is required when any user complaning for a long transaction and you want to record all activity of Transcation.
        SM21- System log is for the recent logs for your CI and application server. What ever happen in SAP it will write a system log.

2. what is the process of kernel upgrade in sap ?
Ans:  Kernel Upgrade Process having following simple steps.

        1.Checks to be done before kernel upgrade
        2.Download the latest kernel patch from SMP
        3.Stop the Application Server and the SAP OS Collector
        4.Take Backup of the present Kernel directory
        5.Copy the new kernel files to the RUN folder location
        6.Check the permissions of the files in the kernel directory
        7.Start the Application server and the SAP OS Collector

Kernel Upgrade Process

Step 1) Checks to be done before kernel upgrade
a) Find the current version of the  kernel
         ==> execute the command disp+work -v to get the present kernel version
         ==> use the R/3 SYSTEM->STATUS to get the present kernel level
b) Note the Compilation mode from disp+work -v (here UNICODE)
c) The Operating system BIT length.
     ==>This can be found using "winmsd" (in windows) and "isainfo -v" or "uname -a" on unix servers.
             Also "tp -v" will give the OS bit length.

Step 2) Download the latest kernel patch from SMP

http://service.sap.com/swdc 

 --->Support Packages and Patches --->SAP NetWeaver ---> SAP NETWEAVER---> SAP NETWEAVER 7.0 (2004S) ---> Entry by Component---> Application Server Java--->SAP Kernel 7.00 32 bit UNICODE
There are 2 files to be downloaded from SMP:

a) Database Independent Files
This is of the nomenclature SAPEXE_<Patch level>-<release date>.SAR

b) Database Dependent files
This is of the nomenclature SAPEXEDB_<Patch level>-<release date>.SAR

Step 3) Uncar the .SAR files
Uncar the files using the SAPCAR utility and store it in a directory. Use the command:
SAPCAR -xvf <filename.SAR>

Step 4) Stop the Application Server and the SAP OS Collector

               In windows, stop the SAPOSCOL service (Start-> run-> services.msc)
               In Unix servers, use the command:   saposcol –k

Step 5) Take Backup of the present Kernel directory 

==> Copy the present kernel folder safely. This is important because the activity is completely reversible and 

switching over to the old kernel will be possible. 

Step 6) Copy the new kernel files to the RUN folder location 

 ==>Copy the files in such a manner that the RUN folder is overwritten by the new files. 

Step 7) Check the permissions of the files in the kernel directory 

The Database independent files such as "brtools", "brbackup", "R3load" etc. will usually have <DB>SID as 

the owner. In such cases, the owner of the files needs to be changed using the "CHOWN" command to the 

appropriate user. 

                      chown [-R] newowner filenames 

                      chmod <1>permissions filename 

Step 8) Start the Application server and the SAP OS Collector 

Now the kernel patching activity is complete. 

In windows, start the SAPOSCOL service (Start-> run-> services.msc) 

In Unix servers, use the command:  saposcol –l 

Step 9) Check the latest Kernel level 

==> Execute the command disp+work -v to get the new kernel level 

==> Also run the command R3Trans -d to check if database connection too is fine.

==> use the R/3 SYSTEM->STATUS to get the updated kernel level

How to identify long running background jobs

1) First of all identify the job that is long running and identify details like job class, workprocess that is executing the job

2) Click on the job to view the display job screen. In the screen, click on job log to understand what is being performed by the job currently. This may give details like job is currently extracting some data packages or processing data packages etc

3) Identify the executing server and process id of the job from the step 1 and goto transaction SM50 of the respective executing server to view more details about the background job running.

Figure out the status of the job like On Hold or running from the process overview. If the job is On Hold, find out the reason for On Hold by examing the "Reason" column of SM50 transaction. Reason for On Hold could be due to CPIC/RFC/DEBUG/ENQ/PRIV/UPD etc.

Double click on the reason column for detailed information on the same and troubleshoot accordingly. If reason is RFC, check out which RFC it is referring to and cross check whether destination system is up or not and any other problems with that system.
If it is ENQ, check out any lock issues like lock overflow etc
If it is PRIV, check out for memory bottlenecks
If it is UPD, check out whether any update issues
If it is CPIC, check out for any network , gateway, message server and other communication problems

4) After performing step3, if you figure out job is not on Hold and it is in running state, then examine report column to identify what report/program is being executed by the job. Once you got the report/program details, figure whether it sap program or custom program and take actions accordingly.

5) Also examine Action and table columns in SM50 transaction of respective executing server to identify what is the action( roll in/roll out /Sequential read/Physical read/insert/update/delete etc) being carried out by the job currently and what is the table on which action is being carried out.

If it is sequential read, figure out the cost of that sequential etc and consider for indexing etc. If it is physical read, check out whether there are too many swaps and consider resizing buffers accordingly. If you observed delay is due to high roll in/roll out, identify reasons for the same and tune buffer/memory parameters accordingly.

6) Once you get the table details on which action is being carried out, figure out

How many records are existing in the table ?
Is this taking long time due to volume of records ?
Are there proper indexes on the table ?(If no proper index, consider index creation by taking help of DBA )
Is the table having upto date statistics ? (If statistics are out of date,
consider updating statistics of that table)

7) Consider debugging the process in SM50 ( Program/Session -> Program -> Debugging ) to figureout the issue

8) Using ST05 or ST12, a trace can be taken for background job to figure out where exactly time is being consumed and to identify various cpu/memory bottlenecks or any buffer issues.

9) STAT/STAD transcation can be used to figure out what is the reason for high response time and actions can be taken accordingly

10) By taking help of ABAP er, even ABAP run time analysis can be done using SE30 transaction

By following the above steps, you can pin point the issue and take actions accordingly to minimize runtime of long running background jobs.

Troubleshooting long running transport

How to troubleshoot when a transport is running for unusually long duration and not getting completed or terminated ?

How to troubleshoot when a transport is in truck status for a long duration of time ?

How to cancel a transport request which is in truck status or running status ?

How to terminate a long running transport request to re-import again ?

Transport is not getting terminated. How to do terminate?

How to troubleshoot when a transport is running for unusually long duration and not getting completed or terminated ?

Go to transaction STMS_IMPORT and identify the transport which is running since a long duration.
In the below screenshot, transport with the truck symbol is the long running one



Issue could be due to following reasons :
1) Non availability of space to perform the operation (i.e filesystem or tablespace is 100% full)
Ans:Check out if any of the filesystems (like sapmnt, oraarch etc) of the Central Instance, Database and application servers is 100% full. If so, please add necessary space, which resolves the issue automatically and completes the import of transport.
Also, check out tablespaces fill levels. If autoextend is off and tablespace is 100% full then add sufficient datafiles, which resolves the issue

2) RD* jobs are not running in SAP system
Ans:Check out in SM37 whether RDD* jobs(RDDIMPDP, RDDIC3L, RDDVERSL etc) are running or not. If not, please make sure they are scheduled and perform the import of the transport again

3) Update got deactivated
Ans:Checkout in SM13 whether update is active or not. If it is not active, activate it and import the Transported to Production System.

4) There are no free background workprocesses
Ans:Check in SM50 whether all background workprocesses are in running status. If so, you will need to wait for the free background workprocess to run RDD* jobs to complete the import of the transport. To avoid this issue in future you may increase the number of background workprocesses

Transport is not getting terminated. How to do terminate?

1) If you are unable to terminate a transport which is running, goto SM50 and identify the pid of the transport process. Try to cancel the process with core or without core as shown below.



2) If it is not getting terminated from SAP level, then goto Oslevel and kill.

Command for the same in AIX or HP-UX is kill -9 <PID>
If it is not getting killed from oslevel also, try to search for processes related to tp or R3trans and kill them as well
Eg in AIX or HP-UX : ps –ef |grep tp     Or      ps –ef |grep r3trans

3) If it is not getting terminated from that level, you may try to kill as shown below at SAP level :
Goto Import monitor and


Navigate as below and right click and delete entry to delete the transport which is being imported


By any one of the above 3 methods, transport will surely get terminated. So then you can add to queue again and re-import

Some knowledge on sap workprocess

1. DIALOG WORK PROCESS


Parameters
rdisp/max_wprun_time=600 to 1800sec
rdisp/wp_no_dia


Monitoring Dialog Work Process


SM50-Local Instance (Central Instance):- To display the list of process configured on that instance.
SM66-Global Instance (Including Central Instance and Dialog Instances)


Dialog Process Screen
No, Type, PID, Status (Running, Waiting, Holding, Terminated/Stopped, Ended), Reason (Sleep, Private, Enque mode), Start, Err, Semaphore, CPU, Time, Report, Client, Users, Action, Table.


Using DPMON we can monitor the status of Work Process at OS Level


2. BACKGROUND PROCESS


Background Job Classes
ClassA- High Priority
ClassB- Medium Priority
ClassC- Low Priority


SM36- We can Define Background Jobs
SA38- We can create variant.


Variants are stored in Table TVARV.


Job Status
1. Scheduled, 2. Released, 3. Ready, 4. Active, 5. Finished, 6. Canceled.


Background Job Steps
ABAP Program
External Program
External Commands
Using above Programs we can define Background jobs


Background Job Mechanism
When the dialog user defines to run a job in the background it is entered into the tablesTBTCT and TBTCS


TBTCS (Background processing time schedule table)
TBTCT (Compare value for batch job selection)


Background job scheduler runs for every 60sec or the time specified by the parameterrdisp/btctme=60sec
rdisp/wp_no_btc


Monitoring


SM37- We can monitor Background jobs
SM62- It’s used to display SAP events which will be triggered in the Background by using SAPEVT.
SM69, SM49-External Commands
SM64- To trigger the event in the Background


3. UPDATE PROCESS


SAP TRANSACTION: - It consists of multiple transactions which are handled by different Dialog work process these are updated in Temporary tables. Update process reads the Temporary tables to update the Database based on Transaction Id.
Each Transaction is Logical Unit of Work (LUW).


LUW: - It’s a Transaction which can be committed or rolled back


Types of Updates
Local Update
Asynchronous Update
Synchronous Update


Types of Update Process
V1 Update- High Priority
V2 Update- Low Priority
V3 Update- SAP Reserved
There should be at least one V1 update process defined for every 5 Dialog process


Dialog Process updates each dialog step tasks in temporary tables. These are VB* tables and each of them
VBHDR (Header):- It stores header information
VBMOD (Modules):- These are used to update the transaction.
VBDATA: - The exact data to be updated.
VBERR (Error):- The errors that are occur during the update.


Transaction Id is generated from “NRIV” table (Number Range Intervals)
Monitoring
SM13-We can monitor Update process
SM14- We can activate and deactivate Update process
Update Status
Init, Run, Auto, Error (Ora1631, 1632, 1653, 1654, 255, 275, 1555, Deadlock, Number Range Problem, Support Packages or Notes)


Using following Transactions we can get the granular information about Update Failure
SM21, SM37, ST22, SM13, SM50, SM66




Update Parameters


rdisp/vb_stop_active= 0 or 1:- Set to “0” so that update can be deactivated. If the value is set to be “1”update can’t be deactivated
rdisp/vbdelete:- This parameter delete the old update requests based on number of days. Default 50 days (which are older than 50 days it will delete).
rdisp/vbmail:- It’s used to send an email if update throws an error. This can be viewed in “SBWP” (SAP Business Work Place). Based on user
rdisp/vbname:- Name of the server where updates are processed.
rdisp/vbreorg=0 or 1:- Use to delete the incomplete the update request “0” for Not Delete, “1” for Delete
rdisp/vb_delete_after_execution:- It’s used to delete the update request soon after the execution of update. Set it to “1” for delete record and “2” for not deleting
rdisp/wp_no_vb


4. ENQUEUE PROCESS


It’s used to communicate to obtain a lock while updating a record.


Enqueue time will be 1m/s to 5m/s for Central Instance and 100m/s for Dialog Instance


SM12:- Monitoring Enqueue locks. It displays lock arguments based on Table name, Client and User name (Lock arguments Time and Table)


Enque Problems


Lock Table overflow
enque/table_size=4 MB By Default ( We can increase up to 100 MB)
Enque Time Increase
rdisp/wp_no_enq ( Increase enqueue work process from 0 to 100)
Dead Locks
SM12:- Releasing locks
SM04:- for ending the user session.




5. SPOOL PROCESS


It is only process which is used to output the documents to the printers, fax, Email, etc.
TemSe: - (Temporary Sequential objects) it’s nothing but spool request. It will store spool request up to 32,000 to 99, 000.
rspo/spool_id/max_number=32000 to 99000
rdisp/wp_no_spo


Parameter
rspo/store_location =g or db (To store the spool request at OS level or Database level)
g= OS Level (TemSe Resides in Global Directory) Spool size is small (Around 300MB)Path= \usr\sap\<SID>\SYS\global


db=Database level (TemSe resides in these tables TST01, TST03)


TST01:- It stores the objects and details of spool requests (Author name, No of Copies, Name of Printer etc)
TST03:- Spool Data to be printed


Spool process reads TemSe to generate out put requests. Out put request depends upon the Access Methods
Local Access Method:- Spool process and Host spool resides on the same system (C for windows, L for Unix )
Remote Access Method: Spool process and Host spool resides on two different machines (S for windows, U for Unix)
Front End Printing:- Printers are directly connected to end user systems (F for all)
rdisp/wp_no_spo_fro_max=2 (if 10 spool work process are available 2 will be set for front end printing)


Spool Server: - The server with at least one spool process is called as spool server. It can be Logical (For Fail over and Load balancing of Printers) or Real servers.


SPAD: - For defining the Printer (Output device) and the Spool Server (Logical or Real).


Monitoring
SP01:- It displays the list of spool request (Based on Username and Date Time)
Status (-, +, Waiting, In Process, Printing, Completed, Problem and Error)
SP02:- It displays Individual users spool requests
SPIC: - Spool installation Check use to check spool devices and pending requests
SP12:- TemSe Administration to check memory allocation objects and performs the TemSe consistency check

BRSPACE

BRSPACE??

* Instance management
------------------------------
- Start up database
- Shut down database
- Alter database instance
- Alter database parameters
- Show instance status
- Show database parameters

* Space management
----------- ----------------
- Extend tablespace
- Create tablespace
- Drop tablespace
- Alter tablespace
- Alter data file
- Move data file
- Show tablespaces
- Show data files
- Show redolog files
- Show control files
- Show diska volumes

* Segment management
------------------------------
- Reorganize tables (online)
- Rebuild indexes (online)
- Export tables- Import tables- Alter tables- Alter indexes
- Show tables
- Show indexes
- Show table partitions
- Show index partitions
- Show segments
- Show segment extents
- Show free extents

Checking BR*Tools Release Information

pat2036:oras94 4> brtools –V | brspace -V
BR0651I BRTOOLS 6.40 (40)
Patch Date Info

36 2006-01-11 Small functional enhancements in BR*Tools (note 914174)
38 2006-03-29 BR*Tools support for MDM databases (note 936665)
40 2006-08-30 Wrong message numbers in BR*Tools 6.40 (note 976755)

release note 680046
kernel release 640
patch date 2006-08-30
patch level 40
make platform rs6000_64
make mode OCI_920
make date Sep 5 2006
Summary of the BR Tools

What is BRBACKUP - Backs up data files, conrol files, and online redo log files of the database.
What is BRARCHIVE - Backs up offline redo log files
What is BRRESTORE - Restores data files, control files, and redo log files
What is BRRECOVER - Recovers database files and restores profiles and log files
What is BRSPACE - Manages the database instance, space, and segments (that is, tables and indexes)
What is BRCONNECT - Performs database administration tasks such as statistics update, check database system, adapt next extents, clean up logs and DBA tables. Functions as a help tool to monitor the database during a backup
What is BRTOOLS - Displays the menus from which the other BR programs are called. Functions as an internal help tool started by BRBACKUP, BRARCHIVE, and BRRESTORE.
What is BRGUI - Functions as a Java-based GUI, working as the front-end display program for BR*Tools
Initialization Profile BR* Tools uses the initialization profile init<SID>.sap as a input file.The following are the important parameters in the init<SID>.sap file Ø

exp_dump_dir
exp_table
Imp_table
rebuild_index
reorg_table
show_period
space_copy_dir

exp_dump_dir

This parameter specifies the directory of the export dump file

Syntax : exp_dump_dir = < directory name >
Default : $SAPDATA_HOME/sapreorg

exp_tableThis parameter specifies the table for an export
Syntax: exp_table = [<owner>.]<table> | (<table_list>)
Default : None
Eg:
exp_table= (SDBAH, SAPR3.SDBAH)

imp_tableThis parameter specifies the table for an import
Syntax: imp_table = [<owner>.]<table> | (<table_list>)
Default : None
Eg:
imp_table= (SDBAH, SAPR3.SDBAH)

rebuild_indexThis parameter specifies the database indexes for an index rebuild
Syntax: rebuild_index = [<owner>.]<index> | (<index_list>)
Default : None
Eg:
rebuild_index= (SDBAH`0, SAPR3.SDBAH`0)

reorg_tableThis parameter specifies the table for reorganization
Syntax: reorg_table = [<owner>.]<table> | (<table_list>)
Default : None
Eg:
reorg_table= (SDBAH, SAPR3.SDBAH)

show_TableThis parameter specifies the time period for which BRTOOLS display log files
Syntax : show_period = <days>
Default : 30
Possible values :
0 – Show all available log files
1 – Show logs created today
>1 – Show logs files created in the previous specified number of days

space_copy_dirThis parameter specifies the directory for file copies during space management.
Syntax : space_copy_dir = <directory name>
Default : $SAPDATA_HOME/sapreorg

Logs for BR*Tools

Logs are created for BRBACKUP, BRARCHIVE, BRRESTORE, BRRECOVER, BRCONNECT, and BRSPACE. These supply information about database operations and are useful for problem analysis.

The following types of logs are written: Ø
File System Logs
Database Logs in tables SDBAH and SDBAD


File System Logs

For more information, see:
· BRBACKUP Logs• Detail log - b<encoded timestamp>.<ext> ( eg: bdvecswx.anf ) • Summary log - back<DBSID>.log (eg: backS94.log )
Directory : /oracle/<SID>/sapbackup

· BRARCHIVE Logs• Detail log - a<encoded timestamp>.<ext> (eg: aduryokf.svd ) • Summary log - arch<DBSID>.log (eg: archS94.log )
Directory : /oracle/<SID>/saparch
· BRRESTORE Logs• Detail log - r<encoded timestamp>.<ext> (eg: rdvecswx.rsb ) • Summary log - rest<DBSID>.log ( eg: restS94.log )
Directory : /oracle/<SID>/sapbackup

BRRECOVER Logs• Detail log - v<encoded timestamp>.<ext>
• Summary log - recov<DBSID>.log ( eg: recovS94.log )
Directory : /oracle/<SID>/saparch
· BRSPACE Logs• Detail log - s<encoded timestamp>.<ext> ( eg: sduvytan.tse )
• Summary log - space<DBSID>.log (eg: spaceS94.log )Directory : /oracle/<SID>/sapreorg
· BRCONNECT Logs• Detail log - c<encoded timestamp>.<ext> (eg: cduxtdrn.chk)
• Summary log - conn<DBSID>.log ( eg: connS94.log )
Directory : /oracle/<SID>/sapcheck
Database Logs
The database logs of BRBACKUP, BRARCHIVE, and BRCONNECT are stored in tables SDBAH and SDBAD

SDBAH

This table contains information that refers to the backup as a whole:


Starting time of the backup or BRCONNECT processing
End time of the backup or BRCONNECT processing
BRBACKUP/BRARCHIVE/BRCONNECT return code
BRBACKUP/BRARCHIVE/BRCONNECT action ID (encoded timestamp of the file system log names)
BRBACKUP/BRARCHIVE/BRCONNECT function ID (extension of the file system log names)

SDBAD

This table contains information that refers to the backup of one file:

File name
· Oracle file ID or log group number
· End time of the backup of the file
· Name of the volume where the file was saved
· Position of the file on the volume
· Backup ID of the external backup program
· Compression rate of the software compression

In addition, table SDBAD contains internal BRBACKUP information about compression rates and backup durations for the individual database files. For BRCONNECT, SDBAD tables contain information on the total number of objects processed by BRCONNECT.

BRTOOLS for SAP

BR*Tools provides you with menus to perform a wide range of database administration functions for your database BRTools (and BRSpace) is the successor of SAPDBA. SAPDBA is no longer delivered with WAS 6.40 (NetWeaver 04). You can continue to use SAPDBA 6.20 for Oracle 9.2 on SAP systems that are based on Web AS 6.40. However, SAP recommends that you only use the BR*Tools there. You can of course also use the SQLPLUS command tool.


BR *Tools is the program package containing BRBACKUP, BRARCHIVE, BRRESTORE, BRRECOVER, BRSPACE, BRCONNECT, and BRTOOLS.
BRTOOLS is the program that displays the menus from which the other BR programs are called.
Not all functionality of SAPDBA is included in the new BR*Tools. P.e. the “Alter table or index parameters” and “Reorganize tablespace and data files” are missing.

Overview of the tools



BR*Tools User InterfaceThe user interface to BR*Tools provides you with menus to perform a wide range of database administration functions for your Oracle database. The menus are controlled by BRTOOLS, which in turn calls one of the functional BR programs.
You can use BR*Tools with a:

Character-based interface
GUICharacter-based interface, as in the following example, which shows the main menu:

BR0280I Time stamp 2003-03-06 11.30.57BR0656I

Choice menu
1 - please make a selection------------------------------ Character-based interface
BR*Tools main menu

1 = Instance management
2 - Space management
3 - Segment management
4 - Backup and database copy
5 - Restore and recovery
6 - Check and verification
7 - Database statistics
8 - Additional functions
9 - Exit program

Standard keys: c - cont, b - back, s - stop, r - refr, h - help

----------------------------------------------------------------BR0662I

Enter your choice:

What is BRBACKUP??

This SAP tool for the Oracle database enables you to back up database files.
The smallest unit that can be saved with BRBACKUP is a file. You can use BRBACKUP for backing up both files in the database and non-database files and directories.

Use the backup_mode from the Initialization Profile init<DBSID>.sap or the command option brbackup -m|-mode for this purpose

backup_mode = all/full/incr

This parameter is used by BRBACKUP to determine the scope of the backup activity.
Syntax: backup_mode = all|all_data|full|incr|<tablespace>|<file_ID>|<file_ID1>-<file_ID2>|<generic_path>|sap_dir|ora_dir|<object_list>Default: all

What is BRARCHIVE??

This SAP tool for the Oracle database enables you to archive offline redo log files.

You can also start BRARCHIVE when the database is shut down.
You should archive the offline redo log files on tape using BRARCHIVE.
In contrast to BRBACKUP, BRARCHIVE does not have its own management of tape continuation. When a tape is full, you must restart BRARCHIVE to write to the next volume.Logging for BRARCHIVE

BRARCHIVE writes the following file system logs:

·<SAPDATA_HOME>/saparch/a<encoded timestamp>.<ext>
Every detail log contains information about the actions performed during an archiving run.
·<SAPDATA_HOME>/saparch/arch<DBSID>.log
This summary log contains a brief entry for every archiving operation that was performed.

BRARCHIVE also records its actions in the database tables SDBAH and SDBAD
BRRESTOREThis SAP tool enables you to restore an entire database backup or parts of it, when the backup was performed with BRBACKUP. Any non-database files and directories you saved can also be restored. In the process, the subdirectories in sapdata<n>directories are automatically created, when necessary.
You can also restore the offline redo log files that were backed up with BRARCHIVE. This operation can be performed at the same time as the restore of the corresponding backup.

Ø·BRRESTORE can run unattended when option -c force is set. The option -c only suppresses the first confirmation prompts for mounting a volume.ØØ·BRRESTORE uses the BRBACKUP logs and the summary log from BRARCHIVE to decide where to restore the requested file. You can manually specify a different directory as well.

·One or more incomplete BRRESTORE runs can be completed with the option -f. BRRESTORE automatically determines the files to be restored.

What is BRRECOVER??

The SAP tool BRRECOVER for Oracle databases is used as a database administration tool to help you recover your database. You can use BRRECOVER to perform the following:

Complete database recovery
Database point-in-time (PIT) recovery
Tablespace point-in-time (PIT) recovery
Whole database reset
Restore of individual backup files
Restore and application of offline redo log files
Disaster recovery
What is BRCONNECT ??The SAP tool BRCONNECT for Oracle databases is used as:

· A database administration tool, which you can call yourself from the command line
· A utility tool, which BRBACKUP calls in the background

BRCONNECT is specially designed to administer multi-schema databases, in which you have more than one SAP System in the same Oracle database

Uses
Database System Check with BRCONNECT
Adapt Next Extents with BRCONNECT
Update Statistics with BRCONNECT
Changing Database User Passwords with BRCONNECT
Clean Up Old Logs and Trace Files with BRCONNECT BRCONNECT cleans up the following files:


Detailed BRARCHIVE logs in the saparch directory
Detailed BRBACKUP logs in the sapbackup directory
Detailed BRCONNECT logs in the sapcheck directory
Detailed BRRESTOE logs in the sapbackup directory
Detailed BRSPACE logs in the sapreorg directory
BRBACKUP disk backups of the database files
BRARCHIVE disk backups of the offline redo log files
BRSPACE export dump and export script directories
Oracle trace and audit files
Log records in the SDBAH and SDBAD tables
Log records in the XDBtables
Database check results in DBMSGORAtable

Adding SAP Datafile using BRTools

Hi All,
In this blog I will tell you how to add a new SAP datafile using BRTools:
In Windows login as SIDADM.

              Start --> run --> cmd --> brtools

For Linux and Solaris login as root, then follow these commands:

> su - oraSID > sqlplus /nolog > conn sys as sysdba
Enter password: (Press enter)
Connected.
sql>brtools
---------------------------------------------------
Steps are common once brtools starts:
Step1:
------------------------------------------------------------------------------
BR*Tools main menu

1 = Instance management
2 - Space management
3 - Segment management
4 - Backup and database copy
5 - Restore and recovery
6 - Check and verification
7 - Database statistics
8 - Additional functions
9 - Exit program

Standard keys: c - cont, b - back, s - stop, r - refr, h - help
-------------------------------------------------------------------------------
BR0662I Enter your choice:
2 ----------------> Enter 2

-------------------------------------------------------------------------------
Database space management

1 = Extend tablespace
2 - Create tablespace
3 - Drop tablespace
4 - Alter tablespace
5 - Alter data file
6 - Move data file
7 - Additional space functions
8 - Reset program status

Standard keys: c - cont, b - back, s - stop, r - refr, h - help
-------------------------------------------------------------------------------
BR0662I Enter your choice:
1 -------------> Enter 1

And then enter c two times.

Step2:
-------------------------------------------------------------------------------
Tablespace extension main menu

1 = Extend tablespace
2 - Show tablespaces
3 - Show data files
4 - Show disk volumes
5 * Exit program
6 - Reset program status

Standard keys: c - cont, b - back, s - stop, r - refr, h - help
-------------------------------------------------------------------------------
BR0662I Enter your choice:
1 ---------------> Select
After this all the table space will be displayed
Select the tablespace for which you want to add a new datafile.

For example we are trying to add datafile to tablespace "PSAPSR3".

As an example we have selected
-------------------------------------------------------------------------------
Options for extension of tablespace PSAPSR3 (1. file)

1 * Last added file name (lastfile) ....... [[Drive]:\ORACLE\SID\SAPDATA2\SR3_4\SR3.D
ATA4]
2 * Last added file size in MB (lastsize) . [2000]
3 - New file to be added (file) ........... [[Drive]:\oracle\SID\sapdata2\sr3_5\sr3.d
ata5]
4 # Raw disk / link target (rawlink) ...... []
5 - Size of the new file in MB (size) ..... [2000]
6 - File autoextend mode (autoextend) ..... [yes]
7 - Maximum file size in MB (maxsize) ..... [10000]
8 - File increment size in MB (incrsize) .. [20]
9 - SQL command (command) ................. [alter tablespace PSAPSR3 add dataf
ile 'D:\oracle\SID\sapdata2\sr3_5\sr3.data5' size 2000M autoextend on next 20M m
axsize 10000M]

Standard keys: c - cont, b - back, s - stop, r - refr, h - help
-------------------------------------------------------------------------------
BR0662I Enter your choice:c ---------------> Enter c to continue and create datafiles.
----After that enter n --------------------
BR0675I Do you want to perform this action?
BR0676I Enter 'y[es]' to perform the action, 'n[o]/c[ont]' to skip it, 's[top]'
to abort:
n --------------> Enter n to stop creating another datafile.
Y ------------> It will add a new datafile to it.

To monitor SAP Locks

SAP System Administration is to monitor SAP Lock Entries. It often happens in your SAP System that when your users run transaction codes and their terminal are abnormally disconnected, these situation could cause Lock Entries that could disturb any other active users doing process. Sometimes lock entries could affect your SAP performance as it blocks other users' processes and you need to delete the lock entries so that other users can continue their processes. And as part of your routine monitoring you have to regularly monitor the lock entries.

1. To monitor the lock entries go to transaction code SM12




2. Select the client and user name or leave it blank to see all the lock entries.




3. You can see detailed information for the lock argument




4. Choose one lock entry you want to delete. Be careful before deleting lock entry, make sure it's not used by any processes.

How to monitor SAP System logs

One of the tasks of SAP Basis Administrator is to maintain the health of the system and to keep the system performancegood and the SAP application runs well. You must regularly check the system log for early detection and take action if necessary. This task is part of Daily Monitoring in SAP System Management (SAP CCMS).

You check the SAP system logs from transaction SM21.
1. Click Continue if it's you first time running SM21.


How to monitor SAP System Logs - Pic 1



2. Choose All Remote Systems logs if you have more than one application servers.


How to monitor SAP System Logs - Pic 2


3. Look for any error messages, and do detailed analysis by double clicking it. You have to do thismonitoring daily. Because if too many errors happen it can affect your daily SAP Application Serverperformance.


How to monitor SAP System Logs - Pic 3


4. Now you can see further information from it. Actually the checking process can't run stand alone, you have to check as well error log from System Dump (ST22) or system Process (SM50/SM51)


How to monitor SAP System Logs - Pic 4


How to monitor SAP System Logs - Pic 5

SAP Basis Transaction codes (T-codes)

User Administration:

 

SU01         User Maintenance
SU01D      User Display
SU02         Maintain Authorization Profiles
SU03         Maintain Authorizations
SU05         Maintain Internet users
SU10         User Mass Maintenance
SMLG        Maintain Logon Group
SUPC        Profiles for activity groups
SUIM         Info system Authorizations
PFCG        Profile Generator
PFUD        User Master Data Reconciliation

 

Client Administration:

 

SCC3        Checking Client Copy Log
SCC4        Client Administration
SCC5        Client Delete
SCC7        Client Import Post-Processing
SCC8        Client Export
SCCL        Local Client Copy
SCC9        Remote client copy

 

Database Administration:

 

DB01        Analyze exclusive lock waits
DB02        Analyze tables and indexes
DB12        DB Backup Monitor
DB13        DBA Planning Calendar
DB15        Data Archiving: Database Tables

 

Transport Management System:

 

STMS       Transport Management System
SE01        Transport and Correction System
SE06        Set Up Workbench Organizer
SE07        CTS Status Display
SE09        Workbench Organizer
SE10        Customizing Organizer
SE11        ABAP/4 Dictionary Maintenance
SE16        Data Browser
SE80        Repository Browser
SM30       Call View Maintenance
SM31       Table Maintenance

 

Background Jobs Administration:

 

SM36       Define Background Job
SM37       Background Job Overview
SM39       Job Analysis
SM49       Execute External OS commands
SM62       Maintain Events
SM64       Release of an Event
SM65       Background Processing Analysis Tool
SM69       Maintain External OS Commands

 

Spool Administration:

 

SP01       Output Controller
SP11       TemSe directory
SP12       TemSe Administration
SPAD      Spool Administration

 

Other Administration Tcodes:

 

AL11       Display SAP Directories
BD54       Maintain Logical Systems
OSS1       Logon to Online Service System
SALE IMG   Application Link Enabling
SARA       Archive Management
SICK        Installation Check
SM14       Update Program Administration
SM35       Batch Input Monitoring
SM56       Number Range Buffer
SM58       Asynchronous RFC Error Log
SM59       RFC Destinations (Display/Maintain)
SAINT      SAP Add-on Installation Tool
SPAM      SAP Patch Manager (SPAM)
SPAU       Display modified DE objects
SPDD       Display modified DDIC objects
ST11        Display Developer Traces

 

Daily monitoring TCodes:

 

AL08       Current Active Users
SM12       Display and Delete Locks
SM13       Display Update Records
SM21       System Log
SM50      Work Process Overview
SM51       List of SAP Servers
SM66       System Wide Work Process Overview
ST22        ABAP/4 Runtime Error Analysis
ST01        System Trace
ST02        Setups/Tune Buffers
ST04        Select DB activities
ST05        Performance trace
ST06        Operating System Monitor
ST10        Table call statistics
ST03        Performance, SAP Statistics, Workload
SU56        Analyze User Buffer

 

Other Monitoring Tcodes:

 

OS01       LAN check with ping
RZ01        Job Scheduling Monitor
RZ03        Presentation, Control SAP Instances
ST07        Application monitor
STAT       Local transaction statistics

 

Other Useful Transactions Codes

 

AL22        Dependent objects display
BAOV      Add-On Version Information
SA38       ABAP reporting
SE38        ABAP Editor
HIER        Internal Application Component Hierarchy Maintenance
ICON        Display Icons
WEDI        IDoc and EDI Basis
WE02        IDoc display
WE07        IDoc statistics
WE20         Partner profiles
WE21       Port definition
WE46       IDoc administration
WE47        Status Maintenance
$TAB        Refreshes the table buffers
$SYNC      Refreshes all buffers, except the program buffer