Installing CM Patch May Require Manual IPSA DB Package Drop

(Doc ID 1069884.1)

Last updated on AUGUST 21, 2016

Applies to:

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


When a CM / IPSA patch is applied there may be a need to also manually drop an IPSA DB package as there is a fix for <> which requires this. Indication of this being required is the presence of the following error in the NP log or a on-demand or scheduled archive.

20100119-073008|926|ERROR|Thread-6||||proxy_np|kronwandl|Problem while trying to write the device changes information to the database
java.sql.SQLException: ORA-06550: line 1, column 7:
PLS-00306: wrong number or types of arguments in call to 'WRITE_DEVICE_CHANGE'
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored

       at oracle.jdbc.driver.DatabaseError.throwSqlException(
       at oracle.jdbc.driver.T2CConnection.checkError(
       at oracle.jdbc.driver.T2CConnection.checkError(
       at oracle.jdbc.driver.T2CCallableStatement.execute_for_describe(
       at oracle.jdbc.driver.T2CCallableStatement.execute_for_rows(
       at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(
       at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(
       at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(
       at oracle.jdbc.driver.OracleCallableStatement.executeUpdate(
       at com.metasolv.serviceactivator.util.database.DatabaseUtil.updateDeviceHadChanges(
       at com.metasolv.serviceactivator.networkprocessor.CommitQueueAuditItem.updateDeviceChangeInfo(
       at com.metasolv.serviceactivator.util.ThreadPool$


Recent application of IPSA / CM patch. Specifically CM 5.2.4 patch 1


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