After you have populated the "copy user groups" DB process in your target database, you can override its table rule to edit the list of user groups that will be copied. You need only do this if you don't need all of the user groups that are defined in these DB processes (but it never hurts to have too many user groups as they won't be used unless you link users to them).
At this point, you're ready to submit the background process identified on your "copy user group" DB processes. This background process highlights the differences between the user groups in the demonstration database and the target database (the target database is the environment in which you submit the background process).
When you submit one of the DB processes defined above, you must supply it with an environment reference that points to the source database (i.e., the demonstration database).
When the process runs, it simply highlights differences between the user groups in the source database and the target database. It creates a root object in the target database for every user group that is not the same in the two environments (actually, it only concerns itself with user group that match the criteria on the DB process's table rule described above). You can use the Difference Query to review these root objects and approve or reject them.
After you've approved the root object(s) associated with the user groups that you want copied, submit the CL-APPCH batch process to cause your target database to be changed. You must supply the CL-APPCH process with two parameters:
Copyright © 2011, Oracle and/or its affiliates. All rights reserved.