Uncategorized

WLS Startup Warnings after OBIEE 11.1.1.6 upgrade

After an OBIEE 11.1.1.6 in-place upgrade I accidentally found weird warnings in the startup log of WebLogic since the upgrade. “By accident” since the server started nicely and was available without loss of functionality or performance, so I never checked in detail what happens during startup.

The WLSStart.log contained the following nice list:

{May 1, 2012 9:36:03 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “discussion:Response” has no key column.  It will not be collected.}
{May 1, 2012 9:36:03 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “oracle_bi_instance:essbaseServerMetrics” has no key column.  It will not be collected.}
{May 1, 2012 9:36:03 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “oracle_bi_instance:wls_app_rollup” has no key column.  It will not be collected.}
{May 1, 2012 9:36:03 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “oracle_bi_instance:wls_web_rollup” has no key column.  It will not be collected.}
{May 1, 2012 9:36:03 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “oracle_bi_instance:wls_server” has no key column.  It will not be collected.}
{May 1, 2012 9:36:03 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “oracle_bi_instance:obis_rollup” has no key column.  It will not be collected.}
{May 1, 2012 9:36:03 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “oracle_bi_instance:obips_rollup” has no key column.  It will not be collected.}
{May 1, 2012 9:36:03 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “oracle_bi_instance:obips_requests_rate” has no key column.  It will not be collected.}
{May 1, 2012 9:36:05 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “webcache:request_filter_denied_stats” has no key column.  It will not be collected.}
{May 1, 2012 9:36:05 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “oracle_oim:overall” has no key column.  It will not be collected.}
{May 1, 2012 9:36:05 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “domain_oracle_oim:jdbc” has no key column.  It will not be collected.}
{May 1, 2012 9:36:05 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “oracle_soainfra:total_faults” has no key column.  It will not be collected.}
{May 1, 2012 9:36:06 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “portaltools:Response” has no key column.  It will not be collected.}
{May 1, 2012 9:36:06 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “weblogic_j2eeserver:jvm_runtime” has no key column.  It will not be collected.}
{May 1, 2012 9:36:06 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “weblogic_j2eeserver:jvm_compilation_time” has no key column.  It will not be collected.}
{May 1, 2012 9:36:06 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “weblogic_j2eeserver:jvm_memory_usage” has no key column.  It will not be collected.}
{May 1, 2012 9:36:06 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “weblogic_j2eeserver:jvm_class_loading” has no key column.  It will not be collected.}
{May 1, 2012 9:36:06 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “weblogic_j2eeserver:jvm_threads” has no key column.  It will not be collected.}
{May 1, 2012 9:36:07 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “essbaseapp:appMetrics” has no key column.  It will not be collected.}
{May 1, 2012 9:36:07 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “domain_oracle_oaam:OAAM_Datasource” has no key column.  It will not be collected.}
{May 1, 2012 9:36:07 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “oracle_forms:aggr_FormsResourceUsage” has no key column.  It will not be collected.}
{May 1, 2012 9:36:07 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “oracle_forms:NumberOfSessions” has no key column.  It will not be collected.}
{May 1, 2012 9:36:07 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “oracle_forms:JVMResourceUsage” has no key column.  It will not be collected.}
{May 1, 2012 9:36:07 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “oracle_forms:servlet_rollup_agg” has no key column.  It will not be collected.}
{May 1, 2012 9:36:07 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “reports:Reports_Server_Information” has no key column.  It will not be collected.}
{May 1, 2012 9:36:07 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “reports:Reports_Server_Performance” has no key column.  It will not be collected.}
{May 1, 2012 9:36:07 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “reports:Reports_Server_Response” has no key column.  It will not be collected.}
{May 1, 2012 9:36:07 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “reports:Reports_Servlet_Response” has no key column.  It will not be collected.}
{May 1, 2012 9:36:07 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “reports:Remote_Bridge_Elements” has no key column.  It will not be collected.}
{May 1, 2012 9:36:07 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “analytics:Response” has no key column.  It will not be collected.}
{May 1, 2012 9:36:07 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “portal:portal_page_engine_response_codes_delta” has no key column.  It will not be collected.}
{May 1, 2012 9:36:07 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “portal:portal_page_engine_response_codes” has no key column.  It will not be collected.}
{May 1, 2012 9:36:07 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “portal:portal_page_engine” has no key column.  It will not be collected.}
{May 1, 2012 9:36:07 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “activitygraph:Response” has no key column.  It will not be collected.}
{May 1, 2012 9:36:07 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “essbase:serverMetrics” has no key column.  It will not be collected.}
{May 1, 2012 9:36:07 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “oracle_federation:protocol_profiles_rollup” has no key column.  It will not be collected.}
{May 1, 2012 9:36:07 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “oracle_federation:protocol_profiles_events_rollup” has no key column.  It will not be collected.}
{May 1, 2012 9:36:07 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “oracle_federation:protocol_profiles_protocol_phase_events_rollup” has no key column.  It will not be collected.}
{May 1, 2012 9:36:08 AM CEST} {Warning} {oracle.dms.collector} {BEA-000000} {Metric table “personalization:Response” has no key column.  It will not be collected.}

Browsing through MOS I found MOS document ID 1434193.1 which states: 

Cause:
This is known to be caused by a change to the Metric Service.
This does not cause any functional problem and it is expected to be fixed in the future versions. An internal bug is logged and progressed to have this addressed.

Solution:
The warnings can be ignored as it has no affect on the Reports Servers and the its functionality. 

So really good to know in case you are browsing your log files for warnings and come across this.

Cheers!

Related Posts

Leave a Comment