Home » RDBMS Server » Server Utilities » IMPORT Problem
IMPORT Problem [message #69518] Thu, 24 January 2002 23:31 Go to next message
Keshav Tripathy
Messages: 30
Registered: November 2001
Member
We are badly stuck with an import problem with st_txn_trlr. While importing, the import is
aborting saying 'maximum number of extents reached', and then rolling back some 2900000 rows out of a total of 3500000 of rows. We have all curradt user tablspaces
offline except the default tablespace which has about 400 MB space. The 'oerr' shows that it is necessary to
increase a combination of initial extent,nextxtent,pctincrease etc. We have already tried
different combinations - starting from initial = 256 K, next = 256 k,pctincrease = 0 upto initial = 4m, next = 4m and pctincrease = 50%. But the same error message is coming. We had been trying this for the last 5hrs., but in vain. Please extend guidance, if it is not absolutely impossible. We know we should not have bothered you with such a request.
The question is what is the right combination ? and how to determin that ? The st_txn_trlr table structure is as follows :

storeid varchar2(2) not null,
txn_typ varchar2(3) not null,
txn_yy varchar2(2) not null,
txn# number(6,0) not null,
line# number(3,0),
item_cd varchar2(7),
conv_factr_txn number(7,3),
qty_txn number(7,2),
measr_unit_txn varchar2(4),
flg_batch#_req varchar2(1),
tot_qty_ret number(7,2),
rate number(10,2),
value number(10,2))

The oracle error messages we came across are ORA 1631 followed by ORA1542.
Re: IMPORT Problem [message #69521 is a reply to message #69518] Fri, 25 January 2002 04:25 Go to previous messageGo to next message
Ajay Gandhi
Messages: 14
Registered: January 2002
Junior Member
I believe your tablespace Max_Extents parameter is set too low. Try creating the table before the import with a big Initial extent. Also try commit=y in the import clause, that will get rid of rollback problems.

Re: IMPORT Problem [message #69523 is a reply to message #69518] Fri, 25 January 2002 04:55 Go to previous messageGo to next message
Grant
Messages: 578
Registered: January 2002
Senior Member
Try exporting the table again and make sure COMPRESS=Y. Then try the import again. This will create one initial extent for the table to fit it all in one extent. Also are you sure the target tablespace is the culprit. You could be running out of extents in TEMP or rollback segements. What is the exact error in the alert log?
Re: IMPORT Problem [message #69560 is a reply to message #69521] Thu, 31 January 2002 07:02 Go to previous message
José Luis Delgado Solano
Messages: 9
Registered: January 2002
Junior Member
Just increase to UNLIMITED your maxextents for that table... or tables...

In the other hand, check if the tablespace is online...

Hope this helps!
Previous Topic: HELP I NEED HELP WITH ORACLE
Next Topic: HELP
Goto Forum:
  


Current Time: Thu Mar 28 16:27:14 CDT 2024