WebLogic Server10.3.3在RedHat启动报错问题

November 9th, 2011 admin No comments

在RedHat安装WebLogic Server,新疆Domain之后,启动报错。
 
start error log:
 
starting weblogic with Java version:
java version “1.6.0_18″
Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
Java HotSpot(TM) 64-Bit Server VM (build 16.0-b13, mixed mode)
Starting WLS with line:
/home/weblogic/jdk1.6.0_18/bin/java -server   -Xms1024m -Xmx1024m  -XX:MaxPermSize=256m -Dweblogic.Name=AdminServer -Djava.security.policy=/server/weblogic/wlserver_10.3/server/lib/weblogic.policy  -Dweblogic.ProductionModeEnabled=true   -da  -Dplatform.home=/server/weblogic/wlserver_10.3 -Dwls.home=/server/weblogic/wlserver_10.3/server -Dweblogic.home=/server/weblogic/wlserver_10.3/server   -Dweblogic.management.discover=true  -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/server/weblogic/patch_wls1033/profiles/default/sysext_manifest_classpath:/server/weblogic/patch_ocp353/profiles/default/sysext_manifest_classpath  weblogic.Server
<2011-11-9 上午11时20分11秒 CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 16.0-b13 from Sun Microsystems Inc.>
<2011-11-9 上午11时20分27秒 CST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.3.0  Fri Apr 9 00:05:28 PDT 2010 1321401 >
<2011-11-9 上午11时20分28秒 CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<2011-11-9 上午11时20分28秒 CST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<2011-11-9 上午11时20分28秒 CST> <Notice> <Log Management> <BEA-170019> <The server log file /home/xzuser/weblogic/user_projects/domains/xztelant/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.>
<2011-11-9 上午11时20分30秒 CST> <Error> <Security> <BEA-090870> <The realm “myrealm” failed to be loaded: weblogic.security.service.SecurityServiceException: java.lang.ExceptionInInitializerError.
weblogic.security.service.SecurityServiceException: java.lang.ExceptionInInitializerError
        at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:342)
        at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:221)
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1783)
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
        Truncated. see log file for complete stacktrace
Caused By: java.lang.ExceptionInInitializerError
        at com.octetstring.vde.util.guid.GuidGenerator.nextGuidInBytes(GuidGenerator.java:125)
        at com.octetstring.vde.util.guid.Guid.<init>(Guid.java:84)
        at com.octetstring.vde.backend.standard.BackendStandard.add(BackendStandard.java:379)
        at com.octetstring.vde.backend.BackendHandler.add(BackendHandler.java:460)
        at com.octetstring.vde.util.LDIF.importLDIF(LDIF.java:279)
        Truncated. see log file for complete stacktrace
Caused By: java.lang.NullPointerException
        at java.lang.System.arraycopy(Native Method)
        at com.octetstring.vde.util.guid.GuidParamGenerator.generateNodeID(GuidParamGenerator.java:47)
        at com.octetstring.vde.util.guid.GuidStateManager.initializeGUIDParameters(GuidStateManager.java:59)
        at com.octetstring.vde.util.guid.GuidStateManager.<init>(GuidStateManager.java:30)
        at com.octetstring.vde.util.guid.GuidStateManager.<clinit>(GuidStateManager.java:23)
        Truncated. see log file for complete stacktrace
>
<2011-11-9 上午11时20分30秒 CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<2011-11-9 上午11时20分30秒 CST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.security.service.SecurityServiceRuntimeException: [Security:090399]Security Services Unavailable
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:916)
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
        at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
        at weblogic.security.SecurityService.start(SecurityService.java:141)
        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
<2011-11-9 上午11时20分30秒 CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<2011-11-9 上午11时20分30秒 CST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<2011-11-9 上午11时20分30秒 CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
 
起初以为是Domain建的有问题,新建几次之后发现问题依旧。
 
再来看 AdminServer Log 信息:
 
####<2011-11-9 上午11时16分52秒 CST> <Info> <Socket> <Unknown> <AdminServer> <[ACTIVE] ExecuteThread: ‘0′ for queue: ‘weblogic.kernel.Default (self-tuning)’> <<WLS Kernel>> <> <> <1320808612236> <BEA-000406> <PosixSocketMuxer was built on Apr 24 2007 16:05:00>
####<2011-11-9 上午11时16分52秒 CST> <Info> <Socket> <Unknown> <AdminServer> <[ACTIVE] ExecuteThread: ‘0′ for queue: ‘weblogic.kernel.Default (self-tuning)’> <<WLS Kernel>> <> <> <1320808612260> <BEA-000436> <Allocating 4 reader threads.>
####<2011-11-9 上午11时16分52秒 CST> <Info> <Socket> <Unknown> <AdminServer> <[ACTIVE] ExecuteThread: ‘0′ for queue: ‘weblogic.kernel.Default (self-tuning)’> <<WLS Kernel>> <> <> <1320808612262> <BEA-000446> <Native IO Enabled.>
####<2011-11-9 上午11时16分52秒 CST> <Info> <IIOP> <Unknown> <AdminServer> <[ACTIVE] ExecuteThread: ‘0′ for queue: ‘weblogic.kernel.Default (self-tuning)’> <<WLS Kernel>> <> <> <1320808612487> <BEA-002014> <IIOP subsystem enabled.>
####<2011-11-9 上午11时16分53秒 CST> <Info> <Security> <Unknown> <AdminServer> <[ACTIVE] ExecuteThread: ‘0′ for queue: ‘weblogic.kernel.Default (self-tuning)’> <<WLS Kernel>> <> <> <1320808613882> <BEA-000000> <Starting OpenJPA 1.1.1-SNAPSHOT>
####<2011-11-9 上午11时16分53秒 CST> <Info> <Security> <Unknown> <AdminServer> <[ACTIVE] ExecuteThread: ‘0′ for queue: ‘weblogic.kernel.Default (self-tuning)’> <<WLS Kernel>> <> <> <1320808613952> <BEA-000000> <StoreServiceImpl.initJDO - StoreService is initialized with Id = ldap_BEHRdjJXKDRkR3PSHSqhc+DU36k=>
####<2011-11-9 上午11时16分53秒 CST> <Info> <Security> <Unknown> <AdminServer> <[ACTIVE] ExecuteThread: ‘0′ for queue: ‘weblogic.kernel.Default (self-tuning)’> <<WLS Kernel>> <> <> <1320808613998> <BEA-090074> <Initializing Authenticator provider using LDIF template file /home/xzuser/weblogic/user_projects/domains/xztelant/security/DefaultAuthenticatorInit.ldift.>
####<2011-11-9 上午11时16分54秒 CST> <Info> <Security> <Unknown> <AdminServer> <[ACTIVE] ExecuteThread: ‘0′ for queue: ‘weblogic.kernel.Default (self-tuning)’> <<WLS Kernel>> <> <> <1320808614009> <BEA-090511> <The following exception has occurred:
java.lang.ExceptionInInitializerError
 at com.octetstring.vde.util.guid.GuidGenerator.nextGuidInBytes(GuidGenerator.java:125)
 at com.octetstring.vde.util.guid.Guid.<init>(Guid.java:84)
 at com.octetstring.vde.backend.standard.BackendStandard.add(BackendStandard.java:379)
 at com.octetstring.vde.backend.BackendHandler.add(BackendHandler.java:460)
 at com.octetstring.vde.util.LDIF.importLDIF(LDIF.java:279)
 at com.octetstring.vde.util.LDIF.importLDIF(LDIF.java:235)
 at weblogic.security.utils.ProviderUtils.loadFullLDIFTemplate(ProviderUtils.java:739)
 at weblogic.security.utils.ProviderUtils.loadLDIFTemplate(ProviderUtils.java:583)
 at weblogic.security.utils.ProviderUtils.loadLDIFTemplate(ProviderUtils.java:489)
 at weblogic.security.utils.ProviderUtils.loadLDIFAuthenticatorTemplate(ProviderUtils.java:316)
 at weblogic.security.providers.authentication.DefaultAuthenticationProviderImpl.initialize(DefaultAuthenticationProviderImpl.java:128)
 at com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:65)
 at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)
 at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
 at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
 at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
 at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:47)
 at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:300)
 at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:221)
 at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1783)
 at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
 at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
 at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
 at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
 at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
 at weblogic.security.SecurityService.start(SecurityService.java:141)
 at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: java.lang.NullPointerException
 at java.lang.System.arraycopy(Native Method)
 at com.octetstring.vde.util.guid.GuidParamGenerator.generateNodeID(GuidParamGenerator.java:47)
 at com.octetstring.vde.util.guid.GuidStateManager.initializeGUIDParameters(GuidStateManager.java:59)
 at com.octetstring.vde.util.guid.GuidStateManager.<init>(GuidStateManager.java:30)
 at com.octetstring.vde.util.guid.GuidStateManager.<clinit>(GuidStateManager.java:23)
 at com.octetstring.vde.util.guid.GuidGenerator.nextGuidInBytes(GuidGenerator.java:125)
 at com.octetstring.vde.util.guid.Guid.<init>(Guid.java:84)
 at com.octetstring.vde.backend.standard.BackendStandard.add(BackendStandard.java:379)
 at com.octetstring.vde.backend.BackendHandler.add(BackendHandler.java:460)
 at com.octetstring.vde.util.LDIF.importLDIF(LDIF.java:279)
 at com.octetstring.vde.util.LDIF.importLDIF(LDIF.java:235)
 at weblogic.security.utils.ProviderUtils.loadFullLDIFTemplate(ProviderUtils.java:739)
 at weblogic.security.utils.ProviderUtils.loadLDIFTemplate(ProviderUtils.java:583)
 at weblogic.security.utils.ProviderUtils.loadLDIFTemplate(ProviderUtils.java:489)
 at weblogic.security.utils.ProviderUtils.loadLDIFAuthenticatorTemplate(ProviderUtils.java:316)
 at weblogic.security.providers.authentication.DefaultAuthenticationProviderImpl.initialize(DefaultAuthenticationProviderImpl.java:128)
 at com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:65)
 at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)
 at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
 at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
 at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
 at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:47)
 at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:300)
 at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:221)
 at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1783)
 at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
 at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
 at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
 at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
 at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
 at weblogic.security.SecurityService.start(SecurityService.java:141)
 at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
 
从以上日志可以发现,没有AdminServer没有找到主机,这是因为我们在hosts文件没有配置DNS的原因造成的。
 
Solution:
 
Make sure that the “hosts” file (see location below per OS) includes the DNS names that match the servers configuration.
On Linux: /etc/hosts
On Windows: %SystemRoot%\system32\drivers\etc
On Windows 64-bit: %SystemRoot%\sysWOW64\drivers\etc
On Apple Macintosh: /private/etc/hosts
 
问题解决!
 

Reference for Troubleshooting WebLogic Server Issues (WLS Support Patterns) [ID 1189504.1]

November 1st, 2011 admin No comments

In this Document
Purpose
Reference for
Troubleshooting WebLogic Server Issues (WLS Support Patterns)

Master Notes
jRockit Support
Patterns

Web Services Support
Pattern

Workshop Support Pattern
WebLogic Tuxedo Connector Support Pattern
Core Server/JVM/Memory Issues Support Patterns
Oracle/JDBC-Related Support Patterns
Security-Related Support Patterns
Performance-Related Articles
Miscellaneous Support Patterns


Applies to:

Oracle Weblogic Server - Version: 6.1 and
later [Release: and later ]
Information in this document applies to
any platform.

Purpose

This note contains a reference
to all the notes that are related to troubleshooting the various components of
WebLogic Server (e.g., JDBC, Security, Core, Clustering, etc).

Reference for Troubleshooting WebLogic Server
Issues (WLS Support Patterns)

Oracle
WebLogic Server Product Information Center
> Note 1054263.1

Master Notes

  • Master Note for Troubleshooting WebLogic - Enterprise JavaBeans (EJBs)
    Issues Note
    1143025.1
  • Master Note for Oracle WebLogic Server Core Server/JVM/Memory Issues Support
    Patterns Note
    760172.1
  • Master Note on Oracle WebLogic Server Clustering and Load Balancing Support
    Patterns Note
    760941.1
  • Master Note on Oracle WebLogic Server JTA/JTS/Transactions Support Patterns
    Note
    761116.1
  • Master Note on Oracle WebLogic Server JDBC/Database/Drivers Support Patterns
    Note
    761097.1
  • Master Note on Oracle WebLogic Server Security and Authentication Support
    Patterns Note
    761136.1
  • Master Note on Oracle WebLogic Server Deployment Support Patterns Note
    761035.1
  • Master Note on Oracle WebLogic Server Proxy Plug-In Support Patterns Note
    761125.1
  • Master Note on Oracle WebLogic Server Node Manager Support Patterns Note
    761121.1
  • Master Note on Oracle WebLogic Server JSP and Servlet Support Patterns Note
    761112.1
  • Master Note on Oracle WebLogic Server JCA and WTC Connectors Support
    Patterns Note
    761046.1

jRockit Support Patterns

  • The Undocumented Oracle JRockit Troubleshooting Tips Note
    1137024.1
  • Oracle JRockit and Memory Consumption - Memory Leaks In Java Heap Note
    1137239.1
  • Where to Download JRockit Full Installers, Patch Sets and One-off Patches Note
    1215533.1
  • Oracle JRockit and Wrong Computation - Undocumented Troubleshooting Tip Note
    1265037.1

Web Services Support Pattern

  • Oracle WebLogic Server Web Services Support Patterns Note
    761142.1

Workshop Support Pattern

WebLogic Tuxedo Connector Support Pattern

  • WebLogic Tuxedo Connector Leads to Out of Memory Errors Support Pattern Note
    1135105.1

Core Server/JVM/Memory Issues Support
Patterns

  • Oracle WebLogic Server Core Server/JVM/Memory Issues Support Patterns -
    Investigating Out of Memory/Memory Leak Problems Note
    877172.1
  • Oracle WebLogic Server Core Server/JVM/Memory Issues Support Patterns -
    Unexpected High CPU Usage with WLS Note
    779349.1
  • Oracle WebLogic Server Core Server/JVM/Memory Issues Support Patterns -
    Generic Server Hang Note
    1264286.1
  • OutOfMemoryError and Memory Leak Debugging Methodology Note
    1054263.1
  • Unexpected High CPU Usage with WLS Note
    779349.1
  • Binary Core File Analysis WebLogic Server Support Pattern Note
    779344.1
  • WebLogic Server Hang Application Deadlock Support Pattern Note
    1134260.1
  • WebLogic Server (6.1 to 8.1) JDBC Hang Support Pattern Note
    1135278.1

Oracle/JDBC-Related Support Patterns

  • Oracle and RAC (Real Application Clusters) Configuration and Testing
    WebLogic Server Support Pattern Note
    1148726.1
  • Investigating “ORA-01000: maximum open cursors exceeded” WebLogic Server
    Support Pattern Note
    1141024.1
  • CLOB/BLOB Data Type Handling Issues WebLogic Server Support Pattern Note
    1332275.1
  • Investigating JDBC MultiPool Issues in WebLogic Server Support Pattern Note
    1148756.1
  • Investigating JDBC Problems with WebLogic Server (WLS) Support Pattern Note
    1135198.1

