Exalogic Virtual: How To Truncate Tables In EMOC Database For TableSpace Related Issues In EMOC
(Doc ID 2421249.1)
Last updated on JULY 25, 2018
Applies to:Oracle Exalogic Elastic Cloud Software - Version 220.127.116.11.170418 and later
Oracle Virtual Server x86-64
In Exalogic Virtual racks, you can run into issues of EMOC database running out of the table space. When that happens you may see following issues:
- EMOC Jobs hanging or getting terminated with "Flow not run yet" message in Job logs.
- All EMOC related jobs (like create/stop/start/delete of vservers, asset discovery/deletion, network creation/deletion, account, credentials or resource updates etc.) failing with below "unable to extend table" ORA errors in EMOC and Proxy Controller cacao logs.
This MOS Note provides detailed steps for identifying the tables which occupy most space in EMOC database (causing tablespace issues) and procedure for truncating those tables to clear the space in EMOC database.
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
|1. TAKE BACKUP OF THE CONTROL STACK USING EXABR ★★★★ VERY IMPORTANT ★★★★|
|2. IDENTIFYING TABLES WHICH ARE HUGE IN SIZE IN EMOC DATABASE ON EMOC CONTROL VSERVER|
|3. DELETING/TRUNCATING USER TABLE SPACE IN EMOC DB ON EMOC VM|