There have been reported problems with dimension corruption (fixed in
SP4) -- and this sounds like what you might be running into.
Stop the msmdsrv service, go into the AS data folder and rename each of the
database folder temporarily to something else, then restart the service. If
it comes up, then one-by-one stop and restart the service bring each
database on-line until you find the one with the corrputed dimension. Then
do a similar activity with each dimension until you find the corrupted
dimension. Once you find those, then do a full process of the dimension (and
underlying cubes/partitions which might be affected).
--
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.
"quertyanalysis" <quertyanalysis (AT) discussions (DOT) microsoft.com> wrote
Quote:
The MSSQLServerOLAPService, when started, hangs in the starting mode. It
takes more than 24 hours for the service to change the status from
"starting"
to "started". I've checked the memory in Task Manager and it's fine. Has
anyone encountered this problem? Any insights and suggestions are
appreciated. |