Security-Related Support Patterns

  • Understanding WebLogic Security Providers Support Pattern Note
    779219.1
  • WebLogic Server Plug-Ins and SSL Support Pattern Note
    780026.1
  • WebLogic Server (WLS) SSL Basic Constraints Support Pattern Note
    1084556.1
  • Connecting to LDAP Server Over SSL From WebLogic Server Support Pattern Note
    1086628.1
  • Investigating Transaction Problems Support Pattern Note
    779556.1
  • Kerberos and SPNEGO Configuration Issues Support Pattern Note
    779272.1
  • Understanding and Investigating SSL Issues Support Pattern Note
    1078957.1
  • Investigating Domain Trust Issues Support Pattern Note
    1332288.1
  • SSL Configuration and Node Manager Support Pattern Note
    1088993.1
  • HTTP Session Replication Failures Support Pattern Note
    779350.1
  • Re-Encrypting Domain Passwords Support Pattern Note
    1087296.1
  • Troubleshooting Web Services and SSL Issues (Transport-level Security)
    Support Pattern Note
    1086572.1
  • Authentication Errors Starting WLS Support Pattern Note
    1087194.1
  • Understanding LDAP Group Membership Search (Static vs Dynamic) Support
    Pattern Note
    1082916.1
  • Troubleshooting LDAP Issues Support Pattern Note
    1077534.1

Performance-Related Articles

  • Weblogic Slow Start Up Time and Managed Server Cannot Establish Connection
    With Admin Server on Linux And Solaris Systems Intermittently Note
    1052950.1
  • Weblogic: Performance Problems After Migrating From WLS 8.1 To WLS 10.3 And
    Moving To SUN Sparc T5240 With CMT Chips Note
    860459.1
  • WLS 10.3.2: Weblogic Pre-Complied JSP performance issue Note
    1130930.1
  • When Using Hibernate with WebLogic Server (WLS), Performance Degradation
    Along with Stuck Threads And Too Many Files Errors Are Seen Note
    1094284.1
  • How to make the WebLogic Workshop performance better? Note
    1068692.1
  • WebLogic 10.3: Stuck Thread and Performance Problem On Solaris With SUN JDK
    Note
    1103719.1

Miscellaneous Support Patterns

  • WebLogic Product related Support Patterns Note
    970768.1
  • General Diagnostic Process for Problems with WebLogic Server (WLS) Proxy
    Plug-in Support Pattern Note
    780007.1
  • WebLogic Server (WLS) EJB RMI Server Hang Support Pattern Note
    1134285.1
  • Troubleshooting J2CA Connection Pooling Issues in WebLogic Server Support
    Pattern Note
    1135134.1
  • Debugging Recompilation of Precompiled JSPs in WebLogic Server (WLS) Support
    Pattern Note
    1101942.1
  • Multicast Errors Support Pattern Note
    1092037.1
  • Troubleshooting Pending JMS Messages Support Pattern Note
    1204064.1

显示相关信息
相关内容


产品


  • Middleware > Application Servers > Weblogic Server > Oracle
    Weblogic Server

关键字


DEBUGGING; DIAGNOSTIC; HANGING; LEAK; MEMORY LEAK; PERFORMANCE
PROBLEMS; TROUBLESHOOT; WEBLOGIC

错误


ORA-1000

Categories: Weblogic Tags: , ,

Oracle 10.2.0.4在Windows2008 x64上启动 Database Control时出错

October 28th, 2011 admin No comments

创建数据库时,提供Database control出错,

Ok,没问题,一会儿重建,但是重建过程中报错如下:

C:\Users\Administrator>emca -config dbcontrol db -repos create

EMCA 开始于 2011-10-28 18:47:34
EM Configuration Assistant, 10.2.0.1.0 正式版
版权所有 (c) 2003, 2005, Oracle。保留所有权利。

