Online DBA

<<Back to Oracle ASM Main Page Where is my Data on the Disk In this post I will show you, how you can trace your data from Database to disk where it is stored and how you can read it directly from disk So let us quickly setup the environment Step1> Login to DB Instance and Create a Tablespace SQL>create tablespace TRACE_DATA datafile '+TEST_DATA'; Step2> Find File# and Name of The Datafile SQL> col "File" for a80 select f.FILE#, f.NAME "File", t.NAME "Tablespace" from V$DATAFILE f, V$TABLESPACE t where t.NAME='TRACE_DATA' and f.TS# = t.TS#; Step3> Create A Table in  TRACE_DATA Tablespace and Insert few Records SQL>create table DATA_TRACE_TEST (n number, name varchar2(16)) tablespace TRACE_DATA; SQL>insert into DATA_TRACE_TEST values (1, 'CREDITCARD'); SQL>insert into DATA_TRACE_TEST values (2, 'DEBITCARD'); SQL> commit; Step4> Find the Information of the Inserted R...

<<Back to Oracle Main Page ORA-00845 Raised While Starting the DB Instance DB AlertLog Extract Followings is recorded in the database Alertlog   WARNING: You are trying to use the MEMORY_TARGET feature. This feature requires the /dev/shm file system to be mounted for at least 2147483648 bytes. /dev/shm is either not mounted or is mounted with available space less than this size. Please fix this so that MEMORY_TARGET can work as expected. Current available is 2090700800 and used is 1694498816 bytes. Ensure that the mount point is /dev/shm for this directory. memory_target needs larger /dev/shm Cause The new Automatic Memory Management functionality uses /dev/shm on Linux for SGA and PGA management. The errors occur if either MEMORY_TARGET or MEMORY_MAX_TARGET is configured larger than the configured /dev/shm size, or if /dev/shm is mounted incorrectly. Investigation Checked if /dev/shm is mounted # /cd dev/shm # df -h . Filesystem      S...

<<Back to Oracle Main Page Database Alertlog is Flooded with Trace File After DB Restart After restart of the database I noticed today that the database alertlog is being flooded with trace files Extract of Database Alert Log =========================================================== Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_ora_88103.trc: Thu Aug 09 10:37:42 2018 Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_ora_88103.trc: Thu Aug 09 10:37:54 2018 Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_ora_88103.trc: Thu Aug 09 10:38:07 2018 Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_ora_88103.trc: Thu Aug 09 10:38:57 2018 Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_ora_88103.trc: Thu Aug 09 10:39:15 2018 Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_ora_88103.trc: Thu Aug 09 10:39:31 2018 Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_...

<<Back to DB Administration Main Page CRS-2566: User 'dbatst1' does not have sufficient permissions to operate on resource 'ora.driver.afd', Log Extract CRS-2566: User 'dbatst1' does not have sufficient permissions to operate on resource 'ora.driver.afd', [ 2018-08-06 11:26:46.919 CEST ] PRCR-1006 : Failed to add resource ora.wdtestdba.db for wdtestdba PRCR-1071 : Failed to register or update resource ora.wdtestdba.db CRS-2566: User 'dbatst1' does not have sufficient permissions to operate on resource 'ora.driver.afd', which is part of the dependency specification. [ 2018-08-06 11:26:51.541 CEST ] DBCA_PROGRESS : DBCA Operation failed. Cause  user ( 'dbatst1' ) or primary group (oinstall) does not have privilege on ora.driver.afd $ crsctl stat res ora.driver.afd -p |grep ACL ACL=owner:oragrid:rwx,pgrp:asmadmin:r-x,other::r--,user:oragrid:r-x Solution : Modify the afd driver resource group to database ...

<<Back to Ansible Main Page Creating Directories on Linux Using Ansible File Module With Item Command - name:  create dirs   become: True   file:     path: "{{ item }}"     state: directory     owner: oragrid     group: oinstall     mode: 0755   with_items:      - "{{ oracle_gh }}"   OR Without Item Command - name:  create dirs   become: True   file:     path: /u01/oragrid/12.2.0.1/grid     state: directory     owner: oragrid     group: oinstall     mode: 0755

<<Back to DB Administration Main Page /u01/oragrid/12.2.0.1/grid/lib/libclntshcore.so.12.1: file too short $ ./asmcmd Error: /u01/oragrid/12.2.0.1/grid/lib/libclntshcore.so.12.1: file too short at /u01/oragrid/12.2.0.1/grid/bin/asmcmdcore line 300.  at /u01/oragrid/12.2.0.1/grid/bin/asmcmdcore line 301. Cause The installation has been done with -ignorePrereq option Solution 1> Clean deinstall this oracle home Do ensure to run the cluster verification utility and fix all Warning and Failures reported by cluvfy utility and re-run the installation you can run  cluvfy for single instance as shown below $GRID_HOME//runcluvfy.sh stage -pre hacfg and for RAC $GRID_HOME//runcluvfy.sh stage -pre crsinst -n node1,node......noden Note:(node1,node2...noden are the list of RAC nodes)

<<Back to Exadata Main Page Exadata The disk has been confined and is in an offline state Error Description Data hard disk entered confinement offline status. The LUN 0_7 changed status to warning - confinedOffline. CellDisk changed status to normal - confinedOffline. All subsequent I/Os on this disk are failed immediately. Confinement tests will be run on the disk to determine if the disk should be dropped Checked the AlerHistory from the Cell # cellcli -e list alerthistory          2_1     2018-07-27T01:56:15+02:00       warning         "Data hard disk entered confinement offline status. The LUN 0_7 changed status to warning - confinedOffline. CellDisk changed status to normal - confinedOffline. All subsequent I/Os on this disk are failed immediately. Confinement tests will be run on the disk to determine if the disk should be dropped. St...