Weblogic Server backup

Have been facing issues with starting of WLS and Managed servers etc. The install went fine and set up worked for few weeks and due to server issues like not shutdown gracefully, issues started with WLS servers not starting up properly etc.
So want to take a back of known good state. Please let me know which are the important directories to take backup and which ones can be deleted in case of issues. So we don't have to re-install servers.

Experts, need your input. What are the directories to backup for WLS and managed server- so we don't have to re-install

Similar Messages

Problem getting started weblogic server (for BI Publisher)

Hello,
I am trying to run services BI publisher
But I can't because I have the following error:
SVR_GRP =
JAVA Memory arguments: -Xms256m -Xmx1024m
WLS Start Mode=Production
CLASSPATH=C:\BI11\ORACLE~1\modules\oracle.jdbc_11.1.1\ojdbc6dms.jar;C:\BI11\Oracle_BI1\bifoundation\jdbc\jdk16\bijdbc.jar;;C:\BI11\patch_wls1035\profiles\defaul
t\sys_manifest_classpath\weblogic_patch.jar;C:\BI11\JROCKI~1.2-4\lib\tools.jar;C:\BI11\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\BI11\WLSERV~1.3\server\lib\weblo
gic.jar;C:\BI11\modules\features\weblogic.server.modules_10.3.5.0.jar;C:\BI11\WLSERV~1.3\server\lib\webservices.jar;C:\BI11\modules\ORGAPA~1.1/lib/ant-all.jar;C
:\BI11\modules\NETSFA~1.0_1/lib/ant-contrib.jar;C:\BI11\wlserver_10.3\server\lib\weblogic.jar;C:\BI11\oracle_common\modules\oracle.dms_11.1.1\dms.jar;C:\BI11\or
acle_common\modules\oracle.jmx_11.1.1\jmxframework.jar;C:\BI11\oracle_common\modules\oracle.jmx_11.1.1\jmxspi.jar;C:\BI11\oracle_common\modules\oracle.odl_11.1.
1\ojdl.jar;C:\BI11\ORACLE~1\soa\modules\commons-cli-1.1.jar;C:\BI11\ORACLE~1\soa\modules\oracle.soa.mgmt_11.1.1\soa-infra-mgmt.jar;C:\BI11\ORACLE~1\modules\orac
le.jrf_11.1.1\jrf.jar;C:\BI11\WLSERV~1.3\common\derby\lib\derbyclient.jar;C:\BI11\WLSERV~1.3\server\lib\xqrl.jar
PATH=C:\BI11\patch_wls1035\profiles\default\native;C:\BI11\WLSERV~1.3\server\native\win\32;C:\BI11\WLSERV~1.3\server\bin;C:\BI11\modules\ORGAPA~1.1\bin;C:\BI11\
JROCKI~1.2-4\jre\bin;C:\BI11\JROCKI~1.2-4\bin;C:\oracle11g\dbhome\bin;C:\;C:;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\VAIO;C:\Program Files\Ja
va\jre6\bin;;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\E900\system\bin32;C:\E900\DEMO\bin32;C:\BI11\Oracle_BI1\products\Essbase\EssbaseServer\bin;
C:\BI11\Oracle_BI1\bin;C:\BI11\Oracle_BI1\opmn\bin;C:\BI11\Oracle_BI1\opmn\lib;C:\BI11\Oracle_BI1\perl\bin;C:\BI11\WLSERV~1.3\server\native\win\32\oci920_8
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Oracle JRockit(R) (build R28.1.3-11-141760-1.6.0_24-20110301-1429-windows-ia32,
compiled mode)
Starting WLS with line:
C:\BI11\JROCKI~1.2-4\bin\java -jrockit -Xms256m -Xmx1024m -Dweblogic.Name=AdminServer -Djava.security.policy=C:\BI11\WLSERV~1.3\server\lib\weblogic.policy -D
weblogic.ProductionModeEnabled=true -Doracle.home=C:\BI11\Oracle_BI1 -da -Dplatform.home=C:\BI11\WLSERV~1.3 -Dwls.home=C:\BI11\WLSERV~1.3\server -Dweblogic.hom
e=C:\BI11\WLSERV~1.3\server -Dcommon.components.home=C:\BI11\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk
14Logger -Ddomain.home=C:\BI11\USER_P~1\domains\BIFOUN~1 -Djrockit.optfile=C:\BI11\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config
.dir=C:\BI11\USER_P~1\domains\BIFOUN~1\config\FMWCON~1\servers\AdminServer -Doracle.domain.config.dir=C:\BI11\USER_P~1\domains\BIFOUN~1\config\FMWCON~1 -Digf.a
risidbeans.carmlloc=C:\BI11\USER_P~1\domains\BIFOUN~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\BI11\USER_P~1\domains\BIFOUN~1\config\FMWCON~1\arisidprov
ider -Doracle.security.jps.config=C:\BI11\USER_P~1\domains\BIFOUN~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=C:\BI11\USER_P~1\domains\BIFOUN~1\
servers\AdminServer\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=C:\BI11\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\BI11\ORACLE~1
\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dbi.oracle.home=C:\BI11\Oracle_BI1
-DEPM_ORACLE_HOME=C:\BI11\Oracle_BI1 -Dweblogic.MaxMessageSize=50000000 -DEPM_ORACLE_HOME=C:\BI11\Oracle_BI1 -DHYPERION_HOME=C:\BI11\Oracle_BI1 -DEPM_ORACLE_IN
STANCE=novalue -Dhyperion.home=C:\BI11\Oracle_BI1 -DEPM_REG_PROPERTIES_PATH=C:\BI11\USER_P~1\domains\BIFOUN~1\config\fmwconfig -Depm.useApplicationContextId=fal
se -Doracle.biee.search.bisearchproperties=C:\BI11\Oracle_BI1\bifoundation\jee\BISearchConfig.properties -Dweblogic.management.clearTextCredentialAccessEnabled=
true -Doracle.notification.filewatching.interval=2000 -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.security.SSL.enableJSSE=true -Dfile.enc
oding=utf-8 -Doracle.ecsf.security.service=oracle.biee.search.security.BISearchSecurityService -Doracle.ecsf.configuration.class=oracle.biee.search.services.BIS
earchServiceConfiguration -Dxdo.server.config.dir=C:\BI11\user_projects\domains\bifoundation_domain\config\bipublisher -DXDO_FONT_DIR=C:\BI11\Oracle_BI1\common\
fonts -Dem.oracle.home=C:\BI11\oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dw
lw.logErrorsToConsole=false -Dweblogic.ext.dirs=C:\BI11\patch_wls1035\profiles\default\sysext_manifest_classpath weblogic.Server
[WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
<Apr 10, 2012 3:07:11 PM CEST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable thi
s check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Apr 10, 2012 3:07:11 PM CEST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disabl
e this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true><Apr 10, 2012 3:07:12 PM CEST> <Info> <WebLogicServer> <BEA-000377> <Starting We
bLogic Server with Oracle JRockit(R) Version R28.1.3-11-141760-1.6.0_24-20110301-1429-windows-ia32 from Oracle Corporation>
<Apr 10, 2012 3:07:12 PM CEST> <Info> <Management> <BEA-141107> <Version: Weblogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<Apr 10, 2012 3:07:14 PM CEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Apr 10, 2012 3:07:14 PM CEST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Apr 10, 2012 3:07:15 PM CEST> <Notice> <Log Management> <BEA-170019> <The server log file C:\BI11\user_projects\domains\bifoundation_domain\servers\AdminServer
\logs\AdminServer.log is opened. All server side log events will be written to this file.>
Apr 10, 2012 3:07:23 PM oracle.security.jps.internal.igf.ovd.OvdIGFServiceProvider pushLdapNamesTolibOvd
SEVERE: JPS-02592
<Apr 10, 2012 3:07:23 PM CEST> <Error> <Security> <BEA-090892> <The loading of OPSS java security policy provider failed due to exception, see the exception sta
ck trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Er
ror message: JPS-02592: Failed to push ldap config data to libOvd for service instance "idstore.ldap" in JPS context "default", cause: org.xml.sax.SAXParseExcep
tion: <Line 2, Column 1>: XML-20108: (Fatal Error) Start of root element expected.>
<Apr 10, 2012 3:07:23 PM CEST> <Critical> <WebLogicServer> <BEA-000386> <Serversubsystem failed. Reason: weblogic.security.SecurityInitializationException: The
loading of OPSS java security policy provider failed due to exception, see theexception stack trace or the server log file for root cause. If still see no obv
ious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-02592: Failed to push ldap config data to libOvd f
or service instance "idstore.ldap" in JPS context "default", cause: org.xml.sax.
SAXParseException: <Line 2, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message:JPS-02592: Failed to push ldap config data to libOvd for service instance "idsto
re.ldap" in JPS context "default", cause: org.xml.sax.SAXParseException: <Line 2, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1398)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.JpsRuntimeException: JPS-02592: Failed to push ldap config data to libOvd for service instance "idstore.ldap" in JPS context "def
ault", cause: org.xml.sax.SAXParseException: <Line 2, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:167)
at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:369)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
Truncated. see log file for complete stacktraceCaused By: oracle.security.jps.JpsException: JPS-02592: Failed to push ldap conf
ig data to libOvd for service instance "idstore.ldap" in JPS context "default",cause: org.xml.sax.SAXParseException: <Line 2, Column 1>: XML-20108: (Fatal Erro
r) Start of root element expected.
at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPDPService(PolicyUtil.java:2855)
at oracle.security.jps.internal.policystore.PolicyUtil.getPDPService(PolicyUtil.java:3099)
at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:164)
at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:369)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.service.idstore.IdentityStoreException: JPS-02592: Failed to push ldap config data to libOvd for service instance "idstore.ldap"
in JPS context "default", cause: org.xml.sax.SAXParseException: <Line 2, Column1>: XML-20108: (Fatal Error) Start of root element expected.
at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider$NoLibOvd.getInstance(LdapIdentityStoreProvider.java:341)
at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance(LdapIdentityStoreProvider.java:118)
at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance(LdapIdentityStoreProvider.java:74)
at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.findServiceInstance(ContextFactoryImpl.java:139)
at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:170)
Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.service.igf.IGFException: JPS-02592: Failed to push ldap config data to libOvd for service instance "idstore.ldap" in JPS context
"default", cause: org.xml.sax.SAXParseException: <Line 2, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
at oracle.security.jps.internal.igf.ovd.OvdIGFServiceProvider.pushLdapNamesTolibOvd(OvdIGFServiceProvider.java:321)
at oracle.security.jps.internal.igf.ovd.OvdIGFServiceProvider.prepareDataPush2libOvd(OvdIGFServiceProvider.java:370)
at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider$NoLibOvd.getInstance(LdapIdentityStoreProvider.java:339)
at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance(LdapIdentityStoreProvider.java:118)
at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance(LdapIdentityStoreProvider.java:74)
Truncated. see log file for complete stacktrace
Caused By: org.xml.sax.SAXParseException: <Line 2, Column 1>: XML-20108: (FatalError) Start of root element expected.
at oracle.ods.virtualization.engine.config.parsers.ConfigErrorHandler.fatalError(ConfigErrorHandler.java:101)
at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:432)
at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:287)
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:414)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:356)
Truncated. see log file for complete stacktrace
Caused By: org.xml.sax.SAXParseException: <Line 2, Column 1>: XML-20108: (FatalError) Start of root element expected.
at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:422)
at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:287)
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:414)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:355)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:226)
Truncated. see log file for complete stacktrace
>
<Apr 10, 2012 3:07:23 PM CEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Apr 10, 2012 3:07:23 PM CEST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Apr 10, 2012 3:07:23 PM CEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
help me please
Thanks.
Edited by: 842284 on 10 avr. 2012 07:41

