Database - RAC/Scalability (MOSC)

MOSC Banner

tfa inventory FAILED-INTERRUPTED

edited Sep 11, 2015 10:01AM in Database - RAC/Scalability (MOSC) 1 commentAnswered

Hi All,

I have recently implemented TFA across all nodes in our Exadata env.

All was OK until I start to generate reports using "diagcollect" option.

During diagcollect, "Failed Exception" was report on one of the nodes, investigating further I noticed it was a Java Heap Out-Of-Memory error.

Therefore I restart the TFA process on two of the nodes.

Now when I check status I see below:

.-------------------------------------------------------------------------------------------------------.

| Host         | Status of TFA | PID    | Port | Version    | Build ID             | Inventory Status   |

+--------------+---------------+--------+------+------------+----------------------+--------------------+

| gbdocex1db01 | RUNNING       |  71176 | 5000 | 12.1.2.5.2 | 12125220150811045228 | COMPLETE           |

| gbdocex1db02 | RUNNING       | 116841 | 5000 | 12.1.2.5.2 | 12125220150811045228 | FAILED-INTERRUPTED |

| gbdocex1db03 | RUNNING       | 108083 | 5000 | 12.1.2.5.2 | 12125220150811045228 | RUNNING            |

| gbdocex1db04 | RUNNING       | 124376 | 5000 | 12.1.2.5.2 | 12125220150811045228 | FAILED-INTERRUPTED |

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center