Home » RDBMS Server » Server Administration » Tablespace issue on certain workstations (oracle 8i 8.1.7.4.1)
Tablespace issue on certain workstations [message #546203] Mon, 05 March 2012 13:51 Go to next message
echomaster
Messages: 7
Registered: September 2005
Location: Canada
Junior Member
I am NOT a db admin but I do 'maintain' my application that runs with oracle 8i.

I am now getting the error on certain workstations:

ORA-03232: unable to allocate an extent of 16 blocks from tablespace 3

I have access to DBA Studio and all the tables in the STORAGE tab show no more than 65% usage

How do I fix this - I have read across forums like this that it is a fragmentation issue - is this true?


Re: Tablespace issue on certain workstations [message #546204 is a reply to message #546203] Mon, 05 March 2012 13:58 Go to previous messageGo to next message
BlackSwan
Messages: 23048
Registered: January 2009
Senior Member
why does my error message no match what you posted?
did you mistype the number?
32320, 00000, "REFRESH FAST of \"%s\".\"%s\" unsupported after container table PMOPs"
// *Cause:  A Partition Maintenance Operation (PMOP) has been performed on the 
//          materialized view, and no materialized view supports
//          fast refersh after container table PMOPs.
// *Action: Use REFRESH COMPLETE.  Note: you can determine why your 
//          materialized view does not support fast refresh after PMOPs using
//          the DBMS_MVIEW.EXPLAIN_MVIEW() API.
Re: Tablespace issue on certain workstations [message #546212 is a reply to message #546203] Mon, 05 March 2012 14:58 Go to previous messageGo to next message
LKBrwn_DBA
Messages: 447
Registered: July 2003
Location: WPB, FL
Senior Member
Perhaps all you need is to add more space to the "TEMP" tablespace.
Find out which is tablespace #3:
SELECT ts#, name FROM sys.ts$ WHERE ts# = 3;

[Updated on: Mon, 05 March 2012 23:06] by Moderator

Report message to a moderator

Re: Tablespace issue on certain workstations [message #546215 is a reply to message #546203] Mon, 05 March 2012 15:19 Go to previous messageGo to next message
joy_division
Messages: 4545
Registered: February 2005
Location: East Coast USA
Senior Member
echomaster wrote on Mon, 05 March 2012 14:51
How do I fix this - I have read across forums like this that it is a fragmentation issue - is this true?


Could be. With an 8k block size, you are looking at 131072 bytes. You need to have a contiguous chunk of that size.

[edit]

I also wanted to point out that "certain workstations" is irrelevant, or at least without defining what you mean by it. A workstation to me is a client that connects to a database server and has nothing to do with storage in the database.

[Updated on: Mon, 05 March 2012 15:22]

Report message to a moderator

Re: Tablespace issue on certain workstations [message #546218 is a reply to message #546215] Mon, 05 March 2012 15:38 Go to previous messageGo to next message
echomaster
Messages: 7
Registered: September 2005
Location: Canada
Junior Member
Certain clients show this ORA-03232 error when refreshing the db whereas other clients do not show this error and refresh fine with the app presenting the 'patient list'.

How do I make a contiguous block in a table.

sorry for the newbie-speak but I am not a db admin
Re: Tablespace issue on certain workstations [message #546244 is a reply to message #546218] Mon, 05 March 2012 23:08 Go to previous messageGo to next message
Michel Cadot
Messages: 59775
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
2 ways (among other);
1/ increase the size of the tablespace file(s)
2/ (if you can't 1) export the objects in the tablespace, truncate the objects in it, import the objects you exported (with ignore=y).

Regards
Michel
Re: Tablespace issue on certain workstations [message #546419 is a reply to message #546244] Tue, 06 March 2012 11:30 Go to previous messageGo to next message
echomaster
Messages: 7
Registered: September 2005
Location: Canada
Junior Member
So I used [ SELECT ts#, name FROM sys.ts$ WHERE ts# = 3; ] and found it tablespace 3 was TEMP. I used DBA Studio to AUTOEXTEND the size of the datafile (only 1.9% was in use). I went to the client w/s and this did not fix the ORA-03232 error. However I went to app and changed the query parameters from [ Feb 2011 through to Dec 2012 ] to [ Feb 2012 through to Dec 2012 ] and now no tablespace error.

Might someone have an explanation?

All the best
jim
Re: Tablespace issue on certain workstations [message #546422 is a reply to message #546419] Tue, 06 March 2012 11:52 Go to previous message
Michel Cadot
Messages: 59775
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
You need less temp space for the second one, obviously.

Regards
Michel
Previous Topic: Deleting Archive log in DR
Next Topic: Oracle and Active Directory services
Goto Forum:
  


Current Time: Tue Nov 25 18:28:26 CST 2014

Total time taken to generate the page: 0.08371 seconds