I am offering Remote SAP Basis Support and Service to your company. No matter your company have dedicated SAP Basis or not, we can help you. Your company could hire me as Remote SAP Basis.
You can check here for futher information.
This video show you on how to generate solman key (you needed when installing SAP ERP server) without having solman server. This little trick is really helpfull.
Happy watching, guys !!
I also have uploade a brand new slideshow video on step by step on how to install SAP NetWeaver 7 EHp 2 Process Integration (formerly known as SAP Exchange Infrastructure a.k.a SAP XI).
It’s really easy to follow.
Happy watching and enjoy !!
Recently, I have uploaded a new slideshow video about how to install SAP NetWeaver 7 EHp 2 Mobile Infrastructure. You can check it out here on youtube link (
Happy watching, guys !!
For this trial, I am trying to install SAP ERP 6 Ehp 5 using IBM DB2 10.5 FP 4. For the OS, I am using SuSE Linux Enterprise Server 12 (the latest one) using btrfs as file system. Usually, I used ext3 for the file system.
This installation is running well and smoothly but it takes long enough when “Import ABAP” step.
After installation is finished, I am trying to access the server using SAPGUI. But I got some error like this “os release linux 3.12.28-4-default #1 smp thu sep 25 17:02:34 utc 2014 (9879bd4) x86_64 is not supported with this kernel (720)”. I know that this error is because I use SLES 12 and this OS is using the latest production release kernel.
I tried to update SAP kernel to 415 level for this error and this was succeeded. I haven’t found this error again.
But I have found a new error. The error message is “UUID daemon (uuidd) not found. Please check SAP note 1391070”
The problem was about uuidd. On this SAP note, I have found a little script to check_libuuidd. You can download from the SAP note.
sles12:~/sapinst # ./check-libuuid.sh
[ check-libuuid.sh Revision : #20 $ Date : 2014/09/26 $ ]
SLES 12 (SP 0) system
libuuid package: libuuid1-2.25-6.69.x86_64
uuidd package: uuidd-2.25-6.1.x86_64
WARNING: Unmatching version numbers of libuuid and uuid-runtime!
WARNING: This is probably caused by an incomplete system upgrade!
2.25 and 2.25 ; 6.1.x86_64 and 6.69.x86_64
uuidd is active.
uuidd is running permanently.
installed libuuid and uuidd are ok!
/usr/sbin/uuidd -t ok!
And now, I can login again to my SAP server without error again.
Exsort not enough memory, exsort setvbuf failed, and system no task storage shortdump is happening on my production SAP ERP 6 server after we migrated my ERP to my new hardware. After searching on SAP service marketplace and observing my new server settings, I have found out the problem.
I want to lock all the users in SAP during MTP. I know using SU10 we can do it. Any other alternative ways to lock the users.
Is there a way in SAP to unlock a locked user for a limited time, then automatically after x time set the user back to lock status?
You can fill in “valid from” and “valid until”, but you cannot say from Monday to Friday from 8 – 12:00 for part time workers.
Can we schedule to lock all users?
If users get locked, from SU01 you can unlock them.
Use SU10 to mass lock/unlock the users.
Use address data or authorisation data to get a list of users – select the ones you want and
Once this is done click on lock or unlock.
You can also use transaction code EWZ5 to mass lock/unlock the users
Execute program EWULKUSR in SE38
Set a profile parameter (login/failed_user_auto_unlock) to unlock at midnight the locked users.
Here’s an ABAP code, short and simple, isn’t it?
DATA: time_limit TYPE sy-datum.
DATA: days TYPE i VALUE 40.
time_limit = sy-datum – days.
UPDATE usr02 SET uflag = 64 WHERE trdat < time_limit.
If you don’t want to specify the time in the program, you can use SE38 to schedule it as a daily background job with the date and time.
Probably the easiest way would be to write a sqlplus SQL script that sets all the UFLAG fields in table USR02 to 64 EXCEPT for the BNAMEs you don’t want locked. When you are done, you can do the same again but change the UFLAG field to 0.
The SQL statement would look like:
update SAPR3.USR02 set UFLAG = 64 where MANDT = <client number> and BNAME != <don’t lock user 1>
AND BNAME != <don’t lock user 2>;
You can replace != with <> if you want. To run this from an OS command line, you would type:
Unix/Oracle 8—> sqlplus internal @<SQLpath+SQLname>
NT/Oracle 8.0—> plus80 internal @<SQLpath+SQLname>
NT/Oracle 8.1—> sqlplus internal @s<SQLpath+SQLname>
Unix/Oracle 9:–> sqlplus /nolog @<SQLpath+SQLname>
NT/Oracle 9—–> sqlplus /nolog @<SQLpath+SQLname>
In UNIX you can cron the script to schedule it. In NT you can schedule it as a task.
This is another method to UNLOCK ALL users.
Start Oracle Server manager (I assume you are on Oracle)
update sapr3.usr02 set uflag=’0′ where mandt=’399′;
When users are locked, the uflag is set to 64.
Finish, just query to check.
select bname, uflag from sapr3.usr02 where mandt=’399′;
Please note that unlocking users from low level (like Oracle sqlplus) should be used as last resort. Frequent use of low level access may tempt you to use on other things. Highly dangerous and your IS auditors will not be too happy.
Is there a way to set a list of users that cannot be locked, even if we try to lock them manually, and even if they fail connection ( wrong password )?
Increase this parameter in SAP Instance profile:
login/fails_to_user_lock = 6 (max is 99 wrong attempts, i.e, value 99). Currently you have a value of 3.
login/failed_user_auto_unlock (for your midnight unlocking).
Ask users to remember passwords!! If someone is deliberately login-in with different username/password (thereby blocking legitimate access of that user), check hostname from SM21.
This is considered as DoS (Denial of Service).
The following steps will guide you trough the mirroring of an AIX rootvg.
This info is valid for AIX 4.3.3, AIX 5.1, AIX 5.2 and AIX 5.3.
- Make sure you have an empty disk, in this example its hdisk1
- Add the disk to the vg via “extendvg rootvg hdisk1
- Mirror the vg via: “mirrorvg rootvg”
- Adapt the bootlist to add the current disk, the system will then fail to hdisk1 is hdisk0 fails during startup
- do bootlist -o -m normal
- this will list currently 1 disk, in this exmaple hdisk0
- do bootlist -m normal hdisk0 hdisk1
- Run a bosboot on both new disks, this will install all software needed for boot on the disk
- bosboot -ad hdisk0
- bosboot -ad hdisk1