By Tim Gorman
In Part I of this series we talked about the initial set up and some of the components of dbvrep. We walked through the few questions needed prior to asking about your databases. Now we will look at setting up the replication for your databases, of which there are usually two, referred to as source […]
We’re inspired to see bloggers doing things they love and using this platform to make their voices heard. Here’s a look at some interesting projects around the globe.
Oracle’s 18.104.22.168 was released a few weeks ago (You can download it from OTN here: Oracle 22.214.171.124 Download). While technically a minor point release, it contains a couple of major features that would normally be rolled out in a more substantial version change like 12cR2 or perhaps V13.
There is a time in every SQL Server DBA career where a mail came in with a “replication is not working, please check” message. This article is intended to provide with quick tips on how to handle common replication errors and performance problems in a one way transactional replication topology
Oh boy, there is a data problem:
I received the below error in soa_server1 :-Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 603 seconds BEA1-3FB6FB464035C13E3227 at From the above error, transaction timeout should be increased regarding to heavy transaction on soa server.to do this follow the following steps :-access weblogic console --> Deployment --> and search for Soa_infra. ( expand it)
Since Oracle 10g, Oracle provides a great tool to import and export data from databases: Data Pump. This tool offers several helpful options, particularly one that allows to import data in a different tablespace than the source database. This parameter is REMAP_TABLESPACE. However, how can you do the same when you cannot use Data Pump to perform Oracle import and export operations?