We can look into why bypass isn't working but the first question I have is why are you including a pega OOB table in your RAP file at all.
I would want to see the complete log file from prpcUtils but there are 2 issues. The first issue is why is import wizard not recognizing that the pr_data_admin table exists which is probably related to the database user who is running prpcUtils not having he privileges needed to get the metadata of objects in the data and rules schemas. I believe that even if you choose to bypass making schema changes the import wizard will still go through the synchronization to know what schema changes are needed. The second issue is why does it try to create the table again if you have selected bypass.
I actually read the problem description incorrectly. You have set this to false and thus you are not trying to bypass making schema changes.
So I still want to understand why you are including a pega OOB table in your RAP file but the ultimate issue is with regards to privileges. Does the database user who is running prpcUtils have Select_Catalog_Role? This is an Oracle OOB privilege which allows the user to view the catalog and thus metadata of all of the schemas in the database. Without this privilege the user is not able to find the metadata of the pr_data_admin table and thus assumes it doesn't exists and tries to create it.