30.10.2014 Views

Administration Guide - Avaya Support

Administration Guide - Avaya Support

Administration Guide - Avaya Support

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

MAS Alarms<br />

MAS Alarm - MT PERF 23<br />

Level<br />

Major.<br />

System Descriptor<br />

FEDB Max Size: FEDB File Size exceeding 2.0 GB.<br />

Description<br />

This alarm indicates that the size of the front end database has exceeded 2.0 GB.<br />

Repair Procedure<br />

1. Stop the MM Messaging Application Server service. See Appendix C,<br />

Stopping and Restarting Modular Messaging Services.<br />

2. Save the current copy of FEDB database. The FEDB database,<br />

fedb.mdb, is located in<br />

C:\Program Files\<strong>Avaya</strong> Modular Messaging\VServer<br />

3. Copy C:\Program Files\<strong>Avaya</strong> Modular Messaging\VServer\FEDB.bak<br />

to C:\Program Files\<strong>Avaya</strong> Modular Messaging\VServer\fedb.mdb.<br />

4. Set registry key HKLM->Software->Octel->Geneva->Vups_<br />

UserProfileServiceMgr->NodeSeqTable value to 0,0;<br />

5. Set registry key HKLM->Software->Octel->Geneva->Vups_<br />

UserProfileServiceMgr->CosSeqNo value to 0.<br />

6. Start the MM Messaging Application Server service.<br />

Note: Changing the registry in this way causes the FEDB to be rebuilt when the<br />

MAS is restarted. This effectively takes the database out of service, possibly<br />

for several hours.<br />

<strong>Avaya</strong> Modular Messaging Release 3.1 with the <strong>Avaya</strong> MSS<br />

February 2007 MAS <strong>Administration</strong> <strong>Guide</strong><br />

A–27

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!