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.

 

vnet: [ID 214931 kern.info] vnet0: vnet_addmac: programming macaddr(2:8:20:ad:ea:21) is not supported

November 10, 2015 Leave a comment

I created VNIC withing LDom Guest (devdbvm) by dladm create-vnic -l net0 vnic3, it showed failures and

Nov 10 11:21:58 devdbvm vnet: [ID 214931 kern.info] vnet0: vnet_addmac: programming macaddr(2:8:20:ad:ea:21) is not supported

Solution:

  1. Stop the guest

root@jecdb02:~# ldm stop -f devdbvm
LDom devdbvm stopped

2. Set mac-address of vnet with 8 X alt-mac-addres with command
root@jecdb02:~#  ldm set-vnet alt-mac-addrs=auto,auto,auto,auto,auto,auto,auto,auto vnet0 devdbvm

3. Show the binding

ldm list-bindings devdbvm

vnet0            primary-vsw0@primary        0    network@0  00:14:4f:fa:f8:68        1                         1500
00:14:4f:fa:6a:04
00:14:4f:f8:76:eb
00:14:4f:fa:de:4d
00:14:4f:fb:aa:d2
00:14:4f:fa:da:e2
00:14:4f:fb:9a:40
00:14:4f:fb:d3:6b
00:14:4f:fb:63:f5

4. Start the VM

Categories: LDom

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

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