Java system copy hang on Import Java Dump

[Former Member]

Hi all!

I´m running a java system copy (MII 14), Linux RHE and Sybase, NW 731.

The installation hangs on Import Java Dump, without errors in sapinst.

I found some topics with similar issues, but Nothing help my case.

Database is online, trans log OK, disk space enought, memory ok, swap ok.

In the sta files, IMPORT_2_POSTPROCESS.sta and IMPORT_4_POSTPROCESS.sta, the last table has BRK status, but i can´t find why.

E.g., the IMPORT_2_POSTPROCESS.sta, last line:

T:J2EE_CACHE_CONTENT:METADATA POSTPROCESS BRK           05.03.15 09:30:17

And log file IMPORT_2_POSTPROCESS.XML.log:

Mar 5, 2015 9:30:15 AM com.sap.inst.dbtools [Thread[pool-1-thread-1,5,main]] Info: Directing logs for com.sap.inst.jload.DBJob@1843095f to file IMPORT_2_POSTPROCESS.XML.log

Mar 5, 2015 9:30:15 AM com.sap.inst.dbtools [Thread[pool-1-thread-1,5,main]] Info: Directing logs for com.sap.inst.jload.DBJob@4fd654da to file IMPORT_2_POSTPROCESS.XML.log

Mar 5, 2015 9:30:15 AM com.sap.inst.dbtools [Thread[pool-1-thread-1,5,main]] Info: Started logging to IMPORT_2_POSTPROCESS.XML.log

Mar 5, 2015 9:30:15 AM com.sap.inst.dbtools [Thread[pool-1-thread-1,5,main]] Info: Connecting to database

Mar 5, 2015 9:30:16 AM com.sap.inst.dbtools [Thread[pool-1-thread-1,5,main]] Info: Connected to database

Mar 5, 2015 9:30:17 AM com.sap.inst.dbtools [Thread[pool-1-thread-1,5,main]] Info: Trying to read status file /tmp/sapinst_instdir/NW731/SYB/COPY/SYSTEM/STD/AS-JAVA/IMPORT_2_POSTPROCESS.sta

Mar 5, 2015 9:30:17 AM com.sap.inst.dbtools [Thread[pool-1-thread-1,5,main]] Warning: Status file /tmp/sapinst_instdir/NW731/SYB/COPY/SYSTEM/STD/AS-JAVA/IMPORT_2_POSTPROCESS.sta found

Mar 5, 2015 9:30:17 AM com.sap.inst.dbtools [Thread[pool-1-thread-1,5,main]] Info: Resuming previous execution

Mar 5, 2015 9:30:17 AM com.sap.inst.dbtools [Thread[pool-1-thread-1,5,main]] Info: Postprocessing table J2EE_CACHE_CONTENT

jmigmon.console.log last lines:

Processing tasks

completed:18 aborted:0 running:1 pending:1

completed:18 aborted:0 running:2 pending:0

Starting task IMPORT_2_POSTPROCESS.XML

Starting task IMPORT_4_POSTPROCESS.XML

Starting to log to IMPORT_2_POSTPROCESS.XML.log

Starting to log to IMPORT_4_POSTPROCESS.XML.log

Postprocessing J2EE_CACHE_CONTENT

Jload.trc last lines:

Mar 5, 2015 9:30:17 AM                       com.sap.inst.dbtools [Thread[pool-1-thread-1,5,main]] Info: Resuming previous execution

Mar 5, 2015 9:30:17 AM                       com.sap.inst.dbtools [Thread[pool-1-thread-1,5,main]] Info: Postprocessing table J2EE_CACHE_CONTENT

Mar 5, 2015 9:30:17 AM                       com.sap.inst.dbtools [Thread[pool-1-thread-1,5,main]] Info: Statement text is <?xml version="1.0"?>

<Dbtable name="J2EE_CACHE_CONTENT" creation-date="">

<properties>

      <author></author>

      <description>

            <description>J2EE_CACHE_CONTENT</description>

            <language></language>

      </description>

</properties>

<ignore-config></ignore-config>

<predefined-action></predefined-action>

<position-is-relevant>false</position-is-relevant>

<deployment-status></deployment-status>

<columns>

      <column>

            <builtIn-type>integer</builtIn-type>

            <decimals>0</decimals>

            <default-value>0</default-value>

            <is-not-null>true</is-not-null>

            <java-sql-type>INTEGER</java-sql-type>

            <length>0</length>

            <name>RID</name>

            <position>1</position>

      </column>

      <column>

            <builtIn-type>string</builtIn-type>

            <decimals>0</decimals>

            <default-value> </default-value>

            <is-not-null>true</is-not-null>

            <java-sql-type>VARCHAR</java-sql-type>

            <length>128</length>

            <name>KEY_NAME</name>

            <position>2</position>

      </column>

      <column>

            <builtIn-type>long</builtIn-type>

            <decimals>0</decimals>

            <default-value>0</default-value>

            <is-not-null>true</is-not-null>

            <java-sql-type>BIGINT</java-sql-type>

            <length>0</length>

            <name>CREATION_TIME</name>

            <position>3</position>

      </column>

      <column>

            <builtIn-type>long</builtIn-type>

            <decimals>0</decimals>

            <default-value>0</default-value>

            <is-not-null>true</is-not-null>

            <java-sql-type>BIGINT</java-sql-type>

            <length>0</length>

            <name>EXPIRATION_TIME</name>

            <position>4</position>

      </column>

      <column>

            <builtIn-type>binary</builtIn-type>

            <decimals>0</decimals>

            <default-value></default-value>

            <is-not-null>false</is-not-null>

            <java-sql-type>LONGVARBINARY</java-sql-type>

            <length>2000</length>

            <name>OBJECT_ATTR</name>

            <position>5</position>

      </column>

      <column>

            <builtIn-type>binary</builtIn-type>

            <decimals>0</decimals>

            <default-value></default-value>

            <is-not-null>false</is-not-null>

            <java-sql-type>BLOB</java-sql-type>

            <length>50000000</length>

            <name>LARGE_OBJECT_ATTR</name>

            <position>6</position>

      </column>

      <column>

            <builtIn-type>binary</builtIn-type>

            <decimals>0</decimals>

            <default-value></default-value>

            <is-not-null>false</is-not-null>

            <java-sql-type>LONGVARBINARY</java-sql-type>

            <length>2000</length>

            <name>OBJECT_VALUE</name>

            <position>7</position>

      </column>

      <column>

            <builtIn-type>binary</builtIn-type>

            <decimals>0</decimals>

            <default-value></default-value>

            <is-not-null>false</is-not-null>

            <java-sql-type>BLOB</java-sql-type>

            <length>50000000</length>

            <name>LARGE_OBJECT_VALUE</name>

            <position>8</position>

      </column>

</columns>

<primary-key>

      <columns>

            <column>RID</column>

            <column>KEY_NAME</column>

      </columns>

      <tabname>J2EE_CACHE_CONTENT</tabname>

</primary-key>

<indexes></indexes>

<technical-info></technical-info>

<database-exclusive-info></database-exclusive-info>

<db-specifics></db-specifics>

</Dbtable>

Mar 5, 2015 9:30:17 AM                       com.sap.inst.dbtools [Thread[pool-1-thread-1,5,main]] Info: Postprocessing J2EE_CACHE_CONTENT

[former_member659746]

Hi,

the problem is the ASE locks concept. By defualt, sapinst installs the parameter number of locks to 1 Million. This is not enough if you use, ex, 20 processes. Just calculate like this:

10 processes = 1 Million locks

Locks

For most SAP systems, the default of one million locks configured by the installer will not be sufficient. If systems are migrated from database platforms that provide lock escalation (like DB2 or MaxDB), or from platforms that do not have a global lock list (like Oracle), it can become difficult to estimate the maximum number of locks required simultaneously. The recommendation is to start with anumber of locksconfigured between 2 and 5 million with a rough formula of 1 million locks per terabyte of used data space.

