一、疑問，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的默認行為。