SYSTEMSTATE DUMPs: An example of how to take and upload them [ID 125568.1]

Applies to:

Enterprise Manager for Oracle Database - Version: 8.1.7.4 and later [Release: and later ]
Oracle Server - Enterprise Edition - Version: 6.0.0.0 and later [Release: 6.0 and later]
Oracle Database Configuration Assistant - Version: 8.1.7 and later [Release: 8.1.7 and later]
Information in this document applies to any platform.

Purpose

To provide step by step instructions for taking system state dumps to assist database hanging/locking issues and to further provide instructions for
delivering the output for examination

Scope and Application

scope

SYSTEMSTATE DUMPs: An example of how to take and upload them

1) Get the process/procedure/query/command/database hung

2) Start SQLPLUS and connect as SYSDBA or SYSOPER

Prior to 11g

ALTER SESSION SET EVENTS 'IMMEDIATE TRACE NAME SYSTEMSTATE LEVEL 266';

11g and later

ALTER SESSION SET EVENTS 'IMMEDIATE TRACE NAME SYSTEMSTATE LEVEL 258';


If you cannot connect to the database to take the dump the following note may assist you in taking the dump

Note:121779.1 Taking Systemstate dumps when you cannot connect to Oracle

3) Exit SQLPLUS

4) Wait 5 minutes

5) Repeat steps 2-4 ... 2 more times

6) At this point you can do what is necessary to unhang the process

7) Locate the trace files (3) in the user_dump_dest

The user_dump_dest is defined in your parameter file or can be viewed by SHOW PARAMETER USER_DUMP_DEST

8) Upload the 3 trace files via My Oracle Support

NOTE :

If REAL APPLICATION CLUSTER (RAC) is being used ... it is strongly suggested that systemstates be done from each node ... after which ... they should be renamed to clearly indicate which node the dump originated from if it is not already clear by the file name

EXAMPLE:

sqlplus / as sysdba

SQL*Plus: Release 11.2.0.2.0 Production on Tue Oct 12 18:21:40 2010

Copyright (c) 1982, 2010, Oracle. All rights reserved.


Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> ALTER SESSION SET EVENTS 'IMMEDIATE TRACE NAME SYSTEMSTATE LEVEL 266';

Session altered.

SQL> show parameter user_dump_dest

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
user_dump_dest string /ora/ora_11.2.0.2/diag/rdbms/ora11202/ora11202/trace

SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

> cd /ora/ora_11.2.0.2/diag/rdbms/ora11202/ora11202/trace

> ls -alt

-rw-r----- 1 oracle oinstall 1461273 Oct 12 18:19 ora11202_ora_3915.trc
-rw-r----- 1 oracle oinstall 202940 Oct 12 18:19 ora11202_ora_3915.trm
drwxr-x--- 3 oracle oinstall 20480 Oct 12 18:19 .
-rw-r----- 1 oracle oinstall 194243 Oct 12 18:19 alert_ora11202.log
drwxr-xr-x 2 oracle oinstall 4096 Oct 11 16:06 cdmp_20101011160628
drwxr-x--- 15 oracle oinstall 4096 Sep 14 15:45 ..

> more ora11202_ora_3915.trc

Trace file /ora/ora_11.2.0.2/diag/rdbms/ora11202/ora11202/trace/ora11202_ora_391
5.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /ora/ora_11.2.0.2/11202
System name: Linux
Node name: filnx10
Release: 2.6.9-42.0.3.EL
Version: #1 Mon Sep 25 17:14:19 EDT 2006
Machine: i686
Instance name: ora11202
Redo thread mounted by this instance: 1
Oracle process number: 20
Unix process pid: 3915, image: oracle@filnx10 (TNS V1-V3)


*** 2010-10-12 18:19:39.705
*** SESSION ID:(1.7) 2010-10-12 18:19:39.705
*** CLIENT ID:() 2010-10-12 18:19:39.705
*** SERVICE NAME:(SYS$USERS) 2010-10-12 18:19:39.705
*** MODULE NAME:(sqlplus@filnx10 (TNS V1-V3)) 2010-10-12 18:19:39.705
*** ACTION NAME:() 2010-10-12 18:19:39.705
*** ACTION NAME:() 2010-10-12 18:19:39.705

===================================================
SYSTEM STATE (level=10, with short stacks)
------------
System global information:
processes: base 0x3f3bac6c, size 150, cleanup 0x3f3caa8c
allocation: free sessions 0x3e87927c, free calls (nil)
control alloc errors: 0 (process), 0 (session), 0 (call)
PMON latch cleanup depth: 0
seconds since PMON's last scan for dead processes: 49
system statistics:
0 OS CPU Qt wait time
40 logons cumulative
20 logons current
5281 opened cursors cumulative
29 opened cursors current
13 user commits
0 user rollbacks
114 user calls
31001 recursive calls
904 recursive cpu usage
10 pinned cursors current
....

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

转载于:http://blog.itpub.net/22308399/viewspace-750809/

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
图像识别技术在病虫害检测中的应用是一个快速发展的领域,它结合了计算机视觉和机器学习算法来自动识别和分类植物上的病虫害。以下是这一技术的一些关键步骤和组成部分: 1. **数据收集**:首先需要收集大量的植物图像数据,这些数据包括健康植物的图像以及受不同病虫害影响的植物图像。 2. **图像预处理**:对收集到的图像进行处理,以提高后续分析的准确性。这可能包括调整亮度、对比度、去噪、裁剪、缩放等。 3. **特征提取**:从图像中提取有助于识别病虫害的特征。这些特征可能包括颜色、纹理、形状、边缘等。 4. **模型训练**:使用机器学习算法(如支持向量机、随机森林、卷积神经网络等)来训练模型。训练过程中,算法会学习如何根据提取的特征来识别不同的病虫害。 5. **模型验证和测试**:在独立的测试集上验证模型的性能,以确保其准确性和泛化能力。 6. **部署和应用**:将训练好的模型部署到实际的病虫害检测系统中,可以是移动应用、网页服务或集成到智能农业设备中。 7. **实时监测**:在实际应用中,系统可以实时接收植物图像,并快速给出病虫害的检测结果。 8. **持续学习**:随着时间的推移,系统可以不断学习新的病虫害样本,以提高其识别能力。 9. **用户界面**:为了方便用户使用,通常会有一个用户友好的界面,显示检测结果,并提供进一步的指导或建议。 这项技术的优势在于它可以快速、准确地识别出病虫害,甚至在早期阶段就能发现问题,从而及时采取措施。此外,它还可以减少对化学农药的依赖,支持可持续农业发展。随着技术的不断进步,图像识别在病虫害检测中的应用将越来越广泛。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值