APAR status
Closed as program error.
Error description
Problem Description: Import fails when similarly named remote profile already exists. Customer receives an error, "Cannot find specified object," when trying import the sftp.bbh.com Remote Profile from another instance. The remote profile does not already exist in the new instance. Customer ran the following query and determined there was a similarly named Remote Profile already in the new instance: Select profile_id, name, remote_host from SFTP_PROF where UPPER(NAME) LIKE '%SFTP.XXX.COM%' This returned a Remote Profile with the name "qcsftp.xxx.com". When the qcsftp.bbh.com Remote Profile was deleted, the import for sftp.xxx.com runs successfully. From reviewing the code in the SSHRemoteProfileProxy class, it appears that the import logic first checks for a remote profile name "like" the name. Simulation Steps (Steps taken by support or customer to replicate or comments) Reproduced error on oxnard:46000 (5020402). From reviewing the code in the SSHRemoteProfileProxy class, it appears the import queries the SFTP_PROF table to find a remote profile name that is like the name in the export xml file (e.g.,sftp.xxx.com) using a query like this: SELECT COUNT(NAME) FROM SFTP_PROF WHERE UPPER(NAME) LIKE ? If the name already exists, it queries the table again to find the current column values to compare to the export file for an update. Only this time it looks for an exact match on name. The where predicate for that query is as follows: WHERE NAME = ? The first query finds the "qcsftp.xxx.com" remote profile when it queries the SFTP_PROF table for a remote profile name like "sftp.xxx.com". The second query ends up throwing the "Cannot find specified object." error since it does not find a remote profile name equal to "sftp.xxx.com". Expected Behavior (The desired results) Customer is able to import remote profile when a remote profile with a similar, but different, name already exists. Business Impact (How the customer is impacted by the problem) Customer unable to import remote profile even though it does not exist in the system.
Local fix
STRRTC - 416028 PC / PC Circumvention: None No workaround available
Problem summary
USERS AFFECTED: All users who use the SFTP profile import functionality PROBLEM DESCRIPTION: Import causes issues when a similarly named remote profile already exists in the system. PLATFORMS AFFECTED: ALL
Problem conclusion
RESOLUTION SUMMARY: A code fix has been provided. DELIVERED IN: 5020500_3
Temporary fix
Comments
APAR Information
APAR number
IT00431
Reported component name
STR B2B INTEGRA
Reported component ID
5725D0600
Reported release
524
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-03-19
Closed date
2015-03-17
Last modified date
2015-03-19
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
STR B2B INTEGRA
Fixed component ID
5725D0600
Applicable component levels
R525 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2.4","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
19 March 2015