MDS Error 300034 - The member code is already used by a member that was deleted. Pick a different code or ask an administrator to remove the deleted member from the MDS database + Solution

Hi All

when we tried to delete the members whose code is not autogenerated ( ie having specific code to the member) and try to insert the same code member we will get this error.

The delete in MDS is a Soft delete which will available in MDS tables even after these deletes .

So fallow these steps to avoid the error

Step1 :

 Reverse the transaction of the deleted member to bring the member and its code back to an active state.
See here for reactivating a deleted member: https://msdn.microsoft.com/en-us/library/ff487037(v=sql.110).aspx

 Step 2 :
After that , use entity based staging to purge (permanently delete) the code from MDS. This will require using an import type of 4 or 6.
Here is more information regarding entity based staging: https://msdn.microsoft.com/en-us/library/ee633854(v=sql.110).aspx

 Step 3: 
Insert the member with same code now you wont get error .

Comments

Post a Comment

Popular posts from this blog

SSAS : A connection cannot be made to redirector. Ensure that 'SQL Browser' service is running. (Microsoft.AnalysisServices.AdomdClient). + Solution

Problem : have installed Analysis service on my server machine through remote login from my service account. I am able to open Analysis services from there. When I open SSMS from the same service account on my local machine, I am not able to connect to that Analysis service. It is giving me error by saying : "A connection cannot be made to redirector. Ensure that 'SQL Browser' service is running. (Microsoft.AnalysisServices.AdomdClient). A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connection host has failed to respond 10.245.192.111:2382(System)." Solution : Based on my research, the issue was caused by the Browser Service account was changed to the domain account. In your scenario, you can try to connect to the Analysis Service using <Servername>:2383 instead of instance name. Or you can change the Browser Service account to "Local System".
Read more

SSIS Error : Unable to infer the XSD from the XML file. The XML contains multiple namespaces

Image
Problem : When we have Multiple Namespaces in the Xml Source which we need to load the Data from   as we shown below Then we will face a issue in generating XSD for that XML Error : Unable to infer the XSD from the XML file. The XML contains multiple namespaces. (Microsoft Visual Studio) Solution : First we need to avoid multiple namespaces to transform your source file to a format that doesn’t refer to the namespaces. SSIS has an XML task that can do the transformation. 1) Add the XML task to an SSIS   Control Flow and edit it. 2) Change the OperationType property value to XSLT, the SourceType to File connection and the Source to your source file that has the problem. 3) Set the SaveOperationResult property to True and expand the OperationResult branch. Set DestinationType to File Connection and the Destination to a new XML file ( ModifiedInput.XML). 4) Add the below script to a new file and save it with an xslt file extension (Input.XSLT) <
Read more