(Is it ALTER DATABASE something? No, wait, maybe it's ALTER SYSTEM. I can find masses of highly technical writing which seems to assume you already know it all, and I can find introductory material which assumes you bearly know what a computer is, but I can find almost none of the material I want - the bit in the middle! It's really very difficult indeed to find any useful info at all - just finding out the exact command to cause a log switch took me ages. Well, I can never find anything in the Oracle docs. That is quite the difference! but wait, it gets create table cipher_rc6_sbox ( input number, output number ) Įlapsed: insert /*+ APPEND */ into cipher_rc6_sbox Now, same table - no drop table cipher_rc6_sbox Įlapsed: create table cipher_rc6_sbox ( input number, output number ) Įlapsed: same table - BULK drop table cipher_rc6_sbox ĥ where rownum select used_ublk*8/1024 "RBS used in MEG" from v$transaction Just assuming you are loading into heavily indexed declareĮlapsed: select used_ublk*8/1024 "RBS used in MEG" from v$transaction Consider the following 4 create table cipher_rc6_sbox ( input number, output number ) Įlapsed: create index t1_idx on cipher_rc6_sbox(input) Įlapsed: create index t2_idx on cipher_rc6_sbox(output) Įlapsed: create index t3_idx on cipher_rc6_sbox(input,output) Įlapsed: create index t4_idx on cipher_rc6_sbox(output,input) You also did not set up an INITIAL, NEXT (should probably be 1m and 1m in many generic cases to start with).īut, yes, your approach generates THE MOST undo possible. Problem here is you said "max extents is 121 for this RBS", so - didn't matter that the file could grow, you did not let the RBS grow. You do not say what version of Oracle you are using either - in 9i, you should use AUM (automatic undo mgmt) instead of manually creating your own RBS's.Īutoextend lets a file grow as segments extend. The ADMIN guide would be a second "must read" for you followed by the backup and recovery guide (at least 2 times). The concepts guide (a MUST MUST read for any Oracle professional) covers it as well. If you have my book "expert one on one Oracle" - i describe how RBS is used. Just means you tried to wrap back around in the RBS and couldn't - but could not grow it either). It only takes a tiny - let longer lived - transaction to cause this. we use RBS space in a circular fashion - we cannot reuse RBS data until the transactions that were using it committed. Were there other transactions happening here? look in v$transaction (perhaps you left a window open last week sometime. Might not be your transaction that is causing this.
Is there a Better Way(tm) to create the data I'm trying to create? I suspect this means I fundamentally don't understand how this stuff works. :-SĬreate Public Rollback Segment RollbackSeg1 Tablespace RollbackData Storage (Optimal 4M) automatically extends to be whatever size it needs to be! Clearly I was catastrophically mistaken. I was under the impression that using AUTOEXTEND means that the thing. (And I am the *only* person using this DB.) It's only a test database, so I haven't allocated much rollback. how much rollback do you NEED? :-| I wouldn't have thought this tiny thing would need very much. ORA-01628: max # extents (121) reached for rollback segment ROLLBACKSEG1Įrm. ORA-01562: failed to extend rollback segment number 1 5 insert into cipher_rc6_sbox (input, output) values (n, (2*n+1)*n)