ccm cant add phones Update failed. Could not insert new row into the table

Unanswered Question
Jan 17th, 2009
User Badges:

I have a ccm 6.0.1.2000-3, and I cant insert new phones, The error is Update failed. Could not insert new row into the table. the same problem occur when I try to change pin on some users

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Rob Huffman Sun, 01/18/2009 - 07:39
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi Samuel,


It sounds like this bug;


CSCsl22549 Bug Details


CM5.1.3- Database cannot be updated due to full change notify queue.


Symptom:


Getting error "Update failed. Could not insert new row into the table." from

CCMAdmin web page when trying to update/reset some device.


Setting CFwdAll from the phone also doesn't work.


Conditions:

CM 5.1(1)-5.1(3) and ***CM6.x


From CLI on the publisher:

run sql select count(*) from device -> works fine

run sql update device set description = 'test' where pkid =

'27b24dbd-9bc8-43ee-92ef-211f7c9dfbd3' also gives error:

"Could not insert new row into the table"


run sql select count(*) from DBLCNQueue -> 39606 rows present

"show tech notify" was showing:

Msg I 0/0 P 0 DB 39606 **DB count > 50**


Workaround:

Empty DBLCNQueue table from SSH into Pub: run sql delete from DBLCNQueue

Reboot Pub and then the Subs one by one. Note that deleting entries from

DBLCNQueue delete all change notifications. Any changes made to the system

will not take effect until after the reboot.



Status

Fixed


Severity

3 - moderate


Last Modified

In Last Year


Product

Cisco Unified Communications Manager (CallManager)


Technology



1st Found-In

5.1(3)


Fixed-In

6.0(0.246)

7.0(0.78)

5.1(3.1112.1)

6.1(1.52)

5.1(3.77)

6.1(1.9901.46)

7.0(0.39000.26)

5.1(3.9901.100)

6.0(1.2126.1)

6.1(1.2102.2)

5.1(2.3125.2)

6.1(2.1000.13)

7.0(0.66666.1)

7.0(0.66666.2)

7.0(1.11000.2)



Hope this helps!

Rob

Actions

This Discussion