Tag Info

New answers tagged


As you already mentioned documentation that you cannot use table level filtering on replication. You might like to try another approach instead. Replicate whole database and change all tables except those you need to use to BLACKHOLE engine. alter table X engine=BLACKHOLE;


@Hpk, since you have already answered your own question, my answer will provide you some food for thoughts : I ask because I need a way of rebuilding or reorganizing based on internal fragmentation rather than external and I don't want to create logic to rebuild/reorg if a avg_page_space_used_in_percent < 75 if the fill factor in the first place is 70 ...


avg_page_space_used_in_percent does not care about fill factor. Therefore if you set an index to have fill factor of 40, your avg_page_space_used_in_percent will straight away be 40.


This is because flush table tablename1,tablename2 with read lock; is contained within one transaction and flush table tablename1 with read lock; flush table tablename2 with read lock; Is not. In this second scenario the first table is locked for that session. That session can't acquire a second lock on another table because the session already has ...


According to this page, all locks in a session have to be obtained in a single statement. A session that requires locks must acquire all the locks that it needs in a single LOCK TABLES statement. While the locks thus obtained are held, the session can access only the locked tables


What you are saying is right. The database should not be shrinked. However there are some exceptions. Let's say you move a lot of historical data out of your DB and it goes down from 100GB to 10GB. You may want to reduce it back to 10 or 20 or 50GB. The thing to remember when you decide to go on with a shrink is that data (clustered and non clustered ...


What powershell syntax are you using? If you do not enclose the select between single quotes, Powershell will treat it like a variable. If that's the problem, please try: $command.CommandText = 'SELECT COUNT (*) AS COUNT FROM v$session'


You need to grant the DBA role to the user. SYSDBA does not give you the right to these objects.

Top 50 recent answers are included