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
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
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
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
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
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
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 ?
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