Important SAP Basis Transaction

SAP Transport Management

STMS Central Transport Management System
SE01 Transport and Correction System
SE02 Environment Analyzer
SE03 Transport Utilities
SE06 Set up Workbench Organizer
SE07 Transport System Status Display
SE09 Workbench Organizer (Initial Screen)
SE10 Customizing Organizer

SAP User Management

SU01 User Maintenance

SU01D User Display

SU02 Maintain Authorization Profiles

SU03 Maintain Authorizations

SU05 Maintain Internet users

SU10 User Mass Maintenance

SMLG Maintain Logon Group

SUPC Profiles for activity groups

SUIM Info system Authorizations

PFCG Profile Generator

PFUD User Master Data Reconciliation

S002 Easy System Administration Menu

ZAUT maintenance. Requesting new users, changing authorisation, etc.

Tcodes for Daily Monitoring

SM04 Displays User List

AL08 Displays Current Active Users

SM12 Display and Delete Locks

SM13 Display Update Records

SM21 Displays System Log

SM50 Displays Work Process Overview

SM51 Displays List of SAP Servers

SM66 Displays System Wide Work Process Overview

ST22 Displays ABAP/4 Runtime Error Analysis

ST01 Displays System Trace

ST02 SAP Setups/Tune Buffers

ST04 DB activities (SQL Server Performance Analysis)

ST05 Displays Performance trace

ST06 or ST06N Operating System Monitor

ST10 Displays Table call statistics

ST03 Displays Performance, SAP Statistics, Workload

Important DB transaction

DB01 Analyze exclusive lock waits

DB02 Analyze tables and indexes

DB12 DB Backup Monitor

DB13 DBA Planning Calendar

DB15 Data Archiving: Database Tables

DBACOCKPIT - Contains relevant functionality from the old transaction

codes ST04, DB02, DB13, DB12, DB14, and DB13C

Client Administration in SAP

SCC0  Client Copy

SCC1  Client Copy - Special Selections

SCC2  Client transport

SCC3  Client Copy Log

SCC4  Client administration

SCC5  Client Delete

SCC6  Client Import

SCC7  Client Import – Post Processing

SCC8  Client Export

SCC9  Remote Client Copy

SCCL  Local Client Copy

Background Jobs Administration

SM36 Define Background Job

SM37 Background Job Overview

SM39 Job Analysis

SM49 Execute External OS commands

SM62 Maintain Events

SM69 Maintain External OS Commands

Spool Administration

SPAD Spool Management

SP00 Spool and Relate Area
SP01 Spool Control
SP02 Display output Requests
SP03 Spool: Load Formats
SPCC Spool Consistency check
SPIC  Spool : Installation Check Tables
SP11 TemSe Contents
SP12 TemSe Administration

SAP DBTech JDBC: [258]: insufficient privilege

Hi All,

Error while export catalogue object fails with SAP DBTech JDBC: [258]: insufficient privilege error in SAP HANA DB.

Exact error log is:

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

. 

SAP DBTech JDBC: [258]: insufficient privilege: Can't export view SAPSID.0BW:BIA:SID:0SD_C03. user has no privilege on the underlying objects 

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

Solution: 

Login to SAP HANA Studio as the SYSTEM user

In the security area grant the user that is having the issue the system privilege EXPORT

Thanks,

Sharib

SAPOSCOL not starting "Cannot create Shared Memory"

Hi All,

Below are the commands to use saposcol

Login as adm

To start,
sidadm>saposcol -l
To stop,
sidadm>saposcol -k
To check status,

sidadm>saposcol -s

But some time we have error messages like "Cannot create Shared Memory".

You can use command

sidadm>saposcol -c to clear the shared memory and try starting saposcol.

In case if it doesnt start after that also, you can try below command:

>ipcs -ma|grep 4dbe

Share memory key for SAPOSCOL is "4dbe"

you can see that shared memory is assigned and the owner is root.

To clean this you need to execute below command:

ipcrm -m {Memory ID}

In above screenshot you can see that the memory id is 4.

So, the command to clear shared memory is

>ipcrm -m 4

In my example, I tried to clear memory with SIDadm user which is not the owner of the memory assigned. So, clear this memory with root user.

Once it is cleared, you can try starting saposcol with the same command which is shown above.

Example is:

And once, it is started you can check the status with below command:

>saposcol -s.

Thanks,

Sharib Tasneem

Log on to remote server and start database

Hi All,

We had a issue few days back where we installed CI and DB on separate host and things went fine till the time we refreshed system with PRD database.

Error log:

sidadm> startsap
Database SID must be started first
Log on to remote server and start database

Our DB was up and running and listener was also up.

Even R3trans -d and R3trans -x were successful.

