Skip to main content

Posts

Showing posts from January, 2016

ORA-27102: out of memory Linux-X86_64 Error: 28: No space left on device

Upon startup of Linux database get ORA-27102: out of memory Linux-X86_64 Error: 28: No space left on device (Doc ID 301830.1) Issue: ====== ORA-27102: out of memory Linux-x86_64 Error: 28: No space left on device Solution: ========= 1. Ask SA to increase "kernel.shmall" in /etc/sysctl.conf     Formula:     RAM * 1024 * 1024 * 1024 / page_size     Ex:-     RAM = 50GB     $getconf PAGE_SIZE ==> 4096     50*1024*1024*1024/4096 = 13107200 ==> kernel.shmall 2. After updating kernel.shmall, ask SA to do "sysctl -p" to activate changes. 3. Start the DB Note: ==== Kernel values will be set in below files 1. Updating below files doesn't require system reboot.     /proc/sys/kernel/shmmax     /proc/sys/kernel/shmall     /proc/sys/kernel/shmmni     Usage:  # echo "536870912" > /proc/sys/kernel/shmmax       ...

CRS Upgrade from 11g to 12c

Complete Steps: ============= 1. Pre Health checks  Take following command output by login as ororacrs user to one of the CRS node     crs_stat -t     crs_stat -t |grep vip     crs_stat -t |grep ons     crsctl query crs activeversion     crsctl query crs softwareversion     ocrcheck     ocrcheck -config     crsctl query css votedisk     crsctl check crs     crsctl check cluster -all     crsctl stat res -t -init  2. Set black out and perform pre health checks  3. Stop services     Stop all web services        Stop all app services        Stop db services using following commands         login as ortest on one DB node only - and run:             $ORACLE_HOME/bi...

Oracle Database Upgrade from 11g to 12c Manually

Complete Steps: ============ Note: ------- Below Action Plan is for Non RAC DB, If it is RAC means, Upgrade the CRS to 12c and proceed with db upgrade. Only change is just disable the  cluster db parameter initially and enable back once upgrade complete. 1. Set the blackouts & perform pre Health Checks. 2. Backup the Database and File System.     2.1 Take Cold Backup.     2.2 Start up the DB only     2.3 Check for the integrity of the source database.             Note 556610.1  Script to Collect DB Upgrade/Migrate Diagnostic Information (dbupgdiag.sql)         If the dbupgdiag.sql script reports any invalid objects, run $ORACLE_HOME/rdbms/admin/utlrp.sql (multiple times) to validate the invalid objects in the database             until there is no change in the number of invalid objects. ...

VNC Display Issue

Issue: ======== >>> Could not execute auto check for display colors using command /usr/bin/xdpyinfo. Check if the DISPLAY variable is set.    Failed <<<< Fix: ==== Login as your user [user@host ~]$ xhost + 129.155.100.229 129.155.100.229 being added to access control list bash-4.1$ [user@host ~]$ Login as oracle user bash-4.1$ export DISPLAY=test.host.com:1.0 bash-4.1$ xhost + 100.100.100.100 129.155.100.229 being added to access control list bash-4.1$ xclock Warning: Missing charsets in String to FontSet conversion ^C bash-4.1$ pwd /oracrs/oracle bash-4.1$ id uid=11001(ororacrs) gid=11001(dboracrs) groups=11001(dboracrs),1001(dba) bash-4.1$ bash-4.1$ export DISPLAY=test.host.com:7.0 bash-4.1$ xhost + 100.100.100.100 129.155.100.229 being added to access control list bash-4.1$ xclock Warning: Missing charsets in String to FontSet conversion ^C bash-4.1$ #######################################################################

SQL Run Time

Historic SQL: =========== SELECT  SQL_ID,ELAPSED_TIME_TOTAL/60000000/60 "Hours Ran" FROM DBA_HIST_SQLSTAT WHERE SQL_ID='*****'  ORDER BY 2 DESC; Current SQL: ========== SELECT SQL_TEXT,ELAPSED_TIME/60000000/60 "Hours Taken" FROM v$sqlarea WHERE SQL_ID='*****';