Runtime Errors DBIF_RSQL_TABLE_UNKNOWN in BW system

Hi Guys,
We refreshed BW system from production to sandbox. SGEN finished successfully.
Now I am strucked at bdls. when i ran bdls i am getting below dump pls help me to resolve this.
Runtime Errors         DBIF_RSQL_TABLE_UNKNOWN
Date and Time          05.02.2008 08:32:09
What happened?
     Error in ABAP application program.
     The current ABAP program "SBDLS31220080205083134" had to be terminated because
      one of the
     statements could not be executed.
     This is probably due to an error in the ABAP program.
What can you do?
     Print out the error message (using the "Print" function)
     and make a note of the actions and input that caused the
     error.
     To resolve the problem, contact your SAP system administrator.
     You can use transaction ST22 (ABAP Dump Analysis) to view and administer
      termination messages, especially those beyond their normal deletion
     date.
     is especially useful if you want to keep a particular message.
Error analysis
     An SAP Open SQL statement contains a table that does not exist in the
     database or is not listed in the ABAP Data Dictionary.
     The table is "/BI0/0100000086 " or another table that is accessed in the
      statement.
How to correct the error
     Probably the only way to eliminate the error is to correct the program.
     Please check the entries in the system log (Transaction SM21).
     Internal call code.........: "[RSQL/READ//BI0/0100000086 ]"
     You may able to find an interim solution to the problem
     in the SAP note system. If you have access to the note system yourself,
     use the following search criteria:
     "DBIF_RSQL_TABLE_UNKNOWN" C
     "SBDLS31220080205083134" or "SBDLS31220080205083134"
     "RELEVANT_TABLES_DETERMINE"

Hi Nani,
check the temp tables like :
EDP13
EDP21
EDPP
Change source system entry to target system manually. Then try to rerun the BDLS.
Thanks,
Sanjay

Similar Messages

Portal Runtime Error while creating new system in portal content

Hi
Can anyone solve my problem, i am geting error while creating new system in p ortal content
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.templateSelection
Component Name : com.sap.portal.admin.templateselectionwizard.default
com/sap/portal/iviewserver/cache/OClass.
Exception id: 11:29_26/12/06_0014_5891950
See the details for the exception ID in the log file

Hi,
Check this link for creating system object
http://help.sap.com/bp_epv260/EP_EN/documentation/EP/N03_BB_InstallGuide_EN_US.doc
Regards
Arun

RUNTIME ERROR WHILE CREATING NEW SYSTEM IN EP6

Hi
Can anyone solve my problem, i am geting error while creating new system PORTAL FOR to connect biw 3.5 system
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.templateSelection
Component Name : com.sap.portal.admin.templateselectionwizard.default
com/sap/portal/iviewserver/cache/OClass.
Exception id: 11:29_26/12/06_0014_5891950
See the details for the exception ID in the log file
thanks in advance
Rock

hi,
check the log file and let me the the error.
manish

SMSY generating runtime error on adding new system

In our solution manager system, while trying to add a new system details
via SMSY transaction we are getting the Runtime Errors
OBJECTS_OBJREF_NOT_ASSIGNED.
Please find the dump details.
Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED
Exception              CX_SY_REF_IS_INITIAL
Date and Time          29.05.2008 10:47:54
Short text
    Access via 'NULL' object reference not possible.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLSMSY_ACTUALIZE_DATA" had to be terminated because
     it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
     caught in
    procedure "UPDATE_HOST_LCR" "(FORM)", nor was it propagated by a RAISING
     clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    You attempted to use a 'NULL' object reference (points to 'nothing')
    access a component (variable: "ACCESSOR").
    An object reference must point to an object (an instance of a class)
    before it can be used to access components.
    Either the reference was never set or it was set to 'NULL' using the
    CLEAR statement.
