Oracle released a new BI extension for Open Office with the latest Open Office release (v. 3.3) . This extension gives us the ability to embed information from BI EE 10g into Open Office Calc, Writer and Impress documents (equivalents of Excel, Word and Powerpoint). OO Calc supports the ability to embed entire reports including tabular views, pivot tables and charts. OO Writer and OO Impress only support embedding of charts into the documents.
In the movie “Ironman 2,” Larry Ellison makes a cameo appearance as a billionaire, playboy software magnate. It is a role he knows well. He is playing himself — chief executive of Oracle Corp, one of Silicon Valley’s most enduring, successful and flamboyant figures.
Materialized Views and Partitioning are two key Oracle features when working with data warehouses. Using them together though can sometimes cause unexpected problems when you need to refresh them, as we found on a recent project. Here’s what happened, reproduced using the SH Sample Schema.
Archiving data requires creating a strategy for long-term data retention. This strategy is usually determined in collaboration with IT, line of business and legal teams. This strategy could be impacted by one of two types of requirements – internal requirements, where for example a company must keep all customer records accessible and online for a period of 24 months, or requirements that stem from government regulations like Sarbanes-Oxley, HIPAA, PCI, etc. For example, HIPAA requires that medical records be retained up to two years after a person’s death. Sarbanes-Oxley requires audit data be kept for seven years after the conclusion of the audit and CFR (Life Sciences) requires that pharmaceutical companies retain clinical trial data for 35 years. Requirements are extremely stringent for companies that must retain data for legal purposes, and most are not prepared to hold data for such long time frames, let alone guarantee it hasn’t been altered in any way.
Changing the Character Set After Database Creation
In some cases, you may wish to change the existing database character set. For instance, you may find that the number of languages that need to be supported in your database have increased. In most cases, you will need to do a full export/import to properly convert all data to the new character set. However, if and only if, the new character set is a strict superset of the current character set, it is possible to use the ALTER DATABASE CHARACTER SET to expedite the change in the database character set.
This describes how I set up Oracle 10g on OSX Tiger for development use.
Sergio has an excellent instruction on how to install Oracle 10g on Panther. However because the Oracle requires gcc 3.3 and Tiger uses gcc 4 by default. Some hacks are in order.
The last two evenings I spent on installing Oracle 10g on my iBook. Don’t ask why I have to have Oracle on an iBook, I just wanted to play around with it. Problem was that I haven’t read somewhere before that right now no Oracle database seems to run on Apple’s Tiger yet but only on 10.3 (“Panther”).
When I realized that, I already had tried to solve the problem a few hours. So I wasn’t in the mood to let it go. There had to be a way and I think – a few minutes ago – I found it.
1.Is there any advantage of storing date field as Number datatype in the table ? we have
few tables like this
Sergio’s Blog: Installing Oracle Database 10g on Mac OS X: Sergio’s Blog
Oracle HTML DB tips, tricks and examples.
« HTML DB 1.6 Available for Download | Main | Updated VMWare Kits: Desktop Data Center »
January 02, 2005
Installing Oracle Database 10g on Mac OS X
Recently Oracle and Apple announced the availability of Oracle Database 10g for Mac OS X. In in this — longer than usual — blog post, I document my experience installing the Oracle database on my Mac. In a subsequent post, I’ll talk about my experience installing Oracle HTML DB. These instructions should not be considered a best practice, but they are steps that worked for me. I tried to incorporate as many screenshots as possible to help you when you are performing the install.
1. Hardware Requirements
The Quick Installation Guide states the following hardware requirements:
• 512 MB RAM
• 1GB or twice the size of RAM swap space
• 400MB of disk space in /tmp
• 2Gb disk space for software files
• 1.2Gb disk space for database files
I performed my installation on an
Store the VMS date as timestamp in oracle.
1) Use “delimited” text for unload
2) Before you invoke SQL*Loader ,define the NLS date (both on OS and
init*.ora) to match the date/timestamp format on unloaded file.
e.g If the date on unloaded file : 1998012113351752
VMS : $ DEFINE/SYSTEM NLS_TIMESTAMP_FORMAT
Init*.ora : nls_timestamp_format=”YYYYMMDDHH24MISSFF”