An important aspect of data loading is to ensure that there are sufficient locks to support parallel imports into multiple tables. Keep in mind that the default schema for the SAP database is to use data rows locking – and that bulk loading is transactional in nature – even if the row modifications are not logged. As a result, you need to have sufficient locks for the number of rows loaded per table based on the commit frequency of the bulk load operation. The default installation also should set the row lock promotion to 2 billion rows. As a consequence, the loads will not escalate to a partition or table lock as normally would be expected. This is deliberate as concurrent loads into the same table (due to splits) could contend with one another if lock escalation occurred.

link:

https://help.sap.com/viewer/ase_best_practices/8d96aacd3e744255976646c12f5e8d73.html

Nuno

[janos_czettler]

Hi All,

we have faced same error during a JAVA import process at system copy of a JAVA stack.

Our environment:

OS: RHEL 7.1 (latest verison)

DB: Sybase ASE 16.0.0.5 (latest version)

SWPM: SWPM 1.0 SP07 (lates version)

There are no problem with the free disk spaces, sybase log are is totally free, no other error in the sapinst dir (actually is /tmp/sapinst_instdir/NW740SR2/SYB/COPY/SYSTEM/STD/AS-JAVA ).

What I see is that there is a process running:

jdiadm   11878 11551  0 Apr27 pts/1    00:01:17 /tmp/sapinst_instdir/NW740SR2/SYB/COPY/SYSTEM/STD/AS-JAVA/sapjvm/sapjvm_6/bin/java -classpath /tmp/sapinst_instdir/NW740SR2/SYB/COPY/SYSTEM/STD/AS-JAVA/install/sltools/sharedlib/sap.com~tc~bl~offline_launcher~impl.jar -showversion -Xmx1024m -XX:+HeapDumpOnOutOfMemoryError com.sap.engine.offline.OfflineToolStart com.sap.inst.jmigmon.jMigMon /usr/sap/JDI/SYS/global/security/lib/tools/iaik_jce.jar:/usr/sap/JDI/SYS/global/security/lib/tools/iaik_jsse.jar:/usr/sap/JDI/SYS/global/security/lib/tools/iaik_smime.jar:/usr/sap/JDI/SYS/global/security/lib/tools/iaik_ssl.jar:/usr/sap/JDI/SYS/global/security/lib/tools/w3c_http.jar:/tmp/sapinst_instdir/NW740SR2/SYB/COPY/SYSTEM/STD/AS-JAVA/install/sltools/sharedlib:/usr/sap/JDI/SYS/global/syb/linuxx86_64/sybjdbc/jconn4.jar -mode import -sid JDI -dsn jdbc/pool/JDI -ssprops /usr/sap/JDI/SYS/global/security/data/SecStore.properties -sskey /usr/sap/JDI/SYS/global/security/data/SecStore.key -importDirs /mnt/install/JDIexport/JAVA/JDMP -suppressVerboseLog

But this running java binary does not use any resource (CPU, disk IO)

Is anybody give up an incident to SAP? I think we will...

Regards: Janos

[janos_czettler]

some additional info:

The import process become hanging status at the last two phases (in import.jmigmon.states):

IMPORT_0_METADATA.XML=+

IMPORT_4_POSTPROCESS.XML=+

IMPORT_3.XML=+

IMPORT_14_J2EE_CONFIGENTRY.XML=+

IMPORT_15_J2EE_CONFIGENTRY.XML=+

IMPORT_12_J2EE_CONFIGENTRY.XML=+

IMPORT_18_J2EE_CONFIGENTRY.XML=+

IMPORT_10_J2EE_CONFIGENTRY.XML=+

IMPORT_7_J2EE_CONFIGENTRY.XML=+

IMPORT_16_J2EE_CONFIGENTRY.XML=+

IMPORT_5_J2EE_CONFIGENTRY.XML=+

IMPORT_9_J2EE_CONFIGENTRY.XML=+

IMPORT_6_J2EE_CONFIGENTRY.XML=+

IMPORT_13_J2EE_CONFIGENTRY.XML=+

IMPORT_8_J2EE_CONFIGENTRY.XML=+

IMPORT_19_J2EE_CONFIGENTRY.XML=+

IMPORT_11_J2EE_CONFIGENTRY.XML=+

IMPORT_17_J2EE_CONFIGENTRY.XML=+

IMPORT_1.XML=+

IMPORT_2_POSTPROCESS.XML=?

IMPORT_20_J2EE_CONFIGENTRY_POSTPROCESS.XML=?

[Former Member]

Hi Janos,

We are facing the exact same issue and we have raised an OSS to SAP. Awaiting their reply..

[janos_czettler]

Hi Shilpa,

thanks for your reply!

Fortunately I have to copy an empty - but patched up to latest SP stack - JAVA stack so my workaround was that I installed a new one instead of copy the existing, but it is not a correct way.

If you have any result with your incident could you share us the possible solution?

Thank you if you can.

Regards,

Janos

[chetna_verma2]

Hi,

I am facing similar issue where java import hangs for table at 99% with no errors in error logs .

OS is AIX 7.1 and DB is Oracle 11.2.0.4 .

I'm performing a PI ( ABAP+JAVA) Target System copy using swpm .

Last line in Import.sta is the following :

T:T_CHUNK:METADATA CREATE OK	22.05.15 15:08:15
T:T_CHUNK:DATA INSERT BRK	27.05.15 16:53:30

Jload.trc shows :

com.sap.inst.dbtools [Thread[main,5,main]] Info: Importing table T_CHUNK : 99% complete (2594709 rows)

com.sap.inst.dbtools [Thread[main,5,main]] Info: Job T_CHUNK[null] : commiting transaction. Total rows inserted : 2602548

Any ideas you can share on this ?

I am using JVM version vmVersion=6.1.071

Thank you .

[Former Member]

Hi Chetna,

We have raised an OSS for SAP, however there is no resolution from SAP yet

Best Regards,

Shilpa

[Former Member]

Hi Shilpa,

We are facing a similar issue and not getting any clue to go past this.

Were you able to get over this issue?

Could you be kind to provide your inputs on this?

Best Regards

Suman Reddy

[Former Member]

Hello All,

I has similar issue as above and couldn't find any solution anywhere on SCN though there were a few customers who have already faced this issue.

Just wanted to post the solution here which might be useful for the next victim

This is not an issue with SWPM nor Jload; but a deadlock situation with Sybase and Migmon.

1. Restart the installation from Scratch to make it a clean installation.

2. Set jobNum=1 in import.jmigmon.properties file. This can be done in the initial steps as well while you are providing the parameters.

That finished my job !!

Best Regards

Suman Reddy

[janos_czettler]

Hi Suman,

thanks for you replay and workaround tip!

Regards,

Janos

[Former Member]

Hi,

I am facing exactly same issue on Sybase for EP import.

I will use no. of import processes = 1 and will post my results.

Regards

Rupesh

[Former Member]

Yes i am able to complete import java with this trick

Regards

Rupesh

[Former Member]

Hi Marcos,

Could you resolve this issue. I am doing a system copy of PI system, Linux RHE and Sybase, NW 731.

And I am stuck at the exact same phase?

Thanks.

[MaLoo]

Hi Marcos,

Did you have any succes? I am facing exact the same issue, also Sybase, NW 730, only OS is Windows 2012. Did a run on Windows 2008 without problems, but now I am facing this issue.

[Former Member]

Hi Martin.

By system copy i can´t finish the installation.

The solution was install an AS Java, and do a export of the MII component in the source system, and import on target.

If you can resolve, please, let me know.

Regards.

[MaLoo]

Ok, thanks for your answer. I'll let you know.