Splitting F00950 per environment

You probably know that Oracle does not recommend or support placing table F00950 anywhere other than in the System data source, making it environment specific (see document id 1054242.1- E1:SEC: How to Define Different Security Setup by Environment). But you might ask yourself why not? One might argue that preliminary tests showed all security types appear to work correctly and despite duplicating security maintenance, it would be great to define security per environment.

Well, I have recently come across a concrete issue that will happen if F00950 is anywhere else but in System data source.

Here is the scope. An admin user needs to create a number of solution explorer tasks in DV. DV has its own F00950 mapped to Control Tables - Test and in it there is a Solution Explorer security record enabling OMW Logging (with this setting on, any sol. explorer task that is create or modified will be automatically added to users’ default project in OMW). The user then creates the new tasks, and then goes to OMW to move them from their default project to another project he can then promote eventually promote to PY and PD. But there he