Unable to start service

Synopsis of the issue was.
1. ges_taf service was unable to start on node2 and status UNKNOWN on node3
2. internal service ges_ges was writing message "ORA-44305: service ges_ges is running" in imon log every 10 minutes

[wbeqdrac08p:oracle]/u01/app/oracle/product/10.2.0/log/wbeqdrac08p/racg> tail -f imon_ges_ges.log
2009-04-29 11:13:04.626: [ RACG][1228056896] [28246][1228056896][ora.ges_ges.ges2.inst]: clsrcsnstartsrv: service name ges_ges already exists
2009-04-29 11:23:05.015: [ RACG][1228056896] [28246][1228056896][ora.ges_ges.ges2.inst]: clsrcsnstartsrv: service name ges_ges already exists
2009-04-29 11:23:05.015: [ RACG][1228056896] [28246][1228056896][ora.ges_ges.ges2.inst]: CLSR-0002: Oracle error encountered while executing clsrcsnstartsrv : execute2

2009-04-29 11:23:05.016: [ RACG][1228056896] [28246][1228056896][ora.ges_ges.ges2.inst]: ORA-44305: service ges_ges is running
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.DBMS_SERVICE", line 444
ORA-06512: at "SYS.DBMS_SERVICE", line 365
ORA-06512: at line 1


Resolution
1. when service is added using srvctl, netmgr or any other tool, it gets added in spfile with service_names parameter. This is not required 10204 onwards, meaning parameter service_names to be kept NULL. I also verified this with Oracle consultant over the phone
2. If we keep service_names to NULL, some process (I believe either pmon or racg) updates the parameter every 10 mins with db_unique_name value but in CAPITAL. So case does matter. I set it as lower case and it stopped putting ORA-44305 messages in imon log files.