输入以下信息:
数据库 SID: xzorcl
监听程序端口号: 1521
SYS 用户的口令:
DBSNMP 用户的口令:
SYSMAN 用户的口令:
SYSMAN 用户的口令: 通知的电子邮件地址 (可选):
通知的发件 (SMTP) 服务器 (可选):
—————————————————————–

已指定以下设置

数据库 ORACLE_HOME ……………. D:\oracle\product\10.2.0\db_1

数据库主机名 ……………. WIN-KJ3JMIK5JDJ
监听程序端口号 ……………. 1521
数据库 SID ……………. xzorcl
通知的电子邮件地址 ……………
通知的发件 (SMTP) 服务器 ……………

—————————————————————–
是否继续? [是(Y)/否(N)]: y
2011-10-28 18:48:12 oracle.sysman.emcp.EMConfig perform
信息: 正在将此操作记录到 D:\oracle\product\10.2.0\db_1\cfgtoollogs\emca\xzorcl\e
mca_2011-10-28_06-47-34-下午.log。
2011-10-28 18:48:21 oracle.sysman.emcp.EMReposConfig createRepository
信息: 正在创建 EM 资料档案库 (此操作可能需要一段时间)…
2011-10-28 18:50:49 oracle.sysman.emcp.EMReposConfig invoke
信息: 已成功创建资料档案库
2011-10-28 18:51:00 oracle.sysman.emcp.util.DBControlUtil secureDBConsole
信息: 正在保护 Database Control (此操作可能需要一段时间)…
2011-10-28 18:51:24 oracle.sysman.emcp.util.DBControlUtil secureDBConsole
信息: 已成功保护 Database Control。
2011-10-28 18:51:24 oracle.sysman.emcp.util.DBControlUtil startOMS
信息: 正在启动 Database Control (此操作可能需要一段时间)…
2011-10-28 19:01:25 oracle.sysman.emcp.EMConfig perform
严重: 启动 Database Control 时出错
有关详细资料, 请参阅 D:\oracle\product\10.2.0\db_1\cfgtoollogs\emca\xzorcl\emca_
2011-10-28_06-47-34-下午.log 中的日志文件。
java.io.IOException: 句柄无效。
        at java.io.FileInputStream.close0(Native Method)
        at java.io.FileInputStream.close(FileInputStream.java:245)
        at sun.nio.cs.StreamDecoder$CharsetSD.implClose(StreamDecoder.java:505)
        at sun.nio.cs.StreamDecoder.close(StreamDecoder.java:198)
        at java.io.InputStreamReader.close(InputStreamReader.java:187)
        at java.io.BufferedReader.close(BufferedReader.java:502)
        at oracle.sysman.assistants.util.sqlEngine.SQLEngine$ErrorStreamReader.r
un(SQLEngine.java:2406)
        at java.lang.Thread.run(Thread.java:595)
无法完成配置。 有关详细资料, 请参阅 D:\oracle\product\10.2.0\db_1\cfgtoollogs\em
ca\xzorcl\emca_2011-10-28_06-47-34-下午.log 中的日志文件。

 

经查询,此问题是由于enterprise manager database
control组件的跟CA证书授权过期造成的,其证书到期日为2010年12月31日,2011年安装此版本数据库都会出现这个问题,官方的解决方案是打Patch
8350262

 

单实例数据库应用此patch的方法如下:

1、安装或者升级数据库到10.2.0.4过程中忽略此错误继续安装,数据库的创建不受影响。
2、使用opatch把此补丁应用到oracle安装
设置ORACLE_HOME和ORACLE_SID系统环境变量,将%ORACLE_HOME%\opatch加入PATH环境变量,将patch
8350262解压缩,打开cmd窗口,进入解压缩后目录,执行
cmd>opatch
apply

得到如下信息输出:

D:\8350262>D:\oracle\product\10.2.0\db_1\OPatch\opatch apply
Invoking OPatch 10.2.0.4.2