Hi,
Please navigate to the fmwconfig folder and check the adapters.os_xml file.
$DOMAIN_HOME/config/fmwconfig/ovd/default/adapters.os_xml
There are chances the adapters.os_xml file could be corrupted due to which the Weblogic server fails to start.
Please verify if the adapters.os_xml file is valid.
In case the file is corrupted, please perform the following steps :
1) Take a backup of $DOMAIN_HOME/config/fmwconfig/ovd/default/adapters.os_xml
2) Delete $DOMAIN_HOME/config/fmwconfig/ovd/default/adapters.os_xml
3) copy adapters.os_xml from $MW_HOME/oracle_common/modules/oracle.ovd_11.1.1/templates/ to $DOMAIN_HOME/config/fmwconfig/ovd/default/
4) Restart the server.
Regards,
Kal

Weblogic Server 9.2 not starting

Hello All,
Our weblogic server 9.2 admin server is not being started. This is a admin instance and we are having issue with the managed server startup as well.
We get the following error message - I have read another thread as well on this forum for different version of weblogic but nothing seems to be working. Currently the log says that some ldap files inside the ldap directory and log files are owned via root and when we try to start the server with dmadmin user, the files are not accessable.
Our problem is -
(1) It is a production box so we have to careful when we change the ownership of the files if required from root to dmadmin.
(2) If we change the ownership or delete the ldap files how it will impact to the production environment.
(3) We have test environment and there all these files are owned by dmadmin user but in production some how few of them are owned by root and not starting up...since we are using the dmadmin seesion to start it....
I am pretty new to Weblogic server so dont know how to solve it. Please share your thoughts....
JAVA Memory arguments: -Xms256m -Xmx512m
WLS Start Mode=Production
CLASSPATH=:/documentum/bea9.2/patch_weblogic920/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/documentum/bea9.2/jdk/lib/tools.jar:/documentum/bea9.2/weblogic/server/lib/weblogic_sp.jar:/documentum/bea9.2/weblogic/server/lib/weblogic.jar:/documentum/bea9.2/weblogic/server/lib/webservices.jar::/documentum/bea9.2/weblogic/common/eval/pointbase/lib/pbclient51.jar:/documentum/bea9.2/weblogic/server/lib/xqrl.jar::
PATH=/documentum/bea9.2/weblogic/server/bin:/documentum/bea9.2/jdk/jre/bin:/documentum/bea9.2/jdk/bin:/oracle/app/oracle/product/10.2.0.3/bin:/documentum/product/6.0/convert:/documentum/java/1.5.0_00/bin:/documentum/product/6.0/bin:/documentum/dba:/usr/bin:/etc:/usr/sbin:/usr/ucb:/home/dmadmin/bin:/usr/bin/X11:/sbin:.
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://hostname:port/console *
starting weblogic with Java version:
Starting WLS with line:
/documentum/bea9.2/jdk/bin/java -Xms256m -Xmx512m -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 -da -Dplatform.home=/documentum/bea9.2/weblogic -Dwls.home=/documentum/bea9.2/weblogic/server -Dwli.home=/documentum/bea9.2/weblogic/integration -Dweblogic.management.discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/documentum/bea9.2/patch_weblogic920/profiles/default/sysext_manifest_classpath -Dweblogic.Name=adminServer -Djava.security.policy=/documentum/bea9.2/weblogic/server/lib/weblogic.policy weblogic.Server
<Apr 17, 2012 10:11:44 PM EDT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
/documentum/bea9.2/weblogic/platform/lib/p13n/p13n-schemas.jar:/documentum/bea9.2/weblogic/platform/lib/p13n/p13n_common.jar:/documentum/bea9.2/weblogic/platform/lib/p13n/p13n_system.jar:/documentum/bea9.2/weblogic/platform/lib/wlp/netuix_common.jar:/documentum/bea9.2/weblogic/platform/lib/wlp/netuix_schemas.jar:/documentum/bea9.2/weblogic/platform/lib/wlp/netuix_system.jar:/documentum/bea9.2/weblogic/platform/lib/wlp/wsrp-common.jar>
<Apr 17, 2012 10:11:45 PM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with IBM J9 VM Version 2.3 from IBM Corporation>
<Apr 17, 2012 10:11:47 PM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Temporary Patch for CR322044 Tue Jul 31 12:48:52 IST 2007
WebLogic Temporary Patch for CR334842 Thu Aug 2 14:45:06 2007
WebLogic Temporary Patch for CR284142 Tue Oct 10 16:41:47 2006
WebLogic Temporary Patch for CR299086 Wed Nov 15 18:45:32 2006
WebLogic Temporary Patch for CR276285 Thu Nov 16 10:27:34 2006
WebLogic Server 9.2 Tue Dec 12 14:26:03 PST 2006 876043 >
<Apr 17, 2012 10:11:54 PM EDT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /documentum/bea9.2/license.bea>
<Apr 17, 2012 10:11:54 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Apr 17, 2012 10:11:54 PM EDT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Apr 17, 2012 10:11:54 PM EDT> <Error> <Log Management> <BEA-170020> <The server log file ./servers/adminServer/logs/adminServer.log could not be opened successfully.>
<Apr 17, 2012 10:11:56 PM EDT> <Error> <EmbeddedLDAP> <000000> <Error opening the Transaction Log: ./servers/adminServer/data/ldap/ldapfiles/EmbeddedLDAP.tran (Permission denied)>
<Apr 17, 2012 10:11:56 PM EDT> <Error> <EmbeddedLDAP> <000000> <Error Instantiating 'dc=DctmDomain': null>
<Apr 17, 2012 10:11:56 PM EDT> <Critical> <EmbeddedLDAP> <BEA-171522> <An error occurred while initializing the Embedded LDAP Server. The exception thown is java.lang.ClassCastException: com.octetstring.vde.backend.BackendRoot incompatible with com.octetstring.vde.backend.standard.BackendStandard. This may indicate a problem with the data files for the Embedded LDAP Server. If the problem is with the data files and it can not be corrected, backups of previous versions of the data files exist in ./servers/adminServer/data/ldap/backup.>
<Apr 17, 2012 10:11:56 PM EDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
java.lang.ClassCastException: com.octetstring.vde.backend.BackendRoot incompatible with com.octetstring.vde.backend.standard.BackendStandard
     at weblogic.ldap.EmbeddedLDAP.start(EmbeddedLDAP.java:273)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
<Apr 17, 2012 10:11:56 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Apr 17, 2012 10:11:56 PM EDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Apr 17, 2012 10:11:56 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

Thanks Arun. Your reply is helpful. How can I identify weather I am using the node manager or not....What we use is the following script to start the server...
#this script will start Documentum Application
. /home/dmadmin/.profile
nohup /documentum/bea9.2/domains/DctmDomain/startWebLogic.sh > /documentum/dba/log/Weblogic/StartWL.log &
sleep 90
nohup /documentum/bea9.2/domains/DctmDomain/startMethodServer.sh >/documentum/dba/log/Weblogic/startMethodServer.log &
sleep 90
These are the files currently owned via root. I have asked the Unix team to change the ownership because I even can not delete the file inside the ldap directory owned via root. Then I will try to restart the server ....
<Domain_Home>\data\ldap\ldapfiles\EmbeddedLDAP.tran
<Domain_Home>\logs\adminServer.log
<Domain_Home>\logs\DctmDomain.log
Kindly suggest if we are on the right track....and about the node manager...
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
One more thing if you see our script -
#this script will start Documentum Application
. /home/dmadmin/.profile
nohup /documentum/bea9.2/domains/DctmDomain/startWebLogic.sh > /documentum/dba/log/Weblogic/StartWL.log &
sleep 90
nohup /documentum/bea9.2/domains/DctmDomain/startMethodServer.sh >/documentum/dba/log/Weblogic/startMethodServer.log &
sleep 90
We start the Method server after the weblogic server and we get the nested error which says - Could not obtain the lock
<Domain_Home>\tmp\DctmServer_MethodServer.lok
server might already running..
Thanks for your help

Weblogic server failing to start

Hi All,
Need help in starting up the weblogic server with the below error:
starting weblogic with Java version:
Starting WLS with line:
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b50)
Java HotSpot(TM) Client VM (build 19.1-b02, mixed mode)
C:\Oracle\MIDDLE~1\JDK160~1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=DefaultServer -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Djavax.net.ssl.trustStore=C:\Oracle\Middleware\wlserver_10.3\server\lib\DemoTrust.jks -Dweblogic.nodemanager.ServiceEnabled=true -Xverify:none -da -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Djps.app.credential.overwrite.allowed=true -Dcommon.components.home=C:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=C:\JDEVEL~1\jdevhome\jdev\SYSTEM~1.29\DEFAUL~1 -Djrockit.optfile=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=C:\JDEVEL~1\jdevhome\jdev\SYSTEM~1.29\DEFAUL~1\config\FMWCON~1\servers\DefaultServer -Doracle.domain.config.dir=C:\JDEVEL~1\jdevhome\jdev\SYSTEM~1.29\DEFAUL~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=C:\JDEVEL~1\jdevhome\jdev\SYSTEM~1.29\DEFAUL~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\JDEVEL~1\jdevhome\jdev\SYSTEM~1.29\DEFAUL~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=C:\JDEVEL~1\jdevhome\jdev\SYSTEM~1.29\DEFAUL~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=C:\JDEVEL~1\jdevhome\jdev\SYSTEM~1.29\DEFAUL~1\servers\DefaultServer\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dwsm.repository.path=C:\JDEVEL~1\jdevhome\jdev\SYSTEM~1.29\DEFAUL~1\oracle\store\gmds -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1035\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_oepe1050\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_ocp360\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sysext_manifest_classpath weblogic.Server
<30 Jan, 2013 11:31:17 AM IST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<30 Jan, 2013 11:31:17 AM IST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<30 Jan, 2013 11:31:18 AM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 19.1-b02 from Sun Microsystems Inc.>
<30 Jan, 2013 11:31:19 AM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<30 Jan, 2013 11:31:20 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<30 Jan, 2013 11:31:20 AM IST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<30 Jan, 2013 11:31:20 AM IST> <Notice> <LoggingService> <BEA-320400> <The log file C:\JDeveloper\jdevhome\jdev\system11.1.1.6.38.62.29\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<30 Jan, 2013 11:31:20 AM IST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\JDeveloper\jdevhome\jdev\system11.1.1.6.38.62.29\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log00020. Log messages will continue to be logged in C:\JDeveloper\jdevhome\jdev\system11.1.1.6.38.62.29\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log.>
<30 Jan, 2013 11:31:20 AM IST> <Notice> <Log Management> <BEA-170019> <The server log file C:\JDeveloper\jdevhome\jdev\system11.1.1.6.38.62.29\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log is opened. All server side log events will be written to this file.>
<30 Jan, 2013 11:31:21 AM IST> <Error> <EmbeddedLDAP> <BEA-000000> <Error Instantiating 'dc=DefaultDomain': null>
<30 Jan, 2013 11:31:21 AM IST> <Critical> <EmbeddedLDAP> <BEA-171522> <An error occurred while initializing the Embedded LDAP Server. The exception thrown is java.lang.ClassCastException: com.octetstring.vde.backend.BackendRoot cannot be cast to com.octetstring.vde.backend.standard.BackendStandard. This may indicate a problem with the data files for the Embedded LDAP Server. If the problem is with the data files and it can not be corrected, backups of previous versions of the data files exist in C:\JDeveloper\jdevhome\jdev\system11.1.1.6.38.62.29\DefaultDomain\servers\DefaultServer\data\ldap\backup.>
<30 Jan, 2013 11:31:21 AM IST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
java.lang.ClassCastException: com.octetstring.vde.backend.BackendRoot cannot be cast to com.octetstring.vde.backend.standard.BackendStandard
     at weblogic.ldap.EmbeddedLDAP.start(EmbeddedLDAP.java:303)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
<30 Jan, 2013 11:31:21 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<30 Jan, 2013 11:31:21 AM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<30 Jan, 2013 11:31:21 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Process exited.

Hi,
With data folder, You can also delete or rename tmp and cache folder in same location (${DOMAIN_HOME}/servers/${SERVER_NAME}/).
Just rename/delete all three folders and restart JVM again.

Weblogic Server 6.1 with MS Windows 2000 Cluster

Hello everybody,
following situation:
We want to implement a Microsoft Cluster (Failover) with MS Cluster Service and
2 nodes (maybe later we try the Weblogic Software clustering with load balancing
as a part of an documentum and infotehna DMS). On both nodes we made the same
test installation of the Weblogic Server 6.1 and started it with services (instead
of cmd-file).
It's working fine seperate on every node, than we started to implement the MSCS
on these machines and only one node is working. On the other node (after a failover
to this node) the service started but break down only a few seconds later.
Now, my question is: Can we use the Weblogic Server 6.1 in an Windows 2000 Advanced
Server Failover Cluster with 2 nodes? Or do we need a special Add-on to do this???
Best regards,
Ronny

Ronny,
I'm don't know the specifics of MS Cluster Service but given that it works like
other common HA frameworks (assumption on my part) you may need to use the MS
cluster framework in isolation from the 'software-based' clustering approach that
WLS 6.x currently provides. For example, in other HA Frameworks there is typically
a heartbeat mechanism that informs the framework that a node is dead and the framework
in turn calls scripts that migrate the failed node 'applications' over to the
healthy node. In WLS, you could mimic the same approach where a single admin
server fails over to a backup server not using the WLS 'software' admin/mgd server
cluster value-add. In others words, you would need to script a heartbeat mechanism
for the single WLS server and also script failover to a backup node when the heartbeat
indicates 'failure'. This technique would be used in isolation (not using the
current WLS software-based cluster configuration).
My 2 cents,
Chuck Nelson
DRE
BEA Technical Support

Weblogic.server.ServiceFailureException:com- embedded LDAP error

Hi
While starting teh weblogic server, I am getting error as
weblogic.server.ServiceFailureException: Error initialisng embedded LDAP server - with nested exception
java.lang.ClassCastException:com.octetstring.vde.backend.BackendRoot
the server is not started (I have installed it as a window service in Win2k)
Any help on this ?

there are few different ways to fix this. I do this frequently
--Delete the data folder and boot the server it will fix the issue. You will lose all the users information (except admin user) need to recrate any ohter users you created.make sure backup data folder
-- Second get the data folder from domain_bak folder
Hope this will fix your problem
Thanks
ksr
Edited by: ksr11 on Nov 24, 2010 10:33 AM

Weblogic Server error - OutOfMemoryError: PermGen space

Dear All,
For Oracle BPM 11g (Implement the Process Model) implementation on windows
I am using windows 7 64 Bit OS. I have
Installed 10g DB
Run the RCU Utility for SOAINFRA, ORABAM, SSPDM and MDS schemas successfully.
Installed Weblogic Server 11gr1(10.3.5)
Installed Oracle Jdeveloper 11g - 11.1.1.6.0
Installed SOA 11g using \Java\jdk1.6.0_24
From Jdeveloper I installed the extensions for SOA Composite Editor and BPM studio.
Created Domain for SOA server
All installations, utitlities and configurations completed successfully.
After starting the Weblogic Admin. server (server is up and OK)
The Problem starts here
When I login to weblogic Admin console I get the following error
javax.servlet.ServletException: java.lang.OutOfMemoryError: PermGen space on
the command prompt window and even on the browser window.
I am able to trace the problem. To get the Idea following are some details of
$MW_HOME/user_projects/domains/soa_domain/bin/setDomainEnv.cmd
call "%WL_HOME%\common\bin\commEnv.cmd"
call "%DOMAIN_HOME%\bin\setSOADomainEnv.cmd"
call "%DOMAIN_HOME%\bin\setSOADomainEnv.cmd"
set WLS_HOME=%WL_HOME%\server
set XMS_SUN_64BIT=256
set XMS_SUN_32BIT=256
set XMX_SUN_64BIT=512
set XMX_SUN_32BIT=512
set XMS_JROCKIT_64BIT=256
set XMS_JROCKIT_32BIT=256
set XMX_JROCKIT_64BIT=512
set XMX_JROCKIT_32BIT=512
if "%JAVA_VENDOR%"=="Sun" (
    set WLS_MEM_ARGS_64BIT=-Xms256m -Xmx512m
    set WLS_MEM_ARGS_32BIT=-Xms256m -Xmx512m
) else (
    set WLS_MEM_ARGS_64BIT=-Xms512m -Xmx512m
    set WLS_MEM_ARGS_32BIT=-Xms512m -Xmx512m
if "%JAVA_VENDOR%"=="Oracle" (
    set CUSTOM_MEM_ARGS_64BIT=-Xms%XMS_JROCKIT_64BIT%m -Xmx%XMX_JROCKIT_64BIT%m
    set CUSTOM_MEM_ARGS_32BIT=-Xms%XMS_JROCKIT_32BIT%m -Xmx%XMX_JROCKIT_32BIT%m
) else (
    set CUSTOM_MEM_ARGS_64BIT=-Xms%XMS_SUN_64BIT%m -Xmx%XMX_SUN_64BIT%m
    set CUSTOM_MEM_ARGS_32BIT=-Xms%XMS_SUN_32BIT%m -Xmx%XMX_SUN_32BIT%m
set MEM_ARGS_64BIT=%CUSTOM_MEM_ARGS_64BIT%
set MEM_ARGS_32BIT=%CUSTOM_MEM_ARGS_32BIT%
if "%JAVA_USE_64BIT%"=="true" (
    set MEM_ARGS=%MEM_ARGS_64BIT%
) else (
    set MEM_ARGS=%MEM_ARGS_32BIT%
set MEM_PERM_SIZE_64BIT=-XX:PermSize=128m
set MEM_PERM_SIZE_32BIT=-XX:PermSize=128m
After taking the backup
I tried changing the Permsize to 256, 512 and even 1024.
started the Weblogic Admin server and tried to login, but the same error.
Details of setSOADomainEnv.cmd
set JAVA_OPTIONS=%JAVA_OPTIONS%
set DEFAULT_MEM_ARGS=-Xms512m -Xmx1024m
set PORT_MEM_ARGS=-Xms768m -Xmx1536m
if "%JAVA_VENDOR%" == "Oracle" goto OracleJVM
set DEFAULT_MEM_ARGS=%DEFAULT_MEM_ARGS% -XX:PermSize=128m -XX:MaxPermSize=512m
set PORT_MEM_ARGS=%PORT_MEM_ARGS% -XX:PermSize=256m -XX:MaxPermSize=512m
what are the recommended values I need to put for Permsize in setDomainEnv.cmd?
Do I also need to change the values in setSOADomainEnv.cmd ?
Please correct me where I am wrong. How can the OutOfMemoryError: PermGen space
issue be resolved ?
Thanks
Ajaz Ahmed

Hi Lakshman,
Thanks for the prompt resonse.
1. How many managed servers do you have in your domain ?
I have only one managed server (soa_server1)
2. If yes, How you are starting the Managed server ? Is that by Nodemanager or Startscript ?
Yes. I start the managed server by startscript (using startmanagedweblogic)
3. Can you check the <managed_server1>.out log file what java heap size is mentioned ?
I have not reached the managed server startup (though it starts and gives
the last line as SOA platform is accepting and running the requiests.
My problem is with weblogic server, which after login I get the Permgen out of memory error.
4. Can you show us the start up arguements of your each managed server ?
   AdminConsole-->Environments---.Servers--->YourManagedServer--->Configuration (TAB)--->ServerStart (SubTab)---> Arguments:(TextArea)
I am not able to get the console. Because when I login the weblogic console,
Immediately I get the error as
javax.servlet.ServletException: java.lang.OutOfMemoryError: PermGen space
Please clear my doubt as which of the files
setDomainEnv.cmd or setSOADomainEnv.cmd, I should change the values and
into which file and which step.
My priority is weblogic console to be working without any errors. So Far Managed server is OK.
Thanks
Ajaz Ahmed

Weblogic server not getting started.(undefined mbean reference.)

Hi ,
I am using Weblogic server 7.0 in solaris and i have deployed web applications to the managed servers.
When i am restarting my admin server , i am getting the following error:
<May 22, 2009 12:08:23 PM IST> <Critical> <WebLogicServer> <000364> <Server failed during initialization. Exception:weblogic.management.configuration.ConfigurationException: undefined mbean reference: iciciprulife:Name=DefaultWebApp,Server=adminserver,Type=WebAppComponent
weblogic.management.configuration.ConfigurationException: undefined mbean reference: iciciprulife:Name=DefaultWebApp,Server=adminserver,Type=WebAppComponent
at weblogic.management.internal.xml.ConfigurationParser$ConfigurationHandler.resolveMBeanAttributes(ConfigurationParser.java:809)
at weblogic.management.internal.xml.ConfigurationParser$ConfigurationHandler.endDocument(ConfigurationParser.java:337)
at weblogic.apache.xerces.parsers.SAXParser.endDocument(SAXParser.java:1235)
at weblogic.apache.xerces.validators.common.XMLValidator.callEndDocument(XMLValidator.java:1159)
at weblogic.apache.xerces.framework.XMLDocumentScanner$EndOfInputDispatcher.dispatch(XMLDocumentScanner.java:1531)
at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:399)
at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:1138)
at weblogic.management.internal.xml.ConfigurationParser.parse(ConfigurationParser.java:227)
at weblogic.management.internal.xml.XmlFileRepository.createOrLoadDomain(XmlFileRepository.java:483)
at weblogic.management.internal.xml.XmlFileRepository.bootStrapAndLoadActiveDomain(XmlFileRepository.java:354)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:217)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:202)
at weblogic.management.AdminServer.configure(AdminServer.java:196)
at weblogic.management.AdminServerAdmin.initialize(AdminServerAdmin.java:111)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:664)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
>
The WebLogic Server did not start up properly.
Exception raised:
weblogic.management.configuration.ConfigurationException: undefined mbean reference: iciciprulife:Name=DefaultWebApp,Server=adminserver,Type=WebAppComponent
at weblogic.management.internal.xml.ConfigurationParser$ConfigurationHandler.resolveMBeanAttributes(ConfigurationParser.java:809)
at weblogic.management.internal.xml.ConfigurationParser$ConfigurationHandler.endDocument(ConfigurationParser.java:337)
at weblogic.apache.xerces.parsers.SAXParser.endDocument(SAXParser.java:1235)
at weblogic.apache.xerces.validators.common.XMLValidator.callEndDocument(XMLValidator.java:1159)
at weblogic.apache.xerces.framework.XMLDocumentScanner$EndOfInputDispatcher.dispatch(XMLDocumentScanner.java:1531)
at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:399)
at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:1138)
at weblogic.management.internal.xml.ConfigurationParser.parse(ConfigurationParser.java:227)
at weblogic.management.internal.xml.XmlFileRepository.createOrLoadDomain(XmlFileRepository.java:483)
at weblogic.management.internal.xml.XmlFileRepository.bootStrapAndLoadActiveDomain(XmlFileRepository.java:354)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:217)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:202)
at weblogic.management.AdminServer.configure(AdminServer.java:196)
at weblogic.management.AdminServerAdmin.initialize(AdminServerAdmin.java:111)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:664)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
Reason: Fatal initialization exception
Throwable: weblogic.management.configuration.ConfigurationException: undefined mbean reference: iciciprulife:Name=DefaultWebApp,Server=adminserver,Type=WebAppComponent
weblogic.management.configuration.ConfigurationException: undefined mbean reference: iciciprulife:Name=DefaultWebApp,Server=adminserver,Type=WebAppComponent
at weblogic.management.internal.xml.ConfigurationParser$ConfigurationHandler.resolveMBeanAttributes(ConfigurationParser.java:809)
at weblogic.management.internal.xml.ConfigurationParser$ConfigurationHandler.endDocument(ConfigurationParser.java:337)
at weblogic.apache.xerces.parsers.SAXParser.endDocument(SAXParser.java:1235)
at weblogic.apache.xerces.validators.common.XMLValidator.callEndDocument(XMLValidator.java:1159)
at weblogic.apache.xerces.framework.XMLDocumentScanner$EndOfInputDispatcher.dispatch(XMLDocumentScanner.java:1531)
at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:399)
at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:1138)
at weblogic.management.internal.xml.ConfigurationParser.parse(ConfigurationParser.java:227)
at weblogic.management.internal.xml.XmlFileRepository.createOrLoadDomain(XmlFileRepository.java:483)
at weblogic.management.internal.xml.XmlFileRepository.bootStrapAndLoadActiveDomain(XmlFileRepository.java:354)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:217)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:202)
at weblogic.management.AdminServer.configure(AdminServer.java:196)
at weblogic.management.AdminServerAdmin.initialize(AdminServerAdmin.java:111)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:664)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
+ set +x
Canany one please help me to rectify the above problem.
Thanks in advance.
Krikar

Hi take a backup of config.xml file first and then replace it with config.xml.booted. This is the config file which ran successfully last time.
Note : I am assuming this is not production server. If it is then I would suggest you to open a SR with support.
Edited by: mchellap on May 22, 2009 3:43 PM

Weblogic server installation error

Hi,
I has installed weblogic server 10.3.2 in C:\Oracle\Middleware, then i uninstalled weblogic server. Now i want to install again, but i got this error: http://imageshack.us/photo/my-images/812/asdasdmi.jpg/
Please help me and give me some ideas of what to do, i'm so confused.
Thanks
Edited by: Roger22 on 29.06.2011 19:37

Hi,
If no other weblogic serverss installed on that machine, then you could delete the registry key corresponding to the old installation.
It seems you are using windows.
click start button-->Run-->type 'regedit' without quotes and then search for the key weblogic and delete that key.
*Please make sure you will have a backup of registry keys.
presee CTRL + F and type weblogic and click next and find a key smiliar to this below.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\BEA Products
select the BEA Products folder lefthandside and delete that.
remove BEA products shortcut from start menu and reboot your machine once and then try installing weblogic server.
Thanks
Weblogic Admin

The WebLogic Server not starting up properly.

Hi Guys,
Can any body help me for following error with weblogic.
We are using weblogic 8.1 sp 4.
While starting weblogic server it displays following error.
==========================================================
<13-Oct-2006 09:13:07 o'clock BST> <Error> <Configuration Management> <BEA-150029> <There was an error reading the MBean mydomain:Name=cman_m1,Server=cman_m1,Type=ServerStart. The value {3DES}7wwcZnDbae0xMa4dJR/tOA== for attribute PasswordEncrypted could not be read successfully.>
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.management.configuration.ConfigurationException: [Configuration Management:150029]There was an error reading the MBean mydomain:Name=cman_m1,Server=cman_m1,Type=ServerStart. The value {3DES}7wwcZnDbae0xMa4dJR/tOA== for attribute PasswordEncrypted could not be read successfully.'
Reason: weblogic.management.configuration.ConfigurationException: [Configuration Management:150029]There was an error reading the MBean mydomain:Name=cman_m1,Server=cman_m1,Type=ServerStart. The value {3DES}7wwcZnDbae0xMa4dJR/tOA== for attribute PasswordEncrypted could not be read successfully.
==========================================================

create a new boot.properties file with usernam & password
and
Make the backup of cofig.xml file,
then Edit the config.xml
PasswordEncrypted={ksskjfhsdjfsdfhdk} server="Admin_WLS">
replace with
Password="weblogic" server="Admin_WLS">
restart the WLS now

Weblogic server startup not happening

Hello,
Using obiee 11g in linux,
My admin tool stops responding due to some reason so did a forced closeing then after that nothing was working
So stopped opmnctl and trying restarting,its not working then thought will retstart the weblogic Server
now thats not working totally gone case any help pls.
A part of the error i am shwoing
<Sep 16, 2011 11:35:16 AM IST> <Error> <EmbeddedLDAP> <BEA-000000> <Error opening the Transaction Log: /orcl/oracleBI/user_projects/domains/bifoundation_domain/servers/AdminServer/data/ldap/ldapfiles/EmbeddedLDAP.tran (Permission denied)>
<Sep 16, 2011 11:35:16 AM IST> <Error> <EmbeddedLDAP> <BEA-000000> <Error Instantiating 'dc=bifoundation_domain': null>
<Sep 16, 2011 11:35:16 AM IST> <Critical> <EmbeddedLDAP> <BEA-171522> <An error occurred while initializing the Embedded LDAP Server. The exception thrown is java.lang.ClassCastException: com.octetstring.vde.backend.BackendRoot cannot be cast to com.octetstring.vde.backend.standard.BackendStandard. This may indicate a problem with the data files for the Embedded LDAP Server. If the problem is with the data files and it can not be corrected, backups of previous versions of the data files exist in /orcl/oracleBI/user_projects/domains/bifoundation_domain/servers/AdminServer/data/ldap/backup.>
<Sep 16, 2011 11:35:16 AM IST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
java.lang.ClassCastException: com.octetstring.vde.backend.BackendRoot cannot be cast to com.octetstring.vde.backend.standard.BackendStandard
at weblogic.ldap.EmbeddedLDAP.start(EmbeddedLDAP.java:303)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
<Sep 16, 2011 11:35:16 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Sep 16, 2011 11:35:16 AM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Sep 16, 2011 11:35:16 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Thanks
Edited by: user123 on Sep 16, 2011 11:40 AM

An error occurred while initializing the Embedded LDAP Server. The exception thrown is java.lang.ClassCastException: com.octetstring.vde.backend.BackendRoot cannot be cast to com.octetstring.vde.backend.standard.BackendStandard. This may indicate a problem with the data files for the Embedded LDAP Server. If the problem is with the data files and it can not be corrected, backups of previous versions of the data files exist in /orcl/oracleBI/user_projects/domains/bifoundation_domain/servers/AdminServer/data/ldap/backup.Looks like LDAP issue...do you have any external authentication setup ?? You can think investigation issue in that direction..Check the complete error code.

Weblogic Server cannot find Service accounts in my MSAD via LDAP

Hello,
I've configured an LDAP security provider in my WebLogic server but it's only finding some of my users, not my "service account" users.
The users are found in the following locations in the tree:
OU=Users,OU=Accounts,DC=dev,DC=mtb,DC=com
OU=Service,OU=Accounts,DC=dev,DC=mtb,DC=com
So I configured the LDAP provider with the following settings:
User Base DN: OU=Accounts,DC=dev,DC=mtb,DC=com
All Users Filter: (blank)
User from Name Filter: (&(cn=%u)(objectclass=user))
User Search Scope: subtree
User Name Attribute: cn
User Object Class: user
But it cannot find users in the "Service" node, only users in the "Users" node. Both users have CN=, and "user" as part of their objectClass string. Any idea what I might be missing?
Thank you,
-Ben

Hi
1. I hope you already created a datasource on Weblogic Side using weblogic admin console and create New Data Source. Create a data source preferably with this JNDI Name "jdbc/mydbDSDS". It can be anything, but standard is jdbc/whatevernameyouwant. Once data source is created, you give db details like host, port, sid, username/password. Then deploy to appropriate server(s) like using Targets screen. Once all done. Under your domain/config/jdbc, you should see a .xml file with some unique name that has all the datasource details. The jndi name tag should be like this: <jndi-name>jdbc/mydbDSDS</jndi-name>
2. Now, edit your persistence.xml file to refer above jndi name. By default, I know, it adds that wierd name with jdbc/jdbc etc etc. But you can edit it always. Take a backup of your persistence.xml file and edit it to look like this.
<persistence-unit name="mydbDS">
    <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
    <jta-data-source>jdbc/mydbDSDS</jta-data-source>
    <properties>
      <property name="eclipselink.target-server" value="WebLogic_10"/>
      <property name="eclipselink.cache.shared.default" value="false"/>
    </properties>
</persistence-unit>
</persistence>Save it. Redeploy and see how that goes. The above file is simplified version. What it means is, just refer already deployed data source whose jndi name is "jdbc/mydbDSDS". If you really have some extra properties, you can retain them. Otherwise they are not required.
Thanks
Ravi Jegga

Exception:weblogic.server.ServiceFailureException:

JAVA Memory arguments: -Xms96m -Xmx256m
WLS Start Mode=Development
CLASSPATH=C:/cspDomain/lib/patches/CSP_patch_434.jar;;;C:\bea\WEBLOG~1\server\lib\weblogic_knex_patch.jar;C:\bea\WEBLOG~1\common\lib\log4j.jar;C:\bea\WEBLOG~1\server\lib\debugging.jar;C:\bea\WEBLOG~1\server\lib\knex.jar;C:\bea\WEBLOG~1\javelin\lib\javelin.jar;C:\bea\WEBLOG~1\server\lib\wlw-lang.jar;C:\bea\JROCKI~1\lib\tools.jar;C:\bea\WEBLOG~1\server\lib\weblogic_sp.jar;C:\bea\WEBLOG~1\server\lib\weblogic.jar;C:\bea\WEBLOG~1\server\lib\ant\ant.jar;C:\bea\JROCKI~1\jre\lib\rt.jar;;C:\bea\WEBLOG~1\common\eval\pointbase\lib\pbclient44.jar;C:\bea\WEBLOG~1\server\lib\webserviceclient.jar;C:\bea\WEBLOG~1\server\lib\webserviceclient+ssl.jar;C:\bea\WEBLOG~1\server\lib\xbean.jar;C:\bea\WEBLOG~1\server\lib\wlxbean.jar;C:\bea\WEBLOG~1\server\lib\xqrl.jar;C:\bea\WEBLOG~1\server\lib\netui\netui-compiler.jar;C:\bea\WEBLOG~1\server\lib\wli.jar;C:\bea\WEBLOG~1\server\lib\fop.jar;C:\bea\WEBLOG~1\integration\adapters\sample\lib\sample-eis.jar;C:\bea\WEBLOG~1\portal\lib\wps_system.jar;C:/cspDomain/lib/post/ClaimsServiceClient.jar;C:/cspDomain/lib/post/commons-beanutils.jar;C:/cspDomain/lib/post/commons-collections.jar;C:/cspDomain/lib/post/commons-digester.jar;C:/cspDomain/lib/post/commons-fileupload.jar;C:/cspDomain/lib/post/commons-logging.jar;C:/cspDomain/lib/post/commons-validator.jar;C:/cspDomain/lib/post/hibernate2.jar;C:/cspDomain/lib/post/junit.jar;C:/cspDomain/lib/post/log4j-1.2.8.jar;C:/cspDomain/lib/post/MemberServiceClient.jar;C:/cspDomain/lib/post/PhsAudit.jar;C:/cspDomain/lib/post/PhsBOD.jar;C:/cspDomain/lib/post/PhsExceptions.jar;C:/cspDomain/lib/post/PhsLogging.jar;C:/cspDomain/lib/post/PhsSchema.jar;C:/cspDomain/lib/post/PhsUtility.jar;C:/cspDomain/lib/post/ProductServiceClient.jar;C:/cspDomain/lib/post/ProviderServiceClient.jar;C:/cspDomain/lib/post/PurchaserServiceClient.jar;C:/cspDomain/lib/post/ServiceLocator.jar;C:/cspDomain/lib/post/struts-adapter.jar;C:/cspDomain/lib/post/struts.jar;C:/cspDomain/lib/post/strutstestcase.jar;C:/cspDomain/lib/post/west_fax_client.jar;C:/cspDomain/settings
PATH=C:\bea\WEBLOG~1\server\bin;C:\bea\JROCKI~1\jre\bin;C:\bea\JROCKI~1\bin;C:\OraHome1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\bea\WEBLOG~1\server\bin\oci920_8
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
=== Debugging ===
This window is necessary for debugging code using WebLogic Workshop
Starting WLS with line:
C:\bea\JROCKI~1\bin\java -jrockit -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms96m -Xmx256m -Xverify:none -ea -da:com.bea... -da:javelin... -da:weblogic... -Dplatform.home=C:\bea\WEBLOG~1 -Dwls.home=C:\bea\WEBLOG~1\server -Dwli.home=C:\bea\WEBLOG~1\integration -Dlog4j.configuration=file:C:\bea\WEBLOG~1\common\lib\workshopLogCfg.xml -Dweblogic.management.discover=true -Dweblogic.ProductionModeEnabled= -Dejbruntime.database=oracle81xthin -Dweblogic.security.SSL.ignoreHostnameVerify=false -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true -Dweblogic.Name=cspServer -Djava.security.policy=C:\bea\WEBLOG~1\server\lib\weblogic.policy weblogic.Server
ERROR: Proxy already running...
<May 6, 2005 2:58:55 PM GMT+05:30> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA WebLogic JRockit(TM) 1.4.2_04 JVM Version ari-31788-20040616-1132-win-ia32 from BEA Systems, Inc.>
<May 6, 2005 2:58:55 PM GMT+05:30> <Info> <Configuration Management> <BEA-150016> <This server is being started as the administration server.>
<May 6, 2005 2:58:55 PM GMT+05:30> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
WebLogic XMLX Module 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
WebLogic Integration 8.1 SP3 Wed Jun 30 14:05:38 PDT 2004 405464
WebLogic Portal 8.1 SP3 Wed Jun 30 14:02:15 PDT 2004 405464>
<May 6, 2005 2:58:56 PM GMT+05:30> <Notice> <Management> <BEA-140005> <Loading domain configuration from configuration repository at C:\CSPDOM~3\domains\CSPDOM~1\.\config.xml.>
Could not bind to Weblogic server (Error attaching to Weblogic Server.).
<May 6, 2005 2:59:00 PM GMT+05:30> <Notice> <Log Management> <BEA-170019> <The server log file C:\CSPDomain\domains\cspDomain\cspServer\cspServer.log is opened. All server side log events will be written to this file.>
<May 6, 2005 2:59:01 PM GMT+05:30> <Error> <EmbeddedLDAP> <000000> <Error Instantiating 'dc=cspDomain': null>
<May 6, 2005 2:59:01 PM GMT+05:30> <Critical> <EmbeddedLDAP> <BEA-171522> <An error occurred while initializing the Embedded LDAP Server. The exception thown is java.lang.ClassCastException: com.octetstring.vde.backend.BackendRoot. This may indicate a problem with the data files for the Embedded LDAP Server. If the problem is with the data files and it can not be corrected, backups of previous versions of the data files exist in .\cspServer\ldap\backup.>
<May 6, 2005 2:59:01 PM GMT+05:30> <Critical> <WebLogicServer> <BEA-000364> <Server failed during initialization. Exception:weblogic.server.ServiceFailureException: Error initializing Embedded LDAP Server - with nested exception:
[java.lang.ClassCastException: com.octetstring.vde.backend.BackendRoot]
java.lang.ClassCastException: com.octetstring.vde.backend.BackendRoot
     at weblogic.ldap.EmbeddedLDAP.initialize()V(EmbeddedLDAP.java:192)
     at weblogic.t3.srvr.T3Srvr.initializeHere()V(T3Srvr.java:816)
     at weblogic.t3.srvr.T3Srvr.initialize()V(T3Srvr.java:670)
     at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:344)
     at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
--------------- nested within: ------------------
weblogic.server.ServiceFailureException: Error initializing Embedded LDAP Server - with nested exception:
[java.lang.ClassCastException: com.octetstring.vde.backend.BackendRoot]
     at weblogic.ldap.EmbeddedLDAP.initialize()V(EmbeddedLDAP.java:276)
     at weblogic.t3.srvr.T3Srvr.initializeHere()V(T3Srvr.java:816)
     at weblogic.t3.srvr.T3Srvr.initialize()V(T3Srvr.java:670)
     at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:344)
     at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
>
<May 6, 2005 2:59:01 PM GMT+05:30> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: weblogic.server.ServiceFailureException: Error initializing Embedded LDAP Server - with nested exception:
[java.lang.ClassCastException: com.octetstring.vde.backend.BackendRoot]>
Stopping the Weblogic Workshop debugger...
Debugger Stopped.
i am getting the above exception what is the problem
thanks,
siva
Thanks & Regards,
Siva VP,
[email protected]

Deletion of this folder works. But the error popups again while i am restarting server. Should i delete this everytime before i start. Is there any other way to fix this?

Weblogic Server Upgrade Installer

Hi ,
Can anybody help me How can i download weblogic Server Upgrade Installer
I want to upgrade weblogic10.3.5.0 to weblogic 12c
Thanks
Bhaskar

Hi,
http://docs.oracle.com/cd/E24329_01/doc.1211/e24492/prepare.htm#BABFIDAB
From the above link
WebLogic Server 12.1.1 is a new major release, there is no upgrade installer for this release
You Can follow this link,it has step wise details
http://docs.oracle.com/cd/E24329_01/web.1211/e24497/upgrade_dom.htm#i1072877
Prior u need to install weblogic 12.1.1.0,and take backup of your existing domain.
Choose the Domain Upgrade Wizard option from the Oracle program group in the Windows Start Menu by clicking Programs > Oracle WebLogic > WebLogic Server 12c > Tools > Domain Upgrade Wizard.
Regards
Fabian

Reset WebLogic Server Password

Hello,
I need to reset a password for the admin user of a weblogic server 10.3.3. How do you reset a password?
I tried running "java weblogic.security.utils.AdminAccount <NewAdminUserName> <NewAdminPassword> ." (after I ran setDomainEnv.cmd). The process appears to run successfully, however it doesnt return any messages. However the "%my_domain%/security/DefaultAuthenticatorInit.ldift" was modified. So I shutdown the server, try to login with the new password and it still needs the old password!
I looked through Oracle's WebLogic API to find any more info on the function, but nothing is available (deprecated?).
Steps I did:
1.) Run setDomainEnv.cmd, in "%my_domain%/bin" directory
2.) In the "%my_domain%/security" directory, I ran "java weblogic.security.utils.AdminAccount weblogic Password1 ."
3.) Try to start up server with new password, and server rejects new password. Accepts only old password.
Thank you,
Gavin
Edited by: GavinWoods on Jan 18, 2011 1:30 PM

Just in case anyone comes by this, I figured it out! (Thanks to: http://shmukum.wordpress.com/2010/05/04/resetwladminpasswd/ )
I needed to do one last thing: Delete the "*ldap*" folder in the "*%Domain_Home%/servers/%server_name%/data/*" folder.
so overall, here's steps that need to be done:
1.) Open Command prompt > run setDomainEnv.cmd in the *%DomainHome%/bin* folder
2.) In a file browser, backup %DomainHome%/security/DefaultAuthenticatorInit.ldift, then delete the file.
3.) In command prompt, go to the %DomainHome%/security/ directory, run the following command (period is important): java weblogic.security.utils.AdminAccount weblogic MyPassword .
4.) Step 3 should create a anew DefaultAuthenticatorInit.ldift
5.) Go to *%Domain_Home%/servers/%server_name%/data/*, delete ldap folder
6.) Clear out boot.properties
7.) Verify server starts up under new password
8.) Create new boot.properties for your weblogic server(s)
Warning: step 5: will clear out all LDAP security realm settings in your domain.
Hope this helps someone when they scour the forum.
-Gavin

Weblogic Server backup

Similar Messages

Maybe you are looking for