DTP failure

Hi There,
DTP has got failed due to ASSIGN_TYPE_CONFLICT, this dtp is getting failed daily coz of teh same eror. but at times I it works when we delte the bad request and repeat the dtp..
Could any one plz give me sol for this!!
Jyothi

Hi...
This dump is very common with data load based on DTP (Data Transform Process). You can observe you failed load in DTP Monitor as follows:
If you clink on ABAP dump icon as above you go to TA ST22 (ABAP Runtime Error) to see dump.
It is caused by changed meta data of objects involved in this data loads. A process (mode) used for the runtime of BI objects has a certain and determined lifetime. Generated program (GP) which is serving for transformation (TRAN) between source and target objects of your load no longer match the metadata because the metadata changes during this lifetime. It means that you have recently changed something within your source and target objects (e.g. via TA RSA1) then you transported just some part of your changes recently but not whole data flow. Therefore your GP* program is referencing to u201Eoldu201C runtime version of objects and they are already changed to u201Enewu201C version
To solve such a failed upload you need to regenerate your GP* program u2013 this involves re-activate transformation. This can be a 1st step. If this doesnu2019t help you need to go deeper and re-activate and re-transport other objects involved in data flow like 1. source object of the DTP (DSO/DS/IS for example; depending in your particular flow); 2. target object of the DTP (e.g. InfoCube/DSO/InfoProvider IO); 3. transformation; 4. the DTP as it self.
Kindly assign me some points if this helps you...
Regards,
Debjani...
Edited by: Debjani Mukherjee on Sep 6, 2008 11:27 AM

Similar Messages

DTP Failure with additional KYF

I have created a cube that is being fed by 2 DSO's. Both DSO's have the same keys. One DSO (DSO1) has 1 KYF and the other (DSO2) has 2 KYF's (say KYF1 and KYF2). I have successfully added a 3rd KYF (KYF3) to DSO2 and have loaded the DSO successfully.
However, when I add KYF3 to the cube and try to load it, I get a generic DTP failure message saying 'Error while updating to target Z*** (type INFOCUBE), Message no. RSBK241'.
When I remove the the new KYF3 from the cube, it loads successfully. Interestingly enough, when I remove KYF2 and keep the newly added KYF3 in the cube, it also loads successfully.
Any ideas?

Hi,
The reason you're getting this error when you add the new key is that there is a structural change in the cube and therefore the underlying transformation is no longer valid. You can check your transformation it will show up as inactive. Now since the DTP is based on this transformation it is also not valid and therefore fails.
You need to reactivate your transformation and then your DTP when you make changes to any object.
Hope this helps.
Regards.

Dtp failure in processchain

Hi Folks,
In my process chain dtp failure occur. There are totally 21 data packages are in my dtp. In out of 21 datapackages, 2
datapackages went to short dump. Remaining 19 datapackages fine.Because of that 2 data packages my DTP overall
status goes to RED. That DTP is in full update mode.
Now my question is,
1) When I right click on that DTP, it will show one option REPAIR. Pls explain that Repair option. what scenario that repair option used?
2) After Rectifying error, when i agin load data to target, is it necessary delete that previous red request in target or not?
Pls give me solution asap
Tha

Hi....
Kindly find the answers below :
1) When I right click on that DTP, it will show one option REPAIR. Pls explain that Repair option. what scenario that repair option used?
Repair DTP is used to repairt the failed load.......It means it will repair the existing failed load like Error DTP.....This will help ypyou to save time......instead of starting it from the scratch..........
If you delete the bad request from the target you will get the Repeat option ....
Once your analysis is done....you need to repair the load..
2) After Rectifying error, when i agin load data to target, is it necessary delete that previous red request in target or not?
Yes, to repeat a load first you have to delete the bad request for the target....
Otherwise, when you will repeat the load it will again fail.....I forgot the exact error message........but it will fail......
But to Repair you don't need to delete the existing request......
Regards,
Debjani..

DTP failure which was in process chain after transport

Hi,
I created a DTP in Development Server and it get transported to QA successfully.
I also created a Prcocess Chain that execute that DTP. When I tried to transport this Process Chain to QA, transport was sucess but when i check in QA process chain was not in active mode. its showing the error that DTP is not in active A version.
Error:Process variant DTP_LOAD DTP_4AEIYC0UV528F7W1JL587E7HR does not exist in version A
I checked the DTP in QA and I noticed that the DTP has been converted to a different technical name which is not the same as the one I transported from Development.
Example: DTP DTP_LOAD DTP_4AEIYC0UV528F7W1JL587E7HR in Dev is converted to DTP_4AN4TVDRYNSMT95UGI48JVC6J in QA.
Please advise how I can transport the Process Chain that call this DTP from dev to QA

Hi Sri,
You need to collect your DTP along with the Process chain in the same request. When you migrate DTPs from DEV to QA , a new DTP ID are generated in QA system and your DTP in the Process chain points to DEV's DTP and that is why you get this error. You can also find more information when you turn on the " Detail View On" from the menu. This will display technical name of all the objects in your process chain.
so recollect your DTPs and the process chains objects in the same transport request and migrated to QA ,this will Fix you issue.
Hope it helps,
Cheers,
Balaji

Is there any OSS note for this DTP failure???

I have loading from DSO to open hub...using DTP.(BI 7 system).It fails frequently..can anybody suggest me some patches needed for this....I have got manual solution..but if somebody..give me OSS note etc..then it will be great help...
regards,
Neo

Neo,
What is your patch / SP level and also what is the error you get - without that no one can get you any Notes specific to your issue...
Arun

DTP runs endless and fails

Hiii ,
When I execute the DTP which loads data to ODS ,It runs endless and fails .
I reactivated the ODS ,Retransported Still issue persists.
Also i tried creating new DTP it also goes into endless and status remains Yellow and turns red after some time.
Kindly help
Regards.
Akshay

Hi Akshay,
Please check in ST22 or SM21 for any errors raised by DTP failure. It might happen that it is due to partition max level reached.
Please check free background processes in SM50 and data volume in DTP request. If possible change the DSO settings as Kodanda has suggested.
Thanks
Amit

ABAP/4 processor : ASSIGN_TYPE_CONFLICT

I am recieveing this error message ABAP/4 processor : ASSIGN_TYPE_CONFLICT when i ran a DTP from a flat file datasource
to the data source object (DSO) Can someone help me ?? please...

Hi,
if you have written some own code in transformation please make sure that you are using fields witch have the same data type...
ASSIGN_TYPE_CONFLICT
DTP -ASSIGN_TYPE_CONFLICT
DTP failure
Regards
Andreas

Common issues with BW environment

Hello Experts,
could you please mention all teh common issues faced in BW environment with the solution available.
I have many issues and I wante dto know whether all teh teams face the same.
This would a good oppurtunity to have everything in one thread.
Thanks and regards
meps

Hi,
We will have somany issues plz check some of them
1. DTP Failure
Select the step-> right click and select “Display Message”-> there we will get the message which gives the reason for ABEND.
A DTP can failure due to following reasons, in such case we can go for restarting the job.
System Exception Error
Request Locked
ABAP Run time error.
Duplicate records
Erroneous Records from PSA.
Duplicate records:            In case of duplication in the records, we can find it in the error message along with the Info Provider’s name. Before restarting the job after deleting the bad DTP request, we have to handle the duplicate records. Go to the info provider -> DTP step -> Update tab -> check handle duplicate records -> activate -> Execute DTP. After successful competition of the job uncheck the Handle Duplicate records option and activate. DTP Log Run:
If a DTP is taking log time than the regular run time without having the back ground job, then we have to turn the status of the DTP into Red and then delete the DTP bad request (If any), repeat the step or restart the job.
Before restarting the Job/ repeating the DTP step, make sure about the reason for failure.
If the failure is due to “Space Issue” in the F fact table, engage the DBA team and also BASIS team and explain them the issue. Table size needs to be increased before performing any action in BW. It’ll be done by DBA Team. After increasing the space in the F fact table we can restart the job.
Erroneous Records from PSA:      When ever a DTP fails because of erroneous records while fetching the data from PSA to Data Target, in such cases data needs to be changed in the ECC. If it is not possible, then after getting the approval from the business, we can edit the Erroneous records in PSA and then we have to run the DTP. Go to PSA -> select request -> select error records -> edit the records and save.Then run the DTP. 2.      INFO PACKAGE FAILURE: The following are the reasons for Info Pack failure.
Source System Connection failure
tRFC/IDOC failure
Communication Issues
Processing the IDOC Manually in BI
Check the source system connection with the help of SAP BASIS, if it is not fine ask them to rebuild the connection. After that restart the job (Info Pack).
Go to RSA1 -> select source system -> System -> Connection check.
In case of any failed tRFC’s/IDOC’s, the error message will be like “Error in writing the partition number DP2” or “Caller 01, 02 errors”. In such case reprocess the tRFC/IDOC with the help of SAP BASIS, and then job will finish successfully.
If the data is loading from the source system to DSO directly, then delete the bad request in the PSA table, then restart the job
Info Pack Long Run: If an info pack is running long, then check whether the job is finished at source system or not. If it is finished, then check whether any tRFC/IDOC struck/Failed with the help of SAP BASIS. Even after reprocessing the tRFC, if the job is in yellow status then turn the status into “Red”. Now restart / repeat the step. After completion of the job force complete.
Before turning the status to Red/Green, make sure whether the load is of Full/Delta and also the time stamp is properly verified.
Time Stamp Verification:
Select Info Package-> Process Monitor -> Header -> Select Request -> Go to source System (Header->Source System) -> Sm37-> give the request and check the status of the request in the source system -> If it is in active, then we have to check whether there any struck/failed tRFC’s/IDOC’s If the request is in Cancelled status in Source system -> Check the Info Pack status in BW system -> If IP status is also in failed state/cancelled state -> Check the data load type (FULL or DELTA) -> if the status is full then we can turn the Info Package status red and then we can repeat/restart the Info package/job. -> If the load is of Delta type then we have to go RSA7 in source system-> (Compare the last updated time in Source System SM37 back ground job)) Check the time stamp -> If the time stamp in RSA7 is matching then turn the Info Package status to Red -> Restart the job. It’ll fetch the data in the next iterationIf the time stamp is not updated in RSA7 -> Turn the status into Green -> Restart the job. It’ll fetch the data in the next iteration.
Source System
BW System
Source System RSA7
Source System SM37
Action
I/P Status RED(Cancelled)
I/P Status (Active)
Time stamp matching with SM37 last updated time
Time stamp matching with RSA7 time stamp
Turn the I/P Status into Red and Restart the Job
I/P Status RED(Cancelled)
I/P Status (Cancelled)
Time stamp matching with SM37 last updated time
Time stamp matching with RSA7 time stamp
Turn the I/P Status into Red and Restart the Job
I/P Status RED(Cancelled)
I/P Status (Active)
Time stamp is not matching with SM37 last updated time
Time stamp is not matching with RSA7 time stamp
Turn the I/P status into Green and Restart the job
I/P Status RED(Cancelled)
I/P Status (Cancelled)
Time stamp is not matching with SM37 last updated time
Time stamp is not matching with RSA7 time stamp
Turn the I/P status into Green and Restart the job
Processing the IDOC Manually in BI:
When there is an IDOC which is stuck in the BW and successfully completed the background job in the source system, in such cases we can process the IDOC manually in the BW. Go to Info Package -> Process Monitor -> Details -> select the IDOC which is in yellow status(stuck) -> Right click -> Process the IDOC manually -> it’ll take some time to get processed.******Make sure that we can process the IDOC in BW only when the back ground job is completed in the source system and stuck in the BW only.   3.      DSO Activation Failure: When there is a failure in DSO activation step, check whether the data is loading to DSO from PSA or from the source system directly. If the data is loading to DSO from PSA, then activate the DSO manually as follows
Right click DSO Activation Step -> Target Administration -> Select the latest request in DSO -> select Activate -> after request turned to green status, Restart the job.
If the data is loading directly from the source system to DSO, then delete the bad request in the PSA table, then restart the job
4.      Failure in Drop Index/ Compression step: When there is a failure in Drop Index/ compression step, check the Error Message. If it is failed due to “Lock Issue”, it means job failed because of the parallel process or action which we have performed on that particular cube or object. Before restarting the job, make sure whether the object is unlocked or not. There is a chance of failure in Index step in case of TREX server issues. In such cases engage BASIS team and get the info reg TREX server and repeat/ Restart the job once the server is fixed. Compression Job may fail when there is any other job which is trying to load the data or accessing from the Cube. In such case job fails with the error message as “Locked by ......” Before restarting the job, make sure whether the object is unlocked or not. 5. Roll Up failure: “Roll Up” fails due to Contention Issue. When there is Master Data load is in progress, there is a chance of Roll up failure due to resource contention. In such case before restarting the job/ step, make sure whether the master data load is completed or not. Once the master data load finishes restart the job. 6. Change Run – Job finishes with error RSM 756       When there is a failure in the attribute change run due to Contention, we have to wait for the other job (Attribute change run) completion. Only one ACR can run in BW at a time. Once the other ACR job is completed, then we can restart/repeat the job. We can also run the ACR manually in case of nay failures. Go to RSA1-> Tool -> Apply Hierarchy/Change Run -> select the appropriate Request in the list for which we have to run ACR -> Execute. 7. Transformation In-active: In case of any changes in the production/moved to the production without saving properly or any modification done in the transformation without changing, in such cases there is a possibility of Load failure with the error message as “ Failure due to Transformation In active”. In such cases, we will have to activate the Transformation which is inactive. Go to RSA1 -> select the transformation -> Activate In case of no authorization for activating the transformation in production system, we can do it by using the Function Module - RSDG_TRFN_ACTIVATE Try the following steps to use the program "RSDG_TRFN_ACTIVATE” here you will need to enter certain details:Transformation ID: Transformation’s Tech Name (ID)Object Status: ACTType of Source: “Source Name”Source name: “Source Tech Name”Type of Target: Target NameTarget name: “Target Tech Name”
Execute. The Transformation status will be turned into Active.
Then we can restart the job. Job will be completed successfully.
     8. Process Chain Started from the yesterday’s failed step:
In few instances, process chain starts from the step which was failed in the previous iteration instead of starting from the “Start” step.
In such cases we will have to delete the previous day’s process chain log, to start the chain form the beginning (from Start variant).
Go To ST13-> Select the Process Chain -> Log -> Delete.
Or we can use Function Module for Process Chain Log Deletion: RSPROCESS_LOG_DELETE.
Give the log id of the process chain, which we can get from the ST13 screen.
Then we can restart the chain.
Turning the Process Chain Status using Function Module:
At times, when there is no progress in any of the process chains which is running for a long time without any progress, we will have to turn the status of the entire chain/Particular step by using the Function Module.
Function Module: RSPC_PROCESS_FINISH
The program "RSPC_PROCESS_FINISH" for making the status of a particular process as finished.
To turn any DTP load which was running long, so please try the following steps to use the program "RSPC_PROCESS_FINISH" here you need to enter the following details:
LOG ID: this id will be the id of the parent chain.
CHAIN: here you will need to enter the chain name which has failed process.
TYPE: Type of failed step can be found out by checking the table "RSPCPROCESSLOG" via "SE16" or "ZSE16" by entering the Variant & Instance of the failed step. The table "RSPCPROCESSLOG" can be used to find out various details regarding a particular process.
INSTANCE & VARIANT: Instance & Variant name can be found out by right clicking on the failed step and then by checking the "Displaying Messages Options" of the failed step & then checking the chain tab.
STATE: State is used to identify the overall state of the process. Below given are the various states for a step.
R Ended with errors
G Successfully completed
F Completed
A Active
X Canceled
P Planned
S Skipped at restart
Q Released
Y Ready
Undefined
J Framework Error upon Completion (e.g. follow-on job missing)
9. Hierarchy save Failure:
When there a failure in Hierarchy Save, then we have to follow the below process...
If there is an issue with Hierarchy save, we will have to schedule the Info packages associated with the Hierarchies manually. Then we have to run Attribute Change Run to update the changes to the associated Targets. Please find the below mentioned the step by step process...
ST13-> Select Failed Process Chain -> Select Hierarchy Save Step -> Rt click Display Variant -> Select the info package in the hierarchy -> Go to RSA! -> Run the Info Package Manually -> Tools -> Run Hierarchy/Attribute Change Run -> Select Hierarchy List (Here you can find the List of Hierarchies) -> Execute.

Failure for DTP

Hello Gurus,
        I have a failure for DTP, detailed message in the monitor as follows, please show me how can I deal with it?
       Data Package 14: Errors During Processing
                      Update to DataStore Object ZCANDTRA : 50001 -> 50001 Data Records
                      Data package 14 / 04/29/2010 18:44:24 / Status 'Processed with Errors'
Many thanks

Hi,
It looks like the record has got some errors check what the desciption tells you and also check if it any special characters.If it is special characters then include those and reload.It should work fine.
Harish
Edited by: Harish3152 on Apr 30, 2010 10:59 AM

DTP Full load failure ?

Hi all ,
we have enhanced the 0material_attr datasource by adding 4 new fields .
we ran the full infopackage and it is updated successfully in PSA .
but iam running the DELTA DTP it is getting failed and goes to short dump , saying that no more storage sapce availble for extending an internal table .
any help on this ?
Thanks

This is related to Table space issue.
Ask your basis to check weather you have sufficient free space in PSATEMP table and other respective tables.
You can get more details about table space in DB02 transaction.
Or
decrease the Packet size, and split the selection and run the DTP or ask basis to increase the space.
Can you post the exact Dump so that we can provide you the exact details if above info does not help.
Regards
KP

Auto retry of select statements on failure

I have a IBM Message Broker message flow that accesses the database to fetch some data. following are the steps in a message flow. (similar pattern is there in other flows as well)
1) Parse the input message
2) Invoke a ESQL compute node that accesses the database. This uses DataDirect ODBC drivers to access the database.
3) process the data
4) Invoke an external Java class that also accesses the database. This Java class uses Spring/Hibernate and uses the Oracle UCP library.
Steps 2 and 4 access an Oracle database on which failover features are NOT enabled. Following is our observation.
If the database fails when executing step 2, then the message flow pauses until a valid connection is available and then proceeds with the execution, the point to note is that the message flow does not experience a failure. It simply pauses until it gets a connection and continues once it gets a connection.
If the database fails when executing step 4, the message flow gets an error.
What we want is for step 2 and 4 to execute the same way, meaning that we want the message flows to wait until a valid connection is available and then continue without any errors.
I feel that there is some feature in DataDirect driver that cause step 2 to pause the message flow and prevent an error. We want the same behaviour in step 4 as well.
So, is there some way (via configuration or any other means) to get this behaviour using oracle UCP library.
One thing to note is that we are not in position to change the Java code since it has been developed by a third party.
To achieve this I have written a test and the following are details.
For this I have created a service with the following properties. Point to note is that we run the service on only one instance at a time, if it goes down then it is started on the second instance.
Service name: LDL_TEST02
Service is enabled
Server pool: CSAHEDA_LDL_TEST02
Cardinality: 1
Disconnect: false
Service role: PRIMARY
Management policy: AUTOMATIC
DTP transaction: false
AQ HA notifications: true
Failover type: SELECT
Failover method: NONE
TAF failover retries: 180
TAF failover delay: 5
Connection Load Balancing Goal: LONG
Runtime Load Balancing Goal: NONE
TAF policy specification: BASIC
Edition:
Preferred instances: CSAHEDA1
Available instances: CSAHEDA2
Following is in my tnsnames.ora file and I am using the oracle oci driver.
TESTA =
(DESCRIPTION =
(ENABLE = BROKEN)
(LOAD_BALANCE = off)
(FAILOVER = on)
     (ADDRESS_LIST =
     (ADDRESS = (PROTOCOL = TCP)(HOST = vip.host1)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = vip.host2)(PORT = 1521)))
(CONNECT_DATA =
(SERVICE_NAME = LDL_TEST02)
(FAILOVER_MODE =
(BACKUP = TESTA2)
(TYPE = SELECT)
(METHOD = PRECONNECT)
(RETRIES = 120)
(DELAY = 5)
This is how I run my test.
1)I have a simple test that simply loops through a list of select statements.
2)each time it takes a connection from the connection pool, executes the statement and returns the connection to the connection pool.
3)I keep this running for around 10 minutes.
4) once the test has started I bring down the service wait for 3 minutes and the start the service on the second instance.
5) what I expect is for the test to pause for 3 minutes and then get the correct value from executing the select statement. and continue without pause.
Following is the config for the connection pool.
     <bean id="dd_Datasource" class="oracle.ucp.jdbc.PoolDataSourceFactory" factory-method="getPoolDataSource">
          <property name="connectionFactoryClassName" value="oracle.jdbc.xa.client.OracleXADataSource"/>
          
          
          
          
          
          
          <property name="URL" value="jdbc:oracle:oci:/@TESTA" />
          
          
          
          
          <property name="user" value="user" />
          <property name="password" value="user" />
          <property name="connectionPoolName" value="dd_connectionpool" />
          <property name="minPoolSize" value="2" />
          <property name="maxPoolSize" value="4" />
          <property name="initialPoolSize" value="2" />
          <property name="connectionWaitTimeout" value="10000" />
          
          <property name="validateConnectionOnBorrow" value="true"/>
          
          
          
          
     </bean>
As you can see I have tried many combinations.
Sometimes I see the thread pause for 3 minutes without error and then continue.
Sometime I start seeing 'oracle.ucp.UniversalConnectionPoolException: Cannot get Connection from Datasource' as soon as the servic is down.
Sometime the first error above is seen after 30 seconds (always the first one).
Can you guys shed any light on this? And how can I get the desired behaviour?
Edited by: user12181209 on 30-May-2012 02:22
reworded.
Edited by: user12181209 on May 30, 2012 6:28 AM
reworded the title for clarity.
Edited by: user12181209 on Jun 1, 2012 6:01 AM

Hi,
Yesterday, a similar question on running slow view was post :
View is tooo slow....
You can read different questions to try to help you.
Nicolas.

Process chain failure at AND condition

Hi gurus,
Please help me with this issue .
the process chain is failing at the AND process after the DTPgets succesful . its giving the error message as"THIS AND PROCESS IS NOT WAITING FOR EVENT RS PROCESS".
PLEASE SUGGEST.

Yes,
there are two dtps which are connected to this AND process.process chain is successful untill this dtps and failed at this AND condition. please suggest to fix this and let me know wht will be the possible reason for this failure.
thanks for your help

Error DBIF_RSQL_SQL_ERROR and DBIF_REPO_SQL_ERROR while running DTP

Hi to all,
I am loading the data from PSA to DSO, while running DTP, after some records load a run time error coming DBIF_RSQL_SQL_ERROR or DBIF_REPO_SQL_ERROR .
Also i tried the Number of Processes reduce from 3 to 1 in DTP, but still same error .
i have searched the SDN and found that it is due to table space problem.
if it is due to table space , how i will find it and how to correct it.
Please can any one tell we why it is coming and what is the solution for that.
i shall be thankful to you for this.
Regards
Pavneet Rana

Thanks for reply,
i have checked ST22 . and found the error text for 2 runtime error .
first for DBIF_RSQL_SQL_ERROR
second for DBIF_REPO_SQL_ERROR
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Date and Time          14.03.2011 22:00:21
Short text
     SQL error in the database when accessing a table.
What can you do?
     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.
How to correct the error
    Database error text........: "SQL30081N A communication error has been
     detected. Communication protocol being used: "TCP/IP". Communication API being
     used: "SOCKETS". Location where the error was detected: "200.1.1.66".
     Communication function detecting the error: "recv". Protoco"
    Internal call code.........: "[RSQL/FTCH/RSBMONMESS ]"
    Please check the entries in the system log (Transaction SM21).
    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_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
    "CL_RSBM_LOG_REQUEST_ROOT======CP" or "CL_RSBM_LOG_REQUEST_ROOT======CM00F"
    "GET_STATIC_BUFFER"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
   3. If the problem occurs in a problem of your own or a modified SAP
   program: The source code of the program
      In the editor, choose "Utilities->More
   Utilities->Upload/Download->Download".
   4. Details about the conditions under which the error occurred or which
   actions and input led to the error.
   The exception must either be prevented, caught within proedure
   "GET_STATIC_BUFFER" "(METHOD)", or its possible occurrence must be declared in
    the
   RAISING clause of the procedure.
   To prevent the exception, note the following:
Information on where terminated
    Termination occurred in the ABAP program "CL_RSBM_LOG_REQUEST_ROOT======CP" -
     in "GET_STATIC_BUFFER".
    The main program was "RSBATCH_EXECUTE_PROZESS ".
    In the source code you have the termination point in line 29
    of the (Include) program "CL_RSBM_LOG_REQUEST_ROOT======CM00F".
    The program "CL_RSBM_LOG_REQUEST_ROOT======CP" was started as a background job.
    Job Name....... "BIDTPR_2256_1"
    Job Initiator.. " a"
    Job Number..... 18254200
    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
    procedure "GET_STATIC_BUFFER" "(METHOD)", but it was neither handled locally
     nor declared
    in the RAISING clause of its signature.
    The procedure is in program "CL_RSBM_LOG_REQUEST_ROOT======CP "; its source
     code begins in line
    1 of the (Include program "CL_RSBM_LOG_REQUEST_ROOT======CM00F ".
Source Code Extract
Line SourceCde
    1 method get_static_buffer.
    2   data l_s_storage type rsbm_s_storage.
    3   l_s_storage = get_s_storage( ).
    4   check l_s_storage-type = rsbm_c_storagetype-database..
    5   delete o_th_nodes_static where logid = n_logid.
    6   delete o_t_msg_static where logid = n_logid.
    7   delete o_t_logpar_static where logid = n_logid.
    8   select *
    9     from rsbmnodes connection (l_s_storage-id)
   10     appending corresponding fields of table o_th_nodes_static
   11     where logid = n_logid.
   12
   13   data l_count_monmess type sytabix.
   14   select count( * ) from rsbmonmess
   15     into l_count_monmess
   16     where logid = n_logid.
   17   if l_count_monmess > 50000.
   18     select * from rsbmonmess up to 50000 rows connection (l_s
   19       appending corresponding fields of table o_t_msg_static
   20       where logid = n_logid
   21       and   posit < 50
   22       order by node posit.
   23   else.
   24     select * from rsbmonmess connection (l_s_storage-id)
   25       appending corresponding fields of table o_t_msg_static
   26       where logid = n_logid
   27       order by node posit.
   28   endif.
>>>>>   select * from rsbmlogpar
   30     appending corresponding fields of table o_t_logpar_static
   31     where logid = n_logid.
   32   field-symbols: <l_s_nodes> type rsbmnodes,
   33                  <l_s_log> type s_log.
   34   read table o_th_log assigning <l_s_log>
   35     with table key logid = n_logid.
   36   if sy-subrc <> 0.
   37     break hoeferf.                                          "
   38   endif.
   39   loop at o_th_nodes_static assigning <l_s_nodes>.
   40     if <l_s_nodes>-node > <l_s_log>-maxnode.
   41       <l_s_log>-maxnode = <l_s_nodes>-node.
   42     endif.
43   endloop.
44 * --- set datapackage buffer
45   cl_rsbk_dp_state=>free_buffer( n_requid ).
46   cl_rsbk_dp_state=>fill_buffer( n_requid ).
47 endmethod.
Runtime Errors         DBIF_REPO_SQL_ERROR
Date and Time          14.03.2011 15:34:32
Short text
     SQL error "-99999" occurred when accessing program
What can you do?
     Note which actions and input led to the error.
     For further help in handling the problem, contact your SAP administrato
     You can use the ABAP dump analysis transaction ST22 to view and manage
     termination messages, in particular for long term reference.
How to correct the error
     Database error text........: "CLI0108E Communication link failure.
      SQLSTATE=40003"
     Triggering SQL statement...: "CX_SY_NATIVE_SQL_ERROR========CP "
     Internal call code.........: "[REPO/*/43/LOAD/CX_SY_NATIVE_SQL_ERROR===
     Please check the entries in the system log (Transaction SM21).
     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_REPO_SQL_ERROR" " "
     "SAPLSYDB" or "LSYDBU27"
     "DB_COMMIT"
     If you cannot solve the problem yourself and want to send an error
     notification to SAP, include the following information:
     1. The description of the current problem (short dump)
        To save the description, choose "System->List->Save->Local File
     (Unconverted)".
     2. Corresponding system log
        Display the system log by calling transaction SM21.
        Restrict the time interval to 10 minutes before and five minutes
     after the short dump. Then choose "System->List->Save->Local File
     (Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
    In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
Information on where terminated
    Termination occurred in the ABAP program "SAPLSYDB" - in "DB_COMMIT".
    The main program was "RSBATCH_EXECUTE_PROZESS ".
    In the source code you have the termination point in line 7
    of the (Include) program "LSYDBU27".
    The program "SAPLSYDB" was started as a background job.
    Job Name....... "BIDTPR_2252_1"
    Job Initiator.. "A"
    Job Number..... 12541100
Source Code Extract
Line SourceCde
    1 FUNCTION DB_COMMIT.
    2 *"----------------------------------------------------------------------
    3 *"*"Lokale Schnittstelle:
    4 *"----------------------------------------------------------------------
    5
    6   EXEC SQL.
>>>>>     COMMIT WORK
    8   ENDEXEC.
    9
   10 ENDFUNCTION
please can any one tell me cause for runtime error.
i shall be thankful to you for this.
regards
pavneet rana
Edited by: pavneet rana on Mar 15, 2011 1:29 PM

Portfast case ping transmit failed general failure

Hi
today i add a host in a vlan, but it can't ping itself and get ping transmit failed general failure unless remove the spaning portfast command. i try difeerent vendor PC, IBX... ,HX..,DXl..., all host can't ping itself.
the reason is the portfast? but portfast isn't only fotr host pc,
the following is same our command about spaning.sorry for i can't past all command because our com private.
errdisable recovery cause udld
errdisable recovery cause bpduguard
errdisable recovery cause security-violation
errdisable recovery cause channel-misconfig
errdisable recovery cause pagp-flap
errdisable recovery cause dtp-flap
errdisable recovery cause link-flap
errdisable recovery cause gbic-invalid
errdisable recovery cause l2ptguard
errdisable recovery cause psecure-violation
errdisable recovery cause dhcp-rate-limit
errdisable recovery cause unicast-flood
errdisable recovery cause vmps
errdisable recovery cause storm-control
errdisable recovery cause arp-inspection
errdisable recovery interval 30
power redundancy-mode redundant
no file verify auto
spanning-tree mode pvst
spanning-tree loopguard default
spanning-tree portfast bpduguard default
spanning-tree extend system-id

what do you see under "show interface status" of the switch when the issue occurs?
do you see input/output rate on that interface when the issue occurs?
what is the spanning-tree state of that port?
when you say you get "ping transmit failed", are you getting that error when you try to ping the PC's IP address from the PC?
are you able to ping 127.0.0.1?
and, what does the PC's network connection say?

Processing terminated Error in DTP

Hello gurus,
When I tried to do full load in DTP , I get Processing terminated error after End Routine.
I tried to run same DTP for one material and it executed Properly without any error.
There are only 25000 records in Full load.
Following is the exact Error Message.
'Data package Status 'Processed with Errors'
Message no. RSBK257'
Please suggest .
Thanks ,

May be due to incorrect data, DTP is getting failed when it comes to end routine calculations,
click on the Red Icon on the error message, it'll give you more information about the failure
or else set the break-point in the end routine and then execute the dtp in Debuggin mode(expert mode)
then you can find when actually it is getting wrong.
ex: May be some time when you get blank data for date fields , it'll throw an error saying 0Date is out of Factory range, ...
So debug and check which filed data is wrong.

DTP failure

Similar Messages

Maybe you are looking for