Proactive monitoring of the SAP systems, will help to understand issues in advance & helps us to take corrective actions and  thus will lead to lesser downtime of the systems, improving profitability of the business organisation.

 

Monitoring can be focused on ABAP stack(including database checks), Java Stack and Oslevel checks.

 

 

 

 

ABAP Stack Checks :

 

 

 

SM50 : (Process Overview)

 

This transaction code will be useful to view the processes that are running currently in an sap insance. In this view you can check whether there are free workprocesses to execute the processes. If all the workprocesses are in running state and no work process is idle it means that wait times will increase for the processes that are waiting in the dispatcher queue leading to performance degradation. If you find that there are no free workprocceses for maximum times that you may consider, increasing the number of workprocesses.

 

 

How to increase the number of work processes

 

 

SM66 : (Global process overview)

This transaction code will be useful to view the processes that are running across all instances/application servers of a SAP system. Similar to SM50 checks can be done in this transaction as well.

 

 

 

 

SM51 : (Application servers status)

 

This transaction code will be useful to view all the hostnames and application servers status. If any application server is down, the same can be identified using status of the server column. We can also figure out different Message types (Dialog, Batch, Update, Upd2, Spool, ICM etc) configured for the respective servers.

 

 

 

 

SM12 : (Lock entry list)

This transaction code will be useful to view all the sap locks that are present in the system. As part of monitoring, we need to look for any old sap locks that are more than 1 day. If any such locks, we need to analyse the reason for that lock for such longer duration and take actions accordingly. A lock can be set for such a long duration due to a long running background job or a lock is not released due to an application error or a program terminated abruptly but lock not released etc.

 

 

 

 

How to delete a sap lock?

 

ST22  : (ABAP Dumps )

This transaction code will be useful to view all the abap dumps that have occured in the system on a given day. As part of daily monitoring, it is the responsibility of the basis administrator to analyse the dumps and take necessary actions to avoid issues.

Some of the examples of abap dumps are timeout issue, database space issue, spool overflow issue etc

 

 

 

 

SM21 : (System log)

This transaction is useful to view the log of the sap system for various operations. This log will be very useful to identify various issue in advance and to take necessary measures. System log is the place to check out for any timeout, network issues, database space issues, message server issues, spool overflow, locktable overflow etc issues.

Additional details :

SAP System log

 

SM13 : (Update Requests overview)

This transaction is useful to figure the status of update system. Incase an update is inactive we can figure out the same from this transaction and necessary action can be taken and update can be activated again.

 

 

 

 

Update got deactivated. what is the reason for update deactivation? How to activate the update ?

 

 

 

 

SM14 transaction can be called internally from SM13. These both transactions are useful for update administration.

In SM13, you can select status (canceled, to be updated, v1 executed, v2 executed, all ) and time interval during which you would like to view the status execute to check the overview of updates as per the status and time interval selected.

 

 

 

 

In case of canceled updates, analysis to be done whether to repeat update.

 

 

 

 

ST02 : (Tune summary )

 

 

 

This transaction will be used to monitor

 

 

 

•  Buffer statistics like hitratio, swaps, db access details, size of buffer and free size of buffer etc

•  Important statistics related to  Roll area, Page area, Extended memory and heap memory
• Call statistics like select, insert, update and delete

 

As a basis administrator, it is our responsibility to ensure there is more hit ratio for the buffers and less swaps to ensure efficient performance of the sap system. In case you see there are more swaps and less hit ratios for most of the buffers, then tuning buffers to be carried out to ensure optimal performance.

DB12 (Backup logs) : This transaction is useful to check the details of

 

• last successful backup
• overview of database backups ( Success / failure of backup with log details)
• Archiving directory status (Free space of oraarch )
• Overview of redolog files ( Number of redologs that are not yet backed up)
• overview of redolog backups (Success / failure of backup with log details)

 

DB13 (DBA Planning calender) :

 

 

This transaction will be useful to schedule various database backups & clean up jobs like ( whole database backup offline/online, Full backup online/offline, incremental backup offline/online, redolog backup, update statistics, check db, cleanup logs, compress database, verify database, initialize tape and validate structure jobs).

 

 

In this transaction, you can also check the status of every job that was scheduled and can reschedule in case of failures.

 

 

DB14  (DBA operations log) :

 

This transaction will be useful to check the status of following :

• Database backup
• Redolog backup
• BRSPACE log (extend tablespace issues etc)
• BRCONNECT operations (Update optimiser statistics , database check etc)

As an sap basis administrator it is our responsibility to check and ensure backups and other cleanup jobs are successful everyday. Incase of failures, should figure out root cause and take actions like rescheduling and ensure these jobs are successful.

 

 

SM37 ( Job status overview) :

 

This transaction will be useful to have an overview of jobs with different statuses.

As part of daily monitoring, SAP basis administrator should use this transaction to findout canceled jobs and active jobs(for eg: long running – more than 24hrs etc).

 

 

Incase of canceled jobs, root cause for the failure to be figured out from the logs of the respective job and to be actioned by rescheduling etc.

Incase of long running jobs, we need to figure out the reason for long running and action them accordingly.

 

 

In SM37, using extended job selection option, we can even select the jobs based on start condition, steps (like abap program, external command or external program), period etc

 

 

How to identify long running jobs in sap ?

How to troubleshoot a background job running for long duration in sap?

 

ST04 (Database alert logs and performance) :

 

This transaction will be useful for (oracle) database administration. In this screen, goto Alerts and drill down further. Click on “Database Check” to find out any errors or warnings related to database like MISSING_STATISTICS, STATS_TOO_OLD, LAST_BACKUP_FAILED, LAST_ARCHIVE_FAILED etc. After going through the error or warning in details take necessary corrective actions based on the error like running update stats again, re-triggering backup etc

 

Under Alerts, you can view Alert monitor which will summarize status of the database under different heads like

 

• Space Management
• Performance
• Backup/restore
• SAP Consistency
• Health

Drill down on each of these to find out potential problems. These are color coded for ease of administrator (Red for errors, yellow for Warnings and Green for OK status)

 

For Eg: If PSAPSR3 tablespace is >90%, you can see Space management in red color. Then it is the responsibility of Basis administrator to take necessary actions on the same.

 

SP01 ( Check Spool status ) :

 

This transaction is useful to find out the status of spool request and output request. In SP01 transcation, you can list the spool requests or output requests between a given interval.

In the list generated, you can check out the status of spool requests and findout any errors by drilling down further.

For eg: if so many spools are in waiting status, find out whether output device is available or not.

If many spool are in error status, figure out if there is any network issue and take necessary actions.

What are the different Spool statuses and their significance?

If  customers complain that they are not able print anything from SAP, check out whether there is any spool overflow.

What is spool overflow ? How to troubleshoot spool overflow issue ?

 

SXI_Cache :

 

This Tcode is specific to XI or PI system. This Tcode is used to findout whether cache refresh is happening or not. Incase if cache refresh is happening successfully, it will indicate the same in green color. Otherwise it will be in red indicating a problem with cache refresh.

 

If there is a problem with cache refresh then basis administrator has to troubleshoot the same.

 

 

SLDCHECK :

 

This Tcode will be useful to figure out whether connection to the SLD system from the system on which you are testing is fine or not. In case the connection is fine, all checks will appear in green. Incase of any issues, it will appear in red or yellow and then basis administator has to troubleshoot it and make sure SLDCHECK is working fine.

 

Ensuring SLDCHECK is working fine is important to keep all systems in the landscape in sync.

 

 

SXI_MONITOR :

 

This TCode is specific to XI or PI system. This transaction will be useful to figure out any errors or warnings in the processing of XI or PI messages. In case of any issues, this needs to be informed to functional team and should be troubleshooted accordingly with the functional team inputs.

 

 

DBO1 :

 

This transaction code is useful to findout the database locks that are present in the SAP system.

 

As part of daily monitoring, SAP Basis administrator has to figure out if there are any long pending locks more than 1 day etc and analyse reasons for the same. Sometimes if programs/jobs got terminated abruptly without removing the database locks set, this will lead to performance issues as other programs which needs that lock cannot set etc and they have to wait indefinitely as these locks won’t get released automatically. In case of any long pending locks, Basis administrators should contact DBA team if any an dfigure out the reason for these locks and action accordingly

 

Jack Stack Checks :

 

Please refer below links to understand Daily Java monitoring of SAP Landscape:

 

SAP Java monitoring check list 1

 

SAP Java monitoring check list 2

To monitor live Cache system, please refer below link :

Live Cache Monitoring in SAP

 

 

Please find below table which summarizes daily monitoring tasks that are to be performed by the SAP Basis Administrator :

 

Sno Task ABAP Stack Checks 1 Check process overview(SM50) 2 Check overall system process overview(SM66) 3 Check application servers status(SM51) 4 Check for any pending locks (SM12) 5 Check for Dumps in the system(ST22) 6 Check System log for any errors(SM21) 7 Check for any hanged updates or update status(SM13) 8 Check for excessive swapping (ST02) 9 Check for critical job status like backup,updatestats,checkdb etc(DB13) 10 Check for longrunning/failed jobs status(SM37) 11 Check database alertlogs and performance(ST04) 12 Check spool job status (SP01) 13 Check cache status (sxi_cache) for PI System 14 Check SLD functionality(SLDCHECK) 15 Check SXI_MONITOR for PI system 16 Check for Database locks(DB01) Java Stack Checks 1 Check java portal accessibility using link 2 Check server0 log for java system for critical errors 3 Check accessibility of management console 4 Check server node status 5 Check default trace for critical java errors 6 Check java reports for memoryconsumption/swapping Os level checks 1 Check filesystems usage (shouldb be <80%) 2 Check for swap space using topas etc 3 Check for work directory log files at oslevel for errors

 

 

 

1. Download all the necessary languages from SAP service marketplace. The languages will be in DVD type (you might need to download all languages files – almost 5GB sizes). Please ensure the languages is download as per your SAP system component version. Let say,  CRM will be have its own languages type and ECC will have its own languages type.

2. Put all the downloaded files into your EPS/in folder.

3. In client 000, execute report from transaction code SE38. Click Add to add a new language entry. As for this example, we are going to add Bulgarian language. Save and click Activate.

4. Click on Simulate to find the new entry for parameter zcsa/installed_languages. Go to transaction code RZ10, choose Instance Profile. Add or edit the parameter zcsa/installed_languages with the new value as per simulation earlier.

5. Go to transaction code SMLT. Choose Language > Classify. Fill in the Language and Supplementation Language. Please be noted that the Supplementation Language can be defined once only. As per SAP recommendation, the Supplementation Language is advisable to set to English or German. After Save, you can see the language entry is added to the SMLT language entries.

6. Highlight the language that you have classified earlier. Choose Language > Import Package. Click on Settings, ensure below settings are selected. Then, click on Find Package (s).  This will searching the language package from the EPS/in directory. You can see the packages state from the Status column (define either the upload language package is valid or not). Select Execute to start import the language.

7. You can monitor the import status from transaction code STMS or SMLT, under Imported Packages folder.

8. Once the import is completed. You can proceed to import the support packages. Choose Language > Special Actions > Import Support Packages. Ensure, the related support packages are downloaded and stored at the EPS/in directory. Once come at Import Language Data, choose Overwrite on Handling Repaired Objects. Wait for the support packages import to complete.

9. Import language parts of support packages is successful.

10. You have now successfully imported & installing the language in SAP. Additional to language import steps, you need to execute the language supplementary to the newly imported language.

What is the use of solution manager, and what we can do with solution manager?

Now a days solution manager is mandatory.

1. it is used for generating keys and downloading support packages

2. it is used to document user requirments and preparing senarios what needs to to be adopted using solution manager, where the blue print is the part of solution manager.

3. it is used for reporting, solution desk,to manage the change requests and use to monitor entire landcape Central message processing in the SAP Solution Manager:
– Display customer data, problem description, priority, attached documents, Service Level Agreements (SLA)
– Assign processor
– Send messages to the creator and other processors
– Forward message to other processors or support units
– Create documents and URLs
– Attach documents
– Status assignment and monitoring
– Create a worklist with selection conditions *– Shankar

I have a requirement to install SAP Solution Manager Solution Support Enablement Package (SEP) in our solution manager 4.0. This SEP contains, RBE, TDMS, …etc.,

I checked for the software download at market place but couldn’t find the software package, can anyone help me to download this SEP for windows/oracle.

Look at following:

http://service.sap.com/swdc -> Download -> Installations and Upgrades -> Entry by Application Group -> Installations and Upgrades -> SAP Technology Components -> SAP Support Enablement Package – >SAP Support Enabl. Package 1.0

How to configure the service desk on Solution Manger 4.0. I want to cofigure Solution Manger only for service desk I have install Solution Manger 4.0. What is the Step please explain.

Check: http://service.sap.com/rkt-solman

There are tutors, PDFs and powerpoints to guide you through the configuration process. *– Markus

If you have 3 or 4 client systems, must you install SAP solution manager for each one of these systems and manage them independently -or- 2. Can you install One Solution manager, that will manage all 3 these systems in one solution manager -or- 3. Do you install 3 Solution managers for each of the systems, then another one linked to the 3 individual solution managers, which then in turn manages the 3 systems in one.

In any System landscape only one solution manager is installated in one system and it will communicate with the other system using the RFC and collect the report from each and every system through (SDCCN).

If SAP* and DDIC logins are locked and you are not able to login through SAP GUI then we can unlock SAP* and DDIC at database level

by resetting the flags of SAP* and DDIC to 0 in the table USR02 where all the user records are saved. When the logins are locked out then

the flag value will be 128. If we change it to 0 at database level then it will get unlocked.

Below is the query for resetting the flag

UPDATE prd.USR02 set UFLAG = ’00′ where MANDT = ’000′ and bname= ‘DDIC’;

Here prd is the database name; UFLAG is the field which we need to set to 0, MANDT represents in which client the login belongs to and

BNAME is the field which contains logins. If you want to reset the flag for SAP* when it gets locked then replace DDIC with SAP* in above query.

or

1) Login to database using / as sysdba

2) select aname from sapsr3.usr02 where mandt=000;

3)delete from sapsr3.usr02 where aname=’SAP*’ and mandt=000;

R/3 System

• SM21 System Log

All warnings and error messages should be analyzed and corrected. This procedure should include documenting all problems and their resolution.

• AL01 SAP Alert Monitor

All Alerts should be acknowledged, analyzed, corrected, and documented.

• RZ02 System Monitor

Administrators should monitor the system monitor first thing each morning. This procedure should confirm all systems are running and using the proper Operation Mode.

• SM37 Job Log Overview

Administrators should examine all canceled jobs. These jobs should be analyzed and repaired if necessary. Problems and resolution should be documented.

Administrators should check all logs, including list output and application logs for all critical jobs.

Administrators must release all jobs scheduled by users with no rights to release.

• RZ01 Graphical Job Monitor

Administrators should monitor run-time statistics for each job. This information should be used to fine-tune background job schedules and can provide administrators with some advance warning if jobs begin to perform badly.

• SM13 Update Records

This transaction displays aborted updates; it should never occur in a production system. These updates should be reported to and corrected by the developers as soon as possible.

• SM66/SM50 Process Overview

Administrators should check the system processes throughout the day. Long-running background jobs, and runaway or poorly written reports can consume enormous system resources if not controlled. Administrators can use this transaction to spot-check their environments. It is appropriate to investigate these activities with the end users before killing these processes. All unexplained process failures should be investigated as well.

• SP01 Spool Request Overview

Failed print jobs can be restarted. Often these jobs fail because of problems on the client end (for example, PC running SAPLPD is shut off). Because R/3 tracks print jobs only to the target queue, actual successful print jobs are not guaranteed by a complete status in the output controller. Critical and mass print jobs should be confirmed by the end users before they are deleted from the TemSe.

• SE01 Transport Logs

All warnings and error messages should be analyzed and corrected. This procedure should include documenting all problems and resolutions.

• ST03 Workload Analysis

When it comes to tuning an R/3 system, there is no replacement for experience. Administrators should stay on top of the workload analysis numbers in their system, especially when you have no performance problems. Having a clear picture of how your system performs when working well, provides a “feel” for the system. This “feel” enables you to see problems coming and, in many cases, prevent them.

• ST02 Buffer Analysis

Buffers should be monitored on a regular basis. Hit ratios, free space, free dir entries, and swaps should be monitored. This process helps the administrator in the ongoing tuning process.

• SM35 Batch Input Logs

Batch Input logs should be checked after each run. The batch input process flags errors and allows you to reprocess after repairing .

• SM12 Lock Entries

From time to time, a user may lock an object and for some reason (such as a lost connection or program error) the lock remains. All old lock entries should be analyzed and corrected.

• SP12 TemSe Administration

Administrators should check the file system and database storage requirements, especially when printing mass quantities of data. A TemSe consistency check (RSPO0043) should be scheduled to run daily, just prior to the spool reorganization (RSPO0041).

• TU02 Profile Parameter Changes

The R/3 System monitors all system profiles for changes. Although not perhaps a daily activity, administrators should confirm that profiles are adjusted only by authorized users and whenever possible with the R/3 profile maintenance tool.

Database

• DB12 SAPDBA Logs

• Verify success of nightly backup.
• Verify free space in log directory

 

• DB02 Storage Management

• Monitor database growth.
• Monitor table and index growth and fragmentation.
• Monitor optimizer statistics if necessary for your database.
• Monitor the database error log daily.
• Monitor total logical and physical reads per day to keep track of the development of database workload through time.
• If they are supported by your database, pay particular attention to the most expensive SQL statements.

• ST04 Database Logs

• AL02 Database Alert Monitor

All alerts should be acknowledged, analyzed, corrected and documented.

• DB03 Parameter Changes

