Well, the database is the same since it is
RAC. What I suspect is the common pit fall
in loosly-clustered RAC systems where
the application or Oracle installation
or config is not the same on both nodes.
Very easy to do, and even more so on
Chief Architect, Database Solutions
>From: Michele Donna [mailto:michele.donna@(protected)]
>Sent: Thursday, March 24, 2005 3:29 AM
>Subject: [suse-oracle] Strange cluster problem
>We have a strange problem on Sles 9 / Oracle 22.214.171.124 / SAP SEM
>3.2 (sorry if this post is partially related to Oracle but I'm
>the configuration is :
> - SAP Central instance is on a 2 node cluster (on the other
>node there's an application server)
> - Oracle installed on 2 other nodes and clustered (both sap
>and oracle are clustered with lifekeeper)
>When running the database instance on node A, there are no
>problems, but if the database node switch on server B there
>happen dumps of type
: can bind a LONG value only for insert into a LONG column
: invalid length for DATE or NUMBER bind variable
>I believe there was some oracle client issue but all is ok..
>It seems there's something broken with the sql statements..
>Do you have any suggestion ?
>Many thanks and regards,
>To unsubscribe, email: suse-oracle-unsubscribe@(protected)
>additional commands, email: suse-oracle-help@(protected)
>see http://www.suse.com/oracle/ before posting
To unsubscribe, email: suse-oracle-unsubscribe@(protected)
For additional commands, email: suse-oracle-help@(protected)
Please see http://www.suse.com/oracle/ before posting