cancel
Showing results for 
Search instead for 
Did you mean: 

error occurs in phase create database when CRM2007 IDES installation

Former Member
0 Kudos

i got error from the install log file like this:

<BR>

<BR>

ERROR 2010-04-11 20:31:29.328

CJS-00084 SQL statement or script failed. 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. SOLUTION: See ora_sql_results.log and the Oracle documentation for details.

<BR>

<BR>

I used Oracle 10.2.0.4 as system required 10.2.0.2 above. And i only installed application only, without sample DB. Anyway, is there anyone met this before? Your response will be highly appreciated.

Edited by: Gabriel Liu on Apr 11, 2010 2:54 PM

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello,

This is a known SAPINST bug, which occurs with 10.2.0.4. The problem is that one of the comment lines at the beginning of catproc.sql reads "Rem arithikr 12/13/00 - 1489592: expect ORA-955 on defaultdest". When SAPINST scans the output of the script it misinterprets this text as a real ORA-955 error. You can fix this as follows:

- Break off the installation with "Stop"

- Go to the SAPINST installation directory

- For safety, make a backup copy of the file control.xml

- Open the control.xml file in a text editor - careful when you edit this file!

- Locate the function this.runCatproc

- A few lines below the function head you find the statement

script.execute_AbortOnFailure();

- Replace this with

script.execute();

- Restart SAPINST and choose "Continue old installation"; the error should no longer occur

Regards,

Mark

Former Member
0 Kudos

Thanks Mark, it didn't happened again.

<BR>

However, another one occured in phase "Import ABAP". Here is the ERROR message.

<BR>

-


<BR>

ERROR 2010-04-13 11:03:30.171 CJS-30023 Process call 'C:\usr\sap\C12\SYS\exe\uc\NTAMD64\R3load.exe -testconnect' exits with error code 2. For details see log file(s) R3load.exe.log. ERROR 2010-04-13 11:03:30.328 FCO-00011 The step testDatabaseConnection with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|testDatabaseConnection was executed with status ERROR .

<BR>

-


<BR>

So is this another SAPinst bug? If it was, I might find some notes about it right?

Edited by: Gabriel Liu on Apr 13, 2010 5:28 AM

<BR>

-


<BR>

I opened the listener from services, now the installation can proceed.

Edited by: Gabriel Liu on Apr 13, 2010 6:31 AM

Former Member
0 Kudos

Hi Gabriel,

No, I'm pretty sure that this is a genuine problem. Can you post the R3load.exe.log file?

Regards,

Mark

Former Member
0 Kudos

Hi Mark, this is the content of R3load.exe.log, which when I got the error I said before. As conclude from the code '12541', I guess it might be caused by Oracle DB listener not open. So after start the listener from Win SRV services, the installation process continued. And it seems finished successfully so far.

<BR>

-


<BR>

sapparam: sapargv( argc, argv) has not been called. sapparam(1c): No Profile used. sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline C:\usr\sap\C12\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20100413110325 C:\usr\sap\C12\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP C:\usr\sap\C12\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE] Compiled Sep 28 2007 00:58:27 C:\usr\sap\C12\SYS\exe\uc\NTAMD64\R3load.exe -testconnect DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541 DbSl Trace: CONNECT failed with sql error '12541' DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541 DbSl Trace: CONNECT failed with sql error '12541' (DB) ERROR: db_connect rc = 256 DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541 DbSl Trace: CONNECT failed with sql error '12541' DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541 DbSl Trace: CONNECT failed with sql error '12541' (DB) ERROR: DbSlErrorMsg rc = 99 C:\usr\sap\C12\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s) C:\usr\sap\C12\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20100413110330

<BR>

-


<BR>

This is the first time I install a IDES, I am not sure about all I have done, maybe it won't considered as completely successful after I running all post installation tasks. So if any further advices, let me know. Great thanks!

Answers (3)

Answers (3)

Former Member
0 Kudos

HI Mark,

I was having same error while ECC 6.0 installation on HP-UX and Oracle 10.2.0.4 db.

The solution given by you worked for me. But in addition with solution provided by you, I had to do activity mentioned in blog http://scn.sap.com/thread/1628459 with solution given by Markus.

Thanks & Regards,

Ishan

former_member204746
Active Contributor
0 Kudos

you will need to learn your error messages.

like this one:

SOLUTION: See ora_sql_results.log and the Oracle documentation for details.

Former Member
0 Kudos

Hi,

Is this the step when the just after the DB created and the cat* script is being run. ?

Mark