DBAsupport.com Forums - Powered by vBulletin
Results 1 to 3 of 3

Thread: How to upgrate 817(32bit) to 817(64bit)?

  1. #1
    Join Date
    Mar 2001

    Question How to upgrate 817(32bit) to 817(64bit)?

    I want to install the 817(64bit) software and use the old datafiles to startup database, is it ok? TIA!

  2. #2
    Join Date
    May 2004
    To Convert to 64 bit, Yes you will still be using the same datafiles.

    If you have access to metalink. Then you could see the doc there however below are the steps for the same as well. The steps below apply to 8.1.7.x for your version you may have to get the relevant patches.

    Solution Description
    The solution here is a walkthrough of doing a word conversion considering that
    you are going to upgrade from (32-bit) to (64-bit). This
    applies if you are running Java inside the database. For databases running
    Oracle Apps, please note that certain apps-specific patches may also be
    1) Shutdown your 32-bit database. Shutdown the listener.
    2) Take a cold backup of this database.
    3) Install Oracle RDBMS (64-bit)
    4) Apply patchset (64-bit) to this oracle home.
    5) Copy your init.ora from the 32-bit home to the 64-bit home.
    6) Edit the init.ora of the 64-bit ORACLE_HOME so that the following
    parameters are set as follows:
    aq_tm_processes = 0
    job_queue_processes = 0
    _system_trig_enabled = FALSE
    db_block_buffers= (at least 2000)
    shared_pool_size= (at least 150MB)
    java_pool_size= (at least 20MB)
    7) sqlplus internal or sys , startup restrict your database using the ORACLE HOME of
    8) delete from duc$ where pack='JIS$INTERCEPTOR$' and proc='USER_DROPPED';

    9) Go to Metalink, select Patches, and put in 1994933 for the 'Patch Number'.
    It will come up with a patch saying that it is for HP, but it is actually
    generic for Oracle on all platforms.
    After downloading the patch, extract it and keep track of where you put the rmsro.sql and invalidate.sql files.
    10) Now run the following, again from sql*plus connected as internal or sys:
    SQL> @?/javavm/install/initjvmaux.sql
    SQL> @/rmsro.sql
    SQL> call rmsro.run();
    SQL> @/invalidate.sql
    11) shutdown normal the database
    12) If you are following this procedure because you are converting word size
    from 32-bit to 64-bit **ON SOLARIS**, then you also need
    to apply another fix.
    Go to Metalink, select Patches, and put in 2209569 for the 'Patch Number'.
    After downloading the patch, extract it and put the classes.bin file from
    the downloaded patch into $ORACLE_HOME/javavm/admin. This will replace the
    classes.bin file which is already there.
    13) Startup restrict your 64-bit database
    14) Sql*plus internal or sys and type
    SQL> create or replace java system
    2 /
    15) Shutdown the database
    16) Startup restrict the database, connect as internal or sys and run
    SQL> @?/rdbms/admin/utlrp.sql;
    -- To check on the progress of utlrp.sql, you can open a second sql
    prompt and do a select count(*) from dba_objects where status!='VALID';
    This count should keep decreasing as the script progresses to
    revalidate all the objects.
    -- If you get an ORA-29554 unhandled Java out of memory condition error,
    simply rerun utlrp.sql again and it will pick up where it left off.
    17) Shutdown the database
    (Note: you may get an ORA-600 [729] error which is a harmless memory leak.
    If that is the case, simply do a shutdown abort before continuing)
    18) Change the _SYSTEM_TRIG_ENABLED parameter in your init.ora as follows.
    19) Startup restrict, connect as internal or sys and run:
    SQL> insert into duc$ (owner, pack, proc, field1, operation#, seq)
    values ('SYS','JIS$INTERCEPTOR$','USER_DROPPED',0,1,1);
    SQL> commit;
    20) shutdown the database
    21) Modify the database startup parameters JOB_QUEUE_PROCESSES and
    AQ_TM_PROCESSES (and shared_pool_size/java_pool_size/db_block_buffers if
    you modified them earlier) back to their original values.
    22) restart the database
    23) check that you are able to startup & shutdown normally the database
    without hanging anywhere.

  3. #3
    Join Date
    Aug 2000
    Jolo, Sulu
    whewwww....can i just use export/import from the 32-bit db to the 54-bit db?

Posting Permissions

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

Click Here to Expand Forum to Full Width