Information on where terminated
    Termination occurred in the ABAP program "SAPLSMSY_ACTUALIZE_DATA" - in
     "UPDATE_HOST_LCR".
    The main program was "SAPLSMSY_MAIN ".
    In the source code you have the termination point in line 2013
    of the (Include) program "LSMSY_ACTUALIZE_DATAF01".
    The termination is caused because exception "CX_SY_REF_IS_INITIAL" occurred in
    procedure "UPDATE_HOST_LCR" "(FORM)", but it was neither handled locally nor
     declared
    in the RAISING clause of its signature.
    The procedure is in program "SAPLSMSY_ACTUALIZE_DATA "; its source code begins
     in line
    1983 of the (Include program "LSMSY_ACTUALIZE_DATAF01 ".
Source Code Extract
Line SourceCde
1983 FORM UPDATE_HOST_LCR USING    IV_HOST STRUCTURE SMSY_HOST.
1984
1985   DATA:
1986         ACCESSOR        TYPE REF TO CL_SLD_ACCESSOR,
1987         VALUE           TYPE STRING,
1988         VALUE1          TYPE STRING,
1989         EX              TYPE REF TO CX_SLD_API_EXCEPTION,
1990         T_INAMES        TYPE SLD_T_STRING,
1991         INSTREF         TYPE REF TO CL_SLD_CIM_INSTANCE,
1992         SYSTREF         TYPE REF TO CL_SLD_CIM_INSTANCE,
1993         CLNTREF         TYPE REF TO CL_SLD_CIM_INSTANCE,
1994         LINKREF         TYPE REF TO CL_SLD_CIM_INSTANCE,
1995         INSTHANDLE      TYPE STRING,
1996         SYSTHANDLE      TYPE STRING,
1997         CLNTHANDLE      TYPE STRING,
1998         LINKHANDLE      TYPE STRING,
1999         T_KEYPROP       TYPE SLD_T_VALUELIST,
2000         I               TYPE I,
2001         PROPLIST        TYPE SLD_T_VALUELIST,
2002         PROPERTY        TYPE SLD_S_VALUELIST,
2003         FILTER          TYPE REF TO CL_SLD_FILTER.
2004
2005   DATA STRING          TYPE STRING.
2006   DATA IV_SYSTEM       TYPE SMSY_SYSTEM_SAP.
2007
2008   GET_SLD_TOP_INFO.
2009
2010 * Test the connection to the SLD server:
2011   TRY.
2012
>>>>>       ACCESSOR->PING( ).
2014
2015     CATCH CX_SLD_API_EXCEPTION INTO EX.
2016       VALUE = EX->GET_TEXT( ).
2017       MSGMACRO 'SCDT_LIS_IF' 'E' 11 'LCR_ERROR'.
2018   ENDTRY.
2019
2020
2021 * Catch all exceptions potentially triggered by the API:
2022   TRY.
2023
2024
2025 *   Create a new instance representation object for class SAP_BCSystem.
2026 *   If an accessor object is supplied in the constructor, the object
2027 *   reference of the representation can be used in other accessor
2028 *   methods.
2029       CREATE OBJECT SYSTREF
2030         EXPORTING
2031           CLASSNAME      = 'SAP_ComputerSystem'
2032           ACCESSOR       = ACCESSOR.
I am already at the latest support package i.e13
Regards
Anthony

Hi Anthony
Is your problem solved . I M facing the same problem . I found another thread which is suggesting to follow SAP note 1042815. But it seems that we need to change Some standard include to get it fixed .
Does SAP suggest to change their own program .
Waiting for your reply .

Getting Runtime Error on SAP CRM system TSV_ILLEGAL_REFERENCE

Runtime Errors         TSV_ILLEGAL_REFERENCE
Date and Time          07.03.2011 13:05:08
     Short text
          The reference to an internal table is destroyed.
     What happened?
          Error in the ABAP Application Program
          The current ABAP program "SAPLBUPA_SELECT" had to be terminated because it has
          come across a statement that unfortunately cannot be executed.
          The administration data for the access to an internal table can no
          longer be interpreted.
     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.
     Error analysis
          This is probably an erro in program "SAPLBUPA_SELECT". The administration data
           for
          accessing an internal table was probably destroyed by a memory
          overwriter. Such a memory overwriter is usually caused by one of the
          following programming errors:
          1) A dynamic ASSIGN with too great an offset and/or length specification
             was positioned beyond the end of the source field used in the ASSIGN.
             In the next write access to the corresponding field symbol, the
             system wrote past the limitis of the source field.
          2) A DO ... VARYING loop with an incorrect increment or too large a
             number of passes can also be positioned beyond the limits of the
             structure and be overwritten.
          3) In using the statement ASSIGN ... CASTING a memory area was
             interpreted with a different type and consequently overwritten.
     How to correct the error
          Probably the only way to eliminate the error is to correct the program.
          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:
          "TSV_ILLEGAL_REFERENCE" " "
          "SAPLBUPA_SELECT" or "LBUPA_SELECTU03"
          "BUP_BUT000_SELECT_WITH_GUID"
