SAP Network Diagnosis with NIPING

To help diagnose the network or measure network metrics you can test the connection using SAP's NIPING program. You can use NIPING to analyze the network connection between any two machines running SAP software, for example between:

• Frontend PC and application server

• Two application servers, perhaps belonging to different SAP systems

• Application server and database server or live cache server

• RFC server or client programs and application server

The machines can be connected either by a local area network (LAN) or wide area network (WAN).

In contrast to the normal PING command, NIPING operates on the TCP socket layer, which is the same layer used by SAP application programs. Therefore, NIPING can be used to identify also errors related to the TCP and socket implementation on the platform.

Please fetch the latest version of NIPING from the service market place as described in SAP note 799428. If this is not possible for you, you can use the NIPING which is located in the executables directory on any SAP server.

How to use NIPING
Starting NIPING without arguments displays a short help message. Find a short exlanation of the most important options below:

First start the NIPING server on computer A (e.g., the Application Server) with the command line:
  niping -s -I 0        (the last character is zero, not the letter O)

Then start the client (e.g. on the front-end machine) with the command:
  niping -c -H <nipingsvr> [ -B <buffersize> -L <loops> -D <delay> ]

           <nipingsvr> may also be the host name or the IP address of host A. The remaining arguments are optional.
           <buffersize> (default 1000 bytes) determines the size of the data packets. Please test at least the values 500, 1000, 1400, 1500, 4000 and 10000. This test is especially important to find errors related to the maximum transmission unit (MTU). Please also refer to notes 26086, 107407, 67098 and 44803.
           <loops> is the number of packets sent (default 10). To find spurious erors it may help to simulate high network load using 1000 loops or more. For a permanent test use a number of e.g. 1000000 loops.
If you test during productive hours and don't want to consume too much bandwidth you can set a <delay> between requests (<delay> is in milliseconds).

Examples

1) Measuring network metrics (throughput and RTT)

Throughput is the number of bytes per second that an application can send through the network. Measured values will vary according to the actual load of the network. Round trip time (RTT) is the time for a small data packet to be transmitted from the sender to the receiver and back again to the sender. RTT is mainly influenced by network topology and equipment and normally cannot be improved significantly by increasing  bandwidth.
1.1) Measuring throughput

niping -c -H <nipingsvr> -B 100000
The use of large blocks reduces impact of network latency. After completion niping will report throughput as value tr2 in kB/s (kilobytes per second).

Typical throughput values:

Fast Ethernet - 10000 KB/s
WLAN (IEEE 802.11g) - 5000 KB/s
DSL 1000 - 100 KB/s
ISDN - 7 KB/s
UMTS - up to 700 KB/s
GPRS - 6 KB/s
1.2) Measuring RTT

niping -c -H <nipingsvr> -B 1 -L 100
(The buffersize of 1 may cause an error in older versions of niping. If so please use  niping -c -H <nipingsvr> -B 20 -L 100   instead)
Small blocks and 100 loops are used to measure the average RTT. The value av2 represents the RTT in ms (milliseconds)

Typical RTT values:

Fast Ethernet - <1 ms
WLAN (IEEE 802.11g) - 10 ms
Cable - 10 ms
DSL without Fastpath - 40 ms
ISDN - 200 ms
UMTS - 300 up to 400 ms
GPRS - 700 up to 1000 ms
Satellite - 1000ms
2) Long LAN stability test:

niping -c -H <nipingsvr> -B 10000 -D 100 -L 360000

This test will consume 100000 Bytes/second of bandwidth (about 10% of a 10 mbps Ethernet) and run for 10 hours.
You need the newest NIPING version for this test, please follow SAP note 799428 to get it.
3a) Long WAN test (stability):

niping -c -H <nipingsvr> -B 200 -D 1000 -L 36000

This test uses about 5% of an ISDN line of 64 kbps and also runs for 10 hours.
Interpreting NIPING's output: In this test, the times measured by NIPING correspond mostly to the network latency (round trip time - RTT). The throughput measurement has no meaning in this case.
3b) Long WAN test (idle timeouts):

niping -c -H <nipingsvr> -P -D 3600000

This test establishes a TCP connection and sends a test packet every hour (delay of 3600000ms). It runs for 10 hours. The goal is to see if the TCP connection is disrupted by some "idle timeout". Most firewalls apply such timeouts. But SAP applications make use of long lasting TCP connection and thus may be hit by such idle timeouts.

You need the newest NIPING version for this test, please follow SAP
note 799428 to get it.
4) Short throughput/stability test:

niping -c -H <nipingsvr> -B 1000000 -L 100

Tests connection with 100 MB of data as fast as possibly. On a 100 Mbps Ethernet this should take about 10 seconds. During the test, other applications may be impaired. On a slow WAN connection, reduce loops to 10 (-L 10).

Interpreting NIPING's output: This test uses large blocks of data. Therefore, it can be used to measure throughput available to NIPING. Check the output "tr2". It states the throughtput in kilo-byte per second measured from all packets except the fastest and the slowest one. Multiply this value by 10 to obtain an estimate of the line bandwidth in kilo-bit per second (kbps). Does this value differ by a large amount (at least a factor of two) from the one expected for the connection you are analyzing? This could be an indication of network problems: Either the line is overloaded, or there are other problems with the connection.
5) MTU test:

See related notes 155147 and 107407 for an explanation of this test (even if you are not analyzing a Windows system).

niping -c -H <nipingsvr> -B <nnn>

Vary <nnn> according to these values: 500, 1000, 1400, 1500, 4000, 10000 and 40000
Additional information

Note for Windows NT/2000: If client or server are under heavy load while you perform the measurement, you should start NIPING with high priority. To do this, start NIPING with the following command line:
start /b /wait /high niping <normal_NIPING_arguments>

Please test the TCP/IP communication between all concerned machines. Using the options described above, you can either do a long time connection test to find intermittent problems or do a short term stress test with large packets to find fundamental connection problems.

NIPING should not abort with an error message under any circumstances. An error is always indicated by a line starting with "*** ERROR ...".
Entries like "NiIRead: hdl 0 recv would block (errno=EAGAIN)" do not indicate an error!

If you can reproduce an error using NIPING then the problem is definitely related to the network layers, not to the application.
Information needed by SAP

If you need further assistance from SAP support, please start both client and server with the additional argument
-V 2 -T <tracefile>

Replace <tracefile> with an appropriate file name for trace output. Now send both trace files along with a description of what you did to produce the traces to SAP. (For example, attach the files to a problem message).

Header Data

Release Status:	Released for Customer
Released on:	12.01.2012  13:26:05
Master Language:	English
Priority:	Recommendations/additional info
Category:	Special development
Primary Component:	BC-NET Network Infrastructure
Secondary Components:	BC-CST-NI Network Interface

 Note 500235 - Network Diagnosis with NIPING

Read More

NOTE : Network performance

Summary

Symptom

1. What is the focus of this note?

2. For which parts of the SAP environment is the network important?

3. Which symptoms indicate performance problems in the network area?

4. Which communications protocols are used in the SAP environment?

5. Which statistics are important for a network?

6. How can the statistics of a network be measured?

7. What must be taken into account when measuring the network statistics?

8. What other network tools exist?

9. What are good values for throughput and roundtrip time?

10. What is to be done if a communication has a throughput that is too low?

11. What is to be done if a communication has increased roundtrip times?

Other terms
FAQ, frequently asked questions
Solution

1. What is the focus of this note?

              This note cannot and will not provide an overview of all the aspects of networks. Instead, this note focuses on SAP-specific details and on performance aspects in particular.

2. For which parts of the SAP environment is the network important?

              A network is used when software resources communicate with each other across host boundaries, for example:

• Communication between the front end and the SAP system

• Communication between different SAP instances of an SAP system

• Communication of an SAP system with its database

• Communication between different SAP systems (for example, using RFC)

• Communication of SAP systems with non-SAP systems

              In addition, some communications within a host are also comparable with network communications (for example, the connection of an SAP instance with an Oracle database using TCP/IP).
              It is very important to include the network in performance analyses. Network performance problems are often recognized too late.

3. Which symptoms indicate performance problems in the network area?

              Time that is lost in the network usually results in "lost" time and apparently inconsistent time information for the partners who are involved in the communication. For example, a communication between an SAP instance and an Oracle database has the following typical symptoms:

• SAP transactions like SM50 or SM66 show a considerably higher number of database accesses than the Oracle session overview (for example, transaction ST04).

• SQL traces (transaction ST05) show considerably longer runtimes for SQL statements than the Oracle Shared Cursor Cache (column ELAPSED_TIME in V$SQL).

• SQL traces show individual runtime peaks that cannot be explained by other factors, such as disk accesses, or resource bottlenecks.

• The average database response time (transaction ST03N) increases even though Oracle does not seem to cause the problem.

              For more information, see Note 805934.

4. Which communications protocols are used in the SAP environment?

              Typical protocols on the individual layers are:

• Application layer

• Presentation layer:

• Oracle: TTC (Two Task Common)

• Session layer:

• Oracle: TNS (Transparent Network Substrate)

• Transport layer:

• SAP: NI (Network Interface)

• TCP

• Network layer:

• IP

• Data transfer layer

• Transfer technology layer

5. Which statistics are important for a network?

              The following properties are important for a network:

• Bandwidth:

           The bandwidth indicates what volume of data (typically in bits) for each time unit can theoretically be transferred by the technology used.

• Throughput:

           The throughput indicates what volume of data (typically in bits) for each time unit can be transferred by an application. The upper limit of the throughput is determined by the bandwidth. If different applications and processes use the same connection in parallel, the throughput that is actually possible may also be considerably lower than the theoretical bandwidth.

• Latency:

           The latency indicates how long it takes to send a request from a source to a target.

• Roundtrip time:

           The roundtrip time indicates how long it takes for an entire communication: source -> target -> source. It is usually about twice as long as the latency time.
              In addition, the reliability of the network is of central importance, that is, there should be as few communication errors as possible.

6. How can the statistics of a network be measured?

• Throughput

           You can use the SAP tool NIPING to measure the throughput that is currently possible:

• Start the NIPING server on <target_host> using:

                    niping -s

• Start the NIPING client on <source_host> using:

                    niping -c -H <target_host> -B 30000

• For example, the output is as follows:
  
  ------- times -----
  avg    4.695 ms
  max    36.867 ms
  min    0.658 ms
  tr  12479.766 kB/s
  excluding max and min:
  av2     1.178 ms
  tr2 49729.472 kB/s

• The approximate throughput is displayed in the last line. In this case, it is about 50 Mbyte/s, that is, 400 Mbit/s.

• For more information about NIPING, see Note 500235.

• Roundtrip time

           You can use the SAP tool NIPING to measure the roundtrip time:

• Start the NIPING server on <target_host> using:

                    niping -s

• Start the NIPING client on <source_host> using:

                    niping -c -H <target_host> -B 20 -L 10000

• For example, the output is as follows:
  
  ------- times -----
  avg    0.181 ms
  max    30.678 ms
  min    0.061 ms
  tr    107.963 kB/s
  excluding max and min:
  av2     0.178 ms
  tr2   109.808 kB/s

• The approximate roundtrip time is displayed in the line before the last line - in this case, it is 178 microseconds.

• It is useful to repeat this test several times to familiarize yourself with the typical values and differences.

• For more information about NIPING, see Note 500235.

7. What must be taken into account when measuring the network statistics?

              For different reasons, problems may occur when you measure network statistics:

• If there is a resource bottleneck on one of the servers involved (CPU bottleneck, paging, and so on), poor NIPING results may also be caused by this resource bottleneck.

• To catch temporary outliers, you must constantly monitor the network. Individual NIPING tests are not sufficient to do this.

• Using PING to determine the roundtrip time causes problems because PING is based on the ICMP protocol, which the network may handle differently than typical SAP communications.

8. What other network tools exist?

              In addition to the tools mentioned above, the following tools are also available:

• TRACERT (WINDOWS) / TRACEROUTE (UNIX)

           You can use this tool to determine the stations between a source host and a target host:

Route to the target host:  tracert    <target_host> (WINDOWS)
                    traceroute <target_host> (UNIX)

• NETSTAT

           You can use NETSTAT to read details about the network configuration, for example:

Active connections: netstat
Routing table:     netstat -r

• NSLOOKUP

           You can use NSLOOKUP to check the name resolution of a server:

Details about the name resolution: nslookup <host>

• IPCONFIG (WINDOWS)

           You can use IPCONFIG to display the current network configuration.

Current information:            ipconfig
Renewing all network adapters: ipconfig /renew

9. What are good values for throughput and roundtrip time?

• Throughput

           On all communication paths that involve larger data volumes, we recommend that you use a network topology with at least Gigabit Ethernet. In this case, Gigabit Ethernet results in typical throughputs of 400 Mbit/s.
           For connections that are not critical, or for communication channels with less data traffic, you can also use topologies with a lower bandwidth. For example, 100 Mbit Ethernet typically allows a throughput of 80 Mbit/s.

• Roundtrip time

           Increased roundtrip times may cause performance to deteriorate gradually. This applies even more, the greater the number of fast, small communications. For example:

• If you execute many fast queries on an Oracle database and if the "Time / User Call", therefore, is only 1.0 ms, a roundtrip time of 0.5 ms has a considerable effect and prolongs the average database accesses by 50 %.

• If the "Time / User Call" on Oracle is 10 ms instead, the network causes only an overhead of 5 % if it has a roundtrip time of 0.5 ms.

           Therefore, it is difficult to define values that are generally good. However, for performance-critical LAN environments (for example, a server network between SAP and the database), you can assume that the following threshold values apply:

• Good value: Roundtrip time <= 0.3 ms

• Moderate value: 0.3 ms < roundtrip time <= 0.7 ms

• Below average value: Roundtrip time > 0.7 ms

           For WAN environments, considerably longer roundtrip times are often acceptable.
           If both communication partners run on the same server and if, therefore, no classic network communication is required, roundtrip times are typically lower than or equal to 0.1 ms.

10. What is to be done if a communication has a throughput that is too low?

              The following approaches are available:

• Determine the main cause of the large load on the network. Individual SQL statements that read a high number of data records from the database and that are executed several times in parallel may already cause an overload on 100 Mbit networks. Therefore, with regard to Oracle databases (for example), check whether there are individual SQL statements with a high number of fetches or processed data records. Perform this check in accordance with Note 766349. Backups and replications may also have significant bandwidth requirements. Therefore, these operations should not use any critical communication channels (for example, the server network between SAP and the database).

• Ensure that critical communications run in their own network segment and that they cannot be interrupted by an external load.

• Check whether you can use a higher bandwidth by implementing short-term measures (for example, by reconfiguring the network).

• Switch to a network topology with a higher bandwidth.

11. What is to be done if a communication has increased roundtrip times?

              If you experience performance problems due to the roundtrip time, you can improve the situation as follows:

• If the problem is caused mainly by an increased roundtrip time, take account of the following points:

• Consult your network partner for the analysis and optimization of the network topology. The TCP/IP settings, such as the Maximum Transmission Unit (MTU) or the TCP Window Size, may affect network performance considerably.

• If possible, execute time-critical activities with a high number of roundtrips (for example, SAP background jobs) locally on the target server (for example, on the database server).

• When you use an Oracle database, ensure in accordance with Note 562403 that the Oracle Net configuration (TCP.NODELAY, SDU, DEFAULT_SDU_SIZE, and so on) is optimal.

• If the high number of roundtrips is also a cause of the problem, try to reduce the number of roundtrips:

• In the case of database accesses, avoid executing many individual database queries from the ABAP and try to bundle several queries instead.

• Test whether increasing rsdb/max_blocking_factor and rsdb/max_in_blocking_factor improves the situation for individual SQL statements or for the entire system. For Oracle, also refer to Note 881083 for more information about this.

Header Data

Release Status:	Released for Customer
Released on:	23.12.2008  17:00:30
Master Language:	German
Priority:	Recommendations/additional info
Category:	FAQ
Primary Component:	BC-NET Network Infrastructure
Secondary Components:	BC-DB-ORA Oracle

Affected Releases

Release-Independent

Note 1100926 - FAQ: Network performance

Read More

How to Configure WEB-GUI for SAP

Table of Contents

Step 1: Verifying the configuration parameters for ICM
Step 2: Activate Required Services
Step 3: Publishing Services
STEP 4: Login In to the SAP GUI though Web.

Summary

The purpose is this document is to show step by step to configure webgui for SAP Netweaver . Applies to SAP Netweaver R/3 System

Step 1: Verifying the configuration parameters for ICM.

Use Transaction SMICM (ICM Monitor).
Displays the ICM configuration and monitoring. Make sure it is running. Check the following ICM parameters.

[Menu-> Goto -> Parameters ->Display]

1. icm/server_port_0 PROT=HTTP,PORT=8000
2. icm/host_name_full <Full Qualified Domain Name>

I will use the domain name as testp1.bomain.cpstl

Following parameters should be checked.

Step 2: Activate Required Services:

Following 3 services need to be enabled.

1. /default_host/sap/bc/gui/sap/its/webgui
2. /default_host/sap/public/bc/ur
3. /default_host/sap/public/bc/its/mimes

Use Tcode ‘SICF’ to enable services. Then execute it to show the services trees.

Then activate the mentioned services according to the below guide.

1. /default_host/sap/bc/gui/sap/its/webgui
2. /default_host/sap/public/bc/ur
3. /default_host/sap/public/bc/its/mimes

Right click on the relevant service and then activate it.

Step 3: Publishing Services:

Run T-Code SIAC_PUBLISH_ALL_INTERNAL  to activate the services. Will take few minutes. While running it will show the status message like:

Finally the following screen can be seen.

STEP 4: Login In to the SAP GUI though Web

Type one of the following URLin the web browser

1. http://<IP>:8000/sap/bc/gui/sap/its/webgui
2. http://testp1.bomain.cpstl:8000/sap/bc/gui/sap/its/webgui

Then the login screen will come.

Then ask you to provide the username and password. Login an roam in to the SAP 

Refecence : SAPNOTE 517484

Author:      Priyashantha Fernando

Company: CPSTL – Sri Lanka

Original Post @ http://scn.sap.com/docs/DOC-29485

Read More

How To Extend Table space on oracle on Linux

How To Extend Table space on oracle on Linux

Table of Contents

1. Check the table space before extend
2. Using SAP GUI
3. Check Using SQL on OS and select the datafiles of tablespaces.
4. Extend Table space on oracle.
5. Login in to the console from <orasid> user.
6. Run brtools with following options.
7. Verify the extended table-space.
8. Though SAP GUI
9. Check Using SQL on OS and select the datafiles of tablespaces.

Summary

The purpose is this document is to show how to extend a database table space using BRTOOLS in LINUX environment and then verify whether the in the new data file has been added correctly or not. The

The Document will guide to use: Commands and GUI usage for particular task.

Applies to SAP Netweaver R/3 System

Check the table space before extend Using SAP GUI

Use TCODE DB02 and check the database size. [The Total size is 293.97 GB]

Use tcode DB02 select the tablespace which is intend to extend. Eg: PSAPSR3
[= PSAPSR3]

It shows the last datafile as the sr3.data18.

Check Using SQL on OS and select the datafiles of tablespaces.

Login to SQL from the user <oraSID>

Erppi1# su orapi1

erppi1:orapi1 54>

erppi1:orapi1 53> sqlplus / as sysdba

SQL>

SQL> select file_name from dba_data_files;

Then It will display datafiles till the last.

Eg : /oracle/PI1/sapdata4/sr3_18/sr3.data18

Extend Table space on oracle Login in to the console from <orasid> user

Log in to the operating system with a user who has authorize for Oracle DBA and then run the command BRTOOLS.

Erppi1# su orapi1

erppi1:orapi1 54>

Run brtools with following options

Run brtools and then follow the following steps.

erppi1:orapi1 54> brtools

BR0651I BRTOOLS 7.00 (32)

BR0280I BRTOOLS time stamp: 2012-06-26 09.51.52

BR0656I Choice menu 1 - please make a selection

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

BR*Tools main menu

1 = Instance management

2 - Space management

3 - Segment management

4 - Backup and database copy

5 - Restore and recovery

6 - Check and verification

7 - Database statistics

8 - Additional functions

9 - Exit program

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

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

BR0662I Enter your choice:

2

BR0280I BRTOOLS time stamp: 2012-06-26 09.51.56

BR0663I Your choice: '2'

BR0280I BRTOOLS time stamp: 2012-06-26 09.51.56

BR0656I Choice menu 5 - please make a selection

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

Database space management

1 = Extend tablespace

2 - Create tablespace

3 - Drop tablespace

4 - Alter tablespace

5 - Alter data file

6 - Move data file

7 - Additional space functions

8 - Reset program status

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

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

BR0662I Enter your choice:

1

BR0280I BRTOOLS time stamp: 2012-06-26 09.51.56

BR0663I Your choice: '1'

BR0280I BRTOOLS time stamp: 2012-06-26 09.51.56

BR0657I Input menu 81 - please check/enter input values

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

BRSPACE options for tablespace extension

1 - BRSPACE profile (profile) ...... [initPI1.sap]

2 - Database user/password (user) .. [/]

3 ~ Tablespace name (tablespace) ... []

4 - Confirmation mode (confirm) .... [yes]

5 - Scrolling line count (scroll) .. [20]

6 - Message language (language) .... [E]

7 - BRSPACE command line (command) . [-p initPI1.sap -s 20 -l E -f tsextend]

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

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

BR0662I Enter your choice:

c

BR0280I BRTOOLS time stamp: 2012-06-26 09.52.04

BR0663I Your choice: 'c'

BR0259I Program execution will be continued...

BR0291I BRSPACE will be started with options '-p initPI1.sap -s 20 -l E -f tsextend'

BR0280I BRTOOLS time stamp: 2012-06-26 09.52.04

BR0670I Enter 'c[ont]' to continue, 'b[ack]' to go back, 's[top]' to abort:

c

BR0280I BRTOOLS time stamp: 2012-06-26 09.52.11

BR0257I Your reply: 'c'

BR0259I Program execution will be continued...

###############################################################################

BR1001I BRSPACE 7.00 (32)

BR1002I Start of BRSPACE processing: seivvhdr.tse 2012-06-26 09.52.11

BR0484I BRSPACE log file: /oracle/PI1/sapreorg/seivvhdr.tse

BR0280I BRSPACE time stamp: 2012-06-26 09.52.11

BR1009I Name of database instance: PI1

BR1010I BRSPACE action ID: seivvhdr

BR1011I BRSPACE function ID: tse

BR1012I BRSPACE function: tsextend

BR0280I BRSPACE time stamp: 2012-06-26 09.52.11

BR0656I Choice menu 301 - please make a selection

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

Tablespace extension main menu

1 = Extend tablespace

2 - Show tablespaces

3 - Show data files

4 - Show disk volumes

5 * Exit program

6 - Reset program status

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

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

BR0662I Enter your choice:

c

BR0280I BRSPACE time stamp: 2012-06-26 09.52.23

BR0663I Your choice: 'c'

BR0259I Program execution will be continued...

BR0280I BRSPACE time stamp: 2012-06-26 09.52.24

BR0658I List menu 302 - please select one entry

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

List of tablespaces for extension

1. Pos. Tablespace    Files/AuExt.   Total[KB] Used[%]    Free[KB]  MaxSize[KB]

  1 - PSAPSR3          18/18      175484928     96.07 6901376    176291840

  2 - PSAPSR3700        9/9        88948736     87.78 10866112     88948736

  3 - PSAPSR3USR        1/1          389120     95.82 16256     10240000

  4 - PSAPTEMP          1/0         2048000      0.00 2048000      2048000

  5 - PSAPUNDO          1/1         7987200      0.00 7987136     10240000

  6 - SYSAUX            1/1          634880     89.99 63552     10240000

  7 - SYSTEM            1/1          921600     98.41 14656     10240000

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

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

BR0662I Enter your selection:

1

BR0280I BRSPACE time stamp: 2012-06-26 09.52.27

BR0663I Your selection: '1'

BR0280I BRSPACE time stamp: 2012-06-26 09.52.27

BR0657I Input menu 303 - please check/enter input values

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

Options for extension of tablespace PSAPSR3 (1. file)

1 * Last added file name (lastfile) ....... [/oracle/PI1/sapdata4/sr3_18/sr3.data18]

2 * Last added file size in MB (lastsize) . [9216]

3 - New file to be added (file) ........... [/oracle/PI1/sapdata4/sr3_19/sr3.data19]

4 ~ Raw disk / link target (rawlink) ...... []

5 - Size of the new file in MB (size) ..... [9216]

6 - File autoextend mode (autoextend) ..... [yes]

7 ? Maximum file size in MB (maxsize) ..... []

8 - File increment size in MB (incrsize) .. [20]

9 - SQL command (command) ................. [alter tablespace PSAPSR3 add datafile '/oracle/PI1/sapdata4/sr3_19/sr3.data19' size 9216M autoextend on next 20M maxsize M]

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

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

BR0662I Enter your choice:

5

BR0280I BRSPACE time stamp: 2012-06-26 09.57.52

BR0663I Your choice: '5'

BR0280I BRSPACE time stamp: 2012-06-26 09.57.52

BR0682I Enter integer value for "size" (1-32767) [9216]:

9216

BR0280I BRSPACE time stamp: 2012-06-26 09.57.59

BR0683I New value for "size": '9216'

BR0280I BRSPACE time stamp: 2012-06-26 09.57.59

BR0657I Input menu 303 - please check/enter input values

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

Options for extension of tablespace PSAPSR3 (1. file)

1 * Last added file name (lastfile) ....... [/oracle/PI1/sapdata4/sr3_18/sr3.data18]

