EBS CLONE遇到的sh: 987140 Illegal instruction(coredump)问题解决方法

萨尔法保护

前段时间在我在AIX平台做EBS DB CLONE的时候遇到了不少问题。现在我把主要的一些问题罗列一下，对需要注意的地方进行了注释。希望大家做CLONE的时候顺利一点。
$ perl adcfgclone.pl dbTier   
Enter the APPS password [APPS]:  apps
ERROR : Unable to set CLASSPATH
    /u01/orauat/uatdb/9.2.0/appsutil/clone/bin/../jlib/classes111.zip: is  missing

First Creating a new context file for the cloned system.
The program is going to ask you for information about the new system:
sh: 987140 Illegal instruction(coredump)
ERROR: context creation not completed successfully.
Please check /tmp/adcfgclone.err file for errors
$ more /tmp/adcfgclone.err
stackpointer=2ff208c0
JVMXM004: JVM is performing abort shutdown sequence
JVMDG217: Dump Handler is Processing a Signal - Please Wait.
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /u01/orauat/uatdb/9.2.0/appsutil/clone/bin/javacore987140.1202908182.txt
JVMDG215: Dump Handler has Processed Exception Signal 4.

解决方法：
--cp /t06/orauat/uatdb/9.2.0/jdbc/lib/classes111.zip 到/t06/orauat/uatdb/9.2.0/appsutil/clone/jlib
在clone appsTier的时候也有找不到classes111.zip的报错，
解决方法：
--cp /t06/appltest/testora/iAS/jdbc/lib/classes111.zip 到/t06/appltest/testcomn/clone/bin/../jlib
　　$ perl adcfgclone.pl dbTier   
Enter the APPS password [APPS]:
　　First Creating a new context file for the cloned system.
The program is going to ask you for information about the new system:
　　sh: 1085606 Illegal instruction(coredump)
ERROR: context creation not completed successfully.
Please check /tmp/adcfgclone.err file for errors
　　$ more /tmp/adcfgclone.err   
        stackpointer=2ff20870
JVMXM004: JVM is performing abort shutdown sequence
JVMDG217: Dump Handler is Processing a Signal - Please Wait.
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /u01/orauat/uatdb/9.2.0/appsutil/clone/bin/javacore1085606.1202993517.txt
JVMDG215: Dump Handler has Processed Exception Signal 4.
　　--解决方法：
To implement the solution, please execute the following steps:
　　1. cd $ORACLE_HOME/appsutil/clone/jre
2. mv lib lib.old
3. mv bin bin.old
4. ln -s jre/bin bin
5. ln -s jre/lib lib
6. run the perl adcfgclone.pl dbTier again.
　　 在Clone appsTier的时候也有时候碰到这样的报错，解决方法和以上差不多，具体如下：
　　--解决方法：
To implement the solution, please execute the following steps:
　　1. cd $COMMON_TOP/clone/jre
2. mv lib lib.old
3. mv bin bin.old
4. ln -s jre/bin bin
5. ln -s jre/lib lib
6. run the perl adcfgclone.pl dbTier again.
　　Beginning database tier Apply - Tue May 14 20:57:48 2009
Log file located at /t06/orauat/uatdb/9.2.0/appsutil/log/uat_erpdb/ApplyDBTier_02142057.log
RC-00110: Fatal: Error occurred while relinking of ApplyDBTechStack
　　ERROR while running Apply...
　　 ERROR: Failed to execute /t06/orauat/uatdb/9.2.0/appsutil/clone/bin/adclone.pl
　　 Please check logfile.
　　$tail -n 100 /t06/orauat/uatdb/9.2.0/appsutil/log/uat_erpdb/ApplyDBTier_02142057.log
AutoConfig is exiting with status 1
　　RC-50013: Fatal: Failed to instantiate driver /u01/orauat/uatdb/9.2.0/appsutil/driver/instconf.drv
Raised by oracle.apps.ad.clone.ApplyDBTechStack
　　
StackTrace:
java.lang.Exception: RC-50013: Fatal: Failed to instantiate driver /t06/orauat/uatdb/9.2.0/appsutil/driver/instconf.drv
        at oracle.apps.ad.clone.ApplyDBTechStack.checkInstallDrvErr(ApplyDBTechStack.java:717)
        at oracle.apps.ad.clone.ApplyDBTechStack.runInstallConfigDriver(ApplyDBTechStack.java:622)
        at oracle.apps.ad.clone.ApplyDBTechStack.<init>(ApplyDBTechStack.java:389)
        at oracle.apps.ad.clone.ApplyDBTier.<init>(ApplyDBTier.java:149)
        at java.lang.reflect.Constructor.newInstance(Native Method)
        at oracle.apps.ad.clone.util.CloneProcessor.run(CloneProcessor.java:68)
        at java.lang.Thread.run(Thread.java:513)
　　
[AutoConfig Error Report]
The following report lists errors AutoConfig encountered during each
phase of its execution.  Errors are grouped by directory and phase.
The report format is:
      <filename>  <phase>  <return code where appropriate>
　　  [INSTANTIATE PHASE]
  AutoConfig could not successfully instantiate the following files:
    Directory: /t06/orauat/uatdb/9.2.0/bin
      <file_spec_api>         INSTE8         --<file_spec_api>对AIX而言是个有歧义文件要用引号引起来才能识别，但在CLONE的时候却会因为这个文件的识别问题而发生错误。在做PRECLONE的时候需要删除这种引起歧义的文件。做完PRECLONE之后再删除是没用的。
　　
AutoConfig is exiting with status 1
　　RC-50013: Fatal: Failed to instantiate driver /u01/orauat/uatdb/9.2.0/appsutil/driver/instconf.drv
Raised by oracle.apps.ad.clone.ApplyDBTechStack
　　
StackTrace:
java.lang.Exception: RC-50013: Fatal: Failed to instantiate driver /u01/orauat/uatdb/9.2.0/appsutil/driver/instconf.drv
        at oracle.apps.ad.clone.ApplyDBTechStack.checkInstallDrvErr(ApplyDBTechStack.java:717)
        at oracle.apps.ad.clone.ApplyDBTechStack.runInstallConfigDriver(ApplyDBTechStack.java:622)
        at oracle.apps.ad.clone.ApplyDBTechStack.<init>(ApplyDBTechStack.java:389)
        at oracle.apps.ad.clone.ApplyDBTier.<init>(ApplyDBTier.java:149)
        at java.lang.reflect.Constructor.newInstance(Native Method)
        at oracle.apps.ad.clone.util.CloneProcessor.run(CloneProcessor.java:68)
        at java.lang.Thread.run(Thread.java:513)
　　
　　解决方法：
$cd /T06/orauat/uatdb/9.2.0/appsutil/driver
$ls
adrdbtmpl.drv     instconf.drv      instconf.drv.bak
$ mv instconf.drv instconf.drv.old
$ mv instconf.drv.bak instconf.drv