Unable to open connection using connection string

Product:
Cognos Planning 10.1.1
(PLANSRVR_version=PLANSRVR-AW32-ML-RTM-10.1.6235.51-0)
C8BISRVR-AW32-ML-RTM-10.1.6304.10-0 = IBM Cognos Business Intelligence Server Update, PLANSRVR-AW32-ML-RTM-10.1.6303.19-0 = Planning Server Update
Windows 2008 R2 server
Oracle Database

Symptom:
Error when you try to Start Cognos Planning service.

Error message in Planningerrorlog.csv file:
E6525D43-48B1-4123-8C99-7BFA5DFA2515} 14 2014-04-09 16:57:09.832 UTC +120 epPlanningService 10.1.4074.0 default ThreadSystemConnectionPool.cpp RefreshConnectionPool 260 OraOLEDB -2147467259 Unable to open connection using connection string of Provider=OraOLEDB.Oracle;Data Source=server.DOMAIN.COM;User ID=SERVICEACCOUNT;Password=*********; and timeout of 15 seconds.~~~~ORA-12504: TNS:listener was not given the SERVICE_NAME in CONNECT_DATA DOMAIN\UserAccount DOMAIN\SERVER DOMAIN\UserAccount DOMAIN\SERVER 3408 4968
{E6525D43-48B1-4123-8C99-7BFA5DFA2515} 15 2014-04-09 16:57:09.847 UTC +120 epPlanningService 10.1.4074.0 default ThreadSystemConnectionPool.cpp Run 138 OraOLEDB -2147467259 Unable to open connection using connection string of Provider=OraOLEDB.Oracle;Data Source=server.DOMAIN.COM;User ID=SERVICEACCOUNT;Password=*********; and timeout of 15 seconds.~~~~ORA-12504: TNS:listener was not given the SERVICE_NAME in CONNECT_DATA DOMAIN\UserAccount DOMAIN\SERVER DOMAIN\UserAccount DOMAIN\SERVER 3408 4968

Possible Cause:
This can happen when you restart the Cognos Planning service, from Cognos configuration or direct from windows services.

And the planning store settings inside Cognos configuration for oracle is set to advance and you use this syntax;
databasehostname.domain.COM:1521/oracleserverid.domain.COM

instead of this syntax;
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=databaseserver.domain.COM)(PORT=1521))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=oraclename.domain.COM)))

Redo the access syntax in Cognos Configuration and try to start Cognos again.
Both syntax of access to Oracle work for Cognos Content Store, but not for Cognos Planning Store.