Stefan, Instance name ties all of the executables and memory structures together. Database name ties all of the datafiles and control files together. Other than that there is no reason to keep them the same. MANY years ago, Oracle 6.0.36, I was reading the manual on SQLNET V1 and came across a sentence that said one "should pick a SID that is NOT case sensitive". The reason was that one had to use the following to connect to a database "<protocol>:<Host>:<sid>". Well T stood for TCP, Host (in my env) was called BRAHMS, and the SID was "02" (zero two), reason numbers are case insensitive, logical??? But the database name was "ATDDB". Worked like a charm. Dick Goulet Senior Oracle DBA -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Stefano Cislaghi Sent: Monday, November 08, 2010 5:10 AM To: Oracle L Subject: Instance name different from database name Hi all, does anybody know, or have consireded, any implication about having an instance name completely different from database name? I want to say, instance name maybe is D0EUNAME and database is DNAME ... I'm using a 2 nodes cluster with 11gR2 grid infrastrucre and database. During DB creation even if I've specified an instance name database starts using db name and dbname is registered in clusterware. In OFA I've have /admin/DNAME/ instead maybe admin/D0EUNAME Supposing that dbname maybe equals to sid in best practices, there're documents that suggest and explain why and how avoid this? Thanks Stefano -- http://www.stefanocislaghi.eu -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l