The Art Of Supporting Oracle Applications

Louise Jacobs Red Rock Consulting INTRODUCTION
A myriad of tools and techniques are available to assist you in supporting your Oracle Applications installation. This paper outlines the basic architecture, problem solving process and some of the more common tools and techniques, including tips and hints for investigating Oracle Applications support issues. Some of these techniques tend to be more technical oriented, and are quite involved, such that they could be the subject of a White Paper in themselves. Therefore the aim of this paper is to provide simply a high level summary of these tools and techniques. It is designed for the Functional User or Support Analyst who has an interest in improving his/her problem solving skills, and gaining a better understanding of the tools and techniques available.

Copyright © 2000 Louise Jacobs – Red Rock Consulting

THE ORACLE APPLICATIONS ARCHITECTURE
Depending on the Oracle Applications version you are running, the architecture of the Oracle Applications environment will vary. The fundamental differences in the architecture are as follows Release 10 The Release 10 architecture supports both the Graphical User Interface (GUI) Client and Character Mode forms. Release 10 SmartClient (SC) works with an Oracle Applications server running Release 10.7. Through the character mode forms tool, you can access data through workstation clients. There are generally two tiers in this architecture – Database tier (contains the database, application logic and the concurrent mangers) Client tier (contains logic required to display the GUI front-end forms and some of the business logic and error handling)

(Source: Oracle Applications for MS Windows Clients Installation Manual. Applications Server for Window NT Edition. Release 10SC Production 16.1 pg 2-2) Release 10.7 NCA – Release 11 A third tier is introduced in the later releases of Oracle Applications. The client interface is provided through a Java Applet Viewer or Web browser that launches the applications forms server from the middle tier. The threetier structure is as follows – Database tier contains the data manipulation logic and manages the database. Application tier contains the applications specific logic and manages the Oracle Applications and other development tools (the forms and procedures that define the application), including the Web Application Server software. Desktop client tier provides the User interface display. The introduction of the middle Application tier eliminates the need to install and maintain application software on each desktop client, and helps to reduce network traffic. The fundamental difference with the Internet Computing architecture is that only the presentation layer of Oracle Applications is on the desktop tier in the form of a plug-in to a standard Internet Browser.

Copyright © 2000 Louise Jacobs – Red Rock Consulting

(Source: Oracle Applications Release 11 for Unix Concepts pg 1-2) Release 11i (11.5) The Internet Computing architecture of Release 11i provides a framework for multi-tiered, distributed computing that supports Oracle Applications products. It is the 100% Internet Oracle Applications suite that allows companies to run their worldwide operations from a single, centrally managed site. The Database tier manages an Oracle8i (8.1.6) Relational Database Management System (RDBMS) which offers additional features only used by this Release.

(Source: White Paper - Upgrading to and administering Release 11i: A Technical Perspective)

Copyright © 2000 Louise Jacobs – Red Rock Consulting

$AP_TOP. In the basic directory structure. Custom programs should reside in a custom directory structure under the custom application top directory. You create this directory and set the environment variable $APPL_TOP to point to it. A product directory tree starts with a directory that uses the product’s abbreviation. Beneath each Product top directory are various subdirectories to hold the different types of product files. Forms programs will reside in the forms directory. The Autoinstall process sets up a directory tree for each fully installed or dependent product within this directory. eg ap for Oracle Payables. This is known as the Product Top directory eg $GL_TOP. report programs will reside in the reports directory.Basic Structure of the $APPL_TOP It is important to have a general understanding of Oracle’s APPL_TOP and the directory structure of the Oracle Applications product files. as some of the tools and techniques for investigating support issues require you to directly access these specific program files. sql scripts in the sql directory and so on…. Below that is a sub-directory that uses the product version. there is a top Applications directory that holds one set of product files. It helps to know where the applications code resides for the various products. $FA_TOP. Copyright © 2000 Louise Jacobs – Red Rock Consulting . gl for Oracle General Ledger.

and save the file to a secure directory. I can’t stress enough the importance of reviewing the log file from your Concurrent processes. which transfer information. then it will not be supported by Oracle Support Services. but that does not mean that there were no exceptions encountered. it is always good practice to just quickly review the log file. as they will need to be addressed. Even if your concurrent request completed without an error status. It is also important to try to reproduce the problem in another environment if possible. report or program error. Processes such as the Oracle Assets Periodic Mass Copy and the General Ledger Journal Import may complete successfully. Reviewing your concurrent log files. things such as personal profile options can be reviewed. some or only one of the above environments? Try to examine the differences between the environments if the problem exists in one but not the other. to avoid losing it should the Concurrent Manager requests get purged. Or. such as referring to MetaLink and User Guides. or with interfaces. Test. always review the log file and associated report output for any records that were not successful in the process. Application. and you may need to seek the services of a Consulting organisation. If it is a single user. The following questions can assist in identifying and resolving problems in a timely manner. Has this function worked previously? If the answer is yes.com/support/ Copyright © 2000 Louise Jacobs – Red Rock Consulting . There are numerous ways to investigate problems. What environment is it happening in? Is the problem reproducible? Is this a Production. Always take note of the errors that appear in your log file. Technical References and so on. Has this problem occurred before. then you will need to explore areas such as patch application. is it a group of users accessing the same responsibility? Review the differences in the responsibilities to try to pin point the issue. then a call can be logged with Oracle Support for assistance. MetaLink is a Web support service available from Oracle Support Services. Have there been any changes to the configuration of the system – technical or functional? Technical eg – upgrade of the Database. and the problem remains unsolved. METALINK Before logging a call with Oracle Support Services. It was developed to provide Oracle customers with a 24x7 resource to access information from repositories regarding support information. the above questions should be answered as well as performing research on MetaLink. if you cannot resolve the problem. Is this standard functionality or a customisation of Oracle applications? If the problem is standard functionality and the initial research has been done. including solutions. If it is a customisation made to the application. during the testing phase of your implementation or an upgrade? You could review your records at this stage to see if this has occurred previously and how it was resolved. however some basic questions can be asked regardless of whether the issue is related to a form. This will aid the problem solving process if the issue needs to be logged with Oracle Support Services. Functional eg – Values in the System Options form have been modified within a particular module. Forms or Reports. The following address allows you to register on and access MetaLink www. Is the problem user specific? You will need to identify if other users are experiencing the problem reported or if it relates to one user only. With processes such as these. User Acceptance Testing (UAT) or Development system? Is it occurring in all. Has it stopped working as a result of a stand-alone Patch or Patchset being applied? At this point it is also a good idea to obtain the current Patchset level you have for the particular module.oracle.CLARIFYING THE PROBLEM As users of Oracle Applications you will be confronted with various problem scenarios during day-to-day procedures.

Bugs and briefly on the Forums available. (Source: MetaLink Training Notes. and the reviewing of Patches. Oracle Corporation Australia Pty Ltd) Copyright © 2000 Louise Jacobs – Red Rock Consulting .There are various facets to MetaLink. updating and reviewing of Technical Assistance Requests (TARS). however the focus of this paper will be on the search function for previous reported incidents and the logging.

Copyright © 2000 Louise Jacobs – Red Rock Consulting .The Search Function The Basic Search Enter the search criteria in the search field (To the left of the Search Button). Then click on the search button and your results will be displayed.

the order in which information is shown. Copyright © 2000 Louise Jacobs – Red Rock Consulting . take some time to review the actual search methods available. You can narrow your search by selecting one or more options. To ensure that your search is effective.The Advanced Search The Advanced Search page allows you to refine and further customise your query when searching for information on the site. There are five methods and generally their use will vary on the type of problem/error that you encounter. and the source or area of the site you wish to search. This is the information the above search retrieved. Below is the screen dump of the Advanced search screen. These options include selecting the type of search.

Using AND++ with a comma: All words BEFORE the COMMA must exist. Using AND++ without a comma: EXAMPLE: Using the keywords. All documents with the words "APP-43446 unable to find" will appear in the hit list but those documents with "taxcode for this transaction" also appearing in the document will score higher than those without these optional words. "APP-43446 unable to find. while each word AFTER the comma scores higher if present. The precise phrase "APP-43446 TAXCODE" does not have to appear in any of these documents. Copyright © 2000 Louise Jacobs – Red Rock Consulting ."APP-43446 TAXCODE” will return all documents in which both "APP43446" and "TAXCODE" appear. EXAMPLE: Using the keywords. taxcode for this transaction" will return all documents in which "APP-43466 unable to find" appear but "taxcode for this transaction" are optional.Match All (AND++) Search This is used for general keyword searches and is the default for both basic and advanced searches. The more frequently the keywords exist in the document the higher the score on the hit list returned.

ConText Syntax Search Use the ConText Syntax option if you want to conduct a detailed search that involves more than keywords. 80z86 best. pest. EXAMPLE: Using the keywords. A document ID number is a unique identification number assigned to every file stored in Oracle's Support Knowledge Base. “APP-43446 Taxcode’’ will find all documents in which “APP43446’’ appears and all documents in which “Taxcode” appears. Scores take into account word frequency so it is possible that an article containing 10 occurrences of “AR_STATEMENT_HISTORY” would score more than an article containing both terms. EXAMPLE: Using the keywords. Performs the same function as {end-of-file} end of file regular brackets except it prevents {ORA-600} ORA-600 the penetration of other expansion operators. rest. Copyright © 2000 Louise Jacobs – Red Rock Consulting . again without needing to know the ConText search search syntax. tenderest 80186. Document ID numbers can be obtained from an Oracle analyst or by looking at the document ID in hitlists from other types of MetaLink searches. The underscore matches any single character. however it would rank "ORA-942" as more important than “AR_STATEMENT_HISTORY”. teeniest. Expands a query to include all $scream scream screaming screamed terms having the same stem or root word as the specified term. Any open parentheses encountered before the close parenthesis indicate nested groups. This option searches the site using the ConText Query language. Weighted (FUZZY) Search Use the Weighted (FUZZY) search option to find documents that contain any of the keywords (like a Match any (OR) search) but by using a comma you can rank the importance of the keywords. jest. The following table provides examples for some commonly used search operators: Symbol-Operator % Wildcard Character ( _ ) Wildcard Character Input 10565% te%st 80_86 _est Description The percent symbol matches any substring. The ConText Query language uses special search operators that define terms within a query expression.6 test. Result 10565. or paul parenthesis encountered is the end peter and/or paul and mary and mary) of the group. The first close (peter. The open parenthesis indicates the beginning of a group. Doc ID Search Querying by document ID number allows you to retrieve a specific document from Oracle Support Services' databases. "ORA-942. The Match any (OR) option is a Boolean expression that allows you to find documents in which either of two or more search words appear. AR_STATEMENT_HISTORY" would find documents that contain either of those keywords. Expands a query to include all terms with similar spellings as the ?feline feline defined filtering specified term (English-language text only).80286. test ( ) Group Character { } Group Character $ Stem Expansion ? Fuzzy Expansion Match any (OR) Search Use the Match any (OR) option to find information on multiple topics or for synonyms.

it is sent to a queue in the Metalink System. Below is a screen dump representing a search for a specific TAR number. Copyright © 2000 Louise Jacobs – Red Rock Consulting . Below is a screen dump of a Global TAR search by a single Customer Support Identifier (CSI) Or Multiple CSI’s within the same country.Create. All TARS are transferred into the internal tracking system every 15 minutes and an analyst will then be assigned to work on it.Technical Assistance Request (TAR) . update and modify the TARS in Metalink. When you create an internet TAR (iTAR). Update and Modify With the correct privileges. you have the ability to create.

Copyright © 2000 Louise Jacobs – Red Rock Consulting .

product. Ie Statement Generation program file arxsgp. You can choose to order it by Patch Number or Release Date. If you find a problem that has been reported before and there is a patch available you can download the patch directly from the web site. You can also view a list of available patches for a product and platform. Type in the desired patch that you wish to download. If you know the file that the problem occurred in. Then it will list all the patches that contain this file. Then click submit. language and type. It is very important to read the README.txt as there could be prerequisite or other important instructions you need to follow.Patches A patch is a collection of fixed bugs assembled and tested by support analysts and developers within Oracle. then type this in the Includes File box. Copyright © 2000 Louise Jacobs – Red Rock Consulting . the release. platform.lpc.

1) The bug may not be published 2) Bugs have to be newer than June 1998 3) You can only view bugs that match the products and platforms that are licensed according to the CSIs you have inserted in the ‘Show Licence’ section of Metalink.Bugs These are issues that are logged into the bug database and this is the primary tool used by Development to determine the problem and devise a solution. You can also determine the order of your query results by sorting how you would like the information displayed. This will retrieve the history of the bug and provide a resolution. The Bug Database Search page allows you to specify your search either by a bug number or by other search criteria such as product version. or status. Copyright © 2000 Louise Jacobs – Red Rock Consulting . platform. If you can not retrieve a bug then it may be due to the following reasons.

If this is not obtainable within 2 days then advice from Oracle will be given. It also gives you the opportunity to reply to questions posted by other people. Option to click on ‘Only Threads in which I participate. Click on the Open Forum Button Summary Copyright © 2000 Louise Jacobs – Red Rock Consulting . Changed.Forums A forum is an interactive area for discussions and commentaries dedicated to a certain topic. Forums allow you to post questions and comments and receive responses within 2 business days from a Support Analyst who has expertise in that product area. that is the forum threads which you have posted a message or replied to a message. so a reply to a particular posting becomes part of the ‘thread’. Changed. Select the relevant Forum Product Groups from the drop-down list. New. Click on the type of Thread: All. The forums are intended to address problems with a severity level 2. All – Threads posted since the date indicated in the posting period. If the problem is a severity 1 then you must make a call to support.Only those threads with changes – ie new replies From the time drop down list. Forums are threaded.Only those threads posted since your last visit.3 or 4. New. select the number of days for which you would like to view messages.

Providing the navigation and keystrokes helps in the replication of your issue. The current patchset level of the particular product you are logging the tar for. de-support information and the Certification Application that allows you to obtain product interoperability information. the Concurrent Manager will display a status of ERROR and a log file can be reviewed to show what the error is. You can customise your user profile. close rates. Form and Report. A brief description of the issue. as it represents the business impact of the problem. These are Product. Report or Program. Please see the section on How to identify the version of a Program. Providing the version of the Form. Platform Version and Database Version. Also the answers to the question in the Clarifying the problem section of this paper would also greatly assist the analyst in the problem solving process. and status.1 Oracle Support Services – Logging a TAR To aid users and support analysts in problem resolution there are certain requirements needed by Oracle Support. including complete error messages if applicable.Metalink Quick Reference Sheet. These include areas like product lifecycle which references product availability. Platform. Product version. and account to receive only the information that you want to receive and administer privileges which allows you to do general maintenance. Document id 115465. You can access TAR management reports to provide a list of outstanding tars. If every customer continuously rang and logged every call as a severity 1 or 2 then there would be no use in having severities. You generally know if there is a work around then the problem is less serious than that of a program erroring continuously. For example if it is a form error it will displayed on your screen and generally you can click on the history button to get a more detailed error message. For Further information about Metalink please review. Copyright © 2000 Louise Jacobs – Red Rock Consulting . If the error occurs for a Report or a Program.Metalink is so vast that there are several areas that have not been mentioned. product alerts. Be reasonable when selecting the severity level of your tar.

It is often used to find the value of an ‘Id’ column.7 GUI –11 Help > Tools > Examine Release 11i Help > Diagnostics > Examine Copyright © 2000 Louise Jacobs – Red Rock Consulting .7 Character \Other Debug Release 10. which is usually the primary key used to identify records in a table. The Navigation path for this is as follows Release 10.THE EXAMINE/DEBUG TOOL The Examine utility can be very useful to view values of ‘hidden’ fields in a form that relate directly to columns in the Oracle tables in your database.

You may have noticed on your Tools menu in Rel 10.5 of Forms. displaying debug messages as each step executes. It also controls access to most of the other functions on the ‘Tools’ menu.Utilities:Diagnostics This profile determines if the diagnostic utility Examine requires an Oracle database password. 1) The setting of “Yes” means that you can automatically use the Examine tool when the choice is on the menu. Please note that this option does not work with version 4.7SC. This will effectively run your form in debug mode. that there is also a debug option available. Copyright © 2000 Louise Jacobs – Red Rock Consulting . Your System Administrator controls the setting of this profile option. but is fixed in version 6. 2) The setting of “No” mans that you must enter a password to use the Examine tool when it appears on the menu.

and PROGRAM? It is important to identify the current version of the program that is experiencing the problem. as a bug in the version of the program you are running may be the cause of your problem. Form A Form version is easily obtained via the front-end application. including the Database version.HOW DO I IDENTIFY THE VERSION OF A FORM. Copyright © 2000 Louise Jacobs – Red Rock Consulting .7 Character \Help Version Release 10. the Applications version. the Form Name and Form Version.7 GUI –11i Help > About Oracle Applications This will provide you with several pieces of useful information. REPORT. The navigation path is as follows – Release 10.

you will also need to relink the form executables. Form Name: (example FNDSCSGN). this will help determine the form patchset level. and go to the appropriate directory For Reports: Release 10. If you are on a UNIX platform. will assist in finding previous form issues.30). Individual Form Version (example 11.Report/Executable To obtain the version of a report or concurrent executable.5. You can try to regenerate the Oracle Standard Forms (All platforms) and relink form executables (UNIX Only) Regenerate the forms that are causing the problems. this is important if reporting a bug to development is necessary. obtain the following information by navigating to ‘Help-> ‘About Oracle Applications’ in the Forms menu Oracle Forms Version (example 4. you need to firstly log on to the operating system. Forms can be regenerated by either using the adadmin installation utility. Copyright © 2000 Louise Jacobs – Red Rock Consulting .0. or manually at the command line.10. Refer to the Installations Manuals that are appropriate for your Release and Platform.2).7 Cd $<Product_TOP>/srw Release 11 Cd $<Product_TOP>/reports For a Spawned Concurrent program: Cd $<Product_TOP>/bin Issue the following command to retrieve the version number of the report program or the libraries used by a concurrent executable – Unix: Strings -a <Program name>|grep ‘Header’ Or Ident <Program name>|more NT: Find /i “Header” <Program name> FORM ERRORS If the problem is occurring in a standard Oracle Form.10.

2546. Then. Executable Program Enter the following command. 101. use the r25run32. This will also rule out if there is in fact a concurrent manager problem. if a TAR is logged with Oracle Support Services. if the parameters you see in the Concurrent request are 1.rdf destype=<file or printer name> desname=<>batch=yes TRACE TOOLS SQL*Trace Copyright © 2000 Louise Jacobs – Red Rock Consulting .7) Product_TOP/reports (Apps 11) To run a report from the command line. This log file will reside under the <Product_TOP> directory.exe executable to run a report: r25run32 userid=apps/apps@vd11 report=<Report name>. In this situation. you would enter the following command GLPPOS <userid/password> 0 Y 1 101 2546 Y This will execute the process and produce a debug log file in the format Lxxxxx. Eg For the General Ledger Posting program. The information in this log file can give Oracle Support Services a better idea of what may be causing the problem. they will quite often request you to run the process from the command line. and the userid and password: <Program name> <userid/password> 0 Y <Parameters> Y <Parameters> is the parameters you see from that concurrent request Note: when you run a concurrent program executable from the command line. issue the following command Unix r25run userid=<userid/password> report= <Report name>.rdf destype=<file or printer name> desname=<>desformat=<>batch=yes NT In NT. go to the command line in your operating system and change directory to where the program resides: Cd $<Product_TOP>/sub-directory. you should use a space instead of a comma to separate between each parameter. To do this you need to firstly take note of the exact parameters as listed in the parameters field when you view your concurrent request. substituting the parameters from the Concurrent Manager. <userid>/<passwd> is the username/password of the apps account for your database.log. Reports Report programs reside in: Product_TOP/srw (Apps 10.HOW DO I RUN A PROGRAM AND REPORT FROM THE COMMAND LINE? Sometimes there is insufficient information in the Concurrent log file to determine the reason why a particular concurrent process is failing or completing with errors.

then the concurrent managers. Its presence in the init. then the concurrent managers. which can be useful when there are performance issues or problems with database objects. If there are a number of users on the system or the system is unavailable due to 24 x 7 requirements. Additionally. a database level trace may not always be feasible. then the database. Restart the database.ora file. 2) Modify the start up parameter file (init. Turn the Trace feature on when you are at the point in the form that you want to turn trace on GUI versions Help > Tools > Trace Copyright © 2000 Louise Jacobs – Red Rock Consulting . Restore the original init.SQL*Trace is a facility which assists you in identifying the SQL statements that are executed by a process.ora file sets the initial value for this trace. You can additionally enable or disable the SQL trace facility just for a specific session with the SQL_TRACE option of the ALTER SESSION command. The SQL statement to achieve this is ALTER SESSION SET SQL_TRACE = TRUE Form Trace A Form level trace requires the Trace option to be available as a menu item. The trace process is as follows – Navigate to the Form for which you wish to set the Trace. Perform a shut down of the concurrent managers. then the database. The Database trace process is as follows – 1) Perform a shut down of the concurrent managers. The value of the initialisation parameter SQL_TRACE dictates whether the SQL trace facility is enabled or disabled when you begin a session in ORACLE.7 only) Database Trace A Database level trace requires a shutdown and startup of both the Concurrent Managers and the Database. Steps 1-3 and 6-8 above should always be performed by your Database Administrator.ora) to ensure the following initialisation parameters are set SQL_TRACE=TRUE USER_DUMP_DEST (destination directory for trace output) TIMED_STATISTICS=TRUE 3) 4) 5) 6) 7) 8) Restart the database. Retrieve the trace file(s) from the USER_DUMP_DEST directory. This allows you to obtain smaller and more readable trace files and is particularly useful for developers. This will apply to all sessions on an ORACLE instance. There are four levels in your Oracle Applications at which SQL*Trace can be enabled – Database Form Report Profile (applicable to Release 10. Run the process for which the problem is occurring. it provides you with statistical information for further analysis.

the parameter TIMED_STATISTICS in the init.Rel 10. Turn the Trace feature off. Note: if a trace file is being generated to track performance.ora file must be set to TRUE. GUI versions Help > Tools > Trace Rel 10. or you will severely degrade your system performance. The trace file will be in the USER_DUMP_DEST directory.7 Character \Other Trace Off Rel 11i Help > Diagnostics > Trace Locate the trace file(s) with the time stamp when you ran your trace. Execute the actions you wish to trace. Report Trace Copyright © 2000 Louise Jacobs – Red Rock Consulting . Make sure this step is done.7 Character \ Other Trace On Rel 11i Help > Diagnostics > Trace - Note the time trace is started.

2) \Navigate Concurrent Program Define.rdf and .rex does not exist. Include an additional line after the statement FND SRWINIT in the Before Report Trigger – srw. 3) If the .rex files in the appropriate srw directory.rdf file resides. 3) Enter Query mode. 2) Create a backup copy of your current . you can easily regenerate the report executable by doing the following: UNIX R25convm userid=<userid>/<password> source=<Report name> stype=rdffile dtype=rexfile dest=<Report name> overwrite=yes batch=yes NT R25conv32 syntax: R25convm userid=<userid>/<password> source=<Report name> stype=rdffile dtype=rexfile dest=<Report name> overwrite=yes batch=yes 4) Modify the . 5) Execute Query. Copyright © 2000 Louise Jacobs – Red Rock Consulting .7: In Character Mode: 1) Log on as System Administrator. 7) Locate the trace file(s) from the USER_DUMP_DEST directory. Create the .rex file for the report.A Report level trace would generally require a developer or technical resource. 5) Convert the modified .rdf file UNIX R25convm userid=<userid>/<password> source=<Report name> stype=rexfile dtype=rdffile dest=<Report name> overwrite=yes batch=yes NT R25conv32 syntax: R25convm userid=<userid>/<password> source=<Report name> stype=rexfile dtype=rdffile dest=<Report name> overwrite=yes batch=yes 6) Run the report. and involves the following steps – 1) Logon as applmgr and change directory to where your .rex text of the report if necessary.do_sql (‘alter session set sql_trace=TRUE’) This will activate the SQL Trace in the report Include an additional line after the statement FND SRWEXIT in the After Report Trigger – srw. There is another method that can be used to trace an individual report within Oracle Applications for Release 10. 4) Enter your report-name in the short name field.do_sql (‘alter session set sql_trace=FALSE’) This will deactivate the SQL Trace in the report after the report completes.rex file into an .

making sure that profile option trace = Y. by setting the profile “Utilities:SQL Trace” to “Yes”. Site. then create a new parameter: Add sequence number.e.6) 7) 8) 9) Navigate to the next block. the equivalent trace utility for concurrent programs is set within each individual Concurrent Program definition. Arrow down through the parameters. Cursor is now in the concurrent program details. 3) Enter Query mode. Responsibility and User.7. In GUI Mode: 1) Log on as System Administrator. looking for the name = 'trace'. then create a new parameter: Enter Seq = 999 Parameter = trace Description = report trace Click on Enabled Value Set = Y or N Default Type = profile Default Value= No Required = no Enable Security = no 8) Save the record 9) Run the report. If not found. 6) Click on the [Parameters] button.users can see the profile option but cannot update it. 7) Search through parameters. This option is controlled by your System Administrator . such as 999 Name = Trace Description = Report Trace Enabled = YES Value Set = Yes_No Required = No Enable Security = No Default Type = Profile Default Value= NO 10) Save the record 11) Run the report. The trace can be enabled at all levels. In Release 11. This profile option is only applicable to Release 10. If not found. 2) Navigate to Concurrent>Program>Define. Utilities:SQL Trace SQL trace files can also be generated for concurrent programs through the use of this profile option. making sure that profile option trace = YES. It is only the System Administrator or Application Developer responsibility that has access to define concurrent programs. i. 4) Enter your report_name in the short name field 5) Execute Query. Application. looking for parameter name = ‘trace’. Copyright © 2000 Louise Jacobs – Red Rock Consulting . Select Parameters.

Copyright © 2000 Louise Jacobs – Red Rock Consulting .

Full Print a debug message for each SQL statement executed and keep any temporary data in the database Indicates whether to enable the trace option. there is a utility available called TKPROF which should be applied to the trace file(s) to reformat the output in a more readable format . As the format of the trace output is difficult to read.11i) OE:Debug (Release 10.7 . Available values are Yes or No This profile option is used by Oracle Support Services as a tool to identify a problem with the code. Regular Print a debug message for each subroutine executed.7 – 11i) Comments For the cost update program. Extended Print a debug message for each SQL statement executed.7 – 11i) MRP:Debug Mode (Release 10. Available values are Yes or No Indicates whether debug messages are displayed on forms. Available values are Yes or No This profile option is used by Oracle Support Services as a tool to identify a problem with the code. These profile options serve to provide more information in the Concurrent log file in the form of debug tracing messages – Product Oracle Cost Management Updateable At all levels for the System Administrator Profile Option CST:Cost update debug level (Release 10. this value can be found easily through the following SQL query using SQL*Plus – SELECT value FROM v$parameter WHERE name = 'user_dump_dest'.7 . Available values are Yes or No Indicates whether to enable debug messages within MRP and Oracle Work in Process.The information produced by a SQL*Trace is stored in output files with a .7 – 11i) Oracle Assets Application Responsibility User Application Responsibility User FA: Print Debug (Release 10.7 – 11i) OE:Debug Trace Oracle Order Entry Application Responsibility User Application Copyright © 2000 Louise Jacobs – Red Rock Consulting . DEBUG/TRACE PROFILE OPTIONS There are several profile options across the Oracle Applications that can assist with problem resolution. available values are as follows None Do not print debug messages. Available values are Yes or No This profile option is used by Oracle Master Scheduling/MRP At all levels At all levels MRP:Trace Mode (Release 10. The basic command syntax of the TKPROF utility is as follows – $ tkprof <trace file> <output file> If you do not know the destination directory for the creation of your trace files.11i) FA: Print Timing Diagnostics (Release 10.trc extension.

The database must have write permissions to the specified directory. No The database cannot create debug files. Oracle General Ledger At all levels FSG: Message Detail (Release 10. Available values are Yes The database may create debug files in the nominated directory. Specifies the directory where the Workflow debug files are created. Available values are Yes or No. Available values are Yes or No Determines the level of detail reported in the move transaction concurrent log file during move and resource transaction validation/processing. GL:Debug Directory (Release 11-11i) Oracle Projects Application Responsibility User PA:Debug Mode (Release 11 -11i) Copyright © 2000 Louise Jacobs – Red Rock Consulting . Message level 2 Reports and time stamps processing activities and errors. II and III messages. Full Catalog I. Message level 1 Reports processing activities and errors. Indicates whether a trace file is created during a Concurrent Program execution. Determines if PA processes and reports are run in debug mode.7 – 11i) Oracle Work in Process At all levels TP:WIP Concurrent Message Level (Release 10.7 . Normal Catalog II and III messages.Responsibility User (Release 10.11i) Oracle Support Services as a tool to identify a problem with the code.7 – 11i) Must be set by System Administrator. Error messages are divided into three categories Catalog I – contains detailed statistics useful for program debugging Catalog II – contains process messages useful for finding out where a process failed Catalog III – contains only error messages Available values for this profile option are None No messages. Minimal Catalog III messages. Available values are Message level 0 Reports only errors. Determines the level of detail in your error message log file for FSG reports.

Determines if Account Generator processes are run in debug mode. the value should ALWAYS be set to No. unless otherwise instructed by Oracle Support Services for debugging purposes. the value should ALWAYS be set to No. For performance reasons. This profile option is used for finding problems with Purchasing Workflow processes. Available values are Yes or No. For performance reasons.Oracle Purchasing At all levels PO:Set Debug Concurrent ON (Release 11 –11i) At all levels PO:Set Debug Workflow ON (Release 11 – 11i) Account Generator At all levels Account Generator:Run in Debug Mode (Release 11 – 11i) This profile option is used for finding problems with Requisition Import. unless otherwise instructed by Oracle Support Services for debugging purposes. Copyright © 2000 Louise Jacobs – Red Rock Consulting .

Possible Resolution Ask your DBA to check the available space in the FA data and index tablespaces. and booting the machine will eliminate any run away processes and reclaim resources. as it is specific to certain variations of Unix. e. or if an .7. Fix is also included in 11.h. and Sendmail is not configured correctly for the system. When programs terminate abnormally.D for Rel 11. or an attempt has been made to use a segment of memory for which it does not have permission.0. Retained Earnings accounts contain disabled or expired segments Possible Resolution Fixed in Patch 932703 or in 11.COMMON UNIX O/S SIGNAL ERRORS Signal errors are how Unix processes communicate with each other and the operating system. Ask your Unix Administrator to verify the Sendmail configuration. which is located usually in the /usr/include/sys sub-directory. Oracle Alert process If email (Unix Sendmail) is part of the action items defined in the Alert definition. The meaning of the signal message is contained in a file called signal. SIGNAL 10 A Signal 10 usually suggests a memory or addressing error. There are several patches available on Metalink for Signal 10 errors caused by bugs in the various Oracle products. Examples of Signal 10 errors include Process AP Mass Additions Create Possible Cause Lack of space in the database. This will provide more meaningful error messages on the setup issues/steps not completed prior to running the Open Next Period process. If it is a memory-related problem. Some of the more common Signal errors are as follows – SIGNAL 4 A Signal 4 error usually indicates an illegal/unknown instruction was encountered. This is not a problem with the operating system.g. this is communicated to other processes and the kernel by means of a Signal code. but is part of the operating system’s mechanism of protecting itself. sometimes shutting down the Concurrent Managers and the database. where an Oracle executable has attempted to access memory incorrectly.02 Patch 713261. program pointers/addresses for memory allocations are incorrect or corrupted.1. Perform relevant FA setup Apply database Server side patch 642941 for Rel 10.7 Product 16. Some encounters with a Signal 4 error. THE DREADED SIGNAL 11!! A Signal 11 error indicates that a memory fault has occurred. is non-functional or is missing. and allocated an additional datafile if necessary. The most common causes of a Signal 11 are – Copyright © 2000 Louise Jacobs – Red Rock Consulting . Explore Metalink for the error to find out if your particular problem is related to a known bug for which there may be a patch. This is typically caused by bugs in the code. Possible cause is not having set up the Revaluation Reserve and Amortization Accounts for all Categories/Books. for which there are patches available.AR. include – Process AR to GL Transfer FA Mass Revaluation Preview Report Open and Close GL periods Possible Cause In Rel 10.rdf file has been incorrectly ftp’d from the client in ASCII mode. you may only have 5 accounting periods open at one time. but it can also be caused by a bug in the code. The actual code associated with the signal indicates the nature of the termination.

An example of using the debug feature is outlined below.3 Maintenance Pack) The problem with Signal errors is that whilst we know the meaning of the Signal code that was encountered. 4) Issue the following command Adrelink force=y ranlib=y link_debug=y “fa FAMCP” This will produce a log file called adrelink.0. This log file will be appended to every time a relink command is initiated.log.7 -Fixed with Patch 534568 (or Patchset C or higher) For Rel 11 – Fixed with 709527 (or Patchset 11. this is usually due to the dump destination directory being full. or in $ORACLE_HOME/dbs.C – part of the 11. 5) Re-run the process that produced the Signal error. It is important to trap the file as soon as it is created. $FA_TOP/bin 3) Make a backup copy of the current executable. The core dump file is usually contained in the directory where the command was issued. producing a debugged version of the core dump.FA. and is produced in the form of a file called ‘core’. a core dump is usually produced. It is always a good idea to rename the core dump file produced and move it to a different directory. or the process not having write access to the dump directory. For Rel 10. The information contained in the core dump file is most valuable in helping to resolve a Signal error. Periodic Mass Copy. Produce a debugged version of the Core Dump file !! You can relink the executable in debug mode by using the Adrelink utility.0. Rollback Segments etc 5) Reports ftp’d using incorrect mode – ASCII instead of BINARY Examples of Signal 11 errors include Process FA Periodic Mass Copy FA Mass Change Possible Cause Header file corruption Bug in Mass Change program Possible Resolution Fixed with Patches 924617 and 958462. e. which can be located in $APPL_TOP/install/log. 6) Turn debug off by typing in the following command – Copyright © 2000 Louise Jacobs – Red Rock Consulting . This will allow you to rerun the process causing the Signal error. how do we pinpoint which of the possible causes actually caused this violation ? What to look for with Signal errors … Trap the Core Dump file !! When a Signal error is encountered by the system. as these types of files are overwritten the next time a core dump occurs. This provides more comprehensive statistics than the standard core dump file produced without debug switched on.1) Data Corruption 2) File Size – insufficient disk space in $APPLCSF/out directory where concurrent manager output is created 3) Kernel parameter problems 4) Lack of storage space in Tablespaces. If a core dump is not generated.g.g. This core dump is created at the instant the process was ‘aborted’. for the Oracle Assets Periodic Mass Copy process (executable FAMCP) – 1) Log in as APPLMGR to the operating system and environment affected. 2) Change directory to the directory in which the executable resides e.

Run the process from the operating system command line 9. and check the status of each record for data corruption. This can then be sent to Oracle Support Services to help them determine why the core dump occurred. etc 7.Adrelink force=y ranlib=y link_debug=n “fa FAMCP” The problem with a core dump file is that it is not easily decipherable. Check Metalink for known bugs relating to this Signal code and any patches available 6. such as application of patches. If Signal error occurred when running a report : 1) Check disk space in $APPLCSF/out directory 2) Check report was ftp’d in BINARY mode 3) Check SRW. try narrowing down the parameters e. Rerun the process in debug mode 1) Application debug mode e. run the standard report to see if it too errors 5. and use it to produce a stack trace from the core dump.USER_EXIT (FND SRWEXIT) in After Report Trigger 5) Check for P_CONC_REQUEST_ID parameter in user parameters 10. Identify the records being processed. Run the SQL statements being executed by the program. rollback segments. can be used as a guide to trying to determine the cause of a Signal error – Action 1. and is based on a standard report. The Unix command “script” should be used to capture the output of the debugger. utilising the techniques described earlier in this White paper.USER_EXIT (FND SRWINIT) in Before Report Trigger 4) Check SRW.g. Check for data corruption: 1) Check parameters entered when submitting the Concurrent Request. upgrades or configuration ? What is the current Patch Set level for the product? Is the error reproducible in the same environment ? Is the error reproducible in another environment ? Is the problem related to a specific User or Responsibility? If using Release 10. Log TAR with Oracle Support Services 13. 12. You will need to enlist the help of your DBA or a technical resource with expertise in this area. If it is a report process. Identify full version numbers of the product. check input file for errors in field mapping or the presence of invalid characters 3) Process of elimination. Answer the basic questions – Has the process worked before ? If so. Send debugged core dump file and concurrent log file to 1) Oracle Support Services 2) DBA Include all relevant version numbers Copyright © 2000 Louise Jacobs – Red Rock Consulting . as you will need to determine which debugger exists on your system. Check storage space in tablespaces. and has anything changed since then. RDBMS and the program that encountered the error 4. Checklist for Signal errors The following general checklist. smaller date range 2) If submitted by batch feed. Locate core dump file – rename and move to a separate directory 3. Bounce the Concurrent Manager 8. is the error reproducible in Character mode ? Is it standard or customised functionality ? If it’s a custom report.g. FA:Print Debug (profile option) 2) ADRELINK utility 11. when.7SC. Review Concurrent Request log for any useful information on the error encountered 2.

If the value is set to ‘Yes’.sql that produces the output in html format (fa_trc. Copyright © 2000 Louise Jacobs – Red Rock Consulting . and produces an output file called t107. log into SQL*Plus as the APPS user and type @trace. In Release 11i.0+ or Netscape 4. log a TAR with Oracle Support Services and send the trace results to them for further investigation. you can locate it on Metalink.7 and 11.TIPS AND HINTS FOR COMMON APPLICATION ERRORS Asset Trace This SQL script is designed to provide detailed information on a single asset.sql You will be prompted to enter the ASSET_ID and BOOK_TYPE_CODE [uppercase]. The script captures the data contained in all the Oracle Assets tables for an individual asset. and the value of the FA: Print Debug profile option to ‘Yes’. If there are no other errors. it will process all the assets in your Depreciation Book and capture ALL errored assets in the log file. The script is called trace10. you will ALWAYS be asked to run this script for the offending asset(s). It is extremely useful for troubleshooting problems with your assets. or alternatively contact Oracle Support Services and get them to e-mail the script to you. In this situation. you will be able to resubmit the depreciation process.sql or start trace.html). the process will complete successfully.sql (Rel 10) or trace11. Alternatively. then the cache is reset after EVERY asset. You can set the buffer to either ‘No’ or ‘Yes’. To get the ASSET_ID run the following statement in SQL*Plus select asset_id from fa_additions where asset_number = '[the asset number]'.0+. It controls the caching buffer used when depreciation is run.lis and t11. If you cannot find the script on your system. the program will fail at that point and rollback any depreciation that was committed. If you set the value to ‘No’.sql (Rel 11). There is also a tracehtml. This version of the trace script works with both Release 10 and Release 11 of Oracle Assets. This way you can fix all of your errors in one pass. To effectively analyse the asset data in the trace output. When depreciation encounters an error in Rel 10. and rerun depreciation . If depreciation fails. and you set the FA:Deprn Single value to ‘Yes’. and this time only the corrected assets will process. Please note you should only ever change the value of this profile option to ‘Yes’ when depreciation fails. Whenever you log a TAR with Oracle Support Services for problems with particular assets. which can be viewed using IE Explorer 4. change the value of this option to ‘Yes’ under the ‘Fixed Assets Manager’ responsibility.the process will fail again. and outputs the details to a spool file. Profile Option FA:Deprn Single This profile option should be used specifically when a depreciation run fails in Oracle Assets.lis respectively. You should find this file in the admin/sql directory under $FA_TOP. then the cache is reset after every 20 assets. Once your resolve this. resubmit depreciation. the run depreciation and close periods have been broken out to separate processes. but you will find that the log file now produces detailed information on the actual asset causing the failure. you really need to have a good understanding of the Oracle Asset tables in order to determine if there is data corruption. To run the script.

the profile option Account Generator: Run in Debug mode has not been set to ‘Yes’). in which case no information is logged in the workflow tables.sql can be run. This provides the same information that the Workflow Monitor does. (NOTE: If the value for the field is _SYNCH#_. go to Menu Help -> Tools -> Examine. Running the script involves the following steps – 1) Check the profile option Account Generator: Run in Debug mode. 3) After you receive the error.sql to retrieve any data. Release 11 of Oracle Assets is delivered with this SQL*Plus test script called faxagtst. The latest script comes with 11. Note down the itemkey value required to run wfstatus. 2) The reason why Account Generator could not build this code combination.sql gives important debug messages.sql. a script called wfstatus. Copyright © 2000 Louise Jacobs – Red Rock Consulting . if the customer has Workflow Monitor set up. This script is contained in patch 375496 and can be downloaded from Metalink.ap375496. and hence wfstatus. Account Generator FA Test Script This script assists in diagnosing problems in Oracle Assets concurrent processes that fail due to account generation. 4) After getting the itemkey value. (No or Null value means that the account generator process is being run in 'Synch' mode. The output from the script tells the User the following – 1) The code combination id that Account Generator attempted to build. This should be set to Yes.sql – AP Trial Balance Rebuild script This script can be useful if your AP Trial Balance report is not reporting correctly on outstanding liability. All the information that feeds this script is contained in the log file from the failed run. 3) If Dynamic insertion is set to ‘Yes’. and look for the value for field CHARGE_ACC_WF_ITEMKEY (Click on the arrow next to the Field Zone and then Query up the CHARGE_ACC_WF_ITEMKEY). simulate the error. navigate to lines/header zone and commit (Save). by navigating to the Distribution zone of Enter Purchase Order or Enter Requisition.sql. it will prompt you for a number of parameters. When you run the script. The wfstatus. You should find this in the $FA_TOP/admin/sql directory. It replaces the Flexbuilder Test screen used in Release 10. This is important for the wfstatus. including error messages for the processes that are erroring.sql would not retrieve any information) 2) After setting the profile option to ‘Yes’. and trying to build the account again. Note the script is not needed for cash basis installations. Contact Oracle Support Services for the latest version.03 Minipack. Account Generator Purchasing Workflow Test Script In order to find out what is wrong with the Account Generator workflow. discard changes in the distribution zone. The script is a data fix script that can be run to recreate the trial balance records in the AP_TRIAL_BALANCE table for all records (payments and invoice distributions) that have been transferred to GL within a specified range of accounting dates. The parameter WF_ITEM_KEY is required to run this script.

How to create an AR Debug log file This function is normally used in the Transactions. Tools. Examine. or the value of the maximum extents parameter increased to allow for further growth. There are a few ways to determine what the UTL_FILE_DIR setting is – 3) Run the following in SQL*Plus for the related instance: Select value from v$parameter where upper(name) = 'UTL_FILE_DIR'. Customers. <output path> relates to the UTL_FILE_DIR directory where the database writes files. or a ‘max # extents’ error referring to a database object such as a table or index. 4) The UTL_FILE_DIR setting should be held in the init<sid>. contact your DBA. If the error occurs often within your Oracle Applications. i. <filename> is whatever you wish to call the output created.log 5) Hit the key that will invoke the error/problem. then the solution is to increase the Col/Row for the Printer style. select: Help. This will give you a box with 3 fields. REP-1222 Invalid body size REP-1212 Object is not fully enclosed by its enclosing object REP-1211 Object is larger than enclosing body These are common errors that can occur with the running of reports. There is no default setting for this parameter if it is not set.ora file. The cause of these errors is usually that the Rows/Columns defined in the Printer Style you are trying to use do not cover the whole of the report.e. If you encounter errors with rollback segments. If it is a Standard applications report. It is the initialisation parameter OPEN_CURSORS that determines the maximum number of cursors. If the setting needs to be added to the init<sid>. as the size of the rollback segment will need to be increased. i. A log file should then be created in the output directory with the filename you have specified. 2) From the Help menu at the top of the form. If it is a custom program that fails with this error. ORA-01000 Maximum Number Of Cursors Exceeded This is one of the most common errors that can occur. Copyright © 2000 Louise Jacobs – Red Rock Consulting . then a developer should review the code to see if the program can be modified to use fewer cursors. then restart the database.e. then please note that your DBA will need to bring down the database instance and bring it back up for the changes to be effective. Customers and Receipts screens. Enter the Following: In Block: Parameter In Field: AR_DEBUG_FLAG In Value: FS <output_path> <filename> Where F = File S = Screen. The Debug steps are as follows – 1) Go through the steps that you would perform to encounter the error/problem but stop just before you would get the actual error. ORA-01562:failed to extend rollback segment number (n) ORA-01628:max # extents (n) reached for rollback segment Errors with rollbacks segments are common in the Oracle database when storage becomes a problem. If it is a customised report you need to establish the size of the report and set-up a Printer Style as appropriate.ora file under the $ORACLE_HOME/dbs directory. The output gives details of the packages that are being used on the process when an error occurs. modify the OPEN_CURSORS parameter to increase its value. Enter the password if prompted. The reason for this error is that Oracle has reached the set limit of open cursors allowed for that executable or User session. your DBA should shut down Oracle. Don't hit the key that will invoke the error.

If you need to run a data fix script. Applications community for customers and partners • Oracle Technet which is a great source for Oracle technical information • OAUGnet which is a Oracle Application User Group that provides an opportunity for Oracle users to share knowledge and experience About the Presenter Janice Wilson has had 14 years within the IT industry. and insert a SPOOL OFF command after the last SQL statement. Always review any data fix scripts sent to you by Oracle Support Services before you run them. and not just when you encounter issues in your Oracle Applications . there are a multitude of tools and techniques available to assist us in troubleshooting Oracle Applications problems. in her experience with Oracle applications. Depending on the type of issue.FIXES FOR DATA CORRUPTION If your problem is in fact caused by data corruption. but not least. a data fix will be required to update the records in error. You just need to become familiar with the tools and techniques available to assist you. it is essential that you perform a backup of the Oracle Application tables that will be affected by the fix. However. CONCLUSION As you can see. you will be able to find the solution here!! Don’t forget there are also numerous support networks available for users of Oracle Applications such as • Oracle AppsNet which is an online. output should always be spooled before and after the data fix to verify its results. approximately 80% of the problems encountered within Oracle Applications can be resolved without having to rely totally on external support. we can use a variety of methods for analysis.there’s a wealth of knowledge in Metalink’s repositories. 8 of which has been spent working with Oracle applications. then update the script to insert the SPOOL <filename> command before execution of the script. A reliable support tool is encouraged for the following reasons – • Record history of issues and resolutions • Configuration management • Identify recurring issues • Identify training needs Supporting your Oracle Applications can be a bit daunting and overwhelming at times. wherever possible. It is always good practice to perform regular refreshes of your Test environment to keep your Test environment up to date with your Production environment. Being aware of the tools available enables us to more effectively support our Oracle Applications and become more productive in our investigation. and try and make full use of them. Back up the tables the script is either inserting. And don’t forget about Metalink!! Invest the time to explore this site. we can provide crucial information to Oracle Support Services to assist them in determining the cause of the error. by being able to perform a more detailed investigation. more often than not. SPOOL OFF Last. She has performed a variety of roles. Even if we cannot resolve the issue ourselves. and if the script does not contain a SPOOL <filename> command. updating or deleting records from. in my experience. This will greatly reduce the turnaround time for problem resolution. to form an effective audit trail. Additionally. always run the data fix script in a Test environment before running it against Production. Example as follows SPOOL UPD_PAY_DIST Update ap_payment_distributions_all set amount = base_amount where invoice_payment_id = 13548 and payment_line_number = 33. including Copyright © 2000 Louise Jacobs – Red Rock Consulting . When you do encounter a problem.

Technical Analyst and Business Analyst. Copyright © 2000 Louise Jacobs – Red Rock Consulting . DBA. She is currently employed by Red Rock Consulting in the role of Senior Consultant in the Applications Support team.Developer.

Sign up to vote on this title
UsefulNot useful