Exadata: Database Instance Terminated Due To ORA-29770 (Doc ID 2611552.1)

Last updated on APRIL 17, 2023

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 and later
Information in this document applies to any platform.

Symptoms

In Exadata environment, 12.1 Database instance terminated due to ORA-29770

alert_DBNAME1.log

Wed Oct 16 08:11:15 2019
TT00: Standby redo logfile selected for thread 1 sequence 88568 for destination LOG_ARCHIVE_DEST_2
Wed Oct 16 08:11:21 2019
Archived Log entry 30052 added for thread 1 sequence 88567 ID 0xe916827a dest 1:
Wed Oct 16 08:15:52 2019
Auto-tuning: Shutting down background process GTX1
Wed Oct 16 08:15:55 2019
LMS2 (ospid: 187206) has not called a wait for sub 0 secs.
Errors in file /u01/app/oracle/admin/PGCMIP1B/diag/rdbms/dbname/dbname1/trace/dbname1_lmhb_187212.trc (incident=837014):
ORA-29770: global enqueue process LMS2 (OSID 187206) is hung for more than 70 seconds
Incident details in: /u01/app/oracle/admin/PGCMIP1B/diag/rdbms/dbname/dbname1/incident/incdir_837014/dbname1_lmhb_187212_i837014.trc
LOCK_DBGRP: GCR_SYSTEST debug event locked group GR+DB_DBNAME by memno 1

Changes

NONE

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

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

Exadata: Database Instance Terminated Due To ORA-29770 (Doc ID 2611552.1)

Applies to:

Symptoms

Changes

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!