CJS-00084 - ORA 955 while doing Migration/Installation using NW 6.40 kernel

[Former Member]

Dear Experts,

We need to migrate our ECC5 system from HP-Unix, Oracle 10.2.0.2 to Windows 2003(64 bit), Oracle 10.2.0.4. Oracle version 10.2.0.4 is installed using DVD 51036975. While using sapinst at the target win2003 server using NW 6.40, at Installation Phase 16 out of 32, i.e "Create Oracle database", I am getting the below error

ERROR 2010-09-17 18:00:02

CJS-00084 SQL statement or script failed.<br>DIAGNOSIS: Error message: ORA-955 for defaultdestSQL> Rem bnainani 11/29/00 - specify compatible=8.0 for create_queue_tableSQL> Rem liwong 10/20/00 - add def$_destination.flagSQL> Rem bnainani 11/15/00 - specify compatible=8.0 for queue tableSQL> Rem narora 09/13/00 - add comment on new def$_destination columnsSQL> Rem liwong 09/01/00 - add master w/o quiesce: fixesSQL> Rem liwong 07/12/00 - add total_prop_time_latSQL> Rem liwong 06/29/00 - add total_txn_count, total_prop_timeSQL> Rem liwong 05/17/00 - add_master_db w/o quiesceSQL> Rem jstamos 05/17/00 - add_master_db w/o quiesceSQL> Rem elu 01/24/00 - add column apply_init to def$_destinationSQL> Rem alakshmi 12/02/99 - Bug 979398: Before-row insert trigger onSQL> Rem def$_propagatorSQL> Rem wesmith 10/31/98 - change shape of table def$_pushed_transactionsSQL> Rem jnath 02/23/98 - bug 601972: split anonymous pl/sql blocksSQL> Rem wesmith 01/21/98 - create def$_pushed_transactions table forSQL> Rem server-side RepAPISQL> Rem nbhatt 07/27/97 - change create_queuetable -> create_queue_tableSQL> Rem nbhatt 04/21/97 - change 'TRACKING' in CREATE_QUEUE to 'DEPENDENCYSQL> Rem nbhatt 04/21/97 - change syntax of create_queueSQL> Rem liwong 04/16/97 - Alter view system.AQ$DEF$_AQ{CALL,ERROR}SQL> Rem liwong 04/11/97 - Fixing defaultdest_primary typoSQL> Rem jstamos 04/10/97 - remove unneeded indexesSQL> Rem nbhatt 04/08/97 - change create_qtable to create_queuetableSQL> Rem jstamos 04/04/97 - tighter AQ integrationSQL> Rem liwong 04/02/97 - Add schema_name, package_name in def$_calldestSQL> Rem ato 03/31/97 - create_qtable interface changeSQL> Rem liwong 03/25/97 - remove batch_no from def$_tranorderSQL> Rem liwong 02/24/97 - pctversion --> 0 for def$_aqcall, def$_aqerrorSQL> Rem liwong 02/22/97 - Remove dropping view aq$def$_aqcallSQL> Rem ademers 02/07/97 - Remove constraint def$_calldest_callSQL> Rem liwong 01/11/97 - drop and create aq$def$_aqcall (temporary)SQL> Rem liwong 01/10/97 - Alter view aq$def$_aqcallSQL> Rem liwong 01/07/97 - Alter default value for batch_noSQL> Rem jstamos 12/23/96 - change temp$nclob colSQL> Rem jstamos 11/21/96 - nchar supportSQL> Rem sjain 11/11/96 - Remove dummy buffer # commentSQL> Rem asgoel 11/05/96 - Disable misc_tracking in def$_aqerrorSQL> Rem sjain 11/06/96 - deferror changesSQL> Rem vkrishna 10/28/96 - change STORED IN to STORE AS for lobSQL> Rem sjain 10/02/96 - Aq conversionSQL> Rem sbalaram 09/24/96 - ARPC performance - add foreign key indexSQL> Rem jstamos 09/06/96 - rename temp$lob and temporarily change nclobSQL> Rem sjain 09/03/96 - AQ conversonSQL> Rem ademers 08/02/96 - queue_batch default in def_destinationSQL> Rem ademers 07/29/96 - queue_batch default in def_callSQL> Rem ademers 07/29/96 - queue_batch defaultSQL> Rem jstamos 07/24/96 - add system.temp$lobSQL> Rem sbalaram 07/22/96 - create def$_aqcall and def$_aqerror tablesSQL> Rem jstamos 06/12/96 - LOB support for deferred RPCsSQL> Rem ldoo 06/28/96 - Comment out queue_table from def_tranorderSQL> Rem ademers 05/30/96 - create def_originSQL> Rem ademers 05/28/96 - fix def_destination col namesSQL> Rem ldoo 05/09/96 - New security modelSQL> Rem sjain 05/01/96 - add seq col to def_destinationSQL> Rem ademers 04/29/96 - add batch_no, dep_scn to def_callSQL> Rem jstamos 12/04/95 - 324303: use index to avoid sorting the queueSQL> Rem jstamos 08/17/95 - code review changesSQL> Rem jstamos 08/16/95 - add comments to tablesSQL> Rem wmaimone 01/04/96 - 7.3 mergeSQL> Rem hasun 01/31/95 - Modify tables.<br>SOLUTION: See ora_sql_results.log and the Oracle documentation for details.

In some other posts, noticed using SAP Notes 972263 and 1094599 have helped for similar error message, but these are for Unix & NW 7.0 Prodcuts, while we are doing a migration/Installation using SAPNW 6.40 on Windows 2003 platform. Can anybody advice the solution for my scenario?.

Thanks & Rgds,

Abhishek

[former_member709110]

Hi,

Well it was really difficult to read anything from the log you have pasted . May be you can look at or paste the ora_sql_results.log , that way we might figure out the issue.

Regards,

Neel

[Former Member]

Hi Neel,

The log is close to 30 MB, so I am placing some errors for different objects being encountered.

SQL> CREATE TYPE kupc$_LobPieces AS VARRAY(4000) OF VARCHAR2(1000);

2 /

CREATE TYPE kupc$_LobPieces AS VARRAY(4000) OF VARCHAR2(1000);

*

ERROR at line 1:

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

SQL>

SQL> -- Table to contain filter list elements (e.g., TABLE list) on source

SQL> -- database during a network job.

SQL> CREATE GLOBAL TEMPORARY TABLE sys.ku$_list_filter_temp (

2 process_order NUMBER,

3 duplicate NUMBER,

4 object_name VARCHAR2(500),

5 base_process_order NUMBER )

6 ON COMMIT PRESERVE ROWS

7 /

CREATE GLOBAL TEMPORARY TABLE sys.ku$_list_filter_temp (

*

ERROR at line 1:

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

create table system.logstdby$parameters (

*

ERROR at line 1:

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

SQL>

SQL> create table system.logstdby$events (

2 event_time timestamp, /* The timetamp the event took effect */

3 current_scn number, /* The change vector SCN for the change */

4 commit_scn number, /* SCN of commit record for failed transaction */

5 xidusn number, /* Trans id component of a failed transaction */

6 xidslt number, /* Trans id component of a failed transaction */

7 xidsqn number, /* Trans id component of a failed transaction */

8 errval number, /* Error number */

9 event varchar2(2000), /* first 2000 characters of statement */

10 full_event clob, /* The complete statement */

11 error varchar2(2000), /* error text associated with failure */

12 spare1 number, /* Future expansion */

13 spare2 number, /* Future expansion */

14 spare3 varchar2(2000) /* Future expansion */

15 ) LOB (full_event) STORE AS (TABLESPACE SYSAUX CACHE PCTVERSION 0

16 CHUNK 16k STORAGE (INITIAL 16K NEXT 16K))

17 TABLESPACE SYSAUX LOGGING

18 /

create table system.logstdby$events (

*

ERROR at line 1:

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

SQL>

SQL> create index system.logstdby$events_ind

2 on system.logstdby$events (event_time asc) tablespace SYSAUX;

create index system.logstdby$events_ind

*

ERROR at line 1:

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

SQL> create type dbms_xplan_type

2 as object (plan_table_output varchar2(300));

3 /

create type dbms_xplan_type

*

ERROR at line 1:

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

Thanks & Rgds,

Abhishek

[former_member709110]

Hi,

Can you open the keydb.xml and check which phase it has errored out ?

Regards,

Neel

[Former Member]

Hello Neel,

It's executing the phase runCatprocSql. I was thinking that Error messages are coming as the objects already exist in the source system & hence in the target system while the catproc.sql is trying to create them again & hence this ORA - 001955 Error message, so was thinking of ignoring these & proceed.

Any advice.

Thanks & Rgds,

Abhishek

[former_member709110]

Hi,

Mannually run the catproc.sql (as sysdba) , if it complete (which i am sure it will) then change the status of the step in keydb.xml to "OK" (to skip the step) and proceed.

Regards,

Neel

[Former Member]

Hi,

Please check this link. I tried this solution and it works to me.

Thanks