on 03-27-2007 10:42 AM
Good morning.
We want to install MySAP ERP 2005 on Linux on a IBM xseries 346 64 bit.
I've seen that Red Hat EL 4 is certified by SAP
In this page, http://www50.sap.com/linux/platforms/index.asp, is also specified the kernel to use.
But I haven't find any other suggestions on http://service.sap.com/pam
I'm a little bit confused about the correct version: AS, ES... 4.2, 4.4, 5?
Can anyone please give me a suggestion about the correct version to choose??
Regards,
Luca
Dear Luca,
I now remember that I also ran into this problem. It is caused by MaxDB. Please have a look at SAP note <a href="https://service.sap.com/sap/support/notes/848436">848436</a> and check section "20 Sep 05 ERP ABAP: MaxDB Parameter SHAREDSQL".
It also took me a long time to figure out, what causes the problem. Setting the correct parameters in <dbsid>_sapdb_db_parameter.txt solves the problem. Another workaround is to use only one single R3load process, because in this case the situation can be avoided.
Best Regards,
Hannes Kuehnemund
SAP Linuxlab
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Good evening to everybody.
Thank you very much Hannes for your suggestion.
I've set one single R3load process, and something seems changed.
In fact, I didn't receive any feedback from "top" command on the terminal before.
Now, I see that 2 process of sdb user are running. Sometimes also appears a R3load process of devadm user.
You can see a screenshot on the following URL: http://www.lucasozio.it/top.png
The process of import abap (step 17) is so long?? It's more than 24 hours that it is running.
The server is a IBM xseries 346 intel xeon 64 4 GB RAM and 2 DISK (300 GB) on raid 1(sw).
Thank you very much.
Regards.
Luca
Dear Luca,
using a software raid may slow down the system, but I don't know by which factor (as I never gave it a try).
Using only one single R3load process was the second workaround which should only be used if the first one (changing parameters) does not work. The first workaround is the official one, and should be use first. Maybe I didn't point it out clearly enough.
As long as there are running processes (R3load and kernel(which is MaxDB kernel process)) something is happening. Using vmstat or iostat you could check if data is written to disk.
Cheers,
Hannes
Hi Hannes,
Your suggestions solved myroblem with ECC installation!!!!!
It has been a long installation process (about 4 days), but successfull.
Thank you very much for your help.
The last question.
I've installed a java sap gui (for Linux) on the same machine to test my SAP installation.
During logon I receive the following error
Attempt to load shared library libJPlatin.so failed
see for details www.lucasozio.it/error_gui.JPG
To solve the problem:
- I've set permission 777 to this file.
- set LD_LIBRARY_PATH to /SAPCLIENT/bin
I've read a post this problem is due to the java 64 bit version? Is it correct?
So I can't solve this problem?
Dear Luca,
up to now, only the Linux 32bit version of the JavaGUI is available. If you want to run the 32bit JavaGUI in a x86_64 (64bit) environment, you have to install a 32bit JDK and several other libraries (libXp for example). If you do an
ldd /path/to/libJPlatin.so
you will see, which 32bit libraries you need. You may have to extract these libs from other 32-bit rpm packages/deb packages yourself. When having the missing libs you have to use
LD_PRELOAD /path/to/libs/lib.so
to ensure that these libs are loaded before the 64bit versions. Then it should work.
Best Regards
Hannes
Hello Hannes,
The note 848436 does not exist anymore. Can you give me advices about what should I change in the file? I'm on Windows 2003.
Here is the actual content:
Paramfile for Max DB
#
#
Parametername Parametervalue //Comment
CACHE_SIZE 180096
LOG_MIRRORED NO
MAXUSERTASKS 50
MAXCPU 1
LOG_IO_QUEUE 200
MAXLOCKS 300000
CAT_CACHE_SUPPLY 10000
JOIN_MAXTAB_LEVEL4 64
_UNICODE YES
DEFAULT_CODE ASCII
PACKETSIZE 131072
MCOD NO
Thank You,
Mona
Thanks to all.
Before buy RHEL 4 I'm performing a test installation with CentOS Linux (4.4) of mySAP ERP 2005
The great problem is that I'm occurring always a problem with 17 step in import ABAP.
Loading of 'SAPSLOAD' import package: ERROR
Import Monitor jobs: running 2, waiting 7, completed 38, failed 25, total 72.
Loading of 'SAPSSEXC_1' import package: ERROR
Import Monitor jobs: running 1, waiting 7, completed 38, failed 26, total 72.
Loading of 'SAPSPROT' import package: ERROR
Import Monitor jobs: running 0, waiting 7, completed 38, failed 27, total 72.
Import Monitor jobs: running 1, waiting 6, completed 38, failed 27, total 72.
Import Monitor jobs: running 2, waiting 5, completed 38, failed 27, total 72.
Import Monitor jobs: running 3, waiting 4, completed 38, failed 27, total 72.
Loading of 'SAPDFACT' import package: ERROR
Import Monitor jobs: running 2, waiting 4, completed 38, failed 28, total 72.
Loading of 'SAPDDIM' import package: ERROR
Import Monitor jobs: running 1, waiting 4, completed 38, failed 29, total 72.
Loading of 'SAPUSER' import package: ERROR
Import Monitor jobs: running 0, waiting 4, completed 38, failed 30, total 72.
Import Monitor jobs: running 1, waiting 3, completed 38, failed 30, total 72.
Import Monitor jobs: running 2, waiting 2, completed 38, failed 30, total 72.
Import Monitor jobs: running 3, waiting 1, completed 38, failed 30, total 72.
Loading of 'SAP0000' import package: ERROR
Import Monitor jobs: running 2, waiting 1, completed 38, failed 31, total 72.
Loading of 'SAPUSER1' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 38, failed 32, total 72.
Loading of 'SAPDODS' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 38, failed 33, total 72.
I've read in sdn forums that this problem is due to an incorrect version of jdk. Only 1.4.2_08 is correct. But for 64 bit architecture this version doesnt' exist.
For this test, at this moment I've installed <b>IBM J9SE VM (build 2.2, J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20060824 </b>.. suggested by a sdn users.
But without result.. always the same error.
If we choose to buy RHEL 4 Update 4, is provided this package (1.4.2_08)??
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Luca,
for every Linux distribution running on x86_64 hardware, you need the IBM 1.4.2 JDK. Even with RHEL4 you have to stay with the IBM JDK. The version I have running here is the following:
./java -version
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.2)
IBM J9SE VM (build 2.2, J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20060824 (JIT enabled)
J9VM - 20060802_1551_LHdSMr
JIT - r7_level20060707_1808ifx1)
I assume you set the JAVA_HOME variable to /opt/IBMJava2-amd64-142 before restarting the installer. Also the PATH variable needs to be adjusted to have /opt/IBMJava2-amd64-142/bin in the first place.
If you already set the above variables, the log files are worth a look. What do they say?
Cheers,
Hannes
Hi,
I suppose you are referring to Sun's jdk 4.0.2_08 version. This is only for 32bits platforms.
To use with IBM xServers (x86_64), you must install the most recent jdk at the following link:
http://www-128.ibm.com/developerworks/java/jdk/linux/download.html
You can confirm that point at Sap note 861215.
Red Hat don't provide this package with the EL distribution (and with none, I think).
Sorry, I can't help you with CentOS installation...
Regards,
JC Llanes.
This is the java version that I've installed:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.2)
IBM J9SE VM (build 2.2, J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20060824 (JIT enabled)
J9VM - 20060802_1551_LHdSMr
JIT - r7_level20060707_1808ifx1)
I've not yet set JAVA_HOME variable, nor PATH. Any other "customization" to do?
This is the last part of the "import.monitor.java.log" when start errors:
Import Monitor jobs: running 3, waiting 31, completed 38, failed 0, total 72.
Loading of 'SAPAPPL0_9' import package: ERROR
Import Monitor jobs: running 2, waiting 31, completed 38, failed 1, total 72.
Loading of 'SAPAPPL1_9' import package: ERROR
Loading of 'SAPAPPL2_5' import package: ERROR
Import Monitor jobs: running 0, waiting 31, completed 38, failed 3, total 72.
Import Monitor jobs: running 0, waiting 31, completed 38, failed 3, total 72.
Import Monitor jobs: running 1, waiting 30, completed 38, failed 3, total 72.
Import Monitor jobs: running 2, waiting 29, completed 38, failed 3, total 72.
Import Monitor jobs: running 3, waiting 28, completed 38, failed 3, total 72.
Loading of 'SAPSSEXC_6' import package: ERROR
Import Monitor jobs: running 2, waiting 28, completed 38, failed 4, total 72.
Loading of 'SAPSSEXC_2' import package: ERROR
Import Monitor jobs: running 1, waiting 28, completed 38, failed 5, total 72.
Loading of 'SAPAPPL0_5' import package: ERROR
Import Monitor jobs: running 0, waiting 28, completed 38, failed 6, total 72.
Import Monitor jobs: running 1, waiting 27, completed 38, failed 6, total 72.
Import Monitor jobs: running 2, waiting 26, completed 38, failed 6, total 72.
Import Monitor jobs: running 3, waiting 25, completed 38, failed 6, total 72.
Loading of 'SAPAPPL0_1' import package: ERROR
Import Monitor jobs: running 2, waiting 25, completed 38, failed 7, total 72.
Loading of 'SAPAPPL0_8' import package: ERROR
Import Monitor jobs: running 1, waiting 25, completed 38, failed 8, total 72.
Loading of 'SAPAPPL0_6' import package: ERROR
Import Monitor jobs: running 0, waiting 25, completed 38, failed 9, total 72.
Import Monitor jobs: running 1, waiting 24, completed 38, failed 9, total 72.
Import Monitor jobs: running 2, waiting 23, completed 38, failed 9, total 72.
Import Monitor jobs: running 3, waiting 22, completed 38, failed 9, total 72.
Loading of 'SAPAPPL0_4' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 38, failed 10, total 72.
Loading of 'SAPPOOL' import package: ERROR
Import Monitor jobs: running 1, waiting 22, completed 38, failed 11, total 72.
Loading of 'SAPSDIC_1' import package: ERROR
Import Monitor jobs: running 0, waiting 22, completed 38, failed 12, total 72.
Import Monitor jobs: running 1, waiting 21, completed 38, failed 12, total 72.
Import Monitor jobs: running 2, waiting 20, completed 38, failed 12, total 72.
Import Monitor jobs: running 3, waiting 19, completed 38, failed 12, total 72.
Loading of 'SAPSSEXC_11' import package: ERROR
Import Monitor jobs: running 2, waiting 19, completed 38, failed 13, total 72.
Loading of 'SAPSSEXC_8' import package: ERROR
Import Monitor jobs: running 1, waiting 19, completed 38, failed 14, total 72.
Loading of 'SAPAPPL1_11' import package: ERROR
Import Monitor jobs: running 0, waiting 19, completed 38, failed 15, total 72.
Import Monitor jobs: running 1, waiting 18, completed 38, failed 15, total 72.
Import Monitor jobs: running 2, waiting 17, completed 38, failed 15, total 72.
Import Monitor jobs: running 3, waiting 16, completed 38, failed 15, total 72.
Loading of 'GLFUNCA' import package: ERROR
Import Monitor jobs: running 2, waiting 16, completed 38, failed 16, total 72.
Loading of 'SAPAPPL1_2' import package: ERROR
Import Monitor jobs: running 1, waiting 16, completed 38, failed 17, total 72.
Loading of 'SAPAPPL0_10' import package: ERROR
Import Monitor jobs: running 0, waiting 16, completed 38, failed 18, total 72.
Import Monitor jobs: running 1, waiting 15, completed 38, failed 18, total 72.
Import Monitor jobs: running 2, waiting 14, completed 38, failed 18, total 72.
Import Monitor jobs: running 3, waiting 13, completed 38, failed 18, total 72.
Loading of 'SAPSSEXC_13' import package: ERROR
Import Monitor jobs: running 2, waiting 13, completed 38, failed 19, total 72.
Loading of 'SCPRSVALS' import package: ERROR
Import Monitor jobs: running 1, waiting 13, completed 38, failed 20, total 72.
Loading of 'SAPAPPL1_6' import package: ERROR
Import Monitor jobs: running 0, waiting 13, completed 38, failed 21, total 72.
Import Monitor jobs: running 1, waiting 12, completed 38, failed 21, total 72.
Import Monitor jobs: running 2, waiting 11, completed 38, failed 21, total 72.
Import Monitor jobs: running 3, waiting 10, completed 38, failed 21, total 72.
Loading of 'SAPAPPL0_3' import package: ERROR
Import Monitor jobs: running 2, waiting 10, completed 38, failed 22, total 72.
Loading of 'SAPSDOCU' import package: ERROR
Import Monitor jobs: running 1, waiting 10, completed 38, failed 23, total 72.
Loading of 'SAPAPPL1_3' import package: ERROR
Import Monitor jobs: running 0, waiting 10, completed 38, failed 24, total 72.
Import Monitor jobs: running 1, waiting 9, completed 38, failed 24, total 72.
Import Monitor jobs: running 2, waiting 8, completed 38, failed 24, total 72.
Import Monitor jobs: running 3, waiting 7, completed 38, failed 24, total 72.
Loading of 'SAPSLOAD' import package: ERROR
Import Monitor jobs: running 2, waiting 7, completed 38, failed 25, total 72.
Loading of 'SAPSSEXC_1' import package: ERROR
Import Monitor jobs: running 1, waiting 7, completed 38, failed 26, total 72.
Loading of 'SAPSPROT' import package: ERROR
Import Monitor jobs: running 0, waiting 7, completed 38, failed 27, total 72.
Import Monitor jobs: running 1, waiting 6, completed 38, failed 27, total 72.
Import Monitor jobs: running 2, waiting 5, completed 38, failed 27, total 72.
Import Monitor jobs: running 3, waiting 4, completed 38, failed 27, total 72.
Loading of 'SAPDFACT' import package: ERROR
Import Monitor jobs: running 2, waiting 4, completed 38, failed 28, total 72.
Loading of 'SAPDDIM' import package: ERROR
Import Monitor jobs: running 1, waiting 4, completed 38, failed 29, total 72.
Loading of 'SAPUSER' import package: ERROR
Import Monitor jobs: running 0, waiting 4, completed 38, failed 30, total 72.
Import Monitor jobs: running 1, waiting 3, completed 38, failed 30, total 72.
Import Monitor jobs: running 2, waiting 2, completed 38, failed 30, total 72.
Import Monitor jobs: running 3, waiting 1, completed 38, failed 30, total 72.
Loading of 'SAP0000' import package: ERROR
Import Monitor jobs: running 2, waiting 1, completed 38, failed 31, total 72.
Loading of 'SAPUSER1' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 38, failed 32, total 72.
Loading of 'SAPDODS' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 38, failed 33, total 72.
Can you have some suggestions to solve the problem?
<b>Can I retry to resume installation from the point 17 or I've to start from the beginning and clear my last installation?
</b>
Good Morning to everybody.
I''ve set all PATH and variables (JAVA_HOME, LD_ASSUME_KERNEL) in bash_rc file, as suggested in yours replies.
But the problem is not still solved.
Reading log files, I've noticed that MAXDB instance wasn't start., and this cause many errors.
So I've started it manually, with command
./dbmcli -d MDB -u control,***** db_online
I've restarted the installation process (as root), with the option "continue old installation".
It restarted from step 17 , IMPORT ABAP. It seems that the previous errors doesn't occurs but after a night the process is "locked" on this step. No errors, no warnings..
I've interrupted the process, and tried to restart. At this point I've received this messages
<b>ERROR 2007-03-27 05:43:10
CJS-30022 Program 'Migration Monitor' exits with error code 103. For
details see log file(s) import_monitor.java.log, import_monitor.log.</b>
But this log doesnt' contain any errors or warnings.
Any suggestions? I really don't know how to solve the problem.
Hi Luca,
I've seen this error CJS-30022 one time. It was solved restarting the database and Retrying. There was a locked DB process as seen in another installation trace. I can't remember the file name, but you can take a look at the latest ones at the install log dir.
Be aware too about the permissions of the installation dir (change it to 777).
Regards,
JC Llanes.
Hi,
I've followed all yours tips to solve my problem, but after 5 hours the installer is always on step "IMPORT ABAP". Giving "top" command on a terminal no processes related to SAP are running, the disk usage not increase.
The situation is locked.
I don't receive any error or messages from the installer.
THe last messages on <b>import_monitor.log</b> are
TRACE: 2007-03-28 13:47:32 com.sap.inst.migmon.LoadTask processPackage
Loading of 'GLFUNCA' import package into database:
/usr/sap/DEV/SYS/exe/run/R3load -i GLFUNCA.cmd -dbcodepage 4103 -l GLFUNCA.log -nolog -c 0
TRACE: 2007-03-28 13:47:32 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL0_10' import package into database:
/usr/sap/DEV/SYS/exe/run/R3load -i SAPAPPL0_10.cmd -dbcodepage 4103 -l SAPAPPL0_10.log -nolog -c 0
the last messages of <b>import_monitor.java.log </b>are:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.2)
IBM J9SE VM (build 2.2, J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20060824 (JIT enabled)
J9VM - 20060802_1551_LHdSMr
JIT - r7_level20060707_1808ifx1)
Import Monitor jobs: running 1, waiting 10, completed 61, failed 0, total 72.
Import Monitor jobs: running 2, waiting 9, completed 61, failed 0, total 72.
Import Monitor jobs: running 3, waiting 8, completed 61, failed 0, total 72.
I don't think that is a problem on db..
bash>./dbmcli -d MDB -u DBM,DBM db_state
OK
State
ONLINE
In SAPAPPL0_10.log, there are errors that says, but I think that they referred to my previous tests (the date is not specified in this log)
DbSl Trace: EXECUTE on connection 0, rc=-10821 (Session not connected)
(IMP) ERROR: LOCK TABLE failed for table ZSKCOUNLAN
DbSl Trace: EXECUTE on connection 0, rc=-10821 (Session not connected)
What is the maxdb log in sapinst_instdir, that you said in your previous post??
Any other suggestions?
REgards.
Luca
Hi Luca,
You're right. The RH version 4 is certified by Sap. But they don't certify "updates" of each version.
I have a lot of Sap systems (including some productives) running RHEL4 Update 3, and they run OK.
But, if I had to install a new system, then I would choose RHEL4 Update 4 (the most recent "tested" that appears at the Supported Platforms link you've seen). I would choose too the most recent kernel tested by Sap (not the latest at RH site).
I would not install RH version 5. This is NOT certified.
Hope it can help. Best Regards,
JC Llanes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, RHEL4 Uptade 4 is the latest available and certified Red Hat release for SAP.
RHEL5 is on its way to certification. If everything goes well, it will be certified at least for 7.00 based products by mid/end of Q2.
RHEL4 Update 5 can automatically be used at customer site, when it is released by Red Hat according our now certification rules.
Best Regards,
Hannes Kuehnemund
SAP Linuxlab, Walldorf
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.