Another quick tip about running DBCA:
# Error:
[oracle@dbsrv database]$ ./runInstaller Starting Oracle Universal Installer... Checking installer requirements... All installer requirements met. Preparing to launch Oracle Universal Installer from /tmp/OraInstall2015-06-25_06-37-23PM. Please wait ...Error in CreateOUIProcess(): 13 : Permission denied
# Solution:
mount -t ext3 -o remount default /tmp
Ok doke?
Matheus.
Everything is old. RHEL and Database versions. But can be useful if you are preparing a nonprod lab of your legacy env, right?
Let’s see the problem:
[oracle@dbsrv database]$ ./runInstaller Starting Oracle Universal Installer... Checking installer requirements... Checking operating system version: must be redhat-3, SuSE-9, redhat-4, UnitedLinux-1.0, asianux-1 or asianux-2 Failed <<<<
The “easiest” workaround:
[oracle@dbsrv database]$ ./runInstaller -ignoreSysPrereqs
The “hardway” workaround:
1. Copy parameter file: $ cp database/install/oraparam.ini /tmp 2. Edit parameter file: $ vi /tmp/oraparam.ini 2.1. Change [Certified Versions] Linux=redhat-3,SuSE-9,redhat-4,UnitedLinux-1.0,asianux-1,asianux-2 to [Certified Versions] Linux=redhat-3,SuSE-9,redhat-4,UnitedLinux-1.0,asianux-1,asianux-2,redhat-5 3. Run the installer again: $ ./runInstaller -paramFile /tmp/oraparam.ini
KB: Requirements For Installing Oracle10gR2 On RHEL 5/OEL 5 (x86_64) [ID 421308.1]
Matheus.
# Error
RMAN-03002: failure of backup command at 06/28/2015 14:56:30 RMAN-06059: expected archived log not found, loss of archived log compromises recoverability ORA-19625: error identifying file +DGFRA/corpdb/archivelog/2015_06_27/thread_1_seq_20198.1192.883524615 ORA-17503: ksfdopn:2 Failed to open file +DGFRA/corpdb/archivelog/2015_06_27/thread_1_seq_20198.1192.883524615 ORA-15012: ASM file '+DGFRA/corpdb/archivelog/2015_06_27/thread_1_seq_20198.1192.883524615' does not exist
# Solution
First of all, you need to know which files exists or not:
RMAN> CROSSCHECK ARCHIVELOG ALL;
Then, clear the missing and run another backup.
RMAN> DELETE EXPIRED ARCHIVELOG ALL;
It’s hardly recommended that you make a full backup after that, to ensure you have a recoverable state.
Matheus.
When we are preparing to move a database or something like that, it’s useful to know if there is any session connecting by SID, right?
It can be done with:
select distinct machine,username,inst_id from gv$session where service_name = 'SYS$USERS';
Cheers!
Some Linux basics… To add a group or a user (this case “new_group”) to the ssh and sudoers file:
[root@db-server ~]# vi /etc/ssh/sshd_config [root@db-server ~]# cat /etc/ssh/sshd_config |grep new_group AllowGroups ssh_group1 root oinstall linux new_group [root@db-server ~]# vi /etc/sudoers [root@db-server ~]# cat /etc/sudoers |grep new_group %new_group ALL=(ALL) PASSWD: ALL [root@db-server ~]# service sshd restart Stopping sshd: [ OK ] Starting sshd: [ OK ] [root@db-server ~]#
Matheus.
# Solution:
Make sure that /dev/shm is mounted. You can check this by typing df -k at the command prompt. It will look something like this:
Filesystem Size Used Avail Use% Mounted on
…
shmfs 1G 512M 512M 50% /dev/shm
If you don’t find it then you will have to manually mount it as root user. The size should be more than MEMORY_TARGET or MEMORY_MAX_TARGET.
For example, if the MEMORY_TARGET is less than 2 GB, you should make like that:
#root: mount -t tmpfs shmfs -o size=2048m /dev/shm
I recommend you add an entry in /etc/fstab so that the mount remains persistent even after a reboot.
To make it, add the following entry in /etc/fstab:
shmfs /dev/shm tmpfs size=2048m 0 0
Helped?
Share this post!
Matheus.
# Problem
SQL> drop tablespace UNDOTBS1; drop tablespace UNDOTBS1 * ERROR at line 1: ORA-01548: active rollback segment '_SYSSMU10_1251904955$' found, terminate dropping tablespace
SQL> drop rollback segment "_SYSSMU3_1251904955$"; Rollback segment dropped. SQL> drop tablespace UNDOTBS1; drop tablespace UNDOTBS1 * ERROR at line 1: ORA-01548: active rollback segment '_SYSSMU10_1251904955$' found, terminate dropping tablespace
# Solution
CREATE ROLLBACK SEGMENT rb1 STORAGE(INITIAL 1M next 1M minextents 20) tablespace UNDOTBS5; CREATE ROLLBACK SEGMENT rb2 STORAGE(INITIAL 1M next 1M minextents 20) tablespace UNDOTBS5; CREATE ROLLBACK SEGMENT rb3 STORAGE(INITIAL 1M next 1M minextents 20) tablespace UNDOTBS5;
# Why?
The UNDO_MANAGEMENT is set as ‘MANUAL’, right? To drop any undo the default UNDO must have at least one segment.
Matheus.
The situation:
We have a GoldenGate on Allow Mode running some extracts on RAC One Node Database (reading the archivelogs). And then, suddenly, the instance crashes (network lost contact to the server) and the other instance (thread) was auto started by CRS. To the database no problems: The other node redologs was used during the startup recover and every thing is ok.
The application running with Weblogic serverpool and gridlink just had a little contention and continued the operation thought the started instance. The Goldengate switch was manually made, but some sequences was lost. What we found? the sequences was in the old thread’s redologfiles. It should be backed up if fast_start_mttr_target was different to zero. Buuut, the world is not so beautiful:
raconenodedb> show parameters mttr NAME TYPE VALUE ------------------------------------ fast_start_mttr_target integer 0
How we solved?
Simple solution: identified the group/thread and made a cp from ASM. The copied redolog was used as archivelog on goldengate and everything was ok.
raconenodedb> select sequence#,group#,thread# from v$log where thread#=2 order by 1; SEQUENCE# GROUP# THREAD# ---------- ---------- ---------- 39636 6 2 39637 7 2 39638 8 2 39639 9 2 39640 10 2
ASMCMD> cp group_10.288.859482805 /oracle/grup10_thread2 copying +DGDATA/MYDB/ONLINELOG/group_10.288.859482805 -> /oracle/grup10_thread2
Easy like that.
Matheus.
Quick tip:
# Error:
[root@db1gridserver1 bin]# ./acfsload start -s
Can’t exec “/usr/bin/lsb_release”: No such file or directory at /grid/product/11.2.0/lib/osds_acfslib.pm line 511.
Use of uninitialized value $LSB_RELEASE in split at /grid/product/11.2.0/lib/osds_acfslib.pm line 516.
# Solution:
[root@db1gridserver1 bin]# yum install redhat-lsb-core-4.0
Note: Bug 17359415 – Linux: Configuring ACFS reports that cannot execute ‘/usr/bin/lsb_release’ (Doc ID 17359415.8)
Matheus.
Today’s post is a quick post!
Very quick post! very very quick post!
But it’s a helpful post!
Connected as sys with sysdba:
select x.ksppinm name,
ksppdesc description,
y.kspftctxvl value,
y.kspftctxdf isdefault,
decode(bitand(y.kspftctxvf, 7), 1,'MODIFIED',4,'SYSTEM_MOD','FALSE') ismod, decode(bitand(y.kspftctxvf, 2), 2, 'TRUE', 'FALSE') isadj
from sys.x$ksppi x, sys.x$ksppcv2 y
where x.inst_id = userenv('Instance')
and y.inst_id = userenv('Instance')
and x.indx + 1 = y.kspftctxpn
order by name;
Matheus.
