Archive

Archive for the ‘ORA-XXX’ Category

cannot enable executable stack as shared object requires: Permission denied

March 20, 2017 Leave a comment

Symptoms

  1. Can’t automatically mount the filesystem

ora.acfsdg.vol1.acfs

OFFLINE ONLINE       testprdvm01            mounted on /utility_

files,STABLE

OFFLINE OFFLINE      testprdvm02            volume /utility_file

s offline,STABLE

2. Manually start by command srvctl

[root@testprdvm02 ~]# srvctl start filesystem -d /dev/asm/vol1-116

PRCR-1079 : Failed to start resource ora.acfsdg.vol1.acfs

CRS-5016: Process “/bin/mount” spawned by agent “ORAROOTAGENT” for action “start” failed: details at “(:CLSN00010:)” in “/u01/app/grid/diag/crs/testprdvm02/crs/trace/crsd_orarootagent_root.trc”

Error mounting file system ‘/dev/asm/vol1-116’ on ‘/utility_files’: /sbin/mount.acfs.bin: error while loading shared libraries: libclntsh.so.12.1: cannot enable executable stack as shared object requires: Permission denied

CRS-2674: Start of ‘ora.acfsdg.vol1.acfs’ on ‘testprdvm02’ failed

Fix:

Solution :
1. Open file /etc/selinux/config
2. change “SELINUX=enforcing” to “SELINUX=disabled”
3. Reboot

 

Categories: ORA-XXX, Uncategorized

ORA-00603: ORACLE server session terminated by fatal error

March 13, 2017 Leave a comment

Symptoms

  1. JDBC Client reported connection failure happened
  2. DB alert showed below errors at time the connection failure happened

mtype: 61 process 14042 failed because of a resource problem in the OS. The OS has most likely run out of buffers (rval: 4)
Errors in file /u02/oradiag/diag/rdbms/roamprd/roamprd1/trace/roamprd1_ora_14042.trc  (incident=29338):
ORA-00603: ORACLE server session terminated by fatal error
ORA-27504: IPC error creating OSD context
ORA-27300: OS system dependent operation:sendmsg failed with status: 105
ORA-27301: OS failure message: No buffer space available
ORA-27302: failure occurred at: sskgxpsnd2
opiodr aborting process unknown ospid (14042) as a result of ORA-603
2017-03-12 05:34:31.770000 +08:00
Sweep [inc][29338]: completed

Cause

High value of MTU for loop back adapter  on UEK3 causes the issue.

Fix

  1. Change loop back adapter MTU size

ifconfig lo mtu 16436

  1. Add MTU=16436 to /etc/sysconfig/network-scripts/ifcfg-lo
  2. Set vm.min_free_kbytes=32768 (32M)

 

Categories: ORA-XXX, Uncategorized

ORA-00392: log 1 of thread 1 is being cleared, operation not allowed

January 26, 2016 Leave a comment

Sympton

1. After restoring the backup of database from ASM to filesystem, it showed messages follows when opening the database with restlogs

SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-00392: log 1 of thread 1 is being cleared, operation not allowed
ORA-00312: online log 1 thread 1: ‘/u02/oradata/neprd6/redo01.log’

2. Check the database log status, it showed status of log files

SQL> select group#, status from

GROUP# STATUS
———- —————-
1 CLEARING_CURRENT
2 CLEARING
3 CLEARING
4 CLEARING
5 CLEARING
6 CLEARING_CURRENT
7 CLEARING
8 CLEARING
9 CLEARING

9 rows selected.

Fix:

  1. Clear the log manually SQL> alter database clear logfile group 1;

    Database altered.

    SQL> alter database clear logfile group 6;

    Database altered.

    SQL> select group#, status from v$log;

    GROUP# STATUS
    ———- —————-
    1 CURRENT
    2 CLEARING
    3 CLEARING
    4 CLEARING
    5 CLEARING
    6 CURRENT
    7 CLEARING
    8 CLEARING
    9 CLEARING

    9 rows selected.

  2. Start the database with resetlogs
    SQL> alter database open resetlogs;

    Database altered.

 

Error accessing package DBMS_APPLICATION_INFO

February 4, 2015 Leave a comment

After migrating oracle database from 7.3.4.0 to Oracle 12c1, some old oracle 7.3.4 clients showed the errors below

Error accessing package DBMS_APPLICATION_INFO
ERROR:
ORA-06550: line 1, column 40:
PLS-00553: character set name is not recognized
ORA-06550: line 0, column 0:
PL/SQL: Compilation unit analysis terminated

