SAP Parameters

 The default profile and the instance profiles are stored in /usr/sap/SID/SYS/profile (and /sapmnt/SID/profile).

To see the list of SAP parameters, run the report RSPFPAR or RSPARAM using SE37. The reports show the parameters for the instance from where you are running the reports. You can use TU02 to display the parameters for all the instances.

You can display the parameters from OS using the following commands

sappfpar name=<SID> nr=<nn>

or

sappfpar pf=<full_path_of_profile>

sappfpar is useful when you want to verfy the paramters while the SAP system is down.

Some parameters can be changed temporarily and dynamically using the transaction RZ11. Use RZ10 to change the parameters permanently but be care - if you start making changes to the parameters using RZ10, a new profile file is created based on the settings in the database and you end up losing the changes that were made directly to the files. You would be under the assumption that it is the parameter that has caused your system to malfunction and try to undo the change, but that would not work.

 

SAP Rebuilding Indexes

Rebuilding SAP Index

When an indexed field in a table is changed repeatedly, the data is deleted from the index and re-insterted at a new block in the index. The new entries are always added to the right side of the index tree and therefor deletion is relatively to the left. When the index elements are deleted and added repeatedly, the left side of the index tree tends to be sparse and the right side keeps growing.

Fragmented index results in increased usage of database space and more blocks being read into the buffer. This can be avaoided by rebuilding the index.

One can measure index fragmentation using the report RSORATAD or using DB02 --> Detailed Analysis --> Enter Index --> Detailed Analysis --> Analyze Index --> Storage Quality. If storage quality is less than 50% you may need to reorg the index. If you wish to run an analysis on all the indexes, run the report RSORAISQN. Check SAP note 970538 for more details for more information on the restriction with using this report. Do not run the report without reading the note. You can also get an idea on the amount of fragmentation by comaring the size of the table and the index. If the size of the index is larger than that of the table, the index is fragmented.

To rebuild index, you can use one the following methods:
1. brspace -f idrebuild -i <index_list>
2. Using DB02
DB02 --> Detailed Analysis (in the "Tables and Indexes" section) --> Object Name: <index> --> Detailed Analysis --> Alter Index --> Coalesce / Rebuild
3. Using RSORAISQ report
   Call SAP transaction SE38 and execute the report RSORAISQ.
   Input the tablespace name and the index name in Object Selection section.
   Check rebuild option in Function Code section.
   A report will be generated with details on the index.
   Click on the Index Rebuild button.
   You will be prompted to feed the name of the index and tablespace again, enter the details and execute.
4. Rebuild indexes offline using the report RSANAORA
5. Mass rebuild of indexes using the report RSORAISQN

SAP License key after system copy in ECC 6.0

License key after system copy in ECC 6.0

After system copy, there is a temporary license. To  get back the old system number you
 must first delete all old licenses in tcode SAPLICENSE, then, request a new license at http://service.sap.com/licensekey
then, choose the proper system,  under "technical installation" section. An then reinstall licenses via saplikey or SAPLICENCSE .

SAP Install DFS licenses

Installation DFS licenses :

• Run /DFS/CUST  - DocFlow CUST
• Choose Card 019005 (Optional)
• Go Description - License loading
• Chose  file with DFS licenses 

HP-UX: Disk and Filesystem tasks

  Search for attached disk
                ioscan -fnC disk
   Initialize a disk for use with LVM
                pvcreate -f /dev/rdsk/c0t1d0
   Create the device structure needed for a new volume group.
                 cd /dev
                 mkdir vgdata
                 cd vgdata
                 mknod group c 64 0x010000
  Create volume group vgdata
                 vgcreate vgdata  /dev/dsk/c0t1d0 { if your expecting to use more than 16 physical disks use the -p option, range from 1 to 256 disks. }
   Display volume group vgdata
                 vgdisplay -v vg01
   Add another disk to volume group
                 pvcreate -f /dev/rdsk/c0t4d0
                 vgextend vg01 /dev/dsk/c0t4d0
    Remove disk from volume group
                 vgreduce vg01 /dev/dsk/c0t4d0
     Create a 100 MB logical volume lvdata
                 lvcreate -L 100 -n lvdata vgdata
                 newfs -F vxfs  /dev/vgdata/rlvdata
      Extend logical volume to 200 MB
                 lvextend -L 200 /dev/vgdata/lvdata
      Extend file system to 200 MB
                 { if you don't have Online JFS  installed volumes must be unmounted before you can extend the file system.  }
                 fuser -ku /dev/vgdata/lvdata                        { kill all process that has open files on this volume. }
                 umount /dev/vgdata/lvdata
                 extendfs /data
                 { for  Online JFS,     200 MB  / 4 MB  = 50 LE; 50 x 1024 = 51200 blocks }
                  fsadm -F vxfs -b 51200 /data
        Set largefiles to support files greater than 2GB
                  fsadm -F vxfs -o largefiles /data
 
Exporting and Importing disks across system.
        1.  make the volume group unavailable
               vgchange -a n /dev/vgdata
        2. Export the the disk while creating a logical volume map file.
                vgexport -v -m data_map vgdata
        3.  Disconnect the drives and move to new system.
        4.   Move the data_map file to the new system.
        5.  On the new system recreate the volume group directory
                 mkdir /dev/vgdata
                 mknod /dev/vgdata/group c 64 0x02000
        6. Import the disks to the new system
                  vgimport -v -m data_map /dev/vgdata  /dev/dsk/c2t1d0 /dev/dsk/c2t2d0
        7.  Enable the new volume group
                  vgchange -a y /dev/vgdata
 Renaming a logical volume
          /dev/vgdata/lvol1  -> /dev/vgdata/data_lv
         umount /dev/vgdata/lvol1
         ll  /dev/vgdata/lvol1                                      take note of the minor ( e.g 0x010001 )
                        brw-r-----   1 root       root        64 0x010001 Dec 31 17:59 lvol1
         mknod  /dev/vgdata/data_lv b 64 0x010001       create new logical volume name
         mknod  /dev/vgdata/rdata_lv c 64 0x010001
         vi /etc/fstab                                               { reflect the new logical volume  }
         mount -a
 
         rmsf /dev/vgdata/lvol1
         rmsf /dev/vgdata/rlvol1

SAP Creating User & Role for new RFC connection

Creating User & Role for new RFC connection

 We need to make an role which acts a  definite functional module in SAP.

Go to PFCG and create new role Z_ALLO_RFC. Open Authorizations tab  and  click generete new profile


 

then click Change Authorization Data.

Add object S_RFC and fill the fields.

 Then generate profile.
After Create new user ZAAA_RFC and assign this Role via SU01 Make it  "system" type.

In SM59 create new rfc connection click create icon. Under Logon&Secur tab add  created user and password.


 
Click save chenges and try to test connection under Utilities- Task -Test connection and Authorization test.