Results 1 to 12 of 12
  1. #1
    Join Date
    Nov 2010
    Posts
    21

    Unanswered: getting SQL1428N after creating federated view

    Dear All,
    DB2 Version: 9.7 fp5
    AIX 6.1

    We are having 7 instances on our server and out of them 6 are multipartition and one is single partition.
    I have created one federated view in single partition instance with reference of a table in multipartition instance.
    There is one script is running which is checking connectivity for all the databases 4 times a day, at the time of script execution, we are getting severe messages in db2diag log file in the form of SQL1428N.
    I am clueless, no errors reported from users and I am not getting any information about this anywhere.

    Any help will be appreciated.

    -Harsh

  2. #2
    Join Date
    Sep 2013
    Location
    India
    Posts
    246
    please post the full diag error message. is the view working fine ? also post the commands you used to for configuring federation (node,wrapper,server,mapping).
    ssumit

  3. #3
    Join Date
    Nov 2010
    Posts
    21
    View is working fine.
    commands for the same is below:

    we have cataloged the node then database and then used below commands to create federated view:

    bash-3.00$ db2 "create wrapper drda97 library 'libdb2drda.a'"

    DB20000I The SQL command completed successfully.



    bash-3.00$ db2 "CREATE SERVER FED_SVR_97 TYPE DB2/UDB VERSION 9.7 WRAPPER DRDA97 AUTHORIZATION "xxxxx" PASSWORD "zzzzzzzz" OPTIONS(DBNAME 'zzzzzzz', FOLD_ID 'L', FOLD_PW 'L')"

    DB20000I The SQL command completed successfully.



    bash-3.00$ db2 "CREATE USER MAPPING FOR xxxxxx SERVER FED_SVR_97 OPTIONS (REMOTE_AUTHID 'xxxx', REMOTE_PASSWORD 'xxxxxxxx')"

    DB20000I The SQL command completed successfully.



    db2 "CREATE NICKNAME xxx.AO_RCC_MAP FOR FED_SVR_97.xxxx.AO_RCC_MAP"

    DB20000I The SQL command completed successfully.

    SNAP FROM DIAG LOG IS BELOW:

    Log: 22072014 TIME 10:07:05 Database paamdb is connected

    2014-07-22-10.04.15.517178+330 I699935916A740 LEVEL: Severe

    PID : 15466964 TID : 1 PROC : db2bp

    INSTANCE: paaminst NODE : 000

    APPID : *LOCAL.paaminst.140722043414

    EDUID : 1

    FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary logging func, probe:0 DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes

    sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1428 sqlerrml: 15

    sqlerrmc: PAAMINST TPRNDE

    sqlerrp : SQLEIMAT

    sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000

    (4) 0x00000000 (5) 0x00000000 (6) 0x00000000

    sqlwarn : (1) (2) (3) (4) (5) (6)

    (7) (8) (9) (10) (11)

    sqlstate:

    2014-07-22-10.04.15.517415+330 I699936657A5689 LEVEL: Severe

    PID : 15466964 TID : 1 PROC : db2bp

    INSTANCE: paaminst NODE : 000

    APPID : *LOCAL.paaminst.140722043414

    EDUID : 1

    FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary logging func, probe:0 MESSAGE : DB2RA DATA #1 : Hexdump, 1048 bytes

    0x0000000110133880 : 4442 3236 3452 4120 0000 0418 0107 0003 DB264RA ........

    0x0000000110133890 : 0006 0040 0000 0000 0000 0008 8000 0009 ...@............

    0x00000001101338A0 : 0000 0001 1001 0F70 0000 0009 4000 0001 .......p....@...

    0x00000001101338B0 : 0FFF FFFF FFFF E890 0000 0000 4000 0001 ............@...

    0x00000001101338C0 : 0000 0000 0000 0000 0000 000E 4000 0001 ............@...

    0x00000001101338D0 : 0FFF FFFF FFFF E8A8 0000 0004 4000 0002 ............@...

    0x00000001101338E0 : 0FFF FFFF FFFF EA60 0004 0000 8000 0012 .......`........

    0x00000001101338F0 : 0000 0001 1023 CFE0 0000 0004 8000 0002 .....#..........

    0x0000000110133900 : 0FFF FFFF FFFF F1A8 0000 0004 8000 0002 ................

    0x0000000110133910 : 0FFF FFFF FFFF F1AC 0000 0004 8000 0002 ................

    0x0000000110133920 : 0FFF FFFF FFFF F1B0 0000 0004 8000 0002 ................

    0x0000000110133930 : 0FFF FFFF FFFF F1B4 0000 0004 8000 0002 ................

    0x0000000110133940 : 0FFF FFFF FFFF F1B8 0000 0004 8000 0002 ................

    0x0000000110133950 : 0FFF FFFF FFFF F1BC 0000 0004 8000 0002 ................

    0x0000000110133960 : 0FFF FFFF FFFF F1C0 0000 0004 8000 0002 ................

    0x0000000110133970 : 0FFF FFFF FFFF F1C4 0000 0004 8000 0002 ................

    0x0000000110133980 : 0FFF FFFF FFFF F1C8 0000 0004 8000 0002 ................

    0x0000000110133990 : 0FFF FFFF FFFF F1CC 0000 0004 8000 0002 ................

    0x00000001101339A0 : 0FFF FFFF FFFF F1D0 0000 0004 4000 0007 ............@...

    0x00000001101339B0 : 0FFF FFFF FFFF F1D4 0000 0004 8000 0007 ................

    0x00000001101339C0 : 0FFF FFFF FFFF F1D8 0000 0004 8000 0007 ................

    0x00000001101339D0 : 0FFF FFFF FFFF F1DC 0000 0004 8000 0007 ................

    0x00000001101339E0 : 0FFF FFFF FFFF F1E0 0000 0004 4000 0007 ............@...

    0x00000001101339F0 : 0FFF FFFF FFFF F1E4 0000 0004 8000 0007 ................

    0x0000000110133A00 : 0FFF FFFF FFFF F1E8 0000 0004 8000 0007 ................

    0x0000000110133A10 : 0FFF FFFF FFFF F1EC 0000 0004 8000 0007 ................

    0x0000000110133A20 : 0FFF FFFF FFFF F1F0 0000 0004 4000 0007 ............@...

    0x0000000110133A30 : 0FFF FFFF FFFF F1F4 0000 0004 8000 0007 ................

    0x0000000110133A40 : 0FFF FFFF FFFF F1F8 0000 0004 8000 0007 ................

    0x0000000110133A50 : 0FFF FFFF FFFF F1FC 0000 0004 8000 0007 ................

    0x0000000110133A60 : 0FFF FFFF FFFF F200 0000 0004 4000 0007 ............@...

    0x0000000110133A70 : 0FFF FFFF FFFF F204 0000 0004 8000 0007 ................

    0x0000000110133A80 : 0FFF FFFF FFFF F208 0000 0004 8000 0007 ................

    0x0000000110133A90 : 0FFF FFFF FFFF F20C 0000 0004 8000 0007 ................

    0x0000000110133AA0 : 0FFF FFFF FFFF F210 0000 0004 4000 0007 ............@...

    0x0000000110133AB0 : 0FFF FFFF FFFF F214 0000 0004 8000 0007 ................

    0x0000000110133AC0 : 0FFF FFFF FFFF F218 0000 0004 8000 0007 ................

    0x0000000110133AD0 : 0FFF FFFF FFFF F21C 0000 0004 8000 0007 ................

    0x0000000110133AE0 : 0FFF FFFF FFFF F220 0000 0004 4000 0007 ....... ....@...

    0x0000000110133AF0 : 0FFF FFFF FFFF F224 0000 0004 8000 0007 .......$........

    0x0000000110133B00 : 0FFF FFFF FFFF F228 0000 0004 8000 0007 .......(........

    0x0000000110133B10 : 0FFF FFFF FFFF F22C 0000 0004 8000 0007 .......,........

    0x0000000110133B20 : 0FFF FFFF FFFF F230 0000 0004 4000 0007 .......0....@...

    0x0000000110133B30 : 0FFF FFFF FFFF F234 0000 0004 8000 0007 .......4........

    0x0000000110133B40 : 0FFF FFFF FFFF F238 0000 0004 8000 0007 .......8........

    0x0000000110133B50 : 0FFF FFFF FFFF F23C 0000 0004 8000 0007 .......<........

    0x0000000110133B60 : 0FFF FFFF FFFF F240 0000 0014 8000 0001 .......@........

    0x0000000110133B70 : 0FFF FFFF FFFF F234 0000 0014 8000 0001 .......4........

    0x0000000110133B80 : 0FFF FFFF FFFF F248 0000 0014 8000 0001 .......H........

    0x0000000110133B90 : 0FFF FFFF FFFF F25C 0000 000E 8000 0001 .......\........

    0x0000000110133BA0 : 0FFF FFFF FFFF F278 0000 0004 8000 0002 .......x........

    0x0000000110133BB0 : 0FFF FFFF FFFF F290 0000 0004 8000 0002 ................

    0x0000000110133BC0 : 0FFF FFFF FFFF F294 0000 0004 8000 0002 ................

    0x0000000110133BD0 : 0FFF FFFF FFFF F288 0000 0002 8000 0003 ................

    0x0000000110133BE0 : 0FFF FFFF FFFF F286 0000 0004 8000 0002 ................

    0x0000000110133BF0 : 0FFF FFFF FFFF F28C 0000 0004 4000 0002 ............@...

    0x0000000110133C00 : 0000 0001 1012 6740 0000 0004 4000 0002 ......g@....@...

    0x0000000110133C10 : 0000 0001 1012 6744 0000 0004 4000 0002 ......gD....@...

    0x0000000110133C20 : 0000 0001 1012 6748 0000 0007 4000 0001 ......gH....@...

    0x0000000110133C30 : 0000 0001 1012 674C 0000 0007 4000 0001 ......gL....@...

    0x0000000110133C40 : 0000 0001 1013 3CC0 0000 0001 4000 0001 ......<.....@...

    0x0000000110133C50 : 0FFF FFFF FFFF EA88 0000 0002 4000 0008 ............@...

    0x0000000110133C60 : 0FFF FFFF FFFF E860 0000 0000 4000 0001 .......`....@...

    0x0000000110133C70 : 0000 0000 0000 0000 0000 0002 4000 0008 ............@...

    0x0000000110133C80 : 0FFF FFFF FFFF E862 0000 0004 4000 0002 .......b....@...

    0x0000000110133C90 : 0FFF FFFF FFFF EA98 ........

    -Harsh

  4. #4
    Join Date
    Sep 2013
    Location
    India
    Posts
    246
    Hi,

    The messages coming in diag is not related to your federation. They might be written by logger in response to some / any one activities listed below:

    1. space filled for db2dump directory apth.
    2. recent index / reorg failed restarted.
    3. recent restart of server/instance/db.
    4. recent version upgrade of instance/db.
    etc.

    please check some binary dumps are also written in db2dump or not. The messages are harmless, you can ignore.

    You can try

    db2rbind dbname -l logfile.txt all to test that messages not come again.

    for further investigation try to find the trend (time wise,event wise etc) when those messages are written to diag.

    please post the outcome/ resolution.

    ssumit
    ssumit

  5. #5
    Join Date
    Nov 2010
    Posts
    21
    Thanks for your response sumit:

    The Node TPRNDE in diag log is the node where I have cataloged the remote database.
    I have tried uncataloging this remote db, no such errors are in db2diag file after uncataloging of remote db.
    Again I have catataloged the remote db and error re-appears.

    This error always comes at the time we are executing db2 connectivity check script.

    -Harsh

  6. #6
    Join Date
    Sep 2013
    Location
    India
    Posts
    246
    Hi,

    Certainly some commands are triggering those messages to the diag. Can u post the script body.
    ssumit

  7. #7
    Join Date
    Nov 2010
    Posts
    21
    su - instance -c db2 connect to dbname
    su - instance -c db2 terminate

    This is the only command (for all the databases)

    -Harsh

  8. #8
    Join Date
    Sep 2013
    Location
    India
    Posts
    246
    Hello harshrpce ,

    Its clear now, The reason for the messages is the issuance of command:

    su - instance -c db2 terminate


    Db terminate will kill all the processes running on server which are communicating with any client connected, during this DB2 tries to free all the IPC (Inter Process Communications) resource and in turn write the error messages in diag.

    Please confirm , hope you have set DBM CFG parameter KEEPFENCED=YES.
    If set to "NO" then such message will always come in diag.

    You can safely ignore the messages.

    ssumit
    ssumit

  9. #9
    Join Date
    Nov 2010
    Posts
    21
    Hi ssumit,
    Thanks for your response, that parameter is set to YES.
    I have commented that terminate command, will see if error occurs again.
    will share the same if happens....

    -Harsh

  10. #10
    Join Date
    Nov 2010
    Posts
    21
    Still same error
    Any other clue
    -Harsh

  11. #11
    Join Date
    Apr 2012
    Posts
    1,035
    Provided Answers: 18
    most likely the script(s) needs adjusting, specifically to use connect-reset, detach/attach appropiately , possibly also appropriate setting of DB2NODE/DB2INSTANCE depending on your limited description of your environment and script(s).

    You just need to get some good scripters... the issue here is not with db2 but with programming competence.

  12. #12
    Join Date
    Sep 2013
    Location
    India
    Posts
    246
    agree with db2mor. Sequence of steps in script needs to be reviewed.
    ssumit

Posting Permissions

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