SAP OS/DB Migration CoE Team

Tablespace Administration

2010-08-11T18:36:00.001+05:30

• Creation of a new tablespace, for example as a preparation to move certain tables out of the standard tablespace PSAP into a special tablespace
• Deletion of a tablespace, for example after an upgrade
• Extending tablespaces by adding a data file or tempfile or by resizing existing data files
• Moving data files, for example because after adding a new disk a data file which was created on another disk needs to be moved to the new disk This lesson describes the actions of BRTOOLS or BRGUI under the main menu item Space management.

Creating and Dropping tablespaces

On normal operation creating a new tablespace or dropping an existing tablespace is not necessary.

The creation of a new tablespace is necessary for example

• in preparation for the upgrade: During the upgrade, the old ABAP programs in PSAP are deleted and the new ABAP programs are imported into the new tablespace PSAP.
• in preparation for an online reorganization of a tablespace, for example to switch from a dictionary managed to a locally managed tablespace.

To create a new tablespace use BRTOOLS or BRGUI and select Space management ? Create tablespace. To enter the main menu mode of BRSPACE, select continue in the next screen and select Create tablespace from the BRSPACE menu. As an alternative, you can start brspace -f tscreate and press continue.. Now fill in the necessary information by selecting the appropriate menu items.

Create a tablespace using BR*Tools

BR0657I Input menu 305 - please check/enter input values
-------------------------------------------------------------------------------
Main options for creation of tablespace in database T00
1 - Tablespace name (tablespace) ......... [PSAPT00NEW]
2 - Tablespace contents (contents) ....... [data]
3 - Segment space management (space) ..... [auto]
4 # Database owner of tablespace (owner) . []
5 ~ Table data class / tabart (class) .... []
6 - Data type in tablespace (data) ....... [both]
7 # Joined index/table tablespace (join) . []
Standard keys: c - cont, b - back, s - stop, r - refr, h - help
-------------------------------------------------------------------------------
BR0662I Enter your choice:

The main options and their possible entries are:

tablespace

Enter the name of the tablespace to be created. According to the SAP conventions, the tablespace name should start with the letters "PSAP", followed by the SCHEMA-ID, plus a unique name.

contents

• data for normal tablespaces containing tables and/or indexes
• temp for a temporary tablespace
• undo for an undo tablespace

space

You can select either auto for automatic segment space management (default) or manual for manual segment space management.

owner

Changing this is only possible if you have multiple components in one database. The owner is SAP of the database schema you create the tablespace for.

data

In the "old" tablespace layout a tablespace contained either tables (table) or indexes (index). In the new MCOD tablespace layout, tablespaces contain tables and indexes (both). SAP recommends generally to create new tablespaces containing data and indexes to simplify administration.

join

If in the data field you entered either table or index, you can enter here the corresponding index or table tablespace. In the first case, BRSPACE will create both tablespaces. In the second case, BRSPACE creates only a index tablespace on joins it with already existing table tablespace. When you entered both in the data field, this option is not selectable.

After continuing, the menu for the data file properties is shown. The screenshot shows the output after changing autoextent to yes.

Options for creation of a tablespace

BR0657I Input menu 306 - please check/enter input values
--------------------------------------------------------------------
Space options for creation of tablespace PSAPT00TST (1. file)
1 - Tablespace file name (file) .......... [G:\oracle\T00\sapdata3\0tst.data1]
2 # Raw disk / link target (rawlink) ..... []
3 - File size in MB (size) ............... [2]
4 - File autoextend mode (autoextend) .... [yes]
5 - Maximum file size in MB (maxsize) .... [10]
6 - File increment size in MB (incrsize) . [2]
7 - SQL command (command) ................ [create tablespace PSAPT t management local autoallocate segment space management auto datafi le\T00\sapdata3\t00tst_1\t00tst.data1" size 2M autoextend on next 2M M]
Standard keys: c - cont, b - back, s - stop, r - refr, h - help
--------------------------------------------------------------------
BR0662I Enter your choice:

The main options and their possible entries are:

file

The name of the new data file for the tablespace. The default path and file name follows the SAP naming conventions for data files. You can create a tablespace with up to five data files using BRSPACE.

size

Size of the data file in MB.

autoextend

If set to yes, the new data file is created autoextensible. In this case, maxsize and incrsizemust be specified. If set to no, maxsize and incrsizecannot be specified and their entries are locked.

maxsize

For autoextensible data files, this parameter specifies the maximum size in MB up to which the data file can be increased.

incrsize

For autoextensible data files, this parameter specifies the size in MB, by which the data file is automatically increased when necessary.

Now the tablespace will be created. Because creating a tablespace is a structural change in the database, a control file backup is created in the directory $SAPDATA_HOME/sapreorg/ before and after the creation. In addition the action will be reported in $SAPDATA_HOME/sapreorg/struc .log.

To drop a tablespace use BRTOOLS or BRGUI and select Space management ? Drop tablespace. To enter the main menu mode of BRSPACE, select continue in the next screen and select Drop tablespace from the BRSPACE menu. As an alternative, you can start brspace -f tsdrop and enter continue.

Now a list of tablespaces is shown, from where you can select the tablespace to be dropped. After selecting the tablespace you can set the force option (default: no). Per default, BRSPACE will not drop a tablespace which is not empty. Using the force option, BRSPACE will drop the tablespace even if it is not empty.

When a tablespace is dropped, BRSPACE will

• create a control file backup in the directory $SAPDATA_HOME/sapreorg/ before and after the deletion
• check if the tablespace is empty. If the tablespace is not empty, it will not be dropped unless you force it by setting the force mode to yes.
• take the tablespace offline
• drop the tablespace including data files
• remove all subdirectories for the data files
• create an entry of the action in struc.log

Enlarging Tablespaces

To make a tablespace larger, there are three possible ways:

• a new data file can be added to the existing tablespace.

Use this option, if the existing data files cannot be resized because there is no disk space available on the disks holding the existing data files, or because the existing data files already have their maximum size and you don't want to make them larger.

• the properties of an existing data file can be changed to be autoextensible. Use this option to simplify further tablespace administration in the future. Any autoextensible data file will grow automatically when needed up to a maximum file size defined.

Caution: When using autoextensible data files, you have to monitor the disk space usage. In this case, a tablespace overflow can still occur if the disks holding these data files are full!

• an existing data file can be resized.

Use this option if you want to keep the control over the data file growth.

To enlarge a tablespace by adding a new data file start BRTOOLS or BRGUI and select Space management? Extend tablespace. To enter the main menu mode of BRSPACE, select continue in the next screen and select Extend tablespace from the BRSPACE menu. As an alternative, you can use brspace -f tsextend and enter continue.

After selecting the tablespace to be extended, a menu similar to the menu when creating a tablespace is shown. Enter the appropriate values as described above when creating a tablespace.

To switch an existing file to be autoextensible start BRTOOLS or BRGUI and select Space management ? Alter data file ? Maintain autoextend. To enter the main menu mode of BRSPACE, select continue in the next screen. As an alternative, you can use brspace -f dfalter and select Maintain autoextend.

Now select the data file from the list. The list only contains all data files because you can change maxsize and incrsize with this function.

In the next screen, the parameters for automatic extension of the data file have to be entered (maxsize,incrsize - see above).

To resize an existing data file start BRTOOLS or BRGUI and select Space management ? Alter data file ? Resize data file. To enter the main menu mode of BRSPACE, select continue in the next screen. As an alternative, you can use brspace -f dfalter and select Resize data file.

Now select the data file from the list. Specifiy the new data file size and continue.

Moving or Renaming Data Files

To move or rename a data file, it is not sufficient to just move or rename the file itself, as Oracle would not know about the new file name or location. After moving or renaming a data file, the new file name has to be entered in the control file with Oracle commands. Using BRSPACE, all necessary actions are performed.

You might want to move an existing data file to another location if

• you want to move data files from a file system to raw devices or from raw devices to a file system (on UNIX)

• you had to extend a tablespace by adding a new data file, but because of lack of disk space in the disks containing sapdata directories, the data file was created on another disk which was not intended to hold data files. After adding another disk you want to move this data file to the new disk.

• you need to replace a disk on Windows (due to different drive letters used).

To move or rename a data file start BRTOOLS or BRGUI and select Space management ? Move data file. To enter the menu mode of BRSPACE, select continue in the next screen. As an alternative, you can use brspace -f dfmove and enter continue. Now select the data file to move from the list of data files.

In the next screen, enter the required information:

destination

enter the full path of the sapdata directory where data file shall be moved to. This directory must already exist. The subdirectory for the data file must not be entered and will be created by BRSPACE.

parallel

when moving more than one data file, you can parallelize the copy process. Enter the number of copy processes here.

force

To move or rename a data file, the database needs to be shut down. BRSPACE will normally only shut down the database, if SAP is not running. You can force BRSPACE to shut down the database even when SAP is connected by setting the force option.

Additional Database Space Management Options

To show database information start BRTOOLS or BRGUI and select Space management ? Additional space functions.

You can view information about tablespace, data files, redo log and control files. Also disk usage information of all directories containing database data can be displayed.

To alter a tablespace start BRTOOLS or BRGUI and select Space management ? Alter tablespace. Now you have the following possibilities:

set tablespaces offline and online

When a tablespace is set offline, it cannot be accessed anymore. For SAP to work correctly, all tablespaces belonging to the corresponding database schema user SAP must be online!

There are situations, when Oracle sets a tablespace offline. This happens for example when Oracle receives an I/O error from the operating system when writing into a data file. To avoid corrupt blocks to be written, Oracle sets this tablespace offline.

Caution: Whenever a tablespace is offline, and it was not actively set offline by an database administrator, you must find the reason for this and solve the problem causing Oracle to set this tablespace offline! After finding and resolving the problem, the tablespace can be set online using this menu.

In databases having multiple components in one database (MCOD), the tablespaces belongs to one schema user SAP could be set offline to perform certain administrative actions without affecting other SAP systems using a different SAP user. But even in this situation, the tablespaces SYSTEM, PSAPROLL/PSAPUNDO and PSAPTEMP must not be set offline, because these tablespaces are used by all schema users.

set or reset the backup status

The backup status is regularly set by BRBACKUP when performing an online backup and reset after the backup. When BRBACKUP crashed during an online backup, one or more tablespaces remain in backup mode. This situation is checked by the database system check, which reports the following warning if a tablespace is in backup mode:BR0970W Database administration alert - level: WARNING, type: TABLESPACE_IN_BACKUP, object: PSAPC11 In this case,

• a normal shutdown would not work
• if the database crashes or a shutdown abort is performed while a tablespace is in backup mode, the database would need a manual recovery in order to be opened.

To avoid a manual recovery, reset the backup status when a tablespace is in backup mode when the following conditions are true:

• Analyzing the situation it turns out that an online backup crashed
• There is currently no online backup running.
Coalesce free extents

Coalescing free extents means that several free extents which directly follow each other are combined to a single, larger free extent. The tool database system check will automatically coalesce free extents for all tablespaces. Manually coalescing free extents using this menu makes sense when a high amount of data was deleted in the database, for example after archiving data or the deletion of a client.

OS DB Migration

2010-08-09T20:03:00.002+05:30

Pre Export Process In Application level:-

o Check the Java JRE version (Min 1.4.1).
o Check the QCM table entries of SAP.
o Check for cancelled and update task
o Delete table entries from TATGPC, TATGPCA
o Check the incremental table conversion
o Cancel all released jobs
o Check for the operation modes
o Delete unnecessary spool data
o De-schedule all SAP jobs
o Delete all the batch jobs
o Release all repairs and correction and transports
o delete background input logs
o Delete job logs
o Delete the tRFC
o Check for the code pages installed
o Check the DDIC password for 000 client

Pre Export Process In OS level:-

o Deschedule all OS DB backups
o Shutdown all external interface
o The source should have minimum SP3

Pre Export Process In DB level:-

o Update DB statistics
o Change the DB to no archive log mode

Steps to Start the DB export

o Enter the system as adm
o Create to directory in the source system eg, Export, Install
o Check for the PSAPTEMP, the size should be 2 times the largest index
o Start the R3setup.bat program from the kernel CD (use the 45B_EXT kernel cd for the migration as the target system is AIX 5.3, always check the PAM before using the kernel cd.)
o Edit the DBEXPORT.R3S file and skip the update of statistics as it is already done and update statistics of R3SETUP is high time consuming. It can even run for days for a DB size more than 1 TB
o Edit the DBEXPORT.R3S to stop for splitter
o Start the export
o The export stops at the given breakpoint for the splitter
o Split the STR files generated
o Repeat the export process

Import process

o Check the Java version ( Minimum JRE version 1.4.1 )
o Check all necessary drives and filesystems. ( #mkdir /oracle/client/92x_64, # cd /oracle/stage, #mkdir 920_64 )
o Create to directory eg, Install, Import
o From install directory run instool.sh of Ext. kernel cd for AIX.
o set environment.
#csh
#setenv LIBPATH /sapmnt//exe:/oracle//920_64/lib.
o Install the central instances. R3SETUP –f CENTRAL.R3S
o In the next installation process choose “Exit”
o Install Oracle software as per WAS640 guide with ora user.
o After the oracle installation is done repeat the installation of the R3SETUP
o The R3SETUP stops for Migration key check phase
o Create the tablespaces of the required sizes
o Restart the database in no archive log mode
o Start the import process
o Complete the post installation steps from the migration guide of 45 B

Some of the problems faced with the above mentioned source and target system

1. During the export phase after the STR files are created the export stops with an error saying
“Cannot connect to DB”

Solution: Delete the following R3load, R3szchk, R3ldctl from the Instal directory.

2. Use update of DB statistics by sapdba or brtools. Avoid using the update of statistics by the export
Process

Solution: Edit the DBEXPORT.R3S file and delete the lines DBCOMPUTESTAT4MIG_XT*,
DBCOMPUTESTAT4MIG*, BRCONNECTEXPSTAT*

3. Export takes a huge time

Solution: Use the java based package splitter to split the STR files for the export.

4. Export fails complaining the PSAPTEMP size is small.

Solution: Check the size of the PSAPTEMP before export. It should be atleast 2 times the size of the largest index for R/3.

5. During the import process check the aio settings in the OS level.

Solution: We have used the mix server of 512 and max server of 1024 during the import process

6. The import process fails due to lack of space to extend the extent at PSAPROLL

Solution: Try using the PSAPUNDO in place of PSAPROLL

7. The total system downtime could be reduced if MIGMON was used. The firewall rule prevented
from the use of migmon between the source and the target.

Post Installation jobs for BASIS area

1. Replace the disp+work of the kernel.
2. Delete the table entries as mentioned in the Heterogeneous system copy guide of 45B
3. Edit the RFC destination address of other connected system.
4. Change the printer definition of the target. Test all the printers are working or we need to make changes in the settings.
5. Set up the TMS
6. Check for the ALE and IDOCS flow after the new system is up
7. Schedule all the basic BASIS background jobs.
8. Take a full offline backup

Reason for moving to Oracle 9.2.0.7

9.2.0.4 being the first stable release of R/3 had many bugs which are listed in the SAP and Oracle sites were later removed in later subsequent releases.

This oracle will be upgraded to Oracle 10.2.0.2 and for the upgrade the source should be at oracle 9.2.0.7 before it can be upgraded to 10g.

As we go higher up in the in the Optimizer gets improved hence the execution plans are improved and this results is transactions executing faster

Using of the Package splitter

The java based package splitter can be used to split the STR files
• Open new terminal preparation for splitter tool.
• Edit packet_splitter_end.properties file
• Use splitter guide for clarification.
• setenv JAVA_HOME /usr/opt/java141.
• using adm user, start split process.

NetWeaver Installation Part I

2010-07-26T17:30:00.000+05:30

1. How to make sap autostart with the OS restart after the Upgrade?

A. /usr/sap/sapservices - after the upgrade execute cd $DIR_PUT/bin/ execute ./installsapinit.sh

2. What are the port numbers used by the NIM daemon?

A. 3901 and 3902 hence 01 and 02 should NOT be used for SAP instance numbers.

3. Can I install SAP on NFS mounted filesystems under AIX?

A. No, there might be problems when JVM is started.

4. What is heterogeneous installation of SAP?

A. Installing an SAP system with instances running on different operating systems.

We need to download NW07_01_REL.zip from the marketplace and extract it to the installation directory to update the control.xml. Since, this avoids "sapcontrol not found dir DIR_EXECUTABLE and DIR_CT_RUN" error.

5. Why do we disable VM Container in PI systems?

A. To reduce memory consumption. Long GC runtimes in the AS JAVA of the NetWeaver PI cause shutdown of the server nodes.

6. Why do we set ulimits (soft limits) before the installation?

A. SAP Note: 323816

7. After the PI 7.11 installation PISUPER is lack of which role?

A. SAP_NWA_FULL. Manually assign it.

8. What is an SMD agent?

A. This is a standalone Java program that runs on each of the systems managed by SAP solution manager diagnostics. The installation of the diagnostics agent is a part of the Installation Master DVD. This gets installed automatically with the Primary Application server and Additional application server. Or we do have an option to installation separately for non-SAP systems. http://service.sap.com/diagnostics

9. What is a SAP Host Control Agent?

10. How to update the Preequisite checker with the lastest conditions?

A. Download the latest version of SAR file PREREQUISITE_CHECK_DATA_700.SAR from the marketplace and extract the files to /IM_AIX_PPC64/COMMON/INSTALL

11. What SAP Guides are used for Installation?

A. Master Guide, Technical Infrastructure Guide, Media Guide, Specific Notes.

12. What is the difference between Standard, Distributed, and High-Availability system installation types?

Standard - PAS, DB, and SCS run on single host

Distribute - PAS, DB and SCS run on different hosts

HA - PAS, DB, ASCS, SCS each run on separate host

Both ASCS and SCS run in a switchover cluster infrastructure. ASCS and SCS must have their own Enque replication server (ERS) instance.

13. What is the need of standalone host agent?

14. Examples for possible distributed and HA system installations

15. Describe about Standalone Host Agent.

A. Using the host agent you can centrally monitor any host with the Alert Monitor or the NWA or ACC. The host agent is used by the ACC for starting, stopping and relocating SAP instances and databases.

The host agent is automatically installed during the installation of NW components. You may need to install a standalone host agent in case

1. If you want to manage a host that does not have an SAP instance or component

2. If you have upgraded your SAP system to NW7.1 or higher and want the instances of the upgraded system to be managed by the ACC

The host agents contain

1. The control program saphostexex

2. The SAP NW Management agent SAPHostControl (sapstartsrv)

3. The sapacosprep executable of the Adaptive Computing Infrastructure

4. The operating system collector saposcol

The installed programs are automatically started when the host is booted.

The automatic start is ensured by the startup script sapinit that start the required executables.

16. Where can you find the result of the Prerequisite check phase in the SAPInst?

A. Check the results in the file prerquisites_checker_results.html under the installation directory.

17. How to run a test for High-capacity tape drive?

A. tar -cvf /dev/ where is rmt0.

18. How to display the available disks on AIX?

A. lspv and lspv -p for freespace

19. How to display the RAM size on AIX?

A. lsattr -El sys0 -a realmem

20. How to check the C++ runtime levels on AIX?

A. lslpp -L xlC.aix50.rte and lslpp -L xlC.rte

21. How to check the OS version on AIX?

A. lslpp -l bos.rte

22. How to ML and TL levels on AIX?

A. oslevel -r or oslevel -s

23. Describe about AIO need under AIX?

A. If the database is installed using the filesystems, the settings for AIO should be maxservers = minservers = 1.2 X number of datafiles used for the Oracle

Having more number of maxservers for AIO will cause problems, the reason is the surplus AIO processes are charged against the database system rather than root and have a lower scheduling priority. All processes become active very quickly and once active, the AIO servers are never stopped.

24. What is the check condition for max processes per user (maxprocs) on AIX?

A. max processes per user > max aio servers + all other process of the ora user. Increase maxprocs to 4096 (or any high value).

25. How do you adjust minperm and maxperm parameters on AIX?

A. SAPNote: 973227

26. What library will be used for LDAP on AIX?

A. libldap.a

27. How to check the fileset consistency on AIX?

A. lppchk -v

28. How to do a printer check on AIX?

A. lp -d and check the spool with the command lpstat -t

29. Which XML file contains space requirements for SAP system installation?

A. DATAUNITS/EXPORT_1/DB/ORA/DBSIZE.XML

30. What is the X11, Perl, NLS, saplocales, fonts, codepages, NFS installation necessary prior to the start of the SAP installation?

If the application servers are installed decentralized, NFS must be installed.

fonts and code pages should be pre-installed.

X11 is needed for Oracle database software installation with runInstaller.

Perl should be installed for applying Oracle interim patches

31. When do we install ABAP Central Services?

A. Only if you perform a high-availability installation.

Kinds of SAP Tables

2010-07-26T17:27:00.000+05:30

What is transparent table?
Transparent Table : Exists with the same structure both in dictionary as well as in database exactly with the same data and fields.

What is a cluster table? Where and when we use these tables?
Pooled Table : Pooled tables are logical tables that must be assigned to a table pool when they are defined. Pooled tables are used to store control data. Several pooled tables can be combined in a table pool. The data of these pooled tables are then sorted in a common table in the database.

What is a pool table? Where and when we use these tables?
Cluster Table : Cluster tables are logical tables that must be assigned to a table cluster when they are defined. Cluster tables can be used to store control data. They can also be used to store temporary data or texts, such as documentation.

What is the major difference between Standard tables, Pooled tables and Clustered Tables?

A transparent table is a table that stores data directly. You can read these tables directly on the database from outside SAP with for instance an SQL statement.

Transparent table is a one to one relation table i.e. when you create one transparent table then exactly same table will create in data base and if is basically used to store transaction data.

A clustered and a pooled table cannot be read from outside SAP because certain data are clustered and pooled in one field.

One of the possible reasons is for instance that their content can be variable in length and build up. Database manipulations in ABAP are limited as well.

But pool and cluster table is a many to one relationship table. This means many pool table store in a database table which is know as table pool.

All the pool table stored table in table pool does not need to have any foreign key relationship but in the case of cluster table it is must. And pool and cluster table is basically use to store application data.

Table pool can contain 10 to 1000 small pool table which has 10 to 100 records. But cluster table can contain very big but few (1 to 10) cluster table.

For pool and cluster table you can create secondary index and you can use select distinct, group for pool and cluster table. You can use native SQL statement for pool and cluster table.

A structure is a table without data. It is only filled by program logic at the moment it is needed starting from tables.

A view is a way of looking at the contents of tables. It only contains the combination of the tables at the basis and the way the data needs to be represented. You actually call directly upon the underlying tables.

How many tables we will come across in ABAP?
Ans : 3 types : Pooled , clustered, Transparent

How many kinds of internal table are there?
Ans: 5 Types.
Standard Table,
Sorted Table,
Index Table,
Hashed Table,
Any Table ( Generic type , Rarely used )

Some more NetWeaver QA on Installation and Migration

2010-07-26T17:26:00.002+05:30

Can I install an SAP NetWeaver 7.0 SR3 system on 32-bit platforms?

As of SAP NetWeaver 7.0 SR3 (SPS 14) you can install only dialog instances on 32-bit platforms. All remaining instances (central instance, database instance, central services instance (SCS), ABAP central services instance (ASCS)) you can install only on 64-bit platforms.

Is SAP Solution Manager 7.0 a new release following SAP Solution Manager 4.0?

SAP Solution Manager 4.0 SR4 (SPS 15) was renamed to SAP Solution Manager 7.0 to make the name compliant with SAP NetWeaver 7.0.

The new name SAP Solution Manager 7.0 brings with it the advantage of both SAP Solution Manager and SAP NetWeaver having the same release number, and is aligned with SAP's decision to streamline its product offerings. This decision also highlights the close alignment and joint go-to-market strategy of these two products.

The renaming of SAP Solution Manager 4.0 to SAP Solution Manager 7.0 is a name change only, therefore the SAP Solution Manager functionality, release schedule, installations, or other technical aspects of SAP Solution Manager will not be affected.

How can I install SAP Solution Manager Diagnostics on an SAP Solution Manager 3.2 system upgraded to SAP Solution Manager 7.0?

Proceed as follows:

Install the Java Add-In for ABAP with SAPinst.
Deploy LMSERVICE*_.SCA with SAPinst
For more information, see the installation guides at http://service.sap.com/instguides -> SAP Components -> SAP Solution Manager -> Release 7.0

Can I install an SAP NetWeaver 7.0 system as a non-Unicode system?

You can install an SAP NetWeaver 7.0 SR1 or SR2 ABAP system as a non-Unicode system. When you install an SAP NetWeaver 7.0 SR1 or SR2 dual-stack system (ABAP+Java), the ABAP part of this system can also be installed as non-Unicode. The Java part of this system can only be installed as Unicode.
As of SAP NetWeaver 7.0 SR3, you cannot install an SAP NetWeaver 7.0 ABAP system or the ABAP part of an SAP NetWeaver 7.0 SR3 dual-stack system as non-Unicode any longer.
However, non-Unicode is still supported when you perform the system copy for an SAP system upgraded to SAP NetWeaver 7.0 SR3.

Where can I find the Configuration Wizard?

The Configuration Wizard is a Java application in the SAP NetWeaver Administrator:
http://:/nwa -> Configuration Management -> Scenarios -> Configuration Wizard
or open the application with the following shortcut directly:
http://:/nwa/cfg-wizard

What are the benefits of using the Configuration Wizard?

You only have to read a reduced number of guides and get familiar with a reduced number of tools.
You do not need to check conflicting configuration settings and mutual dependencies between components, as the configuration wizard takes care of these dependencies.
Reduced time and effort for setup

How can I cancel/re-execute configuration task which has "Currently executing" status?

This may happen if your web session has expired during execution of configuration task which was not able to finish in the background because it needed some user input/response. The next time you login to Configuration Wizard if the server is not restarted you will see this task with "Currently executing" status which prevents you from re-executing the task. The status can be cleared by restarting the "tc~lm~ctc~cul~startup_app" application. To do this go to
http://:/nwa -> Operation Management -> Systems -> Start & Stop -> Java EE Applications
Then stop and start the application.

What takes place during a homogeneous system copy?

The main purpose of a homogeneous system copy is to build a test, demo or training system or to move a system to a new hardware. The difference from a heterogeneous system copy is that both the database and operating system remain the same. Because of this on some platforms there is the possibility to perform the copy using database dependent methods. Please read SAP Note 89188. Please note - no matter if you change the version or bit version of either the operating system or the database, the system copy is still considered to be a homogeous system copy (e.g. system copy from Windows 2000 32-bit to Windows 2003 x64).

What takes place during a heterogeneous system copy (migration)?

The main purpose of a heterogeneous system copy is to create a copy of an already existing R/3 system on the platform where either operating system, or database, or both differ from the operating system/database of the source system.
The whole migration process consits of five main steps:
a) preparation steps on the source system
b) export of the source system data into database-independent format. In a ABAP+ Java system it#s required to both export the ABAP and the Java stack.
c) transfer of the data made during the export
d) new system installation together with data import
e) post-processing steps within the target system

Which tools are used during a migration on source and target systems?

The main programs used for the migration are - depending on the kernel release 'R3SETUP' or 'sapinst'. When working, they call some other programs for particular purposes: R3LOAD, R3LDCTL, R3SZCHK. There are also several command files or, in another words, installation templates, that have the extensions R3S (R3SETUP) or xml (sapinst).
For the kernel-tools used during a migration some rules should be followed:
a) Tools used at the export on the source system must have the same version as on the target system.
b) Tools used must all have the same kernel-version. (do not mix up kernel-tools of different releases)
c) Tools must have the same kernel release as the system which is migrated.
The Java system copy tools do not depend on the kernel-version and you can always use the latest version of these tools.For details on this please refer to note #784118.
These rules should be applied unless otherwise specified in an appropriate installation/migration note or guide. Please keep this in mind when downloading a patched version of any mentioned tool from SAP Service Marketplace.

What is the purpose of the files of different types that are used during a migration?

DDL.TPL is used for creation of table/index definition in database specific syntax, contains negative list of tables, views and indexes, assignment of TABARTs to storeage unit and next extent size of table/index. TABART stands for a data class. Fore more details on this please refer to note #46272.
SAP<.STR contains table/index definitions from ABAP Dictionary.
SAP.TPL, export directory, block and file sizes.
SAP. - (e.g.001, 002), so called dump files contains the data of all tables of a tabart in a non-platform-specific file format.
These are binary files and they should never been changed by any editor.
SAP.EXT contains initial sizes for tables and indexes. Not applicable to some RDBMS (e.g. MS SQL Server).
SAP.TOC contains position of table data within the corresponded dump file, name of the dump file , time stamp of unload, table rows number.
TOC files must never been changed besides the approval of SAP Support is given.
SAP.log contains useful information in case of error and for restart point.
SAP.TSK files used by R3load as of release 6.20. For details please refer to note # 455195

I am considering a database/operating system change. Are there any requirements that should be met before the migration starts?

A heterogeneous system copy requires a certified consultant responsible for the migration as well as the migration services if a productive system is affected. Please refer to SAP Note ' 82478 where the requirements are described in detail.

How and from where can I get all the necessary tools for a migration?

To order a Migration Kit please create customer message under XX-SER-SWFL-SHIP component and specify exact OS and DB versions as well as Kernel Release of the system you would like to migrate. A migration guide can be downloaded at: http://service.sap.com/instguides. A list of notes with the most up to date information might be found in beginning of the migration guide.

Is there anything else I need to have/ to do/ to know before doing a migration?

You also need an installation package to build up the target system and installation guide, which you can get in the same way as the Migration Kit and System Copy Guide. Please also read carefully Note #82478 and information stored under http://service.sap.com/osdbmigration.
You may find very useful information in the SAP OS/DB Migration Service and SAP OS/DB Migration Service Planning Guide (please, pay attention to chapter "Organizational Steps"), where you also can find out all prerequisites and requirements for this procedure. Please, note that the migration must be performed by a Basis consultant with special certification for OS/DB Migration.

How can I check whether a migration of a specific product/os-db-combination is supported?

Please check whether both the source and the target product/os-db-combination is supported first. Please refer to the Platform Availability Matrix on http://service.sap.com/pam for this.
In addition please check both the system copy guide and the relevant notes for any restrictions. In some exceptional cases it may be necessary to set up a pilot project for a specific system copy.
Fore more details regarding the availability of system copy procedures odf BW 3.0B/3.1 and SAP NetWeaver 04 systems please refer to: http://service.sap.com/bi --> Services & Implementation --> System Copy and Migration.
Please also refer to the following notes:
#777024 - BW3.0 and BW3.1 System Copy
#771209 - NW04: System copy (supplementary note)
#888210 - NW04s: System copy (supplementary note)
#543715 - Projects for BW Migrations and system copies
For more details on the system copy of 'SAP Web AS Java 6.40' based systems please refer to note #785848 on restrictions and procedures.

Where can I find information on how to optimize the overall runtime of a system copy?

You may refer to: HTTP://service.sap.com/systemcopy -> System Copy & Migration -> Optimization for this.

Are there any restrictions regarding system copies in general?

Yes, there are. You should always refer to the corresponding system copy guide to check the details. For instance for the system copy of ABAP+Java or Java systems of release NW 7.0 the following applies:
- "Refresh"of the database is not supported. A"refresh" of the database means that only the database is loaded with the content of a database of a different system. As in this scenario no migration controller is invoked, this is not supported.
- Copying the database only is not supported
- Copying the central instance only is not supported. The migration controller deletes all dialog instances in the database, so the system is not complete any longer.
- Reinstalling the central instance without the database is not supported.
The migration controller deletes all dialog instances in the database, so the system is not complete any longer.

Is it possible to perform a final migration of a productive system without a "test" run?

No, you should never do this. You should perform a test migration on a comparable hardware with a system which is a copy of the productive database. This is necessary both to get an idea of the overall runtime of the productive migration an to recognize major issues at the export/import before the final migration.
The same applies for the migration key. That means the migration key is generated as a self-service and should be tested before the productive migration. In case of any issues with the key generated it's not possible to create migration keys by the weekend support.

Configure ALE

2010-07-26T17:26:00.001+05:30

Tcode: SALE
Step 1: Create Logical System
Next screen will be
Create logical systems YLS800, YLS810
Save it and back
Step 2 : Assign Client to Logical System
Dbl Click on 800 Client and give the logical system as YLS800
Dbl Click on 810 Client and give the logical system as YLS810
Step 3 : Create RFC destination
Give the RFC destination Connection type, Description and Target Host
Click on Logon/Security
Give the Language Client, User , Password
Click on Test Connection and Remote Logon
Step 4 : Create Port WE21
Select own port name and give the own port name and click on continue
Give the Description and RFC Destination created by you ie YLS810RFC
Step 5 : Create Partner Profiles WE20
Give the Partner no Parrtner type Type Agent Lang and save it
Click on Outbound Parameters
Give the Message type , Reciever Port Basic type and save it
Step 6 : Create Distribution Model
Click on Create Message type give the shorttext and Technical name and continue
Step 7 : Generate Partner Profiles
Enivornment -> Generate Partner Profiles
Give the logical system name
Step 7 :
save it , So material 858 Created
Step 8 : Send material BD10
Step 9 : Check the Idoc WE02
Click on F8
Step 10 : Execute the program RBDMOIND- Status Conversion with Successful tRFC Execution
You can check the status record status 12 appears.
Step 11. Login 810 ABAP EDITOR SE38
Execute the program RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
S\tep 12 : Idoc List WE02
Check the entrty in MARA TABLE

Enable an SAP R/3 System send Idocs to SAP PI

2010-07-26T17:25:00.000+05:30

Maintain the Sender R3 system 1. SM59 : Create a RFC destination to XI
2. WE21 : Create a TRFC Port ->Specify the RFC Destination Created
3. BD54 : Create a Logical System for the Idoc Receiver
4. WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters

Log on to XI System: 1. SM59 : RFC Destination for Sender System
2. IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP. eg. SAPID1 [Optional Step. Not mandatory]
3. IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.

To Enable Acknowledgement: SXMB_ADM ->Integration Engine Configuration ->Specific Configuration ->Add New entry -> Select parameters as:
Category: RUNTIME
Parameters: ACK_SYSTEM_FAILURE
Current Value: 1

Go to SLD: 1. Create Technical System: Choose WEB AS ABAP if the system is R/3 -> Define SAP SID, Installation Number and Database Host Name a Maintain message Server Details according to Sender System -> Maintain Client Details of Sender System ->Select a Installed Product for Sender System

2. Create Business System: Choose WEB AS ABAP if the system is R/3 -> Choose the Technical System and the client Created Before -> Choose the Installed Product -> Set:
Business System Role: Application System
Related Integration Server: Integration Server

Idoc Tunneling in XI To prevent performance consuming XMLization and de-XMLization IDOCs are tunneled through SAP XI IDOC adapter meaning no XMLiziation is executed before the IDOC is passed onto the pipeline. Note the message is converted to UTF-8 codepage.
Start transaction SXMB_ADMIN on SAP XI.
Select option Configuration->Integration Engine Configuration and add two parameter EXTERNAL_MAPPER in the category IDOC.
Configure the parameter according to the conditions below:
If Message Code and Message Function are specified in the partner profile:
..ReceiverPort...
If only the Message Code is specified in the partner profile:
..ReceiverPort..
If only Message Function is specified in the partner profile:
..ReceiverPort...

Integration Builder Integration Directory:
1. Add Business System: Adapter Specific Identifiers -> 'Logical System' identical to the 'Logical System Name' in the SLD Business System
2.IDoc Receiver Communication Channel: port the same as XI System IDX1

Archive Log Generation during Oracle Online Backup

2010-07-26T17:24:00.000+05:30

When the oracle online backup is kick started a SQL command issued which puts the tablespaces into backup active mode, then copies the datafiles to disk / tape. Once the backup is complete, anothe sql statement issued which takes the tablespace out the backup mode.
The sqls are
alter database/tablespace begin backup;
alter database/tablespace end backup;
This can be seen via v$backup dynamic view.
SQL> select * from v$backup ;

FILE# STATUS CHANGE# TIME
---------- ------------------ ---------- ---------
1 ACTIVE 831311 05-MAY-10
2 ACTIVE 831311 05-MAY-10
3 ACTIVE 831311 05-MAY-10
4 ACTIVE 831311 05-MAY-10
5 ACTIVE 831311 05-MAY-10
6 ACTIVE 831311 05-MAY-10

6 rows selected.

So, during the backup, all the tablespaces/datafiles are sealed and are not writable. Transaction changes are recorded in rego log files or sga or rollback/undo segments or something and then will be written back into the datafile when the database/tablespace is taken out of the backup mode.

We might have observed during the online backup there is a change of huge generation of redo data which may impact the database performance if the database is in archivelog mode.

Let's see what are steps taken during the online backup.

1. The tablespace is checkpointed.
2. The checkpoint SCN number in the datafile headers cease to increment with checkpoints.
3. Full images (before and after image) of the changed database blocks are written to the redologs.

When you issue

alter tablespace tbs_name begin backup;

A checkpoint is performed against the target tablespace and the datafile header is frozen, so, no more updates are allowed on the datafile header, this is for the database to know which was the last time the tablespace had a consistent image of the data.

But during the backup, the corresponding datafiles in the tablespace allow just normal read/write operations, that is IO activity is not frozen.

In case of redo log generation, each block will be recorded into the redo logs files, the first the block is changed. So, if a row is modified for the first time inside the data block since online backup is started, the complete block image is recorded in the redo log files but the subsequent transactions on the block will only record the transaction just as normal.

Above three steps are required to guarantee consistency during the file is restored and recovered. By the freezing the checkpoint SCN in the file headers, any subsequent recovery on that backup copy of the file will know that it must commence at that SCN. Having an old SCN in the file header tells recovery that the file is an old one, and that it should look for the redo log file containing that SCN, and apply recovery starting there. Note that checkpoints to the datafiles in online backup mode are not suppressed during the backup, only the incrementing of the main checkpoint SCN flag. An "Online backup checkpoint" SCN marker in the file header continues to increment as periodic or incremental checkpoints progress normally.

By initially checkpointing the datafiles that comprise the tablespace and logging full block images to redo, Oracle guarantees that any blocks changed in the datafile while in online backup mode will also be available in the redologs in case they are ever used for a recovery.

Now many one claim that during online backup there is excessive redo log generation than normal mode. It actually depends on the amound of block changes during online backup. Because the first time a block is changed logging of full images of the changed blocks in these tablespaces are recorded to the redo logs. Normally, Oracle logs an entry into the database block. But during the online backup, by logging full images of changed database blocks to the redologs, Oracle eliminates the possibility of the backup containing irresolvable split blocks. To understand this reasoning, you must first understand what a ssplit block is.

Typically, Oracle database blocks are a multiple of OS blocks. For instance, most AIX installations offer a default block size of 4MB and where as Oracle's default blcok size is of 8KB. That means the file system stores data in 4MB chunks and oracle reads or writes in 8K chunks or multiples of 8K. While backing up a datafile, backup utility (brbackup in the case of SAP) makes a copy of the datafile from the filesystem, using OS utilities such as copy, dd, cpio or ocopy. While making this copy, it is reading in OS block sized increments. If the database writer happens to be writing a DB block into the datafile at the sametime that backup utility is reading that block's constituent OS blocks, the backup copy of the DB block could contain some OS blocks from before the database performed the write, and some from after. This would be a split block.

By logging the full block image of the changed block to the redologs, it guarantees that in the event of a recovery, any split blocks that might be in the backup copy of the datafile will be resolved by overlaying them with the full legitimate image of the block from the redologs. Upon completion of a recovery, any blocks that got copied in a split state into the backup will have been resolved through application of full block images from the redologs.

Bootstrapping SAP Web dispatcher

2010-07-26T17:23:00.000+05:30

$ pwd
/sapmnt/EP1/webdisp2_710
$ sudo ./sapwebdisp -bootstrap
SAP Web Dispatcher Bootstrap
============================

This bootstrap will perform the following steps:
1. create profile file "sapwebdisp.pfl" for SAP Web Dispatcher (if not already existing)
2. create user for web based administration in file "icmauth.txt" (if not already exisiting)
3. start SAP Web Dispatcher with the created profile

After the bootstrap you can use the web based administration

Generating Profile "sapwebdisp.pfl"
Hostname of Message Server (rdisp/mshost): hostname
HTTP Port of Message Server (ms/http_port): 8100
Checking connection to message server...OK
Unique Instance Number for SAP Web Dispatcher (SAPSYSTEM): 22
HTTP port number for SAP Web Dispatcher: 8002
Create configuration for s(mall), m(edium), l(arge) system (default: medium): m
Profile "sapwebdisp.pfl" generated
Authentication file "icmauth.txt" generated
Web Administration user is "icmadm" with password "Ea9qaPtT"
Restart sapwebdisp with profile: sapwebdisp.pfl
sapwebdisp started with new pid 278536
Web administration accessible with "http://:8002/sap/wdisp/admin"

SAP Web Dispatcher bootstrap ended (rc=0)
$ *** SAP Web Dispatcher up and operational (pid: 278536) ***

AIX tools for SAP Administrators Set 5

2010-07-26T17:22:00.000+05:30

Check APAR Level
instfix is used to install filesets associated with keywords or fixes.
instfix -i | grep
***********************************************************************************
Check concurrent io settings on oracle filesystems
lsfs |grep cio
To change the filesystems to CIO mounts execute the following scripts
Script1:
lsfs -c |grep sapdata|cut -d":" -f 1|while read f
do
chfs -a options=cio $f
umount $f
mount $f
done
Script 2
lsfs -c |grep [mirr,orig]log[A,B]|cut -d":" -f 1|while read f
do
chfs -a options=cio $f
umount $f
mount $f
done

***********************************************************************************
Setting Max Processes allowed per User
The parameter maxuproc defines this.
To check the current value
lsdev -El sys0
To change the parameter maxuproc
chdev -l sys0 -a maxuproc=
***********************************************************************************
The xhost program is used to add or revert access to the X server for specified hosts. This connection / port is used by VNC, X Manager.
All connection from all the server with the following command
xhost +
or
xhost +
***********************************************************************************
slibclean
/usr/bin/slibclean
Removes any currently unused modules in kernel and library memory.
This unloads all object files with load and use counts of 0. It can also be used to remove object files that are no longer used from both the shared library region and in the shared library and kernel text regions by removing object files that are no longer required.

SAP Table Logging

2010-07-26T17:21:00.000+05:30

Table logging is a functionality SAP provides to automatically track changes on tables set as "LOG DATA CHANGES".
By default SAP delivers mainly config tables set like that since the main reason was to enable automatic logging of config changes.
The functionality could indeed harm your system performance but , as per OSS note 608835, you should not have problems since only config tables are set to be logged...
"Generally, you can activate logging in your system without any problems because SAP only delivers Customizing tables with activated logging. Customizing tables usually contain a relatively small amount of data which is only changed occasionally.
To be more precise: Basically all Customizing tables are delivered with activated logging because the requirements of external auditors are inconsistent as regards the logging of tables.
Tables for master and transaction data, on the other hand, are delivered by SAP without logging indicators. A large number of these tables are subject to mass changes which would cause performance problems if they were logged. You should use great caution if you want to log any of these tables.
Practice has shown that, bearing the above restrictions in mind, logging does not cause any problems in the production, Customizing and development environments.
If performance or memory problems occur unexpectedly, you can easily determine which table causes the problems:
Select the "Administration --> Number of logs (selective)" menu option (Shift+F8) in transaction scu3. Enter a time interval in the selection screen displayed and leave the table selection empty. If you now start the report, it returns a list of all logged tables with the number of recorded logs. You can then deactivate the logging of the tables most frequently logged in transaction SE13.
As described above, SAP delivers all Customizing tables with activated logging. Due to the relatively low number of changes in Customizing, it is not useful to remove the logging indicator from all tables except a selected few, especially since the requirements for the logging of pages may be changed by your external auditor from time to time."

If you want to monitor changes in application tables, you need to rely on aplication change objects. Ex: for table MARA, we don't have it set to auto changes, yet, we have the log of changes through standard change objects, programmed within the standard MM02, MM01... transactions.

Script for killing all processes matching a search string!

2010-07-26T17:19:00.001+05:30

ps -e -o ":%p:%a" | grep

| cut -d":" -f2|while read p
do
echo processes $p
kill -9 $p
done

Near Zero Downtime Upgrade

2010-07-26T16:18:00.001+05:30

Here's a brief steps for accomplishing a near zero downtime upgrade.

1) A golden client is built with ERP 6.0 built. SPAU/SPDD is done and is relaible
2) Table logging in turned on in the source release since that date.
3) The tools keeps flushing the delta between the two systems. Here the tool manages the strucure changes and others for standard SAP objects. For custom tables or any special add on's, you have to provide the list.
4) A 2 - 6 hour outage for the last delta to be flushed out.

But this is still in testing phase in SAP Labs.

Best Technical Practices for SAP Landscape Maintenance
In this post I would like to share my experience on Proactive measures to be taken in a SAP Landscape.
The recommendations are slightly biased towards technical aspects of SAP; hence I would request the readers to only apply them in your own environment after a careful analysis. Thanks for it!
You are most welcome for your suggestions and corrections.

I would like to divide the main topic into 7 sub-components

* Proactive Measures
* Performance Optimization
* Disaster Recovery
* Problem-Solution Approach
* Onsite vs Off-shore Support Delivery
* Upgrades
* System copies

Proactive Measures
This section emphasizes on key recommendations on preparation aspects to be satisfied for ever-challenging and ongoing performance tuning by Basis, ABAP and Functional Leads. These recommendations might give an impression that they would involve efforts during the initial stages of practice. But indeed this practice yields fruitful results once put in practice. Patience definitely pays! I would also be helping out in getting the intended results indeed by giving examples and code wherever necessary. Before I start just want to ensure the readers that this model works PERFECTLY if basis team works at a client place or close to the client environment. In off-shore support model, implementing these recommendations would be slightly tough. Though, the decision is left for you to decide which of them best suits your needs. I believe now I am ready go into topic.

1. Technical review Tracker:
This can be a Power-point presentation or a Word document depicting the technical aspects based on which the tuning, enhancements and changes can be decided. This presentation is updated twice in month by the Basis Team and will be reviewed by the Technical lead, Functional leads and other influencing persons. The objective of periodic reviews of this presentation would be to achieve the intermediate goals set during the review meetings. Let me be more specific about this presentation. The following are the slides that can be used for this presentation. Keep in mind that this presentation is unique to each SAP system landscape like ECC, BI, PI, SOLMAN, CRM, SRM etc.
1. Hardware Details
2. CPU Utilization of Primary, Additional Apps, Database servers
3. System landscape and the transport route
4. Database space management
5. Buffer Invalidations
6. Top Background Jobs
7. EarlyWatch Recommendations

I would give a brief about each of the above on how it works. H/W details slide shows hostname, RAM, physical/virtual CPUs on the LPAR/Server, CPU entitled capacity, IP address etc. CPU Utilization slide would help in identifying the CPU power bottlenecks and under utilization of CPU. This helps in identifying the SAP components causing the maximum utilization there by optimizing the total performance of the server and also reorganizing the logon groups. This helps especially during month-end releases and COPA activities which imposes maximum impact on the total server performance. Now, database space management slide. As we all know this is very crucial for the overall performance of the SAP server.

Script for killing all processes matching a search string!

ps -e -o ":%p:%a" | grep | cut -d":" -f2|while read p
do
echo processes $p
kill -9 $p
done

0 comments
NetWeaver Installation Part II
Posted by Venky on at 8:21 AM

32. What are sapadm, adm and webadm used for?
A. sapadm is used for Central monitoring services. adm is dedicated to Diagnostic agent installation. webadm is created to use web administration interface for Internet Communication Manager (ICM) and web dispatcher.

33. How to prepare SAP system for NWDI integration?
A . If you select check box Prepare SAP system for NWDI Integration on the screen NWDI Landscape, SAPinst copies all SCAs belonging to the software units that you installed to the global transport directory.

The SAP NetWeaver Development Infrastructure has a set of services that provide central storage and distributed versioning of Java source code, plus centralized build services and a predefined change management process that control the folow of the software through the landspace. To integrate your SAP system into the development landscape, NWDI requires all installed software components to be available in the file system.

34. How do you plan the Switchover Cluster?
A. To reduce unplanned downtime for your SAP system by setting up a switchover cluster. This setup installs critical software units - know as "single points of failure" (SPOFs) - across multiple host machines in the cluster. In the event of a failure on the primary node, proprietary switchover software automatically switches the failed software unit to another hardware node in the cluster.
Manual intervention is not required. Applications accessing the failed software unit might experience a short delay but can then resume processing as normal.
Switchoever clusters also have the advantage that you can deliberately initiate switchover to free up a particular node for planned system maintenance. Switchover solutoins can protect against hardware failure and operating system failure but not against human error.

35. What a switchover cluster consists of?
A.
1. HW cluster of two or more physically separate host machines to run multiple copies of the critical software units, in an SAP system the SPOFs referred to above.
2. Switchover software to detect failure in a node and switch the affected software unit to the standby node, where it can continue operating.
3. A mechanism to enable application software to seamlessly continue working with the switched software unit - normally this is achieved by virtual addressing.

36. How do you manage the creation of operating systems users during the SAP installation in the case of NIS (Network Information System)?
A.
SAPinst checks if the required services are available on the host and creates them if necessary. See the log messages about the service entries and adapt the network-wide (NIS) entries accordingly.
SAPinst checks the NIS users, groups, and services using NIS commands. However, SAPinst does not change NIS configurations.
For a distributed or a high-availability system, its recommended that you distribute account information (operating system users and groups) over the network by using NIS.
Note: If you use NFS-V4 file system, you have to create the ora user on the NFS server.
37. Directory structure of ABAP+Java System.

AIX tools for SAP Administrators Set 4

