R12 Upgrade Path Advice (RHEL 3)

Dear All,
I would like you to provide me some input on R12 upgrade.
Our current setup is
OS: Red Hat Linux AS 3.0 32-bits
EBS: 11.5.10.2
DB: 10.2.0.4
New setup
OS: Red Hat Linux 6.x 64-bits
EBS: 12.1.3
DB: 11.2.0.3
I have searched various notes, but can not find anything specific to it RHEL 3.0.
R12 is not supported on RHEL3.0, so I can't upgrade it on current system and then migrate it to RHEL6 system using note 471566.1.
Can you please advice me what options we have here ?.
Thanks in advance
Regards

Our current setup is
OS: Red Hat Linux AS 3.0 32-bits
EBS: 11.5.10.2
DB: 10.2.0.4
New setup
OS: Red Hat Linux 6.x 64-bits
EBS: 12.1.3
DB: 11.2.0.3
I have searched various notes, but can not find anything specific to it RHEL 3.0.
R12 is not supported on RHEL3.0, so I can't upgrade it on current system and then migrate it to RHEL6 system using note 471566.1.
Can you please advice me what options we have here ?.You do not need RHEL 3.0 and you just need to lay down R12 on RHEL 6.x 64-bit and do the upgrade from that node. The 11i node is not used during the upgrade, and there is no point of installing R12 on an OS and migrate it to a different OS.
Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.1.1) for Linux x86-64 [ID 761566.1]
Oracle E-Business Suite Upgrades and Platform Migration [ID 1377213.1]
Interoperability Notes Oracle EBS 11i with Oracle Database 11gR2 (11.2.0) [ID 881505.1]
Oracle E-Business Suite Release 12.1.3 Now Available
https://blogs.oracle.com/stevenChan/entry/ebs_1213_available
Thanks,
Hussein

Similar Messages

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

Upgrading Unity 4.0.5 to version 8 and replacing the server. Need advice for most efficient upgrade path.

Hello,
I need to upgrade Unity 4.0.5 without failover to Unity 8, and we are replacing the server as well.
What would be the most efficient upgrade path for this?
Thanks!!

Brian,
The most efficient path is to use COBRAS. I have a number of posts explaining the overall process. At the highest-level, this allows you to build out the new Unity 8x environment, get it integrated with AD/Exchange, and then build out configurations that don't migrate over (there are a few which are highlighted in the COBRAS help). From there, you migrate data over from the 4x system. There may or may not be a few steps along the way but they are outlined in numerous posts I've contributed to regarding COBRAS and also in the COBRAS Help which is located at www.ciscounitytools.com.
Hailey
Please rate helpful posts!

Not able to compile .pll or .fmb through installation file in R12 Upgrade.

While compiling .pll or .fmb individually using this command
1. frmcmp_batch module=$AU_TOP/forms/US/XXIB_I10_BA_BALEVEL.fmb userid=apps/appla1na output_file=$XXIB_TOP/forms/US/XXIB_I10_BA_BALEVEL.fmx compile_all=special batch=yes
OR
2.frmcmp_batch module=XXIB_I10_EXT_SEARCH.fmb userid=apps/appla1na output_file=$XXIB_TOP/forms/US/XXIB_I10_EXT_SEARCH.fmx compile_all=special
The file gets compiled and .plx & .fmx is generated.
Same command in .install file doesnt get compiled. Sample given below
# +======================================================================+
# Generation of English Forms
# +======================================================================+
echo "------------------------------- " | tee -a $LOG_FILE
echo "Generating Forms in English ... " | tee -a $LOG_FILE
echo "------------------------------- \n" | tee -a $LOG_FILE
export FORMS_PATH=$AU_TOP/resource:$AU_TOP/forms/US:$XXIB_TOP/forms/US:$FORMS_PATH
#exportFORMS60_PATH=$XXIB_TOP/forms/US:$AU_TOP/resource:$XXIB_TOP/resource:$AU_TOP/forms/US:$FORMS60_PATH
rmf $XXIB_TOP/forms/US/XXIB_I10_BA_BALEVEL.fmx
#commented out for R12 Upgrade by KISHAN WIPRO
#f60gen $XXIB_TOP/forms/US/XXIB_I10_BA_BALEVEL.fmb $APPS_LOGIN_ID Compile_All=YES output_file=$XXIB_TOP/forms/US/XXIB_I10_BA_BALEVEL.fmx >> $LOG_FILE 2>> $LOG_FILE
#command used to compile in R12
frmcmp_batch module=$AU_TOP/forms/US/XXIB_I10_BA_BALEVEL.fmb userid=$APPS_LOGIN_ID output_file=$XXIB_TOP/forms/US/XXIB_I10_BA_BALEVEL.fmx compile_all=special batch=yes
if [ $? -eq 0 ];
then
echo "Billed Accounts Level Form Generation successful. " | tee -a $LOG_FILE
else
echo "Billed Accounts Level Form Generation failed. \n Please check the log file for error details and re-run." | tee -a $LOG_FILE
exit 1
fi
Need some help urgent
Contact me @ [email protected]
Edited by: 862540 on Oct 2, 2011 11:23 PM

Hi,
I have tried it, by inserting it before the form compilation code the echo command works , but then while compilation it gives me an error as file not found . This file XXIB_I10_BA_BALEVEL.fmb is existing in the given path . Is it a problem with the userid being given so. As i am able to compile the file individually(During individual compilation i have hard coded the username and password), not through a installlation file . Have even checked the FORMS_PATH even thats right .
Command used in installation file :
# +======================================================================+
echo "------------------------------- " | tee -a $LOG_FILE
echo "Generating Forms in English ... " | tee -a $LOG_FILE
echo "------------------------------- \n" | tee -a $LOG_FILE
export FORMS_PATH=$AU_TOP/resource:$AU_TOP/forms/US:$XXIB_TOP/forms/US:$FORMS_PATH
#export FORMS60_PATH=$XXIB_TOP/forms/US:$AU_TOP/resource:$XXIB_TOP/resource:$AU_TOP/forms/US:$FORMS60_PATH
rmf $XXIB_TOP/forms/US/XXIB_I10_BA_BALEVEL.fmx
#commented out for R12 Upgrade by KISHAN WIPRO
#f60gen $XXIB_TOP/forms/US/XXIB_I10_BA_BALEVEL.fmb $APPS_LOGIN_ID Compile_All=YES output_file=$XXIB_TOP/forms/US/XXIB_I10_BA_BALEVEL.fmx >> $LOG_FILE 2>> $LOG_FILE
echo "Starting with compilation of English Form BA_BALEVEL"
frmcmp_batch module=XXIB_I10_BA_BALEVEL.fmb userid=$APPS_LOGIN_ID output_file=$XXIB_TOP/forms/US/XXIB_I10_BA_BALEVEL.fmx compile_all=special
if [ $? -eq 0 ];
then
echo "Billed Accounts Level Form Generation successful. " | tee -a $LOG_FILE
else
echo "Billed Accounts Level Form Generation failed. \n Please check the log file for error details and re-run." | tee -a $LOG_FILE
exit 1
fi
Not able to diagonis the error .
Regards
KISHAN.M.G

10.2.0.4 on OEL x86-64 Upgrade Path Issues

I am performing a new installation of Oracle Enterprise Manager Grid Control (OEM GC). I want to want to run Oracle Enterprise Manager 10.2.04 on Linux x86-64 - OEL 4 update 5. My installation for OMS and Repository will be on one server. I will install the database separate from the OEM GC installation.
My upgrade path is a full install of Oracle Enterprise Manager 10.2.0.3 followed by patch to 10.2.0.4. I desire to have my databases at 11g so I would have to upgrade 10gR2 database to 11g database as well. My questions are as follows:
1) Linux x86-64 is not supported on 10.2.0.3 according to certify page. Why is OEL 4 update 4,5 not on Certification page for OEM GC?
2) What installation instruction set should I follow for 10.2.0.3 GC on Linux x86-64? Linux x86-64 documentation following RHEL install?
2) Oracle 11g Repository is also not supported on 10.2.0.3. Is it possible (is it supported?) for me to install Oracle Database 11.1.0.6 EE as repository for OEM GC 10.2.0.3 then only patch OEM GC to 10.2.0.4?
Thank you.

There is no direct full installer to 10.2.0.3 Database. Do I need to do the following:
1) Install OEL 4 Update 5 x86_64
2) Meet prerequisites for Oracle Db 10.2.0.1 (x86_64 - only full installer is 10.2.0.1)
3) Patch Db to 10.2.0.2 or 10.2.0.3 (is there a reason for 10.2.0.3)
4) Install OEM GC 10.2.0.3
a) requires 10.1.0.4, 10.1.0.5, 10.2.0.2 or 10.2.0.3 database
b) use ignore system requirements parameter since OEL 4 Update 5 (x86_64) is not supported
5) I am not sure if any patches are required to OS, DB or OEM at this level
6) Patch OEM GC 10.2.0.3 to 10.2.0.4
7) I am not sure if any patches are required to OS, DB or OEM at this level
8) Follow note: 467677.1 replacing OEM GC 10.2.0.1 with my version 10.2.0.3 and upgrade db to 11g
done
Does this look correct? Is there a more efficient way?

Adobe Reader 8.1.7 upgrade path?

Could someone please explain the upgrade path to Adobe Reader 8.1.7 for me? I read the tech note "Adobe Acrobat and Reader Updating and Deployment Information" and I find myself still a little unsure.
Our most currently deployed version is 8.1.6 but some of our users still have older versions (8.1.2 ~ 8.1.5) installed. I have been distributing Adobe Reader via SMS 2003 since version 8.1.2 as below:
8.1.2 - Customized using Adobe Cusomtization Wizard 8 (Setup.exe /sPB /rs /rps)
8.1.3 - Customized using Adobe Cusomtization Wizard 8 (Setup.exe /sPB /rs /rps)
8.1.4 - Straight (installAdbeRdrUpd814_all_incr.msp /qb-! /norestart)
8.1.5 - Straight install (AdbeRdrUpd815_all_incr.msp /qb-! /norestart)
8.1.6 - Straight install (AdbeRdrUpd816_all_incr.msp /qb-! /norestart)
So what is my upgrade path for Adobe Reader 8.1.7 - straight install (AdbeRdrUpd817_all_incr.msp /qb-! /norestart) or do I need to customize it using the Adobe Cusomization wizard to retain the desired settings? Appreciate any advice that anyone can offer. Thanks very much.

Thanks for your reply Deepak. That is what I was expecting but when I read the Adobe KB cpsid_49880 (link), it had me feeling somewhat unsure as to what is correct. The "quarterly" and "security" releases and unacceptable upgrade paths.
Administrative Deployment
Due to the intentional difference between "Security" and "Quarterly" Updates, IT professionals desiring to deploy Acrobat or Reader products from an Administration Installation Point (AIP) must follow certain guidelines as noted below.
AIP Creation: Quarterly Updates cannot be applied to an AIP in which a Security Update was the most recently applied Update. Therefore, to deploy a new full Quarterly Update from an AIP, create an AIP (or use previous) which includes only Quarterly Updates.
To clarify, shown below are examples of acceptable and UNacceptable "AIP" configurations:
    Acceptable:      Acrobat 9.0.0 (Original Product) -> 9.1.0 (Quarterly) -> 9.1.1 (Security)
    Acceptable:      Acrobat 9.0.0 (Original Product) -> 9.1.0 (Quarterly) -> 9.1.2 (Quarterly)
    Unacceptable: Acrobat 9.0.0 (Original Product) -> 9.1.0 (Quarterly) -> 9.1.1 (Security) -> 9.1.2 (Quarterly)
