Learning by Doing

I ran into some issue with goldengate where it's not taking any of the update statement, they are all sent directly to ignore when we ran view param we see this statement, basically this is handling all the issue with update and send update statement to ignore count when the process thinks it cannot handle the update statement. REPERROR (1403, IGNORE) I then commented that line and restarted the replicat process. Upon starting the process, I encountered the following 2019-08-01 12:33:45  WARNING OGG-01004  Aborted grouped transaction on AVL_RPT_FOD.ALERT_MTS_SALT, Database error 1403 (OCI Error ORA-01403: no data found, SQL <UPDATE "AVL_RPT_FOD"."ALERT_MTS_SALT" x SET x."STATUS_ID" = :a9,x."FACILITY_TYPE_ID" = :a10,x."START_DATE" = :a11,x."END_DATE" = :a12,x."WEB_MERCATOR_X" = :a13,x."WEB_MERCATOR_Y" = :a14,x."FACILITY_NAME" = :a15 WHERE x."ID" = :b0>). 2019-08-01 12...

This is just a quick note of what can stop mongosqld from working properly that I wasn't aware of. Background: My work runs everything mongodb inside of docker containers, so sometimes it's not as straight forward to see immediately of what's preventing your container from working properly What happened: I ran into issue that my container does not stay up after I updated my drdl to reflect new fields introduced to the underlying collection. How to debug: Go to the host server, copy out entrypoint.sh and add sleep 100000000 to before mongosqld is executed. This force the container to stay up for us to look into issue. Cause of the issue: When I updated the drdl, I used tab instead of space, which is causing the mongsqld to error out Fix: Just replace tab with space and everything is back to normal