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 621
目前 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 8172
文章目录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 950
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类，使您可以直接使用它。 您可以在此处查看演示： : #...
【直流微电网保护】【本地松弛母线、光伏系统、电池和直流负载】【光伏系统使用标准的光伏模型+升压变换器】【电池使用标准的锂离子电池模型+双有源桥变换器】Simulink仿真实现
01-01
【直流微电网保护】【本地松弛母线、光伏系统、电池和直流负载】【光伏系统使用标准的光伏模型+升压变换器】【电池使用标准的锂离子电池模型+双有源桥变换器】Simulink仿真实现
成都市2019年人口分布矢量数据（SHP格式）及GIS分析方法
01-01
成都市作为中国西部地区具有战略地位的核心都市，其人口的空间分布状况对于城市规划、社会经济发展及公共资源配置等研究具有基础性数据价值。本文聚焦于2019年度成都市人口分布的空间数据集，该数据以矢量格式存储，属于地理信息系统中常用的数据交换形式。以下将对数据集内容及其相关技术要点进行系统阐述。 Shapefile 是一种由 Esri 公司提出的开放型地理空间数据格式，用于记录点、线、面等几何要素。该格式通常由一组相互关联的文件构成，主要包括存储几何信息的 SHP 文件、记录属性信息的 DBF 文件、定义坐标系统的 PRJ 文件以及提供快速检索功能的 SHX 文件。 1. **DBF 文件**：该文件以 dBase 表格形式保存与各地理要素相关联的属性信息，例如各区域的人口统计数值、行政区划名称及编码等。这类表格结构便于在各类 GIS 平台中进行查询与编辑。 2. **PRJ 文件**：此文件明确了数据所采用的空间参考系统。本数据集基于 WGS84 地理坐标系，该坐标系在全球范围内广泛应用于定位与空间分析，有助于实现跨区域数据的准确整合。 3. **SHP 文件**：该文件存储成都市各区（县）的几何边界，以多边形要素表示。每个多边形均配有唯一标识符，可与属性表中的相应记录关联，实现空间数据与统计数据的联结。 4. **SHX 文件**：作为形状索引文件，它提升了在大型数据集中定位特定几何对象的效率，支持快速读取与显示。 基于上述数据，可开展以下几类空间分析： - **人口密度评估**：结合各区域面积与对应人口数，计算并比较人口密度，识别高密度与低密度区域。 - **空间集聚识别**：运用热点分析（如 Getis-Ord Gi* 统计）或聚类算法（如 DBSCAN），探测人口在空间上的聚集特征。 - **空间相关性检验**：通过莫兰指数等空间自相关方法，分析人口分布是否呈现显著的空间关联模式。 - **多要素叠加分析**：将人口分布数据与地形、交通网络、环境指标等其他地理图层进行叠加，探究自然与人文因素对人口布局的影响机制。 2019 年成都市人口空间数据集为深入解析城市人口格局、优化国土空间规划及完善公共服务体系提供了重要的数据基础。借助地理信息系统工具，可开展多尺度、多维度的定量分析，从而为城市管理与学术研究提供科学依据。 资源来源于网络分享，仅用于学习交流使用，请勿用于商业，如有侵权请联系我删除！
20mm 高速钢立铣刀ENDMILL 20mm.SLDPRT
01-01
20mm 高速钢立铣刀ENDMILL 20mm.SLDPRT
【浏览器自动化测试】基于Playwright的OJ监控系统设计：实现竞赛平台7×24小时无人值守运维与性能基线预警
01-01
内容概要：本文介绍如何通过前端监控与浏览器自动化测试技术，构建7×24小时无人值守的OJ（在线判题）系统监控机器人，应用于计算机竞赛场景。核心包括使用Playwright实现多层级自动化测试（冒烟、回归、压测），结合Synthetics监控、Web Vital体验红线、K8s边缘节点部署及Prometheus/Grafana监控体系，实现从全球节点模拟真实选手操作、实时采集性能指标到自动告警与可视化分析的闭环。代码层面展示了Docker镜像构建、自动化脚本注入性能监听、推送指标至Pushgateway及K8s定时任务编排的完整流程。; 适合人群：具备前端开发、自动化测试或运维监控经验，熟悉Node.js、Kubernetes和Prometheus的技术人员，适用于教育机构、竞赛平台或企业级OJ系统的研发与运维团队； 使用场景及目标：①赛前大规模健康检查并生成健康度雷达图；②商业赛事中保障SLA服务等级；③赛后通过流量回放定位系统瓶颈；④实现告警降噪与根因快速定位； 阅读建议：建议结合文中提供的Dockerfile、Playwright脚本与K8s配置进行实践部署，重点关注Web Vital指标采集逻辑、多环境隔离策略及Grafana看板联动，深入理解“测试即代码、监控即服务”的云原生竞赛运维新模式。
elenium 的 Web 自动化测试实战项目的开发流程
01-01
自动化测试实战项目开发
【顶级EI复现】计及连锁故障传播路径的电力系统 N-k 多阶段双层优化及故障场景筛选模型（Matlab代码实现）
最新发布
01-01
【顶级EI复现】计及连锁故障传播路径的电力系统 N-k 多阶段双层优化及故障场景筛选模型（Matlab代码实现）内容概要：本文介绍了名为《【顶级EI复现】计及连锁故障传播路径的电力系统 N-k 多阶段双层优化及故障场景筛选模型（Matlab代码实现）》的技术资源，重点围绕电力系统中连锁故障的传播路径展开研究，提出了一种N-k多阶段双层优化模型，并结合故障场景筛选方法，用于提升电力系统在复杂故障条件下的安全性与鲁棒性。该模型通过Matlab代码实现，具备较强的工程应用价值和学术参考意义，适用于电力系统风险评估、脆弱性分析及预防控制策略设计等场景。文中还列举了大量相关的科研技术支持方向，涵盖智能优化算法、机器学习、路径规划、信号处理、电力系统管理等多个领域，展示了广泛的仿真与复现能力。; 适合人群：具备电力系统、自动化、电气工程等相关背景，熟悉Matlab编程，有一定科研基础的研究生、高校教师及工程技术人员。; 使用场景及目标：①用于电力系统连锁故障建模与风险评估研究；②支撑高水平论文（如EI/SCI）的模型复现与算法验证；③为电网安全分析、故障传播防控提供优化决策工具；④结合YALMIP等工具进行数学规划求解，提升科研效率。; 阅读建议：建议读者结合提供的网盘资源，下载完整代码与案例进行实践操作，重点关注双层优化结构与场景筛选逻辑的设计思路，同时可参考文档中提及的其他复现案例拓展研究视野。
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、付费专栏及课程。

余额充值