I have been revising a number of my configuration extensions recently and when they were first put in I was running 22.214.171.124 OEM and 126.96.36.199 agents. Now we are on 188.8.131.52 with a mixture of 184.108.40.206 and 220.127.116.11 agents. I noticed a couple of things…
18.104.22.168 OEM and 22.214.171.124 Agent
Unfortunately I never noted down the maximum number of characters you could have in a configuration extension (but I would assume it is restricted by the agent version and will therefore be the same as below) with this combination however, if you do hit the maximum limit you will receive a Java error in the console. This behaviour changes in 126.96.36.199.
188.8.131.52 OEM and 184.108.40.206 Agent
Now from 220.127.116.11 onwards if there is an issue with your configuration extension and you preview you it via the console you won’t receive ANY errors. The preview box will come back with ‘no data to display’. If you take a look at the logs at the back end you will see the java collection error. The maximum number of characters seems to be around 3700 in total.
18.104.22.168 OEM and 22.214.171.124 Agent
When you are running 126.96.36.199 OEM and agents it seems that the maximum character limit has been significantly increased, in fact increased to the point in which stopped testing, I got a bit bored at 17000 characters. To give you an idea this is like 30 SQL statements like this:
select distinct(grantee) from dba_tab_privs where table_name in ('DBA_JOBS')
and grantee not in ('SYS','SYSTEM','SYSMAN','DBA','WMSYS','DBSNMP','OUTLN','EXFSYS',
'ORDSYS','APEX_040100') group by grantee
If you are running on 188.8.131.52 and are thinking about using configuration extensions then it makes a lot of sense to move to 184.108.40.206 as you could probably store all your SQL in a single extension instead of spreading them across multiple extensions.