ORA-01555 in importing table

i have used a script to export a table from a database located in a machine and i'm importing the content of the table to another machine.
The table has 207 7390260 records.
But in the process of importing the data, it occurs the error: ORA-01555: snapshot too old: rollback segment number 2 with name "_SYSSMU2$" too small.
i've tried to change my undo_retention parameter to 1800, but the error continues to occur. i'm not sure if i can increase the undo_retention to a much bigger size. can i?
I'm using oracle 10g
here are some information about the undo tablespace:
AUTOEXT Tablespace Name File Name Size (M) Size (MaxMBytes) Used (M) Free (M)
YES UNDOTBS1 undotbs01.dbf 6000 131071,94 15,25 5967,88

there is no information in the alert.log about the query.
i only have a log file created that says:
ORA-39125: Worker unexpected fatal error in KUPW$WORKER.GET_TABLE_DATA_OBJECTS while calling DBMS_METADATA.FETCH_XML_CLOB [TABLE_DATA:"SCHEMA"."TABLE1":"D090502H1559"]
ORA-01555: snapshot too old: rollback segment number 2 with name "_SYSSMU2$" too small
ORA-06512: at "SYS.DBMS_METADATA", line 1546

Similar Messages

ORA-01555 while gathering table statistics

Hello All,
While running a job to gather table statics it failed and I saw in my alert logs ORA-01555, below is the job:
DBMS_STATS.GATHER_TABLE_STATS (SCHEMA_NAME, TABLE_NAME, PARTITION_NAME, ESTIMATE_PERCENT => DBMS_STATS.AUTO_SAMPLE_SIZE, METHOD_OPT=> 'FOR ALL COLUMNS SIZE AUTO');What is the reason behind the ORA-01555 ?
How can I prevent it in the future ?
Regards,

There are two queries,
Below query for optimal undo size based on your undo retention
select d.undo_size / (1024 * 1024) "ACTUAL UNDO SIZE (MEGS)",
substr(e.value, 1, 25) "UNDO RETENTION (Secs)",
(to_number(e.value) * to_number(f.value) * g.undo_block_per_sec) /
(1024 * 1024) "NEEDED UNDO SIZE (MEGS)"
from (select sum(a.bytes) undo_size
from v$datafile a, v$tablespace b, dba_tablespaces c
where c.contents = 'UNDO'
and c.status = 'ONLINE'
and b.name = c.tablespace_name
and a.ts# = b.ts#) d,
v$parameter e,
v$parameter f,
(select max(undoblks / ((end_time - begin_time) * 3600 * 24)) undo_block_per_sec
from v$undostat) g
where e.name = 'undo_retention'
and f.name = 'db_block_size';
Below is the result from my database;
        ACTUAL UNDO SIZE (MEGS)     UNDO RETENTION (Secs)     NEEDED UNDO SIZE (MEGS)
       20860                     900          955.6171875
Another query is based how much undo retention you have to configure as per the undo size
select d.undo_size / (1024 * 1024) "ACTUAL UNDO SIZE (MEGS)",
substr(e.value, 1, 25) "UNDO RETENTION (Secs)",
round((d.undo_size / (to_number(f.value) * g.undo_block_per_sec))) "OPTIMAL UNDO RETENTION (Secs)"
from (select sum(a.bytes) undo_size
from v$datafile a, v$tablespace b, dba_tablespaces c
where c.contents = 'UNDO'
and c.status = 'ONLINE'
and b.name = c.tablespace_name
and a.ts# = b.ts#) d,
v$parameter e,
v$parameter f,
(select max(undoblks / ((end_time - begin_time) * 3600 * 24)) undo_block_per_sec
from v$undostat) g
where e.name = 'undo_retention'
and f.name = 'db_block_size';
Below is the result from my database;
        ACTUAL UNDO SIZE (MEGS)     UNDO RETENTION (Secs)     OPTIMAL UNDO RETENTION (Secs)
     20860                           900                         19646
BTW, have you tried again by executing the same ?Yes with no problem, it only happened once
In the link you mention I read the below
"The ORA-1555 happens when people try to save space typically. They'll have small
rollback segments that could grow if they needed (and will shrink using OPTIMAL). So,
they'll start with say 10 or so 1meg rollback segments. These rollback segments COULD
grow to 100meg each if we let them (in this example) however, they will NEVER grow unless
you get a big transaction.
If your database does lots of little transactions, the RBS will never grow on their own.
They will stay small.
Now, someone needs to run a query that will take 5 minutes. On your system however the
rollback wraps every 2 minutes due to lots of little transactions going on. In this
system, ORA-1555's will happen frequently. What you need to do here is size rollback so
that it wraps less frequently (less frequently then your long running queries). Here if
I sized the rollback so that I had 10, 10meg segments (not so they could GROW to 10meg
but that they are starting at 10meg) we would wrap maybe every 20minutes now. that'll
give that 5minute query plenty of time to complete without reusing rollback it needs.
I Think this is exactly my case, how can I resize my redo segments ? and how can I check its current size?

Abap import error DbSl Trace: ORA-1403 when accessing table SAPUSER

hi all
I am installing ERP 6.0 (ABAP) on win2003 cluster, oracle 10g, I have error at database instance intallation. here some logs
DD03L.log
I:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20090812102157
I:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#18 $ SAP
I:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Apr 3 2009 09:03:56
I:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe -i DD03L.cmd -dbcodepage 4103 -l DD03L.log -stop_on_error
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(RTF) ########## WARNING ###########
 Without ORDER BY PRIMARY KEY the exported data may be unusable for some databases
(TPL) ERROR: unknown template variable "tablespace"
I:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
I:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20090812102157
import_monitor.log
ERROR: 2009-08-12 10:21:57 com.sap.inst.migmon.LoadTask run
Loading of 'DD03L' import package is interrupted with R3load error.
Process 'I:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe -i DD03L.cmd -dbcodepage 4103 -l DD03L.log -stop_on_error' exited with return code 2.
For mode details see 'DD03L.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
WARNING: 2009-08-12 10:22:25
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-08-12 10:22:25
1 error(s) during processing of packages.
INFO: 2009-08-12 10:22:25
Import Monitor is stopped.
sapinst_dev.log
ERROR 2009-08-12 10:22:25.718
 CJSlibModule::writeError_impl()
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
TRACE 2009-08-12 10:22:25.718 [iaxxejsbas.hpp:483]
 EJS_Base::dispatchFunctionCall()
JS Callback has thrown unknown exception. Rethrowing.
ERROR 2009-08-12 10:22:25.734 [sixxcstepexecute.cpp:951]
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|8|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR ( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.).
TRACE 2009-08-12 10:22:25.781 [iaxxgenimp.cpp:752]
 CGuiEngineImp::showMessageBox
<html> <head> </head> <body> An error occurred while processing service SAP ERP 6.0 Support Release 3 > SAP Systems > Oracle > High-Availability System > Based on AS ABAP > Database Instance( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.). You may now <ul> <li> choose Retry to repeat the current step. </li> <li> choose View Log to get more information about the error. </li> <li> stop the task and continue with it later. </li> </ul> Log files are written to C:\Program Files/sapinst_instdir/ERP/SYSTEM/ORA/HA/ABAP/DB. </body></html>
TRACE 2009-08-12 10:22:25.781 [iaxxgenimp.cpp:1255]
 CGuiEngineImp::acceptAnswerForBlockingRequest
Waiting for an answer from GUI
sapinst.log
WARNING 2009-08-12 10:22:25.718
Execution of the command "C:\j2sdk1.4.2_21-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2_21"
Java(TM) Platform, Standard Edition for Business (build 1.4.2_21-b03)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_21-b03, mixed mode)
Import Monitor jobs: running 1, waiting 1, completed 26, failed 0, total 28.
Loading of 'DD03L' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28.
ERROR 2009-08-12 10:22:25.718
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2009-08-12 10:22:25.734
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|8|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR ( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.).
any idea
Regards
ABH

hi
All logs are above (include import_monitor.log and java)
thanks

Import tables with nested table : ORA-00600

In Oracle 9.2
Create object, type as table, and table with nested table (store as syms_ntab) are successfully.
Also its export.
In process of import on another server (also 9.2, 'fromuser=one touser=two') shows errors:
. . importing table "SYMS_NTAB"
IMP-00058: ORACLE error 600 encountered
ORA-00600: internal error code, arguments: [kokeeafi1], [2], [2], [], [], [], [], []
IMP-00075: Warning: The nested table may contain partial rows or duplicate rows
But for all that table is created and error occur on phase inserting strings.
What is this?
In Oracle 8.0.5 i perform similar operation without error.

From Oracle error messages and codes manual:
ORA-00600 internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]
Cause: This is the generic internal error number for Oracle program exceptions. It indicates that a process has encountered a low-level, unexpected condition. Causes of this message include:
* timeouts
* file corruption
* failed data checks in memory
* hardware, memory, or I/O errors
* incorrectly restored files
The first argument is the internal message number. Other arguments are various numbers, names, and character strings. The numbers may change meanings between different versions of Oracle.
Action: Report this error to Oracle Support Services after gathering the following information:
* events that led up to the error
* the operations that were attempted that led to the error
* the conditions of the operating system and databases at the time of the error
* any unusual circumstances that occurred before receiving the ORA-00600 message
* contents of any trace files generated by the error
* the relevant portions of the Alter files
Note: The cause of this message may manifest itself as different errors at different times. Be aware of the history of errors that occurred before this internal error.

