Category: 12c

EM12c Agent – java.lang.OutOfMemoryError: Java heap space

After an AIX 7.1 server reboot, there was one agent which did not started. The command emctl start agent resulted in a java.lang.OutOfMemoryError: Java heap space message. In the agent subdirectory some dumpfiles were created: -rw-r—– 1 oracle dba 291373 Oct 19 11:00 javacore.20151019.110002.14876844.0002.txt -rw-r—– 1 oracle dba 22182281 Oct 19 11:00 heapdump.20151019.110002.14876844.0001.phd -rw-r–r– 1 oracle dba 167408 Oct 19 11:00 Snap.20151019.110002.14876844.0003.trc First I took a look in the agent logfiles to gather more information. /u00/app/oracle/product/agent12c/agent_inst/sysman/log/emdctlj.log 2015-10-19 10:59:11,711 [1:F7DA781F:main-16449708] INFO – EmdCtl Timezone = Europe/Zurich 2015-10-19 10:59:11,884 [1:F288756D:main-11600120] INFO – EmdCtl Timezone = Europe/Zurich 2015-10-19 10:59:13,584 [1:2CF29A0A] INFO – Disconnecting: client terminus 2015-10-19 10:59:13,585 [1:2CF29A0A] INFO – stdout: Status agent Failure:unable to connect to http server at https://srvaix111.mvn.ch:3874/emd/lifecycle/main/. [peer not aut henticated]…

Read More

Patching a DBaaS Database in the Oracle Cloud

To apply a Patch on a Database which is hosted by Oracle is done with one mouse click. This service is available only if you have selected the full database service during the DBaaS order process. To the manual: https://docs.oracle.com/cloud/latest/dbcs_dbaas/CSDBI/GUID-50BDEF7D-A30E-4B32-BAE7-486538413E2D.htm#CSDBI3422 Patchset Availability As soon as a new Oracle patchset is available, you can see that in the database management dashboard of the selected database. The precheck function verifies if the selected database is ready to patch. Precheck Result After 2 until 3 minutes and a refresh of the page you see the result.               Command Line Interface dbpatchm If you have no web access, all these steps can be executed manually in the shell.…

Read More

Oracle Enterprise Manager 12cR5 – Clone a PDB to the Oracle Cloud

Cloning an on-premise PDB to the Oracle Cloud is basically done in three steps. 1. Select your PDB – 2. Start Clone Menu – 3. Verify new PDB. In the basic clone menu, Oracle uses some default settings in the background, for example the source datafiles will be packed in a compressed file which is located in /tmp directory of the source server. When your /tmp directory is too small, the clone process fails. Why this directory is used? I don’t know. But it could be a problem when you clone bigger databases. Maybe we can edit the clone procedure, but this is a task for me for a day when it’s raining outside… All cloning steps are well monitored,…

Read More