Upgrade from 10GR1 to 10GR2: Spatial Component invalid

I'm currently upgrading a database on a solaris box from 10GR1 to 10GR2 (10.1.0.2.0 to 10.2.0.1.0). After running catupgrd the Spatial Component is marked as invalid.
Spatial INVALID 10.2.0.1.0 00:30:28
I checked through the log file of the upgrade and I see the following error..
PL/SQL procedure successfully completed.
ALTER TYPE SDO_GEOMETRY REPLACE
ERROR at line 1:
ORA-22314: method information mismatch in ALTER TYPE
I'm currently re-running catupgrd but it's highly unlikely that this will work second time around. I'll have a look for the actual SQL and see what it's trying to do. Anyone seen this before?

I'm doing another 10.1.0.4 to 10.2.0.1 upgrade and I'm having the same issue again with spatial
Spatial INVALID 10.2.0.1.0 00:05:47
I've run the catupgrd about 5 times now and spatial is still invalid. The output from running the catupgrd is showing little information. What's the best way about finding out what's invalid or what's to be done?

Similar Messages

  • Upgrading from 10gR1 to 10gR2

    I can't seem to find any documentation on how to install R2 over top of R1. Do have to export everything out of the R1 instance and import it into the new one or is there a way to install it like a patch on top of the original install?

    Hi,
    is there a way to install it like a patch on top of the original install? No, this is two different release (and not patchset), from same version I agree, but different release, you need to install 10gR2 into a new ORACLE_HOME directory.
    http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14238/preup.htm#i1008013
    Nicolas.

  • Porting Sql profiles from 10gR1 to 10gR2

    Hi,
    I require some sql profiles to be ported from 10gR1 to 10gR2, as these profiles are important for the application to perform optimally.Could you please share your thoughs or suggestions, thanks in advance.
    Balaji.

    You may use the package DBMS_SQLTUNE.
    From oracle documentation:
    Import/Export SQL Tuning Sets and SQL Profiles
    You use DBMS_SQLTUNE subprograms to move SQL Profiles and SQL Tuning Sets from one system to another using a common programmatic model. In both cases, you create a staging table on the source system and populate that staging table with the relevant data. You then move that staging table to the destination system following the method of your choice (such as datapump, import/export, or database link), where it is used to reconstitute the objects in their original form. These steps are implemented by means of subprograms included in this package:
    Call the CREATE_STGTAB_SQLPROF Procedure or the CREATE_STGTAB_SQLSET Procedure to create the staging table on the source system.
    Call the PACK_STGTAB_SQLPROF Procedure or PACK_STGTAB_SQLSET Procedure to populate the staging table with information from the source system.
    Once you have moved the staging table to the destination system, you call the UNPACK_STGTAB_SQLPROF Procedure or the UNPACK_STGTAB_SQLSET Procedure to recreate the object on the new system.

  • ASM RAC Migration from 10gR1 to 10GR2 32 to 64-bit

    please advise how can i move forward with migration having the following requirement.
    Thanks.
    - 2-node RAC Cluster on windows server 2003 32-bit
    - Version is 10gR1 Standard Edition on both Nodes with ASM at the moment. (asmcmd is not available in 10gR1)
    - Migration is needed to be done to a new hardware setup having new high speed disks, 10g R2 Enterprise Edition with ASM and 64-bit windows server 2003.
    Now i need to migrate to the new hardware with different hardware,windows version,Oracle Version and new disks as well.
    Migration PLan:
    1- install 32-bit enteprise edition 10gR2 on existing system and migrate RAC from 10gR1 Standard Edition to 10gR2 Enterprise Edition first.
    2- how should i de-attach datafiles in ASM so that i can take them to new machine. attach them and run rest of the migration steps. (in a non-asm environment i can just copy the datafiles using network to the new machine)
    3- once the diskgroup/datafile are available on new hardware i can run the scripts to change wordsize.
    please advise how step2 can be done.
    do i need to take care of the 2 rac-nodes or just do all the migration using one node?
    thanks.

    Hi;
    1- Installl Redhat Enterprose Linux 5 64 bit ( need to confirm the 5.x version ) as the current DB 10.2.0.5 will not certified for RHEL6Correct only 11.2.0.3 db version is certified with RHEL6.
    In oracle certification I can see the certified 64 bit RHEL OS for 10.2.0.5 is RHEL5 ("Oracle Database 10.2.0.5.0 is certified on Linux x86-64 Red Hat Enterprise Linux 5"). Please let me know the last supported version in RHEL5 which I can go for. I could not find anything about it. I am thinking, I can go for RHEL 5.5 and in the same OS can I upgrade DB 10.2.0.5 to version 11.2.0.3 after the migration.?The latest version is 5.8 and you can download it from e-delivery.
    PS:Please dont forget to change thread status to answered if it possible when u belive your thread has been answered, it pretend to lose time of other forums user while they are searching open question which is not answered,thanks for understanding
    Regard
    Helios

  • Upgrading from Oracle database 10.1.0.2 to 10.2.0.3

    Hello
    I'm new to oracle database installations. I'm trying to upgrade from 10.1.0.2 to 10.2.0.3 but have no clue on how to do it...
    What must i do and where can i download the necessary executables? Metalink?
    I thank in advance all your help!
    Best regards

    OK,
    This is an upgrade from 10g Rel 1 to 10g Rel 2 plus the 10.2.0.3.0 patchset. It means you will have to perform these operation>
    0. Perform a full backup of your current environment.
    1. Install 10gR2 on a separate Oracle Home.
    2. Apply the 10.2.0.3.0 patchset on top of this new oracle installation.
    3. Perform the database upgrade process to upgrade your database from 10gR1 to 10gR2-3
    This is not an upgrade guide and there are a lot of details you must consider prior to actually executing this procedure, I suggest you to read the 10gR2 upgrade guide you can find here --> http://download.oracle.com/docs/cd/B19306_01/server.102/b14238/toc.htm
    ~ Madrid
    http://hrivera99.blogspot.com/

  • DB upgrade fom 9i to 10gR2

    Do we need to know if failover and loadbalancing is implemented to plan for DB upgrade from 9i to 10gR2? If so why?

    Hi,
    Issues when upgrading from Oracle 9i :
    1. Hash Group by aggregation which allows a hash algorithm to process group by statements. You have to use for sorts ORDER BY.
    2. 10g CBO has been added costed subquery unnesting and view merging functionality.
    a. Symptoms might range from high parse times to wrong results
    3.The CONNECT Role has been changed since 10g R2
    4. Parse times may increase after upgrade/migration
    Hope it helps....
    Thanks
    LaserSoft

  • INVALID Objects after upgrade from 12.1.1 to 12.1.3

    Hi
    Recently I have applied 9239090, 13984450, 10627841 patches to upgrade from 12.1.1 to 12.1.3, but now there are a number of Invalid objects in the DB.
    I have tried to compile them through 'adadmin' utility, and even ran 'utlirp.sql' with 'utlrp.sql'. Tried bouncing all db, apps tier, apache but they still remains 'Invalid'. What kind of objects are they and whether they will have any impact on apps? How to compile them?
    Any help will be really appreciated. Thanks.
    As a test I tried to compile one object and get the following errors:
    Package Body APPS.FFP55370_01011990@EBS12
    Error(347,1): PL/SQL: Statement ignored
    Error(347,5): PLS-00306: wrong number or types of arguments in call to 'ARREARAGE'
    Error(382,1): PL/SQL: Statement ignored
    Error(382,5): PLS-00306: wrong number or types of arguments in call to 'ARREARAGE'
    Invalid Objects list
    FFP55370_01011990
    FFP50529_01011900
    FFP50775_01011900
    FFP52090_01011990
    FFP50576_01011900
    FFP54520_01011995
    ImportExport
    FFP58914_01010001
    FFP60324_01010001
    FFP56324_01011990
    FFP50523_01011900
    FFP54824_01012000
    FFP59200_01011990
    FFP55331_01011998
    FFP55359_01011990
    FFP58907_01010001
    FFP55328_01011998
    FFP55356_01011990
    FFP58908_01010001
    FFP59176_01012004
    FFP57126_01011995
    FFP60588_01011990
    FFP61138_01010001
    FFP61170_01010001
    FFP61884_01010001
    FFP61867_01010001
    FFP62357_01012000
    FFP62358_01012000
    FFP62376_01012000
    FFP51848_01011990
    FFP50533_01011900
    FFP50531_01011900
    FFP54413_01011995
    FFP54409_01011995
    FFP52683_01071999
    WWV_FLOW_LIST_OF_VALUES_DATA
    WWV_FLOW_LISTS_OF_VALUES$
    FFP58919_01010001
    FFP58887_01042004
    FFP51846_01011990
    FFP59110_01011990
    FFP57215_01011999
    FFP56739_01011999
    FFP56325_01011990
    FFP59192_01011990
    FFP1915_01010001
    FFP56596_01012001
    FFP1918_01010001
    FFP57217_01012000
    FFP59113_01011990
    FFP55243_26121999
    FFP56327_01011990
    FFP54521_01011995
    FFP60587_01011990
    FFP60593_01011990
    FFP60793_01012004
    FSAH_DUPLICATE_PKG
    FFP61920_01010001
    FFP55366_01011990
    FFP52681_01071999
    FFP51840_01011990
    FFP52621_01011996
    FFP55065_01011990
    FFP53477_01012001
    FFP59131_01011990
    FFP51850_01011990
    FFP51838_01011990
    FFP59273_01012004
    FFP51849_01011990
    FFP55077_01011990
    FFP59251_01012004
    FFP55240_26121999
    FFP54414_01011995
    FFP54393_01011995
    FFP58912_01010001
    FFP54823_01012000
    FFP57196_01012000
    FFP55362_01011990
    FFP57216_01012000
    FFP57125_01011995
    FFP60833_01012000
    FFP60943_01011990
    FFP60964_01012000
    FFP61532_01011990
    XLA_00707_AAD_C_000026_PKG
    FFP61919_01010001
    FFP62359_01012000
    FFP55060_01011990
    FFP50510_01011900
    FFP55355_01011990
    FFP55058_01011990
    FFP54406_01011995
    FFP51867_01011990
    FFP54474_01011995
    FFP55361_01011990
    FFP58885_01042004
    FFP51844_01011990
    FFP56716_01012001
    FFP59175_01012004
    FFP54525_01011995
    FFP54909_01011990
    FFP56329_01011990
    FFP54407_01011995
    FFP56052_01012000
    FFP54524_01011995
    FFP56056_01012000
    FFP54404_01011995
    FFP54523_01011995
    FFP58913_01010001
    FFP55306_01011995
    FFP50525_01011900
    FFP55333_01011998
    FFP1916_01010001
    FFP58911_01010001
    FFP60555_01010001
    FFP61156_01010001
    FFP61152_01010001
    FFP52982_01010001
    FFP61511_01012000
    FFP62356_01012000
    FFP62378_01012000
    FFP62379_01012000
    FFP51404_01011997
    FFP55358_01011990
    FFP55067_01011990
    FFP52115_01011990
    FFP51887_01011990
    FFP54398_01011995
    FFP54411_01011995
    WWV_FLOW_GENERIC
    WWV_FLOW_FIELD_TEMPLATES
    FFP53720_01011990
    FFP54827_01012000
    FFP50522_01011900
    FFP55330_01011998
    FFP54912_01011990
    FFP59116_01011990
    FFP59115_01011990
    FFP54394_01011995
    FFP56330_01011990
    FFP56434_01012001
    FFP58163_01011951
    FFP59114_01011990
    FFP56328_01011990
    FFP58910_01010001
    FFP60606_01011990
    FFP61440_01011990
    XLA_20065_AAD_C_000030_PKG
    FFP55069_01011990
    FFP53540_01012001
    FFP55364_01011990
    FFP55375_01011990
    FFP50577_01011900
    FFP52481_01010001
    RE_PROFILER
    FFP58915_01010001
    FFP58920_01010001
    FFP51888_01011990
    FFP50928_01011997
    FFP56333_01011990
    FFP55063_01011990
    FFP55367_01011990
    FFP51068_01011997
    FFP59111_01011990
    FFP56332_01011990
    FFP56323_01011990
    FFP57190_01012000
    FFP1919_01010001
    FFP59191_01011990
    FFP51966_01011998
    FFP54403_01011995
    FFP55368_01011990
    FFP1917_01010001
    FFP60592_01011990
    FFP60607_01011990
    FFP61277_01011951
    FFP61871_01010001
    FFP61926_01010001
    FFP61897_01010001
    FFP62377_01012000
    FFP51837_01011990
    FFP50512_01011900
    FFP52744_01071999
    FFP52724_01071999
    FFP51411_01011999
    FFP50527_01011900
    FFP58888_01042004
    FFP58870_01042004
    FFP59117_01011990
    FFP56331_01011990
    FFP55080_01011990
    FFP59112_01011990
    FFP50583_01011900
    FFP54518_01011995
    FFP55079_01011990
    FFP59195_01011990
    FFP56053_01012000
    FFP56322_01011990
    FFP55373_01011990
    FFP54449_01011995
    FFP54522_01011995
    FFP54948_01011990
    FFP58918_01010001
    FFP60591_01011990
    RDT_1
    FFP60944_01011990
    FFP60963_01012000
    FFP61124_01010001
    FFP61912_01010001
    MSD_DEM_OBI_DEMANTRA_MV
    FFP55372_01011990
    FFP50773_01011900
    FFP53497_01012001
    FFP51406_01011997
    FFP50506_01011900
    FFP50508_01011900
    FFP51843_01011990
    FFP55062_01011990
    FFP55078_01011990
    FFP55070_01011990
    FFP57220_01012000
    FFP56326_01011990
    FFP51906_01011990
    FFP53224_01011999
    FFP56337_01011995
    FFP58909_01010001
    FFP58906_01010001
    FFP58861_01042004
    FFP51841_01011990
    FFP50581_01011900
    FFP56321_01011990
    FFP50524_01011900
    FFP60589_01011990
    FFP61924_01010001
    XLA_00707_AAD_C_000044_PKG
    F
    G

    Hi Gents,
    All objects starting with FF have been successfully compiled by the fix pointed out by you. Thanks v much for your help. Much appreciated.
    Now a total of 15 invalid objects are remaining. I could manage to find solution of 14 objects (which I understand can be safely ignored, and highlighted the source of the solution below).
    The only one remaining is this materialized view. I tried to compile it but but did not throw any errors, and still remains under invalid state. Not sure how to go about it. I can confirm that this is not a custom object.
    MSD_DEM_OBI_DEMANTRA_MV     MATERIALIZED VIEW
    --> I found an answer about them on *MOS [ID 967352.1]*, and will now safely ignore them now.
    FSAH_DUPLICATE_PKG     PACKAGE BODY
    RE_PROFILER     PACKAGE BODY
    XLA_00707_AAD_C_000026_PKG     PACKAGE BODY
    XLA_00707_AAD_C_000044_PKG     PACKAGE BODY
    XLA_20065_AAD_C_000030_PKG     PACKAGE BODY
    --> I followed this thread for resolution on these objects. I believe that they can be safely ignored now.
    247 Invalids are not getting compiled
    ImportExport     JAVA SOURCE
    ImportExport     JAVA CLASS
    WWV_FLOW_LIST_OF_VALUES_DATA     SYNONYM
    WWV_FLOW_LISTS_OF_VALUES$     SYNONYM
    WWV_FLOW_GENERIC     SYNONYM
    WWV_FLOW_FIELD_TEMPLATES     SYNONYM
    RDT_1     TABLE
    F     TABLE
    G     TABLE

  • I just purchased the upgrade from trial to full version. It does not work. It asks for my orginal serial key and when I paste in the trial key it says invalid??

    Downloaded trial and then purchased the activate the full version option. The activation keys don't work. It wants an 'original' key. When I use the trial key it rejects it as invalid! Have I just been robbed of 75 quid?

    lanceblack,
    You know, I had seen your similar post in other forum with same issue. This itself is confusing for other participants including myself to keep track of forum discussion regarding same issue.
    It would be nice if you keep your issue in proper forum in one place, less confusion for others.
    Corky02 said better than I did yesterday. I am not quite sure why or what impresssion that you'd easily upgrade from try-out app into full-license. For many people are aware that what it means or what does this having to do with upgrading qualification with any applications. Why did you think you would get to upgrade that easily from trail try out app to licensed one?
    I don't think the Apple's ads are misleading. I just think you got yourself confused. Sorry I can't help you. IF I am Apple employee, I would love to help you and get this resolved for you. I am just one of those participants helping others.
    Once again, I am sorry that you get your view all wrong and lead into thinking that you are entitled to do so. But you need to understand that once if you had purchased a full license app from try-out app. Most people know what does that mean with try out app for the first time. And most people know that if they wish to purchase an application, this means purchasing a boxed (or electronic downloaded file) from Apple retail store (or online store). Plus, new venue at Apple offering Mac App store. I think that is a little confusion for some people who are not familiar with the difference.
    I do believe that if you purchase from Mac App store, it doesn't require to put in license serial number. I think it is a different approach for some reason. I had bought some other Mac apps (not Aperture) from Mac App store few times. I haven't purchased Aperture updated version straight from Mac App store online. I bought mine from Apple retail store in Canada in person.
    I still don't understand why you still think Apple is misleading you all the way. I don't think it is. In case if you haven't notice... there is way for you to get in touch with Apple called Apple Support Express Lane. Give it a try.

  • Upgraded from Elements 9 to 12 and the Adobe site says my serial number is invalid. [was:Pardner 1]

    I just upgraded from elements 9 to 12 and the Adobe site says my serial number is invalid. I copied right off my old box.

    double check that you have the correct number:  http://helpx.adobe.com/x-productkb/global/find-serial-number.html
    if you're certain you do, contact adobe support:  http://www.adobe.com/support/chat/ivrchat.html

  • HT201272 I recently upgraded from an Iphone 4S to 5. I am having trouble with magicjack; each time i install it it gives me an error message "The installation associated with this device is invalid". Cannot seem to access account info or make calls.

    I recently upgraded from an Iphone 4S to 5. I am having trouble with magicjack; each time i install it it gives me an error message "The installation associated with this device is invalid". Cannot seem to access account info or make calls.

    I have exactly the same trouble.
    If you wet the answer, please let me know!!

  • Any Proactive measures for 10GR2 when upgrading from W2K3 to W2K3 EE

    Current environment
    SQL> select banner from v$version;
    BANNER
    Oracle Database 10g Release 10.2.0.2.0 - Production
    PL/SQL Release 10.2.0.2.0 - Production
    CORE 10.2.0.2.0 Production
    TNS for 32-bit Windows: Version 10.2.0.2.0 - Production
    NLSRTL Version 10.2.0.2.0 - Production
    We are planning an OS upgrade from windows 2003 stand edition to Windows 2003 enterprise edition.
    1) From the ORACLE prospective will there be any bottlenecks.
    2) Are they any proactive measures i need to take.If so can you provide me link to a doc which might be helpful
    Any comments are appreciated.

    Both Windows 2003 Standard Edition and Enterprise Edition are certified platforms for Oracle 10g Rel. 2.
    I can see you are currently working with patchset 10.2.0.2.0. You didn't mention if you are planning to upgrade to 10.2.0.3.0 but if you are willing to do so, there are several issues reported by the oracle community, I have included verbatim transcripts from the referred sites, just to name a few:
    http://www.pythian.com/blogs/356/oracle-10203-patchset-known-issues-and-bugs
    Other platforms to watch out with 10.2.0.3 patchset are Windows and Linux 32 bit - Metalink Note 403616.1 “Many Child Cursors create in 10.2.0.3 on Windows and Linux”. This will likely affect applications with heavy usage of bind variables (perhaps, ones with cursor_sharing=force/similar as well) and busy OLTP is a good candidate. See for yourself the note I mentioned above - it describes some symptoms and consequences (latch contention, ORA-4031, ORA-600) pretty well. The good news is that Linux platform has one-off patch available already - patch 5705795.
    http://www.pythian.com/blogs/335/oracle-10203-patchset-is-out
    Oracle 10.2.0.3 patchset is out
    December 5th, 2006 - by Marc Fielding
    My colleague Vamsi Chikkam noticed that the Oracle 10.2.0.3 patchset has been released for Linux and Windows 32-bit. The major bugfixes are the same as my original post with a few additions:
    * Identical SQL run in different schemas may modify the wrong schema’s tables (bug 5458753)… we have run into this problem at a client site and it’s not pretty. Workarounds include qualifying schema names in SQL and one-off patches for 10.2.0.2. MetaLink note 329673.1 has more details.
    * When cursors are being reloaded frequently in the shared pool, PLS-306/ORA-1722/ORA-1858 errors can occur (bug 4752541)
    * Under Windows platforms, triggers referencing :NEW/:OLD using NCHAR/NVARCHAR character sets can error out (bug 5388136)
    * The same issue as bug 5388136 above also causes compilation errors on 10.2.0.2 databases upgraded from previous releases under Windows(bug 5383828)
    http://www.orafaq.com/maillist/oracle-l/2007/03/05/0329.htm
    To inform you about important information regarding your software, Oracle is notifying you of an issue discovered in a recent download of a database patch set or bundle. This issue affects the following patch sets and bundles (hereinafter "Patch Set"):
    * 10.2.0.3 all ports
    * Windows 32 and 64 bit patch bundles: + 9.2.0.7 Bundle 13, 14, 15 + 9.2.0.8 Bundle 2, 3 and 4 + 10.1.0.5 Bundle 9, 10, 11 + 10.2.0.2 Bundle 9, 10, 11, 12, 13 + 10.2.0.3 Bundle 1
    Oracle believes that the number of customers with user data that may be affected by this Patch Set is small; however, the information contained in this announcement is intended to help you determine if your data may be affected and what to do if it is. Please read through this message in its entirety to determine if you have the issue and be sure to perform all recommended steps before contacting support. This information should be maintained for your reference as necessary.
    Due to 2007 U.S. and Canadian changes to Daylight Saving Time, you may have stored timestamp data in your Oracle database which was not previously within Daylight Saving Time, but is now included (e.g., timestamp data with dates falling between March 11, 2007 and April 1, 2007). Such data must be corrected BEFORE installing a Patch Set into your Oracle Database. The instructions to detect and correct affected data prior to installing Patch Set are documented in MetaLink (for more information, see MetaLink [1]Note ID # 359145.1).
    ~ Madrid
    http://hrivera99.blogspot.com/

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

  • Issue in oracle upgrade from 9i to 10g.

    Hi,
    I have an MS access application running on oracle database.Recently database is upgraded from 9i to 10g.
    After upgrade application is facing the conversion problem.it is throwing an error on varchar and time stamp field showing invalid timestamp message.NLS setting of both the version is same.Please suggest.

    Thank you,
    Here are the answers of your queries.
    Yes,This is affecting only MS access application because no other application is accessing this database.
    No,No other component of the application is changed or upgraded it is only database which is upgraded.
    The error is ORA-06502:PL/SQL:numeric or value error:Character to number conversion error.(In the application the value of this field is defind as Double and in database table it is VarChar and the system was working fine untill database upgrade after upgrade it is giving above error.)
    For another field it is giving the error "No valid timestamp" although the same was working fine before upgrade.
    No I have not traced the actual sessions but from the backup of 9i I have checked NLS setting and compared it with 10g and found that both are the same.
    Hope I have not confused you.

  • Why upgrading from Oracle 8i to Oracle 9i?

    Hi,
    The company I work in is evaluating whether upgrading from 8i to 9i of Oracle database. Apart from the fact that it's always usefull and reasonable to upgrade towards the latest versions, it seems to me that the main features of version 9i are with reference to the data warehouse management that where I work we don't use. From the viewpoint of PL/SQL are there particular differences between 8i and 9i? In other words I have to point out important reasons for justifying the upgrade? Thanks!

    Both versions are already de-supported. Other than taking advantage of new features that newer versions of database software provide, it is necessary to keep pace with upgrades so as to stay in support and continue to get security fixes/patches. Each new version has a "New Features" guide that lists the new features as compared to the previous release.
    9iR1 New Features - http://download.oracle.com/docs/cd/A91202_01/901_doc/server.901/a90120/toc.htm
    9iR2 New Features - http://download.oracle.com/docs/cd/B10501_01/server.920/a96531/toc.htm
    10gR1 New Features - http://download.oracle.com/docs/cd/B14117_01/server.101/b10750/toc.htm
    10gR2 New Features - http://download.oracle.com/docs/cd/B19306_01/server.102/b14214/toc.htm
    11gR1 New Features - http://download.oracle.com/docs/cd/B28359_01/server.111/b28279/toc.htm
    11gR2 New Features - http://download.oracle.com/docs/cd/E11882_01/server.112/e10881/toc.htm
    http://www.oracle.com/support/lifetime-support-policy.html?origref=http://www.oracle.com/us/support/index.html
    HTH
    Srini

  • Solaris 10 upgrade from 9 - Upgrade option not presented

    I have moved the system disk from a v880 to a v480 and successfully booted.
    I've successfully tested the upgrade using pfinstall.
    /usr/sbin/install.d/pfinstall -D /tmp/profile
    I had the following text in /tmp/profile
    install_type upgrade
    root_device /dev/dsk/c1t0d0s0
    This finished with:
    Test run complete. Exit status 0.
    I had to mount /dev/dsk/c1t0d0s0 to /a before running pfinstall otherwise the program would fail with Exit status 2.
    Original slice layout is:
    # df -h | grep c1t0
    /dev/dsk/c1t0d0s0 9.8G 4.2G 5.6G 43% /
    /dev/dsk/c1t0d0s3 9.8G 3.7G 6.1G 38% /usr
    /dev/dsk/c1t0d0s4 9.8G 3.9G 5.9G 40% /var
    /dev/dsk/c1t0d0s5 9.8G 1.8G 8.0G 19% /opt
    /dev/dsk/c1t0d0s6 20G 2.0G 18G 11% /export/home
    Because of http://docs.sun.com/app/docs/doc/820-4041/6nfhjnlao?l=Ja&a=view
    I moved var from slice 3 to / on slice 0
    I also removed "swap" entries in vfstab, and even removed the second disk in the system (which didn't have an OS)
    ok> boot cdrom - nowin
    this results with no upgrade option presented
    Can someone tell me what I can do? I don't have experience with Jumpstart or Live upgrade
    Thanks

    Hi,
    Yes and no.
    11gR1 and 11gR2 are fully supported (premier support). 10gR1 and 10gR2 are in extended support. About 9.2 it's a bit more complicated and the general extended support ended : check note 161818.1 for further details.
    After the extended support there is still the sustaining support.
    Read that to understand the notions :
    http://www.oracle.com/us/support/library/lifetime-support-technology-069183.pdf
    Best regards
    Phil

Maybe you are looking for