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

Oracle GoldenGate monitoring tool: ggserr. the log errors cannot be ignored. After the Oracle factory installed the monitoring plug-in for the OEM 12C in the primary database of the production environment recently, an exception occurred to the Oracle GoldenGate instance synchronized to more than a dozen external databases, frantically Go To The ggserr in the GoldenGate root directory. log input the following error log: www.2cto.com 2013-02-22 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.2013-02-22 22:33:26 WARNING OGG-01930 Oracle Gol DenGate Capture for Oracle, pzj_cx9.prm: Datastore error in 'dirbdb': BDB0060 PANIC: fatal region error detected; run recovery.2013-02-22 22:33:26 WARNING OGG-01930 Oracle GoldenGate Capture for Oracle, role: datastore error in 'dirbdb': BDB0060 PANIC: fatal region error detected; run recovery.2013-02-22 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.2013-02-22 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 real contact with GoldenGate, the 500G/goldengate VG was hit by 1-200G ggserr in less than a few days. log support is similar. This file finally began to enter my field of view. Www.2cto.com 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 Records of the GGSCI command stop and start the Oracle GoldGate process that has been executed errors some useful INFO and WARNING information due to ggserr. log error logs display events in the order of occurrence. Therefore, it is a good tool when locating the error cause. For example, you want to locate the problem: which time point does a process stop? A process cannot perform TCP/IP communication or establish a database connection. A process cannot open a file. There are many ways to view ggserr. log Error log: 1. Use the standard shell command to view ggserr in the Oracle GoldenGate root directory. log2. Use the Oracle GoldenGate ctor monitoring tool. 3. Run the view ggsevt command in GGSCI. The view ggsevt command syntax is: view ggsevt. Many times, ggserr. log errors are very large. If you use tail-f ggserr. log will feel how frequently its logs are played, just as I hit more than 200 GB in recent days, waiting for Oracle to solve the problem .... In fact, you can usually view ggserr. you can use shell commands to filter logs, such as displaying only the error message: more ggserr. log | grep ERROR as Oracle GoldenGate is used in a single day, the ERROR log will continue to grow. We need to regularly archive and back up and clean up the log, just like alert log in Oracle Database. GoldenGate ggserr. the log clearing method is as follows: cat/dev/null> ggserr. log or> ggserr. do not delete logs. Back up logs before cleaning. Note: After logs are cleared on Unix systems, the Collector process may stop reporting log information. To restart reporting log information, restart the Collector process (restart the mgr process) after cleaning ). Source http://blog.csdn.net/xiangsir/article/details/8640241