Pre-Upgrade functional steps

I need to know the pre-upgrade functional steps in SCM modules. Can you refer a document or SOP

Attiq wrote:
Thank you hussain i have the same document already but it does not have detailed FUNCTIONAL steps for Financials, SCM and projectsIt is covered in the same doc under "Preparing for the Upgrade" section.
Thanks,
Hussein

Similar Messages

What pre-upgrade safety steps

Hi all, I'm intending to upgrade my 24-inch iMac from Leopard 10.5.8 to SL. I run Time Machine so obviously before I start I'll say "backup now" then unmount and unplug the TM drive. I don't seem to be using any of the stuff described in the wikidot site (http://snowleopard.wikidot.com/) but I need perl and MySQL. I would use Carbon Copy Cloner to create a bootable copy before the upgrade but I haven't got an available disk. I'd like to keep the TM drive dedicated and it's not that great for space anyway. If I go ahead w/o a CCC clone - which many must do - then if there is trouble would there be a path back to 10.5.8 via the install media plus the TM stuff? I assume if so it would be laborious - but relatively unlikely to have to be done. I'd be grateful for any thoughts. TIA - Terry.

I would advise against erasing your only backup in order to change it from a TM backup to a CCC clone. That's a highly dangerous thing to do. If you've only got one backup, that's not particularly safe (better than nothing, though) and your first priority should be creating a second backup on a new hard drive. It does happen that, right when someone needs their one and only backup, they discover there's something wrong with it, and all their data is gone. If you've got limited funds available, there's less to be gained from upgrading to SL than there is to be lost if something goes wrong with your current backup system. If you insist on upgrading with only the one backup, note that a Time Machine backup can restore your system just as well as a CCC clone, assuming that you have a Mac OS X install disk matching the system under which the TM backup was made and you haven't excluded anything.
Once you've dealt with the backup situation, before upgrading you should verify your hard drive with Disk Utility (don't install an update or upgrade on a damaged drive!) and you should disconnect all peripherals. Then, assuming your current system is working just fine, install 10.6 right on top of it.

I am trying to update my iTunes to 10.5.1 so that I can upgrade my 3GS phone but am getting the following error message when trying to install the itunes:Install step failed: Run pre upgrade script for apple mobile device support. Contact software manufac

I am trying to update my iTunes to 10.5.1 so that I can upgrade my 3GS phone but am getting the following error message when trying to install the itunes: Install step failed: Run pre upgrade script for apple mobile device support. Contact software manufacturer for assistance. I am on a MacBook pro running 10.5.8 OS. Has anyone seen this before and how can I get it resolved.
Thanks for your help in advance....

Did you ever figure out the problem? "Contact Software Manufacturer"?? That sounds ominous... I've got the same issue and I'm pretty durn aggravated right about now....
Thanks!

SLA Pre-Upgrade program - Post steps

Dear All,
We upgrade our oracle applications to R12.1.3 from 11.5.10.2. Before upgrade, we applied the patch patch 5233248 and ran the concurrent program with the below values
Migrate all sets of books: Yes
Start Date: “01/01/1976”: Jan-76
End Date : (Left Blank)
The above concurrent in 11i insance took only 1 minute. Is this normal ?. There are many steps mentioned in the document R12.0 and R12.1: FAQ for the SLA Upgrade: SLA Pre-Upgrade, Post-Upgrade, and Hot Patch [ID 604893.1] .
Since I already mentioned to upgrade all GL during the upgrade process itself by mentioning the above parameters in the concurrent program. Do I have to still do anything on this regard after the upgrade
Please advise

936074 wrote:
Thanks Hussein. the pre upgrade program ran only for 1 minute. is this normal ?It should take more time. Please query GL_PERIOD_STATUSES table to verify.
Thanks,
Hussein

11i Upgrade - Projects Pre-Upgrade steps

We are upgrading from 10.7SC to 11i (11.5.2) and in running several of the Category 2 pre-upgrade steps, we have found that only really old projects show up as exceptions that should be "fixed" prior to the upgrade.
These projects are now closed and the revenue/invoices etc. are for prior fiscal years. We will probably get accounting errors (from flexfield/acct combinations that have been disabled) if we try to process the old transactions. We are also not sure that we want to write revenue events or create changes for fiscal years already closed.
Has anyone else seen this? How did you handle it -- did you reopen projects, re-enable accounts and process the exceptions noted by the scripts? Will upgrade FAIL because of the presence of these exceptions?
Any input you can provide would be helpful.
Thanks in advance,
Maria
null

Hi,
In your above output it will be
The Most Recent Release Patchsets on Metalink(Not Included Above) are:
=======================================================================================
ad        R12.AD.A.6          7305220 08/11/05 11:14:22 Checkin Released     By_Metalink
ad        R12.AD.B.2          8502056 09/12/16 06:44:40 Checkin Released     By_Metalink
ad        R12.AD.B.3          9239089 10/07/07 14:22:15 Checkin Released     By_Metalink
cdr       R12.CDR.A          10161040 11/05/11 08:39:23 Checkin Released     By_Metalink
cla       R12.CLA.B           8506229 09/06/30 23:13:11 Checkin Released     By_Metalink
Thanks

Pre Bankruptcy FICO Steps?

Hi Experts
My client is filing for Pre packaged Bankruptcy in US. After that a new company code has to be created and start again from fresh. They do have Asset accounting involved in FI module.
Can anybody tell me what are the things that need to be done in SAP Finance module before Bankruptcy filing in regard to assessment and Configuration?
What i know on this case is :
- Shortened fiscal year has to be created
- Asset Depreciation Revaluation
What happens in Controlling?
I really appreciate your response.
Thanks in advance
Meenakshi.N
Edited by: Meenakshi.Nakshatrula on Apr 8, 2010 3:27 AM
Edited by: Meenakshi.Nakshatrula on Apr 9, 2010 8:51 PM

Attiq wrote:
Thank you hussain i have the same document already but it does not have detailed FUNCTIONAL steps for Financials, SCM and projectsIt is covered in the same doc under "Preparing for the Upgrade" section.
Thanks,
Hussein

Pre Upgrade Project details Required

Hi Experts,
Could anyone please explain in detail with sufficient links/materials as to what kind of a role does an Abapper Play in Pre Upgrade Project.
What kind of Problems one can face and solutions to it if possible.
Thanks in Advance.
Regards
Ullas

Hi Ullas,
please check this link
abaper role in Upgradation project
SAP Upgrade project
Regarding the Steps involved in Upgrade Project
First it will be to find objects whcih are impacted by upgrade. Now most of the solution providers have tools to do this work automatically with less human involvement. These tools give you a list of custom developments that will be impacted by upgrade which need correction in higher version. Each object in the list will be distributed to a person in team for fix. It is the responsibity of the Abaper to find out the error and fix the error in a given program and make it error free. This is checked by testing the object after the correction is completed. For exapmle a screen number has changed in higher version for a particular transaction. This implies a correction to all custom programs where this screen is used in BDC. Another example may be an obsolete function module which is not available in higher version and it is the responsibility of Abaper to find out suitable replacement for this.
But prior to this activity there is one more activity. If there are any changes to standard SAP developments like user exits or changes to standard code or changes to data dictionary, then they will not be reflected automatically after upgrade. There are transaction SPAU for workbench objects and SPDD for data dictionary objects. Abaper has to analyse the changed done to standard programs and dictionary objects and has to decide whther these are required in higher version. If they are required then correct them through these transaction codes.
There is a document given by SAP on roles played by different people in an upgrade project. I suggest you to read that.
Best regards,
raam

Do you run Pre-Upgrade Assistant when migrate from 10.1 to 10.2

Hello,
I tried to upgrade from 10.1 to 10.2 on Windows. Base on installation guide, you have to install 10.2 in a separate ORACLE_HOME, then run utlu102i.sql through SQL before run DBUA. Since I installed 10.2 without create start database because SID is same as 10.1. How to run pre-upgrade assistant? Or should I setup new SID for 10.2 and change it back after migrate database from 10.1 to 10.2.
Your assistance will be appreciated,

I'd suggest to check the "manual upgrade/migration" method described in upgrade doc.
As a summary:
utlu102.sql is just a step to verify some prereqs needed before going to 10.2
You'll need to shutdown your 10.1 DB. Copy your .ora files from 10.1.to 10.2; adjust them appropriately.
Set your Oracle_home to 10.2; keep same SID. Startup upgrade, then run catpatch.sql (if i remember correctly).
All these steps are well described in the manual.

