OGG-08221 Cannot register or unregister EXTRACT

Have you read last ‘Failure unregister integrated extract’ and still impossible to unregister Integrated Extract on Oracle Database?

Is it’s ‘Impossible mission’ to unregister extract?
dba

It’s is throwing OGG-08221  in ggserr.log when unregister Extract?

GGSCI (dbcloud as ggate@etldb) 40> unregister extract ETL01  database

2017-04-28 11:56:29 ERROR OGG-08221 Cannot register or unregister EXTRACT ETL01 because of the following SQL error: OCI Error retrieving bind info for query (status = 100).

CAUSE

Sometimes when a server crash, rebooted, OGG or database is not shutdown cleanly, the Integrated Extract is left in an indeterminate state.

SOLUTION

Unregistered this manually from the database.

Use SYSDBA and execute these below, substitute MYEXTRACT with your extract name

SQL> exec DBMS_XSTREAM_GG_ADM.STOP_OUTBOUND('OGG$MYEXTRACT',true);
SQL> exec DBMS_XSTREAM_ADM.DROP_OUTBOUND('OGG$MYEXTRACT');
SQL> exec DBMS_STREAMS_ADM.REMOVE_QUEUE(queue_name => 'GGMINING.OGG$Q_MYEXTRACT', cascade => true, drop_unused_queue_table => true);

If the above works correctly, execute these selects to check.

SQL> select * from DBA_XSTREAM_OUTBOUND;
SQL> select * from SYS.XSTREAM$_SERVER;

Make sure you don’t see anything to do with this extract.

NOTE

You can use the above method to clean up any unregister extract database issues. However DO NOT use this as a substitute for GGSCI UNREGISTER. Always attempt the normal ggsci unregister first.

Read:  UNREGISTER EXTRACT DATABASE Fails with SQL error: OCI Error retrieving bind info for query (status = 100) (Doc ID 2088522.1)

One thought on “OGG-08221 Cannot register or unregister EXTRACT

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.