Upgrading from weblogic 10.3.0.0 to 10.3.2.0?

Hey guys,
I am currently trying to upgrade my 10.3.0.0 weblogic server to 10.3.2.0 and i receive an error message stating that
"The product maintenance level of the current installer (Weblogic Server:10.3.2.0) is not compatible with the maintenance level of the product installed on your system (Weblogic Server 10.3.0.0). Please obtain a compatible installer or perform maintenance on your current system to achieve the desired level."
My question is:
- Is there an out of the box easy way to upgrade from 10.3.0.0 to 10.3.2.0?
thanks.

Hi,
Try giving a different BEA_HOME for weblogic server 10.3.2.0. I think this should help!

Similar Messages

Upgrade from Weblogic 10.3.1 to 10.3.3 Issues

Hi
We are in process of migrating/upgrading from Weblogic server 10.3.1 to 10.3.3.
A heavily distributed application is being migrated with high volume transaction on clustered environment.
Have anybody experienced any issues/ concerns when migrating from Weblogic 10.3.1 to 10.3.3?
Please share your experience.
Thanks
Edited by: user4151568 on Oct 28, 2011 8:55 AM
Edited by: user4151568 on Oct 28, 2011 8:55 AM
Edited by: user4151568 on Oct 28, 2011 8:55 AM

Hi,
Use the below link to upgrade from 10.3.5 to 10.3.6
https://gdgprasad.wordpress.com/2014/05/03/how-to-upgrade-web-logic-server-wls-10-3-5-to-10-3-6-in-windows-64-bit/
http://docs.oracle.com/cd/E24902_01/doc.91/e18840/upgrade_1036.htm#EOHWL193
How Can I Download Upgrade Installers for Oracle WebLogic Server (WLS)? [ID 1074946.1]
First try to upgrade your test Environment and then you can see if you face any issue or not.
Hope it helps

Steps to upgrade from Weblogic Portal 8.1 to Webcenter Portal 11.1.1.6

Currently I'm involved in consulting for a client who has Weblogic Portal (WLP) 8.1. I'm trying to find documentation for upgrade from WLP 8.1 to Webcenter 11.1.1.6.
I found the below link but the starting point for upgrade is Oracle WebCenter 10g (10.1.3)
http://docs.oracle.com/cd/E23943_01/doc.1111/e22628/wcmap.htm
I'm not clear if I should migrate from WLP 8.1 to WLP 10.3.x and then to Webcenter or direct migration from WLP 8.1 to Webcenter is possible ?
Any pointers / links / case study would be helpful.
Thanks for the helping soul in advance.

Thank you jiri for the quick response.
Regarding your comment 'upgrade from WLP 8.1 to WLP 10.3.5 is not for free', I did some search and found that the documentation is available for upgrading from 8.1 to 10.3.4 as below :
http://docs.oracle.com/cd/E26806_01/wlp.1034/e14253/upgrade_process.htm
Also when I went to the 10.3.5 documentation library (http://docs.oracle.com/cd/E35968_01/index.htm), I found the below link (where the upgrade process points 8.1 to 10.3.4 instead of 8.1 to *10.3.5*)
http://docs.oracle.com/cd/E26806_01/wlp.1034/e14253/toc.htm
My understanding (after reading the documentation + your comment) is that we can upgrade from 8.1 to 10.3.4 but to upgrade to 10.3.5 we need to pay Oracle. Could you point me to a link which has that information ?
Thank you for your help.

Error upgrading from weblogic 7 to weblogic 10.3

We are upgrading app from weblogic 7 to 10.3. Thie app compiles ok and every page before the login is displayed successfully. When we try to login we are getting the following error:
Exception in thread "main" java.lang.AbstractMethodError: weblogic.xml.schema.binding.BeanCodecBase.getCompositor()Lweblogic/xml/schema/binding/ModelGroupCompositor;
     at weblogic.xml.schema.binding.BeanCodecBase.gatherContents(BeanCodecBase.java:299)
     at weblogic.xml.schema.binding.CodecBase.serializeFill(CodecBase.java:297)
     at weblogic.xml.schema.binding.CodecBase.serialize_internal(CodecBase.java:234)
     at weblogic.xml.schema.binding.CodecBase.serialize(CodecBase.java:193)
     at weblogic.xml.schema.binding.RuntimeUtils.invoke_serializer(RuntimeUtils.java:192)
     at weblogic.xml.schema.binding.RuntimeUtils.invoke_serializer(RuntimeUtils.java:178)
     at weblogic.webservice.core.DefaultPart.invokeSerializer(DefaultPart.java:335)
     at weblogic.webservice.core.DefaultPart.toXML(DefaultPart.java:304)
     at weblogic.webservice.core.DefaultMessage.toXML(DefaultMessage.java:651)
     at weblogic.webservice.core.ClientDispatcher.send(ClientDispatcher.java:209)
     at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:146)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:473)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:459)
     at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:306)
     at com.workscape.aws.examples.weblogic.clientclases.PINService_PortType_Stub.authenticateUser(Unknown Source)
could someone advise how to fix this problem?
Thanks in advance

Hi,
Your EJB 2.1 application should deploy and run fine on WLS 10.3 without modification.
- Matt

Upgrading from Weblogic 6.1sp5/TopLink 3.6.3 to Weblogic 8.1/TopLink 9.0.4

Hi.
We are doing the migration from Weblogic 6.1sp5/TopLink 3.6.3 to Weblogic 8.1 & TopLink 9.0.4
We have been reading available documentation and started the migration. We have not had any problems with package ranaming issues and XML DOCTYPES changes.
As we do have a lot of ammedmed querys, we do prefer to use a java class as our proyect mapping descriptor rather than a huge XML.
We are currently porting all our querys to the new system.
As we are doing a lot of changes we are also updating our EJB 1.1 entity beans to EJB 2.0 (maybe in the future we will deploy our EJBs with local interfaces too).
The main problem we are facing right now is with all the querys we had in our toplink-cmp-<bean>.xml files. Even if most of the finders are "REDIRECT" querys that had to be ammendmed we have a good number of "EXPRESSION"s on them.
As far as we are able to see we should move them to the TopLink Project java file in the querys section. The question is: is it possible to declare them in the ejb-jar.xml file into the <ejb-ql> tag (we have seen that the TopLinkImplemented string appears on the <ejb-ql> telling the container who should handle the query, so if Weblogic can be "tricked" to do that "ejb-ql" it may be possible to do the same with a TopLink expression isn't it?.
Another issue we don't have clear is if now all the querys must be either ejb-ql (compliant with the EJB 2.0 standard) or named querys (either TopLink expressions or SQL querys) defined in the TopLink Project java or XML files. What happened with the redirect querys
I would like to point just another issue we have "solved" but we are not really satisfied with how we solved it.
We are using timestamp locking with our entity beans. The shouldBindAllParameters is set to true too and we have the logging activated so we have been able to track down the problem.
The problem seems to be something like this.
You create a new entity bean and TopLink issues a sentence like this against the DB (Oracle 8.1.7 I must say we have also configured the login session to use the Oracle8PlatformSupport)
INSERT INTO FOO(OID,OCA) VALUES (?, ?)
bind => [1, 2004-04-26 13:16:45.251]
As far as we know Oracle 8.1.7 doesn't store the milliseconds (we are using DATE type in Oracle tables) so the ".251" value is stored as "0"
Then we try to delete the entity bean and TopLink sends this sentence to the database:
DELETE FROM FOO WHERE ((OID = ? AND OCA = ?))
bind => [1, 2004-04-26 13:16:45.251]
Then, a TOPLINK-5003 (the object has been modified or deleted since last read) is raised and the transaction is rolled back.
We tried without binding and it works perfect (it seems that the timestamp is treated as YYYY-MM-DD SSSSS in the "to_date" function issued)
As we would like to keep with binding all parameters in order to optimize our database accesses we have changed the default jdbc driver (sun.jdbc...) that is showed when reading the proper property of the login sesion with the oracle.jdbc.driver.OracleDriver. This latest driver seems to solve the problem with the reminders of the timestamps but this brings us a doubt.
If we have configured two datasources in our Weblogic's config.xml file (one for transactional operations, beeing that one also an XA driver as we need to coordinate RDBMS operations with a JMS service, and the other one being a "standar" oracle.jdbc.driver.OracleDriver) why is that the driver used as default by the login method is that "weird" sun.jdbc... driver? Shouldn't TopLink use one (the XA driver I hopefully) of the drivers defined in Weblogic's datasource?
1. Is the issue we are seeing with the timestamp a known bug/problem?
2. Is there a better way to solve it than changing the driver (we are affraid of the "new" issues changing it could raise)
I have seen that with TopLink 3.6.3 and the "default" driver used in the login (it is the same by default on both TopLink 3.6.3 and TopLink 9.0.4) the binded timestamp are "truncated" to the second resolution and it works without any problem.
Thanks in advance.
Ignacio

Not sure on all of the issues, but can provide some information on some of them.
Re-directors:
Support was added for re-director to core queries, so now your named queries can make use of re-director if they require advanced dynamic execution. So all re-director queries can become named queries.
Timestamp locking:
In general we would always suggest numeric version locking if you have the choice. I'm not clear on what you are saying about the driver having an effect on the problem, however in general Oracle 8 does not support milliseconds, if you use timestamp locking with local timestamps they will have milliseconds and the database values will not match the ones in memory.
To resolve this you can,
- Use server timestamps TimestampLockingPolicy.useServerTime()
- Clear the timestamp's milli/nano second value through an aboutToInsert event.
- Extend Oracle8Platform.convertObject to clear the timestamp's milli/nano second value.
- If you can use Oracle 9 or 10 there is now a TIMESTAMP type that does support milliseconds.
If a different driver seems to be solving this, it is most likely the database ignores the milliseconds in the comparison, but the driver you are using sends the millisecond to the database incorrectly when binding.

How to upgrade from weblogic 10.3.5 to 10.3.6

Hello I have been deployed three Weblogic domains across two Windows servers 2008 R2, one domain host oracle business intelligence publisher, one domain host JEE enterprise applications and one domain will host Oracle form and Oracle report.
My JEE applications are supposed to be deployed on WEBLOGIC 10.3.6 since the first thing I did was installed ORACLE BUSINESS INTELLIGENCE PUBLISHER following Oracle recommendation which is to run setup.exe enterprise install for new installation on the first Windows server and run setup.exe enterprise install scale out out on the second server,
I hoped the installer was installed weblogic server 10.3.6 but instead was installed WebLogic Server 10.3.5.0; The version Of BI_PUBLISher standalone I installed is 11.1.1.7.0, according the certification Matrix this version on Windows 2008 R2 is certified for Oracle JDK 1.6.0_35+ for WEBLOGIC 10.3.5.0 and Oracle JDK 1.7.0_07+ for weblogic 10.3.6 I do not underatnd why the installer installed Windows 10.3.5 rather than 10.3.6.
My question is can I upgrade to WEBLOGIC 10.3.6 and Oracle JDK 1.7.0_07+, if yes could you explain to me the procedure...

check this Installing and Setting Up Oracle BI Applications
Prerequisite to Running the Business Analytics Applications Suite Installer
Make sure you have met the following prerequisites before you run the Business Analytics Applications Suite installer:
The installer is a generic installer and requires JDK or JRockit to be installed. See Section 3.2.1, "Installing JDK or JRockit," for more information.
35 GB free disk space is required to run the Business Analytics Applications Suite installer. This disk space will be released after the installer finishes.
To run the Business Analytics Applications Suite installer:
Launch the Business Analytics Applications Suite installer by entering the following:
The Business Analytics Applications Suite installer displays the Welcome screen.
Platform
Command
Windows
In a command prompt:
setup.exe -jreLoc <Drive:\...\jdk or jrockit location>
Where jdk or jrockit location is the directory that contains the bin folder.
For example:
setup.exe -jreLoc C:\jdk
UNIX and Linux
./runInstaller -jreLoc <jdk or jrockit location>
Note: If you are running the installer on a Linux machine that does not have the file /etc/oraInst.loc, the Specify Inventory Location screen will display. For information about this screen, see Section B.1, "Specify Inventory Location."
open a new thread for new issues please

Options for upgrading from weblogic 10.3.0 for 'workshop' applications?

We have a few upgraded Workshop applications that we need to keep running and don't want to have to rewrite - they are successfully deployed on a 10.3.0.0 server. As of 10.3.1 Oracle seems to have dropped all support for workshop. Is there a way to upgrade the 10.3.0.0 server such that the apps will run, or to run these apps on a 10.3.2 or later server? If so, does documentation exist? Thanks!

hi,
Even i want to connect webspere MQ 7 with weblogic 10.3, can u suggest me some document where i can follow step by step?
I have too tried using some binding file,but it is not reading the same.

Appc error when upgrade from weblogic sp5 to sp6

Hi,
I got an appc compilation error for an Entity Bean. It is exactly the same code. the generated xxxx__WebLogic_CMP_RDBMS.java compiles in weblogic8.1sp5. After upgrading to sp6, I got the following error for "cannot resolve symbol
symbol : method setStringForClob (int,java.lang.String)
location: interface oracle.jdbc.OraclePreparedStatement".
I checked the generated java code. addition code is generated on sp6 which reference to oracle.jdbc.OraclePreparedStatement.setStringForClob().
The databased used is oracle 9i. driver is oracle shipped ojdbc14.jar for 9i. If I change to 10g driver, it compiles of course. But we don't have plan to upgrade the driver.
Would someone help me find what is wrong.
Thanks alot
JC

any ideas about this problem?? i am getting the same error. is it a bug in the weblogic sp 6??
Thanks,
Raj

Upgrade From Weblogic 9.1 to Weblogic 10

Hi,
I am planning to make such an upgrade soon. I am interested in few things about W10. I have a complex enough EJB application but with a single domain configuration. I also have a EJB2.1 application and I target the same EJB version on W10.
a) what the are available W10 subversions and which are the major differences between each?
b) Java EE version is changed between W9 and W10? I am on JDK5 on W9. Is JDK6 supported in W10?
c) I will have to change all the deployment descriptors?
d) What other configuration changes are there in W10 comparing with W9 - domain folder changes, configuration file changes for JDBC, JMS etc?
e) What the the "known" problematic areas of such an upgrade?
Does anybody has experience with such kind of an upgrade?
What is the best approach to follow?
Sorry that I am asking so many questions and thanks in advance for whatever answer.
Doru

I figured it out.
There is a parameter in setDomainEnv.cmd file 'WLS_STDOUT_LOG' .If you set this as an enviroment variable with the
value equal the name and path of the file.The console logs and all the system .out statements will go to the file you mentioned
ias the value of the environment variable.

Upgrading from weblogic 8.1 to 10gr3 facing problem with the Building

Internal compiler error
java.lang.NullPointerException at org.eclipse.jdt.internal.compiler.lookup.ReferenceBinding.binarySearch(ReferenceBinding.java:108)
     at org.eclipse.jdt.internal.compiler.lookup.ParameterizedTypeBinding.getMethods(ParameterizedTypeBinding.java:542)
     at org.eclipse.jdt.internal.compiler.lookup.Scope.findMethod(Scope.java:1069)
     at org.eclipse.jdt.internal.compiler.lookup.Scope.getMethod(Scope.java:2072)
     at org.eclipse.jdt.internal.compiler.ast.MessageSend.resolveType(MessageSend.java:428)
     at org.eclipse.jdt.internal.compiler.ast.CastExpression.resolveType(CastExpression.java:460)
     at org.eclipse.jdt.internal.compiler.ast.LocalDeclaration.resolve(LocalDeclaration.java:187)
     at org.eclipse.jdt.internal.compiler.ast.AbstractMethodDeclaration.resolveStatements(AbstractMethodDeclaration.java:428)
     at org.eclipse.jdt.internal.compiler.ast.MethodDeclaration.resolveStatements(MethodDeclaration.java:195)
     at org.eclipse.jdt.internal.compiler.ast.AbstractMethodDeclaration.resolve(AbstractMethodDeclaration.java:402)
     at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.resolve(TypeDeclaration.java:1084)
     at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.resolve(TypeDeclaration.java:1165)
     at org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.resolve(CompilationUnitDeclaration.java:366)
     at org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.analyseCode(CompilationUnitDeclaration.java:102)
     at org.eclipse.jdt.internal.compiler.Compiler.process(Compiler.java:626)
     at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:392)
     at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile(AbstractImageBuilder.java:362)
     at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.compile(BatchImageBuilder.java:174)
     at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile(AbstractImageBuilder.java:299)
     at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.build(BatchImageBuilder.java:59)
     at org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll(JavaBuilder.java:269)
     at org.eclipse.jdt.internal.core.builder.JavaBuilder.build(JavaBuilder.java:177)
     at com.bea.wstudio.javabuilderx.JavaBuilderX.build(JavaBuilderX.java:66)
     at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:624)
     at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
     at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:166)
     at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:197)
     at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:247)
     at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
     at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:249)
     at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:302)
     at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:334)
     at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:137)
     at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
     at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
     Utilities/src/com/att/edb/dppco/util     ErrKey.java     line 0     1247660099328     104158