2 * Last added file size in MB (lastsize) . [9216]

3 - New file to be added (file) ........... [/oracle/PI1/sapdata4/sr3_19/sr3.data19]

4 ~ Raw disk / link target (rawlink) ...... []

5 - Size of the new file in MB (size) ..... [9216]

6 - File autoextend mode (autoextend) ..... [yes]

7 ? Maximum file size in MB (maxsize) ..... []

8 - File increment size in MB (incrsize) .. [20]

9 - SQL command (command) ................. [alter tablespace PSAPSR3 add datafile '/oracle/PI1/sapdata4/sr3_19/sr3.data19' size 9216M autoextend on next 20M maxsize M]

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

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

BR0662I Enter your choice:

7

BR0280I BRSPACE time stamp: 2012-06-26 09.58.19

BR0663I Your choice: '7'

BR0280I BRSPACE time stamp: 2012-06-26 09.58.19

BR0682I Enter integer value for "maxsize" (0-32767) []:

9216

BR0280I BRSPACE time stamp: 2012-06-26 09.58.24

BR0683I New value for "maxsize": '9216'

BR0280I BRSPACE time stamp: 2012-06-26 09.58.24

BR0657I Input menu 303 - please check/enter input values

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

Options for extension of tablespace PSAPSR3 (1. file)

1 * Last added file name (lastfile) ....... [/oracle/PI1/sapdata4/sr3_18/sr3.data18]

2 * Last added file size in MB (lastsize) . [9216]

3 - New file to be added (file) ........... [/oracle/PI1/sapdata4/sr3_19/sr3.data19]

4 ~ Raw disk / link target (rawlink) ...... []

5 - Size of the new file in MB (size) ..... [9216]

6 - File autoextend mode (autoextend) ..... [yes]

7 - Maximum file size in MB (maxsize) ..... [9216]

8 - File increment size in MB (incrsize) .. [20]

9 - SQL command (command) ................. [alter tablespace PSAPSR3 add datafile '/oracle/PI1/sapdata4/sr3_19/sr3.data19' size 9216M autoextend on next 20M maxsize 9216M]

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

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

BR0662I Enter your choice:

c

BR0280I BRSPACE time stamp: 2012-06-26 09.58.30

BR0663I Your choice: 'c'

BR0259I Program execution will be continued...

BR0280I BRSPACE time stamp: 2012-06-26 09.58.30

BR1091I Next data file can be specified now

BR0675I Do you want to perform this action?

BR0676I Enter 'y[es]' to perform the action, 'n[o]/c[ont]' to skip it, 's[top]' to abort:

c

BR0280I BRSPACE time stamp: 2012-06-26 09.59.30

BR0257I Your reply: 'c'

BR0678I The action will be skipped...

BR0259I Program execution will be continued...

BR0280I BRSPACE time stamp: 2012-06-26 09.59.30

BR0370I Directory /oracle/PI1/sapreorg/seivvhdr created

BR0280I BRSPACE time stamp: 2012-06-26 09.59.33

BR0319I Control file copy created: /oracle/PI1/sapreorg/seivvhdr/cntrlPI1.old 31211520

BR0280I BRSPACE time stamp: 2012-06-26 09.59.33

BR0370I Directory /oracle/PI1/sapdata4/sr3_19 created

BR0280I BRSPACE time stamp: 2012-06-26 09.59.33

BR1088I Extending tablespace PSAPSR3...

Verify the extended table-space

Though SAP GUI

Use DB02 and then refresh to get oracle space statistics.
Then select OK to confirm the action.

Then Check the status thorugh the DB02 and database size.
[New Size is 302.97 GB]

Then check the extended tablespace and added datafile.
[= PSAPSR3] Then

[New datafile has been added as sr3.data19 ]

Check Using SQL on OS and select the datafiles of tablespaces.

Login to SQL from the user <oraSID>
Check Using SQL on OS and select the datafiles of tablespaces.
Login to SQL from the user <oraSID>

Erppi1# su orapi1

erppi1:orapi1 54>

erppi1:orapi1 53> sqlplus / as sysdba

SQL>

SQL> select file_name from dba_data_files;

Then It will display datafiles till the last.
Eg : /oracle/PI1/sapdata4/sr3_18/sr3.data18

Author:                Priyashantha Fernando

Company:           CPSTL – Sri Lanka

Created on:        26 June 2012

Original Post @ http://scn.sap.com/docs/DOC-29484

Read More