cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
447
Views
0
Helpful
3
Replies

Call Manager 9.x orphaned data

Sam Jesberg
Level 1
Level 1

I used the bulk import/export menu, to import some Call Pickup Groups.

The bulk job said 16 records "passed"

When I go to look for them in the GUI, they do not appear.

When I try to search the DN in the Route Plan Report, is says "null exception"

When I try to create them manually, it errors saying they already exist.

Is there a "run sql delete" command I can use to delete these orphaned CPG out of the system?

Maybe a solution I'm not thinking about?

Since this issue breaks the Route Plan Report feature, I might have to reinstall call manager for my customer, which I'd much like to avoid.

Thanks,

Sam

1 Accepted Solution

Accepted Solutions

The resolution is to go the root and delete the PKID for the orphaned Call Pick Up group numbers.

Go to the CLI of CUCM and run the below command to get the PKID for orphaned numbers.

admin:run sql select pkid,dnorpattern from numplan where dnorpattern = 'number'

for Ex :- admin:run sql select pkid,dnorpattern from numplan where dnorpattern = '1000'

Once you get the PKID for the orphaned numbers, get to the root account and delete the PKID by below command 

delete from numplan where pkid='PKID'

for Ex :- delete from numplan where pkid='d190feb9-dd1b-0777-c80c-a64b93653f22'

You need to get into the dbaccess to run the below command. Involve TAC so as to get the root access and they will perform the workaround. 

This will prohibit you from rebuilding the server. Hope this will be helpful. 

Regards

Abhay Reyal

Regards
Abhay Singh Reyal
The Only Way To Do Great Work Is To Love What You Do. If You Haven’t Found It Yet, Keep Looking. Don’t Settle

View solution in original post

3 Replies 3

Sam Jesberg
Level 1
Level 1

I found this information on a forum, but it did not work (the sql command to delete). Just for reference:

FYI the issue was that BAT inserted the Pickup Group Numbers into the
numplan table, but errored out on inserting the Pickup Group Names into the
the appropriate table, leaving the numplan entries orphaned. The solution
that TAC eventually worked out was to use the CLI to remove them from the
table. The command they used was:

run sql delete from numplan where dnorpattern = 'XXXX'

where XXXX was the bad pickup group number.

The resolution is to go the root and delete the PKID for the orphaned Call Pick Up group numbers.

Go to the CLI of CUCM and run the below command to get the PKID for orphaned numbers.

admin:run sql select pkid,dnorpattern from numplan where dnorpattern = 'number'

for Ex :- admin:run sql select pkid,dnorpattern from numplan where dnorpattern = '1000'

Once you get the PKID for the orphaned numbers, get to the root account and delete the PKID by below command 

delete from numplan where pkid='PKID'

for Ex :- delete from numplan where pkid='d190feb9-dd1b-0777-c80c-a64b93653f22'

You need to get into the dbaccess to run the below command. Involve TAC so as to get the root access and they will perform the workaround. 

This will prohibit you from rebuilding the server. Hope this will be helpful. 

Regards

Abhay Reyal

Regards
Abhay Singh Reyal
The Only Way To Do Great Work Is To Love What You Do. If You Haven’t Found It Yet, Keep Looking. Don’t Settle

Abhay,

Thank you. You're actually the one that worked with me on the TAC case, with Ken, to get this fixed. I appreciate!