Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Unable to delete partition and duplicate entries in NumPlan table

I have a partition named "BillingInternal" and have double-checked to make sure all devices, etc are not using it. However, when I try to delete this partition, it tells me it is in use by a CS, CM or NumPlan.

I found that the NumPlan table has a reference to this partition via extension 6104. Interestingly enough, the NumPlan table had two different entries for x6104, each corresponding to different partitions. I deleted the phone, rebooted the server and the double entries are still there. In addition, the NumPlan table also has duplicate entries for x5110. All others are single entries.

What is this for and should there be:

1. Duplicates?

2. Entries for extensions that have been deleted?

8 REPLIES
New Member

Re: Unable to delete partition and duplicate entries in NumPlan

What version of Call Manager are you running? I had a similar problem. After days of fighting it, we were told by TAC to upgrade. That fixed it. We were then able to go back and delete the old partitions.

New Member

Re: Unable to delete partition and duplicate entries in NumPlan

I am running 3.09.

What did you have to upgrade to?

New Member

Re: Unable to delete partition and duplicate entries in NumPlan

After doing some additional digging into NumPlan's table values, I just want to know if I am safe to delete the duplicated ("unused") references to the duplicate extensions?

New Member

Re: Unable to delete partition and duplicate entries in NumPlan

Not sure....but I'd run a clean backup before deleting them so you can recover if it fails. Good Luck.

Cisco Employee

Re: Unable to delete partition and duplicate entries in NumPlan

I never feel comfortable recommending any manual interaction with the SQL database.

However, I can tell you that if you try to delete a record from NumPlan that is still linked to by a record in a different table, the delete command will fail.

If the delete command succeeds then it should not have any ill effects in my experience. And you should probably restart all CallManagers in the cluster at this point (after waiting a minute) so that the database layer service can re-read the database into CallManager.

New Member

Re: Unable to delete partition and duplicate entries in NumPlan

I'm not a fan of manually altering the SQL tables either, so I found a work-around within the CM SA web utility.

The fix is:

1. Look at the NumPlan table, look for duplicate extensions and their corresponding "fkRoutePartition" field values.

2. Look at the RoutePartition table and match the NumPlan's "fkRoutePartition" values to the RoutePartition's "pkid" values for the corresponding Partition. Make a note of the "name" values.

3. Go into the CM SA web utility, go to the phone device and delete the existing extension (this should delete one of the duplicates, or triplicates, etc, in the NumPlan table).

4. Click on "Line X", key in the same extension and the duplicate's partition Name. At this point (since the row is already in the table), the other values should auto-populate (like the CFNA, CFB, CS's, etc).

5. Click on Update and Close, then Update at the device level.

6. Go back into the problem extension, click on delete.

7. Check the NumPlan table and that duplicate extension should be removed.

8. Repeat for additional duplicates.

This came to me this morning, I tested it and watched the tables . . .

Voila, the dupes are gone and no need to worry about direct SQL data manipulation. Finally, I was able to delete the un-needed Partition and CS.

My question to those who should be in the know . . . why the duplicates?

New Member

Re: Unable to delete partition and duplicate entries in NumPlan

. . . why the duplicates?

I started on 3.08, then 3.09 and both had the duplication issue. Now, I am running CM 3.12c and still have the duplication issue crop up periodically.

I have found that what you do in the CM System Administration screens (when deleting extensions) isn't always reflected in the tables due to other devices (hunt groups for example) pointing to the deleted extension.

Given:

A device with x5108.

A Pilot Point configured with a Hunt Group pointing to x5108.

Procedure (to create the problem):

1. Delete x5108 and update.

2. Delete the device that used x5108.

At this point, the Phone Administrator (person) thinks all is well because the System Administrator interface reports no errors, but the DBA would see something different. But if you would look at the NumPlan table, you would find that the x5108 record still exists . . . because the Hunt Group is still pointing to that record. Somehow, SQL knows about the reference and DOES NOT delete the record, even though the System Administration utility goes happily on its merry way. Even if you delete the Hunt Group's reference to the deleted extension AFTER deleting the phone, the record still stays in the table.

To resolve use the following (same process from my previous post):

1. Look at the NumPlan table, look for duplicate extensions and their corresponding "fkRoutePartition" field values.

2. Look at the RoutePartition table and match the NumPlan's "fkRoutePartition" values to the RoutePartition's "pkid" values for the corresponding Partition. Make a note of the "name" values.

3. Go into the CM SA web utility, go to the phone device and delete the existing extension (this should delete one of the duplicates, or triplicates, etc, in the NumPlan table).

4. Click on "Line X", key in the same extension and the duplicate's partition Name. At this point (since the row is already in the table), the other values should auto-populate (like the CFNA, CFB, CS's, etc).

5. Click on Update and Close, then Update at the device level.

6. Go back into the problem extension, click on delete.

7. Check the NumPlan table and that duplicate extension should be removed.

8. Repeat for additional duplicates.

Further research (from an illiterate), shows that CSCdt27581 (see http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdt27581) says to manually delete the record from the NumPlan table . . . my question to this solution is:

What is the state of the Hunt Group at this point?

Would it be pointing to an invalid "pkID" after the record deletion? Then what would happen? (according to one of the previous posts, this record couldn't be deleted, so this question is probably moot)

Could it be that some of these (and possibly other) issues are because the System Administrator doesn't seem to enforce table integrity as well as what the SQL does?

Any more, when I delete an extension, I run Enterprise Manager in parallel to make sure what I did in SA really happened in SQL. I also periodically open the NumPlan table and check for duplicates.

New Member

Re: Unable to delete partition and duplicate entries in NumPlan

If you are having similar issues and want more detail from TAC, referring to case number B936634 may assist the research.

246
Views
0
Helpful
8
Replies