STREAMS Duplicate database - GV$LOGMNR_SESSION still contains entries
482458Nov 9 2006 — edited Dec 7 2006We duplicated a Streams replicated database. I have scripts that clean out the Production replication information (EXEC DBMS_STREAMS_ADM.REMOVE_STREAMS_CONFIGURATION). This was hanging as the database had entries in GV$LOGMNR_SESSION that showed connected sessions trying to mine the log. Hence the capture process did not drop.
Anyone come across this before?