Re: 9i on Windows 2000 Server Workgroup

"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?

>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

...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.

Regards
HJR Received on Sat Jun 19 2004 - 19:00:35 CDT