I know this is a popular subject, but I didn't manage to find the right answer. Maybe someone can give me a hint.
I have a database which is about 4 Tb in size. The problem comes from short space. I have a table with a BLOB column and I want to update some of the records with null (the updated total amount of deleted data will be about 1.6 Tb). I know that this operation will generate a huge amount of archivelog. I can take the servers out of production for a weekend and disable archivelogs, but the thorn in my side is a STREAMS configuration about which I don't know much. I understand that if I disable archive logging the streams will not like it.
Do you have any suggestion?
Possible solutions depend on four digit Oracle version and edition and platform, neither of which you mention.
Streams is implemented by shipping and reading archivelogs, so if you disable archivelog streams will stop to function.
Something is architecturally really really wrong if you want top update 40 percent of the database in one shot.
You are trying to fight symptoms, where a cure is needed.
Problem is not archivelog. Problem is the architecture of this 'application'.
Senior Oracle DBA
The db version is RAC 10g 10.2.0.4
The cure is that I moved the data to another place, and now I have to delete the old data. The database without blobs has about 800 Gb. The design was not very good in tje first place, I know. Now I'm moving some of the blobs to another storage area.