oracle - Failed to execute stored procedure in different database? -


The stored procedure that performs well with the development database but fails to execute in the production database? Error returned: "PLS-00306: Call code in and Lieutenant process; "Wrong number or type of argument type"> VC ++ database Oracle

Closed: An error occurred due to incorrect synonyms.

In this error, you are not performing any problems in the process of the way this error is executed You are calling it in a database versus the other, what to do with it. This is a collar in DEV which is sending the correct combination of parameters and parameter types. The logic, which is finally calling the process in Prodi, is sending a different combination of parameters.

First see the procedure specification in both databases, to ensure that it is actually the same. See differences in parameters, data types, or any difference in the default faucet or similar.

Check the logic calling the actual process between the next database. Generally it will be lost in one of the parameters or the data type will be incorrect. If you are not using nominated signaling, then the order of your parameters is also important.

If you are finally sure that all are equal, then it is possible that one of the parameters coming in and your C ++ drivers are not calling the same phone in the process

< P> This is a concrete and obvious error and it is telling you that there is some difference in how this is finally being told. good luck.


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -