Installing WCS - upgrade path

Hello, I have WCS with location version 3.0.101.0 on CD, and want to know the best path to take regarding installing and upgrading to work with my controllers. I have two WiSMs with versions 3.2.78.4 and 4.0.179.11 with about 350 access points. I know I need to upgrade the controller verisons to be the same. Should I upgrade to WCS 4.0.87.0? Do I need to upgrade in steps, or go for the latest version right off. I want to upgrade WCS before adding any controllers.
Thanks

We upgraded our WLCs to 4.0.179.8 prior to installing the WCS (installed from scratch 4.0.81.0) and had good success.
The release notes for 4.x discussed a problem if you update the WLC to 4.x while the LWAPs are connected. I remember something about the APs being unable to download the new firmware successfully which sounds like you could end up with a real mess on your hands if the APs lock up in that state.
From page 6 of the installation notes: 6 "Connecting 1100 and 1300 Series Access Points: You must install software release 4.0.179.8 on the controller before connecting 1100 and 1300 series access points to the controller."
Here is the link to the installation notes:
http://www.cisco.com/cgi-bin/Software/Tablebuild/doftp.pl?ftpfile=cisco/crypto/3DES/wireless/aironet/WLAN/4400/WLC-4.0.179.11-ReleaseNotes.pdf&app=Tablebuild&status=showC2A
In terms of AP licensing, we ran into an issue where there were no AP licenses for the WCS. However, since this was a new install of WCS 4.0, and you are performing an upgrade, your experience might be better than ours was. If you run into AP licensing issues with WCS 4.0, you may want to reference the following forum thread:
(forum user, ethiel, ended up with better information than TAC on this particular problem):
http://forums.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Wireless%20-%20Mobility&topic=General&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1ddc79a8
Finally, you may want to double check the firmware rev levels of your existing access points. Hopefully, this will not apply to you, but since you said you are running 3.x on one of your WiSMs...
Message Type : Field Notice
Title: Cisco Field Notice: FN - 62474 - LWAPP 1231 Fails to Upgrade to 4.0.155.0 with 4402 Image
URL:
http://www.cisco.com/en/US/customer/products/hw/wireless/ps430/products_field_notice09186a00806e3ac7.shtml
Posted: July 14, 2006
Summary: When a 1200, 1130 or 1240-series Access Point, with an LWAPP image installed that is prior to 12.3(11)JX, attempts to connect to a Wireless LAN Controller running 4.0.155.0 software, the Access Point may be unable to complete downloading its updated
software.
Hope this helps
- John

Similar Messages

WLSE to WCS upgrade path

Hi,
Could anybody tell me if they are aware of an upgrade path from WLSE to WCS using existing WLSE hardware? Can anybody point out the main benefits/features moving to WCS from WLSE?
Many thanks
SJ

Hi Scott,
Just the 1130-19 or 1133 are supported;
The new Cisco WCS SKU family, WCS-WLSE-UPG-K9, is now available for CiscoWorks WLSE customers that wish to migrate from CiscoWorks WLSE (Models 1130-19 or 1133) to Cisco WCS. These new SKUs are price-adjusted to make transitioning from CiscoWorks WLSE to Cisco WCS cost-effective.
All CiscoWorks WLSE conversion SKUs ship with two special conversion CDs. These CDs check to make sure that a CiscoWorks WLSE is installed prior to beginning the Cisco WCS conversion process. The software will not install if the CiscoWorks WLSE software check, performed by the conversion software, does not pass.
This SKU family supports only ***CiscoWorks WLSE hardware models 1130-19 and 1133. To find the model number of a CiscoWorks WLSE, look at the compliance label on the bottom of the chassis front bezel. ***Only CiscoWorks WLSE with a compliance label that says 1130-19 or 1133 can be converted to Cisco WCS.
Note: CiscoWorks WLSE Express (Model 1030) and CiscoWorks WLSE (Model 1105) are not supported with CiscoWorks WLSE conversion SKUs. Do not install the CiscoWorks WLSE CDs on the CiscoWorks WLSE Express (Model 1030) appliance or CiscoWorks WLSE (Model 1105). This conversion is not supported and it will not work.
Once converted, a CiscoWorks WLSE is no longer a self-contained appliance; it becomes a server that runs Cisco WCS software using RedHat Linux ES v. 4.0. The converted CiscoWorks WLSE operates as a new Cisco WCS installation and supports only lightweight access points and wireless LAN controllers that are running Lightweight Access Point Protocol (LWAPP). Autonomous access points are not supported by a converted CiscoWorks WLSE.
Customers migrating their CiscoWorks WLSE to Cisco WCS do not need to buy a copy of RedHat Linux ES v. 4.0 software. A copy of RedHat Linux ES v. 4.0 software is included with the CiscoWorks WLSE migration CDs. (RedHat Linux AS v. 4.0 is not supported by a converted CiscoWorks WLSE.)
From this good doc;
http://www.cisco.com/en/US/products/sw/cscowork/ps3915/prod_bulletin0900aecd804b4635.html
Hope this helps!
Rob

