Procwatcher: Script to Monitor and Examine Oracle DB and Clusterware Processes

最新推荐文章于 2021-12-10 11:21:03 发布
转载 最新推荐文章于 2021-12-10 11:21:03 发布 · 807 阅读 · 0

Procwatcher是一款用于监控Oracle数据库及集群进程的工具，能够收集进程堆栈跟踪和SQL数据，适用于解决会话级挂起、性能问题及内存管理等场景。本文档详细介绍了其安装要求、适用场景及命令操作。

 

 

Purpose

Procwatcher is a tool to examine and monitor Oracle database and/or clusterware processes at an interval.   The tool will collect stack traces of these processes using Oracle tools like oradebug short_stack and/or OS debuggers like pstack, gdb, dbx, or ladebug and collect SQL data if specified.

 

Requirements

  • Must have /bin and /usr/bin in your $PATH
  • Have your instance_name or db_name set in the oratab and/or set the $ORACLE_HOME env variable.(PRW searches the oratab for the SID it finds and if it can't find the SID in the oratab it will default to $ORACLE_HOME). Procwatcher cannot function properly if it cannot find an $ORACLE_HOME to use.
  • Run Procwatcher as the oracle software owner if you are only troubleshooting homes/instances for that user. If you are troubleshooting clusterware processes (EXAMINE_CLUSTER=true or are troubleshooting for multiple oracle users) run as root.
  • If you are monitoring the clusterware you must have the relevant OS debugger installed on your platform; PRW looks for:

Linux - /usr/bin/gdb
HP-UX and HP Itanium - /opt/langtools/bin/gdb64 or /usr/ccs/bin/gdb64
Sun - /usr/bin/pstack
IBM AIX - /bin/procstack or /bin/dbx
HP Tru64 - /bin/ladebug

 

 

Procwatcher is Ideal for:

  • Session level hangs or severe contention in the database/instance. See Note: 1352623.1
  • Severe performance issues. See Note: 1352623.1
  • Instance evictions and/or DRM timeouts.
  • Clusterware or DB processes stuck or consuming high CPU (must set EXAMINE_CLUSTER=true and run as root for clusterware processes)
  • ORA-4031 and SGA memory management issues. (Set sgamemwatch=diag or sgamemwatch=avoid4031 (not the default). See Note: 1355030.1
  • ORA-4030 and DB process memory issues. (Set USE_SQL=true and process_memory=y).
  • RMAN slowness/contention during a backup. (Set USE_SQL=true and rmanclient=y).

Procwatcher is Not Ideal for...

  • Node evictions/reboots. In order to troubleshoot these you would have to enable Procwatcher for a process(es) that are capable of rebooting the machine. If the OS debugger suspends the processs for too long *that* could cause a reboot of the machine. I would only use Procwatcher for a node eviction/reboot if the problem was reproducing on a test system and I didn't care of the node got rebooted. Even in that case the INTERVAL would need to be set low (30) and many options would have to be turned off to get the cycle time low enough (EXAMINE_BG=false, USE_SQL=false, probably removing additional processes from the CLUSTERPROCS list).
  • Non-severe database performance issues. AWR/ADDM/statspack are better options for this...
  • Most installation or upgrade issues. We aren't getting data for this unless we are at a stage of the installation/upgrade where key processes are already started.

 

Procwatcher User Commands

To start Procwatcher:

./prw.sh start



Or if you want to start on all nodes in a clustered environment:

./prw.sh start all




To stop Procwatcher: :

./prw.sh stop



Or if you want to stop on all nodes in a clustered environment:

./prw.sh stop all



To check the status of Procwatcher:

./prw.sh stat

 

To package up Procwatcher files to upload to support:

./prw.sh pack



All user syntax available:

./prw.sh help

 

（第78天）DB RU 补丁升级：19C 升级到 19.22
LuciferLiu_DBA
03-24 618
目前 Oracle 19C 是最新的稳定支持的版本，生产环境中使用的越来越多。当然，随着客户使用量的增多，自然无可避免的产生了很多 BUG，Oracle 每季度都会发布一个 RU 补丁来修复当前季度所产生的一些重要 BUG 补丁。作为 DBA，DB 补丁修复必然是需要掌握的一项技能。本文将介绍如何将数据库升级到最新的 RU 版本。
【0036】 pg_ctl启动服务报错：stopped waiting， pg_ctl: could not start server，Examine the log output.
Postgres 数据库内核开发工程师
05-06 8171
文章目录1. pg_ctl启动服务报错2. 解决方案 1. pg_ctl启动服务报错     当使用pg_ctl命令启动服务时，如下： su postgres -c '/usr/local/xxxx/bin/pg_ctl -D /home/soft/xxxx/DATA -m fast start'     有时会遇到终端错误信息提示，并且服务无法起来（ps -eLf|grep postgres）。其打印的错误信息如下： 2021-05-06 16:03:34.051 GMT [128363] DEBUG:
Procwatcher: Script to Monitor and Examine Oracle DB and Clusterware Processes (文档 ID 459694.1)
weixin_30367873的博客
08-05 161
Applies to: Oracle Database - Enterprise Edition - Version 10.2.0.2 to 12.1.0.1 [Release 10.2 to 12.1] Linux x86 HP-UX PA-RISC (64-bit) IBM AIX on POWER Systems (64-bit) Oracle Solaris on SPARC (64-...
Procwatcher: Script to Monitor and Examine DB and Clusterware Pro-459694.1
10-30 182
Procwatcher: Script. to Monitor and Examine Oracle DB and Clusterware Processes (文档 ID 459694.1)In this ...
MOS：Master Note for Real Application Clusters (RAC) Oracle Clusterware and Oracle Grid Infrastructur
Zhong Weicheng Study Notes
03-21 3746
Master Note for Real Application Clusters (RAC) Oracle Clusterware and Oracle Grid Infrastructure RAC Best Practice and Starter Kit Information The goal of the Oracle Real Application Clusters (RA
RAC Assurance Support Team: RAC and Oracle Clusterware Starter Kit and Best Practices (Generic) [ID
07-20 1543
RAC Assurance Support Team: RAC and Oracle Clusterware Starter Kit and Best Practices (Generic) [ID 810394.1] Modified 09-FEB-2011     Type
oracle 诊断利器之一—Procwatcher
我的Oracle DBA之路
01-07 1091
http://www.killdb.com/2011/10/16/oracle-诊断利器之一-procwatcher.html 今天有人问道，是否有工具来收集系统的诊断信息呢？比如收集crs进程的？ 收集某个进程的cpu或内存消耗等等？虽然可以通过shell脚本在实现，但是 oracle其实提供了这样的工具的，那就是Procwatcher，该工具，大家可以从MOS上下载， 那么这个功能是干什
Master Note: How to diagnose Database Performance - FAQ [ID 402983.1]
沉淀
05-10 852
如何利用oracle工具诊断性能问题，这篇问题起到提纲的作用，可以根据文中提到的方法，顺藤摸瓜，确定并解决问题
CRS 诊断数据收集：常见工具及其用法摘要 (Doc ID 1526158.1)
u010692693的专栏
11-19 768
适用于: Oracle Database - Enterprise Edition - 版本 10.2.0.1 到 11.2.0.3 [发行版 10.2 到 11.2] 本文档所含信息适用于所有平台 用途 本文档提供了用于诊断 CRS/GRID 问题的工具的快速指南。 适用范围 本文档的目标受众是需要诊断 CRS/Grid Infrastructure 问题的
Troubleshooting 'cursor: pin S wait on X' waits. (文档 ID 1349387.1)
mybluetiankong的专栏
01-04 949
In this Document   Purpose   Troubleshooting Steps   What is a 'Cursor: pin S wait on X' wait?   What causes 'Cursor: pin S wait on X' waits?
Troubleshooting 'library cache: mutex X' Waits. (文档 ID 1357946.1)
热门推荐
badman250的专栏
03-16 3万+
PURPOSE The purpose of the article is to help troubleshoot contention for the wait event 'library cache: mutex X'. TROUBLESHOOTING STEPS What is a 'library cache: mutex X' wait? The mutex feat
【论文笔记】Crop phenotyping in a context of Global Change: what to measure and how to do it
crush111的博客
12-10 1079
【论文笔记】Crop phenotyping in a context of Global Change: what to measure and how to do it 全球变化背景下的作物表型：测什么&如何去做 1.摘要： High-throughput crop phenotyping, particularly under field conditions, is nowadays perceived as a key factor limiting crop genetic advan
umbraco.examine.linq:LINQ to Lucene Umbraco的查询提供程序
04-30
umbraco.examine.linq已发布为“ Linq To Examine” 什么是Linq要检查的？ 该项目允许您根据自己的类使用LINQ查询Lucene索引。 该项目带有一个基本的Result类，使您可以直接使用它。 您可以在此处查看演示： : #...
语音分离基于平均谐波结构建模的无监督单声道音乐声源分离（Matlab代码实现）
01-01
【语音分离】基于平均谐波结构建模的无监督单声道音乐声源分离（Matlab代码实现）内容概要：本文介绍了基于平均谐波结构建模的无监督单声道音乐声源分离方法，并提供了相应的Matlab代码实现。该方法通过对音乐信号中的谐波结构进行建模，利用音源间的频率特征差异，实现对混合音频中不同乐器或人声成分的有效分离。整个过程无需标注数据，属于无监督学习范畴，适用于单通道录音场景下的语音与音乐分离任务。文中强调了算法的可复现性，并附带完整的仿真资源链接，便于读者学习与验证。; 适合人群：具备一定信号处理基础和Matlab编程能力的高校学生、科研人员及从事音频处理、语音识别等相关领域的工程师；尤其适合希望深入理解声源分离原理并进行算法仿真实践的研究者。; 使用场景及目标：①用于音乐音频中人声与伴奏的分离，或不同乐器之间的分离；②支持无监督条件下的语音处理研究，推动盲源分离技术的发展；③作为学术论文复现、课程项目开发或科研原型验证的技术参考。; 阅读建议：建议读者结合提供的Matlab代码与网盘资料同步运行调试，重点关注谐波建模与频谱分解的实现细节，同时可扩展学习盲源分离中的其他方法如独立成分分析（ICA）或非负矩阵分解（NMF），以加深对音频信号分离机制的理解。
python餐厅点餐系统（代码+数据库+LW）
01-01
摘 要 如今社会上各行各业，都喜欢用自己行业的专属软件工作，互联网发展到这个时候，人们已经发现离不开了互联网。新技术的产生，往往能解决一些老技术的弊端问题。因为传统餐厅点餐信息管理难度大，容错率低，管理人员处理数据费工费时，所以专门为解决这个难题开发了一个餐厅点餐系统，可以解决许多问题。 餐厅点餐系统实现的功能包括菜品类型管理，菜品信息管理，轮播图管理以及对已完成，未支付，已取消，已支付，已退款等状态的订单进行管理等功能。该系统采用了Mysql数据库，Python语言等技术进行编程实现。 餐厅点餐系统可以提高餐厅点餐信息管理问题的解决效率，优化餐厅点餐信息处理流程，保证餐厅点餐信息数据的安全，它是一个非常可靠，非常安全的应用程序。 关键词：餐厅点餐系统；Mysql数据库；Python语言
【智能汽车技术】基于线控与域控的智能底盘系统架构：新能源汽车滑板底盘创新形态及实车测试验证
01-01
内容概要：本文系统介绍了新能源汽车领域智能底盘技术的发展背景、演进历程、核心技术架构及创新形态。文章指出智能底盘作为智能汽车的核心执行层，通过线控化（X-By-Wire）和域控化实现驱动、制动、转向、悬架的精准主动控制，支撑高阶智能驾驶落地。技术发展历经机械、机电混合到智能三个阶段，当前以线控转向、线控制动、域控制器等为核心，并辅以传感器、车规级芯片、功能安全等配套技术。文中还重点探讨了“智能滑板底盘”这一创新形态，强调其高度集成化、模块化优势及其在成本、灵活性、空间利用等方面的潜力。最后通过“2025智能底盘先锋计划”的实车测试案例，展示了智能底盘在真实场景中的安全与性能表现，推动技术从研发走向市场验证。; 适合人群：汽车电子工程师、智能汽车研发人员、新能源汽车领域技术人员及对智能底盘技术感兴趣的从业者；具备一定汽车工程或控制系统基础知识的专业人士。; 使用场景及目标：①深入了解智能底盘的技术演进路径与系统架构；②掌握线控技术、域控制器、滑板底盘等关键技术原理与应用场景；③为智能汽车底盘研发、系统集成与技术创新提供理论支持与实践参考。; 阅读建议：建议结合实际车型和技术标准进行延伸学习，关注政策导向与行业测试动态，注重理论与实车验证相结合，全面理解智能底盘从技术构想到商业化落地的全过程。
【顶级EI复现】计及连锁故障传播路径的电力系统 N-k 多阶段双层优化及故障场景筛选模型（Matlab代码实现）
最新发布
01-01
【顶级EI复现】计及连锁故障传播路径的电力系统 N-k 多阶段双层优化及故障场景筛选模型（Matlab代码实现）内容概要：本文介绍了名为《【顶级EI复现】计及连锁故障传播路径的电力系统 N-k 多阶段双层优化及故障场景筛选模型（Matlab代码实现）》的技术资源，重点围绕电力系统中连锁故障的传播路径展开研究，提出了一种N-k多阶段双层优化模型，并结合故障场景筛选方法，用于提升电力系统在复杂故障条件下的安全性与鲁棒性。该模型通过Matlab代码实现，具备较强的工程应用价值和学术参考意义，适用于电力系统风险评估、脆弱性分析及预防控制策略设计等场景。文中还列举了大量相关的科研技术支持方向，涵盖智能优化算法、机器学习、路径规划、信号处理、电力系统管理等多个领域，展示了广泛的仿真与复现能力。; 适合人群：具备电力系统、自动化、电气工程等相关背景，熟悉Matlab编程，有一定科研基础的研究生、高校教师及工程技术人员。; 使用场景及目标：①用于电力系统连锁故障建模与风险评估研究；②支撑高水平论文（如EI/SCI）的模型复现与算法验证；③为电网安全分析、故障传播防控提供优化决策工具；④结合YALMIP等工具进行数学规划求解，提升科研效率。; 阅读建议：建议读者结合提供的网盘资源，下载完整代码与案例进行实践操作，重点关注双层优化结构与场景筛选逻辑的设计思路，同时可参考文档中提及的其他复现案例拓展研究视野。
BUUCTF(Misc)解题过程[源码]
01-01
本文详细介绍了在BUUCTF(Misc)题目中解决FLAG问题的步骤。首先通过WinHex检查图片文件头和十六进制匹配情况，查找flag字符串或隐藏文件。若未找到，则使用StegSolve进行图像隐写分析，包括LSB隐写和图片叠加等方法。随后发现文件头为50 4b，将其保存为zip文件，但文件损坏。通过foremost文件分离成功获取文件，最终在WinHex中查看未知文件类型，得到flag{dd0gf4c3tok3yb0ard4g41n~~~}。整个过程展示了从图片中提取隐藏信息的多种技术手段。
计及需求侧响应日前、日内两阶段鲁棒备用优化(Matlab代码实现）
01-01
计及需求侧响应日前、日内两阶段鲁棒备用优化(Matlab代码实现）
examine and elaborate the answer in english
11-10
In SystemVerilog, there are several types of coverage used to assess the thoroughness of testing. ### Code Coverage - **Line Coverage**: It ensures that each line of code in the design is executed at least once. For example: ```systemverilog module code_coverage_example; reg a, b, c; always @(*) begin c = a & b; // This line's execution is tracked by line coverage end endmodule ``` - **Branch Coverage**: Guarantees that all possible branches of conditional statements (such as if - else, case statements) are executed. ```systemverilog module branch_coverage; reg [1:0] sel; reg out; always @(*) begin if (sel == 2'b00) begin out = 1'b0; end else if (sel == 2'b01) begin out = 1'b1; end else begin out = 1'bx; end end endmodule ``` - **Condition Coverage**: Verifies all possible outcomes of conditional expressions in the design, ensuring that all possible value combinations of conditions are tested. ```systemverilog covergroup condition_cg @(posedge clk); cond_cover: coverpoint (condition1 && condition2); endgroup ``` ### Functional Coverage Functional coverage focuses on whether the functional features of the design are fully tested. It is defined based on the design's functional specifications. For example, for a processor, functional coverage may include the execution of the instruction set and testing of different operation modes. ```systemverilog covergroup functional_cg; opcode_cover: coverpoint cpu.opcode; mode_cover: coverpoint cpu.mode; endgroup ``` ### Assertion Coverage Assertion coverage is used to verify whether the assertions in the design are triggered. Assertions are statements used to check if the design behavior meets expectations. By assertion coverage, it can be ensured that assertions are correctly executed during testing. ```systemverilog module assertion_coverage; reg clk, rst; reg [7:0] data; always @(posedge clk) begin assert (data < 8'hFF) else $error("Data out of range"); end endmodule ``` ### Toggle Coverage Toggle coverage measures the state changes of signals during testing, ensuring that all possible signal transitions (from 0 to 1, from 1 to 0) are tested. ```systemverilog covergroup toggle_cg @(posedge clk); toggle_cover: coverpoint signal iff (enable) { bins rise = (0 => 1); bins fall = (1 => 0); } endgroup ``` ### Path Coverage Path coverage is used to verify the behavior of different signal paths in the design, ensuring that all possible signal propagation paths are tested. ```systemverilog module path_coverage; reg a, b, c, d; wire e, f; assign e = a & b; assign f = c | d; wire out = e ^ f; endmodule ``` ### Interface Coverage Interface coverage focuses on the usage of interfaces in the design, ensuring that all functions and protocols of the interface are fully tested. For example, for a bus interface, interface coverage may include different bus transaction types and address ranges. ```systemverilog covergroup interface_cg; transaction_type_cover: coverpoint bus_if.transaction_type; address_range_cover: coverpoint bus_if.address; endgroup ``` ### Transaction Coverage Transaction coverage is based on transactions in the design. It ensures that all possible transaction types and sequences are tested. For example, for a communication system, transaction coverage may include different message types and message lengths. ```systemverilog covergroup transaction_cg; message_type_cover: coverpoint comm_system.message_type; message_length_cover: coverpoint comm_system.message_length; endgroup ``` ### State Machine Coverage State machine coverage verifies the behavior of state machines, ensuring that all states and state transitions of the state machine are fully tested, which helps to check if the state machine performs state transitions correctly according to the design specifications and avoid issues such as state loss or illegal state transitions [^1]. ```systemverilog covergroup state_machine_cg @(posedge clk); state_transition: coverpoint state_machine.current_state -> state_machine.next_state; endgroup ``` ### Block Coverage Block coverage focuses on the execution of code blocks, ensuring that each code block (such as always blocks, tasks, functions) in the design is executed at least once. ```systemverilog covergroup block_cg; always_block_cover: coverpoint always_block_executed; task_cover: coverpoint task_executed; endgroup ``` ### Weighted Coverage Weighted coverage can be used to specify the proportion of a certain coverage point in the overall. For example, when covering a counter, the goal is to observe a range rather than collect all cases. In this case, option.weight = 0 can be set, which means that the coverage rate of this group or point is not calculated in the overall coverage statistics [^2]. ```systemverilog covergroup weighted_cg; coverpoint counter { option.weight = 5; bins small = {[0:10]}; bins medium = {[11:50]}; bins large = {[51:$]}; } endgroup ```
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值