ORA-30036: unable to extend segment in tablespace

-

ORA-30036: unable to extend segment in tablespace

Error: unable to extend segment by %s in undo tablespace %s

Note: This is a general discussion which can be applied to any tablespace having this problem.

The tablespace mentioned in the error is unable to extend.

Reason for the Error:
~~~~~~~~~~~~~~~~~~~~~~~~~~~
There is not enough space left either due to the datafiles belonging to the tablespace are  being full,  autoextend which is not set at datafile level due to which they cannot increase in size whenever required or due to a disk which is full.

You will have to check the size of the datafiles attached to the tablespace and check whether they can autoextend or not.

Resolution for the Error:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Check if your disk or mount point containing database files (belonging to the respective tablespace) is not full. If it is full then provide your database with new disk(s) having enough free space on them.

The datafiles are reaching their size limit value. In that case you can either resize the current database file(s) or can add new database file(s) to the tablespace.

You can also make autoextend on if possible or permitted.

Sample {Assuming tablespace as UNDOTBS}
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

-- To add more space to a file issue following command:

alter database datafile 'C:\ORACLE\ORADATA\ORCL\UNDOTBS_01.DBF' resize 1000m;

-- To turn on the autoextend feature on a datafile use following command:

alter database datafile 'C:\ORACLE\ORADATA\ORCL\UNDOTBS_01.DBF' 
autoextend on next 100m maxsize 2000m;

-- To add a new datafile to the tablespace use following command:
 
alter tablespace UNDOTBS add datafile 
'C:\ORACLE\ORADATA\ORCL\UNDOTBS_02.DBF' size 100m 
 
 
[with autoextend on]
 
alter tablespace UNDOTBS01 add datafile 
'C:\ORACLE\ORADATA\ORCL\UNDOTBS_02.DBF' size 100m 
autoextend on next 100m maxsize 2000m;
 
 
 
Note: There are different commands when dealing with temporary 
tablespace.

Comments

Post a Comment

Back To Top

Popular posts from this blog

error 18 at 0 depth lookup: self signed certificate

-
I was trying to test SSL connection between MySQL client and server. For that I created SSL certificate and keys by following the MySQL documentation at: Creating SSL Certificates and Keys Using openssl After finishing up all the commands when I verify the certificates by using: openssl verify -CAfile ca.pem server-cert.pem client-cert.pem I got the following output: error 18 at 0 depth lookup : self signed certificate error server-cert.pem: verification failed client-cert.pem: OK  Reason : The Common Name value used for the server and client certificates/keys must each differ from the Common Name value used for the CA certificate. Otherwise, the certificate and key files will not work for servers compiled using OpenSSL. Solution : When OpenSSL prompts you for the Common Name for each certificate, use different names. Common Name (e.g. server FQDN or YOUR name) []: I used values as follows: CA Cert:  ssl-ca-cert Server Cert: ssl-ca-server-cert Client Cert:  ssl-c
Read more

How to check fragmentation in MySQL tables

-
MySQL tables, including MyISAM and InnoDB, two of the most common types, experience fragmentation as data is inserted, updated and deleted randomly. Fragmentation can leave large holes in your table, blocks which must be read when scanning the table. Optimizing your table can therefore make full table scans and range scans more efficient. We will mention how to check fragmentation in MySQL tables using SQL queries. USE < put_your_dbname_here > SELECT TABLE_NAME, CONCAT(ROUND(( data_length + index_length ) / ( 1024 * 1024 ), 2), 'M') TOTAL_SIZE, CONCAT(ROUND(( DATA_FREE ) / ( 1024 * 1024 ), 2), 'M') DATA_FREE FROM information_schema.TABLES where table_schema = database() and ROUND(( DATA_FREE ) / ( 1024 * 1024 ), 2) > 0.00 ORDER BY DATA_FREE DESC; SELECT TABLE_NAME, ROUND(((Data_length - (TABLE_ROWS * Avg_row_length))/Data_length) * 100, 2) FRAG_Percent FROM information_schema.TABLES where table_schema = database() and TABLE_ROWS > 0
Read more

How to Drop or Remove or Decommission a Database in Oracle

-
How to Drop or Remove or Decommission a Database in Oracle Database Decommission steps for Oracle 10G and 11g databases Note: ~~~~~~~~ Every organization has its own documented way of removing or decommissioning the active/running database that is supporting an Enterprise’s Application. Here I am presenting some general steps which may coincide with your organization’s standard operation procedure (SOP). 1)   Please get the required approval from Business/Customer to proceed for database decommissioning. 2)   Send the Notification to Business/Customer that we are going to decommission the database. (if required) 3)   Raise a Request for Storage and Backup team to take the required backup (provide all the details in the raised request) and to keep the Backup for a specified period of time, say for next 2 years, (That is called the backup retention period). Retention Period may be varied based on your business needs and SLA. The backup can be on disk or
Read more