on 06-08-2011 4:05 AM
Hi Experts.
I face this problem while installing SOLMAN 7.0 EHP1 for MAXDB on Windows 2003 . DO you have any idea what happens with my installation?*
*(Before installing this, I have more than 80GB hard disk and 4Gb RAM on Server)*An error occurred while processing option SAP Solution Manager 7.0 EhP1 > SAP Systems > MaxDB > Central System > Central System( Last error reported by the step: Execution of JLoad tool 'C:\j2sdk1.4.2\bin\java.exe -classpath "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ADA\CENTRAL\AS\install\sharedlib\launcher.jar" -showversion -Xmx512m com.sap.engine.offline.OfflineToolStart com.sap.inst.jload.Jload "C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ADA/CENTRAL/AS/install/lib/iaik_jce.jar;C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ADA/CENTRAL/AS/install/sharedlib/jload.jar;C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ADA/CENTRAL/AS/install/sharedlib/antlr.jar;C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ADA/CENTRAL/AS/install/sharedlib/exception.jar;C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ADA/CENTRAL/AS/install/sharedlib/jddi.jar;C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ADA/CENTRAL/AS/install/sharedlib/logging.jar;C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ADA/CENTRAL/AS/install/sharedlib/offlineconfiguration.jar;C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ADA/CENTRAL/AS/install/sharedlib/opensqlsta.jar;C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ADA/CENTRAL/AS/install/sharedlib/tc_sec_secstorefs.jar;C:\sapdb\programs\runtime\jar\sapdbc.jar" -sec TST,jdbc/pool/TST,
SAPDEMO/sapmnt/TST/SYS/global/security/data/SecStore.properties,
SAPDEMO/sapmnt/TST/SYS/global/security/data/SecStore.key -dataDir "C:\Documents and Settings\Administrator\Desktop\SOLMAN\SOLMAN JAVA Component\51040439\DATA_UNITS\SOLMAN_JAVA_EXPORT_JDMP" -job "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ADA\CENTRAL\AS\IMPORT.XML" -log jload.log' aborts with return code 1. SOLUTION: Check 'jload.log' and 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ADA/CENTRAL/AS/jload.java.log' for more information.
Once I went and check jload.java.log and jload.log, there's something relate to space disk. Here are the log for the 2 files:
Jun 8, 2011 10:21:42 AM com.sap.inst.jload.Jload main
SEVERE: couldn't connect to DB
Jun 8, 2011 10:21:42 AM com.sap.inst.jload.Jload logStackTrace
SEVERE: com.sap.dbtech.jdbc.exceptions.DatabaseException: [-907]: Space for user session exhausted
at com.sap.dbtech.jdbc.packet.ReplyPacket.createException(ReplyPacket.java:65)
at com.sap.dbtech.jdbc.ConnectionSapDB.throwSQLError(ConnectionSapDB.java:1061)
at com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:689)
at com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:563)
at com.sap.dbtech.util.security.AuthenticationManager.<init>(AuthenticationManager.java:78)
at com.sap.dbtech.jdbc.ConnectionSapDB.doConnect(ConnectionSapDB.java:405)
at com.sap.dbtech.jdbc.ConnectionSapDB.<init>(ConnectionSapDB.java:136)
at com.sap.dbtech.jdbc.DriverSapDB.connect(DriverSapDB.java:246)
at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215)
at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection(OpenSQLDataSourceImpl.java:522)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:276)
at com.sap.inst.jload.db.DBConnection.connectViaSecureStore(DBConnection.java:105)
at com.sap.inst.jload.db.DBConnection.connect(DBConnection.java:149)
at com.sap.inst.jload.Jload.main(Jload.java:583)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
And this's jload.log:
8.06.11 10:21:42 com.sap.inst.jload.Jload main
SEVERE: couldn't connect to DB
08.06.11 10:21:42 com.sap.inst.jload.Jload logStackTrace
SEVERE: com.sap.dbtech.jdbc.exceptions.DatabaseException: [-907]: Space for user session exhausted
at com.sap.dbtech.jdbc.packet.ReplyPacket.createException(ReplyPacket.java:65)
at com.sap.dbtech.jdbc.ConnectionSapDB.throwSQLError(ConnectionSapDB.java:1061)
at com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:689)
at com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:563)
at com.sap.dbtech.util.security.AuthenticationManager.<init>(AuthenticationManager.java:78)
at com.sap.dbtech.jdbc.ConnectionSapDB.doConnect(ConnectionSapDB.java:405)
at com.sap.dbtech.jdbc.ConnectionSapDB.<init>(ConnectionSapDB.java:136)
at com.sap.dbtech.jdbc.DriverSapDB.connect(DriverSapDB.java:246)
at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215)
at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection(OpenSQLDataSourceImpl.java:522)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:276)
at com.sap.inst.jload.db.DBConnection.connectViaSecureStore(DBConnection.java:105)
at com.sap.inst.jload.db.DBConnection.connect(DBConnection.java:149)
at com.sap.inst.jload.Jload.main(Jload.java:583)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Edited by: Bui Tony on Jun 8, 2011 5:06 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for all your quick respond.
The issue was solved after I reinstalled DB.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
> I face this problem while installing SOLMAN 7.0 EHP1 for MAXDB on Windows 2003 . DO you have any idea what happens with my installation?*
I HIGHLY recommend not using a 32bit operating system for Solution Manager, you will run into lots of problems and issues concerning memory usage and limitations of the 32bit platform.> 08.06.11 10:21:42 com.sap.inst.jload.Jload logStackTrace
> SEVERE: com.sap.dbtech.jdbc.exceptions.DatabaseException: [-907]: Space for user session exhausted
It seems that the maximum memory on 32bit is reached already. Decrase the CACHESIZE of the database, restart the database and press "retry" in sapinst.
This will not be the only problem you will get, use a 64bit server and at least 8 GB memory for Solution Manager.
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
78 | |
9 | |
8 | |
6 | |
6 | |
6 | |
6 | |
6 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.