• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 846
  • Last Modified:

Unable to write License usage information to NDS

Cannot find a solution for:

10-04-2007 .....
     NLSLSP.NLM: WARNING: Unable to write license usage information to NDS. Historical usage information may be incomplete. Check "[Root]" partition synchronization status. Service will continue. WGCST.WGCST.westgen.
0
OCMBOCESRIC
Asked:
OCMBOCESRIC
  • 5
  • 4
1 Solution
 
OCMBOCESRICAuthor Commented:
I deleted the server NLS_LSP object in NDS. What next?
0
 
ShineOnCommented:
Is there more than one server?
0
 
OCMBOCESRICAuthor Commented:
Yes but only one getting it. Tried DSrepair, sync, etc.
0
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
ShineOnCommented:
What does your replica ring look like - is this the one with Master of [Root]?  Is this the DA server?  Does it hold a read/write or master replica of the partition with the license containers?
0
 
ShineOnCommented:
To answer the earlier question about the NLS_LSP object - to re-create it, you LOAD SETUPNLS on the server whose NLS_LSP object was deleted.  Beyond that...
0
 
OCMBOCESRICAuthor Commented:
Did that but still got the same message immediately after loading setupnls
0
 
OCMBOCESRICAuthor Commented:
what is the "beyond that"? Checking to answering your other Qs...
0
 
OCMBOCESRICAuthor Commented:
this server is the one with Master of [Root]....
0
 
ShineOnCommented:
That's the beyond that.  Now that the object is back but you're still getting the message, and we know he's Master of [Root] we can start troubleshooting the problem.

As the message indicates, NLSLSP is having trouble with writing license usage info into the directory, presumably because of inconsistencies in the replica ring.

When you say "tried DSREPAIR, sync, etc." what exactly did you try?   If all you did was a dsrepair unattended repair, I suggest you try this:

DSREPAIR -A
 Advanced Options menu
 Partition and Replica Operations
    select the [root] partition
 Report synchronization status of all servers

This will give you a report of whether all the replicas in the ring are in sync.  If they're not, then the reason for the message is there are too many unsynchronized transactions for NLSLSP to complete the action.  If they're not in sync but there aren't any replicas that aren't communicating (ex: -625 errors, etc) and time is in sync, then you should take the "Repair Ring, Selected Replica."

If you have errors anywhere along the way, and you're not sure what to do, post back.
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now