Message-Id: <10674.121417@fatcity.com> From: GP2Z/INF/RAHAL Date: Wed, 8 Nov 2000 14:48:07 -0000 Subject: RE: urgent help needed This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C04992.7EEEB580 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable hello, please find joined here a document ABOUT "ADMINISTERING A DATABASE", I = hope that to be going to find you an interest, =20 <>=20 good courage? > -----Message d'origine----- > De: Allan Nelson [SMTP:anelson@houston.rr.com] > Date: mercredi 8 novembre 2000 03:20 > =C0: Multiple recipients of list ORACLE-L > Objet: Re: urgent help needed >=20 > Try the O'Reilly book Oracle Database Administration Essentials or = some > thing like that. > Allan > ----- Original Message ----- > To: "Multiple recipients of list ORACLE-L" > Sent: Tuesday, November 07, 2000 8:35 AM >=20 >=20 > > hi > > > > could anyone help me on where to start for oracle dba, > > where can i find a checklist to see the items i should > > follow starting from installing oracle to configuring, > > fine tuning the database. > > > > appreciate ur help > > > > dave > > > > __________________________________________________ > > Do You Yahoo!? > > Thousands of Stores. Millions of Products. All in one Place. > > http://shopping.yahoo.com/ > > -- > > Please see the official ORACLE-L FAQ: http://www.orafaq.com > > -- > > Author: david mccoll > > INET: david123_1111@yahoo.com > > > > Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 > > San Diego, California -- Public Internet access / Mailing = Lists > > = -------------------------------------------------------------------- > > To REMOVE yourself from this mailing list, send an E-Mail message > > to: ListGuru@fatcity.com (note EXACT spelling of 'ListGuru') and in > > the message BODY, include a line containing: UNSUB ORACLE-L > > (or the name of mailing list you want to be removed from). You may > > also send the HELP command for other information (like = subscribing). >=20 > --=20 > Please see the official ORACLE-L FAQ: http://www.orafaq.com > --=20 > Author: Allan Nelson > INET: anelson@houston.rr.com >=20 > Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 > San Diego, California -- Public Internet access / Mailing = Lists > -------------------------------------------------------------------- > To REMOVE yourself from this mailing list, send an E-Mail message > to: ListGuru@fatcity.com (note EXACT spelling of 'ListGuru') and in > the message BODY, include a line containing: UNSUB ORACLE-L > (or the name of mailing list you want to be removed from). You may > also send the HELP command for other information (like subscribing). ------_=_NextPart_000_01C04992.7EEEB580 Content-Type: application/octet-stream; name="ch6.htm" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="ch6.htm" Administering a Database

=20

6
Administering = a=20 Database

This chapter describes how to administer Oracle8.

Specific topics discussed are:

  • Starting and Shutting Down a Database with = Server=20 Manager=20

  • Starting=20 and Shutting Down a Database with Oracle Enterprise Manager=20

  • Running=20 Multiple Instances=20

  • Using Novell Directory Services (NDS)=20

  • Authenticating=20 Database Administrators=20

  • Encrypting=20 Database Passwords=20

  • Using=20 the Oracle Enterprise Manager Console=20

Starting and = Shutting Down a=20 Database with Server Manager

Starting Server=20 Manager

To start or shut down an Oracle8 database with Server Manager:

  1. Start Server Manager at the = MS-DOS command=20 prompt:=20 

    C:\>SVRMGR

    or from the NetWare Console prompt: 

    :LOAD SVRMGR
  1. Connect to the Oracle8 database = using your=20 user name:=20 

    SVRMGR> CONNECT =
INTERNAL/PASSWORD
  2. Follow the instructions below:=20
Oracle8 User's Guide for = NetWare
Release=20 8.0.3 for NetWare
A56083_01
3D""=20
Library		 3D""=20
Product
Contents
Index
To...   Go to Section... =  

Start a database  

Starting=20 a Database with Server Manager  

Shut down a database  

Shutting=20 Down a Database with Server Manager =  

Starting a Database = with Server=20 Manager

