8 replies to this topic

[Yee Ming Yew]

We are recently using PROIV kernel from 5.5 build 401 to 5.5 build 407. Since then I've been facing this problem

SQL Level
368 - SQL ERROR : INVALID DATA TYPE FOR SQL

PROIV Level
filedef=FILEXXX Mismatch - regen required

I have install the build 407 bootstrap onto my existing PROIV bootstrap directory (build 401). I've been doing this way of upgrading since the last 2 builds of PROIV 5.5, and it seems to be fine until in this one.

Refer to our previous post of this problem, we have been told that there will be a fixed for kernel in next release. Do any one have any idea this problem has been fixed?????????

[Rob Donovan]

Hi,

I think that is the 'Client' version number that you gave us (401 & 407), not the kernel version.

The Kernel version (currently at 5.5r221), is below the client version in the Help/About menu.

How did you upgrade?

The safest method of upgrading ProIV should be as follows,

• Export all functions,files,Global Logics and Value Vars from the old system.
• Install the new version of ProIV into a new dir.
• Import all functions,files,Global Logics and Value Vars.
• Regen all functions.

I would not be sure that this is the problem, but its just the way I always upgrade ProIV accounts and I have never had any problems following these steps.

Also, try putting the SQL trace option (TRACELSQL = 15) on ProIV and see what the actual SQL statement is being sent to Oracle. It may give you some hints.

Rob D.

[Yee Ming Yew]

Thanks Rob,
I will try it now.

[Yee Ming Yew]

Sorry, forgot to mention that I am using Linux version. PRO-IV hasn¡¦t release the version 5.5v221 for Linux.

[Andrew Morgan]

Hi,

This message now appears if a file def has changed and you have not regened all the functions using it.

If a global function access the same file(s) as the calling function and the global function has not been genned after a file change PROIV sometimes gave a Thread Exception, since the new SQL Layer this message now appers.


Andrew

[Wim Soutendijk]

In addition to that, you will have to log out on all sessions after the regen to get rid of the message for all users.
I you have used the function prior to the change and the regen has taken place in another session, you can still get the error message.

[Yee Ming Yew]

Thanks a lot, I had try all the suggestion but the problem still happen. Is there any better solution for this problem?


Rob, May I know how to activate the SQL trace log?

Thanks

[Rob Donovan]

Hi,

There are 2 methods of logging SQL...

TRACELSQL and SQL_DEBUG.

Take a look at this post, it explains how to use them....

http://www.proivrc.c...27&hl=sql_debug

Rob D