The following warning is often found during Ogg log inspection:
16:52:56 warning OGG-00952 Oracle goldengate manager for Oracle, Mgr. PRM: purging log history from Ogg. ggs_ddl_hist older than 15:52:56. 084114: cocould not delete rows from Ogg. ggs_ddl_hist, no database specified.
16:52:56 warning OGG-00952 Oracle goldengate manager for Oracle, Mgr. PRM: purging log history from Ogg. ggs_ddl_hist_alt older than 2013-01-13 15:52:56. 084261: cocould not delete rows from Ogg. ggs_ddl_hist_alt, no database specified.
16:52:56 warning OGG-00952 Oracle goldengate manager for Oracle, Mgr. PRM: purging log history from Ogg. ggs_marker older than 15:52:56. 084448: cocould not delete rows from Ogg. ggs_marker, no database specified.
At first, we did not pay much attention to it. Later we found that the table space usage of Ogg gradually increased. I thought it had something to do with it, so I checked the information online. Indeed
The cause of this warning is that Ogg needs to enter the database to perform this operation, so we need to add the following parameters to the Manager:
Userid Ogg, password dfasdfasfasdadfad, encryptkey default
The manager does not need to restart the process to modify the parameters. It only needs to refresh the process:
Refresh Manager
The above warning was not found in the Ogg ggserr. log monitoring again.
Warning OGG-00952 purging log history from Ogg. ggs_ddl_hist