Before starting the database, ensure that a database instance has = been=20 created.

  1. Start up the database by entering = one of the=20 following commands:=20
    Command   Description  

    SVRMGR> STARTUP  

    Uses the default INITSID.ORA file located in your=20 ORACLE_HOME\DATABASE directory to start the Oracle8 = database.=20  

    SVRMGR> STARTUP PFILE=3DPATH\FILENAME =  

    Uses an initialization file other than the default to start = your=20 database. PATH\FILENAME specifies an = initialization=20 parameter file other than the default, INITSID.ORA. = The=20 following example starts the database using a file named = INIT2.ORA.

    SVRMGR> STARTUP PFILE=3D%ORACLE_HOME%\DATABASE\INIT2.ORA=20  

    After completing these steps, you can connect to the Oracle8 = database.=20

Shutting Down a = Database with=20 Server Manager

To shut down a database using Server Manager:

  1. Connect to the Oracle8 database = using your=20 username:=20 

    SVRMGR> CONNECT =
INTERNAL/PASSWORD
  1. Enter the following command:=20 

    SVRMGR> SHUTDOWN [MODE]

    

    where MODE is one of the following: =
 
    Normal  
    The database waits for all currently connected =
users to disconnect and disallows any new connections before shutting =
down. This is the default mode.  
    Immediate =
 
    The database terminates and =
rolls back active transactions, disconnects clients, and shuts down. =
 
    Abort  
    The database terminates active transactions and =
disconnects users; it does not roll back transactions. The database =
performs automatic recovery and rollback the next time it is started. =
Use this mode only in emergencies.  
    Transactional =
 
    Prevents clients from =
losing work, and at the same time, does not require all users to log =
off. After submitting this statement, no client can start a new =
transaction on this particular instance. If a client attempts to start =
a new transaction, they are disconnected. After all transactions have =
either committed or aborted, any client still connected to the instance =
is disconnected. At this point, the instance shuts down just as it =
would when a SHUTDOWN IMMEDIATE statement is submitted. =
 

Starting and = Shutting Down a=20 Database with Oracle Enterprise Manager

Oracle Enterprise Manager enables you to start and shut down your = Oracle8=20 database in several different ways. This section describes how to use = the=20 Navigator. You can also use:

    • SQL Worksheet=20
    • Instance Manager

See the Oracle=20 Enterprise Manager Administrator's Guide for information on = using these=20 tools to start your database.=20

Note:=20

This section assumes you have configured Oracle Enterprise = Manager. If=20 you have not, see the section "Configuring=20 Oracle Enterprise Manager" in Chapter 3, "Configuration = Tasks" for=20 instructions.

 =20

  1. Choose = Start>Programs>Oracle Enterprise=20 Manager>Enterprise Manager.=20

    The Repository Login Information dialog box appears.

  1. Enter your repository user login = information.=20

    Note:=20

    A Net8 service name entry is only necessary if you are = connecting=20 from a client Console machine to the Oracle8 repository = database. If the=20 repository database is on your Console, you do not need to = enter a=20 service name.

     =20

    The Oracle Enterprise Manager Console appears. The = Navigator=20 Window displays in the upper-left portion of the console.

  2. Double-click Databases in the=20 Navigator window of the Oracle Enterprise Manager Console.=20

    The list of databases in your Oracle Enterprise Manager network = appears.=20

  3. Select the appropriate database.=20

  4. Choose = Tools>Applications>Oracle=20 Instance Manager from the main menu.=20

    The Login Information dialog box appears.=20

    Note:=20

    If this is the first time you have used Oracle Instance = Manager, the=20 Login Information dialog box appears. If you have = previously=20 logged in, the Oracle Instance Manager opens without prompting = you to=20 log on. Go to Step 8.=20

     =20

  5. Enter the INTERNAL user name and = password, and=20 Net8 service name for the Oracle8 database.=20

  6. Click OK.=20

    The Oracle Instance Manager window appears.

  7. Double-click Initialization = Parameters in the=20 Navigator tree.=20

    The initialization parameters appear for the Oracle8 database. =

  8. Click Save.=20

    The Save Configuration dialog box appears.

  9. Enter an appropriate = configuration name for=20 the initialization parameters (for example, SALES_DB) and click OK.=20

  10. Choose File>Exit to Console = from the main=20 menu.=20

    You are returned to the Oracle Enterprise Manager Console.

  11. Double-click Databases in the=20 Navigator window of the Oracle Enterprise Manager Console.=20

  12. Follow the instructions below:=20
    To...   Go to Section... =  

    Start a database  

    Starting=20 a Database with Oracle Enterprise Manager =  

    Shut down a database  

    Shutting=20 Down a Database with Oracle Enterprise Manager=20  

Starting a Database = with Oracle=20 Enterprise Manager

  1. Right-click the database in the = Navigator tree=20 that you want to start.=20

  1. Choose Connect from the menu that = appears.=20

    The Login Information dialog box appears.

  2. Enter the INTERNAL user name and = password, and=20 click OK.=20

  3. Choose Startup from the menu that = appears:=20

    The Startup dialog box appears.=20

  4. Provide the appropriate = information and choose=20 OK.=20

    Your Oracle8 database starts.

Shutting Down a = Database with=20 Oracle Enterprise Manager

  1. Right-click the database in the = Navigator tree=20 that you want to shut down.=20

  1. Choose Connect from the menu that = appears.=20

    The Login Information dialog box appears.

  2. Enter the INTERNAL user name and = password, and=20 click OK.=20

  3. Choose Shutdown from the menu = that=20 appears:=20

    The Shutdown Options dialog box appears:

  4. Provide the appropriate = information and choose=20 OK.=20

    Your Oracle8 database shuts down.

Running Multiple=20 Instances

To run multiple instances, it is assumed that you have already done = steps=20 1,2, and 3:

  1. Add a new SID name to the = listener in=20 LISTENER.ORA.=20

  1. Setup a new service name in = TNSNAMES.ORA that=20 uses the IPC protocol.=20

  2. Create a new parameter file in = the=20 ORACLE_HOME\DATABASE directory of the form initSID.ora. Be sure that = the=20 control_file parameter specifies a new control file name , and the = db_name=20 points to the new database name.=20

  3. Start Server Manager=20 

    LOAD SVRMGR
  4. Connect as INTERNAL.=20 

    SVRMGR>CONNECT =
INTERNAL/<PASSWORD@service_name that was created in =
Step2>
  5. Start up the database with the = new instance:=20 

    SVRMGR>STARTUP =
PFILE=3D%ORACLE_HOME%DATABASE\INITSID.ORA

    where SID is the name of the instance.

Using Novell = Directory=20 Services

Novell Directory Services (NDS) is an object-oriented implementation = of=20 directory services that allows you to build sophisticated naming = schemes that=20 model business organizational structures and is consistent with the = emerging=20 X.500 Standard for a directory.

Novell Directory Services (NDS) first became available with NetWare = 4,=20 providing users with global access to network resources such as = servers, shared=20 drives and databases regardless of where they are physically located. = This=20 feature allows users from multiple locations to use a single login to = access a=20 multi-server and multi-database network, and to view the entire network = in a=20 single directory.

A user logged in to NDS can be automatically authenticated to use an = Oracle=20 database running on any server in the directory.

Oracle DBAs working in an NDS environment can:

  • Create an Oracle database object (known as = an=20 instance) in the directory.=20

  • Map NDS users, groups, and organizational = units to a=20 database user. This allows NDS users (individually, in groups, or in=20 organizational units) automatic access to a single database user = account.=20

  • Map NDS groups to database roles. This = allows members=20 of these NDS groups to automatically inherit the privileges of the = database=20 role to which they are mapped.=20

  • Create Oracle users.=20

  • Assign database roles to users and other = database=20 roles.=20

  • Assign privileges to users and database = roles.=20

  • Modify default and temporary tablespace = values and=20 user profile information.=20

Instructions for performing these tasks are provided in online help = format=20 within the NWADMIN Oracle Snap-In for NetWare Administrator dialog = boxes.=20

See in this chapter and your Novell documentation for a complete=20 discussion of NDS features.  =20

Requirements

To use NDS with Oracle8 Server, you must do the = following:=20

  • Run NetWare 4.1.=20

  • Run the NWADMIN utility on a Windows 3.1 = workstation.=20

  • Install SQL*Net 2.3 server networking = software.=20

  • Install the following SQL*Net 2.2.2.0.3 or = later=20 client networking software:=20

    • If running Windows, install SQL*Net = 2.2.2.0.3 or=20 later networking software.=20
    • If running OS/2, install SQL*Net = 2.2.2.0.0 or later=20 networking software.

  • Install the Oracle Snap-In for NetWare = Administrator.=20

Table=20 6-1, "The INIT%SID%ORA Parameters to set to Enable NDS Mapping" = lists the=20 INIT%SID%.ORA parameters that must be set to enable NDS mapping.=20

An NDS user or group to a database user  =20

OS_AUTHENT_PREFIX=3D""  =20

An NDS group to a database role  =20

OS_ROLES=3DTRUE  =20

Do not put a space between the double quotes for=20 OS_AUTHENT_PREFIX.  =20

Working with the = Directory=20 Tree

The Oracle Snap-In for NetWare Administrator allows you to create an = Oracle=20 database instance object in an NDS directory tree. The Oracle Instance = Object=20 looks and behaves just as any other NDS object and is subject to = exactly the=20 same security features, such as, the ability to control the access = rights to the=20 object itself. Once this object has been created, a DBA can provide = groups and=20 users with access and privileges to the database instance which it = represents.=20 The Oracle Snap-In for NetWare Administrator is described fully in=20 context-sensitive online help.

Using the Oracle = Snap-in for=20 NetWare Administrator

During database instance object creation, you should define = additional=20 properties of your database instance, which allow a DBA to perform = tasks such as=20 assigning NDS groups and users to a database login and assigning NDS = groups to=20 database roles.=20

This section describes how to create a database instance object = in a=20 container object called DESKTOP. Create your database instance = object=20 under a container object appropriate to your environment. Before = you=20 access the online help procedures, you should review your NetWare = 4.1=20 documentation for information on logging on to a NetWare server = and=20 running NWADMIN.  =20

To create a database instance = object in a=20 container object:=20

 =20

Start NWADMIN. The NetWare Administrator screen appears. =  =20

 =20

Select Tools->Browse in the main menu bar (if necessary). = The [Root]=20 screen appears (depending upon your current context or setting) = .  =20

 =20

Double-click on the object under which you will create the = database.

For example, double-click on "oracle" to access the object = "desktop".=20 Then double-click on "desktop" to see the following objects:  =20

 =20

Select Object->Create from the NetWare Administrator main = menu bar=20 to create a database under "desktop". The New Object dialog box = appears.=20  =20

 =20

Select Oracle Instance from the Class of New Object list and = choose=20 [OK]. The Create Instance dialog box appears.

The Create Instance dialog box contains a check box called = Define=20 Additional Properties.  =20

 =20

Select this option to assign groups and roles. The Oracle = Instance=20 dialog box appears.

This dialog box contains a list of "pages" that access = individual=20 property sheets where you can assign access privileges. The types = of=20 properties that you can assign include: Identification, User = Mappings,=20 Role Mappings, Privileges, User Storage, and Connect Address.

It is essential that you assign the correct Oracle SID in the = "SID=20 Name" field, and that you assign the correct NetWare Server on = which this=20 instance is running in the 'Host' field. It is best to use the = directory=20 browsing facility to ensure that the name and full directory = context of=20 this server is correctly entered.  =20

 =20

Click on Help under each "page" for context-sensitive = instructions on=20 using that feature of the Oracle Instance Object. Attention: If = you move a=20 database from one server to another server in an NDS tree, you = must also=20 specify the new server name. Failing to do so will cause all = automatic=20 authentication to fail.  =20

Operating System = Authentication=20 for Database Administration

To take advantage of secure operating system authentication for = database=20 administration privilege, Database administrators who use CONNECT = INTERNAL or=20 CONNECT username as SYSDBA from a client workstation must = belong to the=20 NetWare group that controls the list of authorized Oracle DBAs. This = group name=20 must be assigned to the "Admin Group" field of the Oracle Instance=20 identification page shown above, for example: 

ORACLE_DBA.context_name

where <context_name> is the position of an object = within the=20 NDS directory tree, for example, DESKTOP.ORACLE. It is best to use the = directory=20 browsing facility to ensure that the name and full directory context of = this=20 group is correctly entered. In the same way, the 'Operator Group' field = allows=20 you to select the NDS group which will be used to authenticate users = who use=20 CONNECT username as SYSOPER.

The NetWare group ORACLE_DBA.<context name> = is=20 created without any members during installation at the root of the = directory.=20 You may choose to use this group or any other group for controlling = Database=20 Administrator privileges.

To add or delete users from the group, use a NetWare 4.1 utility = such as=20 NWADMIN or NETADMIN from a client workstation. To change the membership = of the=20 group, you must be the group manager, or be logged in as ADMIN or an = equivalent=20 user.

To use the Oracle8 Database Administration Tools for Windows or = OS/2, you=20 must be a member of the ORACLE_DBA.<context_name> group = and be=20 logged in to the NetWare directory service, or you must supply the = appropriate=20 password so that Oracle can use the password file to authenticate you. =

The CONFIG.ORA file parameter ORACLE_GROUP is not used with NetWare = 4.1 with=20 NDS. Specify the database administration group name in the Admin Group = text box=20 on the Identification page of the Oracle Instance dialog box.

End User=20 Authentication

The Oracle Instance dialog box shown earlier allows the = administrator to=20 create users within the Oracle database and completely manage these = users'=20 properties. NDS users, groups, and organizational units may be mapped = to Oracle=20 users to allow a one-to-one mapping between operating system users and = Oracle=20 users or to allow a many-to-one mapping between operating system users = and=20 Oracle users. In addition, NDS groups can be mapped to Oracle database = roles to=20 allow the operating system to be used to grant roles to users = connecting to the=20 Oracle Server. By using the features of the security integration = between the=20 Oracle Server and Novell Directory Services, administrators have = maximum=20 flexibility in managing the security of the database or the = applications which=20 are built to use the database. Security management can also be safely = delegated=20 to the Network Administrator.

Troubleshooting

If you have problems installing the Oracle Snap-In for NetWare = Administrator,=20 there are several troubleshooting procedures to perform.

On the Oracle8=20 Server

Oracle fails to extend the NDS schema if you install the Oracle8 = Server=20 before installing NDS for NetWare 4.1. If this occurs, you = must do the=20 following:=20

 =20

Install NDS on your NetWare 4.1 server.  =20

 =20

Load the following NLM on the server containing the root NDS = database:=20 : LOAD ORASCHEM

ORASCHEM extends the NDS schema to add the Oracle objects = class.  =20

Oracle fails to extend the NDS schema if you install the Oracle8 = Server on a=20 NetWare server which does not contain a read-write or master partition = of the=20 directory database. If this occurs, you mut do the following:=20

 =20

Copy the ORASCHEM NLM file to a server which does contain a = read-write=20 or master partition of the directory database.  =20

 =20

Execute the NLM on this server by loading it at the console: : = LOAD=20 ORASCHEM  =20

Allow time for the directory to re-synchronize and ensure the schema = changes=20 have propagated to all partitions.

On the = client

When you start NWADMIN, you will receive a message stating that = NWORACLE.DLL=20 can not be found. This file allows you to create an Oracle database = instance in=20 an NDS directory tree.

  • You should be sure that an entry similar to = the=20 following appears in your NWADMIN.INI file:=20

[Snapin Object DLLs] = NWORACLE=3Dc:\orawin\bin\nworacle.dll

  • You should also be sure that the = NWORACLE.DLL file is=20 in the directory.=20

Using Bindery=20 Services

Bindery services are available with NetWare 4.x.

Bindery-based users can access any object in the directory by using = multiple=20 accounts. But this can result in more work for the network supervisor,=20 especially if numerous users need several accounts.

Bindery services users should be grouped within bindery contexts = defined by=20 workgroups, shared resources, and information usage and exchange. =

Operating System = Authentication=20 for Database Administration

Database administrators who use CONNECT INTERNAL from a client = workstation=20 must belong to the NetWare group that controls the list of authorized = Oracle=20 DBAs and be logged onto the NetWare server which is running the Oracle8 = Server.=20 By default, this group is named ORACLE_DBA, although it can be changed. = The=20 OSOPER group is called ORACLE_OPER and can not be changed. For all = NetWare=20 releases for Oracle8 Server 7.2 or later, these two groups are checked = by all=20 SIDs, along with each SID checking the ORACLE_SID_DBA and = ORACLE_SID_OPER groups=20 (where SID is each database instance name).

The NetWare group ORACLE_DBA is created without any members. To add = or delete=20 users from the group, use the following:

  • an equivalent NetWare 4.1 utility such as = NWADMIN or=20 NETADMIN from a client workstation=20

To change the membership of the group, you must be the group = manager, or be=20 logged in as SUPERVISOR or as a SUPERVISOR-equivalent user.

To use the Oracle8 Database Administration Tools, you must be a = member of the=20 ORACLE_DBA group and be logged in to the NetWare Server or give the = database=20 administration password.

If you are not using NetWare 4.1 with NDS, you can change the name = of the=20 ORACLE_DBA NetWare group at any time by specifying the new group name = in the=20 CONFIG.ORA file. The ORACLE_GROUP CONFIG.ORA parameter specifies the = name of the=20 NetWare group that controls DBA access to the database. If your = CONFIG.ORA file=20 does not have the ORACLE_GROUP parameter set, the name of the current = database=20 administration group defaults to ORACLE_DBA.

To change the name of the group, add (or modify) the following line = to your=20 CONFIG.ORA file: 

ORACLE_GROUP=3Dgroup=20

where <group> is the name of the new database = administration=20 group.=20

Make sure there are no spaces around the equal sign (=3D) and = that there is=20 a carriage return at the end of the last line in the CONFIG.ORA = file. For=20 more information about the CONFIG.ORA file and parameters, refer = to=20 Appendix B, "Configuration Parameters".  =20

Creating Automatic = Authorization=20 Accounts

When enrolling Oracle users, you have the option of = using=20 NetWare usernames as the basis for Oracle usernames so that database = users can=20 connect to the Oracle8 Server somewhat faster and more conveniently. = You can use=20 either Server Manager or SQL*Plus to enroll users.

When using the NetWare username for authentication, the database=20 administrator should set the OS_AUTHENT_PREFIX parameter in the = INIT%SID%.ORA=20 file (by default INITORCL.ORA). If this parameter is not set, the = default value=20 is OPS$.

The syntax for granting automatic logins when using the default = value of=20 OS_AUTHENT_PREFIX is as follows: 

SVRMGR> CREATE USER OPS$sysid IDENTIFIED =
EXTERNALLY;

where <sysid> is the user's NetWare username. If the = prefix=20 parameter is set to a value other than OPS$, use that value. For = example, to=20 enroll a user whose NetWare username is OPUS, when OS_AUTHENT_PREFIX is = set to=20 XXX, enter: 

SVRMGR> CREATE USER =
XXXOPUS IDENTIFIED EXTERNALLY;

Then, if you are logged on to the NetWare server as OPUS from a = client=20 workstation and you connect to Oracle, you need not explicitly enter = your Oracle=20 username.

For example, start SQL*Plus. At the prompt, enter your username or a = / on the=20 client workstation. Oracle searches the dictionary tables for an = automatic login=20 username that corresponds to the NetWare username OPUS, verifies it, = and allows=20 you to connect to Oracle as XXXOPUS.

Because the Oracle username is the whole name XXXOPUS, all objects = created by=20 XXXOPUS (that is, tables, views, indexes, and so on) are prefixed by = this name.=20 For another user to reference the table FISH owned by XXXOPUS, that = user enters:=20 

SVRMGR> SELECT * FROM XXXOPUS.FISH=20

An Oracle user does not have to be logged in to any file server in = order to=20 connect to the Oracle8 Server unless they are using an automatic = authorization=20 account.

You can set OS_AUTHENT_PREFIX to the null string (a set of double = quotes with=20 no string included). This eliminates the need for any prefix to the = NetWare=20 usernames.

Granting Roles with = NetWare=20 Groups

The Oracle8 Server allows database roles to be granted to users = directly by=20 NetWare. NetWare groups are created and administered using the NWADMIN = utility=20 for NetWare 4.1 from client workstations. SUPERVISOR or equivalent = access is=20 often needed to create groups.

You must set one INIT%SID%.ORA parameter (OS-ROLES) to TRUE to use = NetWare=20 groups to grant a database role. Once set, all roles are managed by the = operating system. Roles granted explicitly with SQL will not be in = effect. The=20 default setting for this parameter is FALSE.

  • To use NetWare groups to identify and grant = user=20 roles, take the following steps=20
    Table 6-5=20 Steps to Use NetWare Groups to Identify and Grant User Roles=20