oracle streams

Iv. Clear Streams Replication environment On the one hand is to facilitate the test environment behind the construction, on the one hand because the 10g streams replication environment is very simple to remove, so this is the last section of this chapter. To remove the entire replication environment, simply log on to the Streams Administrator account on the sou

Description:Originally, one-way transmission of Streams was directly configured on two database servers,The original source database is two clusters of 64-bit HP-UNIX Oracle11gR2 database,The original target database is a 64-bit Linux Oracle11gR2 database,Now on the basis of the above, the Oracle11gR2 of a 64-bit Linux as the source database, the two clusters of 64-bit HP-UNIX Oracle11gR2 database as the target database,Install the one-way transmissio

the source and target DatabasesSource:View the data file location:Select file_name from dba_data_filesCreate a tablespace:Create tablespace streams_spaceDatafile '+ DATADG/cboms/datafile/streams_space.dbf'Size 5 M autoextend onCreate a user:Create user strmadminIdentified by strmadminDefault tablespace streams_spaceAuthorize the dba role:Grant dba to strmadminGrant Stream Management permissions:Exec dbms_streams_auth.grant_admin_privilege ('strmadmin') ---- use sys or system to execute Objectiv

This section mainly describes the workflow of communication, as well as some related features (processing logic), the content is equally boring, but think twice about the value of reading. In the entire streams replication environment, the propagation process is responsible for copying the source-side modification queues to the target database. 1. LCR Segmentation Streams passes messages through a queue s

Step by step, gathering small streams ------ oracle easily modifies the entire row of data, ------ oracle As you learn more and more about your knowledge and discover your own shortcomings, record the knowledge you learned this time. Although oracle is used in the project, it is not very good for

Step by step, gathering small streams ------ oracle quick add test data, ------ oracle Some time ago, problems were found during implementation and need to be modified at that time. Because the data in the database is real data, it cannot be modified. Otherwise, a large leak may occur, therefore, adding test data is easy to modify, and the efficiency of adding a

the previous chapter (primarily the Oracle environment, where the previous replication environment has been purged) and set the environment as follows: Source database Sid:jssweb, Target library: jssstr; Copying objects in Schema:member, partially synchronizing DML, partially synchronizing DDL operations; Local capture, one-way synchronization; Dbms_streams_adm. Maintain_tables generate configuration scripts; The

Problem: A Streams exception is found in the source database, for example: Check: select * from dba_capture. An error is returned. ORA-26744: STREAMS capture process "CAPTURE_STREAM" does not support "BHOMSWAS". "DBMS_TABCOMP_TEMP_UNCMP" because of the following reason: ORA-26767: No enough redo log information for LogMiner Oracle metalink explanation:

As described earlier, Oracle provides two ways for database-level replication: A, Maintain_global B, Pre_instantiation_setup, Post_instantiation_setup Maintain_global is suitable for small and medium-sized database creation, while Pre_instantiation_setup+post_instantiation_setup is suitable for the creation of large database, here we demonstrate through pre_ The Instantiation_setup and Post_instantiation_setup procedures Create a database-level

Second, the initialization of the environment Before you are ready to create a streams replication environment, there are some preparations that need to be made, as follows: 1. Configure Administrator account For ease of administration, it is not recommended to use Sys/system users, nor is it recommended to use System tablespace, and recommend that everything be new. The user needs to be created separately on the Source/target side and must have re

In the previous chapter we practiced a streams synchronization of a single table, it looks very simple is not (if you feel complex, it is not because the streams itself is complex, but to configure the streams earlier preparation is more complex), in fact it is very simple, from small to see big, We should also see from the example above that streams's operation

: Source database Sid:jssweb, Target library: jssstr Downstream capture Copy webdata table space, configured for bidirectional replication Synchronous DDL Operations Dbms_streams_adm. Maintain_tts Direct Build Configuration STREAMS management has been created, and the database chain for source and target-side communication has also been created See more highlights of this column: http://www.bianceng.cnhttp://www.bianceng.cn/database/

STATUS Capture_ty ------------------------------ -------- ---------- Jssweb$cap ENABLED Downstream Jssstr> select Propagation_name,status from Dba_propagation; Propagation_name STATUS ------------------------------ -------- Propagation$_75 ENABLED Jssstr> select Apply_name,status from dba_apply; Apply_name STATUS ------------------------------ -------- Apply$_jssweb_82 ENABLED See more highlights of this column: http://www.bianceng.cnhttp://www.bianceng.cn/database/

Schema-level replication can be done through DBMS_STREAMS_ADM. Maintain_schemas created, after the space-level trial of the previous table, the creation of a schema-level replication environment is relatively straightforward. The examples in this chapter continue to follow the environment in the previous chapter (primarily the Oracle environment, where the previous replication environment has been purged) and set the environment as follows: Source d

Step by step, gathering small streams ------ quickly add test data to oracle Some time ago, problems were found during implementation and need to be modified at that time. Because the data in the database is real data, it cannot be modified. Otherwise, a large leak may occur, therefore, adding test data is easy to modify, and the efficiency of adding a single one is too low, so the solution isAdd new easy-t

Database: SC _source and SC _dest Requirement: Copy all objects under the product user in SC _source to SC _dest. I. preparations: 1.1 place the SC _source and SC _dest databases in the archive Mode 1.2 if some tables do not have a primary key, configure secondary logs on the source database (SC _source) to ensure the accuracy of replication. Alter database add supplemental log data (primary key, unique) columns; 1.3 Source: some parameters are set for the target database

Guidance: A few days ago, we used the package to complete the streams configuration. However, it would be more intuitive to use the OEM in management. Of course, it would be almost the same if we knew all the related packages. In 9i OEM, it seems that the function of streams is not very strong. It's just some simple applications. Next, we have time to build 10gr2, and we want to skip 10gr1. The following is

Guide: The last few days are used package to complete the streams configuration, but in the management of OEM will feel more intuitive, of course, all the relevant package very understanding, it is almost. In the 9i OEM, it looks like the streams function is not very strong. Just a few simple applications. There is time to engage in 10gr2, want to skip 10gr1. The following is a process script that creates a

ORA-26663 for removing process Errors When configuring Streams:SQL> exec dbms_apply_adm.drop_apply ('target _ APPLY_STREAM ');BEGIN dbms_apply_adm.drop_apply ('target _ APPLY_STREAM '); END; *ERROR at line 1:ORA-26663: error queue for apply process ORA-26663: error queue for applyProcess TARGET_APPLY_STREAM must be emptyMust be emptyORA-06512: at "SYS. DBMS_APPLY_ADM_INTERNAL", line 359ORA-06512: at "SYS. DBMS_APPLY_ADM_INTERNAL", line 334ORA-06512: at "SYS. DBMS_APPLY_ADM", line 690ORA-06512: a

> select Sysdate from Dual@jssweb; Sysdate ------------ 24-mar-09 Because Jssbak is a new library, we create a new user and table space to hold the replicated data: jssbak> Create tablespace webdata datafile¨/data/oracle/oradata/jss bak/webdata01.ora¨size 200m; Tablespace created. Jssbak> create user member identified by member default Tablespace webdata quota unlimited on webdata; User created. Jssbak> Grant Connect,resource to member; Gran