Oracle DBA Place

When Oracle Management Service (OMS) filesystem is 100% full, you may loose <oms_home>/sysman/config/emoms.properties Actually the file will remain empty with size of zero bytes. A small file that can cause Grid Control not to function.   emctl start oms . . . Could not find Console Server Port in /software/oracle/OEM10gR2 /oms10g/sysman/config/emoms .properties Oracle claims that you have to install a new OMS instead of the old one. (Notes: 418453.1, 418159.1) After some struggles looking for the undocumented syntax of the file, I managed to make OMS working again ;))   The lesson 1. Always BACKUP 2. Monitor the filesystem of OMS itself 3. Create some jobs for deleting old logs and unneeded archives. 4. Don't belive everything is written on Metalink.   Anyway, here is my file Enjoy :)   emoms.properties #Sun Apr 15 19:12:18 IDT 2007 oracle.sysman.emSDK.svlt .ConsoleServerName=jigles oracle.sysman.eml.mntr.emdRepPw d= write here an unen

As DBAs that working tightly with the operation system (OS), we need to know how to query the OS and its hardware. Usually we do it before fresh install, upgrade or migration of the DB/OS. Here is the first and basic commands, Later on I will go further more. Is my Operating System is 64-bit ? Linux: uname -m On 64-bit, you will get: x86_ 64 On 32-bit, you will get: i686 or similar HP: getconf KERNEL_BITS Solaris: /usr/bin/isainfo –kv On 64-bit, you will get: 64 -bit sparcv9 kernel modules On 32-bit, you will get: 32 -bit sparc kernel modules Checking whether current oracle installation is 32-bit or 64-bit. file $ORACLE_HOME/bin/oracle Linux: On 64-bit, you will get: oracle: setuid setgid ELF 64 -bit LSB executable, AMD x86-64, version 1 (SYSV), for GNU/Linux 2.4.0, dynamically linked (uses shared libs), not stripped On 32-bit, you will get: oracle: setuid setgid ELF 32 -bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.5, dynamically l

In oracle 10g we were introduced MMON process which collects metrics and statistics. No more complex queries for monitoring the database No more heavy load on the database done by our own monitoring scripts Just query one view or two. Of course that you can enhance this mechanism by changing the thresholds, push the alerts via mail... All of these can be done via SQL or by using Enterprise Manager/Database Console. Warning & critical threshold can be set by using DBMS_SERVER_ALERT package Thresholds definition can reviewed by using: SELECT object_name, metrics_name, warning_value, critical_value FROM dba_thresholds; Outstanding alerts can be reviewed by using: SELECT reason FROM dba_outstanding_alerts; When the alerts are cleared it can be reviewed by querying DBA_ALERT_HISTORY See: Using DBMS_SERVER_ALERT

Background: Migrating HP-UX oracle 9i to 10g On Linux RH4 using transportable tablespace to ASM The last step in this kind of procedure is to transfer the database file from filesystem to ASM using RMAN: RMAN> backup as copy tablespace TRANS_TEST format '+DATA/psdwh/datafile'; Starting backup at 22-FEB-07 using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: sid=136 devtype=DISK RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of backup command at 02/22/2007 14:06:40 RMAN-20202: tablespace not found in the recovery catalog RMAN-06019: could not translate tablespace name "TRANS_TEST" It looks like we are hit bug#2656503 (not published on Metalink) which states that rman does not recognizes plugged in tablespaces until they a

Background: Using ASM with asmlib by multipath software The Story: Restarted ASM instance for the first time: [loki:oracle@+ASM] /etc/init.d >su - Password: [root@loki ~]# /etc/init.d/oracleasm stop Unmounting ASMlib driver filesystem: [ OK ] Unloading module "oracleasm": [ OK ] [root@loki ~]# /etc/init.d/oracleasm start Loading module "oracleasm": [ OK ] Mounting ASMlib driver filesystem: [ OK ] Scanning system for ASM disks: [ OK ] [root@loki ~]# /etc/init.d/oracleasm scandisks Scanning system for ASM disks: [ OK ] [root@loki ~]# /etc/init.d/oracleasm listdisks PRDWH_DATA_1 PRDWH_DATA_2 [root@loki ~]# logout We got the following Error: [ loki:oracle@+ASM] /etc/init.d >sqlplus "/ as sysdba" SQL*Plus: Release 10.2.0.3.0 - Production on Mon Feb 26 13:47:13 2007 Copyright (c) 1982, 2006, Oracle. All Rights Reserved. Connected to an idle instance. SQL> startup ASM instance started Total System Global Area 130023424 bytes Fixed Size 2071000 bytes Vari