OGG "Loading data from file to Replicat"table静态数据同步配置过程

OGG "Loading data from file to Replicat"table静态数据同步配置过程

大家好,又见面了,我是全栈君,今天给大家准备了Idea注册码。

OGG “Loading data from file to Replicat”table静态数据同步配置过程

一个、mgr过程

GGSCI (lei1) 3> view params mgr

port 7809

 

二、抽取进程extftor

GGSCI (lei1) 4> view params extftor

SOURCEISTABLE

userid goldengate, password yyyyy
rmthost 192.168.100.189, mgrport 7809


RMTFILE /u02/ggs/dirdat/pp, MAXFILES 1000, MEGABYTES 100

table test.xxx;

 

三、复制进程repftor

GGSCI (lei1) 5> view params repftor


SPECIALRUN
END RUNTIME
userid goldengate, password yyyy
exttrail /u02/ggs/dirdat/pp
ASSUMETARGETDEFS

map test.xxx target testhvr.xxxx;

请注意:

上面的參数是exttrail(不是extfile),exttrail參数是与抽取进程的MAXFILES和MEGABYTES配合使用的,通俗的说,exttrail是相应的/u02/ggs/dirdat/pp000000。/u02/ggs/dirdat/pp000001,/u02/ggs/dirdat/pp000002。/u02/ggs/dirdat/pp000003等等。

而extfile 參数,相应的是/u02/ggs/dirdat/pp

 

四、从操作系统命令行发起extract(注意:此种extract,ggsci的info all是看不到的)

[oracle@lei1 ggs]$ cd /u02/ggs
[oracle@lei1 ggs]$ pwd
/u02/ggs
[oracle@lei1 ggs]$ extract paramfile /u02/ggs/dirprm/extftor.prm reportfile /u02/ggs/dirrpt/EXTFTOR.rpt
---->请务必确保发起上面extract的securecrt不中断!

建议在vncserver或者以nohup方式运行此extract。

nohup方式运行请參考:http://blog.csdn.net/msdnchina/article/details/46333375

 

此时,extract会在/u02/ggs/dirdat/下例如以下的文件:

[oracle@lei1 dirdat]$ pwd
/u02/ggs/dirdat
[oracle@lei1 dirdat]$ ls -lrt pp* | wc -l
424
[oracle@lei1 dirdat]$ 

等待extract完毕(能够从/u02/ggs/dirrpt/EXTFTOR.rpt中推断):

---------------------------------------以上省略------------------------------------------- 
2015-06-02 01:35:10  INFO    OGG-01026  Rolling over remote file /u02/ggs/dirdat/pp000422.

2015-06-02 01:35:22  INFO    OGG-01026  Rolling over remote file /u02/ggs/dirdat/pp000423.

***********************************************************************
*                   ** Run Time Statistics **                         *
***********************************************************************


Report at 2015-06-02 01:35:32 (activity since 2015-06-02 00:02:59)

Output to /u02/ggs/dirdat/pp:

From Table TEST.XXXX:
       #                   inserts:      3005    --------->抽取了3005条记录
       #                   updates:         0
       #                   deletes:         0
       #                  discards:         0


REDO Log Statistics
  Bytes parsed                    0
  Bytes output          43269697047
--->此处是该rpt文件的终点。

                                                 
五、从操作系统命令行发起repftor(注意:此种repftor,ggsci的info all是看不到的)

[oracle@lei1 ggs]$ cd /u02/ggs
[oracle@lei1 ggs]$ pwd
/u02/ggs
[oracle@lei1 ggs]$replicat paramfile /u02/ggs/dirprm/repftor.prm reportfile /u02/ggs/dirrpt/REPFTOR.rpt
---->请务必确保发起上面replicat的securecrt不中断!建议在vncserver或者以nohup方式运行此replicat。
nohup方式运行请參考:http://blog.csdn.net/msdnchina/article/details/46333375

等待replicat完毕(能够从/u02/ggs/dirrpt/REPFTOR.rpt中推断):

---------------------------------------以上省略------------------------------------------- 
Switching to next trail file /u02/ggs/dirdat/pp000422 at 2015-06-02 04:48:11 due to EOF, with current RBA 98987715
Opened trail file /u02/ggs/dirdat/pp000422 at 2015-06-02 04:48:11


Switching to next trail file /u02/ggs/dirdat/pp000423 at 2015-06-02 04:48:39 due to EOF, with current RBA 97717950
Opened trail file /u02/ggs/dirdat/pp000423 at 2015-06-02 04:48:39


***********************************************************************
*                   ** Run Time Statistics **                         *
***********************************************************************

Last record for the last committed transaction is the following: 
___________________________________________________________________
Trail name :  /u02/ggs/dirdat/pp000423
Hdr-Ind    :     E  (x45)     Partition  :     .  (x04) 
UndoFlag   :     .  (x00)     BeforeAfter:     A  (x41) 
RecLength  :    83 (x0053)    IO Time    : 2015-06-02 00:03:04.183247  
IOType     :     5  (x05)     OrigNode   :   255  (xff)
TransInd   :     .  (x03)     FormatType :     R  (x52)
SyskeyLen  :     0  (x00)     Incomplete :     .  (x00)
AuditRBA   :          0       AuditPos   : 0
Continued  :     Y  (x01)     RecCount   :     1  (x01)

2015-06-02 00:03:04.183247 Insert             Len    83 RBA 82048951
Name: TEST.XXXX
___________________________________________________________________

Reading /u02/ggs/dirdat/pp000423, current RBA 96448185, 3005 records

Report at 2015-06-02 04:48:52 (activity since 2015-06-02 03:03:36)

From Table TEST.XXXX to TESTHVR.XXXX:
       #                   inserts:      3005 --------->插入了3005条记录
       #                   updates:         0
       #                   deletes:         0
       #                  discards:         0


Last log location read:
     FILE:      /u02/ggs/dirdat/pp000423
     SEQNO:     423
     RBA:       96448185
     TIMESTAMP: 2015-06-02 00:03:04.183247
     EOF:       NO
     READERR:   400


CACHE OBJECT MANAGER statistics

CACHE MANAGER VM USAGE
vm current     =  23.82M   vm anon queues =  23.82M
vm anon in use =      0    vm file        =      0 
vm used max    =  23.82M   ==> CACHE BALANCED

CACHE CONFIGURATION
cache size       = 512M   cache force paging = 881M
buffer min       =  64K   buffer highwater   =   4M
pageout eligible size =   4M

================================================================================
RUNTIME STATS FOR SUPERPOOL

CACHE Transaction Stats
trans active   =      0    max concurrent =      3 
non-zero total =   8.81K   trans total    =   8.81K

CACHE File Caching
disk current   =      0    disk total  =      0 
disk caching   =      0    file cached =      0 
file retrieves =      0 

CACHE MANAGEMENT
buffer links  =  52.83K  anon gets   =      0 
forced unmaps =      0   cnnbl try   =      0 
cached out    =      0   force out   =      0 

Allocation Request Distribution
< 128B:       0 
 128B:        0         0     | 512B:     2.94K     5.87K
   2K:    19.79M        0     |   8K:        0         0 
  32K:        0         0     | 128K:        0         0 
 512K:        0         0     |   2M:        0         0 
   8M:        0         0     |  32M:        0         0 
 128M:        0         0     | 512M:        0         0 
   2G:        0         0     |   8G:        0 

Cached Transaction Size Distribution
    0:        0 
 < 4K:        0 
   4K:        0         0     |  16K:        0         0 
  64K:        0         0     | 256K:        0         0 
   1M:        0         0     |   4M:     8.81K        0 
  16M:        0         0     |  64M:        0         0 
 256M:        0         0     |   1G:        0         0 
   4G:        0         0     |  16G:        0         0 
  64G:        0         0     | 256G:        0         0 
   1T:        0         0     |   4T:        0         0 
  16T:        0         0     |  64T:        0         0 
 256T:        0         0     |1024T:        0         0 

================================================================================
CUMULATIVE STATS FOR SUPERPOOL

CACHE Transaction Stats
trans active   =      0    max concurrent =      0 
non-zero total =      0    trans total    =      0 

CACHE File Caching
disk current   =      0    disk total  =      0 
disk caching   =      0    file cached =      0 
file retrieves =      0 

CACHE MANAGEMENT
buffer links  =      0   anon gets   =      0 
forced unmaps =      0   cnnbl try   =      0 
cached out    =      0   force out   =      0 

Allocation Request Distribution
< 128B:       0 
 128B:        0         0     | 512B:        0         0 
   2K:        0         0     |   8K:        0         0 
  32K:        0         0     | 128K:        0         0 
 512K:        0         0     |   2M:        0         0 
   8M:        0         0     |  32M:        0         0 
 128M:        0         0     | 512M:        0         0 
   2G:        0         0     |   8G:        0 

Cached Transaction Size Distribution
    0:        0 
 < 4K:        0 
   4K:        0         0     |  16K:        0         0 
  64K:        0         0     | 256K:        0         0 
   1M:        0         0     |   4M:        0         0 
  16M:        0         0     |  64M:        0         0 
 256M:        0         0     |   1G:        0         0 
   4G:        0         0     |  16G:        0         0 
  64G:        0         0     | 256G:        0         0 
   1T:        0         0     |   4T:        0         0 
  16T:        0         0     |  64T:        0         0 
 256T:        0         0     |1024T:        0         0 


QUEUE Statistics:
num queues    =     15     default index =      0 
cur len       =      0     max len       =      0 
q vm current  =      0     vm max        =      0 
q hits        =  61.61K    q misses      =     21 

queue size  q hits  curlen  maxlen     cannibalized
  0   64K   8.81K      3       3       0 
  1  128K   8.81K      3       3       0 
  2  256K   8.81K      3       3       0 
  3  512K   8.81K      3       3       0 
  4    1M   8.81K      3       3       0 
  5    2M   8.81K      3       3       0 
  6    4M   8.81K      3       3       0 
  7    8M      0       0       0       0 
  8   16M      0       0       0       0 
  9   32M      0       0       0       0 
 10   64M      0       0       0       0 
 11  128M      0       0       0       0 
 12  256M      0       0       0       0 
 13  512M      0       0       0       0 
 14    1G      0       0       0       0 

================================================================================
RUNTIME STATS FOR CACHE POOL #0
POOL INFO   group: repftor  id: p22586_BLOB
trans active  =       0   trans concurrent (max) =     3 
trans total   =    8.81K  (9015 )
flag          = 0x00000030
last error    = (0=<none>)

Allocation Request Distribution
< 128B:       0 
 128B:        0         0     | 512B:     2.94K     5.87K
   2K:    19.79M        0     |   8K:        0         0 
  32K:        0         0     | 128K:        0         0 
 512K:        0         0     |   2M:        0         0 
   8M:        0         0     |  32M:        0         0 
 128M:        0         0     | 512M:        0         0 
   2G:        0         0     |   8G:        0 

================================================================================
CUMULATIVE STATS FOR CACHE POOL #0
POOL INFO   group: repftor  id: p22586_BLOB
trans active  =       0   trans concurrent (max) =     0 
trans total   =       0   (0 )
flag          = 0x00000030
last error    = (0=<none>)

Allocation Request Distribution
< 128B:       0 
 128B:        0         0     | 512B:        0         0 
   2K:        0         0     |   8K:        0         0 
  32K:        0         0     | 128K:        0         0 
 512K:        0         0     |   2M:        0         0 
   8M:        0         0     |  32M:        0         0 
 128M:        0         0     | 512M:        0         0 
   2G:        0         0     |   8G:        0 


QUEUE Statistics:
num queues    =     15     default index =      0 
cur len       =      0     max len       =      0 
q vm current  =      0     vm max        =      0 
q hits        =  61.61K    q misses      =     21 

queue size  q hits  curlen  maxlen     cannibalized
  0   64K   8.81K      3       3       0 
  1  128K   8.81K      3       3       0 
  2  256K   8.81K      3       3       0 
  3  512K   8.81K      3       3       0 
  4    1M   8.81K      3       3       0 
  5    2M   8.81K      3       3       0 
  6    4M   8.81K      3       3       0 
  7    8M      0       0       0       0 
  8   16M      0       0       0       0 
  9   32M      0       0       0       0 
 10   64M      0       0       0       0 
 11  128M      0       0       0       0 
 12  256M      0       0       0       0 
 13  512M      0       0       0       0 
 14    1G      0       0       0       0 

================================================================================
RUNTIME STATS FOR CACHE POOL #0
POOL INFO   group: repftor  id: p22586_BLOB
trans active  =       0   trans concurrent (max) =     3 
trans total   =    8.81K  (9015 )
flag          = 0x00000030
last error    = (0=<none>)

Allocation Request Distribution
< 128B:       0 
 128B:        0         0     | 512B:     2.94K     5.87K
   2K:    19.79M        0     |   8K:        0         0 
  32K:        0         0     | 128K:        0         0 
 512K:        0         0     |   2M:        0         0 
   8M:        0         0     |  32M:        0         0 
 128M:        0         0     | 512M:        0         0 
   2G:        0         0     |   8G:        0 

================================================================================
CUMULATIVE STATS FOR CACHE POOL #0
POOL INFO   group: repftor  id: p22586_BLOB
trans active  =       0   trans concurrent (max) =     0 
trans total   =       0   (0 )
flag          = 0x00000030
last error    = (0=<none>)

Allocation Request Distribution
< 128B:       0 
 128B:        0         0     | 512B:        0         0 
   2K:        0         0     |   8K:        0         0 
  32K:        0         0     | 128K:        0         0 
 512K:        0         0     |   2M:        0         0 
   8M:        0         0     |  32M:        0         0 
 128M:        0         0     | 512M:        0         0 
   2G:        0         0     |   8G:        0 
--->此处是该rpt文件结尾。

 

版权声明:本文博客原创文章,博客,未经同意,不得转载。

版权声明:本文内容由互联网用户自发贡献,该文观点仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 举报,一经查实,本站将立刻删除。

发布者:全栈程序员-用户IM,转载请注明出处:https://javaforall.cn/117299.html原文链接:https://javaforall.cn

【正版授权,激活自己账号】: Jetbrains全家桶Ide使用,1年售后保障,每天仅需1毛

【官方授权 正版激活】: 官方授权 正版激活 支持Jetbrains家族下所有IDE 使用个人JB账号...

(0)


相关推荐

  • pycharm快速删除一行快捷键:ctrl+x(剪切掉)「建议收藏」

    pycharm快速删除一行快捷键:ctrl+x(剪切掉)「建议收藏」pycharm快速删除一行快捷键:ctrl+x(剪切掉)

  • GSLB相关概念

    GSLB相关概念域组:当网站使用CDN提供服务并用DNS解析原理构建GSLB时,通常会由权威DNS设置一个CDN对源站提供服务的域名作为源站域名的别名(CNAME).这个别名被称为"域组",GSLB可以将它映射成一个由多个虚拟服务器(VirutalServer)组成的服务池(Pool),这些虚拟服务器就是用户输入网站URL后经负载均衡调度直接提供服务的服务器.GSLB在解析域名的时候会直接返回其中一个虚拟服务器…

  • Java事务管理[通俗易懂]

    Java事务管理[通俗易懂]事务的ACID属性:原子性(Atomicity)、一致性(Consistency)、隔离性或独立性(Isolation)和持久性(Durabilily)一、Java事务管理Java事务管理有三种类型:JDBC事务、JTA(JavaTransactionAPI)事务、容器事务1.1JDBC事务JDBC的一切行为包括事务是基于一个Connection的,JDBC通过Connec…

  • REST API和SOAP API区别[通俗易懂]

    REST API和SOAP API区别[通俗易懂]RESTAPI优点:1.轻量级的解决方案,不必向SOAP那样要构建一个标准的SOAPXML。2.可读性比较好:可以把URL的名字取得有实际意义。3.不需要SDK支持:直接一个Http请求就可以,但是SOAP则可能需要使用到一些Webservice的类库(例如Apache的Axis)缺点:1.复杂的应用中,URL可能非常长,而且不容易解析。SOAPAPI优点:1.定…

  • 机器学习 —— 浅谈贝叶斯和MCMC

    机器学习 —— 浅谈贝叶斯和MCMC‍‍Abstract:最近课业内的任务不是很多,又临近暑假了,就在网上搜了一些有关于机器学习和深度学习的课程进行学习。网上的资料非常繁多,很难甄别,我也是货比三家进行学习…

  • Java日志管理

    Java日志管理

发表回复

您的电子邮箱地址不会被公开。

关注全栈程序员社区公众号