3 Replies Latest reply on Jun 18, 2012 8:25 AM by 783262

    Update large amount of BLOB (archivelog problem)

      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?