Archive

Archive for the ‘Uncategorized’ 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

 

Advertisements
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

DBCA, running on oracle zone, pops up “Out of Memory”

April 20, 2016 Leave a comment

Runing on oracle zone, dbca showed “out of memory”. It may caused by  setting sga size higher than the capped-memory: [ locked: 2G] in zone configuration.

capped-memory:
physical: 4G
[swap: 4G]
[locked: 2G]

Fix: Incraese the capped-memory :[locked: <value higer than SGA>]

 

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.

 

ORA-27054: NFS file system where the file is created or resides is not mounted with correct options

September 25, 2015 Leave a comment

Problem:

I duplicated a production to standby server by rman. It returned the messages below

ORA-27054: NFS file system where the file is created or resides is not mounted with correct options.

Solution

Since the backupset was located at NFS server, after changing mount options with ” rsize=32768,wsize=32768″, the problem was fixed.

Categories: Uncategorized

ORA-01157: cannot identify/lock data file 44 – see DBWR trace file

August 31, 2015 Leave a comment

Problems

  1. Application server showed java.sql.SQLException: ORA-01157: cannot identify/lock data file 44 – see DBWR trace file
  2. Node 2 of RAC was restarted 2 days ago and the diskgroups were umounted.
  3. But the corresponding tablespaces on the database were online
  4. And select file_name to show following errors

SQL> select file_name from dba_data_files;
ERROR:
ORA-01157: cannot identify/lock data file 44 – see DBWR trace file
ORA-01110: data file 44: ‘+DATA4/ispro/datafile/fttxwkf_tbs.1021.885226031’

Fixed

  1. Login ASM
  2. Mount the diskgroup
  3. The state of diskgroup were changed to mounted

SQL> select name, state from  v$asm_diskgroup;

NAME                           STATE
—————————— ———–
DATA1                          CONNECTED
DATA2                          MOUNTED
DATA3                          MOUNTED
DATA4                          MOUNTED

4. But select file_name, still show following errors

SQL> select file_name from dba_data_files;
ERROR:
ORA-01157: cannot identify/lock data file 44 – see DBWR trace file
ORA-01110: data file 44: ‘+DATA4/ispro/datafile/fttxwkf_tbs.1021.885226031’

5. Try online tablespace again by the following command, the problem got fixed since the state of DATA4 changed from MOUNTED to CONNECTED

SQL>  alter tablespace FTTXWKF_TBS online;

Tablespace altered.

SQL> select name, state from  v$asm_diskgroup;

NAME                           STATE
—————————— ———–
DATA1                          CONNECTED
DATA2                          MOUNTED
DATA3                          MOUNTED
DATA4                          CONNECTED

Categories: Uncategorized

sendmail show “domain.com: Name server timeout”

April 9, 2015 Leave a comment

After I setup sendmail relay on the Red Hat Enterprise Linux Server 5.5 based on some online docuements, it always tells the following steps

1. Change /etc/mail/sendmail.mc entry “dnl define(`SMART_HOST’, `smtp.your.provider’)dnl” to “define(`SMART_HOST’, `[mailserver1][mailserver2]’)dnl”

2. Remake the /etc/mail/sendmail.cf by the command make

3. Restart the sendmail services

# service sendmail restart

But when I did sendmail testing, it showed error below. I searched on the internet, there are no any workable clue.

domain.com: Name server timeout

… Transient parse error — message queued for future delivery

… queued

Finally, I found that the procedure for setup sendmail relay above, it assums that DNS has been setup. Therefore, if there is no DNS, extra setup procedures are required.

1. Uncomment the entry below in /etc/mail/submit.mc

define(`confDIRECT_SUBMISSION_MODIFIERS’,`C’)dnl

2. Create /etc/mail/service.switch with the content below

####### start of file #########
hosts files
aliases files
####### end of file ###########

3. Restart sendmail

Categories: Uncategorized