Oracle goldengate monitoring tool: ggserr. log error logs cannot be ignored

Oracle has recently installed the monitoring plug-in for OEM 12C in the primary database of the production environment.
An exception occurred to the Oracle goldengate instance. Enter the following error log in the ggserr. log directory of the goldengate root directory:

22:33:26 warning OGG-01930 Oracle goldengate capture for Oracle, pcqstqz1.prm: datastore error in 'dirbdb': bdb0060 panic: Fatal region error detected; run recovery.
22:33:26 warning OGG-01930 Oracle goldengate capture for Oracle, pzj_cx9.prm: datastore error in 'dirbdb': bdb0060 panic: Fatal region error detected; run recovery.
22:33:26 warning OGG-01930 Oracle goldengate capture for Oracle, pzj_cx9.prm: datastore error in 'dirbdb': bdb0060 panic: Fatal region error detected; run recovery.
22:33:26 warning OGG-01930 Oracle goldengate capture for Oracle, pzj_cx9.prm: datastore error in 'dirbdb': bdb0060 panic: Fatal region error detected; run recovery.
22:33:26 warning OGG-01930 Oracle goldengate capture for Oracle, pcqstqz1.prm: datastore error in 'dirbdb': bdb0060 panic: Fatal region error detected; run recovery.

For those of me who have been in touch with goldengate in the real sense, they are scared. The 500g/goldengate VG will be attacked in less than a few days.
1-200 GB ggserr. Log logs support almost. This file finally began to enter my field of view.

Ggserr. log is very important for goldengate monitoring, but we seldom pay attention to it. Oracle engineers will check this when they come.
You can use the Oracle goldengate error log to view many important information, such:
History of ggsci commands
Stop and start the Oracle goldgate Process
Processed information
Error
Some useful info and warning information

Because the ggserr. log error log displays events in the order of occurrence, it is a good choice when locating the cause of the error.
Tool. For example, you want to locate the problem:
Time point at which a process is stopped
A process cannot communicate with TCP/IP or establish a database connection.
A process cannot open a file

There are many ways to view the ggserr. log error log:
1. Use standard shell commands to view ggserr. log in the Oracle goldengate root directory
2. Use the Oracle goldengate ctor monitoring tool to view
3. View ggsevt in ggsci

The syntax of the view ggsevt command is view ggsevt.

Many times, the error log of ggserr. log is very large. If you use tail-F ggserr. log, you will feel
How frequently the logs are played, just as I hit more than 200 GB in recent days, waiting for Oracle to solve the problem ....
In fact, we can use shell commands to filter ggserr. Log logs. For example, only the error message is displayed:

More ggserr. log | grep Error

With the use of Oracle goldengate in a single day, error logs will continue to grow. We need to regularly archive and back up and clean up the logs,

Just like Alert Log in Oracle Database.

The following describes how to clean goldengate ggserr. log:

CAT/dev/null> ggserr. Log

Or

> Ggserr. Log

Do not delete the file. Make sure to back up the file before cleaning it.

Note: On Unix systems, After logs are cleared, the collector process may stop reporting log information. To start reporting log information again,

Restart the collector process after cleaning (restart the Mgr process ).

For reprint, please indicate the author's source and original article link:

Http://blog.csdn.net/xiangsir/article/details/8640241