No question at this time
The DBA-Village forum
|Ever registered users||48524|
|Total active users||1409|
|Act. users last 24h||3|
|Act. users last hour||0|
|Registered user hits last week||77|
|Registered user hits last month||415||
Oracle to stop spilled transaction
If you think this item violates copyrights, please click here
||Oracle to stop spilled transaction
||Sivakumar KS, India
||Jun 10, 2020, 16:43, 58 days ago
||Linux == x86_64 x86_64 x86_64 GNU/Linux
||oracle 12c == Enterprise Edition Release 184.108.40.206.0 - 64bit Production
In our streams envirnoment, some of long process / transactions creates more archive generation in source DB, Hence streams also begin mining the archive log fast and try to apply on the target side, But same time it creating spilled transaction on target DB,we encount such situation only if source DB had few big volumne transaction.
How to avoid creating / encount spilled transaction. since once it is spilled then appply process get hungs / processing very slow. is there any way to propagate transaction slowly as per streams capacity.
Note: I do not want to ignore those spilled transaction.which should apply in target side.
also we do not have control on these transaction since source DB is hosted insurance product, so we do not have control on it.
could you help me to advice for the above.
FYI we have the following stream settings in our envirnoment
also streams_pools_Size as 25 GB. ( is there impact if we set more stream_pool_size then required ? ?)
Also apart fromt the above is there any other setting can be considered for part of spill / performance. since if we encount spill / big volume of transaction then parallelisam also not working, coz source goes for paused for flow control.
IS there any way to create more than one DB_link which allows to serve / send data to target etc., is just my thought correct me if I am wrong.
Thanks for your support.
||Reply - Top of page