Re: Oracle 7.3.4 Upgrade failed ...

The '4 character limit' on SIDs was once (and may still be) a limitation on VMS systems and the way in which the SQL*Net configuration was used, and Oracle Corp has (for some time) suggested setting a 4-character limit on SIDs for all platforms because of this.

The problem with SID1 and SID2 colliding may be down to the way that Oracle generates a key for the shared memory segment. I believe there is an option on some platforms to create a file in the $ORACLE_HOME/dbs directory with a name like config{sid}.opt which specifies the SHM key that should be used. Unfortunately I don't remember the necessary details of how (and where) this works.

--

Jonathan Lewis
Yet another Oracle-related web site: http://www.jlcomp.demon.co.uk

Liz Reen wrote in message ...
>In article <82380g$4o6$1_at_zingo.tninet.se>, zeth.johansson_at_ifsab.se
>says...
>> Hi Brian!
>>
>> I've had the same problem with Oracle 7.3.4 on HP-UX. When I had two
>> different ORACLE_SIDs with the same first three characters, e g SID1 and
>> SID2, Oracle couldn't tell which was which. When I renamed SID2 to 2SID,
it
>> worked fine. I haven't talked to Oracle support about it, but my own
>> conclusion is that multiple ORACLE_SIDs with the same first three
characters
>> aren't allowed.
>>
>> Regards
>>
>> Zeth
>>
>>
>>
>>
>>
>I run to sids TRACSDEV and TRACTRAN on the same HP-UX system. The Oracle
>version is 7.3.3. We haven't had any problems.
>
>Liz
>--
>My real address is L I Z R a t A O L d o t C O M
>
Received on Tue Dec 07 1999 - 07:53:50 CST