Results 1 to 7 of 7
  1. #1
    Join Date
    Aug 2015
    Posts
    16

    Answered: SQL0104N An unexpected token "D:\Program" was found following "<identifier>".

    Dear Team
    Need your assistance, i receive below error when tried to update db cfg LOGARCHMETH1

    update db cfg for xxx using LOGARCHMETH1 DISK: D:\Program File\veritas\netbackup\bin\nbdb2.dll

    SQL0104N An unexpected token "D:\Program" was found following "<identifier>".
    Expected tokens may include: "ALT_COLLATE". SQLSTATE=42601

    Operating System :Windows Server 2012 Standard Edition
    Database DB2 :- DB2 v9.7.1100

    Appreciate your assitance

    Thank you
    Amy Badri

  2. Best Answer
    Posted by mark.b

    "Dear Amy,

    There is no any impact of db2 API use. It's just another way of setting db2 database parameters, but this requires C/C++ programming.
    You can read about NTFS junction points here: junction point.
    Just create the following link: D:\ProgramFile -> D:\Program File
    And use this:

    update db cfg for xxx using LOGARCHMETH1 VENDOR: D:\ProgramFile\veritas\netbackup\bin\nbdb2.dll
    (don't forget to remove the space between : and D)"


  3. #2
    Join Date
    Jul 2013
    Location
    Moscow, Russia
    Posts
    666
    Provided Answers: 55
    Hi,

    try this:
    update db cfg for xxx using LOGARCHMETH1 VENDOR:'D:\Program File\veritas\netbackup\bin\nbdb2.dll'
    or
    update db cfg for xxx using LOGARCHMETH1 VENDOR: D:\progra~1\veritas\netbackup\bin\nbdb2.dll
    Don't specify a space between : and D above (I did it since this site converts the concatenation of these symbols to a smile )
    Last edited by mark.b; 06-20-16 at 11:56.
    Regards,
    Mark.

  4. #3
    Join Date
    Aug 2015
    Posts
    16
    Dear Mark

    Im still received same error .

    db2 => update db cfg for xxx using LOGARCHMETH1 VENDOR:'D:\Program File\veritas\netbackup\bin\nbdb2.dll'

    SQL0104N An unexpected token "'D:\Program File\veritas\netbackup\bin\nbdb2"
    was found following "<identifier>". Expected tokens may include:
    "ALT_COLLATE". SQLSTATE=42601


    But for below received different error. is it mean patch does not exist?
    db2 => update db cfg for xxx using LOGARCHMETH1 VENDOR: D:\progra~1\veritas\netbackup\bin\nbdb2.dll

    SQL5099N The value "D:\progra~1\veritas\netbackup\bin\nbdb2.dll" indicated by
    the database configuration parameter "LOGARCHMETH1" is not valid, reason code
    "2". SQLSTATE=08004



    Thank you
    Amy Badri

  5. #4
    Join Date
    Jul 2013
    Location
    Moscow, Russia
    Posts
    666
    Provided Answers: 55
    Seems there is a problem with a path with a space in it.
    There is a suggestion to use some API to set such a path if needed.
    http://www.ibm.com/support/knowledge...=SSEPGG_10.5.0

    But I'd suggest you to create a junction point without a space in the name pointing to the library, and use this junction in the db2 parameter.
    Regards,
    Mark.

  6. #5
    Join Date
    Aug 2015
    Posts
    16
    Dear Mark

    is there any impact on db2 Cfg Set API ? especially on life production environment ?
    is it correct need to naming back Program File to Program_File or ProgramFile ?
    what do you mean on create a junction point ?

    Appreciate your kind assistance



    Thank you

  7. #6
    Join Date
    Jul 2013
    Location
    Moscow, Russia
    Posts
    666
    Provided Answers: 55
    Dear Amy,

    There is no any impact of db2 API use. It's just another way of setting db2 database parameters, but this requires C/C++ programming.
    You can read about NTFS junction points here: junction point.
    Just create the following link: D:\ProgramFile -> D:\Program File
    And use this:

    update db cfg for xxx using LOGARCHMETH1 VENDOR: D:\ProgramFile\veritas\netbackup\bin\nbdb2.dll
    (don't forget to remove the space between : and D)
    Last edited by mark.b; 06-21-16 at 03:40.
    Regards,
    Mark.

  8. #7
    Join Date
    Aug 2015
    Posts
    16
    Dear Mark

    Manage to update db cfg LOGARCMETH by using below command
    db2 => update db cfg for XXXX using LOGARCHMETH1 'VENDOR:\Program Files\bin\nbdb2.dll'


    Thank you for guide and assistance to solve this issue


    Rgds
    Amy Badri

Tags for this Thread

Posting Permissions

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