Replication is working fine but compare hangs.
When ora_setup is run with lower case tns alias or SID, but config file is using upper case for @o.SID or @o.TNSALIAS.
In that case ora_setup would create a lower case entry in database line in connections.yaml file. And compare would be expecting a lower case *declt*SID*.lck file while post created an upper case lock file.
Example:
datasource:o.ORA11GR2
jessica.mytest tony.mytest myhost@o.ORA11GR2
Run ora_setup with lower case tns alias ora11gr2 which result in lower case ora11gr2 in database line in connections.yaml file
o.ORA11GR2:
database: ora11gr2
dstype: oracle
password: 579fd983ba1a5cbeca
plugin_direction: both
plugin_version: 1
tns_alias: ora11gr2
user: SPLEX9902
On target post creates upper case lock file ORA11GR2 when compare is launched
declt_1-1_ORA11GR2_a01174f_p5635.lck
Compare is expecting lower case declt_1-1_ora11gr2_a01174f_p5635.lck and it hang
WORKAROUND:
1. Rerun ora_setup with upper case tns alias on source and target and use the same case for datasource and @o.SID or @o.TNSALIAS in config file. Cleanup and reactivate config.
2. If you can not clean up and rerun ora_setup, then shutdown sp_cop and modify the connections.yaml file database entry to upper case if the *declt*SID*.lck is generated with upper case on target. You may have to change var dir/db/sid_routes.actid and sid_wildcards.actd to upper case SID_routes.actid and SID_wildcards.actid to avoid reader failed to load routedb error.
Example:
o.ORA11GR2:
database: ora11gr2 ------------> Change this to ORA11GR2
dstype: oracle
password: 579fd983ba1a5cbeca
plugin_direction: both
plugin_version: 1
tns_alias: ora11gr2
user: SPLEX9902
If you modified source connections.yaml file database entry to upper case, then go to var dir/db
mv ora11gr2_routes.28 ORA11GR2_routes.28
mv ora11gr2_wildcards.28 ORA11GR2_wildcards.28
STATUS:
This issue will be addressed in future release of 9.2
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center