Hi, The bit about tnsnames.ora helped a lot, but there's another problem.
The new spacewalk database I am attempting to connect to is hosted on an Oracle RAC cluster. I'm not sure if anyone on this list has tried it before, and while it sounds a bit crazy to me anyway, there seems to be problems with doing this with spacewalk. Spacewalk it seems, is only geared around having the database on a single instance, and with a RAC cluster you can have multiple instances (for failover, I gather). So while I can set spacewalk to look for a single instance (SPACEWALK1 in my case) it will work, and I can use spacewalk with the database residing on Oracle RAC. However it can't seem to be configured for other instances (SPACEWLK2, SPACEWALK3, etc) because spacewalk's reliance on a single SID in the configuration. At least, that's what I understand from what our DBA tells me anyway. Is there a way to reconfigure spacewalk to connect in such an environment, or is this going to sound like a feature request for a future version of spacewalk? Thanks. Nathan >Nathan, > >Most likely there's defined SPACEWLK service in /etc/tnsnames.ora. So >you have to either a) fix tnsnames.ora definition and let /etc/rhn/rhn.conf >as it was or b) remove tnsnames.ora and specify new db_name, db_host and >db_port in rhn.conf. > > >Regards, > >-- >Michael Mr?ka >Satellite Engineering, Red Hat
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
