reset CM3.x dbase ?

[alpritchard]

Does anyone know a quick way to erase the CM dbase in order to start again- other than re-installing the whole package from scratch.

ie the equivalent of IOS cmd "write erase"

[avanderzanden]

HI

So you mean you don't have a backup of your DB :-)

I think you are raising a crucial point here. I have also suffered from numerous occacions where my userpart of the database got corrupted. I tried to recovered the DB via the accompanied backup but still it did not work ( on CM 3.0.5a ) , so had to reinstall CM3.05 to recover. On previous 3.X releases I have also met the famous error so I am no longer scared by this.

I think this issue should trigger Cisco by properly descibing how to do this in tips and tricks.( Hello ...)

BTW I did not see any response from Cisco people on my posting from yestday , wonder if and when Cisco people read this, I assume they do...

Regards

Aad

[alpritchard]

i logged a tac case to see what the official response was and hey there isn't a quick way to purge the dbase.

Reinstall is the only current way.

If i re-install, take a backup of the clean dbase and then use this at some point in the future to restore from that kind of achieves the same thing.

Tho' from what you said above it isn't guranteed to work !

[dgoodwin]

When you say the "userpart of the database" are you referring to the Global Directory portion of the CallManager administration?

If so, this is LDAP information held in the DC Directory application.

If that is the only part on which you need to "start from scratch" I believe you can go to a command prompt (Start -> Run -> cmd) and from the directory C:\dcdsrvr\bin run the command:

C:\dcdsrvr\bin>cleandsa

Then run:

C:\dcdsrvr\bin>avvid_cfg "(local)" CCM0300

where CCM0300 is the current database in use. You can find that DB name by looking in the CallManager GUI and go to Help -> About and click Details.

It's always a good idea to run an avvid_save before you run these commands so you can always do an avvid_restore if you mess things up.

Also note that this is the command that you may run on a publisher machine. The commands for a subscriber would be slightly different.

As far as the CallManager SQL database, there is no way to wipe this info, you would have to reinstall the machine.

[avanderzanden]

Hi

By userpart I meant that only the USER DB was corrupt, the devices listed allright in the DB.

I printed your info for future reference. Thanks for the tips!

Aad

[MJefferson]

I had the same problem on a 3.0(6) Call Manager. Is this something we can expect to encounter now?

[jschonemann]

What would the command be for a subscriber machine?

[kechambe]

Configuring the subscriber server

---------------------------------

- cd C:\dcdsrvr\bin

cd C:\dcdsrvr\bin

- Stop the directory services. This can be done using Service Manager. The service name is "DC Directory Server". Stop this service.

net stop dcdirectory

-run cleandsa on the subscriber server

cleandsa

- Start the DC Directory service.

net start dcdirectory

- configure the subscriber. PLEASE REPLACE **publisher** by actual publisher hostname. Similarly **subscriber** by the actual subscriber name.

avvid_scfg.cmd **publisher** **subscriber**

(i.e.) avvid_scfg.cmd keithscm1 keithscm2

Thanks,

Keith