Note: This chapter assumes that Oracle Names and all the related SQL*Net products have been installed at your site.
The main function of the command procedure ORA_NETCONFIG:NAMESCTL.COM is to check that the privileges required to start the Names Server are present (see the section "Names Server Privileges"). If a NAMESCTL START command is entered and the required privileges are not present, an error is displayed and NAMESCTL exits.
Note: Start the Names Server using the Oracle account.
Warning: If you enter the NAMESCTL interactive mode by giving the NAMESCTL command without a subcommand and you have received a warning about inadequate privileges, DO NOT attempt to start the Names Server. The Names Server process may still start, depending on the privileges you do have, but it may not function properly.
Warning: DO NOT start the Names Server from a process that has a UIC in the system group, for example a group less than or equal to MAXSYSGROUP. If you give a NAMESCTL START command from such a process, an error is displayed and NAMESCTL exits. If you enter a NAMESCTL command with no arguments, you are warned not to start the Names Server from within the NAMESCTL utility.
| Privilege | Function |
| CMKRNL | Facilitate kernel mode processing |
| NETMBX | Use DECnet |
| PRMMBX | Create a permanent mailbox on which to listen (The mailbox is permanent so that the logical name associated with it goes into the SYSTEM logical name table.) |
| SYSNAM | Create SYSTEM logical names and shared logical name tables |
| TMPMBX | Create temporary mailboxes |
| Note: Before attempting to start the Names Server, the process that starts the Names Server must have the privileges in this table or be able to have them set. As noted above, the NAMESCTL command file will attempt to set these privileges and warn the user if it was unable to do so. | |
| Table 5-1 Privileges and Their Functions | |
Note: The presence of the NAMES.PREFERRED_SERVERS clause in SQLNET.ORA supersedes the presence of TNSNAMES.ORA in TNS_ADMIN. Therefore, if the use of a Names Server has been specified with SQLNET.ORA, then even if TNSNAMES.ORA exists and has a complete list of connection addresses, the client will not read TNSNAMES.ORA.