I recently saw a set of programming standards that stated it was better not to use an ORDER BY clause on a SELECT statement. Instead SELECT into an internal table and use SORT. The actual statement was....."In most cases it is preferable to do the sorting within the ABAP program instead of on the database server.  That means: fill the internal table via a SELECT statement and then sort via the SORT statement instead of coding a SELECT u2026 ORDER BY.  The sorting of large amounts of data on the database server affects the performance of all users on the system, whereas the sorting within the ABAP program u2018onlyu2019 affects the application server.  However, if an index exists on the table that can be used for the sorting then the SELECT u2026 ORDER BY doesnu2019t cause any undue strains on the system."

I think this is no longer correct particularily with regards to Systemi/iSeries which we normally run in 2 tier mode.

What are people opinion on this?

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.

Hi Sap Experts,

My clients SAP is going to be live before that I want to do pre golive check from sap.

How to do pre golive check , Please suggest the procedure

Thanks & Regards

Vinay Patel

Hello Experts,

We have a requirement to connect the remote DB DB2 (No SAP) which is on I series from our SAP ECC EHP 5 system so I made a below entry in table DBCON -

Database connection - PRMS_TEST

DBS                            - DB4

Username                   - SAP

*Password                    ***********

Connection Information - AS4_HOST=S1031993;AS4_DB_LIBRARY=RMTLIB

but while doing the test connection, it gives the below error-

B  Loading DB library '/usr/sap/ECD/DVEBMGS00/exe/dbdb4slib.so' ...
M  *** ERROR => DlLoadLib()==DLENOACCESS - dlopen("/usr/sap/ECD/DVEBMGS00/exe/dbdb4slib.so") FAILED  "/usr/sap/ECD/DVEBMGS00/exe/dbdb4slib.so: cannot open shared object file: No such file or directory"  [dlux.c       445]
M  {root-id=000C298267DF1EE0BBC9171365715368}_{conn-id=00000000000000000000000000000000}_0
B  *** ERROR => Couldn't load library '/usr/sap/ECD/DVEBMGS00/exe/dbdb4slib.so'
 [dbcon.c      5263]
B  {root-id=000C298267DF1EE0BBC9171365715368}_{conn-id=00000000000000000000000000000000}_0
B  ***LOG BYG=> could not load library for database connection PRMS_TEST  [dbds         886]
B  ***LOG BZY=> unexpected return code 8192       calling DBDS       [dbacds       1536]

My SAP environment is -

SAP - ECC EHP 5

Kernel Release 720 patch 90

OS     - Red Hat Linux 5.5 - 64 bit

Database - DB2 (DB6)

Kindlly let us know if I have to put the file dbdb4slib.so in kernel directory and from where I can get this file and if my DBCON entry is correct ?

Regards

Saurabh Mishra

there is a known problem with LineBreak-Parsing (since 07.2014) in WebDynpro-ABAP (not JAVA)

1962566 - Wrong parsing of LineBreak tag (<br>) in FormattedTextEdit

http://service.sap.com/sap/support/notes/1962566

and a note with corresponding kernel-versions:

1980933 - New unified rendering version

http://service.sap.com/sap/support/notes/1980933

but Kernel-7.42 is not mentioned yet in that sap-note http://service.sap.com/sap/support/notes/1980933

we have installed now Kernel-742-PL-118, and this is still not solved.

when do we get a solution to this issue ???

I was looking at usr/sap/trans/log and see a lot of old logs.

I ran tp check all and it created a report

The report showed more than 8,000 log files that can be deleted in the usr/sap/trans/log

Can I delete these old log files or is this going to create more problems for me.

THanks

Joe

I recently saw a set of programming standards that stated it was better not to use an ORDER BY clause on a SELECT statement. Instead SELECT into an internal table and use SORT. The actual statement was....."In most cases it is preferable to do the sorting within the ABAP program instead of on the database server.  That means: fill the internal table via a SELECT statement and then sort via the SORT statement instead of coding a SELECT u2026 ORDER BY.  The sorting of large amounts of data on the database server affects the performance of all users on the system, whereas the sorting within the ABAP program u2018onlyu2019 affects the application server.  However, if an index exists on the table that can be used for the sorting then the SELECT u2026 ORDER BY doesnu2019t cause any undue strains on the system."

I think this is no longer correct particularily with regards to Systemi/iSeries which we normally run in 2 tier mode.

What are people opinion on this?

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.

I recently saw a set of programming standards that stated it was better not to use an ORDER BY clause on a SELECT statement. Instead SELECT into an internal table and use SORT. The actual statement was....."In most cases it is preferable to do the sorting within the ABAP program instead of on the database server.  That means: fill the internal table via a SELECT statement and then sort via the SORT statement instead of coding a SELECT u2026 ORDER BY.  The sorting of large amounts of data on the database server affects the performance of all users on the system, whereas the sorting within the ABAP program u2018onlyu2019 affects the application server.  However, if an index exists on the table that can be used for the sorting then the SELECT u2026 ORDER BY doesnu2019t cause any undue strains on the system."

I think this is no longer correct particularily with regards to Systemi/iSeries which we normally run in 2 tier mode.

What are people opinion on this?

Hi Experts,

Could you please help me if there are any particular things I need to backup/pre-requisites in AS/400 system. Also could you please help me with any useful stuff that could help in the system refresh process.

I am doing the system refresh with out using SWPM.

Please share the information ASAP.

Regards,

Amarnath

Hello Experts,

We have a requirement to connect the remote DB DB2 (No SAP) which is on I series from our SAP ECC EHP 5 system so I made a below entry in table DBCON -

Database connection - PRMS_TEST

DBS                            - DB4

Username                   - SAP

*Password                    ***********

Connection Information - AS4_HOST=S1031993;AS4_DB_LIBRARY=RMTLIB

but while doing the test connection, it gives the below error-

B  Loading DB library '/usr/sap/ECD/DVEBMGS00/exe/dbdb4slib.so' ...
M  *** ERROR => DlLoadLib()==DLENOACCESS - dlopen("/usr/sap/ECD/DVEBMGS00/exe/dbdb4slib.so") FAILED  "/usr/sap/ECD/DVEBMGS00/exe/dbdb4slib.so: cannot open shared object file: No such file or directory"  [dlux.c       445]
M  {root-id=000C298267DF1EE0BBC9171365715368}_{conn-id=00000000000000000000000000000000}_0
B  *** ERROR => Couldn't load library '/usr/sap/ECD/DVEBMGS00/exe/dbdb4slib.so'
 [dbcon.c      5263]
B  {root-id=000C298267DF1EE0BBC9171365715368}_{conn-id=00000000000000000000000000000000}_0
B  ***LOG BYG=> could not load library for database connection PRMS_TEST  [dbds         886]
B  ***LOG BZY=> unexpected return code 8192       calling DBDS       [dbacds       1536]

My SAP environment is -

SAP - ECC EHP 5

Kernel Release 720 patch 90

OS     - Red Hat Linux 5.5 - 64 bit

Database - DB2 (DB6)

Kindlly let us know if I have to put the file dbdb4slib.so in kernel directory and from where I can get this file and if my DBCON entry is correct ?

Regards

Saurabh Mishra

There is a new Kernel option for those of us running 7.x kernels. Once again SAP have changed the IBM i SAP kernel structure.

I am interested if people have opinions about the best usage of this new option.

Below is the start of note #1632754

With SAP NetWeaver 2004s and associated products and with the application

basis 7.0x together with the 7.20 kernel, SAP introduces a new directory

structure with IBM i; you can use this to maintain a kernel while the

instances of the system are active. This minimizes the amount of time for

which the system is unavailable.

With the new directory structure, the SAP kernel is installed in a central

directory (indicated by the profile parameter DIR_CT_RUN). From there, the

kernel is copied during the system start to the instance-specific kernel

directories (indicated by the profile parameter DIR_EXECUTABLE). The kernel

is replicated using the program sapcpe. Each SAP instance then uses the

kernel from its own instance-specific directory.

So it looks like we can set DIR_CT_RUN to update the kernel from a central location.

Anyone got any plans or thoughts on this option?

Thanks

Matthew

Hi Experts,

I am in a very tough situation. We have restored the production data to test system (Cleared library R3TTTDATA in test system and restored R3PPPDATA )

Created journals and catlogs as well.

I have noticed my test system is with 741 kernel where as my production is at 721 kernel now I am not able bring the system up.

I assume the only solution is to downgrade the kernel in my test system. Could you please help me in this tough situation. What all steps I need to take to downgrade the kernel version.

Please guide me with detailed steps.

Thanks,

Amarnath

I'm trying to find out what's the maximum value that you can put in for rdisp/max_wprun_time

Thanks

Joe

Hi Guys,  since the kernel upgrade the system has been having a huge number of dumps & the performance has gone down drastically.  did some checking on SM50 & DB01, i can see so many locks on the NRIV table.

Has anyone come across this issue before ?

Thanks in advance

Chris

Termination occurred in the ABAP program "SAPLSNR3" - in "READ_NRIV".

The main program was "RBDAPP01 ".

In the source code you have the termination point in line 245

of the (Include) program "LSNR3F01".

The program "SAPLSNR3" was started as a background job.

Job Name....... "Z_AUTOBILL"

Job Initiator.. "BATCHADM"

Job Number..... 15174905

The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in

procedure "READ_NRIV" "(FORM)", but it was neither handled locally nor declared

in the RAISING clause of its signature.

The procedure is in program "SAPLSNR3 "; its source code begins in line

240 of the (Include program "LSNR3F01 ".

>>>>>     SELECT SINGLE FOR UPDATE * FROM NRIV WHERE

  246                                      OBJECT    = P_OBJECT

  247                                  AND SUBOBJECT = P_SUBOBJECT

  248                                 AND NRRANGENR = P_NR_RANGE_NR

  249                                  AND TOYEAR    = '0000'.

Hello Experts,

We have a requirement to connect the remote DB DB2 (No SAP) which is on I series from our SAP ECC EHP 5 system so I made a below entry in table DBCON -

Database connection - PRMS_TEST

DBS                            - DB4

Username                   - SAP

*Password                    ***********

Connection Information - AS4_HOST=S1031993;AS4_DB_LIBRARY=RMTLIB

but while doing the test connection, it gives the below error-

B  Loading DB library '/usr/sap/ECD/DVEBMGS00/exe/dbdb4slib.so' ...
M  *** ERROR => DlLoadLib()==DLENOACCESS - dlopen("/usr/sap/ECD/DVEBMGS00/exe/dbdb4slib.so") FAILED  "/usr/sap/ECD/DVEBMGS00/exe/dbdb4slib.so: cannot open shared object file: No such file or directory"  [dlux.c       445]
M  {root-id=000C298267DF1EE0BBC9171365715368}_{conn-id=00000000000000000000000000000000}_0
B  *** ERROR => Couldn't load library '/usr/sap/ECD/DVEBMGS00/exe/dbdb4slib.so'
 [dbcon.c      5263]
B  {root-id=000C298267DF1EE0BBC9171365715368}_{conn-id=00000000000000000000000000000000}_0
B  ***LOG BYG=> could not load library for database connection PRMS_TEST  [dbds         886]
B  ***LOG BZY=> unexpected return code 8192       calling DBDS       [dbacds       1536]

My SAP environment is -

SAP - ECC EHP 5

Kernel Release 720 patch 90

OS     - Red Hat Linux 5.5 - 64 bit

Database - DB2 (DB6)

Kindlly let us know if I have to put the file dbdb4slib.so in kernel directory and from where I can get this file and if my DBCON entry is correct ?

Regards

Saurabh Mishra

Hi

We implemented SAP Single Sign on last year using Kerberos and it was working beautifully until last Friday.

Since Last friday, we are getting a weird error on our development system( We are lucky that it has not started happening on our Production systems)...

Sapgui 710 [Build 9003] Tue Aug 24 16:27:16 2010

: 'SAP System Message:

Security Network Layer (SNC) error

Our configuration is:

snc/enable                                  1                                           

snc/gssapi_lib                              /lib/libgssapi_krb5.a(libgssapi_krb5.a.so)  

snc/identity/as                             p:SAPservice/sapdev.<domain_name>@<i5_REALM>

snc/accept_insecure_gui                     1                                           

snc/accept_insecure_rfc                     1                                           

snc/accept_insecure_r3int_rfc               1                                           

snc/permit_insecure_start                   1

Now the funny part is that we know what the fix is..We have to advance our PC clocks on the PC to maybe a couple of minutes ahead and then it lets us log into the system.

The Work process trace file shows us the following :

N Sun Aug 22 10:45:10 2010                                                                            

N  *** ERROR => SncPEstablishContext()==SNCERR_GSSAPI  [sncxxall.c 3357]                              

N        GSS-API(maj): Miscellaneous failure                                                          

N        GSS-API(min): Clock skew too great          <<<<<<========================                                                 

N      Unable to establish the security context                                                       

N  <<- SncProcessInput()==SNCERR_GSSAPI                                                               

M  *** ERROR => ThSncIn: SncProcessInput (SNCERR_GSSAPI) [thxxsnc.c    976]                           

M  *** ERROR => ThSncIn: SncProcessInput [thxxsnc.c    981]                                           

M  in_ThErrHandle: 1                                                                               

M  *** ERROR => ThSncIn: SncProcessInput (step 4, th_errno 44, action 1, level 1) [thxxhead.c   10631]

Looking at it, someone will wonder that its the clcok skew and that its off.

But we have looked at the iSeries clock, the domain controller clock and the PC clcok, which are all within minutes of each other. The iseries is synced to the domain using CHGNTPA every 60 minutes using (*MAXADJ).

Also Our domain controller setting for Kerberos Policy for Maximum tolerance for computer clock synchronization is set to 5 minutes.

Now it even get's more interesting. We have three SAP systems on the same lpar configured for SAP SNC SSO.

one of them works and two of them gies us this error. When we advance our PC times by  only a couple of minutes, then these two also start working.

So that make us believe, it must be something within the SAP application, as all three share the same OS configuration.(time, REALMS, krb5 settings etc). The one that works is a BI system and is at SPS 15, but the two that give us trouble are at SPS11.

Any advise on where i should look further inside SAP??? System i??

I am all stumped...

Thanks in advance for all your help.

Abhi

Edited by: ABHI GUPT on Aug 27, 2010 11:23 AM

I'm trying to find out what's the maximum value that you can put in for rdisp/max_wprun_time

Thanks

Joe

Dear all,

As per sap note 1178684, we can check the validity period of the saprouter by executing "sapgenpse get_my_name -n validity"

I am wondering how to run that command in as/400 ?

Please advise. I am not familiar with as/400 OS.

Thanks

Regards,

Kent

Hi Sap Experts,

My clients SAP is going to be live before that I want to do pre golive check from sap.

How to do pre golive check , Please suggest the procedure

Thanks & Regards

Vinay Patel