Itunes was working fine. Tries to install latest upgrade and get error message about an invalid character in the path "Program Files (x86)". PC, Win7, nothing else appears to be having same issue.

Itunes was working fine. Tried to install latest upgrade and get error message about an invalid character in the path "Program Files (x86)". PC, Win7, nothing else appears to be having same issue. Program still works, simply cannor upgrade.

Thanks b noir,
I tried this solution without success. After FixIt ran and didn't find a problem, either in looking for issues with "software upgrade" or "iTunes" it kindly offered to help me uninstall iTunes. I had thought of this as a possibilty but it seems to me that if you do that you lose a lot of "non-native-to-Apple" information you might have entered. I did this once and recovery was painfull. Is there a way to uninstall iTunes without losing all of that sort of thing? Any help would be appreciated.

Issue while installing WCS using omii.ini: Database ping failed

Hi,
I am trying to install WCS on local linux VM. I am following the document 'Oracle WebCenter Sites: Installing on Oracle WebLogic Application Server".
Following are the things I have been able to do successfully:
Install Oracle DB, create a database and then create a user for this database
Install WebLogic server, create domain, create admin server, managed server, and finally create a datasource. THe datasource connection to the DB created in step 1 above is successfull.
I downloaded the WCS installer from Oracle Website 'WebCenterSites_11.1.1.6_bp1'. I am installing using silent installer using omii.ini file.
During installation, on receiving the prompt to install CS and CAS applications, I installed them successfully via WebLogic console.
I tested the URL 'http://localhost:7001/cs/HelloCS' and it showed me the Oracle WCS 11g page.
Now, when I go back to the wcs installation terminal and hit Enter, it gives following error:
[2013-07-11 01:32:21.861][CS.INSTALL][INFO] 1. If your platform requires you to manually deploy the Sites application, deploy Sites now. Otherwise, continue with step 2 2. Restart your application server. 3. Test the URL http:////HelloCS to see if application is deployed successfully 4. If the test is successful, press ENTER. URL http://localhost:7001/cs/HelloCS [2013-07-11 01:41:16.841][CS.INSTALL][INFO] CSSetupEngine.testConnectionAction: Testing user configuration and database connectivity. [2013-07-11 01:41:17.118][CS.INSTALL][INFO] CSSetupEngine.postURL: PostURL success for http://localhost:7001/cs/HelloCS [2013-07-11 01:41:17.118][CS.INSTALL][INFO] CSSetupEngine.testConnectionAction: Web Server and Application Server Configuration test finished successfully. [2013-07-11 01:41:17.118][CS.INSTALL][INFO] CSSetupEngine.testConnectionAction: Attempting to Ping the Database. [2013-07-11 01:41:17.459][CS.INSTALL][ERROR] CSSetupEngine.doPing: Database Ping Failed. Make sure your application server and web server are running. Response received = HTTP/1.1 200 OK HOST_SERVICE: FutureTenseContentServer:11.1.1.6.1 Transfer-Encoding: chunked Date: Wed, 10 Jul 2013 20:11:17 GMT Set-Cookie: JSESSIONID=vpMNRd1Fwb1NJyb5NH1pXx5dfmPhzzyJL2S3yYry3FwQqL8hFVJ6!1994306862; path=/; HttpOnly Content-Type: text/html; charset=UTF-8 X-Powered-By: Servlet/2.5 JSP/2.1 [2013-07-11 01:41:17.459][CS.INSTALL][ERROR] CSSetupEngine.doPing: Database Ping Failed. Make sure your application server and web server are running. Response received = HTTP/1.1 200 OK HOST_SERVICE: FutureTenseContentServer:11.1.1.6.1 Transfer-Encoding: chunked Date: Wed, 10 Jul 2013 20:11:17 GMT Set-Cookie: JSESSIONID=vpMNRd1Fwb1NJyb5NH1pXx5dfmPhzzyJL2S3yYry3FwQqL8hFVJ6!1994306862; path=/; HttpOnly Content-Type: text/html; charset=UTF-8 X-Powered-By: Servlet/2.5 JSP/2.1 [2013-07-11 01:41:17.460][CS.INSTALL][ERROR] CSSetupEngine.testConnectionAction: Database Ping was attempted with WCSDataSource as the DSN. The URL that was passed in = http://localhost:7001/cs/CatalogManager. Please Check your connection and property files settings. [2013-07-11 01:41:17.460][CS.INSTALL][ERROR] CSSetupEngine.testConnectionAction: Install was unable to ping the database. Installation has halted. [2013-07-11 01:41:17.461][CS.INSTALL][ERROR] Worker.run. Install failed. Please check log file. Click Yes to modify your install choices and re-try install. Click No to terminate application.
It looks like DB ping is getting failed.
But I am not sure how to resolve this error.
Please help. I am pasting the content of my bea_omii.ini file that I have used. (Please view as HTML, as formatting is getting lost on this page.)
Do let me know if any other information is required from my end.
bea_omii.ini:
#ContentServer install properties #Thu Apr 17 12:03:27 IST 2008 # Content Server Information # Specify the directory where you want to install Content Server i.e on windows C\:/csinstall on unix /opt/csinstall CSInstallDirectory=/home/oracle/WCS # Path to the Shared Directory i.e on windows C\:/csinstall/Shared on unix /opt/csinstall/Shared CSInstallSharedDirectory=/home/oracle/WCS/Shared # For delivery installation set Development to false Development=true # CSInstallType single/upgrade/cluster default is single only needed for upgrade or cluster #CSInstallType=single # This is to select APPSERVER Note: PORTALSERVER is not supported CSInstallPlatformType=APPSERVER # Set the application/portal server you want to install # Possible options are: wls92 for ( weblogic server), websphere60 (for webshpere), tomcat5 (for tomcat) CSInstallAppServerType=wls92 # Set the path to the server directory ex. For weblogic, on windows CSInstallAppServerPath=C\:\\bea\\wlserver_10.3 # on unix CSInstallAppServerPath=/u01/software/bea/wlserver_10.3 CSInstallAppServerPath=/home/oracle/Oracle/Middleware/wlserver_10.3 # [WEBLOGIC ONLY] Set the path to the weblogic domain i.e. on windows CSInstallWLDomainPath=C\:/bea/user_projects/domains/base_domain # on unix CSInstallWLDomainPath=/u01/software/bea/user_projects/domains/base_domain CSInstallWLDomainPath=/home/oracle/Oracle/Middleware/user_projects/domains/WCSDomain # [WEBLOGIC ONLY] Set the weblogic domain name i.e. base_domain name from path C\:/bea/user_projects/domains/base_domain CSInstallAdminDomainName=WCSDomain # Option for manual deployment (Should always be set to true) CSInstallbManual=true #Manual deployment needs to set the path where installer has to explode the war CSManualDeployPath=/home/oracle/WCS/deployment # Set the context path for your web application for example /cs/ sCgiPath=/cs/ # Set the database type Possible options #CSInstallDatabaseType= [SQL Server, DB2, Oracle10] CSInstallDatabaseType=Oracle10 # Set the data source name CSInstallDBDSN=WCSDataSource # By default it is installed as a primary cluster member. To install as cluster member make CSInstallType=cluster. CSInstallType=single #WEM installation IsWEMInstall=TRUE #hostname where cs is installed CASHostName=localhost # port number of cs installation CASPortNumber=7003 #Server HostName of internally accessible CAS CASHostNameLocal=localhost #Server PortNumber of internally accessible CAS CASPortNumberLocal=7003 #Server HostName where CAS is actually deployed CASHostNameActual=localhost # Select the default logger name (possible values com.fatwire.cs.core.logging.StandardLog, com.fatwire.cs.core.logging.TraditionalLog # com.fatwire.cs.core.logging.StandardTraditionalLog , org.apache.commons.logging.impl.Log4JLogger LoggerName=org.apache.commons.logging.impl.Log4JLogger # Set the host name where the application will be running CSInstallWebServerAddress=localhost # Set the port number where the application will be running CSInstallWebServerPort=7001 # Set this property to true if you are installing Spark CSInstallSpark=false # Sample Sites Information # Set this true if you want to install Avisports sample site. Avisports=true # CS-Direct and CS-Direct Advantage properties. Please don't touch them ContentCentre=true CatalogCentre=true # Set this true if you want to install CS Engage otherwise false MarketingStudio=true # Set this to true if you want to install Commerce Connectors CommerceConnector=true # Set this to true to install Structure and Navigation for FS2 this is only installed if this is development mode FSCore=true # Set this to true to install Engage Extensions for Structure and Navigation. This depends on Development and FSCore FSEngageCore=true # Set this to true to install Store Schema. This depends on Development and FSCore FSStoreSchema=true # Set this to true to install Engage Extensions for Store Schema. This depends on Development, CommereceConnector and FSEngageCore FSEngageStoreSchema=true # Set this to true to install Document Schema. This depends on Development and FSCore FSDocSchema=true # Set this to true to install Sample Visitors. This depends on Development and FSCore FSLocalUser=true # Set this to true to install Pretty URL Package. This depends on Development and FSCore FSPrettyURL=true # Set this to true to install Store Demo Data. This depends on Development and FSStoreSchema FSStoreDemoData=true # Set this to true to install Document Demo Data. This depends on Development and FSDocSchema FSDocDemoData=true # Set this to true to install Engage Store Data. This depends on Development,FSStoreDemoData,FSEngageStoreSchema and FSStoreSchema FSEngageStoreDemoData=true # If you want to install First Site II Site View set it true otherwise false. This depends on Development and FSStoreSchema FSSiteView=true # Set this to true to install Analytics. This depends on Development,FSCore,FSEngageCore,FSStoreSchema,CommerceConnector and CatalogCentre FSAnalytics=true # Set this to true to install Legacy (core) asset types (Article, Linkset). This depends on Development and ContentCentre CCSampleAssets=true # Set this to true to install Burlington Financial asset types. This depends on Development and ContentCentre CCSampleAssetsBF=true # Set this to true to install Engage and Analytics extensions for Burlington Financial. This depends on Development,MarketingStudio and ContentCentre MSSampleAssetsBF=true # Set this to true to install HelloAssetWorld asset types. This depends on Development and ContentCentre CCSampleAssetsHW=true # Set this to true to install GE Lighting asset types. This depends on Development and ContentCentre CatCSampleAssets=true # Set this to true to install Hello World sample site. This depends on Development and ContentCentre CCSampleSiteHW=true # Set this to true to install Burlington Financial sample site. This depends on CCSampleAssets and CCSampleAssetsBF CCSampleSiteBF=true # Set this to true to install Burlington Financial Extensions sample site. MSSampleSiteBF=true # Set this to true to install GE Lighting sample site. MSSampleSiteGE=true # Spark sample site components # Set this to true to install Document Management sample asset types DMSampleAssets=false # Set this to true to install Content Management sample asset types WCMSampleAssets=false # Set this to true to install Base Components SparkSampleSite=false # Set this to true to install Sample Data SparkSampleData=false # Set this to true to install Sample Portlets. Set this true if this is a portal server SparkSamplePortlets=false

Thanks for your reply Yct.
I got the ping issue resolved today, there was an issue in the data source. Finally I was able to complete the installation successfully.
But there is one more issue now. After completing the installation, I am trying to access the URL to get to the WCS login page, but with no success.
Below, I am mentioning few URLs that I tried, and the outcome:
http://localhost:7001/cs/HelloCS , This URL gives me a page with some static content messages like 'Welcome to Oracle WebCenter Sites 11gR1'. Then there are some text lines in blue color. I think this page is working as expected.
http://localhost:7001/cs/login , this URL automatically gets redirected to the URL 'http://localhost:7003/cas/login?service=http%3A%2F%2Flocalhost%3A7001%2Fcs%2Fwem%2Ffatwire%2Fwem%2FWelcome' and I get an error message 'Firefox can't establish a connection to the server at localhost:7003.'
http://localhost:7001/cas/login, this takes me to login page, where when I enter fwadmin@xceladmin credentials, I am taken to JASIG Central Authentication Service page, which is again static, and I can't do anything on this page
http://localhost:7001/cs/Satellite?c=Page&cid=1327351719456&pagename=avisports%2FPage%2FHomeLayout1 , this takes me to the Avisports site, which is functional
http://localhost:7001/cs/Satellite?c=Page&childpagename=FirstSiteII%2FFSIILayout&cid=1124747609916&pagename=FSIIWrapper, this takes me to he FirstSit page, which is again functional
Issue: I am not getting the main login page, where I would get 3 sites(Avisports/FirstsiteII) in the dropdown.
Looks like there is something wrong going on.
Following I am pasting my omii.ini file, if it helps:
#ContentServer install properties
#Thu Apr 17 12:03:27 IST 2008
# Content Server Information
# Specify the directory where you want to install Content Server i.e on windows C\:/csinstall on unix /opt/csinstall
CSInstallDirectory=/home/oracle/WCS
# Path to the Shared Directory i.e on windows C\:/csinstall/Shared on unix /opt/csinstall/Shared
CSInstallSharedDirectory=/home/oracle/WCS/Shared
# For delivery installation set Development to false
Development=true
# CSInstallType single/upgrade/cluster default is single only needed for upgrade or cluster
#CSInstallType=single
# This is to select APPSERVER Note: PORTALSERVER is not supported
CSInstallPlatformType=APPSERVER
# Set the application/portal server you want to install
# Possible options are: wls92 for ( weblogic server), websphere60 (for webshpere), tomcat5 (for tomcat)
CSInstallAppServerType=wls92
# Set the path to the server directory ex. For weblogic, on windows CSInstallAppServerPath=C\:\\bea\\wlserver_10.3
# on unix CSInstallAppServerPath=/u01/software/bea/wlserver_10.3
CSInstallAppServerPath=/home/oracle/Oracle/Middleware/wlserver_10.3
# [WEBLOGIC ONLY] Set the path to the weblogic domain i.e. on windows CSInstallWLDomainPath=C\:/bea/user_projects/domains/base_domain
# on unix CSInstallWLDomainPath=/u01/software/bea/user_projects/domains/base_domain
CSInstallWLDomainPath=/home/oracle/Oracle/Middleware/user_projects/domains/WCSDomain
# [WEBLOGIC ONLY] Set the weblogic domain name i.e. base_domain name from path C\:/bea/user_projects/domains/base_domain
CSInstallAdminDomainName=WCSDomain
# Option for manual deployment (Should always be set to true)
CSInstallbManual=true
#Manual deployment needs to set the path where installer has to explode the war
CSManualDeployPath=/home/oracle/WCS/deployment
# Set the context path for your web application for example /cs/
sCgiPath=/cs/
# Set the database type Possible options
#CSInstallDatabaseType= [SQL Server, DB2, Oracle10]
CSInstallDatabaseType=Oracle10
# Set the data source name
CSInstallDBDSN=WCSDataSource
# By default it is installed as a primary cluster member. To install as cluster member make CSInstallType=cluster.
CSInstallType=single
#WEM installation
IsWEMInstall=TRUE
#hostname where cs is installed
CASHostName=localhost
# port number of cs installation
CASPortNumber=7003
#Server HostName of internally accessible CAS
CASHostNameLocal=localhost
#Server PortNumber of internally accessible CAS
CASPortNumberLocal=7003
#Server HostName where CAS is actually deployed
CASHostNameActual=localhost
# Select the default logger name (possible values com.fatwire.cs.core.logging.StandardLog, com.fatwire.cs.core.logging.TraditionalLog
# com.fatwire.cs.core.logging.StandardTraditionalLog , org.apache.commons.logging.impl.Log4JLogger
LoggerName=org.apache.commons.logging.impl.Log4JLogger
# Set the host name where the application will be running
CSInstallWebServerAddress=localhost
# Set the port number where the application will be running
CSInstallWebServerPort=7001
# Set this property to true if you are installing Spark
CSInstallSpark=false
# Sample Sites Information
# Set this true if you want to install Avisports sample site.
Avisports=true
# CS-Direct and CS-Direct Advantage properties. Please don't touch them
ContentCentre=true
CatalogCentre=true
# Set this true if you want to install CS Engage otherwise false
MarketingStudio=true
# Set this to true if you want to install Commerce Connectors
CommerceConnector=true
# Set this to true to install Structure and Navigation for FS2 this is only installed if this is development mode
FSCore=true
# Set this to true to install Engage Extensions for Structure and Navigation. This depends on Development and FSCore
FSEngageCore=true
# Set this to true to install Store Schema. This depends on Development and FSCore
FSStoreSchema=true
# Set this to true to install Engage Extensions for Store Schema. This depends on Development, CommereceConnector and FSEngageCore
FSEngageStoreSchema=true
# Set this to true to install Document Schema. This depends on Development and FSCore
FSDocSchema=true
# Set this to true to install Sample Visitors. This depends on Development and FSCore
FSLocalUser=true
# Set this to true to install Pretty URL Package. This depends on Development and FSCore
FSPrettyURL=true
# Set this to true to install Store Demo Data. This depends on Development and FSStoreSchema
FSStoreDemoData=true
# Set this to true to install Document Demo Data. This depends on Development and FSDocSchema
FSDocDemoData=true
# Set this to true to install Engage Store Data. This depends on Development,FSStoreDemoData,FSEngageStoreSchema and FSStoreSchema
FSEngageStoreDemoData=true
# If you want to install First Site II Site View set it true otherwise false. This depends on Development and FSStoreSchema
FSSiteView=true
# Set this to true to install Analytics. This depends on Development,FSCore,FSEngageCore,FSStoreSchema,CommerceConnector and CatalogCentre
FSAnalytics=true
# Set this to true to install Legacy (core) asset types (Article, Linkset). This depends on Development and ContentCentre
CCSampleAssets=true
# Set this to true to install Burlington Financial asset types. This depends on Development and ContentCentre
CCSampleAssetsBF=true
# Set this to true to install Engage and Analytics extensions for Burlington Financial. This depends on Development,MarketingStudio and ContentCentre
MSSampleAssetsBF=true
# Set this to true to install HelloAssetWorld asset types. This depends on Development and ContentCentre
CCSampleAssetsHW=true
# Set this to true to install GE Lighting asset types. This depends on Development and ContentCentre
CatCSampleAssets=true
# Set this to true to install Hello World sample site. This depends on Development and ContentCentre
CCSampleSiteHW=true
# Set this to true to install Burlington Financial sample site. This depends on CCSampleAssets and CCSampleAssetsBF
CCSampleSiteBF=true
# Set this to true to install Burlington Financial Extensions sample site.
MSSampleSiteBF=true
# Set this to true to install GE Lighting sample site.
MSSampleSiteGE=true
# Spark sample site components
# Set this to true to install Document Management sample asset types
DMSampleAssets=false
# Set this to true to install Content Management sample asset types
WCMSampleAssets=false
# Set this to true to install Base Components
SparkSampleSite=false
# Set this to true to install Sample Data
SparkSampleData=false
# Set this to true to install Sample Portlets. Set this true if this is a portal server
SparkSamplePortlets=false

WCS upgrade to Prime 1.2

I'm currently running WCS 7.0.230 ready for upgrade to Prime 1.2. Reading Cisco docs, the path is to upgrade from WCS to NCS 1.1.1.24 firstly, then to Prime 1.2
so far...
export.bat all > wcs-export.zip
also performed a backup via the GUI backup tool
have a NCS 1.1.1.24 - 30 day eval license (docs say eval is enough before upgrading to Prime 1.2 which you have purchased)
A couple of things are not clear to me,
http://www.cisco.com/en/US/docs/net_mgmt/prime/infrastructure/1.2/quickstart/guide/cpi_qsg.html#wp56675
currently WCS runs
7.0.230
Feature - plus
AP limit 150
Type permanent
Does this mean I need to uninstall WCS to install NCS cleanly or is there an upgrade path without uninstalling WCS manually? In the download section you can only download for Small/medium/Large. I intend to download medium, but again there are no specifics I can find in relation to my WCS license i.e. - AP limit = NCS medium or do I look at my new Prime License 500 Device upgrade LIC
I'm looking for better documentation WCS > Prime.

I manged to upgrade to NCS 1.1.1.24 without any problems and successfully migrate the WCS backup file into NCS.
The next issue I have is upgrading from NCS 1.1.1.24 to Prime 1.2.
Performed NCS backup successfully
admin# show repository defaultRepo
backup-20130422-0950.tar.gpg
PI-upgrade-bundle-1.2.1.12.tar.gz
Upgrade not successful (i'm still running NCS eval license, should I be importing Prime PAK licenses after upgrade to Prime?)
admin# application upgrade PI-upgrade-bundle-1.2.1.12.tar.gz defaultRep o
Save the current ADE-OS running configuration? (yes/no) [yes] ?
Generating configuration...
Saved the ADE-OS running configuration to startup successfully
Initiating Application Upgrade...
Stage 1 of 7: Transferring file ...
-- complete.
Stage 2 of 7: Unpacking file ...
-- complete.
% One or more required RPM's not found in the bundle
admin# show ver
Cisco Application Deployment Engine OS Release: 2.0
ADE-OS Build Version: 2.0.1.038
ADE-OS System Architecture: x86_64
Copyright (c) 2005-2010 by Cisco Systems, Inc.
All rights reserved.
Hostname: SV195968
Version information of installed applications
Cisco Prime Network Control System
Version : 1.1.1.24

Ciscoworks 3.2.1 Upgrade Path

We have Ciscoworks 3.2.1 (Windows Server). We also currently have Cisco Prime Infrastructure 1.2 (appliance) for wireless management.
I'm getting a bit confused trying to determine the appropriate upgrade path for the LMS server. I'm wondering if I should be upgrading the existing server to Prime Infrastructure 1.2 which will run on the windows server or migrate the wired management to the Prime Infrastructure 1.2 appliance? I like the idea of one management portal for both wired and wireless networks. Does Cisco take a module based approach to the licensing of the Prime Infrastructure products? In other words, do I need to simply buy the "LMS module" for use on the existing appliance? The Windows Server has dated hardware so I would also need to confirm that it supports the upgrade if that is the recommended path.
I'd like to hear what others have done that have made the switch to Prime Infrastructure from LMS.

LMS and Cisco PI are intended to merge in coming period, but in Cisco PI it almost run a parallel to LMS and is not the complete replacement of LMS.
Every new release comes out with more LMS featured baked inside Cisco PI. Hence I recommend you to keep your LMS for LAN Management tasks.
Cisco PI is an complete and evolved upgrade to WCS/NCS. You can upgrade the following Cisco Prime Network Control System products to Cisco Prime Infrastructure 1.2:
•Cisco Prime Network Control System 1.0.0 (NCS 1.0 MR2, 1.0.2.29)
•Cisco Prime Network Control System 1.1.0 (NCS 1.1 FCS, 1.1.0.58)
•Cisco Prime Network Control System 1.1.1 (NCS 1.1 K MR1, 1.1.1.24)
On Server side, I think CPI can't be installed on LMS Windows server as it has to have a virtulized environment. You should keep and treat both separately. However, if you have got the LMS 4.2 license with CPI , you should upgrade your LMS to version 4.2 and get CPI to manage wireless infrastructure.
-Thanks

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.

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

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.

Hi, I currently have Lightroom 5.6 for MAC and Adobe has launched Lightroom 6 - I am trying to understand if there is an upgrade path for 5.6 users and how much does it cost, if any or is a forklift upgrade i.e. new software all together. Thanks

Hi, I am a Lightroom user and currently have 5.6 version (DVD Version). The lightroom 6 version, for existing lightrrom users, is there an upgrade path or it is a new software entirely. In either cases, what costs are associated.
Thanks,
Raj

LR 6 is a new payfor upgrade, $80 in the US if you have the serial-number-licensed LR 5. If you're already using the CC version of LR+PS then it just comes along as a new app you can install.
It’ll run alongside your LR5 so you can try it out and see if it’s something you want.
The only trial is a LR-6-CC version that you can convert to a serial-number-licensed version if you buy a serial-number. I think the download in LR 5 when it notifies you of an upgrade is what you can use to try it, although I don’t have personal experience with that seeing as I have the CC version of LR+PS so the CC App provided the Install button for me.
The main issues people are having are for some system configurations performance is worse. Adobe rewrote it to use the GPU in the Develop module but some people’s video cards aren’t up to the task, and for some people even turning off the GPU, while speeding things up, doesn’t make it as fast as LR 5.
On my system it seems to work great.

Upgrade Path 8.1.6 to 8.1.7.4

Hi,
I have to upgrade Oracle 8.1.6 to Oracle 8.1.7.4. In the Oracle8i Migration Release 3 (8.1.7) PDF documentation, I don't find a upgrade path. So I think I can directly uprade to 8.1.7.4. But somebody told me that I have first upgrade to 8.1.7.0?
Is there anybody with experince in this topic and can help me?
Oliver

You have to first upgrade from 8.1.6 to 8.1.7.0 and then apply the 8.1.7.4 patch. 8.1.7.4 is not the full blown database software, it's an upgrade.
The readme for 8.1.7.4 states:
This is not a complete software distribution and you must install it over an existing 8.1.7 Oracle Server installation.

Upgrade Path for migrating Essbase 7.1 to Essbase 11.1.2.1??

Can any one tell me the upgrade path (and related documents) for migrating Essbase 7.1 to Essbase 11.1.2.1??

Thanks Nathan for your response.
Will the below Essbase Upgrade steps work (From version 7.1 to Version 11.1.2.1 directly)?
1. Install Essbase 11.1.2.1 in one server (new) and Shared Services in another server (new). Both the new servers with Win 2008 OS.
2.Login to EAS console in the new server. Open the outline version 7.1 and then migrate to version 11.1.2.1.
3. Copy the artifacts (such as Calc Scripts and Rule Files etc.) from the Old Essbase directory (Version 7.1) to the new Essbase directory (Version 11.1.2.1).
4. Extract data from the old system and import into the new system.
5. Export Essbase security from old system and import to the shared services of the new system. This might requires some manual interventions.
Or, do I have to upgarde from version 7.1 to 11.1.1.3 and then from 11.1.1.3 to 11.1.2.1?

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

Installing WCS - upgrade path

Similar Messages

Maybe you are looking for