SAP Jload TroubleShooting
需积分: 0 164 浏览量
2010-07-11
22:24:51
上传
评论
收藏 17KB PDF 举报
05.07.2010 Page 1 of 3
SAP Note 942766 - Jload troubleshooting
Note Language: English Version: 1 Validity: Valid Since 21.04.2006
Summary
Symptom
You experience problems with installation/upgrade/system copy while running
JLoad.
Other terms
JLoad, SAPinst, JUP
Reason and Prerequisites
JLoad can sometimes experience problems executing the export/import process
for several reasons. This note aims to collect and keep up to date the most
often symptoms and their solutions.
Solution
Before you create a support message check if any of the following standard
problems is the reason for the failure:
JLoad hangs during import of a database.
Solution: On some JREs JLoad has problem due to bugs in ZIP implementation.
Not all cases are identified but following JDKs are known to cause
problems:
- SUN: 1.4.2_10
- SUN: 1.5.0_07
- SAP: 1.5.0_07
JLoad fails with message in the logfile "SEVERE: couldn't
connect to DB"
Solution: Please check and ensure that:
- Your database server is started.
- Your database instance is running and you can connect to it
through the network interface
- The entries in secure store contain the correct options for
connecting to the database. (These can be checked via
configtool and this only applies to the case when JLoad is run
using secure store parameters)
Jload fails during import when Java export is mounted via NFS,
one of following strings is in the logfile:
- Solaris:"SEVERE: java.util.zip.ZipException: invalid block
type"
- HP-UX:"SEVERE: java.io.IOException: Value too large to be
stored in data type" or "SEVERE: java.io.IOException: Invalid
argument"
Reson: Unkonwn. Probably limitation in filesize in NFS2.
评论0