Oracle Interim Patch Installer version 10.2.0.4.2
Copyright (c) 2007, Oracle Corporation.  All rights reserved.

Oracle 主目录       : D:\oracle\product\10.2.0\db_1
主产品清单: C:\Program Files\Oracle\Inventory
   从           : n/a
OPatch 版本    : 10.2.0.4.2
OUI 版本       : 10.2.0.4.0
OUI 位置      : D:\oracle\product\10.2.0\db_1\oui
日志文件位置 : D:\oracle\product\10.2.0\db_1\cfgtoollogs\opatch\opatch2011-10-28
_19-26-38下午.log

ApplySession 将中间补丁程序 ‘8350262′ 应用到 OH ‘D:\oracle\product\10.2.0\db_1′

Running prerequisite checks…

OPatch 从产品清单中检测到非集群 Oracle 主目录, 将仅对本地系统打补丁。

为 Oracle 主目录备份文件和产品清单 (不是用于自动回退)
正在备份受补丁程序 ‘8350262′ 影响的文件以用于恢复。此操作将需要一些时间…

********************************************************************************
***********
Oracle Configuration Manager is installed but not configured.  OCM enables Oracl
e to
provide superior, proactive support for our customers. Oracle strongly recommend
s customers
configure OCM. To complete the configuration of OCM, refer to the OCM Installati
on and
Administration Guide (http://www.oracle.com/technology/documentation/ocm.html).
********************************************************************************
***********

正在备份受补丁程序 ‘8350262′ 影响的文件以用于回退。此操作将需要一些时间…

正在为组件 oracle.sysman.agent.core, 10.2.0.4.0a 打补丁…
用 “\sysman\jlib\emCORE.jar\oracle\sysman\eml\sec\fsc\FSWalletUtil.class” 更新 j
ar 文件 “D:\oracle\product\10.2.0\db_1\sysman\jlib\emCORE.jar”
用 “\sysman\jlib\emCORE.jar\oracle\sysman\eml\sec\rep\RepWalletUtil.class” 更新
jar 文件 “D:\oracle\product\10.2.0\db_1\sysman\jlib\emCORE.jar”
用 “\sysman\jlib\emCORE.jar\oracle\sysman\eml\sec\util\RootCert.class” 更新 jar
文件 “D:\oracle\product\10.2.0\db_1\sysman\jlib\emCORE.jar”
用 “\sysman\jlib\emCORE.jar\oracle\sysman\eml\sec\util\SecConstants.class” 更新
jar 文件 “D:\oracle\product\10.2.0\db_1\sysman\jlib\emCORE.jar”
用 “\sysman\jlib\emd_java.jar\oracle\sysman\eml\sec\fsc\FSWalletUtil.class” 更新
 jar 文件 “D:\oracle\product\10.2.0\db_1\sysman\jlib\emd_java.jar”
用 “\sysman\jlib\emd_java.jar\oracle\sysman\eml\sec\rep\RepWalletUtil.class” 更
新 jar 文件 “D:\oracle\product\10.2.0\db_1\sysman\jlib\emd_java.jar”
用 “\sysman\jlib\emd_java.jar\oracle\sysman\eml\sec\util\RootCert.class” 更新 ja
r 文件 “D:\oracle\product\10.2.0\db_1\sysman\jlib\emd_java.jar”
用 “\sysman\jlib\emd_java.jar\oracle\sysman\eml\sec\util\SecConstants.class” 更
新 jar 文件 “D:\oracle\product\10.2.0\db_1\sysman\jlib\emd_java.jar”
ApplySession 将中间补丁程序 ‘8350262′ 添加到产品清单

Verifying the update…
Inventory check OK: Patch ID 8350262 is registered in Oracle Home inventory with
 proper meta-data.
Files check OK: Files from Patch ID 8350262 are present in Oracle Home.
——————————————————————————–

The following warnings have occurred during OPatch execution:
1) OUI-67294:
********************************************************************************
***********
Oracle Configuration Manager is installed but not configured.  OCM enables Oracl
e to
provide superior, proactive support for our customers. Oracle strongly recommend
s customers
configure OCM. To complete the configuration of OCM, refer to the OCM Installati
on and
Administration Guide (http://www.oracle.com/technology/documentation/ocm.html).
********************************************************************************
***********

——————————————————————————–

OPatch 会话已完成, 但出现警告。

OPatch completed with warnings.

D:\8350262>

完成后检查%ORACLE_HOME%\cfgtoollogs\opatch\目录下生成的日志文件确认安装patch是否成功。
3、应用patch成功后,重新配置em
dbconsole
cmd>emctl secure dbconsole
-reset

输出:

Microsoft Windows [版本 6.1.7601]
版权所有 (c) 2009 Microsoft Corporation。保留所有权利。

C:\Users\Administrator>emctl secure dbconsole -reset
Environment variable ORACLE_SID not defined. Please define it.

C:\Users\Administrator>set ORACLE_SID=xzorcl

C:\Users\Administrator>emctl secure dbconsole -reset
Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
Copyright (c) 1996, 2007 Oracle Corporation.  All rights reserved.
https://WIN-KJ3JMIK5JDJ:1158/em/console/aboutApplication
Enter Enterprise Manager Root Password :
********
DBCONSOLE already stopped…   Done.
Agent is already stopped…   Done.
Securing dbconsole…   Started.
Checking Repository…   Done.
Checking Em Key…   Done.
Checking Repository for an existing Enterprise Manager Root Key…
WARNING! An Enterprise Manager Root Key already exists in
the Repository. This operation will replace your Enterprise
Manager Root Key.
All existing Agents that use HTTPS will need to be
reconfigured if you proceed. Do you wish to continue and
overwrite your Root Key
(Y/N) ?
Y
Are you sure ? Reset of the Enterprise Manager Root Key
will mean that you will need to reconfigure each Agent
that is associated with this OMS before they will be
able to upload any data to it. Monitoring of Targets
associated with these Agents will be unavailable until
after they are reconfigured.
(Y/N) ?
Y
Generating Enterprise Manager Root Key (this takes a minute)…   Done.
Fetching Root Certificate from the Repository…   Done.
Updating HTTPS port in emoms.properties file…   Done.
Generating Java Keystore…认证已添加至keystore中
认证回复已安装在 keystore中
   Done.
Securing OMS …   Done.
Generating Oracle Wallet Password for Agent….   Done.
Generating wallet for Agent …    Done.
Copying the wallet for agent use…    Done.
Storing agent key in repository…   Done.
Storing agent key for agent …   Done.
Configuring Agent…
Configuring Agent for HTTPS in DBCONSOLE mode…   Done.
EMD_URL set in D:\oracle\product\10.2.0\db_1/WIN-KJ3JMIK5JDJ_xzorcl/sysman/confi
g/emd.properties
   Done.
Configuring Key store..   Done.
Securing dbconsole…   Sucessful.

C:\Users\Administrator>

根据提示输入管理员密码,然后会有两次确认请求,两次都是输入大写的Y

4、重新启动dbconsole
cmd>emctl
start dbconsole

输出:
 
C:\Users\Administrator>emctl start dbconsole
Environment variable ORACLE_SID not defined. Please define it.
C:\Users\Administrator>set ORACLE_SID=xzorcl
C:\Users\Administrator>emctl start dbconsole
Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
Copyright (c) 1996, 2007 Oracle Corporation.  All rights reserved.
https://WIN-KJ3JMIK5JDJ:1158/em/console/aboutApplication
Starting Oracle Enterprise Manager 10g Database Control …OracleDBConsolexzorcl
 服务正在启动 …………….
OracleDBConsolexzorcl 服务已经启动成功。
 
 
至此,DBConsole服务顺利启动成功。
Categories: Oracle Tags: ,