i am using jdk160_05 as standard VM
checked with jrockit_160_05 as an Standard VM, when building i am getting the same above error
can anybody help me on this

hmm so are you compiling your old 8.1 code in WLS 10.3 and getting the error during compilation?
I found similar issue reported before:-
Re: Running Eclipse with Jrockit issues

Weblogic upgrade from 8.1 to 10.3.6 - Apache Beehive

Hi
We are trying to upgrade from Weblogic 8.1 to 10.3.6, the applications use Apache Beehive.
Would like to know if Weblogic 10.3.6 supports Apache Beehive Integration. Tried to do a Proof of concept, the beehive control objects are not getting set and because of it I am getting null pointer exception.
Rgds
Srini

Hi Srini,
it supports but you need to upgrade correctly.
follow this link
Beehive Applications
after upgrade if you found some error like classnotfound error.
If those are the errors you were also experiencing, then please follow one of these options to resolve this issue:OPTION
1:Identify all the JARs that contain the beehive classes and explicitly add the jar files to the classpathOPTION
2:When you created the domain (if you used the Config Wizard), do you make it a "Workshop" domain? If not, try that.That should deploy the Workshop framework (Beehive controls, NETUI, etc) libraries as shared libraries. Then these libraries should be referenced in your applications weblogic.xml and weblogic-application.xml.
regards,
Kal

