[solved] Failed to collect metadata for Universe

We have BOMM 12.1.0.9 working with BOXI3 SP5 on windows 2003 / Oracle 10 repositories and face a LOT of issues.

  • BOMM is not able to collect metadata on any univers with error message

[I-0000000] 2012-06-29 14:19:27.300 Universe [/TST/Datawarehouse Universe]. Collection starting
[W-0000000] 2012-06-29 14:19:27.331 Universe [Datawarehouse Universe] Failed to collect metadata for Universe Unknown Error : Datawarehouse Universe
[I-0000000] 2012-06-29 14:19:27.347 Universe [/TST/Datawarehouse Universe]. Collection finished
[I-3026719] 2012-06-29 14:19:27.378 Universe [Datawarehouse Universe]. Universe [Datawarehouse Universe]. Universe [Datawarehouse Universe] Failed to collect metadata for Universe Unknown Error : Datawarehouse Universe
[W-3026719] 2012-06-29 14:19:27.394 Universe [Datawarehouse Universe]. 0000000
[W-3026757] 2012-06-29 14:19:27.409 Universe [Datawarehouse Universe]. Collection failed. Correct errors indicated in the log and rerun the integrator.
[I-3026764] 2012-06-29 14:19:27.425 Universe collection progress: 1 of 1 completed
[W-3026614] 2012-06-29 14:19:27.519 User collection complete. Users processed: 5; errors: 0 deleted: 0. Groups processed: 7; errors: 0 deleted: 0

in other case, when BOmm runs a job, it create about 100 sessions on Oracle server and nobody can connect on it ! The only way is to kill sessions in such times

Also, it takes hour to collect informations when they are only a few reports

Thank you for your help and advises on this product

Bernard


bernard timbal :fr: (BOB member since 2003-05-26)

you will get unknown error in case the Designer SDK is crashing, are you on windows 2008 env ?
what is the user under which BOE SIA is running ?
is BO Client App installed on the sever where integrator is running ?

the oracle sessions are for BOMM repo user? this was an issue in earlier version 12.1.0.5 but you are on 12.1.0.9 the fix should be there already


manoj_d (BOB member since 2009-01-02)

Hi manoj

Thank you for your reply. It’s hard to find people knowing this product. Are you using it ?
We are on Win2003 server using a special admin account to launch and run sia
yes, bomm is installed on the same box than boe
I will check the permissions of the admin account and let you know

Regards

Solved : It was definitively a missing right on the AD account running the SIA


bernard timbal :fr: (BOB member since 2003-05-26)

what right was missing we are seeing same issue in another customer env, they also run the services using a service account, but not able to figure out what permission is missing


manoj_d (BOB member since 2009-01-02)

Humm, you seems to work on this product at BO Right ? :wink:

what about this error on the log regarding reports analyse according to you ?

what time out it is talking about ?


bernard timbal :fr: (BOB member since 2003-05-26)

yes, I work on this product developemnt, can you attach the log to the case that you have filed with support, I will take a look

the CMS connection is dropping or expiring I need to see where is this happening


manoj_d (BOB member since 2009-01-02)

are you able to reproduce the issue with oracle session not closing by collecting universes from a folder ? if yes, can you export that universe to BIAR file and attach to the case ? I need to reproduce this for debugging


manoj_d (BOB member since 2009-01-02)

Hi Manoj,

Thank you for your input. Regarding the case, I am sure that the issue is due to AD missing rights on the account witch runs the SIA. While I change it to another one, it runs fine without error. As I change again the SIA owner with the BO account service, same issue. There is something about a missing right preventing the AD account to launch the designer (because I suspect BOMM to launch Designer session in background to analyse univers, right ?) Would it be possible to have the list of the rights the AD account should have ? Regards


bernard timbal :fr: (BOB member since 2003-05-26)

is it possible to have a conf call and look at your env ? I will have to run some tests in your env with additional tracing to findout which call is failing

since you already have a case can you have support setup a call for this ?


manoj_d (BOB member since 2009-01-02)

Hi Manoj

It is very kind to you to propose such think but I think, the best thing is to let the BO-SAP guy in charge of the case (which is not closed) deal with :lol:

Thank you again for you replies !
Regards
Bernard


bernard timbal :fr: (BOB member since 2003-05-26)