You are on page 1of 40

ADVANCED SUPPLY CHAIN PLANNING Troubleshooting Guide

Author: Creation Date: Last Updated: Control Number: Version:

Oracle Advanced Planning Development July 21, 2000 March 13, 2002 ascp_troubleshootingguide_v18_13mar02.doc 1.8

NOTE: The following information is confidential and is for internal use only.

Document Control
Change Record

Date 21-July-00 1-Aug-00 2-Aug-00 15-Aug-00 04-Apr-01 07-Nov-01 13-Feb-02 28-Feb-02 13-Mar-02

Author Sophia Lee Sophia Lee Sophia Lee Sophia Lee Jignesh Mehta Francois Gerbaux Sam Tupe Moshin Lee Francois Gerbaux

Version 1.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8

Change Reference No previous document Added Sridhar L and Sridhar H. comments on format Added HLS Error Messages, Sridhar L. and Sam Tupe’s edits Added UI Technology Notes from Jignesh Mehta and PWB tips Added TCF Server Administration guide Updated planning engine section for scheduler Updating release issus across operating units Minor wording edits Updated scheduler section for patchset G

Reviewers

Name Sridhar Lakshminarayanan Sridhar Hoskote Paul Dominic Scott Malcolm Shailesh Kumar

Team and Position Planning - Development Manager Planning - QA Manager Planning - QA Manager Planning - Group Manager Planning UI/ATP Development Manager

Contributors

Name Sridhar Lakshminarayanan Sridhar Hoskote Paul Dominic Scott Malcolm Sam Tupe Mukundan Srinivasan Francois Gerbaux Jerome Levadoux Murari Ram Jignesh Mehta

Team and Position Planning - Development Manager Planning - QA Manager Planning - QA Manager Planning - Group Manager Planning - Sr. Project Lead Planning - Project Lead Planning - Development manager Planning - Sr. Application Engineer Planning - Sr. QA Analyst Planning/ATP Sr. Applications Engineer

Document Control Ascp_troubleshootingguide_v18_13mar02.doc Oracle/Client Confidential - For internal use only

ii

Contents

Document Control.............................................................................................................................ii General Guideline ............................................................................................................................. 1 Instances Setup ................................................................................................................................. 2 Source & Destination Relationship............................................................................................ 2 Partitions........................................................................................................................................... 3 Creating Partitions … ................................................................................................................ 3 Collections ........................................................................................................................................ 4 Problem Accessing Forms from the Navigator with ASCP Responsibility …........................... 4 Collections Program Failed / Exited with Fatal Error …........................................................... 4 Collections Program Finished with Warning … ........................................................................ 4 Collections Program Setup ........................................................................................................ 4 SNP: Snapshots on Source Instance: APS Source Snapshot Diagnostics .................................. 5 User Interface Technology................................................................................................................ 6 Workflow and Java Bean Technology within APS.................................................................... 6 Gantt Chart ................................................................................................................................ 6 Horizontal Plan .......................................................................................................................... 7 Perspectives Chart ..................................................................................................................... 7 Deployment................................................................................................................................ 8 Planner Workbench Tips ........................................................................................................... 8 UI Technology FAQs................................................................................................................. 9 Planning Engine .............................................................................................................................. 10 Debugging Procedures............................................................................................................. 10
Debug mode..................................................................................................................................... 10 Signals 6, 10, 11, 113, etc…............................................................................................................ 10 Generating data files ........................................................................................................................ 10 Generating data files - alternative procedure 1 ................................................................................ 11 Generating data files - alternative procedure 2 ................................................................................ 11

Plan Failed / Exited with Fatal Error … .................................................................................. 12
Total cycle time of the demands ...................................................................................................... 12 Arithmetic overflow when using large integer factor....................................................................... 12 Setup of aggregate resources in the routings ................................................................................... 13 Network flow is incomplete............................................................................................................. 13 Maximum energy overflow.............................................................................................................. 14 Maximum activity duration ............................................................................................................. 14 Overflow on granularity precision and maximum activity duration ................................................ 14 Manager saved solution ................................................................................................................... 15 Running Plans Concurrently:........................................................................................................... 15 Collection Running: ........................................................................................................................ 15 Error Message: “CPLEX Error 32011: Licensing Problem: corrupted or nonexistent license file” -15 Make sure to set MSC:HOUR_UOM to “HR” in Profile Options. ................................................. 15 Make sure to set “Retain dates within calendar boundary” to “Yes” in Profile Options. ................ 16 Make sure UOM - Referential Integrity........................................................................................... 16
Document Control Ascp_troubleshootingguide_v18_13mar02.doc Oracle/Client Confidential - For internal use only iii

Make sure Unit# - Referential Integrity........................................................................................... 16

Plan Finished with Warning …................................................................................................ 16
Incorrect setup for alternates and simultaneous............................................................................... 16

Incorrect results ....................................................................................................................... 16
Orders are being pushed out of the planning horizon ...................................................................... 16 Orders scheduled earlier than their due date.................................................................................... 17 Requirements are scheduled out of shifts ........................................................................................ 17 Orders are late.................................................................................................................................. 17

Plan Hanging / Poor Performance …....................................................................................... 18 Patch Application Issues.......................................................................................................... 18
ILOG Planner library patch not applied .......................................................................................... 18 Failure to relink MSONEW............................................................................................................. 18 Patch 1988819 ................................................................................................................................. 19 Patch 1638977 (or 1645431 for NT) ............................................................................................... 19 Patch 1851016 for HP only ............................................................................................................. 20

Autorelease/Release Issues with Operating Units ........................................................................... 21 TCF Server Administration............................................................................................................. 23

ServerControl Usage............................................................................................................. 23 Starting a TCF Server........................................................................................................... 24 ServerControl vs SocketServer........................................................................................ 24 Checking the Status of a TCF Server ........................................................................... 25 Shutting Down a TCF Server ........................................................................................... 25 Updating a TCF Server........................................................................................................ 26 TCF Configuration Options .............................................................................................. 27 Troubleshooting the TCF server ..................................................................................... 30
Appendix A: Primary and Alternate Resource Setup...................................................................... 34 Appendix B: Online Planning - Simulation Options ....................................................................... 36

Document Control Ascp_troubleshootingguide_v18_13mar02.doc Oracle/Client Confidential - For internal use only

iv

doc Oracle/Client Confidential . Turn Debug on Rerun the Plan Use error information in log file to resolve issues General Guideline Ascp_troubleshootingguide_v18_13mar02.For internal use only 1 . 2.General Guideline When an error occurs. do the following to get a more descriptive log file: 1. 3.

doc Oracle/Client Confidential . Instances Setup Ascp_troubleshootingguide_v18_13mar02. On the other hand. each destination instance can collect from multiple source instances.For internal use only 2 . Source & Destination Relationship · Each source instance can be planned with only one destination.Instances Setup This section covers instances related setup.

· The following Technical Note available from Metalink provides a detailed explanation on Partition Management in APS: 137293. This profile option should be set to No for production use.1 Partitions Ascp_troubleshootingguide_v18_13mar02.doc Oracle/Client Confidential .Partitions This section covers questions pertaining to APS partitions. Creating Partitions … · When do I use the concurrent program “Create APS Partitions”? You need to run the "Create APS Partitions" concurrent program to create partitions before you can create and run a plan. then the "number of plan partitions" parameter to the concurrent program mentioned above becomes irrelevant. you need to run the“Create APS Partitions” concurrent program afterwards so that it can create the partition that every plan will share. “Number of Instance Partitions” should be set to the number of source instances you will be collecting from.For internal use only 3 . · What is the purpose of the profile option "MSC:Share Plan Partitions"? The profile option "Share MSC Partitions" was added as a workaround for test/demo scenarios where you expect a lot of plans to be created by different testers and demoers. NOTE: If the “MSC:Share Plan Partitions” profile is set to Yes. since we only create one partition for plans (you can enter “1” just to be safe). If you do decide to enable it.

Problem Accessing Forms from the Navigator with ASCP Responsibility … · FRM-41830: List of values contains no entries: You need to run collections before you can access the forms on ASCP. In this case. Collections Program Setup · Make sure that every parameter is set to “Yes” in Complete Refresh unless you want to wipe off some data intentionally. Þ Make sure the corresponding profile is corrected to point to the right descriptive flex. Make sure to set the profile option MRP_Cutoff_Offset_Months in the destination to cover your planning period. Þ Correct the flex. However.Unique constraint violated for operation_resource_seq” Ignore this warning. it will fail due unmatched user names. if you set BOM:No. if someone other than you ran a manual Refresh Snapshot in the source instance the last time. make sure you validate that the APS Flex Fields Profile Options are actually pointing to unused flex columns. and then you try to run Collections. it will not affect the plan in any way. all BOM data previously collected will be purged. To correct this: Þ Determine which attribute column is the problem. For example. Collections Program Failed / Exited with Fatal Error … · Failed in Data Pull: Invalid num type/data type . · Collections Program Finished with Warning … · Warning Message: “Warning . · Failed in Refresh Snapshot: The collections program has a built-in Source Refresh Snapshot function.You have mismatched data types between your Source and Destination (Planning).doc Oracle/Client Confidential . Collections Ascp_troubleshootingguide_v18_13mar02. This failure in Data Pull could be a result of using a descriptive flex which was already used or has incorrect values.Collections This section contains troubleshooting recommendations for the collections process.For internal use only 4 .

137491.doc Oracle/Client Confidential . however.. Collection Workbench) prior to launching plans.· Supplier Capacity cannot be set up in source and collected to destination (planner server) if you are running a 10.1 explains the use and maintenance of Snapshots and Snapshots logs related to APS. SNP: Snapshots on Source Instance: APS Source Snapshot Diagnostics Metalink Note.For internal use only 5 . It.7 or 11 source instance. can be set up in your destination (i.e. Collections Ascp_troubleshootingguide_v18_13mar02.

doc Oracle/Client Confidential . Gantt Chart. Deployment. designed to have an applet running inside it. this new element also makes it possible to add Java beans into WebForms.0. Horizontal Plan. Perspectives Chart.0. the following user changes are supported: · Supply. Forms 6i Technology. BeanArea is only functional in WebForms. After the user makes changes in the Gantt chart view. During on-line planning. It is intended to replace the 'userarea' element that has been used in Forms4. and FAQ. The following diagram displays different Java modules within APS. The Gantt Chart has been implemented as Java bean within a form which can be used to view activities in a resource-centric or order-centric fashion. User Interface Technology Ascp_troubleshootingguide_v18_13mar02. A beanarea is a visible UI element inside a form. You can also have a beanarea that is designed to manage and manipulate multiple applets that run in their own separate frames. Workflow and Java Bean Technology within APS BeanArea is a new element in Forms6. APS User Interface Java beans Gantt Chart Horizontal Plan Perspectives Chart Gantt Chart 1.5. Please also note that: 1.User Interface Technology This section contains troubleshooting tips for the ASCP User Interface (UI). BeanArea is only available and functional in Forms6.For internal use only 6 . 2. In addition to the existing support of java applets with userarea in Forms4. Specific topics including Workflow and Java Bean Technology within APS.5. we issue a re-plan.

The APS Gantt chart customizations reside in the mscjar. The horizontal plan is useful for viewing data in a combination of levels of time buckets (day. Demand.jar fndewt. The horizontal plan has been implemented as Java bean within a form. The Gantt Chart is available from the Planner Workbench. Horizontal Plan 1. 4.jar (ewttdg. The horizontal plan bean is a customization of the Java component called PivotTable developed by the Bali group at Oracle.jar file. Resource Availability. 2. period).jar fndewt. Gantt Chart technology is based on the Java component provided by AOL which is called FNDGANTT. The horizontal plan is viewable from the Planner Workbench. Supplier capacity.5) 3. Resource Requirements. Hence.jar fndtdg. fndswing. week.jar fndjle.· · · · 2.jar 3.doc Oracle/Client Confidential . the APS Gantt chart depends on the following FND jar files: · · · · · fndgantt.jar from 11.jar fndpromise.jar fndewtpv. 2. the Resource Horizontal Plan. Perspectives for Java is a charting tool used to draw different type of charts in the Planner Workbench. Perspectives Chart 1. It can be used to view the Material Horizontal Plan.jar file and is depends on the following FND jar files: · · · · 4. Charts are available in the Planner Workbench for following views: User Interface Technology Ascp_troubleshootingguide_v18_13mar02. and the Supplier Horizontal Plan.5.jar fndswing. APS Horizontal plan bean resides in the mscjar.For internal use only 7 .

They are hence deployed as jar files on the client. Jar file source location: · · 3. Runtime location of jar files: · · All FND jar files are located under /OA_JAVA/oracle/apps/fnd/jar/ All APS jar files are located under /OA_JAVA/oracle/apps/msc/jar/ Planner Workbench Tips · User-Defined PWB: You can navigate to Tools/Preferences/Other to set up your default display/preferences. Jar file loading is very fast compared to the loading of Java classes themselves. Resources. All WebForms (Forms6i) have been implemented as Java layers. All FND jar files are located under $FND_TOP/java/jar/ All APS jar files are located under $MSC_TOP/java/jar/ 2. Horizontal Plan. Vertical Plan Actions The FND jar file fndtdg. Actions. Inventory.g. APS charts reside in mscjar.jar Deployment 1. Organizations.jar is required for APS charts. Product Family) Þ Snapshot Start Date/Time Þ Plan Start Date/Time Þ View Recommendations for (Days from Today) Þ Default Left Tab (Actions.For internal use only 8 .· · · · 3. Key Performance Indicators (KPIs). Projects) Þ Default Right Tab (Key Indicators. Supply Chain) User Interface Technology Ascp_troubleshootingguide_v18_13mar02.doc Oracle/Client Confidential . Items.. You have the following options: Þ Category Set (e. 4.

Causes/Resolution Actions: Þ If you are launching the workbench for the first time after applying any patch or after bringing up the environment. Make sure all of your database objects are valid. Þ Null pointer exceptions: · · For the horizontal plan. · · Problem: Java exception. Þ In most Java exceptions. · Causes/Resolution Actions: Þ Make sure the profile values for TCF. For example. Þ Make sure MSC tables are analyzed. Þ Class verify error: Ask FND to provide the correct version of jar files.For internal use only 9 . Þ Make sure jar files are placed in the correct directory for the run time environment as mentioned above. apply this setting. It is most likely a forms bug or error. Þ Forms 6i is a web form technology.UI Technology FAQs · Problem: After selecting a node on the left panel of the planner workbench. User Interface Technology Ascp_troubleshootingguide_v18_13mar02. This may not mean that there is anything wrong with Java. Causes/Resolution Actions: Þ Security exception when you log in: Make sure your Jinitiator's Applet access is set to unrestricted.doc Oracle/Client Confidential . This happens only at the first launch of the workbench. workbench performance is very slow. Please see the TCF Administration section of this guide. it is very helpful to have information on Jinitiator’s Java console as well as information within the relevant log file. In such cases. the application will load the new jar files which may cause some delay in displaying the workbench. the right panel of the workbench does not show anything (blank screen). If there is anything wrong at the form level. set access to unrestricted. make sure that you have selected at least one order type to be displayed in the Preferences window. Problem: TCF connection fails. you will see a Java error message. it you should check the TCF log file as well as the Jinitiator Java console. if there is a TCF issue. Alternatively. and open Oracle Applications again. close all of your browser windows. It is very important to ascertain the exact navigation that results in the error. TCF:HOST and TCF:PORT are set correctly. open the Jinitiator control panel. All forms are laid out using Java.

For internal use only 10 . please set the profile option MRP_DEBUG to Yes. There will not be any error message.doc Oracle/Client Confidential . For example: HLSDriver::readIntraSupplyTransfers Could not find dest operation for network flow transfer transaction id: 1790602 . instance id: 21 . For Scheduler issues. signal 10 is in general caused by some corruption of the executable. Note 4: do not confuse these files by the "snapshot files" generated by the snapshot process.Planning Engine This section contains troubleshooting tips for the ASCP in-memory planning engine. 11. etc… The signals reported by the UI are actually operating system messages. Several different errors could result in the same signal. Signal 6 and 11 On Unix signal 6 and 11. To turn on the debug mode." is printed in the log file. Note 3: It is possible for the scheduler to fail even before generating these files. Please contact development to resolve these. There will always be a message in the log describing the error condition. Note 2: These files will be overwritten every time a plan is run. they are necessary to figure out most problems. This information is in general necessary for debugging. Note 1: These files are not generated for unconstrained plans (since the scheduler is not used). So you should make sure that plans will not be run in your environment while you generate these files. Signal 113 This type of signal happens in general in the scheduler. routing sequence id: 46806 Signal 10 On Unix.. Generating data files The APS planning engine can generate scheduler data files that allows developers to have a complete view of the data used. it is important to report where the failure is happening as indicated by the log file. Debugging Procedures Debug mode The planning engine will print more information in the log when the debug mode is turned on. It may be worth trying to re-link MSONEW. to op seq num: 30 . 113. Planning Engine Ascp_troubleshootingguide_v18_13mar02. op seq num: 20 . The files have been generated if the string: "> Writing files. 10. are unexpected errors.. if you get this error. Signals 6. supply id: 1790602 . Because of this.

Assuming that you have run the snapshot already (which should be the case). This is done either with setenv FDWHOAMI 0.create a directory with write permission. For example: /home/fgerbaux/data 3 .704.Make sure that permissions are available to write in this directory: chmod 777 data 3 .20454 or FDWHOAMI=0.out files in the directory Generating data files . if any. It can also be $APPL_TOP/log. For example: apps/apps@apsdev Planning Engine Ascp_troubleshootingguide_v18_13mar02.For internal use only 11 . 2 . create a subdirectory "data" with write permission. and can read the snapshot files.704. the engine will print a directory "data" located in the log directory. This will write .out files in the directory.704. or $MSO_TOP/log. Generating data files .Set the environment variable FDWHOAMI to "0.dat. 2 . On Unix systems it is as follows: 1 . So you can also apply the following procedure.dat.In order to generate these files. and .alternative procedure 2 You can also generate the data files by running the planner directly from command line. you can directly run the memory based planner using: $MSO_TOP/bin/MSONEW <connect string> 0 Y -d -t <plan_id> (this is 0=zero) <connect string> is the string you would use to connect to the database with sqlplus.In any directory in which you have write permission.set the profile option: "MSO: HLS flat files path" to the complete path of this directory. (do not cd into this directory) 3 . 1 .doc Oracle/Client Confidential .Run the plan.alternative procedure 1 If the profile option "MSO: HLS flat files path" is not set (null).Run the plan. This procedure is slightly more complicated.20454". This will write . and .20454 export FDWHOAMI depending on your shell. on a drive visible by the concurrent manager: mkdir data chmod 777 data 2 .Create a subdirectory called "data" in the log directory. The log directory is in general $APPLCSF/log. please use the following procedure: 1 .

.000. The limitation is that the largest supply quantity for a buy item multiplied by the floating point precision should be less than 1.0004 = 4 is an integer..5.01 for a resource would in effect multiply the requirement on this resource by 10. This may be due to an error in setting up a routing (with. [0. and cause an overflow. Plan Failed / Exited with Fatal Error … Total cycle time of the demands Messages: "Could not cancel the slacks for demand xxx.000!. For example. The supplier capacity and the usage for resource requirements are converted to integer using this factor. For example: if you have a usage of 0.000 (1 billion).000.0004. for example.' The program should write data files into the sub directory data.<plan_id> is the id of your plan.. Arithmetic overflow when using large integer factor "Solver Error : IlcAddI : overflow at creation of expression : [0. Planning Engine Ascp_troubleshootingguide_v18_13mar02.000.doc Oracle/Client Confidential . The scheduler will convert some of the floating point numbers to integers using an "integer factor" as defined by the profile "MSO: Floating Point Precision". so that 10000 * 0.0/bin/MSONEW Program was terminated by signal 6" This error is caused by an arithmetic overflow in the scheduler. Please check that resource requirements are not longer than 2 horizons" "Scheduling forward failed for demand xxx" "Could not calculate exceptions for demand xxx" "Lead time is greater than the scheduling horizon" These messages are usually due to some very large cycle times. But the duration may also be spread across several requirements. your plan name .2104000000]. However if you have a supply quantity of 1. which can be found in the first lines of the log file.000 it will be multiplied by the same factor. The resource efficiency and utilization factors are used to inflate resource requirements and may also cause this problem.. you should use a floating point precision of 10000.. The general limitation is that the complete cycle time of the unconstrained plan should be no more than 20 years in duration. setting both parameters to 0.2104000000] /opt/oracle/apps/PBS1/mso/11. a very large usage for one requirement)..For internal use only 12 . Or you can select it in the database by: select plan_id from msc_plans where compile_designator='.

the "schedule flag" for the requirements in this operation (30) are all NO. Aggregate resources in routings is not supported by ASCP. If you have some effectivity set for operations."MSO: Floating Point Precision for Transportation Capacities (Volume)" Setup of aggregate resources in the routings Message: “ ### Warning: resouce <resource id> dept <department id> used in routing does not exist. routing sequence id: 46806 This is caused by an incomplete network routing. This problem is solved in patchset F with the patch 2021411 by adding separate profile options for each use of the floating point precision. it may be that there is no operation 30 effective at the time considered.there may be some effectivity problem. You have defined arcs in your network for which there is no corresponding operation. In the above example: there is an arc from operation 20 to operation 30. Effectivity should not disable any operations is the network. With patchset E. op seq num: 20 . This means that the operation is not scheduled."MSO: Floating Point Precision for Usages in Routings" . consider the following possible causes: . which in turn means a loss of precision for very small number such as routing usages.This problem will happen on 32 bit platforms only. but operation 30 is not found.doc Oracle/Client Confidential . Network flow is incomplete Fatal error. so the scheduler does not see it. aborting HLSDriver::readIntraSupplyTransfers Could not find dest operation for network flow transfer transaction id: 1790602 .For internal use only 13 . was an aggregate resource used in a routing? Make sure you use only individual resources in routings. to op seq num: 30 . There should be at least one scheduled requirement in the operation. The limit for 64-bit platforms is an extremely large number. supply id: 1790602 . If you checked your network definition and it is complete (operation 30 exists)."MSO: Floating Point Precision for Transportation Capacities (Weight)" ."MSO: floating Point Precision" (is still used for the size of supplies for buy items) . Planning Engine Ascp_troubleshootingguide_v18_13mar02.” Did you use aggregate resource(s) in your plan? If you did. instance id: 21 . you may have to diminish your floating point precision. . .” Or “ ### Error: <resource Id> dept <department id> used in requirement was not read.

000. or the efficiency/utilization of the resource.For internal use only 14 . The default value is the duration of the planning horizon. multiplied by the capacity of your resource should not exceed a value which depend of your platform.000 when using period buckets. Usually this failure is due to some error in setting up the routing.000 * 43. The limitation is as follow: the maximum size of a time bucket (defined in plan options). Overflow on granularity precision and maximum activity duration Fatal error.000 will exceed the limit. Deparement Id.000. For 32 bit platforms this value is 1073741822. aborting createEnergyTimeTableMinuteTimeStep Maximum energy overflow resource: 960 62 1 capacity = 2147483647 > max energy per bucket = 1073741822 This is indicates that you have exceeded the maximum capacity possible for a resource. aborting HLS Resource Load Compute Min Duration Maximum activity duration of 6935 days exceeded.Maximum energy overflow Fatal error. In practice the maximum resource capacity for 32 bit platforms is about 20.doc Oracle/Client Confidential . and you are planning with period buckets (30 days = 43200 minutes). Instance Id): 11110 50 1 Routing: (inventory item id)39789 Organization Id: 111 Operation Sequence: 20 Resource Sequence: 10 Activity Duration (hours): 756000 Quantity: 4500 Resource Usuage (min): 10080 Basis Type: 1 Rounding Control Type: 1 Routing Type: 2 Max Capacity consumed: 1 Resource efficiency: 1 Resource utilization: 1 Patchset G defines a new profile option: "MSO: Maximum Activity Duration". aborting HLSDriver::readParameters ### Error: the product of maximum activity duration (in minutes) 43200 and granular precision 1000000 exceeds the maxmimum integer number 2147483647 for this platform please either reduce the number in profile option MSO: Maximum Activity duration/(planning horizon) Or decrease the number in MSO: HLS Granular precision Planning Engine Ascp_troubleshootingguide_v18_13mar02. For 64bit platforms the value is extremely large. The plan will fail with this message if one activity (resource requirement) exceeds the duration defined by this profile. Maximum activity duration Fatal error. in minute.000. Resource (Resource Id. the product of 1. For example: if you have a resource with a capacity of 1.

Running Plans Concurrently: Were you running the same plan twice? Or. however. You cannot have two concurrent runs of the same plan. Check which directory this file is pointing to. etc… There is a limit on this precision defined by the following rule: The granularity precision multiplied by the maximum activity duration should be less than 2 billions on 32 bits platforms.ptr TDB8DD5/ (this file name might be different depending on the customer. since G requires a more recent version of the libraries. Collection Running: Is someone running a complete refresh collection? The plan cannot be launched while collection program is running. You will get this error if you violate this rule. somebody else might be running your plan while you are also running it. The first plan will not be affected.perms T.0001. This should not happen on patchset G. The second plan run will result in failure immediately. A value of 1000 means you will consider a precision of 1/1000. Make sure this directory contains the following three files: . This could result in unique constraint violations.doc Oracle/Client Confidential . Manager saved solution Message: "Could not restore manager saved solution" Please apply patch 1988819 for an update of the ILOG Scheduler library.Patchset G defines the new profile option "MSO: HLS Granularity Precision". it will be a file starting with a capital T.For internal use only 15 .) Make sure to set MSC:HOUR_UOM to “HR” in Profile Options. 10. Please read the patching section below for details on this patch. This number defines the number of the resource hours (processing time) for requirements. Error Message: “CPLEX Error 32011: Licensing Problem: corrupted or nonexistent license file” You need to: Verify the license file -> environment variable (APPL_CPLEX_LICDIR) is defined.000 a precision of 0. Planning Engine Ascp_troubleshootingguide_v18_13mar02.

and some of the requirement can not be executed in 1 shift. HLS will attempt to repair the setup by changing the status of resources from simultaneous to principal as needed. res seq num yy. This limitation is removed in patchset G. alternate number zz These messages are related to the setup of principal resources in the definition of a routing. WARNING . Incorrect results Orders are being pushed out of the planning horizon Note: When one order is being pushed out to the end of the (constrained) horizon: all downstream orders will also be pushed out. It is recommended that the setup is fixed to avoid such messages. There are xxx simultaneous resources with no principal. Make sure UOM . APS will be unable to schedule such requirements before the end of the (constrained) horizon.Referential Integrity.Make sure to set “Retain dates within calendar boundary” to “Yes” in Profile Options. There should be one and only one principal resource for a replacement group of an operation resource.doc Oracle/Client Confidential . Schedule Across Breaks parameter If set to No. Planning Engine Ascp_troubleshootingguide_v18_13mar02. you need to schedule in minutes for the corresponding horizon. For example from 8:00 to 17:00. This is a limitation of APS before G. Will use simultaneous. However this may cause some other problems in your setup. Make sure Unit# . Plan Finished with Warning … Incorrect setup for alternates and simultaneous. This is because orders are scheduled just in time when they are needed.Referential Integrity. Shifts are round hours Please check that resources shift are defined as round hours. WARNING.For internal use only 16 . In general "schedule across break" should be set to Yes. If you need to define more precise shifts. but also. ## Warning: multiple principal resources for item xxx. all upstream orders.Fixing principal operation resource for operation id xx. and not from 8:30 to 17:15.

Orders are late There are several potential causes that need to be checked: Upstream or downstream orders are overloading a resource When one order is late: all downstream orders will also be late. To avoid this issue. Requirements are scheduled out of shifts This is possible in patchset G as the scheduler does not look at the exact position of breaks inside a time bucket. This is because orders are scheduled just in time when they are needed. please apply patch 1988819 as described later in this document. . Planning Engine Ascp_troubleshootingguide_v18_13mar02. If a better precision is needed. This may result in supplies which are earlier than their demand. in order to respect both due dates. Orders scheduled earlier than their due date This can happen for 2 reasons: . So some supplies may be scheduled earlier than their due dates in order to respect resource availability.Supply schedule Because of supply schedules. the scheduler will not look at the position of breaks within one day. it will be scheduled for the earliest of the demand if possible.The first availability of a required resource is early compared to the due date. it is always possible to define plan options with finer time buckets. Planning Time Fence Using the planning time fence will prevent new planned orders to be scheduled too early in the schedule. This could cause some orders to be late. then the corresponding operation may get pushed out. ILOG propagation error One particular bug from the ILOG library would cause some supplies to be incorrectly pushed out.doc Oracle/Client Confidential . The problem is data dependent. it is possible that not enough components are produced for a particular assembly (unmet demand). So a requirement of 3 hours on that day will become a requirement of 6 hours. but also. and cannot be linked to any specific functional situation. or 2 simultaneous in the same resource group use the same resource. For example if you have daily buckets and shifts from 6:00 to 18:00 (12 hours). all upstream orders. Instead the scheduler will inflate the duration of requirements to account for the breaks within a bucket. but it may be scheduled from 0:00 to 6:00. In this case the corresponding order will be pushed out by APS. Instead it will assume that the time during this day is 50% efficient only (12/24). Simultaneous is also the principal resource If you set up a routing so that a simultaneous operation resource requires the same resource as its principal.For internal use only 17 .If a supply is pegged to 2 demands.

Failure to relink MSONEW "ld: 0711-317 ERROR: Undefined symbol: . If you get this error please apply patch 1638977 (or 1645431 for NT). Please read the patching section below for details on this patch. Profile options don’t cause the plan to fail. Plan Hanging / Poor Performance … · Snapshot is Hanging: You could run “Gather Schema Statistics” with: Þ Schemaname= “MSC“ Þ Estimate_percent = “10” (default value) Þ Degree = “4” Þ Internal Flag = “NOBACKUP” (default value) Gather Schema Statistics” is not necessary after net change collections. Þ Use aggregated time bucket in Plan Options to improve the performance. · Conflicts: There could be conflicts due to: Þ Snapshot with itself . Patch Application Issues ILOG Planner library patch not applied __0fJIlcLinOptOnetworkDualOptvK /release/fnd115/v1154upg/mso/11.a(msohdtrd.o) The patch application will fail to relink executable MSONEW because of the absence of the Ilog Planner library (one of the 3rd party libraries used by ASCP).two snapshots cannot be run at the same time.HLSMathDurableModel::getIntegerFactor()" Planning Engine Ascp_troubleshootingguide_v18_13mar02.For internal use only 18 .a(msohmnfl.o) __0FYIlcLinearRegisterLicensePCci /release/fnd115/v1154upg/mso/11.Preprocessing leadtimes APS will schedule orders so that the order date is in the present. This may cause some orders to be late. It will only slow down the performance.0/lib/libmso.0/lib/libmso.5.doc Oracle/Client Confidential . · Optimized Plan Running: Were you running an Optimized plan? Is Optimizer hanging? You should: Þ Verify the Profile Options to make sure everything is set up correctly.5. It’s recommended to use default value as much as possible. Þ Plan is running while Auto Release Planner Order is also running.

ca" (This bug was actually already fixed in the previous Scheduler library patch 1558791. This patch requires relinking MSONEW after being applied. this problem has been removed after patchset F. Patch 1988819 This patch contains a bug fix version of ILOG Scheduler 4. starting with patch 1645243.o file with the same version. 2002. licensed to "oracle-redwood shores. please make sure that this patch has been applied. but still requires some manual intervention for patchset E. even though the header files are more recent. for example: ILOG Solver 4. ) An other problem fixed was causing some incorrect results with orders being pushed out and some performance problems. for Scheduler4. You may want to come back to the previous version before applying a WPS patch. hence it is very important to make a backup of the .56. ca" ILOG Scheduler 4. One of the problems fixed is a plan failure with status113 with the message: "Could not restore manager saved solution" If you see this message. and including patchset E.sh force=y ranlib=y "mso MSONEW" The log file will show the version of the ILOG libraries. Relinking MSONEW is done using Unix command: $ adrelink. PLEASE DO NOT USE THIS PATCH FOR PATCHSET G OR LATER.sh force=y ranlib=y "mso MSONEW" (or just rerun the adpatch copy driver). This patch is required for APS for all engine patch released after February 21.400. This is a "soft" pre-requisite: this dependency is mentioned in the README of the patch 1645243. Again.doc Oracle/Client Confidential . Patch 1638977 (or 1645431 for NT) This patch contains the new ILOG Planner library. If you are using WPS on the same instance with patchset E: be aware that WPS and MSO are both using the library libmso. This patch can safely be applied to any version of APS before patchset G.o file before copying the new versions from a mso patch. Because of this problem it is highly recommended to always apply this patch.For internal use only 19 . This is caused by adpatch not replacing the . Then run: $ adrelink. There is no clear functional situation in which they always arise.a.560. The bugs fixed are data dependent. This problem has been solved for patchset F.Please make a backup and then manually copy all mso . Planning Engine Ascp_troubleshootingguide_v18_13mar02.55. licensed to "oracle-redwood shores.o files from the msc/mso patch you are trying to apply to your environment.

