Eclipse Community Forums: Jubula

Help

Home

Home » Archived » Jubula » database full(Is there a way to reduce consumption from within Jubula ?)

Show: Today's Messages :: Show Polls :: Message Navigator

database full [message #1720119]

Thu, 14 January 2016 14:51

Joost Andrae

Messages: 12
Registered: January 2014

Junior Member

Hi,

I just wanted to import my project to my production user account. Unfortunately the import fails:

Connection to Database successful.
Importing projects...
Reading projects...
Reading project file /C:/tmp/foo/myproject_1.0_20160114.xml.
Project "myproject" in version 1.0 requires the following project(s):
- project "unbound_modules_concrete" in version 8.1
Finished reading projects.
Importing myproject_1.0...
Error occurred while importing myproject_1.0:
org.eclipse.jubula.client.core.persistence.PMSaveException: Can't save project.Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.BatchUpdateException: ORA-12953: The request exceeds the maximum allowed database size of 11 GB

I already removed the test result summary but there's still no way to import it...

Do you have an idea how to get around this without reinstalling the oracle db ?

Report message to a moderator

Re: database full [message #1720217 is a reply to message #1720119]

Fri, 15 January 2016 09:48

Achim Loerke

Messages: 376
Registered: July 2009
Location: Braunschweig, Germany

Senior Member

The 11GB limit is enforced by the Oracle XE database. All schemas count towards this limit. So if there already is data in the database you might just run into this limit with your import.

If this is the cause there is nothing you can do but to use another instance of the database.

- Achim

Report message to a moderator

Re: database full [message #1720219 is a reply to message #1720217]

Fri, 15 January 2016 10:28

Joost Andrae

Messages: 12
Registered: January 2014

Junior Member

Hi,

in the meantime I've fixed this.

I queried for the tablespace size as system user:

SELECT NVL(b.tablespace_name,
NVL(a.tablespace_name,'UNKOWN')) name,
round(kbytes_alloc/1024,2) Mbytes,
round((kbytes_alloc-NVL(kbytes_free,0))/1024,2) used,
round(NVL(kbytes_free,0)/1024,2) free,
round(((kbytes_alloc-NVL(kbytes_free,0))/kbytes_alloc)*100,2) pct_used
FROM ( SELECT SUM(bytes)/1024 Kbytes_free,
tablespace_name
FROM sys.dba_free_space
GROUP BY tablespace_name ) a,
( SELECT SUM(bytes)/1024 Kbytes_alloc,
SUM(maxbytes)/1024 kbytes_max,
tablespace_name
FROM sys.dba_data_files
GROUP BY tablespace_name )b
WHERE a.tablespace_name (+) = b.tablespace_name
ORDER BY PCT_USED;

NAME MBYTES USED FREE PCT_USED
UNDOTBS1 5315 34,25 5280,75 0,64
SYSAUX 790 748,13 41,88 94,7
SYSTEM 360 358,31 1,69 99,53
USERS 10610 10610 0 100

Then I saw that tablespace USERS is far too big.

Then I checked the content of tablespace USERS:

SELECT distinct owner, segment_type, segment_name
FROM dba_segments
WHERE tablespace_name='USERS';

and I saw two old project users which I deleted including data:

drop user MYUSER CASCADE;
drop user MYUSER1 CASCADE;

Afterwards I was able to import again Smile