|
|
|
date: Mon, 31 Oct 2005 08:29:05 -0800,
group: microsoft.public.exchange2000.information.store
back
Re: Help event 1025!
Hi JA,
If you create a new database and move the mailboxes to it you will not move
any of the whitespace with you. So depending on the amount of existing
whitespace in your database you can see some change in the size of the
database file. (check the 1221 events to determine how much whitespace you
have)
Give your current situation moving to a new store might not be a bad idea.
It will not correct any major issues with the database but it also will not
move any corrupted data ... if we can't move it via MAPI it won't be moved.
Hope this Helps,
--
Matthew Byrd
Microsoft PSS
Run Microsoft Exchange Server Best Practices Analyzer Today
http://www.microsoft.com/exchange/exbpa
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
"JA" wrote in message
news:639FDE06-29C5-4D4A-A0D6-D6ADEFBA3490@microsoft.com...
> Wow thanks for the very informative response....yes i am with you in
> saying
> that if there are not many of these its should not be a concern.
>
> Although i have antoher question.
>
> If i create a new database and move mailboxes there will the database size
> shrink? or will an offline defrang still need to be performed?
>
> thx
>
> "Matthew Byrd [MSFT]" wrote:
>
>> Hi JA,
>>
>> The error code here 0xfffffaea translates into JET_errTableLocked. If
>> you
>> received only a single one of these or a small group I would not be too
>> worried it was probably a transient issue that does not necessarily
>> indicate
>> an issue with your server. If on the other hand you received quite a few
>> of
>> these >10 - 15 or so then I would be a bit concerned.
>>
>> In the case of receiving many I would make sure that Exchange is running
>> at
>> the latest version. For Exchange 2000 right now that is basically
>> anything
>> greater than version 6603 or the executables. (just check store.exe)
>>
>> Update Rollup for Exchange 2000 (KB870540)
>> http://www.microsoft.com/downloads/details.aspx?FamilyID=363A57A4-8BED-4BBB-BBE4-ABC11AB04611&displaylang=en
>>
>> Also make sure that any 3rd party application that are touching Exchange
>> directly (AV, Backup) are updated to the latest versions available.
>>
>> You may also want to schedule some down time to run an offline defragment
>> of
>> the database. For 100GB this will take around 10 hours or so if you can
>> do
>> it to local disk.
>>
>> Since you have a 100GB database I know that you are running The
>> Enterprise
>> version I would strongly recommend that you create additional databases /
>> storage groups and reduce the size of your databases.
>>
>> Once last thing ... as always run ExBPA it maybe able to tell you more
>> than
>> just what I have put here.
>>
>> Hope this Helps,
>> --
>> Matthew Byrd
>> Microsoft PSS
>>
>> Run Microsoft Exchange Server Best Practices Analyzer Today
>> http://www.microsoft.com/exchange/exbpa
>>
>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>> "JA" wrote in message
>> news:D5D33A7E-1489-47C7-B43E-C37F2F85A064@microsoft.com...
>> > sorry, this data base is over 100GB and there is not much i can do with
>> > it. I
>> > am planning a exch 2003 upgrade within the next month or so. Should i
>> > be
>> > worried about this. this is the only instance.
>> >
>> > i find articlles related to database curuption but not with the exact
>> > error
>> > code of 0xfffffaea
>> >
>> > "JA" wrote:
>> >
>> >> Event Type: Warning
>> >> Event Source: MSExchangeIS Mailbox Store
>> >> Event Category: General
>> >> Event ID: 1025
>> >> Date: 10/31/2005
>> >> Time: 9:17:38 AM
>> >> User: N/A
>> >> Computer: TYLER
>> >> Description:
>> >> An error occurred on database "2-Second Storage Group\BCST Mailbox
>> >> Store
>> >> Function name or description of problem: SLINK::EcUpdate
>> >> Error: 0xfffffaea
>> >>
>> >>
>> >>
>>
>>
>>
date: Tue, 1 Nov 2005 16:32:50 -0500
author: Matthew Byrd [MSFT]
|
|
