Upgrade From 7.2.0.10 To 7.2.0.12 Fails with Error PLS-00306: wrong number or types of arguments in call to 'GET_AVAILABLE_ORDER_ID_BLOCK' (Doc ID 2220920.1)

Last updated on JANUARY 16, 2020

Applies to:

Goal

OSM was upgraded from 7.2.0.10.2 to 7.2.0.12.0. It was successful with no errors in the UI.
Post upgrade - you are unable to create an order as it is failing because of below error as seen in the logs.


ERROR in a log:
-----------------------
<05-Jan-2017 2:44:06,157 EST PM> <ERROR> <core.logSQLException> <Thread-61> <SQL Exception 6,550 : ORA-06550: line 1, column 7:
PLS-00306: wrong number or types of arguments in call to 'GET_AVAILABLE_ORDER_ID_BLOCK'
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
>
java.sql.SQLException: ORA-06550: line 1, column 7:
PLS-00306: wrong number or types of arguments in call to 'GET_AVAILABLE_ORDER_ID_BLOCK'
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored

       at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:462)
       at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405)
       at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:931)
       at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:481)
       at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205)
       at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:548)
       at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:213)
       at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:1111)
       at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1488)
       at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3760)
       at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3945)
       at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:9259)
       at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1537)
      

In installLog.txt found following error:

-------------------------------------------

Thu Jan 05 12:09:04 EST 2017: BEAConfig:  OMS EAR FILE /opt/app/osm/OSM_Patch_7_2_0_12_0/bin/oms.ear
weblogic.Deployer invoked with options:  -adminurl t3://<DomainName>:9001 -user weblogic -source /opt/app/osm/OSM_Patch_7_2_0_12_0/bin/oms.ear -name oms -targets ucmsvt2_cls -deploy -upload -timeout 600 -verbose -noexit -usenonexclusivelock
<Jan 5, 2017 12:09:08 PM EST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, oms [archive: /opt/app/osm/OSM_Patch_7_2_0_12_0/bin/oms.ear], to ucmsvt2_cls .>
Task 20 initiated: [Deployer:149026]deploy application oms on ucmsvt2_cls.
Task 20 failed: [Deployer:149026]deploy application oms on ucmsvt2_cls.
Target state: deploy failed on Cluster ucmsvt2_cls
Context path '/oms' is already in use by the module: oms application: oms.ear
Context path '/oms' is already in use by the module: oms application: oms.ear
Context path '/oms' is already in use by the module: oms application: oms.ear

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.