Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 
0 Kudos

Below are two frequent errors while accessing Change Item History application in SAP Netweaver GDS.

1. Connection error: Specified jdbc Alias parameter is invalid or Data source is not running.

Solution: Create a custom data source
for connecting to database of MDM repository in ‘Netweaver Administration’ -->
ConfigurationManagemen-->Infrastructure-->Application Resources.

Creation of jdbc datasource depends on database being used. Below link will be helpful to create required jdbc datasource.


After creating custom datasource successfully, create an alias for this datasource with the name ‘gdstr’ in lowercase. Name of datasource can be any name but it’s recommended not to keep same name as of alias.

2. You do not have authorization to use the MDM Change Tracker application.

Solution: If we use SAP Netweaver GDS in portal mode then there is authorization error on click of Change Item History button. To fix this issue Role with MDM_CHANGE_TRACKER action has to be assign to Portal user.

GDS Console uses Netweaver UME Guest user for the change tracker authentication. So in GDS Console it is enough to assign the change tracker role for the UME Guest user.

But when user login to portal it uses Netweaver UME user for it. The change tracker uses that UME user for authentication. So the portal user needs to have the change tracker role as well.

SAP recommends assigning the change tracker role to portal users in Netweaver Administrator UME. This can easily achieved by creating a UME role and assign MDM_CHANGE_TRACKER action to this role, afterwards assign this role to a group for all portal users.

In both GDS console and portal mode user should have assigned a role with change tracking enabled in MDM console.

Labels in this area