Edit D:\app\Administrator\product\11.2.0\dbhome_1\owb\lib\int\oracle\sysman\resources\ViwCMMsg.class
?? /? ?? ????? !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~?????????????????????????????????????????????????????????????????????????????????????????????????????????? contents [[Ljava/lang/Object; <init> ()V Code LineNumberTable getContents ()[[Ljava/lang/Object; <clinit> SourceFile ViwCMMsg.java ?? ?? [Ljava/lang/Object; java/lang/Object 1000 ,>>>An unexpected exception occurred: >>> {0} 1001 'Not a valid Oracle Applications schema. 2000 $>>>Connection failed. >>>Reason: {0} 2001 +>>>Lost database connection. >>>Reason: {0} 2003 >>>File not found: {0} 2004 ?rerequisite patch has not been applied to the Oracle Applications instance. For more information, refer to the Oracle Management Pack for Oracle Applications Readme. 3002 Concurrent Managers 3003 Requests 3004 Programs 3005 &Concurrent Processing Tuning Assistant 3011 Tuning Advisor 3006 #Concurrent Manager Usage by Program 3007 ?isplays a summary of Concurrent Manager Usage during a given time period. Use this information to determine which concurrent manager and program combinations are potential bottlenecks. 3008 Program Run Summary by Status 3009!Displays a summary of Program Executions during a given time period. Results are grouped by execution status. Use this information to examine expected execution times for programs. Select a row or rows in this report and drill down to see which requests ran for the selected program(s). 3015 Reporting Period 3016 Requests that Waited 3017 MRequests that Waited shows additional information about requests that waited. 3018 30191Tuning Advisor provides information about possible problems that may be impeding the concurrent processing performance and offers possible solutions for correcting the problems. This report shows utilization information and the number of waiting requests for each concurrent manager by hour over a 24 hour by 7 day period. Visually identify which concurrent managers were running at near capacity and there were many waiting requests during the same time period. Drilldown from selected time periods with possible problems to see possible tuning suggestions. 3027 Tuning Suggestion 3028 ?uning Suggestion provides possible solutions for correcting the problems that may be impeding the concurrent processing performance. 3020 (Concurrent Manager High Utilization (%): 3021 'Concurrent Manager Low Utilization (%): 3022 "Waiting Request Backlog Threshold: 3026 /Tuning Advisor Problem Identification Threshold 3235 RUtilization percentage at which a concurrent manager is considered highly utilized 3236 ZUtilization percentage at which a concurrent manager is considered to have excess capacity 3237 XThe number of waiting requests at which waiting requests are considered to be backlogged 3238 HParameters which control how Tuning Advisor identifies possible problems 3023 Select Items for Report 3024 Yes 3025 No 3168 Completed 3169 Inactive 3170 Pending 3171 Running 3172 Waiting 3173 Resuming 3174 Normal 3175 Canceled 3176 Error 3177 Scheduled 3178 Warning 3179 On Hold 3180 No Manager 3181 Standby 3182 Suspended 3183 Terminating 3184 Disabled 3185 PAUSED 3186 Terminated 3034 !Waiting Requests by Hour (24 x 7) 30354Waiting Requests by Hour shows the amount of time requests waited by hour over a 24 hour by 7 day period. Visually locate the time periods with the largest backup. Select hours in the report and drill down to see which requests were waiting. Use this information to adjust request scheduling, if possible. 3012 Time Period 3013 Utilization 3014 Capacity (minutes) 3029 Requests that Ran 3030 3189 Repeating Requests 3031 Diagnostic Message 3032 Suggestions 3033 Reason 3036 Suggestion {0} 3109 Resubmit Interval 3110 Resubmit Interval Unit 3111 Resubmit Interval Type 3112 Resubmit Time 3113 Resubmit End Date 3115 Description 3203 %0 capacity with many waiting requests 3204 +High utilization with many waiting requests 3205 *Low utilization with many waiting requests 3206 ?here were many waiting requests during this time period while the capacity of one of the concurrent managers which could run these waiting requests was 0. Click "Suggestions" below to see tuning suggestions. 3208 ?here were many waiting requests during this time period while this concurrent manager was under utilized. Waiting requests may be on hold or they were processed during this time period. No tuning suggestions for this situation. 3207 ?here were many waiting requests during this time period while this concurrent manager was highly utilized. Click "Suggestions" below to see tuning suggestions. 3209 ?onsider increasing the worker processes for this concurrent manager or adding more concurrent managers if hardware, OS and database resources are available. 3210 ?onsider changing workshift of this concurrent manager or adding more concurrent managers if hardware, OS and database resources are available. 3211 xConsider rebalancing resources from the following concurrent managers which were under utilized at the same time period. 3212 ]Consider rescheduling the following repeating requests to other time periods with light load. 3213 WConsider telling users theses programs were waiting more often during this time period. 3214?here were many waiting requests at this time period and this concurrent manager was highly utilized. It means more concurrent manager capacity would be helpul to reduce the waiting requests. If hardware, OS and database resources are available, adding more concurrent managers will achieve this goal. Note: Adding concurrent managers or increasing worker processes requires additional resources from the node, database and network. If such resources are not available, adding additional concurrent managers or increasing worker processes will probably degrade performance. Use Oracle Capacity Planner to get hardware, OS and Database statistics. 3215fThere were many waiting requests at this time period and the capacity of this concurrent manager was 0. Adding capacity of this concurrent manager would be helpul to reduce the request waiting time. If hardware, OS and database resources are available, adding more concurrent managers will also achieve this goal. Note: Adding concurrent managers will cause additional resources will be consumed on the node, database and network. If such resources are not available, adding additional concurrent managers will probably degrade performance. Use Oracle Capacity Planner to get hardware, OS and Database statistics. 3216?here were many waiting requests at this time period and this concurrent manager was highly utilized. At the same time, there were other concurrent managers which were under utilized and some hardware, OS and database resources were wasted. Removing these resources and giving them to this highly utilized concurrent managers will be helpful to reduce waiting requests and improve performance. 3217?There were many waiting requests at this time period and the capacity of this concurrent manager was 0. At the same time, there were other concurrent managers which which were under utilized and some hardware, OS and database resources were wasted. Removing these resources and giving them to this concurrent manager will be helpful to reduce request waiting time improve performance. 3218?epeating requests were scheduled to run repeatedly. If these repeating requests could be rescheduled to other time periods with light load, it will reduce requests waiting time and improve performance. Note 1: If a repeating request was scheduled to run too often (less than an hour), rescheduling it will probably not improve performance. Note 2: These repeating requests included repeating requests from running requests and waiting requests. 3219?epeating requests were scheduled to run repeatedly. These repeating requests were scheduled to run repeatedly when the capacity for this concurrent manager was 0. If they could be rescheduled to other time periods when this concurrent manager has capacity, it will reduce requests waiting time. Note 1: If a repeating request was scheduled to run too often (less than an hour), rescheduling it will probably not improve performance. 3220RUsers submitted requests for these programs and they couldn't get run immediately or they were running but caused other requests waiting. Tell users about this situation and ask them to submit these kind of requests at a different time if possible. Note: The requests were non-repeating requests and included waiting or running requests. 3221?sers submitted requests for these programs and they couldn't get run immediately because one of the concurrent managers which could run them was not up. Tell users about this situation and ask them to submit these kind of requests at a different time if possible. Note: The non-repeating requests of these programs included non-repeating requests from running requests and waiting requests. 3038 Concurrent Manager 3039 Program 3040 Times Run 3041 CM ID 3042 Avg Duration (min) 3043 Min Duration (min) 3044 Max Duration (min) 3045 Total Duration (min) 3046 Node 3047 Type 3048 Wait Length (min) 3049 User Name 3050 Priority 3051 Single Thread 3052 Earliest Start 3053 Actual Start 3054 Actual Completion 3055 Request ID 3056 Constrained 3057 Run Alone 3058 HH24:MI DD-MON-YYYY 3059 $Concurrent Managers by Hour (24 x 7) 3060?oncurrent Managers by Hour shows availability and utilization of concurrent managers by hour over a 24 hour by 7 day period. This report includes capacity information for each concurrent manager that was running. The capacity is based on the number of minutes that processes for each concurrent manager ran during each hour period. Visually identify which concurrent managers had excess capacity and which were running at near capacity. This report also includes information on the overall number and runtime of requests during each hour period. Drilldown from selected time periods to see which requests were running. Adjust the scheduling of requests accordingly. 3061 3062 GRequests that Ran shows additional information about requests that ran. 3063 Long Running Requests 3064?ong Running Requests shows run times for requests started during a given time period that took longer than a given number of minutes to run. Use this information to identify slow requests. A possible remedy for slow requests would be to schedule the requests during off peak hours. Another use for this information is to identify programs which could run in a concurrent manager dedicated to long running requests. Creating specialized concurrent managers to handle long running and short running requests can improve overall throughput because short running requests that do not have to wait for long running requests to complete will be processed more quickly. 3065 Duration (min) 3114 Duration (hour) 3066 Parameters 3067 Program Wait Summary 3068Displays a summary of programs that waited during a given time period. Use this information to identify programs that waited a long time relative to other programs. Select a row or rows in this report and drill down to see which requests waited for the selected program(s). 3069 Avg Wait (min) 3070 Min Wait (min) 3071 Max Wait (min) 3072 Total Wait (min) 3073 Program: 3074 Data Displayed: 3076 (Data is displayed for the chosen Program 3075 UDisplay in red all hours with Minutes Requests Spent Waiting greater than this value: 3079 Minutes Requests Spent Waiting 3080 Number of Requests that Waited 3077 Choose a Display Option 3078 ;Move this slider to adjust the red/yellow display threshold 3082 Monday 3083 Tuesday 3084 Wednesday 3085 Thursday 3086 Friday 3087 Saturday 3088 Sunday 3081 All Programs 3090 Concurrent Manager: 3091 Concurrent Manager Utilization 3092 'Concurrent Manager Utilization Fraction 3093 &Concurrent Manager Capacity in Minutes 3094 Request Runtime in Minutes 3095 Number of Requests that Ran 3096 4Request Runtime to Concurrent Manager Capacity Ratio 3097 Choose Display Option 3098 3099 3Data is displayed for the chosen Concurrent Manager 3100 All Concurrent Managers 3101 Previous Week 3102 Previous Four Weeks 3103 One Week Starting: 3104 Time Period: 3105 Start: 3106 End: 3107 Requests included in report 3108 Minimum duration: 3118 Minimum wait time: 3119 Maximum wait time: 3120 Status 3121 Application 3122 Application included in report 3123 3124 Application: 3125 All Applications 3126 "Short Running Requests that Waited 3127?hort Running Requests that Waited is useful for determining which requests are waiting a relatively long time compared to their run time. A request can wait longer than its runtime. If many such requests are identified, it may be beneficial to create a concurrent manager which specializes in processing short running requests. This may help to increase the throughput of these requests. 3158 Request Run Summary by Month 3159?equest Run Summary by Month shows the total request runtime, average request runtime and number of requests that ran on a monthly basis. Use this information to determine if overall performance is improving or deteriorating on a month to month basis. The average duration of a request in minutes('Avg Duration (min)') is a good indication of system performance change over time. Also, use this information to note if the number of requests ('Number of Requests') is increasing or decreasing over time. 3128 Phase 3129 Maximum run time: 3130 Drilldown from: 3131 Requests: 3132 Time Periods: 3133 ,Concurrent Processing Tuning Assistant Login 3134 &Login to an Oracle Applications Schema 3136 Retrieving Request Details 3138 $Retrieving Request Notification List 3142 Retrieving Request Print List 3135 Retrieving Requests that Waited 3137 Calculating Statistics 3139 Retrieving Concurrent Managers 3140 &Retrieving Concurrent Manager Capacity 3141 )Retrieving Concurrent Manager Utilization 3037 &Analyzing Data And Getting Suggestions 3143 Request Limit 3144 3About Oracle Concurrent Processing Tuning Assistant 3202 -&About Concurrent Processing Tuning Assistant 3148 aDisplay in red all hours with Concurrent Manager Utilization greater than this percent (%) value: 3149 2Oracle Concurrent Processing Tuning Assistant Help 3161 Number of Requests 3187 Print Style 3190 Application ID 3191 Notify 3192 Print To 3193 Name 3194 Requestor 3195 3196 Schedule 3197 Date 3188 Copies 3198 General 3199 Schedule Options 3200 Completion Options 3247 bThe number of cells representing high utilization and many waiting requests in the overview table. 3248 aThe number of cells representing low utilization and many waiting requests in the overview table. 3249 ?he number of cells representing that there was no capacity available and there were many requests waiting to be processed in the overview table. 3250 IThe number of cells representing no problems found in the overview table. 3223 Legend: 3224 3225 3226 &No capacity with many waiting requests 3227 No problem conditions found 3228 #Concurrent Manager Problem Overview 3229 QSelect a problem area and drilldown to see problem details and tuning suggestions 3230 7Select a concurrent manager to see its problem overview 3231 Increasing Capacity 3232 Rebalancing Resources 3233 Rescheduling Requests 3234 3239 High Utilization Cell Count 3240 Low Utilization Cell Count 3241 No Capacity Cell Count 3242 &No Problem Conditions Found Cell Count 3243 `Concurrent manager utilization(%) and number of waiting requests run by this concurrent manager. 3244 'Oracle Applications Connect Information 3245 Oracle Applications 3246 ?o concurrent managers have been discovered. Please use "Add Connection" under File menu, or use the Discovery Wizard on Enterprise Manager console to add them to the navigator then relaunch this tool. 3501 Connecting to "{0}"@{1}... 3502 Disconnecting from {0}... 3000 -Oracle Concurrent Processing Tuning Assistant 3150 Minutes 3151 Hours 3152 Days 3153 Weeks 3154 None 3160 Year - Month 3162 Language 3163 Submitted 3164 Requested Start 3165 Completion Text 3166 Request Details 3167 3201 Req_{0}.{1} 3251 )&Connect to an Oracle Applications Schema 3252 SThis Information is only available when connecting to a live Applications instance. oracle/sysman/resources/ViwCMMsg java/util/ListResourceBundle "oracle/sysman/resources/ViwCMMsgID !?? ? ?? ?? ? *? ? ? ? ?? ? ? ? ? ? ?? ? ? ? Y? YSYSSY? YSYSSY? Y SY SSY? Y SY SSY? Y SYSSY? YSYSSY? YSYSSY? YSYSSY? YSYSSY ? YSYSSY ? YSYSSY ? YSY SSY ? Y SY SSY ? Y SY SSY? Y!SY"SSY? Y#SY$SSY? Y%SY&SSY? Y'SY(SSY? Y)SYSSY? Y*SY+SSY? Y,SY-SSY? Y.SY/SSY? Y0SY1SSY? Y2SY3SSY? Y4SY5SSY? Y6SY7SSY? Y8SY9SSY? Y:SY;SSY ? Y<SY=SSY ? Y>SY?SSY ? Y@SYASSY ? YBSYCSSY ? YDSYESSY!? YFSYGSSY"? YHSYISSY#? YJSYKSSY$? YLSYMSSY%? YNSYOSSY&? YPSYQSSY'? YRSYSSSY(? YTSYUSSY)? YVSYWSSY*? YXSYYSSY+? YZSY[SSY,? Y\SY]SSY-? Y^SY_SSY.? Y`SYaSSY/? YbSYcSSY0? YdSYeSSY1? YfSYgSSY2? YhSYiSSY3? YjSYkSSY4? YlSYmSSY5? YnSYoSSY6? YpSYqSSY7? YrSYsSSY8? YtSYuSSY9? YvSYwSSY:? YxSY&SSY;? YySYzSSY<? Y{SY|SSY=? Y}SY~SSY>? YSY?SSY?? Y?Y?SY@? Y?Y?SYA? Y?Y?SYB? Y?Y?SYC? Y?Y?SYD? Y?Y?SYE? Y?Y?SYF? Y?Y?SYG? Y?Y?SYH? Y?Y?SYI? Y?Y?SYJ? Y?Y?SYK? Y?Y?SYL? Y?Y?SYM? Y?Y?SYN? Y?Y?SYO? Y?Y?SYP? Y?Y?SYQ? Y?Y?SYR? Y?Y?SYS? Y?Y?SYT? Y?Y?SYU? Y?Y?SYV? Y?Y?SYW? Y?Y?SYX? Y?Y?SYY? Y?Y?SYZ? Y?Y?SY[? Y?Y?SY\? Y?Y?SY]? Y?Y?SY^? Y?Y?SY_? Y?Y?SY`? Y?Y?SYa? Y?Y?SYb? Y?Y?SYc? Y?Y?SYd? Y?Y?SYe? Y?Y?SYf? Y?Y?SYg? Y?Y?SYh? Y?Y?SYi? Y?Y?SYj? Y?Y?SYk? Y?Y?SYl? Y?Y?SYm? Y?Y?SYn? Y?Y?SYo? Y?Y?SYp? Y?YwSSYq? Y?Y?SYr? Y?Y?SYs? Y?Y?SYt? Y?Y?SYu? Y?Y?SYv? Y?Y?SYw? Y?Y?SYx? Y?Y?SYy? Y?Y?SYz? Y?Y?SY{? Y?Y?SY|? Y?Y?SY}? Y?Y?SY~? Y?Y?SSY? Y SYSSY ?? YSYSSY ?? YSYSSY ?? YSYSSY ?? YSY SSY ?? Y SY SSY ?? Y SY SSY ?? YSYSSY ?? YSYSSY ?? YSYSSY ?? YSYSSY ?? YSYSSY ?? YSYSSY ?? YSYSSY ?? Y SY SSY ?? Y SY SSY ?? Y SY!SSY ?? Y"SY#SSY ?? Y$SY%SSY ?? Y&SY'SSY ?? Y(SY)SSY ?? Y*SY+SSY ?? Y,SY SSY ?? Y-SY.SSY ?? Y/SY0SSY ?? Y1SY2SSY ?? Y3SY4SSY ?? Y5SY6SSY ?? Y7SY8SSY ?? Y9SY:SSY ?? Y;SY<SSY ?? Y=SY>SSY ?? Y?SY@SSY ?? YASYBSSY ?? YCSYDSSY ?? YESYFSSY ?? YGSYHSSY ?? YISYJSSY ?? YKSY?SY ?? YLSYMSSY ?? YNSYOSSY ?? YPSYQSSY ?? YRSYSSSY ?? YTSYUSSY ?? YVSYWSSY ?? YXSYYSSY ?? YZSY[SSY ?? Y\SY]SSY ?? Y^SY_SSY ?? Y`SYaSSY ?? YbSYcSSY ?? YdSYeSSY ?? YfSYgSSY ?? YhSYiSSY ?? YjSYkSSY ?? YlSYmSSY ?? YnSYoSSY ?? YpSYqSSY ?? YrSYsSSY ?? YtSYuSSY ?? YvSYwSSY ?? YxSYySSY ?? YzSY{SSY ?? Y|SY}SSY ?? Y~SYSSY ?? Y?SY?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?YGSSY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?YSSY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?SY ?? Y?Y?S? ? ? ? ? ?
Ms-Dos/Windows
Unix
Write backup
jsp File Browser version 1.2 by
www.vonloesch.de