一、疑问，OGG-集成模式-复制进程是否需要集成模式注册？

疑问：如标题所示？个人新增集成模式的复制进程操作步骤如下：

add replicat repcc01 ,integrated,exttrail ./dirdat/c1, NODBCHECKPOINT

dblogin useridalias ogguser
register replicat repcc01 database

start repcc01 

此时：有同事沟通说某项目操作都省略了register replicat repcc01 database，及集成复制注册操作？

那么是否可以省略？ 为啥集成模式的复制进程，不注册也OK呢？？？

二、参考MOS文档

Newly created OGG Integrated Replicat Process ABEND without error (Doc ID 2400351.1)    
Oracle GoldenGate - Version 12.1.2.0.0 and later
SYMPTOMS
This is an issue with integrated replicate.
Starting Replication process for the first time and the process abend with no errors in report file and db alert log.
Last couple lines in the replicate report file:
2018-05-10 11:14:02 INFO OGG-06604 Database "db-name" CPU info: CPU Count 4, CPU Core Count 4, CPU Socket Count 4.
2018-05-10 11:14:02 INFO OGG-02545 Parameter GROUPTRANSOPS is ignored by Integrated Replicat when parallelism is greater than 1.
2018-05-10 11:14:02 INFO OGG-02527 Integrated Replicat does not populate a trace table.
CAUSE
By default, there is no need to register replicate process for IR.  It would be registered automatically when you add integrated replicate.
When you start the IR, you should be able to see below message in the report file.
INFO OGG-02528 REPLICAT REPLCAT-NAME successfully registered with database as inbound server OGG$REPLCAT-NAME.

In this case, there is no error returned when you add IR.  But when you register it manually , it returns the below error:
register replicat REPLICAT-NAME database
2018-05-15 19:17:56 ERROR OGG-02508 Cannot register REPLICAT REPLICAT-NAME because of the following SQL error: OCI Error ORA
 (status = 60019-ORA-60019: Creating initial extent of size 14 in tablespace of extent size 8
ORA-06512: at "SYS.DBMS_XSTREAM_GG_ADM", line 345
ORA-06512: at line 1
). See Replicat user privileges in the Oracle GoldenGate for Oracle Installation and Setup Guide.
SOLUTION
If you are not seeing the entry of Integrated replicat name in the DB alert log or report file, you could manually register the replicat.
 The error might be different , but it will provide us some clue for the root cause.

In this case , the register was failed due to "ORA-60019: Creating initial extent of size 14 in tablespace of extent size 8"
Set db_securefile='PERMITTED' as stated in below document fixed the issue.
ORA-60019: Creating initial extent of size 14 in tablespace of extent size 8 while using CTAS (Doc ID 2180175.1)
NOTE: In the images and/or the document content above, the user information and data used represents fictitious data from
 the Oracle sample schema(s) or Public
Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead,
 is purely coincidental and not intended in any manner.


Customer RecommendedORA-60019: Creating initial extent of size 14 in tablespace of extent size 8 while using CTAS (Doc ID 2180175.1)    
Oracle Database - Enterprise Edition - Version 12.1.0.2 and later
CREATE TABLE  AS SELECT * FROM (CTAS) fails with ORA-60019: Creating initial extent of size 14 in tablespace of extent size 8. 
db_securefile is set to "PREFERRED"
SOLUTION
Setting the db_securefile='PERMITTED'  has solved the issue. This can be used as a workaround. 

小结： MOS这篇文档说了，当你使用集成模式添加了复制进程，启动之后会自动进行集成注册！ 但是需要注意的是如果日志中没有看到集成模式注册的信息就可能存在问题了！

这篇文档的情况是,集成复制进程abend，但是日志中并没有很详细的信息！ 当手工对复制进程注册时，会立即报错，提示无法在表空间中创建extent,这是特定的报错， 修改表空间相关的参数就可以了！！！

三、MOS文档涉及的参数

https://docs.oracle.com/en/database/oracle/oracle-database/19/refrn/DB_SECUREFILE.html#GUID-6F7C5E21-3929-4AB1-9C72-1BB9BDDB011F
DB_SECUREFILE = { NEVER | PERMITTED | PREFERRED | ALWAYS | IGNORE }


PERMITTED if the COMPATIBLE initialization parameter is set to 11.2.0.1, 11.2.0.2, or 11.2.0.3, or PREFERRED if the COMPATIBLE initialization parameter is set to 12.0.0.0 or higher


PERMITTED
允许将 LOB 创建为 SecureFiles。
PREFERRED
所有 LOB 都创建为 SecureFiles，除非BASICFILE在 LOB 存储子句中明确指定或表空间是手动段空间管理表空间。当PREFERRED被设置时，在那里的情况下BASICFILE否则会从该分区或列级LOB存储继承被忽略; LOB 将被创建为 SecureFiles。
如果COMPATIBLE初始化参数未设置为11.1.0或更高，则 LOB 不会被视为 SecureFiles。
如果一个 LOB 列有两个分区（一个具有启用了 ASSM 的表空间，另一个具有未启用 ASSM 的表空间），那么具有启用 ASSM 的表空间的分区中的 LOB 将被视为 SecureFiles另一个分区中的 LOB 将被视为 BasicFiles。
如果应用程序未通过 SecureFiles 认证，则DB_SECUREFILE可以将初始化参数的值设置PERMITTED为获取 Oracle 数据库 11 g的默认行为。