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 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'.

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

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'.

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

Thanks

Joe

Hello,

We are implementing SAP ECC 6.0 on iSeries, i5/OS V5R4.

The application server & the database server are implemented on one centralized physical iSeries server.

We recently attempted to copy one SAP system (DEV) from one iSeries server to another, through restoring from an Entire System backup.

After successfully conducting the restore onto the new (destination) iSeries server, and conducting all the necessary host name changes to be the same as the host name of the source system, we encountered a problem when trying to start the SAP : all the jobs under sub-system R3_00 are started, except the jobs constituting the SAP work processes; i.e. WP00, WP01, …etc.

The following is the file holding the SAP start log :

/usr/sap/<SID>/DVEBMGS00/work/sapstart.log

SAP-R/3-Startup Program Rel 700 V1.8 (2003/04/24)                  

-

Starting at 2008/04/07 13:55:49                                    

Startup Profile: "/usr/sap/PRO/SYS/profile/START_DVEBMGS00_MASAPPRO"

Execute Pre-Startup Commands                                       

-

(47) Local: /usr/sap/PRO/SYS/exe/run/cleanipc 00 remove            

(47) Executing "/usr/sap/PRO/SYS/exe/run/cleanipc 00 remove"...    

(47) Okay!                                                         

(47) Local: CLRLIB LIB(R3WRK00)                                    

(47) Executing CL command "CLRLIB LIB(R3WRK00)"...                 

(47) Okay!                                                                     

(47) Local: /usr/sap/PRO/SYS/exe/run/sapmscsa pf=/usr/sap/PRO/SYS/profile/PRO_DVEBMGS00_MASAPPRO -n

(47) Executing "/usr/sap/PRO/SYS/exe/run/sapmscsa pf=/usr/sap/PRO/SYS/profile/PRO_DVEBMGS00_MASAPPRO -n"...

(47) Okay!                                                                               

Starting Programs                                                              

-

(47) Spawning program "/usr/sap/PRO/SYS/exe/run/saposcol" asynchronously...    

(47) Okay, child's pid=52.                                                     

(52) Starting: local /usr/sap/PRO/SYS/exe/run/saposcol                         

(47) Spawning program "/usr/sap/PRO/SYS/exe/run/msg_server pf=/usr/sap/PRO/SYS/profile/PRO_DVEBMGS00_MASAPPRO" asynchronously...

(47) Okay, child's pid=53.                                                     

(53) Starting: local /usr/sap/PRO/SYS/exe/run/msg_server pf=/usr/sap/PRO/SYS/profile/PRO_DVEBMGS00_MASAPPRO

(47) Spawning program "/usr/sap/PRO/SYS/exe/run/disp+work pf=/usr/sap/PRO/SYS/profile/PRO_DVEBMGS00_MASAPPRO" asynchronously...

(47) Okay, child's pid=54.                                                     

(54) Starting: local /usr/sap/PRO/SYS/exe/run/disp+work pf=/usr/sap/PRO/SYS/profile/PRO_DVEBMGS00_MASAPPRO

(47) Spawning program "/usr/sap/PRO/SYS/exe/run/rslgcoll pf=/usr/sap/PRO/SYS/profile/PRO_DVEBMGS00_MASAPPRO -F" asynchronously...

(47) Okay, child's pid=55.                                                     

(55) Starting: local /usr/sap/PRO/SYS/exe/run/rslgcoll pf=/usr/sap/PRO/SYS/profile/PRO_DVEBMGS00_MASAPPRO -F

(47) Spawning program "/usr/sap/PRO/SYS/exe/run/rslgsend pf=/usr/sap/PRO/SYS/profile/PRO_DVEBMGS00_MASAPPRO -F" asynchronously...

(47) Okay, child's pid=56.                                                     

(56) Starting: local /usr/sap/PRO/SYS/exe/run/rslgsend pf=/usr/sap/PRO/SYS/profile/PRO_DVEBMGS00_MASAPPRO -F

(47) Spawning program "/usr/sap/PRO/SYS/exe/run/igswd_mt -mode=profile pf=/usr/sap/PRO/SYS/profile/PRO_DVEBMGS00_MASAPPRO" asynchronously...

(47) Okay, child's pid=57.                                                     

(57) Starting: local /usr/sap/PRO/SYS/exe/run/igswd_mt -mode=profile pf=/usr/sap/PRO/SYS/profile/PRO_DVEBMGS00_MASAPPRO

(47) Waiting for Child Processes to terminate.                                 

(47) **** 2008/04/07 13:55:56 Child 53 terminated with Status 0 . ****         

(47) **** 2008/04/07 13:56:25 Child 54 terminated with Status 0 . **** 

Thank you in advance for your cooperation.

Best regards.

Reda Khalifa

Hi,

I'm trying to setup DBACOCKPIT in our Solution Manager to check the database in the other SAP systems, some of them live in remote iSeries. I've seen that a DBCON entry is created like this one:

AS4_HOST=<host>;AS4_CON_TYPE=SOCKETS;AS4_DB_LIBRARY=R3<SID>DATA;AS4_NQE_OPTIMIZE_METHOD=F;AS4_DB_RDBNAME=<SID>;

I've setup the connection with user <SID>ADM.

This connection is failing:

ERROR Database connection %_E30_CS02: ADBC error 'Internal error         16  has occured'

But I cannot find any reason in logs. In SAP wp appears a generic message like 'CPFB752 occured. Refer to job log', but the corresponding log for QXDARECVR is not saved.

If I change the user of connection and I use QSECOFR, the connection works. But I don't know the way to find what authorizations are missing.

Any idea ?

Regards,

Joan

Hi Guys,

We have many dumps when run a program in our system R/3 4.6C over V5R3M0.

The many dumps is:

DBIF_RSQL_SQL_ERROR

SQL error "-904" occurred when accessing table "A073 ".

OSS SAP say that i have to delete SQLPKG when the error appear.

I execute this deletion all weekend with DLTR3PKG; but the packages overflow quickly and i can close the system only the sunday.

Any suggestions? i try delete the A073 SQLPKG with the command:

WRKOBJ OBJ(ALL/A073) OBJTYPE(SQLPKG) on-line the last week; and we have many errors after this delete (all process with access to this table not run).

I increase the SQLPKG´s size to 1 GB (note 306823), but the problem persist.

Best Regards,

Ernesto Castro.

Hello,

We are facing problem in EHP4 installation.

Error:

START OF PHASE PREP_INIT/VALCHK_INI

SEVERE ERROR: SAP_ABA                        is in an undefined state,

              that is not safe to be upgraded !!!

              Reason: Upgrade wasn't completed.

              Call the SAP Support!!!

           - "continue"

            - "cancel"

Enter one of these options [continue] := continue

ERROR: Component 'SAP_ABA'' is in an undefined state 'Upgrade wasn't completed' - maybe upgrade was not reset?

We realized the problem was caused due to termination of EHPI gui(Staging server reboot).

Now as we trying to start it again we are facing above issus.

We reffered note:Note 1251735 - Add. Info. - SAP Enhancement Package Installer (7.10/5)

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

Phase: VALCHK_INI

Description: In this phase, an error can occur when you have incorrectly tried to reset the enhancement package installation. For example, you have not used the "Back" button on the GUI or the "Reset Installation" command from the menu bar. Instead, you have just aborted SAPehpi and deleted the installation directory. This results in an inconistent state in the system and a failure in phase VALCHK_INI when you start the installation program again.

If you were in one of the preparation roadmap steps when you tried to reset the installation, proceed as follows:

Procedure for UNIX and Windows:

      1. Change to the EHPI/abap/bin directory (Windows: EHPI\abap\bin)

      2. Enter the following command:

           ./SAPehpi reset prepare (Windows: .\SAPehpi. exe reset prepare)

      3. Delete the EHPI directory.

      4. Start SAPehpi again.

Procedure for IBM i:

      1. Start Qshell by entering the command QSH.

      2. Enter the following commands:

           cd <base directory>/EHPI/abap/bin

           export LIBPATH=.

           ./SAPehpi reset prepare

      3. Delete the EHPI directory.

      4. Start SAPehpi again.

If you already had reached the Preprocessing roadmap step, then contact SAP Support.

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

As suggested we raised the OSS Message but i guess SAP is taking time to solve their mess.

Due to urgency, we appreciate your inputs.

Regards,

Prasad

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

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

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,

We are implementing SAP ECC 6.0 on iSeries, i5/OS V5R4.

The application server & the database server are implemented on one centralized physical iSeries server.

We recently attempted to copy one SAP system (DEV) from one iSeries server to another, through restoring from an Entire System backup.

After successfully conducting the restore onto the new (destination) iSeries server, and conducting all the necessary host name changes to be the same as the host name of the source system, we encountered a problem when trying to start the SAP : all the jobs under sub-system R3_00 are started, except the jobs constituting the SAP work processes; i.e. WP00, WP01, …etc.

The following is the file holding the SAP start log :

/usr/sap/<SID>/DVEBMGS00/work/sapstart.log

SAP-R/3-Startup Program Rel 700 V1.8 (2003/04/24)                  

-

Starting at 2008/04/07 13:55:49                                    

Startup Profile: "/usr/sap/PRO/SYS/profile/START_DVEBMGS00_MASAPPRO"

Execute Pre-Startup Commands                                       

-

(47) Local: /usr/sap/PRO/SYS/exe/run/cleanipc 00 remove            

(47) Executing "/usr/sap/PRO/SYS/exe/run/cleanipc 00 remove"...    

(47) Okay!                                                         

(47) Local: CLRLIB LIB(R3WRK00)                                    

(47) Executing CL command "CLRLIB LIB(R3WRK00)"...                 

(47) Okay!                                                                     

(47) Local: /usr/sap/PRO/SYS/exe/run/sapmscsa pf=/usr/sap/PRO/SYS/profile/PRO_DVEBMGS00_MASAPPRO -n

(47) Executing "/usr/sap/PRO/SYS/exe/run/sapmscsa pf=/usr/sap/PRO/SYS/profile/PRO_DVEBMGS00_MASAPPRO -n"...

(47) Okay!                                                                               

Starting Programs                                                              

-

(47) Spawning program "/usr/sap/PRO/SYS/exe/run/saposcol" asynchronously...    

(47) Okay, child's pid=52.                                                     

(52) Starting: local /usr/sap/PRO/SYS/exe/run/saposcol                         

(47) Spawning program "/usr/sap/PRO/SYS/exe/run/msg_server pf=/usr/sap/PRO/SYS/profile/PRO_DVEBMGS00_MASAPPRO" asynchronously...

(47) Okay, child's pid=53.                                                     

(53) Starting: local /usr/sap/PRO/SYS/exe/run/msg_server pf=/usr/sap/PRO/SYS/profile/PRO_DVEBMGS00_MASAPPRO

(47) Spawning program "/usr/sap/PRO/SYS/exe/run/disp+work pf=/usr/sap/PRO/SYS/profile/PRO_DVEBMGS00_MASAPPRO" asynchronously...

(47) Okay, child's pid=54.                                                     

(54) Starting: local /usr/sap/PRO/SYS/exe/run/disp+work pf=/usr/sap/PRO/SYS/profile/PRO_DVEBMGS00_MASAPPRO

(47) Spawning program "/usr/sap/PRO/SYS/exe/run/rslgcoll pf=/usr/sap/PRO/SYS/profile/PRO_DVEBMGS00_MASAPPRO -F" asynchronously...

(47) Okay, child's pid=55.                                                     

(55) Starting: local /usr/sap/PRO/SYS/exe/run/rslgcoll pf=/usr/sap/PRO/SYS/profile/PRO_DVEBMGS00_MASAPPRO -F

(47) Spawning program "/usr/sap/PRO/SYS/exe/run/rslgsend pf=/usr/sap/PRO/SYS/profile/PRO_DVEBMGS00_MASAPPRO -F" asynchronously...

(47) Okay, child's pid=56.                                                     

(56) Starting: local /usr/sap/PRO/SYS/exe/run/rslgsend pf=/usr/sap/PRO/SYS/profile/PRO_DVEBMGS00_MASAPPRO -F

(47) Spawning program "/usr/sap/PRO/SYS/exe/run/igswd_mt -mode=profile pf=/usr/sap/PRO/SYS/profile/PRO_DVEBMGS00_MASAPPRO" asynchronously...

(47) Okay, child's pid=57.                                                     

(57) Starting: local /usr/sap/PRO/SYS/exe/run/igswd_mt -mode=profile pf=/usr/sap/PRO/SYS/profile/PRO_DVEBMGS00_MASAPPRO

(47) Waiting for Child Processes to terminate.                                 

(47) **** 2008/04/07 13:55:56 Child 53 terminated with Status 0 . ****         

(47) **** 2008/04/07 13:56:25 Child 54 terminated with Status 0 . **** 

Thank you in advance for your cooperation.

Best regards.

Reda Khalifa

Hi Guys,

We have many dumps when run a program in our system R/3 4.6C over V5R3M0.

The many dumps is:

DBIF_RSQL_SQL_ERROR

SQL error "-904" occurred when accessing table "A073 ".

OSS SAP say that i have to delete SQLPKG when the error appear.

I execute this deletion all weekend with DLTR3PKG; but the packages overflow quickly and i can close the system only the sunday.

Any suggestions? i try delete the A073 SQLPKG with the command:

WRKOBJ OBJ(ALL/A073) OBJTYPE(SQLPKG) on-line the last week; and we have many errors after this delete (all process with access to this table not run).

I increase the SQLPKG´s size to 1 GB (note 306823), but the problem persist.

Best Regards,

Ernesto Castro.

Dear All,

Is there a standard way to delete the job logs XXXBDCLG, XXXJOBLG for a deleted client XXX, in directory    '/sapmnt/<SID>/global',  or this could only be done at the OS level ?

Thank you in advance for your cooperation.

Best regards.

Reda

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'.

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 Guys,

We have many dumps when run a program in our system R/3 4.6C over V5R3M0.

The many dumps is:

DBIF_RSQL_SQL_ERROR

SQL error "-904" occurred when accessing table "A073 ".

OSS SAP say that i have to delete SQLPKG when the error appear.

I execute this deletion all weekend with DLTR3PKG; but the packages overflow quickly and i can close the system only the sunday.

Any suggestions? i try delete the A073 SQLPKG with the command:

WRKOBJ OBJ(ALL/A073) OBJTYPE(SQLPKG) on-line the last week; and we have many errors after this delete (all process with access to this table not run).

I increase the SQLPKG´s size to 1 GB (note 306823), but the problem persist.

Best Regards,

Ernesto Castro.

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

Thanks

Joe

Hi,

I'm trying to setup DBACOCKPIT in our Solution Manager to check the database in the other SAP systems, some of them live in remote iSeries. I've seen that a DBCON entry is created like this one:

AS4_HOST=<host>;AS4_CON_TYPE=SOCKETS;AS4_DB_LIBRARY=R3<SID>DATA;AS4_NQE_OPTIMIZE_METHOD=F;AS4_DB_RDBNAME=<SID>;

I've setup the connection with user <SID>ADM.

This connection is failing:

ERROR Database connection %_E30_CS02: ADBC error 'Internal error         16  has occured'

But I cannot find any reason in logs. In SAP wp appears a generic message like 'CPFB752 occured. Refer to job log', but the corresponding log for QXDARECVR is not saved.

If I change the user of connection and I use QSECOFR, the connection works. But I don't know the way to find what authorizations are missing.

Any idea ?

Regards,

Joan