11i-R12 upgrade and MOS 954704.1 (pre-upgrade

I am performing the 11.5.10.2 -> R12.1.1 Upgrade using the Maint Wizard (v2.19) on Linux x86.
I am at this step:
Cat - Upg to Rel 12.1.1
ProdFamily - Perform the Upgrade
Task - Apply Preinstall Patches
Step - Check for critical pre-upgrade patches for Financials
Action - Follows MOS note 954704.1 to apply pre-upgrade patches
I would like to know whether I need to use any special options/parameters to adpatch when applying these R12 patches.
Thanks

I don't understand. I haven't applied ANY R12 patches (except OAS 10.1.2.3) yet since I am still at a "pre-upgrade" step.
So the R12 patch cannot be in AD_BUGS.
The R12.AD.A.delta.4 patch is 6510214. Don't I need to know whether it is in the Rapid Install upgrade driver u6678700.drv?Sorry, I thought you are asking how to find if it is applied or not later after the upgrade.
Just follow the same logic we did with Patch 6856840, search MOS for (R12.AD.A.DELTA.4, Patch 6510214) and you will get the list of patches that includes this patch (according to MOS website, I can see that this patch is only included in R12.AD.A.DELTA.6).
Thanks,
Hussein

EBS database pre-upgrade tool

Hi All,
I am upgrading EBS database from 10.2.0.3 to 11.2.0.3
OS - RHEL 5
EBS - 12.1.3
While running pre-upgrade too , utl112i.sql am getting some warning. Please help me what step I can follow for this warning.
WARNING: --> Database contains schemas with objects dependent on DBMS_LDAP package.
.... Refer to the 11g Upgrade Guide for instructions to configure Network ACLs.
.... USER APPS has dependent objects.
Thanks,

Srini,Hussein.
Thanks for the update. I have gone through the mentioned link and doc - http://docs.oracle.com/cd/E11882_01/network.112/e16543.pdf.
I didn't understand properly. And we haven't implement LDAP/AD inegration to EBS. And this DB need a connection other database thorugh DBLINK.
When I query : select * from dba_dependencies where referenced_name IN ('UTL_TCP','UTL_SMTP','UTL_MAIL','UTL_HTTP','UTL_INADDE','DBMS_LDAP') and owner NOT IN('SYS','PUBLIC','ORDPLUGINS'); Getting a long output. Sorry to put the below.
APPS OKS_MAIL PACKAGE PUBLIC UTL_SMTP SYNONYM HARD
APPS MTH_EVENT_PKG PACKAGE BODY PUBLIC UTL_SMTP SYNONYM HARD
APPS IBY_BANKACCXFR_PUB PACKAGE BODY PUBLIC UTL_TCP SYNONYM HARD
APPS JTF_DIAGNOSTIC_COREAPI PACKAGE BODY PUBLIC UTL_TCP SYNONYM HARD
APPS OKS_MAIL PACKAGE BODY PUBLIC UTL_TCP SYNONYM HARD
APPS WSH_OTM_HTTP_UTL PACKAGE BODY PUBLIC UTL_TCP SYNONYM HARD
APPS HZ_HTTP_PKG PACKAGE BODY PUBLIC UTL_TCP SYNONYM HARD
APPS IBY_NETUTILS_PVT PACKAGE BODY PUBLIC UTL_TCP SYNONYM HARD
APPS IBY_PAYMENT_ADAPTER_PUB PACKAGE BODY PUBLIC UTL_TCP SYNONYM HARD
APPS IBY_BANKACCXFR_PUB PACKAGE BODY APPS UTL_TCP NON-EXISTENT HARD
APPS JTF_DIAGNOSTIC_COREAPI PACKAGE BODY APPS UTL_TCP NON-EXISTENT HARD
APPS OKS_MAIL PACKAGE BODY APPS UTL_TCP NON-EXISTENT HARD
APPS WSH_OTM_HTTP_UTL PACKAGE BODY APPS UTL_TCP NON-EXISTENT HARD
APPS HZ_HTTP_PKG PACKAGE BODY APPS UTL_TCP NON-EXISTENT HARD
APPS IBY_NETUTILS_PVT PACKAGE BODY APPS UTL_TCP NON-EXISTENT HARD
APPS IBY_PAYMENT_ADAPTER_PUB PACKAGE BODY APPS UTL_TCP NON-EXISTENT HARD
OWNER NAME TYPE REFERENCED_OWNER REFERENCED_NAME REFERENCED_TYPE REFERENCED_LINK_NAME DEPE
APPS FND_OID_PLUG PACKAGE BODY APPS DBMS_LDAP NON-EXISTENT HARD
APPS FND_SSO_REGISTRATION PACKAGE BODY APPS DBMS_LDAP NON-EXISTENT HARD
APPS FND_LDAP_UTIL PACKAGE APPS DBMS_LDAP NON-EXISTENT HARD
APPS FND_SSO_REGISTRATION PACKAGE APPS DBMS_LDAP NON-EXISTENT HARD
APPS FND_LDAP_USER PACKAGE APPS DBMS_LDAP NON-EXISTENT HARD
APPS FND_OID_PLUG PACKAGE APPS DBMS_LDAP NON-EXISTENT HARD
APPS FND_OID_UTIL PACKAGE APPS DBMS_LDAP NON-EXISTENT HARD
APPS WF_OID PACKAGE BODY APPS DBMS_LDAP NON-EXISTENT HARD
APPS WF_LDAP PACKAGE BODY APPS DBMS_LDAP NON-EXISTENT HARD
APPS FND_OID_UTIL PACKAGE BODY APPS DBMS_LDAP NON-EXISTENT HARD
APPS FND_LDAP_UTIL PACKAGE BODY APPS DBMS_LDAP NON-EXISTENT HARD
APPS WF_OID PACKAGE APPS DBMS_LDAP NON-EXISTENT HARD
APPS FND_OID_DIAG PACKAGE BODY APPS DBMS_LDAP NON-EXISTENT HARD
APPS FND_LDAP_USER PACKAGE BODY APPS DBMS_LDAP NON-EXISTENT HARD
APPS WSH_U_CSPV PACKAGE BODY APPS UTL_HTTP NON-EXISTENT HARD
APPS MSC_E1APS_UTIL PACKAGE BODY APPS UTL_HTTP NON-EXISTENT HARD
APPS BIS_CORRECTIVE_ACTION_PVT PACKAGE BODY APPS UTL_HTTP NON-EXISTENT HARD
APPS HZ_LOCATION_SERVICES_PUB PACKAGE APPS UTL_HTTP NON-EXISTENT HARD
APPS OKS_MAIL PACKAGE BODY APPS UTL_HTTP NON-EXISTENT HARD
APPS BIS_PMV_PMF_PVT PACKAGE BO
Am getting total - 166 rows selected
Kndly suggest me what I need to do here before upgrade and after upgrade. In the document, need to do some action after upgrade to 11.2.0.3. But I didn't get a clarity what I need to do. I know this showing my lack in security knowledge.
How important this one and What step I can follow for this output. Do I need to check/consider for this warnings. ?
Thanks and sorry to ask these problems.

Pre-Upgrade Tasks

Hi Experts
My client is planning to execute a 782 SIA to 8.1.1.x SIA Siebel Upgrade and as a part of initial pre-upgrade tasks we have following queries.
1 Lots of custom columns created on EIM Tables.Being known the fact that all the EIM tables dropped and recreated with vanilla schema ,please let us know how to preserve the custom extensions done on the EIM tables as a pre-upgrade step.
2 We have ENU as primary and 4 other Global languages deployed on both Application and database and planning to execute the Multilingual upgrade for all the langs at once.Any pre-upgrade tasks with respect to the Multilingual setup.
3 Please list the obsolete tables for the above upgrade path and also any handy sql query to identify the custom columns and indexes on these obsolete tables to preserve the date.
Thanks in Advance.
RR

Hi,
Your understanding of the upgrade is not correct. As long as your X columns are in Siebel Tools they will be there after the upgrade. Promise.
The steps for the ML upgrade are all in Bookshelf for you to read. You will need to install the all LEP's before attempting to run the upgrade. There is also a step to make sure you LOVs correctly reflect your languages with no missing languages or extra languages.
R
Robert Ponder
Lead Architect and Director
Ponder Pro Serve

Help on pre upgrade assessment

Pl. tell me what can be the typical questions asked to the client on Pre Upgrade assessment of SAP APO (latest version)

Hi,
Your questions should be on the current processes at the client side,
Pain areas,
Future requirements,
Improvement areas,
Key performance indicators,
Desired functionality,
System perspective needs,
Existing data volume
Required data volume
Issues facing
Regards
R. Senthil Mareeswaran.

BO XI 3.1 installation and Upgrade activity Steps

Hi Experts,
Right now we are using BO XI R2 Version, Planning to uninstall XI R2 and do a fresh installation of BO XI 3.1 with SP3.
Do I need to install the Java latest version for XI 3.1? Right now we have the following setting,
         j2re1.4.2_04
         j2re1.4.2_16
         jre1.5.0_14
Since the up gradation of Reports, user, groups, universe events etc are from XI R2 version to XI 3.1.So Is it enough to
install BO XI 3.1 with SP 3, or do I have to go for FixPack inorder to avoid problem after this upgrade activity.
Could you please tell me about the BOXI R2 to XI 3.1 installation and Upgrade activity Steps.
Regards,
Sridharan

Hi,
you dont need a special JRE version on the Server. With the installation of BO a own JRE will be installed for BOE. Only for developing WebI reports the developer need a 1.6.x JRE later on.
There is already FixPack 3.1 out but installing "only" SP3 should be sufficient.
I would recommend you check the upgrade guide from Rel.2 to XI 3.1:
https://websmp208.sap-ag.de/~sapidb/011000358700001646952008E/xi3-1_bip_upgrade_en.pdf
You need a S-User to Login.
Regards
-Seb.

SLA Pre- upgrade programs and process and SLA Post upgrade

Hi Guys
Can anybody please let me know what are the SLA Pre- upgrade programs and process we have to run and SLA Post upgrade process and programs.
Thanks
Ajeesh

Pl post details of OS and EBS versions. Pl see if MOS Doc 604893.1 (R12: FAQ for the SLA Upgrade: SLA Pre-Upgrade, Post-Upgrade, and Hot Patch) can help
HTH
Srini

Oracle Upgrade -- Pre-Upgrade 10.2.0.4 to 11.2.0.1

Hello,
I want to do an Oracle Upgrade to version 11.2g!
At this point I did some things (in Windows Server 2003 X64):
1-) Install Oracle 10.2.0.1 (DVD Media);
2-) Installation of Oracle patchset 10.2.0.4 (note 871735);
3-) Installation of interim / last generics patch (note 1137346);
4-) Installation of SAP ECC 6.0 SR3 by SAPInst
5-) After SAP installation I did all the corrections in Oracle parameters as it mentioned in note 830576.
As you see above, all the SAP system was well installed!
But now I want to do the Oracle Upgrade process to the last version, Oracle DB 11.2g (11.2.0.1)... and so I´m following the Upgrade guide "Upgrade to Oracle Database 11g Release 2 (11.2) Windows.pdf" with some SAP notes for Upgrade process.
So I´m at this point in planning chapter where is recommended to check so things in actual database, one of this checks are running some SQL-scripts to perform an Oracle database upgrade with DBUA to release 11.2 (as mentioned in note 1431793 - Oracle 11.2.0: Upgrade Scripts)
I ran two Pre-Scripts, the @pre_upgrade_status.sql and @pre_upgrade_tasks.sql but both outputs showed some warnings and they are worrying me... so what I ask to you is some kind of help in analyse of them and tell me if this issues are relevant for the upgrading process and if so, what you recommend me to do to correct their!
Next I will post here this two log scripts... they are long!!!

PRE_UPGRADE_TASKS.log:
SQL> @pre_upgrade_tasks.sql
PRE-UPGRADE Tasks: === START ===
2010-08-05 18:24:13
Recompiling invalid objects
This reduces the number of invalid objects as much as possible.
COMP_TIMESTAMP UTLRP_BGN 2010-08-05 18:24:13
DOC>   The following PL/SQL block invokes UTL_RECOMP to recompile invalid
DOC>   objects in the database. Recompilation time is proportional to the
DOC>   number of invalid objects in the database, so this command may take
DOC>   a long time to execute on a database with a large number of invalid
DOC>   objects.
DOC>
DOC>   Use the following queries to track recompilation progress:
DOC>
DOC>   1. Query returning the number of invalid objects remaining. This
DOC>       number should decrease with time.
DOC>          SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
DOC>
DOC>   2. Query returning the number of objects compiled so far. This number
DOC>       should increase with time.
DOC>          SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;
DOC>
DOC>   This script automatically chooses serial or parallel recompilation
DOC>   based on the number of CPUs available (parameter cpu_count) multiplied
DOC>   by the number of threads per CPU (parameter parallel_threads_per_cpu).
DOC>   On RAC, this number is added across all RAC nodes.
DOC>
DOC>   UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel
DOC>   recompilation. Jobs are created without instance affinity so that they
DOC>   can migrate across RAC nodes. Use the following queries to verify
DOC>   whether UTL_RECOMP jobs are being created and run correctly:
DOC>
DOC>   1. Query showing jobs created by UTL_RECOMP
DOC>          SELECT job_name FROM dba_scheduler_jobs
DOC>          WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>
DOC>   2. Query showing UTL_RECOMP jobs that are running
DOC>          SELECT job_name FROM dba_scheduler_running_jobs
DOC>          WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>#
COMP_TIMESTAMP UTLRP_END 2010-08-05 18:24:15
DOC> The following query reports the number of objects that have compiled
DOC> with errors (objects that compile with errors have status set to 3 in
DOC> obj$). If the number is higher than expected, please examine the error
DOC> messages reported with each object (using SHOW ERRORS) to see if they
DOC> point to system misconfiguration or resource constraints that must be
DOC> fixed before attempting to recompile these objects.
DOC>#
                  0
DOC> The following query reports the number of errors caught during
DOC> recompilation. If this number is non-zero, please query the error
DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors
DOC> are due to misconfiguration or resource constraints that must be
DOC> fixed before objects can compile successfully.
DOC>#
                          0
Purging Recyclebin
This reduces the time needed for upgrading the database.
Truncating SYS.AUD$
This reduces the time needed for upgrading the database.
Gathering Oracle Dictionary Statistics
This reduces the time needed for upgrading the database.
Running Pre-Upgrade-Information Tool utlu112i.sql
This is a mandatory task for manual database upgrades.
This tool is also run in pre_upgrade_status.sql.
Oracle Database 11.2 Pre-Upgrade Information Tool 08-05-2010 18:24:45
Script Version: 11.2.0.1.0 Build: 003
Database:
--> name:          PRD
--> version:       10.2.0.4.0
--> compatible:    10.2.0
--> blocksize:     8192
--> platform:      Microsoft Windows x86 64-bit
--> timezone file: V4
Tablespaces: [make adjustments in the current environment]
--> SYSTEM tablespace is adequate for the upgrade.
.... minimum required size: 905 MB
--> PSAPUNDO tablespace is adequate for the upgrade.
.... minimum required size: 84 MB
--> SYSAUX tablespace is adequate for the upgrade.
.... minimum required size: 210 MB
--> PSAPTEMP tablespace is adequate for the upgrade.
.... minimum required size: 61 MB
Flashback: OFF
Update Parameters: [Update Oracle Database 11.2 init.ora or spfile]
Note: Pre-upgrade tool was run on a lower version 64-bit database.
--> If Target Oracle is 32-Bit, refer here for Update Parameters:
-- No update parameter changes are required.
--> If Target Oracle is 64-Bit, refer here for Update Parameters:
WARNING: --> "shared_pool_size" needs to be increased to at least 472 MB
Renamed Parameters: [Update Oracle Database 11.2 init.ora or spfile]
-- No renamed parameters found. No changes are required.
Obsolete/Deprecated Parameters: [Update Oracle Database 11.2 init.ora or spfile]
--> remote_os_authent            11.1       DEPRECATED
--> background_dump_dest         11.1       DEPRECATED   replaced by "diagnostic_dest"
--> user_dump_dest               11.1       DEPRECATED   replaced by "diagnostic_dest"
Components: [The following database components will be upgraded or installed]
--> Oracle Catalog Views         [upgrade] VALID
--> Oracle Packages and Types    [upgrade] VALID
Miscellaneous Warnings
WARNING: --> Database is using a timezone file older than version 11.
.... After the release migration, it is recommended that DBMS_DST package
.... be used to upgrade the 10.2.0.4.0 database timezone version
.... to the latest version which comes with the new release.
Recommendations
Oracle recommends gathering dictionary statistics prior to
upgrading the database.
To gather dictionary statistics execute the following command
while connected as SYSDBA:
EXECUTE dbms_stats.gather_dictionary_stats;
Oracle recommends removing all hidden parameters prior to upgrading.
To view existing hidden parameters execute the following command
while connected AS SYSDBA:
SELECT name,description from SYS.V$PARAMETER WHERE name
        LIKE '\_%' ESCAPE '\'
Changes will need to be made in the init.ora or spfile.
Oracle recommends reviewing any defined events prior to upgrading.
To view existing non-default events execute the following commands
while connected AS SYSDBA:
Events:
SELECT (translate(value,chr(13)||chr(10),' ')) FROM sys.v$parameter2
      WHERE UPPER(name) ='EVENT' AND isdefault='FALSE'
Trace Events:
SELECT (translate(value,chr(13)||chr(10),' ')) from sys.v$parameter2
      WHERE UPPER(name) = '_TRACE_EVENTS' AND isdefault='FALSE'
Changes will need to be made in the init.ora or spfile.
PRE-UPGRADE Tasks: === FINISHED ===
SQL> spool off

Pre-Upgrade functional steps

Similar Messages

Maybe you are looking for