Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Determining sizing requirements for Oracle databases

Before running BMC BladeLogic Data Migration Manager, you must ensure that your Oracle database has the free space required for successful data migration to version 8.5. To determine those requirements, use the sizing_8x_temp_undo.sql script provided by BMC Server Automation. 

The script provides minimum space requirements for these migration paths:

  • Migration from version 8.3.x to version 8.5.00
  • Migration from version 8.2.x to version 8.3.00
  • Migration from version 8.1.x to version 8.2.00
  • Migration from version 8.0.x to version 8.1.00
  • Migration from version 7.6.x or 7.7.x to 8.0, when executed as part of a chained migration to 8.1.0.

The script provides space requirements for these Oracle space characteristics:

  • UNDO tablespace size
  • TEMP tablespace size
  • Extra free space in the tablespace holding the table data
  • Extra free space in the tablespace holding the index data

Before you begin

Locate the sizing_8x_temp_undo.sql script. If you extract the entire contents of external-files.zip, the script is located in the /db_scripts/oracle/utility/migration_sizing_8x_temp_undo directory.

To determine minimum size requirements for Oracle data migration

  1. Use the following command to execute the sizing script:

    sqlplus <blcore_db_username>/<password>@<connectIdentifier> @sizing_8x_temp_undo.sql

    Where:

    • <blcore_db_username> is the database user name
    • <connectIdentifier> is a TNS alias, a fully qualified TNS connection descriptor, an EZ-Connect string, or an instance System Identifier (SID)

      Example

      sqlplus bladelogic/mypassword@blade @sizing_8x_temp_undo.sql

    The script creates an output file (sizing_ora_mig_to_850_output.txt) in the directory in which you executed the command.
    The output includes these sections:

    • Migration Path 8.3.x to 8.5.0
    • Migration Path 8.2.x to 8.3.0
    • Migration Path 8.1.x to 8.2.0
    • Migration Path 8.0.x to 8.1.x
    • Migration Path 7.6.x or 7.7.x to 8.0
  2. Use the output to compare the value for each resource of a migration path (TEMP, UNDO, data free space, and index free space) to its corresponding value in the other paths of your data migration. Select the largest value as the minimum space requirement for each resource.
    BMC recommends a minimum size requirement of no less than 4 GB for each resource.
    For example, suppose you are migrating data from version 7.6.x or 7.7.x to version 8.2.0. If TEMP SPACE REQUIREMENTS has the following values:
    • Migration Path 8.1.x to 8.2.0: 7.9 GB
    • Migration Path 8.0.x to 8.1.x: 72.22 GB
    • Migration Path 7.6.x or 7.7.x to 8.0: 300.69 GB

    You would use 300.69 GB as the minimum requirement for TEMP SPACE.

    It is assumed that no other load is placed on the database instance during the migration process; that is, application services are down and no other applications are competing for shared server resources.

  3. If your environment is shared with other applications, after you determine the TEMP and UNDO disk space requirements for migrating your BMC Server Automation data, add those to the cumulative minimum requirements for TEMP and UNDO disk space for your other applications. Before executing the data upgrade, make sure that the total TEMP disk space requirements and total UNDO disk space requirements for BMC BladeLogic Data Migration Manager and all other applications are available.
    The following table shows an example:

    Application

    TEMP Disk Space Requirement

    UNDO Disk Space Requirement

    BMC Server Automation

    20 GB

    18 GB

    App1

    15 GB

    16 GB

    App2

    10 GB

    12 GB

    Total Requirement:

    45 GB

    46 GB

Note

These guidelines assume that you do not use archive logging while the BMC BladeLogic Data Migration Manager is executing. If for some reason you cannot turn off archive logging in your environment, you need to allocate additional archive log space for the duration of the data upgrade.

Where to go from here

Migrate your database. See Migrating your database by using BMC BladeLogic Data Migration Manager.

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Pedro Barbero iglesias

    I am very sorry but... it seems that sizing_8x_temp_undo.sql doesn't contemplates the upgrade path to version 8.5.x. This must be wrong and someone should clarify it. 

    Feb 11, 2015 04:54
    1. Yechezkel Schatz

      Hi, Pedro. Do you mean to say that you recently used the script and it did not give any information about an upgrade path to 8.5? Were you prompted to submit your comment when you saw that I just now added mention of 8.5 on this page? Please clarify and I'll research this issue further. Thanks, Yechezkel

      Feb 11, 2015 05:24
      1. Pedro Barbero iglesias

        I haven't tried that out yet... but I will do it soon. I just wanted make notice that the documentation sometimes it is a little bit confusing, that's all.

        I will update the post , as soon as I run the script. :o)

        Regards.

        Feb 11, 2015 05:36
        1. Yechezkel Schatz

          Thanks, Pedro. I added the missing upgrade path in a new bulleted line in step 1. One of the developers assured me that the script works for this upgrade path as well.

           

          Feb 12, 2015 04:49