Data Connector 7.0 SP5 Release Notes

Article:DOC2996  |  Created: 2010-09-21  |  Updated: 2010-09-23  |  Article URL
Article Type


Build number 7.0.8641

Data Connector (formerly known as Connector Solution) is a component of the Symantec Management Platform. This component lets you transfer data between external data sources and the configuration management database (CMDB). The ability to transfer data lets you leverage the data that already exists in the CMDB or other applications. Data transfers can be scheduled, so updates can be regularly and automatically made to keep data current. Data Connector supports many data formats: OLEDB, ODBC, LDAP, XML, and CSV.

Data Connector also lets you manipulate the data that is already in the CMDB. This ability lets you easily normalize and correct errors in your data. For example, you can use Data Connector to normalize company names so data is consistent.

This document contains the following topics:

Installation and upgrade


Data Connector 7.0 requires the following:

  • Symantec Management Platform 7.0 SP2 or later.

New installation

Data Connector is included in the Symantec Management Platform installation. It is no longer a seperate product.

You can install this product by using the Symantec Installation Manager. You can download the installation files directly to your server or you can create offline installation packages.

For more information, see the Symantec Management Platform Installation Guide and knowledgebase article 45732.


You can upgrade this product from Connector Solution 6x. The product is upgraded when you upgrade Notification Server 6x to Symantec Management Platform 7.0 SP5.

For more information, see the Symantec Management Platform Installation Guide and knowledgebase article 45732.

Installation and Upgrade issues

The following issues are known issues related to installing and upgrading this product. If additional information about an issue is available, click the Article ID link.

Issue Article ID Internal ID
Connector purge policy values are not migrated

Connector Purge Policy Configuration page settings are not migrated when migrating from Connector Solution 6.x to this version of Data Connector. The settings on this page are “Keep log files for a number of days old” and “Number of log files to keep per rule.” If you do not want to use the default values for these settings, you must manually change them.



Back to top

Fixed Issues in This Release

The following are issues that were fixed in this release. If additional information about an issue is available, click the Article ID link.

Issue Article ID Internal ID
Unable to map to the columns when creating a CMDB rule

When you created a new CMDB rule, if you chose SQL Query or Report for the target you were unable to map to the columns for the CMDB rule. The columns did not appear in the Key column mappings drop-down lists.



Back to top

Known Issues in This Release

The following are known issues for this release. If additional information about an issue is available, click the Article ID link.

Issue Article ID Internal ID
Transferring data with an Oracle database

Currently you can only use OLEDB and “Directly enter connection string” data source definition types to connect with an Oracle database. If you are connecting using Directly enter connection string, you must use the following string:

"Provider=MSDAORA.1;Data Source=ATRS;User ID=system;Password=password"

If you try to use the ODBC data source definition type, you will get the following error:

“Test failed. ERROR [IM003] Specified driver could not be loaded due to system error 1114 (Oracle in OraClient10g_home1). “

Cannot connect to SQL Server when using ODBC data source definition

Data Connector cannot connect to a Microsoft SQL Server if you use an ODBC data source definition. Instead, use an OLEDB data source definition to define a SQL Server data source.

Unable to get child objects from path when using 'Anonymous' Authentication type with an LDAP data source in an Active Directory environment

With an LDAP data source, if you use anonymous authentication and attempt to load the classes, you get the following error:

"An operations error ocurred"

This is not a bug, but a configuration issue. This is caused by the LDAp server not being configured to allow anonymous data retrieval.

Only the first associated resource returned instead of all of them

When you are editing a column expression in a resource transfer rule, if you select an association from the resource attribute selector that allows for multiple associated resources, the evaluation of this selection returns only one and NOT all of the associated resources.

Error sorting Run History data for a data connector rule

For the data connector rule pages in the Symantec Management Console, there is a Run History section that displays information in a table. If you click certain column heading to sort the data by that column, you get an error that results in no data being displayed in the table. The columns that cause this problem are Run Time, Log File, and Test Run. Note that not all rule types have these columns.

Error sorting Manage Resource Data Classes and Manage Resource Associations data for a bulk resource export rule

For the Bulk resource export rule page in the Symantec Management Console, there are a Manage Resource Data Classes section and a Manage Resource Associations section that display information in a table. If you click a column heading in one of these tables to sort the data, you get an error that results in no data being displayed in the table.

Error sorting test results of a health check task test

With a few data connector or CMDB rules created, if you run the Connector Rules Health Check Task or CMDB Rule Health Check Task, you will get an error if you click on a column to sort the data in the Output section of the Details dialogue of the task.

Duplicate entries in the verbose logging page when running a resource import rule

After removing resources and running a resource import rule with “Delete removed resources” selected, a section named “Removed resources” is added to the verbose logging page. If you select or deselect any checkbox in the Display section of the resource import rule page, the page is refreshed. After the page is refreshed, all resources that were previously listed in the “Removed resources” section are duplicated in the section, so the list of resources you removed is duplicated.

Unhandled exception occurs when testing an incomplete OLEDB data source

If you are configuring an OLEDB data source and the configuration is incomplete and you use the “Test data source” feature before saving the page, the page crashes and displays an unhandled exception message. If you save the page before using “Test data source,” the page properly reports the incomplete configuration without crashing. If the page crashes, changes made in the page might be lost. However, you can re-enter the configuration information by reloading the page.

Data imported into a multirow data class does not generate a change history

If you import data into a multirow data class with no key column and use "Update" mode,
No change history information is generated.

Status reported from a test run of an organizational rule is incorrect

If you create an organizational group import rule that can create new groups and resources in the CMDB if they do not exist and you import data that requires the creation of new groups, the number of groups created, as reported by a test run of the rule is not correct and does not match the value reported by the actual running of the rule, which is correct.

 Limitations of the OLEDB data source import query

If you choose to use a direct query, the query string is passed to the selected OLEDB data provider for processing. Data Connector expects the OLEDB data provider to execute the query and return a data table.  Data Connector does not process the query in any way. Depending on the data
provider, the query syntax and supported operations can vary (see the documentation for the OLEDB data provider for more information).

If the OLEDB data provider supports transaction, Data Connector starts a transaction before executing the query. The transaction is rolled back at the end of the execution. This ensures that data is not modified through the processing based on the import query. However, if the selected OLEDB data provider does not support transaction, then the data protection is not available.

Unhandled exception 'Failed to load viewstate' when switching data source transfer direction

When you configure a Resource Import/Export Rule, if there are already data
class or association mappings configured on the page and you change the data
replication direction (import to export or export to import), the page will
crash with an unhandled exception error. You cannot change the data replication
direction for a configured and saved rule. You must create a new rule instead.

Limitation with the bulk resource export test feature

If you are configuring a bulk resource export rule and enable the "Export only the changes between export runs" option, all the subsequent runs after a full run are incremental runs. However, every time you use the “Test run” feature, the feature performs a full, not incremental, test run.

Connector rules health check task reports a healthy status even after data classes are deleted

If you configure a rule with some data classes and subsequently delete some of these data classes from the CMDB and run the Connector rules health check task, the task reports that the rule is healthy. This is because when the health check task runs each rule as a test, missing data classes are ignored.

Script errors with connector rules opened from "Connector rules health check Task"

After running "Connector rules Health Check Task," if you select 'Task Instance Details' to view the details of running the task and then click on a rule to open the rule configuration page, you get the error "top.windowManager is null or not an object" and you will not be able to modify the rule.



 Avoid running rules concurrently

Stagger rule schedules to avoid contention and performance problems.

Exported rows number is greater than the total number of rows

The bulk resource export rule's run status exported row count is currently
calculated as the sum of the number of resources added or updated, plus the number of resources removed since lthe ast run. As a result, the message "x out of y rows of data have been exported" can be misleading in cases when there were removed resources.

 LDAP authentication caching

On the LDAP data source configuration page, when you successfully authenticate to an LDAP server, the authentication persists until the page is reloaded. Because of this behavior, if the user name and password are changed after the initial successful authentication, the page does not re-authenticate and continues to use the same connection.
The security risk is minimal because the connection is re-authenticated when the page is reloaded or when any import operation is performed.

Collection migration issue

Data connector v6.x could have CMDB Rules, Resource Export Rules, and Bulk Resource Export Rules which use “Collections”. During the migration process, the “Collections” used by those rules are converted to “Resource Targets”, and “Resource Targets” that are converted from the “Collections” should contain the same memberships as the legacy “Collections”. In this release, the converting process is not functioning properly; the “Resource targets” converted from the legacy “Collections” do not contain memberships. To work around, you need to recreate the “Resource Targets” for those rules by using the legacy “Collections” to make them work properly.

 Virtual data class documentation missing

The help and user guide documentation is missing the information for virtual data classes. Virtual data classes let you integrate 3rd party system data with the Symantec Management Platform CMDB without the need to import the data into the CMDB.

External data that is mapped to a virtual data class appears as a normal resource data class in the CMDB. Virtual data classes provide seamless integration with the Symantec Management Platform reporting features; you can create resource reports based on virtual data classes using the report builder just like reports with any other resource data classes. The report queries the data directly from the external data source at the time you run the report.

The following provides some brief information on using virtual data classes. More information will be made available in an updated version of the Data Connector documentation.

The virtual data class feature uses the Microsoft SQL Server Linked Server functionality to connect to 3rd party system data. Linked servers to these systems must initially be setup in SQL Server before you can use virtual data classes. See the Microsoft documentation about Linked Servers ( for more information.

To create an editable virtual data class

1. In the Symantec Management Console, on the Settings menu, click All Settings.

2. In the left pane, click Settings > Notification Server > Resources and Data Class Settings > Data Classes.

3. Right-click Data Class, and click New > Virtual Data Class.

4. In the right pane, configure the virtual data class.

5. Click Save changes.


Back to top

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices