ABAP Import error "DDL statement failed" and "ORA-00955"

[Former Member]

Hi experts.

In DB Instance Installation with R3load, I'm facing some import errors.
ABAP import stop due to them.

I faced similar errors in this import, before this error related  to SAPAPPL0.

For example the error of SAPSDIC. (with same error massages .)

However, after I tried "Retry" they're solved.

According to ".TSK file", after I click "Retry" button in the sapinst  window, the ABAP import is restarted  and proceed a little.
However, in this time, the import stop soon after that.

Could someone help me to solve is problem, plsease?

Below are error messages
==================================
<sapinst window  message>
An error occured while processing option SAP NetWeaver 7.0 Support Release 3 ･･･
Program Migration Monitor exits with error code 103.For more details see log file(s) import_monitor.java.log, import_monitor.log
 
<import_monitor.java.log>
Loading of 'SAPAPPL0' import package:ERROR
Import Monitor jobs:running 0, waiting 1, completed 26, failed1, total 28,

<import_monitor.log>
WARNING:YYYY-MM-DD hh:mm:ss
Cannot start import of packages with views because not all import packages with tables are loaded successfully.

WARNING:YYYY-MM-DD hh:mm:ss
1 error(s) during proccessing of packages.

INFO:YYYY-MM-DD hh:mm:ss
Import Monitor is stopped.
===================================

I also checked SAPAPPL0.log.

<SAPAPPL0.log>
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF16
(GSI) INFO: dbname   = "dbname(dummy)"                                                                                    "
(GSI) INFO: vname    = "ORACLE                          "
(GSI) INFO: hostname = "server hostname(dummy)"
(GSI) INFO: sysname  = "Linux"
(GSI) INFO: nodename = "nodename(dummy)"
(GSI) INFO: release  = "2.6.32-400.21.1.el5uek"
(GSI) INFO: version  = "#1 SMP Wed Feb 20 01:35:01 PST 2013"
(GSI) INFO: machine  = "x86_64"
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file /export_dir/ABAP/DB/SQLFiles.LST
(SQL) INFO: /export_dir/ABAP/DB/SQLFiles.LST not found
(SQL) INFO: Searching for SQL file APPL0.SQL
(SQL) INFO: APPL0.SQL not found
(SQL) INFO: Searching for SQL file /export_dir/ABAP/DB/ORA/APPL0.SQL
(SQL) INFO: /export_dir/ABAP/DB/ORA/APPL0.SQL not found
(DB) INFO: /1CN/STXSAPX0104 dropped #YYYYMMDDhhmmss
(DB) INFO: /1CN/STXSAPX0104 created #YYYYMMDDhhmmss
(IMP) INFO: import of /1CN/STXSAPX0104 completed (0 rows) #YYYYMMDDhhmmss
(DB) INFO: /1CN/STXSAPX0104~0 created #YYYYMMDDhhmmss
(DB) ERROR: DDL statement failed
(CREATE TABLE "/1CN/STXSAPX0105" ( "CLIENT" VARCHAR2(9) DEFAULT '000' NOT NULL , "VARNUMH" RAW(16) NOT NULL , "STFKZ" VARCHAR2(3) DEFAULT ' ' NOT NULL , "KZBZG" VARCHAR2(9) DEFAULT ' ' NOT NULL , "KUMZA" NUMBER(10) DEFAULT 0 NOT NULL , "KUMNE" NUMBER(10) DEFAULT 0 NOT NULL , "EXPNT" NUMBER(5) DEFAULT 0 NOT NULL , "MWSK1" VARCHAR2(6) DEFAULT ' ' NOT NULL , "MWSK2" VARCHAR2(6) DEFAULT ' ' NOT NULL , "KONMS" VARCHAR2(9) DEFAULT ' ' NOT NULL , "KONWS" VARCHAR2(15) DEFAULT ' ' NOT NULL , "KSTBM" NUMBER(18,5) DEFAULT 0 NOT NULL , "MEINS" VARCHAR2(9) DEFAULT ' ' NOT NULL , "KZNEP" VARCHAR2(3) DEFAULT ' ' NOT NULL , "MXWRT" NUMBER(15,2) DEFAULT 0 NOT NULL , "GKWRT" NUMBER(15,2) DEFAULT 0 NOT NULL , "PTERM" VARCHAR2(12) DEFAULT ' ' NOT NULL , "VALDT" VARCHAR2(24) DEFAULT '00000000' NOT NULL , "VALTG" VARCHAR2(6) DEFAULT '00' NOT NULL  ) TABLESPACE PSAPSR3  STORAGE (INITIAL 0000000016K NEXT 0000000040K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
DbSlExecute: rc = 102
  (SQL error 955)
  error message returned by DbSl:
ORA-00955: name is already used by an existing object
(DB) INFO: disconnected from DB
==================================================

[Reagan]

Hello

DbSlExecute: rc = 102
  (SQL error 955)
  error message returned by DbSl:
ORA-00955: name is already used by an existing object
(DB) INFO: disconnected from DB

This means there is already an object with the same name.

Open the TSK file for the SAPAPPL0 and check the status of the table /1CN/STXSAPX0105

Check whether the table SAPSR3./1CN/STXSAPX0105 is present at the database level.

Either modify the TSK file and retry in sapinst or drop the table SAPSR3./1CN/STXSAPX0105 and retry.

Regards

RB

[Former Member]

Thanks all,

Actually, there is already the table  /1CN/STXSAPX0105 in DB.
Before SAPAPPL0 import,  the one of SAPAPPL0_1 ran.

I think this is the reason that the table is already exist.

And I think that this existing table can occur import error.
But after SAPAPPL0_1 import executing, it  is quite natural that there is  the table.

In this case, should I delete existing  /1CN/STXSAPX0105?
If I delete  /1CN/STXSAPX0105 from database, are there any risks?

Best Regards,

Naomi Yamane

[former_member206552]

Hi Naomi,

As suggested by Regan, drop teh table and retry,

you can follow this link on how to drop a table

http://www.w3schools.com/sql/sql_drop.asp

drop table sapsr3.'/1CN/STXSAPX0105';

Best Regards
Marius

[ashish_vikas]

No, you should not delete table manually. And is that table empty ?

Can you please explain in details what you are doing.. system copy ? If yes, how did you performed package splitting ?

One table should not be part of 2 packages : SAPAPPL0 and SAPAPPL0_1.

Can you please share SAPAPPL0.TSK & SAPAPPL0_1.TSK file content for this table.

Best regards

ashish

[Former Member]

Hi Marius and ashish,

Thank you for your advices.

I explain more infomation.

■About what I'm doing now

Now I'm doing system copy. (SAP configuration : CI only to Distributed)

And now I'm in DB instance installation phase.

In the target DB server, there is another Oracle DB for another SAP system.

In this DB installation, I'm trying to install a new DB separately.

■About Export

Few days ago, I exported DB data with R3load from source CI's DB.

In this time, I used paralell export option, but didn't use one for split table.

And I'll tell you an additonal infomation,

before this expot, ddl statement were not generated by a job, SMIGR_CREATE_DDL.

■About TSK files

SAPAPPL0.TSK & SAPAPPL0_1.TSK　have same table.

I'll check more details of TSK file later.

If you know  some poitns to check carefully in them, could you tell me about it?

Best Regards,

Naomi Yamane

[ashish_vikas]

you need to see carefully why do you have same table in 2 packages !!

Check what happened at time of Export with files

SAPAPPL0.TSK & SAPAPPL0_1.TSK (for export) >> do you have same table 2 time here ?

SAPAPPL0.STR & SAPAPPL0_1.STR >> do you have same table 2 time here ? Did Package splitting worked fine ?

SAPAPPL0.LOG & SAPAPPL0_1.LOG (for export) >> Did this able(only this ?) got exported 2 times ?

best regards

ashish

[Former Member]

Hi,

You can try the below note .

1844436 - ORA-00955: name is already used by an existing object

This note is for the upgrade but we can try and see if the table has the owner and if the table is in the database.

If yes check if the table has entry and take backup then try to drop it and recreate it.

Or

Try to clear Oracle related issue (e.g. corruption or inconsitency in Oracle data dictionary)

Oracle related issue:

- flush the sharedpool with SQL>alter system flush shared_pool,

- restart the database to clear out the rowcache.

As per note.

1233860 - ORA-00955 "Name is already used by existing object"

Thanks

Rishi Abrol

[ashish_vikas]

Hi,

in SAPAPPL0.TSK what is the status for table /1CN/STXSAPX0105 ? If this is xeq, change this to err and retry.

best regards

ashish