Blog

oracle.sysman.gcagent.task.TaskTimeoutException: task timeout: 120000 MILLISECONDS for oracle_database: ORCL:Response

There following alert has been received with timeout error message “…oracle.sysman.gcagent.task.TaskTimeoutException: task timeout: 120000 MILLISECONDS…” 

 Host=oemnode1 
 Target type=Database Instance 
 Target name=OEMPROD
 Incident creation time=13/11/2020 10:09:39 PM AEDT 
 Last updated time=13/11/2020 10:09:39 PM AEDT 
 Message=Metric evaluation error start - oracle.sysman.emSDK.agent.fetchlet.exception.FetchletException: Timeout during collection: oracle.sysman.gcagent.task.TaskTimeoutException: task timeout: 120000 MILLISECONDS for oracle_database:OEMPROD:Response 
 Severity=Critical 
 Incident ID=463520 
 Event count=1 
 Incident Status=New 
 Escalated=No 
 Priority=High 
 Incident owner=SYSMAN
 Incident Acknowledged By Owner=No 
 Categories=Availability 
 ...
..
.

Subscribe to get access

Read more of this content when you subscribe today.

Subscribe

ORA-10561: block type ‘TRANSACTION MANAGED DATA BLOCK’

The standby database alert log has the following errors:

Tue Nov 17 11:43:51 2020
 Errors in file /u01/app/oracle/diag/rdbms/stbytestdb/STBYTESTDB/trace/STBYTESTDB_mrp0_7269.trc:
 ORA-00600: internal error code, arguments: [3020], [3], [115047], [115047], [], [], [], [], [], [], [], []
 ORA-10567: Redo is inconsistent with data block (file# 3, block# 115047, file offset is 942465024 bytes)
 ORA-10564: tablespace SYSAUX
 ORA-01110: data file 3: '/u02/oradata/STBYTESTDB/sysaux01.dbf'
 ORA-10561: block type 'TRANSACTION MANAGED DATA BLOCK', data object# 8316
 Tue Nov 17 11:43:51 2020
 MRP0: Background Media Recovery process shutdown (STBYTESTDB)

SOLUTION

Subscribe to get access

Read more of this content when you subscribe today.

Subscribe

How to Speed Up Index Creation in AWS PostgreSQL RDS

I was asked by a client about how to speed up index creation in a terabytes AWS PostgreSQL database. This post tries to explain all the details, and give some examples in real situation.

Subscribe to get access

Read more of this content when you subscribe today.

Subscribe

SSMA : Violation of PRIMARY KEY constraint

While running SSMA migrates Oracle database to Microsoft SQL Server, the constraint violation errors occurred for some tables as below:

Violation of PRIMARY KEY constraint ‘TABLENAME_PK’. Cannot insert duplicate key in object ‘USER.TABLE’. The duplicate key value is (John).

Subscribe to get access

Read more of this content when you subscribe today.

Subscribe

How to Migrate On-Premise Oracle Database onto AWS RDS Microsoft SQL Server

Introduction

This article will demonstrate step by step how to migrate on-premise Oracle database onto AWS RDS SQL Server, the issues encountered plus their solutions and workarounds during the migration.

The following environment and tools will be involved in this activity:

  • Oracle Database 19c
  • SQL Server 2019
  • AWS RDS SQL Server 2019
  • Oracle Client 19c
  • AWS Database Migration Service ( DMS) or AWS S3
  • SQL Server Management Studio ( SSMS )
  • Microsoft SQL Server Migration Assistant (SSMA) for Oracle

There is no direct migration on-premise Oracle database onto AWS SQL Server RDS, so the the high level migration procedure will be:

  1. Migrate on-premise Oracle database by using SSMA to on-premise SQL Server database.
  2. Migrate on-premise SQL Server database onto AWS RDS SQL Server.

Subscribe to get access

Read more of this content when you subscribe today.

Subscribe