Some really funky hardware-looking problems can be fixed by draining
the NVRAM battery for 5 minutes, and then reinstalling the microcode.
We used to do this on some IBM RT's in Cincinnati, and a recent poster
to AIX-L indicates that it's still useful in some situations.

Why don't you try using iptrace and ipreport to see the behavior of your
telnet sessions ??

/usr/bin/uname -M
Gets the machine type

acledit

AIX tools for SAP Administrators Set 3

savevg -v -n -9 / _rootvg.img rootvg
This can be used to build a NIM installable image to recover your systems

alternatively, the command line call for a mksysb to tape (to include map
and exclude files) is /usr/bin/mksysb '-m' '-e' '-i' /dev/rmt0

Finding which lpp contains a file:
lslpp -w /usr/sbin/umount

AIX Standalone Diagnostics
http://www.ibm.com/developerworks/wikis/display/WikiPtype/IBM+Standalone+Diagnostics

Show real memory
lsattr -El sys0 | grep realmem
lsattr -El mem0

Example
user@(/home/user)$ lsattr -El sys0
SW_dist_intr false Enable SW distribution of interrupts True
autorestart true Automatically REBOOT system after a crash True
boottype disk N/A False
capacity_inc 0.01 Processor capacity increment False
capped false Partition is capped False
conslogin enable System Console Login False
cpuguard enable CPU Guard True
dedicated false Partition is dedicated False
ent_capacity 4.00 Entitled processor capacity False
frequency 1056000000 System Bus Frequency False
fullcore false Enable full CORE dump True
fwversion IBM,SF240_358 Firmware version and revision levels False
id_to_partition 0X800001D372E00006 Partition ID False
id_to_system 0X800001D372E00000 System ID False
iostat true Continuously maintain DISK I/O history True
keylock normal State of system keylock at boot time False
log_pg_dealloc true Log predictive memory page deallocation events True
max_capacity 6.00 Maximum potential processor capacity False
max_logname 9 Maximum login name length at boot time True
maxbuf 20 Maximum number of pages in block I/O BUFFER CACHE True
maxmbuf 0 Maximum Kbytes of real memory allowed for MBUFS True
maxpout 8193 HIGH water mark for pending write I/Os per file True
maxuproc 1024 Maximum number of PROCESSES allowed per user True
min_capacity 0.10 Minimum potential processor capacity False
minpout 4096 LOW water mark for pending write I/Os per file True
modelname IBM,9117-570 Machine name False
ncargs 8 ARG/ENV list size in 4K byte blocks True
nfs4_acl_compat secure NFS4 ACL Compatibility Mode True
pre430core false Use pre-430 style CORE dump True
pre520tune disable Pre-520 tuning compatibility mode True
realmem 16777216 Amount of usable physical memory in Kbytes False
rtasversion 1 Open Firmware RTAS version False
sed_config select Stack Execution Disable (SED) Mode True
systemid IBM,0265151DA Hardware system identifier False
variable_weight 64 Variable processor capacity weight False

See if you AIX system's hardware is CHRP (some sort of PowerPC reference
platform spec, I believe) :
bootinfo -p
chrp

AIX tools for SAP Administrators Set 2

List subsystem, this shows the subsystems that are active and inactive along with their PIDs
lssrc -a

This starts sendmail
startsrc -s sendmail -a "-bd -q30m"

lsps is used to list the characteristics of paging space

Turning off ip forwarding:
/usr/sbin/no -o ipforwarding=0

Detailed info about a specific error (errors are stored in NVRAM on AIX)
errpt -a -jE85C5C4C

Checking the fileset installation
lslpp -l

show LPAR configuration
lparstat -i or prtconf

Run the ssadiag against the drive and the adapter and it will tell you if it fails or not. Then if its a hot plugable it can be replaced online.

Backup to tape:
env - /usr/bin/mksysb '-m' '-i' '-X' /dev/rmt0
The "env -" is because some sort of environment variable can confuse
mksysb, making it error out instead of doing your backup
There's also "smitty mksysb"

You can create an image using the savevg command i.e.
savevg -v -n -9 / _rootvg.img rootvg

AIX tools for SAP Administrators Set 1

VM Utilization
vmstat 3 5

Checking for CLOSE_WAITs
CLOSE_WAIT Indicates passive close. Server just received first FIN from a client.
netstat -a | grep CLOSE_WAIT | wc -l

ps auxxxx
The -a option tells ps to list the processes of all users.
The -u option tells ps to provide detailed information about each process.
The -x option adds to the list processes that have no controlling terminal, such as daemons, which are programs that are launched during booting (i.e., computer startup) and run unobtrusively in the background until they are activated by a particular event or condition.

Top 10 processes
svmon -Pvt 10 | more

Top 10 users
svmon -Uvt 10 | more

ipcs -pmb | grep

ipcs

topas -P
Topas Monitor for host: vws031 Interval: 2 Tue Feb 9 12:15:44 2010

DATA TEXT PAGE PGFAULTS
USER PID PPID PRI NI RES RES SPACE TIME CPU% I/O OTH COMMAND
decadm 819304 1196242 63 20 40710 11971 43398 41:22 0.2 0 1 disp+wor
root 495666 1 60 20 709 31 2466 28:57 0.1 0 0 kulagent
in0437891966236 1855502 60 20 740 109 740 0:00 0.1 0 3 topas
cipadm 700444 737466 82 20 88459 471 138722 61:15 0.0 1 1 jlaunch
cipadm 352362 737466 82 20 8769 471 18335 43:44 0.0 0 0 jlaunch
cipadm 753914 737466 82 20 12576 471 29115 31:51 0.0 0 0 jlaunch
decadm 745700 1196242 60 20 932 1160 1343 5:57 0.0 0 0 gwrd
root 1306808 1 60 20 238 360 422 1:42 0.0 0 25 saphoste
sapadm 1818770 1 60 20 52494 2446 232104 22:36 0.0 0 0 sapstart

To show the version of the software
lslpp -al | grep

To show the OS version
oslevel -r

VM tuning
vmo

Stopping lan and enabling it

ifconfig en2 down detach
chdev -l ent2 -a jumbo_frames=yes
chdev -l en2 -a mtu=9000
chdev -l en2 -a state=up

NFS tuning parameters, good to check on if you're getting badcalls in nfsstat
nfso -a

nfsstat -m shows great info about full set of NFS mount options

To check for software problems:
lppchk -v
lppchk -c
lppchk -l

Identifying server node ID in multi-server node environment

If performance issues occur on a portal it might help to determine which server/dispatcher is used to answer requests.
Use the doc below to help you identify the dispatcher/server

Logon to a portal URL https:///irj/portal OR another portal being used
As soon as you have logged on type in the browser window javascript:alert(document.cookie)
This will produce a box similar to the screen shot below

JSESSIONID is a unique ID that you can check in the /usr/sap/SID/JC00/j2ee/cluster/instance.properties this will indicate the server0 used and the dispatcher, particularly useful if multiple web dispatchers are used for Load balancing.

SAP Basis interesting question and answers

2010-07-26T16:10:00.002+05:30

What is transparent table?
Transparent Table : Exists with the same structure both in dictionary as well as in database exactly with the same data and fields.

What is a cluster table? Where and when we use these tables?
Pooled Table : Pooled tables are logical tables that must be assigned to a table pool when they are defined. Pooled tables are used to store control data. Several pooled tables can be combined in a table pool. The data of these pooled tables are then sorted in a common table in the database.

What is a pool table? Where and when we use these tables?
Cluster Table : Cluster tables are logical tables that must be assigned to a table cluster when they are defined. Cluster tables can be used to store control data. They can also be used to store temporary data or texts, such as documentation.

What is the major difference between Standard tables, Pooled tables and Clustered Tables?

A transparent table is a table that stores data directly. You can read these tables directly on the database from outside SAP with for instance an SQL statement.

Transparent table is a one to one relation table i.e. when you create one transparent table then exactly same table will create in data base and if is basically used to store transaction data.

A clustered and a pooled table cannot be read from outside SAP because certain data are clustered and pooled in one field.

One of the possible reasons is for instance that their content can be variable in length and build up. Database manipulations in ABAP are limited as well.

But pool and cluster table is a many to one relationship table. This means many pool table store in a database table which is know as table pool.

All the pool table stored table in table pool does not need to have any foreign key relationship but in the case of cluster table it is must. And pool and cluster table is basically use to store application data.

Table pool can contain 10 to 1000 small pool table which has 10 to 100 records. But cluster table can contain very big but few (1 to 10) cluster table.

For pool and cluster table you can create secondary index and you can use select distinct, group for pool and cluster table. You can use native SQL statement for pool and cluster table.

A structure is a table without data. It is only filled by program logic at the moment it is needed starting from tables.

A view is a way of looking at the contents of tables. It only contains the combination of the tables at the basis and the way the data needs to be represented. You actually call directly upon the underlying tables.

How many tables we will come across in ABAP?
Ans : 3 types : Pooled , clustered, Transparent

How many kinds of internal table are there?
Ans: 5 Types.
Standard Table,
Sorted Table,
Index Table,
Hashed Table,
Any Table ( Generic type , Rarely used )

Some more NetWeaver QA on Installation and Migration

Can I install an SAP NetWeaver 7.0 SR3 system on 32-bit platforms?

As of SAP NetWeaver 7.0 SR3 (SPS 14) you can install only dialog instances on 32-bit platforms. All remaining instances (central instance, database instance, central services instance (SCS), ABAP central services instance (ASCS)) you can install only on 64-bit platforms.

Is SAP Solution Manager 7.0 a new release following SAP Solution Manager 4.0?

SAP Solution Manager 4.0 SR4 (SPS 15) was renamed to SAP Solution Manager 7.0 to make the name compliant with SAP NetWeaver 7.0.

The new name SAP Solution Manager 7.0 brings with it the advantage of both SAP Solution Manager and SAP NetWeaver having the same release number, and is aligned with SAP's decision to streamline its product offerings. This decision also highlights the close alignment and joint go-to-market strategy of these two products.

The renaming of SAP Solution Manager 4.0 to SAP Solution Manager 7.0 is a name change only, therefore the SAP Solution Manager functionality, release schedule, installations, or other technical aspects of SAP Solution Manager will not be affected.

