What Happens to Data When an SL8500 Library is Moved to a New Complex

Moving an SL8500 library from one complex to another affects the way data is displayed, sorted, and filtered on all STA screens.

STA rolls up data for the entire library complex, so moving one library to another will affect the data for the complexes. STA uses a unique Library Complex Name to identify each complex (such as SL8500_1 where 1 is the complex ID). If you move a library from one complex to another, the Library Complex Name associated with it changes. As a result, data for the moved library will be associated with two different library complexes within the historical data of STA.

For example, consider the following scenario:

  1. An SL8500 library, "BigLibraryA", is assigned to a complex with two other libraries. Oracle Service assigns ID 1 to the complex.
  2. In STA, you create a connection to BigLibraryA. The Library Complex Name for BigLibraryA is SL8500_1.
  3. STA monitors BigLibraryA, and all data for the library is rolled up to Library Complex Name SL8500_1.
  4. After three months, you decide to move BigLibraryA to a new complex. You remove the STA connection to BigLibraryA, and all data for the library is retired, as described in What Happens to Data When Libraries Are Removed.
  5. Oracle Service moves BigLibraryA to the new complex, which has complex ID 2.
  6. You reestablish the STA connection to BigLibraryA. This has the following effects on new and historical data for the library:
    • Because BigLibraryA is now in complex ID 2, the STA Library Complex Name for the library is SL8500_2, and all data collected by STA from this point forward is rolled up to that Library Complex Name.
    • All historical data, from the first three-month period, is still rolled up to Library Complex Name SL8500_1.
    • When you sort or filter data by Library Complex Name, the data for BigLibraryA is associated to two different complexes, depending on the time period.