01 sap technical operation manual330491328098515

Bharat Aluminium Company Limited

SAP Technical Operation Manual

Author -------: Varun Chawla

Checked By -------: Rina Sriwastwa

Approved By -------: Subrata Banerjee

BALCO SAP Technical Operation Manual

April 1, 2007

Table of Contents

1. Preface1.1 About This Document1.2 How to Use This Document

2. Global System Description2.1 R/3 Systems

2.1.1 Development System2.1.2 Quality Assurance System2.1.3 Production System

2.2 Hardware2.2.1 Desktop Environment2.2.2 Mobile Computers2.2.3 Desktop Operating Systems

2.3 LAN Environment2.3.1 Hardware Topology2.3.2 Network Operating System

3. Maintenance Of Instances3.1 Procedure for Starting Instance3.2 Procedure for Stopping Instance

4. User Access Management 4.1 Procedure for User creation4.2 Procedure for User deletion4.3 SAP R/3 Security4.4 Procedure for User authorization maintenance4.5 User Access Review

5. Transporting Objects 5.1 Procedure For Transporting Layouts

5.2 Procedure For Transporting Requests5.3 Procedure For Transporting Requests at O.S Level

6. Data file Addition6.1 Procedure for Data file addition – Offline6.2 Procedure for Data file addition – Online

7. STMS

BALCO - Confidential

of 116

Version 1.2


April 1, 2007

7.1 Procedure for configuring STMS8. Client copy

8.1 Procedure for client copy9. Parameter Change

9.1 Procedure for parameter change10. Software Logistics

10.1 R/3 System Landscape10.1.1 Policies

10.1.1.1 Development and Testing10.1.1.2 Training10.1.1.3 Upgrade10.1.1.4 Installation

10.1.2 Procedures10.1.2.1 Development and Testing10.1.2.2 Training10.1.2.3 Upgrade10.1.2.4 Installation

10.1.3 Roles and Responsibilities10.2 Upgrading SAP Software Release/System Components

10.2.1 Policies10.2.1.1 Sequence of Systems to Be Upgraded10.2.1.2 Backup10.2.1.3 Adjustments10.2.1.4 Verification

10.2.2 Procedures10.2.2.1 Sequence of Systems to Be Upgraded10.2.2.2 Backup10.2.2.3 Adjustments10.2.2.4 Verification

10.2.3 Roles and Responsibilities11. Backup 11.1 Procedure for Online database backup 11.2 Procedure for Offline database backup 11.3 Procedure for Archive log backup


of 116

Version 1.2


April 1, 2007

11.4 Procedure for rootvg backup 11.5 Procedure for Volume Group backup12 Server Refresh13 Backup Restore 13.1 Database Restore14 Details of initSID.sap15 Details of initSID.ora16 Details of initSID.utl17 List of Transactions performed for a daily system monitoring18. Formats 18.1 User Creation Form 18.2 Transport Request Form 18.3 Profile Parameter Change Requisition

Document Maintenance

Name of the person responsible for maintaining the master copy of this manual:


of 116

Version 1.2


April 1, 2007

NAME DEPARTMENT COMPANY PHONE

Varun Chawla IT Bharat Aluminium Company Limited

+919993003196

The following people play significant roles in capacity planning and/or maintenance of this manual and should be notified of any proposed changes:


S.Siddiqui IT Mumbai Corporate +919867367371

Subrata Banerjee IT Bharat Aluminium Company Limited

+919893022525

Rina Sriwastwa IT Bharat Aluminium Company Limited

+919893101324

The following people have copies of this manual and should be notified of any changes made:


S.Siddiqui IT Mumbai Corporate +919867367371

Subrata Banerjee IT Bharat Aluminium Company Limited

+919893022525

Rina Sriwastwa IT Bharat Aluminium Company Limited

+919893101324

Preface

1.1 About This Document


of 116

Version 1.2


April 1, 2007

This document contains information about R/3 System operation. This information includes system environment descriptions, policies, procedures, and lists of the roles and responsibilities for all relevant aspects of R/3 operation. This document aims to enable SAP customers to document their R/3 System policies, procedures, and responsibilities. For IT managers, this document provides guidelines for implementing the R/3 Basis System.

1.2 How to Use This DocumentThis document is a template for the documentation of R/3 System policies, procedures, and responsibilities. It describes an R/3 landscape with three systems: one Development System, one Quality System, and Production System. This is representative of many real, live customer scenarios.The information can be changed and modified in the tables according to the needs.

Global System Description

2.1 R/3 Systems

R/3 system has three system landscape with separate systems for Development , Quality assurance & Production system


of 116

Version 1.2


April 1, 2007

2.1.1 Development System

In the Development System (Integration System), all SAP customizing takes place, customer objects are developed, and SAP objects are modified. The Development SAP system has SAN storage

Name BALCO DEVELOPMENT SYSTEM ( BDS )

Location BALCO KORBA

Hardware IBM P Series Machine ( 06-244BG )—P520

Operating System AIX 5.3

Database Oracle 10g

R/3 Release ECC 6.0

Patch Level Updated Till Date (83)

Installation Number 0020249835

Active Hardware Key Q1852632850

Customer Number 0000354415

License Key 1SPCZH3K9KHDYIJI78DLDIIE

2.1.2 Quality Assurance System

The Quality Assurance System (Consolidation System) is used to test the objects that were created or modified in the Development System.

It also acts as a training client. The Quality Assurance SAP system has SAN storage

Name BALCO QUALITY SYSTEM ( BQS )


of 116

Version 1.2


April 1, 2007


Hardware IBM P Series Machine ( 06-0799E )—P510


Database Oracle 10g

R/3 Release ECC 6.0



Active Hardware Key V1839177504


License Key YWV1TWPY8Y7S1HRGHGYAJKG4


of 116

Version 1.2


April 1, 2007

2.1.3 Production System

Production System is a production environment of R/3 System where. Realtime business transaction takes place .Production System consists of a database server and an application server configured in cluster with AIX HACMP & SAP HA The production SAP system has SAN storage .All R/3 Systems are linked via a FDDI backbone network.

(a) Database Server Details

Name BALCO PRODUCTION SYSTEM ( BPS )


Hardware IBM P Series Machine ( 06-EDDAG )-P550


Database Oracle 10g

R/3 Release ECC 6.0



Active Hardware Key Y1782407196




of 116

Version 1.2


April 1, 2007

(b) Application Server Details

Name BALCO PRODUCTION SYSTEM ( BPS )


Hardware IBM P Series Machine ( 06-EDD9G )-P550


Database Oracle 10g

R/3 Release ECC 6.0



CIN Installation Y1782407196

Customer Key 0000354415


2.2 Hardware

2.2.1 Desktop Environment

PC/CPU Type NumberPIII 30PIV & Pentium Dual core

800

2.2.2 Mobile Computers


of 116

Version 1.2


April 1, 2007

PC/CPU Type NumberPentium / Pentium dual core /Pentium core2Duo

170

2.2.3 Desktop Operating Systems

2.3 LAN Environment

2.3.1 Hardware Topology

The implemented LAN environment is a 100 MB Ethernet with UTP cabling (unshielded twisted pair)

2.3.2 Network Operating System

The network operating system for the office environment is Microsoft Windows Network OS

Maintenance Of Instance

3.1 Proce d ure for Start ing I n st a n c es BALCO - Confidential

of 116

Version 1.2

Operating System NumberWindows 98 30Windows Xp professional

800


April 1, 2007

St e p s

Login to the database server you want to connect as telnet <IP Addr> / through xbrowser

Enter the userid as login and its password. Give the following command at the prompt #> su – ora<dbsid> To start the listener at the prompt give <dbid>:ora<dbsid> #> lsnrctl

start Give the following command at the prompt and exit from the

prompt <dbid>:ora<dbsid> #>exit Give the following command at the prompt #> su – <sid>adm For starting up of the database at the prompt give

<dbid>:<sid>adm#>startdb Database will be mounted and opened. Login to the application server you want to connect as telnet <IP

Addr> Enter the userid as login and its password. Give the following command at the prompt #> su – <sid>adm For starting up of the central instance services at the prompt give

<dbid>:<sid>adm#>startsap ASCS00 Now at the command prompt of database server give

<dbid>:<sid>adm#>startsap DVEBMGS01 Now at the command prompt of application server give

<dbid>:<sid>adm#>startsap D02

3.2 Proce d ure for Stopping Da t aba s e I n st a n c e

St e p s

Login to the application server you want to connect as telnet <IP


of 116

Version 1.2


April 1, 2007

Addr> Enter the userid as login and its password. Give the following command at the prompt #> su – <sid>adm At the command prompt of application server give

<dbid>:<sid>adm#>stopsap D02 Login to the database server you want to connect as telnet <IP

Addr> Enter the userid as login and its password. Give the following command at the prompt #> su – <sid>adm At the command prompt of database server give

<dbid>:<sid>adm#>stopsap DVEBMGS01 For stopping up the central instance services at the prompt of

application server give <dbid>:<sid>adm#>stopsap ASCS00 For stopping up the database at the prompt of database server give

<dbid>:<sid>adm#>stopdb Database will be closed and unmounted Give the following command at the prompt and exit from the

prompt <dbid>:<sid>adm #>exit Give the following command at the prompt #> su – ora<dbsid> To stop the listener at the prompt give <dbid>:ora<dbsid> #> lsnrctl

stop

User Access Management

4.1 Proce d ure for User c re a t i o n

Policy


of 116

Version 1.2


April 1, 2007

For creation & modification of a User ID in SAP, the user ID creation/modification form is to be filled up duly approved by the core member & division head . The roles to be assigned to the userid must be provided by the business core member . The filled up form is submitted to SAP user administrator . The SAP user administrator after taking approval from basis head creates the SAP user id & assigns the roles provided by the business core member . The user id creation /modification form is attatched in annexure 1.

Nomenclature

For creating a new user ID the standard nomenclature is followed ; (i) For named user ids : The following combinations are considered if similar

named users exists . The options considered in priority as numbers given below :

1. First name + 1st letter of Last name 2. First name + last name 3. 1st letter of First name + Last name(ii) For generic SAP user ids :

The SAP user id is made up of - The first two characters represents the SAP module to which the user belongs. The next two or more than two characters represents the function/roles to be performed by the userFor example the User ID FIAP represents the account payable function in finance module

Ste p s

Transaction code to create a new ID SU01. Type down the name of the user to be created in the User field

appearing on the screen. Click create in the User menu or press F6 to create the user

ID, create user master record screen will appear.


of 116

Version 1.2


April 1, 2007

Give the initial password init06 as a standard; confirm the same in the next field.

Type the user group the user belongs to, like MM, PM etc. Give the validity period if required from and to for the user. Select the type of user like dialog or background. Type the Roles names to be attached to the user which is

created as per the requisition from the key user. Strike “Enter”. The user address details screen will appear. Fill in the First

name and Name fields as per details available. These will also appear in the mails sent by the user.

Strike Enter. Maintain Fixed Values screen would appear. Give the start menu if requested or keep it blank. Give the

default output device the user would use for printing, if specified

Select date format DD.MM.YYYY and decimal notation as “,” (comma) and Print immediately.

Strike Enter. The license details for the user has to be entered --- 1. operational user / requistion & confirmation user / information user / Basis user Click Enter. The User is created now.

4.2 Proce d ure for User deletion

Policy

H.R department conveys through e-mail to SAP User Administrator & basis leader about the exit of an Employee , and then after getting the approval of SAP Basis head the SAP User Administrator deletes the user id from SAP system The HOD for a business function can also advice for deletion of a user .


of 116

Version 1.2


April 1, 2007

In this case the user id creation /deletion /modification form is to be filled up by the core member / HOD duly approved by HOD

St e p s

Transaction Code Su01. Type the User ID to be deleted in the User Field. Click Delete in User menu or press SHIFT+ F2. A confirmation will be asked by the system, click Yes. It will ask mail user will also be deleted, confirm Yes. The user will be deleted. Delete all the scheduled background jobs of the deleted user .

User profile modifcation

4.3 SAP R/3 security

Policy for password management

There is a forced change of password on first logon . In case the user administrator resets the password of the user , in that case also the system asks for the change password .The user has to provide password


of 116

Version 1.2


April 1, 2007

as per the parameters defined in profile

User locks While working in the system if the user gets locked because of the R/3 security defined , the user has to send the request for unlocking the userid through mail to the user administrator If the user gets locked because of R/3 security policy , the user administrator unlocks it & conveys it back to the user . The basis leader also locks the user id if the id is not being used for a period of 2 months .The same is conveyed through email to the business core member / HOD .

Login through SAP GUI logon pad access control can be improved by changing the following SAP profile parameters

Rdisp / gui_auto_logout = 1800 By making this change the user connection is closed after 30 minutes of without usage

login / fail_to_user_lock = 5 By making this change the SAP user is locked after making 5 wrong attempts.

login / fail_to_session_end = 3 By making this change the SAP connection is automatically closed after making 3 wrong attempts by the user.

Login / min_password_lng = 6By making this change the SAP system only excepts the password with at least 6 characters

Login / password_expiration_time =90By making this change the password given gets expired after a period of 3 months


of 116

Version 1.2


April 1, 2007

List of core members

Authorization Maintenance

4.4 Proce d ure for User a u t h o r izat i on m a int e n an ce

P rerequ i sites

In case of a new Authorization requirement the SU53 screen for the object and object class details is required from the Key User and the approval of core team is required . In case of a cross plant code authorization approval of core team member and HOD IT is required. In case of authorizations given on temporary basis the mail printout should be filled along with note of the authorization given and revoked details.

S t eps


of 116

Version 1.2


April 1, 2007

If new Role to be created for user naming should be like Z_specificrolename.

Select the user specific role by using SU01 transaction code and going to change mode.

Copy the user specific role and call transaction pfcg. Paste the user specific role name and click the change button

.Then the new screen will appear. Select the authorization button and then change the auth. data.

Select the Object class to be changed. In case of new Object class, which is not present in the tree click, insert manually.

Expand the node to go to specific object under that class. Select the node and click insert in case of new object

being inserted. The object will come to change tree under the specific object class.

Expand the object node to get the fields under that object. Change the fields according to the user requirements by

double clicking the field and maintaining the values in maintaine field values window which appears on double clicking the field.

Click enter. The field values are now inserted to the field. Click on generate button to generate the role. The Authorizations are now maintained in the role, which is

attached to the user. User should log on to be able to use the new authorizations.


of 116

Version 1.2


April 1, 2007

4.5 User Access Review

The users being created into the SAP system by the basis administrator after the approval of concerned core team member and departmental H.O.D. are being reviewed by the Basis Administrator head .Then after a period of six months a user access review is being performed in terms of their authorizations of the user according to transactional level ie what all authorizations they have according to the segregation of their duties being defined by the respective core team member. Then the review list is being provided to concerned core team member for their approval and if any changes pointed out are being taken into account and necessary changes if to be made is being performed.


of 116

Version 1.2


April 1, 2007

Transporting Objects

5.1 Proce d ure For Tr a n s por t i n g La y o u ts

Policy

For transporting a layout set from qa server to production server. The layout set should be sent in required format called Transport request form with proper details of the layout set by key user. Then it is examined by the SAP transport administrator and transported after approval from Basis Head. From development server to qa server layout set will be transported by SAP Transport Administrator

St e p s

Source s y stem/client


of 116

Version 1.2


April 1, 2007

Goto Tools->Abap/4 Workbench-> Abap/4 Editor. ( SE38) Enter RSTXSCRP program and execute. By default object form is selected. Type the layout set name against object name. Select EXPORT in Mode (default). In ctrl parameters for file operation select “from / on front-

end “ ( by default it is selected ) A screen displays to enter file name. Input file name (same as layoutset name) and store in a pc. Press enter. See the result “object was exported “. The object is exported

in a file on the local pc in working directory.

Target S y s t em/client

Goto Tools->Abap/4 Workbench-> Abap/4 Editor. ( SE38) Enter RSTXSCRP program and execute. By default object form is selected. Type the layout set name (request) against object name. Change the Mode to IMPORT. In ctrl parameters for file operation select “from / on

frontend “(by default it is selected). A screen displays to enter file name. Input file name (same as layoutset name) stored in a pc

during export (i.e from source client). Press enter. See the result log message “object imported and activated “.

5.2 Proce d ure F or Tr a n s p o r t i n g R e quests

PolicyBALCO - Confidential

of 116

Version 1.2


April 1, 2007

For transporting request from qa server to production server. The request should be sent in required format called Transport request form with proper details of the request by core user. The request is then released in the development server .Then it is being examined by the SAP transport administrator and transported after approval from Basis Head. From development server to qa server request will be transported by SAP Transport Administrator

St e p s

Call transaction STMS. Select Overview ----> imports or (F5). Select and open respective queue using mouse double click. Use refresh button to refresh the queue. select the request to be transported by using mouse

and then edit ---->select -->select/deselect request ( F9) ( the request will turn yellow in queue)

Once selected the request is to be filtered out of queue as we are importing single request. to do so use edit --->filter, popup for filter will come with request number or Sr. number in queue depending on the selection, select the request.

Now the queue will have only selected requests. The queue is now to be adjusted, for this use queue --->adjust (cntrl + F6) continue in the popup confirmations.

After adjusting the queue the request is ready for import and the same can be done by request ------>import a popup for client entry will come enter the client in to it and confirm the import to STB popup and the request will be imported.

5.3 Proce d ure F or Tr a n s p o r t i n g R e quests at O.S Level

Pr e r eq u isite


of 116

Version 1.2


April 1, 2007

For transporting a request from qa server to production server .The request should be sent in required format called Transport request form with proper details of the request by core user. Then it is examined by the SAP Transport administrator and transported after approval from Basis Head

St e p s

telnet 10.101.71.227 ( DBS Server ) login as <sid>adm and give password . dbs: <sid>adm >cd /usr/sap/trans/data dbs:<sid>adm > ftp 10.101.71.225 press enter , press enter

again as login name is same .Give password now you have ftp prompt .

ftp>cd /usr/sap/trans/data ftp> mget * XXXXXX * , press enter , press y ftp > cd ../cofiles ftp > lcd ../cofiles ftp > mget * XXXXXX * , press enter , press y ftp > bye Call transaction STMS. Select Overview ----> imports or (F5). Select and open respective queue using mouse double click. Go to Extras -------> Other Requests-------> Add Type the Request name as SIDKXXXXXX and press enter Use refresh button to refresh the queue. select the request to be transported by using mouse

and then edit ---->select -->select/deselect request ( F9) ( the request will turn yellow in queue)

Once selected the request is to be filtered out of queue as we are importing single request. to do so use edit --->filter, popup for filter will come with request number or Sr. number in queue depending on the selection, select the request.


of 116

Version 1.2


April 1, 2007

Now the queue will have only selected requests. The queue is now to be adjusted, for this use queue --->adjust (cntrl + F6) continue in the popup confirmations.

After adjusting the queue the request is ready for import and the same can be done by request ------>import a popup for client entry will come enter the client in to it and confirm the import to STB popup and the request will be imported.

Data file Addition

6.1 Proce d ure for D a t a fi l e a ddit i o n – Offli n e

Pr e r eq u isite

It is important to stop the application server instance so that no users can login during this process and after addition start the sap instances immediately.

St e p s

Stop Sap instances of application server. Login as <sidadm> in dbs server <sidadm > brtools select 2 - space management select 1 – Extend tablespace select 3 – tablespace name write the name of the Tablespace Select C – continue Now brspace will be started and ask for continue, back or stop. Select C - continue Suggested values appear like, Size, data file path, size in M.


of 116

Version 1.2


April 1, 2007

If need to be change file size select option 5 and put required value of file size in M.

If need to be change the path of the file then select option 3 and give the new path as /oracle/DBSID/sapdata1-4 and then press enter

Select C - continue It will ask for next datafile can be specified now (for additional

datafile) Select N – for skip it. It will start adding datafile A directory is created for datafile and datafile is added to this

directory After adding datafile and controlfile creation it will ask to

continue, back or stop. Select C- continue Brspace completed successfully. Select C – continue Select b – for back select 9 – exit program Brtools completed successfully. Check the successful datafile addtion by refreshing DB02. Start the instances of application server . ( startsap r3 )

6.2 Proce d ure for D a t a fi l e a ddit i o n – Onli n e

Pr e r eq u isite

Data file addition to a table space should be done when the load and number of users are less in the system.

St e p s

Login as <sidadm> in dbs server <sidname > brtools select 2 - space management


of 116

Version 1.2


April 1, 2007

select 1 – Extend table space select 3 – table space name write the name of the Table space Select C – continue Now brspace will be started and ask for continue, back or stop. Select C - continue Suggested values appear like ,Size ,data file path ,size in M. If need to be change file size select option 5 and put required

value of file size in M. If need to be change the path of the file then select option 3 and

give the new path as /oracle/DBSID/sapdata1-4 and then press enter

Select C - continue It will ask for next data file can be specified now (for additional

data file) Select N – for skip it It will start adding data file A directory is created for data file and data file is added to this

directory After adding data file and control file creation it will ask to

continue, back or stop. Select C- continue Brspace completed successfully. Select C – continue Select b – for back select 9 – exit program Brtools completed successfully. Check the successful datafile addtion by refreshing DB02


of 116

Version 1.2


April 1, 2007

STMS

7.1 Proce d ure for c o n f i g u r ing STMS

Pr e r eq u isites

A fresh STMS configuration is done in two conditions, first when a new SAP instance is installed or secondly when the existing configuration is completely deleted through SE06.

St e ps

When STMS transaction is executed for the first time you can configure Transport system as per your landscape and requirements. The steps to be followed for a standard STMS configurationof a Single system are as listed below.

Execute transaction STMS. A popup window will ask to either choose or configure the

transport Domain. If the instance is a system being added to existing landscape

the domain controller can be selected as required. As of this case the instance is to be configured as single

system configuration so a domain controller is to be created. Select the Domain controller name give description for it and

save. When the popup is closed and you get initial screen of

STMS where you should get the message you have logged in to domain controller.


of 116

Version 1.2


April 1, 2007

As a case of single system configuration we will have to create a virtual system to be used for managing transport.

To create a system go to systems. Go to Systems -------Create -------Virtual system. A pop up window will appear for name and description of the

virtual system. Save the system. Perform activate and distribute the configuration, so that the

configuration is reflected for all the systems. Extras--Distribute and activate Configuration

Go to transport route screen. Select Configuration -----standard Configuration----

Development and Production system. A pop up widow would ask which is dev and which is prod

system. Select the controller system as the Dev system and Virtual

system as production system. Save and again activate and distribute the configuration to all

systems. With this STMS configuration the system is now ready for

generating requests with the virtual system as the target system.

When a transport route is created there should be two transport layers, one would be standard sap layer and one would be a Z transport layer which can be assigned to a package which can be used for doing the developments.

The package can be configured using transaction SE21, while configuring please mention the layer as described above.

In case the new system being configured is to be attached to an existing system then, when the STMS transaction is executed at the first time, select the controller to which the system is to be added. The system will then send request to the controller to accept the system.


of 116

Version 1.2


April 1, 2007

Then go the controller system and accept the new system in the TMS.

Once the new system is accepted to the controller system, the new transport routes should be changed as desired.


of 116

Version 1.2


April 1, 2007

Client copy

8.1 P r ocedure for cli e nt c opy

Pre r equisites

Client copy can be done in one system for different client or from one system to another system i.e. from Prod to dev system. First understand the requirement like which data is required in new client this will help in profile selection for copy.

Steps for Client Co p y

Case 1: Client co p y in one s y stem

Login in the system other than ddic andsap* user. Execute transaction SCCL Check the target client. Select the profile as per requirement, the available profiles are

SAP_ALL All Client-Specific Data w/o Change Documents SAP_APPL Customizing and Application Data w/o Change Docs SAP_APPX SAP_APPL without Authorization Profiles and Roles SAP_CUST Customizing SAP_CUSV Customizing and User Variants SAP_CUSX Customizing Without Authorization Profiles/Roles SAP_PROF Only Authorization Profiles and Roles SAP_UCSV Customizing, User Master Records and User Variants SAP_UCUS Customizing and User Master Records SAP_UONL User without Authorization Profiles and Roles SAP_USER User Master Records and Authorization Profiles

Click on scheduled as background job Check the source client and profile name Select the background server


of 116

Version 1.2


April 1, 2007

Click on schedule job

Enter the date and time when you want to execute the job , set the night time when there will be no user ( Or very less user) in the system.

A verification window will appear, check the target client, Profile name and source client is as required. See the desired data is selected i.e. boxes marked for client copy.

If everything is ok click on continue. Message will appear “Background Job was successfully

scheduled; log is displayed in scc3” Execute transaction scc3 for detail logs and any errors.

Case 2: Client Co p y from diffe r ent s y stem

Logon to the source client, which is to be, exported with a user other than ddic and sap*

Execute transaction SCC8. Select the Profile and target system. Click on schedule as background job. Select the date and time of execution. Verification pop up window will appear, check the values and

click on continue. Three requests will be created, note the requests number.Data

files and cofiles will be created. See the log in scc3 for successful export.

Move the datafiles and cofiles in the target system in respective directories of target system. Create a new client in the target system.

Use SCCL to copy the client 000 to newly created client. With tp addtobuffer and tp import, import the

exported files in the new client. Execute SCC7 for post processing.


of 116

Version 1.2


April 1, 2007

Para m e ter Change

9.1 Proce d ure for p a r a m e ter c h a n ge


of 116

Version 1.2


April 1, 2007

Pr e r eq u isite

The parameter change request form is filled properly by Basis Administrator with the details mentioned in the format. The request is forwarded to GM (IT) for approval. Parameter change should be carried out only on approval. Plan the instance restart for making the change effective.

St e p s

Execute transaction RZ10. Select the profile of the server of which you need to change

parameter. Select extended maintenance Click on change. Select and double click on the parameter you need to change. A new screen will appear with the value of parameter. Put the new

value. Click on copy button or Shift+F4. At bottom you will see changes

were made. Click on exit (shift + F3). Again click on exit. A popup will appear “The profile was changed, save changes? “

Click on yes. Now you will come to RZ10 first screen. Click on save button. New pop up will appear “incorrect parameter values detected,

Display values “Say yes. The screen will show the values again. Then click on exit. A pop up will appear asking “Do you want to Activate the profile

“Say yes. A New popup will appear profile and version saved and activated.


of 116

Version 1.2


April 1, 2007

A caution message will come with message profile is saved at os level you have to restart the application server.

Press Enter and come out of the screen. Stop and restart the sap instance.

Software Logistics

10.1 R/3 System Landscape

A well-defined strategy for setting up the R/3 System landscape is essential. For example, if you are expecting a lot of R/3 development and enhancement work, you should set up a dedicated development and quality


of 116

Version 1.2


April 1, 2007

assurance system. This ensures that developing your own objects has no impact on the production system. If there is little or no development, a one-or two-system landscape may be sufficient. The validity of the objects must be considered:• WBO objects are immediately valid within one system in all clients. • Most of the CO objects are only valid within one client in one system Environment

The following table shows all participating systems

System Name

Machine Name

System Type Role

BDS IBM P Series

Development Customizing and Development

BQS IBM P Series

Quality Assurance

Integration testing

BPS IBM P Series

Production Delivery

Following is a table of implemented clients and their purpose (except 000 and 001).

System Name

Client Purpose

BDS 020 Customizing and Development

030 Development Testing


of 116

Version 1.2


April 1, 2007

040 Sand BoxBQS 100 Integration Testing

BPS 100 Production

10.1.1 Policies

10.1.1.1 Development and Testing

A three-system landscape is set up to ensure smooth system operation. This ensures that neither development nor testing affects the availability of the production system.

10.1.1.2 Training

The development and the production systems are never used for training. The performance in a production system would be affected, and untested development objects may cause problems during training.

10.1.1.3 Installation

To ensure that system setup is correct, all installation tasks are performed by SAP-certified R/3 technical consultants.

10.1.2 Procedures

10.1.2.1 Development and Testing

See "Change Management and Transporting."

10.1.2.2 Training


of 116

Version 1.2


April 1, 2007

For training purposes, copies of a customized client including test data are used. The training client is saved, and is restored after training is completed.

10.1.2.3 Installation

To ensure that all systems are installed and configured correctly, all installation and upgrade tasks must be performed by SAP-certified R/3 technical consultants or experienced Basis Administrators. The installation or upgrade must be verified by the application department.Use the following transactions for System Lancdscape :SCC4 : Client AdministrationSCCL : Client Copy

10.1.3 Roles and Responsibilities

Task RoleChecking WBO setup Basis AdministratorChecking the transport system setup on each system

Basis Administrator

Performing client copy Basis AdministratorCustomizing Application project teamInstalling R/3 system SAP-certified R/3 technical

consultantsExperienced Basis Administrators

10.2 Change Management and Transporting

10.2.1 Policies

10.2.1.1 Developments and Customizing

All development and customizing work takes place in the Development System.


of 116

Version 1.2


April 1, 2007

10.2.1.2 Responsibility for WBO and CO Objects

The manager of a subproject is responsible for the objects in that project.

10.2.2 Procedures

10.2.2.1 Developments and Customizing

After development or customizing for a change request has been completed, the request is closed and released into the common transport directory. There is no automatic import into the quality assurance system. The Basis Administrator must be notified that there are objects to be imported. After successful testing, performed by members of the application department, the objects will be transported into the production system. The imports into the delivery systems must be performed manually by the Basis Administrator. Testing must be documented in a special form for being revisable and is a prerequisite for imports into downstream systems.

10.2.2.2 Responsibility for WBO and CO Objects

A project is set up in the WBO and the CO. A change request contains tasks for each member of the project team. A developer is only allowed to release his own tasks. The change request can only be released and transported by the project manager. The project manager is responsible for the integrity of the objects and must check the related transport logs.

10.2.3 Roles and Responsibilities

Tasking RoleReleasing finished tasks Programmer / Functional ConsultantsImporting new objects Basis AdministratorTesting objects Application department


of 116

Version 1.2


April 1, 2007

10.3 Upgrading SAP Software Release/System Components

Environment

Upgrading the R/3 landscape affects all systems, from the development system to the production systems.

10.3.1 Policies

10.3.1.1 Sequence of Systems to Be Upgraded

The first system to be upgraded is the development system. The developers and the administrator are responsible for the technical system check. When testing is complete, the quality assurance system has to be upgraded. The quality assurance system integrity must be tested by the application departments. When the test is complete, the production systems must be upgraded. To minimize downtime, this must be done at night or on the weekend.

11.3.1.2 Backup

Before any system component (R/3, DB, OS) is upgraded, a valid backup of the whole system (OS level) must be made.

10.3.1.3 Adjustments

Adjustments must be made together with the persons responsible for the objects.

10.3.1.4 Verification


of 116

Version 1.2


April 1, 2007

The development system is verified by the developers and the Basis Administrator. The quality assurance and production systems must be checked by the application departments.

10.3.2 Procedures

10.3.2.1 Sequence of Systems to Be Upgraded

