Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

When i export Oracle data by R3load I got the error for LOB table.

Dear all.

I got some error.

Version : oracle 10.2.0.2

Patch : Patch 5636728 : applied on Tue Apr 06 17:48:49 CEST 2010

Created on 15 Feb 2007, 21:35:47 hrs US/Pacific

Bugs fixed:

5636728

Patch 7237154 : applied on Tue Apr 06 13:51:09 CEST 2010

Created on 14 Aug 2008, 12:30:32 hrs PST8PDT

Bugs fixed:

4430244, 5752105, 6140309, 5558627, 5747462, 5376783, 6376915, 7237154

5212539, 7015250, 6455795, 5913430, 5386204, 5093837, 5667736, 6033289

5970301, 5245129, 6996749, 5959612, 6819785, 4771672, 6086497, 5728380

5657620, 5396550

-


Error log .

1. in the Export_monitor.java.log File

java version "1.4.2.12"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2.12-061213-02:03)

Java HotSpot(TM) 64-Bit Server VM (build 1.4.2 1.4.2.12-061213-10:06-IA64W IA64W, mixed mode)

Export Monitor jobs: running 1, waiting 0, completed 73, failed 0, total 74.

Unloading of 'SAPSSEXC_3' export package: ERROR

Export Monitor jobs: running 0, waiting 0, completed 73, failed 1, total 74.

2. in the Export_monitor.log File

TRACE: 2010-04-06 15:27:59 com.sap.inst.migmon.LoadTask processPackage

Unloading of 'SAPSSEXC_3' export package from database:

/usr/sap/EDE/SYS/exe/run/R3load -e SAPSSEXC_3.cmd -datacodepage 4102 -l SAPSSEXC_3.log -stop_on_error

ERROR: 2010-04-06 15:28:01 com.sap.inst.migmon.LoadTask run

Unloading of 'SAPSSEXC_3' export package is interrupted with R3load error.

Process '/usr/sap/EDE/SYS/exe/run/R3load -e SAPSSEXC_3.cmd -datacodepage 4102 -l SAPSSEXC_3.log -stop_on_error' exited with return code 2.

For mode details see 'SAPSSEXC_3.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

INFO: 2010-04-06 15:28:29

All export packages are generated.

INFO: 2010-04-06 15:28:29

All export packages are processed.

WARNING: 2010-04-06 15:28:29

1 error(s) during processing of packages.

INFO: 2010-04-06 15:28:29

Export Monitor is stopped.

3. in the SAPSSEXC_3 log file.

(RTF) ########## WARNING ###########

Without ORDER BY PRIMARY KEY the exported data may be unusable for some databases

DbSl Trace: ORA-01555 occurred when reading from a LOB

(EXP) ERROR: DbSlLobGetPiece failed

rc = 99, table "DYNPSOURCE"

(SQL error 1555)

error message returned by DbSl:

ORA-01555: snapshot too old: rollback segment number with name "" too small

ORA-22924: snapshot too old

(DB) INFO: disconnected from DB

/usr/sap/EDE/SYS/exe/run/R3load: job finished with 1 error(s)

/usr/sap/EDE/SYS/exe/run/R3load: END OF LOG: 20100406152801

To solve , the following actions was performed..

alter table DYNPSOURCE modify lob (FIELDINFO) (pctversion 100);

alter table DYNPSOURCE modify lob (LOGICINFO) (pctversion 100);

alter table DYNPSOURCE modify lob (EXTENSIONS) (pctversion 100);

alter table DYNPSOURCE modify lob (FIELDINFO) (retention);

alter table DYNPSOURCE modify lob (LOGICINFO) (retention);

alter table DYNPSOURCE modify lob (EXTENSIONS) (retention);

alter system set undoautotune='FALSE';

alter system set undo_retention=65000;

But I still have the problem. How can i fix it.

If you have experienc as same problem. please share the solution.

Thanks.

Former Member
replied

Hello Lucas,

at first a question to Eric.

I am pretty surprised, that everybody points Lucas to the size of PSAPUNDO. How do you come to this conclusion, in case of such an error case (without the undo segment name) and no massive undo generation in the system (which is the case by R3load export).

@ Lucas:

I still disagree and would take a look at the corruption, because of the errors are still pointing to this issue.

> It's very strange due to there is no error in alert log file. generally, this error must be written the error in the alert log file.

No, in general not. If every ORA error would be logged in the alert log file - holy cow.

Did you really run the SQL that was mentioned in the sapnote #983230 or metalink note #452341.1 with all its commands (for example the "set serverout on" is very important) and for every LOB field?

What does the SAP support said?

I am not sure what's exactly stored in DYNPSOURCE - if only the compiled code is stored in there, you maybe can recreate it .. but i am not sure.

Regards

Stefan

0 View this answer in context

Helpful Answer

by
Not what you were looking for? View more on this topic or Ask a question