Uncategorized

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!

Uncategorized

In-place upgrade within OBIEE 11 versions (from .3 to .5 o r .6 or from .5 to .6) can be a whole lot quicker than out-of-place ones but are also more interesting in terms of potential issues arising. After two uneventful in-place upgrades from 11.1.1.5 to 11.1.1.6 I had a more challenging third upgrade with some unexpected errors.

If you look at the official upgrade guide, all went fine up to item 6: “Upgrading system components“. Executing upgradenonj2eeapp.sh, however, threw an error while re-deploying:

./upgradenonj2eeapp.sh -oracleInstance /bishiphome/Middleware/instances/myinstance/ -adminHost localhost -adminPort 7001 -adminUsername weblogic

Command failed: NonJ2EEManagement Applicationdeployment failed.


Looking into the provision.log (situated in MW_HOME/instances/myinstance/diagnostics/logs/OPMN/opmn) read as follows:

[Deployer:149163]The domain edit lock is owned by another session in non-exclusive mode – this deployment operation requires exclusive access to the edit lock and hence cannot proceed. If you are using “Automatically Aquire Lock and Activate Changes” in the console, then the lock will expire shortly so retry this operation.


I ran the upgradenonj2eeapp.sh a second time to see what it would do:

SEVERE: Command failed:
oracle.as.config.ProvisionException: Exception while unregistering the instance
    at oracle.as.config.impl.OracleASInstanceImpl.unregister(OracleASInstanceImpl.java:290)
    at oracle.as.config.impl.OracleASInstanceImpl.unregister(OracleASInstanceImpl.java:250)
    at oracle.as.config.provisioner.commands.UnregisterInstanceCommand.execute(UnregisterInstanceCommand.java:34)
    at oracle.as.config.provisioner.InstallerCmdLine.run(InstallerCmdLine.java:146)
    at oracle.as.config.provisioner.InstallerCmdLine.main(InstallerCmdLine.java:46)
Caused by: oracle.as.config.impl.SimpleProvisionException: Failed to unregister instance instance1. It does not exist on the adminserver.

So, a real no-go situation. Luckily, the OBIEE EMG already had a post which contained part of the solution. Root cause of the initial error was that there was a lock on the configuration I hadn’t seen:
“Release Configuration” removed the immediate error source. Next step was re-running upgradenonj2eeapp.sh again to see what would happen and obviously the error “Failed to unregister instance instance1. It does not exist on the adminserver.” still persisted since initially the first half of the script had run through and un-registered my instance. So off to some opmnctl commands to undo the damage.

1.) Deploy the instance again:

./opmnctl redeploy -oracleInstance /bishiphome/Middleware/instances/myinstance -adminHost localhost -adminPort 7001 -adminUsername weblogic

Command requires login to weblogic admin server (localhost):
  Username: weblogic
  Password:

Redeploying NonJ2EEManagement Application…weblogic.Deployer invoked with options:  -adminurl localhost:7001 -username weblogic -name NonJ2EEManagement -source /bishiphome/Middleware/Oracle_BI1/opmn/applications/NonJ2EEManagement.ear -redeploy -upload -noexit

Task 1 initiated: [Deployer:149026]deploy application NonJ2EEManagement [Version=11.1.1] on AdminServer.
Task 1 completed: [Deployer:149026]deploy application NonJ2EEManagement [Version=11.1.1] on AdminServer.
Target state: redeploy completed on Server AdminServer

Done
Command succeeded.


2.) Register the instance again:

./opmnctl registerinstance

Command requires login to weblogic admin server (localhost):
  Username: weblogic
  Password:

Registering instance
Command succeeded.

 After these steps, I was able to run the actual shell for the upgrade process again:

./upgradenonj2eeapp.sh -oracleInstance /bishiphome/Middleware/instances/instance1/ -adminHost localhost -adminPort 7001 -adminUsername weblogic
Unregister instance…

Command requires login to weblogic admin server (localhost):
Username: weblogic
Password:

Unregistering instance
Command succeeded.
redeploy NonJ2EEManagement.ear…

Command requires login to weblogic admin server (localhost):
Username: weblogic
Password:

Redeploying NonJ2EEManagement Application…weblogic.Deployer invoked with options:  -adminurl localhost:7001 -username weblogic -name NonJ2EEManagement -source /bishiphome/Middleware/Oracle_BI1/opmn/applications/NonJ2EEManagement.ear -redeploy -upload -noexit

Task 2 initiated: [Deployer:149026]deploy application NonJ2EEManagement [Version=11.1.1] on AdminServer.
Task 2 completed: [Deployer:149026]deploy application NonJ2EEManagement [Version=11.1.1] on AdminServer.
Target state: redeploy completed on Server AdminServer

Done
Command succeeded.
re-register instance…

Command requires login to weblogic admin server (localhost):
Username: weblogic
Password:

Registering instance
Command succeeded.
Successfully upgraded NonJ2EEManagement.ear and the registeration.

 One of those little things that can ruin your evening…

Cheers!