o) This patch application is manual. This patch is a "soft" pre-requisite: it is only mentioned in the readme of patch 1840749. Planning Engine Ascp_troubleshootingguide_v18_13mar02. please relink MSONEW manually or apply another engine patch.5.For internal use only 20 . The error will mention undefined symbols containing "IlcLin". you will be unable to relink MSONEW. PLEASE DO NOT USE THIS PATCH FOR PATCHSET G OR LATER.doc Oracle/Client Confidential .0/lib/libmso.o) __0FYIlcLinearRegisterLicensePCci /release/fnd115/v1154upg/mso/11. More specifically. adpatch will fail to apply "c" drivers for other engine patches. Patch 1851016 for HP only This is a Rogue Wave library patch for HP only that corrects an issue causing extra memory consumption.a(msohmnfl.0/lib/libmso.a(msohdtrd. After applying this patch. All subsequent engine patches on HP will have as a pre-requisite the application of patch 1851016. For example: __0fJIlcLinOptOnetworkDualOptvK /release/fnd115/v1154upg/mso/11.5. as detailed in the README.If this patch is not applied.

The release process (manual or autorelase) populates the PO_REQUISITIONS_INTERFACE TABLE with the operating unit information.g. Autorelease/Release Issues with Operating Units Ascp_troubleshootingguide_v18_13mar02. 2. Define Advanced Supply Chain Planner OU1 in destination instance d. So . In the source instance. To overcome this issue in the case of Manual Release: 1.. so that the information is picked up from the interface table no matter what. 4. some reqs are populated with OU1 and some are populate as OU2). OR In the source instance .doc Oracle/Client Confidential . both the responsibilities Advanced Supply Chain Planner OU1 and Advanced Supply Chain Planner OU2 will schedule the req import program to run periodically and the information from both the operating units OU1 and OU2 will be processed.. (In this case all the records for OU1 will be imported.g.g. in the case above . because OU1 is attached to the Advanced Supply Chain Planner responsibility) The OU2 operating information will not be processed by the Req Import Program. OU1).g:. It launches the PO REQ Import program on the source instance. Example : SOURCE : USER_A has Advanced Supply Chain Planner OU1 pointing to Operating_unit_1 USER_A has Advanced Supply Chain Planner OU2 pointing to Operating_unit_2 DESTINATION : USER_A has Advanced Supply Chain Planner OU1 USER_A has Advanced Supply Chain Planner OU2 To overcome this issue in the case of Auto-Release: In the source instance . Define Advanced Supply Chain Planner OU2 in destination instance Use the correct responsibility to release planned orders based on the Operating units. so that the information is picked up from the interface table no matter what. This is the same responsibility which did the Manual / Auto release in ASCP. Advanced Supply Chain Planner) is attached to a particular operating unit (e.as many responsibilities as operating units have to be defined in the source and destination. So .. schedule the Req Import Program to run periodically from each of the responsibilities (belonging to different operating units) . Define Advanced Supply Chain Planner OU2 attached to OU2 in source instance c. 3. Define Advanced Supply Chain Planner OU1 attached to OU1 in source instance b. 2. In general . a. schedule the Req Import Program to run periodically from each of the responsibilities (belonging to different operating units) . 3.Autorelease/Release Issues with Operating Units The Release process of Releasing of Purchase Requisitions from ASCP to Purchasing involves passing the operating unit to the po_requisitions_interface. in the case above . The req import program imports all the information from the interface table belonging to the operating unit attached to the responsibility. In case there are two operating units . in case of multiple Operating Units .For internal use only 21 . (e. both the responsibilities Advanced Supply Chain Planner OU1 and Advanced Supply Chain Planner OU2 will schedule the req import program to run periodically and the information from both the operating units OU1 and OU2 will be processed. each responsibility (e. This is done using the Responsibility (e. You will have to define a responsibility in the source which points to the right operating unit and then run Requisition Import using that responsibility. The process is explained as follows : 1. 2. Advanced Supply Chain Planner).

Autorelease/Release Issues with Operating Units Ascp_troubleshootingguide_v18_13mar02.doc Oracle/Client Confidential .For internal use only 22 .

In a production installation.For internal use only 23 .apps>] The DBC parameter is required when passing the START command to the SocketServer.) ServerControl Usage jre oracle.txt LOGLEVEL*=[ERROR|EXCEPTION|EVENT|PROCEDURE|STATEMENT] LOGMODULE*=[<product name>|<oracle.doc Oracle/Client Confidential . embed them in quotes.fnd. if this is not specified you will not be able to see if an error occurs. which basically provides a clean interface around all the different SocketServer functions that an administrator might perform (starting.dbc file you start the server with.TCF Server Administration The TCF (Thin Client Framework) Server is a middle tier process that enables certain Java components of the Oracle Applications user interface to communicate with the middle tier and the database tier. the TCF Server process should always be running.apps.tcf.dbc file and set the TCF:HOST and TCF:PORT profile options accordingly.ServerControl) do not get passed on to the SocketServer process. The ServerControl will connect to the database specified by that .tcf. The SocketServer can run in HTTP or SSL mode by specifying the PROTOCOL argument . it will be able to connect to any database which has a .apps. it is not limited to connecting to only the . It must point to a dbc file located under $FND_TOP/secure. The JRE_PARAMS argument can be used to pass in java runtime parameters to the SocketServer (for a list of available ones.ServerControl [START|STOP|STATUS|UPDATE] <portnumber|default=10021> [<param=value>]* "param=value" parameters include: Default values are highlighted. To pass multiple arguments. etc. Administration of the SocketServer is typically handled through the ServerControl class. the value will default to 10021.dbc DEBUG=[TRUE|FALSE] JRE_PARAMS=<jre parameters> OUTPUTFILE=<output file name> PROTOCOL=[SOCKETS|HTTP|SSL] STOP_MODE=[IMMEDIATE|NORMAL] ENV*=/<env_path>/env. After the server is started up. updating. If the port number is omitted. The terms TCF Server and SocketServer are often used interchangeably.dbc file in the $FND_TOP/secure directory. Note that the normal jre arguments you pass directly in when running the ServerControl (eg jre mx128m oracle. TCF Server Administration Ascp_troubleshootingguide_v18_13mar02. Specify OUTPUT_FILE if you want any log output and error messages to be logged to a file. · · · · · · · · · DBC=$FND_TOP/secure/<dbc_file>.fnd. The DEBUG parameter when set to true will cause a window to pop up listing all the clients that are currently connected to the server.see the section on HTTP and SSL mode for more details. type 'jre-help'). stopping.

However. unlike ServerControl which requires the OUTPUTFILE argument. any JRE parameters can be passed directly into the SocketServer. you might use SocketServer. The . the ServerControl will take care of updating the TCF:HOST and TCF:PORT profiles in the database for you (whatever database is pointed to by the DBC file that is passed in). Environment files should be located under $OA_HTML. Not all environment variables can be passed in from the command line.ServerControl START 10021 .instead of a PROTOCOL argument. as is the ENV parameter when running in SSL mode. to start the TCF Server you need to change to the appropriate environment (typically if you log in as applmgr this will alread be set) and run the ServerControl with the START command: jre oracle.SocketServer 10021 .STOP_MODE is used only when stopping a TCF Server.apps. After logging onto the forms server. see the section on shutting down a SocketServer for more details. and sometimes support may find it more convenient to have users start the SocketServer directly when encountering problems.tcf. as it needs to pass in some additional arguments. however. TCF Server Administration Ascp_troubleshootingguide_v18_13mar02. it uses the flags "-h" and "-ssl" for HTTP mode and SSL mode respectively. The ENV parameter can be used to pass in environment variables and values for all of the above arguments. Plus. name=value pairs on each line. updating. The SocketServer class takes slightly different arguments .zip and jdbc111. no whitespace). if you for some reason did not want the TCF:HOST and TCF:PORT profiles updated. so the JRE_PARAMS arg is not required. See the generic AOL logging doc for more details on these parameters. The DBC parameter is required.fnd. we now require that the TCF Server be started on the same machine as the forms server. the TCF Server could be started on any machine.zip files should have been installed under your $JAVA_TOP. The environment should contain.fnd. SocketServer does print debugging output directly to the window it was started in.doc Oracle/Client Confidential .tcf. If an argument is passed in both the environment file and on the command line..apps. Starting a TCF Server In previous versions of 11i. Examples are given below. LOGLEVEL and LOGMODULE can be set to vary the number of log messages that will appear (should be used in conjunction with OUTPUTFILE). the command line argument will be override the environment file. among other things. It uses the flag "-d" instead of the DEBUG argument. It is also possible to pass in environment variables using java '-D' flag. An environment file is required when starting the server in SSL mode. etc) that the ServerControl can.5. The default is to print out errors and exceptions. Beginning with 11.zip files included in the CLASSPATH. plus the SocketServer cannot be used to perform any of the other administrative functions (stopping. Additionally. This requirement is necessary to support SSL mode.For internal use only 24 . by pointing it to a text file containing the arguments above in the format of a java Properties file (roughly. the java runtime engine.. And unlike with ServerControl. but using an environment file is cleaner. The ServerControl in START mode can take every parameter listed above with the exception of 'STOP_MODE'. and the apps. The differences in the arguments taken can be confusing and in general ServerControl is used more frequently because it provides a cleaner interface towards starting the SocketServer. for all modules. ServerControl vs SocketServer You can also start a SocketServer using the SocketServer class directly: jre oracle.2.

we in general recommend that ServerControl always be used unless you have a specific reason to call SocketServer directly.dbc' file to point to this SocketServer. Database downtime will not generally require the TCF Server to be restarted.tcf.fnd. which uses TCF. Find All) and press the View Tree button in the upper right corner .apps. Comments The TCF Server will need to be restarted any time patches are applied which modify Java code. even STATEMENT's.dbc This will start a TCF Server listening at port 10021 in sockets mode. but restarting TCF as part of a general purpose 'Restart the system' script would be a good administrative practice.tcf. ServerControl and SocketServer are two classes which provide the same functionality when it comes to starting a SocketServer (in fact.tcf.ServerControl START 10021 DBC=$FND_TOP/secure/host_dbname.fnd.tcf. The simplest policy would be to restart TCF Server after completion of any patch. eg: jre oracle.dbc JRE_PARAMS="-ms128m -mx128m" This will start up the TCF Server with 128megs of stack and heap space.fnd. Shutting Down a TCF Server Login to your TCF Server machine and type: TCF Server Administration Ascp_troubleshootingguide_v18_13mar02. Examples jre oracle.apps.doc Oracle/Client Confidential . and will update the site-level profiles TCF:HOST and TCF:PORT in the database specified in the 'host_dbname. Checking the Status of a TCF Server Login to your TCF Server machine and type: jre oracle. Query up any records (eg. When running in HTTP or SSL mode.fnd.txt'. jre oracle.ServerControl STATUS 10021 This should return a list of all open connections to the TCF Server (including the one you're making now to check the status).tcf.ServerControl START 10021 DBC=$FND_TOP/secure/host_dbname.apps. to the file 'tcflog.ServerControl START 10021 DBC=$FND_TOP/secure/host_dbname. simpler interface.fnd.For internal use only 25 .apps. and will update the site-level profiles TCF:HOST and TCF:PORT accordingly. To provide a cleaner.txt LOGLEVEL=STATEMENT This will start a TCF Server listening at port 10021 in HTTP mode. ServerControl ends up calling SocketServer).apps. Sign onto apps as the System Administrator and navigate to the Define Menus form (try Application->Menus). though.the Menu Viewer screen should appear.Essentially. be sure to specify the appropriate PROTOCOL argument.dbc PROTOCOL=HTTP OUTPUTFILE=tcflog. jre oracle. It will also output all log messages.ServerControl STATUS 10021 PROTOCOL=HTTP Another more advanced test you can run is to try running the Function Security Menu Viewer application.

not just the default of errors and exceptions.fnd. ie and OUTPUTFILE should have been specified).fnd.jre oracle.5.tcf.ServerControl UPDATE 10021 PROTOCOL=HTTP GET=JDBC will connect to a SocketServer running in HTTP mode and output to your log file how many JDBC connections are currently in the pool. Currently. Again.apps. But note that this is a very imprecise metric. GET=JDBC will output the current state of the JDBC connection pool in use to the log file (logging must be turned on.fnd. be sure to specify the appropriate PROTOCOL argument.ServerControl STOP 10021 Because the TCF Server may have active client connections in progress. these include the following: · · · LOGLEVEL=[ERROR|EXCEPTION|EVENT|PROCEDURE|STATEMENT] LOGMODULE=[<product name>|<oracle.For internal use only 26 . Support may request this info if a customer is encountering problems. while running a SocketServer. GET=VERSION will return the java revisions of any class files that have been currently loaded. It should never be relied upon for accurate results. jre oracle. in bytes.apps.doc Oracle/Client Confidential .2.5.ServerControl UPDATE 10021 LOGLEVEL=STATEMENT LOGMODULE=oracle.tcf will set your logging level to log all levels of messages.tcf. there are two options for shutdown mode: STOP_MODE=[IMMEDIATE|NORMAL] NORMAL mode causes TCF to refuse additional connections and shutdown when the last active connection closes. only used as a guideline.apps.apps>] GET=[MEMORY|JDBC|VERSION] The LOGLEVEL and LOGMODULE properties are the same as those which you set when starting the server. but here you can set them dynamically. The GET call can be used to query up certain bits of information about the SocketServer's current status: GET=MEMORY will return the current amount of memory in use and how much the JVM says is available. when running in HTTP or SSL mode. etc.fnd. as it relies on java's own Runtime class's methods 'freeMemory' and 'totalMemory'.and should be used only after giving users some notice since there is potential for data loss if they have uncompleted transactions.apps. how many are in use. jre oracle. the UPDATE option for the ServerControl was not supported.fnd.2.tcf. TCF Server Administration Ascp_troubleshootingguide_v18_13mar02.tcf. there are certain options you can set or properties you can get (in addition to the STATUS above) at runtime.ServerControl STOP 10021 STOP_MODE=IMMEDIATE PROTOCOL=HTTP Updating a TCF Server Prior to 11. In 11.apps. IMMEDIATE mode will terminate active connections -. Examples jre oracle.

or SSL) is not enough. The environment variable HTTP_TIMEOUT tells the server how long (in minutes) it should keep disconnected sessions around before shutting them down. In the base 11i release. the client needs to know which protocol to use when trying to connect.TCF Configuration Options 1) HTTP/SSL Mode TCF can use a few different protocols to communicate data between a client and the middle tier server. So even if the TCF Server detects that the connection is closed. In 11. Actual configuration details will depend on the proxy software used and cannot be spelled out here. The tag will be stripped out of course before actually attempting to connect to the specified server machine. If the hostname is not prepended with anything.2) for signalling this is to prepend the TCF:HOST profile with the text "http://" for HTTP and "https://" for SSL.the proxy server may choose to time out the connection after a certain timeout period. especially when running in SSL mode. A value too low can result in users getting timed out in the middle of an active TCF client session. The default is 60 minutes. In the latter case. beyond just specifying the protocol: TCF Server Administration Ascp_troubleshootingguide_v18_13mar02. to allow you to communicate (securely if needed) through a properly configured proxy server. it needs to keep the TCF session active . Just starting the TCF Server in the appropriate mode (sockets.5. A value too high will mean that abnormally terminated sessions will stay in memory for a long time. When running a TCF application from within forms. Some proxy server configuration may be required to allow traffic through to the machine you are running your socket server on. hogging resources. In each case. The convention we adopted (in 11. both names are commonly used and we allow either as a convenience. are two names for the same TCF Server mode. we definitely need to be able to shut down that TCF session.2. However. TCF includes full support for HTTP as well as SSL. the network connection from the client to the server will not necessarily be maintained for the duration of the client session . otherwise it would stay around forever. it will take care of updating the TCF:HOST profile with the "http://" or "https://" tag when using the HTTP/SSL protocols. Running through a firewall HTTP mode is provided specifically so TCF users can connect through a firewall (although it is not required that they do so). Available settings are: PROTOCOL=[TCP|SOCKETS|HTTP|HTTPS|SSL] Note that TCP and SOCKETS.For internal use only 27 . HTTP support was only available for certain applications. the client will connect using the default sockets protocol. HTTP.5. respectively. Special notes for SSL mode Running in SSL mode requires a few additional steps. Unfortunately it is not possible for the client to determine on the fly what mode the server is running in. All this behind the scenes timeout and reconnecting should be transparent to the user. and the same is true of HTTPS and SSL. When connecting through a proxy server.doc Oracle/Client Confidential . When using the ServerControl to start up the SocketServer. as the server may not be able to tell whether the disconnect occurred because of a proxy server timeout or because the client aborted abnormally. These are set using the PROTOCOL parameter of the ServerControl utility. the TCF Server does need to be able to shut down the session eventually after being disconnected for some period of time. the proxy settings are picked up from the JInitiator settings automatically. Determining the optimal value for this will P require some thought. so it needs to be "told" this info somehow.on the next client request it will reconnect the client to the server. the default(s).

One example of this is the ServerControl class . or get the STATUS of a SocketServer running in SSL mode. under $JAVA_HOME/lib/security). so will re-use the same certificate database (certdb.fnd.zip files should already be under the 8.it acts as a client when attempting to STOP.dbc file. before starting your SocketServer. The password again gets created as part of the forms install. The . and can be used to create Oracle Wallets which contain thecertificates required to use the SSL protocol. Examples jre oracle. UPDATE. Both the FORMS60_WALLET and FORMS60_HTTPS_NEGOTIATE_DOWN parameters should already be set as part of your forms install. So the command: jre oracle. and will likely be under the $ORACLE_HOME/owm area. It updates the TCF:HOST profile in the database pointed to by 'host_dbname.· · · · · creation of an Oracle Wallet w/password (part of forms install) addition of password into . Two .ServerControl START 10021 DBC=$FND_TOP/secure/host_dbname.6 ORACLE_HOME area: · · $ORACLE_HOME/owm/lib/jlib/jssl-1_1.tcf.txt file exists under the $JAVA_HOME/lib/security directory.1.dbc' to "http://hostname" and the TCF:PORT profile to 10021 TCF Server Administration Ascp_troubleshootingguide_v18_13mar02.doc Oracle/Client Confidential .tcf. and the certdb. when running a TCF application whose client does not use forms. in order to run in SSL mode you will need to make sure JAVA_HOME is set and the certdb.jar On the client side. you then need to add it into the .jar $ORACLE_HOME/owm/lib/jlib/javax-ssl-1_1.txt file exists on the machine you are running your TCF client from. most TCF applications will be connecting through forms. Environment variables can be passed in using the java system properties or using the ENV file argument described in the usage section above.jar and javaxssl-1_1.For internal use only 28 .fnd.dbc file that you pass into the SocketServer.apps. a certificate database (certdb.dbc PROTOCOL=HTTP starts the server in HTTP mode.ServerControl STATUS 10021 PROTOCOL=SSL will only work properly if JAVA_HOME is set. the jssl-1_1. that info should be passed in via the FORMS60_WALLET environment variable.txt file should mirror whatever is setup in your forms environment.zip files also need to be added to the CLASSPATH on the server side. The SocketServer needs to know the location of this wallet.jar files in the CLASSPATH on the client. Wallets are protected by passwords .apps. The FORMS60_HTTPS_NEGOTIATE_DOWN environment variable is an optional parameter which tells a server that it can accept connections from a client that uses weaker level encryption (eg 40-bit instead of 128-bit) than the server supports.so you also need to tell the socket server what that password is when starting it up. using AdminAppServer FORMS60_WALLET environment variable to tell TCF Server the location of the wallet. To add it to the . use the AdminAppServer utility. A wallet should already have been installed as part of the forms server install. However. the values that go into the env.txt) that forms is using (which gets installed with JInitiator.txt) under $JAVA_HOME/lib/security The Oracle Wallet Manager is installed along with the database and forms.dbc file (encrypted).

fnd. Memory usage varies widely by application.txt PROTOCOL=SSL where the env. so unfortunately there is no good metric for calculating what you should set the memory limits to. you can START multiple instances (using the SocketServer class directly perhaps.doc Oracle/Client Confidential . this implies a RAM footprint of (10+n)MB for the JRE process. allocate a heap size of (2+n)MB. to avoid setting and resetting TCF:HOST and TCF:PORT at the site level) and then setting TCF:HOST and TCF:PORT manually at the Application level to direct users of different applications to different instances of TCF Server's.dbc JRE_PARAMS="-ms42m -mx42m -DFND_MAX_JDBC_CONNECTIONS=40" where "-ms42m -mx42m" tell the JRE that the starting and maximum heap sizes should be 42MB (40 users + 2MB spare) and "-DFND_MAX_JDBC_CONNECTIONS=40" tells the JRE to set a Java System property (Java's alternative to O/S environment variables) called "FND_MAX_JDBC_CONNECTIONS" to 40.For internal use only 29 . Each instance can run on a different machine if desired. In addition to the 8MB footprint of the JRE executable itself.dbc'.jre oracle. The FND_MAX_JDBC_CONNECTIONS variable defaults to 14 to accommodate the default JRE heap size of 16MB. 2) Concurrency The default amount of memory any jre process starts with (16M) is quite low . You may find it useful to allow more memory per user or less depending on the load your installation places on the TCF Server. for n users. and the encrypted wallet password should already be in 'host_dbname.dbc ENV=env.ServerControl START 10021 DBC=$FND_TOP/secure/host_dbname. which is generally much smaller than the total number of users on the system. The FND_MAX_JDBC_CONNECTIONS variable can also be specified in the ENV environment file.apps.txt file reads: FORMS60_HTTPS_NEGOTIATE_DOWN=FALSE FORMS60_WALLET=$ORACLE_HOME/owm/wallet HTTP_TIMEOUT=120 starts the server in SSL mode and updates the TCF:HOST profile to "https://hostname" and TCF:PORT to 10021. For 40 concurrent users. Recall that concurrency refers to the number of users who have the supported UI components active on their screens at any given moment in time. TCF employs a JDBC connection caching technology which also needs to be told how many concurrent connections are to be allowed. the ServerControl command line would look like: jre oracle. To enhance performance. If your installation places especially heavy demands on the TCF Server.fnd. you will have to adjust this value upwards accordingly.apps.tcf. A very simple rule you can start out with is. These numbers are intended only as a starting point for effective tuning of your system.ServerControl START 10021 DBC=$FND_TOP/secure/host_dbname. The wallet should be located under $ORACLE_HOME/owm/wallet or else this will not work.tcf. TCF Server Administration Ascp_troubleshootingguide_v18_13mar02. but care must be taken to ensure that theenvironment it runs in is the same and that any proxy server configuration required for HTTP tunnelling or SSL support is done correctly. But if you are running one of the more memory-intensive applications.if you are expecting multiple users to use the SocketServer you will likely want to increase this limit. Exactly how much you want to increase this to will vary based on how many concurrent users you are expecting and which applications they are running. so this part of the JRE_PARAMS setting should not be omitted.

but TCF will function properly on any port which the O/S allows you to use. There are four basic-types of errors: 1) Unable to connect to the socket server 2) Unable to connect to the database 3) Hangs upon connecting to the socket server 4) Java exceptions being raised in the java console Application-specific errors . and errors raised there are often very descriptive and give a good indication of what the problem is. If that window is no longer available. get more information from them than just that. no data displayed. they can redirect their socketserver output into a log file and check the log file when problem occurs again.g.doc Oracle/Client Confidential . the ServerControl class was introduced as a more formal means of starting/stopping the socket server. you need to identify which type of error is occurring . Some debug information is output by default.. This document will review the different errors. though. the single most useful thing to do is try to check the console window in which the SocketServer process was started in. Get the specific error that they see. there may be proxy server configuration required to allow clients to make connections to the port you have selected. so you can categorize it into one of the types of errors that we're expecting. and several different reasons each error might occur. and give general debugging guidelines as well as specific things to watch out for with each error. Troubleshooting the TCF server There are several different errors that one might encounter when attempting to connect to the TCF socket server. we'll go over some basic troubleshooting tips that are generally useful across all types of errors.5. however note that it does not currently give any useful debugging output. The Unix utility 'netstat' is handy for understanding the sockets usage on your server.e.3) TCF Server port We recommend use of port numbers in the range 10021-10029 as a standard which will simplify locating TCF Servers.For internal use only 30 . For 11. to see what errors come up. Then we'll go into other specific things to look out for with each error: General Tips First off. If you're not positive if your error falls into this category. Don't be TCF Server Administration Ascp_troubleshootingguide_v18_13mar02.often users will just log a bug saying 'the TCF socket server is down/not working'. but only occurs after running for some period of time. For protocols other than TCP/Sockets. have the user restart the SocketServer and then try reconnecting. For *ALL* errors.are typically *not* TCF related and should be routed to the appropriate product team. exceptions that occur after the application has already started. it should go to the product teams first who can then determine if it is a TCF issue. errors which only occur when running a particular application . First. If the problem does not reproduce upon restarting the socketserver.

You may also see "Unable to connect to dispatcher.make sure to check user-level profiles. Check the window the SocketServer was started in. What host and port was it started with? Make sure that the profiles TCF:HOST and TCF:PORT on the client point to the socket server you are trying to connect to. Specific Errors 1) Unable to connect to the socket server The standard error message for this is: "The application was unable to establish a network connection with the TCF SocketServer listening on port: <port> on host: <host>. or if it only happens for a particular one. be used to check if the socket server is accepting connections on the host and port it was started on. and from which application.0) utility to check profiles right before launching the TCF app. The simplest application to check is the FND menu viewer. If the user is unable to access these you you'll have to run the profiles form or check in sql*plus directly . or it may be that the client jar files are not set up correctly. When the error occurs on the client. The ServerControl class can (for 11. Determine if the error occurs for any application that attempts to connect. the former only has to do with whether a window listing open connections pops up." Things to check: · · Was the socket server ever started? The system administrator should be able to check if the process is running.apps. For 11.fnd. or start your own and try connecting.tcf. too. and the latter does not output anything useful (not until 11. TCF Server Administration Ascp_troubleshootingguide_v18_13mar02.5). the server most likely was not started.2). To get any meaningful debug output on the server side. The best way to check them is to use the Help->Diagnostics->Examine (Tools->Examine in 11.5. Please contact your system administrator. not just site-level ones. In summary then.For internal use only 31 · . it might be an application-specific problem.fooled by the DEBUG and OUTPUTFILE parameters.5. If you are able to connect from the ServerControl but not from an application. If it hangs upon connecting. however." the exact message may vary slightly between versions and products. always: · · · · Find out the exact error the user is seeing. The user needs to log onto the machine where it was started and run: jre oracle.ServerControl STATUS <port#> If it gives an "unable to connect to SocketServer" error. the Server has stopped accepting connections for some reason and must be bounced (see error (3)). Is the socket server host machine accessible from the client? Try telnetting to the host to see if it is reachable. check what gets printed out on the server. try connecting using ServerControl and see if that gives you any more info. the user will have to start the socket server using the SocketServer class directly. Check if they can connect from other applications.doc Oracle/Client Confidential .

