Import Abap - Canceled Erp 6.0

[Former Member]

Hi,

I`m installing Erp 6.0 on Oracle 11g and AIX 7 , while ABAP Import phase is running the installation is stopped, when I returned the installation I had the following errors in the same phase import abap.

"

/usr/sap/GMD/SYS/exe/run/R3load: START OF LOG: 20130130120919

/usr/sap/GMD/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
/usr/sap/GMD/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]
Compiled Jan 23 2008 21:47:44
/usr/sap/GMD/SYS/exe/run/R3load -ctf I /medios/erp6.0/export/51033500_1/EXP1/DATA/SAPSSEXC.STR /tmp/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/DDLORA.TPL SAPSSEXC.TSK ORA -l SAPSSEXC.log

/usr/sap/GMD/SYS/exe/run/R3load: job completed
/usr/sap/GMD/SYS/exe/run/R3load: END OF LOG: 20130130120919

/usr/sap/GMD/SYS/exe/run/R3load: START OF LOG: 20130130120919

/usr/sap/GMD/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
/usr/sap/GMD/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]
Compiled Jan 23 2008 21:47:44
/usr/sap/GMD/SYS/exe/run/R3load -i SAPSSEXC.cmd -dbcodepage 4102 -l SAPSSEXC.log -stop_on_error

DbSl Trace: ORA-1403 when accessing table SAPUSER

(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
(DB) ERROR: DDL statement failed
(CREATE TABLE "AAB_ID_PROP" ( "NAME" VARCHAR2(90) DEFAULT ' ' NOT NULL , "DEF_MODE" NUMBER(3) DEFAULT 0 NOT NULL  ) TABLESPACE PSAPSR3700 STORAGE (INITIAL 25278 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

/usr/sap/GMD/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/GMD/SYS/exe/run/R3load: END OF LOG: 20130130120919

/usr/sap/GMD/SYS/exe/run/R3load: START OF LOG: 20130130122327

/usr/sap/GMD/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
/usr/sap/GMD/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]
Compiled Jan 23 2008 21:47:44
/usr/sap/GMD/SYS/exe/run/R3load -i SAPSSEXC.cmd -dbcodepage 4102 -l SAPSSEXC.log -stop_on_error

DbSl Trace: ORA-1403 when accessing table SAPUSER

(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
(DB) INFO: AAB_ID_PROP dropped #20130130122327

(DB) INFO: AAB_ID_PROP created #20130130122327

(IMP) INFO: import of AAB_ID_PROP completed (750 rows) #20130130122327

(DB) INFO: AAB_ID_PROP~0 created #20130130122327

(DB) ERROR: DDL statement failed
(CREATE TABLE "AAB_ID_PROPT" ( "LANGU" VARCHAR2(3) DEFAULT ' ' NOT NULL , "NAME" VARCHAR2(90) DEFAULT ' ' NOT NULL , "DESCRIPT" VARCHAR2(240) DEFAULT ' ' NOT NULL  ) TABLESPACE PSAPSR3700 STORAGE (INITIAL 128721 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

/usr/sap/GMD/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/GMD/SYS/exe/run/R3load: END OF LOG: 20130130122327

/usr/sap/GMD/SYS/exe/run/R3load: START OF LOG: 20130130122640

/usr/sap/GMD/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
/usr/sap/GMD/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]
Compiled Jan 23 2008 21:47:44
/usr/sap/GMD/SYS/exe/run/R3load -i SAPSSEXC.cmd -dbcodepage 4102 -l SAPSSEXC.log -stop_on_error

DbSl Trace: ORA-1403 when accessing table SAPUSER

(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
(DB) INFO: AAB_ID_PROPT dropped #20130130122640

(DB) INFO: AAB_ID_PROPT created #20130130122640

(IMP) INFO: import of AAB_ID_PROPT completed (1488 rows) #20130130122640

(DB) INFO: AAB_ID_PROPT~0 created #20130130122640

(DB) ERROR: DDL statement failed
(CREATE TABLE "BRATEXT" ( "SPRSL" VARCHAR2(3) DEFAULT ' ' NOT NULL , "BRANCHE" VARCHAR2(15) DEFAULT ' ' NOT NULL , "TABNAME" VARCHAR2(90) DEFAULT ' ' NOT NULL , "FELDNAME" VARCHAR2(90) DEFAULT ' ' NOT NULL , "VBRKZ" VARCHAR2(3) DEFAULT ' ' NOT NULL , "LFDNR" VARCHAR2(30) DEFAULT '0000000000' NOT NULL , "KEYINH" RAW(255) , "TEXTBRAN" VARCHAR2(396) DEFAULT ' ' NOT NULL , "TEXTSAP" VARCHAR2(396) DEFAULT ' ' NOT NULL , "TXTVB" VARCHAR2(6) DEFAULT ' ' NOT NULL , "DEVCLASS" VARCHAR2(90) DEFAULT ' ' NOT NULL , "FELDLNG" VARCHAR2(9) DEFAULT '000' NOT NULL , "BRANREL" VARCHAR2(9) DEFAULT ' ' NOT NULL  ) TABLESPACE PSAPSR3700 STORAGE (INITIAL 16384 NEXT 0000010240K 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

/usr/sap/GMD/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/GMD/SYS/exe/run/R3load: END OF LOG: 20130130122640

/usr/sap/GMD/SYS/exe/run/R3load: START OF LOG: 20130130122734"

• I applied this note: Note 455195 - R3load: Use of TSK files
• I changed the number proccess and sessions in oracle

          SQL> alter system set PROCESSES=200 scope=SPFILE;
          SQL> alter system set SESSIONS=500 scope=SPFILE;

• I uninstalled and Install again but I have the same error.
• I had installed succesfully with these file systems 

• /sapmnt

  /usr/sap/GMD

  /usr/sap/trans

  /oracle

  /oracle/client

  /oracle/stage/112_64

  /oracle/GMD

  /oracle/GMD/11203

  /oracle/GMD/origlogA

  /oracle/GMD/origlogB

  /oracle/GMD/mirrlogA

  /oracle/GMD/mirrlogB

  /oracle/GMD/oraarch

  /oracle/GMD/sapreorg

  /oracle/GMD/sapdata1

  /oracle/GMD/sapdata2

  /oracle/GMD/sapdata3

  /oracle/GMD/sapdata4

• But I removed these and I created only 2 file system for oracle

• /oracle

  /oracle/GMD

• I dont know if this is the reason the errors , Will I create again the others file systems ?
• When I retry the file SAPSSEXC.TSK changes with more OK

Please your help

Thanks and regards

Graciela T

[volker_borowski2 · Accepted solution]

Hello,

stopp hunting the wrong rabbit.

This error (SAPUSER / ORA-1403) is completely normal during the installation,

because the table is not set up then.

Check your  SAPSSEXC log:

DbSl Trace: ORA-1403 when accessing table SAPUSER

(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
(DB) INFO: AAB_ID_PROPT dropped #20130130122640

(DB) INFO: AAB_ID_PROPT created #20130130122640

(IMP) INFO: import of AAB_ID_PROPT completed (1488 rows) #20130130122640

As you see, you get the SAPUSER error, but R3load continues, creates and loads a table.

Everything is ok.

The -955 has to be related elsewhere (No idea about this one).

I just did an installation last week, that was completely successfull and

EVERY SAP*.log file had this SAPUSER error.

Volker

[Former Member · Accepted solution]

Hi,

thanks for your help, It was a network problem , the error was fixed.

Regards

Graciela

[Reagan]

Hello

Can you try to drop those tables if they are present ?

Else go through this note.

Note 89677 - ORA-955 for R/3 installation

This note is not relevant for your release but just check whether it helps you.

Cheers

RB

[Former Member]

Hi Reagan,

I checked into database, the table SAPUSER is empty , I inserted this field

INSERT INTO "OPS$GMPADM".SAPUSER VALUES ('GMP', 'gmppas30');

but doesn`t work, I'm not sure if sapowner is correct

Regards

Graciela

[Reagan]

Hello Graciela

The insert statement isnt correct.

Please correct it by referring to the following example.

Eg:

insert into OPS$<SID>ADM.SAPUSER values ('SAPSR3', 'P@s5w0rD');

By the way there is an SAP Note that carries a script to create the OPS$ users.

Please check it in SMP.

Cheers

RB

[Former Member]

Hi,

Check the owner of SAPUSER table with the following command on DB level. It should show OPS$GMPADM

SELECT OWNER FROM DBA_TABLES WHERE TABLE_NAME = 'SAPUSER';

Change password for SAPSR3 via BRTOOLS and see if it is updated in SAPUSER table

Give connect and resource to OPS$GMPADM by the following command

GRANT CONNECT, RESOURCE TO "OPS$GMPADM";

Ensure R3trans -d is working fine.

Regards,

Sohrab Kapoor

[Former Member]

Hi,

    Sometime, this kernel  bug issue might occur.

To check the issue. Please try this.

1.login to the system as orasid.

2.sqlplus "/as sysdba"

3. execute desc <your sapschema ID>.BRATEXT

4. If you can see the tables created then you open  SAPSSEXC.TSK  file and change the err to ign

5. Dont retry the sapinst.

6. Stop the installation and contine with old installation.

This will fix the issue.

I have faced this issue has occurred manytimes for me and i have fixed in this way.

Thanks and Regards,

Vimal

[Former Member]

As well as I would suggest you to try with the latest kernel and its patch.

Thanks and Regards,

Vimal

[Former Member]

hi Vimal,

I checked in the database but  I can`t see these tables

Do you have another suggestion ?

Best regards

Graciela

[Former Member]

Hi,

   Please make sure you are using correct schema ID and its table name. If you entered just the table name, it wont show you. It will says table doesnt exist .

So I would suggest you to check  whether you are entering the correct schema ID.

If possible, can you please share us the output you got .

As well as please execute select username from dba_users  ;

and paste the results too.

Thanks and Regards,

Vimal

[Former Member]

Hi Vimal

this is the result of select

1488 rows selected.

SQL> SELECT * FROM SAPSR3.D010INC;      in the file is err

no rows selected

SQL> select username from dba_users;

USERNAME
------------------------------
OPS$GMPADM
OPS$SAPSERVICEGMP
OPS$ORAGMP
SYS
SYSTEM
SAPSR3
OUTLN
ORACLE_OCM
DIP
APPQOSSYS
DBSNMP

11 rows selected.

SQL> SELECT * FROM SAPSR3.AAB_ID_PROPT         in the file is OK

[Former Member]

Hi,

   Can you please attach the latest  SAPSSEXC.TSK file ?

As well as please attach the SAPSSEXC.log . From the output you gave, the error you have updated seems to be old or not correct.

Please attach the latest file .

Thanks and Regards,

Vimal

[Reagan]

Good Day

This is what I could see.

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

It looks like the objects are already present.

Also check this:

DbSl Trace: ORA-1403 when accessing table SAPUSER

Please check whether the SAPUSER table has entries. If not follow this note.

Note 400241 - Problems with ops$ or sapr3 connect to Oracle

Cheers

RB

[Former Member]

Hi Regan

I applied this note but I the error continue

Please your help

Graciela

[former_member188883]

Hi Graciela,

It seems your installation is not clean. I suggest you to un-install existing setup. Clean up all the filesystems. Install a fresh OS and repeat the installation again with only 2 file systems as you mentioned above. It should go clean.

Regards,

Deepak Kori

[Former Member]

Hi,

thanks for your response, I installed in another server, its the first installation on this server, but I have the same error.

Do you have another suggestion ?

best regards

Graciela