Error while importing the database of Oracle 10.2g to MaxDB - DB Migration

[Former Member]

Hi,

We are testing the data migration from Oracle 10.2g to MaxDB 7.6. First i have exported the oracle database without any errors. But while importing to MaxDB i am getting error as below,

tail -f ImportMonitor.console.log

java.class.version = 49.0

java.home = /opt/java1.5/jre

java.ext.dirs = /opt/java1.5/jre/lib/ext

java.class.path = migmon.jar

java.library.path = /opt/java1.5/jre/lib/PA_RISC2.0W:/opt/java1.5/jre/lib/PA_RISC2.0W/server:/opt/java1.5/jre/../lib/PA_RISC2.0W:/tmp/sapinst_exe.18812.1291025270:/usr/sap/BE1/SYS/exe/run:/sapdb/programs/lib/lib64:/usr/lib

java.io.tmpdir = /var/tmp/

Import Monitor jobs: running 1, waiting 1, completed 72, failed 0, total 74.

Loading of 'SAPAPPL1_11' import package: ERROR

Import Monitor jobs: running 0, waiting 1, completed 72, failed 1, total 74.

And tail -f SAPAPPL1_11.log

(IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed

rc = 26, table "VBRK"

ERROR : Prepare/modify for GetPages failed(dbrc=26).

(SQL error 0)

error message returned by DbSl:

(DB) ERROR: DDL statement failed

(CREATE TABLE "VBRL" ( "MANDT" VARCHAR2(3) UNICODE DEFAULT '000' NOT NULL , "VBELN" VARCHAR2(10) UNICODE DEFAULT ' ' NOT NULL , "POSNR" VARCHAR2(6) UNICODE DEFAULT '000000' NOT NULL , "VBELN_VF" VARCHAR2(10) UNICODE DEFAULT ' ' NOT NULL , "NETWR" NUMBER(15,2) DEFAULT 0 NOT NULL , "MWSBP" NUMBER(13,2) DEFAULT 0 NOT NULL , "KWERT_RL" NUMBER(13,2) DEFAULT 0 NOT NULL , "MWSBP_RL" NUMBER(13,2) DEFAULT 0 NOT NULL , "KUNAG" VARCHAR2(10) UNICODE DEFAULT ' ' NOT NULL , "UVPRS" VARCHAR2(1) UNICODE DEFAULT ' ' NOT NULL , "LOGSYS" VARCHAR2(10) UNICODE DEFAULT ' ' NOT NULL ) NO FIXED LENGTH COLUMN )

DbSlExecute: rc = 102

(SQL error -955)

error message returned by DbSl:

I tried multiple time by modifying the loadArgs=-nolog -c 10000 -merge_bck . But still same error "(SQL error -955)"

Thanks,

Narendra

[Former Member]

Hi,

it is not astonishing that the error occurs every time you try this create table statement.

A table with this name already exists. And error -955 tells us exactly this.

What to do?

As I do not know if there is data in this table and/or if there are views / other database objects

using this table, I cannot decide, if dropping this table would be a good idea.

But what I do not understand is, why during one (?) loading in a clean (?) database this

table is tried to create more than once. Or was the database you are loading into not clean,

fresh and empty? Then it will happen that not only this table, but some others will result in an error

because they exist already.

Elke