Unable to connect Oracle (10g) database with SYS on Node2.

[Ghazanfar_1]

Hi Gurus,

I have issue with ServiceGuard. On node1, I can access the database through SYS but on Node2 I am unable to access the database through SYS (but can access through other account). When I tried to connect, it connected to an idle instance.

There is another issue with node2, that archive logs are not being applied to DR-Site(Oracle DataGuard) when package is up from Node2.

On Node1, everything is working fine.

[Duncan Edmonstone]

You're not giving us much to go on here are you? What actual commands did you type in? And from where? Was this a failure to login using sqlplus on node2, or was it from another location, what did you fail to login to? The database? EM dbconsole? Another utility? What error messages did you get? As for Data Guard, how did you configure it? Are you using the broker? You do know the Data Guard broker doesn't work with a cold failover cluster (like Serviceguard or HACMP) don't you (at least not without a fairly nasty hack)?

[Ghazanfar_1]

You're not giving us much to go on here are you?

What actual commands did you type in?

Ans: sqlplus / as sysdba

And from where?

Ans: command line. directly connected to Node2(telnet)

Was this a failure to login using sqlplus on node2, or was it from another location, what did you fail to login to?The database? EM dbconsole? Another utility?

Ans: unable to connect to DB, it connected as idle instance with no DB available.

What error messages did you get?

Ans: Connected to an idle instance

As for Data Guard, how did you configure it? Are you using the broker? You do know the Data Guard broker doesn't work with a cold failover cluster (like Serviceguard or HACMP) don't you (at least not without a fairly nasty hack)?

Ans: Not through broker ... its working fine on Node1

[Duncan Edmonstone]

So are you sure you have ORACLE_HOME and ORACLE_SID set the same on both nodes? Could explain both issues you are seeing? You still haven't explained how Data Guard was setup on the primary?

[Andres_Stickar]

The Oracle is configured with passw file ?

If not, probably you cannot connect remotely with SYS.

If you are not sure about it, try this.

sqlplus "/@INSTANCE  as sysdba"

where INSTANCE is your instance name "PRD, ORA, LAB ,etc"

if you have "insufficient privileges" the you have not passw file and you must create it.

There are a lot of recipes In the internet to do that 

Andrés

[Ghazanfar_1]

Can this happen because of different SYS passwords on both nodes?

Secondly, how can we check what is the SYS password?

I think .. we should focus on SYS account issue .. may be if it resovled the Dataguard issue will resolve too.

[Ghazanfar_1]

The issue has been found, its with $ORACLE_HOME.
On node1, its /ora......./102
On node2, its /ora......./102/

Now, there is another issue occurs... On node2 when I remove the slash(/) the database (lets say abc1) connected successfully. But there is another database abc2, now it is connected as idle instance.

So, without slash(/) abc1 is connecting fine, but not abc2.
And with slash(/) abc2 is connecting fine, but not abc1.

There is single ORACLE_HOME.
I have checked the oratab, listeners.ora and tnsnames.ora ... in all of the ORACLE_HOME is set without slash(/).

[Ghazanfar_1 · Accepted solution]

Issue resolved... changed the ORACLE_HOME path from haoracle.