Results 1 to 8 of 8
  1. #1
    Join Date
    Apr 2003
    Location
    Los Alamos/Santa Fe, NM
    Posts
    69

    Angry Unanswered: problems migrating from 8.1.7 to 9i??

    Anyone else out there having problems migrating a Java application from 8.1.7 to 9i? What was the problem and how did you resolve it?

    Thanks.
    Michellea Southern-David

  2. #2
    Join Date
    Apr 2003
    Location
    Los Alamos/Santa Fe, NM
    Posts
    69

    addition

    The problem I am having is that the code I am running runs 30 sec on 8.1.7 and 20 min on 9.2.0. I tested the code on the server runing Solaris 5.8 and Oracle 8.1.7, then I cleared the server reinstalled Solaris 5.8 and Oracle 9.2.0.

    Again I am using the same code, same server, same db build, and same init.ora file. Just different database versions. The server is E450.

    Is there something I need to change when building the 9.2.0 database with the ddl? I am also using the Oracle java thin driver for the application.

    Any ideas??
    Michellea Southern-David

  3. #3
    Join Date
    Jul 2003
    Posts
    2,296
    check indexes etc.

    also, what is your compatible parameter set to on the 9i db?

    I also do not suggest using the EXACT same init.ora since you
    have many parameters no longer used in 9i that you had in 8i.

    Not to mention using UNDO instead of rollback and tons of other stuff.
    - The_Duck
    you can lead someone to something but they will never learn anything ...

  4. #4
    Join Date
    Apr 2003
    Location
    Los Alamos/Santa Fe, NM
    Posts
    69

    oh no..I need to take a oracle 9i db class

    and I thought 8.1.7 to 9i would be basicly the same. Stupid me.

    Undo instead of rollbacks...I really need to look into that thanks.
    The indexes look just fine.

    Here is the init.ora file -
    db_name = %%SID%%
    instance_name = %%SID%%
    service_names = %%SID%%
    control_files = (%%CONTROL_FILES%%)


    timed_statistics = %%TIMED_STATISTICS%%
    sql_trace = %%SQL_TRACE%%
    max_dump_file_size = %%MAX_DUMP_SIZE%%


    db_block_buffers = %%DB_BLOCK_BUFFERS%%
    db_block_size = %%DB_BLOCK_SIZE%%


    shared_pool_size = %%SHARED_POOL_SIZE%%
    java_pool_size = %%JAVA_POOL_SIZE%%
    large_pool_size = %%LARGE_POOL_SIZE%%


    log_checkpoint_interval = %%LOG_CHECKPOINT_INTERVAL%%
    log_checkpoint_timeout = %%LOG_CHECKPOINT_TIMEOUT%%
    processes = %%PROCESSES%%
    open_cursors = %%OPEN_CURSORS%%


    #sort_area_retained_size = %%SORT_AREA_RETAINED_SIZE%%
    #sort_area_size = %%SORT_AREA_SIZE%%


    db_file_multiblock_read_count = %%DB_FILE_MULTIBLOCK_READ_COUNT%%


    parallel_max_servers = %%PARALLEL_MAX_SERVERS%%
    #dml_locks = 200


    audit_trail = %%AUDIT_TRAIL%%
    #timed_statistics = %%TIMED_STATISTICS%%


    #max_dump_file_size = %%MAX_DUMP_FILE_SIZE%%



    #Uncommenting the line below will cause automatic archiving
    #if archiving has been enabled using
    #ALTER DATABASE ARCHIVELOG;


    log_archive_start = %%LOG_ARCHIVE_START%%
    log_buffer = %%LOG_BUFFER%%
    log_archive_dest = %%LOG_ARCHIVE_DEST%%
    log_archive_format = %%LOG_ARCHIVE_FORMAT%%



    #If using public rollback segments, define how many rollback segments each instance will pick up
    #using the formula, number of rollback segments = transactions/ transactions_per_rollback_Segment
    #In this example each instance will grab 40/5 = 8;
    # transactions = 40
    # transactions_per_rollback_segment = 5



    utl_file_dir = %%UTL_FILE_DIR%%
    background_dump_dest = %%BACKGROUND_DUMP_DEST%%
    core_dump_dest = %%CORE_DUMP_DEST%%
    user_dump_dest = %%USER_DUMP_DEST%%


    os_authent_prefix = ""


    #job_queue_processes = %%JOB_QUEUE_PROCESSES%%
    #job_queue_interval = %%JOB_QUEUE_INTERVAL%%
    #distributed_transactions = %%DISTRIBUTED_TRANSACTIONS%%
    #open_links = %%OPEN_LINKS%%



    #Uncomment the following line if you wish to enable the Oracle Trace product
    #to trace server activity. This enables scheduling of server collections
    #from Oracle Enterprise Manager Console.
    #Also, if the oracle_trace_collection_name parameter is non-null,
    #every session will write to the named collection, as well as enabling
    #you to schedule future collections from the console.
    # oracle_trace_enable = TRUE


    # remote_login_passwordfile = shared
    # text_enable = TRUE


    #The following parameters are needed for the Advanced
    #Replication Option
    # job_queue_processes = 2
    # job_queue_interval = 10


    # open_links = 4



    #Parameter added by Data Migration Assistant
    compatible = 8.1.6
    db_domain = world
    query_rewrite_enabled = true
    Michellea Southern-David

  5. #5
    Join Date
    Apr 2003
    Location
    Los Alamos/Santa Fe, NM
    Posts
    69

    9i supports both rollback and undo

    http://www.dbasupport.com/oracle/ora9i/undo.shtml

    This article states that both UNDO and Rollback tablespaces can be used in 9i. Just an FYI...although I am still checking into the new UNDO tablespaces.
    Michellea Southern-David

  6. #6
    Join Date
    Jul 2003
    Posts
    2,296

    Re: 9i supports both rollback and undo

    Originally posted by msouthern
    http://www.dbasupport.com/oracle/ora9i/undo.shtml

    This article states that both UNDO and Rollback tablespaces can be used in 9i. Just an FYI...although I am still checking into the new UNDO tablespaces.
    Well, yes, you are correct, but 9i auto-manages UNDO while YOU have
    to manage rollback. I was just giving an example of the differences.

    Another example is you don't need db_block_buffers and in their place
    you use db_cahe_size, db_keep_cache_size, and other parameters
    (did I list those correctly?).

    All old parameters still work, but then you are not using the full
    capabilities of 9i. There is also a 'compatable' clause which you would
    want to set to your 9i version (ex: compatible = "9.2.0.4")

    I just started on 9i in June and DEFINITELY got a wakeup call. there
    are MANY MANY differences and I am still learning a great deal myself.

    Sometimes the hard way
    - The_Duck
    you can lead someone to something but they will never learn anything ...

  7. #7
    Join Date
    Apr 2003
    Location
    Los Alamos/Santa Fe, NM
    Posts
    69

    UG..

    Yep...you are right UNDO tablespaces are better.
    Do you use Uniform or Auto locally managed tablespaces?
    Did you reconfigure your system tablespace to be locally managed? How did it work for you?

    I see what you mean. Lots of parameters discontinued. Lots of new parameters.

    The main thing that Oracle changed that affected our application was the oracle Java driver location. It went from Oracle.jdbc.driver.OracleDriver to Oracle.jdbc.OracleDriver. That one thing really effected our preformance. The query I was tuning went from 20 min to 6 sec. Weird how that works.
    Michellea Southern-David

  8. #8
    Join Date
    Apr 2003
    Location
    Los Alamos/Santa Fe, NM
    Posts
    69

    Duck

    BTW...Thanks for the information and help.
    Michellea Southern-David

Posting Permissions

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