数据库无法关闭及启动(ora-24324,ora-01089)
oracle@hostname $sqlplus / as sysdbaSQL*Plus: Release 10.2.0.2.0 - Production on Wed Aug 19 10:39:10 2009Copyright (c) 1982, 2005, Oracle. All Rights Reserved.Connected.SQL> startup nomount;ORA-01081: cannot start already-running ORACLE - shut it down firstSQL> shutdown immediate;ORA-24324: service handle not initializedORA-24323: value not allowedORA-01089: immediate shutdown in progress - no operations are permittedSQL> shutdown abort;ORA-01031: insufficient privilegesSQL> exitDis
Unable to create a new central inventory at location.....
when upgrade db from 10.2.0.1 to 10.2.0.4 on redhat es4 64bit get error "Unable to create a new central inventory at location....."no found /etc/oraInst.loc in /etc,but found it in /oracle/oraInventory then:#cd /etc #ln -s /oracle/oraInventory/oraInst.loc oraInst.loc re-install the patchset ok.[@more@]
zt: windows2003管理(SP2-1503)
windows2003服务器的一个普通用户不能正常启动sqlplus SP2-1503: Unable to initialize Oracle call interface SP2-0152: ORACLE may not be functioning properl 下面的操作可以解决上面的问题。 Assign the "Create global objects" user right to the non-Administrator account. 1. Click Start, point to Programs, point to Administrative Tools, and then click Local Security Policy. 2. Expand Local Policies, and then click User Rights Assignment. 3. In the right pane, double-click Create global objects.
TNS-12537, TNS-12560, TNS-00507的处理
服务器在更新IP重启后发现listener无法启动,发生报错TNS-12537, TNS-12560, TNS-00507 ,检查配置正常,新建一个listener也一样.$ lsnrctl startLSNRCTL for HPUX: Version 10.2.0.4.0 - Production on 11-JUL-2009 10:16:59Copyright (c) 1991, 2004, Oracle. All rights reserved.Starting /db02/product/10.1/bin/tnslsnr: please wait...TNS-12537: TNS:connection closedTNS-12560: TNS:proto adapter errorTNS-00507: Connection closed检查/etc/hosts发现127.0.0.1 localhost.domain localhost这行已不存在.在system administrator修
关于AWR的几个知识点
从网上摘录关于AWR的一些知识点要使用AWR必须设置STATISTICS_LEVEL参数,共有三个:BASIC、TYPICAL、ALL。Oracle 10g后,默认值是TYPICAL。查看默认参数设置:select snap_interval, retention from dba_hist_wr_control;默认情况为AWR的统计数据保留7天,并且每小时获取一次快照。Oracle 10g提供以下命令可以修改快照收集时间间隔和保存时间:execute dbms_workload_repository.modify_snapshot_settings(interval => 20, retention => 10080);以上命令修改为每20分钟收集一次并保留七天。可以为AWR数据创建baseline,保存这些数据
RAC数据库COPY到单实例的测试环境
场景: RAC(10.2.0.2)生产数据库要复制一份到测试环境的单实例.并改变dbname(proddb->uatdb)步骤:1.热备RAC其中一个节点.2.将热备文件移到UAT对应的目录,以下步骤均在UAT上执行3.sqlplus / as sysdba alter system set db_name='proddb' scope=spfile; shutdown immediate startup mount;4.用命令alter database rename file将数据文件/在线重做日志文件目录改为UAT下对应的目录5.检查文件路径是否正确select name from v$datafile ; select name from v$tempfile; select member from v$logfile ;6.在sqlplus中执行 recover da
遇到Bug 5928612
上了QUEST监控数据库软件,遇到第二个database bug,即Bug 5928612,Performance Analysis无法在历史中看到dbms_job所发出的SQL语句,即发现了某时段SQL执行异常也无法获得具体的SQL语句,反而只能用AWR/ADDM来取得当时的Top语句.目前数据库版本为10.2.0.2,需要升级到10.2.0.4以上.DescriptionIf a job is run through DBMS_JOB then the columnsSQL_ADDRESS and SQL_HASH_VALUE are not populated in V$SESSION which can hinder performance monitoring.(the columns show as 0). A similar issue exists for DBMS_SCHEDULER under <Bug:5
遇到BUG:5103658
背景说明: spotlight以RAC方式连接XDB数据库时产生连接成功后即中断,spotlight无法正常以RAC方式监控XDB; 但能以RAC方式监控同样平台,同样版本的另一个RAC数据库.分析:根据连接时产生的错误提示ORA-03113: end-of-file on communication channel, 并在alert数据库报警日志文件中产生trc文件及ORA-07445: exception encountered: core dump [] [] [] [] [] []错误提示. Trc文件中发现:*** 2009-03-03 15:44:47.458ksedmp: internal or fatal errorORA-07445: 鍑虹幇寮傚父閿欒?: 鏍稿績杞?偍 [] [] [] [] [] []Current SQL state
install db2v8 on linux
[root@linuxb local]# groupadd db2grp1[root@linuxb local]# groupadd db2fgrp1[root@linuxb local]# groupadd dasadm1[root@linuxb local]# useradd db2inst1 -g db2grp1[root@linuxb local]# useradd db2fenc1 -g db2fgrp1[root@linuxb local]# useradd dasusr1 -g dasadm1[root@linuxb local]# passwd db2inst1[root@linuxb local]# passwd db2fenc1[root@linuxb local]# passwd dasusr1http://he.fi/bchunk/[root@linuxb db2inst1]# rpm -ivh bchunk-1.2.0-0.i386.rpm[root@linuxb db2]# bchunk IBM.DB2.Enterprise.Edition.v8.2.Lin
db2表空间状态为0x4080
问题描述:用户报应用无法访问,开发发现连接数据库异常进入OS,发现DB2已经crash,发出命令db2start,数据库启动,用户连接测试成功,但无法查询表,检查表空间发现数据/索引表空间状态为0x4080,rollforward pending.而用户临时表空间状态为0x4000db2 list tablespaces show detail|grep State执行:db2 "rollforward database ips3 to end of logs and stop tablespace (dataspace,idxspace,datasystmp) online"这几个表空间状态恢复正常,再检查用户临时表空间:db2 list tablespace containers for 6ls -rlt /dev/rlvdatautmp发现文件
db2更新大表
当更新一个大表,可能导致错误:DB21034E The command was processed as an SQL statement because it was not avalid Command Line Processor command. During SQL processing it returned:SQL0964C The transaction log for the database is full. SQLSTATE=57011可能的原因:1、事务过大,导致所有的日志文件都满,此时解决方法有:1)加大日志文件数量或容量2)在事务中对大表执行关闭日志操作db2 +c "alter table ods.table1 activate not logged initially"db2 +c "update ods.table1 set col1=''"两条命令要在