To determine the FC HBA WWN on Oracle Enterprise Linux (OEL) use:
cat /sys/class/fc_host/host<number>/port_name
For example:
[root@host sys]# cat /sys/class/fc_host/host6/port_name 0x2100001b329308df [root@host sys]# cat /sys/class/fc_host/host5/port_name 0x2100001b329388d9
After upgrade to EMC Networker 7.6.1 NDMP are failing with:
filer:/vol/vol0/etc 6899:nsrdsa_save: Warning: Could not determine job id. Continuing ... filer:/vol/vol0/etc 39078:nsrdsa_save: SYSTEM error: Could not establish jobid with server. filer:/vol/vol0/etc 39078:nsrdsa_save: DSA save time could not be retrieved, exiting
Thsi is a known bug in 7.6.1. The fix is available here:
Oracle offers the ability to specify so called ‘alternative’ archive log destinations in case the primary archive log destination gets full. You can enable this feature by setting:
log_archive_dest_1='location=+FRA REOPEN=0 MANDATORY alternate=log_archive_dest_2' log_archive_dest_2='location=/some_path MANDATORY' log_archive_dest_state_1=ENABLE log_archive_dest_state_2=ALTERNATE
A configuration often used involved using the flash recovery area as primary destination and a nfs destination as alternative archive log destination.
Few weeks ago Oracle released the first patchset for 11g Release 2 database. This is a summaization of other blog posts regarding upgrading or installating 11.2.0.2.0.
At the moment (4th November 2011) 11.2.0.2.0 is available for the following platforms:
Upgrading Grid Infrastructure to 11.2.0.2.0 on RHEL 4
Upgrading RAC database to 11.2.0.2.0
I am pretty busy the last weeks so i had no time for updates. I will have more time next week.
Ever wanted to use variables in your RMAN scripts? Until and including 10g R2 this was impossible. Starting with 11g R1 it is possible.
Lets me show you a short example how to do it:
First we create a simple (and imcomplete) script with the following content:
connect target / backup &1;
The variable “&1″ will be replaced with the first command line argument supplied on the command line. “&2″ is the second argument and so on.
Suppose we want to backup our database we start RMAN with:
-bash-3.2$ rman target / @test.scr USING \"database\"
The resulting output will be:
Recovery Manager: Release 11.2.0.1.0 - Production on Mon Aug 2 08:16:07 2010 Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved. connected to target database: ORA11R2P (DBID=2658288218) RMAN> backup database; 2> Starting backup at 02-AUG-10 using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=148 device type=DISK channel ORA_DISK_1: starting full datafile backup set channel ORA_DISK_1: specifying datafile(s) in backup set input datafile file number=00001 name=/u01/oradata/ORA11R2P/system01.dbf input datafile file number=00002 name=/u01/oradata/ORA11R2P/sysaux01.dbf input datafile file number=00003 name=/u01/oradata/ORA11R2P/undotbs01.dbf input datafile file number=00005 name=/u01/oradata/ORA11R2P/testneu.dbf input datafile file number=00004 name=/u01/oradata/ORA11R2P/users01.dbf channel ORA_DISK_1: starting piece 1 at 02-AUG-10
As you can see in the bold line RMAN replaced the variable with the first argument specified on the command line (“database”).
With this method you can create powerful and yet simple scripts for backing up your database.
This is a short post on how to tune Linux for running Oracle.
It wont cover the background directly but i am trying to give some links with further informations.
I am planning to improve it over the time.
Currently this article covers:
With end of July 2010 support for Oracle 10g Release 2 ends. You can order (at additional costs of course) so called extended support to get support until July 2011. After this date there is so called “Sustaining Support” which offers support for several more years.
Update: I was told the first year of Extended Support is free of charge (Thanks Martin!). So customers have a little bit more time to test and upgrade.
See the following picture for the support end dates:
So if you start with new projects i´d strongly recommend to use Oracle 11g Release 2 at best or if 11g R2 is not an options 11g R1.
I just found Oracle released 10.2.0.5.0 patchset for the following platforms:
See Doc ID 1088172.1 for a list of fixed problems.
This is a short posting about an error i found today.
This errors prevents the import of tables with lob columns when using traditional import, deferred segment creation and an altered tablespace name.
For this i created a test case in which we
Note: While blogging this for a fried i was in hurry; i will rewrite some paragraphs with evening… but the problem should become clear while reading…
