Skip to Content
author's profile photo Former Member
Former Member

NW2004s MCOD install not detecting existing Oracle instance

We are attempting to perform a distributed database installation for

NW2004s AS-JAVA. We wish to use an existing SAP/Oracle database

called "JB1" running on Oracle/HP-UX using MCOD. The JB1 database instance

already contains a functioning NW2004s SAP AS-JAVA system.

We execute sapinst on the UNIX database host and

choose a Distributed Oracle DB installation. We enter the SAP SID

as "PD2" and the database SID as "JB1". However, it appears that

sapinst is not recognizing that the JB1 instance is already in

existence.

In our first attempt, sapinst removed all the redo logs and re-created

them, then attempted to perform a "CREATE DATABASE" command. This did

not seem to be the behavior we wanted for simply adding another schema

for the PD2 system. We restored the JB1 database from backup and are

now trying to run sapinst again.

I am seeing entries in the sapinst_dev.log that indicate:

"Oracle database exist: false"

Also, it appears from the ora_sql_results.log file that sapinst is not

correctly connecting to JB1 as sqlplus returns "connected to an idle

instance". It appears the subsequent SQL script which selects from V$INSTANCE comes back with no entries which then causes sapinst to think there is no existing JB1 instance.

The JB1 database is running when we start sapinst and we are able to

connect as sysdba from the orajb1 account.

My assumption is that sapinst should not be trying to re-create the JB1

database and that it is simply unable to detect that it already exists

and should be doing an MCOD install. Can anyone assist in determining why

sapinst cannot connect with sqlplus?

Regards,

Mike Tarr

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Nov 27, 2007 at 03:41 PM

    I have determined that if the JB1 database is shut down when I start

    sapinst, then sapinst will attempt to start it and detects the instance

    successfully. Should the existing database not be running when SAPINST is started for an MCOD install? It seems that there is still a problem with SAPINST connecting to the running JB1 instance.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 29, 2007 at 03:04 PM

    As mentioned above, found that by letting SAPINST start Oracle, it could successfully connect. Although I still don't believe this is the correct behavior, I was able to complete the MCOD installation, so this problem is effectively resolved.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 29, 2007 at 05:33 PM

    Is Oracle 10G mandatory for upgrading 2004 to 2004s? We have Oracle 9.2 and I am not sure If we need to upgrade Oracle before Portal Upgrade. Please reply.

    Thanks.

    Praveen

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.