Running a Trace on a Process

本文档详细介绍了如何在Oracle Applications软件中对出现ORA错误或运行时间过长的进程进行跟踪。主要内容包括设置跟踪输出目录、开启时间统计、启用进程跟踪、提交请求及获取分析跟踪文件。
Running a Trace on a Process [ID 148145.1]  

--------------------------------------------------------------------------------

The purpose of this document is to inform. users of all Releases of Oracle
Applications software how to execute a trace on a process.


SCOPE & APPLICATION
-------------------
This document is intended for users of all Releases of Oracle Applications
software that need to run traces on processes where a process terminates with an
ORA error or a process is running for a very long time.


RUNNING A TRACE ON A PROCESS
----------------------------
1) Make sure that a directory has been established for the trace output, and for
performance issues on a process, also make sure that timed statistics are turned
on. To discern the directory where the trace will be written to, execute the
following sql:

select value from v$parameter where name = 'user_dump_dest';//查找trace文件存放路径
//trace文件存放路径:[/ora1159/prod/proddb/9.2.0/admin/PROD_erpapp/udump]

To turn timed statistics on, execute the following sql:

alter system set timed_statistics = true; //设置时间统计功能开
在sqlplus 下执行即可

2) Make sure that trace has been enabled for the process by doing the following:

     a) Navigate to System Administrator -> Concurrent -> Program -> Define.//并发-方案-定义
     b) On the Concurrent Programs form, with your cursor in the Program field,
        do query enter, enter the name of the process to be traced, i.e. enter
        GMS:%Costing%Expense% to query up the GMS: Costing and Funds Check on
        Expense Report process, then enter query run.//查找出需要跟踪的请求程序定义
     c) In the Request region of the Concurrent Programs form, check the box
        entitled "Enable Trace".//在程序定义的请求区域,将允许跟踪选项打勾。
     d) Close the Concurrent Programs form. and exit to Navigator.//关闭并发程序的form。

3) In the Grants Super User responsibility(授权的超级用户责任下), submit the process as follows:
在相应的超级用户职责下(该请求程序被授权给该职责),提交请求:查看-请求-提交新请求-单个请求:选择相关的请求,填写相关的参数后,运行。
   a) For Release 11i users, navigate to Reports -> Run. (请求->运行) In the submit a new
      request form, choose either single request or request set and click on the
      OK button. In the submit request form, choose the process from the list
      of values, enter any and all relevant parameters and submit the process.
   b) For Release 10.7 and 11.0 users, navigate to Other -> Requests -> Run.
      In the submit a new request form, choose either single request or request
      set and click on the OK button. In the submit request form, choose the
      process from the list of values, enter any and all relevant parameters and
      submit the process.

4) Once the process has completed, position your cursor on the relevant process
on the request form, click on the view output button, and save a copy of the
output; click on the view log button and save a copy of the log.
//一旦请求执行完毕,将光标放到刚执行的请求上,点击查看输出按钮,将输出保存为文本文件。点击查看日志按钮,导出文本文件。

5) Turn timed statistics off by executing the following sql: //关闭时间统计功能

alter system set timed_statistics = false; //设置时间统计功能关

6) You can find the trace file (*.trc) by checking in the INIT.ORA file for the
user_dump_dest directory location, or you can execute the following sql:
你现在可以去查找刚生成的trace文件了,路径就是上面查找出的路径,也可以在 INIT.ORA中的user_dump_dest 项查看。或者再执行下面的语句。
select value from v$parameter where name = 'user_dump_dest'; //查找trace文件存放路径
这个是96上的路径:/ora1159/prod/proddb/9.2.0/admin/PROD_erpapp/udump。在该路径下,按时间排序,第一个文件即是刚生成的trace文件。
查看命令是 >ls -lt ./
7) Tkprof the trace file with an explain plan. If it is a performance issue,
tkprof the trace file with an explain plan and sort. See Tkprof a Trace File
With Explain Plan, Note 148137.1.
使用Tkprof命令处理该trace文件,具体用法另有解释。
8) Upload the following to Metalink under the associated TAR number:
将以下4个文件提交给Metalink。
   a) copy of output;//输出文件
   b) copy of log;//日志文件
   c) raw trace file; and //trace文件
   d) tkprof'd trace file.//执行过的trace文件

来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/10359218/viewspace-677410/,如需转载,请注明出处,否则将追究法律责任。

转载于:http://blog.itpub.net/10359218/viewspace-677410/

Commands and options Description -o file Write the HTML trace report to the specified file. If you don't specify this option, systrace saves your report to the same directory as systrace.py and names it trace.html. -t N | --time=N Trace device activity for N seconds. If you don't specify this option, systrace prompts you to end the trace by pressing the Enter key from the command line. -b N | --buf-size=N Use a trace buffer size of N kilobytes. This option lets you limit the total size of the data collected during a trace. -k functions |--ktrace=functions Trace the activity of specific kernel functions, specified in a comma-separated list. -a app-name |--app=app-name Enable tracing for apps, specified as a comma-separated list of process names. The apps must contain tracing instrumentation calls from the Trace class. You should specify this option whenever you profile your app—many libraries, such as RecyclerView, include tracing instrumentation calls that provide useful information when you enable app-level tracing. For more information, see Define custom events. To trace all apps on a device running Android 9 (API level 28) or higher, pass the wildcard character "*", including the quotation marks. --from-file=file-path Create an interactive HTML report from a file, such as TXT files that include raw trace data, instead of running a live trace. -e device-serial |--serial=device-serial Conduct the trace on a specific connected device, identified by its device serial number. categories Include tracing information for the system processes you specify, such as gfx for system processes that render graphics. You can run systrace with the -l command to see a list of services available to your connected device.翻译
08-08
Java Python 2024 ICS Lab4: Tiny Shell Assigned: Dec. 02, Due: Sat, Jan. 04, 2025, 11:59PM Introduction The purpose of this lab is to become more familiar with the concepts of process control and signalling. You’ll do this by writing a simple Unix shell program that supports job control. Logistics Any clarifications and revisions to the lab will be posted on the course Web page. Hand Out Instructions You can get the Tiny Shell Lab with git from the ICS Course Server, you just need to switch lab4 branch git fetch git checkout lab4 It contains 26 files, one of which is called “README”. Please read “README” to check if you have all the files. After making sure you get the right handout. Then do the following: • Type the command make to compile and link some test routines. • Type your name and student ID in the header comment at the top of tsh.c. Looking at the tsh.c (tiny shell) file, you will see that it contains a functional skeleton of a simple Unix shell. To help you get started, we have already implemented the less interesting functions. Your assignment is to complete the remaining empty functions listed below. As a sanity check for you, we’ve listed the approximate number of lines of code for each of these functions in our reference solution (which includes lots of comments). 1 • eval: Main routine that parses and interprets the command line. [70 lines] • builtin_cmd: Recognizes and interprets the built-in commands: quit, fg, bg, and jobs. [25 lines] • do_bgfg: Implements the bg and fg built-in commands. [50 lines] • waitfg: Waits for a foreground job to complete. [20 lines] • sigchld_handler: Catches SIGCHILD signals. 80 lines] • sigint_handler: Catches SIGINT (ctrl-c) signals. [15 lines] • sigtstp_handler: Catches SIGTSTP (ctrl-z) signals. [15 lines] Each time you modify your tsh.c file, type make to recompile it. To run your shell, type tsh to the command line: unix> ./tsh tsh> [type commands to your shell here] General Overview of Unix Shells A shell is an interactive command-line interpreter that runs programs on behalf of the user. A shell repeatedly prints a prompt, waits for a command line on stdin, and then carries out some action, as directed by the contents of the command line. The command line is a sequence of ASCII text words delimited by whitespace. The first word in the command line is either the name of a built-in command or the pathname of an executable file. The remaining words are command-line arguments. If the first word is a built-in command, the shell immediately executes the command in the current process. Otherwise, the word is assumed to be the pathname of an executable program. In this case, the shell forks a child process, then loads and runs the program in the context of the child. The child processes created as a result of interpreting a single command line are known collectively as a job. In general, a job can consist of multiple child processes connected by Unix pipes. If the command line ends with an ampersand ”&”, then the job runs in the background, which means that the shell does not wait for the job to terminate before printing the prompt and awaiting the next command line. Otherwise, the job runs in the foreground, which means that the shell waits for the job to terminate before awaiting the next command line. Thus, at any point in time, at most one job can be running in the foreground. However, an arbitrary number of jobs can run in the background. For example, typing the command line tsh> jobs causes the shell to execute the built-in jobs command. Typing the command line T 2 tsh> /bin/ls -l -d runs the ls program in the foreground. By convention, the shell ensures that when the program begins executing its main routine int main(int argc, char *argv[]) the argc and argv arguments have the following values: • argc == 3, • argv[0] == “/bin/ls”, • argv[1]== “-l”, • argv[2]== “-d”. Alternatively, typing the command line tsh> /bin/ls -l -d & runs the ls program in the background. Unix shells support the notion of job control, which allows users to move jobs back and forth between background and foreground, and to change the process state (running, stopped, or terminated) of the processes in a job. Typing ctrl-c causes a SIGINT signal to be delivered to each process in the foreground job. The default action for SIGINT is to terminate the process. Similarly, typing ctrl-z causes a SIGTSTP signal to be delivered to each process in the foreground job. The default action for SIGTSTP is to place a process in the stopped state, where it remains until it is awakened by the receipt of a SIGCONT signal. Unix shells also provide various built-in commands that support job control. For example: • jobs: List the running and stopped background jobs. • bg : Change a stopped background job to a running background job. • fg : Change a stopped or running background job to a running in the foreground. • kill : Terminate a job. The tsh Specification Your tsh shell should have the following features: • The prompt should be the string “tsh> ”. 3 • The command line typed by the user should consist of a name and zero or more arguments, all separated by one or more spaces. If name is a built-in command, then tsh should handle it immediately and wait for the next command line. Otherwise, tsh should assume that name is the path of an executable file, which it loads and runs in the context of an initial child process (In this context, the term job refers to this initial child process). • tsh need not support pipes (|) or I/O redirection (< and >). • Typing ctrl-c (ctrl-z) should cause a SIGINT (SIGTSTP) signal to be sent to the current foreground job, as well as any descendents of that job (e.g., any child processes that it forked). If there is no foreground job, then the signal should have no effect. • If the command line ends with an ampersand &, then tsh should run the job in the back- ground. Otherwise, it should run the job in the foreground. • Each job can be identified by either a process ID (PID) or a job ID (JID), which is a positive integer assigned by tsh. JIDs should be denoted on the command line by the prefix ’%’. For example, “%5” denotes JID 5, and “5” denotes PID 5. (We have provided you with all of the routines you need for manipulating the job list.) • tsh should support the following built-in commands: – The quit command terminates the shell. – The jobs command lists all background jobs. – The bg command restarts by sending it a SIGCONT signal, and then runs it in the background. The argument can be either a PID or a JID. – The fg command restarts by sending it a SIGCONT signal, and then runs it in the foreground. The argument can be either a PID or a JID. • tsh should reap all of its zombie children. If any job terminates because it receives a signal that it didn’t catch, then tsh should recognize this event and print a message with the job’s PID and a description of the offending signal. Checking Your Work We have provided some tools to help you check your work. Before you run any executable program, please make sure it has the execution permission. If not, use “chmod +x” to give it the execution permission. Reference solution. The Linux executable tshref is the reference solution for the shell. Run this program to r 2024 ICS 、 C++ esolve any questions you have about how your shell should behave. Your shell should emit output that is identical to the reference solution (except for PIDs, of course, which change from run to run). Shell driver. The sdriver.pl program executes a shell as a child process, sends it commands and signals as directed by a trace file, and captures and displays the output from the shell. Use the -h argument to find out the usage of sdriver.pl: 4 unix> ./sdriver.pl -h Usage: sdriver.pl [-hv] -t -s -a Options: -h -v -t -s -a -g Print this message Be more verbose Trace file Shell program to test Shell arguments Generate output for autograder We have also provided 16 trace files (trace{01-16}.txt) that you will use in conjunction with the shell driver to test the correctness of your shell. The lower-numbered trace files do very simple tests, and the higher-numbered tests do more complicated tests. You can run the shell driver on your shell using trace file trace01.txt (for instance) by typing: unix> ./sdriver.pl -t trace01.txt -s ./tsh -a ”-p” (the -a ”-p” argument tells your shell not to emit a prompt), or unix> make test01 Similarly, to compare your result with the reference shell, you can run the trace driver on the reference shell by typing: unix> ./sdriver.pl -t trace01.txt -s ./tshref -a ”-p” or unix> make rtest01 For your reference, tshref.out gives the output of the reference solution on all races. This might be more convenient for you than manually running the shell driver on all trace files. The neat thing about the trace files is that they generate the same output you would have gotten had you run your shell interactively (except for an initial comment that identifies the trace). For example: bass> make test15 ./sdriver.pl -t trace15.txt -s ./tsh -a ”-p” # # trace15.txt - Putting it all together # tsh> ./bogus ./bogus: Command not found. tsh> ./myspin 10 Job (9721) terminated by signal 2 tsh> ./myspin 3 & [1] (9723) ./myspin 3 & 5 tsh> ./myspin 4 & [2] (9725) ./myspin 4 & tsh> jobs [1] (9723) Running ./myspin 3 & [2] (9725) Running ./myspin 4 & tsh> fg %1 Job [1] (9723) stopped by signal 20 tsh> jobs [1] (9723) Stopped [2] (9725) Running tsh> bg %3 %3: No such job tsh> bg %1 [1] (9723) ./myspin 3 & tsh> jobs [1] (9723) Running [2] (9725) Running tsh> fg %1 tsh> quit bass> Hints • Read every word of Chapter 8 (Exceptional Control Flow) in your textbook. • Use the trace files to guide the development of your shell. Starting with trace01.txt, make sure that your shell produces the identical output as the reference shell. Then move on to trace file trace02.txt, and so on. • The waitpid, kill, fork, execve, setpgid, and sigprocmask functions will come in very handy. The WUNTRACED and WNOHANG options to waitpid will also be useful. • When you implement your signal handlers, be sure to send SIGINT and SIGTSTP signals to the entire foreground process group, using ”-pid” instead of ”pid” in the argument to the kill function. The sdriver.pl program tests for this error. • One of the tricky parts of the lab is deciding on the allocation of work between the waitfg and sigchld_handler functions. We recommend the following approach: – In waitfg, use a busy loop around the sleep function. – In sigchld_handler, use exactly one call to waitpid. While other solutions are possible, such as calling waitpid in both waitfg and sigchld_handler, these can be very confusing. It is simpler to do all reaping in the handler. • In eval, the parent must use sigprocmask to block SIGCHLD signals before it forks the child, and then unblock these signals, again using sigprocmask after it adds the child to the job list 6 ./myspin 3 & ./myspin 4 & ./myspin 3 & ./myspin 4 & by calling addjob. Since children inherit the blocked vectors of their parents, the child must be sure to then unblock SIGCHLD signals before it execs the new program. The parent needs to block the SIGCHLD signals in this way in order to avoid the race condition where the child is reaped by sigchld_handler (and thus removed from the job list) before the parent calls addjob. • Programs such as more, less, vi, and emacs do strange things with the terminal settings. Don’t run these programs from your shell. Stick with simple text-based programs such as /bin/ls, /bin/ps, and /bin/echo. • When you run your shell from the standard Unix shell, your shell is running in the foreground process group. If your shell then creates a child process, by default that child will also be a member of the foreground process group. Since typing ctrl-c sends a SIGINT to every process in the foreground group, typing ctrl-c will send a SIGINT to your shell, as well as to every process that your shell created, which obviously isn’t correct. Here is the workaround: After the fork, but before the execve, the child process should call setpgid(0, 0), which puts the child in a new process group whose group ID is identical to the child’s PID. This ensures that there will be only one process, your shell, in the foreground process group. When you type ctrl-c, the shell should catch the resulting SIGINT and then forward it to the appropriate foreground job (or more precisely, the process group that contains the foreground job). Evaluation Your score will be computed out of a maximum of 90 points based on the following distribution: 80 Correctness: 16 trace files at 5 points each. 10 Style points. We expect you to have good comments (5 pts) and to check the return value of EVERY system call (5 pts). Your solution shell will be tested for correctness on a Linux machine, using the same shell driver and trace files that were included in your lab directory. Your shell should produce identical output on these traces as the reference shell, with only two exceptions: • The PIDs can (and will) be different. • The output of the /bin/ps commands in trace11.txt, trace12.txt, and trace13.txt will be different from run to run. However, the running states of any mysplit processes in the output of the /bin/ps command should be identical. We have provided you with a test le called grade-shlab.pl. Following is the example of correct case: 7 unix> ./grade-shlab.pl -f tsh.c CS:APP Shell Lab: Grading Sheet for tsh.c Part 0: Compiling your shell gcc -Wall -O2 tsh.c -o tsh gcc -Wall -O2 myspin.c -o myspin gcc -Wall -O2 mysplit.c -o mysplit gcc -Wall -O2 mystop.c -o mystop gcc -Wall -O2 myint.c -o myint Part 1: Correctness Tests Checking trace01.txt... Checking trace02.txt... Checking trace03.txt... Checking trace04.txt... Checking trace05.txt... Checking trace06.txt... Checking trace07.txt... Checking trace08.txt... Checking trace09.txt... Checking trace10.txt... Checking trace11.txt... Checking trace12.txt... Checking trace13.txt... Checking trace14.txt... Checking trace15.txt... Checking trace16.txt... Preliminary correctness score: 80 Hand In Instructions • You only need to commit the tsh.c file to svn server if you modify it. • Make sure you have included your name and student ID in the header comment of tsh.c. We strongly recommend you to multiple commit your code to svn during implementation ———————————————— 版权声明:本文为博主原创文章,遵循 CC 4.0 BY-SA 版权协议,转载请附上原文出处链接和本声明。 原文链接:https://blog.youkuaiyun.com/gavegift/article/details/144958687翻译
05-19
下载方式:https://pan.quark.cn/s/a4b39357ea24 在纺织制造领域中,纱线的品质水平对最终制成品的整体质量具有决定性作用。 鉴于消费者对于产品规格和样式要求的不断变化,纺织制造工艺的执行过程日益呈现为一种更为复杂的操作体系,进而导致对纱线质量进行预测的任务变得更加困难。 在众多预测技术中,传统的预测手段在面对多变量间相互交织的复杂关系时,往往显得力不从心。 因此,智能计算技术在预测纱线质量的应用场景中逐渐占据核心地位,其中人工神经网络凭借其卓越的非线性映射特性以及自适应学习机制,成为了众多预测方法中的一种重要选择。 在智能计算技术的范畴内,粒子群优化算法(PSO)和反向传播神经网络(BP神经网络)是两种被广泛采用的技术方案。 粒子群优化算法是一种基于群体智能理念的优化技术,它通过模拟鸟类的群体觅食行为来寻求最优解,该算法因其操作简便、执行高效以及具备优秀的全局搜索性能,在函数优化、神经网络训练等多个领域得到了普遍应用。 反向传播神经网络则是一种由多层节点构成的前馈神经网络,它通过误差反向传播的机制来实现网络权重和阈值的动态调整,从而达成学习与预测的目标。 在实际操作层面,反向传播神经网络因其架构设计简洁、实现过程便捷,因此被广泛部署于各类预测和分类任务之中。 然而,该方法也存在一些固有的局限性,例如容易陷入局部最优状态、网络收敛过程缓慢等问题。 而粒子群优化算法在参与神经网络优化时,能够显著增强神经网络的全局搜索性能并提升收敛速度,有效规避神经网络陷入局部最优的困境。 将粒子群优化算法与反向传播神经网络相结合形成的PSO-BP神经网络,通过运用粒子群优化算法对反向传播神经网络的权值和阈值进行精细化调整,能够在预测纱线断裂强度方面,显著提升预测结果的...
植物实例分割数据集 一、基础信息 数据集名称:植物实例分割数据集 图片数量: - 训练集:9,600张图片 - 验证集:913张图片 - 测试集:455张图片 总计:10,968张图片 分类类别:59个类别,对应数字标签0至58,涵盖多种植物状态或特征。 标注格式:YOLO格式,适用于实例分割任务,包含多边形标注点。 数据格式:图像文件,来源于植物图像数据库,适用于计算机视觉任务。 二、适用场景 • 农业植物监测AI系统开发:数据集支持实例分割任务,帮助构建能够自动识别植物特定区域并分类的AI模型,辅助农业专家进行精准监测和分析。 • 智能农业应用研发:集成至农业管理平台,提供实时植物状态识别功能,为作物健康管理和优化种植提供数据支持。 • 学术研究与农业创新:支持植物科学与人工智能交叉领域的研究,助力发表高水平农业AI论文。 • 农业教育与培训:数据集可用于农业院校或培训机构,作为学生学习植物图像分析和实例分割技术的重要资源。 三、数据集优势 • 精准标注与多样性:标注采用YOLO格式,确保分割区域定位精确;包含59个类别,覆盖多种植物状态,具有高度多样性。 • 数据量丰富:拥有超过10,000张图像,大规模数据支持模型充分学习和泛化。 • 任务适配性强:标注兼容主流深度学习框架(如YOLO、Mask R-CNN等),可直接用于实例分割任务,并可能扩展到目标检测或分类等任务。
室内物体实例分割数据集 一、基础信息 • 数据集名称:室内物体实例分割数据集 • 图片数量: 训练集:4923张图片 验证集:3926张图片 测试集:985张图片 总计:9834张图片 • 训练集:4923张图片 • 验证集:3926张图片 • 测试集:985张图片 • 总计:9834张图片 • 分类类别: 床 椅子 沙发 灭火器 人 盆栽植物 冰箱 桌子 垃圾桶 电视 • 床 • 椅子 • 沙发 • 灭火器 • 人 • 盆栽植物 • 冰箱 • 桌子 • 垃圾桶 • 电视 • 标注格式:YOLO格式,包含实例分割的多边形标注,适用于实例分割任务。 • 数据格式:图片为常见格式如JPEG或PNG。 二、适用场景 • 实例分割模型开发:适用于训练和评估实例分割AI模型,用于精确识别和分割室内环境中的物体,如家具、电器和人物。 • 智能家居与物联网:可集成到智能家居系统中,实现自动物体检测和场景理解,提升家居自动化水平。 • 机器人导航与交互:支持机器人在室内环境中的物体识别、避障和交互任务,增强机器人智能化应用。 • 学术研究与教育:用于计算机视觉领域实例分割算法的研究与教学,助力AI模型创新与验证。 三、数据集优势 • 类别多样性:涵盖10个常见室内物体类别,包括家具、电器、人物和日常物品,提升模型在多样化场景中的泛化能力。 • 精确标注质量:采用YOLO格式的多边形标注,确保实例分割边界的准确性,适用于精细的物体识别任务。 • 数据规模充足:提供近万张标注图片,满足模型训练、验证和测试的需求,支持稳健的AI开发。 • 任务适配性强:标注格式兼容主流深度学习框架(如YOLO系列),便于快速集成到实例分割项目中,提高开发效率。
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符  | 博主筛选后可见
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值