cancel
Showing results for 
Search instead for 
Did you mean: 

DBIF_RSQL_INVALID_RSQL executing DTP

Former Member
0 Kudos

Executing a DTP gets me the following error:

Error: DBIF_RSQL_INVALID_RSQL

Excep: CX_SY_OPEN_SQL_DB

I increased the packet size, but didnt work. Has anyone encounter the same problem on your loads?

Thank you,

David G

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Can u give the dump details??? If you are loading to the cube...can u delete the index and then try loading

Regards,

B

Former Member
0 Kudos

Thank you for your answer,

In this case we are uploading to an DSO so no indexes are needed to delete.

I looked for the notes in sap but didnt find the same problem as it suggested. In the transaction ST22, no more information was provided.

Let me know if you need more code

thanks again.

Here the code file


                                                                                ¿Qué ha sucedido?                                                                                
Error in the ABAP Application Program                                                                                
The current ABAP program "CL_RSODSO_SEMANTIC_PACKETIZER=CP" had to be                          
      terminated because it has                                                                     
     come across a statement that unfortunately cannot be executed.                                                                                
¿Qué puede hacer?                                                                                
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 which actions and input led to the error.                                                                                
For further help in handling the problem, contact your SAP administrator                       
     .                                                                                
You can use the ABAP dump analysis transaction ST22 to view and manage                         
     termination messages, in particular for long term reference.                                                                                
Anál.errores                                                                                
Es ist eine Ausnahme aufgetreten, die weiter unten näher erläutert wird.                       
     Die Ausnahme, der die Klasse 'CX_SY_OPEN_SQL_DB' zugeordnet ist,                               
     wurde in der Prozedur "FETCH_PACKAGE" "(METHOD)" weder abgefangen,                             
     noch durch eine RAISING-Klausel propagiert.                                                    
     Da der Aufrufer der Prozedur nicht mit dem Auftreten der Ausnahme                              
     rechnen konnte, wurde das laufende Programm abgebrochen.                                       
     Der Grund für die Ausnahme ist:                                                                                
The SQL statement generated from the SAP Open SQL statement violates a                         
     restriction imposed by the underlying database system of the ABAP                              
     system.                                                                                
Possible error causes:                                                                                
o The maximum size of an SQL statement was exceeded.                                          
      o The statement contains too many input variables.                                            
      o The input data requires more space than is available.                                       
      o ...                                                                                
You can generally find details in the system log (SM21) and in the                          
    developer trace of the relevant work process (ST11).                                        
    In the case of an error, current restrictions are frequently displayed                      
    in the developer trace.                                                                                
Notas para corregir errores                                                                     
    The SAP Open SQL statement concerned must be divided into several                           
    smaller units.                                                                                
If the problem occurred due to the use of an excessively large table                        
    in an IN itab construct, you can use FOR ALL ENTRIES instead.                               
    When you use this addition, the statement is split into smaller units                       
    according to the restrictions of the database system used.                                                                                
If the error occures in a non-modified SAP program, you may be able to                      
    find an interim solution in an SAP Note.                                                    
    If you have access to SAP Notes, carry out a search with the following                      
    keywords:                                                                                
"DBIF_RSQL_INVALID_RSQL" "CX_SY_OPEN_SQL_DB"                                                
    "CL_RSODSO_SEMANTIC_PACKETIZER=CP" or "CL_RSODSO_SEMANTIC_PACKETIZER=CM002"                 
    "FETCH_PACKAGE"                                                                                
Die Ausnahme muß entweder verhindert werden, innerhalb der Prozedur                         
    "FETCH_PACKAGE" "(METHOD)" abgefangen werden oder                                           
    ihr potentielles Auftreten in der RAISING-Klausel der Prozedur                              
    deklariert werden.                                                                          
    Um die Ausnahme zu verhindern, beachten Sie bitte folgendes:                                


 Lín.  Txt.fte.                                                                                
43                  <fs_t_output_packet>    TYPE table,                                        
   44                  <fs_s_fetcharea_before> TYPE any,                                          
   45                  <fs_s_fetcharea_after>  TYPE any.                                          
   46                                                                                
47   DATA:          l_t_msg                 TYPE rsodso_t_msg,                                 
   48                  l_no_data_read          TYPE rs_bool,                                      
   49                  l_key_has_changed       TYPE rs_bool,                                      
   50                  l_lines_selected        TYPE int4.                                         
   51                                                                                
52   TRY.                                                                                
53                                                                                
54 *   --------------------------------------------------------------------                    
   55 *   INITIALISATION                                                                          
   56 *   --------------------------------------------------------------------                    
   57                                                                                
58     ASSIGN p_r_t_datapacket->*       TO <fs_t_datapacket>.                                  
   59     ASSIGN p_r_t_output_packet->*    TO <fs_t_output_packet>.                               
   60     ASSIGN p_r_s_fetcharea_before->* TO <fs_s_fetcharea_before>.                            
   61     ASSIGN p_r_s_fetcharea_after->*  TO <fs_s_fetcharea_after>.                             
   62                                                                                
63     l_no_data_read = rs_c_false.                                                            
   64                                                                                
65     CLEAR <fs_t_output_packet>.                                                             
   66     CLEAR <fs_s_fetcharea_before>.                                                          
   67     CLEAR <fs_s_fetcharea_after>.                                                           
   68                                                                                
69 *   --------------------------------------------------------------------                    
   70 *   FETCH LOGIC                                                                                
71 *   --------------------------------------------------------------------                    
   72                                                                                
FETCH NEXT CURSOR  p_cursor                                                             
   74     APPENDING TABLE    <fs_t_datapacket>                                                    
   75     PACKAGE SIZE       p_packet_size.                                                       
   76                                                                                
77 *   NO DATA TO READ (SEE ITEM 1)                                                            
   78                                                                                
79     IF sy-subrc <> 0.                                                                       
   80       IF LINES( <fs_t_datapacket> ) = 0.                                                    
   81         l_no_data_read = rs_c_true.                                                         
   82         RAISE EXCEPTION TYPE cx_rsodso_stop_processing.                                     
   83       ELSE.                                                                                
84         APPEND LINES OF <fs_t_datapacket> TO <fs_t_output_packet>.                         
   85         CLEAR <fs_t_datapacket>.                                                           
   86         RAISE EXCEPTION TYPE cx_rsodso_stop_processing.                                    
   87       ENDIF.                                                                                
88     ENDIF.                                                                                
89                                                                                
90     l_lines_selected = LINES( <fs_t_datapacket> ).                                         
   91                                                                                
92 *   LAST PACKET TO BE PROCESSED (SEE ITEM 2)                                               
 

Former Member
0 Kudos

Another comment,

this is working fine in development environment, but not in production.

Former Member
0 Kudos

Can u ask the basis to chk for the tablespace availability for which ur DSO belong..migt be because of table space non availability.

Regards,

B

former_member392467
Discoverer
0 Kudos

Please try note 1133141.

Regards,

Therdsak