Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Smarts NCM: Data Migration from 4.1.1 to 9.x: How to update cm_device_server table in multi-Device Server environment (329969)

Last Updated: 5/29/2020Categories: TroubleshootingTotal Views: 7734Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

This article explains how to update the Smarts NCM cm_device_server table as the final step in the data migration from Smarts NCM 4.1.1 to 9.x in an environment that has more than one Device Server

Smarts NCM 9.2 documentation states the following:

After the adapters' migration, you have to manually update the cm_device_server table
with the Device Server hostname for the adapters to appear in the synchronization options.

To update the cm_device_server table, run the following commands:

su - pgdba

psql voyencedb <NCM_database_password>

update cm_device_server set device_server_name='<Device Server

name>';

These instructions assume the environment only has one Smarts NCM Device server installed.

Resolution

Environments with more than one Smarts NCM Device Server will need to complete the following steps on the Database Server:

Run the following commands to login to the Smarts NCM database:

su - pgdba

psql voyencedb

<NCM_database_password>

Run the following command to update the cm_device_server table based on Device Server ID:

update cm_device_server set device_server_name='<Device server name>'where device_server_idx='<Device server idx>';

Test to ensure that the listing is correct by running the following query to view the table:

Select * from voyence.cm_device server;

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - NCM

Take Our Survey

Support Assistant