kill MSAS session

sometimes BPC server has some dead loop mdx query that run a few hours, make the server cpu 90% busy, and active thread is more than 9. to identify those dead loop mdx sessions, run the following mdx query.

select session_connection_id,session_user_name,
session_start_time ,session_last_command_start_time as cmd_start_time,session_last_command_end_time as cmd_end_time,
session_last_command_elapsed_time_ms as cmd_elapsed_time_ms,session_idle_time_ms,session_last_command FROM $SYSTEM.DISCOVER_SESSIONS

pay attention to those that have 0 session_idle_time_ms and big cmd_elapsed_time_ms, pick up there connection_id and kill them.

to kill the sesion, run
(Cancel xmlns="http://schemas.microsoft.com/analysisservices/2003/engine")
(ConnectionID)
replace_with_id_number
(/ConnectionID)
(/Cancel)

Comments

Opatch apply/lsinventory error: oneoff is corrupted or does not exist

I am applying the quarterly patch for 19c RDBMS, I tried using napply but failed, but somehow it corrupted the inventory though nothing applied. further apply and lsinventory command ran into error like this: $ ./OPatch/opatch lsinventory Oracle Interim Patch Installer version 12.2.0.1.21 Copyright (c) 2020, Oracle Corporation. All rights reserved. Oracle Home : /u02/app/oracle/19.0.0 Central Inventory : /u01/app/oraInventory from : /u02/app/oracle/19.0.0/oraInst.loc OPatch version : 12.2.0.1.21 OUI version : 12.2.0.7.0 Log file location : /u02/app/oracle/19.0.0/cfgtoollogs/opatch/opatch2020-09-08_13-35-59PM_1.log Lsinventory Output file location : /u02/app/oracle/19.0.0/cfgtoollogs/opatch/lsinv/lsinventory2020-09-08_13-35-59PM.txt -------------------------------------------------------------------------------- Inventory load failed... OPatch cannot load inventory ...

oracle dba_hist_sysmetric_summary

found this blog is helpful to get CPU and IO statistics on oracle database. http://shob-dbadmin.blogspot.ca/2012/12/how-to-find-total-io-of-database.html courtesy to Shomil Bansal , below are hist writing, not mine. How to find total IO of the database instance Total IO of database instance is sum of the physical reads, physical writes and redo writes. There are several views to find these values. v$sysmetric - Reports metric values for only the most current time sample 60 secs. v$sysmetric_summary - Reports metric values for time sample of 1 hour. v$sysmetric_history - Reports metric values every 60 sec from the time instance is up. Better way to analyse IO using this view to take deltas between two time periods. dba_hist_sysmetric_history - All the above views are refreshed when the instance is restarted. This view, part of AWR, stores the historical stats. I have used this view for my report. Query: ====== set lines 350...

Oracle ASM DISK IO performance

Oracle OEM show a chart of disk performance, as shown in the chart below. when the OEM target database is 10gr2, the number of average disk response time (ms) is 0.01 ms, which unreasonable low. when the target database is 11gr2, the number is about 10ms, which I think is reasonable. it's time to find out where the discrepency comes from. The backend query is this one: set linesize 200 col name format a9 col path format a19 --col MB_per_sec format select t3.name,t2.name,t2.path,t2.reads,t2.read_time,round(t2.read_time/t2.reads*1000,3) rd_rspd_ms,t2.writes,round(t2.write_time/t2.writes*1000,3) wr_rspd_ms, round((t2.read_time+t2.write_time)/(t2.reads+t2.writes)*1000,3) dsk_rspd_ms,round((t2.bytes_read+t2.bytes_written)/1024/1024/(t2.read_time+t2.write_time)) MB_per_sec from V$asm_disk t2, v$asm_diskgroup t3 where t3.group_number=t2.group_number order by 1,2 / NAME NAME PATH ...

DBA

Search This Blog