CM Upgrade 5.2.3 to 5.2.4 generates DB errors when trying to deploy the CM application in weblogic console (Doc ID 1267366.1)

Last updated on AUGUST 21, 2016

Applies to:

Oracle Communications Configuration Management - Version: 5.2.3 and later   [Release: 5.2 and later ]
Information in this document applies to any platform.

Symptoms

When upgrading CM 5.2.3 to CM 5.2.4, the following errors was seen in the weblogic console (when trying to deploy the CM application) and also in the nohup.out (if running WL with nohup), or on the command line:

[EJB:011028]The DataSource with the JNDI name: CM/Datasource could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.

[EJB:011020]The database table: ip_mappings does not contain the columns: device_id. Please consult your database mappings in the weblogic-cmp-rdbms.xml deployment descriptor and ensure these match your database schema.

[EJB:011020]The database table: cm_workitem does not contain the columns: archive_permissions. Please consult your database mappings in the weblogic-cmp-rdbms.xml deployment descriptor and ensure these match your database schema.



Changes

Recent IPSA and CM upgrade from 5.2.3 to 5.2.4

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms