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

vRealize Orchestrator workflows begin running slowly overtime (56443)

Last Updated: 6/14/2019Categories: How toTotal Views: 3415Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

vRealize Orchestrator workflows that query the vmo_logevent table may run more slowly over time. All functions of the vRealize Orchestrator system seem to be functioning as normal, but workflow runs take longer and longer to complete.

Cause

By default, the originatoruri column on the vmo_logevent table is not indexed. Queries on the vmo_logevent table that are filtered by originatoruri will take longer as the vmo_logevent table grows.

Resolution

To resolve this issue, add an index on the originatoruri column for the vmo_logevent table to dramatically speed up these queries.

Ensure there is enough storage space on /storage/db partition

Run the command to see available disk space:

df -h /storage/db

 Query the current size of the vmo_logevent table. The new index will be smaller than the entire table.

SELECT pg_size_pretty(pg_relation_size('vmo_logevent'::regclass));

Log in to the VMware vRealize Automation virtual appliance using SSH.

Launch PostgreSQL CLI

cd /opt/vmware/vpostgres/current/bin

su postgres

psql vcac

Run the following query to create the index for originatoruri in the vmo_logevent table.

CREATE INDEX CONCURRENTLY IF NOT EXISTS idx_logeventoriginatoruri01 ON vmo_logevent (originatoruri);

Note: It is safe to create the index while vRealize Automation services are running, however it will take longer than if the services are stopped.

Inspect the vmo_logevent table to confirm the index has been created

\d vmo_logevent

Confirm the new idx_logeventoriginatoruri index appears in the "Indexes:" section of the output

\q

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
安装 vCenter Server 6.7 时，出现错误“‘PSC_FQDN’与 Platform Services Controller 证书中的主机名不匹配 ('PSC_FQDN' doesn't match with hostname in Platform Services Controller certificate)” (56812)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Aria Automation Orchestrator

Related Versions:

VMware vRealize Orchestrator 7.4.x

VMware vRealize Orchestrator 7.3.x

VMware vRealize Orchestrator 7.2.x

VMware vRealize Orchestrator 7.1.x

VMware vRealize Orchestrator 7.0.x

Take Our Survey

Support Assistant