The development and the quality assurance system can be upgraded during the day in cooperation with the programmers (Test System) and the application departments (quality assurance system). The production system must be updated at night or on the weekend. Preparations must be made for restoring the old system in case of a failure.

10.3.2.2 Backup

To be able to restore the system to a consistent state in the case of an unexpected failure, the system must be backed up on the operating system level before it is upgraded.A complete backup on the OS must be made after a successful upgrade.

10.3.2.3 Adjustments

After PREPARE has run, adjustments must be analyzed so that adjustments can be made as requested during the upgrade. This is particularly important for adjustments to the data dictionary (SPDD). SPAU adjustments can be made after the upgrade is completed. Adjustments must be stored in a separate change request so they are available when subsequent systems (quality assurance and production) are upgraded.

10.3.2.4 Verification

The development system is verified by the developers and the Basis Administrator. The upgraded quality assurance system must be checked by


of 116

Version 1.2


April 1, 2007

the application departments. The production system should not be upgraded before the successful upgrade of the quality assurance system has been confirmed by the application departments.

Backup

11.1 Procedure for Online Data backup

Pr e r eq u isite

By taking online backup we can avoid SAP downtime. After completion of online DB backup, backup of redo log files is a must. The online DB backup is consistent only after backup of offline redo logs which gets generated during the backup. Before starting online database backup following things should be ensured


of 116

Version 1.2


April 1, 2007

Backup should be taken during off-peak hours for better system response to users.

Before starting online database backup one should take backup of all archive files. This is because during online backup new archive file keeps generated as system is available to users, to avoid any bottleneck of archive full.

Make proper entry in Backup register for online backup of production server with proper volume names & date.

After completion of online database backup following things should be ensured. After successful completion of online DB backup archive backup of redolog files should be taken immediately.

St e p s

Following are the steps to be performed for online database backup. Login to the server you want to take backup as telnet <IP

Addr> Give the root as login and its password. Give the following command at the prompt #> su –

ora<dbsid> At the prompt now give <dbid>:ora<dbsid> #> brbackup –i

force –v <volume name> It will ask for confirmation and wait for reply before

initializing the volume name. Give ‘c’ to continue and it will initialize the tape in Drive

with respective volume name. Initialized media is ready for start of backup

Exit from ora<dbsid> exit Go to user <sidadm> by typing su - <sidadm> At command prompt now give brtools Give your option of choice as 4 Give option of your choice as 1 Give choice as 2 and specify on which device the backup will be

started according to the initsid.sap file


of 116

Version 1.2


April 1, 2007

Give your choice as 6 Type Online Give option as c Give option as c Give option as c and backup will be get started After the completion of backup exit from brtools After end of the Online DB Backup, take the archive backup

immediately. Without archive backup, online backup is not complete. (refer document for archive backup)

Check the Online backup log and archive backup log properly to ensure backup gets completed without any error/warnings.

11.2 Procedure for Offline Data backup

Pr e r eq u isite

During offline database backup SAP is not available to users. During offline backup database is shutdown by brbackup utility and backup of all datafiles, control file and online redo log files taken on the media. After completion of backup, database instance starts in normal mode. As database instance is down during offline backup this backup is in a consistent state with control file and online redo log files. We can restore offline backup and start the database without applying redologs. Where as if online backup is to be restored, redo log files needs to be applied to bring the database to a consistent state.

Before starting offline database backup following things should be ensured

Inform the user in advance for the planning of backup as SAP will not be available to users during offline DB backup.

Make proper entry in Backup register in offline backup


of 116

Version 1.2


April 1, 2007

column of production server with proper volume names. Keep the backup volume ready in respective drive so

backup can be started immediately after SAP instance shutdown.

St e p s Following are the steps to be performed for online database backup.

Login to the server you want to take backup as telnet <IP Addr>

Give the root as login and its password. Give the following command at the prompt #> su –





Exit from ora<dbsid> exit Go to user <sidadm> by typing su - <sidadm> At the command prompt type stopsap r3 At command prompt now give brtools Give your option of choice as 4 Give option of your choice as 1 Give choice as 2 and specify on which device the backup will be

started according to the initsid.sap file Give your choice as 6 Type Offline_force by this database will be down automatically

and after the end of backup it starts up the database automatically

Give option as c Give option as c


of 116

Version 1.2


April 1, 2007

Give option as c and backup will be get started On completion of backup exit from brtools and start the central

instance by startsap r3 Login into SAP application server and check the backup

log properly to ensure backup completed successfully.

11.3 Procedure for Archive log backup

Pr e r eq u isite

If the database is running in archive mode it constantly generates offline redo log files in directory /<oracle_home>/saparch or /<oracle_home>/oraarch (in new version). If this directory becomes full and no space left to accommodate new offline redo log file, the database get stuck

at that moment. No update takes place in the database till there is enough free space made available in archive directory.

To avoid such situation archive directory should be monitored constantly and backup of archive files should be taken regularly. Archive backup is also required in case of database restore. You can recover the database till the time of last available archive file conditionally all archive files from last online/offline backup are available and retrievable from media.

So backup of archive is as much important as backup of database.On safer side backup of each archive file on two different media is recommended in case of failure/damage of a media. The same procedure is followed in following steps

St e p s Following are the steps to be performed for archive log backup.

Login to the server you want to take backup as telnet <IP


of 116

Version 1.2


April 1, 2007

Addr> Give the root as login and its password. Give the following command at the prompt #> su –





Exit from ora<dbsid> exit Go to user <sidadm> by typing su - <sidadm> At command prompt now give brtools Give your option of choice as 4 Give option of your choice as 2 Give option c Give option c Give option c After the completion of backup Make proper entry of archives

files backedup on respective media


of 116

Version 1.2


April 1, 2007

11.4 Procedure for rootvg backup

Pr e r eq u isite Root backup is the backup of each and every file on a particular server. As application server contains only application instances, ensure all the applications on a particular server is shutdown properly before start of backup. File in use will not be backed-up during root backup.

St e p s Insert the media with proper marking on media. Make respective

entry in Operating System backup column of backup register. Stop application instances running on a particular server. (refer

document for startup and shutdown of SAP instances) Login with root user on a particular server. Umount all networked mounted FS from this server. From root prompt give the command as “smit mksysb” which will

be asking the following parameters to be entered for starting the root backup or the system backup of the server

* Backup DEVICE or FILE [ ] +/ +/Create MAP files? No + +EXCLUDE files? No + +


of 116

Version 1.2


April 1, 2007

List files as they are backed up? No + +Verify readability if tape device? No + +Generate new /image.data file? Yes + +EXPAND /tmp if needed? No + +Disable software packing of backup? No + +Backup extended attributes? Yes + +Number of BLOCKS to write in a single output (Leave blank to use a system default)

[ ] # #

Press ENTER to start backup. After completion of backup it will give summary of how many files

backedup. Press done to come back to previous screen. Come out of smit. Remount all NFS which was unmounted before start of backup Start application instances on a particular server. (refer document

for startup and shutdown of SAP instances) Make proper entry into backup register with respective server name. Keep the df –k marked with date of backup which was used for root

backup.


of 116

Version 1.2


April 1, 2007

11.5 Procedure for other volume group (VG) backup

St e p s Insert the media with proper marking on media. Make respective

entry in Operating System backup column of backup register. Login with root user on a particular server. From root prompt give the command as “smit savevg” which will

be asking the following parameters to be entered for starting the volume group backup

Back Up a Volume Group to Tape/File

Type or select values in entry fields.Press Enter AFTER making all desired changes.

* Backup DEVICE or FILE +/* VOLUME GROUP to back up +List files as they are backed up? No +Generate new vg.data file? Yes +Create MAP files? No +EXCLUDE files? No +EXPAND /tmp if needed? No +Disable software packing of backup? No +Backup extended attributes? Yes +Number of BLOCKS to write in a single output (Leave blank to use a system default)

[ ] #


of 116

Version 1.2


April 1, 2007

Verify readability if tape device No +

Press ENTER to start backup. After completion of backup it will give summary of how many files

backedup. Press done to come back to previous screen. Come out of smit. Make proper entry into backup register with respective server name. Keep the df –k marked with date of backup which was used for

Groip backup.Server Refresh

Prerequisite

Backup media of the Prod server's latest database backup is required. Media of the redolog backup is also required if you want to apply redologs.

Steps for server refresh

Login through telnet and stop the SAP, Database and listener of the instance which is to be refreshed.

Telnet the server which is to be refreshed and rename the control file, summary log files of brbackup and brarchive as follows

#cd /oracle/dbsid/sapbackup #mv backSID.log backSID.log.current date #cd /oracle/dbsid/saparch #mv archSID.log archSID.log.current date. #cd /oracle/dbsid/OriglogA/cntrl #mv cntrlSID.dbf cntrlSID.dbf.current date Now copy the backSID.log and archSID.log from Prod System to

system where restoration is to be performed in respective directories. Copy the detailed brbackup log file of the backup you want to restore

from Prod system to system where restoration is to be performed. Load the required media in ultrium drive.


of 116

Version 1.2


April 1, 2007

telnet the server which is to be refreshed and login as oracle user ora<SID>

Run the brrestore query option Ora<SID> brrestore –q This output will create the directories if required and give the details

of media required. Check the output of query it should be terminated successfully. Now start the database restore as Ora<SID> brrestore -b < detail log file name > -m full This will restore all datafiles, controlfiles and redologs if an offiline

backup is restored. In case of online backup restore this command will restore archive

logs which are required to make online backup consistent. After brrestore completed successfully. Check the owner and

permissions of datafiles, controlfiles. Case1: Offline backup restored

Ora<SID> sqlplus “/ as sysdba”SQL> startup nomount;SQL> alter database mount;Check for the database mounted successfully.SQL> shutdown immediate;SQL> startupNow the database will be mounted and opened.

Case2: Online backup is restoredOra<SID> sqlplus “/ as sysdba”SQL> startup nomount;SQL> alter database mount;SQL> recover database until cancel using backup controlfile;SQL> alter database open resetlogs;Now database will be opened.Ora<SID> lsnrctl start


of 116

Version 1.2


April 1, 2007

Backup Restoration Procedure

Prerequisites

Tapes of the latest backup. Tapes of the redo logs after backup till the crash time. Root backup of the database server. The cause of database crash to be

sorted out before restore of database.

Steps

Restore the root backup after creating the required vgs and lvols with required size.

Check for the files in /oracle/dbsid/sapbackup, latest backSID.log and the log files (Summary logfile and detail logfile) of the backups should be available. If the latest summary logfile and details log file is not available then it needs to be restored from the backup media usingbrrestore.

ora<dbsid>brrestore -n <det_log> ora<dbsid>brrestore –n <sum_log> Check the sapdata1 to 6 directories for the sizes. Log in as ora<sid> brerestore –b < logfile name > -m full

<logfile name > the detailed logfile name of the backup to be restored.

This will restore all the datafiles and controlfiles to their respective location. Also restore the mirror copies of the control file and the online redo log files.


of 116

Version 1.2


April 1, 2007

CASE 1 >> If restoring offline backup and there is no need to apply redo logs (Partial recovery), before opening the database. There is no need to recover database in this case.

CASE 2 >> If you need to apply redologs (Restoring Online backup) then do not open the database as archives are still to be restored. Database can be checked by giving startup mount and shutdown commands from sql prompt.

Check the /oracle/dbsid/saparch directory for size; It should have enough space to restore all redo log files.

Make changes in initSID.sap for using tapes of redo logs. Login as user ora<dbsid> and restore the archives in saparch

directory. Ora<dbsid> brrestore – a XXXXX –YYYYY

This will Restore the archived redo log files with the log sequence numbers from XXXXX through YYYYY into the archiving directory

We can specify the alternate path incase to restore files to any other directory, but files should be in /oracle/dbsid/saparch (archive_directory) while recovering database.

Once all the redo logs are restored, copy control file and online redo log files to their respective directories i.e. control file to oracle/dbsid/dbs, oracle/dbsid/sapdata1/cntrl/,oracle/dbsid/sapdata2/cntrl/ and online redo log files to /oracle/dbsid/origlogA,oracle/dbsid/mirrlogA, /oracle/dbsid/origlogB, oracle/dbsid/mirrlogB.

Get in as sqlplus “/ as sysdba” Type command startup mount. RECOVERY OPTIONS 1

Type command recover database until YYYY-MM-DD-HH-MIN-SEC.

Give the time up to the last archive to be applied. System will ask manual one by one application or auto

application of all archive.


of 116

Version 1.2


April 1, 2007

Select Auto for all archives. The recovery is now completed up to the specified time.

RECOVERY OPTIONS 2 If the recovery is required to be done through control file give

command recover database using backup control file. After recovery give command alter database open noresetlogs.

If this doesn’t work then we have to give, alter database open resetlogs, this will open the database up till the recovery time and the redolog count will be reset.


of 116

Version 1.2


April 1, 2007

Details of initSID.sap

# @(#) $Id: //bas/700_REL/src/ccm/rsbr/initSID.sap#10 $ SAP######################################################################### ## SAP BR*Tools sample profile. ## The parameter syntax is the same as for init.ora parameters. ## Enclose parameter values which consist of more than one symbol in ## double quotes. ## After any symbol, parameter definition can be continued on the next ## line. ## A parameter value list should be enclosed in parentheses, the list ## items should be delimited by commas. ## There can be any number of white spaces (blanks, tabs and new lines) ## between symbols in parameter definition. ## Comment lines must start with a hash character. ## #########################################################################

# backup mode [all | all_data | full | incr | sap_dir | ora_dir# | all_dir | <tablespace_name> | <file_id> | <file_id1>-<file_id2># | <generic_path> | (<object_list>)]# default: allbackup_mode = all

# restore mode [all | all_data | full | incr | incr_only | incr_full# | incr_all | <tablespace_name> | <file_id> | <file_id1>-<file_id2># | <generic_path> | (<object_list>) | partial | non_db# redirection with '=' is not supported here - use option '-m' instead# default: all


of 116

Version 1.2


April 1, 2007

# "compress -b 12 -c $ > $"# no defaultcompress_cmd = "compress -c $ > $"

# uncompress command# first $-character is replaced by the source file name# second $-character is replaced by the target file name# <source_file_name> = <target_file_name>.Z# for uncompress command the -c option must be set# no defaultuncompress_cmd = "uncompress -c $ > $"

# directory for compression [<path_name> | (<path_name_list>)]# default: value of the backup_root_dir parametercompress_dir = $SAPDATA_HOME/sapreorg

# brarchive function [save | second_copy | double_save | save_delete# | second_copy_delete | double_save_delete | copy_save# | copy_delete_save | delete_saved | delete_copied]# default: savearchive_function = copy_delete_save

# directory for archive log copies to disk# default: first value of the backup_root_dir parameterarchive_copy_dir = $SAPDATA_HOME/sapbackup

# directory for archive log copies to stage# default: first value of the stage_root_dir parameterarchive_stage_dir = $SAPDATA_HOME/sapbackup

# delete archive logs from duplex destination [only | no | yes | check]# default: only# archive_dupl_del = only


of 116

Version 1.2


April 1, 2007

# new sapdata home directory for disk_copy | disk_standby# no default# new_db_home = /oracle/C11

# stage sapdata home directory for stage_copy | stage_standby# default: value of the new_db_home parameter# stage_db_home = /oracle/C11

# original sapdata home directory for split mirror disk backup# no default# orig_db_home = /oracle/C11

# remote host name# no default# remote_host = <host_name>

# remote user name# default: current operating system user# remote_user = <user_name># tape copy command [cpio | cpio_gnu | dd | dd_gnu | rman | rman_gnu# rman_dd | rman_dd_gnu]# default: cpiotape_copy_cmd = dd

# disk copy command [copy | copy_gnu | dd | dd_gnu | rman | rman_gnu]# default: copydisk_copy_cmd = copy

# stage copy command [rcp | scp | ftp]# default: rcpstage_copy_cmd = rcp

# pipe copy command [rsh | ssh]# default: rsh


of 116

Version 1.2


April 1, 2007

pipe_copy_cmd = rsh

# flags for cpio output command# default: -ovBcpio_flags = -ovB

# flags for cpio input command# default: -iuvBcpio_in_flags = -iuvB

# flags for cpio command for copy of directories to disk# default: -pdcu# use flags -pdu for gnu toolscpio_disk_flags = -pdcu

# flags for dd output command# default: "obs=16k"# recommended setting:# Unix: "obs=nk bs=nk", example: "obs=64k bs=64k"# Windows: "bs=nk", example: "bs=64k"dd_flags = "obs=64k bs=64k"

# flags for dd input command# default: "ibs=16k"# recommended setting:# Unix: "ibs=nk bs=nk", example: "ibs=64k bs=64k"# Windows: "bs=nk", example: "bs=64k"dd_in_flags = "ibs=64k bs=64k"

# number of members in RMAN save sets [ 1 | 2 | 3 | 4 | tsp | all ]# default: 1saveset_members = 1

# additional parameters for RMAN


of 116

Version 1.2


April 1, 2007

# rman_channels and rman_filesperset are only used when rman_util,# rman_disk or rman_stage# rman_channels defines the number of parallel sbt channel allocations# rman_filesperset = 0 means:# one file per save set - for non-incremental backups# all files in one save set - for incremental backups# the others have the same meaning as for native RMAN# rman_channels = 1# rman_filesperset = 0# rman_maxpiecesize = 0 # in KB - former name rman_kbytes# rman_rate = 0 # in KB - former name rman_readrate# rman_maxopenfiles = 0# rman_maxsetsize = 0 # in KB - former name rman_setsize# additional parameters for RMAN version 8.1# the parameters have the same meaning as for native RMAN# rman_diskratio = 0 # deprecated in Oracle 10g# rman_pool = 0# rman_copies = 0 | 1 | 2 | 3 | 4 # former name rman_duplex# rman_proxy = no | yes | only# special parameters for an external backup library, example:# rman_parms = "BLKSIZE=65536 ENV=(BACKUP_SERVER=HOSTNAME)"# rman_send = "'<command>'"# rman_send = ("channel sbt_1 '<command1>' parms='<parameters1>'",# "channel sbt_2 '<command2>' parms='<parameters2>'")# rman_compress = no | yes# rman_maxcorrupt = (<dbf_name>|<dbf_id>:<corr_cnt>, ...)

# remote copy-out command (backup_dev_type = pipe)# $-character is replaced by current device address# no defaultcopy_out_cmd = "dd ibs=8k obs=64k of=$"

# remote copy-in command (backup_dev_type = pipe)


of 116

Version 1.2


April 1, 2007

# $-character is replaced by current device address# no defaultcopy_in_cmd = "dd ibs=64k obs=8k if=$"

# rewind command# $-character is replaced by current device address# no default# operating system dependent, examples:# HP-UX: "mt -f $ rew"# TRU64: "mt -f $ rewind"# AIX: "tctl -f $ rewind"# Solaris: "mt -f $ rewind"# Windows: "mt -f $ rewind"# Linux: "mt -f $ rewind"rewind = "mt -f $ rewind"

# rewind and set offline command# $-character is replaced by current device address# default: value of the rewind parameter# operating system dependent, examples:# HP-UX: "mt -f $ offl"# TRU64: "mt -f $ offline"# AIX: "tctl -f $ offline"# Solaris: "mt -f $ offline"# Windows: "mt -f $ offline"# Linux: "mt -f $ offline"rewind_offline = "mt -f $ offline"

# tape positioning command# first $-character is replaced by current device address# second $-character is replaced by number of files to be skipped# no default# operating system dependent, examples:# HP-UX: "mt -f $ fsf $"


of 116

Version 1.2


April 1, 2007

# TRU64: "mt -f $ fsf $"# AIX: "tctl -f $ fsf $"# Solaris: "mt -f $ fsf $"# Windows: "mt -f $ fsf $"# Linux: "mt -f $ fsf $"tape_pos_cmd = "mt -f $ fsf $"

# mount backup volume command in auto loader / juke box# used if backup_dev_type = tape_box | pipe_box# no default# mount_cmd = "<mount_cmd> $ $ $ [$]"

# dismount backup volume command in auto loader / juke box# used if backup_dev_type = tape_box | pipe_box# no default# dismount_cmd = "<dismount_cmd> $ $ [$]"

# split mirror disks command# used if backup_type = offline_split | online_split | offline_mirror# | online_mirror# no default# split_cmd = "<split_cmd> [$]"

# resynchronize mirror disks command# used if backup_type = offline_split | online_split | offline_mirror# | online_mirror# no default# resync_cmd = "<resync_cmd> [$]"

# additional options for SPLITINT interface program# no default# split_options = "<split_options>"

# resynchronize after backup flag [no | yes]


of 116

Version 1.2


April 1, 2007

# default: no# split_resync = no

# pre-split command# no default# pre_split_cmd = "<pre_split_cmd>"

# post-split command# no default# post_split_cmd = "<post_split_cmd>"

# volume size in KB = K, MB = M or GB = G (backup device dependent)# default: 1200M# recommended values for tape devices without hardware compression:# 60 m 4 mm DAT DDS-1 tape: 1200M# 90 m 4 mm DAT DDS-1 tape: 1800M# 120 m 4 mm DAT DDS-2 tape: 3800M# 125 m 4 mm DAT DDS-3 tape: 11000M# 112 m 8 mm Video tape: 2000M# 112 m 8 mm high density: 4500M# DLT 2000 10/20 GB: 10000M# DLT 2000XT 15/30 GB: 15000M# DLT 4000 20/40 GB: 20000M# DLT 7000 35/70 GB: 35000M# recommended values for tape devices with hardware compression:# 60 m 4 mm DAT DDS-1 tape: 1000M# 90 m 4 mm DAT DDS-1 tape: 1600M# 120 m 4 mm DAT DDS-2 tape: 3600M# 125 m 4 mm DAT DDS-3 tape: 10000M# 112 m 8 mm Video tape: 1800M# 112 m 8 mm high density: 4300M# DLT 2000 10/20 GB: 9000M# DLT 2000XT 15/30 GB: 14000M# DLT 4000 20/40 GB: 18000M


of 116

Version 1.2


April 1, 2007

# DLT 7000 35/70 GB: 30000Mtape_size = 200G

# volume size in KB = K, MB = M or GB = G used by brarchive# default: value of the tape_size parameter# tape_size_arch = 200G

# level of parallel execution# default: 0 - set to number of backup devicesexec_parallel = 0

# address of backup device without rewind# [<dev_address> | (<dev_address_list>)]# no default# operating system dependent, examples:# HP-UX: /dev/rmt/0mn# TRU64: /dev/nrmt0h# AIX: /dev/rmt0.1# Solaris: /dev/rmt/0mn# Windows: /dev/nmt0 | /dev/nst0# Linux: /dev/nst0tape_address = /dev/rmt0.1

# address of backup device without rewind used by brarchive# default: value of the tape_address parameter# operating system dependent# tape_address_arch = /dev/rmt/0mn

# address of backup device with rewind# [<dev_address> | (<dev_address_list>)]# no default# operating system dependent, examples:# HP-UX: /dev/rmt/0m# TRU64: /dev/rmt0h


of 116

Version 1.2


April 1, 2007

# AIX: /dev/rmt0# Solaris: /dev/rmt/0m# Windows: /dev/mt0 | /dev/st0# Linux: /dev/st0tape_address_rew = /dev/rmt0

# address of backup device with rewind used by brarchive# default: value of the tape_address_rew parameter# operating system dependent# DLT 2000 10/20 GB: 10000M# DLT 2000XT 15/30 GB: 15000M# DLT 4000 20/40 GB: 20000M# DLT 7000 35/70 GB: 35000M# recommended values for tape devices with hardware compression:# 60 m 4 mm DAT DDS-1 tape: 1000M# 90 m 4 mm DAT DDS-1 tape: 1600M# 120 m 4 mm DAT DDS-2 tape: 3600M# 125 m 4 mm DAT DDS-3 tape: 10000M# 112 m 8 mm Video tape: 1800M# 112 m 8 mm high density: 4300M# DLT 2000 10/20 GB: 9000M# DLT 2000XT 15/30 GB: 14000M# DLT 4000 20/40 GB: 18000M# DLT 7000 35/70 GB: 30000Mtape_size = 200G

# volume size in KB = K, MB = M or GB = G used by brarchive# default: value of the tape_size parameter# tape_size_arch = 200G

# level of parallel execution# default: 0 - set to number of backup devicesexec_parallel = 0


of 116

Version 1.2


April 1, 2007

# address of backup device without rewind# [<dev_address> | (<dev_address_list>)]# no default# operating system dependent, examples:# HP-UX: /dev/rmt/0mn# TRU64: /dev/nrmt0h# AIX: /dev/rmt0.1# Solaris: /dev/rmt/0mn# Windows: /dev/nmt0 | /dev/nst0# Linux: /dev/nst0tape_address = /dev/rmt0.1

# address of backup device without rewind used by brarchive# default: value of the tape_address parameter# operating system dependent# tape_address_arch = /dev/rmt/0mn

# address of backup device with rewind# [<dev_address> | (<dev_address_list>)]# no default# operating system dependent, examples:# HP-UX: /dev/rmt/0m# TRU64: /dev/rmt0h# AIX: /dev/rmt0# Solaris: /dev/rmt/0m# Windows: /dev/mt0 | /dev/st0# Linux: /dev/st0tape_address_rew = /dev/rmt0

# address of backup device with rewind used by brarchive# default: value of the tape_address_rew parameter# operating system dependent# tape_address_rew_arch = /dev/rmt/0m


of 116

Version 1.2


April 1, 2007

# address of backup device with control for mount/dismount command# [<dev_address> | (<dev_address_list>)]# default: value of the tape_address_rew parameter# operating system dependent# tape_address_ctl = /dev/...

# address of backup device with control for mount/dismount command# used by brarchive# default: value of the tape_address_rew_arch parameter# operating system dependent# tape_address_ctl_arch = /dev/...

# volumes for brarchive# [<volume_name> | (<volume_name_list>) | SCRATCH]# no defaultvolume_archive = (BPSA01, BPSA02, BPSA03, BPSA04, BPSA05, BPSA06, BPSA07, BPSA08, BPSA09, BPSA10, BPSA11, BPSA12, BPSA13, BPSA14, BPSA15, BPSA16, BPSA17, BPSA18, BPSA19, BPSA20, BPSA21, BPSA22, BPSA23, BPSA24, BPSA25, BPSA26, BPSA27, BPSA28, BPSA29, BPSA30)

# volumes for brbackup# [<volume_name> | (<volume_name_list>) | SCRATCH]# no defaultvolume_backup = (BPSB01, BPSB02, BPSB03, BPSB04, BPSB05, BPSB06, BPSB07, BPSB08, BPSB09, BPSB10, BPSB11, BPSB12, BPSB13, BPSB14, BPSB15, BPSB16, BPSB17, BPSB18, BPSB19, BPSB20, BPSB21, BPSB22, BPSB23, BPSB24, BPSB25, BPSB26, BPSB27, BPSB28, BPSB29, BPSB30)

# expiration period for backup volumes in days# default: 30


of 116

Version 1.2


April 1, 2007

expir_period = 0

# recommended usages of backup volumes# default: 100tape_use_count = 100

# backup utility parameter file# default: no parameter file# util_par_file = initSID.utl#util_par_file = /oracle/BPS/102_64/dbs/initBPS.utl# mount/dismount command parameter file# default: no parameter file# mount_par_file = initSID.mnt

# Oracle connection name to the primary database# [primary_db = <conn_name> | LOCAL]# no default# primary_db = <conn_name>

# Oracle connection name to the standby database# [standby_db = <conn_name> | LOCAL]# no default# standby_db = <conn_name>

# description of parallel instances for Oracle RAC# parallel_instances = <inst_desc> | (<inst_desc_list>)# <inst_desc_list> - <inst_desc>[,<inst_desc>...]# <inst_desc> - <Oracle_sid>:<Oracle_home>@<conn_name># <Oracle_sid> - Oracle system id for parallel instance# <Oracle_home> - Oracle home for parallel instance# <conn_name> - Oracle connection name to parallel instance# Please include the local instance in the parameter definition!# default: no parallel instances# example for initRAC001.sap:


of 116

Version 1.2


April 1, 2007

# parallel_instances = (RAC001:/oracle/RAC/920_64@RAC001,# RAC002:/oracle/RAC/920_64@RAC002, RAC003:/oracle/RAC/920_64@RAC003)

# handling of Oracle RAC database services [no | yes]# default: no# db_services = no

# database owner of objects to be checked# <owner> | (<owner_list>)# default: all SAP owners# check_owner = sapr3

# database objects to be excluded from checks# all_part | non_sap | [<owner>.]<table> | [<owner>.]<index># | [<owner>.]<prefix>* | <tablespace> | (<object_list>)# default: no exclusion, example:# check_exclude = (SDBAH, SAPR3.SDBAD)

# database owner of SDBAH, SDBAD and XDB tables for cleanup# <owner> | (<owner_list>)# default: all SAP owners# cleanup_owner = sapr3

# retention period in days for brarchive log files# default: 30# cleanup_brarchive_log = 30

# retention period in days for brbackup log files# default: 30# cleanup_brbackup_log = 30

# retention period in days for brconnect log files# default: 30


of 116

Version 1.2


April 1, 2007

# cleanup_brconnect_log = 30# retention period in days for brrestore log files# default: 30# cleanup_brrestore_log = 30# retention period in days for brrecover log files# default: 30# cleanup_brrecover_log = 30# retention period in days for brspace log files# default: 30# cleanup_brspace_log = 30# retention period in days for archive log files saved on disk# default: 30# cleanup_disk_archive = 30

# retention period in days for database files backed up on disk# default: 30# cleanup_disk_backup = 30

# retention period in days for brspace export dumps and scripts# default: 30# cleanup_exp_dump = 30

# retention period in days for Oracle trace and audit files# default: 30# cleanup_ora_trace = 30

# retention period in days for records in SDBAH and SDBAD tables# default: 100# cleanup_db_log = 100

# retention period in days for records in XDB tables# default: 100# cleanup_xdb_log = 100


of 116

Version 1.2


April 1, 2007

# retention period in days for database check messages# default: 100# cleanup_check_msg = 100

# database owner of objects to adapt next extents# <owner> | (<owner_list>)# default: all SAP owners# next_owner = sapr3

# database objects to adapt next extents# all | all_ind | special | [<owner>.]<table> | [<owner>.]<index># | [<owner>.]<prefix>* | <tablespace> | (<object_list>)# default: all abjects of selected owners, example:# next_table = (SDBAH, SAPR3.SDBAD)

# database objects to be excluded from adapting next extents# all_part | [<owner>.]<table> | [<owner>.]<index> | [<owner>.]<prefix>*# | <tablespace> | (<object_list>)# default: no exclusion, example:# next_exclude = (SDBAH, SAPR3.SDBAD)

# database objects to get special next extent size# all_sel:<size>[/<limit>] | [<owner>.]<table>:<size>[/<limit>]# | [<owner>.]<index>:<size>[/<limit>]# | [<owner>.]<prefix>*:<size>[/<limit>] | (<object_size_list>)# default: according to table category, example:# next_special = (SDBAH:100K, SAPR3.SDBAD:1M/200)

# maximum next extent size# default: 2 GB - 5 * <database_block_size># next_max_size = 1G

# maximum number of next extents# default: 0 - unlimited


of 116

Version 1.2


April 1, 2007

# directory for brrecover file copies# default: $SAPDATA_HOME/sapbackup# recov_copy_dir = $SAPDATA_HOME/sapbackup

# time period for searching for backups# 0 - all available backups, >0 - backups from n last days# default: 30# recov_interval = 30

# degree of paralelism for applying archive log files# 0 - use Oracle default parallelism, 1 - serial, >1 - parallel# default: Oracle default# recov_degree = 0

# number of lines for scrolling in list menus# 0 - no scrolling, >0 - scroll n lines# default: 20# scroll_lines = 20

# time period for displaying profiles and logs# 0 - all available logs, >0 - logs from n last days# default: 30# show_period = 30

# directory for brspace file copies# default: $SAPDATA_HOME/sapreorg# space_copy_dir = $SAPDATA_HOME/sapreorg

# directory for table export dump files# default: $SAPDATA_HOME/sapreorg# exp_dump_dir = $SAPDATA_HOME/sapreorg

# database tables for reorganization


of 116

Version 1.2


April 1, 2007

# [<owner>.]<table> | [<owner>.]<prefix>* | [<owner>.]<prefix>%# | (<table_list>)# no default# reorg_table = (SDBAH, SAPR3.SDBAD)

# database indexes for rebuild# [<owner>.]<index> | [<owner>.]<prefix>* | [<owner>.]<prefix>%# | (<index_list>)# no default# recov_type = complete

# directory for brrecover file copies# default: $SAPDATA_HOME/sapbackup# recov_copy_dir = $SAPDATA_HOME/sapbackup

# time period for searching for backups# 0 - all available backups, >0 - backups from n last days# default: 30# recov_interval = 30

# degree of paralelism for applying archive log files# 0 - use Oracle default parallelism, 1 - serial, >1 - parallel# default: Oracle default# recov_degree = 0

# number of lines for scrolling in list menus# 0 - no scrolling, >0 - scroll n lines# default: 20# scroll_lines = 20

# time period for displaying profiles and logs# 0 - all available logs, >0 - logs from n last days# default: 30# show_period = 30


of 116

Version 1.2


April 1, 2007

# directory for brspace file copies# default: $SAPDATA_HOME/sapreorg# space_copy_dir = $SAPDATA_HOME/sapreorg

# directory for table export dump files# default: $SAPDATA_HOME/sapreorg# exp_dump_dir = $SAPDATA_HOME/sapreorg

# database tables for reorganization# [<owner>.]<table> | [<owner>.]<prefix>* | [<owner>.]<prefix>%# | (<table_list>)# no default# reorg_table = (SDBAH, SAPR3.SDBAD)

# database indexes for rebuild# [<owner>.]<index> | [<owner>.]<prefix>* | [<owner>.]<prefix>%# | (<index_list>)# no default# rebuild_index = (SDBAH~0, SAPR3.SDBAD~0)

# database tables for export# [<owner>.]<table> | [<owner>.]<prefix>* | [<owner>.]<prefix>%# | (<table_list>)# no default# exp_table = (SDBAH, SAPR3.SDBAD)

# database tables for import# <table> | (<table_list>)# no default# do not specify table owner in the list - use -o|-owner option for this# imp_table = (SDBAH, SDBAD)


of 116

Version 1.2


April 1, 2007

Details of initSID.ora

######################################################################### This init.ora profile is a transparent copy of Oracle spfile. ## It was created by BRCONNECT at 2007-07-29 22.30.49. ## Please do not change this file! Maintain only the spfile. ## You can use BRSPACE for the altering of database parameters: ## brspace -f dbparam #########################################################################*._OPTIM_PEEK_USER_BINDS=FALSE*.background_dump_dest='/oracle/BPS/saptrace/background'*.compatible='10.2.0'*.control_file_record_keep_time=30*.control_files='/oracle/BPS/origlogA/cntrl/cntrlBPS.dbf','/oracle/BPS/origlogB/cntrl/cntrlBPS.dbf','/oracle/BPS/sapdata1/cntrl/cntrlBPS.dbf'*.core_dump_dest='/oracle/BPS/saptrace/background'*.db_block_size=8192


of 116

Version 1.2


April 1, 2007

*.db_cache_size=2255864463*.db_files=254*.db_name='BPS'*.dml_locks=4000*.event='10191 trace name context forever, level 1'*.FILESYSTEMIO_OPTIONS='ASYNCH'*.job_queue_processes=1*.log_archive_dest='/oracle/BPS/oraarch/BPSarch'*.log_buffer=1048576*.log_checkpoint_interval=0*.log_checkpoints_to_alert=true*.open_cursors=800*.optimizer_features_enable='10.2.0.1'*.pga_aggregate_target=3007819284*.processes=170*.recyclebin='off'*.remote_login_passwordfile='exclusive'*.remote_os_authent=true*.sessions=340*.sga_max_size=6511728926*.shared_pool_reserved_size=225586446*.shared_pool_size=2255864463*.sort_area_retained_size=0*.sort_area_size=2097152*.statistics_level='typical'*.undo_management='AUTO'*.undo_retention=43200*.undo_tablespace='PSAPUNDO'*.user_dump_dest='/oracle/BPS/saptrace/usertrace'*.workarea_size_policy='AUTO'


of 116

Version 1.2


April 1, 2007

Details Of initSAI.utl

#--------------------------------------------------------------------------## Data Protection for mySAP (R) interface for ORACLE## Sample profile for Data Protection for mySAP (R) Version 5.3# for UNIX##--------------------------------------------------------------------------## This file should be renamed to $ORACLE_HOME/dbs/init$ORACLE_SID.utl# where $ORACLE_HOME is the home directory of the Oracle database and# $ORACLE_SID is the system ID of the Oracle database.# Default is '/oracle/C21/initC21.utl'.## See the 'Data Protection for mySAP (R) Installation &# User's Guide' for a full description.#


of 116

Version 1.2


April 1, 2007

# For a comment symbol the character '#' can be used.# Everything following this character will be interpreted as comment.## Data Protection for mySAP (R) V5R3 accesses its profile# in "read only" mode. All variable parameters like passwords, date of# last password change, current version number will be written into the file# specified with the CONFIG_FILE parameter. The passwords will be encrypted.

#--------------------------------------------------------------------------# Prefix of the 'Backup ID' which will be used for communication with# BR*Tools and stored in the description field of the Tivoli Storage Manager# archive function.# Must be 6 characters.# Default: none.#--------------------------------------------------------------------------BACKUPIDPREFIX BPS___

#--------------------------------------------------------------------------# Number of parallel sessions to be established.# Note: This number must not exceed the number of tape drives simultaneously# available to the node on the Tivoli Storage Manager servers to be accessed.# The valid range of MAX_SESSIONS is from 1 and 32.# Default: none.#--------------------------------------------------------------------------MAX_SESSIONS 1 # Tivoli Storage Manager client sessions

#--------------------------------------------------------------------------


of 116

Version 1.2


April 1, 2007

# Number of parallel sessions to be established for the database backup.# Note: This number must not exceed the number of tape drives simultaneously# available to the node for a database backup on the Tivoli Storage Manager# servers to be accessed.# The valid range of MAX_BACK_SESSIONS is from 1 to 32.# Default: MAX_SESSIONS.#--------------------------------------------------------------------------#MAX_BACK_SESSIONS 1 # Tivoli Storage Manager client sessions for backup

#--------------------------------------------------------------------------#--------------------------------------------------------------------------# Number of parallel sessions to be established for the redo log backup.# Note: This number must not exceed the number of tape drives simultaneously# available to the node for a redo log backup on the Tivoli Storage Manager# servers to be accessed.# The valid range of MAX_ARCH_SESSIONS is from 1 to 32.# Default: MAX_SESSIONS.#--------------------------------------------------------------------------#MAX_ARCH_SESSIONS 1 # Tivoli Storage Manager client sessions for archive

#--------------------------------------------------------------------------# Number of parallel sessions to be established for the backup of control# files. This number is typically used to reduce the number of sessions# to be used for the control file backup after another backup operation.# The valid range of MAX_CONTROL_SESSIONS is from 1 to 32.# Default: MAX_BACK_SESSIONS or MAX_ARCH_SESSIONS,


of 116

Version 1.2


April 1, 2007

depending on the type of# the control file backup.#--------------------------------------------------------------------------#MAX_CONTROL_SESSIONS 1 # Tivoli Storage Manager client sessions for control # file backup.

#--------------------------------------------------------------------------# Number of parallel sessions to be established for the restore of files.# Note: This number must not exceed the number of tape drives simultaneously# available to the node for restore processing backup on the Tivoli Storage# Manager servers to be accessed.# The valid range of MAX_RESTORE_SESSIONS is from 1 to 32.# Default: MAX_SESSIONS.#--------------------------------------------------------------------------#MAX_RESTORE_SESSIONS 1 # Tivoli Storage Manager client sessions for restore

#--------------------------------------------------------------------------# Number of backup copies of redo logs.# The valid range of REDOLOG_COPIES is from 1 to 9.# Default: 1.#--------------------------------------------------------------------------#REDOLOG_COPIES 2

#--------------------------------------------------------------------------# Specifies whether a null block compression of the data is to be performed# before transmission to Tivoli Storage Manager.# Although RL compression introduces additional CPU load, throughput can be


of 116

Version 1.2


April 1, 2007

# improved when the network is the bottleneck. RL compression in Data# Protection for mySAP (R) should not be used together with# Tivoli Storage Manager API compression.# Default: NO#--------------------------------------------------------------------------#RL_COMPRESSION YES

#--------------------------------------------------------------------------# Specifies how many files are read simultaneously and are multiplexed into# one data stream to a Tivoli Storage Manager server. Multiplexing is usefull# when the data rate to a Tivoli Storage Manager server is higher (fast# when the data rate to a Tivoli Storage Manager server is higher (fast# tapes, fast network) than the I/O rate of a single disk.# The valid range of MULTIPLEXING is from 1 to 8.# Default: 1 (meaning no multiplexing)#--------------------------------------------------------------------------#MULTIPLEXING 2

#--------------------------------------------------------------------------# Specifies the block size for disk I/O (in bytes).# The default values have been chosen from our performance experiments in# standard hardware environments.# The valid range of BUFFSIZE is from 4KB to 32MB.# Default: 131072 (128 KB) on UNIX, 32768 (32 KB) on Windows.#--------------------------------------------------------------------------BUFFSIZE 131072 # block size in bytes

#--------------------------------------------------------------------------


of 116

Version 1.2


April 1, 2007

# This optional parameter controls how Data Protection for mySAP(R) uses# the internal buffers for transferring data during a backup.# Valid values: SIMPLE | PREVENT | AUTO# Default: SIMPLE#--------------------------------------------------------------------------#BUFFCOPY AUTO

#--------------------------------------------------------------------------# Name of a program to be called before the backup task is started.# Default: none.#--------------------------------------------------------------------------#FRONTEND pgmname parameterlist

#--------------------------------------------------------------------------# Name of a program to be called after the backup task is completed.# Default: none.#--------------------------------------------------------------------------#BACKEND pgmname parameterlist

#--------------------------------------------------------------------------# Maximum number of data base backup versions to be kept.# Note: Version control by Data Protection for mySAP (R) is only activated# if the R/3 release is 3.0C and higher and the parameter MAX_VERSIONS is# not 0.# The valid range of MAX_VERSIONS is from 0 to 9999.# A value of 0 means no versioning.# Default: 0, no versioning.#--------------------------------------------------------------------------


of 116

Version 1.2


April 1, 2007

#MAX_VERSIONS 4

#--------------------------------------------------------------------------# Indicates whether processing is to be done unattended or whether human# intervention is allowed.# Default:# YES for backup processing# NO for restore processing#--------------------------------------------------------------------------#BATCH YES # unattended automated operation#BATCH NO # manual operation

#--------------------------------------------------------------------------# Control of error situations: Indicates whether and when database backups# and restore operations should be ended when an error occurs during# unattended processing.# Valid values:# YES: Exit if a single file cannot be backed up or restored.# NO: Do not exit when an error occurs.# the number of errors resulting in exiting the processing.# The valid range of EXITONERROR is from 0 to 100.# Default: NO.#--------------------------------------------------------------------------#EXITONERROR 3 # exit after 3 errors

#--------------------------------------------------------------------------# Control of information for reporting purposes, e.g. messages, statistics.# Default: NO (no additional data will be reported).#--------------------------------------------------------------------------#REPORT NO # no additional messages#REPORT YES # all additional messages


of 116

Version 1.2


April 1, 2007

#REPORT 2 # all additional messages + summary

#--------------------------------------------------------------------------# Controls generation of a trace file.# Note: we recommend using the trace function only in cooperation with# Data Protection for mySAP (R) support.# Default: OFF.#--------------------------------------------------------------------------#TRACE OFF

#--------------------------------------------------------------------------# The full path of the trace file.# Note: for an actual trace the string '%BID' will be replaced by# the current backupid.# (.../backint_%BID.trace changes to .../backint_SAP___9809182300.trace).# Default: none.#--------------------------------------------------------------------------#TRACEFILE /oracle/C21/dbs/backint.trace#TRACEFILE /oracle/C21/dbs/backint_%BID.trace

#--------------------------------------------------------------------------# Denotes the maximum size of the trace file in KB.# If not specified, the trace file size is unlimited.#--------------------------------------------------------------------------#TRACEMAX <max. size> # trace file size in KB

#--------------------------------------------------------------------------# Specify the full path of the configuration file.# Default: none.#--------------------------------------------------------------------------


of 116

Version 1.2


April 1, 2007

CONFIG_FILE /oracle/BPS/102_64/dbs/initBPS.bki

#--------------------------------------------------------------------------# Number of times to retry saving/restoring a file in case an error occurs.# The valid range of FILE_RETRIES is from 0 to 100.# Default: 3.#--------------------------------------------------------------------------#FILE_RETRIES 3

#--------------------------------------------------------------------------# Denotes if Data Protection for mySAP (R) shall send error/status# information to a Tivoli Storage Manager server.# The servername must match one of the servers listed in a SERVER statement.# Valid values for verbosity are ERROR | WARNING | DETAIL.# Default: none.#--------------------------------------------------------------------------#LOG_SERVER servername [verbosity]#LOG_SERVER server_a ERROR

#--------------------------------------------------------------------------# Denotes if Data Protection for mySAP (R) shall use a manual sorting file# for disk sorting.# Default: none.#--------------------------------------------------------------------------#SORT_FILE /oracle/C21/dbs/manual_sort_file

#--------------------------------------------------------------------------# Denotes if Data Protection for mySAP (R) shall use a compressed filesize# sorting file for disk sorting.


of 116

Version 1.2


April 1, 2007

# For backup simulations with compression (see manual) this parameter must# be set to a valid file.# Default: none.#--------------------------------------------------------------------------#COMPR_INFO /oracle/C21/dbs/initSID.cfi

#**************************************************************************# Statement for servers and paths.# Multiple servers may be defined.#**************************************************************************

SERVER TSM_BALCO # Servername SESSIONS 5 # Maximum number of sessions # to server_a PASSWORDREQUIRED YES # Use a passwordADSMNODE SAPBPD # Tivoli Storage Manager Nodename BRBACKUPMGTCLASS MDB # Mgmt-Classes BRARCHIVEMGTCLASS MLOG # Mgmt-Classes TCP_ADDRESS 10.101.71.71 # IP address of network interface # on server_a # Overrides IP address of dsm.sys# USE_AT 0 1 2 3 4 5 6 # Days when server_a is used for # backup#**************************************************************************# USE_AT : 0=Su 1=Mo 2=Tu 3=We 4=Th 5=Fr 6=Sa# The valid range of USE_AT is from 0 to 6.# Default: all days


of 116

Version 1.2


April 1, 2007

#**************************************************************************

#SERVER server_b # Servername, as defined in dsm.sys# SESSIONS 2 # Maximum number of sessions # to server_b# PASSWORDREQUIRED YES # Use a password# ADSMNODE NODE # Tivoli Storage Manager Nodename# BRBACKUPMGTCLASS MDB # Mgmt-Classes for database backup# BRARCHIVEMGTCLASS MLOG1 MLOG2 # Mgmt-Classes for

redo log backup# TCP_ADDRESS 192.168.1.1 # IP address of network interface # on server_b # Overrides IP address of dsm.sys# USE_AT 0 1 2 3 4 5 6 # Days when server_b is used for # backup#**************************************************************************# USE_AT : 0=Su 1=Mo 2=Tu 3=We 4=Th 5=Fr 6=Sa# Default: all days#**************************************************************************

#--------------------------------------------------------------------------# End of profile

END


of 116

Version 1.2


April 1, 2007

List of Transactions performed for a daily system monitoring

RZ20 (CCMS System Monitoring / Other Monitoring Tools)


of 116

Version 1.2


April 1, 2007


of 116

Version 1.2


April 1, 2007

SM21 (Sytem Log)

SPAD (Output Devices in SAP spool System)


of 116

Version 1.2


April 1, 2007

SP01 (Spool Request)BALCO - Confidential

of 116

Version 1.2


April 1, 2007

SM50 (Checking Work process Status)

SM51 (List of SAP systems with their work process status)


of 116

Version 1.2


April 1, 2007

ST22 ( ABAP Short Dumps)

SM12 (Select lock Entries)

SM13 (Update Requests)

SM35 (Batch Input Session)


of 116

Version 1.2


April 1, 2007

SM37 (Checking Background Jobs)


of 116

Version 1.2


April 1, 2007

ST02 (Tune Summary)


of 116

Version 1.2


April 1, 2007

DB13 ( DBA Planning Calendar)


of 116

Version 1.2


April 1, 2007

DB02 (Database Monitoring Tool)

DB12 (Backup log)


of 116

Version 1.2


April 1, 2007

ST04 (Checking Alert File)


of 116

Version 1.2


April 1, 2007

SCC4 (Client Overview)


of 116

Version 1.2


April 1, 2007

SM04 (User Overview)

OS06 ( Operating System Overview)


of 116

Version 1.2


April 1, 2007

RZ01 (Job Schedulling Monitor)


of 116

Version 1.2


April 1, 2007

ST06 (Operating System Monitor)


of 116

Version 1.2


April 1, 2007

SE09 (Transport Organiser)


of 116

Version 1.2


April 1, 2007


of 116

Version 1.2


April 1, 2007

Transport Request Form


of 116

Version 1.2


April 1, 2007

Requestor Name &Userid Date

Change Request Customizing Workbench

Type of Change Client-dependent Client-independent

Source System BDS / BWD / EPD / SRD

Source Client 020/130

Target R/3 System BDS Target Client(s) 030/040

Target R/3 System QA BQS/BWP/EPP/SRP Target Client(s) 100

Tested in QA by (please sign) Target R/3 System Production -BPS Target Client(s) 100

Request Number Description

Tested By Whom

Reason for Transporting

Special Requirements

Approved by (please sign)

BALCO-Basis Team USE ONLY

Imported in to BDS by Date

Transport Log Return Codes 0 Transport (export and import test) was successful. 4 Warning messages were generated. 8 Error messages were generated. 12 Fatal error has occurred. other errors

Imported in to QA by Date

Transport Log Return CodesImported in to BPS by Date


of 116

Version 1.2


April 1, 2007

Transport Log Return CodesException handling - Corrected change request

DateReason

Project Management Approval

Date

User I.D Creation Form

1. SAP USER ID

2. User Name:

3 .Designation:

4 .Primary Module for Logon Groups FI / CO / MM / SD / HR / PP / PM / QM / ESS / ABAP / Basis / BW / SRM / Operator

5 .Department/Branch:

6 .Telephone No:

7 .Email Id:

8 .Login reqd for System? (BDS/BQS/BPS/BWD/BWP/EPD/EPP )

9 .Login reqd for Client? (020 / 030 / 040 / 100 / 130 )

10 .Login reqd from Date?

11 .Login reqd till Date?

12 .Authorization reqd? Please Mention Generated Profiles 13.User Signature with Date

14 .Signature of Core team member/ Department Manager

15. Signature of HOD I.T

FOR BASIS USER:


of 116

Version 1.2


April 1, 2007

Created By: Date : Login Id : Communicated(Yes / No)

Communication Method

Profile Parameter Change Request

Date: Server:Instance: Parameter Type: (profile)

Parameter Information

Parameter Name:

Parameter Details

Profile name:

Last change date:

Parameter Values

Present Value :

Default Value if applicable: Requested Changed Value:

Priority : High medium low

Reason for change:

Requisitioner : Approved By


of 116

Version 1.2


April 1, 2007

Remarks from Approver:


of 116

Version 1.2