ISSUE USING PUTTY SFTP FOR PSUB REPORT FILE VIEWING
(Doc ID 452865.1)
Last updated on NOVEMBER 28, 2022
Applies to:
Oracle Clinical - Version 4.5.1 to 4.5.2 [Release 4.5.1 to 4.5.2]Information in this document applies to any platform.
Symptoms
You have set up SFTP as indicated in <Note 344932.1>
You find that PuTTY SFTO (psftp.exe) is the closest client to the instructions provided (actually
looks like they were written for it).
Everything seems to work as expected: from the command line, you can sftp from the middle tier to the
database back-end, login without password (so the privatepublic key is working), but when running a
PSUB report, cannot view its output or log files.
The files are generated by PSUB on the back-end, but they do not get transferred to the temporary
location on the middle-tier
Steps to Reproduce Problem:
The SFTP script as created by the Oracle Clinical file viewing program, cannot run with psftp, since it contains commands that psftp does not understand, such as 'user' or 'ascii'.
You find that PuTTY SFTO (psftp.exe) is the closest client to the instructions provided (actually
looks like they were written for it).
Everything seems to work as expected: from the command line, you can sftp from the middle tier to the
database back-end, login without password (so the privatepublic key is working), but when running a
PSUB report, cannot view its output or log files.
The files are generated by PSUB on the back-end, but they do not get transferred to the temporary
location on the middle-tier
Steps to Reproduce Problem:
The SFTP script as created by the Oracle Clinical file viewing program, cannot run with psftp, since it contains commands that psftp does not understand, such as 'user' or 'ascii'.
This is a typical script:
In this Document
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |