Logical Standby Ghost table??

Hi,

  Oracle 11.2.0.4, RHEL 5.10

 

  Our logical Standby showed some strange actions in testing for this weekend's project.  We are now done with the project, but now Production is showing the strange action too.

  1) In Production, there are SIEBEL "loading" tables, that the STandby database doesn't need for the application team that uses the standby.

  2) I DBMS_LOGSTDBY.SKIP those.

  3) Last night the Production Primary/Standby replication created two ghost copies of one of these tables i specifically skipped, called CMP4$xxxxxx.

 

Any seen that before?  I can't find a metalink or google page about this.

 

Lyall Barbour

 

PS. I skipped those tables and Data GUard is working just fine.  Would like to know why this happened in the first place though, so it doesn't happen in the future.