Andreas' Adventures

Hmm, sometimes life is funny. If I say to you that I have a generic patch, you would expect one patch that can be applied to all versions. Not in this case. I need to apply a patch for the Oracle IDM Suite (10.1.4). Finding the patch is already difficult - and then there are four versions of the same patch - apparently based on different versions of the underlying J2EE. In my opinion this is not generic. Trial and error led me to one of the four versions - which then came back with: OPatch detects your platform as 46 while this patch xxxxxxx supports platforms: 0 (Generic Platform) So again - it seems that my definition of generic differs from Oracle's view. I would understand an error, if the patch was for platform 46 or 18 or whatever. But here a generic patch is apparently not applicable for my platform. Luckily Metalink Note 404473.1 offers a solution. So setting the following: export OPATCH_PLATFORM_ID=0 does trick the opatch into believing that it is no Linux machine any l...

Came across the following last week - and I have to admit that this is something which made my eyes hurt. When you are in the Policy Manager of the Oracle Identity Management Suite and you want to add a group you REALLY need to know that there is a hidden link on this page. Try to find it yourself in the next picture: Found it? No? Let me give you a hint. Look in the blue band and search for some blue text :-) I'm not sure if anybody knew about this. I checked the documentation, and nothing about adding a group to such an Authorization Rule for groups is written in there. I wonder if anybody at Oracle knows about this hidden gem. I will log an SR with Support and also mail some people I know at Oracle to discuss this perfect piece of user interface design.