. 5. Follow the on screen prompts to correctly select the location of the directory to where the patch was extracted on the server. 6. Press to start the file copy procedure. After installion completes, issue the uldbcc.ncf command to unload BCC modules and then reload using the ldbcc.ncf command. NOTE: Newely created BCC resource drivers will utilize the new XML template (BCCClusterResourceSyncronizaion.xlm)included in the patch. Previously created drivers will have to be manually updated as follows. Via IManager access the DirXML Overview link. Locate the existing resource sync drivers and update the Event Transformation Policy on the Subscriber Channel. Simply copy and paste the contents of the provided Event.xml(sys:\tomcat\4\webapps\nps\DirXML.Drivers\Event.xml) and then restart the driver. ***** Note that the internal date displayed using the modules list on the server may not match the date of the actual physical file. This behavior is normal and does not indicate a problem. ISSUE: - Added configuration option to NSMI to force it into synchronous mode. - Fixed defect where NSMI could not create temp files and was returning out of memory. - Failover problem where the syslog on the cluster master node shows an error 1007 trying to online the resource. Workaround solution: Check to ensure there are not NSMIT-######.* files in sys:\tmp. If so, delete them and try again. - Fixed the way eDirVfs handles eDirectory iteration of large objects. Before this change, eDirVfs would emit invalid XML if eDirectory had to iterate over a large object. - Fixed issue where if the resource fails to come online on the target cluster, it will not be marked primary in the BCC state structures. - Addressed an Abend while adding a resource to the BCC watch list. - Updated Event stylesheet to work properly with IDM 2.0.2 - Added trace support for better troubleshooting of BCC (BCCLIB, NSMI, EDIRVFS). Start the modules with the -t switch to enable tracing. - Increased the size of the buffer used for eDirectory reads " />

BCC 1.0 Patch 3 Update

(Last modified: 28Jun2005)

This document (10097836) is provided subject to the disclaimer at the end of this document.

fact

NOVELL TECHNICAL INFORMATION DOCUMENT

TITLE:  BCC 1.0 Patch 3 Update
TID #:  2971540
README FOR:  bccup3.exe

SUPERSEDES:
bccup2.exe

NOVELL PRODUCTS and VERSIONS:
NetWare 6.5

ABSTRACT:

The NLMs included in this patch address multiple issues with the Business
Continuity Cluster 1.0 code for NetWare.


-----------------------------------------------------------------
DISCLAIMER
THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO
NOVELL.  NOVELL MAKES ALL REASONABLE EFFORTS TO VERIFY THIS
INFORMATION.  HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT
IS FOR YOUR INFORMATION ONLY.  NOVELL MAKES NO EXPLICIT OR IMPLIED
CLAIMS TO THE VALIDITY OF THIS INFORMATION.
-----------------------------------------------------------------


INSTALLATION INSTRUCTIONS:


NetWare 6.5
This fix can ONLY be installed to a server running BCC 1.0 and NetWare 6.5 sp2
or later.

1. Run bccup3.exe, unzipping the files into a directory.

2. If the directory where the files were extracted is not located on the server
to be updated, copy that directory structure to the server to be updated.

3. Load NWCONFIG.NLM on the server to be updated.

4. On the main menu of NWCONFIG.NLM, select "Product Options". This will
display a new menu. On this new menu, select "Install a product not listed" and
then press <ENTER>.

5. Follow the on screen prompts to correctly select the location of the
directory to where the patch was extracted on the server.

6. Press <F10> to start the file copy procedure.

After installion completes, issue the uldbcc.ncf command to unload BCC modules
and then reload using the ldbcc.ncf command.

NOTE:
Newely created BCC resource drivers will utilize the new XML template
(BCCClusterResourceSyncronizaion.xlm)included in the patch. Previously created
drivers will have to be manually updated as follows.

Via IManager access the DirXML Overview link.
Locate the existing resource sync drivers and update the Event Transformation
Policy on the Subscriber Channel. Simply copy and paste the contents of the
provided  Event.xml(sys:\tomcat\4\webapps\nps\DirXML.Drivers\Event.xml) and
then restart the driver. 

*****
Note that the internal date displayed using the modules list on the server may
not match the date of the actual physical file. This behavior is normal and
does not indicate a problem.

ISSUE:

- Added configuration option to NSMI to force it into synchronous mode.

- Fixed defect where NSMI could not create temp files and was returning out of
  memory.
 
- Failover problem where the syslog on the cluster master node shows an error
  1007 trying to online the resource.  Workaround solution: Check to ensure
there
  are not NSMIT-######.* files in sys:\tmp.  If so, delete them and try again.
 
- Fixed the way eDirVfs handles eDirectory iteration of large objects.  Before
  this change, eDirVfs would emit invalid XML if eDirectory had to iterate over
a
  large object.

- Fixed issue where if the resource fails to come online on the target cluster,
it     will not be marked primary in the BCC state structures.

- Addressed an Abend while adding a resource to the BCC watch list.

- Updated Event stylesheet to work properly with IDM 2.0.2

- Added trace support for better troubleshooting of BCC (BCCLIB, NSMI,
  EDIRVFS).  Start the modules with the -t switch to enable tracing.

- Increased the size of the buffer used for eDirectory reads

 

document

Document Title: BCC 1.0 Patch 3 Update
Document ID: 10097836
Solution ID: NOVL102279
Creation Date: 01Jun2005
Modified Date: 28Jun2005
Novell Product Class:Netware

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.