ORA-01003: nostatementparsed.

A table is intentionally deleted. When OGG synchronizes data, an error is immediately reported after the table is deleted, as follows:

OCI Error ORA-12096: error in materialized view log on "JTINFO ". "TBL_USERID" ORA-01003: no statement parsed (status = 12096), SQL <INSERT/* + APPEND */INTO "JTINFO ". "TBL_USERID" ("USID_UID", "USID_IMEI", "USID_IMSI", "USID_FLAG", "USID_ACTIVE") VALUES (: a0,: a1,: a2,: a3 ,: a4)> Operation failed at seqno 39169 rba 1751092 Discarding record on action DISCARD on error 12096 Problem replicating JTINFO. TBL_USERID to JTINFO. TBL_USERIDMapping problem with insert record (target format )... * USID_UID = 8087585903USID_IMEI = bytes = 000000000000000USID_FLAG = 0USID_ACTIVE = 1 * Current time: 02:32:45 thanks to the previous logical backup, speed

Create table mlog $ _ TBL_USERID
AS
SELECT * from mlog $ _ TBL_USERID_BAK;

Then the error exception is still...

With the help of the wisdom of the Internet, although online articles did not tell you how to solve the problem, I instantly understood it.

Prepare to restart the replicat process of OGG ..

After the restart, check the OGG's Err Log, terminate the exception, and solve the problem.

The key point is that when I used this table in the application, I dropped the table. As to why this error was reported, I had to sleep and check it later.

Pay attention to your health when you are busy at work.