SAP BASIS DB Interview Questions

Creating Database Statistics, Index Rebuilds, and Log Backup Jobs – MS SQL Server
Database statistics refresh jobs should be scheduled to run twice daily on all the SAP systems. But occasionally a manual refresh needs to be done due to table reorganization, index rebuild, etc.
1. Log on to the server using the adm user ID.
2. Open the MS SQL Server Enterprise Manager.
3. Expand the navigator tree until you see the Management entry. Expand it.
4. Right-click on Database Maintenance Plans and click New Maintenance Plan.
5. Use the wizard to create the job you need.
6. You may now close the Enterprise Manager session and log off the server.
Creating Database Statistics, Index Rebuilds, and Log Backup Jobs – Oracle
1. Log on to the appropriate SAP instance any client.
2. Go to transaction DB13.
3. On the DBA Planning Calender for Oracle Database : Maintain screen, double-click on a blank line on any day in the future.
4. On the Schedule Action for . DD.MM.YYYY popup, use the radio button to turn “on” the task you want to do. For each action, you need to fill in the Start Time in military time format, the Period (Weeks) which is how many weeks between running of this job – blank for one time only, 1 for weekly, 2 for bi-weekly, etc. and Calender if you want to use any calendar except the SAP supplied standard Factory calendar.
These are the details for each action:
Whole database offline + redo log or
Whole database offline backup or
Whole database online + redo log or
Whole database online backup
Generic tape names for database backup
Database backup profile – usually init.sap
Options for ReDo log backup
Redo log backup
Generic tape names for database backup
Options for ReDo log backup
Partial database offline backup or
Partial database online backup
Tablespace names to be included in the back up
This document is the intellectual property of Jo Spencer and may not be edited without permission.
Generic tape names for database backup
Database backup profile – usually init.sap
Check and update optimizer status
Tablespace names to be included in the statistics run
Adapt next extents
Tablespace names for next extents adaption
Check database
N/A
Verify database
Tablespace names to be verified
Database backup profile – usually init.sap
Cleanup logs
N/A
5. You may now leave the DB13 transaction.