RE: Instance name different from database name
Date: Mon, 8 Nov 2010 17:13:58 -0000
Message-ID: <436BDF8ADD67C8408F970444F86AE46A01511C66_at_max-dc1-ex01.azurgroup.net>
> Stefan,
>
>Instance name ties all of the executables and memory structures together.
>Database name ties all of the datafiles and control files together.
Surely for that reason alone (combined with the DB_UINQUE_NAME info for ADR output) keeping these parameters the same would make supportability musch easier
Have seen at least one site where the names are all different and coming into the environment afresh was a major headache where you see datafiles for Database X, processes for Instance Y and ADR files for Z. Try to produce a site report and transition into managed service for that lot.
PMcM
_DISCLAIMER: This message is intended only for the use of the person(s) ("the intended recipient(s)") to whom it is addressed.
It may contain information which is privileged, proprietary and/or confidential within the meaning of applicable law.
If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of this message (including any attachments) is strictly prohibited.
If you have received this message in error, please contact the sender of this message as soon as possible.
The views or opinions expressed in this message are those of the author and may not necessarily be the views held by Maxima Holdings plc. Maxima Holdings plc. Cotswold Court, Lansdown Road, Cheltenham, Glos, GL50 2JA. Registered in England. 5043538. VAT Number - 728778184
This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email
-- http://www.freelists.org/webpage/oracle-lReceived on Mon Nov 08 2010 - 11:13:58 CST