Ensure each library complex at your site has a unique complex ID for STA to roll up library data correctly.
See also How the Library Complex ID Affects STA Data (SL8500 only).
Caution:
The Oracle Service Delivery Platform (SDP) also uses unique complex IDs for tracking library data. If your site uses SDP, contact Oracle Support before changing any complex ID. Changing the complex ID could cause SDP to fail. In most cases, complex IDs are set correctly when SDP is connected.For each SL8500 library monitored by STA, use the CLI to display the complex ID currently assigned:
SL8500> config complexId print
...
Complex Id 3
...
Verify that each standalone library and each library complex has a unique complex ID, and that all libraries in each library complex share the same complex ID.
If you need to change the complex ID of a standalone library, continue this procedure.
Caution:
If you need to change the complex ID of a library in a library complex, contact Oracle Support. Do not continue with this procedure.Place the library offline, and then wait for all transactions to complete.
Change the complex ID of a standalone library. complex_ID is a number, 1–127.
config complexId set complex_ID
For example:
SL8500> config complexId set 5
...
Complex Id 5
Success true
Done
...
Note: TCP/IP stack reset may take a few seconds after command completion.
All TCP/IP connections are terminated when executing this command. You may have to log back in to the library.
For STA to roll up library complex data correctly, each library complex at your site must have a unique complex ID.
On SL8500 libraries, complex IDs are set manually. On all other library models, the complex IDs are set automatically and therefore do not require manual intervention or verification.
Each standalone SL8500 is considered to be a separate complex and therefore must have a unique complex ID. In addition, each multi-library complex must have a unique complex ID, and all libraries within the complex must share the same ID. Valid complex ID values are 1–127.