Android: “database storage is getting low”

»Menü »Einstellungen »Anwendungen »Anwendung verwalten »Alle »Medienspeicher »Daten löschen [Achtung alle pers. Medien Fotos, MP3 etc. sind weg!] »Neustart

Dank geht an mobile_maniac für seinen post auf http://www.android-hilfe.de/

Advertisements

Determine the Oracle Database Platform Specific Release Number

If you ask your Oracle DBMS about its full Oracle Database Release Number, you get an answer like the following (recommended way to query this, compare Identifying Your Oracle Database Software Release):

SQL> COL PRODUCT FORMAT A40
SQL> COL VERSION FORMAT A15
SQL> COL STATUS FORMAT A15
SQL> SELECT * FROM PRODUCT_COMPONENT_VERSION;

PRODUCT               VERSION         STATUS
--------------------- --------------- ---------------
NLSRTL                11.2.0.3.0      Production
Oracle Database 11g   11.2.0.3.0      64bit Production
PL/SQL                11.2.0.3.0      Production
TNS for Solaris:      11.2.0.3.0      Production

But this is simply wrong, the last byte, the Platform specific release number is not 0 in my case, e.g. after you applied a patch cluster (CPU) to your installation!

Solution is to use the opatch utility, which resides in your ORACLE_HOME directory: Start it with the lsinventory parameter and the sky is clear. Have a look at the first line with Database Patch Set Update:

$ /opt/oracle/product/11.2.0.3/OPatch/opatch lsinventory
Oracle Interim Patch Installer version 11.2.0.3.0
Copyright (c) 2012, Oracle Corporation. All rights reserved.</code>

Oracle Home : /opt/oracle/product/11.2.0.3
Central Inventory : /opt/oracle/home/oraInventory
from : /opt/oracle/product/11.2.0.3/oraInst.loc
OPatch version : 11.2.0.3.0
OUI version : 11.2.0.3.0
Log file location : /opt/oracle/product/11.2.0.3/cfgtoollogs/opatch/opatch2012-11-14_15-46-23PM_1.log

Lsinventory Output file location : /opt/oracle/product/11.2.0.3/cfgtoollogs/opatch/lsinv/lsinventory2012-11-14_15-46-23PM.txt

--------------------------------------------------------------------------------
Installed Top-level Products (1):

Oracle Database 11g 11.2.0.3.0
There are 1 products installed in this Oracle Home.

Interim patches (1) :

Patch 14275605 : applied on Wed Oct 17 16:31:29 CEST 2012
Unique Patch ID: 15377775
Patch description: "Database Patch Set Update : 11.2.0.3.4 (14275605)"
Created on 4 Oct 2012, 00:07:51 hrs PST8PDT
Sub-patch 13923374; "Database Patch Set Update : 11.2.0.3.3 (13923374)"
Sub-patch 13696216; "Database Patch Set Update : 11.2.0.3.2 (13696216)"
Sub-patch 13343438; "Database Patch Set Update : 11.2.0.3.1 (13343438)"
Bugs fixed:
14480676, 13566938, 13419660, 10350832, 13632717, 14063281, 12919564
13624984, 13430938, 13467683, 13588248, 13420224, 14548763, 13080778
...

Discovering Oracle Database 11g Memory Management

It is very easy: I want my databases to consume as much memory as they need. But not more than a reasonable amount. And I want Automatic Memory Management and Automatic Shared Memory Management both enabled. Easy you say?

Ok, you’re right – but only if you are a full time Oracle database admin with a long, long time experience. Me, I’m a part-time DBA, with an outside view on the instances. For example, I’m writing scripts to automate the creation of instances, upgrade software and instances to new releases aso.

So I stumbled upon the . In chapter 7, I’ve found what I was looking for (reading the first 5 pages of this chapter). I’ve adapted one of my databases’ pfile and gave it a try.

From now on I will always set
memory_target=4294967296
memory_max_target=6442450944
to enable the Automatic Memory Management. And I will set
sga_max_size=3221225472
sga_target=2147483648
variables.

Hey, stop complaining: I know I should *not* set sga_max_size. But if I don’t do, querying the database for this parameters’ value it says “Dude, it’s equal . And so a simple show sga shows me values, which I don’t like.

This database instance has a small memory footprint now, nearly what I wanted to achieve.

BTW. All other params (db_cache_size,shared_pool_size,large_pool_size, and java_pool_size) have not been set in the pfile.