Jump to content


Photo
- - - - -

Invalid Data Type for SQL


8 replies to this topic

#1 Yee Ming Yew

Yee Ming Yew

    Newbie

  • Members
  • Pip
  • 6 posts
  • Gender:Male
  • Location:Puchong, Malaysia

Posted 16 June 2003 - 04:24 AM

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?????????

#2 Rob Donovan

Rob Donovan

    rob@proivrc.com

  • Admin
  • 1,640 posts
  • Gender:Male
  • Location:Spain

Posted 16 June 2003 - 05:20 AM

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.

#3 Yee Ming Yew

Yee Ming Yew

    Newbie

  • Members
  • Pip
  • 6 posts
  • Gender:Male
  • Location:Puchong, Malaysia

Posted 16 June 2003 - 05:51 AM

Thanks Rob,
I will try it now.

#4 Yee Ming Yew

Yee Ming Yew

    Newbie

  • Members
  • Pip
  • 6 posts
  • Gender:Male
  • Location:Puchong, Malaysia

Posted 16 June 2003 - 06:17 AM

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

#5 Andrew Morgan

Andrew Morgan

    Newbie

  • Members
  • Pip
  • 5 posts
  • Location:United Kingdom

Posted 16 June 2003 - 12:23 PM

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

#6 Wim Soutendijk

Wim Soutendijk

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 211 posts
  • Gender:Male
  • Location:Netherlands

Posted 16 June 2003 - 01:00 PM

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.

#7 Yee Ming Yew

Yee Ming Yew

    Newbie

  • Members
  • Pip
  • 6 posts
  • Gender:Male
  • Location:Puchong, Malaysia

Posted 18 June 2003 - 06:08 AM

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

#8 Rob Donovan

Rob Donovan

    rob@proivrc.com

  • Admin
  • 1,640 posts
  • Gender:Male
  • Location:Spain

Posted 18 June 2003 - 06:47 AM

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

#9 Guest_Jesus_*

Guest_Jesus_*
  • Guests

Posted 04 August 2003 - 01:10 PM

Exiting the application and then killing the connection allegedly sorts this issue, and it only usually happens to the dev that genned the function, the issue id allegedly with proiv sup.



Reply to this topic



  


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users