Impact upgrade copied Roadmap.

Hello,
We are investigating in using our own Roadmap. It will be a copy of the ASAP Implementation Roadmap and will have new structure nodes with related project documentation.
At the moment we are using the ASAP Implementation Roadmap V3.0 Sep 2005 and SOLMAN 3.2 service package 12. Soon we will be upgrading our Roadmap and in the near future we will be upgrading to Solution Manager 4.0.
Can anybody tell me :
1. If you upgrade our Roadmap what will happen with the Roadmap which we have created? Will the new structure nodes be gone? and what will happen with the documentation? Do you need to recreate the Roadmap again?
2. The same questions in case of upgrading Solution Manager?
Hope to hear from you?
regards,
Ralph

Hi
All The Delta queues should be cleared before Upgrade.
Some of the Extractors will have impact, not sure depends.
You must prepare a Check list before Upgrade with the Data Upload time and After upgrade Upload time.
Hope it helps

Similar Messages

Upgrade ASAP roadmap content in Solution Manager

Hello,
Does anyone of you know how to upgrade the ASAP roadmap content in solution manager?
Current we have solution manager 4.0, SP12. The version of the ASAP roadmap content is V3.6 (Dec. 2006). We currently found from the service marketplace the lastest ASAP implementation roadmap (V3.7)
https://websmp106.sap-ag.de/roadmaps.
Is it possible to somehow "upload" this new version into Solution Manager roadmap to replace the older version? Or how should we get the roadmap content upgraded?
Many thanks for your input!!
Regards,
Li

It is delivered in ST-ICO SAP Solution Manager Implementation Cont. Ver 3.6 is in SP11, I would imagine V3.7 is in SP 13.
You would have to up your service pack or use the standalone one until then.
Derek

Copy Roadmap

Hello ALL,
I'm trying to create a new roadmap copying an old one, but whe the system ask about Package I choose $TMP and the following message appears:
"System setting does not allow changes to be made to object SHI3 AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA"
I have no idea what it means... in fact the Solution MAnager System should not be transported... that's why I chosse $TMP
Could you help me saying whats is wrong or how I can make a copy of an existing roadmap ?
thanks in advance.
Enrique

Hi
Are you doing this in ur production system
It seems ur system is locked for changes...consult ur BASIS and check SCC4 and SE03 settings.
Hope it helps to solve ur problem
Regards
Prakhar

Sales Order Type Configaration Correction : Impact on Copy controls and Oth

Dear All,
I wanted to know the impact of correcting a sales order type configuration on the dependent configurations.
we have configured a new sales order documents in V0V8 with a certain billing type (by coping standard order), however after few days when tested in QA box, we realized that Billing type should be not F2 but something else.
I wanted to know, if I can simple change the billing type to zf2 in V0V8 or something else has to be done .. Please suggest.
I wanted to know if by changing the billing type all the table entries created earlier (copy controls) automatically get modifed .
Please suggest.
Anitha

Hi,
Even for your newly created document type(Sales order),the billing type F2 will definitely work if you do some configurations.
The configurations are:
Goto the T.Code "VOV8".Select your order type.Details.
Goto the Billing tab.
If your scenario is "Order-related" billing,maintain the "Order-rel. bill. type" as "F2".
Save.
Goto the T.Code "VTFA" and maintain the copy control for your order and billing and also maintain the settings for your item category.
If your scenario is "Delivery-related" billing,maintain the "Delivery-rel. bill. type" as "F2".
Save.
Goto the T.Code "VTFL" and maintain the copy control for your delivery and billing and also maintain the settings for your item category.
If you want to create a new billing document type,then it should be created by using the T.Code "VOFA" not by "VOV8".
Select the billing document type as "F2" and click on Copy as.Change the name to "ZF2".
Save.
Maintain the relevant configuration changes.
Regards,
Krishna.

Behavior / Impact Upgrading N5K to FEX (reboot?)

Good Day
I am wondering how the behavior is if upgrading Nexus 5500 with connected FEX.
The setup is:
2 Nexus 5596 (vpc roles primary/secondary)
Many FEX 2248 / 2232 connected to the 5596. Every FEX with one link to the primary and one link to the secondary.
- Is it fact that after I will do a SW Upgrade on 5596 all the FEX will reboot after receiving the new image ?
- Will this occur a second time after SW upgrading the 2nd 5596 ?
- What's the behavior if the 2 5596 do not run same version (while upgrading it will be so for a moment, maybe this could stay a longer time) ?
If 1) is true, so all the redundant design is useless while upgrading...
Thanks for answer

The upgrade behavior for dual homed FEX is described in the upgrade guide below. If you follow the process in the guide the FEX will be rebooted once, after the primary switch is successfully upgraded. You initiate the FEX reboot when you are ready.
http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/upgrade/521_N1_1/n5k_upgrade_downgrade_521.html#wp641802
Depending on your topology and your current version you may be able to do an ISSU rather than the disruptive upgrade, the prerequisites are listed in the document. You can also test whether you can do an ISSU with the "show install all impact" command. The command will tell you what the impact of your upgrade will be before you do it, and will verify what components need to be upgraded.
As to your third question, yes the two switches can run a different NX-OS during the upgrade. But you should always review the release notes for your new version just to double check compatibility between your specific releases.

CS2- CS4 upgrade, copy print presets?

I recently upgraded to IDCS4 from IDCS2. While this may not have been the "preferred" method, I installed CS4,then uninstalled CS2. It seems the CS2 "Print Presets" didn't make the upgrade trip.
Can anyone suggest where I might locate my CS2 Print Presets, and (ideally) be able to import them into CS4?
thanks in advance,
Mike

In CS2 you would need to go to File>Print Presets>Define and save the file as a .prst, then load that file into CS4.
I'm afraid that if you haven't saved them from CS2 then they are most likely lost. Perhaps someone knows a sneaky file they reside in?

How to Copy Roadmap using RMDEF, and NOT generate a transport

We want to lock down our production environment from any configuration, but still be able to maintain our Roadmap, via RMDEF/RMAUTH, without generating any transports. Is this possible? Or must I always generate and push the transports from our development/configuration client to production?

You need to read the error messages more closely:
01652, 00000, "unable to extend temp segment by %s in tablespace %s"
// *Cause: Failed to allocate an extent for temp segment in tablespace.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
// files to the tablespace indicated.
01653, 00000, "unable to extend table %s.%s by %s in tablespace %s"
// *Cause: Failed to allocate an extent for table segment in tablespace.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
// files to the tablespace indicated.When you do CREATE TABLE t AS SELECT ... Oracle initially creates the table as a temporary segment in the tablespace where the table will reside.
The ORA-01652 indicates that there is not enough space in the table's tablespace (the table you are trying to create) to grow the table to the size required. It has nothing to do with your temporary tablespace.
The ORA-01653 means that there is not enough space in the tablespace for an existing table to add another extent.
In both cases, you need to add more space (either by adding new datafiles, or by extending the existing datafiles) to the table's tablespace (again, not the temp tablespace).
Just a question. If updating the tables once a month takes too long, why not increase the frequency of updating the tables? If you are on 9i, you may also want to take a look at the mege command.
TTFN
John

ERP 6.0 EHP 4 upgrade- How long to choose to wait before entering downtime?

Wondering if anyone has relevant downtime minimized experiences to share on how long an ERP 6.0 EHP4 production system upgrade can/should wait to confirm phase DOWNCONF_TRANS (at end of the upgrade Preprocessing roadmap) before choosing to enter actual downtime?
We are on our final production system upgrading a simple ERP 2004 only landscape to ERP 6.0 EHP 4 (NW 7.01) running on the IBM i 6.1 platform and could be ready to wait at DOWNCONF_TRANS for actual downtime to start for up to two weeks to meet non-technical business needs. As the IBM i platform doesn't support Incremental Table Conversion (ICNV) it doesn't seem any harm to get this preparation work done early and wait until the optimal business downtime opportunity to enter downtime...
Anyone have actual experience (or a SAP recommendation) on a "well resourced, moderate load" IBM i production system waiting a week or more before starting downtime as above?
Thanks in advance for relevant responses :>

