Skip to Content
avatar image
Former Member

ECC 6.0 installation error - DB2/ AIX

Hello,

I am installing ECC 6.0 using DB2 database Version 8 Fixpak 12 on AIX system in HACMP clustering envt.

I have insatlled DB2 & Central Instance in Node A and DB2 and Dialog Instance in Node B.

But now while starting DB2 in node B by command "startsap db" I am getting below error. Pls help me ASAP........

***********************************

SQL1063N DB2START processing was successful.

Database Manager started

SQL30081N A communication error has been detected. Communication protocol

being used: "TCP/IP". Communication API being used: "SOCKETS". Location

where the error was detected: "192.168.213.41". Communication function

detecting the error: "connect". Protocol specific error code(s): "79",

"*",

"*". SQLSTATE=08001

Activate database failed

**************

Pls help me ASAP..........i am stuck up in installation.

Thanks,

Gautam.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

9 Answers

  • Best Answer
    avatar image
    Former Member
    Feb 12, 2007 at 02:25 PM

    Hi

    please check the following too .

    I suppose you perform IP-Address Takeover .

    (Move Virtual IP-Address 192.168.213.41 of Node A to Node B)

    Did you flush the ARP Cache on Node B ?

    Please check , when this error occurs , to which MAC Address IP Address 192.168.213.41 points in node B's Arp Cache .

     
    ***********************************
    SQL1063N DB2START processing was successful.
    Database Manager started
    SQL30081N A communication error has been detected. Communication protocol
    being used: "TCP/IP". Communication API being used: "SOCKETS". Location
    where the error was detected: "192.168.213.41". Communication function
    detecting the error: "connect". Protocol specific error code(s): "79",
    "*",
    "*". SQLSTATE=08001
    Activate database failed
    
    **************
    

    Furthermore check , that TCP/IP Listening is started properly on Node B via netstat .

    If there is no listening on node B check db2diag.log for Error's regarding starting

    TCPIP processing .

    If there are Error's in db2diag.log regarding TCP/IP processing , please provide .

    Hth + Best regards

    dirk

    Add comment
    10|10000 characters needed characters exceeded

  • Feb 09, 2007 at 12:33 PM

    Hi Gautam,

    you said you installed DB2 on both nodes A & B and additional SAP instances. So I assume you installed the DB2 software on both machines and you installed the DB2 instance and the database on a shared disk.

    I just want to ask you some questions you can check:

    - Did you cataloge the database on your central instance as a remote database?

    - Is the setting for db2comm the same on the second node?

    - Is the entry in /etc/services for SVCENAME on the second node available?

    One additional question according to your setup: do you shutdown the dialog instance to move the central instance as well in case of an failover?

    Regards,

    Steffen

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Steffen Siegmund

      Dear steffen,

      Thanks for your reply. I thougt my installtion and filesystems are wrong. I have no plan to change the installation.

      How will I confirmed the virtual IP successfully moved?

      My current file system ls like that :

      1. /db2 - This is in Local dive of Node A and Node B

      2. /db2/PRD - This is in Shared drive

      3. /db2/PRD/db2dump - This is in Shared drive

      4. /db2/PRD/log_dir - This is in Shared drive

      5. /db2/PRD/sapdata1 - This is in Shared drive

      6. /db2/PRD/saptemp1 - This is in Shared drive

      7. /export/sapPRD - This is in Shared drive

      8. /export/sapmnt - This is in Shared drive

      9. /export/saptrans - This is in Shared drive

      Home directory of the db2prd is created in /db2. So I thought if i will create this mount point in share drive, it will be automatically available in Node B after moving the virtual IP from Node A to Node. That is my reason to change the file system /db2 from Local to share drive.

      Another thing if I will create the mount point /db2/db2prd in share drive, there is no requirement to create the /db2 mount point. What is your idea.

      I have already copied the .dbenv_gipdb.csh and .dbenv_gipdb.sh of /home/prdadm and /db2/db2prd from Node A to Node B and I have changed these files .dbenv_gipapp.csh and .dbenv_gipapp.sh.

      Yes, there is so much resource to run CI + DB + Dialog in Node B.

      What will I do? Can I move to reinstall or not?

      I am getting this out put after executing the netstat command in Node B.

      ***********************************************************************************

      Active Internet connections

      Proto Recv-Q Send-Q Local Address Foreign Address (state)

      tcp4 0 2 gipapp_pers.telnet 192.168.213.21.4talk ESTABLISHED

      tcp4 0 0 loopback.smux loopback.filenet- ESTABLISHED

      tcp4 0 0 loopback.filenet- loopback.smux ESTABLISHED

      tcp4 0 0 loopback.smux loopback.32778 ESTABLISHED

      tcp4 0 0 loopback.32778 loopback.smux ESTABLISHED

      tcp4 0 0 gipapp_pers.32821 gipdb.trap-dae CLOSE_WAIT

      tcp4 0 0 gipapp.32844 gipdb.trap-dae CLOSE_WAIT

      tcp4 0 0 gipapp.filenet- gipapp.32775 ESTABLISHED

      tcp4 0 0 gipapp.32775 gipapp.filenet- ESTABLISHED

      tcp4 0 0 gipapp.filenet- gipapp.32776 ESTABLISHED

      tcp4 0 0 gipapp.32776 gipapp.filenet- ESTABLISHED

      tcp4 0 0 gipapp.filenet- gipapp.32777 ESTABLISHED

      tcp4 0 0 gipapp.32777 gipapp.filenet- ESTABLISHED

      udp4 0 0 192.168.0.255.topsvcs .

      udp4 0 0 gipapp_boot.topsvcs .

      udp4 0 0 192.167.0.255.topsvcs .

      udp4 0 0 gipapp_stby.topsvcs .

      udp4 0 0 loopback.32823 loopback.tick-por

      udp4 0 0 loopback.32831 loopback.cpq-task

      ***********************************************************************************

      Actually my douubts are for reinstallation :

      All the users are created with the Virtual hostname but I kanow it should be with the local server name ( here gipdb_pers and gipapp_pers ). Here when I connect with the user ID prdadm, it is showing <gipdb>prdadm> and <gipapp>prdadm> and other users. I think it should be <gipdb_pers>prdadm> and <gipapp_pers>prdadm. What is your idea about this?

      I have worked in HACMP clustering environment under Oracle 10g and SAP ECC 6.0 (SR1). This was working fine.

      Here Host file entries are like that:

      192.168.213.41 gipdb_svc gipdb (Virtaul IP) - Node A

      192.168.213.42 gipapp_svc gipapp (Virtaul IP) Node B

      192.168.213.43 gipdb_pers (Actual IP ) Node A

      192.168.213.44 gipapp_pers (Actual IP ) Node B

      *****************************************************************************

      Please help me ASAP.

      Thanks

      Gautan

  • avatar image
    Former Member
    Feb 09, 2007 at 01:04 PM

    Hi

    pls check that the DB2 Ports are the same in /etc/services on Node A and Node B

    Check for Port's named
    sapdb2<DBSID>
    
    DB2_db2<dbsid>
    DB2_db2<dbsid>_1   
    DB2_db2<dbsid>_2
    DB2_db2<dbsid>_...
    ...
    DB2_db2<dbsid>_END 
    
    

    and that no other product is using your communication port's on host B .

    Hth + best regards

    dirk

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hello Dirk,

      I have installed the DB2 software locally into both the Nodes Node A and Node B and FixPak 12 also. After that I have installed the Central System ( which is included CI + Database + ASCS) in Node A into the shared mont Points and Virtual name and IP. Actually it is like a single package clustering. When I down the Node A, CI and DB also moved from Node A to Node B. I am trying to start the SAP in Node B. But I am unable to startup the SAP Central System. I have also installed the dialog instance in Node B locally.

      What will I do for this case. Which parameter will be set for this to start the DB2 Database?

      db2set -all in Node B :

      1. su - db2prd

      gipapp:db2prd 1> db2set -all

      [e] DB2CODEPAGE=819

      [e] DB2COMM=TCPIP

      [e] DB2COUNTRY=1

      [e] DB2DBDFT=PRD

      <i> DB2TCPCONNMGRS=1

      <i> DB2CONNECT_IN_APP_PROCESS=NO

      <i> DB2COMM=TCPIP

      [g] DB2SYSTEM=gipapp

      [g] DB2ADMINSERVER=dasusr1

      gipapp:db2prd 2>

      db2 get dbm cfg in Node B

      gipapp:db2prd 2> db2 get dbm cfg

      Database Manager Configuration

      Node type = Client

      Database manager configuration release level = 0x0a00

      Federated Database System Support (FEDERATED) = NO

      Transaction processor monitor name (TP_MON_NAME) =

      Default charge-back account (DFT_ACCOUNT_STR) =

      Java Development Kit installation path (JDK_PATH) = /usr/java14_64

      Diagnostic error capture level (DIAGLEVEL) = 3

      Notify Level (NOTIFYLEVEL) = 3

      Diagnostic data directory path (DIAGPATH) = /db2/db2prd/sqllib/d

      2dump

      SYSADM group name (SYSADM_GROUP) = DBPRDADM

      SYSCTRL group name (SYSCTRL_GROUP) = DBPRDCTL

      SYSMAINT group name (SYSMAINT_GROUP) = DBPRDMNT

      SYSMON group name (SYSMON_GROUP) =

      Client Userid-Password Plugin (CLNT_PW_PLUGIN) =

      Client Kerberos Plugin (CLNT_KRB_PLUGIN) =

      Group Plugin (GROUP_PLUGIN) =

      GSS Plugin for Local Authorization (LOCAL_GSSPLUGIN) =

      Server Plugin Mode (SRV_PLUGIN_MODE) = UNFENCED

      Server List of GSS Plugins (SRVCON_GSSPLUGIN_LIST) =

      Server Userid-Password Plugin (SRVCON_PW_PLUGIN) =

      Server Connection Authentication (SRVCON_AUTH) = NOT_SPECIFIED

      Database manager authentication (AUTHENTICATION) = SERVER_ENCRYPT

      Cataloging allowed without authority (CATALOG_NOAUTH) = NO

      Bypass federated authentication (FED_NOAUTH) = NO

      Java Virtual Machine heap size (4KB) (JAVA_HEAP_SZ) = 2048

      Directory cache support (DIR_CACHE) = YES

      Max requester I/O block size (bytes) (RQRIOBLK) = 32767

      Workload impact by throttled utilities(UTIL_IMPACT_LIM) = 10

      Transaction manager database name (TM_DATABASE) = 1ST_CONN

      Discovery mode (DISCOVER) = SEARCH

      gipapp:db2prd 3>

      ./db2ilist value is db2prd

      I have tried to execute this command also

      ./db2iupdt db2prd but it is not accepting in Node B.

      I have also copied all the port no.( DB2 related ) from the service file of Node A to Node B.

      How will I create the catalog? How will I check the catalog is moved or not from Node A to Node B?

      Please help me ASAP

      Thanks

      Gautam

  • Feb 12, 2007 at 07:51 AM

    Hi Gautam,

    I would first try some tests with DB2 CLP commands.

    You should execute the following commands on both sides before and after the take over.

    db2 list db directory

    db2 list node directory

    db2 connect to DB user <user> using <pwd>

    I guess that your database is cataloged remotely on your dialog instance and locally on your db server before that take over. I am not sure what happens during the take over in your HACMP scripts.

    The HACMP scripts will have to adjust the catalog entries during take over.

    Regards

    Frank

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Dear Frank,

      I have executed all the commands as below: DB2START is now successful but STARTSAP db is still failing. Pls suggest me what should i do now??

      gipapp:prdadm 1> db2 list db directory

      System Database Directory

      Number of entries in the directory = 1

      Database 1 entry:

      Database alias = PRD

      Database name = PRD

      Node name = NODEPRD

      Database release level = a.00

      Comment = Remote database PRD

      Directory entry type = Remote

      Catalog database partition number = -1

      Alternate server hostname =

      Alternate server port number =

      gipapp:prdadm 2> db2 list node directory

      Node Directory

      Number of entries in the directory = 2

      Node 1 entry:

      Node name = GIPAPP

      Comment =

      Directory entry type = LOCAL

      Protocol = TCPIP

      Hostname = gipdb

      Service name = sapdb2PRD

      Node 2 entry:

      Node name = NODEPRD

      Comment = TCPIP Node for database PRD

      Directory entry type = LOCAL

      Protocol = TCPIP

      Hostname = gipdb

      Service name = sapdb2PRD

      gipapp:prdadm 3> db2 connect to PRD user prdadm using admin123

      SQL30081N A communication error has been detected. Communication protoco

      being used: "TCP/IP". Communication API being used: "SOCKETS". Location

      where the error was detected: "192.168.213.41". Communication function

      detecting the error: "recv". Protocol specific error code(s): "", "", "

      SQLSTATE=08001

      gipapp:prdadm 4> db2start

      02/12/2007 02:53:59 0 0 SQL1026N The database manager is already activ

      .

      SQL1026N The database manager is already active.

      gipapp:prdadm 5> startsap db

      Checking db6 db Database

      -


      ABAP Database is not available via R3trans

      Starting SAP-Collector Daemon

      -


      ***********************************************************************

      • This is Saposcol Version COLL 20.89 700 - AIX v6.55 5L-64 bit 060323

      • Usage: saposcol -l: Start OS Collector

      • saposcol -k: Stop OS Collector

      • saposcol -d: OS Collector Dialog Mode

      • saposcol -s: OS Collector Status

      • The OS Collector (PID 594080) is already running .....

      ************************************************************************

      saposcol already running

      Running /usr/sap/PRD/SYS/exe/run/startdb

      02/12/2007 02:54:17 0 0 SQL1026N The database manager is already activ

      .

      SQL1026N The database manager is already active.

      Activate database failed

      R3trans connect failed

      DB startup failed

      gipapp:prdadm 6>

      Regards & Thanks,

      Gautam.

  • Feb 12, 2007 at 09:18 AM

    Hi Gautam,

    it is not supprising that R3trans and startdb fail if you can not connect to the database.

    As you can see from the db and node directory, your database is cataloged remotely pointing to a database on gipdb. You did not state on which node you have executed the commands. I guess you did it on the dialog instance. Please do the same on the db server gipdb.

    The DB2 instance on gipdb has to contain a local database with name PRD.

    After takeover of the db server to the other node the catalog entry of the local database has to be taken over to the new DB server.

    As far as I know HACMP is script based and your HACMP scripts have to perform the catalog changes.

    Regards

    Frank

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Dear Frank,

      Thanks for your reply. But please reply below this.

      Now what will I do? Can I reconfigured the HACMP Clustering software? I have also doubt about the clustering software HACMP. I have told also to IBM but they were not agreed.

      All the users are created with the Virtual hostname but I know it should be with the local server name ( here gipdb_pers and gipapp_pers ). Here when I connect with the user ID prdadm, it is showing gipdb:prdadm> and gipapp:prdadm> and other users. I think it should be gipdb_pers:prdadm> and gipapp_pers:prdadm>. What is your idea about this?

      I have worked in HACMP clustering environment under Oracle 10g and SAP ECC 6.0 (SR1). This is working fine.

      Here Host file entries are like that:

      192.168.213.41 gipdb_svc gipdb (Virtaul IP) - Node A

      192.168.213.42 gipapp_svc gipapp (Virtaul IP) Node B

      192.168.213.43 gipdb_pers (Actual IP ) Node A

      192.168.213.44 gipapp_pers (Actual IP ) Node B

      What will I do now? I have to complete the Installation ASAP and I have

      to take a decision regarding this. Please help me ASAP about this.

      Another thing is that, when Database and SAP Central system in Node A, SAP is working fine and Dialog instance is working in Node B. So, DB2 client is working to connect the DB2 Database which is in Node A. I think DB2 Client in Node B is working fine.

      My SAP Installation is ok or not?

      Please guide me what will I do? Will I reconfigure HACMP Clustering software or not?

      Thanks

      Gautam Poddar

      PricewaterhouseCoopers India

  • avatar image
    Former Member
    Feb 13, 2007 at 10:21 AM

    Hi

    First lets leave that ARP issues behind .

    the Error you get

    >>>snip<<<
    2007-02-12-02.54.25.178082-360 E41801428A421 LEVEL: Error
    PID : 741486 TID : 1 PROC : db2tcpcm 0
    INSTANCE: db2prd NODE : 000
    FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125
    MESSAGE : ADM7009E An error was encountered in the "TCPIP" protocol support.
    A possible cause is that the maximum number of agents has been
    exceeded.
    
    2007-02-12-02.54.25.178309-360 I41801850A386 LEVEL: Error
    PID : 741486 TID : 1 PROC : db2tcpcm 0
    INSTANCE: db2prd NODE : 000
    FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126
    MESSAGE : Return code from sqleGetAgent =
    DATA #1 : Hexdump, 4 bytes
    0x0FFFFFFFFFFF6614 : FFFF FB36 ...6
    >>>unsnip<<<
    

    You get only on Node B .

    I suppose you have an different Database+Node Directory on Node A and Node B

    [Due to different Installation Types on Node A [CI+DB] and Node B[DI]]

    Please give us an

    list database directory 
    list node directory
    

    from <b>Node A</b>

    This Error is caused by an incorrect Database cataloging on Node B and the connect to database PRD works only , if Hostname gipdb is not local due to remote cataloging .

    So first let us know , how your DB is cataloged on node A

    [list db+node directory ] to provide further assistance .

    Hth+Best regards

    dirk

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hello,

      List Database Directory of Node A :

      gipdb:db2prd 2> db2 list database directory

      System Database Directory

      Number of entries in the directory = 1

      Database 1 entry:

      Database alias = PRD

      Database name = PRD

      Local database directory = /db2/PRD

      Database release level = a.00

      Comment = SAP database PRD

      Directory entry type = Indirect

      Catalog database partition number = 0

      Alternate server hostname =

      Alternate server port number =

      list db node directory of Node A :

      gipdb:db2prd 7> db2 list node directory

      SQL1027N The node directory cannot be found.

      I am also giving these of Node B

      gipapp:prdadm 4> db2 list node directory

      Node Directory

      Number of entries in the directory = 2

      Node 1 entry:

      Node name = GIPAPP

      Comment =

      Directory entry type = LOCAL

      Protocol = TCPIP

      Hostname = gipdb

      Service name = sapdb2PRD

      Node 2 entry:

      Node name = NODEPRD

      Comment = TCPIP Node for database PRD

      Directory entry type = LOCAL

      Protocol = TCPIP

      Hostname = gipdb

      Service name = sapdb2PRD

      gipapp:prdadm 5> db2 list db directory

      System Database Directory

      This catalog has been created by SAP in Node B

      Please help me ASAP

      Thanks

      Gautam

      Number of entries in the directory = 1

      Database 1 entry:

      Database alias = PRD

      Database name = PRD

      Node name = NODEPRD

      Database release level = a.00

      Comment = Remote database PRD

      Directory entry type = Remote

      Catalog database partition number = -1

      Alternate server hostname =

      Alternate server port number =

      gipapp:prdadm 6>

  • avatar image
    Former Member
    Feb 13, 2007 at 02:16 PM

    Hi

    As you see , you have an asynchronous setup of DB+Node directory on Node A and Node B .

    First you need to recatalog your database for high availability and cross-takeover of DI and CI+DB <b>on Node B</b>.

    db2 'uncatalog database PRD'
    db2 'catalog Database PRD  as PRDL on /db2/PRD'
    db2 'catalog database PRDL as PRD  at node NODEPRD'
    

    Then you could try an takeover of CI+DB to Node B .

    With this setup then just the takeover of DI to Node a will not work , but this we will discuss in a next step .

    Hth + Best regards

    dirk

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Dear Dirk,

      I got stuck up again...

      Dialog Instance is not started in node B while DB + CI is running in node A. After executing the below commands.

      SAP is working fine only when all CI + DB + DI are in Node B. But earlier it was fine with DB + CI in Node A and DI in B, then why is it failing now. Pls help.

      TRANS.LOG details are as below:

      ******************

      gipapp:prdadm 1> more trans.log

      4 ETW000 R3trans version 6.13 (release 700 - 20.02.06 - 16:15:00).

      4 ETW000 unicode enabled version

      4 ETW000 ===============================================

      4 ETW000

      4 ETW000 date&time : 14.02.2007 - 01:12:35

      4 ETW000 control file: <no ctrlfile>

      4 ETW000 R3trans was called as follows: R3trans -d

      4 ETW000 trace at level 2 opened for a given file pointer

      4 ETW000 [dev trc ,00000] Wed Feb 14 01:12:35 2007

      64 0.000064

      4 ETW000 [dev trc ,00000] db_con_init called

      19 0.000083

      4 ETW000 [dev trc ,00000] create_con (con_name=R/3)

      41 0.000124

      4 ETW000 [dev trc ,00000] Loading DB library '/usr/sap/PRD/SYS/exe/run/dbd

      b6slib.o' ...

      4 ETW000

      39 0.000163

      4 ETW000 [dev trc ,00000] load shared library (/usr/sap/PRD/SYS/exe/run/db

      db6slib.o), hdl 0

      4 ETW000

      771 0.000934

      4 ETW000 [dev trc ,00000] Library '/usr/sap/PRD/SYS/exe/run/dbdb6slib.o' l

      oaded

      4 ETW000

      29 0.000963

      4 ETW000 [dev trc ,00000] function DbSlExpFuns loaded from library /usr/sa

      p/PRD/SYS/exe/run/dbdb6slib.o

      4 ETW000

      31 0.000994

      4 ETW000 [dev trc ,00000] Version of '/usr/sap/PRD/SYS/exe/run/dbdb6slib.o

      ' is "700.08", patchlevel (0.52)

      4 ETW000

      146 0.001140

      4 ETW000 [dev trc ,00000] function dsql_db_init loaded from library /usr/s

      ap/PRD/SYS/exe/run/dbdb6slib.o

      4 ETW000

      31 0.001171

      4 ETW000 [dev trc ,00000] function dbdd_exp_funs loaded from library /usr/

      sap/PRD/SYS/exe/run/dbdb6slib.o

      4 ETW000

      31 0.001202

      4 ETW000 [dev trc ,00000] New connection 0 created

      23 0.001225

      4 ETW000 [dev trc ,00000] 0: name = R/3, con_id = -000000001 state = DISCO

      NNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, oc

      c = NO

      36 0.001261

      4 ETW000 [dev trc ,00000] db_con_connect (con_name=R/3)

      37 0.001298

      4 ETW000 [dev trc ,00000] find_con_by_name found the following connection

      for reuse:

      4 ETW000

      29 0.001327

      4 ETW000 [dev trc ,00000] 0: name = R/3, con_id = 000000000 state = DISCON

      NECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ

      = NO

      4 ETW000

      33 0.001360

      4 ETW000 [dev trc ,00000] DB6 (DB2 UDB) UNICODE database interface 700.08

      [opt]

      4 ETW000

      582 0.001942

      4 ETW000 [dev trc ,00000] DB6 shared library (dbdb6slib) patchlevels

      19 0.001961

      4 ETW000 [dev trc ,00000] (0.8) DB6: V8.2.2 optguidelines in OPEN SQL (n

      ote 150037)

      4 ETW000

      29 0.001990

      4 ETW000 [dev trc ,00000] (0.8) Support of SDBUPDEXCL (note 847616)

      20 0.002010

      4 ETW000 [dev trc ,00000] (0.9) DB6: use export file for dbdb6slib (note

      835135)

      4 ETW000

      29 0.002039

      4 ETW000 [dev trc ,00000] (0.9) DB6: Core in getAndBindSQLDA (note 83318

      3)

      4 ETW000

      28 0.002067

      4 ETW000 [dev trc ,00000] (0.10) DB6: link dbdb6slib.dll on windows with

      libdb6.obj (note 761159)

      4 ETW000

      30 0.002097

      4 ETW000 [dev trc ,00000] (0.10) DB6: DUPLICATE_KEY on MERGE -> repeat (

      note 851474)

      4 ETW000

      37 0.002134

      4 ETW000 [dev trc ,00000] (0.15) DB6: wrong CAST for short string ABAP t

      ype (note 861905)

      4 ETW000

      1021 0.003155

      4 ETW000 [dev trc ,00000] (0.17) DB6: special characters in sidadm passw

      d (note 865839)

      4 ETW000

      29 0.003184

      4 ETW000 [dev trc ,00000] (0.21) DB6: no SAP_INFO comments (note 873889)

      4 ETW000

      29 0.003213

      4 ETW000 [dev trc ,00000] (0.22) DB6: hints: get correlation names from

      view texts (note 868888)

      4 ETW000

      29 0.003242

      4 ETW000 [dev trc ,00000] (0.23) DB6: hints: get correlation names from

      view texts (note 868888)

      4 ETW000

      29 0.003271

      4 ETW000 [dev trc ,00000] (0.26) DB6: DB6_DBSL_CLP_COMMAND STRING_BAD_RE

      F (note 883402)

      4 ETW000

      29 0.003300

      4 ETW000 [dev trc ,00000] (0.27) DB6: activate value compression (note 8

      86231)

      4 ETW000

      29 0.003329

      4 ETW000 [dev trc ,00000] (0.28) DB6: optimization guidelines on views p

      art 2 (note 868888)

      4 ETW000

      29 0.003358

      92111)

      4 ETW000

      29 0.003387

      4 ETW000 [dev trc ,00000] (0.33) DB6: append SAP_TA comment (note 873889

      )

      4 ETW000

      29 0.003416

      4 ETW000 [dev trc ,00000] (0.34) DB6: activate value compression with qu

      oted names (note 886231)

      4 ETW000

      29 0.003445

      4 ETW000 [dev trc ,00000] (0.36) DB6: Repeat isolated DDL statements aft

      er SQL0911 (note 901338)

      4 ETW000

      29 0.003474

      4 ETW000 [dev trc ,00000] (0.41) DB6: add V9 to list of supported DB2 re

      leases (note 912386)

      4 ETW000

      29 0.003503

      4 ETW000 [dev trc ,00000] (0.50) DB6: reread passwords for secondary con

      nections (note 931742)

      4 ETW000

      30 0.003533

      delines (note 868888)

      4 ETW000

      29 0.003562

      4 ETW000 [dev trc ,00000] Supported features:

      18 0.003580

      4 ETW000 [dev trc ,00000] - CLI LOAD for INSERT ... FULLSELECT

      18 0.003598

      4 ETW000 [dev trc ,00000] ..retrieving configuration parameters

      19 0.003617

      4 ETW000 [dev trc ,00000] ..done

      95 0.003712

      4 ETW000 [dev trc ,00000] Running with UTF-8 Unicode

      19 0.003731

      4 ETW000 [dev trc ,00000] DB2 library /db2/db2prd/sqllib/lib64/libdb2.a(sh

      r_64.o) successfully loaded

      4 ETW000

      12566 0.016297

      4 ETW000 [dev trc ,00000] *** ERROR in DB6Connect[dbdb6.c, 1379] (BEGIN)

      78186 0.094483

      4 ETW000 [dev trc ,00000] &+ DbSlConnectDB6( SQLConnect ): [IBM][CLI D

      river] SQL30061N The database alias or database name "PRDL

      4 ETW000

      48 0.094531

      TATE=08004

      4 ETW000

      32 0.094563

      4 ETW000 [dev trc ,00000] &+

      4 ETW000

      31 0.094594

      4 ETW000 [dev trc ,00000] &+

      4 ETW000

      32 0.094626

      4 ETW000 [dev trc ,00000] &+

      4 ETW000

      31 0.094657

      4 ETW000 [dev trc ,00000] *** ERROR in DB6Connect[dbdb6.c, 1379] (END)

      20 0.094677

      4 ETW000 [dbdb6.c ,00000] *** ERROR => DbSlConnect to 'PRD' as 'sapprd' fa

      iled

      4 ETW000

      50 0.094727

      2EETW169 no connect possible: "DBMS = DB6 --- DB2DB

      DFT = 'PRD'"

      ******************

      Regards,

      Gautam.

  • avatar image
    Former Member
    Feb 14, 2007 at 07:47 AM

    Hi

    The error you get is correct , because DB2 does not find PRDL on node A .

    Now lets finalize the configuration and configure node A to be in sync with node B .

    Issue the following Commands on <b>Node A</b>

    db2 'uncatalog database PRD'
    db2 'catalog tcpip node NODEPRD remote gipdb SERVER sapdb2PRD'
    db2 'catalog Database PRD  as PRDL on /db2/PRD'
    db2 'catalog database PRDL as PRD  at node NODEPRD'
    

    Hth + best regards

    dirk

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 01, 2009 at 12:21 PM

    Hi all

    I have installed ASCS, SCS, Database Instance and CI at node A (sappbi-lpar), with virtual name for SAP resource sappbi and db2pbi as database resource virtual name. I have created pbiadm and db2pbi users at node B (sappbiha-lpar). In node A, all works correctly. So I have moved all filesystem and resources to node B. In node B I have this error communication message

    db2 => list node directory

    Node Directory

    Number of entries in the directory = 1

    Node 1 entry:

    Node name = PBI

    Comment =

    Directory entry type = LOCAL

    Protocol = TCPIP

    Hostname = db2pbi

    Service name = sapdb2PBI

    db2 => list database directory

    System Database Directory

    Number of entries in the directory = 1

    Database 1 entry:

    Database alias = PBI

    Database name = PBI

    Node name = PBI

    Database release level = c.00

    Comment =

    Directory entry type = Remote

    Catalog database partition number = -1

    Alternate server hostname =

    Alternate server port number =

    db2 => connect

    SQL30081N A communication error has been detected. Communication protocol

    being used: "TCP/IP". Communication API being used: "SOCKETS". Location

    where the error was detected: "10.xx.xx.xxx". Communication function

    detecting the error: "connect". Protocol specific error code(s): "79", "*",

    "*". SQLSTATE=08001

    I hope your help

    Thanks in advanced

    Add comment
    10|10000 characters needed characters exceeded