Note, Attempting to create an AIP using the last configuration shown above will fail. The failure, however, serves to prevent a usage of updates which is not recommended by Adobe.
If I am simply installing via SMS 2003 using the command "AdbeRdrUpd817_all_incr.msp /qb-! /norestart)" do the above rules not apply (given that the end users have a 8.1.6 installed?

R12 upgrade testing

Hi all,
We have upgraded from 11.5.10.2 to R12 (12.1.3) on linux platform (rhel 4.6 to 6.2)
Can any one suggest what testing(technical) we have to go through after the R12 upgrade has been done.
Thanks

In addition to what you can find in the upgrade manual Oracle E-Business Suite Upgrade Guide the list of sanity check question would include something like the following:
- Create/Update users/responsibilities/functions/menus
- Submit different types of concurrent programs
- Ensure CM and Workflow is working as expected
- Verify OPMN components and log files
- Verify your custom tops (if any exists)
.. etc
You should come up with your own list when you upgrade your test instance and verify the same for production upgrade.
You may Google "R12 Upgrade Lesson Learned" and/or "R12 Post Technical Upgrade" and you should get many hits.
Thanks,
Hussein

Why does NFS umounts itself during R12 upgrade

Dears,
We have a problem in NFS. When our oracle team in upgrading the oracle to R12, after a certain step the NFS umounts, from the client side the error as below,
Jun 23 10:16:53 bananadev01 nfs: [ID 733954 kern.info] NOTICE: [NFS4][Server: appledev01][Mntpt: /u02]NFS server appledev01 not responding; still trying
Jun 23 10:19:57 bananadev01 nfs: [ID 559769 kern.info] NOTICE: [NFS4][Server: appledev01][Mntpt: /u02]NFS server appledev01 ok
Jun 23 10:22:57 bananadev01 nfs: [ID 733954 kern.info] NOTICE: [NFS4][Server: appledev01][Mntpt: /u02]NFS server appledev01 not responding; still trying
On the server, there aint any error related to NFS.
Any help ?

Hi Murali,
We have a 11.5.10.2 instance with 10.2.0.5 database and we are Planning to upgrade the database to 11.2.0.3 during our upgrade R12.1.1, as per the note 761570.1, we have the Patch C and Path D available to us. We have decided to use the path C i.e upgrade the database to 11.2.0.3 during the R12 upgrade itself and no two downtime windows. As per this note 761570.1, in path c If the database upgrade is part of the R12 upgrade, perform all the steps in the Interoperabity Notes except the following steps:
Verify software versions
Run adgrants.sql
Implement and run Autoconfig
Re-create grants and synonyms
Restart Applications server processes
Apply Oracle Human Resources (HRMS) patch 7721754
so does that mean we don't have to apply any patches mentioned under Verify software versions like Interoperability patch , ATG Patch 7456837 etc.. on 11i ?
If you are planning to upgrade the database in the same downtime window of R12 upgrade, then you do not need to apply the patches under "verify software versions" section in the 11i doc. However, you need to consider applying the patches under the same section in (Interoperability Notes EBS R12 with Database 11gR2 [ID 1058763.1]). Those patches should be applied before you release the R12 instance to the users.
Thanks,
Hussein

Upgrade path from Adobe Flash Media Streaming Server 3.5 to Adobe Media Server 5 Professional

Hi All,
We are currently using Adobe Flash Media Streaming Server 3.5 for streaming video via flash. We want to upgrade this to Adobe Media Server 5 Professional.
I would like to understand the complete upgrade path and any specific pre-caution that I may need to take for existing videos.
Please direct me if you there already exists some support material or let me know if any specific details may be required.
Regards,
Amresh

FMS isn't reall suiatable for serving a website or CMS. I suppose you -could- use the included Apache installation to handle your HTTP traffic, but it would require installing a database, an application server, and whatever else you would need. You'd then need to maintain the installation yourself... FMS doesn't have any sort of package manager to handle updating Apache or anything else you might want to attach to it.
I think you'd be better off using a package manager like Plesk or Cpanel, and let it take care of your httpd server and supporting services. My advice is to just use FMS for purposes that specifically call for it.

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.

11i to R12 upgrade

Hi,
I am doing test upgrade 11.5.10.2 to 12.1.1
I am following R12 upgrade guide and 1211 install guide. I finished rapid install step "Creating the Upgrade File System". Now my next step is to perform upgrade (apply upgrade drivers).
It is not clear in the documents and patch readme if I need to apply patches to 11i APPL_TOP or newly created R12 file system. Can somebody help me?
Thanks.

Which document says I need to apply only database driver? So far I have reviewed upgrade guide Part No. E14010-01.In the Same upgrade guide part NO:E14010-01 check the page no:73 it given as follows:
Under Section 3 "Upgrading to Release 12.1.1"
10. Run the American English upgrade patch driver (required)
Applies to 11i release level: All
TUMS step key: N/A
To bring your database to the full Oracle Applications Release 12.1.1 level, use AutoPatch to run the (American English) unified driver (u6678700.drv). It is located in $AU_TOP/patch/115/driver.
Run the driver on the administration server node on your Release 12.1.1 APPL_TOP
using the following commands:
$ adpatch options=nocopyportion,nogenerateportion
Do I need to start database in new R12 file system.Yes. All the steps mentioned under Section 3.9 onwards need to perform in the new 12.1 Oracle _home
-Rk
Edited by: rkthanga on Jul 2, 2010 1:00 PM

R12 Upgrade Report from 11i Getting Error

Hi everyone,
We are currently working an R12 upgrade project from 11.5.10 to 12.1.3. I am currently converting a report from 11i to R12 but it is erroring out when I run it in R12. Below is the log. Any help would be greatly appreciated. Thanks.
Payables: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
XXHH_APXNACHA_CHASE module: XXHH: NACHA Payment Format Chase (HHG)
Current system time is 06-DEC-2011 15:52:03
+-----------------------------
| Starting concurrent program execution...
+-----------------------------
Arguments
P_PAYMENT_BATCH='JRG120111b'
Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
American_America.US7ASCII
Enter Password:
MSG-00001: Org ID: 141
MSG-00001: After SRWINIT
MSG-00099: Inside Get_Company_Name
MSG-00099: Payment Batch = JRG120111b
MSG-00099: No reporting entity setup found.
REP-1419: 'beforereport': PL/SQL program aborted.
REP-0069: Internal error
REP-57054: In-process job terminated:Terminated with error:
REP-1419: MSG-00001: Org ID: 141
MSG-00001: After SRWINIT
MSG-00099: Inside Get_Company_Name
MSG-00099: Payment Batch = JRG120111b
MSG-00099: No reporting entity setup found.
REP-1419: 'beforereport': PL/SQL program aborted.
Report Builder: Release 10.1.2.3.0 - Production on Tue Dec 6 15:52:04 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Start of log messages from FND_FILE
End of log messages from FND_FILE
Program exited with status 1
Concurrent Manager encountered an error while running Oracle*Report for your concurrent request 3660174.
Review your concurrent request log and/or report output file for more detailed information.
Executing request completion options...
Output file size:
0
Finished executing request completion options.
Concurrent request completed
Current system time is 06-DEC-2011 15:52:06
---------------------------------------------------------------------------

It looks as though its failing in your beforereport trigger.
MSG-00099: Inside Get_Company_Name
MSG-00099: Payment Batch = JRG120111b
MSG-00099: No reporting entity setup found.
REP-1419: 'beforereport': PL/SQL program aborted.I dont believe payment batches are used anymore as they need to be done via Payment profiles and therefore you will need to use Payment Instruction ids instead. Also the setup at R12 is Mosaic
try including this. as the first statement in the Beforereport trigger. All the banks tables payment tables has changed so unless you have changed these to you will need to adjust these correctly to the R12 tables.
BEGIN
MO_GLOBAL.INIT ('SQLAP');
MO_GLOBAL.SET_POLICY_CONTEXT('S',FND_PROFILE.VALUE('ORG_ID'));
END;

R12 Upgrade Path Advice (RHEL 3)

Similar Messages

Maybe you are looking for