Novell is now a part of Micro Focus

My Favorites


Please to see your favorites.

Cluster objects are not getting created in landing zone

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


Novell Open Enterprise Server 2 (OES 2) Linux Support Pack 3
Novell Business Continuity Cluster 1.2.2
Novell Cluster Services 1.8.8
Novell Identity Manager 3.6.1


Trying to BCC-Enable a cluster resource and the objects are not showing up in the landing zone in the other cluster.

The following errors show up in the IDM trace logs after enabling debug on the drivers.
  createEntry -672 ERR_NO_ACCESS
  modifyEntry -613 ERR_SYNTAX_VIOLATION


Make sure the proper rights are given to the user who is assigned as security equals on each IDM driver.  BCC 1.2.2 Administration Guide for OES 2 SP3

Use the Admin user as security equals on each IDM driver in BCC cluster.

Additional Information

1. Enable IDM debug logging.   Follow our BCC 1.2.2 Online documentation.
2. Analyze the IDM trace logs.  Look for the following eDirectory type errors.
createEntry -672 ERR_NO_ACCESS

When you BCC enable an NSS cluster resource, the IDM driver will create 4 objects in the destination cluster.
- Cluster resource object which will reside in the cluster container.
The other 3 objects will be in the landing zone container specified in the IDM driver config.
- Virtual NCP server object
- Pool object
- Volume object.


This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7009683
  • Creation Date:02-NOV-11
  • Modified Date:26-APR-12
    • NovellBusiness Continuity Clustering
      Cluster Services

Did this document solve your problem? Provide Feedback