Another thing to keep in mind ... With TDE, the en/de-cryption takes place upon USING the data (sending to client, etc). Therefore it stays encrypted in memory (buffer cache, log buffer, sort segments, etc etc) With Tablespace encryption, en/de-cryption takes place upon READING FROM DISK (resp writing to disk). Therefore it stays in PLAINTEXT in all memory regions. Cheers Stefan ========================= Stefan P Knecht CEO & Founder s@xxxxxxxx 10046 Consulting GmbH Schwarzackerstrasse 29 CH-8304 Wallisellen Switzerland Phone +41-(0)8400-10046 Cell +41 (0) 79 571 36 27 info@xxxxxxxx http://www.10046.ch ========================= On Tue, Feb 24, 2009 at 1:16 AM, harshan eppuram <harshan.eppuram@xxxxxxxxx>wrote: > Hi All, > > We are implementing TDE(Transidential Data Encryption) on a solaris box > 10gr2 RAC ASM for one of client which is a Bank. We are facing following two > issues. This is a 4 TDB database. > > 1. Joining between encrypted and no encrypted table's columns are not > working. > 2. Encryption process is taking too much of time say 5 days ( We first > created tables with out encryption loaded data and then modified the columns > to be encrpted) > > Let me know if anybody come accross such sitiuation. > > Thanks and Regards > Harshan > > > -- > Harshan Eppurath > 040-40214832 > 09392426435 >