Opinion: Naming RAC Instances

[gopi]

In my last shop we had a standard of naming all the instances the same name as the database with the instance number suffixed to the end. What i’m designing now is a database with 4 instances, 2 of which are OLTP and two of which are DSS (The reporting must be real-time so I can’t use the typical ELT type strategy.)

In this scenario I’d like to use a naming standard such as:

wsm_oltp1, wsm_oltp2, wsm_rpt1, wsm_rpt2 while the database is named wsm.
Rather than what I’m used to which is something like:
wsm1, wsm2, wsm3, wsm4 while the database is named wsm.

What’s your opinion about naming instances with a different standard than the database name? (I’m fine with the administration aspects)

Frank

[Mr.Hanky]

We use the standard Pxxx or Dxxx, where xxx is a 3 digit number.
P= Production
D= Developemnt

We recently starting using ...

U for Unit Test
S for System Test
I for integration Test

but this is only for developement environments.

It depends on you, longr descriptive names can be good, but can be a pain in the arse to type 600 times a day.

MH

[stmontgo]

i'd stick with wsm1, wsm2, wsm3, wsm4 and then if somebody really wants to cam em something else well let them do so though an alias in the tnsnames