If you wish to access monitor data from a previous release when upgrading Resource Analyzer, you must migrate the previous Resource Management repository contents into the new release repository.
The migration procedure is executed in batch to migrate the repository used by Resource Analyzer from prior releases to Release 7.7 or higher.
The following conditions are required in order to migrate the Resource Management Repository.
Note: When you run the migration more than once (which is necessary if you continued monitoring in the old release after migration and want the newly monitored data to be migrated), you will get a duplicate record error message. The duplicates are ignored and the new records are added.
How to: |
For these platforms, the migration procedure is executed in a Web Console session.
Note: IBM i was formerly known as i5/OS.
To start the migration job:
or
From the navagation pane, right-click Resource Management - Active/Inactive, select Configuration, and then select Migrate prior release data.
Note: You can also perform this task by clicking the Workspace link in the toolbar, right-clicking Workspace in the navigation pane, and selecting Migrate, General.
Note: This is only required if the old release is Version 7.7.03.
The Resource Management Migration pane opens, as shown in the following image.
The Submit Data Migration Job pane opens.
or
From the navigation pane, right-click Resource Management-Active, and select View Configuration Migration job.
The Deferred List pane opens, displaying the list of deferred requests and to view the request name that was displayed when the deferred migration job was scheduled. Examples of request names are listed in the Deferred ID column, as seen in the following image.
The Status column shows the state of the deferred request, which can be Queued, Executing, or Ready. To see if the status has changed to Ready, either keep refreshing the page using the refresh options located at the top of the page, or redisplay the page at a later time. Once the status is Ready, right-click the request line and select Get to review the job output.
How to: |
The migration information described below is only applicable if the server environment has been upgraded by performing the refresh option during the installation process. To refresh the server, follow the instructions in the Installation Guide for your platform.
Migration Usage Notes:
Once the refresh process has completed successfully, start the server and then the Web Console.
The migration is performed from the Web Console and consists of three phases:
For these platforms, the migration procedure is executed on a Web Console session.
Note: IBM i was formerly known as i5/OS.
To start the migration process, click the Resource Management link on the toolbar in the Web Console. A warning message is displayed, as shown in the following image.
This warning message indicates that the structure of the Resource Management repository has changed. A migration process is required in order to update the existing repository so that new data columns can be archived to the repository. If the migration process is not run, monitor data will still be collected and archived but without the new data columns.
You can:
The Resource Management Configuration Migration pane opens. The sequence of panes is slightly different depending on the repository type.
The options are Yes or No.
For Phase 2 - Migrate data Yes:
Select this option to copy data from the old repository to the new one. When this option is selected, additional information is displayed regarding Phase 3, which is optional and performed from an option on the Configuration menu. See Step 6 for more information.
The Submit Configuration Migration Job pane opens, as shown in the following image.
For Phase 2 - Migrate data No:
Select this option if you do not want data to be copied from the old repository to the new one. When this option is selected, additional information is displayed regarding Phase 3, which is optional and performed from an option on the Configuration menu. See Step 6 for more information.
To run the migration process at a later date, select Resource Management on the menu bar and on the ribbon, in the Configuration group, click Configuration, and select Migrate nnnn release data, where nnnn reflects the release number.
or
From the navigation pane, right-click Resource Management - Active/Inactive and select Configuration, Migrate nnnn release data, where nnnn reflects the release number.
Note: This option will be removed once Phase 3 is complete.
or
From the navigation pane, right-click Resource Management - Active/Inactive and select Configuration, View Configuration Migration job
The Deferred List pane opens.
On the ribbon, in the Configuration group, click Configuration and select Remove old Configuration files.
or
From the navigation pane, right-click Resource Management - Active/Inactive and select Configuration, Remove old Configuration files.
Note: Once you choose to remove the old configuration files, the option to migrate data will no longer be available.
The options are Yes and DDL Only.
For Phase 1 - Create Repositories Yes:
Select this option if you have DBA authority over the existing Resource Management repository tables. New repository tables will be created with a suffix of _nnnn, where nnnn reflects the release number. The process will continue at Phase 2.
For Phase 1 - Create Repositories DDL Only:
Select this option if you do not have DBA authority over the existing Resource Management repository tables. This option creates a file, rmldb.sql, which contains RDBMS specific DDL.
Note: Your DBA must create the new Repository tables in the same location as the original 7.7 tables and both sets of tables have to be accessible on the same Adapter connection on the server. The new tables will have the release number appended to the name. The format will be tablename_release.
The options are Yes or No.
For Phase 2 - Migrate data Yes:
Select this option to copy data from the old repository to the new one. When this option is selected, additional information is displayed regarding Phase 3, which is optional and performed from an option on the Configuration menu. See Step 5 for more information.
The Submit Configuration Migration Job pane opens, as shown in the following image.
For Phase 2 - Migrate data No:
Select this option if you do not want data to be copied from the old repository to the new one. When this option is selected, additional information is displayed regarding Phase 3, which is optional and performed from an option on the Configuration menu. See Step 5 for more information.
To run the migration process at a later date, select Resource Management on the menu bar and on the ribbon, in the Configuration group, click Configuration, and select Migrate nnnn release data, where nnnn reflects the release number.
or
From the navigation pane, right-click Resource Management - Active/Inactive and select Configuration, Migrate nnnn release data, where nnnn reflects the release number.
Note: This option will be removed once Phase 3 is complete.
or
From the navigation pane, right-click Resource Management - Active/Inactive and select Configuration, View Configuration Migration job
The Deferred List pane opens.
On the ribbon, in the Configuration group, click Configuration and select Remove old Configuration files.
or
From the navigation pane, right-click Resource Management - Active/Inactive and select Configuration, Remove old Configuration files.
Note: Once you choose to remove the old configuration files, the option to migrate data will no longer be available.
How to: |
This option is only available when migrating data from Release 7.6 or 7.7. Repository migration is not available from earlier releases.
To start the migration job:
or
From the navigation pane, right click Resource Management - Active/Inactive, select Configuration, and then select Migrate prior release data.
Note: You can also perform this task by clicking the Workspace link in the toolbar, right-clicking Workspace in the navigation pane, and selecting Migrate, General.
Note: For help in identifying the dataset names required on the next two panes, see the chart in Step 6.
For 7700 – 7702, 7703 and 7704 Old release selection, select the type of repository that was configuration on the old release. Values available are Relational or FOCUS. This option is not shown for 76x.
For 76x or 7700 – 7702 Old release selection, the dataset name that was used to save the MASTER files during the configuration of the previous release. For 76x release, there should be at least 15 members in the provided dataset starting with “SM”. For 7700 – 7702, there should be a member called RMLDB.
For 7703 or 7704 Old release selection, this is the supplied MASTER file installed with the product which has approximately 200 members and contains a member called RMLDB.
The dataset name that contains the ACCESS files created/used during the configuration of the previous release.
For 7703 or 7704 Old release selection, this is the dataset name that contains the master file profiles members. They are RMLPD773 (7703) or RMLPD774 (7704) and RMLPRFSY (both releases).
The dataset name of the FOCUS repository from the previous release.
Provide the information required for the fields available.
For all other releases, the same pane will show but without the Create 7.6 compatibility masters option available.
Select the server name to be migrated.
Select Yes if the previous releases system data should be migrated. If Yes is selected, SMCNTRL, SMPRMTRS and SMPRL data will be migrated. Only custom BRL members will be migrated. The SMKNBNAME value in SMCNTRL will not be migrated and any Govern and/or Advise values will be set to OFF. Any compiled rule files must be rebuilt after the migration is completed and new Govern and/or Advise values must be set. The default value is No.
For releases 7700 – 7702, 7703 and 7704, if Yes is selected, one or two additional input boxes are shown depending on Old release selection
This is the dataset that contains Resource Management system information. It was created during the configuration of the old release server.
For 7703 or 7704 Old release selection, this is the supplied MASTER file installed with the product which has approximately 200 members and contains a member called RMLSYS.
Note: If multiple migration runs are being made, only migrate the system data once.
Select Yes if you want to have 7.6 style masters created that will allow existing custom reports to run. Some modifications to your custom reports may be required. An additional input box is shown that allows for an existing application name to be provided.
The earliest date of the data to be migrated. The format is MM/DD/YYYY. The default value is 1/1/1995.
The latest date of the data to be migrated. The format is MM/DD/YYYY. The default value is the current date.
All of the names in the following chart require QUALIF.servertype as a prefix.
Where servertype can be FFS, WFS, or DM.
Dataset name |
76x |
7700-7702 |
7703 |
7704 |
---|---|---|---|---|
EDACONF MASTER |
CONF.MAS |
CONF.MAS | ||
EDAHOME MASTER |
P.HOME.MAS* |
P.HOME.MAS |
P.HOME.MAS | |
ACCESS** |
CONF.ACX |
CONF.ACX |
P.HOME.ACX |
P.HOME.ACX |
CONFIGURATION |
CONF.CFG |
CONF.CFG | ||
REPOSITORY*** |
RMLDB.FOCUS |
RMLDB.FOCUS |
RMLDB.FOCUS | |
SYSTEM* |
RMLSYS.FOCUS |
RMLSYS.FOCUS |
RMLSYS.FOCUS | |
COMPATIBILITY |
App name |
* Only required when migrating system data.
** Only required if old repository is relational.
*** Only required if old repository is FOCUS.
The Submit Data Migration Job pane opens.
or
From the navigation pane, right-click Resource Management-Active, and select View Configuration Migration job.
The Deferred List pane opens, displaying the list of deferred requests and to view the request name that was displayed when the deferred migration job was scheduled. Examples of request names are listed in the Deferred ID column, as seen in the following image.
The Status column shows the state of the deferred request, which can be Queued, Executing, or Ready. To see if the status has changed to Ready, either keep refreshing the page using the refresh options located at the top of the page, or redisplay the page at a later time. Once the status is Ready, right-click the request line and select Get to review the job output.
WebFOCUS |