Import fails with unable to extend table CUSTOM.CASA_TRAN_HIST_UPLD by 6999

Question

Hi,
I have taken export backup of table from 9.2.0.4 on AIX & trying to import in 11.1.0.7.0 on AIX
while importing im getting the following error.
ORA-01653: unable to extend table CUSTOM.CASA_TRAN_HIST_UPLD by 699912 in tablespace CUSTOM
As the table size is 37G , total free space in tablespace is 40G,
& no index on the table.
following are sum lines from import file
Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Export file created by EXPORT:V09.02.00 via direct path
import done in US7ASCII character set and UTF8 NCHAR character set
import server uses AL32UTF8 character set (possible charset conversion)
export server uses AL16UTF16 NCHAR character set (possible ncharset conversion)
. importing DATAMIG's objects into CUSTOM
. . importing table "CASA_TRAN_HIST_UPLD"
IMP-00058: ORACLE error 1653 encountered
ORA-01653: unable to extend table CUSTOM.CASA_TRAN_HIST_UPLD by 699912 in tablespace CUSTOM
IMP-00028: partial import of previous table rolled back: 62844421 rows rolled back
IMP-00017: following statement failed with ORACLE error 1917:
"GRANT SELECT ON "CASA_TRAN_HIST_UPLD" TO "BSGUSER""
IMP-00003: ORACLE error 1917 encountered
ORA-01917: user or role 'BSGUSER' does not exist
Import terminated successfully with warnings.
is there any to resolve the issue.
how to change NCHAR set for import.
Thanks

Answer 1

Hello,
which & how i can set character set for import.About the Character Set, it's a setting at the Database creation. You may check it by using the following query on the Source and Target Databases:
select * from v$nls_parameters; The NLS_CHARACTERSET will give you the Character set of the Database.
It cannot be changed easily. It may imply a Database creation and export/import of data ( see Note *225912.1* ).
Else, when you export (with the Original Export/Import utility) it's recommended to set the NLS_LANG parameter.
The NLS_LANG parameter has 3 components:
- Language
- Territory
- Client Character Set
A wrong setting of the NLS_LANG may lead to conversion. However starting with *9i* most data is exported with the Character Set of the Database regardless the NLS_LANG setting. The following note may give you some details about it:
Export/Import and NLS Considerations [ID 15095.1]Hope this help.
Best regards,
Jean-Valentin