Category: OEM( Oracle Enterprise Manager)

Oracle Enterprise Manager 12c,13c and more

ORA-03206: maximum file size of (4194304) blocks in AUTOEXTEND clause is out of range (DBD ERROR: OCIStmtExecute) from Corrective Action of Add Space to Tablespace

OEM add space to tablespace corrective action failed with the following ORA-03206 error:

...
..
.
OMF directory: +DATAC1
OMF disk group: DATAC1
ASM projected safely usable free space (MB) is: 28548641.667
ASM projected Space Used (%) is: 59.11
Add datafile SQL is: ALTER TABLESPACE "TEST" ADD DATAFILE SIZE 7291M AUTOEXTEND ON NEXT 100M MAXSIZE 32768M
Execute(ALTER TABLESPACE "TEST" ADD DATAFILE SIZE 7291M AUTOEXTEND ON NEXT 100M MAXSIZE 32768M) failed:ORA-03206: maximum file size of (4194304) blocks in AUTOEXTEND clause is out of range (DBD ERROR: OCIStmtExecute)
Disconnected from database

CAUSE

For small datafile tablespace, the maximum datafile size is 32GB ( 32768M ) in theory. But in actual situation, the given size should be little less than 32GB.

SOLUTION

Explicitly specify the maximum datafile size to 31GB ( 31744 M ), for example, instead of the default 32GB ( 32768M ) in corrective action parameters configuration.

Before

Maximum Datafile Size (GB)

After

Maximum Datafile Size (GB)31
...
..
.
OMF directory: +DATAC1
OMF disk group: DATAC1
ASM projected safely usable free space (MB) is:  28548641.667
ASM projected Space Used (%) is: 59.11
Add datafile SQL is: ALTER TABLESPACE "TEST" ADD DATAFILE SIZE 7291M AUTOEXTEND ON NEXT 100M MAXSIZE 31744M
Successfully added new datafile

Materialized View : OEM Monitoring and Alerting through Metric Extension( ME ), Incident Rule ( IR ) and Self Healing through Corrective Action( CA )

In previous posts, we have created following related posts to monitor FRA and auto backup archive logs:

  1. Create a Metric Extension (ME) to Monitor FRA Usage on OEM
  2. Create an Incident Rule for Metric Extension ( ME ) to Monitor FRA Used in OEM
  3. Use Corrective Action ( CA ) to Automate Archivelog Backup When FRA Usage is Over Threshold of Metric Extension ( ME ) in OEM

In this post, we will do the same thing for Materialized Views to monitor, alert and self heal the materialized views.

Subscribe to get access

Read more of this content when you subscribe today.

Subscribe

OEM Agent Home Page Shows ” Communication between the Oracle Management Service to the Agent is unavailable. Any features or displayed information requiring this communication will be unavailable”

After OMS upgraded to 13.4, the agent home pages are showing the following error:

Communication between the Oracle Management Service to the Agent is unavailable. Any features or displayed information requiring this communication will be unavailable

WORKAROUND

This is known issue because of SSLCipherSuites compatibility issue between OMS and Agents after OMS upgrading.

Run the following commands on EM agent server to resolve this issue:

$ emctl status agent

$ emctl pingOMS

$ emctl getproperty agent -name SSLCipherSuites
Oracle Enterprise Manager Cloud Control 13c Release 2
Copyright (c) 1996, 2016 Oracle Corporation.  All rights reserved.
SSLCipherSuites is unset; default value is SSL_RSA_WITH_RC4_128_MD5:SSL_RSA_WITH_RC4_128_SHA:SSL_RSA_WITH_3DES_EDE_CBC_SHA

$ emctl setproperty agent -name SSLCipherSuites -value TLS_RSA_WITH_AES_128_CBC_SHA:TLS_RSA_WITH_AES_256_CBC_SHA:RSA_WITH_AES_256_CBC_SHA256
Oracle Enterprise Manager Cloud Control 13c Release 2
Copyright (c) 1996, 2016 Oracle Corporation.  All rights reserved.
EMD setproperty succeeded

$ emctl getproperty agent -name SSLCipherSuites
Oracle Enterprise Manager Cloud Control 13c Release 2
Copyright (c) 1996, 2016 Oracle Corporation.  All rights reserved.
SSLCipherSuites=TLS_RSA_WITH_AES_128_CBC_SHA:TLS_RSA_WITH_AES_256_CBC_SHA:RSA_WITH_AES_256_CBC_SHA256

$ emctl stop agent

$ emctl start agent

How to Resolve OEM Agent ‘Availability Evaluation Error’

The following commands helped a client to resolve OEM agent “Availability Evaluation Error”. Just run them in sequence until the issue is resolved.

$ ping omshost
$ nslookup omshost
$ emctl pingOMS
$ emctl config agent addinternaltargets
$ emctl secure agent
$ emctl config agent listtargets
$ emctl clearstate agent

$ emctl upload agent
$ emctl reload agent

The agent should show UP now, otherwise continues the following steps:

$ emctl stop agent
$ emctl secure agent
$ emctl clearstate agent
$ emctl secure agent
$ emctl start agent
$ emctl upload agent 
$ emctl reload agent

$ emctl pingOMS 
$ emctl status agent

How to Reinstall and Configure OEM Cloud Control 13c Central Agent 

For some reason, a client has to reinstall OEM central agents in a multi-OMS Oracle Enterprise Manager Cloud Control environment. Certainly the agent has been installed on the same server as the OMS.

First keep a record of the plugins deployed onto the agent already.

$emctl listplugins agent

Then uninstall the agent cleanly as per How to Deinstall OEM Agents in Oracle Enterprise Manager 13C

The next is to install the agent with required plugins deployed.

Now we need discover all WebLogic Domain targes based on the following instructions, and then all those targets will be monitored by the central agent.

Subscribe to get access

Read more of this content when you subscribe today.

Subscribe