This morning the first challenge of the day became the fact that we could not get proper access to one of the databases. We would set the Environment, set the proper ORACLE_SID and yet after logging on would get
ORA-01012: not logged on
with any query ( select * from v$instance ; show parameter blablah ).
Reading the posts on the web give a quick solution… First proof: the alert log was flooded with messages like these:
ORA-04031: unable to allocate 2072 bytes of shared memory ("shared pool","unknown object","sga heap(1,1)","parameter table block
Wed Feb 27 09:31:49 2013
Process J000 died, see its trace file
Wed Feb 27 09:31:49 2013
kkjcre1p: unable to spawn jobq slave process
Sqlplus / as sysdba worked, but any query failed with ORA-01012.
Created a pfile from spfile , edited both SGA_MAX_SIZE and SGA_TARGET and increased the processes as well in the init.ora .
Created spfile file from the altered pfile.
Restarted the Database, and after that happy database ( and dba ).
Sometimes it is almost funny how old habits indeed seldom die. At the Customers site where I am working there still seems to be a culture in which it is not that common to use Gui solutions offered by Oracle to do day-to-day jobs. In Dutch there is an expression telling unknown things makes things disliked. Well this week i came across nice behavior of the NETCA tool in an environment where Grid Infrastructure 22.214.171.124 is running and I must say I really liked it.
My environment is a four Node Cluster on Redhat Linux 5.5, my Grid Infra structure is 126.96.36.199.0.
This week i have patched a preproduction environment with latest PSU patch at this moment ( October 2012). Next week will do the same on the production machines In it self this action is not a big issue when applying it to the Grid infra structure and RDBMS, but ACFS is in use on those boxes. Since I hope this will make an interesting note, I have gathered my steps and want to share them with you.
For a customer I have to implement Oracle Warehouse builder on several servers. So it became an interesting session cause during exploring, well actually it was already during installing found out that there are dependencies to other products that need to be present in the database before you can finish the job successfully. But as always Google is your friend so i was very happy in the end to summarise the steps and put them to a blog.
Bottom-line is that the following components need be present in your database before you can start with the Oracle Warehouse builder:
- Java virtual Machine
The remarkable thing was that during exploring i came across the fact that if you create your database via DBCA these components are installed. If you are a diehard and use the command line / scripts for that well then you need to do just a bit extra to be victorious. The environments in this note were set up manually.