sidadm> R3trans -d
This is R3trans version 6.24 (release 721 - 26.09.13 - 20:13:07 ).
unicode enabled version
R3trans finished (0000).
---------------------------------
sidadm> R3trans -x
This is R3trans version 6.24 (release 721 - 26.09.13 - 20:13:07 ).
unicode enabled version

R3trans finished (0000).

Solution:

Check for parameter named "SAPDBHOST" in DEFAULT.PFL.

Entry should be as

SAPDBHOST =  

Also,

Check DEFAULT.PFL if the file name is "DEFAULT" only then name it to DEFAULT.PFL.

There will be an additional parameter in Java server i.e.

j2ee/dbhost=

Thanks,
Sharib

OCS package SAPKITL705 does not match the current software component vector

Hi All,

After installation of SAP Solution Manager 7.1 SP 04 we encountered below issue:

OCS package SAPKITL705 does not match the current software component vector

Solution:

Before starting any SP import like SAP Basis SAPKB70210 or any other Support pack, please import CTS_PLUG 200,
GW_CORE 200,
RTCISM 100,
IW_BEP 200,
and IW_FND 250

via SAINT transaction with their SP's.

For more detail please refer to SAP Note: 1827677 - Solution Manager 7.1 SPS : OCS package SAPKITL705 does not match the current software component vector

Thanks and Regards,

Sharib Tasneem 

Moving SAPDATA files in SAP DB2 DB Server

Hi All,

In this blog I will show you on "How to move SAP DB2 database files from one location to other.

In our case we are facing drive/disk full issue and this can resolved by moving few of the DB files from one drive to another.

Please make sure that source and target drive format is same.

Steps are mentioned below:


Step 1: Stop SAP.
Step 2: Login to the server using db2 
Step 3: Take Offline backup for database and also OS level backup(Recommended).
Step 4: Stop database.
            >db2stop force
Step 5: Open command prompt and move to the kernel location. Generate script file using below command,      
            >brdb6brt -s -bm RETRIEVE_RELOCATE
              eg: brdb6brt -s ST1 -bm RETRIEVE_RELOCATE

Step 6: Move the script file to the location where offline backup is taken.

Step 7: Rename the script file _NODE0000.scr to _NODE0000.clp so that we can edit the file.

Step 8: Create directory structure where you want to place sapdata. And copy the content from old storage location.

Here is the example above, the files from sapdata3 and sapdata4 are moved from D Drive to F Drive, so we copied the files after creating similar directory structure(D:\db2\SID to F:\db2\SID) and copied the content from parent location to target location.

Step 9: Open the file SID_NODE00000.clp in an editor, and modify the storage as shown below, 

            STORAGE_PATH=, 

      Eg: STORAGE_PATH=D:\db2\ST1\sapdata4,F:\db2\ST1\sapdata4

Step 10: Rename the file back _NODE0000.clp to _NODE0000.scr.

Step 11: move to the location where the script file is copied and Execute the below command,
              db2relocatedb -f _NODE0000.scr 
         eg: db2relocatedb -f ST1_NODE0000.scr

Step 12: Now we can delete or rename old storage location,

Step13: Start SAP and DB now and check the new location from DB13 transaction.

Thanks,

Sharib Tasneem

Note: Please try this your own risk. This blog is only intended for sharing knowlodge only. Not to be used in production landscape.

SXPG_COMMAND_EXECUTE failed for BRCONNECT

Hi All,

While running certain jobs in from TX DB13, it was failing in our landscape as our CI and DB are on different host.

After checking the log, I found the below logs:

+++++++++++++++++++++++++++++++++++++++++++

SXPG_COMMAND_EXECUTE failed for BRCONNECT - Reason: program_start_error: For More Information, See SYS
Message no. Q2233

Diagnosis
This message includes variables. No additional information can be specified.
+++++++++++++++++++++++++++++++++++++++++++

Googled this and found many confusing solutions. Also, for your information, our servers were on AIX and I am sure the solution will work on all linux flavors.

Solution:
Follow SAP note number, Note 446172 - SXPG_COMMAND_EXECUTE (program_start_error) in DB13 section 8.

Login to system as root user and execute the command which is shown below in your SAP primary application Server(CI):

rsh -l adm sapxpg 

Ex: rsh -l SIDadm sapxpg
where hostname name is the hostname of the DB Server.

In my case it failed with permission denied error("Permission denied", "Can't establish connection" or a password query). Now, follow the procedure to fix this error.

Open file /etc/hosts.equiv and make an entry about the other host and the user which should be allowed to execute the command in Db server.

Ex:
hostname sidadm
hostname orasid

Where hostname is the hostname of your SAP Primary application Server and "sid" is the SID of your SAP Server.

Cheers,
Sharib Tasneem