Check which Oracle PSU are installed

With latest version of OPatch:

$ORACLE_HOME/OPatch/opatch lsinventory -bugs_fixed | grep -i ‘DATABASE PSU’

or

set lines 255

col action_time for a40


col action for a8


col namespace for a7


col version for a11


col comments for a40


select substr(ACTION_TIME,1,40) action_time,substr(ACTION,1,8) action,substr(NAMESPACE,1,7) namespace,


substr(VERSION,1,11) version,ID,substr(COMMENTS,1,40) comments,BUNDLE_SERIES


from registry$history;

To install latest OPatch, after download (make sure you only have OPatch zip for the correct Oracle version: 10.2, 11.1, 11.2):

  • mv $ORACLE_HOME/OPatch $ORACLE_HOME/OPatch.old
  • unzip p6880880* -d $ORACLE_HOME

ORA-14450, Global temporary tables and on commit preserve rows

— Clean environment
 drop table gtt;
 drop table gtt
            *
ERROR at line 1:
ORA-00942: table or view does not exist

— Global temporary – preserve rows
create global temporary table gtt ( x int ) on commit preserve rows;
Table created.

— Keeps information until the end of the user session
select duration from user_tables where table_name = ‘GTT’;
DURATION
—————
SYS$SESSION

— Insert one row
insert into gtt values(1);
1 row created.

— Creates a TO lock
select sid, type, id1, id2, lmode from v$lock where id1=(select object_id from all_objects where object_name=’GTT’);
       SID TY        ID1        ID2      LMODE
———- — ———- ———- ———-
      4343 TO     403115          1          3

— Commit transaction
commit;
Commit complete.

— TO lock continues…
select sid, type, id1, id2, lmode from v$lock where id1=(select object_id from all_objects where object_name=’GTT’);
       SID TY        ID1        ID2      LMODE
———- — ———- ———- ———-
      4343 TO     403115          1          3

— Any user that tries to change the table
— Will receive: ORA-14450: attempt to access a transactional temp table already in use
alter table gtt add (y int);
alter table gtt add (y int)
*
ERROR at line 1:
ORA-14450: attempt to access a transactional temp table already in use

— Only after doing truncate
truncate table gtt;
Table truncated.

— TO lock disappears
select * from v$lock where id1=(select object_id from all_objects where object_name=’GTT’);
no rows selected

— With a global temporary table delete rows
drop table gtt;
Table dropped.

create global temporary table gtt ( x int ) on commit delete rows;
Table created.

— The duration is at transaction level
select duration from user_tables where table_name = ‘GTT’;
DURATION
—————
SYS$TRANSACTION

— Insert one row
insert into gtt values(1);
1 row created.

— Creates a TO lock
select sid, type, id1, id2, lmode from v$lock where id1=(select object_id from all_objects where object_name=’GTT’);
       SID TY        ID1        ID2      LMODE
———- — ———- ———- ———-
      4343 TO     403116          1          3

— That disappears as soon as you commit the transaction
commit;
Commit complete.

select sid, type, id1, id2, lmode from v$lock where id1=(select object_id from all_objects where object_name=’GTT’);
no rows selected

— Clean up environment
drop table gtt;
Table dropped.


New Oracle GoldenGate 11.2

Oracle released few weeks ago the new version of GoldenGate 11.2.1.0.0. The biggest novelty is the “integrated capture mode”, meaning that it starts working together with the internal log miner functionality.

This means no extra configuration is needed when extracting from an Oracle RAC or using ASM.

Soon I’ll be testing this new feature for a client.

Meanwhile, I leave you with a snippet of the “Release Notes”, page 6.


New ‘My Oracle Support’

Since this weekend, the http://supporthtml.oracle.com is called just “Dashboard”. Previously (still seen on http://support.oracle.com) it was called “My Oracle Support | Dashboard”.

Since years that Oracle tries to improve their paid support website, with little success. From the time of Metalink, the search speed is still a big handicap. The usability and mainly the user interface do not get any improvement from version to version.

There is the “APEX” layout which I personally don’t like. Then the choice of colors, gradients and curved edges which are all out of fashion and with lack of contrast for today’s webpages standards.

Let’s say what improved in the last 7 or 8 years in the support Oracle website:

  • we can see service request messages history while adding more content
  • we can see the list of files already uploaded to a service request and download them if necessary
  • the search results are a more intelligent (if there is no misspell).

However there is one thing that still I find incomprehensible: the lack of speed of the search engine.

Will it be there one time that a “Google like” (well, maybe the expectation is too high) search engine will be deployed at My Oracle Support?

Just to finish, a first points where the new “My Oracle Support” html version is behind the flash version:

  • no highlight of service request on “customer working” status

And a point where there is an improvement:

  • you can now resize the tables on the dashboard to see more “Service Requests” or more “News”.


Kill long running transactions

For instance the ones running for more than 12hours:

select ‘alter system kill session ”’||s.sid||’,’||s.serial#||”’ immediate;’,
s.osuser,s.machine,s.module, CEIL(24*(SYSDATE-t.START_DATE))
from v$session s, v$transaction t
WHERE S.SADDR=T.SES_ADDR
and CEIL(24*(SYSDATE-t.START_DATE))>12;


Ideas I would like to develop

– testing and documenting the apply of Oracle PSU by:
. clone a master patched Oracle Home
. attach new home to inventory
. move existing DBs to use the new Oracle Home
. run post-PSU operations on each DB (catpsu.sql, etc)

Advantages:
– minimize downtime
– automatize patching


GoldenGate and invalid dates

GoldenGate is a powerful tool bought by Oracle to replace the “Oracle Streams”. It allows heterogeneous replication of data and works just fine almost out-of-the-box.

My client uses it to make a cache copy of data a kind of active standby while running on Oracle 10.2.

Today I had to fight for a problem that comes from the application, which seldom writes to the source database dates in a invalid format, with an year 0 (Oracle should not accept, but the year got in, we are still investigating how).

This makes the GoldenGate replication process to abend, as the write on the target database fails with an “ORA-01841: (full) year must be between -4713 and +9999, and not be 0”.

For the workaround, using GoldenGate MAP function, I managed to transform the dates like the following:
Source: 0000-12-09:08:11:20
Target: 0001-12-09:08:11:20

MAP NESSOFT.NEXT_ORD, TARGET NESSOFT_NL.NEXT_ORD , &
COLMAP ( USEDEFAULTS,
EXPIRE = @IF ( @STRCMP(@STREXT(EXPIRE,1,4),"0000") = 0, @STRCAT("0001-",@STREXT(EXPIRE,6,18)),EXPIRE)
);

This allowed to me also to discover the discard file (.dsc) on the dirrtp folder of GoldenGate, where you can see the output of the MAP function, useful for the debug.


Keyboard for a computer scientist

After working more than 5 years with either an US or English keyboard, I find very difficult to get used to a Swiss keyboard. This is not the case for writing e-mails, but mostly for working. Unfortunately by being a consultant now I’ve often to work on clients terminals and their installed keyboard, not giving even the opportunity to hang around with a US keyboard for my pleasure.

Why the US or English keyboard are better for computer scientists?

– you have easy access to the brackets (), [], {}, which are always in two different keys and not hidden away with AltGr;
– you have easy access to <> in two different keys, not needing to make sure the shift is pressed or not.
– Also comma ´ and ‘ are different keys;
– The slashes / are both in logical places
– The @ is accessible with a simple Shift key, like is the pipe |

And you can also easily use the US-International keyboard to write in many languages, including the portuguese where you have ã,à,é,ç…

I hope that soon will be easier to change keyboards on the OSes and also that a better universal standard (at least for roman alphabet based) appears.


DNS name server, IPv6 and hang of listener

The other day during an operation on one of the DNS servers, some of our RAC listeners went down and stop responding.

We found this happened when they brought down one of the DNS name servers, even thought one was up and running.

Ping, ssh and so on was working fine. But any operation with ‘lsnrctl’ or ‘srvctl xxx listener’ would hang.

After investigation together with the system administrator it was found that it was related to the IPv6 lookups which are activated by default on AIX and are done when the first IPv4 lookup fails.

To solve the problem was just necessary to disable the IPv6 lookups by changing the /etc/netsvc.conf file to:
hosts=local4,bind4

This is explained on this IBM note.