has anyone experienced an issue with the Managed Reporting Administartion not closing its connections to the Database? I have configured my Development Client to use Oracle Authentication/Authorization. I have 1000 test users in the WF_MRUSERS table. When I query it using the MRAdministration tool it will continuously create connections instead of pooling them. I have currently set my max connections to 30, but the tool will not release those connections when the query has finished or when I logout of Managed Reporting Administration.

Any thoughts?

This message has been edited. Last edited by: eric.woerle,

I've opened up a case with IBI on this one. They say they have found an error in my trace file that is currently in programming to be resolved. I didn't get any information on what this error was or what the actual problem is though. I'm hoping to be able to talk to programming about it so I can get some more information soon. I will update as soon as I know what the problem is.

I spoke with IBI regarding this and apparently there is some bug where if your password is greater then 4 character, you get the issue I was experiencing. I trimmed my passwords that I was loading to 4 and I was able to load the users without an issue. With this workaround I was able to access my users through the MR Admin tool and loaded 1000 test users in with no issues. To my knowledge IBI is actively working on a resolution to this.

Any idea whether this is specific to Oracle RDBMs?

We don't use MRE, but our report caster is running from an MS SQL database and our password is longer than 4 characters (of course it is!). Could we be affected by this?

if you were affected by this, you would now.

IBI wasn't very forthcoming with what the issue really is on this one. They didn't want to get into any details so I don't know if this is specific to Oracle or not. My guess is that this has to do with us using ETL to load the users and not the normal MR Admin Tool processes.

When I put my 1000 test users back into my table, I added a few users to the table with passwords and didn't have any issues. The tool creates a 31 character encrypted string. This didn't create any issues in my small test. So it might have something to do with my passwords not matching with the normal length encryption. To be honest, the whole thing just doesn't make any sense to me.

I really do wish that they weren't so secretive about it. It makes it hard to put in the appropriate safe guards and to code properly, when I don't know what I'm coding for. But for now I'll just have to move forward with this and hope that user 10,001 doesn't cause an issue.

luckily for us, we are using SSO for authentication, so the password really doesn't mean anything. We just need something in there.