Deployment error while upgrading from WLS6.1 to WLS9.1

We are upgrading from Weblogic 6.1 to Weblogic 9.1.
We are facing with two issues while upgrading.
1. We are having a start up servlet and that servlet uses Database appender and uses log4j. This class is inside a jar file and this jar is part of the ear file.
The admin server starts but with the following error.
log4j:ERROR Could not create an Appender. Reported error follows.
java.lang.ClassNotFoundException: com.tuiuk.greenfield.foundation.logging.log4j.Dat
abaseAppender
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericCla
ssLoader.java:222)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoa
der.java:195)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoa
der.java:130)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:164)
at org.apache.log4j.helpers.Loader.loadClass(Loader.java:160)
at org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:
164)
at org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.
java:140)
at org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigur
ator.java:153)
at org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMCon
figurator.java:415)
at org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:384)
at org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:783)
at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:66
6)
at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:61
6)
at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:60
2)
at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConver
ter.java:460)
at org.apache.log4j.LogManager.<clinit>(LogManager.java:113)
at org.apache.log4j.Category.getInstance(Category.java:514)
at org.apache.commons.logging.impl.Log4JCategoryLog.<init>(Log4JCategoryLog
.java:104)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorA
ccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingCons
tructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImp
l.java:525)
at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImp
l.java:272)
at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImp
l.java:246)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:395)
at com.bea.console.preferences.spi.FilePreferencesProvider.<clinit>(FilePre
ferencesProvider.java:53)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:164)
at com.bea.portlet.prefs.spi.ProviderFactory.createInstance(ProviderFactory
.java:78)
at com.bea.portlet.prefs.spi.ProviderFactory.setDefaultProviderClass(Provid
erFactory.java:47)
at com.bea.portlet.prefs.spi.IPreferenceStore$Factory.registerDefaultProvid
er(IPreferenceStore.java:128)
at com.bea.netuix.servlets.manager.SingleFileServlet.init(SingleFileServlet
.java:113)
at javax.servlet.GenericServlet.init(GenericServlet.java:256)
at weblogic.servlet.AsyncInitServlet.initDelegate(AsyncInitServlet.java:94)
at weblogic.servlet.internal.WebAppServletContext$AsyncInitRequest.run(WebA
ppServletContext.java:1641)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManage
rImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
log4j:ERROR Could not parse input source [org.xml.sax.InputSource@5d8e63].
java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:396)
at org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.
java:141)
at org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigur
ator.java:153)
at org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMCon
figurator.java:415)
at org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:384)
at org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:783)
at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:66
6)
at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:61
6)
at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:60
2)
at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConver
ter.java:460)
at org.apache.log4j.LogManager.<clinit>(LogManager.java:113)
at org.apache.log4j.Category.getInstance(Category.java:514)
at org.apache.commons.logging.impl.Log4JCategoryLog.<init>(Log4JCategoryLog
2. The second error is
The managed server starts without any problem. Using the appication, we connect to 3rd party library to validate payment details. This 3rd party jar is also part of the ear file.
Basically the ear contains all the ejb jars, 3rd party jars and war files.
In this case we are getting the following error.
com.tuiuk.greenfield.template.navigation.web.handler.GreenfieldExceptionHandler
com.tuiuk.greenfield.foundation.exception.GreenfieldRuntimeException: Locating the PaymentManager Nested exception is:
     java.rmi.RemoteException: EJB Exception: ; nested exception is:
     java.lang.NoClassDefFoundError: com/datacash/logging/LogListener
com.tuiuk.greenfield.foundation.exception.GreenfieldRuntimeException: Locating the PaymentManager Nested exception is:
     java.rmi.RemoteException: EJB Exception: ; nested exception is:
     java.lang.NoClassDefFoundError: com/datacash/logging/LogListener
java.rmi.RemoteException: EJB Exception: ; nested exception is:
     java.lang.NoClassDefFoundError: com/datacash/logging/LogListener
     at weblogic.ejb.container.internal.EJBRuntimeUtils.throwRemoteException(EJBRuntimeUtils.java:95)
     at weblogic.ejb.container.internal.BaseEJBObject.handleSystemException(BaseEJBObject.java:713)
     at weblogic.ejb.container.internal.BaseEJBObject.handleSystemException(BaseEJBObject.java:681)
     at weblogic.ejb.container.internal.BaseEJBObject.postInvoke1(BaseEJBObject.java:447)
     at weblogic.ejb.container.internal.StatelessEJBObject.postInvoke1(StatelessEJBObject.java:72)
     at weblogic.ejb.container.internal.BaseEJBObject.postInvokeTxRetry(BaseEJBObject.java:374)
     at com.tuiuk.greenfield.service.payment.datacash.ejb.PaymentServiceEJB_hlf8l4_EOImpl.getCardType(PaymentServiceEJB_hlf8l4_EOImpl.java:288)
     at com.tuiuk.greenfield.template.orchestration.book.PaymentImpl.getCardType(PaymentImpl.java:190)
     at com.tuiuk.greenfield.template.orchestration.book.BookOrchestratorImpl.getCardType(BookOrchestratorImpl.java:2044)
     at com.tuiuk.greenfield.template.navigation.web.action.book.CheckPaymentCardAction.executeAction(CheckPaymentCardAction.java:109)
     at com.tuiuk.greenfield.template.extension.navigation.struts.action.BaseAction.execute(BaseAction.java:202)
     at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
     at com.tuiuk.greenfield.template.navigation.web.processor.book.BeachBookRequestProcessor.processActionPerform(BeachBookRequestProcessor.java:81)
     at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
     at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
     at com.tuiuk.greenfield.brand.th.navigation.action.THUserInterfaceFactory.doPost(THUserInterfaceFactory.java:105)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165)
     at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:493)
     at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:245)
     at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1069)
     at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:455)
     at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
     at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
     at com.tuiuk.greenfield.brand.th.navigation.action.THUserInterfaceFactory.doPost(THUserInterfaceFactory.java:105)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165)
     at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:493)
     at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:245)
     at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1069)
     at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:455)
     at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
     at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
     at com.tuiuk.greenfield.brand.th.navigation.action.THUserInterfaceFactory.doPost(THUserInterfaceFactory.java:105)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165)
     at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:493)
     at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:245)
     at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1069)
     at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:455)
     at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
     at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
     at com.tuiuk.greenfield.brand.th.navigation.action.THUserInterfaceFactory.doPost(THUserInterfaceFactory.java:105)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3150)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1973)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1880)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1310)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
Caused by: java.lang.NoClassDefFoundError: com/datacash/logging/LogListener
     at com.tuiuk.greenfield.service.payment.datacash.ejb.PaymentManagerEJB.getPreAuthorisationFacade(PaymentManagerEJB.java:255)
     at com.tuiuk.greenfield.service.payment.datacash.ejb.PaymentManagerEJB.getCardType(PaymentManagerEJB.java:158)
     at com.tuiuk.greenfield.service.payment.datacash.ejb.PaymentServiceEJB_hlf8l4_EOImpl.getCardType(PaymentServiceEJB_hlf8l4_EOImpl.java:274)
     ... 66 more
I have added explicitly this 3rd party jar in to the manifest file of the ejb jar that is looking for this jar.
Can you please throw some light in to this.

Hi Sebastiaan,
which database version are you using?
Anyway I would suggest that you get in contact with your DBA and he with Oracle Support.
Based on the bug description this error has something to do with your database and DBMS_STATS (used to calculate statistics for your data) and not really with APEX itself.
Oracle Support should be able to help you to find out which database patch you have to install.
Regards
Patrick
My Blog: http://www.inside-oracle-apex.com
APEX Plug-Ins: http://apex.oracle.com/plugins
Twitter: http://www.twitter.com/patrickwolf