If this problem persists. If the socket server is not started with the DBC arg or it cannot find the .dbc file than what you started it with . The SocketServer must be started with a new argument "DBC=". Remember that the socket server may be looking for a different .dbc file that should be located under $FND_TOP/secure.dbc file specifies that the THIN drivers be used .dbc It's important that the path to the . TCF Server Administration Ascp_troubleshootingguide_v18_13mar02.fnd." Things to check: · · Is the database actually up? Try connecting from SQL*Plus For 11.so.2) Unable to connect to the database The standard error message for this is: "The TCF SocketServer running at <host>:<port> was unable to make a JDBC connection to database <dbname>.dbc file also needs to contain the following variables that identify the database to use: DB_HOST= DB_PORT= DB_NAME= corresponding to the database info in the tnsnames files.dbc file was improperly formatted. too. the most common reason for this is that we now require using DBC files to connect to the database. please contact your system administrator. A very common error to see on the server when this happens is: ld." You may also see "Unable to set context. libocijdbc8. So the command should now read: jre oracle..1: .dbc files are located to lookup multiple . This error can also occur if the . an ENCRYPTED_WALLET_PWD argument must be provided (see the security/AdminAppServer class for more info on this). you must provide this info explicitly (DB_NAME is actually optional if the TWO_TASK and sid of the database are the same.dbc file in the specified directory..it should contain the line: APPS_JDBC_DRIVER_TYPE=THIN The .dbc file be specified.dbc files.For internal use only 32 .dbc file you pass in. pointing to a . rather it relies on the path where those . which is not supported. And when using SSL mode. The thin drivers cannot use the TWO_TASK to resolve the database name.so) Which indicates that the server is attempting to use the THICK jdbc drivers to the database.check the server logs and see if it reports any errors while trying to load the . or a problem with the indicated database. Because the SocketServer can connect to multiple databases. the above error might occur.SocketServer <port#> DBC=$FND_TOP/secure/xxx.5. This may reflect heavy load on the system. You need to make sure the . The GUEST_USER_PWD must be valid.tcf.dbc file.doc Oracle/Client Confidential . it doesn't depend on the specific .so: open failed: No such file or directory (libocijdbc8.apps. but it's good practice to use it).

then typically this indicates that either: a) there is a bug in the code/environment setup problem b) the wrong protocol was used to establish the connection c) the socketserver exited the loop where it accepts connections from the client. The most useful thing to do here is to check the debug output and see if there are any errors coming up. However. the latter suggest you might want to start your socketserver with more memory. this does not explain why the socketserver stopped accepting connections in the first place.For internal use only 33 . One very possible reason is the socket server ran out of memory. TCF Server Administration Ascp_troubleshootingguide_v18_13mar02.2).instead of hanging it should error out right away if there is a protocol mismatch. just make sure the SocketServer is speaking the same protocol as the client.doc Oracle/Client Confidential . There may be class files missing from the CLASSPATH. HTTP. and to check the bug database.2. 3) Hangs upon connecting to the socket server Make sure you try connecting using ServerControl if hanging problems are reported.5. and determining that is a more involved process. Actually. For 11. this used to be an issue but shouldn't be anymore in 11. The former are usually configuration issues. and SSL (for 11. or mismatched versions of java files. The client will use whatever protocol forms was started with (the default is SOCKETS). then this is almost certainly a configuration issue or a bug. For (b). but did not exit For (a) there isn't much to do but check the debug output on the server to see if there's anything obvious that needs to be corrected. If it still hangs. Or there may be an exception occurring somewhere in the java code that can be tracked down in the bug database.5. Supported protocols are Sockets. check the server logs to see if the errors there shed any light on the problem.· Check the server logs . As usual.sometimes ClassNotFoundException's or OutOfMemoryError's raised while it's attempting to connect will result in this error.5 . 4) Exceptions being raised in the java console If an exception is raised in the java console and the TCF application goes down. so you'll know right away that it stopped. we've changed it so that when the socketserver stops accepting connections from the client it will close the socket and exit immediately. (c) is probably the most common.

