2.3.1 BCC Engine
The BCC 1.2.0 patch includes the following major bug fixes for the BCC engine:
Improves the update process to wait for the
before running the BCC install scripts. (Bug 561055)
Modified the
novell-bcc init.d
Typically, the wait is less than 10 seconds.
Modified the post-install script of the Novell BCC specification file to wait up to 5
seconds when
Improves memory management functions that might cause the
the code was simplified and clarified so that the shared memory functions now do exactly what
their names describe. The
keys are not in use by other processes, then to use the verified unique keys for its processing
threads. (Bug 553527)
Improves the detection and handling of
not caught and handled where it occurs, the engine's main thread detects the exception and
gracefully shuts itself down. (Bug 428161)
2.3.2 BCC Resource Driver Template for Identity Manager
The BCC 1.2.0 patch for OES 2 SP1 Linux includes a new BCC resource driver template for
Identity Manager that offers the following new feature and bug fixes:
Uses a newer policy linking format so that you are no longer prompted to update the driver in
iManager. (New)
Adds the host resource name and Novell Distributed File Services (DFS) GUID attributes to
the Volume objects that are synchronized for a BCC-enabled volume resource. (Bug 535127)
No longer creates duplicate NCP Server, Volume, and Pool objects when the landing zone is
not the same location as the cluster server's container. (Found while debugging Bug 537981)
Ensures that a volume resource's link to the virtual NCP Server object is updated to point to the
cluster where the resource is mounted. (Found while debugging Bug 537981)
The event for the
IsClusterEnabled
peer list to be synchronized to the peer clusters, even if the cluster is disabled, if the current
cluster's name is being removed from the peer list. Only this specific change is allowed; other
changes to a resource are dropped (vetoed) by the driver after a cluster is disabled. (Bug
434243)
The new BCC resource driver template is compatible with the following combinations of Identity
Manager and operating systems:
Identity Manager
Identity Manager 3.6 (32-bit)
Identity Manager 3.6.1 (32-bit or 64-bit)
Identity Manager 3.6.1 (32-bit or 64-bit)
Identity Manager 3.5.x
script to wait up to 15 seconds when
is stopped. Typically, the wait is about 1 second.
adminfsd
daemon was modified to generate unique keys to verify that the
bccd
No Memory
policy in a BCC resource driver now allows a resource's
and
daemons to gracefully stop
adminfsd
bccd
bccd
exceptions. In addition, if an exception is
Operating System
OES 2 SP1 Linux (32-bit)
OES 2 SP1 Linux (32-bit or 64-bit)
OES 2 SP2 Linux (32-bit or 64-bit)
®
NetWare
6.5 SP8
is stopped.
bccd
daemon to die. Overall,
What's New for BCC 1.2
27
Need help?
Do you have a question about the BUSINESS CONTINUITY CLUSTERING 1.2.1 - ADMINISTRATION and is the answer not in the manual?
Questions and answers