Abstract: RAPID CLONE: "UNZIP FAILED: COULD NOT FIND DBFINFO.LST"

=============================================================================
PROBLEM DESCRIPTION :
Using Rapid Clone Method. customer is getting the error when runing database
in
mode=apply
** DETAILED DESCRIPTION OF PROBLEM, INCLUDING ALL ERRORS:
Customer is rapid clone and getting the following error
u02/oracle/testdb/8.1.7/appsutil/bin/adclone.sh java=/usr/jdk1.3.1 mode=apply
stage=/u07/orastage component=database method=CUSTOM
dbctxtg=/u02/oracle/testdb/8.1.7/appsutil/TEST.xml
Using Archive:  /u07/orastage/jlib/adconfig.zip
$$Header: adconfig.zip 115.220 2003/01/24 02:37:29 pkm ship                  

    $
Beginning database Apply - Mon Mar  3 07:42:34 MST 2003
Log file located at
/u02/oracle/testdb/8.1.7/appsutil/log/TEST/ApplyDatabase_03030742.log
Unzip Failed:
java.lang.Exception: Could not find dbfinfo.lst
        at
oracle.apps.ad.clone.ApplyDatabase.updParams(ApplyDatabase.java:329)
        at oracle.apps.ad.clone.ApplyDatabase.<init>(ApplyDatabase.java:214)
        at oracle.apps.ad.clone.ApplyDatabase.main(ApplyDatabase.java:625)
ERROR: Database creation not successfull. Please check logfile
Completed Apply...
Message In Log File.
Executing runInstallDriver...
Started unzipping files...
UNZIP used: UnZip 5.41 of 16 April 2000, by Info-ZIP.  Maintained by C.
Spieler.  Send
Unzip 0 FAILED
Instantiating /u02/oracle/testdb/8.1.7/appsutil/template/adcrdbclone.sql to
/u02/oracle/testdb/8.1.7/appsutil/install/TEST/adcrdbclone.sql
instantiate  file:
   source : /u02/oracle/testdb/8.1.7/appsutil/template/adcrdbclone.sql
   dest   : /u02/oracle/testdb/8.1.7/appsutil/install/TEST/adcrdbclone.sql
Unable to Write to File
java.io.FileNotFoundException:
/u02/oracle/testdb/8.1.7/appsutil/template/adcrdbclone.sql (No such file or
directory)
Could not find dbfinfo.lst.
Executing runAutoConfig...
Processing  DriverFile =
/u02/oracle/testdb/8.1.7/appsutil/template/addbtmpl.drv
Uploading  Complete Log File.

The version of adconfig.zip is  $Header: adconfig.zip 115.220 2003/01/24
02:37:29 pkm ship

Customer has applied  patch  2797948  which may be causing this problem
according to Bug 2829244
 


There is already a internal  bug 2829244 for this issue. which say "For
internal use, you can apply RAPID CLONE UPDATE PATCH #2770792 for this fix"

Patch   2770792 is not available yet.
Customer's Go Live Date is Closer. They have to do testing before golive.
Can we get this patch 277079?


TAR NUMBER (ALSO ENSURE BUG NUMBER FIELD IS UPDATED IN THE TAR): 2945179.999

LIST ADDITIONAL DOCUMENTATION AVAILABLE (LOG FILE, REPORT,
on ess30
Yes
DESCRIBE ANY WORKAROUND(S) AVAILABLE TO THE CUSTOMER:

No
LIST NAME & VERSION OF ALL MODULES INVOLVED (FORM, REPORT,
The version of adconfig.zip is  $Header: adconfig.zip 115.220 2003/01/24
02:37:29 pkm ship



Customer 
will be available

Customer's Management 24x7 contact number: 011919848456282
*** 03/05/03 09:37 am *** (CHG: Sta->11)
*** 03/05/03 09:37 am ***
*** 03/05/03 11:55 am ***
can we get the status of this?
from Custoemr:
it can adversely affect our Go-Live Date. Hence I would really
appreciate if you could advise when we can expect to download the Patch.
*** 03/05/03 12:47 pm ***
*** 03/05/03 12:47 pm ***
*** 03/05/03 12:48 pm ***
Patch for download will be available tomorrow.
*** 03/06/03 03:31 am ***
Hi,
I have a cst COLT COMMUNICATION ( tar 2859640.996 ) who faced the same
issue. It 's a critical cst and it 's a P1 tar. So, cst is waiting for this
fix (patch ) tomorrow. Please, do your best, thanks !
*** 03/06/03 10:09 am ***
I have a CT DIAMOND POWER INTERNATIONAL INC TAR (2955265.999)who faced the
same issue. It 's a critical CT  and is waiting for this fix (patch ) ASAP.
Thanks!
*** 03/06/03 11:28 am ***
Until a patch is ready, below is a workaound that I can think of, that should
allow to complete the apply phase of cloning (won't harm anything):

- retreive adconfig,zip 115.209 from Rapid Clone patch 2716712 (file located
in ad/java/ when you unzip the ARU)
- On the target system, go to <clonestage dir>/jlib/ (clonestage dir is the
directory passed as stage=<clonestage dir> to adclone.sh)
- replace the existing adconfig.zip 115.220 by adconfig.zip 115.209
- rerun the adclone.sh apply command normally.
*** 03/06/03 11:35 am *** (CHG: Sta->30)
*** 03/07/03 05:47 am *** (CHG: Sta->11)
*** 03/07/03 05:47 am ***
From customer:
New info : it worked for us. However we need the latest patch, Because I Found

two bugs in adconfig.zip. one is eventhough we have  multiuser environment, it

is taking appltst as a oracle owner and appl_top owner. Please update me as
soon as patch availiable.. I will be doing one more cloning this friday. I
Like to test the new patch
*** 03/07/03 10:36 am ***
the multiuser environment issue is another problem. Please file a
new bug for the problem you are facing and give us more information

As the workaround works to fix the problem with unzip, we should not
update this bug further and mix it with other issues. Doing so will
just confuse customers/users.

*** 03/07/03 10:38 am *** (CHG: Sta->35)
*** 03/07/03 10:38 am ***
*** 03/07/03 10:38 am ***
We will release a one off patch for the unzip problem later today. Until then
follow the instructions given by EFICHET  03/06/03 11:28 am ***

*** 03/07/03 05:00 pm ***
*** 03/07/03 05:57 pm ***
The below mentioned instructions should only be followed by RapidClone
customers that have adconfig.zip version 115.220.

To solve the above mentioned problem, you have two possibilities:

1) Workaround
   ==========
   - retreive adconfig,zip 115.209 from Rapid Clone patch 2716712
     (file located in ad/java/ when you unzip the ARU)
   - On the target system, go to <clonestage dir>/jlib/ (clonestage dir
     is the directory passed as stage=<clonestage dir> to adclone.sh)
   - replace the existing adconfig.zip 115.220 by adconfig.zip 115.209
   - rerun the adclone.sh apply command normally.

  
2) Apply patch 2834496
   ===================
   - Apply the patch for this bug (2834496) with adpatch.
   - Follow the RapidClone Document (Metalink Note 135792.1); perform all
     the steps in "Prepare the Source System for RapidClone" starting
     from step 6 (Create the RDBMS ORACLE_HOME Rapid Clone files).
   - perform the steps for staging the database



  
*** 03/07/03 06:12 pm ***
*** 03/07/03 06:12 pm ***
*** 03/10/03 04:49 am ***
*** 03/10/03 04:49 am *** (CHG: Sta->11)
*** 03/10/03 04:16 pm *** (CHG: Sta->35)
*** 03/10/03 04:16 pm ***
*** 03/10/03 04:16 pm ***
*** 03/10/03 04:18 pm ***
*** 03/11/03 09:54 am ***
*** 03/11/03 10:06 am ***
*** 03/13/03 03:41 am ***
*** 03/13/03 11:03 am *** (CHG: Sta->11)
*** 03/13/03 11:03 am ***
*** 03/13/03 11:57 am *** (CHG: Sta->35)
*** 03/13/03 11:57 am ***
*** 03/13/03 11:57 am ***
*** 03/13/03 11:59 am ***
The below mentioned instructions should only be followed by RapidClone
customers that have adconfig.zip version 115.220.

To solve the above mentioned problem, use the following workaround:

Workaround
==========
  - retreive adconfig,zip 115.209 from Rapid Clone patch 2716712
    (file located in ad/java/ when you unzip the ARU)
  - On the target system, go to <clonestage dir>/jlib/ (clonestage dir
    is the directory passed as stage=<clonestage dir> to adclone.sh)
  - replace the existing adconfig.zip 115.220 by adconfig.zip 115.209
  - rerun the adclone.sh apply command normally.

A Rapidclone rollup patch will be released in the next couple of days.
*** 03/13/03 12:04 pm ***
*** 03/14/03 07:04 am ***
*** 04/10/03 12:53 pm ***
*** 04/10/03 02:15 pm ***
So are you saying that this is fixed for CT in patch 2870461 that is released?
*** 09/11/05 10:33 pm ***

Thanks
Srini