Hi all:

When I update the change dimension, the Analysis Servies will be restart
every 30 Sec. When I look at the data folder, it has create a list of mdmp
files. As a result I use windbg to debug the file and the content of the
file doen't give me any hint:
Loading Dump File [Y:\Program Files\Microsoft Analysis Services\Backup
Data\SQLDmpr0015.mdmp]
User Mini Dump File: Only registers, stack and portions of memory are
available

Windows Server 2003 Version 3790 MP (4 procs) Free x86 compatible
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Debug session time: Thu Apr 21 08:25:06.000 2005 (GMT-7)
System Uptime: not available
Process Uptime: 0 days 0:00:42.000
Symbol search path is: c:\windows\symbol
Executable search path is:
.................................................. ...
(ca8.d58): Access violation - code c0000005 (!!! second chance !!!)
eax=05d32000 ebx=000000c8 ecx=0537b4bc edx=00000000 esi=00000520 edi=00000000
eip=7ffe0304 esp=0537c218 ebp=0537c288 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
SharedUserData!SystemCallStub+0x4:
7ffe0304 c3 ret

Please help me on this, if anyone know the problem!

Thanks,

Kent

Those are mini-dump files.
It means that Analysis Services is crashing -- probably because of dimension
corruption.
You need to contact your support organization and get the latest hotfix for
Analysis Services.
You can do a full reprocess of your dimensions to see if that will fix the
situation, but there is no guarantee that it won't re-occur again.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"kent kent" <kentkent (AT) discussions (DOT) microsoft.com> wrote

I've had the problem you specified in the past as well and indeed it
was caused by corrupt MOLAP structures. The only way I was able to fix
the problem was to go into my Analysis Services "data" folder...find
the .ODB file for the problematic database...delete it and the
corresponding subfolder with the same name. This purges the system
completely of the MOLAP structures, but not of the definition
information which is safely tucked away in the MS Analysis Services
repository. You can then rebuild you MOLAP structures by rebuilding
your database in Analysis Manager. This will recreate the .ODB file
and recreate the corresponding subfolder and its contents.

I was never able to fix my issue by simply rebuilding...I had to do a
full purge as described above and then rebuild in order to recover from
my similar circumstance.

Textbook corruption issue. If any of the data files are corrupt, dimension
or fact data, the services stops and starts itself like this. Reprocessing
dims or fact partitions will be difficult if the services stops and starts
itself this frequently.

If possible, the best thing to do is to delete the OLAP database(s) on the
server and restore them from a good archive. If your data is so large that
it can't be archived, you're better off restoring the entire default data
folder and the last known good copy of your SQL/Access repository.

Good luck, I've had this frustrating problem a few times before.


"Dave Wickert [MSFT]" wrote: