Re: 9i on Windows 2000 Server Workgroup

On Sun, 20 Jun 2004 10:00:35 +1000, "Howard J. Rogers" <hjr_at_dizwell.com> wrote:

>
>"fu manchu" <leondobr_at_verizon.net> wrote in message
>news:q1h9d0dk8nv50hn4u7kjb6u9ad383p59gi_at_4ax.com...
>> Has anyone ever managed to install Oracle 9i 9201 ES on Windows 2000
>> with a workgroup rather than a domain?
>>
>> The install has worked every time for me on Win2000 on a domain, but
>> I've tried at least six installs on a workgroup and every time the
>> listener bombs out with error 12415 and no log info.
>
>I take it that is a typing error. 12415 actually relates to mistaken data
>types in tables columns.
>
>I assume you meant 12514?

• Right, a typo, sorry.

>
>>It generates a
>> Windows memory error and stops. I once converted a workgroup to a
>> domain and then the same install ran fine after failing twice on the
>> machine configured as a workgroup.
>
>Are you talking about an installation of the Oracle software, or the
>creation of a database?
>
>I can only re-iterate what I've mentioned here many, many times: those are
>two completely separate activities, and ought to be kept that way. Do a
>software only installation first, and create your database as a separate
>exercise.
>
>> I'm using the listener.ora and tnsnames.ora generated by the Network
>> Assistant for TCP as follows:
>>
>> # LISTENER.ORA Network Configuration File:
>> E:\oracle\ora92\network\admin\listener.ora
>> # Generated by Oracle configuration tools.
>>
>> LISTENER =
>> (DESCRIPTION_LIST =
>> (DESCRIPTION =
>> (ADDRESS_LIST =
>> (ADDRESS = (PROTOCOL = TCP)(HOST = beast)(PORT = 1521))
>> )
>> )
>> )
>>
>> # TNSNAMES.ORA Network Configuration File:
>> E:\oracle\ora92\network\admin\tnsnames.ora
>> # Generated by Oracle configuration tools.
>>
>> LEND92 =
>> (DESCRIPTION =
>> (ADDRESS_LIST =
>> (ADDRESS = (PROTOCOL = TCP)(HOST = beast)(PORT = 1521))
>> )
>> (CONNECT_DATA =
>> (SERVICE_NAME = lend92)
>> )
>> )
>>
>> Am I naming something wrong? I named the instance global name = lend92
>> same as the SID.
>>
>> I can ping beast, 127.0.0,1, localhost, etc.
>
>Don't rely on 127.0.0.1. Your machine might not be part of a domain, but as
>part of a workgroup it should have its own, fixed, ip address (no DHCP,
>please). If there is no DNS service resolving hostnames, it might be
>problematic to reference things via a machine name like "beast". Try putting
>in the correct IP address so that no host name resolution is needed.
>
>>But the listener cannot see the instance.
>
>What are you relying on when making that statement? If it's just the 12514
>error, then that's not good enough. Find out whether the listener is aware
>of any services at all by typing:
>
>lsnrctl services

• no services
  >
  >...at the command prompt, once you've started the service related to your
  >instance/database. If it shows anything at all, then your instance has in
  >fact dynamically registered itself with the listener, and you should be able
  >to connect to it, provided that your SERVICE_NAME value in your tnsnames.ora
  >matches the service name the listener is aware of *exactly*. Is your service
  >name *really* just "lend92". Or is it something more like "lend92.world" or
  >"lend92.workgroup", for example.
  >
  >To answer your specific question: installations onto a workgroup are
  >certainly possible. But there are machine name resolution issues that need
  >taking care of, or there are networking setup issues that might need
  >configuring properly. For the rest, it's just a question of creating
  >databases that are properly named (when DBCA asks you what name you want for
  >your database, you should put in a fully-qualified name such as
  >"lend92.workgroup". The abbreviated "lend92" should only be your SID, not
  >your database name). It's also a question of knowing what the listener is
  >really aware of, and making sure your Oracle networking files match that
  >exactly.
  

I want to thank you for taking the time to answer this in detail. Most of my previous testing was based on your previous posts.

I've spent way too much time over the past month trying to get this to work on a workgroup rather than a domain.

I simply don't have the time to mess with software that doesn't work right out of the box, two days max. I reinstalled Windows and 9i (software only, made the database after) one more time with no joy, same listener error, gave up, and installed 10g which worked first try (thanks for the global name tip, that was the answer I was hoping for). Versions 807, 817, 73x all worked first try, too, in previous installs over the years.

Sadly (or maybe not), the days when people were willing to spend huge amounts of time troubleshooting products seems to be over for application developers. There are too many other choices, software and hardware are cheap and timelines have shrunk. If SuSE 91 doesn't install properly, no worries, there's Mandrake 10 or any of dozens of others. Oracle won't install? Get MS SQLserver or MySQL.

I guess that's why Oracle came out with 10g.
>
>Regards
>HJR
>
Received on Sun Jun 20 2004 - 09:51:00 CDT