/        !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~contents[[Ljava/lang/Object;()VCodeLineNumberTable getContents()[[Ljava/lang/Object; SourceFile ViwCMMsg.java  [Ljava/lang/Object;java/lang/Object1000,>>>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}2004Prerequisite patch has not been applied to the Oracle Applications instance. For more information, refer to the Oracle Management Pack for Oracle Applications Readme.3002Concurrent Managers3003Requests3004Programs3005&Concurrent Processing Tuning Assistant3011Tuning Advisor3006#Concurrent Manager Usage by Program3007Displays 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.3008Program Run Summary by Status3009!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).3015Reporting Period3016Requests that Waited3017MRequests that Waited shows additional information about requests that waited.301830191Tuning 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.3027Tuning Suggestion3028Tuning 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 Threshold3235RUtilization percentage at which a concurrent manager is considered highly utilized3236ZUtilization percentage at which a concurrent manager is considered to have excess capacity3237XThe number of waiting requests at which waiting requests are considered to be backlogged3238HParameters which control how Tuning Advisor identifies possible problems3023Select Items for Report3024Yes3025No3168 Completed3169Inactive3170Pending3171Running3172Waiting3173Resuming3174Normal3175Canceled3176Error3177 Scheduled3178Warning3179On Hold3180 No Manager3181Standby3182 Suspended3183 Terminating3184Disabled3185PAUSED3186 Terminated3034!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 Period3013 Utilization3014Capacity (minutes)3029Requests that Ran30303189Repeating Requests3031Diagnostic Message3032 Suggestions3033Reason3036Suggestion {0}3109Resubmit Interval3110Resubmit Interval Unit3111Resubmit Interval Type3112 Resubmit Time3113Resubmit End Date3115 Description3203%0 capacity with many waiting requests3204+High utilization with many waiting requests3205*Low utilization with many waiting requests3206There 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.3208There 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.3207There were many waiting requests during this time period while this concurrent manager was highly utilized. Click "Suggestions" below to see tuning suggestions.3209Consider increasing the worker processes for this concurrent manager or adding more concurrent managers if hardware, OS and database resources are available.3210Consider changing workshift of this concurrent manager or adding more concurrent managers if hardware, OS and database resources are available.3211xConsider 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.3213WConsider telling users theses programs were waiting more often during this time period.3214There 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.3216There 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.3217There 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.3218Repeating 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.3219Repeating 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.3221Users 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.3038Concurrent Manager3039Program3040 Times Run3041CM ID3042Avg Duration (min)3043Min Duration (min)3044Max Duration (min)3045Total Duration (min)3046Node3047Type3048Wait Length (min)3049 User Name3050Priority3051 Single Thread3052Earliest Start3053 Actual Start3054Actual Completion3055 Request ID3056 Constrained3057 Run Alone3058HH24:MI DD-MON-YYYY3059$Concurrent Managers by Hour (24 x 7)3060Concurrent 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.30613062GRequests that Ran shows additional information about requests that ran.3063Long Running Requests3064Long 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.3065Duration (min)3114Duration (hour)3066 Parameters3067Program Wait Summary3068Displays 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).3069Avg Wait (min)3070Min Wait (min)3071Max Wait (min)3072Total Wait (min)3073Program:3074Data Displayed:3076(Data is displayed for the chosen Program3075UDisplay in red all hours with Minutes Requests Spent Waiting greater than this value:3079Minutes Requests Spent Waiting3080Number of Requests that Waited3077Choose a Display Option3078;Move this slider to adjust the red/yellow display threshold3082Monday3083Tuesday3084 Wednesday3085Thursday3086Friday3087Saturday3088Sunday3081 All Programs3090Concurrent Manager:3091Concurrent Manager Utilization3092'Concurrent Manager Utilization Fraction3093&Concurrent Manager Capacity in Minutes3094Request Runtime in Minutes3095Number of Requests that Ran30964Request Runtime to Concurrent Manager Capacity Ratio3097Choose Display Option309830993Data is displayed for the chosen Concurrent Manager3100All Concurrent Managers3101 Previous Week3102Previous Four Weeks3103One Week Starting:3104 Time Period:3105Start:3106End:3107Requests included in report3108Minimum duration:3118Minimum wait time:3119Maximum wait time:3120Status3121 Application3122Application included in report31233124 Application:3125All Applications3126"Short Running Requests that Waited3127Short 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.3158Request Run Summary by Month3159Request 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.3128Phase3129Maximum run time:3130Drilldown from:3131 Requests:3132 Time Periods:3133,Concurrent Processing Tuning Assistant Login3134&Login to an Oracle Applications Schema3136Retrieving Request Details3138$Retrieving Request Notification List3142Retrieving Request Print List3135Retrieving Requests that Waited3137Calculating Statistics3139Retrieving Concurrent Managers3140&Retrieving Concurrent Manager Capacity3141)Retrieving Concurrent Manager Utilization3037&Analyzing Data And Getting Suggestions3143 Request Limit31443About Oracle Concurrent Processing Tuning Assistant3202-&About Concurrent Processing Tuning Assistant3148aDisplay in red all hours with Concurrent Manager Utilization greater than this percent (%) value:31492Oracle Concurrent Processing Tuning Assistant Help3161Number of Requests3187 Print Style3190Application ID3191Notify3192Print To3193Name3194 Requestor31953196Schedule3197Date3188Copies3198General3199Schedule Options3200Completion Options3247bThe number of cells representing high utilization and many waiting requests in the overview table.3248aThe number of cells representing low utilization and many waiting requests in the overview table.3249The number of cells representing that there was no capacity available and there were many requests waiting to be processed in the overview table.3250IThe number of cells representing no problems found in the overview table.3223Legend:322432253226&No capacity with many waiting requests3227No problem conditions found3228#Concurrent Manager Problem Overview3229QSelect a problem area and drilldown to see problem details and tuning suggestions32307Select a concurrent manager to see its problem overview3231Increasing Capacity3232Rebalancing Resources3233Rescheduling Requests32343239High Utilization Cell Count3240Low Utilization Cell Count3241No Capacity Cell Count3242&No Problem Conditions Found Cell Count3243`Concurrent manager utilization(%) and number of waiting requests run by this concurrent manager.3244'Oracle Applications Connect Information3245Oracle Applications3246No 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.3501Connecting to "{0}"@{1}...3502Disconnecting from {0}...3000-Oracle Concurrent Processing Tuning Assistant3150Minutes3151Hours3152Days3153Weeks3154None3160 Year - Month3162Language3163 Submitted3164Requested Start3165Completion Text3166Request Details31673201 Req_{0}.{1}3251)&Connect to an Oracle Applications Schema3252SThis Information is only available when connecting to a live Applications instance. oracle/sysman/resources/ViwCMMsgjava/util/ListResourceBundle"oracle/sysman/resources/ViwCMMsgID!*YYSYSSYYSYSSYY SY SSYY SY SSYY SYSSYYSYSSYYSYSSYYSYSSYYSYSSY YSYSSY YSYSSY YSYSSY YSYSSY YSY SSYY!SY"SSYY#SY$SSYY%SY&SSYY'SY(SSYY)SYSSYY*SY+SSYY,SY-SSYY.SY/SSYY0SY1SSYY2SY3SSYY4SY5SSYY6SY7SSYY8SY9SSYY:SY;SSYYSY?SSYY@SYASSYYBSYCSSY YDSYESSY!YFSYGSSY"YHSYISSY#YJSYKSSY$YLSYMSSY%YNSYOSSY&YPSYQSSY'YRSYSSSY(YTSYUSSY)YVSYWSSY*YXSYYSSY+YZSY[SSY,Y\SY]SSY-Y^SY_SSY.Y`SYaSSY/YbSYcSSY0YdSYeSSY1YfSYgSSY2YhSYiSSY3YjSYkSSY4YlSYmSSY5YnSYoSSY6YpSYqSSY7YrSYsSSY8YtSYuSSY9YvSYwSSY:YxSY&SSY;YySYzSSY<Y{SY|SSY=Y}SY~SSY>YSYSSY?YSYSSY@YSYSSYAYSYSSYBYSYSSYCYSYSSYDYSYSSYEYSYSSYFYSYSSYGYSYSSYHYSYSSYIYSYSSYJYSYSSYKYSYSSYLYSYSSYMYSYSSYNYSYSSYOYSYSSYPYSYSSYQYSYSSYRYSYSSYSYSYSSYTYSYSSYUYSYSSYVYSYSSYWYSYSSYXYSYSSYYYSYSSYZYSYSSY[YSYSSY\YSYSSY]YSYSSY^YSYSSY_YSYSSY`YSYSSYaYSYSSYbYSYSSYcYSYSSYdYSYSSYeYSYSSYfYSYSSYgYSYSSYhYSYSSYiYSYSSYjYSYSSYkYSYSSYlYSYSSYmYSYSSYnYSYSSYoYSYSSYpYSYwSSYqYSYSSYrYSYSSYsYSYSSYtYSYSSYuYSYSSYvYSYSSYwYSYSSYxYSYSSYyYSYSSYzYSYSSY{YSYSSY|YSYSSY}YSYSSY~YSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSY SSYY SY SSYY SY SSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYY SY!SSYY"SY#SSYY$SY%SSYY&SY'SSYY(SY)SSYY*SY+SSYY,SY SSYY-SY.SSYY/SY0SSYY1SY2SSYY3SY4SSYY5SY6SSYY7SY8SSYY9SY:SSYY;SYSSYY?SY@SSYYASYBSSYYCSYDSSYYESYFSSYYGSYHSSYYISYJSSYYKSYSSYYLSYMSSYYNSYOSSYYPSYQSSYYRSYSSSYYTSYUSSYYVSYWSSYYXSYYSSYYZSY[SSYY\SY]SSYY^SY_SSYY`SYaSSYYbSYcSSYYdSYeSSYYfSYgSSYYhSYiSSYYjSYkSSYYlSYmSSYYnSYoSSYYpSYqSSYYrSYsSSYYtSYuSSYYvSYwSSYYxSYySSYYzSY{SSYY|SY}SSYY~SYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYGSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSSYYSYSS