科技行者

行者学院 转型私董会 科技行者专题报道 网红大战科技行者

知识库

知识库 安全导航

至顶网软件频道metalink,P4安装oracle8.1.X的解决方法

metalink,P4安装oracle8.1.X的解决方法

  • 扫一扫
    分享文章到微信

  • 扫一扫
    关注官方公众号
    至顶头条

  作者:liping      第一:   Problem statement:   INSTALLER FAILS WHEN RUNNING ON NEW PENTIUM 4 (IV) PROCESSORS      *** 11/20/00 0

作者:中国IT实验室 来源:中国IT实验室 2007年10月4日

关键字: Metalink 新手入门 数据库 ORACLE

  • 评论
  • 分享微博
  • 分享邮件

  作者:liping
  
  第一:
  Problem statement:
  INSTALLER FAILS WHEN RUNNING ON NEW PENTIUM 4 (IV) PROCESSORS
  
  *** 11/20/00 07:18 am ***
  not yet been released to the market. They will be soon. Some awareness with
  the OUI team I believe is already in progress to address this issue.
  =====================
  PROBLEM:
  I am not sure how many platforms this will affect, but I am lead to believe
  that at a minimum, Windows NT and NetWare platforms are affected. (Platforms
  that I am aware of that run on Intel CPUs - Windows NT, Windows95, Windows98,
  Windows ME, Windows 2000, NetWare, Linux, SCO UnixWare, Data General, IBM
  NumaQ - maybe).
  .
  When installing Oracle Products with the Oracle Universal Installer on
  machines that use the Sun JRE and Symmantec JIT, the installer fails, this
  impacts Intel Pentium 4 (IV) CPU platforms as far as I know.
  .
  I have not been able to reproduce this problem because the machines are not
  generally available, however, Intel has been able to. Intel has been able to
  reproduce this problem and contacted Oracle regarding the issue.
  .
  A url on an Intel web site that details the problem is as follows:
  .
  CPUID detection for Intel?Pentium?4 processor system:
  Intel has identified that applications which use the Symantec Just in Time
  Compiler library file ("symcjit.dll" for Microsoft Windows* operating system
  and "symc_jlt.nlm" for Novell Netware* 5.1) may not run properly on Pentium?4
  processor systems because the library does not properly identify the
  processor. The failure typically is that the affected application simply
  terminates. Under Microsoft Windows*, the properties of the DLL are:
  .
  "Symantec Java! JustInTime Compiler Version 3.10.107 for JDK 1.2 Copyright (C)
  will also not work. To confirm the version you are using, select the DLL,
  right click on the selected DLL and select Properties, and then the Version
  tab. Intel encourages all Software developers to do the following immediately:
  .
  .
  Check if your application(s) uses the Symantec Just in Time Library file
  Request an updated library file from your provider
  
  Test your application with the new library file on Pentium?4 processor system
  .
  Ensure you have plans in place to provide application updates and address
  customer concerns
  .
  This will be a huge impact to support. I am not sure how often this CPUID
  detection is performed with our software but apparently it is done at
  installation time.
  =========================
  DIAGNOSTIC ANALYSIS:
  None really, I don't have a machine yet to test this on.
  .
  =========================
  WORKAROUND:
  Some kind of workaround I think exists if the install directory is copied from
  the CD and if a replacement dll is put into place. Not sure of this. A newer
  version of the installer needs to be released with a functional JIT dll from
  Symantec.
  .
  =========================
  RELATED BUGS:
  .
  NA.
  =========================
  REPRODUCIBILITY:
  .
  I believe that Intel has reproduced this with Oracle on NetWare 8.1.6 and
  Oracle on NT 8.1.6.
  =========================
  TESTCASE:
  Install Oracle 8.1.6 for Windows NT on an Intel Pentium IV machine.
  .
  ========================
  STACK TRACE:
  .
  NA.
  =========================
  IMPACT DATE: I am not sure of the date that the Pentium 4 (IV) cpus will
  begin shipping but I believe that it will be very soon.
  .
  *** 11/20/00 08:06 pm *** (CHG: Asg->NEW OWNER)
  *** 11/21/00 11:20 am *** (CHG: Sta->11)
  *** 11/28/00 01:58 pm *** (CHG: Sta->40)
  *** 11/28/00 01:58 pm ***
  *** 12/04/00 03:47 pm ***
  *** 12/18/00 10:37 am ***
  Additional information:
  Not only will OUI be affected by this bug, most of the post-install
  configuration tools will also be affected. Running these tools with "-nojit"
  specified will avoid the hang, but it is not simple to specify "-nojit" for
  some of the products.
  WORKAROUND:
  To avoid the hang in the installation itself, do the following:
  > > a. Copy the install directory from the CD to the hard disk say, e:\temp.
  > > b. Open oraparam.ini and make the following modifications (Assuming CD
  drive is f:)
  * Change the "SOURCE=" line to use the full path to the CD instead of a
  relative path. (i.e. SOURCE=f:/stage/products.jar)
  * Change the "JRE_LOCATION" line to use the full path to the CD instead of a
  relative path. (i.e.
  JRE_LOCATION=f:/stage/Components/oracle/swd/jre/1.1.7/1/DataFiles/Expanded)
  * Change the "OUI_LOCATION" line to use the full path to the CD instead of a
  relative path. (i.e.
  OUI_LOCATION=f:/stage/Components/oracle/swd/oui/1.6.0.9.0/1/DataFiles/Expanded
  * Change the "JRE_MEMORY_OPTIONS" line to add "-nojit" as the first argument.
  (i.e. JRE_MEMORY_OPTIONS=-nojit -ms16m -mx32m)
   ^^^^^^
  * Other entries should remain the same
  .
  c. Launch setup.exe from the temporary location on your hard drive (i.e.
  e:\temp\install\win32\setup.exe). This will use the modified oraparam.ini and
  pick up the information from the CD since the absolute locations are
  specified.
  .
  Choose a Custom install and choose not to create a database during the
  install. This way, the Database Configuration Assistant will not be launched
  during installation.
  The Net8 Configuration Assistant will still be launched, and there is no way
  to suppress it. You will need to kill the Net8 Configuration Assistant if it
  hangs due to the bug. The installation still will have been successful, and
  you can run the DBCA and NetCA after installation.
  To kill NetCA if it hangs during installation:
  In the "Configuration Tools" window, highlight the "Net8 Configuration
  Assistant" and click "Stop". If that does not work, look for the most recent
  JRE process using the Task Manager, and kill it manually. NOTE: the OUI
  itself will also have a jre process. Be sure to kill the one with the most
  recent date, which should be the jre process being used for Net8CA, not the
  one for OUI itself.
  After killing the configuration tools and continuing through the installation
  to the "End of Installation" screen, you should modify the configuration tools
  to use "-nojit", then call the appropriate tools from the Start Menu.
  For each of the following files in the ORACLE_HOME:
  assistants\dbca\dbassist.cl
  assistants\dbma\dbmig.cl
  assistants\ifa\ifa.cl
  bin\owm.cl
  ldap\oidamdin\oidadmin.cl
  network\tools\netasst.cl
  network\tools\netca.cl
  owm\install\instowm.cl
  .
  Edit the contents of the file to add "-nojit" as shown below:
  Command=("C:\Program Files\Oracle\jre\1.1.7\BIN\JREW" -nojit -classpath ....
   this is the only thing you need to add --> ^^^^^^
  .
  Then, launch the necessary tools, like Net8CA and DBCA from the Start Menu.
  *** 01/04/01 07:33 pm *** (CHG: Sta->11)
  *** 01/04/01 07:33 pm ***
  Base bug closed with status 80.
  Re-openi

查看本文来源

    • 评论
    • 分享微博
    • 分享邮件
    邮件订阅

    如果您非常迫切的想了解IT领域最新产品与技术信息,那么订阅至顶网技术邮件将是您的最佳途径之一。

    重磅专题
    往期文章
    最新文章