The R/3 System monitors all database profiles for changes. Administrators should regularly confirm that profiles are adjusted only by authorized users.

Host Operating System

• OS06 OS Monitor

All alerts should be acknowledged, analyzed, corrected, and documented.

• AL16 OS Alert Monitor

All alerts should be acknowledged, analyzed, corrected, and documented.

• OS03 Parameter Changes

The R/3 System monitors all operating system kernel changes. Administrators should regularly confirm that kernel parameters are adjusted only by authorized users.

Network

• ST09/ST08 Network Alert Monitor

All alerts should be acknowledged, analyzed, corrected and documented.

Clients

• SM04 User Overview

Administrators should consider doing spot checks throughout the day to monitor users and their activities. Are all users using the logon groups? Are users logging on using several machines? Are there any unrecognizable user IDs? Are users trying or using transactions they shouldn’t? Are there any phantom users (users who have lost their connections)?

 

Reorganization Reports

 

The following information was taken from OSS note 16083.

Various programs, unrelated to any application, need to be run in most R/3 installations. These reports are responsible for reorganizing or keeping up records no longer needed in the system. If this upkeep process is not maintained, a significant amount of disk space may be used wastefully.

 

These programs typically are run from within the background processing system at periodic intervals. A description of each program describing its function and recommended periodic runtime interval is given below. Most programs require a variant (set of parameters) when running in the background processing system. These variants can be produced from within the ABAP development environment, by choosing Tools Case:Development Program Maintenance ABAP Development.

 

As an added note, correspondence may be noticed between various operating system files and those that require cleaning up from within the R/3 System. These operating system files are located in the /usr/SAP/<sap_system_name>/SYS/global directory, where <sap_system_name> = C21, or PC1 or PC2. It is strongly recommended that these operation system files never be deleted from the operating system level, the removal of which could result in a data inconsistency within the R/3 System.

 

Note: Application-specific reorganization programs are not included in this list.

RSBTCDEL

This program cleans up the background jobs. Typically, this program is used to remove all background job records from the queue that have run successfully and are at least X days old. Various constraints can be defined, in addition to those already mentioned, from within the ABAP programming environment. From within this environment, a full list of input parameters can be seen.

Recommended frequency: During off-peak load hours, every day

Notes: This job should run under the batch administrator privilege to make sure all jobs are deleted, regardless of the client. To delete jobs within a single client, make sure the user does not have the batch administrator privilege.

RSPO0041

This program is responsible for removing spooling objects. Every print request produces a spool object and is archived in case of system failure. These spool objects, printed or not, can then be removed depending upon the input criteria.

Recommended frequency: At least once daily, depending on system load and the number of spool object printouts

RSBDCREO

This program is responsible for cleaning up the batch input session log. If the batch input function of the R/3 System is used, log entries are produced. This program requires a variant.

Recommended frequency: If used, once daily

RSSNAPDL

This program cleans the ABAP runtime error dumps logged from within the system. To make the scheduling of this job easy, a second report called RSNAPJOB exists. The function of this job is to automatically schedule RSSNAPDL to run. The report RSNAPJOB makes two assumptions. The first is that there is already a variant existing called DEFAULT. If this variant does not exist, it must be created. The second assumption is that the repetition period is daily. The initial start time is 1:00 a.m.

Recommended frequency: Daily

RSBPCOLL

This program calculates the job runtime statistics information. A variant is not needed to run this program. The program takes only the periodic jobs that have terminated normally and calculates an average runtime statistic for each job. This data is stored in the transparent database table btcjstat. This table needs periodic reorganization to get rid of any old runtime statistics.

Recommended frequency: Should be run daily depending upon system load

RSBPSTDE

This program cleans the job runtime statistics information. A variant is needed to run this program. This job deletes the statistics that have not been updated since the specified date or number of days.

Recommended frequency: Should be run once a month

RSCOLL00

This program collects performance data across all applicable R/3 servers. No variant is needed.

Recommended frequency: Once an hour

RSM13002

This program cleans the process update requests. No variant is required.

Recommended frequency: Daily

Note: RSM13002 is necessary only if automatic deletion of the process update requests is turned off. By default, this is turned on.

Please adhere to the recommended job names, as listed in the table below, because the naming conventions enable qualified R/3 Basis support to quickly check whether these jobs have been activated in your system.

Summary

Job Name	Program	Variant	Frequency
SAP_REORG_JOBS	RSBTCDEL	YES	DAILY
SAP_REORG_SPOOL	RSPO0041	YES	DAILY
SAP_REORG_BATCHINPUT	RSBDCREO	YES	DAILY
SAP_REORG_ABAPDUMPS	RSSNAPDL	YES	DAILY
SAP_REORG_JOBSTATISTIC	RSBPSTDE	YES	MONTHLY
SAP_REORG_UPDATERECORDS	RSM13002	NO	DAILY
SAP_COLLECTOR_FOR_JOBSTATISTIC	RSBPCOLL	NO	DAILY
SAP_COLLECTOR_FOR_PERFMONITOR	RSCOLL00	NO	HOURLY

 

Note: SAP_COLLECTOR_FOR_PERFMONITOR was previously called COLLECTOR_FOR_PERFORMANCE_MONITOR.

 

Note: Batch input reorganization may not run at the same time as normal batch input activity. The associated job must be scheduled for a time at which no other batch input activity is scheduled.

 

Note: Job SAP_REORG_UPDATERECORDS is only required when automatic delete of update records after their processing has been deactivated. This is not normally the case, however, because automatic deleting is the default setting. This function is controlled by the profile parameter delete_after_execution.

 

Note: To eliminate ABAP dumps created by runtime errors within ABAP programs, use RSSNAPDL. To simplify job planning, utilize an additional existing program: RSNAPJOB. This program schedules RSSNAPDL within a job. Implicit assumptions:

• Job name: RSSNAPDL
• Variant: DEFAULT (must therefore exist)
• Start time: early, 1:00 a.m.
• Repeat interval: daily

 

Added Notes Concerning Individual Clients and Authorizations

Some of the jobs specified work with client-specific objects (for example, jobs). Whether reorganization then has any cross-client influence normally depends on particular authorizations. The following table gives an overview.

 

Job Name	Client-specific
SAP_REORG_JOBS	Yes
SAP_REORG_SPOOL	Yes
SAP_REORG_BATCHINPUT	Yes
SAP_REORG_ABAPDUMPS	No
SAP_REORG_JOBSTATISTIC	No
SAP_REORG_UPDATERECORDS	No
SAP_COLLECTOR_FOR_JOBSTATISTIC	No
SAP_COLLECTOR_FOR_PERFMONITOR	No

 

Note: Jobs that are not client-specific perform a reorganization in all clients affected. They require neither special authorizations nor a special user name.

 

Note: Job SAP_COLLECTOR_FOR_PERFMONITOR is always scheduled in client 000 with user DDIC.

 

For client-specific jobs, note the following correlations:

 

• SAP_REORG_JOBS: Authorization S_BTCH_ADM = ‘N’
  Authorization S_BTCH_JOB-JOBGROUP = ‘*
• S_BTCH_JOB-JOBACTION = ‘DELE’
  (Reorganization only in the client in which the actual job is running)
  Authorization S_BTCH_ADM = ‘Y’
  (Reorganization in all clients)

 

• SAP_REORG_SPOOL: Authorization S_ADMI_FCD-S_ADMI_FCD = ‘SPAD’
  Reorganization runs in chosen client
  (Client = ‘*’ then in all clients)
  Authorization S_ADMI_FCD-S_ADMI_FCD = ‘SPAR’
  (Reorganization only in the client in which the actual job is running)

 

• SAP_REORG_BATCHINPUT: Authorization profile S_BDC_ALL
  (Reorganization only in the client in which the job is running)

 

Additional Comments

The authorizations always relate to the user under whose ID the job is being processed.

If this user has the necessary authorizations to work independent of the client, then it does not matter in which client the actual job is running.

Examples

User ADMIN has the authorization S_BTCH_ADM = ‘Y’. If job SAP_REORG_JOBS is now scheduled with user ADMIN, the jobs are reorganized in all clients.

User REORG has the authorization profile S_BDC_ALL. If job SAP_REORG_BATCHINPUT is now scheduled with user REORG in client 002, the batch input objects are reorganized in client 002.

If job SAP_REORG_ABAPDUMPS is scheduled in any client, all ABAP short dumps are reorganized in all clients.

User SPOOLADM has the authorization S_ADMI_FCD-S_ADMI_FCD = ‘SPAD’. If job SAP_REORG_SPOOL is now scheduled with user SPOOLADM and client 123 program parameters are specified, then the spool objects in client 123 are reorganized irrespective of the client in which the actual job is running. With client value ‘*’, all clients are reorganized.

References to related OSS notes

0005855 Job logs occupy a lot of storage space

0006604 Deleting job logs at operating system level

0007224 Deleting old corrections and transport requests

0009419 System shutdown at 31000 spool requests

0011070 Space requirements of TemSe and spooler

0016513 File system is full – what do I do?

0018307 Batch input logs and reorganization

0019706 Tuning the Spooler

0031927 file l_outfilename – L_RETURNCODE 8

0041547 How does report RSPO0041 work?

0048400 Reorganization of TemSe and Spool

 

SAP Database Administration

The SAP database administration involves the administration activities of the SAP database primarily through SAPDBA  SAP’s proprietory database administration tool and very rarely through native  database  tools. Since the SAP Servers at Subros Ltd are all on Oracle database so the activities would describe  all Oracle related  administration  issues .

Tool: SAPDBA

 

 

Activity	Frequency	Objective of the activity
Using SAPDBA to execute the report  tablespace administration à  Free space And fragmentation	Once daily	To proactively monitor for any future freespace problem in any tablespace, and minimise fragmentation
Using SAPDBA to check system integrity selecting db check verificationà DB system check  or à DB verification using DB verify	Once weekly	To  check databse structure and  verify that there is no oracle Block corruption. Also it confirms that the all the datafiles And control files and log files is safe and in proper place.
Using SAPDBA to check statistics by selecting Additional functionsàdb optimizer control panelà Show all statistics information or check for new statistics or Create missing statistics for tables and indexes	Twice weekly	To enhance the database performance
Using SAPDBA to add a datafile to a tablespace by selecting Tablespace administrations à Alter tablespaces and add datafile	As and when required	To add freespace (max 2GB) to a tablespace facing freespace problem
Using  SAPDBA to Check extent wise fragmentation By selecting Reorganization à check extents and fragmentation	At least twice a Week	To get a picture of the free space and fragmentation  table and extent wise

 

Apart from the SAPDBA menu  sapdba should be run  from the OS prompt with the  following switches .  For details refer “Starting SAPDBA : SAP Help : BC SAP Database Administration : Oracle”.

 

sapdba  –analyze

 

• -check : Generates a log with

• Storage statistics for all tablespaces
• A log of the database structure
• Information on the file systems used by the database

The information in this log gives a very good overview of your database system. You can influence the statistics output Critical number of new extents to be checked: <n> (<n>: number of extents) by defining a number of extents when you start the check run ( sapdba -e <number of extents> -check ), so that the check is against a value which corresponds to your requirements and not against the proposed value 2. You should start the check function weekly, if possible as a background process

 

sapdba –analyze

• -analyze <tablespace(s)|table(s)|<file>|<key_word> : Determines the storage situation in the specified table or tablespaces, and the 20 tables and/or 20 indexes of each tablespace specified that have the most freespace. The ORACLE command on which it is based (ANALYZE <object> COMPUTE/ESTIMATE STATISTICS) is also used during reorganization ( Reduce object size) and when creating current statistics for the DB Cost-based Optimizer (CBO).

 

sapdba –next

 

• -next <tablespace/s> : Alters the NEXT parameters when necessary.

 

sapdba –startup

 

• -startup : Normal startup of database.

 

sapdba –shutdown

 

• -shutdown : Shutting down the database.

 

 

Please note that since the production server is ruunning in an archive log mode so  the filesystem  /oracle/<SAPSID>/saparch should be  monitored  Constantly and accordingly brbackup and brarchive should be scheduled.

 

Other Network ,OS and SAP tool related issues

 

Though Network , OS and SAP tool related administration issues can  be  monitored from the R3 frontend itself  but intervention is needed at the OS level  from time to time . Some  tools that are mentioned here  are  tp, R3trans , R3chop.

 

SAP Tools

 

Activity	Frequency	Objective of the activity
tp addtobuffer  <change request > <SID>	As and when required	To add a change request to buffer for importing into the database
tp showbuffer <SID>	As and when required	To display the contents of the buffer and status of the change requests imported into the buffer
tp delfrombuffer <change request> <SID>	As and when required	To delete the change request from the buffer
tp import <change request> <SID> <clientXXX>	As and when required	To import the contents of the change request into the database
R3trans –w logfile.txt –u inputfile.ctrl	As and when required	To delete a client; the inputfile.ctrl contains the commands for client deletion; logfile.txt is used for recording the logs of the action
R3chop  -ecs or ics from pipe Or to pipe	As  and when required	While exporting or importing a large client beyond 2GB

 

 

Os related commands for administration

 

Process Status            :           ps –aef

File System Status      :           df –k

Vertual Memory          :           vmstat

 

Swap Space               :           swap –s

 

 

Note : Check for existence of any core file in the /usr/sap/<SID>/DVEBMGS00/work and remove them immediately.

 

Network Related Issues

 

In case there is a connectivity issue then the following should be done

 

1. Ping the server to see whether the  server is reachable.

1. Check the IP address of the SAPGUI icon .

3. See whether the proper SAP message server and gateway processes are running or not.
4. If all the above steps are OK then check whether the hub is reachableand proper route add entries are there in the route table. Possibly one can check that by   netstat –nr  or contact Network support group of  your organization.

1. What is the parameter to view the log file?
   1. Parameter rslg/<parameter>

 

2. What is the difference between the log configurator and log viewer
   1. Log configurator sts the severity levels

 

3. How does the RCM talks to the dispatcher
   1. Through Memory Pipes

 

4. What does the data collector contains
   1. The data collector contains the alters of the application server

 

5. Beside a composite role you can not have another composite role
   1. True

 

6. What is an SAP router
   1. A table saptouttab contains entries with permissions Permit/Deny

 

7. Log files are available even if SAP Web AS Java is not running
   1. True / False

 

8. When SAP WEB AS Java is down, the log files are still available in the OS

 

9. If you have too many SAP Java instances in different systems, why do you require a central log for Database
   1. Prerequisite for a central log is identifying one system for the central log. It makes sense to have the database central log also, otherwise the database generated logs will be available in each Java instance. To avoid this, it makes sense to have a central log for database. Central log can be configured for Java Only, Even if you have ABAP+Java, you can configure the central log only for Java

 

10. Difference between logging and tracing
    1. Log is generated even during normal operation
    2. Trace has to be enabled

 

11. What is the table that store the monitoring data from ABAP
    1. MONI

 

12. What are the trace settings available
    1. 0 – No trace
    2. 1 – Errors only
    3. 2 –  Errors and Warning only
    4. 3 – Errors, warnings & information such as alloc & Malloc

 

 

 

13. For debugging Java application, what tool do you use
    1. Application trace is required
    2. You need to restart the Java cluster for byte code marking – verify the answer

 

14. What is the purpose of the Log Manager

Or the Porperty databselogs_init_attempts=20, what does it mean

1. During Instance Start Up if the database is down, the log manager will wait for 20 secs before generating the log.

 

15. Not all Java  Applications can be measured for response time
    1. True

 

16. The location of the log files is based on severity levels
    1. True

 

17. What is JVM
    1. JVM executes the platform independent bytecode generated by the Java Compiler on the relevant hardware

 

18. What is the purpose of bootstrap.properties and instance.properties
    1. These are profile files which are imported while starting the Java instance

 

19. What are the SAP Java Enterprise Runtime  Managers
    1. Log Manager
    2. Ports Manager
    3. Application Thread Manager
    4. Thread Manager
    5. IP Verfication Manager
    6. Connections Manipulator
    7. Locking Manager
    8. Configuration Manager
    9. Class Loading Manager
    10. Cluster Manager
    11. Service Manager

 

20. What is JMX?
    1. Java Management Extension (explain in detail)

 

21. While installing Java support package, the RFC destination user is the ABAP user who is used to connect to the ABAP schema to perform support package installation on Java schema. This scenario is applicable for ABAP+JAVA stack only.  If you have Java schema only then the RFC destination user is not called

 

22. SDM has the deployed version of the Java Programs and Applications.  While applying support packs on SDM, the SDM has to be brought down.  This is called stand alone mode.  When SDM is down, you can not log on to the Java instance

 

23. What is the user which comes in between UME and ABAP user administration?
    1. SAPJSF

 

24. Where is the trace file stored
    1. usr\sap\<SID>\>INSTANCE>\work

 

25. The administration user for SAP Web AS with ABAP & JAVA is
    1. sapjsf
    2. j2ee_admin_sid
    3. j2ee_admin

 

26. The administration user for SAP Java only
    1. J2ee_admin_sid

 

27. ITS is still required because ICM does not support certain programming models especially when certain customers have browser based applications (ITS 3.1G).

 

28. What is the administration tool for ICM?
    1. SMICM

 

29. Create ________________________ only for problems, transfer as little as possible

 

30. If  ICMAN is running in the process id of windows / unix it means icm is running

 

31. What is ICM log file
    1. Dev_icm.log

 

32. What is ABAP dispatcher log file & Java dispatcher log file
    1. Dev_disp and dev_dispatcher

 

33. How communication between ABAP work does processes and ICM happens?
    1. Through Memory Pipes

 

34. What are the administration tools for ITS?
    1. Wgate and Agate
    2. For Integrated ITS you do not require Wgate and Agate

 

