Upgrade path 11.5.9 to R12.1.3..??

Hi All,
Our Current Environment.
OS : RHEL 4 update 8 (32 bit)
EBS Version : 11.5.9
Database :9.2.0.8
We are planning to upgrade EBS from 11.5.9 to R12.1.3. Is below path is corerect.
*Upgrade database from 9.2.0.8 to 11.1.0.7
*lay down R12.1.1 file system
* Apply R12.1.1 upgrade driver
Please help with your suggestions.
Thanks
RB
Edited by: R12DBA on May 18, 2011 10:17 PM

We are planning to upgrade EBS from 11.5.9 to R12.1.3. Is below path is corerect.
*Upgrade database from 9.2.0.8 to 11.1.0.7
*lay down R12.1.1 file system
* Apply R12.1.1 upgrade driver
Please help with your suggestions.Please refer to (Database Preparation Guidelines for an E-Business Suite Release 12.1.1 Upgrade [ID 761570.1]), Path A
Oracle Applications Upgrade Guide: Release 11i to Release 12.1.1
http://download.oracle.com/docs/cd/B53825_03/current/acrobat/121upgrade.pdf
Please note that 11i/R12 is certified with 11gR1/11gR2
Interoperability Notes Oracle EBS 11i with Oracle Database 11gR2 (11.2.0.1) [ID 1265268.1]
Interoperability Notes Oracle EBS 11i with Oracle Database 11gR2 (11.2.0.2) [ID 881505.1]
Interoperability Notes Oracle EBS R12 with Oracle Database 11gR2 (11.2.0.1) [ID 1265232.1
Interoperability Notes EBS R12 with Database 11gR2 [ID 1058763.1]
And, if you want to upgrade to 12.1.3, please refer to:
Oracle E-Business Suite Release 12.1.3 Now Available
http://blogs.oracle.com/stevenChan/entry/ebs_1213_available
Thanks,
Hussein
Thanks,
Hussein

Similar Messages

Upgrade path for 11.5.10.2 to R12.1.3

Hi All,
We are in the process of upgrading our 11.5.10.2 instance to R12.1.3. Could anyone tell me the upgrade path for this
Do we have to mandatorily upgrade first to R12.1.1 and then apply R12.1.3 MP?
Also Please confirm if we have any R12.1.3 software to install? I don't think so but just want to double confirm.
Thanks

Hi,
We are in the process of upgrading our 11.5.10.2 instance to R12.1.3. Could anyone tell me the upgrade path for this
Do we have to mandatorily upgrade first to R12.1.1 and then apply R12.1.3 MP?To upgrade 11i to R12, please refer to:
Oracle Applications Upgrade Guide: Release 11i to Release 12.1.1
http://download.oracle.com/docs/cd/B53825_03/current/html/docset.html
Database Preparation Guidelines for an E-Business Suite Release 12.1.1 Upgrade [ID 761570.1]
Oracle E-Business Suite Release 12.1.3 Now Available
http://blogs.oracle.com/stevenChan/2010/08/ebs_1213_available.html
Also Please confirm if we have any R12.1.3 software to install? I don't think so but just want to double confirm.
You need to upgrade to 12.1.1 then apply 12.1.3 Release Update Pack (Patch 9239090) -- No fresh installation software is available for 12.1.2/12.1.3
Thanks,
Hussein

R12 upgrade path

Hi All,
Does anyone have a document about R12 upgrade path. Would like to know what is the future of R12 with Fusion coming up soon.
Thanks
Srini

If you search for Apps Unlimited in www.oracle.com you will get the hits.
http://www.oracle.com/applications/applications-unlimited.html
Applications Unlimited :
Oracle commits to individual product line enhancements even after the delivery of Oracle Fusion Applications

Upgrade 11.5.10.2 to R12 Windows

Hi
I am currently planning an upgrade as follows:
FROM
Windows 2003
11.5.10.2
11.1.0.7
TO
Windows 2008
12.1.3
11.1.0.7
I would like to go down the following upgrade path:
1. Clone current environment from W2003 to W2008 using rapid clone
2. Upgrade on new server to 12.1.1 using Rapid Install
3. Upgrade to 12.1.3
I have checked the final certifications and thats all ok, however in step 1 for the clone 11.5.10.2 on W2008 is not certified with 11gR1.
So, is it still ok to go down this route when the cloned environment is not certified, even though I will be upgrading to a certified version? I would prefer not to have to upgrade the database to 11gR2 as well.
Thanks in advance.

Hi,
We were in a similar situation with a different OS, and we managed to follow the same approach (even though the target OS was not certified with 11i). We got the confirmation from Oracle support first through a SR before we proceeded with this approach (clone + upgrade). So, please log a SR to confirm for your OS.
Some other certified approaches would be upgrading on the source node then clone the R12 instance. Or, install the same OS of the source node on the target node, do the clone and the upgrade, then upgrade the OS.
Thanks,
Hussein

Upgrade plan for e business suite r12.0.6 on 10.2.0.3

hello all,
i am planning to upgrade our existing set i.e. e business suite r12.0.6 running on 10.2.0.3.
i like to first apply on clone database to test and verify the procedure.
for that i have created close database on same machine.
machine 1:
/data1/PROD --- prod directory represent production database
/data1/DEV -- dev directory represent testing database.
my question are follow
1. it is ok if i upgrade 11gr2 on dev in same machine, will it effect my existing PROD database ???
2. please advice me action plan or document which help me with the step for upgrade.
OS: LINUX REDHAT 5
DB: 10.2.0.3
APPS: R12 12.0.6
thanks

Thank you for your reply husain.,
i don't have spare or another server., so i have to do testing the same machine., apart from performance is there any other impact on running production database.?
and will you please help me where to start...
i already read the notes and i have following doubts
Verify software versions
The following software component versions must exist in your environment.
Software
Minimum Version
Tier
Details
Oracle Database Enterprise Edition
N/A
Database
Read the "Determine the Upgrade Path" subsection in Chapter 2 of the Oracle Database Upgrade Guide 11g Release 2 (11.2). Make sure that direct upgrade is supported from your current release.
--> This part i understood. I m going to use DBUA. from 10.2.0.3 to 11.2.0.3
Oracle E-Business Suite
12.0.4 or 12.1.1 with 9868229, 10163753 and 11071569
Application
If you are on E-Business Suite Release 12.0, apply
Patch 6435000 - Oracle E-Business Suite 12.0.4
Patch 8623536 - 11g Release 2 interoperability patch for Release 12.0.4
Patch 9868229
Patch 7303030 - Oracle E-Business Suite 12.1.1
Patch 9062910 - 11g Release 2 interoperability patch for Release 12.1
Patch 8919489 - 12.1 TXK Delta 3 patch
Patch 9868229
Patch 10163753
Patch 11071569
If you are on E-Business Suite Release 12.1, apply
---> I m not clear with this part., do i need to do anything (i mean i need to apply any patches).
because we already in 12.0.6. (Please advice).
Demand Signal Repository (conditional)
12.1.2 with 9182368
Application
If you are using Demand Signal Repository (DSR), apply
Patch 7303033 - Oracle E-Business Suite 12.1.2
Patch 9182368
--> We are not using DSR so i think i can ignore this part.
Oracle Warehouse Builder (conditional)
11.2.0.1 with 9403153
Warehouse Builder Database
If you are using Oracle Warehouse Builder (OWB) 11g Release 2, apply OWB 11g Release 2 (11.2.0.1) and Patch 9403153. The following E-Business Suite Release 12 products use OWB 11g Release 2:
Oracle Demand Signal Repository (DSR)
Oracle Manufacturing Operations Center (MOC)
Oracle Balance Scorecard (BSC)
--> we are not using OWB., so i think we can ignore this part.
AutoConfig
Latest version with 9852070, 9738085, 11692965, and 12686610
Application
Implement AutoConfig or upgrade to the latest version. See Using AutoConfig to Manage System Configurations with Oracle E-Business Suite Release 12 on My Oracle Support for instructions. If you are on Oracle E-Business Suite Release 12.1, apply patches Patch 9738085 and Patch 9852070.If you are on the IBM Linux on System Z platform and on Oracle E-Business Suite Release 12.1, apply Patch 11692965.
Apply Patch 12686610 (for Oracle E-Business Suite Release 12.0 and 12.1).
---> I didn't understand this part completely, but what i understood is.. i need to apply PATCH 12686610 and to apply this patch i need to apply two more pre-req patch: (Patch R12.TXK.A.delta.7: R12.TXK.A.DELTA.7)
Daylight Saving changes
N/A
Database tier
See Complying with Daylight Saving Time (DST) and Time Zone Rule Changes in E-Business Suite 12 on My Oracle Support for instructions.
--> i didn't understand this part completely.
DirectX
9.0b
Windows customers ONLY - Database tier
On Windows, run the DirectX diagnostics tool DxDiag.exe in c:\windows\system32. If you receive a generic error opening the display adapter information, use the Windows update tool to upgrade to DirectX 9.0b.
---we can ignore becuaes we are on linux.
hope you reply.

Upgrade from SCCM 2012 SP1 CU4 to R2 Fails - Unsupported Upgrade Path

Hi everybody,
I'm currently upgrading our SCCM infrastructure to SCCM 2012 R2 after have finished with the upgrade from SCCM 2012 RTM to SP1 CU4, thus far everything works fine, but when I try to update any
of the site servers, whether CAS or Primary, I'm getting the following error message in the Prerequisites Check:
I've gone through the system requirements and prerequisites over and over again and I can assure you that every possible update, supported OS, feature set, SQL Server, check list, etc,
etc, have been followed as per the official documentation available, however I'm stuck in this point, and surely enough I haven't been able to find out a similar case.Additionally I'm adding
the ConfigMgrPrereq log (the relevant portion of it) in case someone could kindly take a look at it.
<04-25-2014 02:06:46> ******* Start Prerequisite checking. *******
<04-25-2014 02:06:47> ********************************************
<04-25-2014 02:07:00> INFO: Detected current installed build version [7711] for sitecode [BRA]. For Upgrade,
minimum supported installed build version is [7804].
<04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;
Unsupported upgrade path;    Error;
Configuration Manager has detected that one or more sites in the hierarchy are installed with a version of Configuration Manager that is not supported for upgrade.
<04-25-2014 02:07:00> INFO: This rule only apply to primary site, skip checking.
<04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;
Active Replica MP;    Passed
<04-25-2014 02:07:00> INFO: This rule only applies to primary or secondary site in hierarchy, skip checking.
<04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;
Parent site replication status;    Passed
<04-25-2014 02:07:00> <<<RuleCategory: Database Upgrade Requirements>>>
<04-25-2014 02:07:00> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
<04-25-2014 02:07:00> ===== INFO: Prerequisite Type & Server: SQL:INFPROSCCMCDB.usersad.everis.int
=====
<04-25-2014 02:07:00> <<<RuleCategory: Access Permissions>>>
<04-25-2014 02:07:00> <<<CategoryDesc: Checking access permissions...>>>
<04-25-2014 02:07:00> INFPROSCCMCDB.usersad.everis.int;
SQL Server sysadmin rights;    Passed
<04-25-2014 02:07:00> INFPROSCCMCDB.usersad.everis.int;    SQL Server sysadmin rights
for reference site;    Passed
<04-25-2014 02:07:00> INFO: CheckLocalSys is Admin of <INFPROSCCMCDB.usersad.everis.int>.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Site server computer account administrative rights;    Passed
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server security mode;    Passed
<04-25-2014 02:07:09> <<<RuleCategory: System Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
<04-25-2014 02:07:09> INFO: OS version:601, ServicePack:1.
<04-25-2014 02:07:09> INFO: Target computer is a Windows server.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Unsupported site server operating system version for Setup;    Passed
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Domain membership;    Passed
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Pending system restart;    Passed
<04-25-2014 02:07:09> <<<RuleCategory: Dependent Components>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
<04-25-2014 02:07:09> INFO: Return code:0, Major:10, Minor:50, BuildNum:4000
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server version;    Passed
<04-25-2014 02:07:09> INFO: Get Sql edition:Enterprise Edition.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server Edition;    Passed
<04-25-2014 02:07:09> INFO: Checking Tcp is enabled to Static port, SQL Server:INFPROSCCMCDB.usersad.everis.int,
Instance:.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server Tcp Port;    Passed
<04-25-2014 02:07:09> INFO: Checking if SQL Server memory is limited.
<04-25-2014 02:07:09> INFO: SQL Server memory is limited.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Configuration for SQL Server memory usage;    Passed
<04-25-2014 02:07:09> INFO: Checking if SQL Server memory is configured to reserve minimum memory.
<04-25-2014 02:07:09> INFO: Installing the central administration site or primary site, requires SQL
Server to reserve a minimum of 8 gigabytes (GB) of memory.
<04-25-2014 02:07:09> WARN: SQL Server minimum memory is 8000 MB.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;    SQL Server process memory allocation;
Warning;    Configuration Manager requires SQL Server to reserve a minimum of 8 gigabytes (GB) of memory for the central administration site and primary site and a minimum of 4 gigabytes (GB) for the secondary site. This memory is reserved by
using the Minimum server memory setting under Server Memory Options and is configured by using SQL Server Management Studio. For more information about how to set a fixed amount of memory, see
http://go.microsoft.com/fwlink/p/?LinkId=233759.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Case-insensitive collation on SQL Server;    Passed
<04-25-2014 02:07:09> INFO: Check Machine FQDN: <INFPROSCCMCDB.usersad.everis.int>.
<04-25-2014 02:07:09> INFO: getaddrinfo returned success.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Validate FQDN of SQL Server Computer;    Passed
<04-25-2014 02:07:09> INFO:CheckSupportedFQDNFormat <INFPROSCCMCDB.usersad.everis.int>
<04-25-2014 02:07:09> INFO: NetBIOS <INFPROSCCMCDB>
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Primary FQDN;    Passed
<04-25-2014 02:07:09> <<<RuleCategory: Site Upgrade Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking if the target ConfigMgr site is ready to upgrade...>>>
<04-25-2014 02:07:09> <<<RuleCategory: Database Upgrade Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
<04-25-2014 02:07:09> ===== INFO: Prerequisite Type & Server: SDK:INFPROSCCMCMS.usersad.everis.int
=====
<04-25-2014 02:07:09> <<<RuleCategory: Access Permissions>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking access permissions...>>>
<04-25-2014 02:07:09> INFO: The rule 'Administrative rights on site system' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
skipped.
<04-25-2014 02:07:09> <<<RuleCategory: System Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
<04-25-2014 02:07:09> INFO: The rule 'Unsupported site server operating system version for Setup' has
been run on server 'INFPROSCCMCMS.usersad.everis.int', skipped.
<04-25-2014 02:07:09> INFO: The rule 'Domain membership' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
skipped.
<04-25-2014 02:07:09> INFO: Windows Cluster not found on INFPROSCCMCMS.usersad.everis.int.
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;
Windows Failover Cluster;    Passed
<04-25-2014 02:07:10> INFO: The rule 'Pending system restart' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
skipped.
<04-25-2014 02:07:10> <<<RuleCategory: Dependent Components>>>
<04-25-2014 02:07:10> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;
Windows Deployment Tools installed;    Passed
<04-25-2014 02:07:10> INFO: CheckAdkWinPeInstalled on INFPROSCCMCMS.usersad.everis.int.
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;    Windows Preinstallation Environment
installed;    Passed
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;
SMS Provider machine has same domain as site server;    Passed
<04-25-2014 02:07:10> <<<RuleCategory: Site Upgrade Requirements>>>
<04-25-2014 02:07:10> <<<CategoryDesc: Checking if the target ConfigMgr site is ready to upgrade...>>>
<04-25-2014 02:07:10> <<<RuleCategory: Database Upgrade Requirements>>>
<04-25-2014 02:07:10> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
<04-25-2014 02:07:10> ***************************************************
<04-25-2014 02:07:10> ******* Prerequisite checking is completed. *******
<04-25-2014 02:07:10> ******************************************<04-25-2014 02:07:10> INFO: Updating
Prerequisite checking result into the registry
<04-25-2014 02:07:10> INFO: Connecting to INFPROSCCMCMS.usersad.everis.int registry
<04-25-2014 02:07:10> INFO: Setting registry values
If you wonder whether it might be related to this error:
-2014 02:07:00> INFO: Detected current installed build version [7711] for sitecode [BRA]. For Upgrade, minimum supported installed build version is [7804].
I confirm that this one site is a secondary one that's attached to a primary site and this log is from the CAS server, I managed to tall it and delete it from that site, but still appears listed
on the CAS management console, any idea how to force the removal of a secondary site that's attached to a primary from the CAS site when it has been removed already from said primary?
I've already tried the
Preinst /DELSITE XXX command but it only works when the site to remove it's attached to the local site and certainly not from a CAS
Finally, the version, build number and everything is correct, no idea what could be the problem, does anybody know a way to bypass this or force the re-evaluation of this rules, I've got
the impression that it's being cached somehow.
Any help would be highly appreciated,
Thank you.
Marcelo Estrada MCP-MCTS-MCITP-MCSA-MCSE

Hello again everybody,
I've finally managed to fix this up, in the end I had to delete those entries manually from the database as Garry suggested. After this was done the upgrade has gone through as expected with no further ado and has finalized already, now moving on to the
primary sites.
If anybody out there is facing the same issue, what I did was to delete those "stubborn" records executing the following statements over the CAS database:
DELETE
FROMServerDataWHERESiteCode='XXX'
DELETE
FROMSC_SiteDefinitionWHERESiteCode='XXX'
And this is pretty much about it. I'd recommend to take a proper backup first though as best practice.
Thank you all anyways for your answers and comments,
Marcelo Estrada MCP-MCTS-MCITP-MCSA-MCSE

Error Message: "This upgrade path is not supported"

Scenario
During the process of upgrade to Windows 10 Technical Preview, we may encounter the error “This upgrade path is not supported. Please close Setup and re-launch from the root of the media or go back and pick a different installation
choice.” in the Compatibility report.
Analysis
Step 1: Perform the scenario 1: the upgrade installation fails.
Reproduce this error following the steps below:
Download the Windows 10 Technical Preview ISO installation file.
Extract the ISO installation file to C:\New folder, and now the location of the installation file is
C:\New folder\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\.
Click setup.exe from the installation file, and then click
Install now.
Setup is starting, and then get two options Upgrade and
Custom which is the classic setup wizard which we can see during booting from DVD.
Click Upgrade to run upgrade installation, however, the error occurs.
It seems that it is impossible to perform upgrade installation to Windows 10 Technical Preview, although it is fine to click
Custom to perform clean installation which cannot keep the personal setting and applications.
However, what we want is upgrade installation, not clean installation.
Step 2: Perform the scenario 2: the upgrade installation works fine.
If extract the ISO installation to C:\New in the above step2, click the
setup.exe from the installation file C:\New\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\, the upgrade installation would work fine, which is as shown the following two figures:
Step 3: Check the setupact.log
file which contains information about setup actions during the installation of the two scenarios.
Scenario 1: Check the setupact.log file of the scenario 1. The detailed information is shown as below:
2014-10-14 19:03:40, Info UI Determining whether we should run ConX or legacy setup
2014-10-14 19:03:42, Info UI Will launch ConX setup experience
2014-10-14 19:03:42, Info UI Launching ConX setup experience
2014-10-14 19:03:42, Info UI Launching C:\New folder\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\Sources\SetupPrep.exe
2014-10-14 19:03:44, Info UI Unknown command line for ConX setup experience. Launching legacy setup experience.
2014-10-14 19:03:44, Info UI Determining if we are in WDS/Unattend mode
2014-10-14 19:03:44, Info UI No need to hide autorun
2014-10-14 19:03:44, Info [0x0a000a] UI Autorun:Autorun core successfully initialized!!!
2014-10-14 19:03:44, Info [0x0a000b] UI Autorun:Autorun UI successfully initialized!!!
2014-10-14 19:03:44, Info UI AppWindow has layout style 0
2014-10-14 19:03:45, Info UI NavWindow has layout style 0
2014-10-14 19:03:45, Info [0x0a011c] UI WizardDialogPost::SetActive
2014-10-14 19:04:57, Info [0x0a018e] UI Passing command line parameter ("C:\New folder\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\Sources\setup.exe /HideWelcome /uilanguage:en-US /targetlanguage:en-US") to IBS.
Scenario 2: Check the setupact.log file of the scenario 2. The detailed information is shown as below:
2014-10-14 19:08:04, Info UI Determining whether we should run ConX or legacy setup
2014-10-14 19:08:05, Info UI Will launch ConX setup experience
2014-10-14 19:08:05, Info UI Launching ConX setup experience
2014-10-14 19:08:05, Info UI Launching C:\New\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\Sources\SetupPrep.exe
According to the two logs, we can get the following points:
In scenario 1, it would invoke the SetupPrep.exe in the source folder directly to perform an installation preparation. However, it failed to recognize the path
C:\New folder\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\Sources\SetupPrep.exe. Then it would launch legacy setup.
In the scenario 2, Windows setup would be redirected to the ConX setup to perform upgrade installation automatically.
So, what is the difference of the scenario 1 and 2 to bring the different results of upgrade installation?
Workaround
Based on lots of testing, we find that if there is no space in the extracting location of the ISO installation
file, the upgrade installation would work fine.
What’s more, we can get the meaning of the two setup models in the setupact.log:
Legacy setup: it is same with setup from DVD boot.
ConX setup: it would check the compatibility and language UI for upgrade preparation, then perform migration and upgrade directly.
Additional Resource
From the release of Windows 10 Technical Preview, many users have installed and tested Windows 10 Technical Preview, we still hope more and more users would download and install Windows 10 Technical Preview for test, and provide
us your feedback.
Download Windows Technical Preview
http://windows.microsoft.com/en-us/windows/preview-iso
Download Windows Technical Preview for Enterprise
http://www.microsoft.com/en-us/evalcenter/evaluate-windows-technical-preview-for-enterprise
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Hello,
I would guess that existence of a space in the folder name is what the issue is. Try removing the space from the folder name and see if works. New_Folder for example
Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

I am trying to upgrade EPM 8.9(8.49.23) to EPM 9.1 (8.53.08). During dataconversion step the AE process finished succssfully in few seconds. When i see the log it says "There are no conversions to run for upgrade path PF89 (18028,10003)". Please let me kn

I am trying to upgrade EPM 8.9(8.49.23) to EPM 9.1 (8.53.08). During dataconversion step the AE process finished succssfully in few seconds. When i see the log it says "There are no conversions to run for upgrade path PF89 (18028,10003)". Please let me know why it didnt do any conversion. Am i missing something?

yes, that app engine didnt inserted any rows. So now when i tried to drill down i found that there was no data in the "new demo" database on table UPG_DATACONV. That is the reason for all this.
When i applied required for upgrade patch in demo it said couple of patch already exists so those update i skipped. Now when i check upd877654 has a step which imports the data in this table. my change assistant told that the update is already available in my demo so i skipped. Now i am not sure what to do.
I tried reimporting the data and running the analyzer again. But worried that there can be any issues due to this.

Windows 8.1, Update 1 upgrade path

Hi, if there is anyone of any influence who might read this, please, please, for you own sakes make an upgrade path directly from Windows 8.0 --> Windows 8.1, Update 1
I cannot upgrade from W8.0 --> 8.1.
I cannot upgrade due the the following error. But I believe it is a silly error and can be overcome as some have managed:
https://answers.yahoo.com/question/index?qid=20131018074442AAswJqp
http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_install/windows-81-install-unable-to-create-ramdisk/887b5adc-86ce-4c37-9c58-72eca5f712d4?page=8&tm=1396807793681
I even had a MS 3rd line Andswer Desk (ref:1233447567.) guy who was remote controlling my machine trying clean boot give up after saying that if my
MB manufacturer wont support drivers past Vista then there is nothing they "should" do... But Vista is EoS but not extended support as XP is, that ends 2017:
http://windows.microsoft.com/en-gb/windows/lifecycle
This is an issue I'm having with my personal PC but I also work in IT infrastructure and I think this needs to be sorted. This is going to become a BIG issue for many other people who have Vista/XP-grade systems with the requirements for 8.1.1 who will try
to upgrade.
Please can someone help?
System: Q6600, MB: XFX Nvidia Nforce 680i LT, 8GB RAM

Hi,
Windows 8.1 do have have higher requirements for hardware, If your computer hardeware device was too old, you may encounter some problem during install or using Windows 8.1.
Roger Lu
TechNet Community Support

Steps to upgrade OBIA source EBS 11 to R12

Hi,
We have a specific requirement that our EBS source got upgraded from 11.5.10 to R12.
Earlier OBIA Financial,HR Analytics is running successfully. Now we need to map it to R12 source.
Can any one had done this already please suggest required steps.
In my openion changing folders in DAC to point to R12 adaptors and changing files with latest R12 data would work.
Fyi..We haven't done any customizations in the OOB adaptor.
Thanks in advance.
Regards,
Raj
[email protected]

You will need to install 11.2.0.4 into a new ORACLE_HOME, apply the latest 11.2.0.4 PSU patch to the new ORACLE_HOME (see MOS Doc 1454618.1) and then follow the steps in the Upgrade Guide
http://docs.oracle.com/cd/E11882_01/server.112/e23633/upgrade.htm#UPGRD003
see MOS Doc 1189783.1

Upgrade Path from 5.1.4

We are currently running version 5.1.4 and are looking to upgrade. What is the recommended upgrade path or version we should be planning to go to? Our pipeline isn't very complicated since I've read some articles about there not being a direct migration to version 3.0. We currently develop using the RAD toolkit and .NET if that is a factor when upgrading.
Also if someone could clarify which packages I'm looking at migrating to as before I installed Endeca IAP and Dev Studio and I was up and running. I don't see those packages in the newer versions of the software and I'm not 100% on what the packages were renamed to after the transition to Oracle.

It sounds like you are upgrading an Endeca Commerce / Guided Search implementation. This forum is for Oracle Endeca Information Discovery (EID) products. You will get better answers over on the other forum, https://forums.oracle.com/community/developer/english/endeca_experience_management/technical_questions .

Merom / Conroe upgrade path for Intel iMac?

Has anything been released about a processor upgrade path (if possible) to take the Early 2006 IiMacs from the Yonah CPU family to Merom or Conroe?
I'm still steamed to be stuck with a 32-bit CPU (even though it is a good one, funny how that fact is still judiciously left out of all promotional materials) and wondered if I will be left high and dry in 2-3 months when the 64-bit Core 2 Duo chips ship.
It would be nice if there were an upgrade path to bring the early adopter faithful into the 64-bit realm. Anyone heard a mighty rumblin' ?

People have successfully removed the CPU and replaced it. And, the new chips are supposed to be compatible with any Yonah based system.
So, while there is no official upgrade path, it should not be a problem installing a new CPU in the machine later.
Obviously, the heat of the new chips will be a consideration. They may be hotter, they may not be.
And, it will obviously void your warranty.
But, it should be possible.

Upgrade path

we are upgrading from ACS 2.6 to 4.1
should we order the upgrade software (CSACS-4.1-WINUP-K9) or should we order the regular package (CSACS-4.1-WIN-K9)since 2.6 is so out of date?

Hi Martin,
I agree with Scott (no surprise!) One of my co-workers just went down the upgrade path (albeit from a more recent version) and it was very messy. I'm pretty sure he finally just ditched the whole plan and started fresh.
Hope this helps!
Rob

Usually there is a upgrade path for current users of the software at a reduced price. I dont see anything like that for Lightroom 6. Will I have to pay full price just to upgrade to the new LR6 standalone version???

Usually there is a upgrade path for current users of the software at a reduced price. I dont see anything like that for Lightroom 6. Will I have to pay full price just to upgrade to the new LR6 standalone version???

The standalone upgrade is 79 US Dollars.
Go to Products, select Lightroom 6, click on Buy, select Upgrade instead of Full

HT1444 The update vs. upgrade paths are very confusing. I'm running OS X v10.5.8. What upgrade products do I need in order to become current?

The update vs. upgrade paths are very confusing. I'm running OS X v10.5.8 and trying to figure out what versions I need to purchase/download in order to become current.
Thank you!

Phone the Apple Store, order a Mac OS X 10.6 DVD, and run Software Update. If your Mac supports it, buy 10.7 or 10.8 from the Mac App Store.
(70024)

Upgrade path 11.5.9 to R12.1.3..??

Similar Messages

Maybe you are looking for