使用goldengate error log查看错误信息

我们可以使用oracle goldengate error log去查看：

● GGSCI的历史命令
● oracle goldengate进程的启动和停止
● 执行的过程
● 发生的错误
● 信息和提醒条目

因为the error log显示了序列里发生的事件，所以这是一个好的工具去探测错误发生的原因。例如，你可能会发现：

● 某些人停止了进程
● TCP/IP或是数据库连接的错误
● 进程打不开文件

Figure 3 oracle goldengate错误日志（ggserr.log file）

2011-01-08 11:20:56 GGS INFO 301 GoldenGate Manager for Oracle, 
mgr.prm: Command received from GUI (START GGSCI ).
2011-01-08 11:20:56 GGS INFO 302 GoldenGate Manager for Oracle, 
mgr.prm: Manager started GGSCI process on port 7840.
2011-01-08 11:21:31 GGS INFO 301 GoldenGate Manager for Oracle, 
mgr.prm: Command received from GUI (START GGSCI ).
2011-01-08 11:21:31 GGS INFO 302 GoldenGate Manager for Oracle, 
mgr.prm: Manager started GGSCI process on port 7841.
2011-01-08 11:24:15 GGS INFO 301 GoldenGate Manager for Oracle, 
mgr.prm: Command received from GUI (START GGSCI ).
2011-01-08 11:24:15 GGS INFO 302 GoldenGate Manager for Oracle, 
mgr.prm: Manager started GGSCI process on port 7842.
2011-01-08 11:24:16 GGS INFO 399 GoldenGate Command Interpreter for 
Oracle: GGSCI command (ggs): add extract extcust tranlog, begin now.
2011-01-08 11:30:19 GGS INFO 399 GoldenGate Command Interpreter for 
Oracle: GGSCI command (ggs): add rmttrail /home/ggs, extract ggs

查看错误日志

使用下列任何一种方式:

● 在ogg的根目录下使用标准的shell命令的方式去查看ggserr.log文件
● oracle goldengate的助理
● GGSCI下的VIEW GGSEVT命令

语法 VIEW GGSEVT

       过滤错误日志
错误日志会变得比较大，但是能够对期进行过滤，例如，仅过滤含有error的日志：

在OGG目录下执行
$ more ggserr.log | grep ERROR
因为the error log会一直随着你使用OGG而增加，因此必须考虑归档和删除文件中
老旧的条目

注意：在UNIX系统中，日志被清理后，collector进程会停止记录日志到ggserr.log文件中，因此在清理过日志之后必须重启一下collector进程

-------------以下为官方文档参考--------------------------------------------------

Using the error log
Use the Oracle GoldenGate error log to view:
● a history of GGSCI commands
● Oracle GoldenGate processes that started and stopped
● processing that was performed
● errors that occurred
● informational and warning messages
Because the error log shows events as they occurred in sequence, it is a good tool for 
detecting the cause (or causes) of an error. For example, you might discover that:
● someone stopped a process
● a process failed to make a TCP/IP or database connection
● a process could not open a file
Figure 3 The Oracle GoldenGate Error Log (ggserr.log file)
2011-01-08 11:20:56 GGS INFO 301 GoldenGate Manager for Oracle, 
mgr.prm: Command received from GUI (START GGSCI ).
2011-01-08 11:20:56 GGS INFO 302 GoldenGate Manager for Oracle, 
mgr.prm: Manager started GGSCI process on port 7840.
2011-01-08 11:21:31 GGS INFO 301 GoldenGate Manager for Oracle, 
mgr.prm: Command received from GUI (START GGSCI ).
2011-01-08 11:21:31 GGS INFO 302 GoldenGate Manager for Oracle, 
mgr.prm: Manager started GGSCI process on port 7841.
2011-01-08 11:24:15 GGS INFO 301 GoldenGate Manager for Oracle, 
mgr.prm: Command received from GUI (START GGSCI ).
2011-01-08 11:24:15 GGS INFO 302 GoldenGate Manager for Oracle, 
mgr.prm: Manager started GGSCI process on port 7842.
2011-01-08 11:24:16 GGS INFO 399 GoldenGate Command Interpreter for 
Oracle: GGSCI command (ggs): add extract extcust tranlog, begin now.
2011-01-08 11:30:19 GGS INFO 399 GoldenGate Command Interpreter for 
Oracle: GGSCI command (ggs): add rmttrail /home/ggs, extract ggs
To view the error log
Use any of the following:
● Standard shell command to view the ggserr.log file within the root Oracle GoldenGate 
directory
● Oracle GoldenGate Director
● VIEW GGSEVT command in GGSCI
Syntax VIEW GGSEVT
To filter the error log
The error log can become very large, but you can filter it based on a keyword. For example, 
this filter show only errors:
$ more ggserr.log | grep ERROR
Because the error log will continue to grow as you use Oracle GoldenGate, consider 
archiving and deleting the oldest entries in the file.
NOTE The Collector process might stop reporting to the log on UNIX systems after the log 
has been cleaned up. To get reporting started again, restart the Collector process 
after the cleanup.

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/29802484/viewspace-1384591/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/29802484/viewspace-1384591/