35. What is SAP Business One
    1. Application used for Small & Medium Enterprises

 

36. CMS is a part of Java Change Management &

CTS is a part of ABAP Change Management

 

37. How do you transport an object that has been saved as saved as a local object
    1. Assign the same to a transportable package

 

38. Support packs are also dependent on tp, so what transport routes do they take?
    1. SAP Transport routes

 

39. What is the difference between a change request and a transport request?
    1. A change request which is released is called a transport request

 

40. In which all clients you need to schedule RDDIMPDP as event periodic job

 

000	000	000
100 (Cust)	400 (QTST)	600 (PRD)
200 (UT)	500 (TRNG)
300 (SAND)

 

1. Except SAND box, you need to schedule RDDIMPDP as event periodic in all clients.

 

41. Tp creates log files like ULOG, SLOG and ALOG.
    1. (read about these logs)

 

42. What are the Java monitors
    1. (read)

 

43. How are Java applications monitored?

 

44. Where are the ABAP Dumps stored?
    1. Table SNAP

 

45. How many generations are there and what happens when the max size is reached?
    1. Young generation
    2. Tenured generation
    3. Perm generation

 

46. What are the different Dialog Work Process Status
    1. Running
    2. Waiting
    3. Stopped
    4. Hold
    5. PRIV

 

47. A hit ratio of 99.99% means the size of the database buffer is optimal?
    1. True / False ( and why?)

 

48. What is the command used for calling external programs
    1. Sapxfg (verify)

 

49. What is default location of the SQL TRACE?
    1. \DATA directory

 

50. The files are exported in which format?
    1. R3trans format

 

51. Who creates the spool requests? Who creates the output request?
    1. Spool requests are created by the Dialog work process and
    2. Output requests are created by the Spool work process

 

52. How many Enqueue work processes can you have?
    1. You can have more than one enqueue work process in an SAP system but SAP recommendation is to have only one

 

53. Give the following port numbers
    1. Message Server    3600
    2. Dispatcher            3200
    3. Gateway               3300
    4. SAPlpd                 515*
    5. SAProuter          3299
    6. Niping                  3298
    7. Oracle                  1527

 

54. How can you change the trace level of the developer trace without system restart?
    1. Default trace level is 1
    2. Go to SM50, choose the dialog work process,

1. Process > Trace > Dispatcher > Change Trace Level

 

55. What is table logging?
    1. Table logging provides an audit of the customizing changes

 

56. What is Development Class?
    1. Development Class is the former name for the Packages

 

57. The default source for WEB AS 6.40 is UME?
    1. True
    2. False

• What is client 000 in SAP R/3?

Client 000 is defined as the SAP standard and the customer cannot change it. This client serves as a copy template for the creation of further client

 

• What are the different type of work process ?

The following work process in SAP R/3

• Dialog (D): each dispatcher needs at least 2 dialog work processes (not shown above)
• Spool (S): at least 1 per R/3 System (more than 1 per dispatcher allowed)
• Update (V): at least 1 per R/3 System (more than 1 per dispatcher allowed)
• Background (B): at least 2 per R/3 System (more than 1 per dispatcher allowed)
• Enqueue (E): exactly 1 per R/3 System (only 1 E work process is required and allowed)

 

• How do you start SAP R/3?

To start R/3, run the shell script startsap from the home directory of user <sid>adm.
startsap starts the saposcol process, which is the statistics collector for operating system resource data, if it is not yet running.

• startsap calls the script startdb, which starts the database if it is not already started.
• startsap then starts the central instance.
• The R/3 System administrator can start additional instances and application servers. To start the instances independently of the database, use the script startsap.
• startsap has the following options:
• startsap r3: Checks if the database is running; if it is, only the instance is started
• startsap db: Starts only the database
• startsap all: Default entry; starts both the database and the R/3 instance

 

• In what sequence are profile parameter read?

R/3 processes read the appropriate parameters from a C source in the R/3 kernel

• The default profile /usr/sap/<SID>/SYS/profile/DEFAULT.PFL is read; profile values already defined in the C source are replaced with the values in the default profile
• The instance profile /usr/sap/<SID>/SYS/profile/<SID>_<instance>_<hostname> is read; profile values already defined in the default profile or in the C source are replaced with the values defined in the instance profile
• This procedure ensures that system parameter values reflect the instance profile and the values in the default profile and the C source.

 

• What are the step involved before stopping R/3 system?

Before stopping any R/3 system following steps are basic steps to be performed.

• Before the R/3 System is stopped, the R/3 System administrator should check the:
• Check if any background jobs from any application server are active or have been triggered externally. Use transaction SM37
• Check if the background work process BTC is running in any application server.
• Check if any update records are open when the system is stopped, the records are rolled back and set to status init. At startup, the records are processed again.
• The administrator must decide whether to interrupt the jobs or wait until they are finished.
• Give system users advance warning of the system shutdown. To create a system message, you can use transaction SM02.
• Before shutting down the system, use transaction SM04 to check whether users are still logged on, and ask them to log off.
• The R/3 System administrator and administrators of external systems should also inform one another about data transfers between their respective systems.

 

• How do you check the work process from UNIX?

Use the following commands.
To check all the work processes:
ps -ef | grep <SID> | grep dw
To check the message server:
ps -ef | grep <SID> | grep ms

To check the SAP OS collector:
ps -ef | grep sapos

 

• How do you display the server name?

To display the server name, use transaction SM51. Information about the process types is also displayed. For further information, select one of the instances and choose Processes. Alternatively, to display the system processes, use transaction SM66.

 

• How do you display all active users in your system?

To display the overview of all active users on the instance where you are logged on, use transaction SM04. For a user overview of the whole system, call transaction AL08.

 

• Q. What happens to locks when the enqueue server is restarted?

A. If they have not been saved to disk in the backup file, they will be lost. The locks that are inherited by the update task when COMMIT WORK is executed after CALL FUNCTION .. IN UPDATE TASK are saved to the disk. The locks are saved to disk when the update request becomes valid, that is, with the COMMIT WORK. Each time the enqueue server is restarted, the lock entries saved on the disk are reloaded to the lock table. A lock is saved to disk at the point at which the backup flag is set.

 

• Q. The enqueue server is a single-point-of-failure in the SAP System. Can I guarantee high availability for the Enqueue Server?

A. To guarantee this you must use the standalone Enqueue Server with the Replication Server. This is described in the documentation Standalone Enqueue Server.

SAP note 524816 contains the prerequisites that must be fulfilled for using the standalone Enqueue Servers with the Replication Server.

 

• Q. Where is the lock table stored?

A. In the main memory (shared memory) of the enqueue server. All work processes on the enqueue server has access to the table. External application servers execute their lock operations in the enqueue process on the enqueue server. Communication in this case takes place via the relevant dispatchers and the message server.

 

• Q. Can locks exist directly after startup?

A. Yes, the saved locks, which were inherited by the update task, are reloaded to the lock table during startup (see first question).

 

• Q. How fast are lock operations?

A. In work processes on the enqueue server, a few 100 microseconds. In work processes of external application servers you have to include network communications and process changes. Depending on CPU and network load this amounts to a few milliseconds.

 

• Q. What should I do first if a problem arises?

A. Use the diagnosis functions:
sm12 Extras ® Diagnosis and then
sm12 Extras ® Diagnosis in update
If a problem is reported, back up the trace files dev_w*, dev_disp, dev_eq* and check the Syslog.

 

• Q. The following message is displayed in the diagnosis details in SM12:

Lock management operation mode
Internal lock management in same process
What does this message mean and what are the other options?
A. “Internal lock management in same work process” in the diagnosis function means that you are logged onto the enqueue server and your work process can access the lock table straight away. You do not have to delegate enqueue requests to an enqueue process on a remote enqueue server. If you are logged onto an application server that is not an enqueue server, the diagnosis function will provide you with the name of the enqueue server.
Each SAP System has exactly one application server that functions as an enqueue server. This enqueue server maintains the lock table, which is located in a shared memory segment. All of the work processes on the enqueue server can access the lock table. All work processes on other application servers delegate their enqueue requests to a special enqueue work process on the enqueue server.

This procedure is configured automatically. The parameter line “rdisp/enqname =<application server name>” in the default profile DEFAULT.PFL indicates which application server is currently acting as the enqueue server. When an application server detects that its name matches the name of the enqueue server, it creates the lock table and all of its work processes process enqueue requests inline. If an application server detects that its name does not match the name of the enqueue server, it sends all enqueue requests to the enqueue server.
Work processes of the type “enqueue” guarantee that incoming requests are processed immediately. One enqueue process is usually sufficient. In very large SAP Systems with many application servers, a second process can be beneficial. However, it is not expedient to define more than two enqueue processes. If the transaction SM50 -> [CPU] shows that only the first enqueue process is being used, the bottleneck is due to something else.

 

• Q.Why is an enqueue work process required in a central system? Don’t all work processes have the same access to the shared memory and thus to the lock table?

A. Although the enqueue process is not used in a central system, it does not do any harm. Since almost all customers install an application server sooner or later, problems will inevitably arise if the enqueue process is missing. For this reason, the enqueue diagnosis function will output an error if an enqueue process has not been configured.

 

• Q. Are the locks in the lock table also set at the database level? If not, database functions could be used to process objects locked in the SAP system.

A. Locks are not set on the database. The lock table is stored in the main memory of the enqueue server.

 

• Q. Is a lock table built if an enqueue work process is not started on the enqueue server in the instance profile?

A. Yes, because the work processes on the enqueue server use the lock table directly, and not via the enqueue process. The latter is only responsible for lock requests from external application servers.

 

• Q.How can I find out who is currently holding the ungranted lock? In other words, how can check the program after an ENQUEUE to determine which use is currently holding the lock so that I can let him or her know?

A. When the ENQUEUE_… function module is returned, the name of the lock owner is listed in SY-MSGV1.

 

• Q. Can I use special characters in my lock argument (especially the ‘at’ sign (@))?

A. The ‘at’ symbol is used as a wildcard in SAP locks (enqueues). In other words, it can stand for any other character during collision checks. For example, the parameter value 12345@ locks the quantities 123450 to 123459, 12345a to 12345z, and 12345A to 12345Z, and all other values with any special character in the 6th character position.
This is described in detail in the section Lock Collisions.
In order to prevent the wildcard mechanism from being activated in SAP locks when it is not required, you need to ensure when enqueue function modules are called that key value parameters do not contain any wildcard characters.
If key values that you want to use to lock individual entities do contain wildcard characters, you have to replace the wildcards with different characters before the enqueue is called.

 

• Q. With a single-process system as an enqueue server, we have reached X SD Benchmark users. Can this number be increased by using a multiprocessor system (message server on the same machine as the enqueue server)? Can we assume that scaling is linear (number of CPUs * X SD users)? How many processes are advisable if message servers, dispatchers, one dialog, and two enqueue processes are to run on the system?

A. A significant increase in the enqueue server throughput can be expected by using several processors. The CPU load on the enqueue server is distributed relatively evenly between message server, dispatchers, and enqueue work processes, which means that up to 3 processors can be occupied simultaneously. Dispatchers and message server represent the bottleneck with the enqueue. Linear scaling can be expected for up to 3 processors, even if lock requests are so frequent that message server, dispatchers, and work processes are occupied simultaneously. Due to asynchronous system processes (for example, syncer), using more processors can further enhance throughput.

 

• Q. The Syslog often contains messages such as “Enqueue: total wait time during locking: 2500 seconds”. How should I analyze this problem? Or is the entry not critical? (There are no records of terminations or timeouts.)

A. The message is output for information purposes only but may indicate parallel processing errors with ABAP programs. The specified wait time is the time that has elapsed since startup due to the use of the WAIT parameter when the enqueue function module was called.
The WAIT parameter enables a lock attempt to be repeated a number of times, for example, so that the update task does not have to be cancelled when a lock is set temporarily by other programs. The work process remains busy between the lock attempts.

 

• Q. User cannot connect to SAP

A. Check SAP logon settings, ping the host, check message server, check dispatcher, etc

 

• Q. User cannot print

A. See if the user has proper authoriztion. check SAP user setup, check SPAD, check spools, check unix queue or print queue at the os level, etc

 

• Q. Why do you get “GetProcessList failed: 80004005” error while starting SAP console management

A. You have selected one of the Process List nodes in the tree. Then you closed MMC and clicked “Yes” in the dialog “Save console settings to SAPMMC?”. Now when you open again the MMC and those processes are not started, you get this error.

Solution: Start MMC and select SAP Systems in the tree. Then close it and choose “Yes” in the dialog “Save console settings to SAPMMC?”. Now you won’t get this annoying error on every start.

1 – Is data written to the Oracle transaction logs (redo logs) before or after the information is written in the database files?

Click on the button next to the right answer.

 

1. A.    Before
2. After
3. Simultaneously
4. The priority and sequence of database writes and transaction log writes is controlled by         the parameter “dblg_after” in the ORACLE initialization file.
5. Randomly, sometimes before, sometimes after.

 

2 – What is the primary function of the $ORACLE HOME/saparch directory?

Click on the button next to the right answer.

 

1. The saparch directory is a work area for the R/3 database utilities.
2. The saparch directory is a work area for the R/3 Instance tasks.
3. The saparch directory is used as the holding area for online database backups instead of writing them to tape.
4. D.    The saparch directory holds the archived database log files.
5. The saparch directory contains the current database transaction log files.

 

3 – Which customer specific specific files does sapdba save during an offline backup to insure that the Oracle database could be restored to a consistent state in case of problems?

Click on the button next to the right answer.

 

1. The Oracle executables files.
2. The Oracle database transaction log files and archived log files.
3. The tablespace data files, database transaction log files, and the database control file.
4. The database archived log files and R/3 Syslog file.
5. The database transaction log files and the R/3 transport structures.

 

4 – Which customer specific files must be saved during an online database backup to be able to restore the Oracle database to a consistent state ?

Click on the button next to the right answer.

 

1. The Oracle executables, database parameter file, and the tablespace data files.
2. The Oracle online redo log files and the database control file.
3. The archived log files, database control file and the Oracle executables.
4. D.    The tablespace data files, database control file, and all database redo logs written during the online backup.
5. The tablespace data files, database control file, and the database parameter file.

 

5 – What is the primary function of the $ORACLE_HOME/sapbackup directory?

Click on the button next to the right answer.

 

1. A.    The sapbackup directory is used for database backups which are written to disk.
2. The sapbackup directory is a work area for the R/3 Instance tasks.
3. The sapbackup directory is the temporary holding area for the database transaction logs (redo logs) before they are automatically written to tape.
4. The sapbackup directory holds the archived database log files.
5. The sapbackup directory is used by the R/3 database utilities during database reorganizations.

6 – What is the name of the brbackup and brarchive parameter file for an Oracle database used by an R/3 Central Instance with SAP System ID C11?

Click on the button next to the right answer.

 

1. initC11.ini
2. initC11.ora
3. C.    initC11.sap
4. sapdba.ini
5. initC11.dba

 

7 – When using a tape device that supports hardware compression which of the following statements is true ?

Note: There is more than one right answer! Click on the buttons next to the right answers.

 

1. The tape_address and tape_address rew init<SID>.sap parameters are automatically calculated based upon the value of the “compression” parameter.
2. Drivers for hardware compression must be specified for the tape_address and tape_address rew parameters in the init<SID>.sap file.
3. C.    The compression ratio is calculated using “brbackup -k only” immediately after installation and should be repeated at least once a month to update compression ratios.
4. The compression ratio should be calculated using “brbackup -k only” immediately after installation and never needs to be repeated.
5. E.    The “compression” parameter should be set to “hardware” in the init<SID>.sap file.

 

8  – Sapdba and the Computer Center Management System (CCMS) use operating system level programs for certain database administration tasks. Which program would be called by CCMS for backing up the data files for the PSAPBTABD and PSAPBTABI tablespaces?

Click on the button next to the right answer.

 

1. Brarchive
2. Brconnect
3. sapdba –b
4. D.    brbackup
5. backoffl

 

9   – What are the 3 different Oracle database startup modes?

Click on the button next to the right answer.

 

1. Warm, cold, maintenance
2. B.    Mount, nomount, open
3. Online, offline, utility
4. Level 1, level 2, level 3
5. Normal, restrict, utility

 

10 – What are the 3 different Oracle database shutdown modes?

Click on the button next to the right answer.

 

1. Warm, cold, maintenance
2. Level 1, level 2, level 3
3. C.    Normal, immediate, abort
4. Regular, active, passive
5. Standard, now, kill

 

11 – What is the primary purpose of the $ORACLE_HOME/sapreorg directory

(Windows NT: $ORACLE_HOME\sapreorg)?

Click on the button next to the right answer.

 

1. A.    The sapreorg directory is a work area for the R/3 database utilities.
2. The sapreorg directory is a work area for the R/3 Dialog Instance Tasks.
3. The sapreorg directory is used as the holding area for online database backups instead of writing them to tape.
4. The sapreorg directory holds the database transaction log files.
5. The sapreorg directory contains the archived database log files.

 

12 – Based upon the information in the initial sapdba program menu, what is the name of the parameter file used by Oracle when the database is started?

The name of the Oracle parameter file is:spfilesid.ora, initsid.ora

Type the correct file name in the field provided.

 

13 – What is the purpose of the Oracle “OPS$connect” function?

Click on the button next to the right answer.

 

1. A.    OPS$connect authorization allows an operating system user to connect to the database without being prompted for a password.
2. OPS$connect is an Oracle command enabling whoever executes it to administer the database without using sqldba.
3. OPS$connect is used in Oracle Parallel Server installations to enable remote database connections over a LAN.
4. OPS$connect authorization is required of all database users and is required for connection to the database.
5. OPS$connect enables the R/3 System saposcol process to communicate and exchange data             with the database.

 

14 – What is the name of the alert log file for an Oracle database using a system identifier (SID) of C11?

Click on the button next to the right answer.

 

1. ora_log_C11.log
2. ora_log_C11.trc
3. C.    alert_C11.log
4. alert_C11.trc
5. orasrv.log

 

15 – What happens if a table wants to allocate another extent but there is not enough contiguous free space in the tablespace?

Click on the button next to the right answer.

 

1. The extent is allocated in another tablespace.
2. The Oracle error message ORA-1653 is sent to the Syslog file and to the ABAP/4 short dump.
3. The extent is distributed across the free space that is available.
4. Oracle dynamically reorganizes the tablespace to make all available space contiguous.
5. The database switches into maintenance mode and sends a system message to the database administrator.

16 – What action needs to be taken when Oracle returns an ORA-1653 error, failure to allocate an extent for a table in a specific tablespace?

Click on the button next to the right answer.

 

1. The tablespace should be moved to a faster disk so that Oracle can find the extents quicker.
2. B.    The tablespace size should be increased by adding 1 or more datafiles.
3. This is an Oracle internal error message which should be registered with Oracle immediately.
4. The database must be shutdown immediately to avoid damage.
5. The affected table should be dropped to avoid similar problems in the future.

 

17 – Under which circumstances does a table/index have to be reorganized?

Click on the button next to the right answer.

 

1. If the extents belonging to the table/index are distributed across several data files.
2. If a log switch occurs before a database commit is completed.
3. If the tablespace overflows during a redo log file switch.
4. If an archiver stuck situation occurs during a write to the table/index.
5. E.    If the table/index reaches the upper limit for the MAXEXTENTS parameter value when attempting to allocate another extent.

 

18 – Which Oracle component dynamically maintains information about the status of the database redo logs, database mode, names and paths of database files, and is essential during a database recovery?

Click on the button next to the right answer.

 

1. The Oracle parameter file, init<SID>.ora.
2. Each tablespace data file contains this data for the whole database.
3. C.    The Oracle control file, cntrl<SID>.dbf.
4. The SGA definition file, sgadef<SID>.def.
5. The sapdba parameter file, init<SID>.dba.

 

19 – An Instance error occurs when 1 or more Oracle background processes become corrupted. What actions should the database administrator take to correct the problem?

Click on the button next to the right answer.

 

1. This is a serious error. Call the Oracle hotline.
2. Shutdown the operating system and reinstall the Oracle software.
3. C.    Shutdown abort and startup open. The SMON process will use the current redo log files and checkpoint information from the control files to execute an automatic instance recovery upon database startup.
4. Shutdown the operating system and turn all hardware off. After the hardware cools off start everything up again and execute Orainst using the repair option.
5. Restore all missing files, apply the offline redo logs, update the control files, and execute the startup open command.

 

20 – Which files must be restored from tape to allow a full database restore and recovery ?

Click on the button next to the right answer.

 

1. Database control file, tablespace data files, and the database alert log.
2. B.    Tablespace data files, database control file, and all archived database transaction logs created since the last full backup.
3. $ORACLE_HOME, Oracle parameter file, tablespace data files.
4. Database control file, tablespace data files, R/3 Syslog, R/3 Transport directory.
5. Oracle parameter file, tablespace data files, and the Oracle control file.

 

21 – The R/3 System Oracle database has 4 online redo logs, also known as database transaction logs. Each online redo log has a mirrored copy. What is the effect of a log file switch?

Click on the button next to the right answer.

 

1. The current online redo log gets copied to its mirrored copy, upon completion the next online redo log becomes open for writing.
2. The database alternates between writing to the online and offline redo log files.
3. The database switches between writing to the original redo log files and the mirrored redo log files.
4. The current R/3 Syslog file gets copied to the saparch directory and a new Syslog file is created.
5. E.    The current online redo log gets closed and the next online redo log gets opened for writing. The ARCH process gets triggered to begin backing up the recently closed redo log.

 

22 – Which statement is true of online Oracle database backups ?

Click on the button next to the right answer.

 

1. Users may only read data and may not enter data until after the backup is done.
2. Database transaction logs (online redo logs) are not written during online backups.
3. The tablespace data files and control file comprise the complete online backup and are all that is necessary for restoring the database to a consistent status.
4. The database must be running in archivelog mode.
5. Online database backups are not supported by Oracle.

 

23 – Given Oracle database with system ID C11. If tablespace PSAPBTABD has been extended 200 MB by adding another datafile which of the following statements is true?

Click on the button next to the right answer.

 

1. In the event of a full database restore the new tablespace data file will be automatically created based upon information in the initC11.ora file.
2. All data files for PSAPBTABD should be backed up along with the database control file to maintain database recoverability.
3. The database should be shutdown and started up again to register the existence of the new file in the Oracle internal system tables.
4. D.    The data files for PSAPBTABD, the control file, and the redo logs must be backed up to maintain database recoverability.
5. An R3INST database copy should be run to create a clean copy of the complete database.

 

 

24 – What is the highest priority when planning the distribution of the database transaction logs, mirrored transaction logs, archived transaction logs, and tablespace data files over multiple logical device groups?

Click on the button next to the right answer.

 

1. Better performance through more hardware.
2. More flexibility in case of hardware failure.
3. Easier database backups and quicker restores.
4. Higher data security and easier administration.
5. To make the system physically more modular for transport reasons.

25 – Which of the following oracle parameters should never be modified in the init<SID>.ora file?

Note: There is more than one right answer! Click on the buttons next to the right answers.

1. db_block_buffers
2. B.    db_block_size
3. C.    db_name
4. controlfiles
5. shared_pool_size

 

26 – Which of the following configurations would have the slightest impact upon data security and/or performance?

Click on the button next to the right answer.

 

1. Operating system swap and Oracle tablespace data files installed on the same physical disk(s).
2. B.    Operating system swap and SAP kernel (executable files) installed on the same physical disk(s).
3. Operating system swap and Oracle database transaction logs (redo logs) installed on the same disk(s).
4. Operating system swap and the /usr/sap directory on the same physical disk(s).
5. Oracle database archived log files (offline redo logs) accessed over a shared (or NFS) directory connection.

 

27 – The physical separation of database logs from their mirror copies means?

Click on the button next to the right answer.

 

1. Using physically separate partitions of a physical disk.
2. Using physically separate disks.
3. Using physically separate disks in the same logical device group.
4. Using generic database utilities to split the flow of data between randomly chosen operating system directories.
5. Use of database specific utilities to fork log backups to 2 physically separate backup media.

 

28 – Which of the following Oracle parameters should be modified in the init<SID>.ora file to enlarge the shared memory usage for the Oracle database instance?

Note: There is more than one right answer! Click on the buttons next to the right answers.

1. log_archive_dest
2. db_block_size
3. rollback_segments
4. D.    shared_pool_size
5. db_block_buffers

 

29. brbackup tool can create a database backup when the database is up and running or when it has been shutdown. During an online database backup which of the following is TRUE? Click on the button next to the right answer.

 

 

A. Users must stop entering data but may continue working using read-only transactions.

B. Users must stop working because their work would be unrecoverable in case of problems with the backup.

C.Users may continue working without interruption.

D.Power-users may continue working but data-entry users must log off.

E.Users must log off until the online backup is started but then may continue working

 

30. Which of the following statements are correct in regard to using a single run of         BRBACKUP to save both the database files and the offline redo log files?

Note! More than one answer is correct. Please click on the buttons next to the correct answers.

1. BRARCHIVE is started immediately after the database backup is complete: no further intervention by the database administrator is necessary.
2. This technique can only be used for offline database backups, not online backups.
3. C.    The database backup and the backup of the offline redo log files must fit on one tape because changing tapes is not supported.
4. You can backup the database using multiple tape devices in parallel.
5. The tapes used must have been initialized by BRBACKUP.

 

 

31. What happens during the startup of an Oracle database?

Note! More than one answer is correct. Please click on the buttons next to the correct answers.

1. A.    The SGA is created in shared memory according to the parameter settings in the configuration file init<SID>.ora.
2. The Oracle background and shadow processes are created.
3. C.    In the mount phase, all copies of the control file are opened.
4. If necessary, Oracle automatically performs an instance recovery.
5. As the last step, the online redo log files are cleared and the data files are opened.

 

32. What happens during the shutdown of an Oracle database?

Note! More than one answer is correct. Please click on the buttons next to the correct answers.

1. When you shutdown the database with the NORMAL option, the database system disconnects all users before shutting down the database.
2. B.    When you shutdown the database with the NORMAL or IMMEDIATE option, the database system writes a checkpoint before shutting down the database.
3. When you shutdown the database with the ABORT or IMMEDIATE option, open transactions are rolled back before the database is shut down.
4. When you shut down the database with the ABORT option, the R/3 system is shut down, too.
5. E.    Shutting down the database with the ABORT option always requires an instance recovery at the next database startup.

 

33. Which of the following statements express part of the SAP-recommended strategy for creating and updating the table statistics used by the cost-based optimizer?

Note! More than one answer is correct. Please click on the buttons next to the correct answers.

1. No statistics are created for R/3 pool and cluster tables.
2. Statistics are created for all transparent tables that have no statistics.
3. The table DBSTATC can be used to trigger an exact computation of the statistics of specific tables.
4. The update for table statistics refreshes all transparent tables.
5. The table DBSTATC can be used to detect which table statistics need to be refreshed.

 

34. What happens if a table wants to allocate another extent but there is not enough contiguous free space in the tablespace? Click on the button next to the right answer.

 

1. Please click on the button next to the correct answer.
2. The extent is allocated in another tablespace.
3. The extent is distributed across the free space that is available.
4. D.    The Oracle error message ORA 1653 is sent to the file SYSLOG and to the ABAP short dump.
5. Oracle dynamically reorganizes the tablespace to make all available space contiguous.
6. The database switches into maintenance mode and sends a system message to the database administrator.

 

 

35. When the R/3 update task aborts with an Oracle error ORA1653 – failure to allocate an extent for a table in a specific tablespace – what action needs to be taken?

Note! More than one answer is correct. Please click on the buttons next to the correct answers.

1. The tablespace should be reorganized.
2. B.    The tablespace size should be increased by adding a new data file.
3. The table should be reorganized.
4. The storage parameter MAXEXTENTS must be increased.
5. E.    After the cause of the error has been removed, the R/3 update task must be reactivated.

 

36. Which of the following checks are useful for database performance monitoring?

Note! More than one answer is correct. Please click on the buttons next to the correct answers.

 

1. A.    Checking that the CBO statistics are refreshed once a week according to the strategy recommended by SAP.
2. Checking that the archive directory contains enough free space.
3. C.    Checking the data buffer quality.
4. Checking the shared cursor cache for expensive SQL statements.
5. Checking for tables with more than 100 extents.

 

 

 

37. ___________ is used as default user when you can an SAP tool for Oracle administration.

Click on the button next to the right answer.

 

1. A.            SYSTEM
2. SYSDBA
3. SYSOPER
4. SAP<SCHEMA-ID>
5. SIDADM

 

 

38.  Name the standard Database users created in Oracle.

Note! More than one answer is correct. Please click on the buttons next to the correct answers

1. SIDADM
2. ORASID
3. C.    SYS
4. SAP<SCHEMA-ID>
5. E.    SYSTEM

 

39. The recommended method of changing the password of SAP<SCHEMA-ID> is

Click on the button next to the right answer.

 

1. SQL> ALTER USER
2. B.    SAP tool BRCONNECT
3. SQL > ALTER USER
4. SQLPLUS>CHANGE PASSWORD
5. SAP tool BRUSER

 

40. The Oracle tool to test the connection to the database with SID C11 ON HOST twdf0505 is

Click on the button next to the right answer.

1. TNSLISTENER
2. lsnrctl start
3. C.    tnspingC11
4. CONNECT
5. BRCONNECT

 

 

41. Your daily backups are performed with automatic tape selection, no volume for backup is specified. Which tapes will be accepted for backup (assuming the tape lock period is expired in all cases.)

Note! More than one answer is correct. Please click on the buttons next to the correct answers

1. any labeled tape
2. B.    the tape labeled with the volume name you got from DB13, Goto à Tapes needed.
3. C.    A tape labeled with volume name scratch
4. Any unlabeled tape.

 

42. The BR*TOOLS profile init<DBSID>.sap can be edited by;

Click on the button next to the right answer.

 

1. BRBACKUP
2. BRARCHIVE
3. BRTOOLS
4. D.    Operating system editor.
5. None of the above.

43, To perform a complete database reset, you need one of the following backups.

Note! More than one answer is correct. Please click on the buttons next to the correct answers

 

1. A.    complete offline backup
2. complete online backup
3. C.    consistent online backup
4. backup of offline redo log files.

1. itsp/enable = 1

2. For changing which profiles RZ10 s used. Inst/default/start

3. When performing Online backup what should be there. Archival mode on

4. ORACLE_HOME parameter will be where in database,application server.whether it will be user environment or system environment variable.

5. Which parameter can not be changed in init.ora. db_name & db_block

6. No of RFC’s to be created from 2 SAP for accessing 3 clients of target.

7. Integrated Log viewer can be used to do what. change severity

8. Config tool & Visual admin are used combindely used for what. Change parameters for global disp parameters or instance wise.

9. The things which happen automatically when TMS is configured. RFC’s,TMSADM user,etc

10. The Netweaver components SAP CRM,SAP ERP,SAP ECC 6.0.Wrong answer is SAP 4.6c

11. The products offered by SAP. All 4 options (SAP ALL-In-one,SAP Business suite,etc)were given along with 2 wrong options.)

12. Installation post actions (SGEN, SAP Installation check)

13. Where do u see the current support pack of Abap. SPAM & System->status

14. Where do u see the current support pack of Java. Systeminfo.

15. TIME_OUT Error given and gave options. Correct options were the program should be run in background & this program ran for more time exceeded.

16. System status screen shot and asked the DB host.

17 ICM supports what. all the options were correct i.e ICM supports BSP,Integrated ITS,supports JAVA & ABAP. Wrong option was supporting Standalone ITS.

18. Regarding Redolog switch question is what will happen after a redolog switch. Options correct are next redolog file is used and the finished one is     backed to
offline redolog.

19. CCMS alert monitoring is used for ABAP+Java,ABAP,JAVA.

20. Regarding printers. Local printing is used with L and C access methods is the correct option.

21. Regarding CUA the RFC names from child to Central system are given.

22. why do u need  SAP router connection ?

23.what are the basic SP componments (sap_appl , sap_hr , sap_crm)

24.ITS performance param can be dislayed where ? TX SITSPMON

25. what profiles can be viewed in RZ10 of ABAP+JAVA system ? (a.all profiles b.def and start&instance of abap+java except the start&instance of CS of AS JAVA)

26.3 question from SLD connection to solman.(read the roadmaps)

27.a transport domain can have ? 1)only systems in transport group 2)many trans group 3)trans group have common trans dir

28.data sources of UME ?

29.property varients in ABAP monitoring

30.CTS trans (AS JAVA) what is true? (TDC should be NW7 SPS13 )

31.SMTP can have only 1 domain (true) SMTP connects to a MTA (true) SMTP cannot forward to external

32.sap release startgy (5-1-2)

33.Local prnting access methods

34.start sequence in AS java system –> 1)db , java server , disp 2)enqueue , db , disp 3)db,message server , disp (right)

35.ABAP Auth which statement is true -> assign profile to user master (t)

36.the load balancer in AS JAVA –> 1)web disp 2)java disp

37. Between which systems client compare can happen. Between same sap systems,between different sap systems same release,wrong answer is between r/2 & ECC5 systems.

38.in TMS where are the files stored ?Domain.CFG in db & filessytem TP profile only filesystem.

39.What are the different typs of Oracle indexes. Correct options were B Tree index & Bit map index.

40.What is the startup sequence of the SAP system? a)    Database, gateway, dispatcher b)Dispatcher, gateway, database c)Database, dispatcher, gateway

1. Data is written to the Data Files before it is written to the Redo Logs. True/False

2. In an offline backup, what files are backed up?

3. In an online backup, what files are backed up?

4. What are the uses of the sapbackup and sapreorg directories?

5. What are the following files used for?
– init<SID>.sap
– init<SID>.dba
– init<SID>.ora

6. How do you verify corrupt data blocks at least once per Backup cycle?

7. What is the use of the OPS$<SID>adm user in an SAP database?

8. What happens during each of the shutdown options?
– shutdown normal
– shutdown immediate
– shutdown force

9. What happens during each of the startup phases?
– startup nomount
– startup mount
– startup open

10. Explain the 2 phase strategy recommended by SAP for maintaining Optimizer statistics?

11. What is the file to troubleshoot Oracle errors and where is it located?

12. Table and Index Reorganization?

13. If an index or a table is unable to allocate another extent, what would be the error code and the cause of it?

14. Provide a solution to resolve 13 above?

15. Which Oracle file is used during recovery and maintains information about LSNs, etc?

16. What is to be done for an index/table for which the MAXEXTENTS limit has been reached?

17. “Checkpoint not Complete” – Can an archiver stuck situation cause this condition? How about Block Corruption?

18. If a Background Process aborts, what kind of recovery do you initiate after starting up the database?

19. During a log file switch, what is the role of the ARCH process?

20. To run Offline Backups, the database has to be running in ARCHIVELOG mode. True/False?

21. How do you adjust the size of the Shared SQL Cache?

22. How do you adjust the DB_BLOCK_SIZE of your database?

23. Know your SAPDBA Restore & Recovery Menu Paths and available options?

24. Information provided in Report for sapdba -check?

25. Identify the best disk layout for the following files w.r.t to security?
a. origlogA, origlogB, mirrorlogA, mirrorlogB.