Bookshelf Home | Contents | Index | PDF     

Oracle® Business Intelligence Applications Upgrade Guide > Upgrading Oracle BI Applications >

Migrating Data into the Upgraded Data Warehouse

To migrate data into the upgraded data warehouse, follow the appropriate procedure listed in Table 3 based on the version of Analytics from which you are upgrading.

Table 3. Procedures for Migrating Data
From Version
Procedure

Siebel Analytics 7.5.x (Horizontal)

Siebel Business Analytics 7.7, 7.7.1.x, or 7.8 (Horizontal)

Siebel Industry Applications 7.5.x (Vertical)

Siebel Industry Applications 7.7, 7.7.1.x, or 7.8 (Vertical)

Life Sciences 7.8.0, 7.8.1, or 7.8.2 (Vertical)

To migrate data from version 7.5.x to 7.9 (Horizontal)

NOTE:  Upgrading from version 7.5.x requires two stages. In the first stage, you upgrade the data warehouse schema and migrate the data from version 7.5.x to 7.7. In the second stage, you upgrade the data warehouse schema and migrate the data from version 7.7 to 7.9.

  1. Upgrade the data warehouse schema from version 7.5.x to 7.7 by using the DDLimp utility to run the script ddlsme_HOR_77.ctl script.
    1. Navigate to the folder OracleBI\dwrep\Upgrade\CTLFiles.
    2. Use the DDLimp utility to run the ddlsme_HOR_77.ctl script. Use the following command:

    ..\OracleBI\dwrep\bin\DDLIMP /U <USER> /P <PASSWORD> /C <ODBC connect string>
    /G SSE_ROLE /R Y /F <..\OracleBI\dwrep\ddlsme_HOR_77.ctl>
    /L <..\oracleBI\dwrep\ddlsme_HOR_77.log>

    For example:

    DDLIMP /U SADMIN /P SADMIN /C SIEBEL_OLTP /G SSE_ROLE
    /R Y /F C:\OracleBI\dwrep\ddlsme_HOR_77.ctl /L C:\OracleBI\dwrep\ddlsme_HOR_77.log

    Notes:

    • /P <PASSWORD> - The password for Oracle's CRM OLTP.
    • /C <ODBC connect string> - The name of the ODBC connect string.
    • For Oracle databases, use the Siebel Merant ODBC Drivers.
    • In addition, you can use the following commands:
    • /W Y - If the OLTP database is Oracle and Unicode.
    • /Z Y - If the OLTP database is DB2 or SQL Server and Unicode.
    • /B <TABLE_SPACE_NAME> - If you want to create these tables in a separate table space. For DB2, This must be specified as 32K tablespace.
    • /X <INDEX_TABLE_SPACE_NAME> - If you want to create the indexes in a separate tablespace. For DB2, This must be specified as 32K tablespace.
    • /Y - Storage File for DB2/390.
    • /R - Regrant tables.
  2. Copy the file Upgrade.rep file from the folder OracleBI\dwrep\Upgrade\Informatica\Repository into the folder Informatica PowerCenter 7.1.4\RepositoryServer\bin\Backup.
  3. Launch the Informatica Repository Console and restore Upgrade.rep (located in Informatica PowerCenter 7.1.4\RepositoryServer\bin\Backup).
  4. Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\ParameterFiles and copy the file 753_TENERIFE_UPG_PARAMS.txt into the SrcFiles folder on the Informatica Server machine, for example, C:\Program Files\Informatica PowerCenter 7.1.4\Server\SrcFiles.
  5. Rename 753_TENERIFE_UPG_PARAMS.txt to TENERIFE_UPG_PARAMS.txt.
  6. In Informatica Workflow Manager, navigate to the folder UPGRADE_753_to_770_HOR, and execute the following workflows in the order indicated:
    1. Upgrade_R_Image
    2. Upgrade_Unspecifieds
    3. Upgrade_Agree
    4. Upgrade_Asset
    5. Upgrade_Opty
    6. Upgrade_Order
    7. Upgrade_Quote
    8. Upgrade_Response
    9. Upgrade_ServiceRequest
    10. Upgrade_Others
    11. Upgrade_Visibility
    12. UpgradeSlowlyChangingDimensionStartDates
    13. DAC_Metadata_Upgrade_Workflow
  7. Upgrade the data warehouse schema from version 7.7 to 7.9 by following the steps in the procedure To upgrade the data warehouse schema.
  8. Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\SrcFiles and copy the *.csv files into the SrcFiles folder on the Informatica Server machine, for example, C:\Program Files\Informatica PowerCenter 7.1.4\Server\SrcFiles.
  9. Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\ParameterFiles and copy the file 770_TENERIFE_UPG_PARAMS.txt into the SrcFiles folder on the Informatica Server machine, for example, C:\Program Files\Informatica PowerCenter 7.1.4\Server\SrcFiles.
  10. Rename 770_TENERIFE_UPG_PARAMS.txt to TENERIFE_UPG_PARAMS.txt.
  11. In the file TENERIFE_UPG_PARAMS.txt:
    1. Search for the parameter $$SourceConnection.
    2. Set the value to one of the following options, based on your Siebel applications (OLTP) version:
      • SEBL_63
      • SEBL_753
      • SEBL_771
      • SEBL_78
      • SEBL_80
      • SEBL_VERT_753
      • SEBL_VERT_771
      • SEBL_VERT_78
      • SEBL_VERT_80

        For example, if your Siebel applications (OLTP) version is Siebel Industry Applications 7.5.x, the parameter should appear as:

    $$SourceConnection=SEBL_VERT_753

  12. In the file TENERIFE_UPG_PARAMS.txt:
    1. Search for the parameter $$Source_Container.
    2. Set the value to one of the following options, based on your Siebel applications (OLTP) version:
      • Siebel 6.3
      • Siebel 7.5.3
      • Siebel 7.5.3 Vertical
      • Siebel 7.7.1
      • Siebel 7.7.1 Vertical
      • Siebel 7.8
      • Siebel 7.8 Vertical
      • Siebel 8.0
      • Siebel 8.0 Vertical

        For example, if your Siebel applications (OLTP) version is Siebel Industry Applications 7.5.x, the parameter should appear as:

    $$Source_Container=Siebel 7.5.3 Vertical

  13. In the file TENERIFE_UPG_PARAMS.txt, edit the ETL_PROC_WID parameter as follows:

    MPLT_GET_ETL_PROC_WID.$$ETL_PROC_WID=<latest ETL_PROC_WID value from your database>

    You can get this value from W_PARAM_G.ETL_PROC_WID.

  14. In the Informatica Workflow Manager, open the Relational Connection Browser (Connections > Relational), and do the following:
    1. Edit the preconfigured ODBC connection PARAM_OLTP_SIEBEL to point to the Siebel transactional database.
    2. Edit the preconfigured ODBC connection DataWarehouse to point to the newly upgraded data warehouse database.
    3. Edit the preconfigured ODBC connection PARAM_DAC_OLD to point to the previous DAC repository database (the version from which you are upgrading).
    4. Edit the preconfigured ODBC connection PARAM_DAC_NEW to point to the new DAC repository database (the version to which you are upgrading).
  15. In Informatica Workflow Manager, navigate to the folder UPGRADE_770_to_79, and execute the following workflows in the order indicated:
    1. MARKETING_LOAD
    2. Update_Dimensions
    3. Update_Dimension_Unspecified
    4. Update_Facts
    5. SIL_PositionDimensionHierarchy_Full
    6. Load_INT_ORG_DH
    7. DIMENSION_LOAD
    8. DIMENSION_UNSPECIFIED_UPDATE
    9. FACT_UPDATE
  16. Run the Reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs:
    1. Navigate to the directory \OracleBI\dwrep\Upgrade\DbScripts\<database type>.
    2. Open the Reset_infa_seq_gen.bat script, and review the parameters at the top of the file.
    3. Replace the existing values for the parameters to reflect your environment (the parameters are database-specific).

      For Oracle databases:

      Parameter
      Setting

      TARGET_USERID_PWD

      <olap schema user-name>/<olap schema password>@<olap database TNS name>

      For example:

      TARGET_USERID_PWD=siebel/siebel@siebel_olap

      INFA_USERID_PWD

      <user-name of Informatica Repository database that contains the adapter mappings repository metadata>/<password of the Informatica Repository database>@<TNS name of the database for the Informatica Repository>

      For example:

      INFA_USERID_PWD=INFAREP/INFAREP@infa.corp.siebel.com

      INFA_REP

      Name of the Informatica Repository where the adapter mappings are available.

      INFA_U

      User name of the administrator of the Informatica Repository.

      INFA_P

      Password for the administrator of the Informatica Repository.

      INFA_SRV

      Name of the Informatica Server.

      For Microsoft SQL Server databases:

      Parameter
      Setting

      OLAP_SERVER

      Name of the SQL Server for the OLAP database.

      OLAP_DB

      Name of the database on which OLAP data is available.

      OLAP_U

      User name for logging into the database on which OLAP data is available.

      OLAP_P

      Password for logging into the database on which OLAP data is available.

      INFA_SERVER

      Name of the SQL Server for the Informatica Repository database.

      INFA_DB

      Name of the database on which Informatica Repository metadata is available.

      INFA_U

      User name for logging into the database on which Informatica Repository metadata is available.

      INFA_P

      Password for logging into the database on which Informatica Repository metadata is available.

      INFA_REP

      Name of the Informatica Repository where adapter mappings are available.

      INFA_REP_U

      User name of the administrator of the Informatica Repository.

      INFA_REP_P

      Password of the administrator of the Informatica Repository.

      For IBM DB2 databases:

      Parameter
      Setting

      TARGET_USERID_PWD

      <olap schema user-name>/<olap schema password>@<olap database name>

      For example:

      TARGET_USERID_PWD=siebel/db2@OLAP_DB2DB

      INFA_USER

      User name for logging into the database on which Informatica metadata is available.

      INFA_PWD

      Password for logging into the database on which Informatica Repository metadata is available.

      INFADB_ALIAS

      Name of the database in which Informatica Repository metadata is available.

      INFA_REP

      Name of the Informatica Repository where the adapter mappings are available.

      INFA_U

      User name of the administrator of the Informatica Repository.

      INFA_P

      Password of the administrator of the Informatica Repository.

      INFA_SRV

      Name of the Informatica Server.
    4. Run the script.

      NOTE:  Because the Reset_infa_seq_gen.bat file contains user names and passwords, it is recommended that you delete the file after the upgrade process is complete.

  17. To verify the data migrated successfully:
    1. Check whether any of the Informatica mapping log files stored in the directory \Informatica PowerCenter 7.1.4\Server\SessLogs indicates errors or failures.
    2. Check whether the SQL scripts (790_UPGRADE_PRE_CTL_SCRIPT.sql and 790_UPGRADE_PRE_DIMENSION_SCRIPT.sql) that you ran in the SQL client of the database failed or errored out while executing.
    3. Check the log files for the CTL files (Upgrade.ctl and DW.ctl) that you ran using the DDLimp command to determine whether any of the runs failed.

      If you did not detect any errors or failures in the steps above, then the data migration was successful.

  18. (Optional) If the data migration was successful, drop the tables that were created during the upgrade process, such as, W_xxxx_x_784 tables, LKP_xxxx_x, and W_ASSET_D_TMP.

    This step frees the space occupied by these backup tables.

To migrate data from versions 7.7, 7.7.1.x, or 7.8 to 7.9 (Horizontal)

  1. Copy the file Upgrade.rep file from the folder OracleBI\dwrep\Upgrade\Informatica\Repository into the folder Informatica PowerCenter 7.1.4\RepositoryServer\bin\Backup.
  2. Launch the Informatica Repository Console and restore Upgrade.rep (located in Informatica PowerCenter 7.1.4\RepositoryServer\bin\Backup).
  3. Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\SrcFiles and copy the *.csv files into the SrcFiles folder on the Informatica Server machine, for example, C:\Program Files\Informatica PowerCenter 7.1.4\Server\SrcFiles.
  4. Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\ParameterFiles and copy the file <previous version of Siebel Analytics>_TENERIFE_UPG_PARAMS.txt into the SrcFiles folder on the Informatica Server machine, for example, C:\Program Files\Informatica PowerCenter 7.1.4\Server\SrcFiles.
  5. Rename the file <previous version of Siebel Analytics>_TENERIFE_UPG_PARAMS.txt to TENERIFE_UPG_PARAMS.txt.
  6. In the file TENERIFE_UPG_PARAMS.txt:
    1. Search for the parameter $$SourceConnection.
    2. Set the value to one of the following options, based on your Siebel applications (OLTP) version:
      • SEBL_63
      • SEBL_753
      • SEBL_771
      • SEBL_78
      • SEBL_80
      • SEBL_VERT_753
      • SEBL_VERT_771
      • SEBL_VERT_78
      • SEBL_VERT_80

        For example, if your Siebel applications (OLTP) version is Siebel Industry Applications 7.5.x, the parameter should appear as:

    $$SourceConnection=SEBL_VERT_753

  7. In the file TENERIFE_UPG_PARAMS.txt:
    1. Search for the parameter $$Source_Container.
    2. Set the value to one of the following options, based on your Siebel applications (OLTP) version:
      • Siebel 6.3
      • Siebel 7.5.3
      • Siebel 7.5.3 Vertical
      • Siebel 7.7.1
      • Siebel 7.7.1 Vertical
      • Siebel 7.8
      • Siebel 7.8 Vertical
      • Siebel 8.0
      • Siebel 8.0 Vertical

        For example, if your Siebel applications (OLTP) version is Siebel Industry Applications 7.5.x, the parameter should appear as:

    $$Source_Container=Siebel 7.5.3 Vertical

  8. In the file TENERIFE_UPG_PARAMS.txt, edit the ETL_PROC_WID parameter as follows:

    MPLT_GET_ETL_PROC_WID.$$ETL_PROC_WID=<latest ETL_PROC_WID value from your database>

    You can get this value from W_PARAM_G.ETL_PROC_WID.

  9. In the Informatica Workflow Manager, open the Relational Connection Browser (Connections > Relational), and do the following:
    1. Edit the preconfigured ODBC connection PARAM_OLTP_SIEBEL to point to the Siebel transactional database.
    2. Edit the preconfigured ODBC connection DataWarehouse to point to the newly upgraded data warehouse database.
    3. Edit the preconfigured ODBC connection PARAM_DAC_OLD to point to the previous DAC repository database (the version from which you are upgrading).
    4. Edit the preconfigured ODBC connection PARAM_DAC_NEW to point to the new DAC repository database (the version to which you are upgrading).
  10. In the Informatica Workflow Manager, navigate to the appropriate folder and execute the workflows in the order specified:
Application Version
Folder Name
Workflow

7.7 to 7.9 (Horizontal)

UPGRADE_770_to_79
  1. MARKETING_LOAD
  2. Update_Dimensions
  3. Update_Dimension_Unspecified
  4. Update_Facts
  5. SIL_PositionDimensionHierarchy_Full
  6. Load_INT_ORG_DH
  7. DIMENSION_LOAD
  8. DIMENSION_UNSPECIFIED_UPDATE
  9. FACT_UPDATE
  10. DAC_Metadata_Upgrade_Workflow

7.7.1.x to 7.9 (Horizontal)

UPGRADE_771_to_79
  1. Update_Dimensions
  2. Update_Dimension_Unspecified
  3. Update_Facts
  4. SIL_PositionDimensionHierarchy_Full
  5. Load_INT_ORG_DH
  6. DIMENSION_LOAD
  7. DIMENSION_UNSPECIFIED_UPDATE
  8. FACT_UPDATE
  9. DAC_Metadata_Upgrade_Workflow

7.8 to 7.9 (Horizontal)

UPGRADE_78_to_79
  1. SIL_PositionDimensionHierarchy_Full
  2. Load_INT_ORG_DH
  3. DIMENSION_LOAD
  4. DIMENSION_UNSPECIFIED_UPDATE
  5. FACT_UPDATE
  6. DAC_Metadata_Upgrade_Workflow
  1. Run the Reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs:
    1. Navigate to the directory \OracleBI\dwrep\Upgrade\DbScripts\<database type>.
    2. Open the Reset_infa_seq_gen.bat script, and review the parameters at the top of the file.
    3. Replace the existing values for the parameters to reflect your environment (the parameters are database-specific).

      For Oracle databases:

      Parameter
      Setting

      TARGET_USERID_PWD

      <olap schema user-name>/<olap schema password>@<olap database TNS name>

      For example:

      TARGET_USERID_PWD=siebel/siebel@siebel_olap

      INFA_USERID_PWD

      <user-name of Informatica Repository database that contains the adapter mappings repository metadata>/<password of the Informatica Repository database>@<TNS name of the database for the Informatica Repository>

      For example:

      INFA_USERID_PWD=INFAREP/INFAREP@infa.corp.siebel.com

      INFA_REP

      Name of the Informatica Repository where the adapter mappings are available.

      INFA_U

      User name of the administrator of the Informatica Repository.

      INFA_P

      Password for the administrator of the Informatica Repository.

      INFA_SRV

      Name of the Informatica Server.

      For Microsoft SQL Server databases:

      Parameter
      Setting

      OLAP_SERVER

      Name of the SQL Server for the OLAP database.

      OLAP_DB

      Name of the database on which OLAP data is available.

      OLAP_U

      User name for logging into the database on which OLAP data is available.

      OLAP_P

      Password for logging into the database on which OLAP data is available.

      INFA_SERVER

      Name of the SQL Server for the Informatica Repository database.

      INFA_DB

      Name of the database on which Informatica Repository metadata is available.

      INFA_U

      User name for logging into the database on which Informatica Repository metadata is available.

      INFA_P

      Password for logging into the database on which Informatica Repository metadata is available.

      INFA_REP

      Name of the Informatica Repository where adapter mappings are available.

      INFA_REP_U

      User name of the administrator of the Informatica Repository.

      INFA_REP_P

      Password of the administrator of the Informatica Repository.

      For IBM DB2 databases:

      Parameter
      Setting

      TARGET_USERID_PWD

      <olap schema user-name>/<olap schema password>@<olap database name>

      For example:

      TARGET_USERID_PWD=siebel/db2@OLAP_DB2DB

      INFA_USER

      User name for logging into the database on which Informatica metadata is available.

      INFA_PWD

      Password for logging into the database on which Informatica Repository metadata is available.

      INFADB_ALIAS

      Name of the database in which Informatica Repository metadata is available.

      INFA_REP

      Name of the Informatica Repository where the adapter mappings are available.

      INFA_U

      User name of the administrator of the Informatica Repository.

      INFA_P

      Password of the administrator of the Informatica Repository.

      INFA_SRV

      Name of the Informatica Server.
    4. Run the script.

      NOTE:  Because the Reset_infa_seq_gen.bat file contains user names and passwords, it is recommended that you delete the file after the upgrade process is complete.

  2. To verify the data migrated successfully:
    1. Check whether any of the Informatica mapping log files stored in the directory \Informatica PowerCenter 7.1.4\Server\SessLogs indicates errors or failures.
    2. Check whether the SQL scripts (790_UPGRADE_PRE_CTL_SCRIPT.sql and 790_UPGRADE_PRE_DIMENSION_SCRIPT.sql) that you ran in the SQL client of the database failed or errored out while executing.
    3. Check the log files for the CTL files (Upgrade.ctl and DW.ctl) that you ran using the DDLimp command to determine whether any of the runs failed.

      If you did not detect any errors or failures in the steps above, then the data migration was successful.

  3. (Optional) If the data migration was successful, drop the tables that were created during the upgrade process, such as, W_xxxx_x_784 tables, LKP_xxxx_x, and W_ASSET_D_TMP.

    This step frees the space occupied by these backup tables.

To migrate data from version 7.5.x to 7.9 (Vertical)

NOTE:  Upgrading from version 7.5.x requires two stages. In the first stage, you upgrade the data warehouse schema and migrate the data from version 7.5.x to 7.7. In the second stage, you upgrade the data warehouse schema and migrate the data from version 7.7 to 7.9.

  1. Upgrade the data warehouse schema from version 7.5.x to 7.7 by using the DDLimp utility to run the script ddlsme_SIA_77.ctl script.
    1. Navigate to the folder OracleBI\dwrep\Upgrade\CTLFiles.
    2. Use the DDLimp utility to run the ddlsme_SIA_77.ctl script. Use the following command:

    ..\OracleBI\dwrep\bin\DDLIMP /U <USER> /P <PASSWORD> /C <ODBC connect string>
    /G SSE_ROLE /R Y /F <..\OracleBI\dwrep\ddlsme_SIA_77.ctl>
    /L <..\oracleBI\dwrep\ddlsme_SIA_77.log>

    For example:

    DDLIMP /U SADMIN /P SADMIN /C SIEBEL_OLTP /G SSE_ROLE
    /R Y /F C:\OracleBI\dwrep\ddlsme_SIA_77.ctl /L C:\OracleBI\dwrep\ddlsme_SIA_77.log

    Notes:

    • /P <PASSWORD> - The password for Oracle's CRM OLTP.
    • /C <ODBC connect string> - The name of the ODBC connect string.
    • For Oracle databases, use the Siebel Merant ODBC Drivers.
    • In addition, you can use the following commands:
    • /W Y - If the OLTP database is Oracle and Unicode.
    • /Z Y - If the OLTP database is DB2 or SQL Server and Unicode.
    • /B <TABLE_SPACE_NAME> - If you want to create these tables in a separate table space. For DB2, This must be specified as 32K tablespace.
    • /X <INDEX_TABLE_SPACE_NAME> - If you want to create the indexes in a separate tablespace. For DB2, This must be specified as 32K tablespace.
    • /Y - Storage File for DB2/390.
    • /R - Regrant tables.
  2. Copy the file Upgrade.rep file from the folder OracleBI\dwrep\Upgrade\Informatica\Repository into the folder Informatica PowerCenter 7.1.4\RepositoryServer\bin\Backup.
  3. Launch the Informatica Repository Console and restore Upgrade.rep (located in Informatica PowerCenter 7.1.4\RepositoryServer\bin\Backup).
  4. Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\ParameterFiles and copy the file 753_TENERIFE_UPG_PARAMS.txt into the SrcFiles directory on the Informatica Server machine, for example, C:\Program Files\Informatica PowerCenter 7.1.4\Server\SrcFiles.
  5. Rename the file 753_TENERIFE_UPG_PARAMS.txt to TENERIFE_UPG_PARAMS.txt.
  6. In Informatica Workflow Manager, navigate to the folder UPGRADE_753_to_770_SIA, and execute the following workflows in the order indicated:
    1. Upgrade_R_Image
    2. Upgrade_Unspecifieds
    3. Upgrade_Agree
    4. Upgrade_Asset
    5. Upgrade_Opty
    6. Upgrade_Order
    7. Upgrade_Quote
    8. Upgrade_Response
    9. Upgrade_ServiceRequest
    10. Upgrade_Others
    11. Upgrade_Visibility
    12. UpgradeSlowlyChangingDimensionStartDates
    13. Upgrade_Industry_R_Image
    14. Upgrade_Industry_Unspecified
    15. Upgrade_LS_ActivityProduct
    16. Upgrade_LS_Others
    17. Upgrade_Industry_Household
    18. Upgrade_FINS_Visibility
    19. UpgradeSlowlyChangingDimensionStartDates_Industry
    20. DAC_Metadata_Upgrade_Workflow
  7. Upgrade the data warehouse schema from version 7.7 to 7.9 by following the steps in the procedure To upgrade the data warehouse schema.
  8. Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\SrcFiles and copy the *.csv files into the SrcFiles folder on the Informatica Server machine, for example, C:\Program Files\Informatica PowerCenter 7.1.4\Server\SrcFiles.
  9. Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\ParameterFiles and copy the file 770_TENERIFE_UPG_PARAMS.txt into the SrcFiles folder on the Informatica Server machine, for example, C:\Program Files\Informatica PowerCenter 7.1.4\Server\SrcFiles.
  10. Rename 770_TENERIFE_UPG_PARAMS.txt to TENERIFE_UPG_PARAMS.txt.
  11. In the file TENERIFE_UPG_PARAMS.txt:
    1. Search for the parameter $$SourceConnection.
    2. Set the value to one of the following options, based on your Siebel applications (OLTP) version:
      • SEBL_63
      • SEBL_753
      • SEBL_771
      • SEBL_78
      • SEBL_80
      • SEBL_VERT_753
      • SEBL_VERT_771
      • SEBL_VERT_78
      • SEBL_VERT_80

        For example, if your Siebel applications (OLTP) version is Siebel Industry Applications 7.5.x, the parameter should appear as:

    $$SourceConnection=SEBL_VERT_753

  12. In the file TENERIFE_UPG_PARAMS.txt:
    1. Search for the parameter $$Source_Container.
    2. Set the value to one of the following options, based on your Siebel applications (OLTP) version:
      • Siebel 6.3
      • Siebel 7.5.3
      • Siebel 7.5.3 Vertical
      • Siebel 7.7.1
      • Siebel 7.7.1 Vertical
      • Siebel 7.8
      • Siebel 7.8 Vertical
      • Siebel 8.0
      • Siebel 8.0 Vertical

        For example, if your Siebel applications (OLTP) version is Siebel Industry Applications 7.5.x, the parameter should appear as:

    $$Source_Container=Siebel 7.5.3 Vertical

  13. In the file TENERIFE_UPG_PARAMS.txt, edit the ETL_PROC_WID parameter as follows:

    MPLT_GET_ETL_PROC_WID.$$ETL_PROC_WID=<latest ETL_PROC_WID value from your database>

    You can get this value from W_PARAM_G.ETL_PROC_WID.

  14. In the Informatica Workflow Manager, open the Relational Connection Browser (Connections > Relational), and do the following:
    1. Edit the preconfigured ODBC connection PARAM_OLTP_SIEBEL to point to the Siebel transactional database.
    2. Edit the preconfigured ODBC connection DataWarehouse to point to the newly upgraded data warehouse database.
    3. Edit the preconfigured ODBC connection PARAM_DAC_OLD to point to the previous DAC repository database (the version from which you are upgrading).
    4. Edit the preconfigured ODBC connection PARAM_DAC_NEW to point to the new DAC repository database (the version to which you are upgrading).
  15. Define the alignment rule to be used for ETL loads.
    1. Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\SrcFiles and copy the file AlignmentType_LS_782.csv into the SrcFiles folder on the Informatica Server machine, for example, C:\Program Files\Informatica PowerCenter 7.1.4\Server\SrcFiles.
    2. Rename the file AlignmentType_LS_782.csv to AlignmentType.csv.
    3. Open the file AlignmentType.csv, and enter one of the following alignment item types under the ALIGN_TYPE field:
      • Zipcode
      • Account/Contact
      • Brick
    4. Save the file.

      NOTE:  The Oracle Business Analytics Warehouse allows only one alignment type to be used for ETL loads during upgrade.

  16. In Informatica Workflow Manager, navigate to the folder UPGRADE_770_to_79, and execute the following workflows in the order indicated:
    1. MARKETING_LOAD
    2. Upgrade_Dimensions_Industry
    3. Update_Dimensions
    4. Update_Dimension_Unspecified
    5. Update_Facts
    6. Upgrade_LS_Dimensions
    7. Upgrade_LS_Facts
    8. SIL_PositionDimensionHierarchy_Full
    9. Load_INT_ORG_DH
    10. DIMENSION_LOAD
    11. DIMENSION_UNSPECIFIED_UPDATE
    12. FACT_UPDATE
  17. Run the Reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs:
    1. Navigate to the directory \OracleBI\dwrep\Upgrade\DbScripts\<database type>.
    2. Open the Reset_infa_seq_gen.bat script, and review the parameters at the top of the file.
    3. Replace the existing values for the parameters to reflect your environment (the parameters are database-specific).

      For Oracle databases:

      Parameter
      Setting

      TARGET_USERID_PWD

      <olap schema user-name>/<olap schema password>@<olap database TNS name>

      For example:

      TARGET_USERID_PWD=siebel/siebel@siebel_olap

      INFA_USERID_PWD

      <user-name of Informatica Repository database that contains the adapter mappings repository metadata>/<password of the Informatica Repository database>@<TNS name of the database for the Informatica Repository>

      For example:

      INFA_USERID_PWD=INFAREP/INFAREP@infa.corp.siebel.com

      INFA_REP

      Name of the Informatica Repository where the adapter mappings are available.

      INFA_U

      User name of the administrator of the Informatica Repository.

      INFA_P

      Password for the administrator of the Informatica Repository.

      INFA_SRV

      Name of the Informatica Server.

      For Microsoft SQL Server databases:

      Parameter
      Setting

      OLAP_SERVER

      Name of the SQL Server for the OLAP database.

      OLAP_DB

      Name of the database on which OLAP data is available.

      OLAP_U

      User name for logging into the database on which OLAP data is available.

      OLAP_P

      Password for logging into the database on which OLAP data is available.

      INFA_SERVER

      Name of the SQL Server for the Informatica Repository database.

      INFA_DB

      Name of the database on which Informatica Repository metadata is available.

      INFA_U

      User name for logging into the database on which Informatica Repository metadata is available.

      INFA_P

      Password for logging into the database on which Informatica Repository metadata is available.

      INFA_REP

      Name of the Informatica Repository where adapter mappings are available.

      INFA_REP_U

      User name of the administrator of the Informatica Repository.

      INFA_REP_P

      Password of the administrator of the Informatica Repository.

      For IBM DB2 databases:

      Parameter
      Setting

      TARGET_USERID_PWD

      <olap schema user-name>/<olap schema password>@<olap database name>

      For example:

      TARGET_USERID_PWD=siebel/db2@OLAP_DB2DB

      INFA_USER

      User name for logging into the database on which Informatica metadata is available.

      INFA_PWD

      Password for logging into the database on which Informatica Repository metadata is available.

      INFADB_ALIAS

      Name of the database in which Informatica Repository metadata is available.

      INFA_REP

      Name of the Informatica Repository where the adapter mappings are available.

      INFA_U

      User name of the administrator of the Informatica Repository.

      INFA_P

      Password of the administrator of the Informatica Repository.

      INFA_SRV

      Name of the Informatica Server.
    4. Run the script.

      NOTE:  Because the Reset_infa_seq_gen.bat file contains user names and passwords, it is recommended that you delete the file after the upgrade process is complete.

  18. To verify the data migrated successfully:
    1. Check whether any of the Informatica mapping log files stored in the directory \Informatica PowerCenter 7.1.4\Server\SessLogs indicates errors or failures.
    2. Check whether the SQL scripts (790_UPGRADE_PRE_CTL_SCRIPT.sql and 790_UPGRADE_PRE_DIMENSION_SCRIPT.sql) that you ran in the SQL client of the database failed or errored out while executing.
    3. Check the log files for the CTL files (Upgrade.ctl and DW.ctl) that you ran using the DDLimp command to determine whether any of the runs failed.

      If you did not detect any errors or failures in the steps above, then the data migration was successful.

  19. (Optional) If the data migration was successful, drop the tables that were created during the upgrade process, such as, W_xxxx_x_784 tables, LKP_xxxx_x, and W_ASSET_D_TMP.

    This step frees the space occupied by these backup tables.

To migrate data from versions 7.7, 7.7.1.x, or 7.8 to 7.9 (Vertical)

  1. Copy the file Upgrade.rep file from the folder OracleBI\dwrep\Upgrade\Informatica\Repository into the folder Informatica PowerCenter 7.1.4\RepositoryServer\bin\Backup.
  2. Launch the Informatica Repository Console and restore Upgrade.rep (located in Informatica PowerCenter 7.1.4\RepositoryServer\bin\Backup).
  3. Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\SrcFiles and copy the *.csv files into the SrcFiles folder on the Informatica Server machine, for example, C:\Program Files\Informatica PowerCenter 7.1.4\Server\SrcFiles.
  4. Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\ParameterFiles and copy the file <previous version of Siebel Analytics>_TENERIFE_UPG_PARAMS.txt into the SrcFiles folder on the Informatica Server machine, for example, C:\Program Files\Informatica PowerCenter 7.1.4\Server\SrcFiles.
  5. Rename the file <previous version of Siebel Analytics>_TENERIFE_UPG_PARAMS.txt to TENERIFE_UPG_PARAMS.txt.
  6. In the file TENERIFE_UPG_PARAMS.txt:
    1. Search for the parameter $$SourceConnection.
    2. Set the value to one of the following options, based on your Siebel applications (OLTP) version:
      • SEBL_63
      • SEBL_753
      • SEBL_771
      • SEBL_78
      • SEBL_80
      • SEBL_VERT_753
      • SEBL_VERT_771
      • SEBL_VERT_78
      • SEBL_VERT_80

        For example, if your Siebel applications (OLTP) version is Siebel Industry Applications 7.5.x, the parameter should appear as:

    $$SourceConnection=SEBL_VERT_753

  7. In the file TENERIFE_UPG_PARAMS.txt:
    1. Search for the parameter $$Source_Container.
    2. Set the value to one of the following options, based on your Siebel applications (OLTP) version:
      • Siebel 6.3
      • Siebel 7.5.3
      • Siebel 7.5.3 Vertical
      • Siebel 7.7.1
      • Siebel 7.7.1 Vertical
      • Siebel 7.8
      • Siebel 7.8 Vertical
      • Siebel 8.0
      • Siebel 8.0 Vertical

        For example, if your Siebel applications (OLTP) version is Siebel Industry Applications 7.5.x, the parameter should appear as:

    $$Source_Container=Siebel 7.5.3 Vertical

  8. In the file TENERIFE_UPG_PARAMS.txt, edit the ETL_PROC_WID parameter as follows:

    MPLT_GET_ETL_PROC_WID.$$ETL_PROC_WID=<latest ETL_PROC_WID value from your database>

    You can get this value from W_PARAM_G.ETL_PROC_WID.

  9. In the Informatica Workflow Manager, open the Relational Connection Browser (Connections > Relational), and do the following:
    1. Edit the preconfigured ODBC connection PARAM_OLTP_SIEBEL to point to the Siebel transactional database.
    2. Edit the preconfigured ODBC connection DataWarehouse to point to the newly upgraded data warehouse database.
    3. Edit the preconfigured ODBC connection PARAM_DAC_OLD to point to the previous DAC repository database (the version from which you are upgrading).
    4. Edit the preconfigured ODBC connection PARAM_DAC_NEW to point to the new DAC repository database (the version to which you are upgrading).
  10. Define the alignment rule to be used for ETL loads.
    1. Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\SrcFiles and copy the file AlignmentType_LS_782.csv into the SrcFiles folder on the Informatica Server machine, for example, C:\Program Files\Informatica PowerCenter 7.1.4\Server\SrcFiles.
    2. Rename the file AlignmentType_LS_782.csv to AlignmentType.csv.
    3. Open the file AlignmentType.csv, and enter one of the following alignment item types under the ALIGN_TYPE field:
      • Zipcode
      • Account/Contact
      • Brick
    4. Save the file.

      NOTE:  The Oracle Business Analytics Warehouse allows only one alignment type to be used for ETL loads during upgrade.

  11. In Informatica Workflow Manager, navigate to the appropriate folder and execute the workflows in the order specified:
Application Version
Folder Name
Workflow

7.7 to 7.9 (Vertical)

UPGRADE_770_to_79
  1. MARKETING_LOAD
  2. Upgrade_Dimensions_Industry
  3. Update_Dimensions
  4. Update_Dimension_Unspecified
  5. Update_Facts
  6. Upgrade_LS_Dimensions
  7. Upgrade_LS_Facts
  8. SIL_PositionDimensionHierarchy_Full
  9. Load_INT_ORG_DH
  10. DIMENSION_LOAD
  11. DIMENSION_UNSPECIFIED_UPDATE
  12. FACT_UPDATE
  13. DAC_Metadata_Upgrade_Workflow

7.7.1.x to 7.9 (Vertical)

UPGRADE_771_to_79
  1. Update_Dimensions
  2. Update_Dimension_Unspecified
  3. Update_Facts
  4. Upgrade_LS_Dimensions
  5. Upgrade_LS_Facts
  6. SIL_PositionDimensionHierarchy_Full
  7. Load_INT_ORG_DH
  8. DIMENSION_LOAD
  9. DIMENSION_UNSPECIFIED_UPDATE
  10. FACT_UPDATE
  11. DAC_Metadata_Upgrade_Workflow

7.8 to 7.9 (Vertical)

UPGRADE_78_to_79
  1. SIL_PositionDimensionHierarchy_Full
  2. Load_INT_ORG_DH
  3. DIMENSION_LOAD
  4. DIMENSION_UNSPECIFIED_UPDATE
  5. FACT_UPDATE
  6. DAC_Metadata_Upgrade_Workflow
  1. Run the Reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs:
    1. Navigate to the directory \OracleBI\dwrep\Upgrade\DbScripts\<database type>.
    2. Open the Reset_infa_seq_gen.bat script, and review the parameters at the top of the file.
    3. Replace the existing values for the parameters to reflect your environment (the parameters are database-specific).

      For Oracle databases:

      Parameter
      Setting

      TARGET_USERID_PWD

      <olap schema user-name>/<olap schema password>@<olap database TNS name>

      For example:

      TARGET_USERID_PWD=siebel/siebel@siebel_olap

      INFA_USERID_PWD

      <user-name of Informatica Repository database that contains the adapter mappings repository metadata>/<password of the Informatica Repository database>@<TNS name of the database for the Informatica Repository>

      For example:

      INFA_USERID_PWD=INFAREP/INFAREP@infa.corp.siebel.com

      INFA_REP

      Name of the Informatica Repository where the adapter mappings are available.

      INFA_U

      User name of the administrator of the Informatica Repository.

      INFA_P

      Password for the administrator of the Informatica Repository.

      INFA_SRV

      Name of the Informatica Server.

      For Microsoft SQL Server databases:

      Parameter
      Setting

      OLAP_SERVER

      Name of the SQL Server for the OLAP database.

      OLAP_DB

      Name of the database on which OLAP data is available.

      OLAP_U

      User name for logging into the database on which OLAP data is available.

      OLAP_P

      Password for logging into the database on which OLAP data is available.

      INFA_SERVER

      Name of the SQL Server for the Informatica Repository database.

      INFA_DB

      Name of the database on which Informatica Repository metadata is available.

      INFA_U

      User name for logging into the database on which Informatica Repository metadata is available.

      INFA_P

      Password for logging into the database on which Informatica Repository metadata is available.

      INFA_REP

      Name of the Informatica Repository where adapter mappings are available.

      INFA_REP_U

      User name of the administrator of the Informatica Repository.

      INFA_REP_P

      Password of the administrator of the Informatica Repository.

      For IBM DB2 databases:

      Parameter
      Setting

      TARGET_USERID_PWD

      <olap schema user-name>/<olap schema password>@<olap database name>

      For example:

      TARGET_USERID_PWD=siebel/db2@OLAP_DB2DB

      INFA_USER

      User name for logging into the database on which Informatica metadata is available.

      INFA_PWD

      Password for logging into the database on which Informatica Repository metadata is available.

      INFADB_ALIAS

      Name of the database in which Informatica Repository metadata is available.

      INFA_REP

      Name of the Informatica Repository where the adapter mappings are available.

      INFA_U

      User name of the administrator of the Informatica Repository.

      INFA_P

      Password of the administrator of the Informatica Repository.

      INFA_SRV

      Name of the Informatica Server.
    4. Run the script.

      NOTE:  Because the Reset_infa_seq_gen.bat file contains user names and passwords, it is recommended that you delete the file after the upgrade process is complete.

  2. To verify the data migrated successfully:
    1. Check whether any of the Informatica mapping log files stored in the directory \Informatica PowerCenter 7.1.4\Server\SessLogs indicates errors or failures.
    2. Check whether the SQL scripts (790_UPGRADE_PRE_CTL_SCRIPT.sql and 790_UPGRADE_PRE_DIMENSION_SCRIPT.sql) that you ran in the SQL client of the database failed or errored out while executing.
    3. Check the log files for the CTL files (Upgrade.ctl and DW.ctl) that you ran using the DDLimp command to determine whether any of the runs failed.

      If you did not detect any errors or failures in the steps above, then the data migration was successful.

  3. (Optional) If the data migration was successful, drop the tables that were created during the upgrade process, such as, W_xxxx_x_784 tables, LKP_xxxx_x, and W_ASSET_D_TMP.

    This step frees the space occupied by these backup tables.

To migrate data from Life Sciences 7.8.0, 7.8.1 or 7.8.2 to 7.9

  1. Copy the file Upgrade.rep file from the folder OracleBI\dwrep\Upgrade\Informatica\Repository into the folder Informatica PowerCenter 7.1.4\RepositoryServer\bin\Backup.
  2. Launch the Informatica Repository Console and restore Upgrade.rep (located in Informatica PowerCenter 7.1.4\RepositoryServer\bin\Backup).
  3. Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\SrcFiles and copy the *.csv files into the SrcFiles folder on the Informatica Server machine, for example, C:\Program Files\Informatica PowerCenter 7.1.4\Server\SrcFiles.
  4. Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\ParameterFiles and copy the file 782_TENERIFE_UPG_PARAMS_LS.txt into the SrcFiles folder on the Informatica Server machine, for example, C:\Program Files\Informatica PowerCenter 7.1.4\Server\SrcFiles.
  5. Rename the file 782_TENERIFE_UPG_PARAMS_LS.txt to TENERIFE_UPG_PARAMS.txt.
  6. In the file TENERIFE_UPG_PARAMS.txt:
    1. Search for the parameter $$SourceConnection.
    2. Set the value to one of the following options, based on your Siebel applications (OLTP) version:
      • SEBL_63
      • SEBL_753
      • SEBL_771
      • SEBL_78
      • SEBL_80
      • SEBL_VERT_753
      • SEBL_VERT_771
      • SEBL_VERT_78
      • SEBL_VERT_80

        For example, if your Siebel applications (OLTP) version is Siebel Industry Applications 7.5.x, the parameter should appear as:

    $$SourceConnection=SEBL_VERT_753

  7. In the file TENERIFE_UPG_PARAMS.txt:
    1. Search for the parameter $$Source_Container.
    2. Set the value to one of the following options, based on your Siebel applications (OLTP) version:
      • Siebel 6.3
      • Siebel 7.5.3
      • Siebel 7.5.3 Vertical
      • Siebel 7.7.1
      • Siebel 7.7.1 Vertical
      • Siebel 7.8
      • Siebel 7.8 Vertical
      • Siebel 8.0
      • Siebel 8.0 Vertical

        For example, if your Siebel applications (OLTP) version is Siebel Industry Applications 7.5.x, the parameter should appear as:

    $$Source_Container=Siebel 7.5.3 Vertical

  8. In the file TENERIFE_UPG_PARAMS.txt, edit the ETL_PROC_WID parameter as follows:

    MPLT_GET_ETL_PROC_WID.$$ETL_PROC_WID=<latest ETL_PROC_WID value from your database>

    You can get this value from W_PARAM_G.ETL_PROC_WID.

  9. In the Informatica Workflow Manager, open the Relational Connection Browser (Connections > Relational), and do the following:
    1. Edit the preconfigured ODBC connection PARAM_OLTP_SIEBEL to point to the Siebel transactional database.
    2. Edit the preconfigured ODBC connection DataWarehouse to point to the newly upgraded data warehouse database.
    3. Edit the preconfigured ODBC connection PARAM_DAC_OLD to point to the previous DAC repository database (the version from which you are upgrading).
    4. Edit the preconfigured ODBC connection PARAM_DAC_NEW to point to the new DAC repository database (the version to which you are upgrading).
  10. Define the alignment rule to be used for ETL loads.
    1. Navigate to the folder OracleBI\dwrep\Upgrade\Informatica\SrcFiles and copy the file AlignmentType_LS_782.csv into the SrcFiles folder on the Informatica Server machine, for example, C:\Program Files\Informatica PowerCenter 7.1.4\Server\SrcFiles.
    2. Rename the file AlignmentType_LS_782.csv to AlignmentType.csv.
    3. Open the file AlignmentType.csv, and enter one of the following alignment item types under the ALIGN_TYPE field:
      • Zipcode
      • Account/Contact
      • Brick
    4. Save the file.

      NOTE:  The Oracle Business Analytics Warehouse allows only one alignment type to be used for ETL loads during upgrade.

  11. In Informatica Workflow Manager, navigate to the folder UPGRADE_LS_782_to_79, and execute the following workflows in the order indicated:
    1. Upgrade_LS_Dimensions
    2. Upgrade_LS_Facts
    3. SIL_PositionDimensionHierarchy_Full
    4. Load_INT_ORG_DH
    5. DIMENSION_LOAD
    6. DIMENSION_UNSPECIFIED_UPDATE
    7. FACT_UPDATE
    8. DAC_Metadata_Upgrade_Workflow
  12. Run the Reset_infa_seq_gen.bat script to initialize the Informatica sequence generator for incremental runs:
    1. Navigate to the directory \OracleBI\dwrep\Upgrade\DbScripts\<database type>.
    2. Open the Reset_infa_seq_gen.bat script, and review the parameters at the top of the file.
    3. Replace the existing values for the parameters to reflect your environment (the parameters are database-specific).

      For Oracle databases:

      Parameter
      Setting

      TARGET_USERID_PWD

      <olap schema user-name>/<olap schema password>@<olap database TNS name>

      For example:

      TARGET_USERID_PWD=siebel/siebel@siebel_olap

      INFA_USERID_PWD

      <user-name of Informatica Repository database that contains the adapter mappings repository metadata>/<password of the Informatica Repository database>@<TNS name of the database for the Informatica Repository>

      For example:

      INFA_USERID_PWD=INFAREP/INFAREP@infa.corp.siebel.com

      INFA_REP

      Name of the Informatica Repository where the adapter mappings are available.

      INFA_U

      User name of the administrator of the Informatica Repository.

      INFA_P

      Password for the administrator of the Informatica Repository.

      INFA_SRV

      Name of the Informatica Server.

      For Microsoft SQL Server databases:

      Parameter
      Setting

      OLAP_SERVER

      Name of the SQL Server for the OLAP database.

      OLAP_DB

      Name of the database on which OLAP data is available.

      OLAP_U

      User name for logging into the database on which OLAP data is available.

      OLAP_P

      Password for logging into the database on which OLAP data is available.

      INFA_SERVER

      Name of the SQL Server for the Informatica Repository database.

      INFA_DB

      Name of the database on which Informatica Repository metadata is available.

      INFA_U

      User name for logging into the database on which Informatica Repository metadata is available.

      INFA_P

      Password for logging into the database on which Informatica Repository metadata is available.

      INFA_REP

      Name of the Informatica Repository where adapter mappings are available.

      INFA_REP_U

      User name of the administrator of the Informatica Repository.

      INFA_REP_P

      Password of the administrator of the Informatica Repository.

      For IBM DB2 databases:

      Parameter
      Setting

      TARGET_USERID_PWD

      <olap schema user-name>/<olap schema password>@<olap database name>

      For example:

      TARGET_USERID_PWD=siebel/db2@OLAP_DB2DB

      INFA_USER

      User name for logging into the database on which Informatica metadata is available.

      INFA_PWD

      Password for logging into the database on which Informatica Repository metadata is available.

      INFADB_ALIAS

      Name of the database in which Informatica Repository metadata is available.

      INFA_REP

      Name of the Informatica Repository where the adapter mappings are available.

      INFA_U

      User name of the administrator of the Informatica Repository.

      INFA_P

      Password of the administrator of the Informatica Repository.

      INFA_SRV

      Name of the Informatica Server.
    4. Run the script.

      NOTE:  Because the Reset_infa_seq_gen.bat file contains user names and passwords, it is recommended that you delete the file after the upgrade process is complete.

  13. To verify the data migrated successfully:
    1. Check whether any of the Informatica mapping log files stored in the directory \Informatica PowerCenter 7.1.4\Server\SessLogs indicates errors or failures.
    2. Check whether the SQL scripts (790_UPGRADE_PRE_CTL_SCRIPT.sql and 790_UPGRADE_PRE_DIMENSION_SCRIPT.sql) that you ran in the SQL client of the database failed or errored out while executing.
    3. Check the log files for the CTL files (Upgrade.ctl and DW.ctl) that you ran using the DDLimp command to determine whether any of the runs failed.

      If you did not detect any errors or failures in the steps above, then the data migration was successful.

  14. (Optional) If the data migration was successful, drop the tables that were created during the upgrade process, such as, W_xxxx_x_784 tables, LKP_xxxx_x, and W_ASSET_D_TMP.

    This step frees the space occupied by these backup tables.

  
Oracle® Business Intelligence Applications Upgrade Guide Copyright © 2007, Oracle. All rights reserved.