How to configure SMO clone to destination where interactive password entry is not required
- Last Updated:
SnapManager for Oracle (SMO)
When cloning to remote secondary host workflows are processed by command line batch jobs, SMO will prompt for the destination host's password. To avoid the interactive session, the secondary host password can be cached to the primary host, and allows batch jobs to proceed without interuption.