Results 1 to 6 of 6
  1. #1
    Join Date
    Jan 2004
    Location
    India
    Posts
    113

    Unanswered: Oracle 10.2.0.2 to 10.2.0.4

    I am upgrading the oracle from 10.2.0.2 to 10.2.0.4 using 10g Release 2 (10.2.0.4) Patch Set 3 for AIX 5L Based Systems (64-Bit)

    But the documentation never siad to upgrade the DB using DBUA.
    I just wanted to know if patching the Oracle_HOME is good enough .

    As i ran ./runInstaller on the existing oraclehome and now if I select banner from v$version I do see
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
    PL/SQL Release 10.2.0.4.0 - Production
    CORE 10.2.0.4.0 Production
    TNS for IBM/AIX RISC System/6000: Version 10.2.0.4.0 - Productio
    NLSRTL Version 10.2.0.4.0 - Production


    After installingthe patchset the DB was opened with startup upgrade.

    Now the problem is everytime I open the DB i need to use startup Upgrade.

    So I hv a hinge if the Db needs to be upgraded.

    Please help me with this.
    A quick help is really appreciated.

    Thanks and Regards

  2. #2
    Join Date
    May 2004
    Location
    Dominican Republic
    Posts
    721
    what does the documentation says after starting up the database in upgrade mode, did you read further than that (hint: probably something about catpatch.sql)?

    "everytime I open the DB i need to use startup Upgrade" I am curious on why do you need to "open" the DB so often, more interestingly, this being on an AIX system.

  3. #3
    Join Date
    Jan 2004
    Location
    India
    Posts
    113
    Thanks for a quick response . But I need to know do i hv to run catupgrd.sql .

    Starting the DB was for testing the upgrade process. I didn't find any good doc for 10.2.0.2 to 10.2.0.4

    From 10.1 it is reqd and the docs also says that.

    If u could please share ur experience.

  4. #4
    Join Date
    Aug 2003
    Location
    Where the Surf Meets the Turf @Del Mar, CA
    Posts
    7,776
    Provided Answers: 1
    README.html file came with the patchset & enumerates post installation tasks
    You can lead some folks to knowledge, but you can not make them think.
    The average person thinks he's above average!
    For most folks, they don't know, what they don't know.
    Good judgement comes from experience. Experience comes from bad judgement.

  5. #5
    Join Date
    Jan 2004
    Location
    India
    Posts
    113
    Hi Anacedent,
    Thanks for your reply yes I got it and hv applied catupgrd.sql after running the prerequisit check .
    Now while running catupgrd.sql there are a couple .of errors.
    For eg
    grant select on ALL_JOBS to public with grant option
    *
    ERROR at line 1:
    ORA-03113: end-of-file on communication channel

    and subsequently all the following sql statements fail
    ERROR:
    ORA-03114: not connected to ORACLE

    Alert file shows up the following error
    ORA-07445: exception encountered: core dump [lxhh2ci] [SIGSEGV]
    [Address not mapped to object] [0xD574538454243A0] [] []
    ~
    Current status of the DB

    SQL> select open_mode from v$database;

    OPEN_MODE
    ----------
    READ WRITE

    SQL> select status from v$instance;

    STATUS
    ------------
    OPEN MIGRATE

    Can anybody please help me with this.


    Thank You very much.

  6. #6
    Join Date
    Jul 2003
    Posts
    2,296
    # For single-instance installations, use SQL*Plus to log
    in to the database as the SYS user with SYSDBA privileges:

    $ sqlplus "/as sysdba"

    Complete the following procedure to run the Pre-Upgrade Information Tool:

    1. Start the database in the UPGRADE mode:
    SQL> STARTUP UPGRADE

    2. Set the system to spool results to a log file for later analysis:
    SQL> SPOOL upgrade_info.log

    3. Run the Pre-Upgrade Information Tool:
    SQL> @/rdbms/admin/utlu102i.sql

    4. Turn off the spooling of script results to the log file:
    SQL> SPOOL OFF

    ** review log **


    Enter the following SQL*Plus commands:

    SQL> STARTUP UPGRADE /* if not already in upgrade mode */
    SQL> SPOOL patch.log
    SQL> @?/rdbms/admin/catupgrd.sql
    SQL> SPOOL OFF

    # Review the patch.log file for errors and inspect the list of
    components that is displayed at the end of catupgrd.sql script.

    This list provides the version and status of each SERVER component
    in the database.
    #
    If necessary, rerun the catupgrd.sql script after correcting any problems.
    #
    Restart the database:

    SQL> SHUTDOWN IMMEDIATE
    SQL> STARTUP

    #
    Run the utlrp.sql script to recompile all invalid PL/SQL packages now
    instead of when the packages are accessed for the first time.
    This step is optional but recommended.

    SQL> @?/rdbms/admin/utlrp.sql
    - The_Duck
    you can lead someone to something but they will never learn anything ...

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •