Edit D:\app\Administrator\product\11.2.0\dbhome_1\jlib\oracle\sysman\resources\VtoiMsg.class
?? / T #0 "123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? ! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l m n o p q r s t u v w x y z { | } ~ ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L M N O P Q R S contents [[Ljava/lang/Object; <init> ()V Code LineNumberTable getContents ()[[Ljava/lang/Object; <clinit> SourceFile VtoiMsg.java'(%& [Ljava/lang/Object; java/lang/Object 3001 Session 3002 Transaction 3003 Init Parameters 3004 Database 3005 &General 3006 Session ID: 3007 Serial #: 3008 Status: 3009 User Name: 3010 Schema Name: 3011 Program: 3012 OS Information: 3013 OS User Name: 3014 Terminal: 3015 Machine: 3016 Local ID: 3017 Global ID: 3018 State: 3019 Advice: 3020 Date/Time Information 3021 Failure Time: 3022 Last Automatic Retry: 3023 Last Manual Force: 3024 Commit Comment 3025 Parameter Name 3026 Value 3027 Basic Tuning 3028 Instance Specific 3029 Advanced Tuning 3030 Derived 3031 Stored Configuration 3032 Instance State 3033 Shutdown 3034 Started (NOMOUNT) 3035 Mounted 3036 Open 3038 Information 3039 Archive Information 3040 Log Mode 3041 Last SCN Archived 3042 Archive Log Destination(s) 3043 Archive Format 3044 Automatic Archival 3045 SGA Information 3046 Save Configuration 3047 &Name: 3048 &Description: 3049 Shutdown Options 3050 H- wait for all currently connected users to disconnect from the database 3051 A- rollback active transactions and disconnect all connected users 3052 :- instantaneous shutdown by aborting the database instance 3053 B- disconnect all connected users after transactions have completed 3056 Startup Options 3057 Initialization parameters from 3058 Stored configuration 3060 Startup Mode 3061 No Mount 3062 Mount 3064 Restrict access to database 3066 Resource Name 3067 Current 3068 Max 3069 Initial 3070 Limit 2000 ?racle will wait for all the currently connected users to disconnect from the database before shutting down the database. Do you want to continue? 3072 No mount to open 3073 No mount 3074 2001 ,Are you sure you want to mount the database? 3076 oThe database must be mounted to change the database log state. Do you want the database to be mounted for you? 3077 0The state of the database will be changed from 3078 . Are you sure? 3079 ORACLE instance mounted 2002 +Are you sure you want to open the database? 3081 ORACLE instance opened 20046A stored configuration does not exist for this database. Once shut down, you will need to have stored configuration or a copy of the initialization parameter file accessible from the Oracle Management Server machine in order to be able to startup the database. Do you want to create a stored configuration now? 3086 NOARCHIVELOG to ARCHIVELOG? 3087 ARCHIVELOG to NOARCHIVELOG? 2006 ?utomatic archiving of online redo logs will be enabled. This change will only apply to the current instance. To make this change permanent, make the following change to the database initialization parameter file: 2007 ?utomatic archiving of online redo logs wll be disabled. This change will only apply to the current instance. To make this change permanent, make the following change to the database initialization parameter file: 2008 %Applying dynamic parameter(s) failed. 2009 (Applying configured parameter(s) failed. 3093 Archive Logfiles 3094 Destination directory 3095 OK 3096 Cancel 3098 Save As... 3099 Reset 3100 3121 Don't Open 3101 &Browse... 3102 View... 3103 Resource Limit 3104 EDo you want to save the current set of parameters as a configuration? 3105 Current Utilization: 3106 Max Utilization: 3107 Initial Allocation: 3108 Limit: 3109 Resource Limit... 3110 Open Database 3111 ?he Database can be opened with RESETLOGS or NORESETLOGS option. Choose the option you want to use for opening the database. Please note that the database will be opened in read-write mode. 3112 Noresetlogs 3113 Resetlogs 3114 ?he database needs to be opened with RESETLOGS! If you click on Open, then the database will be opened with RESETLOGS and in read-write mode. 3115 - Already exists. Do you want to overwrite it? 3116 cThis operation requires shutting down and restarting the database. Please select the shutdown mode. 3117 ~The database must be mounted but not open to change the log state to archivelog mode. Please select the desired shutdown mode. 3118 ?he database must be mounted but not open to change the log state to no archivelog mode. Please select the desired shutdown mode. 3119 3The database will be shut down and brought up in a 3120 ( state. Please select the shutdown mode. 3125 Resource Utilization for 3126 Long Operations 3127 Active Operations: 3128 Past Operations: 3129 Details for 3131 processed 3132 100% 3133 0 3134 Started: 3135 Elapsed: 3138 Active 3139 Completed 3140 3141 Estimated time remaining: 3142 Completion time: 3143 secs 3144 mins 3145 hours 3146 <local init.ora> 3148 <init.ora> 3149 Save Initialization Parameter 3150 File &Name: 3151 (Please enter a valid configuration name. 3152 Please enter a valid filename. 3153 File saved successfully. 3156 Database not mounted. 3157 1 Does not exist. Please specify a valid filename. 3158 >Database connection is lost. Please reconnect to the database. 3159 Export Stored Configuration 3164 iParameters have been changed. Changes to dynamic deferred parameters will only apply for future sessions. 3166 Parameters have been changed. 3165 Show All States 3168 Logged on since: 3169 Last Activity on: 3170 Background Process 3171 Host Name: 3172 DB Name: 3173 DB Version: 3174 Instance Name: 3175 Instance Start Time: 3176 Restricted Mode: 3177 Archive Log Mode: 3178 Waiting for Log Switch: 3179 !Database and Instance Information 3180 All Initialization Parameters... 3181 _You are not logged on with SYSDBA privilege. Only controls for dynamic parameters are editable. 3182 Re&covery 3183 sIn Archive Log mode, hot backups and recovery to the latest time is possible, but you must provide space for logs. 3184 RIf you change the mode to Archive Log mode, you should take a backup immediately. 3185 mIn No Archive Log mode, only cold backups can be taken, and data can be lost in cases of database corruption. 3186 Archive Log Mode 3187 Log Archive Filename Format: 3188 Automatic archival 3189 hIt is recommended that archive log files be written to multiple locations spread across different disks. 3190 .The database is currently in Archive Log mode. 3191 1The database is currently in No Archive Log mode. 3192 &Memory 3193 Shared Pool : 3194 Buffer Cache : 3196 Java Pool : 3197 User Session Parameters 3198 ?he maximum number of users who can be concurrently connected to the database at any given time. The PROCESSES initialization parameter is based on the value of the maximum number of users and the number of background processes 3199 Max. Concurrent Users: 3200 sThe maximum amount of memory to use for a sort. Larger values of SORT_AREA_SIZE improves efficiency of large sorts. 3201 Sort Area Size: 3202 Normal 3203 Immediate 3204 Abort 3205 Transactional 3206 All Parameters 3207 Description 3208 Yes 3209 No 3210 Database is in an unknown state 3211 Read Only Mode: 3212 {Most probably the session has been closed. Pl. click on the refresh button to update the list of sessions for this database 3213 Kill Session 3214 Kill Post-tx 3215 S&QL 3216 Latest SQL Statement: 3217 Total SGA: 3218 RYou are not logged on with SYSDBA privilege. Only dynamic parameters are editable. 3220 SPFile 3221 Running 3222 ^SPFile parameters are parameters which are stored in the server-side persistent file (spfile). 3223 URunning parameters are the parameters currently in effect for this database instance. 3224 gStatic spfile parameter has been changed. Would you like to restart the database to apply this change? 3225 hDynamic spfile parameter has been changed. Would you like to apply this change to the current database? 3226 ?nder peak load when all concurrent users are using their max sort size allocation, the overall pga memory consumption will be at least 3227 Status 3228 ?atabase state cannot be determined since you are logged in as SYSOPER. The only database operations allowed are Startup and Shutdown of the database 3229 ?lease note that only the current cluster database instance will be stopped and restarted. Do not proceed if all other instances are not stopped. Would you like to proceed with restart of this instance? 4000 Pools 4001 Cursors and Library Cache 4002 Processes and Sessions 4003 Parallel Executions 4004 "Transactions and Rollback Segments 4006 Cache and I/O 4007 #Redo log, Recovery and Control File 4005 Locks 4008 Archive 4009 Backup and Restore 4010 Standby Database 4011 Optimizer 4012 Sort and Hash Joins 4013 Sequences 4014 Objects and LOBs 4015 Shared Server 4016 PL/SQL 4017 License Limits 4018 Security and Auditing 4019 NLS 4020 Cluster Database 4021 %Distributed, Replication and Snapshot 4022 Job Queues 4023 ANSI Compliance 4024 Migration and Compatibility 4025 Diagnostics and Statistics 4026 Network Registration 4027 Memory 4042 Miscellaneous 5506 )System Managed Undo and Rollback Segments 4180 Category 5500 File Configuration 5501 SGA Memory 5502 Resource Manager 5503 Redo Log and Recovery 5504 Sort, Hash Joins, Bitmap Indexes 5505 Transactions 5507 Database Identification 5508 Instance Identification 5509 Automatic Storage Management 4041 Resource Consumer Group 4028 Resource Plan 4029 Name: 4030 Description: 4031 SGA 4032 Large Pool: 4033 B 4034 KB 4035 MB 6399 GB 4036 ORACLE not available 4037 Kill Session Options 4038 7Please specify how you would like to kill this session: 4039 4040 Post Transactional 4043 )No SQL is executed in the current session 4044 Available Groups/Subplans: 4045 Allocation 4046 Activate this plan 4047 AActivate this plan and deactivate the current active plan ''{0}'' 4048 &Parallelism 4049 *Degree of parallelism for consumer groups: 4050 Group/Subplan 4051 Level 4052 Group 4053 Maximum Degree of Parallelism 4054 &Users 4124 Available Roles: 4055 Available Users: 4057 User 4058 Initial Group 4059 Current Initial Consumer Group 4060 Ro&les 4061 Role 4062 -Roles that have the switch privilege for {0}: 4063 -Users that have the switch privilege for {0}: 4064 All users in the database: 4065 All roles in the database: 4066 Admin Option 4067 Re&source Monitors 4077 Active Resource Plan: 4068 Consumer Group Statistics 4069 Consumer Group 4070 Active Sessions 4071 Sessions Waiting 4072 Requests 4073 CPU Wait Time 4074 CPU Waits 4075 Consumed CPU Time 4076 Yields 4084 Edit... 4085 Relative CPU Time Consumed 4086 Total CPU Wait Time 4078 Resource Consumer Group: 4079 Group: 4080 Switch Consumer Group 4081 )Switch all sessions belonging to the user 4087 Active plan: 4082 4083 No active plan 4088 Items in this plan: 4089 Refresh 4090 4091 Last reset: 4092 Last reset: (not reset) 4093 1To change schedule you must login as the user SYS 4094 Current active Resource Plan: 4095 9Daily schedule for automatic activation of Resource Plans 4096 Add 4097 Remove 4098 Schedule: 4099 Enabled 4100 Disabled 4101 (No Resource Plan) 4102 Hour 4103 4104 4105 4106 Session Pool 4107 GMaximum number of concurrently active sessions within a consumer group: 4108 Maximum number of sessions 4109 Timeout (Seconds) 4110 Undo Pool 4111 9Maximum amount of undo space allowed to a consumer group: 4112 Maximum Undo Space (KB) 4113 Execution Time 4114 :Maximum estimated execution time allowed for an operation: 4115 "Estimated Execution Time (Seconds) 4120 Execution Time (Seconds) 4116 Group Switching 4117 USpecify group to switch to when session has been active for specified amount of time: 4118 Switch to group 4119 Use estimate? 4121The active session pool consists of a specified maximum number of user sessions allowed to be concurrently active within a consumer group. Additional sessions beyond the maximum are queued for execution. You can specify a timeout period, after which queued jobs will abort. 4122 pOperations that are estimated to run for a longer time than the specified limit will be prevented from starting. 4123 ?ou can control resources by automatically switching sessions that execute for more than a specified length of time to another consumer group. You can also specify whether Oracle is to use its own estimate of how long an operation will execute. 4160 vSave current database's initialization parameters into a file which can later be used as an init.ora file for startup. 4161 ?Please specify the location to export the stored configuration. 4162 1Explain plan not available for this SQL statement 4174 : 4173 +The exception ({0}) occurred. Message: {1} 4163 Choose the 4164 6stored configuration or initialization parameter file 4165 initialization parameter file 4166 (you will like to start the database with 4167 Starting up database 4168 Shutting down database 4169 Bouncing database 4170 Altering archive state for 4171 $Cancelling shutdown - please wait... 4172 The operation is not cancellable 4175 File Name 4176 on local machine 4177 on OMS machine 4178 Default 4179 Dynamic 4181 Shutting down the database 4182 Starting up the database 4183 Mounting the database 4184 Opening the database 4185 Switching on Archive Log 4186 Switching off Archive Log 4187 rSave current database's initialization parameters into a stored configuration which can later be used for startup. 4188 Use spfile for startup 5000 Introduction 5001Resource Manager allows you to control the processing (CPU) resources made available to specific groups of users by defining a resource plan. A resource plan consists of resource consumer groups and specifies how resources are allocated among them. This wizard takes you through the process of creating and activating a resource plan. You will: - Specify the name for a resource plan - Create resource consumer groups and assign database users to them - Allocate resources to each resource consumer group - Activate the resource plan 5002 Display this page next time 5003 %Specify a name for the resource plan. 5004 4Provide a brief description for the plan (optional). 5005 5006 $Specify a name for the Resource Plan 5007 5008 5009 Selected Users: 5010 Optionally, define new resource consumer groups to be added to this resource plan. Later you will have the opportunity to add existing resource consumer groups. A resource consumer group is an assemblage of users grouped according to their processing resource needs. 5011 /Specify a name for the resource consumer group. 5012 Assign users to this group. 5013 5Provide a brief description of this group (optional). 5014 New Groups: 5015 <Untitled> 5016 5017 Delete 5018 Resource Allocation Mode 5019 =What mode would you like to use for allocating CPU resources? 5020 Basic 5021 Advanced 5022 `Allows you to specify the percentage of CPU resources allocated to each resource consumer group. 5023_Allows you more flexibility to specify the percentage of CPU resources allocated to consumer groups using a multi-level approach. Unused resources at one level are automatically allocated to groups on the next. You can also specify the maximum number of parallel execution servers for operations issued by any session within a resource consumer group. 5024 5025 5026 Degree of Parallelism 5027?ould you like to specify the maximum degree of parallelism for the resource consumer groups? Specifying the degree of parallelism allows you to limit the number of parallel execution servers for operations issued by any session within a resource consumer group. This can prevent one session from using up all the servers, leaving none for the other sessions. If you know that one group makes heavy use of parallel execution servers, then it is useful to set a maximum value. 5028 -No. Use the defaults managed by the database. 5029 /Yes. Specify the maximum degree of parallelism. 5030 Percentages 5031 CPU Resource Allocation 5032 ?pecify the percentage of resource allocated to each consumer group. Percentages represent the minimum CPU resources allocated to a group when all groups are using all allocated resources. The sum of percentages must be less than or equal to 100. 5033 !Add Existing Consumer Group(s)... 5034 Resource Plan Activation 5035 -Would you like to activate the resource plan? 5036 ?ctivate this resource plan immediately and deactivate the existing plan ''{0}'' for the database. Only one plan can be active at any time. 5057 QActivate this resource plan immediately. Only one plan can be active at any time. 5037 fDo not activate this resource plan. You may activate this resource plan later from its property sheet. 5038 ?ote: If you want this or any other resource plan to be activated when the database starts, you need to update the initialization parameter 'RESOURCE_MANAGER_PLAN' to be the plan name. 5039 Resource Plan Wizard 5040 5041?ould you like to modify the percentage of resource allocated to each consumer group? Percentages represent the minimum CPU resources allocated to a group when all groups at a level are using all allocated resources. For any level, the sum of percentages must be less than or equal to 100. CPU resource allocation starts at High level. If there are any unused resources, they are automatically made available to the next level. 5042 Yes. Overwrite the defaults. 5043 >No. Use the defaults calculated based on the importance level. 5044 High 5045 Medium 5046 Low 5047 Add Existing Consumer Group(s) 5048 Available Groups: 5049 Selected Groups: 5050 KSelect the resource consumer group(s) you want to add to the resource plan. 5051 Group Importance Level 5052 Summary 5053 7Review the SQL commands for creating the Resource Plan. 5054 ?pecify a level of importance for the resource consumer groups. Importance levels you specify will be used to calculate CPU resources allocated to each group. 5055 &Higher groups can consume 100% of CPU. 5058 5Please specify names for all Resource Consumer Groups 5059 &Sum of percentages must not exceed 100 5060 )Duplicate Resource Consumer Group ''{0}'' 5061 .Resource Consumer Group ''{0}'' already exists 5200 &Undo 5201 Undo Management: 5202 Current Undo Tablespace: 5203 Undo Retention: 5204 Seconds 5205 Minutes 5206 Hours 5207 Automatic Undo Management 5208 Automatic 5209 Manual 5300 $Control instance crash recovery time 5301 Media Recovery 5302 Desired mean time to recover: 5303 (Current estimated mean time to recover: 5304 5305 5306 Unknown 5400 Shared Pool 5401 Buffer Cache 5402 Large Pool 5403 Java Pool 5460 ?here is no data to display because there is no active Resource Plan. You can activate a Resource Plan through its property pages. 6000 Pool 6001 Block Size 6002 Size For Estimate 6003 Buffers For Estimate 6004 Estd Physical Read Factor 6005 Estd Physical Reads 6006 Buffer Cache Size Advice 6007 Cache Size (MB) 6008 !Relative change in physical reads 6009 0Change in physical reads for various cache sizes 6010 Current cache size 6011 ?If you set cache size to {0}MB physical reads will be unchanged 6012 CIf you set cache size to {0}MB physical reads will increase by {1}% 6013 CIf you set cache size to {0}MB physical reads will decrease by {1}% 6014 Buffer Cache Size Advice - 6015 Estimated Physical Reads 6016 6017 Close 6018 Advice... 6019 6020?uffer Cache Size Advice depends on block reference statistics collected over a period of time. Do you want to enable collection of statistics by setting the initialization parameter 'db_cache_advice' to ON? Note: Since there is a small overhead associated with statistics collection you may want to set db_cache_advice to OFF later. Press the 'All Initialization Parameters' button on General page to edit the value of db_cache_advice. 6021 ?uffer Cache Size Advice depends on block reference statistics collected over a period of time. No statistics have been collected yet because no applications have accessed the database. Press the Refresh button below to retrieve the latest data. 6045The buffer cache advisory is currently turned off due to the use of deprecated buffer cache sizing parameters (e.g. db_block_buffers). To turn on the advisory, please use the new dynamic parameters such as db_cache_size, db_keep_cache_size, db_recycle_cache_size, etc. 6026?his advisory depends on statistics collected over a period of time. Do you want to enable collection of statistics by setting the initialization parameter 'statistics_level' to TYPICAL? Note: Since there is a small overhead associated with statistics collection you may want to set statistics_level to BASIC later. Press the 'All Initialization Parameters' button on General page to edit the value of statistics_level. 6027 Statistics Collection 6030 Create an spfile from a pfile 6031 Create a pfile from an spfile 6032 RBoth the pfile and the spfile must be located on the same machine as the database. 6034 pfile: 6035 spfile: 6036 Local Browse... 6037 pfile location 6038 spfile location 6039 spfile Created 6040 pfile Created 6022 Buffer Cache Size: 6023 6024 6025 5461 Sort Statistics 5462 2Specify the statistic to sort the top sessions by. 5463 Statistic Category: 5464 Sort Statistic: 5465 5466 Redo 5467 Enqueue 5468 Cache 5469 Operating System 5470 5493 Global Cache 5471 SQL 5472 Other 5473 Debug 5492 All 5474 5475 Top sessions by: 5476 Customize... 5477 Show Top: 5478 5479 Details... 5480 Kill Session... 5481 CPU 5482 5483 I/O 5484 User Transactions 5485 Custom 5486 BPlease click on Customize button to specify the sorting statistic. 5494 5487 All Locks 5488 BLOCKING/WAITING Locks 5489 User Type Locks 5490 Filter: 5491 Total Locks: 6150 Rollback Segments 6151 6152 Name 6153 Tablespace 6154 Extents 6155 Size (MB) 6180 6181 6182 6183 Days 6184 Undo Retention ({0}) 6185 Space Required (MB) 6186 5Space required, based on maximum undo generation rate 6187 5Space required, based on average undo generation rate 6188 Current Undo Retention setting 6704 FIf you set Undo Retention to {0} average undo space required is {1} MB 6705 FIf you set Undo Retention to {0} maximum undo space required is {1} MB 6190 Active: 6191 Unexpired: 6192 Expired: 6193 Unused: 6194 System: 6195 Total: 6196 Undo Space Utilization 6197 Undo Space Requirements Estimate 6175 Active transactions 6176 Unexpired extents 6177 Expired extents 6178 Unused space 6179 System 6198 Resumable Statement Information 6199 6200 Start time: 6201 Suspend time: 6202 Time out (secs): 6203 SQL Text: 6204 Error Message: 6300 MTTR (Seconds) 6301 Dirty Buffer Limit 6302 Estimated Cache Writes 6303 Estimated Cache Write Factor 6304 Estimated Total Writes 6305 Estimated Total Write Factor 6306 Estimated Total I/Os 6307 Estimated Total I/O Factor 6308 MTTR Advice 6309 %Target Mean Time To Recover (Seconds) 6310 Relative change in total I/O 6311 .Change in total I/O for various values of MTTR 6312 Current MTTR setting 6313 ;If you set MTTR to {0} seconds, total I/O will be unchanged 6314 ?If you set MTTR to {0} seconds, total I/O will increase by {1}% 6315 ?If you set MTTR to {0} seconds, total I/O will decrease by {1}% 6316 MTTR Advice - 6317 ZMTTR Advice not yet available. Press the Refresh button below to retrieve the latest data. 6318 6319 MTTR Cost Estimates 6320 6321 6322 6323 6400 ]In this mode Oracle manages the size of SQL work areas automatically for the entire instance. 6401 Aggregate PGA Target: 6402 Current PGA Allocated: 6403 &Maximum PGA Allocated (since startup): 6404 '% allocated PGA used by SQL work areas: 6405 Percentage of operations in 6406 optimal (fully cached) mode: 6407 one pass mode: 6408 multipass mode: 6409 ?n general PGA memory should be set large enough to eliminate multipass operations and maximize optimal mode executions. Also, the sum of PGA and SGA should be less than the total system memory minus memory required by the OS and other applications. 6576 zThe sum of PGA and SGA should be less than the total system memory minus memory required by the OS and other applications. 6578 VPGA advice is not yet available. Press the Refesh button below to get the latest data. 6579 WPGA details is not yet available. Press the Refesh button below to get the latest data. 6410 PGA 6411 PGA: 6412 6413 6414 Memory Usage Details... 6500 PGA Memory Usage Details - 6501 SQL Workarea Histogram 6502 6503 Size Range - Low 6504 Size Range - High 6505 Optimal Executions 6506 One Pass Executions 6507 Multipass Executions 6508 Total Executions 6509 PGA Memory Usage Details 6510 Workarea Size 6511 Executions 6512 Optimal executions 6513 One pass executions 6514 Multipass executions 6515 {0} optimal executions ({1}%) 6516 {0} one pass executions ({1}%) 6517 {0} multipass executions ({1}%) 6550 PGA target for estimate (MB) 6551 Cache hit percentage 6552 Overflow 6553 PGA Aggregate Target Advice 6554 PGA Target (MB) 6555 6556 ,Variation of cache hit ratio with PGA target 6557 Current PGA target 6558 EIf you set PGA target size to {0}MB cache hit percentage will be {1}% 6559 PGA Target Advice - 6560 PGA Target: 6561 ,Chart should display PGA target sizes up to 6562 6563 Estimated cache hit percentage 6564 Chart should show: 6565 Execution percentages 6566 Number of executions 6567 Memory usage details... 6568 1PGA Target specified is too low. Continue anyway? 6569 Overflow range 6570 *Show memory usage details for PGA target: 6700 SGA Max Size: 6571 Started with spfile: 6577 Started with pfile 6572 Initialization Parameter Changes 6573 tPlease add the following lines to your init.ora file on the database server for future database startup using pfile. 6574 6701 Maximum Undo Generation Rate: 6702 bytes/minute 6703 Average Undo Generation Rate: 6706 UNLIMITED 6800 Shared Pool Size Advice - 6801 aShared Pool Advice not yet available. Press the Refresh button below to retrieve the latest data. 6802 Shared Pool Size: 6803 6804 Estimated Time Saved 6805 6806 6807 6808 Size for estimate (MB) 6819 Size Factor 6809 Time Saved Factor 6818 Time Saved (Seconds) 6810 Shared Pool Size Advice 6811 Shared Pool Size (MB) 6812 %Relative change in parse time savings 6813 EChange in elapsed parse time savings for various sizes of Shared Pool 6814 Current Shared Pool size 6815 IIf you set Shared Pool size to {0}MB parse time savings will be unchanged 6816 MIf you set Shared Pool size to {0}MB parse time savings will increase by {1}% 6817 MIf you set Shared Pool size to {0}MB parse time savings will decrease by {1}% 6840 RDynamically shrinking shared pool could take a long time. Do you want to continue? 6841 Warning 6850 XML Database Parameters 6851 4Following are XML Database configuration parameters: 6575 Cache Hit Percentage: 6852 <Only SYS, DBA or XDBADMIN can edit configuration parameters. 6790 ZThis feature requires Oracle version {0} or later. You are connected to Oracle version {1} 6791 Feature unavailable 6853 ?our changes to static initialization parameters will be saved to the spfile. However, they will not be in effect unless the instance shutdown and restarted. Do you want to save the changes? oracle/sysman/resources/VtoiMsg java/util/ListResourceBundle !oracle/sysman/resources/VtoiMsgID !"# $ %&