Cannot import localization file to SAAS SBM via the Application Administrator: Error: An error occurred while importing locales: On-Demand user not allowed to import new Key:
(Memberof=CN=Mariner_Group,CN=Users,DC=supportad,DC=aline,DC=com) With this filter it would only import the Active Directory users that were a member of the Mariner_Group cn We've found this free ldap browser tool very helpful in creating the filters as it shows the results of the filter without actually importing the users into Mariner.
Importing users as copies of an existing user via the User Import in LDAP Setup & Tools can cause privilege type issues for the new user depending on what the home page report is set to for the user being copied from. Although the new user may have privileges to a(n) application(s), if the home page report set from the copied user is set to private, attempting to access that application(s) may cause the following error:
No matter which user submits an import request for component versions, and no matter which user is used as the "logon user " for the source type tool, the Component Versions list has another user as "Created by".
If you look in the Privileges section in Application Repository make sure the user you're logged in as has the appropriate permissions to see the newly imported apps.
The symptom of the problem was after adding a new user via the LDAP import tool and then going into the Web Administrator tool and clicking the details button for that user you get an error "Unspecified exec error" and you can't see the details for the user . This only seemed to throw an error for the newly created user. He could still view the details for users already in the system.
This article is for users upgrading from Release Control 6.0 who do not want to deploy the new process apps or snapshots. It explains how to use an auxiliary table to set your custom columns in the Release Control Request and Deployment Unit widgets. If you are using the applications installed with Release Control 6.0.1 or above, the feature described here has already been implemented.
When upgrading Dimensions 6.0 to 7.0 using the manual method, the import can fail on Base Database objects that utilise different tablespaces. For example you may store indices in their own tablespace or you may have users created in a specific user tablespace. The manual upgrade procedure does not create these additional tablespaces as part of the Oracle installation and database creation.
