Solution manager 7.1 Managed System Config Setup DBACockpit connection issues

[former_member223506]

Hello SAP community,

This particular issue has been giving me some serious grief.

So here is some background info about the situation, This Solution Manager 7.1 system was installed a few months back as a test system but we will be migrating to this system once all the config is set up. I had all of our managed systems configured completely at one point in time, but I swear every other change in one of these managed systems requires half of the config steps to be repeated, it is pretty tiresome. The managed system which is giving me the issues today is named BXP. I had the DBAcockpit connection set up before, so I am not sure how it stopped being connected, but it has. This connection is using the user BXPADM. Anyhow I am getting an error about how the DBA cockpit connection cannot be established. The details to this error message tells me that "The connection 'BXP' is not set up correctly", and that "Database connection BXP: ADBC error 'Internal error 16 has occurred'. I had this message come up before when performing the managed system config for another system in our landscape. I think all I did before to fix it was enable the user and reset the password. Of course this isn't fixing my problem know...

In transaction dbacockpit on my solution manager system when I perform a connection test for database connection BXP of course I get the same message about ADBC error 'Internal error 16 has occurred'. When I try to select BXP system to monitor I am informed about the ADBC error and am told the reason is because a remote connection is not available. Why??? Like I previously stated I had this connection set up before so I don't see why I can't make it happen again.

Anyhow, from my solution manager I ran the report ADBC_TEST_CONNECTION and got this as an output:

B Thu May 23 14:51:26 2013

B  Connect to BXP as bxpadm with AS4_CON_TYPE=SOCKETS;AS4_NQE_OPTIMIZE_METHOD=O;AS4_DB_DBNAME=BXP;AS4_HOST=iseries5.plastekgroup.com

C  Secondary DB connect, user bxpadm

C  Environment: AS4_CON_TYPE=SOCKETS;AS4_NQE_OPTIMIZE_METHOD=O;AS4_DB_DBNAME=BXP;AS4_HOST=iseries5.plastekgroup.com;AS4_DB_LIBRARY=R

C  *** ERROR => CPDA0FF occured: XDNXDAAPI:BuildTCPConnection: Can't Connect to: iseries5.plastekgroup.com:963 (79)

[dbsldb4dbi.c 502]

C  {root-id=519D99B0F298270BE10080010A7F00BC}_{conn-id=00000000000000000000000000000000}_0

C  *** ERROR => === Secondary DB connect FAILED! ===

[dbsldb4.cpp  17438]

C  {root-id=519D99B0F298270BE10080010A7F00BC}_{conn-id=00000000000000000000000000000000}_0

C  *** ERROR => === Connection settings ===

[dbsldb4.cpp  19635]

C  {root-id=519D99B0F298270BE10080010A7F00BC}_{conn-id=00000000000000000000000000000000}_0

C  *** ERROR => connected               = FALSE

[dbsldb4.cpp  19636]

C  {root-id=519D99B0F298270BE10080010A7F00BC}_{conn-id=00000000000000000000000000000000}_0

C  *** ERROR => con_hdl                 = 2

[dbsldb4.cpp  19637]

C  {root-id=519D99B0F298270BE10080010A7F00BC}_{conn-id=00000000000000000000000000000000}_0

C  *** ERROR => db_handle               = 0

[dbsldb4.cpp  19638]

C  {root-id=519D99B0F298270BE10080010A7F00BC}_{conn-id=00000000000000000000000000000000}_0

C  *** ERROR => dbhost                  = iseries5.plastekgroup.com

[dbsldb4.cpp  19639]

C  {root-id=519D99B0F298270BE10080010A7F00BC}_{conn-id=00000000000000000000000000000000}_0

C  *** ERROR => dbhostport              =

[dbsldb4.cpp  19640]

C  {root-id=519D99B0F298270BE10080010A7F00BC}_{conn-id=00000000000000000000000000000000}_0

C  *** ERROR => rdbname                 =

[dbsldb4.cpp  19641]

C  {root-id=519D99B0F298270BE10080010A7F00BC}_{conn-id=00000000000000000000000000000000}_0

C  *** ERROR => dblib                   = R3BXPDATA

[dbsldb4.cpp  19642]

C  {root-id=519D99B0F298270BE10080010A7F00BC}_{conn-id=00000000000000000000000000000000}_0

C  *** ERROR => r3sysle_changed         = FALSE

[dbsldb4.cpp  19645]

C  {root-id=519D99B0F298270BE10080010A7F00BC}_{conn-id=00000000000000000000000000000000}_0

C  *** ERROR => query_compl_reval       = O

[dbsldb4.cpp  19646]

C  {root-id=519D99B0F298270BE10080010A7F00BC}_{conn-id=00000000000000000000000000000000}_0

C  *** ERROR => dbconnecttype           = T

[dbsldb4.cpp  19647]

C  {root-id=519D99B0F298270BE10080010A7F00BC}_{conn-id=00000000000000000000000000000000}_0

C  *** ERROR => user                    = bxpadm

[dbsldb4.cpp  19648]

C  {root-id=519D99B0F298270BE10080010A7F00BC}_{conn-id=00000000000000000000000000000000}_0

C  *** ERROR => qaqqinilib              = Default (QUSRSYS)

[dbsldb4.cpp  19652]

C  {root-id=519D99B0F298270BE10080010A7F00BC}_{conn-id=00000000000000000000000000000000}_0

C  *** ERROR => dbjobname               =

[dbsldb4.cpp  19653]

C  {root-id=519D99B0F298270BE10080010A7F00BC}_{conn-id=00000000000000000000000000000000}_0

C  *** ERROR => dbjobuser               =

[dbsldb4.cpp  19654]

C  {root-id=519D99B0F298270BE10080010A7F00BC}_{conn-id=00000000000000000000000000000000}_0

C  *** ERROR => dbjobno                 =

[dbsldb4.cpp  19655]

C  {root-id=519D99B0F298270BE10080010A7F00BC}_{conn-id=00000000000000000000000000000000}_0

C  *** ERROR => rmtexelib               =

[dbsldb4.cpp  19656]

C  {root-id=519D99B0F298270BE10080010A7F00BC}_{conn-id=00000000000000000000000000000000}_0

C  *** ERROR => parallel_alter_tables   = *OFF

[dbsldb4.cpp  19659]

C  {root-id=519D99B0F298270BE10080010A7F00BC}_{conn-id=00000000000000000000000000000000}_0

C  *** ERROR => ===========================

[dbsldb4.cpp  19678]

C  {root-id=519D99B0F298270BE10080010A7F00BC}_{conn-id=00000000000000000000000000000000}_0

B  ***LOG BYI=> connect failed for connection BXP        [dbds         889]

B  ***LOG BZY=> unexpected return code 8192       calling DBDS       [dbacds       1552]

Y  go to separate LUW generation ===> 20130523145126

Y    GuiStatus status update - dyn text unused: SAPMSSY0 PICK

Y

Y Thu May 23 14:51:27 2013

Y  return from separate LUW <=== WP: 3 th_rc=0 OK.

Help and suggestions will be greatly appreciated.

[Edgardo · Accepted solution]

Hi Kristen,

So far all the steps you have performed to diagnose the problem are right.

Given the information available in the trace it seems to me that the cause of the problem is that the listener for XDN is not running at the port 963 of the target system iseries5.plastekgroup.com.

C  *** ERROR => CPDA0FF occured: XDNXDAAPI:BuildTCPConnection: Can't Connect to: iseries5.plastekgroup.com:963 (79)

[dbsldb4dbi.c 502]

Either the port number is wrong or the listener is not started.

To clarify whether the port number is wrong or not, go to the target system and see what is the value entered in the instance profile parameter dbs/db4/xdn_port .

If the value is not 963, change the DBCON entry on the Solution Manager so the target hosts includes that port number; that is, write the host name as iseries5.plastekgroup.com:<port_number> .

If the parameter dbs/db4/xdn_port is not present, you are use the default port 963. I guess then that the problem is that the listener is not running and you must start it. To see a whole of what are the processes that should run and how to start the listener, I would suggest you to have a look on SAP Note 1257635 - DB4: DBSL Direct Drive for DB2 for IBM i (DB2/400) .

Hope this helps you a bit further with your problem.

Best regards

Edgardo

[former_member223506 · Accepted solution]

Excellent suggestions Edgardo! The parameter dbs/db4/xdn_port was set to be a different port number than 963. I included the correct port number on the host name in the connection set up and my solution manager was able to establish the DBA cockpit connection without issue.

Thanks for all your help!