[Spacewalk-list] Error during schema upgrade
David Nutter
davidn at bioss.sari.ac.uk
Tue Feb 16 14:08:30 UTC 2010
On Tue, Feb 16, 2010 at 08:53:51AM -0500, Frey, Evan wrote:
> here's the sql its executing when that error pops up
You probably just have a lot of package file records that's exhausting
the fixed-size tablespace that Oracle uses to store the information
needed to rollback transactions. If possible you might have success by
cleaning up some old package records (e.g. from packages in no
channels) and try the schema upgrade again.
Fortunately, the undo tablespace apparently does not count towards the
XE size limit so you can just make it bigger! This is easy
enough. First, you might like to examine the size of the DBF files
containing your existing undo tablespace:
sqlplus / as sysdba
select file_name, trunc(bytes/1024/1024,2) size_mb, autoextensible, trunc(bytes/1024/1024,2) maxsize_mb from dba_data_files where tablespace_name='UNDO';
You'll get something like:
FILE_NAME
--------------------------------------------------------------------------------
SIZE_MB AUT MAXSIZE_MB
---------- --- ----------
/usr/lib/oracle/xe/oradata/XE/undo.df
300 YES 300
To resize this to something bigger, just do something like:
alter database datafile '/usr/lib/oracle/xe/oradata/XE/undo.dbf' resize 1000m;
This will take ages but once done you will have a much bigger undo
tablespace. Note that if disk space is a consideration shrinking this
tablespace again is much harder - the only way I found to do it was to
shutdown spacewalk, create a new undo tablespace, switch oracle to
using that then dropping the old one.
HTH & regards,
--
David Nutter Tel: +44 (0)131 650 4888
BioSS, JCMB, King's Buildings, Mayfield Rd, EH9 3JZ. Scotland, UK
Biomathematics and Statistics Scotland (BioSS) is formally part of The
Scottish Crop Research Institute (SCRI), a registered Scottish charity
No. SC006662
More information about the Spacewalk-list
mailing list