Portal Upgrade Troubleshooting
  
Version 10.0.01
Portal Upgrade Troubleshooting
During the Portal upgrade, a pre-check is performed to ensure that your existing data collection policies are valid. Under certain circumstances, the pre-check will fail, preventing the upgrade from proceeding.
To resolve issues with invalid data collection policies, refer to the following sections:
Upgrade Pre-check Error Message
Sample Upgrade Log Error Messages
Conditions and Resolutions
Identify Data Collector Policy Status
Fixing Active Policies
Upgrade Pre-check Error Message
The upgrade pre-check failed, preventing the upgrade from proceeding. The pre-check encountered one or more Data Collector policies in an invalid state. This could occur for a number of reasons associated with disabled, inactive policies or with policies where data collection has never occurred. Check the upgrade log and check this document for the possible conditions and resolutions.
Sample Upgrade Log Error Messages
Error messages are listed in the Upgrade Log. In this example, IBM Tivoli Storage Manager is the subsystem associated with an invalid Data Collector policy. The EMC NetWorker message represents an invalid policy, where data collection has never occurred.
8/14/12 11:46 AM ERROR: Multiple Server Instances found for IBM Tivoli Storage Manager:
9/12/13 12:59 PM :is_active:Y
9/12/13 12:59 PM :cxml_id: 100133
9/12/13 12:59 PM :collector_id: 100054
9/12/13 12:59 PM :collector_name: HQ-tsm1
9/12/13 12:59 PM :server_id: 10444
9/12/13 12:59 PM :domain_id: 100000
9/12/13 12:59 PM :server_address: hqent1
9/12/13 12:59 PM :is_active:Y
9/12/13 12:59 PM ERROR: No Server Instance found for EMC NetWorker:
9/12/13 12:59 PM :cxml_id: 100210
9/12/13 12:59 PM :collector_id:100021
9/12/13 12:59 PM :server_id:100904
9/12/13 12:59 PM :domain_id:100000
9/12/13 12:59 PM :server_address:aptnwk2
9/12/13 12:59 PM :is_active:Y
Conditions and Resolutions
Condition
Resolution
A Data Collector has one or more disabled, inactive policies.
2. Delete the policy and rerun the upgrade.
A Data Collector has one or more policies for which collection has never occurred.
2. Delete policy and rerun the upgrade.
A Data Collector has more than one policy configured with the same server.
1. Search the log for: Multiple Server Instances found.
2. Check the policy and server listed in the upgrade log error message and in the Portal; check any policies that reference this server.
3. Delete the policy and rerun the upgrade.
A Data Collector with active policies for which collection has occurred.
The resolution steps are specific to the policy's subsystem. See Fixing Active Policies.
Identify Data Collector Policy Status
To determine if a Data Collector is inactive, take the following steps in the Portal:
1. Navigate to Admin > Data Collection > Collectors.
2. Double-click the Data Collector folder to view each policy, along with its status (Enabled or Disabled).
3. Run the Data Collector Status Summary report to determine if an enabled policy has collected data.
Fixing Active Policies
This section includes instructions for the relevant collected subsystems.
EMC Avamar Policies
1. Create a backup table and include the policy IDs that are failing during upgrade.
CREATE TABLE apt_cxml_emc_avamar_bkp AS SELECT * FROM apt_cxml_emc_avamar
WHERE cxml_emc_avamar_id IN (?,?);
2. Delete these failing policies from the original table.
DELETE FROM apt_cxml_emc_avamar WHERE cxml_emc_avamar_id IN (?,?);
COMMIT;
3. Start the Upgrader.
4. If the policy is INVALID as per the pre-check, then delete the policy.
DELETE FROM apt_cxml_emc_avamar_bkp WHERE cxml_emc_avamar_id = ?;
COMMIT;
5. If the policy is not marked as Invalid, then for every cxml_emc_avamar_id that has failed validation, pick up the server_instance_id from the suggestions and update in the table.
ALTER TABLE apt_cxml_emc_avamar_bkp ADD server_instance_id NUMBER(6,0);
UPDATE apt_cxml_emc_avamar_bkp SET server_instance_id = ? WHERE
cxml_emc_avamar_id = ?;
6. Copy the policy back into the main table.
INSERT INTO apt_cxml_emc_avamar SELECT * FROM apt_cxml_emc_avamar_bkp WHERE
cxml_emc_avamar_id = ?;
COMMIT;
7. Find the collectors to which the previous updated policies belong. For every such collector, run the following update statement.
UPDATE apt_collector_properties SET is_dirty = 'Y' WHERE collector_id = ?;
COMMIT;
IBM TSM Policies
1. Create a backup table and include the policy IDs that are failing during upgrade.
CREATE TABLE apt_cxml_tsm_bkp AS SELECT * FROM apt_cxml_tsm WHERE
cxml_tsm_id IN (?,?);
2. Delete these failing policies from the original table.
DELETE FROM apt_cxml_tsm WHERE cxml_tsm_id IN (?,?);
COMMIT;
3. Start the Upgrader.
4. If the policy is INVALID as per the pre-check, then delete the policy.
DELETE FROM apt_cxml_tsm_bkp WHERE cxml_tsm_id = ?;
COMMIT;
5. If the policy is not marked as Invalid, then for every cxml_tsm_id that has failed validation, pick up the server_instance_id from the suggestions and update in the table.
ALTER TABLE apt_cxml_tsm_bkp ADD server_instance_id NUMBER(6,0);
UPDATE apt_cxml_tsm_bkp SET server_instance_id = ? WHERE cxml_tsm_id = ?;
6. Copy the policy back into the main table.
INSERT INTO apt_cxml_tsm SELECT * FROM apt_cxml_tsm_bkp WHERE cxml_tsm_id =?;
COMMIT;
7. Find the collectors to which the previous updated policies belong. For every such collector, run the following update statement.
UPDATE apt_collector_properties SET is_dirty = 'Y' WHERE collector_id = ?;
COMMIT;
EMC NetWorker Policies
1. Create a backup table and include the policy IDs that are failing during upgrade.
CREATE TABLE apt_cxml_emc_networker_bkp AS SELECT * FROM
apt_cxml_emc_networker WHERE cxml_emc_networker_id IN (?,?);
2. Delete these failing policies from the original table.
DELETE FROM apt_cxml_emc_networker WHERE cxml_emc_networker_id IN (?,?);
COMMIT;
3. Start the Upgrader.
4. If the policy is INVALID as per the pre-check, then delete the policy.
DELETE FROM apt_cxml_emc_networker_bkp WHERE cxml_emc_networker_id = ?;
COMMIT;
5. If the policy is not marked as Invalid, then for every cxml_emc_networker_id that has failed validation, pick up the server_instance_id from the suggestions and update in the table.
ALTER TABLE apt_cxml_emc_networker_bkp ADD server_instance_id NUMBER(6,0);
UPDATE apt_cxml_emc_networker_bkp SET server_instance_id = ? WHERE
cxml_emc_networker_id = ?;
6. Copy the policy back into the main table.
INSERT INTO apt_cxml_emc_networker SELECT * FROM apt_cxml_emc_networker_bkp
WHERE cxml_emc_networker_id = ?;
COMMIT;
7. Find the collectors to which the previous updated policies belong. For every such collector, run the following update statement.
UPDATE apt_collector_properties SET is_dirty = 'Y' WHERE collector_id = ?;
COMMIT;
HP Data Protector Policies
1. Create a backup table and include the policy IDs that are failing during upgrade.
CREATE TABLE apt_cxml_hp_dataprotector_bkp AS SELECT * FROM
apt_cxml_hp_dataprotector WHERE cxml_hp_dataprotector_id IN (?,?);
2. Delete these failing policies from the original table.
DELETE FROM apt_cxml_hp_dataprotector WHERE cxml_hp_dataprotector_id IN (?,?);
COMMIT;
3. Start the Upgrader.
4. If the policy is INVALID as per the pre-check, then delete the policy.
DELETE FROM apt_cxml_hp_dataprotector_bkp WHERE cxml_hp_dataprotector_id = ?;
COMMIT;
5. If the policy is not marked as Invalid, then for every cxml_hp_dataprotector_id that has failed validation, pick up the server_instance_id from the suggestions and update in the table.
ALTER TABLE apt_cxml_hp_dataprotector_bkp ADD server_instance_id NUMBER(6,0);
UPDATE apt_cxml_hp_dataprotector_bkp SET server_instance_id = ? WHERE
cxml_hp_dataprotector_id = ?;
6. Copy the policy back into the main table.
INSERT INTO apt_cxml_hp_dataprotector SELECT * FROM
apt_cxml_hp_dataprotector_bkp WHERE cxml_hp_dataprotector_id = ?;
COMMIT;
7. Find the collectors to which the previous updated policies belong. For every such collector, run the following update statement.
UPDATE apt_collector_properties SET is_dirty = 'Y' WHERE collector_id = ?;
COMMIT;
Generic Backup Policies
1. Create a backup table and include the policy IDs that are failing during upgrade.
CREATE TABLE apt_cxml_generic_bkp_bkp AS SELECT * FROM apt_cxml_generic_bkp
WHERE cxml_generic_bkp_id IN (?,?);
2. Delete these bad policies from the original table.
DELETE FROM apt_cxml_generic_bkp WHERE cxml_generic_bkp_id IN (?,?);
COMMIT;
3. Start the Upgrader now. It should succeed.
4. If the policy is INVALID as per the pre-check, then delete the policy.
DELETE FROM apt_cxml_generic_bkp_bkp WHERE cxml_generic_bkp_id = ?;
COMMIT;
5. If the policy is not marked as Invalid, then for every cxml_generic_bkp_id that has failed validation, pick up the server_instance_id from the suggestions and update in the table.
ALTER TABLE apt_cxml_generic_bkp_bkp ADD server_instance_id NUMBER(6,0);
UPDATE apt_cxml_generic_bkp_bkp SET server_instance_id = ? WHERE
cxml_generic_bkp_id = ?;
6. Now copy the policy back into the main table.
INSERT INTO apt_cxml_generic_bkp SELECT * FROM apt_cxml_generic_bkp_bkp
WHERE cxml_generic_bkp_id = ?;
COMMIT;
7. Find the collectors to which the above updated policies belong. For every such collector, run the following update statement.
UPDATE apt_collector_properties SET is_dirty = 'Y' WHERE collector_id = ?;
COMMIT;