How to resolve this issue, can u pls help me.
Thanks & Regards,
Rajasekhar Reddy P

Hi Edmond,
it's not the ume, it's the com.sap.portal.usermanagement.admin package.
In order to redeploy it, go to following directory:
<drive>\usr\sap\<SAPSID>\JC<instance number>\j2ee\cluster\server0 \apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd
look for the com.sap.portal.usermanagement.admin.par.bak, remove the suffix .bak and restart your engine.
Don't know of this helps, but maybe it's worth a try.
Regards, Karsten

In VL02N, getting runtime error "dynpro_msg_in_help" when deleting outbound delivery in production

Hello SD members,
I have an issue in which while executing VL02N and trying to delete the outbound delivery getting runtime error "dynpro_msg_in_help" in production system.
Kindly suggest how to solve this...
Regards
Venkat

Hi Venkata Pradeep,
Can you please proivde more details about an error to understand the issue.
Regards,
Pravin

Runtime errors "Raise_Exception" occur when running crystal report

Dear all expert,
I had develop a CR. It is fine and I can run it. but in our remote system, there is a runtime error "RAISE_EXCEPTION" with exception condition "EXECUTION_HALTED". There is no error show to me at CR side where the report is running fine. But I wonder why the is a runtime error in the remote system.
Thank You.

Hi Ingo,
I had check the transport folder in my integration solution installer kit folder. There is only Folder with name "ansi" and "unicode_compatible".
The readme for my transport file are as below:
There are two sets of transport files, which can be used with BusinessObjects Enterprise Integration Kit for SAP. One set is ANSI and the other set is Unicode enabled.
The set of transports you must use depends on the BASIS system your SAP system is running on. Additionally, each transport consists of a data file and a cofile, which are listed in brackets behind the transport names.
If your SAP system is running on a BASIS system earlier than 6.20, you must use the files listed below:
(These files are ANSI.)
Open SQL Connectivity transport (K900084.r22 and R900084.r22)
Info Set Connectivity transport (K900085.r22 and R900085.r22)
Row-level Security Definition transport (K900086.r22 and R900086.r22)
Cluster Definition transport (K900093.r22 and R900093.r22)
Authentication Helpers transport (K900088.r22 and R900088.r22)
If your SAP system is running on a 6.20 BASIS system or later, you must use the files listed below:
(These files are Unicode enabled.)
Open SQL Connectivity transport (K900574.r21 and R900574.r21)
Info Set Connectivity transport (K900575.r21 and R900575.r21)
Row-level Security Definition transport (K900576.r21 and R900576.r21)
Cluster Definition transport (K900585.r21 and R900585.r21)
Authentication Helpers transport (K900578.r21 and R900578.r21)
The following files must be used on an SAP BW system:
(These files are Unicode enabled.)
Content Administration transport (K900579.r21 and R900579.r21)
Personalization transport (K900580.r21 and R900580.r21)
MDX Query Connectivity transport (K900581.r21 and R900581.r21)
ODS Connectivity transport (K900582.r21 and R900582.r21)
The dump "raise_exception" occur when in the Crystal Report Designer.
Thank You.