Markus and Volker,
Thank you and points awarded to you both- your prompt and relevant expert responses are very much appreciated!
I thought I'd follow up on the key point Markus made for other forum readers with the same question-
"You have to take into account that once you entered the copy phase (where the shadow system is built) no more transports may run into production (the TMS will be locked). That means that you'd have a full week without the possibility to do changes to the system."
The Upgrade Guide for SAP ERP 6.0 EHP4 SR1 ABAP specifically calls out "You may not perform any more transports into or out of the SAP system" after confirming Preprocessing Roadmap phase LOCK_PRE (ABAP Workbench Locking) or at the latest phase REPACHK2. As Markus points out once you confirm either Preprocessing phase above you will NOT be able to import production support transports so determine your business support needs timing carefully before confirming these key phases.
Volker's timeline comment to have at least a few days to resolve any upgrade uptime issues makes sense too- ultimately it is up to the Basis team to work with the business team to find the best compromise balance of "no transports while waiting for downtime" vs "having time to fix any upgrade process issues" when you have a firm production downtime date to meet.
Thanks again to you both for your expert insightful help :>

Wht is the role of BI Consultant in Upgradation ??

Hi Experts ,
Can anyone give a step by step answer or a link or a material
for the same
Correct answers will be awarded with full points
Regards ,
Subash Balakrishnan

Hi,
The Upgrade Project Lifecycle can be explicitly divided into the following phases:
Phase I:
u2022     Project plan
u2022     Test planning
u2022     Release strategy
u2022     Resource mobilization
u2022     Contingency Planning
This is the Planning Phase of any Upgrade Project. Before beginning, it is highly essential to verify that there is technically a direct upgrade path between the source and target versions on the SAP Service Marketplace including any Industry Solutions. Redefine Business case and Metrics; Establish the Project Plan, then the Agenda for the Project is scheduled, derive the Project estimates, validate the estimate and the resource needs, organise the same. Leveraging the existing processes for development, testing, deployment and transition will decrease the work efforts by 10-30% in contrast to its comparable implementation. Ensure that the scope for Technical upgrades are restricted to the existing functionality and processes, effort is required to confirm if there are any major changes on them based on the review of SAP released notes and documentation.
Phase II:
u2022     Gap Analysis between SAP old and newer versions.
u2022     Identify business flows & custom development for testing
u2022     Test scripts preparation
u2022     Business flow testing in Sandbox system
u2022     Error Identification
u2022     New functionality Identification
This is the Analyze Phase of any Upgrade project. Analyze business processes, Identify Application requirements, Assess Process gaps and define a Role based Authorization design. A list of Development objects critical to the SAP Upgrade must be defined with accuracy. All Efforts to identify the interface points and all application integration.Incase, Client has a test model that is recently used then complete the Test Scripts, Expected results and Test data else complete the re-work and re-development of the entire Test Model. A Sandbox instance needs to be created early in the analysis Phase. Performing Sandbox Upgrade to the new SAP version using the existing Development or Production instance will enable us to forecast the new requirements and the changes foreseen in the Upgrade. It is very essential to conduct SAP Technical Upgrade Assessment and Go-live Functional Check. During Integration Testing, check for unusual long runtimes for Custom Program and transactions; identify any new errors in the existing functionality along with the new functionality that needs to be added.
Phase III:
u2022     Determine Resolution for Gaps
u2022     Identify and design the configuration required
u2022     Determine development work for error resolution
u2022     Consultant testing in Test System
u2022     Design new functionality
u2022     Identify Conversion activities in Productive system
u2022     Super User Training
This is the Design Phase of any Upgrade Project. During this phase, Configuration Upgrades are made and minimal configuration adjustments are detected and adjusted during testing. About 10-20% Design effort is required to remediate the errors in the custom report and other Technical developments since there is a change in the standard SAP Data Model and Data Dictionary objects. Here, Consultant Testing plays an important role in the identifying the minimal errors and adjusting the same. Plan Conversion activities since existing data is in place during the Technical Upgrade.
Phase IV:
u2022     Configure the systems as per the gaps and errors
u2022     Implement relevant SAP Notes & Patches
u2022     Implement Programming Changes
u2022     Implement new functionality
u2022     Consultant/Superuser testing in Test System
This is the Build Phase of any Upgrade Project. Complete the master configuration as per the errors identified and gaps recognized. Build and test the Application components and Technical Architecture through SAP notes and Development changes for the new functionality.Hence, it is necessary to install all the environments needed to support the Upgrade environment. Prepare training material and all the documentation that is necessary for the Enduser/Superuser training in the Test System.
Phase V:
u2022     Final Superuser testing and confirmation
u2022     Resolution of errors identified in Super user testing
This is the Test Phase of any Upgrade Project. Application testing and Integration testing should be completed in full in order to ensure that Upgrade relevant changes works in tune with the Business Processes. Super Users play an important role in testing the same and reporting any new unforeseen errors but at the same time responsibility lies within the Consultants and the Technical Team to ensure that any functionality not working is not a totally new requirement and is a part of the already existing functionality. This will avoid any time and effort being wasted in a totally new functionality.Hence, there should be a trial run of the upgrade process, including all pre- and post-validation tasks, business continuity tasks, and technical upgrade tasks. This is to ensure the Completeness of the Cut-over strategy, resource allotments and various dependencies.
Phase VI:
u2022     Transport upgrade relevant changes in Productive System
u2022     Final Conversion activities
u2022     Go-live
This is the Deploy Phase of any Upgrade Project. Plan for deployment. For this, it is highly important to assess Deployment readiness, authorize deployment, Plan a detailed Release strategy to transport the Upgrade relevant changes to Production. The next task in line will be the plan on Conversion of Data and hence Migration to the Production.Normally, majority of the Upgrades stabilize within a week before the actual handoff to the Support Team.
Testing Management & Control:
Testing is extremely essential, test scripts should be actual, provided by business. Business should be involved as much as possible, to prevent testing of programs or functionalities that is no more used and ensure that programs and functionalities that are used are also tested. Actual and complete test scripts prevent losing time by ineffective testing and surprises after go-live.
Testing has to be done with different customers, domestic and foreign in different countries, to detect language dependent errors.
Print programs in MM (Purchase Order) and SD (Sales Order, Delivery, Invoice) need special attention, because they are very often and very much modified to suit special customer requirements.
The output has to be tested thoroughly and inspected very attentively. The following needs to be checked:
u2022     Are all necessary fields printed out
u2022     Are addresses right and not only with one item line, but with two, three or many.
u2022     Are the texts printed right, is with languages everything in order etc.
User acceptance test with real business roles should be done as extensively as possible, because what is functioning with consultant authorisations /sap-all might not be functioning with business roles with much less authorisations.
Release Strategy:
Follow a detailed and planned strategy to release transport requests relevant to Upgrade. The transport can start from the Sandbox System.But, before being imported to the Development System; the transport requests can be stored in a buffer. Similarly, transport from Development System to Quality Assurance System and from Quality assurance to Production system follows the same strategy.
Country Version Approach & Impact:
Country versions should be given special care to ensure that country-specific deviations and Taxes due to legal implications work well without any issues.
The Go Live Approach , Follow-up Activities, Critical Success Factors & Deliverables:
All development should be stopped. Just the minimum of changes absolutely necessary for support should be done, no other new modules or add-ons should be installed at the same time, otherwise the situation can become very complicated.
Dump analysis is very important to detect errors and these dumps should be taken care of on a daily basis, when testing and after go-live
User variants /batch job variants tend to disappear or become outdated.
Interfaces should be tested very carefully, by users themselves, because only they know what they are really doing. The interface might be functioning basically, but for example the search help for material is not functioning at all. It is difficult to compile all such details in test scripts.
For workflow, a really experienced expert should be involved. Otherwise the search for errors might cost lots of time.Many programs are involved, standard and customer objects and their interrelationship is difficult to see and debug, especially with background processes. And if workflow is not working after upgrade, it might be difficult for customer to find workaround.
It is good to keep a non-upgraded system until the go-live and intensive care period is over. It is quite often good to see, how customer programs were functioning before upgrade, copying of pre-upgrade programs or methods might be very useful to make customer programs run again, when they are using standard ABAP objects that are changed by upgrade or even no more existing after upgrade. And users tend to claim after upgrade that functionalities are no more working, which never have been functioning, to get them without a change request. All these should be taken care of.
Hence, I believe that the above mentioned methodology and key points would suffice to ensure a planned and successful Upgrade without any major surprises or chaos.
Assign points if helpful.
Regards,
Sumit

Photoshop CS2 Upgrade Installation Problems w/ Vista Problems

I recently purchased a new laptop w/ Windows Vista which I'm trying to install my copy of Photoshop CS2 onto. My Photoshop license is an upgrade license ... originally upgraded from Photoshop v4.0.
When installing an upgrade copy of PS CS2, it requires proof of your previous version in order to verify you're a legitimate upgrader. This works fine if you're upgrading from a version of Photoshop after 5.x ...you simply insert your CD and the installation continues. The installation process is less straight-forward for users like myself ... installing from an upgraded version prior to 5. I'm required to call Adobe ... and conduct a phone verification procedure where I give them a code displayed on the screen during installation and they give me a response code to type into the installation form.
I deauthorized my old laptop ... start the installation routine on my new laptop ... call Adobe w/ my verification code ... enter the response code (which is accepted) and complete the installation without any problems. My problem occurs when I go to run the software. The startup screen indicates that the software is still in "Tryout Mode", and the first window I'm presented with is the "Adobe Activation" window requesting my serial number. If I try to enter my CS2 serial number it is rejected with the message:
"You must enter a valid serial number before activating online or viewing activation options. Please check your serial number and re-enter it, or click the Purchase button to buy a copy of this product"
The thing is ... this IS a valid serial number. I've confirmed this with Adobe. (It's probably an upgrade serial number, which is why the software is rejecting it). I called Adobe and they're now telling me that I must enter a paid-support agreement in order to receive help installing my software. They claim their software is working correctly, and it must be a problem with my computer.
Has anybody experienced a problem like this? I refuse to pay more for something that worked fine on XP just to use it on Vista due to bugs in their installation and activation routine.

function(){return A.apply(null,[this].concat($A(arguments)))}
mthight wrote:
Have the bugs of using with Vista been fixed, or still not working? thanks,
I know this is an old problem, but surely there is an answer to fix the problem by now...
What problems? I used Photoshop CS2 with Vista with no problems (I still have it installed on a Vista system if you'd like me to check anything in particular). CS3 and CS4 worked well as well. Haven't tried CS5 on Vista as I have moved up to Windows 7, but I suspect it works just fine.
-Noel

Error during upgrade from OBIEE 10G to 11G

Hello All
I ran into this issue while trying to upgrade my 10g RPD and catalog to 11.1.1.7
After installing 11G, I launched the upgrade utility from Oracle_Common/bin/ua in linux.
I am getting the below error:
UPGAST-00797: Oracle Fusion Middleware Upgrade Assistant cannot be run from an Application Developer Oracle home.
Based on the Oracle Doc. it has the following desc:
UPGAST-00797: Oracle Fusion Middleware Upgrade Assistant cannot be run from an Application Developer Oracle home.
Cause: The user has chosen to perform a upgrade from an Oracle home that does not allow an upgrade.
Action: None.
Level: 1
Type: ERROR
Impact: Upgrade
So what should I do to resolve this issue?
Thanks in advance

Hi,
First of all i am not familiar on linux box.
I tried in windows environment the rpd is deployed with out any errors.
But i ran the ua.bat file in the following path
\MWHOME\Oracle_BI1\bin\ua.bat.
while i am running in oracle_common\bin\ua.bat is not responding in my local system.
Please Mark if it helpful.
Thanks

Can I copy my Lion operating system from one computer to another in the household

Can I copy my Lion operating system from my Mac Air to another household computer?

It should also be noted that you can upgrade all Apple computers in your home free IF you paid for one license.
It should also be noted that you are NOT supposed to sell a computer that contains an UPGRADED copy of Lion.

Upgrade from 8.1.7.4 to 9.2.0.6

I'm planning to upgrade my 8.1.7.4 DB to 9.2.0.6 My question is concerning the order of steps to get there, should I
install 9.2.0.1
upgrade DB from 8.1.7.4 to 9.2.0.1
apply patchset to get to 9.2.0.6
OR
install 9.2.0.1
apply patchset to get to 9.2.0.6
upgrade DB from 8.1.7.4 to 9.2.0.6
Also, I believe I've read there is no downgrade procedure to get back to 8.1..4 from 9.2.0.6. Is this true? Due to space limitations I'll probably end up deinstalling 8.1.7.4 before installing 9.2.0.6.
Anly help is greatly appreciated.

please give the steps which u followed while upgrading from 8.1.7.4 to 9.2.0.6**Please note that my upgrade was on AIX 5.2
Here are the steps I followed, based off the "Oracle9i Database Migration" docs:
**Also see MetaLink Note:214887.1 & Note:159657.1
==> Install 9.2.0.1 (to new HOME destination)
==> Install patch to 9.2.0.6 (depends on your OS)
==> DB Upgrade
-copy parameter file from 8i to 9i ORACLE_HOME/dbs
-copy password file from 8i to 9i ORACLE_HOME/dbs
-adjust parameter file by removing obselete init parameters and adjust deprecated init parameters
-Make sure the SHARED_POOL_SIZE initialization parameter is set to at least 48 MB.
-Make sure the PGA_AGGREGATE_TARGET initialization parameter is set to at least 24 MB.
-Make sure the LARGE_POOL_SIZE initialization parameter is set to at least 8 MB.
-Make sure the COMPATIBLE initialization parameter is properly set for the new Oracle9i release (
-Make sure the DB_DOMAIN initialization parameter is set properly.
-set REMOTE_LOGIN_PASSWORDFILE to NONE in the parameter file
-make sure that the following environment variables point to the new release 9.2 directories:
ORACLE_HOME
PATH
ORA_NLS33
LD_LIBRARY_PATH
-change to the ORACLE_HOME/rdbms/admin directory under 9i HOME
-Start SQL*Plus.
-Connect to the database instance as a user with SYSDBA privileges
-SQL> STARTUP MIGRATE
-SQL> SPOOL upgrade.log
-run script u0801070.sql
The script you run creates and alters certain dictionary tables. It also runs the catalog.sql and
catproc.sql scripts that come with the new 9.2 release, which create the system catalog views and all
the necessary packages for using PL/SQL.
-Display the contents of the component registry to determine which components need to be upgraded:
SQL> SELECT comp_name, version, status
FROM dba_registry;
The following is an example of the output you will see when issuing this query:
COMP_NAME VERSION STATUS
Oracle9i Catalog Views 9.2.0.1.0 VALID
Oracle9i Packages and Types 9.2.0.1.0 VALID
JServer JAVA Virtual Machine 9.0.1 LOADED
Java Packages 9.0.1 LOADED
Oracle XDK for Java 9.0.1 LOADED
Oracle Text 9.0.1 LOADED
Oracle Workspace Manager 9.0.1.0.0 LOADED
Oracle interMedia 9.0.0.0.0 LOADED
Oracle Spatial 9.0.0.0.0 BETA LOADED
Ultrasearch 9.0.1.0.0 LOADED
OLAP Catalog 9.0.1.0.0 LOADED
11 rows selected.
-SQL> SPOOL OFF
-SQL> SHUTDOWN IMMEDIATE
-if you encountered a message listing obsolete initialization parameters when you started the database
then remove the obsolete initialization parameters from the initialization parameter file now.
-SQL> @utlrp.sql (compile any invalid objects)
-Verify that all expected packages and classes are valid:
SQL> SELECT count(*) FROM dba_objects WHERE status='INVALID';
col object_name format a30
col object_type format a15
col owner format a12
SELECT distinct object_name,object_type,owner FROM dba_objects WHERE status='INVALID';
==>RESULTED IN:
OBJECT_NAME OBJECT_TYPE
BALTOTDELETE PROCEDURE
HtoD JAVA CLASS
MILEXTRACT PROCEDURE
MilExtract PROCEDURE
TLRConvertHexToDecimal JAVA CLASS
UTL_FILE PACKAGE BODY
6 rows selected.
-Verify that all components are valid and have been upgraded to release 9.2:
SQL> SELECT comp_name, version, status
FROM dba_registry;
==> After DB upgrade
-backup DB
-Change passwords for oracle supplied accounts to what they were under 8i
sys & system
--view accounts and account status
SELECT username, account_status FROM dba_users ORDER BY username;
--lock all accounts except sys and system
--ALTER USER <username> PASSWORD EXPIRE ACCOUNT LOCK;
-create spfile & restart with new spfile
CREATE SPFILE FROM PFILE='/oracle/product/9.2/dbs/initdb.ora';
shutdown
startup
-Rebuild Unusable Function-Based Indexes
During an upgrade, some function-based indexes may become unusable. To find these indexes, issue the
following SQL statement:
SELECT owner, index_name, funcidx_status
FROM dba_indexes WHERE funcidx_status = 'DISABLED';
-re-configure listeners to point to new oracle home
cp /ora817/product/8.1.7/network/admin/tnsnames.ora .
cp /ora817/product/8.1.7/network/admin/listener.ora .
cp /ora817/product/8.1.7/network/admin/sqlnet.ora .
--update /oratab file to point db at new oracle home
--set remote_login_passwordfile back to exclusive
==> 9.2.0.6 PATCHSET BREAKS UTL_DIR
Fix by applying patch
(see MetaLink Note:303828.1)

Installing Windows 7 "Upgrade" using Boot Camp 4?

I've run myself into a bit of a dilemma and I'm hoping there is a work around... I have a MacBook Pro that came with Lion and Boot Camp 4. I understand Boot Camp 4 does not support running anything earlier than Windows 7. After going through the whole process and installing the full version of 7 on Boot Camp I realized when I got to the part where Windows wanted a license key that my license is only for an "upgrade" and therefore said it wasn't valid. I have Windows Vista that I can upgrade from, but I apparently can't install Vista with Boot Camp 4, and I've read I cannot downgrade to BC3. I'm trying to avoid buying a new license key for a full version of 7. Does anyone know if there is a way to make this work? I hope I have explained it properly... pretty much a catch 22!

OK, here's what you do. I'm assuming that you've got the partition laid out and your drivers ready:
Insert your Win 7 Upgrade DVD and hold down the C key while restarting the Mac This boots Setup
Run through Setup once, formatting your Boot Camp volume. For this go-around, use a Custom install
You will get to a point where you are asked for your Product Key. Skip this request now!
Install the Boot Camp software
Next, go back to your Win 7 Upgrade DVD and allow the AutoRun. Click Install Now on the window that opens.
You're in Setup again. This time, do an Upgrade. You should be back at your Desktop when this runs through. If asked for the key again, skip it.
Click Start > Computer
Now click System properties
At the bottom of the System Properties window is a link, Change product key. Click this link.
Enter the Upgrade key now while you walk through activation. It should be accepted this time.
We've just tricked Windows into thinking it was upgraded, thereby fulfilling the license requirement. This method works because the installer makes no check as to what specific versions of Vista or 7 the upgrade will qualify on. In this way, it is possible to "clean install" an upgrade copy for about $100 less than a full copy.
Nate

Upgrade install problem Photoshop CS5 from CS2, MacOS 10.6.8

Hello,
My wife was using Adobe Photoshop CS2 for a long time. We purchased a Photoshop CS5 upgrade in 2010 through Amazon, but she never installed it after reading about problems other people had with the upgrade. It was still in its shrink wrap seal until last night.
Then she recently went to upgrade her Mac laptop to 10.9 Mavericks from 10.6 Snow Leopard, and discovered that Photoshop CS2 will no longer work since CS2 was a PowerPC application. No problem - we thought we'd just finally install that CS5 upgrade first. The Amazon web page where we bought the product stated that this was a valid upgrade path, so we thought we would not have a problem. However, when we went to do the install, we received an "Inconsistency in the installer database" error.
Going to the support live chat, we were told by Yaseer that we could no longer upgrade from CS2 to CS5 because the CS2 "server" was shut down, and we should go to the forums for help with this instead.
Now what? We own a legal copy of PS CS2, and bought a legal upgrade copy of PS CS5 with the understanding that this was a legal upgrade path, purchased from a reputable dealer (Amazon), but now it doesn't work. There must be something that can be done here.
I'm not using my wife's Adobe id which she used to register her product, but I can provide that id as well as the serial numbers for CS2 and the CS5 upgrade.

run the cleaner, http://www.adobe.com/support/contact/cscleanertool.html
restart your computer
then try to install cs5.
if you're prompted for a cs2 serial number and your cs2 number fails, use the one linked from this page: http://helpx.adobe.com/x-productkb/policy-pricing/creative-suite-2-activation-end-life.htm l

Impact upgrade copied Roadmap.

Similar Messages

Maybe you are looking for