The Streams environment requires proper configuration of the database initialization parameters that support the underlying functionality prior to the configuration of Capture, Propagate, and Apply process. It also requires that we "turn on" additional redo logging functionality. With all this added activity being turned on, we can expect a larger amount of metadata to be accumulated to keep track of all this. As much of this metadata is dynamic, it can cause fragmentation in the SYSTEM and SYSAUX tablespaces where it would be created by default. Due to this, we also recommend (as does Oracle) to move Logging and Streams schemas to their own tablespaces. This also feeds into the ease of "separation of duties" between tablespaces and database schemas and objects that enhance transportability.
Argentina
Australia
Austria
Belgium
Brazil
Bulgaria
Canada
Chile
Colombia
Cyprus
Czechia
Denmark
Ecuador
Egypt
Estonia
Finland
France
Germany
Great Britain
Greece
Hungary
India
Indonesia
Ireland
Italy
Japan
Latvia
Lithuania
Luxembourg
Malaysia
Malta
Mexico
Netherlands
New Zealand
Norway
Philippines
Poland
Portugal
Romania
Russia
Singapore
Slovakia
Slovenia
South Africa
South Korea
Spain
Sweden
Switzerland
Taiwan
Thailand
Turkey
Ukraine
United States