R3 and R4 are simultaneous. Scenario 1: R1 and R2 are primary resources. R4) is an alternate for (R1.For internal use only 34 . If priority is NULL. the value will be defaulted to Resource sequence.No Note: If Resource step num is NULL.doc Appendix A: Primary and Alternate Resource Setup Oracle/Client Confidential . (R3.Yes. R3 is an alternate for R1 Operation Sequence Resource Sequence Resource Flexfield 10 10 R1 Resource step num Priority/Group Principal Flag 10 20 R2 Resource step num Priority/Group Principal Flag Resource step num Priority/Group Principal Flag Values 10 0 1 (Yes) 20 0 1 (Yes) 10 1 1 (Yes) 10 30 R3 Scenario 2: R1 and R2 are simultaneous. 2 .Appendix A: Primary and Alternate Resource Setup Assumption: Primary resource has a priority of “0” Principal Flag: 1 . the value will default to the primary priority. R2) Operation Sequence Resource Sequence Resource Flexfield Values 10 10 R1 Resource step num 10 Priority/Group 0 Principal Flag 1 (Yes) 10 20 R2 Resource step num Priority/Group Principal Flag Resource step num Priority/Group Principal Flag Resource step num Priority/Group Principal Flag 10 0 2 (No) 10 1 1 (Yes) 10 1 2 (No) 10 30 R3 10 40 R4 Ascp_troubleshootingguide_v18_13mar02.

R3 is sequential and R4 is an alternate for R2 Operation Sequence Resource Sequence Resource Flexfield 10 10 R1 Resource step num Priority/Group Principal Flag 10 20 R2 Resource step num Priority/Group Principal Flag Resource step num Priority/Group Principal Flag Resource step num Priority/Group Principal Flag Resource step num Priority/Group Principal Flag Values 10 0 1 (Yes) 10 0 2 (No) 30 0 1 (Yes) 10 1 1 (Yes) 10 1 2 (No) 10 30 R3 10 40 R1 10 50 R4 Ascp_troubleshootingguide_v18_13mar02.For internal use only 35 .Scenario 3: R1 and R2 are simultaneous.doc Appendix A: Primary and Alternate Resource Setup Oracle/Client Confidential .

Appendix B: Online Planning . sources.Simulation Options Oracle/Client Confidential .Simulation Options The following information can be modified by the user during Online Planning: · Supplier Capacity ð Add new supplier capacity ð Modify dates and quantities · Resource Availability ð Add new resource availability ð Modify dates and quantities ð Add new shifts · Supplies ð Add new planned orders ð Firm planned orders. and alternates.doc Appendix B: Online Planning . and purchase order ð Modify quantities. discrete jobs. · Demands ð Add new Manual MDS ð Modify order priority ð Modify date and quantities · Resource Requirements (Through Gantt Charts) Þ Firm Start / End Date Þ Alternate Resource Ascp_troubleshootingguide_v18_13mar02.For internal use only 36 . dates.