Many people will use the WebLogic’s NodeManager to use the start script for starting Managed Servers:
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… Continue reading →
Oracle has released it’s first patch set for Oracle Database 11g Release 2 (22.214.171.124).
See the README at Oracle® Database Patch Set Notes 11g Release 2 (126.96.36.199) Patch Set 1 and Metalink Note ID 1189783.1 at Important Changes to Oracle Database Patch Sets Starting With 188.8.131.52 for more information.
— Checked for relevance on Januari 21, 2017
The Oracle Database version compatibility matrix and version support status matrix are almost mandatory when installing or upgrading clients or servers.
Oracle Database client / server version compatibility matrix
Oracle calls this Client / Server Interoperability Support, Note ID 207303.1
Oracle Database version release support status matrix
Oracle calls this the Database Releases Support Status Summary, Note ID 161818.1
You will be redirected to Oracle Support and you must be registered to gain access to the pages. I did not include the matrices, because these change over time.
Oracle Information about Windows 32 / 64 bit database and client versions
Certification Information for Oracle Database on Microsoft Windows x64 (64-bit), Doc ID 1307195.1
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.
MEMORY_TARGET and MEMORY_MAX_TARGET
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.
Continue reading →
I have been trying to import a private key into ConnectBot for Android.
The key I’m using is working fine when using Putty, but does not work for ConnectBot.
To make it work for ConnectBot, you need to have a OpenSSH version of this file.
Luckily one can also use PuTTYgen to create an OpenSSH key.
In Puttygen, do the following:
- Load the private key: [File] -> [Load Private Key] (*.ppk)
- Enter passphrase if applicable
- Goto: [Conversions] -> [Export OpenSSH key] and save
Continue reading →
Installing the Oracle Instant Client will save you ~600 megabyes compared to the ‘full’ Oracle Client.
- Download Basic Package from the Oracle site
- Unzip to directory x (your ORACLE_HOME)
- Set PATH (Windows) or LD_LIBRARY_PATH (*nix) to the Instant Client directory x
- Move TNSNAMES.ora to directory x/network/admin (or set TNS_ADMIN and ORACLE_HOME).
- Extend with SQL*Plus Package (optional)
- Start your application
Read my full article here: Whiteblog – Installing the Oracle Instant Client. (links in referred blog might not work!)
OLE DB, .NET and ASP.NET drivers are not included in the instant client (first Oracle link might suggest it is). These are included in the ODAC package, download them separately at these locations:
Instant Client vs Full Client (Administrator and Runtime)
What Are The Different Oracle Client Components Installed With Different Installation Types (too much to sum up):
Client master note
Master Note For Oracle Database Client Installation (Doc ID 1157463.1)
Checked for relevance on November 4th, 2019.
Have a look at my Whitehorses Blog where I will explain in more detail.
Final conclusion (on one line):
CustomLog "|<midtier>\Apache\Apache\bin\rotatelogs logs\ssl_request_log 43200" "%t %... %b"
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.