SAP Personas runtime error

SAP front end for SO creation(Using SAP PERSONAS) has a runtime error, meaning that the system log off and message is displayed to login again on its own if no action is taken within 45 min. Is this a default setting? Would it be possible to have it extended.

Hi,
Please go through the below SAP Note and see if that helps:
1583111 - Application Integrator Exception for SAP_LocalSystem, Even Though Different System Specified in iView
BR,
Anurag

Java i-view runtime error

Hi All,
we are using SAP BI 7.0, when running queries thorugh BI Portal we are getting one error saying that " java i-view runtime error, please contact your system administrator". once we got this error. i observed that this problem is occured due to user SAPJSF locked due to incorrect logons in BI ABAP system. if I unlock SAPJSF user we are able to run the queries from BI Portal. this is repetedly happing for us for every 15-20 days but not for fixed interval. we have ran the support desk tool and all the configurations we got is "green".
could any one please let us know
1. why this SAPJSF user is getting locked and how to block
2. how to prevent this user from getting locked.
please help me on this.
Mohan

Hi,
You can watch the Security log at the following location for tracing down the activities of this user.
/usr/sap/<SID>/JC<instance number>/j2ee/cluster/server0/log/system
With Regards,
Saurabh

Runtime error while activating LO Datasource in Source System

Hi Gurus,
I have followed the below steps to activate the SD related LO extractor in ECC
1. RSA5 --> Select all the 2LIS_11,12&13 data source and activate
2. LBWE --> Choose the 2LIS_11,12&13 data source and activate.
Upon execution of the second step , the system return me the following runtime error
Runtime Errors         DDIC_TYPE_INCONSISTENCY
Date and Time          07.07.2011 10:14:29
Short text
     Inconsistency in the Dictionary for the structure "MCQALSB".
What happened?
     Error in the SAP kernel.
     The current ABAP "SAPLMCEX" program had to be terminated because the
     ABAP processor detected an internal system error.
Error analysis
     There is an internal system error.
     eliminated with ABAP/4.
Trigger Location of Runtime Error
     Program                                 SAPLMCEX
     Include                                 LMCEX$04
     Row                                     26
With this error i cant proceed to activate any of the LO data source
Please help
Thanks in advance

The table MCQALSB need to be activated in SE11 and LBWE works fine

TS2363 Why do I get a runtime error R6034 message when installing iTunes 11.1.4.62 on my WIn XP (SP3) system?

iTunes prompted me to download and install the newest version of iTunes (11.1.4.62). I followed all on-screen prompts. iTunes installation gets to the very end, then I get a popup stating that I have a Runtime Error # R6034 "an application has made an attempt to load the C runtime library incorrectly. Please contact the application's support team for more information. Okay, I am doing that. FYI, I am runnning Windows XP (SP3). Oh, and BTW, now iTunes is COMPLELETY unusable, and I cannot synch any of my multiple iOS devices. Help please!

Go to Control Panel > Add or Remove Programs (Win XP) or Programs and Features (Later)
Remove all of these items in the following order:
iTunes
Apple Software Update
Apple Mobile Device Support
Bonjour
Apple Application Support
Reboot, download iTunes, then reinstall, either using an account with administrative rights, or right-clicking the downloaded installer and selecting Run as Administrator.
See also HT1925: Removing and Reinstalling iTunes for Windows XP or HT1923: Removing and reinstalling iTunes for Windows Vista, Windows 7, or Windows 8
Should you get the error iTunes.exe - Entry Point Not Found after the above reinstall then copy QTMovieWin.dll from:
C:\Program Files (x86)\Common Files\Apple\Apple Application Support
and paste into:
C:\Program Files (x86)\iTunes
The above paths would be for a 64-bit machine. Hopefully the same fix with the " (x86)" omitted would work on 32-bit systems with the same error.
tt2

Runtime error when trying to use Thinkvantage system updater

I get a runtime error when trying to use the Thinkvantage system updater.Have tried it numerous times and this is the exact message:
"Runtime error!
Program:C:\Program Files\Lenovo\System Update\tvsu.exe
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information."
Can somebody please help me to get the Thinkvantage system updater working properly?
Thanks-George
This issue has since been resolved.Thanks-G

I'm getting the same error. I tried reinstalling system updater but it didn't help.

Runtime Error in BOM -System attempted use dynpro 1000 program "SAPLXCSA"

Hi Guru's,
While Creating BOM in IS-Retail server using CS01 Tcode,
I am getting a ABAP Runtime Error :
"The system attempted to use dynpro 1000 in program "SAPLXCSA".This dynpro does not exist".
To correct this error Whether any configuration is required in SPRO for BOM ???
Please suggest how to solve the issue ???
Any Input is Highly Appreciated.
Thanks and Regards,
Selva

OSS NOTES

Runtime Error "Cannot find system in table file"

I need assistance!
I have a Blackberry Curve 8310 and have recently installed Version 4.5
I am trying to setup my synchronization. I have followed the steps to setup my calendar to Outlook 2007. It tells me Congratulations! You have successfully configured the product. However, when I press Finish, I get a Runtime Error "Cannot find system in table file"
I have uninstalled the program and reinstalled it - the same error appears.
Any help would be appreciated!
Solved!
Go to Solution.

FIGURED IT OUT!!!
The following steps, which are posted on the RIM Support will work; however, I had to do it a different way. In Step 1, it states that the ilxolkCompanion.fil is located in C:\Program Files\Research In Motion\BlackBerry\Connectors\MS Outlook Connector path...however, when I searched for this file, it was actually located in C:\Program Files\Blackberry\Connectors\MS Outlook Connector. (This could be because I upgraded from 4.2.2 to 4.5 w/o completing a clean uninstall...not too sure why)
Once I located the file through the command prompt, I unregistered as per the instructions in Step 1. I then followed step 2 exactly word for word...and VOILA!!! I now have Version 4.5 working with MS Outlook 2007
ResolutionIf the Connectors folder is still present in C\Program Files\Research In Motion\BlackBerry\Connectors\MS Outlook Connector, follow these steps:
Unregister the old Microsoft Outlook connector ilxolkCompanion.fil.
Open the command prompt.
Navigate to C:\Program Files\Research In Motion\BlackBerry\Connectors\MS Outlook Connector.
Type in the command regsvr32 -u ilxolkCompanion.fil.
In Desktop Manager, Microsoft Outlook will no longer be listed as an available desktop application.
Register the most current Microsoft Outlook connector.
Navigate to C:\Program Files\Research In Motion\BlackBerry\IS71 Connectors\MS Outlook Connector.
Type in the command regsvr32 msoutlookconnector.fil.
In Desktop Manager, Microsoft Outlook will now be registered as an available desktop application.
Once these steps have been completed, configure synchronization again.

Runtime Error Contract -System attempted dynpro 0201 in program "SAPLXM06"

Hi Experts,
While Creating Contract in Me31k transaction in IS-Retail server ,
I am getting a ABAP Runtime Error :
"The system attempted to use dynpro 0201 in program "SAPLXM06".This dynpro does not exist".
Program SAPMM06E
Include MM06EO0C_CUSTSCR1_HEAD_SET_DAT
Row 10
Module type (MODULE PBO)
Module Name CUSTSCR1_HEAD_SET_DATA
Please suggest how to solve the issue ???
Any Input is Highly Appreciated.
Thanks and Regards,
Selva

SOLVED BY SAP NOTES

Runtime Errors DBIF_RSQL_TABLE_UNKNOWN in BW system

Similar Messages

Maybe you are looking for