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

Similar Messages

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 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!

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

Upgraded from 3.0 to 3.1 and have login issues

I have a simple application that I have developed that requires a login. When I was using 3.0 there was not problem, but now with 3.1 when I first attempt to log in I get the error message below in the error log. When I do a back and try to login again, everything is fine. I can recreate the problem every time by logging out, trying to log in for the first time (getting the error), clicking the back button and then logging in again. The second time I get right in. Below is the version and the error message from the log. Has anyone encountered this behavior before?
Version: 3.1.0.00.32
[ecid: 73388049620,1] mod_plsql: /apex/ã½¦ãµ°ã±ç°±1 HTTP-404 ã½¦ãµ°ã±ç°±1: PROCEDURE DOESN'T EXIST
Thanks in advance,
Chris

Chris,
Does the login page to the development environment work properly?
Answer -> This is development. I just started working with APEX so nothing is in production.
I meant the Application Express development tools like the Application Builder, which require you to exercise a login page.
Does this one application that fails also fail if you install it into apex.oracle.com and run it there?
Answer -> I have not tried to do this.
You may wish to do this to gather more data about the problem.
What is different between this failing application and other applications you have developed that do not fail?
Answer -> This is my first application. It started as soon as I upgraded from 3.0 to 3.1
I guess this was too subtle a suggestion that you should collect more data about the problem so that you could state, for example, that all developed applications fail in this way or that only one fails, etc.
Who created that DAD? It's very non-standard -- you have a custom documents table and procedure and you aren't using the standard public user like APEX_PUBLIC_USER to connect.
When you navigate to Home>Administration>About Application Express, this is the "About Application Express" page I meant. Is that giving you this error (?):
Not Found
The requested URL /apex/ã½¦ãµ°ã€±ç°±1 was not found on this server.
Oracle-HTTP-Server/1.3.28 Server at oraweb2.nabp.net Port 7778
What is the database version and edition (xe or otherwise) ?
You may wish to open an SR with Oracle Support as something is very damaged in your installation.
Scott

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

After upgrading from Prosight V6 to V7.5 we are having issue with API's

Team,
Current version 6 of prosight upgraded to version 7.5. We are having our external webservice consumes Prosight webservice which defaulted installed under ProsightWS virtual directory. After up gradation we are running into issue in external application ,application unable to communicate to Prosight new version webservices. Fails in the time of calling in Login method itself in the psPortfoliossecturiy service.
Exception as follows:
“System.Web.Services.Protocols.SoapException: Could not create Security Token for specified User and Password at ProSight.Portfolios.WebServices.WS.psPortfoliosSecuritySOAP.Login(String sUser, String sPassword, Int32 lTimeOut) “
Our web application uses a dedicated user account to interact with Prosight webservice and it runs under windows authentication. Application build on ASP.NET 2.0 and later.
The sad part here is , our web application running perfectly with Prosight v6. :( I would appreciate if anyone could help us to resolve this issue. This is blocking our up gradation from 6 to higher version of prosight.
Thanks for your valuable time
Regards,
Jithesh

Here is the offical documentation from version 8.0 on the backward-compatability of the APIs. This document comes the version 8 installer. Not sure this helps you with the 7.5 issues, but hoping it will help:
Considerations for applications using the PPM Open API via COM
Applications which use the Primavera Portfolio Management (PPM) Open API via any interface (COM, SOAP/RCP or Document/Literal) and were developed and used with previous versions of PPM will continue to operate without the need for recompilation, as Primavera Portfolio Management 8.0 provides full binary backwards compatibility for all of the Open API interfaces. New functionality is available only to applications that are written to take advantage of such functionality.
Note however that any process can only load and use one version of the Microsoft .NET Framework. Therefore, applications developed with the .NET Framework 1.1 cannot use APIs to communicate with software developed using the .NET Framework 2.0 if this would cause the same process to need to load both versions of the .NET Framework.
This means that if any part of an application that uses the Open API which was developed using .NET Framework 1.1 communicates directly with PPM using the COM API (which is in-process), that part of the application would need to be recompiled to target the .NET Framework 2.0. If on the other hand, the application developed using .NET Framework 1.1, only communicates with PPM using SOAP RPC or Web Services (which are out-of-process) then there is no issue.
Instead of recompiling, it is usually sufficient to ”force” the existing executables to actually use the .NET Framework 2.0 instead of the native version of the .NET Framework for which they were compiled (1.1). This can be achieved by using an application config file with the following content:
<?xml version ="1.0"?>
<configuration>
<startup>
<supportedRuntime version="v2.0.50727" />
</startup>
</configuration>
The application config file can easily be created using Notepad or something similar. It does not need to be compiled in any way. It should be named with the exact same name as the executable file plus the suffix “.config”. For example: if the application executable file is called “Tester1.exe” then the config file must be named “Tester1.exe.config”. It must be placed in the same directory as the executable file.
The config file “forces” the application to use the .NET Framework 2.0, which would mean that even when using COM (in-process) Open API calls to PPM, there would still be only one version of the .NET Framework involved in the process (.NET 2.0).
----------------------------------------------------------------------------------------

Upgrade from Director 10.1 to 11.5 embedded font issues

I just upgraded to 11.5 for Mac. When I opened an existing file I developed in 10.1, the embedded fonts went bizarre. I had Times embedded and it did some strange substitutions like the "i"s are in a totally different font as are the question marks. The whole font sets were embedded. No subsetting. Can someone enlighten me as to what is going on?

One of the new features in Director 11.x is a new text engine that does Unicode. Whether it is an improvement or not is up in the air. Anyway, it has new problems. It is quite common to have embedded font problems with projects updated from Director 10. Generally, you can fix them by deleting the embedded font and re-embedding it in Director 11. Just keep the same menber name and it should be fine.

Upgrading from 11.5.10.2 to R12.1.1 issue

Hi,
We are upgrading applications from 11.5.10.2 to R12.1.1.
Database: 10.2.0.3
While applying patch u6678700.drv, the LoadMap.class job is running fo very long time.
In all the workers log file, We can see
view name "xxxxxxxxxxxxxxxxxxxxxxxx"
view does not exist in target database
Executing create statement
create statement is
Where xxxxxxxxxxxxxxxxxx is different for different workers.
In alert log file the following errors are seen
ORA-12012: \316\330\303 \335\355 \307\341\312\344\335\355\320 \307\341\302\341\355 \341\341\346\331\355\335\311 383
ORA-12008: \316\330\303 \335\355 \343\323\307\321 \312\314\317\355\317 \307\341\332\321\326 \307\341\343\307\317\355
ORA-04063: \312\346\314\317 \303\316\330\307\301 \335\355 view "APPS.AR_CONTACTS_V"
ORA-06512: \332\344\317 "SYS.DBMS_SNAPSHOT", line 2254
ORA-06512: \332\344\317 "SYS.DBMS_SNAPSHOT", line 2460
ORA-06512: \332\344\317 "SYS.DBMS_IREFRESH", line 683
ORA-06512: \332\344\317 "SYS.DBMS_REFRESH", line 195
ORA-06512: \332\344\317 line 1
Thanks

While applying patch u6678700.drv, the LoadMap.class job is running fo very long time.Please see (How to Troubleshoot "adpatch" Performance Issues: Slow, Hanging or Crashes [ID 756063.1]).
ORA-12012: \316\330\303 \335\355 \307\341\312\344\335\355\320 \307\341\302\341\355 \341\341\346\331\355\335\311 383
ORA-12008: \316\330\303 \335\355 \343\323\307\321 \312\314\317\355\317 \307\341\332\321\326 \307\341\343\307\317\355
ORA-04063: \312\346\314\317 \303\316\330\307\301 \335\355 view "APPS.AR_CONTACTS_V"
ORA-06512: \332\344\317 "SYS.DBMS_SNAPSHOT", line 2254
ORA-06512: \332\344\317 "SYS.DBMS_SNAPSHOT", line 2460
ORA-06512: \332\344\317 "SYS.DBMS_IREFRESH", line 683
ORA-06512: \332\344\317 "SYS.DBMS_REFRESH", line 195
ORA-06512: \332\344\317 line 1Does the view exist in the database?
I would suggest you log a SR and no similar issues are reported on MOS website.
Thanks,
Hussein

Upgrade from Weblogic 10.3.1 to 10.3.3 Issues

Similar Messages

Maybe you are looking for