Query about the steps for Weblogic Server Upgrade from 8.1 to 10.3

Hi!
We have planned to upgrade our Weblogic Server from 8.1 to 10.3. Could anyone advise me:
1. How to upgrade the Weblogic Server from 8.1 to 10.3? Can the Weblogic Server 10.3 coexist with the Weblogic Server 8.1 in one physical server?
2. Where can the upgrade software be downloaded?
3. We have a web service currently running under Weblogic Workshop as the Weblogic Server is started via the workshop. Can this web service be run under Weblogic Server 10.3?
4. Are there any foreseeable issues/problems that will happen?
Please kindly help me. Thanks a lot.
Best Regards
May

Download location: http://www.oracle.com/technology/software/products/ias/htdocs/wls_main.html
You can upgrade the domain after you install wls 10.3 using QuickStart.
When we migrated we have moved from windows to linux. We have installed, created domain, created managed servers, configured, etc. from scratch. We didn't face any 'show stopper' issues.

Weblogic upgrade from 8.1 to 10.3.6 - WLW_IDE.jar issue

Hi
We are in the process of upgrading our applications from Weblogic 8.1 to 10.3.6. Since WorkShop IDE has been decommissioned since Weblogic 10.3.2 we don't have the WLW_IDE.jar any more in the fusion middleware installation. The build is dependent on this JAR. Would like to know if there is an alternative to WLW_IDE.jar which can be used to make the build or how we can remove the dependency on WLW_IDE.jar - we don't want to rewrite the code.
<taskdef name="wlwBuild" classname="workshop.core.WlwBuildTask" classpath="${weblogic.home}/workshop/wlw-ide.jar"/>
<target name="build">
    <wlwBuild work="${app.dir}/${work.file}" serverclasspath="${server.classpath}">
       <build outputdir="${output.dir}" outputfilename="${output.file}"/>
    </wlwBuild>
