Oracle VM Site Review - Oracle VM Health Check
view counter

Database Feed

Oracle Database, Oracle 10g, Oracle 11g, Oracle XE, Oracle RAC, Oracle Instant Client, Oracle Data Guard and Oracle Exadata resources, news, and support articles.

OCM 11g Preparation – Implement Data Pump to and from remote databases

This topic basically wants us to know how to run expdp and impdp using the “network_link” parameter. This parameter is indeed very useful as this is the only way to:

  • export from a remote database directly locally (like the legacy exp) without generating the file in the remote server and then SCPing.
  • import directly from a remote database without generating any intermediate file.

So be prepared for that. Practice each of the items above and you are done here.
Path do Documentation:

2 ways to move archivelogs - both need RMAN

The database must know where are the files. If you move them from the OS, the database will not be aware of it. But there is a database tool to copy or move files and update the database repository (controlfile). It's RMAN. With RMAN you can either:

  • update the repository after you've moved the file from the OS
  • or do the both: move and update the repository

The syntax is a bit weird, so let's have an example.

RMAN> CATALOG

I have the following archived logs in the /u02/DEMO/fast_recovery_area/DEMO11/archivelog/2015_06_23 directory:

What’s in a Name ? USER_TAB_COLS and USER_TAB_COLUMNS are different.

My son and I are quite similar in some ways ( although he would vehemently dispute this).
Like me, he works in IT, in his case as a Support Engineer.
Like me, he’s called Mike (well, my Mum likes the name…and I can spell it).
Unlike me – as he would be quick to point out – he still has all his own hair.
These similarities have been known to cause confusion – I’m often contacted by recruitment agents with enticing offers to work on…some newfangled stuff I know nothing about, whilst he’s constantly being offered “exciting” Database related opportunities.

INSERT /*+ APPEND */

This example demonstrates that an INSERT /*+ APPEND */ does not put rows into free space within a table, it adds them at the end instead. It also shows that Oracle inserts these rows using a DIRECT PATH mechanism. I tested it on Oracle 11.2.

SQL Server 2016 : availability groups and the new SSISDB support

This blog post is focused on the new supportability of SSIDB catalog on AlwaysOn architecture.
Others studies are available here:

ORA-12838

If you do an INSERT /* APPEND */, you cannot query the table afterwards until you have done a COMMIT. If you try to do so, Oracle gives you an ORA-12838. You can see what I mean in the example below, which I tested on Oracle 11.2:

Bash script to check for final closing /data xml tag in file

Bash script to check for final closing xml tag in file:

Oracle Magazine - March/April 2001

The headline articles of Oracle Magazine for March/April 2001 were on using Oracle 9i Application server to deliver e-business and web based applications. There was some case studies of companies using this technologies including Tantalus Communications, Digital River Commerce System, Tomatoland.com and Oracle themselves.

KScope Day 1

Day 1? Really, is that all? There are so many things going on it feels like day 3.

And I'm not even participating in everything since I'm also coming back to do some family time each day.

Chi Gung

I gave this a go this morning after not being able to find Kent on the first day. It was interesting and there were some good exercises that everyone should consider doing in the morning, though with respect to Kent, for me the woo outweighed a lot of good that can come out of meditation and moving your body.

dbnodeupdate.sh post upgrade step fails on Exadata storage software 12.1.2.1.1

I’ve done several Exadata deployments in the past two months and had to upgrade the Exadata storage software on half of them. Reason for that was because units shipped before May had their Exadata storage software version of 12.1.2.1.0.

The upgrade process of the database nodes ran fine but when I ran dbnodeupdate.sh -c for completing post upgrade steps I got an error that the system wasn’t on the expected Exadata release or kernel:

view counter