migration from oracle 8i to 9i

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • susmita_ganguly@yahoo.com

    migration from oracle 8i to 9i

    Hi

    I am trying to upgrade from oracle 8i to oracle 9i on the same server
    ..I don't know much abt migration .

    Can anyone help me out.

    Thanks.
    Susmita
  • Anna C. Dent

    #2
    Re: migration from oracle 8i to 9i

    susmita_ganguly @yahoo.com wrote:
    Hi
    >
    I am trying to upgrade from oracle 8i to oracle 9i on the same server
    .I don't know much abt migration .
    >
    Can anyone help me out.
    Go RTFM on dbua

    Comment

    • Ravinder Bhalla

      #3
      Re: migration from oracle 8i to 9i

      "Anna C. Dent" <anacdent@hotma il.comwrote in message news:<YdKvb.132 71$kl6.4033@fed 1read03>...
      susmita_ganguly @yahoo.com wrote:
      Hi

      I am trying to upgrade from oracle 8i to oracle 9i on the same server
      .I don't know much abt migration .

      Can anyone help me out.
      >
      Go RTFM on dbua
      Perform the following steps
      ----------------------------
      a) Check for Vesions and Options
      b) Perform COLD Backup
      c) Increase SYSTEM rollback segment size and ensure plenty space free
      in ROLLBACK segments
      d) Check o/s level patch and check certification i.e. showrev -p
      e) List all INVALID objects before upgrade
      f) Ensure SID and ORACLE_HOME set properly.
      g) Ensure no user or role as MIGRATE and OUTLN exists ( if migrating
      from
      8.0.6)
      h) Check no corruption in sys dictionary. Prepare a script 'ANALYZE '
      ||
      object_name || ' valid structure ;' where owner = 'SYS'
      i) Stop Replication and ensure all snapshots refreshes complete.
      j) Stop Listner
      k) Ensure no files need media recovery: v$recover_file
      l) Ensure no files are in backup mode: v$backup
      m) Resolve any outstanding unresolved distributed transaction:
      dba_2pc_pending ( dbms_transactio n.purge_lost_db _entry('local_t rans_id')
      )
      n) Disable all bacth and cronjobs task.
      o) Note Down all controlfile location and sysdba users: v$pwfile_users
      p) Shutdown DB
      q) Backup of init.ora , listener.ora and tnsnames.ora and needs few
      changes
      in init.ora file
      job_queue_proce ss=0
      _SYSTEM_TRIG_EN ABLED=FALSE
      unset COMPATIABLE
      REMOTE_LOGIN_PA SSWORDFILE=NONE (if using password file)
      r) update oratab entry with new ORACLE_HOME
      s) update environment variable
      - ORACLE_HOME
      - PATH
      - ORA_NLS33
      - ORACLE_BASE
      - LD_LIBRARY_PATH
      - ORACLE_PATH

      t) Run Upgrade script : cd $ORACLE_HOME/rdbms/admin
      Sqlplus /as sysdba
      startup restrict or startup migrate
      @u0801070.sql or u0900010.sql
      u) Run @utlrp
      v) Shutdown immediate
      w) Modify Listner.ora with new ORACLE_HOME
      x) Enable cronjob and batch
      y) Change oratab entry
      z) Start the Database

      Comment

      • MINIBOAT

        #4
        Re: migration from oracle 8i to 9i

        susmita_ganguly @yahoo.com wrote in message news:<f79db97d. 0311211202.2419 ed69@posting.go ogle.com>...
        Hi
        >
        I am trying to upgrade from oracle 8i to oracle 9i on the same server
        .I don't know much abt migration .
        >
        Can anyone help me out.
        >
        Thanks.
        Susmita
        Do not recommend the dbua if your DB is not the default sample
        database, I think it is a garbage of Oracle. Please refer to the
        manual upgrade guide:
        I post here because I can not open the original web
        site(http://www.tilsor.com.uy/soporte/Doc...ecnicos/9.htm).

        Complete upgrade checklist for manual upgrades from 8.X to Oracle9i
        (incl. 9.2)

        PURPOSE
        -------

        This document is created for use as a guideline and checklist when
        manually upgrading Oracle 8 or Oracle 8i to Oracle 9i.


        SCOPE & APPLICATION
        -------------------

        Database administrators


        UPGRADE CHECKLIST
        -----------------


        UPGRADING THE DATABASE
        ----------------------
        1. -----------------------------------------------------------------------------

        If your old release version is 8.0.5 or less (8.0.4 or 8.0.3), then
        direct
        upgrade is NOT supported. You must first upgrade this version to
        8.0.6. After
        the upgrade to 8.0.6 or your version IS 8.0.6 or higher, you can
        directly
        upgrade your database to 9i.

        If your old release is 8.0.5 or less, look at not 133920.1 for manual
        upgrading
        the database to 8.0.6 or higher.

        What version is running? What option is installed?
        Select * from v$version;
        Select * from v$option;


        2. -----------------------------------------------------------------------------

        PERFORM a Full cold backup!!!!!!!

        3. -----------------------------------------------------------------------------

        Avoid running out of space during the migration:

        - Prepare the system rollback segment:
        Alter rollback segment system storage (maxextents 121 next 1M);

        - Ensure plenty of free space in the SYSTEM tablespace. A minimum of
        150 Mb
        additional free space:
        Select max(bytes) from dba_free_space where tablespace_name ='SYSTEM';

        - Ensure plenty of free space in the ROLLBACK tablespace. Ensure that
        you have
        at least 1 rollback segment of 70 Mb if the number of objects in the
        database
        exceeds 5000:
        Select count(*) from dba_objects;

        If you run out of space in one of these tablespaces during the
        upgrade, you will
        need to perform the upgrade again.

        4. -----------------------------------------------------------------------------

        Verify the certification of oracle 9i on the OS version you are using.
        Verify all necessary OS patches are installed.
        Example for Solaris:
        $ showrev -p

        5. ------------------------------------------------------------------------------

        Upgrade will leave all objects (packages,views ,...) invalid, except
        for tables.
        All other objects must be recompiled manually.

        List all objects that are not VALID before the upgrade.
        This list of fatal objects.

        Select substr(owner,1, 12) owner, substr(object_n ame,1,30) object,
        Substr(object_t ype,1,30) type,status from dba_objects where status
        <>'VALID';

        To create a script to compile all invalid objects, before upgrading,
        run the
        the script called utlrp.sql in the $ORACLE_HOME/rdbms/admin directory.
        This
        script recompiles all invalid PL/SQL in the database including views.

        $ cd $ORACLE_HOME/rdbms/admin
        $ sqlplus sys/<password for SYSas sysdba
        SQL@utlrp.sql

        Run the script and than rerun the query to get invalid objects.

        spool invalid_pre.lst
        Select substr(owner,1, 12) owner,
        Substr(object_n ame,1,30) object,
        Substr(object_t ype,1,30) type, status from
        dba_objects where status <>'VALID';
        spool off

        This last query will return a list of all objects that cannot be
        recompiled
        before the upgrade in the file 'invalid_pre.ls t'


        6. -----------------------------------------------------------------------------

        Verify the kernel parameters according to the installation guide of
        the
        new version.
        Example for Solaris:
        $ cat /etc/system

        7. ------------------------------------------------------------------------------

        Ensure ORACLE_SID is set to instance you want to upgrade.
        Echo $ORACLE_SID
        Echo $ORACLE_HOME

        8. -----------------------------------------------------------------------------

        As of Oracle 9i the sql NCHAR datatypes will be limited to the Unicode
        character
        set encoding only (UTF8 and AL16UTF16). Any other NCHAR datatype will
        no longer
        be supported. When upgrading to 9i the value of the NCHAR is based on
        the NCHAR
        datatype used in the Oracle8 version. If the old National character
        set is UTF8,
        the new will be UTF8. Otherwise the national character set is changed
        to
        AL16UTF16.

        Verify character set of the database:
        $ Sqlplus SYS/<password for SYS>
        Select name, substrb(value$, 1,40) value from props$;

        9. -----------------------------------------------------------------------------

        If you are upgrading from the 8.0.6 release check no users or roles
        are called
        either MIGRATE or OUTLN.

        Select from * dba_users where username in ('MIGRATE','OUT LN');
        Select from * dba_roles where role in ('MIGRATE','OUT LN');

        10. ----------------------------------------------------------------------------

        Check for corruption in the dictionary, use:

        Set verify off
        Set space 0
        Set heading off
        Set feedback off
        Set pages 1000
        Spool analyze.sql
        Select 'Analyze '||object_type| |' '||object_name
        ||' validate structure;'
        from dba_objects
        where owner='SYS'
        and object_type in ('INDEX','TABLE ','CLUSTER');
        spool off
        This creates a script called analyze.sql.
        Run the script.

        This script (analyze.sql) should not return any errors.

        11. ----------------------------------------------------------------------------

        Ensure that all Snapshot refreshes are successfully completed.
        And replication is stopped.
        $ Sqlplus SYS/<password for SYS>
        Select distinct(trunc( last_refresh)) from dba_snapshot_re fresh_times;

        12. ----------------------------------------------------------------------------

        Stop the listener for the database
        $ lsnrctl
        Lsnrctlstop <listenername >

        13. ----------------------------------------------------------------------------

        Ensure no files need media recovery:
        $ sqlplus SYS/<password for SYS>
        Select * from v$recover_file;

        This should return no rows

        14. ----------------------------------------------------------------------------

        Ensure no files are in backup mode:
        Select * from v$backup where status!='NOT ACTIVE';

        This should return no rows.

        15. ----------------------------------------------------------------------------

        Resolve any outstanding unresolved distributed transaction:

        Select * from dba_2pc_pending ;

        If this returns rows you should do the following:

        Select local_tran_id from dba_2pc_pending ;
        Execute dbms_transactio n.purge_lost_db _entry('<LOCAL_ TRAN_ID>');
        Commit;

        16. ----------------------------------------------------------------------------

        Disable all batch and cron jobs.

        17. ----------------------------------------------------------------------------

        Ensure the users sys and system have 'system' as their default
        tablespace.

        Select username, default_tablesp ace from dba_users where username
        in ('SYS','SYSTEM' );

        To modify use:
        Alter user sys default tablespace SYSTEM;
        Alter user system default tablespace SYSTEM;

        18. ----------------------------------------------------------------------------

        Optionally ensure the aud$ is in the system tablespace when auditing
        is enabled.
        Select tablespace_name from dba_tables where table_name='AUD $';

        19. ----------------------------------------------------------------------------

        Note down where all control files are located.
        Select * from v$controlfile;

        20. ----------------------------------------------------------------------------

        Note down all sysdba users.
        Select * from v$pwfile_users;

        If a passwordfile is used copy it to the new location. On unix the
        default
        is $ORACLE_HOME/dbs/orapw<SID>.

        On windows NT this is %ORACLE_HOME%\d atabase\orapw<S ID>

        21. ----------------------------------------------------------------------------

        Shutdown the database
        $ sqlplus SYS/<password for SYS>
        SQLShutdown immediate

        22. ----------------------------------------------------------------------------

        Change the init.ora file:
        - Make a backup of the init.ora file.
        - Verify that the parameter DB_DOMAIN is set properly.
        - Ensure there is a value for DB_BLOCK_SIZE
        - Comment out the JOB_QUEUE_PROCE SSES parameter, put in a new and set
        this
        explicitly to zero, during the upgrade
        - Comment out the AQ_TM_PROCESSES parameter, put in a new and set this
        explicitly to zero, during the upgrade
        - If archiving is enabled set LOG_ARCHIVE_STA RT=TRUE
        - Ensure that the USER_DUMP_DEST, BACKGROUND_DUMP _DEST and the
        CORE_DUMP_DEST
        are set to an explicit directory
        - Set the parameter _SYSTEM_TRIG_EN ABLED explicitly to FALSE during
        the upgrade
        - Set the parameter OPTIMIZER_MODE to CHOOSE during the upgrade
        - Comment out obsoleted parameters(list in appendix A).
        - Comment out SNAPSHOT_REFRES H_? parameters
        - If your are upgrading from an 8i release ensure the COMPATIBLE
        parameter
        points to the current version. This to ensure a more easy downgrade
        when
        something goes wrong. We can alter this to point to the new release
        when
        everything is tested. If your are upgrading from 8.0.6 then leave the
        parameter unset. Setting this parameter to less than 8.1.X results in
        an
        error during the upgrade.
        - If you are using a passwordfile set the parameter
        REMOTE_LOGIN_PA SSWORDFILE=NONE
        - If you have set the parameter NLS_LENGTH_SEMA NTICS to CHAR, change
        the value
        to BYTE during the upgrade.
        - If you are using a cluster database, set the parameter
        CLUSTER_DATABAS E=FALSE
        during the upgrade.

        23. ----------------------------------------------------------------------------

        Check for adequate freespace on archive log destination file systems.

        24. ----------------------------------------------------------------------------

        Ensure the NLS_LANG variable is set correctly:
        $ echo $NLS_LANG

        25. ----------------------------------------------------------------------------
        If needed copy the listener.ora and the tnsnames.ora to the new
        location
        (when no TNS_ADMIN env. Parameter is used)
        cp $ORACLE_HOME/network/admin <NEW_ORACLE_HOM E>/network/admin

        26. ----------------------------------------------------------------------------

        If your Operating system is Windows NT, delete your services
        With the ORADIM of your old oracle version.

        For Oracle 8.0 this is:
        C:\ORADIM80 -DELETE -SID <SID>

        For Oracle 8i or higher this is:
        C:\ORADIM -DELETE -SID <SID>

        And create the new Oracle 9i service use ORADIM of the 9i ORACLE_HOME:

        C:\ORADIM -NEW -SID <SID-INTPWD <internalpwd-MAXUSERS n
        -STARTMODE AUTO -PFILE ORACLE_HOME\DAT ABASE\init<SID> .ora

        27. ----------------------------------------------------------------------------

        If needed copy the init.ora file to the new oracle_home or
        Create a link to the init.ora.
        cp $OLD_ORACLE_HOM E/dbs/init.ora $NEW_ORACLE_HOM E/dbs/init.ora
        OR
        Ln ?s /init/ora/file/path/init.ora $ORACLE_HOME/dbs/init.ora
        Also check 'ifile' parameters in the init.ora, to be set to the
        correct file.
        if an IFILE is used, verify the above mentioned parameter for the
        init.ora
        and copy this to the correct location. Change the IFILE entry in the
        init.ora
        file when this file changes from location.

        28. ----------------------------------------------------------------------------
        Update the oratab entry, to set the new ORACLE_HOME and disable
        automatic
        startup:
        <SID>:<new ORACLE_HOME>:N

        29. ----------------------------------------------------------------------------

        Update the environment variables like ORACLE_HOME and PATH
        $ . oraenv

        30. ----------------------------------------------------------------------------

        Make sure the following enviroment variables point to the new
        Release directories:
        - ORACLE_HOME
        - PATH
        - ORA_NLS33
        - ORACLE_BASE
        - LD_LIBRARY_PATH
        - ORACLE_PATH

        For HP-UX systems verify the SHLIB_PATH parameter points to the new
        release
        directories.

        $ env | grep ORACLE_HOME
        $ env | grep PATH
        $ env | grep ORA_NLS33
        $ env | grep ORACLE_BASE
        $ env | grep LD_LIBRARY_PATH
        $ env | grep ORACLE_PATH

        HP-UX:
        $ env | grep SHLIB_PATH

        31.----------------------------------------------------------------------------

        Run the upgrade script:
        $ cd $ORACLE_HOME/rdbms/admin
        Sqlplus /nolog
        SQLConnect sys/passwd_for_sys as sysdba

        Use Startup RESTRICT when you are upgrading to Oracle 9.0.1:
        SQLStartup restrict

        Use Startup MIGRATE when you are upgrading to Oracle 9.2:
        SQLStartup Migrate

        Spool the output so you can take a look at possible errors after the
        upgrade:
        SQLSpool Upgrade.log

        Run the appropriate script for your version.

        From Only Script to Run
        ==== =============== ===
        8.0.6 u0800060.sql
        8.1.7 u0801070.sql
        9.0.1 u0900010.sql

        Each of these scripts is a direct upgrade path from the version you
        are
        on to 9i. You do not need to run catalog.sql and catproc.sql as these
        two scripts are called from within the upgrade script.

        Display the contents of the component registry to determine which
        components
        need to be upgraded:
        SQLSelect comp_name, version, status from dba_registry;

        Run the script cmpdbmig.sql to upgrade the components which can be
        upgrade
        with the SYSDBA privilege (This step is only valid for upgrades
        towards 9.2):

        SQL@cmpdbmig.sq l

        The components upgraded by this script are:
        Jserver JAVAVM, oracle XDK for Java, Oracle 9i RAC, Oracle Data
        Mining,
        OLAP analytical Workspace, Oracle 9i Java Packages, Messaging Gateway,
        Oracle Workspace Manager, OLAP Catalog, Oracle Label Security.

        Display the components which were upgraded:
        SQLSelect comp_name, version, status from dba_registry;

        End the spool of the upgrade:
        SQLSpool Off

        32. ----------------------------------------------------------------------------

        Restart the database:
        SQLShutdown Immediate (DO NOT USE SHUTDOWN ABORT!!!!!!!!!)
        SQLStartup restrict

        Executing this clean shutdown flushes all caches, clears buffers and
        performs
        other database housekeeping tasks. Which is needed if you want to
        upgrade
        specific components.

        33. ----------------------------------------------------------------------------

        Run script to recompile invalid pl/sql modules:
        SQL@utlrp

        If there are still objects which are not valid after running the
        script run
        the following:
        spool invalid_post.ls t
        Select substr(owner,1, 12) owner,
        Substr(object_n ame,1,30) object,
        Substr(object_t ype,1,30) type, status from
        dba_objects where status <>'VALID';
        spool off

        Now compare the invalid objects in the file 'invalid_post.l st' with
        the invalid
        objects in the file 'invalid_pre.ls t' you create in step 5.


        34. ----------------------------------------------------------------------------

        Edit init.ora file:
        - Leave the parameter JOB_QUEUE_PROCE SSES=0
        - Leave the parameter AQ_TM_PROCESSES =0
        - remove the parameter _system_trig_en abled from the init.ora file.
        This
        parameter was explicitly set to false during the upgrade.
        - modify the log_archive_des t parameter specify only the path, but
        make sure it
        ends with a '/'. (remove the format)
        e.g. log_archive_des t=/path/arch into log_archive_des t=/path/
        - Modify the marameter log_archive_for mat and add the format
        previously
        removed from the log_archive_des t.
        E.g log_archive_for mat=arch%t_SID_ %s.log
        - If you are using a password file set the REMOTE_LOGIN_PA SSWORDFILE
        parameter
        to the value used before migration.

        35. ----------------------------------------------------------------------------

        Shutdown the database and startup the database.
        $ sqlplus /nolog
        SQLConnect sys/passwd_for_sys as sysdba
        SQLShutdown
        SQLStartup restrict

        36. ----------------------------------------------------------------------------

        Upgrade user tables with NCHAR datatype columns:
        $ sqlplus /nolog
        SQLconnect sys/passwd_for_sys as sysdba
        SQL@utlnchar.sq l
        SQL@n_switch.sq l
        SQLshutdown immediate

        37. ----------------------------------------------------------------------------

        Now edit the init.ora:
        - put back the old value for the JOB_QUEUE_PROCE SSES parameter
        - put back the old value for the AQ_TM_PROCESSES parameter
        - If you change the value for NLS_LENGTH_SEMA NTICS prior to the
        upgrade put
        the value back to CHAR.
        - If you changed the CLUSTER_DATABAS E parameter prior the upgrade set
        it back to
        TRUE
        38. ----------------------------------------------------------------------------

        Create a server parameter file with a initialization parameter file
        SQLCreate spfile from pfile;

        This will create a spfile as a copy of the init.ora file located in
        the
        $ORACLE_HOME/dbs directory.


        39. ----------------------------------------------------------------------------

        Modify the listener.ora file:
        For the upgraded intstance(s) modify the ORACLE_HOME parameter
        to point to the new ORACLE_HOME.

        40. ----------------------------------------------------------------------------

        Start the listener
        $ lsnrctl
        LSNRCTLstart <listenername >

        41. ----------------------------------------------------------------------------

        Enable cron and batch jobs

        42. ----------------------------------------------------------------------------

        Change oratab entry to use automatic startup
        SID:ORACLE_HOME :Y

        43. ----------------------------------------------------------------------------

        To use the new features in 9i change the compatible parameter to the
        new release.
        When everything is well tested, update the compatible parameter in the
        init.ora
        and restart to the new release number.
        COMPATIBLE=9.0. X where x is the release number

        ----------------------------------------------------------------------------

        UPGRADING THE JAVA ENGINE(Only for upgrades to 9.0.1)
        -------------------------
        1. -----------------------------------------------------------------------------
        Check java has previously been installed:
        Run the following query:
        select count(*) from dba_objects where object_type like 'JAVA%'and
        owner = 'SYS';

        If this is >0 then java has been installed. If this value =0 java is
        not
        installed and there is no reason to upgrade the java engine.

        2. -----------------------------------------------------------------------------

        Restart the database:
        $ Sqlplus /nolog
        SQLconnect sys/passwd_for_sys as sysdba
        SQLShutdown immediate
        SQLstartup restrict

        3. -----------------------------------------------------------------------------

        Run the appropriate script depending on what release you are coming
        from:
        $ cd $ORACLE_HOME/javavm/install
        Sqlplus /nolog
        SQLConnect sys/passwd_for_sys as sysdba
        SQLSpool catoutjava.log

        From Only Script to Run
        ==== =============== ===
        8.1.5 jvmu815.sql
        8.1.6 jvmu816.sql
        8.1.7 jvmu817.sql

        After you have run this script, all user classes are invalid. These
        become
        implicitly valid when you executed them. You can explicitly revalidate
        them
        when executing the following command:

        SQLAlter Java Class <ClassNameresol ve;

        4. -----------------------------------------------------------------------------

        Restart the database:
        $ Sqlplus /nolog
        SQLconnect sys/passwd_for_sys as sysdba
        SQLShutdown immediate
        SQLstartup restrict

        ----------------------------------------------------------------------------


        UPGRADING INTERMEDIA TEXT(Only for upgrades towards 9.0.1)
        -------------------------
        1. ----------------------------------------------------------------------------------------

        Restart the database:
        $ Sqlplus /nolog
        SQLconnect sys/passwd_for_sys as sysdba
        SQLShutdown immediate
        SQLstartup restrict

        2. ----------------------------------------------------------------------------------------

        If you have Oracle Image Cartridge release 8.0.n, or Oracle interMedia
        release 8.1.n installed,run the script imdbma to see whether or not
        you need to upgrade:
        $ cd $ORACLE_HOME/ord/im/admin
        $ sqlplus /nolog
        SQLconnect sys/passwd_for_sys as SYSDBA
        SQL@imdbma.sql

        This script displays one of the following strings:
        NOT_INSTALLED - if no prior release of interMedia components
        were installed on your system. You must install
        interMedia, rather than an upgrade.
        INSTALLED - if interMedia release 9.0.1 is already installed
        u080nnn0.sql - the script that performs the upgrade. nnn
        is the release of interMedia or Image Cartridge
        that is currently installed. For example,
        u0800050.sql upgrades from Image Cartridge
        release 8.0.5.0.0. Note: imdbma cannot
        distinguish between 8.0 releases of Image
        Cartridge. If you have an 8.0 release installed,
        the 8.0.5 script is always chosen.

        3. ----------------------------------------------------------------------------------------

        If an upgrade is required, invoke imuphelp to determine if your system
        is ready for an interMedia upgrade.
        $sqlplus /nolog
        SQLconnect sys/passwd_for_sys as sysdba
        SQL@imuphelp.sq l
        This script tells you:
        - if an earlier release of Audio must be deinstalled before upgrading
        - if an earlier release of Video must be deinstalled before upgrading
        Correct any problems found by imuphelp.sql before proceeding.

        4. ----------------------------------------------------------------------------------------

        Upgrade Oracle interMedia Common Files.
        $ cd $ORACLE_HOME/ord/admin
        $ sqlplus /nolog
        SQLconnect sys/passwd_for_sys as sysdba
        Run the appropriate script for the version you are coming from:

        From Only Script to Run
        ==== =============== ===
        8.0.3 u0800030.sql
        8.0.4 u0800040.sql
        8.0.5 u0800050.sql
        8.0.6 u0800060.sql
        8.1.5 u0801050.sql
        8.1.6 u0801060.sql
        8.1.7 u0801070.sql

        Enter the password for ORDSYS when the script asks for it.

        5. ----------------------------------------------------------------------------------------

        Upgrade interMedia.
        $ cd $ORACLE_HOME/ord/im/admin
        $ sqlplus /nolog
        SQLconnect sys/passwd_for_sys as sysdba
        Run the appropriate script for the version you are coming from:

        From Only Script to Run
        ==== =============== ===
        8.0.3 u0800030.sql
        8.0.4 u0800040.sql
        8.0.5 u0800050.sql
        8.0.6 u0800060.sql
        8.1.5 u0801050.sql
        8.1.6 u0801060.sql
        8.1.7 u0801070.sql

        Enter the password for ORDPLUGINS when the script asks for it and
        enter the password for ORDSYS when the script asks for it.

        5. ----------------------------------------------------------------------------------------

        Run the script imchk.sql to verify the upgrade connected as ORDSYS:
        $ cd $ORACLE_HOME/ord/im/admin
        $ Sqlplus ORDSYS/passwd_for_ords ys
        SQL@imchk.sql

        6. ----------------------------------------------------------------------------------------

        Restart the database:
        $ Sqlplus /nolog
        SQLconnect sys/passwd_for_sys as sysdba
        SQLShutdown immediate
        SQLstartup restrict

        ---------------------------------------------------------------------------------------


        Appendix A: Obsolete parameters in 9i:
        --------------------------------------

        _average_dirtie s_half_life
        _lm_statistics
        allow_partial_s n_results
        always_anti_joi n
        always_semi_joi n
        arch_io_slaves
        b_tree_bitmap_p lans
        backup_disk_io_ slaves
        cache_size_thre shold
        cleanup_rollbac k_entries
        close_cached_op en_cursors
        compatible_no_r ecovery
        complex_view_me rging
        cpu_count
        db_block_checkp oint_batch
        db_block_lru_ex tended_statisti
        db_block_lru_la tches
        db_block_lru_st atistics
        db_block_max_di rty_target
        db_file_simulta neous_writes
        delayed_logging _block_cleanout
        discrete_transa ctions_enabled
        distributed_loc k_timeout
        distributed_rec overy_connectio
        fast_full_scan_ enabled
        freeze_DB_for_f ast_instance_re
        gc_defer_time
        gc_latches
        gc_lck_procs
        gc_releasable_l ocks
        gc_rollback_loc ks
        hash_multiblock _io_count
        instance_nodese t
        job_queue_inter val
        job_queue_keep_ connections
        large_pool_min_ alloc
        lgwr_io_slaves
        lm_locks
        lm_procs
        lm_procs
        lm_ress
        lock_sga_areas
        log_block_check sum
        log_files
        log_simultaneou s_copies
        log_small_entry _max_size
        ogms_home
        ops_admin_group
        ops_interconnec ts
        optimizer_perce nt_parallel
        optimizer_searc h_limit
        parallel_defaul t_max_instances
        parallel_min_me ssage_pool
        parallel_server _idle_time
        parallel_transa ction_resource_
        push_join_predi cate
        row_cache_curso rs
        sequence_cache_ entries
        sequence_cache_ hash_buckets
        shared_pool_res erved_min_alloc
        snapshot_refres h_interval
        snapshot_refres h_keep_connecti
        snapshot_refres h_processes
        sort_direct_wri tes
        sort_multiblock _read_count
        sort_read_fac
        sort_spacemap_s ize
        sort_write_buff er_size
        sort_write_buff ers
        spin_count
        temporary_table _locks
        text_enable
        use_ism

        Comment

        • FaheemRao

          #5
          Re: migration from oracle 8i to 9i

          Susmita,

          Doing actually migration is one of the option.
          Second option is that to do a clean installation of Oracel 9i in
          second oracle home.

          Now create DDL scripts for everything in the Database, if you have
          TOAD thats very easy to do.

          From DDL scripts.

          1. Create tablespaces


          2 create and Migrate Data Table Data through following Statement

          Create table_In_9i nologging tablespace_in_9 i as select select * from
          table_in_8i@lin k_to_8i;

          Transfer of Data is much faster since its no logging.


          3. create indexes

          4. create rest of the sschema objects.


          This way is little bit differnet than convenrtional migration
          practices but in this way you dont have to worry about losing oracle
          8i you can continue your application running in 8i untill new 9i
          database is stable.
          Once 9i database is stable you can drop 8i database and un-install 8i.



          Faheem




          peterwang555@ya hoo.com (MINIBOAT) wrote in message news:<7989e439. 0312041254.41dc 712c@posting.go ogle.com>...
          susmita_ganguly @yahoo.com wrote in message news:<f79db97d. 0311211202.2419 ed69@posting.go ogle.com>...
          Hi

          I am trying to upgrade from oracle 8i to oracle 9i on the same server
          .I don't know much abt migration .

          Can anyone help me out.

          Thanks.
          Susmita
          >
          Do not recommend the dbua if your DB is not the default sample
          database, I think it is a garbage of Oracle. Please refer to the
          manual upgrade guide:
          I post here because I can not open the original web
          site(http://www.tilsor.com.uy/soporte/Doc...ecnicos/9.htm).
          >
          Complete upgrade checklist for manual upgrades from 8.X to Oracle9i
          (incl. 9.2)
          >
          PURPOSE
          -------
          >
          This document is created for use as a guideline and checklist when
          manually upgrading Oracle 8 or Oracle 8i to Oracle 9i.
          >
          >
          SCOPE & APPLICATION
          -------------------
          >
          Database administrators
          >
          >
          UPGRADE CHECKLIST
          -----------------
          >
          >
          UPGRADING THE DATABASE
          ----------------------
          1. -----------------------------------------------------------------------------
          >
          If your old release version is 8.0.5 or less (8.0.4 or 8.0.3), then
          direct
          upgrade is NOT supported. You must first upgrade this version to
          8.0.6. After
          the upgrade to 8.0.6 or your version IS 8.0.6 or higher, you can
          directly
          upgrade your database to 9i.
          >
          If your old release is 8.0.5 or less, look at not 133920.1 for manual
          upgrading
          the database to 8.0.6 or higher.
          >
          What version is running? What option is installed?
          Select * from v$version;
          Select * from v$option;
          >
          >
          2. -----------------------------------------------------------------------------
          >
          PERFORM a Full cold backup!!!!!!!
          >
          3. -----------------------------------------------------------------------------
          >
          Avoid running out of space during the migration:
          >
          - Prepare the system rollback segment:
          Alter rollback segment system storage (maxextents 121 next 1M);
          >
          - Ensure plenty of free space in the SYSTEM tablespace. A minimum of
          150 Mb
          additional free space:
          Select max(bytes) from dba_free_space where tablespace_name ='SYSTEM';
          >
          - Ensure plenty of free space in the ROLLBACK tablespace. Ensure that
          you have
          at least 1 rollback segment of 70 Mb if the number of objects in the
          database
          exceeds 5000:
          Select count(*) from dba_objects;
          >
          If you run out of space in one of these tablespaces during the
          upgrade, you will
          need to perform the upgrade again.
          >
          4. -----------------------------------------------------------------------------
          >
          Verify the certification of oracle 9i on the OS version you are using.
          Verify all necessary OS patches are installed.
          Example for Solaris:
          $ showrev -p
          >
          5. ------------------------------------------------------------------------------
          >
          Upgrade will leave all objects (packages,views ,...) invalid, except
          for tables.
          All other objects must be recompiled manually.
          >
          List all objects that are not VALID before the upgrade.
          This list of fatal objects.
          >
          Select substr(owner,1, 12) owner, substr(object_n ame,1,30) object,
          Substr(object_t ype,1,30) type,status from dba_objects where status
          <>'VALID';
          >
          To create a script to compile all invalid objects, before upgrading,
          run the
          the script called utlrp.sql in the $ORACLE_HOME/rdbms/admin directory.
          This
          script recompiles all invalid PL/SQL in the database including views.
          >
          $ cd $ORACLE_HOME/rdbms/admin
          $ sqlplus sys/<password for SYSas sysdba
          SQL@utlrp.sql
          >
          Run the script and than rerun the query to get invalid objects.
          >
          spool invalid_pre.lst
          Select substr(owner,1, 12) owner,
          Substr(object_n ame,1,30) object,
          Substr(object_t ype,1,30) type, status from
          dba_objects where status <>'VALID';
          spool off
          >
          This last query will return a list of all objects that cannot be
          recompiled
          before the upgrade in the file 'invalid_pre.ls t'
          >
          >
          6. -----------------------------------------------------------------------------
          >
          Verify the kernel parameters according to the installation guide of
          the
          new version.
          Example for Solaris:
          $ cat /etc/system
          >
          7. ------------------------------------------------------------------------------
          >
          Ensure ORACLE_SID is set to instance you want to upgrade.
          Echo $ORACLE_SID
          Echo $ORACLE_HOME
          >
          8. -----------------------------------------------------------------------------
          >
          As of Oracle 9i the sql NCHAR datatypes will be limited to the Unicode
          character
          set encoding only (UTF8 and AL16UTF16). Any other NCHAR datatype will
          no longer
          be supported. When upgrading to 9i the value of the NCHAR is based on
          the NCHAR
          datatype used in the Oracle8 version. If the old National character
          set is UTF8,
          the new will be UTF8. Otherwise the national character set is changed
          to
          AL16UTF16.
          >
          Verify character set of the database:
          $ Sqlplus SYS/<password for SYS>
          Select name, substrb(value$, 1,40) value from props$;
          >
          9. -----------------------------------------------------------------------------
          >
          If you are upgrading from the 8.0.6 release check no users or roles
          are called
          either MIGRATE or OUTLN.
          >
          Select from * dba_users where username in ('MIGRATE','OUT LN');
          Select from * dba_roles where role in ('MIGRATE','OUT LN');
          >
          10. ----------------------------------------------------------------------------
          >
          Check for corruption in the dictionary, use:
          >
          Set verify off
          Set space 0
          Set heading off
          Set feedback off
          Set pages 1000
          Spool analyze.sql
          Select 'Analyze '||object_type| |' '||object_name
          ||' validate structure;'
          from dba_objects
          where owner='SYS'
          and object_type in ('INDEX','TABLE ','CLUSTER');
          spool off
          This creates a script called analyze.sql.
          Run the script.
          >
          This script (analyze.sql) should not return any errors.
          >
          11. ----------------------------------------------------------------------------
          >
          Ensure that all Snapshot refreshes are successfully completed.
          And replication is stopped.
          $ Sqlplus SYS/<password for SYS>
          Select distinct(trunc( last_refresh)) from dba_snapshot_re fresh_times;
          >
          12. ----------------------------------------------------------------------------
          >
          Stop the listener for the database
          $ lsnrctl
          Lsnrctlstop <listenername >
          >
          13. ----------------------------------------------------------------------------
          >
          Ensure no files need media recovery:
          $ sqlplus SYS/<password for SYS>
          Select * from v$recover_file;
          >
          This should return no rows
          >
          14. ----------------------------------------------------------------------------
          >
          Ensure no files are in backup mode:
          Select * from v$backup where status!='NOT ACTIVE';
          >
          This should return no rows.
          >
          15. ----------------------------------------------------------------------------
          >
          Resolve any outstanding unresolved distributed transaction:
          >
          Select * from dba_2pc_pending ;
          >
          If this returns rows you should do the following:
          >
          Select local_tran_id from dba_2pc_pending ;
          Execute dbms_transactio n.purge_lost_db _entry('<LOCAL_ TRAN_ID>');
          Commit;
          >
          16. ----------------------------------------------------------------------------
          >
          Disable all batch and cron jobs.
          >
          17. ----------------------------------------------------------------------------
          >
          Ensure the users sys and system have 'system' as their default
          tablespace.
          >
          Select username, default_tablesp ace from dba_users where username
          in ('SYS','SYSTEM' );
          >
          To modify use:
          Alter user sys default tablespace SYSTEM;
          Alter user system default tablespace SYSTEM;
          >
          18. ----------------------------------------------------------------------------
          >
          Optionally ensure the aud$ is in the system tablespace when auditing
          is enabled.
          Select tablespace_name from dba_tables where table_name='AUD $';
          >
          19. ----------------------------------------------------------------------------
          >
          Note down where all control files are located.
          Select * from v$controlfile;
          >
          20. ----------------------------------------------------------------------------
          >
          Note down all sysdba users.
          Select * from v$pwfile_users;
          >
          If a passwordfile is used copy it to the new location. On unix the
          default
          is $ORACLE_HOME/dbs/orapw<SID>.
          >
          On windows NT this is %ORACLE_HOME%\d atabase\orapw<S ID>
          >
          21. ----------------------------------------------------------------------------
          >
          Shutdown the database
          $ sqlplus SYS/<password for SYS>
          SQLShutdown immediate
          >
          22. ----------------------------------------------------------------------------
          >
          Change the init.ora file:
          - Make a backup of the init.ora file.
          - Verify that the parameter DB_DOMAIN is set properly.
          - Ensure there is a value for DB_BLOCK_SIZE
          - Comment out the JOB_QUEUE_PROCE SSES parameter, put in a new and set
          this
          explicitly to zero, during the upgrade
          - Comment out the AQ_TM_PROCESSES parameter, put in a new and set this
          explicitly to zero, during the upgrade
          - If archiving is enabled set LOG_ARCHIVE_STA RT=TRUE
          - Ensure that the USER_DUMP_DEST, BACKGROUND_DUMP _DEST and the
          CORE_DUMP_DEST
          are set to an explicit directory
          - Set the parameter _SYSTEM_TRIG_EN ABLED explicitly to FALSE during
          the upgrade
          - Set the parameter OPTIMIZER_MODE to CHOOSE during the upgrade
          - Comment out obsoleted parameters(list in appendix A).
          - Comment out SNAPSHOT_REFRES H_? parameters
          - If your are upgrading from an 8i release ensure the COMPATIBLE
          parameter
          points to the current version. This to ensure a more easy downgrade
          when
          something goes wrong. We can alter this to point to the new release
          when
          everything is tested. If your are upgrading from 8.0.6 then leave the
          parameter unset. Setting this parameter to less than 8.1.X results in
          an
          error during the upgrade.
          - If you are using a passwordfile set the parameter
          REMOTE_LOGIN_PA SSWORDFILE=NONE
          - If you have set the parameter NLS_LENGTH_SEMA NTICS to CHAR, change
          the value
          to BYTE during the upgrade.
          - If you are using a cluster database, set the parameter
          CLUSTER_DATABAS E=FALSE
          during the upgrade.
          >
          23. ----------------------------------------------------------------------------
          >
          Check for adequate freespace on archive log destination file systems.
          >
          24. ----------------------------------------------------------------------------
          >
          Ensure the NLS_LANG variable is set correctly:
          $ echo $NLS_LANG
          >
          25. ----------------------------------------------------------------------------
          If needed copy the listener.ora and the tnsnames.ora to the new
          location
          (when no TNS_ADMIN env. Parameter is used)
          cp $ORACLE_HOME/network/admin <NEW_ORACLE_HOM E>/network/admin
          >
          26. ----------------------------------------------------------------------------
          >
          If your Operating system is Windows NT, delete your services
          With the ORADIM of your old oracle version.
          >
          For Oracle 8.0 this is:
          C:\ORADIM80 -DELETE -SID <SID>
          >
          For Oracle 8i or higher this is:
          C:\ORADIM -DELETE -SID <SID>
          >
          And create the new Oracle 9i service use ORADIM of the 9i ORACLE_HOME:
          >
          C:\ORADIM -NEW -SID <SID-INTPWD <internalpwd-MAXUSERS n
          -STARTMODE AUTO -PFILE ORACLE_HOME\DAT ABASE\init<SID> .ora
          >
          27. ----------------------------------------------------------------------------
          >
          If needed copy the init.ora file to the new oracle_home or
          Create a link to the init.ora.
          cp $OLD_ORACLE_HOM E/dbs/init.ora $NEW_ORACLE_HOM E/dbs/init.ora
          OR
          Ln ?s /init/ora/file/path/init.ora $ORACLE_HOME/dbs/init.ora
          Also check 'ifile' parameters in the init.ora, to be set to the
          correct file.
          if an IFILE is used, verify the above mentioned parameter for the
          init.ora
          and copy this to the correct location. Change the IFILE entry in the
          init.ora
          file when this file changes from location.
          >
          28. ----------------------------------------------------------------------------
          Update the oratab entry, to set the new ORACLE_HOME and disable
          automatic
          startup:
          <SID>:<new ORACLE_HOME>:N
          >
          29. ----------------------------------------------------------------------------
          >
          Update the environment variables like ORACLE_HOME and PATH
          $ . oraenv
          >
          30. ----------------------------------------------------------------------------
          >
          Make sure the following eniroment variables point to the new
          Release directories:
          - ORACLE_HOME
          - PATH
          - ORA_NLS33
          - ORACLE_BASE
          - LD_LIBRARY_PATH
          - ORACLE_PATH
          >
          For HP-UX systems verify the SHLIB_PATH parameter points to the new
          release
          directories.
          >
          $ env | grep ORACLE_HOME
          $ env | grep PATH
          $ env | grep ORA_NLS33
          $ env | grep ORACLE_BASE
          $ env | grep LD_LIBRARY_PATH
          $ env | grep ORACLE_PATH
          >
          HP-UX:
          $ env | grep SHLIB_PATH
          >
          31. ----------------------------------------------------------------------------
          >
          Run the upgrade script:
          $ cd $ORACLE_HOME/rdbms/admin
          Sqlplus /nolog
          SQLConnect sys/passwd_for_sys as sysdba
          >
          Use Startup RESTRICT when you are upgrading to Oracle 9.0.1:
          SQLStartup restrict
          >
          Use Startup MIGRATE when you are upgrading to Oracle 9.2:
          SQLStartup Migrate
          >
          Spool the output so you can take a look at possible errors after the
          upgrade:
          SQLSpool Upgrade.log
          >
          Run the appropriate script for your version.
          >
          From Only Script to Run
          ==== =============== ===
          8.0.6 u0800060.sql
          8.1.7 u0801070.sql
          9.0.1 u0900010.sql
          >
          Each of these scripts is a direct upgrade path from the version you
          are
          on to 9i. You do not need to run catalog.sql and catproc.sql as these
          two scripts are called from within the upgrade script.
          >
          Display the contents of the component registry to determine which
          components
          need to be upgraded:
          SQLSelect comp_name, version, status from dba_registry;
          >
          Run the script cmpdbmig.sql to upgrade the components which can be
          upgrade
          with the SYSDBA privilege (This step is only valid for upgrades
          towards 9.2):
          >
          SQL@cmpdbmig.sq l
          >
          The components upgraded by this script are:
          Jserver JAVAVM, oracle XDK for Java, Oracle 9i RAC, Oracle Data
          Mining,
          OLAP analytical Workspace, Oracle 9i Java Packages, Messaging Gateway,
          Oracle Workspace Manager, OLAP Catalog, Oracle Label Security.
          >
          Display the components which were upgraded:
          SQLSelect comp_name, version, status from dba_registry;
          >
          End the spool of the upgrade:
          SQLSpool Off
          >
          32. ----------------------------------------------------------------------------
          >
          Restart the database:
          SQLShutdown Immediate (DO NOT USE SHUTDOWN ABORT!!!!!!!!!)
          SQLStartup restrict
          >
          Executing this clean shutdown flushes all caches, clears buffers and
          performs
          other database housekeeping tasks. Which is needed if you want to
          upgrade
          specific components.
          >
          33. ----------------------------------------------------------------------------
          >
          Run script to recompile invalid pl/sql modules:
          SQL@utlrp
          >
          If there are still objects which are not valid after running the
          script run
          the following:
          spool invalid_post.ls t
          Select substr(owner,1, 12) owner,
          Substr(object_n ame,1,30) object,
          Substr(object_t ype,1,30) type, status from
          dba_objects where status <>'VALID';
          spool off
          >
          Now compare the invalid objects in the file 'invalid_post.l st' with
          the invalid
          objects in the file 'invalid_pre.ls t' you create in step 5.
          >
          >
          34. ----------------------------------------------------------------------------
          >
          Edit init.ora file:
          - Leave the parameter JOB_QUEUE_PROCE SSES=0
          - Leave the parameter AQ_TM_PROCESSES =0
          - remove the parameter _system_trig_en abled from the init.ora file.
          This
          parameter was explicitly set to false during the upgrade.
          - modify the log_archive_des t parameter specify only the path, but
          make sure it
          ends with a '/'. (remove the format)
          e.g. log_archive_des t=/path/arch into log_archive_des t=/path/
          - Modify the marameter log_archive_for mat and add the format
          previously
          removed from the log_archive_des t.
          E.g log_archive_for mat=arch%t_SID_ %s.log
          - If you are using a password file set the REMOTE_LOGIN_PA SSWORDFILE
          parameter
          to the value used before migration.
          >
          35. ----------------------------------------------------------------------------
          >
          Shutdown the database and startup the database.
          $ sqlplus /nolog
          SQLConnect sys/passwd_for_sys as sysdba
          SQLShutdown
          SQLStartup restrict
          >
          36. ----------------------------------------------------------------------------
          >
          Upgrade user tables with NCHAR datatype columns:
          $ sqlplus /nolog
          SQLconnect sys/passwd_for_sys as sysdba
          SQL@utlnchar.sq l
          SQL@n_switch.sq l
          SQLshutdown immediate
          >
          37. ----------------------------------------------------------------------------
          >
          Now edit the init.ora:
          - put back the old value for the JOB_QUEUE_PROCE SSES parameter
          - put back the old value for the AQ_TM_PROCESSES parameter
          - If you change the value for NLS_LENGTH_SEMA NTICS prior to the
          upgrade put
          the value back to CHAR.
          - If you changed the CLUSTER_DATABAS E parameter prior the upgrade set
          it back to
          TRUE
          38. ----------------------------------------------------------------------------
          >
          Create a server parameter file with a initialization parameter file
          SQLCreate spfile from pfile;
          >
          This will create a spfile as a copy of the init.ora file located in
          the
          $ORACLE_HOME/dbs directory.
          >
          >
          39. ----------------------------------------------------------------------------
          >
          Modify the listener.ora file:
          For the upgraded intstance(s) modify the ORACLE_HOME parameter
          to point to the new ORACLE_HOME.
          >
          40. ----------------------------------------------------------------------------
          >
          Start the listener
          $ lsnrctl
          LSNRCTLstart <listenername >
          >
          41. ----------------------------------------------------------------------------
          >
          Enable cron and batch jobs
          >
          42. ----------------------------------------------------------------------------
          >
          Change oratab entry to use automatic startup
          SID:ORACLE_HOME :Y
          >
          43. ----------------------------------------------------------------------------
          >
          To use the new features in 9i change the compatible parameter to the
          new release.
          When everything is well tested, update the compatible parameter in the
          init.ora
          and restart to the new release number.
          COMPATIBLE=9.0. X where x is the release number
          >
          ----------------------------------------------------------------------------
          >
          UPGRADING THE JAVA ENGINE(Only for upgrades to 9.0.1)
          -------------------------
          1. -----------------------------------------------------------------------------
          Check java has previously been installed:
          Run the following query:
          select count(*) from dba_objects where object_type like 'JAVA%'and
          owner = 'SYS';
          >
          If this is >0 then java has been installed. If this value =0 java is
          not
          installed and there is no reason to upgrade the java engine.
          >
          2. -----------------------------------------------------------------------------
          >
          Restart the database:
          $ Sqlplus /nolog
          SQLconnect sys/passwd_for_sys as sysdba
          SQLShutdown immediate
          SQLstartup restrict
          >
          3. -----------------------------------------------------------------------------
          >
          Run the appropriate script depending on what release you are coming
          from:
          $ cd $ORACLE_HOME/javavm/install
          Sqlplus /nolog
          SQLConnect sys/passwd_for_sys as sysdba
          SQLSpool catoutjava.log
          >
          From Only Script to Run
          ==== =============== ===
          8.1.5 jvmu815.sql
          8.1.6 jvmu816.sql
          8.1.7 jvmu817.sql
          >
          After you have run this script, all user classes are invalid. These
          become
          implicitly valid when you executed them. You can explicitly revalidate
          them
          when executing the following command:
          >
          SQLAlter Java Class <ClassNameresol ve;
          >
          4. -----------------------------------------------------------------------------
          >
          Restart the database:
          $ Sqlplus /nolog
          SQLconnect sys/passwd_for_sys as sysdba
          SQLShutdown immediate
          SQLstartup restrict
          >
          ----------------------------------------------------------------------------
          >
          >
          UPGRADING INTERMEDIA TEXT(Only for upgrades towards 9.0.1)
          -------------------------
          1. ----------------------------------------------------------------------------------------
          >
          Restart the database:
          $ Sqlplus /nolog
          SQLconnect sys/passwd_for_sys as sysdba
          SQLShutdown immediate
          SQLstartup restrict
          >
          2. ----------------------------------------------------------------------------------------
          >
          If you have Oracle Image Cartridge release 8.0.n, or Oracle interMedia
          release 8.1.n installed,run the script imdbma to see whether or not
          you need to upgrade:
          $ cd $ORACLE_HOME/ord/im/admin
          $ sqlplus /nolog
          SQLconnect sys/passwd_for_sys as SYSDBA
          SQL@imdbma.sql
          >
          This script displays one of the following strings:
          NOT_INSTALLED - if no prior release of interMedia components
          were installed on your system. You must install
          interMedia, rather than an upgrade.
          INSTALLED - if interMedia release 9.0.1 is already installed
          u080nnn0.sql - the script that performs the upgrade. nnn
          is the release of interMedia or Image Cartridge
          that is currently installed. For example,
          u0800050.sql upgrades from Image Cartridge
          release 8.0.5.0.0. Note: imdbma cannot
          distinguish between 8.0 releases of Image
          Cartridge. If you have an 8.0 release installed,
          the 8.0.5 script is always chosen.
          >
          3. ----------------------------------------------------------------------------------------
          >
          If an upgrade is required, invoke imuphelp to determine if your system
          is ready for an interMedia upgrade.
          $sqlplus /nolog
          SQLconnect sys/passwd_for_sys as sysdba
          SQL@imuphelp.sq l
          This script tells you:
          - if an earlier release of Audio must be deinstalled before upgrading
          - if an earlier release of Video must be deinstalled before upgrading
          Correct any problems found by imuphelp.sql before proceeding.
          >
          4. ----------------------------------------------------------------------------------------
          >
          Upgrade Oracle interMedia Common Files.
          $ cd $ORACLE_HOME/ord/admin
          $ sqlplus /nolog
          SQLconnect sys/passwd_for_sys as sysdba
          Run the appropriate script for the version you are coming from:
          >
          From Only Script to Run
          ==== =============== ===
          8.0.3 u0800030.sql
          8.0.4 u0800040.sql
          8.0.5 u0800050.sql
          8.0.6 u0800060.sql
          8.1.5 u0801050.sql
          8.1.6 u0801060.sql
          8.1.7 u0801070.sql
          >
          Enter the password for ORDSYS when the script asks for it.
          >
          5. ----------------------------------------------------------------------------------------
          >
          Upgrade interMedia.
          $ cd $ORACLE_HOME/ord/im/admin
          $ sqlplus /nolog
          SQLconnect sys/passwd_for_sys as sysdba
          Run the appropriate script for the version you are coming from:
          >
          From Only Script to Run
          ==== =============== ===
          8.0.3 u0800030.sql
          8.0.4 u0800040.sql
          8.0.5 u0800050.sql
          8.0.6 u0800060.sql
          8.1.5 u0801050.sql
          8.1.6 u0801060.sql
          8.1.7 u0801070.sql
          >
          Enter the password for ORDPLUGINS when the script asks for it and
          enter the password for ORDSYS when the script asks for it.
          >
          5. ----------------------------------------------------------------------------------------
          >
          Run the script imchk.sql to verify the upgrade connected as ORDSYS:
          $ cd $ORACLE_HOME/ord/im/admin
          $ Sqlplus ORDSYS/passwd_for_ords ys
          SQL@imchk.sql
          >
          6. ----------------------------------------------------------------------------------------
          >
          Restart the database:
          $ Sqlplus /nolog
          SQLconnect sys/passwd_for_sys as sysdba
          SQLShutdown immediate
          SQLstartup restrict
          >
          ---------------------------------------------------------------------------------------
          >
          >
          Appendix A: Obsolete parameters in 9i:
          --------------------------------------
          >
          _average_dirtie s_half_life
          _lm_statistics
          allow_partial_s n_results
          always_anti_joi n
          always_semi_joi n
          arch_io_slaves
          b_tree_bitmap_p lans
          backup_disk_io_ slaves
          cache_size_thre shold
          cleanup_rollbac k_entries
          close_cached_op en_cursors
          compatible_no_r ecovery
          complex_view_me rging
          cpu_count
          db_block_checkp oint_batch
          db_block_lru_ex tended_statisti
          db_block_lru_la tches
          db_block_lru_st atistics
          db_block_max_di rty_target
          db_file_simulta neous_writes
          delayed_logging _block_cleanout
          discrete_transa ctions_enabled
          distributed_loc k_timeout
          distributed_rec overy_connectio
          fast_full_scan_ enabled
          freeze_DB_for_f ast_instance_re
          gc_defer_time
          gc_latches
          gc_lck_procs
          gc_releasable_l ocks
          gc_rollback_loc ks
          hash_multiblock _io_count
          instance_nodese t
          job_queue_inter val
          job_queue_keep_ connections
          large_pool_min_ alloc
          lgwr_io_slaves
          lm_locks
          lm_procs
          lm_procs
          lm_ress
          lock_sga_areas
          log_block_check sum
          log_files
          log_simultaneou s_copies
          log_small_entry _max_size
          ogms_home
          ops_admin_group
          ops_interconnec ts
          optimizer_perce nt_parallel
          optimizer_searc h_limit
          parallel_defaul t_max_instances
          parallel_min_me ssage_pool
          parallel_server _idle_time
          parallel_transa ction_resource_
          push_join_predi cate
          row_cache_curso rs
          sequence_cache_ entries
          sequence_cache_ hash_buckets
          shared_pool_res erved_min_alloc
          snapshot_refres h_interval
          snapshot_refres h_keep_connecti
          snapshot_refres h_processes
          sort_direct_wri tes
          sort_multiblock _read_count
          sort_read_fac
          sort_spacemap_s ize
          sort_write_buff er_size
          sort_write_buff ers
          spin_count
          temporary_table _locks
          text_enable
          use_ism

          Comment

          Working...