How can I install SAP Solution Manager Diagnostics on an SAP Solution Manager 3.2 system upgraded to SAP Solution Manager 7.0?
Proceed as follows:

1. Install the Java Add-In for ABAP with SAPinst.
2. Deploy LMSERVICE*_.SCA with SAPinst
For more information, see the installation guides at http://service.sap.com/instguides -> SAP Components -> SAP Solution Manager -> Release 7.0

Can I install an SAP NetWeaver 7.0 system as a non-Unicode system?
You can install an SAP NetWeaver 7.0 SR1 or SR2 ABAP system as a non-Unicode system. When you install an SAP NetWeaver 7.0 SR1 or SR2 dual-stack system (ABAP+Java), the ABAP part of this system can also be installed as non-Unicode. The Java part of this system can only be installed as Unicode.
As of SAP NetWeaver 7.0 SR3, you cannot install an SAP NetWeaver 7.0 ABAP system or the ABAP part of an SAP NetWeaver 7.0 SR3 dual-stack system as non-Unicode any longer.
However, non-Unicode is still supported when you perform the system copy for an SAP system upgraded to SAP NetWeaver 7.0 SR3.

Where can I find the Configuration Wizard?
The Configuration Wizard is a Java application in the SAP NetWeaver Administrator:
http://:/nwa -> Configuration Management -> Scenarios -> Configuration Wizard
or open the application with the following shortcut directly:
http://:/nwa/cfg-wizard

What are the benefits of using the Configuration Wizard?

* You only have to read a reduced number of guides and get familiar with a reduced number of tools.
* You do not need to check conflicting configuration settings and mutual dependencies between components, as the configuration wizard takes care of these dependencies.
* Reduced time and effort for setup

How can I cancel/re-execute configuration task which has "Currently executing" status?
This may happen if your web session has expired during execution of configuration task which was not able to finish in the background because it needed some user input/response. The next time you login to Configuration Wizard if the server is not restarted you will see this task with "Currently executing" status which prevents you from re-executing the task. The status can be cleared by restarting the "tc~lm~ctc~cul~startup_app" application. To do this go to
http://:/nwa -> Operation Management -> Systems -> Start & Stop -> Java EE Applications
Then stop and start the application.

What takes place during a homogeneous system copy?
The main purpose of a homogeneous system copy is to build a test, demo or training system or to move a system to a new hardware. The difference from a heterogeneous system copy is that both the database and operating system remain the same. Because of this on some platforms there is the possibility to perform the copy using database dependent methods. Please read SAP Note 89188. Please note - no matter if you change the version or bit version of either the operating system or the database, the system copy is still considered to be a homogeous system copy (e.g. system copy from Windows 2000 32-bit to Windows 2003 x64).

What takes place during a heterogeneous system copy (migration)?
The main purpose of a heterogeneous system copy is to create a copy of an already existing R/3 system on the platform where either operating system, or database, or both differ from the operating system/database of the source system.
The whole migration process consits of five main steps:
a) preparation steps on the source system
b) export of the source system data into database-independent format. In a ABAP+ Java system it#s required to both export the ABAP and the Java stack.
c) transfer of the data made during the export
d) new system installation together with data import
e) post-processing steps within the target system

Which tools are used during a migration on source and target systems?
The main programs used for the migration are - depending on the kernel release 'R3SETUP' or 'sapinst'. When working, they call some other programs for particular purposes: R3LOAD, R3LDCTL, R3SZCHK. There are also several command files or, in another words, installation templates, that have the extensions R3S (R3SETUP) or xml (sapinst).
For the kernel-tools used during a migration some rules should be followed:
a) Tools used at the export on the source system must have the same version as on the target system.
b) Tools used must all have the same kernel-version. (do not mix up kernel-tools of different releases)
c) Tools must have the same kernel release as the system which is migrated.
The Java system copy tools do not depend on the kernel-version and you can always use the latest version of these tools.For details on this please refer to note #784118.
These rules should be applied unless otherwise specified in an appropriate installation/migration note or guide. Please keep this in mind when downloading a patched version of any mentioned tool from SAP Service Marketplace.

What is the purpose of the files of different types that are used during a migration?
DDL.TPL is used for creation of table/index definition in database specific syntax, contains negative list of tables, views and indexes, assignment of TABARTs to storeage unit and next extent size of table/index. TABART stands for a data class. Fore more details on this please refer to note #46272.
SAP<.STR contains table/index definitions from ABAP Dictionary.
SAP.TPL, export directory, block and file sizes.
SAP. - (e.g.001, 002), so called dump files contains the data of all tables of a tabart in a non-platform-specific file format.
These are binary files and they should never been changed by any editor.
SAP.EXT contains initial sizes for tables and indexes. Not applicable to some RDBMS (e.g. MS SQL Server).
SAP.TOC contains position of table data within the corresponded dump file, name of the dump file , time stamp of unload, table rows number.
TOC files must never been changed besides the approval of SAP Support is given.
SAP.log contains useful information in case of error and for restart point.
SAP.TSK files used by R3load as of release 6.20. For details please refer to note # 455195

I am considering a database/operating system change. Are there any requirements that should be met before the migration starts?
A heterogeneous system copy requires a certified consultant responsible for the migration as well as the migration services if a productive system is affected. Please refer to SAP Note ' 82478 where the requirements are described in detail.

How and from where can I get all the necessary tools for a migration?
To order a Migration Kit please create customer message under XX-SER-SWFL-SHIP component and specify exact OS and DB versions as well as Kernel Release of the system you would like to migrate. A migration guide can be downloaded at: http://service.sap.com/instguides. A list of notes with the most up to date information might be found in beginning of the migration guide.

Is there anything else I need to have/ to do/ to know before doing a migration?
You also need an installation package to build up the target system and installation guide, which you can get in the same way as the Migration Kit and System Copy Guide. Please also read carefully Note #82478 and information stored under http://service.sap.com/osdbmigration.
You may find very useful information in the SAP OS/DB Migration Service and SAP OS/DB Migration Service Planning Guide (please, pay attention to chapter "Organizational Steps"), where you also can find out all prerequisites and requirements for this procedure. Please, note that the migration must be performed by a Basis consultant with special certification for OS/DB Migration.

How can I check whether a migration of a specific product/os-db-combination is supported?
Please check whether both the source and the target product/os-db-combination is supported first. Please refer to the Platform Availability Matrix on http://service.sap.com/pam for this.
In addition please check both the system copy guide and the relevant notes for any restrictions. In some exceptional cases it may be necessary to set up a pilot project for a specific system copy.
Fore more details regarding the availability of system copy procedures odf BW 3.0B/3.1 and SAP NetWeaver 04 systems please refer to: http://service.sap.com/bi --> Services & Implementation --> System Copy and Migration.
Please also refer to the following notes:
#777024 - BW3.0 and BW3.1 System Copy
#771209 - NW04: System copy (supplementary note)
#888210 - NW04s: System copy (supplementary note)
#543715 - Projects for BW Migrations and system copies
For more details on the system copy of 'SAP Web AS Java 6.40' based systems please refer to note #785848 on restrictions and procedures.

Where can I find information on how to optimize the overall runtime of a system copy?
You may refer to: HTTP://service.sap.com/systemcopy -> System Copy & Migration -> Optimization for this.

Are there any restrictions regarding system copies in general?
Yes, there are. You should always refer to the corresponding system copy guide to check the details. For instance for the system copy of ABAP+Java or Java systems of release NW 7.0 the following applies:
- "Refresh"of the database is not supported. A"refresh" of the database means that only the database is loaded with the content of a database of a different system. As in this scenario no migration controller is invoked, this is not supported.
- Copying the database only is not supported
- Copying the central instance only is not supported. The migration controller deletes all dialog instances in the database, so the system is not complete any longer.
- Reinstalling the central instance without the database is not supported.
The migration controller deletes all dialog instances in the database, so the system is not complete any longer.

Is it possible to perform a final migration of a productive system without a "test" run?
No, you should never do this. You should perform a test migration on a comparable hardware with a system which is a copy of the productive database. This is necessary both to get an idea of the overall runtime of the productive migration an to recognize major issues at the export/import before the final migration.
The same applies for the migration key. That means the migration key is generated as a self-service and should be tested before the productive migration. In case of any issues with the key generated it's not possible to create migration keys by the weekend support.

Configure ALE

Tcode: SALE
Step 1: Create Logical System
Next screen will be
Create logical systems YLS800, YLS810
Save it and back
Step 2 : Assign Client to Logical System
Dbl Click on 800 Client and give the logical system as YLS800
Dbl Click on 810 Client and give the logical system as YLS810
Step 3 : Create RFC destination
Give the RFC destination Connection type, Description and Target Host
Click on Logon/Security
Give the Language Client, User , Password
Click on Test Connection and Remote Logon
Step 4 : Create Port WE21
Select own port name and give the own port name and click on continue
Give the Description and RFC Destination created by you ie YLS810RFC
Step 5 : Create Partner Profiles WE20
Give the Partner no Parrtner type Type Agent Lang and save it
Click on Outbound Parameters
Give the Message type , Reciever Port Basic type and save it
Step 6 : Create Distribution Model
Click on Create Message type give the shorttext and Technical name and continue
Step 7 : Generate Partner Profiles
Enivornment -> Generate Partner Profiles
Give the logical system name
Step 7 :
save it , So material 858 Created
Step 8 : Send material BD10
Step 9 : Check the Idoc WE02
Click on F8
Step 10 : Execute the program RBDMOIND- Status Conversion with Successful tRFC Execution
You can check the status record status 12 appears.
Step 11. Login 810 ABAP EDITOR SE38
Execute the program RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
S\tep 12 : Idoc List WE02
Check the entrty in MARA TABLE

s
Enable an SAP R/3 System send Idocs to SAP PI

Maintain the Sender R3 system 1. SM59 : Create a RFC destination to XI
2. WE21 : Create a TRFC Port ->Specify the RFC Destination Created
3. BD54 : Create a Logical System for the Idoc Receiver
4. WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters

Log on to XI System: 1. SM59 : RFC Destination for Sender System
2. IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP. eg. SAPID1 [Optional Step. Not mandatory]
3. IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.

To Enable Acknowledgement: SXMB_ADM ->Integration Engine Configuration ->Specific Configuration ->Add New entry -> Select parameters as:
Category: RUNTIME
Parameters: ACK_SYSTEM_FAILURE
Current Value: 1

Go to SLD: 1. Create Technical System: Choose WEB AS ABAP if the system is R/3 -> Define SAP SID, Installation Number and Database Host Name a Maintain message Server Details according to Sender System -> Maintain Client Details of Sender System ->Select a Installed Product for Sender System

2. Create Business System: Choose WEB AS ABAP if the system is R/3 -> Choose the Technical System and the client Created Before -> Choose the Installed Product -> Set:
Business System Role: Application System
Related Integration Server: Integration Server

Idoc Tunneling in XI To prevent performance consuming XMLization and de-XMLization IDOCs are tunneled through SAP XI IDOC adapter meaning no XMLiziation is executed before the IDOC is passed onto the pipeline. Note the message is converted to UTF-8 codepage.
Start transaction SXMB_ADMIN on SAP XI.
Select option Configuration->Integration Engine Configuration and add two parameter EXTERNAL_MAPPER in the category IDOC.
Configure the parameter according to the conditions below:
If Message Code and Message Function are specified in the partner profile:
..ReceiverPort...
If only the Message Code is specified in the partner profile:
..ReceiverPort..
If only Message Function is specified in the partner profile:
..ReceiverPort...

Integration Builder Integration Directory:
1. Add Business System: Adapter Specific Identifiers -> 'Logical System' identical to the 'Logical System Name' in the SLD Business System
2.IDoc Receiver Communication Channel: port the same as XI System IDX1

0 comments
Archive Log Generation during Oracle Online Backup
Posted by Venky on Wednesday, May 5, 2010 at 9:36 AM

When the oracle online backup is kick started a SQL command issued which puts the tablespaces into backup active mode, then copies the datafiles to disk / tape. Once the backup is complete, anothe sql statement issued which takes the tablespace out the backup mode.
The sqls are
alter database/tablespace begin backup;
alter database/tablespace end backup;
This can be seen via v$backup dynamic view.
SQL> select * from v$backup ;

FILE# STATUS CHANGE# TIME
---------- ------------------ ---------- ---------
1 ACTIVE 831311 05-MAY-10
2 ACTIVE 831311 05-MAY-10
3 ACTIVE 831311 05-MAY-10
4 ACTIVE 831311 05-MAY-10
5 ACTIVE 831311 05-MAY-10
6 ACTIVE 831311 05-MAY-10

6 rows selected.

So, during the backup, all the tablespaces/datafiles are sealed and are not writable. Transaction changes are recorded in rego log files or sga or rollback/undo segments or something and then will be written back into the datafile when the database/tablespace is taken out of the backup mode.

We might have observed during the online backup there is a change of huge generation of redo data which may impact the database performance if the database is in archivelog mode.

Let's see what are steps taken during the online backup.

1. The tablespace is checkpointed.
2. The checkpoint SCN number in the datafile headers cease to increment with checkpoints.
3. Full images (before and after image) of the changed database blocks are written to the redologs.

When you issue

alter tablespace tbs_name begin backup;

A checkpoint is performed against the target tablespace and the datafile header is frozen, so, no more updates are allowed on the datafile header, this is for the database to know which was the last time the tablespace had a consistent image of the data.

But during the backup, the corresponding datafiles in the tablespace allow just normal read/write operations, that is IO activity is not frozen.

In case of redo log generation, each block will be recorded into the redo logs files, the first the block is changed. So, if a row is modified for the first time inside the data block since online backup is started, the complete block image is recorded in the redo log files but the subsequent transactions on the block will only record the transaction just as normal.

Above three steps are required to guarantee consistency during the file is restored and recovered. By the freezing the checkpoint SCN in the file headers, any subsequent recovery on that backup copy of the file will know that it must commence at that SCN. Having an old SCN in the file header tells recovery that the file is an old one, and that it should look for the redo log file containing that SCN, and apply recovery starting there. Note that checkpoints to the datafiles in online backup mode are not suppressed during the backup, only the incrementing of the main checkpoint SCN flag. An "Online backup checkpoint" SCN marker in the file header continues to increment as periodic or incremental checkpoints progress normally.

By initially checkpointing the datafiles that comprise the tablespace and logging full block images to redo, Oracle guarantees that any blocks changed in the datafile while in online backup mode will also be available in the redologs in case they are ever used for a recovery.

Now many one claim that during online backup there is excessive redo log generation than normal mode. It actually depends on the amound of block changes during online backup. Because the first time a block is changed logging of full images of the changed blocks in these tablespaces are recorded to the redo logs. Normally, Oracle logs an entry into the database block. But during the online backup, by logging full images of changed database blocks to the redologs, Oracle eliminates the possibility of the backup containing irresolvable split blocks. To understand this reasoning, you must first understand what a ssplit block is.

Typically, Oracle database blocks are a multiple of OS blocks. For instance, most AIX installations offer a default block size of 4MB and where as Oracle's default blcok size is of 8KB. That means the file system stores data in 4MB chunks and oracle reads or writes in 8K chunks or multiples of 8K. While backing up a datafile, backup utility (brbackup in the case of SAP) makes a copy of the datafile from the filesystem, using OS utilities such as copy, dd, cpio or ocopy. While making this copy, it is reading in OS block sized increments. If the database writer happens to be writing a DB block into the datafile at the sametime that backup utility is reading that block's constituent OS blocks, the backup copy of the DB block could contain some OS blocks from before the database performed the write, and some from after. This would be a split block.

By logging the full block image of the changed block to the redologs, it guarantees that in the event of a recovery, any split blocks that might be in the backup copy of the datafile will be resolved by overlaying them with the full legitimate image of the block from the redologs. Upon completion of a recovery, any blocks that got copied in a split state into the backup will have been resolved through application of full block images from the redologs.

0 comments
Bootstrapping SAP Web dispatcher
Posted by Venky on Saturday, April 17, 2010 at 9:08 PM

$ pwd
/sapmnt/EP1/webdisp2_710
$ sudo ./sapwebdisp -bootstrap
SAP Web Dispatcher Bootstrap
============================

This bootstrap will perform the following steps:
1. create profile file "sapwebdisp.pfl" for SAP Web Dispatcher (if not already existing)
2. create user for web based administration in file "icmauth.txt" (if not already exisiting)
3. start SAP Web Dispatcher with the created profile

After the bootstrap you can use the web based administration

Generating Profile "sapwebdisp.pfl"
Hostname of Message Server (rdisp/mshost): hostname
HTTP Port of Message Server (ms/http_port): 8100
Checking connection to message server...OK
Unique Instance Number for SAP Web Dispatcher (SAPSYSTEM): 22
HTTP port number for SAP Web Dispatcher: 8002
Create configuration for s(mall), m(edium), l(arge) system (default: medium): m
Profile "sapwebdisp.pfl" generated
Authentication file "icmauth.txt" generated
Web Administration user is "icmadm" with password "Ea9qaPtT"
Restart sapwebdisp with profile: sapwebdisp.pfl
sapwebdisp started with new pid 278536
Web administration accessible with "http://:8002/sap/wdisp/admin"

SAP Web Dispatcher bootstrap ended (rc=0)
$ *** SAP Web Dispatcher up and operational (pid: 278536) ***

SAP Table Logging

Table logging is a functionality SAP provides to automatically track changes on tables set as "LOG DATA CHANGES".
By default SAP delivers mainly config tables set like that since the main reason was to enable automatic logging of config changes.
The functionality could indeed harm your system performance but , as per OSS note 608835, you should not have problems since only config tables are set to be logged...
"Generally, you can activate logging in your system without any problems because SAP only delivers Customizing tables with activated logging. Customizing tables usually contain a relatively small amount of data which is only changed occasionally.
To be more precise: Basically all Customizing tables are delivered with activated logging because the requirements of external auditors are inconsistent as regards the logging of tables.
Tables for master and transaction data, on the other hand, are delivered by SAP without logging indicators. A large number of these tables are subject to mass changes which would cause performance problems if they were logged. You should use great caution if you want to log any of these tables.
Practice has shown that, bearing the above restrictions in mind, logging does not cause any problems in the production, Customizing and development environments.
If performance or memory problems occur unexpectedly, you can easily determine which table causes the problems:
Select the "Administration --> Number of logs (selective)" menu option (Shift+F8) in transaction scu3. Enter a time interval in the selection screen displayed and leave the table selection empty. If you now start the report, it returns a list of all logged tables with the number of recorded logs. You can then deactivate the logging of the tables most frequently logged in transaction SE13.
As described above, SAP delivers all Customizing tables with activated logging. Due to the relatively low number of changes in Customizing, it is not useful to remove the logging indicator from all tables except a selected few, especially since the requirements for the logging of pages may be changed by your external auditor from time to time."

If you want to monitor changes in application tables, you need to rely on aplication change objects. Ex: for table MARA, we don't have it set to auto changes, yet, we have the log of changes through standard change objects, programmed within the standard MM02, MM01... transactions.

* ▼ 2010 (17)
o ▼ July (1)
+ Kinds of SAP Tables
o ► May (4)
+ Some more NetWeaver QA on Installation and Migrati...
+ Configure ALE
+ Enable an SAP R/3 System send Idocs to SAP PI
+ Archive Log Generation during Oracle Online Backup...
o ► April (1)
+ Bootstrapping SAP Web dispatcher
o ► March (2)
+ SAP Table Logging
+ AIX tools for SAP Administrators Set 5
o ► February (9)
+ Near Zero Downtime Upgrade
+ Best Technical Practices for SAP Landscape Mainten...
+ Script for killing all processes matching a search...
+ NetWeaver Installation Part II
+ AIX tools for SAP Administrators Set 4
+ AIX tools for SAP Administrators Set 3
+ AIX tools for SAP Administrators Set 2
+ AIX tools for SAP Administrators Set 1
+ Identifying server node ID in multi-server node en...

* ► 2009 (1)
o ► December (1)
+ NetWeaver Installation Part I

Market place

2010-07-26T16:05:00.000+05:30

What is new in Market place.