File Size is 4 Gigs for copyConfig Resulting in Invalid Archive When Running extractMovePlan (Doc ID 2169578.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Symptoms

ISSUE CLARIFICATION
====================
When using copyconfig script, the maximum file size is 4 gigs resulting in a corrupt jar.

ACTUAL BEHAVIOR
=================
While attempting extract on the same source server using command:
./extractMovePlan.sh -javaHome $JAVA_HOME -archiveLoc /oracle/clone/fullDomainArchive.jar -planDirLoc /oracle/clone/CloneSource
The error message "Invalid archive file" is received

STEPS
=====
cd /oracle/middleware/oracle_common/bin
./copyConfig.sh -javaHome $JAVA_HOME -archiveLoc /oracle/clone/fullDomainArchive.jar -sourceDomainLoc /oracle/middleware/user_projects/domains/prod_domain -sourceMWHomeLoc /oracle/middleware -domainHostName XXXX.YYY.com -domainPortNum 7001 -domainAdminUserName weblogic -domainAdminPasswordFile /oracle/clone/pass.txt -silent true

It created a 4+ Gig .jar file.

EXPECTED BEHAVIOR
===================
copyConfig should not stop at 4 gigs when creating a jar file
The archive created should be valid.

BUSINESS IMPACT
================

Cannot copy the Domain

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.