Upgrade Express: unable to create INITIAL extent for segment in tablespace TS4D

• Article Type: General
• Product: Aleph
• Product Version: 20

Description:
We have started the import step of the Data Pump on our target server using "3. Install Oracle data and u-tree in one step". However, we are seeing Oracle errors in the install_utree.log file:

ORA-39171: Job is experiencing a resumable wait.
ORA-01658: unable to create INITIAL extent for segment in tablespace TS4D

I *think* we understand now what has happened. When we set up the tablespaces on the target db, we mimicked the tablespace setup on our source db in that allocation type is UNIFORM (rather than AUTOEXTEND), and the initial extent of the first data file corresponded with the figures of the source data files from file_list. In this case, tablespace TS4D was set to have an initial extent of 960M and AUTOEXTEND set to no.

This web article seems to describe our situation: http://dbtricks.com/?p=62

We have two questions:

1) how can we stop the Data Pump process (as described in the website article mentioned above) in order to alter the tablespace setup?

2) on a broader note, should we re-think how the new tablespaces on the target db are configured? In other words, should we continue using UNIFORM tablespaces, and if so, should the same number of data files (with the same names) be added to the source db prior to running step 2? Or, should we use AUTOEXTEND tablespaces?

Resolution:
1) You can stop the Install Customer Data process (including the Data Pump) by killing the processes shown by the

> ps -ef | grep install and
> ps -ef | grep imp

commands.

2) Most sites *are* now using AUTOEXTEND. It makes tablespace management much easier. But that's up to you.

[From site:]

We will try the following:

1) drop TS1D,

2) re-create TS1D (and all the other necessary tablespaces) to have initial datafiles set as AUTOEXTEND

3) re-run the Oracle Data pump import.

This worked.

• Article last edited: 10/8/2013