SQL error "-99999" occurred while executing Native SQL.

[Former Member]

Hi,

I am getting below dump while executing a custom report .

Category               Installation Errors

Runtime Errors         DBIF_DSQL2_SQL_ERROR

Except.                CX_SY_NATIVE_SQL_ERROR

Date and Time          03.12.2015 12:08:02

Short Text

     SQL error "-99999" occurred while executing Native SQL.

What happened?

     Error "-99999" has occurred on the current database connection "DEFAULT".

     Database error text: CLI0112E  Error in assignment. SQLSTATE=22005 row=1 c

     Triggering SQL statement: "FETCH NEXT "

What can you do?

     Note down which actions and inputs caused the error.

     To process the problem further, contact you SAP system

     administrator.

     Using Transaction ST22 for ABAP Dump Analysis, you can look

     at and manage termination messages, and you can also

     keep them for a long time.

     Note down which actions and inputs caused the error.

     To process the problem further, contact you SAP system

     administrator.

     Using Transaction ST22 for ABAP Dump Analysis, you can look

     at and manage termination messages, and you can also

     keep them for a long time.

Error analysis

     An exception has occurred which is explained in more detail below. The

     exception, which is assigned to class 'CX_SY_NATIVE_SQL_ERROR' was not cau

      and

     therefore caused a runtime error. The reason for the exception is:

     Database error text: "CLI0112E  Error in assignment. SQLSTATE=22005 row=1

      col=30"

Strange thing is that this dump is coming in our Training system while it is working fine in Dev and QA. I have done reorgcheck for db. Still the error is coming.  DBSL patch is 223 in all systems.

Regards,

Ankit

[Former Member]

Hi,

This is from dev trace

ABAP location info 'ZCUS_POSTOFFICE', 39                                                                         

C  &+     SAP user 'TCS191012', transaction code 'SA38'                                                                    

C  &+                                                                                                                      

C  *** ERROR in DB6Fetch[/bas/741_REL/src/dbs/db6/dbdb6.c, 4157] (END)

B  ***LOG BY2=> sql error -99999 performing FET [dbds         531]

B  ***LOG BY0=> CLI0112E  Error in assignment. SQLSTATE=22005 row=1 col=30 [dbds         531]

A  TH VERBOSE LEVEL FULL

A  ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.

A  ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.

A  ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.

A  ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.

A  ** RABAX: level LEV_RX_HOTSPOT_TRACE entered.

A  ** RABAX: level LEV_RX_HOTSPOT_TRACE completed.

A  ** RABAX: level LEV_RX_SAVE_SHMLOCKS entered.

A  ** RABAX: level LEV_RX_SAVE_SHMLOCKS completed.

A  ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.

A  ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.

A  ** RABAX: level LEV_RX_ROLLBACK entered.

A  ** RABAX: level LEV_RX_ROLLBACK completed.

A  ** RABAX: level LEV_RX_DB_ALIVE entered.

A  ** RABAX: level LEV_RX_DB_ALIVE completed.

A  ** RABAX: level LEV_RX_HOOKS entered.

A  ** RABAX: level LEV_RX_HOOKS completed.

A  ** RABAX: level LEV_RX_STANDARD entered.

A  ** RABAX: level LEV_RX_STANDARD completed.

A  ** RABAX: level LEV_RX_STOR_VALUES entered.

A  ** RABAX: level LEV_RX_STOR_VALUES completed.

A  ** RABAX: level LEV_RX_C_STACK entered.

A 

A Tue Dec 15 12:00:27 2015

A  ** RABAX: level LEV_RX_C_STACK completed.

A  ** RABAX: level LEV_RX_MEMO_CHECK entered.

A  ** RABAX: level LEV_RX_MEMO_CHECK completed.

A  ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.

A  ** RABAX: level LEV_RX_AFTER_MEMO_CHECK completed.

A  ** RABAX: level LEV_RX_INTERFACES entered.

A  ** RABAX: level LEV_RX_INTERFACES completed.

A  ** RABAX: level LEV_RX_GET_MESS entered.

A  ** RABAX: level LEV_RX_GET_MESS completed.

A  ** RABAX: level LEV_RX_INIT_SNAP entered.

A  ** RABAX: level LEV_RX_INIT_SNAP completed.

A  ** RABAX: level LEV_RX_WRITE_SYSLOG entered.

A  ** RABAX: level LEV_RX_WRITE_SYSLOG completed.

A  ** RABAX: level LEV_RX_WRITE_SNAP_BEG entered.

A  ** RABAX: level LEV_RX_WRITE_SNAP_BEG completed.

A  ** RABAX: level LEV_RX_WRITE_SNAP entered.

A 

A Tue Dec 15 12:00:28 2015

A  ** RABAX: level LEV_SN_END completed.

A  ** RABAX: level LEV_RX_WRITE_SNAP_END entered.

A  ** RABAX: level LEV_RX_WRITE_SNAP_END completed.

A  ** RABAX: level LEV_RX_RAL_FOR_RABAX entered.

A  ** RABAX: level LEV_RX_RAL_FOR_RABAX completed.

A  ** RABAX: level LEV_RX_SET_ALERT entered.

A  ** RABAX: level LEV_RX_SET_ALERT completed.

A  ** RABAX: level LEV_RX_COMMIT entered.

A  ** RABAX: level LEV_RX_COMMIT completed.

A  ** RABAX: level LEV_RX_SNAP_SYSLOG entered.

A  ** RABAX: level LEV_RX_SNAP_SYSLOG completed.

A  ** RABAX: level LEV_RX_RESET_PROGS entered.

A  ** RABAX: level LEV_RX_RESET_PROGS completed.

A  ** RABAX: level LEV_RX_STDERR entered.

A  Tue Dec 15 12:00:28 2015

A 

A  ABAP Program ZCUS_POSTOFFICE                         .

A  Source ZCUS_POSTOFFICE                          Line 29.

A  Error Code DBIF_DSQL2_SQL_ERROR.

A  Module  $Id: //bas/741_REL/src/krn/abap/runt/abexsql.c#5 $ SAP.

A  Function DsqlErrorHandler Line 2168.

A  ** RABAX: level LEV_RX_STDERR completed.

A  ** RABAX: level LEV_RX_RFC_ERROR entered.

A  ** RABAX: level LEV_RX_RFC_ERROR completed.

A  ** RABAX: level LEV_RX_RFC_CLOSE entered.

A  ** RABAX: level LEV_RX_RFC_CLOSE completed.

A  ** RABAX: level LEV_RX_IMC_ERROR entered.

A  ** RABAX: level LEV_RX_IMC_ERROR completed.

A  ** RABAX: level LEV_RX_APC_ERROR entered.

A  ** RABAX: level LEV_RX_APC_ERROR completed.

A  ** RABAX: level LEV_RX_DATASET_CLOSE entered.

A  ** RABAX: level LEV_RX_DATASET_CLOSE completed.

A  ** RABAX: level LEV_RX_ERROR_SAVE entered.

A  ** RABAX: level LEV_RX_ERROR_SAVE completed.

A  ** RABAX: level LEV_RX_ERROR_TPDA entered.

A  ** RABAX: level LEV_RX_ERROR_TPDA completed.

A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.

A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.

A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.

A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.

A  ** RABAX: level LEV_RX_END entered.

A  ** RABAX: level LEV_RX_END completed.

A  ** RABAX: end no http/smtp

A  ** RABAX: end apc

A  ** RABAX: end RX_GOTO_RABAX

A  SQL error -99999 occurred while executing Native SQL..

A 

B 

B Tue Dec 15 12:00:41 2015

B  dbsync[db_syexe]: { wait=0, call_no=150, current_ts=20151215120041, last_counter=2015-12-15-06.17.32.688184

C 

C Tue Dec 15 12:02:41 2015

C  Disconnected from 'CRQ'

C  Disconnected: con_hdl=2 ; appl_hdl=2022; appl_id="172.18.128.27.64666.151215061726"

B  Disconnected from connection 3, con_da={R/3*DDFTX,5000049}

I have checked. all notes applied are consistent throughout the landscape. Please help in this

Ankit

[Sriram2009]

Hi Ankit

1. Could you share the current kernel version and release? if it is low try to upgrade the latest version and then check the same custom program.

2. DB2 database version & FP ?

3. I think you may require to raise the support ticket to SAP check further support.

Regards

SS

[Former Member]

Hi,

there is no error in db2diag.log file. I have asked dev team to test this with sap standard table. Will come back with the result.

Can you tell me how to check secondary log ?

SAP CRM 7.3, hpux, db2. Kernel and dbsl patch is same for all systems.

[Former Member]

Hi,

You can check it in ST04 --> Logging (tab from Right panel).

Secondary log section with Field name 'Logs Currently Allocated' will give you the current log usage.

You can find it at OS level via command

db2 get snapshot for database on <DBSID> | grep -i 'allocated currently'

Also you check you have NUM_LOG_SPAN parameter set for Db2.

Regards,

Prithviraj.

[Sriram2009]

Hi Ankit

1. Since it's a custom report have you check in debug mode ?

2.  Could you share your SAP details and OS / DB? could you attach the full dump as text format?

Regards

SS

[former_member200876]

Hi Ankit

     you can check with a ABAP Deveolper

BR.

M. Ezzat

[Former Member]

Hi Ankit,

Check db2diag.log file to understand what exactly went wrong.

I think there might be a case of secondary log full situation.

Regards,

Prithviraj.