How Do I Delete XStream Outbound Created When XStream Is Enabled?
For Oracle to GaussDB synchronization, if you use XStream for log reading, you need to delete XStream Outbound created by the DRS task from the source database after the task is complete. This prevents the disk space from being used up because the Oracle database does not automatically delete archive logs that are not consumed by XStream Outbound.
Procedure
- Run the following SQL statements on the source database to check whether XStream Outbound created by the DRS task exists:
SELECT SERVER_NAME, CONNECT_USER, CAPTURE_USER, CAPTURE_NAME, SOURCE_DATABASE, QUEUE_OWNER, QUEUE_NAME FROM DBA_XSTREAM_OUTBOUND;
The naming format of SERVER_NAME of XStream Outbound is DRS_+Task ID in uppercase. The hyphen in the uppercase task ID will be replaced by an underscore (_), for example, DRS_04981F62_84A4_4974_A5D5_772ED2DF63AC.
- If XStream Outbound exists, run the following SQL statement to delete it: In the following statement, <xstream SERVER_NAME> indicates the value of SERVER_NAME obtained in 1.
BEGIN DBMS_XSTREAM_ADM.DROP_OUTBOUND(server_name => '<xstream SERVER_NAME>');END;
Real-Time Synchronization FAQs
- Can DRS Sync Tables of Different Schemas to the Same Schema?
- Can Online DDL Tools Be Used for Real-time Synchronization?
- How Do I Delete XStream Outbound Created When XStream Is Enabled?
- Why Do I Use the SCAN IP Address to Connect to an Oracle RAC Cluster?
- How Do I Check Supplemental Logging of the Source Oracle Database?
- Which Specifications Should I Select for My DRS Task to Synchronize Data to GaussDB(DWS)?
- Suggestions on Synchronizing Data to GaussDB(DWS)
- Character Set Compatibility Between Oracle and GaussDB
- Garbled Characters or Synchronization Failure Due to Incompatible Character Sets
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
more