Re: Full Ex/Im-port to New Instance, NT

From: Yassir Khogaly <yassir_at_khogaly.freeserve.co.uk>
Date: Sun, 11 Oct 1998 16:43:54 +0100
Message-ID: <6vqk31$3s4$1@newsreader2.core.theplanet.net>

Dear ....You surely Need To Read More About OS users. The Article attached from Oracle Corporation Clearly says USERS WILL HAVE TO BE PRECREATED ....!! Also in case of having droped Database and Re-Installing NT. Or Lost your NT BOOT, Changing From FAT TO NTFS OR ....or Restructuring & Reorgnizing your Database In Full you have to follow this...UNDERSTAND..?

Have Good Time

Regards ...

Article-ID:         <Note:61569.1>
Alias:              OLS:10676850.6
Circulation:        PUBLISHED (ENTERNAL)
Folder:             platform.Desktop.WinNT
Platform:           GENERIC  Generic issue
Topic:              4.5 -- Technical Notes
Subject:            NT: CONFIGURING OS AUTHENTICATION (OPS$ ACCOUNTS)
Modified-Date:      13-AUG-1998 18:39:43
Document-Type:      BULLETIN
Content-Type:       TEXT/PLAIN
Impact:             MEDIUM


Abstract:           This bulletin outlines the steps required to
                    configure a Windows NT server to use OS Authentication
                    from Windows NT or Windows 95 clients using SQLNET
                    2.2 TCP/IP and Named Pipes.

Please refer to the Oracle 7 Server Release 7.3 for Windows NT User's Guide for more information about Using Windows NT OS Authentication.

The steps required to use OS Authentication from an Windows NT or Windows 95 client to a Windows NT server are as follows:

NOTE: The user account needs to be the same name on the Windows NT client

      and on the Windows NT server.  Also the OPS$ account should be post
      fixed with the same name as the Windows NT account.

Create a user account on Windows NT server where the Oracle database resides.
1. Go to the Program Manager and open the Administrative Tools Group.
2. In the Administrative Tools Group double click on the User Manager Icon.
3. Go to the User Menu and select New User
4. Enter the Username: <name> and the same password the user uses on their Windows NT client.
5. Click OK and the users is created for you on Windows NT server.
Create an OPS$ account in the Oracle Database
1. After the database is started, connect to the database as a DBA either through SQLPLUS or SQLDBA
2. Issue the following command: CREATE USERS OPS$<name> IDENTIFIED EXTERNALLY;
3. Issue the following command: GRANT CONNECT TO OPS$<name>;
4. You will want to set the default tablespace and temporary tablespace for the users as well as set quotas and other parameters for the users. This is done with the alter user command as follows: ALTER USER OPS$<name> DEFAULT TABLESPACE <tablespace1> TEMPORARY TABLESPACE <tablespace2> QUOTA 10M ON <tablespace1> QUOTA 10M ON <tablespace2>;
5. For more information on alter user parameters refer to the Server Administrator Guide.
Share a directory on the Windows NT server where the Oracle database resides.

NOTE: You do not need to Share a directory if you are using SQLNET

         Named Pipes.
     a) Go to the File Manager and highlight a directory that you want to
        share.
     b) Go to the Disk Menu and click on Share As
     c) In the New Share parameter box Set the Share Name: and any User
        Limits.  Also if you do not want to share this directory with
        everyone then click on the Permissions button and limit to what
        groups or users that you desire.
     d) Now click on OK button to create the shared directory.

4. Test the new OS Authentication account.

Note: For SQL*NET 2.2 Named Pipes you do not need to perform steps

b) to f)

From the Windows NT client login as the userid that has been setup as an OPS$<userid> on the server.

NOTE: You may need to reboot the client and Login again before the OS

Authentication account will work on the database.

     b) Then run the File Manager
     c) Go to the Disk Menu and select Connect Network Drive.
     d) Select a Drive letter to be assigned to this network drive and if
you
        want to Reconnect at Logon check the check box.
     e) From the list of servers double click on the Windows NT server that
        the database reside on.
     f) Then double click on the shared directory.  If you are prompted for
a
        password, then user?s account that you created on the server has a
        different password than the user logged onto the client.  Go
        ahead and enter the password given to the user when it was created
        on the server.  You should now be sharing a network drive on the
        Database server.  If not please refer to your Windows NT
        documentation on how to share and connect to network drives.
     g) Now run SQLPLUS on the client and login to the database as follows:
        /@SQLNET2_DB_ALIAS.
        NOTE: If you do not have a SQLNET 2 database alias then you will
need
              to create one.  The easiest way for SQLNET 2.2 for Windows NT
              clients Is to use the SQL*NET EASY CONFIGURATION and create
              one.  For more information on this refer the Network Prods.
              User's Guide V2.2 online help file.
     h) You should now be connected to the database without having to enter
a
        username or password.  Again, to connect to the database using the
OS
        Authentication account connect as /@ SQLNET2_DB_ALIAS.


----------------------------------------------------------------------------

                                            Oracle Worldwide Customer

mjain_at_my-dejanews.com wrote in message <6vjs4b$li9$1_at_nnrp1.dejanews.com>...
>Yassir,
>
>---You said---
>>You have to Create all the Database Users As Well as Synonyms, Roles and
>>Grants of all the database users, otherwise your import will not import
all
>>the exported data "user Objects"..
>--------------
>
> If you have to create all these things than the purpose of
>FULL EXPORT/IMPORT is totally defeated.
>
> Believe me Oracle Full import will do it all for you. I think you
>never knew about it. Try it next time, let me know if you found otherwise,
>as I myself would like to know. I have done it myself a dozen of times.
>
>Jurji, thanks for explaining it and also clarifying about the PL/SQL
>stored procedures which may be INVALID due the the order in which they
>get created at the import time. All such procedures will be recomplied
>at the time they are executed, so this should not be an issue. If someone
>thinks it is a problem then you can use Oracle Provided COMPILE_ALL utility
>could be used.
>
>Yassir, hope this clarifies your misunderstanding.
>
>hope this helps out,
>
>Manoj Jain
>Certified Oracle Professional - OCP DBA
>Chauncey Certified Oracle7 DBA
>
>
>In article <361d1602.5989516_at_news.siol.net>,
> jmodic_at_src.si (Jurij Modic) wrote:
>> On Thu, 8 Oct 1998 11:14:53 +0100, "Yassir Khogaly"
>> <yassir_at_khogaly.freeserve.co.uk> wrote:
>>
>> >Hi...
>> >
>> >That is Not all my dear ...!
>> >
>> >You have to Create all the Database Users As Well as Synonyms, Roles and
>> >Grants of all the database users, otherwise your import will not import
all
>> >the exported data "user Objects"..
>>
>> That is simply not true. Full database export/import will take care
>> for all the things you mention. It might be the case that some PL/SQL
>> stored objects will be marked as unvalid but they will eventualy
>> recompile the first time they will be called. Hovewer, users,
>> synonyms, roles etc will be imported just fine.
>>
>> I belive the procedure proposed by Manoj Jain covers just about
>> everything needed to replicate the existing instance.
>
>
>
>>
>> >Best Regards
>> >
>> >B.Sc. Yassir Khogaly
>> >Senior Oracle DBA - Consultant
>> >United Kingdom
>>
>> Regards,
>> --
>> Jurij Modic <jmodic_at_src.si>
>> Certified Oracle7 DBA (OCP)
>> ================================================
>> The above opinions are mine and do not represent
>> any official standpoints of my employer
>>
>
>-----------== Posted via Deja News, The Discussion Network ==----------
>http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
Received on Sun Oct 11 1998 - 10:43:54 CDT