Invalid Data Type for SQL
Posted 16 June 2003 - 04:24 AM
368 - SQL ERROR : INVALID DATA TYPE FOR SQL
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?????????
Posted 16 June 2003 - 05:20 AM
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.
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.
Posted 16 June 2003 - 12:23 PM
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.
Posted 16 June 2003 - 01:00 PM
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.
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users