Re: Processing dimensions never ends

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi,

Copying the database has been done but without success.

The problem seems to be in the OLAP Repository (.mdb file) on this server.

When we transfer (using ARCHIVE) an equivalent OLAP database from another
server (running well) the SAME problem occurs.

The problem is linked to the OLAP Server itself and not the Database.

Is stops during DIMENSION processing so I doubt AS is getting short in
memory (2 Go available).

YES AS and SQL are patched with the latest SP3a.

Best Regards,


"Monte" <Monte@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E317BCA6-EC70-4929-8353-CEA79A9070E4@xxxxxxxxxxxxxxxx
> Hi,
>
> Migrating the OLAP Repository to SQL Server is basically a good option,
but
> I doubt, that that can fix the problem.
> You might try to copy the current database, which copies the
> structure-information without data loaded. This might correct any possible
> data-structural errors.
> You'll have to check via processing the Copy-DB.
>
> Also try making Backups and restoring them to possibly correct structural
> errors.
>
> Another reason could be, that there is not enough physical memory to
process
> the whole Database in one transaction. I came across this problem once and
> had to split the processing into multiple transactions (in fact, one for
each
> dimension/cube).
>
> If all that still didn't fix the problem, there is still the option to
> reinstall AS.
>
> Greetings Monte
>
> PS: I assume AS and SQL are patched with the latest Service Pack? (SP3a i
> guess)
>
> "Jean-Marc PUGIN" wrote:
>
> >
> > Hi,
> >
> > Basically, on one of our customer Analysis Server, processing dimensions
> > never ends.
> >
> > It stops in the Analysis Manager on a random dimension sometimes on a
> > virtual dimension and basically never ends.
> >
> > For example, our procedure which is automated in a batch file launching
a
> > DTS was terminated by the customer after 20 hours.
> >
> > One answer was to migrate the OLAP repository.
> >
> > Can you confirm please ?
> >
> > As we assume that the problem is in the Access database storing the
> > Repository, we are also searching ways to force AS to re-create this
Access
> > database.
> >
> > We asume that the following procedure will do the job:
> >
> > - un-installing Analysis Services
> > - deleting the MDB Access database
> > - installing Analysis Services
> > - restoring the OLAP database
> >
> > Can you confirm please ?
> >
> > If you already have an answer, we will greatly appreciate your help.
> >
> > Best Regards,
> >
> > Jean-Marc PUGIN
> > Co-founder & C.T.O
> >
> > Mobile Workers
> > Software Editor for Corporate Purchasing Portal
> >
> >
> >


.

Relevant Pages

  • Re: Can you update/process AS2005 cube with AMO and SQL authentication
    ... the database instead of a secured access. ... Authentication while its required to access the AS server! ... ' Errors in the OLAP storage engine: ... the dimension, with the ID of 'Product', Name of 'Product' was being ...
    (microsoft.public.sqlserver.olap)
  • RE: Processing dimensions never ends
    ... that that can fix the problem. ... You might try to copy the current database, ... > virtual dimension and basically never ends. ... > One answer was to migrate the OLAP repository. ...
    (microsoft.public.sqlserver.olap)
  • RE: Processing dimensions never ends
    ... that that can fix the problem. ... You might try to copy the current database, ... > virtual dimension and basically never ends. ... > One answer was to migrate the OLAP repository. ...
    (microsoft.public.sqlserver.olap)
  • RE: Processing dimensions never ends
    ... that that can fix the problem. ... You might try to copy the current database, ... > virtual dimension and basically never ends. ... > One answer was to migrate the OLAP repository. ...
    (microsoft.public.sqlserver.olap)
  • RE: Processing dimensions never ends
    ... that that can fix the problem. ... You might try to copy the current database, ... > virtual dimension and basically never ends. ... > One answer was to migrate the OLAP repository. ...
    (microsoft.public.sqlserver.olap)