My Oracle Support Banner

Post Mammoth Expansion OSWatcher Is Not Runing on the Newly Expanded Nodes (Doc ID 2505438.1)

Last updated on JANUARY 08, 2020

Applies to:

Big Data Appliance Integrated Software - Version 4.5.0 and later
Linux x86-64

Symptoms

NOTE: In the examples that follow, user details, table name, company name, email, hostnames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner.

Post Mammoth expansion, OSWatcher is not running on the newly expanded nodes.

The example here is based on a BDA V4.5 expansion.

The symptoms are:
1. On the original cluster hosts the OSWatcher directory is present:

/opt/oracle.ExaWatcher/archive

The directory is not present on the hosts expanded into the cluster.

2. On the original cluster hosts collecting the OSWatcher output as below captures OSWatcher data.

But the rpm does not exist on the hosts expanded into the cluster.

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.