A fresh view on Oracle
Today I ran into an add-on for FireFox which can create a wget command from a download file dialog box. First thing that came in mind was; Will this work for Metalink / My Oracle Support? Yes is does!
The add-on is called ‘cliget’ and can be downloaded here: cliget add-on for FireFox.
[Read the rest of this entry...]
I was preparing some fresh installed OEL5.5 machines for database software installation, but after running ‘yum install oracle-validated‘, the OUI did not pass the prerequisites on two packages. It seems it did not install unixODBC-devel x86_64 and libaio-devel x86_64.
Their Linux may be unbreakable, but their ‘oracle-validated’ package on the public yum server seemed to be broken.
[Read the rest of this entry...]
Many people will use the WebLogic’s NodeManager to use the start script for starting Managed Servers:
StartScriptEnabled=true
The NodeManager will start the Managed Server using the script and monitor the Managed Server when it fails.
One of the mistakes people can make is creating their own start script and start the Managed Server using ‘nohup &’ within this script: Metalink [ID 984122.1] and [ID 861098.1]. The script will finish and the server keeps running, but the NodeManager thinks the Managed Server has failed…
[Read the rest of this entry...]
Oracle has released it’s first patch set for Oracle Database 11g Release 2 (11.2.0.2).
See the README at Oracle® Database Patch Set Notes 11g Release 2 (11.2.0.2) Patch Set 1 and Metalink Note ID 1189783.1 at Important Changes to Oracle Database Patch Sets Starting With 11.2.0.2 for more information.
I knew in Oracle 11g with Automatic Memory Management (AMM), the database was able to give unused memory back to the OS, controlled by MEMORY_TARGET and MEMORY_MAX_TARGET.
This mechanism is present in 11g since day 1 (in 2007), but I never actually played with it.
The Oracle documents state the following:
MEMORY_TARGET specifies the Oracle system-wide usable memory.
MEMORY_MAX_TARGET (…) decide on a maximum amount of memory that you would want to allocate to the database for the foreseeable future.
So my guess is, MEMORY_MAX_TARGET (static) is the maximum you can set MEMORY_TARGET (dynamic) to. A couple of days ago, I wanted to experiment a bit with these memory settings.
[Read the rest of this entry...]
When moving/deleting the listener.log, I used to stop and start the listener and move/delete the listener in between the actions.
This method has a big inconvenience: users can not connect to the database for a few seconds…
What I never knew was that the listener could be told to stop and start logging and take the appropriate action in between.
[Read the rest of this entry...]
Ever had the “wrong authentication protocol” error when using Xming and xhost+ still did not work?
When you are on a private network, you can try using the “-ac” option when starting Xming. Use this only on private trusted networks, because it gives access to everyone.
For mote information on Access Control in Xming and X-Forwarding with PuTTY and SSH, check the Xming troubleshoot guide.
Happy consulting!