What is the correct format for the Oracle JDBC connection string?

Good Day
I am attempting to setup CLM 4.0.1 to connect to an Oracle Database (Oracle 11.2.0.3).
I have downloaded the Oracle JDBC driver v6 (ojdbc6.jar) and have configured the appropriate Environment Variable in WAS 8.0.0.3:
ORACLE_JDBC_DRIVER_FILE = /opt/IBM/Jazz/JazzTeamServer/server/ojdbc6.jar
When running jts/setup, I enter the following URL for the JDBC string:
thin:<jtsdbuser>/{password}@//<server>:1521/<servicename>
However, I am getting the following error when testing the connection to the Database:
I am attempting to setup CLM 4.0.1 to connect to an Oracle Database (Oracle 11.2.0.3).
I have downloaded the Oracle JDBC driver v6 (ojdbc6.jar) and have configured the appropriate Environment Variable in WAS 8.0.0.3:
ORACLE_JDBC_DRIVER_FILE = /opt/IBM/Jazz/JazzTeamServer/server/ojdbc6.jar
When running jts/setup, I enter the following URL for the JDBC string:
thin:<jtsdbuser>/{password}@//<server>:1521/<servicename>
However, I am getting the following error when testing the connection to the Database:
hide details IO Error: Invalid connection string format, a valid format is: "//host[:port][/service_name]"
Accepted answer

Sudheer - your connection string looks correct to me, I believe that the message is 'incorrect' which confuse you, please try to connect to Oracle Service in system console to confirm your Oracle works as expected.
Here is my settings while set DW on Oracle.
data.warehouse.page\:db.jdbc.location=thin\:jazzu01/{password}@//localhost\:1521/DW
Here is my settings while set DW on Oracle.
data.warehouse.page\:db.jdbc.location=thin\:jazzu01/{password}@//localhost\:1521/DW
2 other answers

Hi,
Thanks to Xuan Jiang and Georg Kellner for responding to my question.
I managed to figure out why I was getting the invalid connection string error.
Turns out this was due to the fact that the DB user password had an @ sign in it and so the JDBC connection string had two @s and this is why it complained.
We resolved this by changing the password.
The question now though is, does this mean that Oracle DB passwords cannot have the @ sign in it? Or is there a way to 'escape' this @ sign (like \@)?
Regards,
Sudheer
Thanks to Xuan Jiang and Georg Kellner for responding to my question.
I managed to figure out why I was getting the invalid connection string error.
Turns out this was due to the fact that the DB user password had an @ sign in it and so the JDBC connection string had two @s and this is why it complained.
We resolved this by changing the password.
The question now though is, does this mean that Oracle DB passwords cannot have the @ sign in it? Or is there a way to 'escape' this @ sign (like \@)?
Regards,
Sudheer