Skip to Content
avatar image
Former Member

ORA-00942 Error during unicode export of BI 7.0

Hello Everyone,

I am doing an export of a non-unicode BI 7.0 system to convert and import it into a Unicode database. All the jobs have passed except one and I see the following error in the log file (SAPAPPL0_3.log)

/usr/sap/ABD/SYS/exe/run/R3load: START OF LOG: 20080302124247

/usr/sap/ABD/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP

/usr/sap/ABD/SYS/exe/run/R3load: version R7.00/V1.4

Compiled Jun 9 2007 09:20:06

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

(DB) INFO: connected to DB

(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC

(RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)

(RSCP) WARN: UMGCONTAINER has 1 problems.

(RSCP) INFO: UMGSETTINGS nametab creation: ok.

(RSCP) INFO: Global fallback code page = 1100

(RSCP) INFO: Common character set is not 7-bit-ASCII

(RSCP) INFO: Collision resolution method is 'fine'

(RSCP) INFO: R3trans code pages = Normal

(RSCP) INFO: EXPORT TO ... code pages = Normal

(RSCP) INFO: Check for invalid language keys: active, by default

(RSCP) INFO: I18N_NAMETAB_NORM_ALLOW = 999999999

(RSCP) INFO: I18N_NAMETAB_NORM_LOG = 1000000002

(RSCP) INFO: I18N_NAMETAB_ALT_ALLOW = 10000

(RSCP) INFO: I18N_NAMETAB_ALT_LOG = 10003

(RSCP) INFO: I18N_NAMETAB_OLD_ALLOW = 0

(RSCP) INFO: I18N_NAMETAB_OLD_LOG = 500

(GSI) INFO: dbname = "ABD20070922100908

"

(GSI) INFO: vname = "ORACLE "

(GSI) INFO: hostname = "ussbbdd5 "

(GSI) INFO: sysname = "HP-UX"

(GSI) INFO: nodename = "ussbbdd5"

(GSI) INFO: release = "B.11.23"

(GSI) INFO: version = "U"

(GSI) INFO: machine = "ia64"

(GSI) INFO: instno = "INITIAL "

(EXP) ERROR: DbSlExeRead failed

rc = 103, table "/BIC/SZTERR_CD"

(SQL error 942)

error message returned by DbSl:

ORA-00942: table or view does not exist

(DB) INFO: disconnected from DB

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

/usr/sap/ABD/SYS/exe/run/R3load: END OF LOG: 20080302124251

When I run the following command on /BIC/SZTERR_CD, I do not get any table information back. I am not sure how to fix it though.

SELECT * FROM DBA_OBJECTS WHERE OBJECT_NAME = '/BIC/SZTERR_CD ';

I did finish all the unicode preconversion steps and also ran the SMIGR_CREATE_DDL program. I had exported recently from the same system but I never got this error during that run.

Another question is about the order in which the steps need to be performed. I completed the preconversion steps, then ran the SMIGR_CREATE_DDL program before proceeding to the export phase. Is this right or does it not matter?

Thanks again for your help!

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

4 Answers

  • Best Answer
    avatar image
    Former Member
    Mar 03, 2008 at 06:40 AM

    Hi Stacy,

    You need to create the DB table in SE14, and repeat the export process in the source system.

    Regrads,

    Nahum

    Add comment
    10|10000 characters needed characters exceeded

  • Mar 04, 2008 at 09:34 AM

    is there any line in the R3szchkExport.log similar to this:

    > WARNING: check_size: table BIC/SZTERR_CD not in DB

    you should have checked this BEFORE starting the export...also check if there still exist any NAMETABs within SAP for object BIC/SZTERR_CD using transaction SE37 -> DD_SHOW_NAMETAB; if found, you should delete this nametab (using SE37 -> DD_NAMETAB_DELETE) and redo the (complete) export - which would be the safest way...

    GreetZ, AH

    Add comment
    10|10000 characters needed characters exceeded

  • Mar 02, 2008 at 06:56 PM

    Hello Stacy,

    > When I run the following command on /BIC/SZTERR_CD, I do not get any table information back. I am not sure how to fix it though.

    > SELECT * FROM DBA_OBJECTS WHERE OBJECT_NAME = '/BIC/SZTERR_CD ';

    If the object does not exists on the source target database, please check if the ddic of sap still contains the table definition. (SE11 or SE14)

    If yes you can set the status of the table /BIC/SZTERR_CD to "ok" in the corresponding task file.

    You can not fix this problem in other way after you have started the conversion, because of the export files are already generated (with the information of the sap ddic)...

    > I completed the preconversion steps, then ran the SMIGR_CREATE_DDL program before proceeding to the export phase. Is this right or does it not matter?

    That was the right way.

    Regards

    Stefan

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Mar 04, 2008 at 04:31 PM

    Hello guys,

    Thanks for your replies. I found all the three replies very useful. This problem is solved now, here's what I did

    The table did not exist at the DB level, but it did exist in DDIC. So I just created the same in SE14 and the export continued.

    Thanks again for the prompt replies.

    Cheers,

    Stacy

    Add comment
    10|10000 characters needed characters exceeded