</target>
Rgds
Srini

Hi Srini,
it supports but you need to upgrade correctly.
follow this link
Beehive Applications
after upgrade if you found some error like classnotfound error.
If those are the errors you were also experiencing, then please follow one of these options to resolve this issue:OPTION
1:Identify all the JARs that contain the beehive classes and explicitly add the jar files to the classpathOPTION
2:When you created the domain (if you used the Config Wizard), do you make it a "Workshop" domain? If not, try that.That should deploy the Workshop framework (Beehive controls, NETUI, etc) libraries as shared libraries. Then these libraries should be referenced in your applications weblogic.xml and weblogic-application.xml.
regards,
Kal

Upgrading a project from Weblogic Integration 8.1.3 to Weblogic Integration

Can anyone offer any advice to assist me in upgrading a project from Weblogic Integration 8.1.3 to Weblogic Integration 9.2.1?
Here are some nuances of the project:
* The JNDI, JDBC, & JMS server resources are secured; access is controlled by Deployment Descriptor run-as/security-role/... tags and custom CSPs
* The application is currently build for deployment using wlwBuild ant task (class in workshop.core.WlwBuildTask which is located in the 8.1.3 {weblogic.home}/workshop/wlw-ide.jar - so far I can't find this class/task in my 9.2.1 install)
* The following are the application characteristics (and utilized WLI features): multiple web apps, EJBs, JMS, Page flow/netUI, web services, WLI controls (process, java, transformation), XMLBeans
* One of the project goals is to not make any functional changes and modify as little code as necessary (the only expected justification for a modification is a) fallout out from the JVM 1.5 upgrade or b) something is no longer available in WLI 9.2)
I know there is a edocs page with a tutorial for upgrading from 8.1.4 or 8.1.5 to 9.2, but I am interested in knowing if anyone has insight on upgrading directly from 8.1.3?
Thanks in advance for any and all assistance.
Regards,
Andy Frank

just as a followup to my original message.. regarding the 8.1.4 install log that had all the warnings with the msi it expected and the different one it found... at the bottom of the log..this is what I got;
Property(S): SourcedirProduct = {AC76BA86-7AD7-1033-7B44-A81300000003}
MSI (s) (6C:30) [11:11:23:828]: Product: Adobe Reader 8.1.4 - Update 'KB408682' installed successfully.
MSI (s) (6C:30) [11:11:23:828]: Product: Adobe Reader 8.1.4 -- Installation operation completed successfully.
when i go into adobe reader -> help -> about i stillget 8.1.3

Upgrading from weblogic 10.3.0.0 to 10.3.2.0?

Similar Messages

Maybe you are looking for