PRROWID Pro2 Replication

Malaiyappan

New Member
The Bulk data (1000-m records approx) need to load into the target Oracle database.
It needs to be handled via ETl.
Once data loaded we need to sync up with Pro2 the same value will patch the table.
The PRROWID Column doesn't exist in Source Progress side.

Question:

When the pro2 replicates into the target table Oralce PRROWID has some system generated Unique value like (0x000000003abbd9c5).
How the PRROWID column can handle while via etl manual load.
How the values are getting generated / loaded?

Once the data got loads Pro2, We enable and target replication sync up, It needs to have the value in PRROWID column.
 

Malaiyappan

New Member
Thanks for your input:
Out of these columns, the “PRROWID” column is having NOT NULL constraint in the target table in schema.
But we don’t have any mapping column from the source for this target column.
When we load the data via Pro2 the PRROWID value has - 0x0000000039eaf8b1
Please let us know the how this column should be mapped or populated with values in the target table.
 

Malaiyappan

New Member
Since 1000-m record not possible to load via Pro2, Hence we need to kick start initial load via ETL, Please advise on this.
 

TomBascom

Curmudgeon
The PRROWID column is an extra column created by Pro2. It is not a real column in the source table. It is a result of running the 4gl ROWID() function on the buffer being replicated.

Why is it not possible to load the big table? Pro2 has a feature called "bulk load" that they use for that purpose.
 

Malaiyappan

New Member
Since we have 300 Gb data (1000 m records)i snot possible to Replicate via pro2 might take longer time, Hence we do Bulk load via ETL and enable the Pro2 once data loaded nearly, Hence the Column PRROWID how to handle and populate data from target side.
 

TomBascom

Curmudgeon
I see no reason why it shouldn't be possible. Merely stating that there are a lot of records is not a reason why the Pro2 bulk load will not work.

If you have actually tried it and run into an error or a problem then _that_ might be a valid reason but it would depend on what, specifically, the issue is.
 
Last edited:
Top