BASIS FAQs - 2

1.      What is transport domain?

A transport domain comprises all SAP Systems jointly administrated through the TMS (domain controller).

 

2.      What is transport group?

Group of SAP systems which are having common transport directory.

 

3.      How do you configure the TMS?

You must define which R/3 Systems in the system landscape should be combined in a transport domain and which R/3 System is to be the transport domain controller

 

4.      What are the transport routes?

A route between any 2SAP systems in a landscape can be a consolidation or delivery path.

Consolidation – between development and quality

Delivery – from quality to production

 

5.      How do you do the transports?

The transport routes are used to define in which target system you want to consolidate and deliver change requests.

Transport request will be released in the source system and are imported in the destination system.

SE09 and SE10 are used to release the Transport request

STMS – used to import the request.

In OS level use program tp.

Syntax – tp import <SIDXXX> <SID> clientXXX ux

 

6.      What will happen during the export process?

Files will be created in the OS level in the transport directory

R…… - data files

K…… - control files

Transport directory – usr/sap/trans/data

                                 usr/sap/trans/cofiles

 

7.      What will happen during the import process?

               Datas will be imported in to the database. Get in to usr/sap/trans/bin Syntax – tp import <SIDXXX> <SID> clientXXX ux

 

8.      What types of files are created during the export?

               R…… - data files

               K…… - control files

 

9.      What are the problems usually occurs during the transport and what is return codes?

               0 – succ

               4- Warnings

               8 – Error

               Above 8 – different types of errors

 

10. How do you configure transport profile?

The transport control program requires a transport profile that contains information about establishing the database connection for all R/3 Systems in the transport domain. TMS generates and manages this transport profile as a part of the transport domain configuration. You do not have to adjust the transport profile using operating system functions.

 

11. What is the R3 system startup and shutdown process?

First database will started and then messaging server at last dispatcher will start and it will connect with the messaging server.

 

12. How do you do the load balancing?

By configuring the logon groups. Logon group is a group of application servers.

 

13. What will you do when you cannot login to a dialog server?

First check whether the services are running in the server Check different log files in the OS and database level.

 

14. How do you extend the table space?

You can use SAPDBA for Oracle to extend a tablespace, that is, add a data file. The SAP System can be either active or closed when you extend a tablespace.

You need not shut down the database system if you want to add a data file to a tablespace.

 

Procedure

1.      Choose Tablespace Administration ® Tablespace and enter the name of the tablespace that you want to extend by adding a data file.

2.      Choose Alter tablespace <tablespace name> add data file.

SAPDBA shows a new menu for altering the tablespace.

SAPDBA proposes a path and size for the new data file. It also displays the details of the file system or raw device and its free space, as in the following example for a file system.

New path: '/oracle/LMA/sapdata1/btabd_2/btabd.data2'

New size: 121624 K

File system: '/dev/dsk/c1t1d0s2'

Free space: 121624 K

3.      To show the details of existing data files, choose Show existing data files.

SAPDBA displays the details of the file (or files), including its sequence number, size, and full name with path. For example:

# Size in K Data file name (file system)

-- --------- ------------------------------------------------------------

1 335656 /oracle/LMA/sapdata1/btabd_1/btabd.data1 (/dev/dsk/c1t1d0s2)

4.      To change the path for the new data file, choose new path, Select new path from a list of file systems, or Select new path from a list of raw devices.

You can only change the path, not the data file name. In the above example, you could change /oracle/LMA/sapdata.

5.      To change the size for the new data file, choose New Size and enter the size in bytes, kilobytes, megabytes, gigabytes, or terabytes.

6.      To add more than one new data file, do the following:

a.      Choose Define more than one new data file and select the next free entry.

SAPDBA displays default values for the new data file, as shown above for the first new data file.

b.      Accept the default values or change them as required.

7.      To set Autoextend from the default OFF to ON, do the following:

a.      Choose Autoextend.

SAPDBA prompts you for the incremental and maximum file sizes used in automatic table extension:

The incremental size is the size of the new file that is automatically added to the tablespace to prevent overflow.

The maximum size is the maximum size for automatic extension of the tablespace. Beyond the maximum size, you have to extend the tablespace manually.

b.Enter the incremental and maximum file sizes.

8.      Choose Start to begin adding the data file.

SAPDBA checks that that there is enough space to add the new data file, showing a display like the following:

SAPDBA: Checking space for data files of tablespace

-------------------------------------------------------------

File system: '/dev/dsk/c1t1d0s2'

Current free space: + 20856 K

New data files: - 56 K

Left free space: = + 20800 K -> O.K.

-------------------------------------------------------------

SAPDBA also performs some other checks before adding the file

9.      Enter RETURN to add the data file(s).

SAPDBA adds the new data file(s) to extend the tablespace and also generates a log, <timestamp>.ext. You can check this log to verify that the tablespace extension was successful.

SAPDBA creates a directory or a symbolic link for the data file. The control files (old and new) are backed up under the directory <timestamp> belonging to the log file <timestamp>.ext. SAPDBA then creates the data file with ALTER TABLESPACE ADD DATAFILE. If any of these operations fail, SAPDBA stops immediately.

 

If SAPDBA cannot add the new data file, it deletes the corresponding directory or symbolic link and cancels the tablespace extension. Your system and database are unchanged. Use the Oracle ALERT and trace files to analyze and correct the problem, then repeat the tablespace extension.

When SAPDBA has successfully created the new data file, it automatically goes to the Backup database menu, so that you can back up the extended tablespace.

10.  Be sure to back up the extended tablespace