My Oracle Support Banner

gwm_start_catserv: Error 604 When Synchronizing Parameters in MMON trace file (Doc ID 2379072.1)

Last updated on MARCH 14, 2019

Applies to:

Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

Messages " gwm_start_catserv: error 604 when synchronizing parameters" are filling up the mmon trace file

Ex:
gwm_start_catserv: error 604 when synchronizing parameters
gwm_start_catserv: error 604 when synchronizing parameters

*** 2017-11-21 21:26:27.108
gwm_start_catserv: error 604 when synchronizing parameters

*** 2017-11-21 21:31:27.655
gwm_start_catserv: error 604 when synchronizing parameters
gwm_start_catserv: error 604 when synchronizing parameters

*** 2017-11-21 21:41:29.057
gwm_start_catserv: error 604 when synchronizing parameters


Changes

Recent upgrade and GDS packages are invalid.

You may use the query below to check if package DBMS_GSM_CLOUDADMIN shows invalid :

spool invalids.txt
SELECT version, modified, status FROM dba_registry WHERE comp_id = 'CATALOG';
SELECT version, modified, status FROM dba_registry WHERE comp_id = 'CATPROC';
col OBJECT_NAME for a30
select owner,object_name, object_type
from dba_objects
where status = 'INVALID' order by owner,object_name;
spool off;

 

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
Changes
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.