Results 1 to 4 of 4
  1. #1
    Join Date
    Jun 2003
    Posts
    77

    Question Unanswered: problem in char function, getting SQL0440N

    Hi,

    I've DB2v 7.2 running on windows 2000/NT server.
    The database was working alright untill recently when we've got this strange problem.
    The function char() is not working when used with a schema name.

    Like when I do the following from command center or thru the java code-

    (I've a schema named test which was working fine and has not been changed.)

    create table test.newtable ( name char(12) );

    insert into table test.newtable values( 'myname');

    on doing-

    select * from test.newtable where test.char(name)= 'myname'

    it gives SQL0440N error saying no function by the name char having compatible arguments was found in the function path.

    The same thing was working fine before. I dont know what is causing this problem. No java applications on this database are able to work due to this error.

    when I repeat the same by creating a system table(create table newtable) instead of giving the schema name, it works fine.

    Please let me know if someone knows the cause of this proble.

    Thansk a lot,
    -Preeti

  2. #2
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    What Fixpak level are you at? The latest is Fixpak 10a.
    http://www-3.ibm.com/cgi-bin/db2www/...ist.d2w/report

  3. #3
    Join Date
    Jun 2003
    Location
    Canada
    Posts
    35

    unleast it is a typo ...

    Maybe it is just in an error when you entered your problem in the forum but since you say it does not happens when you use the default schema ...

    select * from test.newtable where test.char(name)= 'myname'


    Might it be that the where should be:

    where char(name)= 'myname'

    or more implicit:

    where char(test.newtable.name)= 'myname'

  4. #4
    Join Date
    Jun 2003
    Posts
    77

    Thumbs up

    Thanks to you both for your replies.

    I've not applied any fixpaks to DB2 7.2 version yet.
    Please let me know if you've experienced the same problem and applied a fixpak to solve it.

    I found the solution to this problem in one of the previous archives of this forum which I want to share with you

    If you go to http://dbforums.com/t643618.html , it has been posted that this problem can occur if someone has changed the system time, and setting back the time of system to default would solve it.
    I followed this and it worked.

    Thanks again for your help.
    -Preeti

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •