One blog that I’ve been reading avidly recently is Guy Kawasaki’s blog.
Another one is Presentation Zen.
I found the second one on the first one.
Guy Kawasaki is a former Apple Executive who talks about… Well I guess we can call it best practise. And it’s fun to read.
Presentation Zen study the art of presenting powerpoints. From the time where it’s done to the time when it’s told to an audiance. He uses the eye of a microscope to study famous presentation styles plus some other goodies.
An ETL is a software which Extract, Transform and Load data.
Extract is from different sources. It can be some databases as well as some text files or even excel documents. We have that a lot here.
Transform is when we have to concatenate data, match some data with others or simply filter them to make sure we have all we need before loading the data.
Load talks for itself I guess.
It’s name is Kettle and we like it 
Well there are some other open source products on the market but Kettle demonstrated more maturity in the project.
When we feedback bugs it’s taken into account very quickly.
It has been recently bought by Pentaho.
All you need to try it is java runtime installed on your computer.
Any DBA who worked on oracle 8i knows where to find init[sid].ora.
The SPFile is located in the same folder just like the Pfile.
Except… It’s not manually managed. It’s managed by oracle. This is done to avoid human error in parameters.
There can be problems in parameters though. During the migration, a parameter (DB_BUFFER_SIZE), from the 8i era was left in the parameter file and was conflicting with another one (DB_CACHE_SIZE) in the parameter file.
When restarted, the database couldn’t even mount…
Don’t worry, when you get that error, there’ll be a list of conflicting parameters.
Usually, you should be able to get into OEM and remove the bad parameter then it would be possible to start again. But it was my luck and OEM was not working too.
There’s only one way out of it. It is possible to get back to the old 8i style and use an init.ora file which can be modified manually.
To do so, connect as sysdba on command line:
C:\SET ORACLE_SID = [Your Sid]
C:\SQLPLUS / as sysdba
SQL>CREATE PFILE=’C:\WHEREVER_YOU_WANT_IT_TO_BE]\INIT[SID]‘ FROM SPFILE=’C:\WHERE_IT_IS\SPFILE[SID].ORA’
As it says, it will create the Pfile from the SPfile. Then it is manually manageable. When the culprit is removed, simply do the opposite thing:
SQL>CREATE SPFILE=’C:\[WHERE_IT_SHOULD_BE]\INIT[SID]‘ FROM SPFILE=’C:\WHERE_IT_SHOULD_BE_TOO\SPFILE[SID].ORA’
This will create a new spfile from the modified init[sid].ora
Now all what is left, is to start the database
SQL>STARTUP
Recent Comments