Mass user Locking and Unlocking in SAP

 Please find the procedure below.

Tools --> Administration --> User Maintenance --> user (i.e. SU01)

Step 1: Select Menu Environment --> Mass Changes.
Step 2: Click "Address Data" button 
Step 3: F8 (execute) to select users to be locked.
Step 4: Select users to be locked and click "Transfer" Button.
Step 5: Click Lock / Unlock icon to lock or unlock the selected users.

courtsey : https://searchsap.techtarget.com/tip/Mass-user-Locking-and-Unlocking-SAP-R-3-46#:~:text=Please%20find%20the%20procedure%20below,and%20click%20%22Transfer%22%20Button.

How to access PO / PI landing page

http://:50000/dir

https://help.sap.com/viewer/bd0c15451669484cbc84a54440340179/7.5.5/en-US/fc319d06d0a241fa89e6f101824cf2ac.html

DBA cockpit ORA-00942 error

After upgrade to EHP2 we were getting the error ORA-00942 on oracle 11g . Implemented the script attached with SAP Note 1546456 and it resolved our issue.

brconnect command to update stats without user intervention or password

brconnect -c -u / -f stats -t all -f collect -p 4

"Message Type X" dump coming while accessing the ST03N data

We were facing the Message_Type_X dump when ever we are trying to see
the historic data in ST03N in APP System.

We go to ST03N -> Administration -> Expert Mode -> Workload --> Total
(When we try to expand the tree node total, immediatly we get the dump)

We found the nearest note to our problem Note 1035246 - ST03N -
MESSAGE_TYPE_X short dump directly after start; where in option 1 is
only valid in our case;and solution job SAP_COLLECTOR_FOR_PERFMONITOR
is available in the system and the report SWNCREORG program doesn’t
exist in the System.

Solution : Resolution is to run the report RSSTAT60 once, the report
corrects any discrepancy between the tables MONI and SAPWLMOIDX. It corrected the error.

Transports stuck in PEQ for long time

Please perform the following cleanup activities to make sure the
transports run smoothly:

1. Ensure that tp.exe process is not running at the OpSys level before
proceeding with the next steps.

2. STMS -> Import Monitor -> remove the obsolete entries "RUNNING" or
error messages ( 1 entry, Select the entry, right click -> Delete
option )

3. please relocate the files under /usr/sap/trans/R3UPG/tmp/ to another temp
directory. Except below files!:
amodprot., moveold.sh, cmodact., tms_test.,
IMODPROT. UMODPROT.

Once the above steps are checked, Kindly refresh the import queue and
reimport the request

Creating mirror logs in oracle if they are missing mirrlogA mirrlogB

SQL) set lines 1000;
SQL) set pagesize 80;
SQL) select group#,status,member from v$logfile;



GROUP# STATUS MEMBER
-----------------------------------------------------------------------------
1 /oracle/SRD/origlogA/log_g11m1.dbf
1 INVALID /oracle/SRD/mirrlogA/log_g11m2.dbf

2 /oracle/SRD/origlogB/log_g12m1.dbf
2 INVALID /oracle/SRD/mirrlogB/log_g12m2.dbf

3 /oracle/SRD/origlogA/log_g13m1.dbf
3 INVALID /oracle/SRD/mirrlogA/log_g13m2.dbf

4 /oracle/SRD/origlogB/log_g14m1.dbf
4 INVALID /oracle/SRD/mirrlogB/log_g14m2.dbf


The above is the system status we can find with command. Invalid is coming due to that the mirrlog doesn't

exist, there is no file at that location.

We may follow the below procedure:



ALTER DATABASE DROP LOGFILE MEMBER '/oracle/SRD/mirrlogA/log_g11m2.dbf';

ALTER DATABASE ADD LOGFILE MEMBER '/oracle/SRD/mirrlogA/log_g11m2.dbf' to group 1;



ALTER DATABASE DROP LOGFILE MEMBER '/oracle/SRD/mirrlogB/log_g12m2.dbf';

ALTER DATABASE ADD LOGFILE MEMBER '/oracle/SRD/mirrlogB/log_g12m2.dbf' to group 2;



ALTER DATABASE DROP LOGFILE MEMBER '/oracle/SRD/mirrlogA/log_g13m2.dbf';

ALTER DATABASE ADD LOGFILE MEMBER '/oracle/SRD/mirrlogA/log_g13m2.dbf' to group 3;


ALTER DATABASE DROP LOGFILE MEMBER '/oracle/SRD/mirrlogB/log_g14m2.dbf';

ALTER DATABASE ADD LOGFILE MEMBER '/oracle/SRD/mirrlogB/log_g14m2.dbf' to group 4;



If it stills shows invalid under status then give the below command :



alter system switch logfile;



SQL) select group#, status, member from v$logfile;

GROUP# STATUS MEMBER
----------------------------------------------------------------------------
1 /oracle/SRD/origlogA/log_g11m1.dbf
2 /oracle/SRD/origlogB/log_g12m1.dbf
2 INVALID /oracle/SRD/mirrlogB/log_g12m2.dbf
3 /oracle/SRD/origlogA/log_g13m1.dbf
3 INVALID /oracle/SRD/mirrlogA/log_g13m2.dbf
4 /oracle/SRD/origlogB/log_g14m1.dbf
4 INVALID /oracle/SRD/mirrlogB/log_g14m2.dbf

The invalid status will disappear.

For more info; please read SAP Note 491160