G Using the User Migration Utility</ti tle> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <meta http-equiv="Content-Language" content="EN"> <meta http-equiv="Content-Style-Type" content="text/css"> <meta http-equiv="Content-Script-Type" content="text/javascript"> <meta name="ro bots" content="all" scheme="http://www.robotstxt.org/"> <meta name="doctitle" content="Oracle® Database Advanced Security Adminis trator's Guide 10g Release 1 (10.1)"> <meta name="partno" content="B10772-01"> <meta name="docid" content="ASOAG"> <link rel="Start" href="../../index.htm" title="Home" type="text/html"> <link rel="Copyright" href="../../dcommon/html/cpyr.htm" title="Copyright" type ="text/html"> <link rel="Stylesheet" href="../../dcommon/css/doccd.css" title="Default" type="text/css"> <link rel="Contents" href="t oc.htm" title="Contents" type="text/html"> <link rel="Index" href="index.htm" title="Index" type="text/html"> <link rel="Prev" href=" asoappf.htm" title="Previous" type="text/html"> <link rel="Next" href="asogls.htm" title="Next" type="text/html"> <link rel="alternat e" href="../b10772.pdf" title="PDF version" type="application/pdf"> </head> <body> <div class="header"> <p><a name="top" id="top" hre f="#BEGIN">Skip Headers</a></p> <table summary="" cellspacing="0" cellpadding="0" width="100%"> <tr> <td align="left" valign="top"><f ont color="#330099" face="Helvetica, Arial, sans-serif"><strong>Oracle® Database Advanced Security Administrator's Guide<br> 10<i >g</i> Release 1 (10.1)</strong><br> Part Number B10772-01</font></td> <td valign="bottom" align="right"> <table summary="" cellspac ing="0" cellpadding="0" width="270"> <tr> <td align="center" valign="top"><a href="../../index.htm"><img src="../../dcommon/gifs/prod icon.gif" alt="Go to Documentation Home" border="0"><br> <font size="-2">Home</font></a></td> <td align="center" valign="top"><a href ="../../nav/portal_3.htm"><img src="../../dcommon/gifs/bookicon.gif" alt="Go to Book List" border="0"><br> <font size="-2">Book List< /font></a></td> <td align="center" valign="top"><a href="toc.htm"><img src="../../dcommon/gifs/conticon.gif" alt="Go to Table of Cont ents" border="0"><br> <font size="-2">Contents</font></a></td> <td align="center" valign="top"><a href="index.htm"><img src="../../dc ommon/gifs/indxicon.gif" alt="Go to Index" border="0"><br> <font size="-2">Index</font></a></td> <td align="center" valign="top"><a h ref="../../mix$101/b12039/toc.htm"><img src="../../dcommon/gifs/mix.gif" alt="Go to Master Index" border="0"><br> <font size="-2">Mas ter Index</font></a></td> <td align="center" valign="top"><a href="../../dcommon/html/feedback.htm"><img src="../../dcommon/gifs /feedback.gif" alt="Go to Feedback page" border="0"><br> <font size="-2">Feedback</font></a></td></tr></table></td></tr></table> <hr> <table summary="layout table" cellspacing="0" cellpadding="0" width="100%"> <tr> <td align="left" valign="top"> <table summary="layo ut table" cellspacing="0" cellpadding="0" align="left" width="90"> <tr> <td align="center" valign="top"><a href="asoappf.htm"><img sr c="../../dcommon/gifs/larrow.gif" alt="Go to previous page" border="0"><br> <font size="-2">Previous</font></a></td> <td align="cente r" valign="top"><a href="asogls.htm"><img src="../../dcommon/gifs/rarrow.gif" alt="Go to next page" border="0"><br> <font size="-2">N ext</font></a></td></tr></table></td> <td align="right" valign="top"><a href="../b10772.pdf"><font size="-2">View PDF</font></a></td> </tr></table> <a name="BEGIN"></a></div> <div class="IND"> <a name="620714"></a>  <h1 cla ss="Title"><font face="Arial, Helvetica, sans-serif" color="#330099">G<br> <a name="ASOAG200">Using the User Migration Utility</a></ font></h1>  <a name="634412"></a> <p class="BP">This chapter describes the User Migration Utility, which can be use d to perform bulk migrations of database users to an LDAP directory where they are stored and managed as enterprise users. It contain s the following topics:</p> <ul class="LB1"> <li class="LB1" type="disc"><a name="634416"></a><a href="asoappg.htm#634446">Benefits o f Migrating Local or External Users to Enterprise Users</a></li> <li class="LB1" type="disc"><a name="634420"></a><a href="asoappg.ht m#634468">Introduction to the User Migration Utility</a></li> <li class="LB1" type="disc"><a name="634424"></a><a href="asoappg.htm#6 34888">Prerequisites for Performing Migration</a></li> <li class="LB1" type="disc"><a name="634428"></a><a href="asoappg.htm#634957"> User Migration Utility Command Line Syntax</a></li> <li class="LB1" type="disc"><a name="634432"></a><a href="asoappg.htm#635026">Acc essing Help for the User Migration Utility</a></li> <li class="LB1" type="disc"><a name="634436"></a><a href="asoappg.htm#635038">Use r Migration Utility Parameters</a></li> <li class="LB1" type="disc"><a name="634440"></a><a href="asoappg.htm#635472">User Migration Utility Usage Examples</a></li> <li class="LB1" type="disc"><a name="634444"></a><a href="asoappg.htm#635686">Troubleshooting Using t he User Migration Utility</a></li></ul> <a name="634446"></a>  <h2 class="H1"><font face="Arial, Helvetica, san s-serif" color="#330099">Benefits of Migrating Local or External Users to Enterprise Users</font></h2>  <a name="634447 "></a> <p class="BP">Migrating from a database user model to an enterprise user model provides solutions to administrative, security , and usability challenges in an enterprise environment. In an enterprise user model, all user information is moved to an LDAP direct ory service.</p> <a name="634448"></a> <p class="BP">Enterprise user security provides the ability to easily and securely manage ent erprise-wide users by providing the following benefits:</p> <ul class="LB1"> <li class="LB1" type="disc"><a name="634449"></a>Central ized storage of user credentials, roles, and privileges in an LDAP version 3-compliant directory server</li> <li class="LB1" type="di sc"><a name="634450"></a>Provides the infrastructure to enable single sign-on using X.509v3-compliant certificates, which is typicall y deployed where end-to-end SSL is required</li> <li class="LB1" type="disc"><a name="634451"></a>Enhanced security <p><a name="6344 52"></a></p> <p class="BP1">Because an enterprise user model is easier to manage, security administrators can perform necessary maint enance changes to user information immediately so they have better control over access to critical network resources. In addition, an enterprise user model is easier for users to use because they have fewer passwords to remember so they are less likely to choose eas ily guessed passwords or write them down where others can copy them.</p> <a name="634463"></a> <div align="center"> <table class="No teAlso" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title="Thi s is a layout table to format a note"> <tr class="NoteAlso"> <td class="NoteAlso"><a name="634455"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH"><strong class="Bold">See Also</strong>:</strong></font> <a name="634462"></a> <p class="NB"><a href=" asoeuscp.htm#1006172">"Introduction to Enterprise User Security"</a><a href="asoeuscp.htm#1006172"></a> for detailed conceptual infor mation about enterprise user security.</p></td></tr></table></div></li></ul> <a name="634468"></a>  <h2 class=" H1"><font face="Arial, Helvetica, sans-serif" color="#330099">Introduction to the User Migration Utility</font></h2>  < a name="634472"></a> <p class="BP">The User Migration Utility is a command-line utility that is used when enterprise user administra tors decide to move their users from a local database model to an enterprise user model. This utility makes it easy to migrate thousa nds of local and external database users to an enterprise user environment in an LDAP directory where they can be managed from a cent ral location. It uses the Oracle JDBC OCI driver to connect to the database.</p> <a name="634473"></a> <p class="BP">Enterprise user administrators can select for migration any combination of the following user subsets in a database:</p> <ul class="LB1"> <li class= "LB1" type="disc"><a name="634474"></a>List of users specified on the command line or in a file</li> <li class="LB1" type="disc"><a n ame="634475"></a>All external users</li> <li class="LB1" type="disc"><a name="634476"></a>All global users</li></ul> <a name="634477" ></a> <p class="BP">In addition, enterprise user administrators can specify values for utility parameters that determine how the use rs are migrated such as</p> <ul class="LB1"> <li class="LB1" type="disc"><a name="634478"></a>Where to put the migrated users in the LDAP directory tree</li> <li class="LB1" type="disc"><a name="634479"></a>Map a user with multiple accounts on various databases to a single directory user entry</li></ul> <a name="634486"></a> <p class="BP">The following sections explain the migration process and the changes that occur to users' schemas.</p> <a name="634491"></a> <div align="center"> <table class="Note" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout table to format a note"> <tr class="Note"> <td class="Note"> <hr> <a name="634489"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">No te:</strong></font> <a name="634490"></a> <p class="NB">After external users are migrated, their external authentication and authori zation mechanisms are replaced by directory-based mechanisms. New passwords are randomly generated for migrated users if they are map ped to newly created directory entries.</p> <hr></td></tr></table></div> <a name="634492"></a>  <h3 class="H2"> <font face="Arial, Helvetica, sans-serif" color="#330099">Bulk User Migration Process Overview</font></h3>  <a name="63 4493"></a> <p class="BP">Bulk user migration is a two-phase process. In phase one, you start the migration process by populating use r information into an interface database table, where enterprise user administrators can verify that the information is accurate befo re committing the changes to the database and the directory in phase two. The process is described in the following steps:</p> <ul cl ass="LB1"> <li class="LB1" type="disc"><a name="634497"></a><a href="asoappg.htm#634507">Step 1: Phase One Preparing for the Migratio n</a></li> <li class="LB1" type="disc"><a name="634501"></a><a href="asoappg.htm#634518">Step 2: Verify User Information</a></li> <li class="LB1" type="disc"><a name="634505"></a><a href="asoappg.htm#634521">Step 3: Phase Two Completing the Migration</a></li></ul> < a name="634507"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Step 1: Phase On e Preparing for the Migration</font></h4>  <a name="634508"></a> <p class="BP">In the first part of the migration proc ess, the utility checks if the <code>ORCL_GLOBAL_USR_MIGRATION_DATA</code> interface table exists in the enterprise user administrato r's schema. If it exists, then the administrator can choose to reuse the table (clearing its contents), reuse the table and its conte nts, or re-create the table. Phase one can be run multiple times, each time adding to the interface table. If the table does not exis t, then the utility creates it in the administrator's schema. The interface table is populated with information about the migrating u sers from the database and the directory. The command line options used determine what information populates this table.</p> <a name= "634516"></a> <div align="center"> <table class="Note" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="Thi s is a layout table to format a note" title="This is a layout table to format a note"> <tr class="Note"> <td class="Note"> <hr> <a na me="634513"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">Note:</strong></font> <a name="634515"></a> <p class="N B">The utility will not create the interface table in the <code>SYS</code> schema.</p> <hr></td></tr></table></div> <a name="634518"> </a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Step 2: Verify User Information< /font></h4>  <a name="634519"></a> <p class="BP">This is an intermediate step to allow the enterprise user administrat or to verify that the user information is correct in the interface table before committing the changes to the database and the direct ory.</p> <a name="634521"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Step 3 : Phase Two Completing the Migration</font></h4>  <a name="634522"></a> <p class="BP">After the interface table user i nformation is checked, then in phase two the utility retrieves the information from the table and updates the directory and the datab ase.</p> <a name="636949"></a> <p class="BP">Depending on whether directory entries exist for migrating users, the utility creates r andom passwords as follows:</p> <ul class="LB1"> <li class="LB1" type="disc"><a name="636954"></a>If migrating users are being mapped to newly created directory entries, then the utility generates random passwords, which are used as credentials for both the database and directory.</li> <li class="LB1" type="disc"><a name="636967"></a>If migrating users are being mapped to existing directory entri es with unset database passwords, then the utility generates random database passwords only.</li></ul> <a name="636955"></a> <p clas s="BP">In either case, after generating the required random passwords, the utility then stores them in the <code>DBPASSWORD</code> an d <code>DIRPASSWORD</code> interface table columns. The enterprise user administrator can read these passwords from the interface tab le and inform migrating users.</p> <a name="634533"></a> <div align="center"> <table class="NoteAlso" border="0" width="80%" cellpad ding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout table to format a note"> <tr class="NoteAlso"> <td class="NoteAlso"><a name="634525"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">See Als o:</strong></font> <a name="634531"></a> <p class="NB"><a href="asoappg.htm#635038">"User Migration Utility Parameters"</a><a href=" asoappg.htm#635038"></a> for a list of command line options and their descriptions.</p></td></tr></table></div> <a name="634534"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">About the ORCL_GLOBAL_USR_MIGRATION_ DATA Table</font></h3>  <a name="634535"></a> <p class="BP">This is the interface table which is populated with inform ation about the migrating users during phase one of the bulk user migration process. The information that populates this table is pul led from the database and checked against existing entries in the directory. If there is corresponding information in the directory, then that is marked in the table for that user. After enterprise user administrators verify the information in this table, changes ar e made to the directory and the database in phase two.</p> <a name="634541"></a> <div align="center"> <table class="Note" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout tabl e to format a note"> <tr class="Note"> <td class="Note"> <hr> <a name="634538"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">Caution:</strong></font> <a name="634540"></a> <p class="NB">The <code>ORCL_GLOBAL_USR_MIGRATION_DATA</code> interface ta ble contains very sensitive information. Access to it should be tightly controlled using database privileges.</p> <hr></td></tr></tab le></div> <a name="634545"></a> <p class="BP">The table columns are listed in <a href="asoappg.htm#634552">Table G-1</a>.</p> < a name="634705"></a> <h5 class="TTW"><a name="634705"></a><a name="634552"></a> <strong><font face="Arial, Helvetica, sans-serif"><e m>Table G-1 ORCL_GLOBAL_USR_MIGRATION_DATA Table Schema</em></font></strong></h5> <table summary="" class="RuleFormalWide" bord er="1" width="100%" cellpadding="3" cellspacing="0" dir="ltr" title=""> <thead> <tr class="Formal"> <th class="Formal" align="left" v align="bottom" scope="col"><a name="634560"></a> <font face="Arial, Helvetica, sans-serif"><strong>Column Name</strong></font></th> < th class="Formal" align="left" valign="bottom" scope="col"><a name="634562"></a> <font face="Arial, Helvetica, sans-serif"><strong>Da taType</strong></font></th> <th class="Formal" align="left" valign="bottom" scope="col"><a name="634564"></a> <font face="Arial, Helv etica, sans-serif"><strong>Null</strong></font></th> <th class="Formal" align="left" valign="bottom" scope="col"><a name="634566"></a > <font face="Arial, Helvetica, sans-serif"><strong>Description</strong></font></th></tr></thead> <tbody> <tr class="Formal" align="l eft" valign="top"> <td class="Formal"><a name="634569"></a> <p class="TB"><code>USERNAME</code> (Primary Key)</p></td> <td class="Fo rmal"><a name="634571"></a> <p class="TB">VARCHAR2(30)</p></td> <td class="Formal"><a name="634573"></a> <p class="TB">NOT NULL</p> </td> <td class="Formal"><a name="634575"></a> <p class="TB">Database user name.</p></td></tr> <tr class="Formal" align="left" valig n="top"> <td class="Formal"><a name="634578"></a> <p class="TB"><code>OLD_SCHEMA_TYPE</code></p></td> <td class="Formal"><a name="63 4580"></a> <p class="TB">VARCHAR2(10)</p></td> <td class="Formal"><a name="634582"></a> <p class="TB">-</p></td> <td class="Formal" ><a name="634584"></a> <p class="TB">Old schema type in the database before migration.</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="634587"></a> <p class="TB"><code>PASSWORD_VERIFIER</code></p></td> <td class="Formal"><a name="634589"></a> <p class="TB">VARCHAR2(30)</p></td> <td class="Formal"><a name="634591"></a> <p class="TB">-</p></td> <td class= "Formal"><a name="634595"></a> <p class="TB">Not used</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal" ><a name="634599"></a> <p class="TB"><code>USERDN</code></p></td> <td class="Formal"><a name="634601"></a> <p class="TB">VARCHAR2(4 000)</p></td> <td class="Formal"><a name="634603"></a> <p class="TB">-</p></td> <td class="Formal"><a name="634605"></a> <p class=" TB">Distinguished Name (DN) of the user in the directory (new or existing).</p></td></tr> <tr class="Formal" align="left" valign="top "> <td class="Formal"><a name="634608"></a> <p class="TB"><code>USERDN_EXIST_FLAG</code></p></td> <td class="Formal"><a name="634610 "></a> <p class="TB">CHAR(1)</p></td> <td class="Formal"><a name="634612"></a> <p class="TB">-</p></td> <td class="Formal"><a name= "634614"></a> <p class="TB">Flag indicating whether the DN already exists in the directory.</p></td></tr> <tr class="Formal" align=" left" valign="top"> <td class="Formal"><a name="634617"></a> <p class="TB"><code>SHARED_SCHEMA</code></p></td> <td class="Formal"><a name="634619"></a> <p class="TB">VARCHAR2(30)</p></td> <td class="Formal"><a name="634621"></a> <p class="TB">-</p></td> <td class ="Formal"><a name="634623"></a> <p class="TB">Shared schema name, if users are to be mapped to a shared schema during phase two.</p> </td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="634626"></a> <p class="TB"><code>MAPPING_TYPE</ code></p></td> <td class="Formal"><a name="634628"></a> <p class="TB">VARCHAR2(10)</p></td> <td class="Formal"><a name="634630"></a> <p class="TB">-</p></td> <td class="Formal"><a name="634632"></a> <p class="TB">Mapping type (database or domain).</p></td></tr> < tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="634635"></a> <p class="TB"><code>MAPPING_LEVEL</code></p></ td> <td class="Formal"><a name="634637"></a> <p class="TB">VARCHAR2(10)</p></td> <td class="Formal"><a name="634639"></a> <p class= "TB">-</p></td> <td class="Formal"><a name="634641"></a> <p class="TB">Mapping level (entry or subtree).</p></td></tr> <tr class="Fo rmal" align="left" valign="top"> <td class="Formal"><a name="634644"></a> <p class="TB"><code>CASCADE_FLAG</code></p></td> <td class ="Formal"><a name="634646"></a> <p class="TB">CHAR(1)</p></td> <td class="Formal"><a name="634648"></a> <p class="TB">-</p></td> <t d class="Formal"><a name="634650"></a> <p class="TB">Cascade flag used when dropping a user (for shared schema mapping only).</p></t d></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="634653"></a> <p class="TB"><code>DBPASSWORD_EXIST_ FLAG</code></p></td> <td class="Formal"><a name="634655"></a> <p class="TB">CHAR(1)</p></td> <td class="Formal"><a name="634657"></a > <p class="TB">-</p></td> <td class="Formal"><a name="634659"></a> <p class="TB">Flag indicating whether the database password ver ifier already exists in the directory for this user.</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal">< a name="634662"></a> <p class="TB"><code>DBPASSWORD</code></p></td> <td class="Formal"><a name="634664"></a> <p class="TB">VARCHAR2 (30)</p></td> <td class="Formal"><a name="634666"></a> <p class="TB">-</p></td> <td class="Formal"><a name="634668"></a> <p class=" TB">Randomly generated database password verifiers that are to be stored in the directory.</p></td></tr> <tr class="Formal" align="le ft" valign="top"> <td class="Formal"><a name="634671"></a> <p class="TB"><code>DIRPASSWORD</code></p></td> <td class="Formal"><a nam e="634673"></a> <p class="TB">VARCHAR2(30)</p></td> <td class="Formal"><a name="634675"></a> <p class="TB">-</p></td> <td class="Fo rmal"><a name="634677"></a> <p class="TB">Randomly generated directory password for new entries.</p></td></tr> <tr class="Formal" al ign="left" valign="top"> <td class="Formal"><a name="634680"></a> <p class="TB"><code>PHASE_COMPLETED</code></p></td> <td class="For mal"><a name="634682"></a> <p class="TB">VARCHAR2(10)</p></td> <td class="Formal"><a name="634684"></a> <p class="TB">-</p></td> <t d class="Formal"><a name="634686"></a> <p class="TB">Information about the phase that has completed successfully.</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="634689"></a> <p class="TB"><code>NEEDS_ATTENTION_FLAG</code></ p></td> <td class="Formal"><a name="634691"></a> <p class="TB">CHAR(1)</p></td> <td class="Formal"><a name="634693"></a> <p class=" TB">-</p></td> <td class="Formal"><a name="634695"></a> <p class="TB">Flag indicating whether the row contains abnormalities that re quire administrator attention.</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="634698"></a> <p class="TB"><code>ATTENTION_DESCRIPTION</code></p></td> <td class="Formal"><a name="634700"></a> <p class="TB">VARCHAR2(100)</p></ td> <td class="Formal"><a name="634702"></a> <p class="TB">-</p></td> <td class="Formal"><a name="634704"></a> <p class="TB">Textua l hint for the administrator if the attention flag is set.</p></td></tr></tbody></table> <a name="634706"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Which Interface Table Column Values Can Be Modified between Phase One and Phase Two?</font></h4>  <a name="634707"></a> <p class="BP">After running phase one of the utility, if necessary, enterprise user administrators can change the interface table columns that are listed in <a href="asoappg.htm#634717">Tabl e G-2</a>.</p> <a name="634784"></a> <h5 class="TTW"><a name="634784"></a><a name="634717"></a> <strong><font face="Arial, Helv etica, sans-serif"><em>Table G-2 Interface Table Column Values That Can Be Modified between Phase One and Phase Two</em></font> </strong></h5> <table summary="" class="HRuleFormalWide" border="1" frame="HSIDES" rules="ROWS" width="100%" cellpadding="3" cellspac ing="0" dir="ltr" title=""> <thead> <tr class="Formal"> <th class="Formal" align="left" valign="bottom" scope="col"><a name="634723"> </a> <font face="Arial, Helvetica, sans-serif"><strong>Column Name</strong></font></th> <th class="Formal" align="left" valign="botto m" scope="col"><a name="634725"></a> <font face="Arial, Helvetica, sans-serif"><strong>Valid Values</strong></font></th> <th class="F ormal" align="left" valign="bottom" scope="col"><a name="634727"></a> <font face="Arial, Helvetica, sans-serif"><strong>Restrictions< /strong></font></th></tr></thead> <tbody> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="634730"></a> <p class="TB"><code>USERDN</code></p></td> <td class="Formal"><a name="634732"></a> <p class="TB">DN of user</p></td> <td class="Formal "><a name="634734"></a> <p class="TB">If this value is changed, then the administrator should verify that the <code>USERDN_EXIST_FLA G</code> and the <code>DBPASSWORD_EXIST_FLAG</code> values are set accordingly.</p></td></tr> <tr class="Formal" align="left" valign= "top"> <td class="Formal"><a name="634737"></a> <p class="TB"><code>USERDN_EXIST_FLAG</code></p></td> <td class="Formal"><a name="63 4739"></a> <p class="TB"><code>T</code>/<code>F</code></p></td> <td class="Formal"><a name="634741"></a> <p class="TB">If the <code >USERDN</code> column value changes, then this column value should also change to reflect the new <code>USERDN</code> status.</p></td ></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="634744"></a> <p class="TB"><code>DBPASSWORD_EXIST_F LAG</code></p></td> <td class="Formal"><a name="634746"></a> <p class="TB"><code>T</code>/<code>F</code></p></td> <td class="Formal" ><a name="634748"></a> <p class="TB">If the <code>USERDN</code> column value changes, then this column value should also change to r eflect whether a database password exists for the new <code>USERDN</code>.</p></td></tr> <tr class="Formal" align="left" valign="top" > <td class="Formal"><a name="634751"></a> <p class="TB"><code>SHARED_SCHEMA</code></p></td> <td class="Formal"><a name="634753"></a > <p class="TB">Shared schema name</p></td> <td class="Formal"><a name="634755"></a> <p class="TB">Specify only if a shared schema exists in the database.</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="634758"></a> <p clas s="TB"><code>MAPPING_TYPE</code></p></td> <td class="Formal"><a name="634760"></a> <p class="TB"><code>DB</code>/<code>DOMAIN</code> </p></td> <td class="Formal"><a name="634762"></a> <p class="TB">Set this value only if <code>SHARED_SCHEMA</code> is not set to <co de>NULL</code>.</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="634765"></a> <p class="TB">< code>MAPPING_LEVEL</code></p></td> <td class="Formal"><a name="634767"></a> <p class="TB"><code>ENTRY</code>/<code>SUBTREE</code></p ></td> <td class="Formal"><a name="634769"></a> <p class="TB">Set this value only if <code>SHARED_SCHEMA</code> is not set to <code> NULL</code>.</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="634772"></a> <p class="TB"><cod e>CASCADE_FLAG</code></p></td> <td class="Formal"><a name="634774"></a> <p class="TB"><code>T</code>/<code>F</code></p></td> <td cla ss="Formal"><a name="634776"></a> <p class="TB">Set this value only if <code>SHARED_SCHEMA</code> is not set to <code>NULL</code>. I f this column is set to true (<code>T</code>), then the users' schema objects are forcibly deleted. If this column is set to false (< code>F</code>), then the administrator must delete all user schema objects before running phase two.</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="634779"></a> <p class="TB"><code>PHASE_COMPLETED</code></p></td> <td class=" Formal"><a name="634781"></a> <p class="TB"><code>ZERO</code>/<code>ONE</code>/<code>TWO</code></p></td> <td class="Formal"><a name= "634783"></a> <p class="TB">If the administrator can resolve the conflicts or ambiguities that are specified with the <code>NEEDS_AT TENTION_FLAG</code>, then this column value can be changed to <code>ONE</code> so phase two can be run with the utility.</p></td></tr ></tbody></table> <a name="634785"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#33009 9">Migration Effects on Users' Old Database Schemas</font></h3>  <a name="634787"></a> <p class="BP">If shared schema mapping is not used, then users retain their old database schemas. If shared schema mapping is used, then users' local schemas are dr opped from the database and they are mapped to a shared schema that the enterprise user administrator creates for this purpose before performing the migration. When migrated users own database objects in their old local database schemas, administrators can specify t hat the schema and objects are not to be dropped by setting the <code>CASCADE</code> parameter to <code>NO</code>. When the <code>CAS CADE</code> parameter is set to <code>NO</code>, users who own database objects in their old local schemas do not migrate successfull y so their objects are not dropped.</p> <a name="634789"></a> <p class="BP">If some users want to retain the objects in their local database schemas and be mapped to a shared schema, then the administrator can manually migrate those objects to the shared schema bef ore performing the bulk user migration. However, when objects are migrated to a shared schema, they are shared among all users who sh are that new schema.</p> <a name="634793"></a> <p class="BP"><a href="asoappg.htm#634797">Table G-3</a> summarizes the effects of setting the <code>MAPSCHEMA</code> and <code>CASCADE</code> parameters.</p> <a name="634846"></a> <h5 class="TTW"><a name="634846 "></a><a name="634797"></a> <strong><font face="Arial, Helvetica, sans-serif"><em>Table G-3 Effects of Choosing Shared Schema Mapping with CASCADE Options</em></font></strong></h5> <table summary="" class="FormalWide" border="1" frame="HSIDES" rules="GROUPS" width=" 100%" cellpadding="3" cellspacing="0" dir="ltr" title=""> <thead> <tr class="Formal"> <th class="Formal" align="left" valign="bottom" scope="col"><a name="634805"></a> <font face="Arial, Helvetica, sans-serif"><strong>MAPSCHEMA</strong></font> <a name="634806"></a> <font face="Arial, Helvetica, sans-serif"><strong>Parameter Setting</strong></font></th> <th class="Formal" align="left" valign="bott om" scope="col"><a name="634808"></a> <font face="Arial, Helvetica, sans-serif"><strong>CASCADE</strong></font> <a name="634809"></a> <font face="Arial, Helvetica, sans-serif"><strong>Parameter Setting</strong></font></th> <th class="Formal" align="left" valign="bot tom" scope="col"><a name="634811"></a> <font face="Arial, Helvetica, sans-serif"><strong>User Migration</strong></font> <a name="6348 12"></a> <font face="Arial, Helvetica, sans-serif"><strong>Successful?</strong></font></th> <th class="Formal" align="left" valign="b ottom" scope="col"><a name="634814"></a> <font face="Arial, Helvetica, sans-serif"><strong>User Schema</strong></font> <a name="63481 5"></a> <font face="Arial, Helvetica, sans-serif"><strong>Objects Dropped?</strong></font></th></tr></thead> <tbody> <tr class="Forma l" align="left" valign="top"> <td class="Formal"><a name="634817"></a> <p class="TB">PRIVATE</p></td> <td class="Formal"><a name="63 4819"></a> <p class="TB">NO (default setting)</p></td> <td class="Formal"><a name="634821"></a> <p class="TB">Yes</p></td> <td clas s="Formal"><a name="634823"></a> <p class="TB">No</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="634825"></a> <p class="TB">SHARED</p></td> <td class="Formal"><a name="634827"></a> <p class="TB">NO</p></td> <td class="Form al"><a name="634832"></a> <p class="TB">Yes<a href="#634831"><sup><font size="-3">Foot</font> 1</sup></a></p></td> <td class="Formal "><a name="634834"></a> <p class="TB">No</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="634 836"></a> <p class="TB">SHARED</p></td> <td class="Formal"><a name="634838"></a> <p class="TB">YES</p></td> <td class="Formal"><a n ame="634843"></a> <p class="TB">Yes<a href="#634842"><sup><font size="-3">Foot</font> 2</sup></a></p></td> <td class="Formal"><a nam e="634845"></a> <p class="TB">Yes</p></td></tr></tbody></table> <table class="TableNote" width="100%" cellpadding="3" cellspacing="0 " dir="ltr" summary="" title=""> <tr class="TableNote" align="left" valign="top"> <td class="TableNote"><sup>1</sup><a name="634831"> </a> <font size="-1">Users migrate successfully only if they do not own objects in their old database schemas; otherwise, they fail.< /font><br> <sup>2</sup><a name="634842"></a> <font size="-1">Users migrate successfully and their old database schemas are dropped.</ font><br></td></tr></table> <a name="634857"></a> <div align="center"> <table class="NoteAlso" border="0" width="80%" cellpadding="0 " cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout table to format a note"> <tr cl ass="NoteAlso"> <td class="NoteAlso"><a name="634849"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">See Also:</str ong></font> <a name="634855"></a> <p class="NB"><a href="asoappg.htm#635038">"User Migration Utility Parameters"</a><a href="asoappg .htm#635038"></a> for detailed information about the <code>MAPSCHEMA</code>, <code>CASCADE</code>, and other parameters that can be u sed with this utility.</p></td></tr></table></div> <a name="634858"></a>  <h3 class="H2"><font face="Arial, Hel vetica, sans-serif" color="#330099">Migration Process</font></h3>  <a name="634859"></a> <p class="BP">Enterprise user s, those that are defined and managed in the directory, can be authenticated to the database either with a password or with a certifi cate. Users that authenticate with a password require an Oracle database password, which is stored in the directory. Users that authe nticate with a certificate must have a valid X.509 v3 certificate.</p> <a name="634862"></a> <p class="BP">This utility performs the following steps during migration:</p> <ol class="LN1" type="1"> <li class="LN1" type="1" value="1"><a name="634863"></a>Selects the users from the database for migration.</li> <li class="LN1" type="1" value="2"><a name="634864"></a>Creates corresponding user entrie s or uses existing entries in the directory.</li> <li class="LN1" type="1" value="3"><a name="634865"></a>Creates new database passwo rds and copies the corresponding verifiers to the directory for migrating users.</li> <li class="LN1" type="1" value="4"><a name="634 866"></a>Puts the schema mapping information for the migrating users' entries in the directory. (optional)</li> <li class="LN1" type= "1" value="5"><a name="634867"></a>Drops or alters the migrating users' local database schemas. (optional) <p><a name="634873"></a>< /p> <div align="center"> <table class="Note" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layo ut table to format a note" title="This is a layout table to format a note"> <tr class="Note"> <td class="Note"> <hr> <a name="634870" ></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">Note:</strong></font> <a name="634872"></a> <p class="NB">In the c urrent release, the utility migrates users with certificate-based authentication and makes them ready for password authentication. Pr eviously SSL-based authenticated users should reset their Oracle database passwords. User wallets are not created as part of this pro cess.</p> <hr></td></tr></table></div> <a name="634886"></a> <div align="center"> <table class="NoteAlso" border="0" width="80%" cel lpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout table to format a no te"> <tr class="NoteAlso"> <td class="NoteAlso"><a name="634876"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">See Also:</strong></font> <a name="634877"></a> <ul class="NL"> <li class="NL" type="disc"><a name="634881"></a><a href="asowalet.htm#1 006084">Chapter 8, "Using Oracle Wallet Manager"</a> for information about creating, managing, and using Oracle wallets.</li></u l></td></tr></table></div></li></ol> <a name="634888"></a>  <h2 class="H1"><font face="Arial, Helvetica, sans-s erif" color="#330099">Prerequisites for Performing Migration</font></h2>  <a name="634892"></a> <p class="BP">The User Migration Utility is automatically installed in the following location when you install Oracle Database Client:</p> <pre class="CE"> <a name="634897"></a>$ORACLE_HOME/rdbms/bin/umu <a name="634898"></a> </pre> <a name="634899"></a> <p class="BP">The following secti ons describe what programs must be running and what user privileges are required to successfully migrate users with the User Migratio n Utility.</p> <a name="634903"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099"> Required Database Privileges</font></h3>  <a name="634904"></a> <p class="BP">To successfully use this utility, enterp rise user administrators must have the following database privileges:</p> <ul class="LB1"> <li class="LB1" type="disc"><a name="63490 5"></a>ALTER USER</li> <li class="LB1" type="disc"><a name="634906"></a>DROP USER</li> <li class="LB1" type="disc"><a name="634907">< /a>CREATE TABLE</li> <li class="LB1" type="disc"><a name="634908"></a>SELECT_CATALOG_ROLE</li></ul> <a name="634909"></a> <p class=" BP">These privileges enable the enterprise user administrator to alter users, drop users, look at dictionary views, and create the in terface table that is used by this utility.</p> <a name="634910"></a>  <h3 class="H2"><font face="Arial, Helvet ica, sans-serif" color="#330099">Required Directory Privileges</font></h3>  <a name="634911"></a> <p class="BP">In add ition to the required database privileges, enterprise user administrators must have the directory privileges which allow them to perf orm the following tasks:</p> <ul class="LB1"> <li class="LB1" type="disc"><a name="634912"></a>Create entries in the directory under the specified user base and Oracle context location</li> <li class="LB1" type="disc"><a name="634913"></a>Browse the user entries und er the search bases</li></ul> <a name="634917"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" c olor="#330099">Required Setup to Run the User Migration Utility</font></h3>  <a name="634921"></a> <p class="BP">Perfo rm the following steps before using the User Migration Utility:</p> <ol class="LN1" type="1"> <li class="LN1" type="1" value="1"><a n ame="634922"></a>Ensure that the directory server is running with SSL enabled for no authentication.</li> <li class="LN1" type="1" va lue="2"><a name="634923"></a>Ensure that the database server is running with encryption and integrity enabled.</li> <li class="LN1" t ype="1" value="3"><a name="634924"></a>Ensure that the database listener has a TCP listening endpoint.</li> <li class="LN1" type="1" value="4"><a name="634925"></a>Create an identity management realm in the directory, if it does not already exist.</li> <li class="LN 1" type="1" value="5"><a name="634926"></a>Create the parent context for the user entries in the directory, if it does not already ex ist. The default (and recommended) location is in the <code>cn=users</code> subtree in the identity management realm.</li> <li class= "LN1" type="1" value="6"><a name="634929"></a>Set up directory access for the database Oracle home by using Oracle Net Configuration Assistant to create an <code>ldap.ora</code> file. Note that the <code>ldap.ora</code> file must include the identity management real m DN so the utility can locate the correct administrative context. The utility searches for this file under <code>$LDAP_ADMIN</code>, <code>$ORACLE_HOME/ldap/admin</code>, <code>$TNS_ADMIN</code>, <code>$ORACLE_HOME/network/admin</code>, and, finally, the Domain Nam e System (DNS) server, if you are using DNS discovery. (See <a class="olinkSRC OIDAG" href="../../dcommon/html/noexist.htm"><em class ="Italic">Oracle Internet Directory Administrator's Guide</em></a> for information about DNS server discovery.) <p><a name="634937"> </a></p> <div align="center"> <table class="Note" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout table to format a note"> <tr class="Note"> <td class="Note"> <hr> <a name="63 4933"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">Note:</strong></font> <a name="634934"></a> <ul class="NL"> < li class="NL" type="disc"><a name="634935"></a>If you plan to use shared schema mapping when migrating users, then you must create th e shared schema before running this utility.</li> <li class="NL" type="disc"><a name="634936"></a>The same <code>ldap.ora</code> file must be used for both phase one and phase two of a user migration.</li></ul> <hr></td></tr></table></div> <a name="634952"></a> <di v align="center"> <table class="NoteAlso" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout table to format a note"> <tr class="NoteAlso"> <td class="NoteAlso"><a name="634940"> </a><font face="Arial, Helvetica, sans-serif"><strong class="NH">See Also:</strong></font> <a name="634941"></a> <ul class="NL"> <li class="NL" type="disc"><a name="634947"></a><em class="Italic"><a class="olinkSRC OIDAG" href="../../dcommon/html/noexist.htm">Oracl e Internet Directory Administrator's Guide</a></em></li> <li class="NL" type="disc"><a name="634951"></a><a href="asoeuscf.htm#100490 3">Chapter 12, "Enterprise User Security Configuration Tasks and Troubleshooting"</a> for detailed information about setting up enterprise user authentication after the user migration is finished.</li></ul></td></tr></table></div></li></ol> <a name="634957"></a >  <h2 class="H1"><font face="Arial, Helvetica, sans-serif" color="#330099">User Migration Utility Command Line Syntax</font></h2>  <a name="634958"></a> <p class="BP">To perform a bulk migration of database users to enterprise u sers, use the following syntax:</p> <pre class="CE"><a name="634959"></a>umu <em class="Variable">parameter1</em> <em class="Variable ">parameter2</em> ... <a name="634960"></a> </pre> <a name="634961"></a> <p class="BP">For parameters that take a single value use t he following syntax:</p> <pre class="CE"><a name="634962"></a>keyword=value <a name="634963"></a> </pre> <a name="634964"></a> <p cl ass="BP">For parameters that take multiple values, use a colon (:) to separate the values as in the following syntax:</p> <pre class= "CE"><a name="634965"></a>keyword=value1:value2:... <a name="634966"></a> </pre> <a name="634970"></a> <p class="BP"><a href="asoapp g.htm#634975">Example 13-1</a> shows the syntax used to run the utility through both phases of the bulk user migration process.< /p> <a name="634975"></a> <h4 class="ET"><font face="Arial, Helvetica, sans-serif"><em>Example 13-1 User Migration Utility Command L ine Syntax</em></font></h4> <pre class="CE"><a name="634976"></a>umu PHASE=ONE <a name="634977"></a>DBADMIN=<em class="Variable">dba _username</em>:<em class="Variable">password </em><a name="634978"></a>ENTADMIN=<em class="Variable">enterprise_admin_DN</em>:<em cla ss="Variable">password </em><a name="634979"></a>USERS=[ALL_GLOBAL | ALL_EXTERNAL | LIST | FILE] <a name="634980"></a>DBLOCATION=<em class="Variable">database_host</em>:<em class="Variable">database_port</em>:<em class="Variable">database_sid </em><a name="634981">< /a>DIRLOCATION=<em class="Variable">ldap_directory_host</em>:<em class="Variable">ldap_directory_port </em><a name="634982"></a>USERS LIST=<em class="Variable">username1</em>:<em class="Variable">username2</em>:<em class="Variable">username3</em>:... <a name="634983" ></a>USERSFILE=<em class="Variable">filename </em><a name="634984"></a>MAPSCHEMA=[PRIVATE | SHARED]:<em class="Variable">schema_name </em><a name="634985"></a>MAPTYPE=[DB | DOMAIN]:[ENTRY | SUBTREE] <a name="634986"></a>CASCADE=[YES | NO] <a name="634987"></a>CONTEX T=<em class="Variable">user_entries_parent_location </em><a name="634988"></a>LOGFILE=<em class="Variable">filename </em><a name="634 989"></a>PARFILE=<em class="Variable">filename </em><a name="634990"></a> </pre> <a name="634991"></a>umu PHASE=TWO <pre class="CE1 "><a name="634992"></a>DBADMIN=<em class="Variable">dba_username</em>:<em class="Variable">password </em><a name="634993"></a>ENTADMI N=<em class="Variable">enterprise_admin_DN</em>:<em class="Variable">password </em><a name="634994"></a>DBLOCATION=<em class="Variabl e">database_host</em>:<em class="Variable">database_port</em>:<em class="Variable">database_sid </em><a name="634995"></a>DIRLOCATION =<em class="Variable">ldap_directory_host</em>:<em class="Variable">ldap_directory_port </em><a name="634996"></a>LOGFILE=<em class=" Variable">filename </em><a name="634997"></a>PARFILE=<em class="Variable">filename </em> </pre> <a name="635002"></a> <div align="ce nter"> <table class="Note" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout table to format a note"> <tr class="Note"> <td class="Note"> <hr> <a name="635000"></a><font face="A rial, Helvetica, sans-serif"><strong class="NH">Note:</strong></font> <a name="635001"></a> <p class="NB">If the enterprise user adm inistrator does not specify the mandatory parameters on the command line, then the utility will prompt the user for those parameters interactively.</p> <hr></td></tr></table></div> <a name="635021"></a> <div align="center"> <table class="NoteAlso" border="0" width= "80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout table to fo rmat a note"> <tr class="NoteAlso"> <td class="NoteAlso"><a name="635005"></a><font face="Arial, Helvetica, sans-serif"><strong class ="NH">See Also:</strong></font> <a name="635006"></a> <ul class="NL"> <li class="NL" type="disc"><a name="635013"></a><a href="asoap pg.htm#635038">"User Migration Utility Parameters"</a><a href="asoappg.htm#635038"></a> for a complete list of all available paramete rs and detailed information about them.</li> <li class="NL" type="disc"><a name="635020"></a><a href="asoappg.htm#635472">"User Migra tion Utility Usage Examples"</a><a href="asoappg.htm#635472"></a> for examples of typical utility uses.</li></ul></td></tr></table></ div> <a name="635026"></a>  <h2 class="H1"><font face="Arial, Helvetica, sans-serif" color="#330099">Accessing Help for the User Migration Utility</font></h2>  <a name="635030"></a> <p class="BP">To display the command-line synta x for using the User Migration Utility, enter the following command at the system prompt:</p> <pre class="CE"><a name="635031"></a>um u HELP=YES <a name="635032"></a> </pre> <a name="635033"></a> <p class="BP">While the <code>HELP</code> parameter is set to <code>YE S</code>, the utility cannot execute.</p> <a name="635038"></a>  <h2 class="H1"><font face="Arial, Helvetica, s ans-serif" color="#330099">User Migration Utility Parameters</font></h2>  <a name="635039"></a> <p class="BP">The foll owing sections list the available parameter keywords and the values that can be used with them when running this utility. The keyword s are not case-sensitive.</p> <a name="635041"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" c olor="#330099">Keyword: HELP</font></h4>  <a name="635063"></a> <table summary="" class="Simple" width="100%" dir="ltr " title=""> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635044"></a> <p class="TS"><strong class="Bold ">Valid Values:</strong></p></td> <td class="Simple"><a name="635046"></a> <p class="TS"><code>YES</code> or <code>NO</code> (These values are not case-sensitive.)</p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635048"></a> <p class="TS"><strong class="Bold">Default Setting:</strong></p></td> <td class="Simple"><a name="635050"></a> <p class="TS"><code> NO</code></p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635052"></a> <p class="TS"><strong class="Bold">Syntax Examples:</strong></p></td> <td class="Simple"><a name="635054"></a> <p class="TS"><code>HELP=YES</code></p></t d></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635056"></a> <p class="TS"><strong class="Bold">De scription:</strong></p></td> <td class="Simple"><a name="635058"></a> <p class="TS">This keyword is used to display help for the uti lity. <code>YES</code> displays the complete command-line syntax. To execute a command, set the value to <code>NO</code>, or do not s pecify a value for the parameter to accept the default.</p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple "><a name="635060"></a> <p class="TS"><strong class="Bold">Restrictions:</strong></p></td> <td class="Simple"><a name="635062"></a> <p class="TS">None</p></td></tr></table> <a name="635064"></a>  <h4 class="H3"><font face="Arial, Helvetica, s ans-serif" color="#330099">Keyword: PHASE</font></h4>  <a name="635087"></a> <table summary="" class="Simple" width="1 00%" dir="ltr" title=""> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635067"></a> <p class="TS"><stron g class="Bold">Valid Values:</strong></p></td> <td class="Simple"><a name="635069"></a> <p class="TS"><code>ONE</code> or <code>TWO< /code> (These values are not case-sensitive.)</p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name= "635071"></a> <p class="TS"><strong class="Bold">Default Setting:</strong></p></td> <td class="Simple"><a name="635073"></a> <p cla ss="TS"><code>ONE</code></p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635075"></a> <p cla ss="TS"><strong class="Bold">Syntax Examples:</strong></p></td> <td class="Simple"><a name="635077"></a> <p class="TS"><code>PHASE=O NE</code> <a name="635078"></a></p> <p class="TS"><code>PHASE=TWO</code></p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635080"></a> <p class="TS"><strong class="Bold">Description:</strong></p></td> <td class="Simple"><a nam e="635082"></a> <p class="TS">Indicates the phase for the utility. If it is <code>ONE</code>, then the utility populates the interfa ce table with the information specified in the command-line arguments and the existing user entries in the directory. If it is <code> TWO</code>, then the utility uses the information that is available in the interface table and updates the directory and the database .</p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635084"></a> <p class="TS"><strong class=" Bold">Restrictions:</strong></p></td> <td class="Simple"><a name="635086"></a> <p class="TS">None</p></td></tr></table> <a name="635 089"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Keyword: DBLOCATION</font>< /h4>  <a name="635113"></a> <table summary="" class="Simple" width="100%" dir="ltr" title=""> <tr class="Simple" align ="left" valign="top"> <td class="Simple"><a name="635092"></a> <p class="TS"><strong class="Bold">Valid Values:</strong></p></td> <t d class="Simple"><a name="635094"></a> <p class="TS"><em class="Variable">host:port:sid</em></p></td></tr> <tr class="Simple" align= "left" valign="top"> <td class="Simple"><a name="635096"></a> <p class="TS"><strong class="Bold">Default Setting:</strong></p></td> <td class="Simple"><a name="635098"></a> <p class="TS">No default setting.</p></td></tr> <tr class="Simple" align="left" valign="top "> <td class="Simple"><a name="635100"></a> <p class="TS"><strong class="Bold">Syntax Examples:</strong></p></td> <td class="Simple" ><a name="635102"></a> <p class="TS"><code>DBLOCATION=</code>my_oracle.us.oracle.com<code>:</code>7777<code>:</code>ora902</p></td>< /tr> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635104"></a> <p class="TS"><strong class="Bold">Descr iption:</strong></p></td> <td class="Simple"><a name="635106"></a> <p class="TS">Provides the host name, port number, and SID for th e database instance.</p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635108"></a> <p class=" TS"><strong class="Bold">Restrictions:</strong></p></td> <td class="Simple"> <ul class="TSB"> <li class="TSB" type="disc"><a name="63 5110"></a>This parameter is mandatory.</li> <li class="TSB" type="disc"><a name="635111"></a>The value for this parameter must be the same for both phase one and phase two.</li> <li class="TSB" type="disc"><a name="635112"></a>The database should be configured for e ncryption and integrity.</li></ul></td></tr></table> <a name="635115"></a>  <h4 class="H3"><font face="Arial, H elvetica, sans-serif" color="#330099">Keyword: DIRLOCATION</font></h4>  <a name="635137"></a> <table summary="" class= "Simple" width="100%" dir="ltr" title=""> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635118"></a> <p class="TS"><strong class="Bold">Valid Values:</strong></p></td> <td class="Simple"><a name="635120"></a> <p class="TS"><em class="Va riable">host:port</em></p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635122"></a> <p class ="TS"><strong class="Bold">Default Setting:</strong></p></td> <td class="Simple"><a name="635124"></a> <p class="TS">This value is a utomatically populated from the <code>ldap.ora</code> file by default.</p></td></tr> <tr class="Simple" align="left" valign="top"> <t d class="Simple"><a name="635126"></a> <p class="TS"><strong class="Bold">Syntax Examples:</strong></p></td> <td class="Simple"><a n ame="635128"></a> <p class="TS"><code>DIRLOCATION=</code>my_oracle.us.oracle.com<code>:</code>636</p></td></tr> <tr class="Simple" a lign="left" valign="top"> <td class="Simple"><a name="635130"></a> <p class="TS"><strong class="Bold">Description:</strong></p></td> <td class="Simple"><a name="635132"></a> <p class="TS">Provides the host name and port number for the directory server where the LD AP server is running on SSL with no authentication.</p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635134"></a> <p class="TS"><strong class="Bold">Restrictions:</strong></p></td> <td class="Simple"><a name="635136"></a> <p class="TS">The value for this parameter must be the same for both phase one and phase two.</p></td></tr></table> <a name="635139"></a >  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Keyword: DBADMIN</font></h4>  <a name="635162"></a> <table summary="" class="Simple" width="100%" dir="ltr" title=""> <tr class="Simple" align="left" val ign="top"> <td class="Simple"><a name="635142"></a> <p class="TS"><strong class="Bold">Valid Values:</strong></p></td> <td class="Si mple"><a name="635144"></a> <p class="TS"><em class="Variable">username</em><code>:</code>password</p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635146"></a> <p class="TS"><strong class="Bold">Default Setting:</strong></p> </td> <td class="Simple"><a name="635148"></a> <p class="TS">No default setting.</p></td></tr> <tr class="Simple" align="left" valig n="top"> <td class="Simple"><a name="635150"></a> <p class="TS"><strong class="Bold">Syntax Examples:</strong></p></td> <td class="S imple"><a name="635152"></a> <p class="TS"><code>DBADMIN=</code>system<code>:</code>manager</p></td></tr> <tr class="Simple" align=" left" valign="top"> <td class="Simple"><a name="635154"></a> <p class="TS"><strong class="Bold">Description:</strong></p></td> <td c lass="Simple"><a name="635156"></a> <p class="TS">Username and password for the database administrator with the required privileges for connecting to the database.</p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635158"></a> <p class="TS"><strong class="Bold">Restrictions:</strong></p></td> <td class="Simple"> <ul class="TSB"> <li class="TSB" type="disc"> <a name="635160"></a>This parameter is mandatory.</li> <li class="TSB" type="disc"><a name="635161"></a>The <code>username</code> val ue for this parameter must be the same for both phase one and phase two.</li></ul></td></tr></table> <a name="635163"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Keyword: ENTADMIN</font></h4>  <a name="635185"></a> <table summary="" class="Simple" width="100%" dir="ltr" title=""> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635166"></a> <p class="TS"><strong class="Bold">Valid Values:</strong></p></td> <td class="Simple"><a na me="635168"></a> <p class="TS"><em class="Variable">userDN:password</em></p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635170"></a> <p class="TS"><strong class="Bold">Default Setting:</strong></p></td> <td class="Simple">< a name="635172"></a> <p class="TS">No default setting.</p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple "><a name="635174"></a> <p class="TS"><strong class="Bold">Syntax Examples:</strong></p></td> <td class="Simple"><a name="635176"></ a> <p class="TS"><code>ENTADMIN=cn=</code>janeadmin<code>,dc=</code><em><code>acme</code></em><code>,dc=</code><em><code>com</code>< /em><code>:</code>welcome</p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635178"></a> <p cl ass="TS"><strong class="Bold">Description:</strong></p></td> <td class="Simple"><a name="635180"></a> <p class="TS">User Distinguish ed Name (UserDN) and the directory password for the enterprise directory administrator with the required privileges for logging in to the directory. UserDN can also be specified within double quotation marks ("...").</p></td></tr> <tr class="Simple" align="left" val ign="top"> <td class="Simple"><a name="635182"></a> <p class="TS"><strong class="Bold">Restrictions:</strong></p></td> <td class="Si mple"><a name="635184"></a> <p class="TS">This parameter is mandatory.</p></td></tr></table> <a name="635186"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Keyword: USERS</font></h4>  <a name="635 228"></a> <table summary="" class="Simple" width="100%" dir="ltr" title=""> <tr class="Simple" align="left" valign="top"> <td class= "Simple"><a name="635189"></a> <p class="TS"><strong class="Bold">Valid Values:</strong></p></td> <td class="Simple"><a name="635191 "></a> <p class="TS"><em class="Variable">value1</em><code>:</code>value2<code>...</code> <a name="635192"></a></p> <p class="TS">Va lues can be:</p> <ul class="TSB"> <li class="TSB" type="disc"><a name="635194"></a><code>ALL_EXTERNAL</code> to select all external u sers, including those who use Kerberos and RADIUS authentication</li> <li class="TSB" type="disc"><a name="635196"></a><code>ALL_GLOB AL</code> to select all global users</li> <li class="TSB" type="disc"><a name="635198"></a><code>LIST</code> to specify users on the command line with the <a href="asoappg.htm#635230">"Keyword: USERSLIST"</a></li> <li class="TSB" type="disc"><a name="635203"></a><co de>USERSFILE</code> for selecting users from the file that is specified with the <a href="asoappg.htm#635255">"Keyword: USERSFILE"</a ></li></ul> <a name="635207"></a> <p class="TS">This parameter takes multiple values. Separate values with a colon (:). <a name="635 208"></a></p> <p class="TS">(These values are not case-sensitive.)</p></td></tr> <tr class="Simple" align="left" valign="top"> <td cl ass="Simple"><a name="635210"></a> <p class="TS"><strong class="Bold">Default Setting:</strong></p></td> <td class="Simple"><a name= "635212"></a> <p class="TS">No default setting.</p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a na me="635214"></a> <p class="TS"><strong class="Bold">Syntax Examples:</strong></p></td> <td class="Simple"> <ul class="TSB"> <li clas s="TSB" type="disc"><a name="635216"></a><code>USERS=ALL_EXTERNAL:ALL_GLOBAL</code> <p><a name="635217"></a></p> <p class="TSI">This usage instructs the utility to migrate all external users and all global users.</p></li> <li class="TSB" type="disc"><a name="635218 "></a><code>USERS=ALL_EXTERNAL:FILE</code> <p><a name="635219"></a></p> <p class="TSI">This usage instructs the utility to migrate a ll external users and all users that are specified in the <code>USERSFILE</code>.</p></li></ul></td></tr> <tr class="Simple" align="l eft" valign="top"> <td class="Simple"><a name="635221"></a> <p class="TS"><strong class="Bold">Description:</strong></p></td> <td cl ass="Simple"><a name="635223"></a> <p class="TS">Specifies which users are to be migrated. If multiple values are specified for this parameter, then the utility uses the union of these sets of users.</p></td></tr> <tr class="Simple" align="left" valign="top"> <td c lass="Simple"><a name="635225"></a> <p class="TS"><strong class="Bold">Restrictions:</strong></p></td> <td class="Simple"><a name="6 35227"></a> <p class="TS">This parameter is mandatory for phase one only, and it is ignored in phase two.</p></td></tr></table> <a n ame="635230"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Keyword: USERSLIST< /font></h4>  <a name="635253"></a> <table summary="" class="Simple" width="100%" dir="ltr" title=""> <tr class="Simple " align="left" valign="top"> <td class="Simple"><a name="635233"></a> <p class="TS"><strong class="Bold">Valid Values:</strong></p>< /td> <td class="Simple"><a name="635235"></a> <p class="TS"><em class="Variable">user1</em><code>:</code>user2<code>:...</code> <a n ame="635236"></a></p> <p class="TS">Separate user names with a colon (:).</p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635238"></a> <p class="TS"><strong class="Bold">Default Setting:</strong></p></td> <td class="Simple">< a name="635240"></a> <p class="TS">No default setting.</p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple "><a name="635242"></a> <p class="TS"><strong class="Bold">Syntax Examples:</strong></p></td> <td class="Simple"><a name="635244"></ a> <p class="TS"><code>USERSLIST=</code>jdoe<code>:</code>tchin<code>:</code>adesai</p></td></tr> <tr class="Simple" align="left" va lign="top"> <td class="Simple"><a name="635246"></a> <p class="TS"><strong class="Bold">Description:</strong></p></td> <td class="Si mple"><a name="635248"></a> <p class="TS">Specifies a list of database users for migration. The users in this list are migrated with other users that are specified with the <code>USERS</code> parameter.</p></td></tr> <tr class="Simple" align="left" valign="top"> <t d class="Simple"><a name="635250"></a> <p class="TS"><strong class="Bold">Restrictions:</strong></p></td> <td class="Simple"><a name ="635252"></a> <p class="TS">This optional parameter is effective only when <code>LIST</code> is specified with the <code>USERS</cod e> parameter.</p></td></tr></table> <a name="635255"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-se rif" color="#330099">Keyword: USERSFILE</font></h4>  <a name="635277"></a> <table summary="" class="Simple" width="100 %" dir="ltr" title=""> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635258"></a> <p class="TS"><strong class="Bold">Valid Values:</strong></p></td> <td class="Simple"><a name="635260"></a> <p class="TS">File name and path.</p></td></tr > <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635262"></a> <p class="TS"><strong class="Bold">Default Setting:</strong></p></td> <td class="Simple"><a name="635264"></a> <p class="TS">No default setting.</p></td></tr> <tr class="Simpl e" align="left" valign="top"> <td class="Simple"><a name="635266"></a> <p class="TS"><strong class="Bold">Syntax Examples:</strong>< /p></td> <td class="Simple"><a name="635268"></a> <p class="TS"><code>USERSFILE=/</code>home/orahome<code>/</code>userslist<code>/</ code>hr_users.txt</p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635270"></a> <p class="TS" ><strong class="Bold">Description:</strong></p></td> <td class="Simple"><a name="635272"></a> <p class="TS">Specifies a file that co ntains a list of database users (one user listed for each line) for migration. The users in this file are migrated with other users t hat are specified with the <code>USERS</code> parameter.</p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simpl e"><a name="635274"></a> <p class="TS"><strong class="Bold">Restrictions:</strong></p></td> <td class="Simple"><a name="635276"></a> <p class="TS">This optional parameter is effective only when <code>FILE</code> is specified with the <code>USERS</code> parameter.< /p></td></tr></table> <a name="635279"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#3 30099">Keyword: MAPSCHEMA</font></h4>  <a name="635313"></a> <table summary="" class="Simple" width="100%" dir="ltr" t itle=""> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635282"></a> <p class="TS"><strong class="Bold">V alid Values:</strong></p></td> <td class="Simple"><a name="635284"></a> <p class="TS"><em class="Variable">schema_type:schema_name</ em> <a name="635285"></a></p> <p class="TS">Schema type can be:</p> <ul class="TSB"> <li class="TSB" type="disc"><a name="635287"></a ><code>PRIVATE</code> <p><a name="635288"></a></p> <p class="TSI">Retains users' old local schemas. Schema name is ignored when sche ma type is <code>PRIVATE</code>. No mapping entries are created in the directory.</p></li> <li class="TSB" type="disc"><a name="63529 0"></a><code>SHARED</code> <p><a name="635291"></a></p> <p class="TSI">Maps users to a shared schema. Mapping entries are created in the directory. Schema name specifies the shared schema name. During shared schema mapping, whether users' local schemas are dropped from the database is determined by the <a href="asoappg.htm#635364">"Keyword: CASCADE"</a> setting.</p></li></ul> <a name="635295"></ a> <p class="TS">(These values are not case-sensitive.)</p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simpl e"><a name="635297"></a> <p class="TS"><strong class="Bold">Default Setting:</strong></p></td> <td class="Simple"><a name="635299">< /a> <p class="TS"><code>PRIVATE</code></p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="63530 1"></a> <p class="TS"><strong class="Bold">Syntax Examples:</strong></p></td> <td class="Simple"><a name="635303"></a> <p class="TS "><code>MAPSCHEMA=SHARED:</code>HR_ALL</p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635305 "></a> <p class="TS"><strong class="Bold">Description:</strong></p></td> <td class="Simple"><a name="635307"></a> <p class="TS">Spe cifies whether the utility populates the interface table with schema mapping information.</p></td></tr> <tr class="Simple" align="lef t" valign="top"> <td class="Simple"><a name="635309"></a> <p class="TS"><strong class="Bold">Restrictions:</strong></p></td> <td cla ss="Simple"> <ul class="TSB"> <li class="TSB" type="disc"><a name="635311"></a>See the <code>SHARED</code> option under Valid Values. </li> <li class="TSB" type="disc"><a name="635312"></a>This parameter is only valid for phase one.</li></ul></td></tr></table> <a nam e="635314"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Keyword: MAPTYPE</fon t></h4>  <a name="635351"></a> <table summary="" class="Simple" width="100%" dir="ltr" title=""> <tr class="Simple" al ign="left" valign="top"> <td class="Simple"><a name="635317"></a> <p class="TS"><strong class="Bold">Valid Values:</strong></p></td> <td class="Simple"><a name="635319"></a> <p class="TS"><em class="Variable">mapping_type</em><code>:</code>mapping_level <a name="6 35320"></a></p> <p class="TS">Mapping type can be:</p> <ul class="TSB"> <li class="TSB" type="disc"><a name="635322"></a><code>DB</co de></li> <li class="TSB" type="disc"><a name="635324"></a><code>DOMAIN</code></li></ul> <a name="635325"></a> <p class="TS">Mapping level can be:</p> <ul class="TSB"> <li class="TSB" type="disc"><a name="635327"></a><code>ENTRY</code></li> <li class="TSB" type="dis c"><a name="635329"></a><code>SUBTREE</code></li></ul> <a name="635330"></a> <p class="TS">Separate mapping type from mapping level with a colon (:). <a name="635331"></a></p> <p class="TS">(These values are not case-sensitive.)</p></td></tr> <tr class="Simple" ali gn="left" valign="top"> <td class="Simple"><a name="635333"></a> <p class="TS"><strong class="Bold">Default Setting:</strong></p></t d> <td class="Simple"><a name="635335"></a> <p class="TS"><code>DB:ENTRY</code></p></td></tr> <tr class="Simple" align="left" valign ="top"> <td class="Simple"><a name="635337"></a> <p class="TS"><strong class="Bold">Syntax Examples:</strong></p></td> <td class="Si mple"><a name="635339"></a> <p class="TS"><code>MAPTYPE=</code>DOMAIN<code>:</code>SUBTREE</p></td></tr> <tr class="Simple" align="l eft" valign="top"> <td class="Simple"><a name="635341"></a> <p class="TS"><strong class="Bold">Description:</strong></p></td> <td cl ass="Simple"><a name="635343"></a> <p class="TS">Specifies the type of schema mapping that is to be applied when <a href="asoappg.ht m#635279">"Keyword: MAPSCHEMA"</a> is set to <code>SHARED</code>. If <code>DB</code> is specified as the mapping type, then the utili ty creates a mapping in directory for the database. If <code>DOMAIN</code> is specified as the mapping type, then the utility creates a mapping in the directory for the domain containing the database. For domain mapping, the utility determines the domain that contai ns the database by an LDAP search in the relevant Oracle context.</p></td></tr> <tr class="Simple" align="left" valign="top"> <td cla ss="Simple"><a name="635348"></a> <p class="TS"><strong class="Bold">Restrictions:</strong></p></td> <td class="Simple"><a name="635 350"></a> <p class="TS">This parameter is effective only when <code>MAPSCHEMA</code> is set to <code>SHARED</code>.</p></td></tr></t able> <a name="635362"></a> <div align="center"> <table class="NoteAlso" border="0" width="80%" cellpadding="0" cellspacing="0" dir= "ltr" summary="This is a layout table to format a note" title="This is a layout table to format a note"> <tr class="NoteAlso"> <td cl ass="NoteAlso"><a name="635354"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">See Also:</strong></font> <a name="6 35360"></a> <p class="NB"><a href="asoappg.htm#635601">"About Using the SUBTREE Mapping Level Option"</a><a href="asoappg.htm#635601 "></a> for more information about using this mapping level option.</p></td></tr></table></div> <a name="635364"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Keyword: CASCADE</font></h4>  <a name=" 635390"></a> <table summary="" class="Simple" width="100%" dir="ltr" title=""> <tr class="Simple" align="left" valign="top"> <td cla ss="Simple"><a name="635367"></a> <p class="TS"><strong class="Bold">Valid Values:</strong></p></td> <td class="Simple"> <ul class=" TSB"> <li class="TSB" type="disc"><a name="635369"></a><code>NO</code> <p><a name="635370"></a></p> <p class="TSI">When users are ma pped to a shared schema, the utility tries to drop their local schemas from the database. If this parameter is set to NO, then users are migrated only if they do not own objects in their local schema. Users who own objects in their old local schemas do not migrate a nd produce an error message in the migration log file.</p></li> <li class="TSB" type="disc"><a name="635371"></a><code>YES</code> <p ><a name="635372"></a></p> <p class="TSI">If this parameter is set to YES, then all users' schema objects are dropped along with thei r local schemas when they are migrated. Privileges and roles that were previously granted to the users are also revoked.</p></li></ul > <a name="635373"></a> <p class="TS">(These values are not case-sensitive.)</p></td></tr> <tr class="Simple" align="left" valign="t op"> <td class="Simple"><a name="635375"></a> <p class="TS"><strong class="Bold">Default Setting:</strong></p></td> <td class="Simpl e"><a name="635377"></a> <p class="TS"><code>NO</code></p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple "><a name="635379"></a> <p class="TS"><strong class="Bold">Syntax Examples:</strong></p></td> <td class="Simple"><a name="635381"></ a> <p class="TS"><code>CASCADE=YES</code></p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="63 5383"></a> <p class="TS"><strong class="Bold">Description:</strong></p></td> <td class="Simple"><a name="635385"></a> <p class="TS" >Specifies whether a user's local schema is dropped when the user is mapped to a shared schema.</p></td></tr> <tr class="Simple" alig n="left" valign="top"> <td class="Simple"><a name="635387"></a> <p class="TS"><strong class="Bold">Restrictions:</strong></p></td> < td class="Simple"><a name="635389"></a> <p class="TS">This parameter is effective only when <code>MAPSCHEMA</code> is set to <code>S HARED</code>.</p></td></tr></table> <a name="635391"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-se rif" color="#330099">Keyword: CONTEXT</font></h4>  <a name="635421"></a> <table summary="" class="Simple" width="100%" dir="ltr" title=""> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635394"></a> <p class="TS"><strong cl ass="Bold">Valid Values:</strong></p></td> <td class="Simple"><a name="635396"></a> <p class="TS">Distinguished Name (DN) of the par ent for user entries. This is the same as the user search base or user create base in an Oracle Internet Directory identity managemen t realm. <a name="635397"></a></p> <p class="TS">Parent DN can also be specified within double quotation marks ("...").</p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635399"></a> <p class="TS"><strong class="Bold">Default S etting:</strong></p></td> <td class="Simple"><a name="635401"></a> <p class="TS">This value is automatically populated from the <cod e>DEFAULT_ADMIN_CONTEXT</code> setting in the <code>ldap.ora</code> file by default. This places new user entries directly under the Oracle Context's parent entry. <a name="637382"></a></p> <p class="TS">In 10<em class="Italic">g</em> Release 1 (10.1), this is not t he preferred location for user entries, so do not use the default setting for this parameter unless it is specifically desired. Inste ad, Oracle recommends that you use "<code>cn=Users, <realm_DN></code>" as your default. Refer to <a href="asoeuscp.htm#1011043" >Figure 11-3, "Related Entries in a Realm Oracle Context"</a><a href="asoeuscp.htm#1011043"></a> for a directory information tre e diagram that shows an Oracle Context.</p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="63540 9"></a> <p class="TS"><strong class="Bold">Syntax Examples:</strong></p></td> <td class="Simple"><a name="635411"></a> <p class="TS "><code>CONTEXT="c=Users, c=us"</code></p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635413 "></a> <p class="TS"><strong class="Bold">Description:</strong></p></td> <td class="Simple"><a name="635415"></a> <p class="TS">Spe cifies the DN of the parent entry under which user entries are created in the directory if there is no directory entry that matches t he userID for the user.</p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635417"></a> <p clas s="TS"><strong class="Bold">Restrictions:</strong></p></td> <td class="Simple"><a name="635420"></a> <p class="TS">This parameter is only valid for phase one.</p></td></tr></table> <a name="635422"></a>  <h4 class="H3"><font face="Arial, Helve tica, sans-serif" color="#330099">Keyword: LOGFILE</font></h4>  <a name="635444"></a> <table summary="" class="Simple" width="100%" dir="ltr" title=""> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635425"></a> <p class="T S"><strong class="Bold">Valid Values:</strong></p></td> <td class="Simple"><a name="635427"></a> <p class="TS">File name and path.</ p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635429"></a> <p class="TS"><strong class="Bol d">Default Setting:</strong></p></td> <td class="Simple"><a name="635431"></a> <p class="TS"><em class="Variable">$ORACLE_HOME</em>< code>/network/log/umu.log</code></p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635433"></a> <p class="TS"><strong class="Bold">Syntax Examples:</strong></p></td> <td class="Simple"><a name="635435"></a> <p class="TS"><code >LOGFILE=</code>home/orahome<code>/network/log/</code>filename.log</p></td></tr> <tr class="Simple" align="left" valign="top"> <td cl ass="Simple"><a name="635437"></a> <p class="TS"><strong class="Bold">Description:</strong></p></td> <td class="Simple"><a name="635 439"></a> <p class="TS">Specifies the log file where details about the migration for each user are written.</p></td></tr> <tr class= "Simple" align="left" valign="top"> <td class="Simple"><a name="635441"></a> <p class="TS"><strong class="Bold">Restrictions:</stron g></p></td> <td class="Simple"><a name="635443"></a> <p class="TS">None</p></td></tr></table> <a name="635445"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Keyword: PARFILE</font></h4>  <a name=" 635467"></a> <table summary="" class="Simple" width="100%" dir="ltr" title=""> <tr class="Simple" align="left" valign="top"> <td cla ss="Simple"><a name="635448"></a> <p class="TS"><strong class="Bold">Valid Values:</strong></p></td> <td class="Simple"><a name="635 450"></a> <p class="TS">File name and path.</p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name=" 635452"></a> <p class="TS"><strong class="Bold">Default Setting:</strong></p></td> <td class="Simple"><a name="635454"></a> <p clas s="TS">No default setting.</p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple"><a name="635456"></a> <p c lass="TS"><strong class="Bold">Syntax Examples:</strong></p></td> <td class="Simple"><a name="635458"></a> <p class="TS"><code>PARFI LE=</code>home/orahome<code>/network/</code>usr/par.txt</p></td></tr> <tr class="Simple" align="left" valign="top"> <td class="Simple "><a name="635460"></a> <p class="TS"><strong class="Bold">Description:</strong></p></td> <td class="Simple"><a name="635462"></a> <p class="TS">Specifies a text file which contains a list of these parameters that are intended to be used in a user migration. Each parameter must be listed on a separate line in the file. If a parameter is specified in both the parameter file and on the command li ne, then the one specified on the command line takes precedence.</p></td></tr> <tr class="Simple" align="left" valign="top"> <td clas s="Simple"><a name="635464"></a> <p class="TS"><strong class="Bold">Restrictions:</strong></p></td> <td class="Simple"><a name="6354 66"></a> <p class="TS">None</p></td></tr></table> <a name="635472"></a>  <h2 class="H1"><font face="Arial, Hel vetica, sans-serif" color="#330099">User Migration Utility Usage Examples</font></h2>  <a name="635473"></a> <p class= "BP">The following sections contain examples of the syntax for some typical uses of this utility.</p> <a name="635474"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Migrating Users While Retaining Their Own Sche mas</font></h3>  <a name="635475"></a> <p class="BP">To migrate users while retaining their old database schemas, set the <code>MAPSCHEMA</code> parameter to <code>PRIVATE</code>, which is the default setting. For example, to migrate users <code>scott 1</code>, <code>scott2</code>, and all external database users, while retaining their old schemas, to the directory at <code>c=Users, c=us</code> with the newly generated database and directory passwords, the syntax shown in <a href="asoappg.htm#635480">Example ;13-2</a> is used.</p> <a name="635480"></a> <h4 class="ET"><font face="Arial, Helvetica, sans-serif"><em>Example 13-2 Migrating Use rs with MAPSCHEMA=PRIVATE (Default)</em></font></h4> <pre class="CE"><a name="635482"></a>umu PHASE=ONE <a name="635483"></a>DBLOCAT ION=<em class="Variable">machine1</em>:<em class="Variable">1521</em>:<em class="Variable">ora_sid </em><a name="635484"></a>DBADMIN= <em class="Variable">system</em>:<em class="Variable">manager </em><a name="635485"></a>USERS=ALL_EXTERNAL:LIST <a name="635486"></a> USERSLIST=<em class="Variable">scott1</em>:<em class="Variable">scott2 </em><a name="635487"></a>DIRLOCATION=<em class="Variable">mac hine2</em>:<em class="Variable">636 </em><a name="635488"></a>CONTEXT="<em class="Variable">c=Users,c=us</em>" <a name="635489"></a>E NTADMIN="<em class="Variable">cn=janeadmin</em>":<em class="Variable">welcome </em><a name="635490"></a> </pre> <a name="635491"></a >umu PHASE=TWO <pre class="CE1"><a name="635492"></a>DBLOCATION=<em class="Variable">machine1</em>:<em class="Variable">1521</em>:<e m class="Variable">ora_sid </em><a name="635493"></a>DBADMIN=<em class="Variable">system</em>:<em class="Variable">manager </em><a na me="635494"></a>DIRLOCATION=<em class="Variable">machine2</em>:<em class="Variable">636 </em><a name="635495"></a>ENTADMIN="<em class ="Variable">cn=janeadmin</em>":<em class="Variable">welcome </em><a name="635496"></a> </pre> <a name="635497"></a> <p class="BP">Af ter phase one completes successfully, the interface table is populated with the user migration information. Then the enterprise user administrator can review the table to confirm its contents. Because no value was specified for the <code>MAPSCHEMA</code> parameter, the utility runs phase one using the default value, <code>PRIVATE</code>, so all users' old database schemas and objects are retained .</p> <a name="635498"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Migrating Users and Mapping to a Shared Schema</font></h3>  <a name="635499"></a> <p class="BP">To migrate users and map them t o a new shared schema, dropping their old database schemas, set the <code>MAPSCHEMA</code> parameter to <code>SHARED</code>. The shar ed schema must already exist or the enterprise user administrator must create it before running the utility with this parameter setti ng. In the following example, users <code>scott1</code>, <code>scott2</code>, and all external database users are migrated to the dir ectory at <code>c=Users, c=us</code> with newly generated database and directory passwords, while mapping all migrated users to a new shared schema in the database.</p> <a name="635503"></a> <p class="BP">Use the syntax shown in <a href="asoappg.htm#635505">Example G-1</a> to run the migration process with <code>MAPSCHEMA</code> set to <code>SHARED</code>.</p> <a name="635505"></a> <h4 cla ss="ET"><font face="Arial, Helvetica, sans-serif"><em>Example G-1 Migrating Users with MAPSCHEMA=SHARED</em></font></h4> <pre class=" CE"><a name="635507"></a>umu PHASE=ONE <a name="635508"></a>DBLOCATION=<em class="Variable">machine1</em>:<em class="Variable">1521< /em>:<em class="Variable">ora_sid </em><a name="635509"></a>DBADMIN=<em class="Variable">system</em>:<em class="Variable">manager </e m><a name="635510"></a>USERS=ALL_EXTERNAL:LIST <a name="635511"></a>USERSLIST=<em class="Variable">scott1</em>:<em class="Variable">s cott2 </em><a name="635512"></a>MAPSCHEMA=SHARED:<em class="Variable">schema_32 </em><a name="635513"></a>DIRLOCATION=<em class="Vari able">machine2</em>:<em class="Variable">636 </em><a name="635514"></a>CONTEXT="<em class="Variable">c=Users, c=us</em>" <a name="635 515"></a>ENTADMIN="<em class="Variable">cn=janeadmin</em>":<em class="Variable">welcome </em> </pre> <a name="635516"></a><a name="6 35517"></a>umu PHASE=TWO <pre class="CE1"><a name="635518"></a>DBLOCATION=<em class="Variable">machine1</em>:<em class="Variable">15 21</em>:<em class="Variable">ora_sid </em><a name="635519"></a>DBADMIN=<em class="Variable">system</em>:<em class="Variable">manager </em><a name="635520"></a>DIRLOCATION=<em class="Variable">machine2</em>:<em class="Variable">636 </em><a name="635521"></a>ENTADMIN= "<em class="Variable">cn=janeadmin</em>":<em class="Variable">welcome </em><a name="635522"></a> </pre> <a name="635523"></a> <p cla ss="BP">After phase one completes successfully, the interface table is populated with the user migration information. Then the admini strator can review the table to confirm its contents. Users <code>scott1</code>, <code>scott2</code>, and the external users are assi gned new randomly generated database and directory passwords. Because no value was specified for the <code>CASCADE</code> parameter, the utility runs phase one using the default value, <code>NO</code>, which means that migrating users who own database objects in the ir old database schemas will fail and their schemas will not be automatically dropped. To determine which users have failed, review t he log file that is located at <code>$ORACLE_HOME/network/log/umu.log</code> by default.</p> <a name="635524"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Mapping Users to a Shared Schema Using Different CASCAD E Options</font></h4>  <a name="635525"></a> <p class="BP">The <code>CASCADE</code> parameter setting determines wheth er users' old database schemas are automatically dropped when mapping to a shared schema during migration. <code>CASCADE</code> can b e used only when <code>MAPSCHEMA</code> is set to <code>SHARED</code>.</p> <a name="635526"></a>  <h5 class="H4 "><font face="Arial, Helvetica, sans-serif" color="#330099">Mapping Users to a Shared Schema with CASCADE=NO</font></h5>  <h5 class="H4"><font face="Arial, Helvetica, sans-serif" color="#330 099">Mapping Users to a Shared Schema with CASCADE=YES</font></h5>  <a name="635541"></a> <a name="635542"></a> <p cla ss="BP">If it is known that no migrating users own database objects or want to retain the objects that they own in their old database schemas, then setting the <code>CASCADE</code> parameter to <code>YES</code> automatically drops all users' schemas and schema objec ts and maps them to the new shared schema. <a href="asoappg.htm#635547">Example G-2</a> shows the syntax to use when setting <co de>CASCADE</code> to <code>YES</code>. In this example, users <code>scott1</code>, <code>scott2</code>, and all external database use rs are migrated to the directory at <code>c=Users, c=us</code>, while mapping all migrating users to a new shared schema in the datab ase.</p> <a name="635547"></a> <h4 class="ET"><font face="Arial, Helvetica, sans-serif"><em>Example G-2 Migrating Users with Shared Schema Mapping and CASCADE=YES</em></font></h4> <pre class="CE"><a name="635549"></a>umu PHASE=ONE <a name="635550"></a>DBLOCATION=< em class="Variable">machine1</em>:<em class="Variable">1521</em>:<em class="Variable">ora_sid </em><a name="635551"></a>DBADMIN=<em c lass="Variable">system</em>:<em class="Variable">manager </em><a name="635552"></a>USERS=ALL_EXTERNAL:LIST <a name="635553"></a>USERS LIST=<em class="Variable">scott1</em>:<em class="Variable">scott2 </em><a name="635554"></a>MAPSCHEMA=SHARED:<em class="Variable">sch ema_32 </em><a name="635555"></a>CASCADE=YES <a name="635556"></a>DIRLOCATION=<em class="Variable">machine2</em>:<em class="Variable" >636 </em><a name="635557"></a>CONTEXT="<em class="Variable">c=Users, c=us" </em><a name="635558"></a>ENTADMIN="<em class="Variable"> cn=janeadmin</em>":<em class="Variable">welcome </em> </pre> <a name="635559"></a><a name="635560"></a>umu PHASE=TWO <pre class="CE 1"><a name="635561"></a>DBLOCATION=<em class="Variable">machine1</em>:<em class="Variable">1521</em>:<em class="Variable">ora_sid </e m><a name="635562"></a>DBADMIN=<em class="Variable">system</em>:<em class="Variable">manager </em><a name="635563"></a>DIRLOCATION=<e m class="Variable">machine2</em>:<em class="Variable">636 </em><a name="635564"></a>ENTADMIN="<em class="Variable">cn=janeadmin</em>" :<em class="Variable">welcome </em><a name="635565"></a> </pre> <a name="635566"></a> <p class="BP">After phase one completes succes sfully, the interface table is populated with the user migration information. Then the administrator can review the table to confirm its contents. Because the <code>CASCADE</code> parameter is set to YES, all migrated users' old database schemas are automatically dr opped, including those who own database objects.</p> <a name="635572"></a> <div align="center"> <table class="Note" border="0" width ="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout table to f ormat a note"> <tr class="Note"> <td class="Note"> <hr> <a name="635569"></a><font face="Arial, Helvetica, sans-serif"><strong class= "NH">Caution:</strong></font> <a name="635571"></a> <p class="NB">If you set the <code>CASCADE</code> parameter to <code>YES</code>, then Oracle recommends that enterprise user administrators back up the database or take an export dump of the users being migrated b efore running this utility. Then if migrated users want their old database objects, they can retrieve them from the export dump.</p> <hr></td></tr></table></div> <a name="635573"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" co lor="#330099">Mapping Users to a Shared Schema Using Different MAPTYPE Options</font></h4>  <a name="635574"></a> <p c lass="BP">When <code>MAPSCHEMA</code> is set to <code>SHARED</code>, the mapping type can be set by specifying a value for the <code> MAPTYPE</code> parameter. This parameter takes two values, which are the mapping type and the mapping level.</p> <a name="635575"></a > <p class="BP">Mapping type can be set at <code>DB</code>, for database, or <code>DOMAIN</code>, for enterprise domain. When mappin g type <code>DB</code> is specified, the mapping is applied only to the database where the shared schema is stored. When <code>DOMAIN </code> is specified as the mapping type, then the mapping is applied to the enterprise domain that contains the database where the s hared schema is stored and also applies to all databases in that domain.</p> <a name="635576"></a> <p class="BP">Mapping level can b e set to <code>ENTRY</code> or <code>SUBTREE</code>. When <code>ENTRY</code> is specified then users are mapped to the shared schema using their full distinguished name (DN). This results in one mapping for each user. When <code>SUBTREE</code> is specified then grou ps of users who share part of their DNs are mapped together. This results in one mapping for user groups already grouped under some c ommon root in the directory tree. <a href="asoappg.htm#635581">Example G-3</a> shows the syntax to use when using the <code>MAPT YPE</code> parameter. In this example, users <code>scott1</code>, <code>scott2</code>, and all external database users are migrated t o the directory at <code>c=Users, c=us</code>, while mapping all migrated users to a new shared schema in the database. In this examp le, the mapping will apply to the enterprise domain that contains the database and the mapping will be performed at the entry level, resulting in a mapping for each user.</p> <a name="635581"></a> <h4 class="ET"><font face="Arial, Helvetica, sans-serif"><em>Example G-3 Migrating Users with Shared Schema Mapping Using the MAPTYPE Parameter</em></font></h4> <pre class="CE"><a name="635583"></a>umu PHASE=ONE <a name="635584"></a>DBLOCATION=<em class="Variable">machine1</em>:<em class="Variable">1521</em>:<em class="Variable">or a_sid </em><a name="635585"></a>DBADMIN=<em class="Variable">system</em>:<em class="Variable">manager </em><a name="635586"></a>USERS =ALL_EXTERNAL:LIST <a name="635587"></a>USERSLIST=<em class="Variable">scott1</em>:<em class="Variable">scott2 </em><a name="635588"> </a>MAPSCHEMA=SHARED:<em class="Variable">schema_32 </em><a name="635589"></a>MAPTYPE=DOMAIN:ENTRY <a name="635590"></a>DIRLOCATION=< em class="Variable">machine2</em>:<em class="Variable">636 </em><a name="635591"></a>CONTEXT="<em class="Variable">c=Users, c=us</em> " <a name="635592"></a>ENTADMIN="<em class="Variable">cn=janeadmin</em>":<em class="Variable">welcome </em> </pre> <a name="635593"> </a><a name="635594"></a>umu PHASE=TWO <pre class="CE1"><a name="635595"></a>DBLOCATION=<em class="Variable">machine1</em>:<em class ="Variable">1521</em>:<em class="Variable">ora_sid </em><a name="635596"></a>DBADMIN=<em class="Variable">system</em>:<em class="Vari able">manager </em><a name="635597"></a>DIRLOCATION=<em class="Variable">machine2</em>:<em class="Variable">636 </em><a name="635598" ></a>ENTADMIN="<em class="Variable">cn=janeadmin</em>":<em class="Variable">welcome </em> </pre> <a name="635601"></a> <h5 class="H4"><font face="Arial, Helvetica, sans-serif" color="#330099">About Using the SUBTREE Mapping Level Option</font> </h5>  <a name="635602"></a> <p class="BP">If a user (<code>scott</code>, for example) who is being migrated will have future user entries in a subtree under it, then it makes sense to create a subtree level mapping from this user entry (<code>cn=scot t</code>) to a schema. However, the database does not interpret the user to be in the subtree so the mapping does not apply to <code> scott</code> himself. For example, if you are migrating the user <code>scott</code> with the DN <code>cn=scott,o=acme</code>, and you choose <code>SUBTREE</code> as the mapping level when you run the utility, then a new mapping is created from <code>cn=scott,o=acme< /code> to the shared schema, but the user <code>scott</code> is not mapped to that schema. Only new users who are created under the < code>scott</code> directory entry are mapped to the shared schema. Consequently, the <code>SUBTREE</code> mapping level should only b e specified when user directory entries are placed under other user directory entries, which would be an unusual directory configurat ion.</p> <a name="635603"></a> <p class="BP">If you want an arbitrary subtree user to be mapped to a single shared schema with only one mapping entry, then you must use Enterprise Security Manager to create that mapping.</p> <a name="635620"></a> <div align="cente r"> <table class="NoteAlso" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to forma t a note" title="This is a layout table to format a note"> <tr class="NoteAlso"> <td class="NoteAlso"><a name="635609"></a><font face ="Arial, Helvetica, sans-serif"><strong class="NH">See Also:</strong></font> <a name="635616"></a> <p class="NB"><a href="asoadmeu.h tm#1008852">"Managing Enterprise Domain Database Schema Mappings"</a><a href="asoadmeu.htm#1008852"></a> for information about using Enterprise Security Manager.</p></td></tr></table></div> <a name="635621"></a>  <h3 class="H2"><font face="Aria l, Helvetica, sans-serif" color="#330099">Migrating Users Using the PARFILE, USERSFILE, and LOGFILE Parameters</font></h3>  <a name="635625"></a> <p class="BP">It is possible to enter user information and User Migration Utility parameters into a text file and pass the information and parameters to the utility using the <code>PARFILE</code> and <code>USERSFILE</code> parameters. The <code>LOGFILE</code> parameter sets the directory path for the log file where details about the migration for each user are written. </p> <a name="635626"></a> <p class="BP">The <code>PARFILE</code> parameter tells the utility where a text file is located that cont ains the parameters for a bulk user migration. The <code>USERSFILE</code> parameter works like the <code>PARFILE</code> parameter, ex cept it contains database users instead of parameters. The parameters and users lists contain one parameter or user for each line. Th e <code>LOGFILE</code> parameter tells the utility where to write the system events that occur during a user migration, such as error s. Use the <code>USERSFILE</code> parameter during phase one of the migration process. The <code>PARFILE</code> and <code>LOGFILE</co de> parameters can be used in both phases.</p> <a name="635630"></a> <p class="BP"><a href="asoappg.htm#635632">Example G-4</a> shows the syntax for a typical parameter text file to migrate users <code>scott1</code>, <code>scott2</code>, and all external datab ase users, while retaining their old schemas, to the directory at <code>c=Users, c=us</code>. In this example a log of migration even ts is written to the file <code>errorfile1</code> in the directory where the utility is run. If another location is desired, then inc lude the path with the file name.</p> <a name="635632"></a> <h4 class="ET"><font face="Arial, Helvetica, sans-serif"><em>Example G-4 Parameter Text File (<strong class="Bold">par.txt</strong>) to Use with the PARFILE Parameter</em></font></h4> <pre class="CE"><a na me="635634"></a>DBLOCATION=<em class="Variable">machine1</em>:<em class="Variable">1521</em>:<em class="Variable">ora_sid </em><a nam e="635635"></a>DBADMIN=<em class="Variable">system</em>:<em class="Variable">manager </em><a name="635636"></a>USERS=ALL_EXTERNAL:LIS T:FILE <a name="635637"></a>USERSLIST=<em class="Variable">scott1</em>:<em class="Variable">scott2 </em><a name="635638"></a>USERSFIL E=<em class="Variable">usrs.txt </em><a name="635639"></a>DIRLOCATION=<em class="Variable">machine2</em>:<em class="Variable">636 </e m><a name="635640"></a>CONTEXT="<em class="Variable">c=Users, c=us</em>" <a name="635641"></a>ENTADMIN="<em class="Variable">cn=janea dmin</em>":<em class="Variable">welcome </em><a name="635642"></a>LOGFILE=<em class="Variable">errorfile1 </em><a name="635643"></a> </pre> <a name="635647"></a> <p class="BP"><a href="asoappg.htm#635649">Example G-5</a> shows the syntax for a typical users li st text file.</p> <a name="635649"></a> <h4 class="ET"><font face="Arial, Helvetica, sans-serif"><em>Example G-5 Users List Text Fil e (<strong class="Bold">usrs.txt</strong>) to Use with the USERSFILE Parameter</em></font></h4> <pre class="CE"><a name="635651"></a> user1 <a name="635652"></a>user2 <a name="635653"></a>user3 <a name="635654"></a> </pre> <a name="635655"></a> <p class="BP">To exec ute phase one of the migration process with these parameters and users list text files, use the syntax shown in <a href="asoappg.htm# 635660">Example G-6</a>.</p> <a name="635660"></a> <h4 class="ET"><font face="Arial, Helvetica, sans-serif"><em>Example G-6 Mig rating Users Using the PARFILE, USERSFILE, and LOGFILE Parameters</em></font></h4> <pre class="CE"><a name="635662"></a>umu PHASE=ONE <a name="635663"></a>DBADMIN=<em class="Variable">system</em>:<em class="Variable">manager </em><a name="635664"></a>PARFILE=<em cl ass="Variable">par.txt </em><a name="635665"></a>LOGFILE=<em class="Variable">errorfile2 </em><a name="635666"></a> </pre> <a name=" 635681"></a> <div align="center"> <table class="Note" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout table to format a note"> <tr class="Note"> <td class="Note"> <hr> <a name ="635669"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">Note:</strong></font> <a name="635671"></a> <p class="NB" >Although the <code>LOGFILE</code> parameter is specified twice, once in the parameter text file as <code>errorfile1</code> (shown in <a href="asoappg.htm#635632">Example G-4</a>) and once on the command line as <code>errorfile2</code> (show in <a href="asoappg .htm#635660">Example G-6</a>), command-line parameters take precedence over those specified inside the parameter file. Consequen tly, in <a href="asoappg.htm#635660">Example G-6</a> the log file will be written to <code>errorfile2</code> because that value is specified on the command line.</p> <hr></td></tr></table></div> <a name="635686"></a>  <h2 class="H1"><font face="Arial, Helvetica, sans-serif" color="#330099">Troubleshooting Using the User Migration Utility</font></h2>  <a na me="635687"></a> <p class="BP">Migration failures are reported to the enterprise user administrator with error messages and log mess ages. The following sections describe common error and log messages and what administrators can do to resolve them.</p> <a name="6356 98"></a> <div align="center"> <table class="NoteAlso" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout table to format a note"> <tr class="NoteAlso"> <td class="NoteAlso"><a n ame="635690"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">See Also:</strong></font> <a name="635693"></a> <p cla ss="NB"><a href="asoappg.htm#636128">"Summary of User Migration Utility Error and Log Messages"</a><a href="asoappg.htm#636128"></a> for an alphabetical listing of error and log messages and links to where they are described in this section.</p></td></tr></table></d iv> <a name="635702"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Common User Migration Utility Error Messages</font></h3>  <a name="635703"></a> <p class="BP">When the utility encounters any err or while running, it displays an error message and stops running. The following sections describe these messages and explain how to r esolve the errors:</p> <ul class="LB1"> <li class="LB1" type="disc"><a name="635707"></a><a href="asoappg.htm#635713">Resolving Error Messages Displayed for Both Phases</a></li> <li class="LB1" type="disc"><a name="635711"></a><a href="asoappg.htm#635804">Resolving Error Messages Displayed for Phase One</a></li></ul> <a name="635713"></a>  <h4 class="H3"><font face="Arial, H elvetica, sans-serif" color="#330099">Resolving Error Messages Displayed for Both Phases</font></h4>  <a name="635714"> </a> <p class="BP">The following error messages may display while the utility is running either phase one or phase two of the migrat ion:</p> <ul class="LB1"> <li class="LB1" type="disc"><a name="635718"></a><a href="asoappg.htm#635748">Attribute value missing : : o rclCommonNicknameAttribute</a></li> <li class="LB1" type="disc"><a name="635722"></a><a href="asoappg.htm#635752">Database connection failure</a></li> <li class="LB1" type="disc"><a name="635726"></a><a href="asoappg.htm#635758">Database error: < database_error_m essage ></a></li> <li class="LB1" type="disc"><a name="635730"></a><a href="asoappg.htm#635772">Database not in any domain : : DB- NAME = < database_name ></a></li> <li class="LB1" type="disc"><a name="635734"></a><a href="asoappg.htm#635776">Database not re gistered with the directory : : DB-NAME = < dbName ></a></li> <li class="LB1" type="disc"><a name="635738"></a><a href="asoappg .htm#635780">Directory connection failure</a></li> <li class="LB1" type="disc"><a name="635742"></a><a href="asoappg.htm#635786">Dire ctory error : : < directory_error_message ></a></li> <li class="LB1" type="disc"><a name="635746"></a><a href="asoappg.htm#6358 00">Multiple entries found : : uniqueMember = < database_DN ></a></li></ul> <dl class="M"> <dt class="M"><a name="635748"></a>< br> <strong>Attribute value missing : : orclCommonNicknameAttribute</strong><br></dt> <dd class="MH1"><a name="635749"></a> <p><stro ng>Cause:</strong> The nickname attribute is not set in the directory in the root identity management realm.</p></dd> <dd class="MH2" ><a name="635750"></a> <p><strong>Action:</strong> Use Enterprise Security Manager Console to set the nickname attribute for the ide ntity management realm.</p></dd> <dt class="M"><a name="635752"></a><br> <strong>Database connection failure</strong><br></dt> <dd cl ass="MH1"><a name="635753"></a> <p><strong>Cause:</strong> The utility was unable to connect to the database.</p></dd> <dd class="MH 2"><a name="635754"></a> <p><strong>Action:</strong> Perform these steps:</p> <ol class="LN2" type="1"> <li class="LN2" type="1" val ue="1"><a name="635755"></a>Check the database status to determine whether it is configured for encryption and integrity.</li> <li cl ass="LN2" type="1" value="2"><a name="635756"></a>Check the privileges and credentials of the enterprise user administrator who is ru nning the utility.</li></ol></dd> <dt class="M"><a name="635758"></a><br> <strong>Database error: < database_error_message ></s trong><br></dt> <dd class="MH1"><a name="635759"></a> <p><strong>Cause:</strong> The utility encountered a database error.</p></dd> <dd class="MH2"><a name="635760"></a> <p><strong>Action:</strong> Check the database error message details for the database.</p> <a name="635770"></a> <div align="center"> <table class="NoteAlso" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" sum mary="This is a layout table to format a note" title="This is a layout table to format a note"> <tr class="NoteAlso"> <td class="Note Also"><a name="635763"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">See Also:</strong></font> <a name="635769"></ a> <p class="NB"><a class="olinkSRC ERRMG" href="../../server$101/b10744/toc.htm"><em class="Italic">Oracle Database Error Messages< /em></a> for information about resolving database error messages.</p></td></tr></table></div></dd></dl> <dl> <dt class="M"><a name="6 35772"></a><br> <strong>Database not in any domain : : DB-NAME = < database_name ></strong><br></dt> <dd class="MH1"><a name="6 35773"></a> <p><strong>Cause:</strong> The database is not a member of any enterprise domain.</p></dd> <dd class="MH2"><a name="6357 74"></a> <p><strong>Action:</strong> Use Enterprise Security Manager to add the database to an enterprise domain in the directory.</ p></dd> <dt class="M"><a name="635776"></a><br> <strong>Database not registered with the directory : : DB-NAME = < dbName ></st rong><br></dt> <dd class="MH1"><a name="635777"></a> <p><strong>Cause:</strong> There is no entry for the database in the Oracle con text that the ldap.ora file points to.</p></dd> <dd class="MH2"><a name="635778"></a> <p><strong>Action:</strong> Use Database Confi guration Assistant or Enterprise Security Manager to register the database in the directory.</p></dd> <dt class="M"><a name="635780"> </a><br> <strong>Directory connection failure</strong><br></dt> <dd class="MH1"><a name="635781"></a> <p><strong>Cause:</strong> The utility was unable to connect to the directory.</p></dd> <dd class="MH2"><a name="635782"></a> <p><strong>Action:</strong> Perform these steps:</p> <ol class="LN2" type="1"> <li class="LN2" type="1" value="1"><a name="635783"></a>Check the directory server status to determine whether the directory server port is configured for SSL with no authentication.</li> <li class="LN2" type="1" value="2"> <a name="635784"></a>Check the privileges and credentials of the enterprise user administrator who is running the utility.</li></ol>< /dd> <dt class="M"><a name="635786"></a><br> <strong>Directory error : : < directory_error_message ></strong><br></dt> <dd clas s="MH1"><a name="635787"></a> <p><strong>Cause:</strong> The utility encountered a directory error.</p></dd> <dd class="MH2"><a name ="635788"></a> <p><strong>Action:</strong> Check the directory error message details for the directory.</p> <a name="635798"></a> < div align="center"> <table class="NoteAlso" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a layou t table to format a note" title="This is a layout table to format a note"> <tr class="NoteAlso"> <td class="NoteAlso"><a name="635791 "></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">See Also:</strong></font> <a name="635797"></a> <p class="NB"><em class="Italic"><a class="olinkSRC OIDAG" href="../../dcommon/html/noexist.htm">Oracle Internet Directory Administrator's Guide</a> f or information about resolving error messages for Oracle Internet Directory.</em></p></td></tr></table></div></dd> <dt class="M"><a n ame="635800"></a><br> <strong>Multiple entries found : : uniqueMember = < database_DN ></strong><br></dt> <dd class="MH1"><a na me="635801"></a> <p><strong>Cause:</strong> The database belongs to more than one enterprise domain in the directory.</p></dd> <dd c lass="MH2"><a name="635802"></a> <p><strong>Action:</strong> Use Enterprise Security Manager or Oracle Directory Manager to ensure t hat the database belongs to only one enterprise domain.</p></dd></dl> <a name="635804"></a>  <h4 class="H3"><fo nt face="Arial, Helvetica, sans-serif" color="#330099">Resolving Error Messages Displayed for Phase One</font></h4>  <a name="635805"></a> <p class="BP">While the utility is running phase one of the migration, syntax or other types of errors may occur . The following error messages may display while the utility is running phase one of the migration:</p> <ul class="LB1"> <li class="L B1" type="disc"><a name="635809"></a><a href="asoappg.htm#635879">Argument missing or duplicated : : < parameter ></a></li> <li class="LB1" type="disc"><a name="635813"></a><a href="asoappg.htm#635883">Database object missing : : SHARED-SCHEMA = <shared_sch ema_name ></a></li> <li class="LB1" type="disc"><a name="635825"></a><a href="asoappg.htm#635895">Error reading file : : < file _name > : : < io_error_message ></a></li> <li class="LB1" type="disc"><a name="635829"></a><a href="asoappg.htm#635901">Erro r reading file : : PARFILE = < file_name > : : < io_error_message></a></li> <li class="LB1" type="disc"><a name="635833"> </a><a href="asoappg.htm#635907">Getting local host name failed</a></li> <li class="LB1" type="disc"><a name="635837"></a><a href="as oappg.htm#635931">Interface table creation in SYS schema not allowed</a></li> <li class="LB1" type="disc"><a name="635841"></a><a hre f="asoappg.htm#635946">Invalid argument or value : : < argument ></a></li> <li class="LB1" type="disc"><a name="635845"></a><a href="asoappg.htm#635977">Invalid arguments for the phase</a></li> <li class="LB1" type="disc"><a name="635849"></a><a href="asoappg. htm#635981">Invalid value : : < user > [ USERSFILE ]</a></li> <li class="LB1" type="disc"><a name="635853"></a><a href="asoappg .htm#635985">Invalid value : : < user > [ USERSFILE ] { = = DBADMIN }</a></li> <li class="LB1" type="disc"><a name="635857"></a ><a href="asoappg.htm#635989">Invalid value : : < user > [ USERSLIST ]</a></li> <li class="LB1" type="disc"><a name="635861"></ a><a href="asoappg.htm#635993">Invalid value : : < user > [ USERSLIST ] { = = DBADMIN }</a></li> <li class="LB1" type="disc"><a name="635865"></a><a href="asoappg.htm#635997">Logging failure : : < io_error_message ></a></li> <li class="LB1" type="disc">< a name="635873"></a><a href="asoappg.htm#636007">No entry found : : CONTEXT = < context ></a></li></ul> <dl class="M"> <dt clas s="M"><a name="635879"></a><br> <strong>Argument missing or duplicated : : < parameter ></strong><br></dt> <dd class="MH1"><a n ame="635880"></a> <p><strong>Cause:</strong> Syntax error. A parameter is missing or has been entered multiple times.</p></dd> <dd c lass="MH2"><a name="635881"></a> <p><strong>Action:</strong> Check the usage syntax.</p></dd> <dt class="M"><a name="635883"></a><br > <strong>Database object missing : : SHARED-SCHEMA = <shared_schema_name ></strong><br></dt> <dd class="MH1"><a name="635884"> </a> <p><strong>Cause:</strong> The shared schema is not present in the database.</p></dd> <dd class="MH2"><a name="635885"></a> <p ><strong>Action:</strong> Create the shared schema.</p></dd> <dt class="M"><a name="635895"></a><br> <strong>Error reading file : : & lt; file_name > : : < io_error_message ></strong><br></dt> <dd class="MH1"><a name="635896"></a> <p><strong>Cause:</strong> Syntax error. The utility cannot read the file that contains the users list that is specified in the USERSFILE parameter.</p></dd> < dd class="MH2"><a name="635897"></a> <p><strong>Action:</strong> Perform these steps:</p> <ol class="LN2" type="1"> <li class="LN2" type="1" value="1"><a name="635898"></a>Check to ensure that the file exists.</li> <li class="LN2" type="1" value="2"><a name="635899 "></a>Check to ensure that the file has the correct permissions so the utility can read it.</li></ol></dd> <dt class="M"><a name="635 901"></a><br> <strong>Error reading file : : PARFILE = < file_name > : : < io_error_message></strong><br></dt> <dd class= "MH1"><a name="635902"></a> <p><strong>Cause:</strong> Syntax error. The utility cannot read the file that contains the list of para meters that is specified in the PARFILE parameter.</p></dd> <dd class="MH2"><a name="635903"></a> <p><strong>Action:</strong> Perfor m these steps:</p> <ol class="LN2" type="1"> <li class="LN2" type="1" value="1"><a name="635904"></a>Check to ensure that the file ex ists.</li> <li class="LN2" type="1" value="2"><a name="635905"></a>Check to ensure that the file has the correct permissions so the u tility can read it.</li></ol></dd> <dt class="M"><a name="635907"></a><br> <strong>Getting local host name failed</strong><br></dt> < dd class="MH1"><a name="635908"></a> <p><strong>Cause:</strong> Syntax error. The utility is unable to read the local host name for the database location or the directory location.</p></dd> <dd class="MH2"><a name="635909"></a> <p><strong>Action:</strong> Explicit ly enter the hostname information with the <code>DBLOCATION</code> and <code>DIRLOCATION</code> parameters.</p> <a name="635929"></a> <div align="center"> <table class="NoteAlso" border="0" width="80%" cellpadding="0" cellspacing="0" dir="ltr" summary="This is a la yout table to format a note" title="This is a layout table to format a note"> <tr class="NoteAlso"> <td class="NoteAlso"><a name="635 912"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">See Also:</strong></font> <a name="635913"></a> <ul class="NL" > <li class="NL" type="disc"><a name="635920"></a><a href="asoappg.htm#635089">"Keyword: DBLOCATION"</a><a href="asoappg.htm#635089"> </a></li> <li class="NL" type="disc"><a name="635927"></a><a href="asoappg.htm#635115">"Keyword: DIRLOCATION"</a><a href="asoappg.htm #635115"></a></li></ul> <a name="635928"></a> <p class="NB">For information about how to use these parameters.</p></td></tr></table> </div></dd> <dt class="M"><a name="635931"></a><br> <strong>Interface table creation in SYS schema not allowed</strong><br></dt> <dd class="MH1"><a name="635932"></a> <p><strong>Cause:</strong> The interface table cannot be created in the <code>SYS</code> schema.</ p></dd> <dd class="MH2"><a name="635933"></a> <p><strong>Action:</strong> Specify another user in the <code>DBADMIN</code> parameter .</p> <a name="635944"></a> <div align="center"> <table class="NoteAlso" border="0" width="80%" cellpadding="0" cellspacing="0" dir= "ltr" summary="This is a layout table to format a note" title="This is a layout table to format a note"> <tr class="NoteAlso"> <td cl ass="NoteAlso"><a name="635936"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">See Also:</strong></font> <a name="6 35943"></a> <p class="NB"><a href="asoappg.htm#635139">"Keyword: DBADMIN"</a><a href="asoappg.htm#635139"></a> for information about setting the <code>DBADMIN</code> parameter.</p></td></tr></table></div></dd> <dt class="M"><a name="635946"></a><br> <strong>Invalid argument or value : : < argument ></strong><br></dt> <dd class="MH1"><a name="635947"></a> <p><strong>Cause:</strong> Syntax error. The argument name or value has been entered incorrectly.</p></dd> <dd class="MH2"><a name="635948"></a> <p><strong>Action:</s trong> Check the usage syntax.</p> <a name="635975"></a> <div align="center"> <table class="NoteAlso" border="0" width="80%" cellpad ding="0" cellspacing="0" dir="ltr" summary="This is a layout table to format a note" title="This is a layout table to format a note"> <tr class="NoteAlso"> <td class="NoteAlso"><a name="635951"></a><font face="Arial, Helvetica, sans-serif"><strong class="NH">See Als o:</strong></font> <a name="635952"></a> <ul class="NL"> <li class="NL" type="disc"><a name="635959"></a><a href="asoappg.htm#634957 ">"User Migration Utility Command Line Syntax"</a><a href="asoappg.htm#634957"></a></li> <li class="NL" type="disc"><a name="635966"> </a><a href="asoappg.htm#635026">"Accessing Help for the User Migration Utility"</a><a href="asoappg.htm#635026"></a></li> <li class= "NL" type="disc"><a name="635973"></a><a href="asoappg.htm#635038">"User Migration Utility Parameters"</a><a href="asoappg.htm#635038 "></a></li></ul> <a name="635974"></a> <p class="NB">For information about using the command line syntax for this utility.</p></td>< /tr></table></div></dd> <dt class="M"><a name="635977"></a><br> <strong>Invalid arguments for the phase</strong><br></dt> <dd class=" MH1"><a name="635978"></a> <p><strong>Cause:</strong> Syntax error. This occurs when you have used a command line argument that is o nly intended for phase one, but you are running phase two.</p></dd> <dd class="MH2"><a name="635979"></a> <p><strong>Action:</strong > Check the usage syntax.</p></dd> <dt class="M"><a name="635981"></a><br> <strong>Invalid value : : < user > [ USERSFILE ]</st rong><br></dt> <dd class="MH1"><a name="635982"></a> <p><strong>Cause:</strong> Syntax error. The user that is specified in this err or message is invalid because they are not a user in the database that is specified in the <code>DBLOCATION</code> parameter.</p></dd > <dd class="MH2"><a name="635983"></a> <p><strong>Action:</strong> Remove the invalid user from the file that is specified with the <code>USERSFILE</code> parameter.</p></dd> <dt class="M"><a name="635985"></a><br> <strong>Invalid value : : < user > [ USERSF ILE ] { = = DBADMIN }</strong><br></dt> <dd class="MH1"><a name="635986"></a> <p><strong>Cause:</strong> Syntax error. The file that is specified in the <code>USERSFILE</code> parameter contains the user who is running the migration utility.</p></dd> <dd class="MH2 "><a name="635987"></a> <p><strong>Action:</strong> Remove that user from the file.</p></dd> <dt class="M"><a name="635989"></a><br> <strong>Invalid value : : < user > [ USERSLIST ]</strong><br></dt> <dd class="MH1"><a name="635990"></a> <p><strong>Cause:</s trong> Syntax error. The user that is specified in this error message is invalid because they are not a user in the database that is specified in the <code>DBLOCATION</code> parameter.</p></dd> <dd class="MH2"><a name="635991"></a> <p><strong>Action:</strong> Remov e the invalid user from the <code>USERSLIST</code> parameter.</p></dd> <dt class="M"><a name="635993"></a><br> <strong>Invalid value : : < user > [ USERSLIST ] { = = DBADMIN }</strong><br></dt> <dd class="MH1"><a name="635994"></a> <p><strong>Cause:</strong> Syntax error. The <code>USERSLIST</code> parameter contains the user who is running the migration utility.</p></dd> <dd class="MH2">< a name="635995"></a> <p><strong>Action:</strong> Remove that user from the <code>USERSLIST</code>.</p></dd> <dt class="M"><a name="6 35997"></a><br> <strong>Logging failure : : < io_error_message ></strong><br></dt> <dd class="MH1"><a name="635998"></a> <p><s trong>Cause:</strong> Syntax error. The utility cannot find the log file or it cannot open the file to write to it.</p></dd> <dd clas s="MH2"><a name="635999"></a> <p><strong>Action:</strong> Perform these steps:</p> <ol class="LN2" type="1"> <li class="LN2" type="1 " value="1"><a name="636000"></a>Check to ensure that the log file exists.</li> <li class="LN2" type="1" value="2"><a name="636001">< /a>Check to ensure that the log file has the correct permissions so the utility can write information to it.</li></ol></dd> <dt class ="M"><a name="636007"></a><br> <strong>No entry found : : CONTEXT = < context ></strong><br></dt> <dd class="MH1"><a name="6360 08"></a> <p><strong>Cause:</strong> The <code>CONTEXT</code> entry is not present in the directory.</p></dd> <dd class="MH2"><a name ="636009"></a> <p><strong>Action:</strong> Perform one of the following options:</p> <ul class="LB2"> <li class="LB2" type="disc"><a name="636010"></a>Use the directory management tool or the LDAP command line utility to create an entry in the directory for the con text value.</li> <li class="LB2" type="disc"><a name="636011"></a>Specify another valid context value.</li></ul></dd></dl> <a name="6 36016"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Resolving Error Messages Displayed for Phase Two</font></h4>  <a name="636017"></a> <p class="BP">Most of the error messages that you encounter while running this utility occur in phase one. After phase one has completed successfully, and while phase two is running, the follo wing error may occur:</p> <dl class="M"> <dt class="M"><a name="636019"></a><br> <strong>Database object missing : : TABLE = ORCL_GLO BAL_USR_MIGRATION_DATA</strong><br></dt> <dd class="MH1"><a name="636020"></a> <p><strong>Cause:</strong> The utility cannot find th e interface table.</p></dd> <dd class="MH2"><a name="636021"></a> <p><strong>Action:</strong> Perform one of the following options:< /p> <ul class="LB2"> <li class="LB2" type="disc"><a name="636022"></a>Run phase one of the utility to create the interface table.</li > <li class="LB2" type="disc"><a name="636023"></a>Check to ensure that the user who is specified in the <code>DBADMIN</code> paramet er is the same user who was specified for that parameter for phase one.</li></ul></dd></dl> <a name="636027"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Common User Migration Utility Log Messages</font></h3> < !--/TOC=h2--> <a name="636028"></a> <p class="BP">Typically, log messages are written to the log file for each user who is migrated, whether the user was migrated successfully or not. The following sections describe these messages and explain how to resolve the err ors:</p> <a name="636029"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color="#330099">Common Log Messages for Phase One</font></h4>  <a name="636030"></a> <p class="BP">While the utility is running phase one of the migration, messages that indicate a user's information has not been successfully populated in the interface table may be written to the log file. After the utility completes phase one, review the log file to check for the following messages:</p> <ul class="LB1" > <li class="LB1" type="disc"><a name="636034"></a><a href="asoappg.htm#636044">Multiple entries found : : < nickname_attribute &g t; = < username ></a></li> <li class="LB1" type="disc"><a name="636037"></a><a href="asoappg.htm#636048">No entry found : : < ; nickname_attribute > = < username > : : Entry found : DN = < dn ></a></li></ul> <dl class="M"> <dt class="M"><a name ="636044"></a><br> <strong>Multiple entries found : : < nickname_attribute > = < username ></strong><br></dt> <dd class=" MH1"><a name="636045"></a> <p><strong>Cause:</strong> The nickname attribute matches multiple users or the user matches with multipl e nickname attributes.</p></dd> <dd class="MH2"><a name="636046"></a> <p><strong>Action:</strong> Resolve the multiple matches and r un the utility again for the users whose log file entry displayed this message.</p></dd> <dt class="M"><a name="636048"></a><br> <str ong>No entry found : : < nickname_attribute > = < username > : : Entry found : DN = < dn ></strong><br></dt> <dd cl ass="MH1"><a name="636049"></a> <p><strong>Cause:</strong> No entry was found for the nickname matching, but an entry already exists for the DN in the directory.</p></dd> <dd class="MH2"><a name="636050"></a> <p><strong>Action:</strong> Specify a different DN for the user.</p></dd></dl> <a name="636055"></a>  <h4 class="H3"><font face="Arial, Helvetica, sans-serif" color=" #330099">Common Log Messages for Phase Two</font></h4>  <a name="636056"></a> <p class="BP">While the utility is runni ng phase two of the migration, messages that indicate a user has not successfully migrated may be written to the log file. After the utility completes phase two, review the log file to check for the following messages:</p> <ul class="LB1"> <li class="LB1" type="disc "><a name="636060"></a><a href="asoappg.htm#636086">Attribute exists : : orclPassword</a></li> <li class="LB1" type="disc"><a name="6 36064"></a><a href="asoappg.htm#636091">Attribute value missing : : orclPassword</a></li> <li class="LB1" type="disc"><a name="636068 "></a><a href="asoappg.htm#636096">Database object missing : : SHARED-SCHEMA = < shared_schema ></a></li> <li class="LB1" type= "disc"><a name="636072"></a><a href="asoappg.htm#636102">Entry found : : DN = < user_DN ></a></li> <li class="LB1" type="disc"> <a name="636075"></a><a href="asoappg.htm#636107">Invalid value : : <interface_table_column_name> = < interface_table_column _value ></a></li> <li class="LB1" type="disc"><a name="636080"></a><a href="asoappg.htm#636111">No entry found : : DN = < user_ DN ></a></li></ul> <dl class="M"> <dt class="M"><a name="636086"></a><br> <strong>Attribute exists : : orclPassword</strong><br></ dt> <dd class="ML"><a name="636087"></a> <p><em class="ML">This message typically occurs with the message <code>Invalid value::<c olumn_name>=<column_value></code>.</em></p></dd> <dd class="MH1"><a name="636088"></a> <p><strong>Cause:</strong> The entry already contains a value for the <code>orclPassword</code> attribute.</p></dd> <dd class="MH2"><a name="636089"></a> <p><strong>Act ion:</strong> Check the <code>DBPASSWORD_EXIST_FLAG</code> column in the interface table for a <code>T/F</code> value that correctly reflects whether a database password exists for this user.</p></dd> <dt class="M"><a name="636091"></a><br> <strong>Attribute value m issing : : orclPassword</strong><br></dt> <dd class="ML"><a name="636092"></a> <p><em class="ML">This message typically occurs with the message <code>Invalid value::<column_name>=<column_value></code>.</em></p></dd> <dd class="MH1"><a name="636093"></a> <p><strong>Cause:</strong> The <code>orclPassword</code> attribute of this user's entry has a null value.</p></dd> <dd class="MH2"> <a name="636094"></a> <p><strong>Action:</strong> Check the <code>DBPASSWORD_EXIST_FLAG</code> column in the interface table for a < code>T/F</code> value that correctly reflects whether a database password exists for this user.</p></dd> <dt class="M"><a name="63609 6"></a><br> <strong>Database object missing : : SHARED-SCHEMA = < shared_schema ></strong><br></dt> <dd class="MH1"><a name="63 6097"></a> <p><strong>Cause:</strong> The shared schema that was specified for this user does not exist in the database.</p></dd> <d d class="MH2"><a name="636098"></a> <p><strong>Action:</strong> Perform one of the following options:</p> <ul class="LB2"> <li class ="LB2" type="disc"><a name="636099"></a>Check to ensure that the correct shared schema was specified for this user. If the shared sch ema name was incorrectly specified, then edit the <code>SHARED_SCHEMA</code> column of the interface table and run phase two of the u tility for this user again.</li> <li class="LB2" type="disc"><a name="636100"></a>Create the shared schema in the database and run ph ase two of the utility for this user again.</li></ul></dd> <dt class="M"><a name="636102"></a><br> <strong>Entry found : : DN = < user_DN ></strong><br></dt> <dd class="ML"><a name="636103"></a> <p><em class="ML">This message typically occurs with the message <code>Invalid value::<column_name>=<column_value></code>.</em></p></dd> <dd class="MH1"><a name="636104"></a> <p><stron g>Cause:</strong> An entry already exists for the specified user DN.</p></dd> <dd class="MH2"><a name="636105"></a> <p><strong>Actio n:</strong> Check the <code>USERDN_EXIST_FLAG</code> column in the interface table for a <code>T/F</code> value that correctly reflec ts whether a user entry already exists in the directory for this DN.</p></dd> <dt class="M"><a name="636107"></a><br> <strong>Invalid value : : <interface_table_column_name> = < interface_table_column_value ></strong><br></dt> <dd class="MH1"><a name="63 6108"></a> <p><strong>Cause:</strong> The value in the interface table column for this user is invalid. Typically, this message is a ccompanied by additional log messages for this user.</p></dd> <dd class="MH2"><a name="636109"></a> <p><strong>Action:</strong> Chec k to ensure that the correct value has been entered for this user.</p></dd> <dt class="M"><a name="636111"></a><br> <strong>No entry found : : DN = < user_DN ></strong><br></dt> <dd class="ML"><a name="636112"></a> <p><em class="ML">This message typically occ urs with the message <code>Invalid value::<column_name>=<column_value></code>.</em></p></dd> <dd class="MH1"><a name="636 113"></a> <p><strong>Cause:</strong> The entry for the DN is missing in the directory.</p></dd> <dd class="MH2"><a name="636114"></a > <p><strong>Action:</strong> Check the <code>USERDN_EXIST_FLAG</code> column in the interface table for a <code>T/F</code> value th at correctly reflects whether a user entry already exists in the directory for this DN.</p></dd></dl> <a name="636128"></a>  <h3 class="H2"><font face="Arial, Helvetica, sans-serif" color="#330099">Summary of User Migration Utility Error and Lo g Messages</font></h3>  <a name="636135"></a> <p class="BP"><a href="asoappg.htm#636145">Table G-4</a> and <a hre f="asoappg.htm#636432">Table G-5</a> list all of the error and log messages in alphabetical order and provides links to the sect ion in this chapter that describes the message and how to resolve it.</p> <a name="636425"></a> <h5 class="TTW"><a name="636425"></a ><a name="636145"></a> <strong><font face="Arial, Helvetica, sans-serif"><em>Table G-4 Alphabetical Listing of User Migration U tility Error Messages</em></font></strong></h5> <table summary="" class="FormalWide" border="1" frame="HSIDES" rules="GROUPS" width=" 100%" cellpadding="3" cellspacing="0" dir="ltr" title=""> <thead> <tr class="Formal"> <th class="Formal" align="left" valign="bottom" scope="col"><a name="636152"></a> <font face="Arial, Helvetica, sans-serif"><strong>User Migration Utility Error Message</strong></f ont></th> <th class="Formal" align="left" valign="bottom" scope="col"><a name="636154"></a> <font face="Arial, Helvetica, sans-serif" ><strong>Phase</strong></font></th></tr></thead> <tbody> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="63 6162"></a> <p class="TB"><a href="asoappg.htm#635879">Argument missing or duplicated : : < parameter ></a><a href="asoappg.htm #635879"></a></p></td> <td class="Formal"><a name="636164"></a> <p class="TB">1</p></td></tr> <tr class="Formal" align="left" valign ="top"> <td class="Formal"><a name="636172"></a> <p class="TB"><a href="asoappg.htm#635748">Attribute value missing : : orclCommonNi cknameAttribute</a><a href="asoappg.htm#635748"></a></p></td> <td class="Formal"><a name="636174"></a> <p class="TB">Both</p></td></ tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="636182"></a> <p class="TB"><a href="asoappg.htm#635752 ">Database connection failure</a><a href="asoappg.htm#635752"></a></p></td> <td class="Formal"><a name="636184"></a> <p class="TB">B oth</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="636192"></a> <p class="TB"><a href="asoa ppg.htm#635758">Database error: < database_error_message ></a><a href="asoappg.htm#635758"></a></p></td> <td class="Formal"><a name="636194"></a> <p class="TB">Both</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="636202 "></a> <p class="TB"><a href="asoappg.htm#635772">Database not in any domain : : DB-NAME = < database_name ></a><a href="asoap pg.htm#635772"></a></p></td> <td class="Formal"><a name="636204"></a> <p class="TB">Both</p></td></tr> <tr class="Formal" align="lef t" valign="top"> <td class="Formal"><a name="636212"></a> <p class="TB"><a href="asoappg.htm#635776">Database not registered with th e directory : : DB-NAME = < dbName ></a><a href="asoappg.htm#635776"></a></p></td> <td class="Formal"><a name="636214"></a> <p class="TB">Both</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="636222"></a> <p class="TB"> <a href="asoappg.htm#635883">Database object missing : : SHARED-SCHEMA = <shared_schema_name ></a><a href="asoappg.htm#635883"> </a></p></td> <td class="Formal"><a name="636224"></a> <p class="TB">1</p></td></tr> <tr class="Formal" align="left" valign="top"> < td class="Formal"><a name="636232"></a> <p class="TB"><a href="asoappg.htm#636019">Database object missing : : TABLE = ORCL_GLOBAL_U SR_MIGRATION_DATA</a><a href="asoappg.htm#636019"></a></p></td> <td class="Formal"><a name="636234"></a> <p class="TB">2</p></td></t r> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="636242"></a> <p class="TB"><a href="asoappg.htm#635780" >Directory connection failure</a><a href="asoappg.htm#635780"></a></p></td> <td class="Formal"><a name="636244"></a> <p class="TB">B oth</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="636252"></a> <p class="TB"><a href="asoa ppg.htm#635786">Directory error : : < directory_error_message ></a><a href="asoappg.htm#635786"></a></p></td> <td class="Formal "><a name="636254"></a> <p class="TB">Both</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="6 36262"></a> <p class="TB"><a href="asoappg.htm#635895">Error reading file : : < file_name > : : < io_error_message ></a> <a href="asoappg.htm#635895"></a></p></td> <td class="Formal"><a name="636264"></a> <p class="TB">1</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="636292"></a> <p class="TB"><a href="asoappg.htm#635901">Error reading file : : PARFILE = < file_name > : : < io_error_message></a><a href="asoappg.htm#635901"></a></p></td> <td class="Formal"><a na me="636294"></a> <p class="TB">1</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="636302"></a > <p class="TB"><a href="asoappg.htm#635907">Getting local host name failed</a><a href="asoappg.htm#635907"></a></p></td> <td class= "Formal"><a name="636304"></a> <p class="TB">1</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a nam e="636312"></a> <p class="TB"><a href="asoappg.htm#635931">Interface table creation in SYS schema not allowed</a><a href="asoappg.ht m#635931"></a></p></td> <td class="Formal"><a name="636314"></a> <p class="TB">1</p></td></tr> <tr class="Formal" align="left" valig n="top"> <td class="Formal"><a name="636322"></a> <p class="TB"><a href="asoappg.htm#635946">Invalid argument or value : : < argu ment ></a><a href="asoappg.htm#635946"></a></p></td> <td class="Formal"><a name="636324"></a> <p class="TB">1</p></td></tr> <tr c lass="Formal" align="left" valign="top"> <td class="Formal"><a name="636332"></a> <p class="TB"><a href="asoappg.htm#635977">Invalid arguments for the phase</a><a href="asoappg.htm#635977"></a></p></td> <td class="Formal"><a name="636334"></a> <p class="TB">1</p>< /td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="636342"></a> <p class="TB"><a href="asoappg.htm# 635981">Invalid value : : < user > [ USERSFILE ]</a><a href="asoappg.htm#635981"></a></p></td> <td class="Formal"><a name="6363 44"></a> <p class="TB">1</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="636352"></a> <p cl ass="TB"><a href="asoappg.htm#635985">Invalid value : : < user > [ USERSFILE ] { = = DBADMIN }</a><a href="asoappg.htm#635985"> </a></p></td> <td class="Formal"><a name="636354"></a> <p class="TB">1</p></td></tr> <tr class="Formal" align="left" valign="top"> < td class="Formal"><a name="636362"></a> <p class="TB"><a href="asoappg.htm#635989">Invalid value : : < user > [ USERSLIST ]</a ><a href="asoappg.htm#635989"></a></p></td> <td class="Formal"><a name="636364"></a> <p class="TB">1</p></td></tr> <tr class="Formal " align="left" valign="top"> <td class="Formal"><a name="636372"></a> <p class="TB"><a href="asoappg.htm#635993">Invalid value : : & lt; user > [ USERSLIST ] { = = DBADMIN }</a><a href="asoappg.htm#635993"></a></p></td> <td class="Formal"><a name="636374"></a> < p class="TB">1</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="636382"></a> <p class="TB"><a href="asoappg.htm#635997">Logging failure : : < io_error_message ></a><a href="asoappg.htm#635997"></a></p></td> <td class="Fo rmal"><a name="636384"></a> <p class="TB">1</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name=" 636392"></a> <p class="TB"><a href="asoappg.htm#635800">Multiple entries found : : uniqueMember = < database_DN ></a><a href=" asoappg.htm#635800"></a></p></td> <td class="Formal"><a name="636394"></a> <p class="TB">Both</p></td></tr> <tr class="Formal" align ="left" valign="top"> <td class="Formal"><a name="636412"></a> <p class="TB"><a href="asoappg.htm#636007">No entry found : : CONTEXT = < context ></a><a href="asoappg.htm#636007"></a></p></td> <td class="Formal"><a name="636414"></a> <p class="TB">1</p></td> </tr></tbody></table> <a name="636542"></a> <h5 class="TTW"><a name="636542"></a><a name="636432"></a> <strong><font face="Arial, He lvetica, sans-serif"><em>Table G-5 Alphabetical Listing of User Migration Utility Log Messages</em></font></strong></h5> <table summa ry="" class="FormalWide" border="1" frame="HSIDES" rules="GROUPS" width="100%" cellpadding="3" cellspacing="0" dir="ltr" title=""> <t head> <tr class="Formal"> <th class="Formal" align="left" valign="bottom" scope="col"><a name="636439"></a> <font face="Arial, Helvet ica, sans-serif"><strong>User Migration Utility Log Message</strong></font></th> <th class="Formal" align="left" valign="bottom" scop e="col"><a name="636441"></a> <font face="Arial, Helvetica, sans-serif"><strong>Phase</strong></font></th></tr></thead> <tbody> <tr c lass="Formal" align="left" valign="top"> <td class="Formal"><a name="636449"></a> <p class="TB"><a href="asoappg.htm#636086">Attribu te exists : : orclPassword</a><a href="asoappg.htm#636086"></a></p></td> <td class="Formal"><a name="636451"></a> <p class="TB">2</p ></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="636459"></a> <p class="TB"><a href="asoappg.ht m#636091">Attribute value missing : : orclPassword</a><a href="asoappg.htm#636091"></a></p></td> <td class="Formal"><a name="636461"> </a> <p class="TB">2</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="636469"></a> <p class= "TB"><a href="asoappg.htm#636096">Database object missing : : SHARED-SCHEMA = < shared_schema ></a><a href="asoappg.htm#636096" ></a></p></td> <td class="Formal"><a name="636471"></a> <p class="TB">2</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="636479"></a> <p class="TB"><a href="asoappg.htm#636102">Entry found : : DN = < user_DN ></a><a hre f="asoappg.htm#636102"></a></p></td> <td class="Formal"><a name="636481"></a> <p class="TB">2</p></td></tr> <tr class="Formal" align ="left" valign="top"> <td class="Formal"><a name="636489"></a> <p class="TB"><a href="asoappg.htm#636107">Invalid value : : <inte rface_table_column_name> = < interface_table_column_value ></a><a href="asoappg.htm#636107"></a></p></td> <td class="Formal" ><a name="636491"></a> <p class="TB">2</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="63649 9"></a> <p class="TB"><a href="asoappg.htm#636044">Multiple entries found : : < nickname_attribute > = < username ></a>< a href="asoappg.htm#636044"></a></p></td> <td class="Formal"><a name="636501"></a> <p class="TB">1</p></td></tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="636509"></a> <p class="TB"><a href="asoappg.htm#636111">No entry found : : DN = < user_DN ></a><a href="asoappg.htm#636111"></a></p></td> <td class="Formal"><a name="636511"></a> <p class="TB">2</p></td> </tr> <tr class="Formal" align="left" valign="top"> <td class="Formal"><a name="636519"></a> <p class="TB"><a href="asoappg.htm#6360 48">No entry found : : < nickname_attribute > = < username > : : Entry found : DN = < dn ></a><a href="asoappg.htm# 636048"></a></p></td> <td class="Formal"><a name="636521"></a> <p class="TB">1</p></td></tr></tbody></table> <a name="634387"></a></ div> <div class="footer"> <hr> <table summary="" cellspacing="0" cellpadding="0" width="100%"> <tr> <td style="width: 33%;" align="le ft"> <table summary="layout table" cellspacing="0" cellpadding="0" align="left" width="90"> <tr> <td align="center" valign="top"><a h ref="asoappf.htm"><img src="../../dcommon/gifs/larrow.gif" alt="Go to previous page" border="0"><br> <font size="-2">Previous</font>< /a></td> <td align="center" valign="top"><a href="asogls.htm"><img src="../../dcommon/gifs/rarrow.gif" alt="Go to next page" border=" 0"><br> <font size="-2">Next</font></a></td></tr></table></td> <td style="width: 34%;" align="center"><img src="../../dcommon/gifs/or acle.gif" alt="Oracle"><br> <a href="../../dcommon/html/cpyr.htm"><font size="-2">Copyright © 1996, 2003 Oracle Corporation</fon t></a><br> <font size="-2">All Rights Reserved.</font></td> <td style="width: 33%;" align="right"> <table summary="" cellspacing="0" cellpadding="0" width="270"> <tr> <td align="center" valign="top"><a href="../../index.htm"><img src="../../dcommon/gifs/prodicon.gif " alt="Go to Documentation Home" border="0"><br> <font size="-2">Home</font></a></td> <td align="center" valign="top"><a href="../../ nav/portal_3.htm"><img src="../../dcommon/gifs/bookicon.gif" alt="Go to Book List" border="0"><br> <font size="-2">Book List</font></ a></td> <td align="center" valign="top"><a href="toc.htm"><img src="../../dcommon/gifs/conticon.gif" alt="Go to Table of Contents" bo rder="0"><br> <font size="-2">Contents</font></a></td> <td align="center" valign="top"><a href="index.htm"><img src="../../dcommon/gi fs/indxicon.gif" alt="Go to Index" border="0"><br> <font size="-2">Index</font></a></td> <td align="center" valign="top"><a href="../ ../mix$101/b12039/toc.htm"><img src="../../dcommon/gifs/mix.gif" alt="Go to Master Index" border="0"><br> <font size="-2">Master ;Index</font></a></td> <td align="center" valign="top"><a href="../../dcommon/html/feedback.htm"><img src="../../dcommon/gifs/feedbac k.gif" alt="Go to Feedback page" border="0"><br> <font size="-2">Feedback</font></a></td></tr></table></td></tr></table></div> </body