BRBackup, smo backup, or smsap backup fails in SMO or SMSAP due to missing profile-to-repository mapping in the credential cache
- Views:
- 233
- Visibility:
- Public
- Votes:
- 9
- Category:
- snapmanager-for-sap
- Specialty:
- legacy
- Last Updated:
- 9/15/2020, 9:25:43 AM
Applies to
- SnapManager for SAP (SMSAP) 3.4.x
- SnapManager for Oracle (SMO) 3.4.x
Issue
When attempting to run a backup through the BR*Tools SMSAP, or issuing a backup command with either SMSAP or SMO, it fails with the error:
[ERROR] SMSAP-20006: There is no profile->repository mapping defined for profile "<SM_PROFILE>" in credentials cache for OS user "<OS_USER>". If profile "<SM_PROFILE>" actually exists, run "profile sync" against the repository in which that profile is contained.