When asking oracle support, of course, they said that it was not support and upgraded to latest clients.Luckly, I found that it was caused by the database character set. After I recreated the database with the default characeter set  WE8MSWIN1252. The problem was fixed.

Categories: ORA-XXX

ORA-00845: MEMORY_TARGET not supported on this system

June 9, 2014 Leave a comment

Today, I tuned the memory_target to 8G on a 11g instance, it showed the errors above when it got restarted. It was caused by the tmpfs size.

[oracle@yhktamvmdb01 etc]$ df -h
Filesystem            Size  Used Avail Use% Mounted on
tmpfs                 7.8G  164K  7.8G   1% /dev/shm <– the size less than 8G.
/dev/sda1             485M   37M  423M   9% /boot

Then, I increased the size by the command below

[root@yhktamvmdb01 ~]# mount -t tmpfs shmfs -o size=12g /dev/shm

[root@yhktamvmdb01 ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
tmpfs                  12G     0   12G   0% /dev/shm <– the size increased to 12G

Start the database successfully

SQL> startup
ORACLE instance started.

Total System Global Area 8551575552 bytes
Fixed Size                  2270360 bytes
Variable Size            5049944936 bytes
Database Buffers         3489660928 bytes
Redo Buffers                9699328 bytes
Database mounted.
Database opened.

Make the change on the tmpfs permanently by editing the /etc/fstab as the following

tmpfs                   /dev/shm                tmpfs   size=12g        0 0

 

 

 

 

Categories: ORA-XXX

ORA-00031: session marked for kill

January 28, 2014 Leave a comment

1. Kill a session, returned the message below.

SQL>  alter system kill session ‘1022,851’;
alter system kill session ‘1022,851’
*
ERROR at line 1:
ORA-00031: session marked for kill

2. Find out the OS process id

SQL> select a.spid,b.sid,b.serial#,b.username from v$process a,v$session b where a.addr=b.paddr and b.status=’KILLED’;

SPID         SID           SERIAL# USERNAME
———— ———- ———- ——————————
15198        ##########        851 EHEALTH

3. Go to OS to find the server process

[oracle@yplodb02 ~]$ ps -ef|grep 15198
oracle   15198     1  1 Jan20 ?        03:41:07 oracleehealthp1 (LOCAL=NO)

oracle    9140 13829  0 15:38 pts/4    00:00:00 grep 15198

4. Kill it by OS command

[oracle@yplodb02 ~]$ kill -9 15198

[oracle@yplodb02 ~]$ ps -ef|grep 15198
oracle   12522 13829  0 15:38 pts/4    00:00:00 grep 15198

 

 

 

 

Categories: Administration, ORA-XXX

ORA-19504: failed to create file “+VOPDATA”

September 5, 2013 Leave a comment

Today, when I created a new database in silent mode, it failed and showed the messages below from ./dbca/voppro/voppro.log file

Copying database files
DBCA_PROGRESS : 1%
DBCA_PROGRESS : 3%
DBCA_PROGRESS : 9%
DBCA_PROGRESS : 15%
ORA-19624: operation failed, retry possible
ORA-19870: error while restoring backup piece /opt/oracle/product/11.2/db_2/assistants/dbca/templates/Seed_Database.dfb
ORA-19504: failed to create file “+VOPDATA”
ORA-15045: ASM file name ‘+VOPDATA’ is not in reference form
ORA-17502: ksfdcre:5 Failed to create file +VOPDATA
ORA-15081: failed to submit an I/O operation to a disk
ORA-06512: at “SYS.X$DBMS_BACKUP_RESTORE”, line 5827
ORA-06512: at line 20

DBCA_PROGRESS : 21%
DBCA_PROGRESS : 30%
Creating and starting Oracle instance
ORA-01503: CREATE CONTROLFILE failed
ORA-01565: error in identifying file ‘+VOPDATA/voppro/system01.dbf’
ORA-17503: ksfdopn:2 Failed to open file +VOPDATA/voppro/system01.dbf
ORA-15173: entry ‘voppro’ does not exist in directory ‘/’

ORA-01503: CREATE CONTROLFILE failed
ORA-01565: error in identifying file ‘+VOPDATA/voppro/system01.dbf’
ORA-17503: ksfdopn:2 Failed to open file +VOPDATA/voppro/system01.dbf
ORA-15173: entry ‘voppro’ does not exist in directory ‘/’

DBCA_PROGRESS : 100%

Cause

After checking, there was no permission on raw disks for oracle account to access  (For my case, the raw disks are /dev/rdsk/emcpower*)

Fix

1. Login all nodes as root

2. Change permission on all /dev/rdsk/emcpower* to 775

# cd /dev/rdsk

# chmod 775 emcpower*