Follow this issue

Details

  • 6614
  • 24 Apr 2012
  • 18 Sep 2017
  • Release Killer
  • Win
  • Rejected
  • Online Environment - 3.0 v49
  • Bug

Links:
#63450 Make dictionary step that makes sure all Counter-% preferences are gone Status: Solved

Steps to Reproduce

See:

 

Hi, we have a customer that has recently upgraded from 6.x to 7.0 SR2. 

The login takes "forever", and we've tracked the problem down to there being 31.000 rows in crm7.userpreference where prefsection = 'System' and prefkey = 'Counter-bla, bla, bla...'. 

SELECT * FROM crm7.userpreference WHERE prefkey like 'Counter-%' 

Are those an old variant of what we now have crm7.refcounts for? Are those preferences still used in 7.0? 

Frode
Content is edited
 

Re: Slow startup caused by 'Counter-%' rows in crm7.userpreference

Safe to delete, to many of them will actually eventually kill the web client. If I remember correct we clean up for 7.1

 

Re: Slow startup caused by 'Counter-%' rows in crm7.userpreference

Excellent, thanks!

 

Re: Slow startup caused by 'Counter-%' rows in crm7.userpreference

 Margrethe Halvorsen Romnes (SuperOffice ASA) wrote:
Safe to delete, to many of them will actually eventually kill the web client. If I remember correct we clean up for 7.1


Please explain "what "kill the web client" means, explicitly.

Thanks,
Jan
 

Re: Slow startup caused by 'Counter-%' rows in crm7.userpreference

I have an FAQ for it: http://cs.superoffice.com/scripts/c­ustomer.exe?_sf=0&custSessionKe­y=&customerLang=en&noCookies=tr­ue?action=viewKbEntry&id=110875­

 

Re: Slow startup caused by 'Counter-%' rows in crm7.userpreference

Thanks!

 

Re: Slow startup caused by 'Counter-%' rows in crm7.userpreference

Deleting the rows reduced the startup time from ~3 minutes to 10 seconds Smile

 

RE: Slow startup caused by 'Counter-%' rows in crm7.userpreference

Margrethe, the counters-preferences are still there after upgrading from 7.0 SR3 to 7.1 RC1. So I don't think they are automatically cleaned up in 7.1.


Comments

This is not likely to happen on any new Databases. We will create a FAQ on how to solve this: http://cs.superoffice.com/scripts/customer.exe?_sf=0&custSessionKey=&customerLang=en&noCookies=true&action=viewKbEntry&id=111238

 


[2012.05.23: frode]

This should be included as a step in the Consistency check in DBSetup.exe