/l /< .=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijkcontents[[Ljava/lang/Object;()VCodeLineNumberTable getContents()[[Ljava/lang/Object; SourceFileVdktRewMsg.java 34 12[Ljava/lang/Object;java/lang/Object1000The Reorg Wizard cannot be launched because there was no target database selected. Select a target database in the navigator tree before attempting to launch the Reorg Wizard.1001UThe Reorg Wizard cannot be launched because the target database was manually configured. Discover the target database using the Discovery Wizard which can be launched from the Navigator menu of the Oracle Enterprise Manager console. Note that an active Intelligent Agent must be running on the same node where the target database is located.1007The Reorg Wizard does not currently support the reorganization of an entire schema. Select the individual schema objects to reorganize.1008xThe Reorg Wizard does not support the reorganization of containers. Select the individual schema objects to reorganize.1009The Reorg Wizard could not be launched because there was a problem with validating the preferred credentials for the target.Verify credentials for the database and node in the 'Preferred Credentials' settings have been set appropriately.1010The Reorg Wizard could not be launched because there was no target segment selected. Before launching the Reorg Wizard select one or more segments from the segment list by clicking in the Reorg? column.3001 Reorg Wizard30023006Welcome3007Display this page next time3008 Reorganization is necessary for:3009 - Relocating objects to another tablespace - Recreating objects with optimal storage attributes - Rebuilding tables that are fragmented - Rebuilding indexes that are fragmented - Repairing migrated rows3010Reorganizations are time consuming and impact object availability. As a result, reorganizations should be targeted to maximize application performance with minimal availability impact. For example, instead of rebuilding an entire tablespace, you may be able to achieve the same benefits by focusing on selected objects within the tablespace. Reorganizations can be run immediately or may be scheduled for execution during off-peak hours to maximize object availability. 3011+Tablespace reorganization is necessary for:30124 - Repairing tablespace free space fragmentation3013;Reorganizations are time consuming and impact object availability. As a result, reorganizations should be targeted to maximize application performance with minimal availability impact. Reorganizations can be run immediately or may be scheduled for execution during off-peak hours to maximize object availability. 3014301530163020Reorganization Option30214Which type of reorganization do you want to perform?3022Reorganize schema objects3023`Use this option to change an object's storage attributes or to eliminate space related problems.3024Reorganize an entire tablespace3025TUse this option to perform a complete tablespace reorganization and defragmentation.3026Repair migrated rows3027NUse this option to repair migrated rows without reorganizing the entire table.3030Object Selection3031)Select one or more objects to reorganize.30323Select one or more objects to repair migrated rows.3033 Available3034Selected3035Add3036Remove3037 Interrupt3038(The following object(s) cannot be added.3040 Tablespace Reorganization Method3041=Which method should be used when reorganizing the tablespace?3042:Recreate objects using the tablespace's storage attributes3043Use this option to ensure all objects in the tablespace have exactly the same extent size. This is the recommended option as it eliminates tablespace freespace fragmentation problems.30448Recreate objects using their existing storage attributes3045hUse this option to ensure all objects in the tablespace are recreated using their existing extent sizes.3050Object Attributes3051Attributes of selected schema objects can be changed during the reorganization. Select an object to change its attributes. When finished making all necessary changes, click Next.3055Scratch Tablespace3056Reorganizations are performed inside the database and require sufficient free space. When a schema object is not being relocated to a different tablespace, temporary space is required during the reorganization.3057Reorganizations are performed inside the database and require sufficient free space. In order to optimize tablespace layout, all of the objects in the tablespace will be moved to a scratch tablespace during the reorganization.3058Migrated row repair is performed inside the database and requires sufficient free space. Problematic rows will be moved to temporary space during the repair.3059+Which tablespace has sufficient free space?3060Current Tablespace3061Use this option if you have enough space in the object's current tablespace to maintain two copies of the object. This is the fastest option as data is moved only once.3062~Use this option if you have enough space in the object's current tablespace to maintain two copies of the rows being repaired.3063|Use this option if you do not have sufficient space in the object's current tablespace to maintain two copies of the object.3065Use this option if you do not have sufficient space in the object's current tablespace to maintain two copies of the rows being repaired.3066Reorganization Method3067Some object types, depending on the Oracle server version, can be reorganized online. With an online reorganization, the objects have higher availability but the reorganization is slower.3068>Do you want the reorganization to favor speed or availability?3069Speed (Offline Reorganization)3070Use this option when either availability is not a concern or a maintenance window exists in which the reorganization can be scheduled. This option results in the fastest reorganization.3071$Availability (Online Reorganization)3072uUse this option when high availability of the objects is important. This option results in the highest availability.3073 Note: Upon completion of an online table reorganization all constraints associated with that table are renamed using the existing name plus an $$OCMinterim suffix.3075Impact Report and Job Summary30764Generate and view the Impact Report and Job Summary.3077 Impact Report3078 Job Summary3079 Generate...3080ReorgImpactRpt.html3081ReorgScript.html3085Reorg Wizard: Work In Progress3086(Generating Impact Summary and Job Script3087 Canceling...3088Processing done.3089Processing failed.3090Processing cancelled by user.3091#Processing was forcibly terminated.3092Cancel3093Close3094 Show Details3095 Hide Details3100Schedule3101eEnter the scheduling information for the job to be submitted, then press Finish to see a job summary.3113=Enter the scheduling information for the job to be submitted.3102-Specify the name and description for the job.3103Name: 3104Description: 3105(When would you like to schedule the job?3106 Immediately3107Submit for a later time3108Date: 3109M/d/yyyy3110Time: 3111h:mm a3112"You must specify a valid job name.3120Cluster3121Table3122Table Partition3123Index3124Index Partition3125 Dependents3140Reorg Wizard Summary3141General3142 Reorg Option:3143Reorganize Entire Tablespace3144Reorganize Schema Objects3145Repair Migrated Rows3146 Reorg Method:3147 Favor speed3148Favor availability3149 Destination:3150Scratch Tablespace:31513152Job Information3153Name:3154 Description:3155 Scheduling:3156Submit the job now3157Submit the job later3158Date:3159Time:3160Selected Objects3180 ReorgPlan3181#Plan generated by the Reorg Wizard.5000`No objects have been selected for reorganization. Select at least one object before continuing.5001pOne or more attributes have been modified. Do you wish to apply these modifications to the reorganization plan?5002GAn error occurred while generating the Impact Summary and Job Script. 5003MAn warning was detected while generating the Impact Summary and Job Script. 5004KAn error was detected while generating the Impact Summary and Job Script. 5005Do you want to continue?5006zThe Impact Summary and Job Script have not been generated. Press the Generate button to generate these before continuing.5007Generating a new Impact Summary and Job Script purges existing data. Are you sure you want to generate a new Impact Summary and Job Script?5008sNo tablespaces are available for use as a scratch tablespace. Deselect at least one tablespace for reorganization.5009ZTip: Increase the size of the wizard to better view all attributes of the selected object.5010You have insufficient privileges to select schema objects. You must have the role SELECT_CATALOG_ROLE and SELECT privilege on the tables SYS.OBJ$, SYS.USER$.6000Oracle Reorg Wizard Help6002vdktrew3190 Note: Upon completion of an online table reorganization all constraints associated with that table are renamed using the existing name plus an $OEM suffix.3191Generate and view the Impact Report and Job Summary. Note: The Job Summary is a summary of the script. The actual script includes both database and OraTcl statements required for job execution.3192(Generating Impact Report and Job Summary3193GAn error occurred while generating the Impact Report and Job Summary. 3194MAn warning was detected while generating the Impact Report and Job Summary. 3195KAn error was detected while generating the Impact Report and Job Summary. 3196zThe Impact Report and Job Summary have not been generated. Press the Generate button to generate these before continuing.3197Generating a new Impact Report and Job Summary purges existing data. Are you sure you want to generate a new Impact Report and Job Summary?3200Online Reorganization Method3201,Starting with Oracle Server 9.2 it is possible to perform online reorganizations on tables that do not have a primary key constraint. These reorganizations are performed using ROWIDs. In this method of reorganization, a hidden column (M_ROW$$) is added to the post-reorganized version of the table.3202ADo you want the reorganization to use the ROWID method if needed?3203No3204Use this option when you only want tables with primary keys to be reorganized online. This option results in the primary key being used to perform the reorganization. Tables without a primary key will be reorganized offline.3205Yes3206Use this option when high availability of the objects is important. This option results in ROWIDs being used when the table does not contain a primary key. If the table contains a primary key then the primary key is used to perform the reorganization."oracle/sysman/resources/VdktRewMsgjava/util/ListResourceBundle$oracle/sysman/resources/VdktRewMsgID!./012345*67856(945  YYSYSSYYSYSSYY SY SSYY SY SSYY SYSSYYSYSSYYSYSSYYSYSSYYSYSSY YSYSSY YSYSSY YSYSSY YSYSSY YSYSSYY SY!SSYY"SY#SSYY$SYSSYY%SYSSYY&SY#SSYY'SY(SSYY)SY*SSYY+SY,SSYY-SY.SSYY/SY0SSYY1SY2SSYY3SY4SSYY5SY6SSYY7SY8SSYY9SY:SSYY;SYSSYY?SY@SSY YASYBSSY!YCSYDSSY"YESYFSSY#YGSYHSSY$YISYJSSY%YKSYLSSY&YMSYNSSY'YOSYPSSY(YQSYRSSY)YSSYTSSY*YUSYVSSY+YWSYXSSY,YYSYZSSY-Y[SY\SSY.Y]SY^SSY/Y_SY`SSY0YaSYbSSY1YcSYdSSY2YeSYfSSY3YgSYhSSY4YiSYjSSY5YkSYlSSY6YmSYnSSY7YoSYpSSY8YqSYrSSY9YsSYtSSY:YuSYvSSY;YwSYxSSY<YySYzSSY=Y{SY|SSY>Y}SY~SSY?YSYSSY@YSYSSYAYSYSSYBYSYSSYCYSYSSYDYSYSSYEYSYSSYFYSYSSYGYSYSSYHYSYSSYIYSYSSYJYSYSSYKYSYSSYLYSYSSYMYSYSSYNYSYSSYOYSYSSYPYSYSSYQYSYSSYRYSYSSYSYSYSSYTYSYSSYUYSYSSYVYSYSSYWYSYSSYXYSYSSYYYSYSSYZYSYSSY[YSYSSY\YSYSSY]YSYSSY^YSYSSY_YSYSSY`YSYSSYaYSYSSYbYSYSSYcYSYSSYdYSYSSYeYSYSSYfYSYSSYgYSYSSYhYSYSSYiYSYSSYjYSYSSYkYSYSSYlYSYSSYmYSYSSYnYSYSSYoYSYdSSYpYSYSSYqYSYSSYrYSYSSYsYSYSSYtYSYSSYuYSYSSYvYSYSSYwYSYSSYxYSYSSYyYSYSSYzYSYSSY{YSYSSY|YSYSSY}YSYSSY~YSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSY SSYY SY SSYY SY SSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYY SY!SSYY"SY#SSYY$SY%SSYY&SY'SSYY(SY)SSYY*SY+SSYY,SY-SS6+:;