Config datastore activation failed.java.sql.SQLException: The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction

From DocWiki

(Difference between revisions)
Jump to: navigation, search
Jayark (Talk | contribs)
(New page: == Config datastore activation failed.java.sql.SQLException: The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction == {...)
Newer edit →

Revision as of 09:04, 4 May 2010

Config datastore activation failed.java.sql.SQLException: The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction

Problem Summary  %MCVD-CVD-3-COMPONENT_SET_CDS_ERROR: Component ConfigDataLinker.setCds error: type=CRS Config Datastore, nodeId=2, Exception=com.cisco.database.util.DBException:

SyncConfigData; nested exception is: java.sql.SQLException: The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction

Getting the above mentioned error while activating config and historical datastore on the second node of the HA cluster.

Error Message java.sql.SQLException: The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction
Possible Cause Verify whether the host file has been updated and whether both nodes can ping each other using host name. Looks like the customer has used the same image of Windows for both nodes. You can confirm this by running MSDTCPing on both nodes. If that is the case then they have to reimage node 2 and install Windows from DVD.

To run MS DTC ping: 1. Download MS DTC Ping from Microsoft Download Center http://download.microsoft.com/download/d/0/0/d00c8f6b-135d-4441-a97b-9de16a1935c1/dtcping.exe 2. Extract it to some dir on both nodes 3. Double click on exe file, on both nodes 4. Now enter the host name of other node and try to ping 5. The ping should work in both directions for MS DTC to work fine

The log file will have the reason why the ping fails; it will also have the Machine CID which should be different for both nodes. If it is the same they have used the same windows image for both the servers.

If there is some other problem to establish the distributed connection the logs will have the details.  This can happen because of firewall blocking the ports or due to 3rd party software or incompatible network adapter driver.
Recommended Action  : Remove the second node from the cluster using Appadmin control center -> component activation page. Install fresh OS using disk in the second node and install CRS.
Release Release 7.0, Release 5.0
Associated CDETS # None

Rating: 0.0/5 (0 votes cast)

Personal tools