cancel
Showing results for 
Search instead for 
Did you mean: 

MSCS: Central Instance Installation Problem - ECC 6.0

Former Member
0 Kudos

Hallo,

I am installing ECC 6.0 on Windows 2003 MSCS with Oracle 10.2.0.2

I have done the following steps succesfully:

Installation of OFS Software, Installation of the ASCS instance, Configure the first MSCS Node, Installation of the Database instance, Configure the additional MSCS Node

Install the ERS server (Enqueue Replication Service) at local disk, Additional Steps for Oracle Failsafe Configuration, Create the Oracle Failsafe Group, Setup a shared database directory, Add the Oracle database resource to Failsafe Group

The problem I have is during the installation of the Central Instance.

(I do the installation at local disk)

At the phase of Post_Installation,

the central instance cannot start correctly , and sapinst cannot finished the installation .

I get the error at the dev trace of work processes :

LOG BY4=> sql error 2289 performing INS on table DDLOG [dbsynseq#1 @ 324]

[dbsynseq0324 ]

B ***LOG BY0=> ORA-02289: sequence does not exist [dbsynseq#1 @ 324] [dbsynseq0324 ]

I have alreday checked the notes

185821 & 582427 that refer to this error code

and I ran the scripts catalog, catproc & utlrp ,

but the problem still persists with the same error ORA-02289

and I cannot finish with the Central Instance Installation

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member433984
Active Contributor
0 Kudos

did you open the support ticket?

Former Member
0 Kudos

Yes, but yet not find a solution.

we restarted the installation from scratch and now we are at the phase of the database instance.

We noticed the following during the configuration of the first MSCS node :

at the time where sapinst creates the sap cluster group, we get the error:

"could not create sap cluster group. Please look at R3Clus.log"

Behind it appears a screen where we are prompted to add manually the values. We added manually the values and then the sap cluster group was succesfully created and the configuration of the first MSCS node finished without reporting errors.

But we noticed that although the SAPLOC share is normaly created in HA installation through ASCS installation and automatically removed when processing First MSCS Node, it was not removed at our case.

We would like to know if the whole above symptom is normal or we must

expect problems at the continuing of the installation of ECC6?

If it is not normal what else we can do, so that sapinst do not

stop at the creation of the sap cluster group ?