Configuration Database Adoption Failed - One or More Limit(s) Exceeded

What Caused the Problem?

The storage subsystem has failed to adopt the configuration database of one or more recently inserted drives because the configuration database exceeds the limits set by this storage subsystem.  More specifically, the configuration database has exceeded one or more of the allowable limits set by the storage subsystem for the following:

Due to the nature of the failure the Recovery Guru Details area does not provide specific information about the problem or the drives causing the problem.

Caution: Electronic discharge can damage sensitive components. Always use proper antistatic protection when handling components. Touching components without using a proper ground may damage the equipment.

Important Notes

Recovery Steps

1

Refer to the Summary tab of the Storage Subsystem Profile and record the maximum limit allowed by this storage subsystem for the following items:

  • Total number of logical drives allowed
  • Number of Remote Mirrors allowed*
  • Number of FlashCopies per logical drive allowed*
  • Number of partitions allowed
  • Number of drive enclosures allowed

Notes:

  • *Some premium feature limit information is only available when the feature is enabled.  If the limit field is not present, then the limit can be assumed to be 0.
  • In the case of when the drive enclosure limit is exceeded, you cannot simply remove the additional drive enclosures from this (the destination) storage subsystem, because there will still be references to the remaining drive enclosures in the configuration database.  You must proceed with step 2.
  • The number of host ports may also be exceeded, but the host port limit is not information that is available in the Storage Subsystem Profile.  Contact your Sales representative if you believe the number of host ports is being exceeded. Do not continue with the remaining Recovery Steps because a host port limit problem cannot be corrected without assistance from your Sales Representative.
2 Remove all of the drives that were recently inserted into this storage subsystem and return them back to the original storage subsystem.

Note: At the original storage subsystem all of the drives will still be native and all of the data will still be accessible. Alternatively, instead of returning the drives to the original storage subsystem, you may insert them into an empty storage subsystem that is known to have limits that support the items referenced by the configuration database. If you use an alternate storage subsystem, ensure that the controllers are powered off prior to attaching the drives.

3

After the drives are recognized by the original or alternate storage subsystem, view the Summary tab of the Storage Subsystem Profile (in the storage management software of the original or alternate storage subsystem) to see how many of each of the following items are currently on that storage subsystem:

  • Total number of logical drives
  • Number of Remote Mirrors
  • Number of FlashCopies per logical drive
  • Number of partitions
  • Number of drive enclosures
4 Follow the appropriate steps to remove the extra items until the total number of each item is at or below the limits supported by this (the destination) storage subsystem, which you recorded in step 1.

Notes:

  • Refer to the online help for the original or alternate storage subsystem if you require assistance with this step.
  • If there is an array that span more than the number of allowed drive enclosures, you will need to reconfigure the arrays so that they are spanning only the allowed number of drive enclosures.
  • A missing array counts against the total logical drive count.
5 When all of the items meet the limits of this (the destination) storage subsystem, remove the drives from the original or alternate storage subsystem.
6 Power down the controllers to this (the destination) storage subsystem, and ensure that there are no additional foreign drives attached to them.
7 Re-insert the drives into this (the destination) storage subsystem, and then power-on the controllers.
8 Click Recheck to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative.