Good afternoon, We're planning on an upgrade in the near future from 8007 to 8105. I'm reaching out to see if anyone had any issues or 'gotchas'. My biggest concern is that we have hundreds of users folders with thousands of private procedures.

Any advice or things to look out for?

Thanks!

This message has been edited. Last edited by: Tamra,

Tom,

Count yourself SUPER lucky that it's not a large migration from 7.x to 8.x. All you'll really have to do is a CM from your 8.0.x to the newer 8.1.x for your repo/MR stuff. Haven't had any issues with that facility yet. Reporting server folders can just be mirrored over (copy/paste). Security can be mapped through CM as well.

I know how super lucky I am as we went through that two years ago.

I've found that the CM tool with 8.0 has failed when packages are too large. Have you had that experience?

Oh yeah? So there is a light at the end of the tunnel you're saying? K, great! lol

The only CMing we did from 8.0.x was from 8.0.09 to 8.1.03. Didn't see any issues with those versions. So, maybe we lucked out with not being on 8.0.07?

- get the latest 8.1.05 instance. RS gen 913 or later. There were issues in SQL Generation when using DBA Security and Business Views before that
- If you currently use GRPLIST and AD groups, you will need to review that closely. GRPLIST will no longer return the AD group but rather the WebFOCUS group.
- DBASECURITY had some big changes to it. If you do anything with DBA Security validate that your sql is still being generated correctly. Namely, there is a change in the way the NAME attribute behaves. It used to be that you could have a generic DBA File for Master files that contained the same field that needed to be restricted on. In that case you would use NAME=SYSTEM. In 8.1.05 now, setting NAME=SYSTEM means that you want that field restriction to ALWAYS be invoked regardless of whether you are using a field from that table or not. Now in 8.1.05 you have to specify the segment to avoid this. You will no longer be able to share a DBAFILE in those cases, but will have to create a DBAFILE for each one separately.
-I find Dynamic Language Switching to be less stable in 8.1.05 then it was in 8.0.08. I now get processing errors when switching between languages that I didn't get before.

When I upgraded from 8.0.08 to 8.1.05, I would say for me the biggest problems were around security of the Reporting server. So if you use a lot of Security there, I would do thorough unit testing of all of that.