I configured the Initial Load – Direct Load Method for migrating data from Source to Target (Oracle to Oracle database).
During this I encountered that Initial Load failed due to the below error. The Initial Load Extract Process got ABENDED.
2014-11-26 06:22:49 ERROR OGG-01203 Oracle GoldenGate Capture for Oracle, INITLD1.prm: EXTRACT abending.
2014-11-26 06:22:49 ERROR OGG-01668 Oracle GoldenGate Capture for Oracle, INITLD1.prm: PROCESS ABENDING.
As many of us do, I too google the error and searched for the solution. Many of them stated that the above error is due to some permission issue as below.,
But I had given all the required permissions to the gg user before starting the Initial Load. On analysing, the error can also be because of the space issue. The replicat could also not be able to insert the record to the table.
I traced the ggserr.log from the Target System and came to know that the tablespace was filled. As predicted REPLICAT process was not able to insert the changes or records to the target table.
Found the below error.,
SCHEMA.TAAS_PROJECT_TEAM by 5 in tablespace SCHEMA_TBS (status = 1653), SQL <INSERT INTO “SCHEMA”.”TAAS_PROJECT_TEAM” …………
On querying the database, it clearly showed that the space got exhausted in the tablespace SCHEMA_TBS.
TABLESPACE_NAME ALLOCATED USED FREE PERCTFREE CONTIGUOUS
—————————— ———— ———— ———— ———- ————
SCHEMA_TBS……………….. 5120.00 5120.00 .00 0 .00
After increasing the size of the tablespace SCHEMA_TBS by adding the datafile to it, I had restarted the Initial Load and it went fine.
TABLESPACE_NAME ALLOCATED USED FREE PERCTFREE CONTIGUOUS
—————————— ———- ———- ———- ———- ———-
SCHEMA_TBS……………….. 35840.00 5120.47 30719.53 85.71 10080.00
SUMMARY:
- Whenever an EXTRACT process or a REPLICAT process ABENDS, one need to always check the error on both the sides Source and Target and not on the respective systems.
- Check if all the corresponding tablespaces has free space before starting the Initial Load.