Issues fixed in Pro2 6.3

Pro2 6.2.3 Generate Target Schema functionality does not generate SQL commands for tables having a table name beginning with Repl

Characters such as é are not saved in the stored odbc password in the file C:\\Pro2\\bprepl\\Scripts\\mfg.pf when using the pro2 6.2.3 web interface link: [https://localhost:9992/pro2/static/landing/replication/settarget|https://localhost:9992/pro2/static/landing/replication/settarget]

Adding a source db using the pro2 6.2.3 web interface generates a .pf file having a -db entry using the logical db name instead of the physical db name

There is no method to stop Pro2 processes based on a schedule on Pro2 6.x

Code generated for the bulk load of a table in Pro2 6.2 does not compile.

Pro2 CDC fails with Value too large to fit in INTEGER (15747) and (2570)

For some files prefix \{&ReplDB} is missing.

Pro2_env.sh doesn’t include the custom folder in the propath to pick the custom files

In Pro2 WAN setup PASOE has memory leaks, several agents consuming gigs of memory.

Data discrepancy issues were found in multiple Pro2 operations.

There should be an easier way to select multiple tables in the Advanced Configuration page when assigning threads in v6.x.

When source databases are CDC enabled during 1st Pass is LAN, no issues are reported but when 2nd PASS is WAN and set ENABLE_OE_CDC YES in predefs.i, get an error when starting Admin tool “DB version is < v11" which is not informative.

EXCEPT_TGT_FIELDS property is still there but has been omitted from the Pro2 templates.