rules.schema.name=pegadpg (existing single schema)
data.schema.name=pegarpg (New schema)
This is not correct. The existing single schema will become the data schema in the new environment. You will have a new rules schema, migrate the rules table to it, upgrade the rules schema, and then upgrade the data schema.
See the section "Upgrading from a single-schema to split-schema configuration" in the guide on how to do a single to split schema upgrade. It is not a one step process using the IUA. You would use the migrate script to migrate the rules tables to new rules schema, run the upgrade of the rules schema, run migrate script again to create rules schema objects (assuming you are using one database for upgrade), and then run the data schema upgrade. The other option would be to upgrade to a single schema and then use the migrate script afterwards to split it. With the single to split approach your existing 6.x system can be in use up until you get to the data schema step. Since the upgrade of the rules schema is the longest part of the upgrade you would minimize down time. For the single schema upgrade and then split your 6.x system needs to be down as soon as you start the upgrade.