ORA-01555: table Re-org

Hi,
While doing Re-org ,we getting Ora-01555.We using 11g.
Alter table CMAR.HISTT move;
ERROR at line 1:
ORA-01555: snapshot too old: rollback segment number 85 with name "_SYSSMU85_4050276716$" too small.
Can we restart again?
Thanks

user13809017 wrote:
Hi,
While doing Re-org ,we getting Ora-01555.We using 11g.
Alter table CMAR.HISTT move;
ERROR at line 1:
ORA-01555: snapshot too old: rollback segment number 85 with name "_SYSSMU85_4050276716$" too small.
Can we restart again?I give up.
Can you?
I would expect the same error as log as DML occurs against CMAR.HISTT table

Diagnosing ORA-01555: what table had the unreconstructable block?

We have some very long-running batch processes (i.e. > 20 hours for a single INSERT statement) and we sometimes get ORA-01555 (snapshot too old) failures. Our undo_retention is 10800 seconds=3 hours.
We have discussed (with the development team) the combination of events that are needed for this situation to arise. They are unable to think of a situation where any of the tables (in today's incident, there are 7 of them) would have been updated after this job started.
Is there a method for analyzing the trace file to determine which table had the block that could not be reconstructed due to overwritten UNDO? This might give us ideas for how to avoid this via operational changes (i.e. changing the job schedule).
Of course, we are also pursuing tuning efforts for this query.
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bi
PL/SQL Release 10.2.0.5.0 - Production
CORE 10.2.0.5.0 Production
TNS for Solaris: Version 10.2.0.5.0 - Production
NLSRTL Version 10.2.0.5.0 - Production
Thanks,
Mike

Well you could still check to see if there are any uncommitted transactions for those tables:
Query the DBA_DML_LOCKS view (and/or DDL view)
http://docs.oracle.com/cd/E11882_01/server.112/e25513/statviews_3157.htm
select * from DBA_DML_LOCKS
SESSION_ID,OWNER,NAME,MODE_HELD,MODE_REQUESTED,LAST_CONVERT,BLOCKING_OTHERS
10,SCOTT,EMP_READ_ONLY,Row-X (SX),None,1163,Not Blocking
69,SCOTT,EMP_READ_ONLY,Row-X (SX),None,1648,Not Blocking
That shows that two session are holding exclusive row lock on the EMP_READ_ONLY TABLE. As a test I inserted a row from two different sessions but did NOT commit it yet.
The DDL version of the view can be used in addition.
See my reply Sep 4, 2013 12:23 AM in this thread from yesterday for more info.
https://forums.oracle.com/message/11174417#11174417
At least in 10g you can tell before you start if there are any issues to resolve. If there are no issues then once you start your query there won't be any issues that could cause the snapshot problem since your query will be first in line.

Why ORA-01555 (Snapshot too old) occures on an unchanged table

Hello,
we have to add a not null column into a large table. The simple update is not good, due to UNDO space.
alter table T add F INTEGER default 0 not null;
ORA-30036: unable to extend segment by in undo tablespace ''It is OK. (We cannot use create + insert + drop + rename due to not enough free space. The table is not partitioned current) So we try this script:
--create the column without default and not null
alter table T add F INTEGER;
--create temp table with the rowids of T (nologging -> minimal log)
create table TMP (row_id rowid) nologging;
--save the rowid-s. (direct -> minimal undo usage)
insert /*+APPEND*/ into TMP(row_id) select rowid from T;
commit;
--the "insert method"
--set the column to "0" with frequently commit
declare
i integer := 0;
commit_interval integer := 10000;
begin
for c in (select * from TMP) loop
    update T set F=0 where rowid=c.row_id;
    i := i + 1;
    if( mod(i,commit_interval)=0) then commit;
    end if;
end loop;
commit;
end;
--set to not-null
alter table T modify F default 0 not null;
--drop the temp table
drop table TMP;the insert method occures
ORA-01555: Snapshot too old (in row 5)The row 5 is the cursor "select * from TMP" in the insert method. The undo usage of this method is below 2 MB.
My question is:
Why oracle need snapshot, while the TMP table does not change during the insert method? The TMP table was populated and commited before the insert method. Why oracle try to read the rows of the TMP table from the undo tablespace?
Thx: lados.

Thank, I have read this article, but there is something, what I don't understand.
As I see, the DML does not clear all the modified datablock header, but it clears only the rollback segment slots. Only the next SQL (even if this is a query) clears the datablock header. This next SQL can clear only when the info is still available in the rollback segment, else ORA-1555 occures.
My question is:
What happens when the next SQL comes only one year later on this block? I don't believe that oracle doesn't handle this situation, but I didn't find how it is handled.
Thx: lados.

Expdp fails with ORA-31693, ORA-02354 and ORA-01555

Hi,
Oracle Database 10.2.0.4.0, Windows Server 2003
I was doing a full database DATA PUMP export as follow:
expdp system/pass@SID FULL=y DIRECTORY=MY_EXPORT DUMPFILE=EXPORT_DB.dmp logfile=EXPORT_DB.log
It always worked fine but today I received an error message :
ORA-31693: Table data object "S"."TABL1" failed to load/unload and is being skipped due to error:
ORA-02354: error in exporting/importing data
ORA-01555: snapshot too old: rollback segment number 10 with name "_SYSSMU10$" too small
The undo_retention parameter is set to its default of 900 currently.
Datafile in UNDO tablespace is 5GB used and this datafile is autoextend up to 32GB.
Any idea of what may causes this error ?
Thanks!

This happens only with the two largest tables which are around 11GB.
Today I do several times export, but always with one error.
First time error with one table, second time with another table... Everything else is exported without errors.

Ora-01555 when export DB on RAC 11GR2

Hi all,
I run a full export on my 11GR2 DB and i have 6 errors on sysman tables :
ORA-31693: Table data object "SYSMAN"."MGMT_POLICY_ASSOC_EVAL_SUMM" failed to load/unload and is being skipped due to error:
ORA-02354: error in exporting/importing data
ORA-01555: snapshot too old: rollback segment number 21 with name "_SYSSMU21_2772229671$" too small
Do you have an idea ?
Thanks.

$ oerr ora 1555
01555, 00000, "snapshot too old: rollback segment number %s with name \"%s\" too small"
// *Cause: rollback records needed by a reader for consistent read are
// overwritten by other writers
// *Action: If in Automatic Undo Management mode, increase undo_retention
// setting. Otherwise, use larger rollback segmentsIf you increase undo_retention parameter you may also need to increase undo tablespace datafiles.

ORA-01555: snapshot too old error while ANALYZE command!!!

Hi All,
I have 2-node 10gR2 RAC on RHEL4. The database is working fine. And i am able to import the schema also. But when i try to analyze all the tables in schema..i'm getting the following error...my undo_tablespace is of 1.2GB in both instances of RAC. and unde_retention is set to 900 (default).
ORA-01555: snapshot too old: rollback segment number with name "" too small
Please, can anybody tell me what might be the problem?
Thanks
Praveen.

Hi,
When the analyze of the table is going on, lot of dml activity is also going on to the table. So run the analyze when there is minimal dml activity on the table. Increase undo_tablespace,undo_retention might help your scenarios.
10g has got guaranteed undo retention, you can also use that.
Regards,
Satheesh Babu.S
http://www.satheeshbabus.blogspot.com

11gR2 Data Pump. Import table in one schema into a different schema

I stady oracle. I export shema HR into file hrexport.dmp. When I import tables from this file I had trouble. I used Enterprise Manager:
1. connected by user SYSTEM as NORMAL
2. selected file, chosen import type - tables
3. data from file was imported
4. chosen tables which tables to import
5. in the next step I try insert row in table Re-Map Shemas and edit cell Destination Shema, but in the list is only one name of shema - HR! Why?
Edited by: alvahtin on 10.03.2013 6:11

Paul M. wrote:
Did you try using impdp command at OS prompt ?I don't know what this command use. I try:
impdp system/oracle remap_schema=hr:inventory tables=employees, departments, locations directory=ORACLES_HOME dumpfile=hrexport.dmp logfile=hrimport.log
But it finished with error:
ORA-39166: Object SYSTEM.EMPLOYEES was not found.
ORA-39166: Object SYSTEM.DEPARTMENTS was not found.
ORA-39166: Object SYSTEM.LOCATIONS was not found.
Job "SYSTEM"."SYS_IMPORT_TABLE_01" successfully completed at 18:43:19
Job "SYSTEM"."SYS_IMPORT_TABLE_01" successfully completed at 18:43:19
Why SYSTEM? I want import to INVENTORY from HR - replaced in the file hrexport.dmp

Getting error while importing tables

Hi,
I have the servers on linux box and clients are installed on my local machine. I have created on DSN for connecting Biserver.
When i'm trying to import tables i am getting an error.
I have placed tns entries in Linux box as mentioned below path.
OBIEE/Oracle_BI1/network/admin
But even though i am not able to import table getting an error.. 'Connection fail'
Regards,
Mall

Since you are using client to import table is it not required in local for tnsnames.ora?
For server you have set that helps after hosting the rpd file, I hope you are not using online mode to import table if you are doing that I dont think that will work...
Try to use your connection details something like below
Call Interface: Default (OCI 10g/11g)
Data source Name->localhost:1521/XE
If helps mark or else let us know your basic test to connect to database like tnsping from command etc..

Error while importing table having ctxcat index

Hi
I created a table and ctxcat index on the same. I exported the same. While importing, table got imported but for index creation it gave error imp-00017 with ora-29855.
Though the index have been created but with some errors. I can see the index in all_indexes table but if i try to see the entry in dba_segments, record is not found.
Seems that index is not created properly.
Pls suggest ASAP.
Regards
Rajiv

What's your source and target Oracle version ?
1) make sure context option is installed on target DB
2) create a user ctxsys, the schema where the context related objects resides

Error in import table data using oracle datapump

i am trying to import table data using oracle datapump
CREATE TABLE emp_xt (
ID NUMBER,
NAME VARCHAR2(30)
ORGANIZATION EXTERNAL (
TYPE ORACLE_DATAPUMP
DEFAULT DIRECTORY backup
LOCATION ('a.dmp')
it return the following error
ORA-29913: error in executing ODCIEXTTABLEOPEN callout
ORA-29400: data cartridge error
KUP-04084: The ORACLE_DATAPUMP access driver does not support the ROWID column.
ORA-06512: at "SYS.ORACLE_DATAPUMP", line 19
please help me

.dmp file generated from exp command file not from oracle_datapump

***Unable to import table which consists of nested tables

Dear all;
I have a problem on migrating my Oracle 8.1.7 database from windows nt environment into the ibm aix 4.3.3 environment. I have been using the import export utility. Exporting the data from the database does not produce any error but importing the export file produces the error as below;
Connected to: Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
With the Partitioning option
JServer Release 8.1.7.0.0 - Production
Export file created by EXPORT:V08.01.07 via conventional path
import done in WE8ISO8859P1 character set and WE8ISO8859P1 NCHAR character set
. importing IIMS's objects into IIMS
IMP-00017: following statement failed with ORACLE error 2331:
"CREATE TABLE "CMGC_CURRENCY" ("CODE" VARCHAR2(10) NOT NULL ENABLE, "DESCP" "
"VARCHAR2(60) NOT NULL ENABLE, "X_RATE" NUMBER(10, 6) NOT NULL ENABLE, "X_DA"
"TE" VARCHAR2(10), "REMARK" VARCHAR2(255), "YEAR" NUMBER(4, 0) NOT NULL ENAB"
"LE, "BANK_AC" VARCHAR2(20) NOT NULL ENABLE, "NSTBL_LEDG" "NSTBL_LEDGLIST" N"
"OT NULL ENABLE, "NSTBL_XRATE" "NSTBL_XRATELIST" NOT NULL ENABLE) PCTFREE 1"
"0 PCTUSED 40 INITRANS 1 MAXTRANS 255 LOGGING STORAGE(INITIAL 65536) TABLESP"
"ACE "IIMS" NESTED TABLE "NSTBL_LEDG" STORE AS "NSTBL_LEDGLIST_LIST" RETURN "
"AS VALUE NESTED TABLE "NSTBL_XRATE" STORE AS "NSTBL_XRATELIST_LIST" RETURN"
" AS VALUE "
IMP-00003: ORACLE error 2331 encountered
ORA-02331: cannot create constraint on column of datatype Named Table Type
Import terminated successfully with warnings.
It seems that the error only occur when importing tables which consists on nested tables. I have done exporting and importing from windows NT into windows NT and from windows NT into AIX but the problem still arises. Please help.
NSTBL_LEDG and NSTBL_XRATE are the nested tables with NSTBL_LEDGLIST and NSTBL_XRATELIST as the datatype accordingly.
Thanks in advance;
andrew

Hi Sayak,
This means we need to installed Oracle client to resolve this problem. Can you please share if you have some knowledge regarding the same.
Thanks,
Mohit

ORA-01555 in importing table

Similar Messages

Maybe you are looking for