DBIF_REPO_SQL_ERROR

Hi,
we are developing BSP pages with HTML and HTMLB code.
Few days ago, we notice the following error when we try to activate and execute pages with HTMLB (this pages always have run):
Runtime errors: DBIF_REPO_SQL_ERROR
   SQL error 1555 occurred when accesing program
Trigger Location of runtime error
Program: CL_HTMLB_INPUTFIELD============CP
Module type: (METHOD)
Module Name:  IF_BSP_ELEMENT~COMPILE_TIME_IS_VALID
So, i don´t know if this error is a database problem. Our database type is Oracle 9.2.0 and our SAP WAS Release 6.40.
I have tried to search in the forum before post my question, but i didn´t find anything about this
Somebody can help me?
Thanks so much.
Susana
Message was edited by: Susana Senent

Do you mind sharing the solution?
Then others who search this forum will also find the answer to your problem - that's the spirit of SDN

Similar Messages

  • JOB Cancelled - DBIF_REPO_SQL_ERROR

    Hello masters,
    An help please....
    I am in SD module.
    Tthe JOB has been cancelled.
    User wants to know what has happened and how fix it to not occur anymore?
    I think this is not a real error in the program.
    However I would like to know the technical explanation in order to inform the user.
    Details about the JOB:
    JOB was cancelled in the 1º step which is an ABAP Z program.
    This JOB runs the end of each month.
    This month the JOB was has not been sent to external interface because the program is giving this DUMP.
    JOB LOG:
    Runtime errors: DBIF_REPO_SQL_ERROR
    Occurred on: 29.06.2007 at 02:45:27
    SQL error 3114 occurred when accessing program
    What happened?
    The system is no longer linked to an ORACLE instance.
    No further operations can be performed on the database.
    What can you do?
    You cannot eliminate this error yourself.
    Please inform your database administrator.
    Make a note of the actions and input which caused the error.
    To resolve the problem, contact your SAP system administrator.
    Thanks in advance!!!!
    Regards,
    Barbara

    Thanks for the repaly,
    The database system is ORACLE.
    Rgds,
    Barbara

  • DBIF_REPO_SQL_ERROR short dumps while activating data in ODS

    Hi All,
    We are using BW3.5 with Oracle 9.2 on AIX 5.3 box, from the past few days we are getting DBIF_REPO_SQL_ERROR short dumps frequently while activating data in ODS.
    Runtime Error          DBIF_REPO_SQL_ERROR
    Date and Time          08.01.2008 13:01:08
         1. A printout of the problem description (short dump)
            To obtain this, select in the current display "System->List->
            Save->Local File (unconverted)".
         2. A suitable printout of the system log
            To obtain this, call the system log through transaction SM21.
            Limit the time interval to 10 minutes before and 5 minutes
            after the short dump. In the display, then select the function
            "System->List->Save->Local File (unconverted)".
         3. If the programs are your own programs or modified SAP programs,
            supply the source code.
            To do this, select the Editor function "Further Utilities->
            Upload/Download->Download".
         4. Details regarding the conditions under which the error occurred
            or which actions and input led to the error.
         Internal call code.........: "[REPO/*/43/LOAD/CX_SY_OPEN_SQL_DB=============CP
         Please check the entries in the system log (Transaction SM21).
         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_REPO_SQL_ERROR" C
         "SAPLRSSM_PROCESS" or "LRSSM_PROCESSF04"
         "CHECK_IF_ANALYZE_IS_NESSESSARY"
    System environment
        SAP Release.............. "640"
        Application server....... "psapdb"
        Network address.......... "158.58.65.11"
        Operating system......... "AIX"
        Release.................. "5.3"
        Hardware type............ "00CD615C4C00"
        Character length......... 16 Bits
        Pointer length........... 64 Bits
        Work process number...... 22
        Short dump setting....... "full"
        Database server.......... "psapdb"
        Database type............ "ORACLE"
        Database name............ "BWP"
        Database owner........... "SAPBWP"
        Character set............ "C"
        SAP kernel............... "640"
        Created on............... "Oct 29 2006 20:49:57"
        Created in............... "AIX 1 5 00538A4A4C00"
        Database version......... "OCI_920 "
        Patch level.............. "155"
        Patch text............... " "
        Supported environment....
        Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
         10.2.0.."
        SAP database version..... "640"
    Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
    Memory usage.............
    Roll..................... 16192
    EM....................... 16759424
    Heap..................... 0
    Page..................... 24576
    MM Used.................. 6604384
    MM Free.................. 1772536
    SAP Release.............. "640"
    User and Transaction
        Client.............. 200
        User................ "R3REMOTE"
        Language key........ "E"
        Transaction......... " "
        Program............. "SAPLRSSM_PROCESS"
        Screen.............. "SAPMSSY0 1000"
        Screen line......... 6
    Information on where terminated
        The termination occurred in the ABAP program "SAPLRSSM_PROCESS" in
         "CHECK_IF_ANALYZE_IS_NESSESSARY".
        The main program was "RSPROCESS ".
        The termination occurred in line 1143 of the source code of the (Include)
         program "LRSSM_PROCESSF04"
        of the source code of program "LRSSM_PROCESSF04" (when calling the editor
         11430).
        The program "SAPLRSSM_PROCESS" was started as a background job.
        Job name........ "BI_PROCESS_ODSACTIVAT"
        Job initiator... "RPRIYANKA"
        Job number...... 02010102
    Also we have a failed job here. Here is the job log.
    Job log overview for job:    BI_PROCESS_ODSACTIVAT / 02010102
    Date       Time     Message text
    08.01.2008 13:01:00 Job started
    08.01.2008 13:01:00 Step 001 started (program RSPROCESS, variant &0000000000188, user ID R3REMOTE)
    08.01.2008 13:01:02 Activation is running: Data target HBCS_O25, from 1,758 to 1,767
    08.01.2008 13:01:02 Data to be activated successfully checked against archiving objects
    08.01.2008 13:01:02 SQL: 01/08/2008 13:01:02 R3REMOTE
    08.01.2008 13:01:02 ANALYZE TABLE "/BIC/AHBCS_O2540" DELETE
    08.01.2008 13:01:02 STATISTICS
    08.01.2008 13:01:02 SQL-END: 01/08/2008 13:01:02 00:00:00
    08.01.2008 13:01:02 SQL: 01/08/2008 13:01:02 R3REMOTE
    08.01.2008 13:01:02 BEGIN DBMS_STATS.GATHER_TABLE_STATS ( OWNNAME =>
    08.01.2008 13:01:02 'SAPBWP', TABNAME => '"/BIC/AHBCS_O2540"',
    08.01.2008 13:01:02 ESTIMATE_PERCENT => 1 , METHOD_OPT => 'FOR ALL
    08.01.2008 13:01:02 INDEXED COLUMNS SIZE 75', DEGREE => 1 ,
    08.01.2008 13:01:02 GRANULARITY => 'ALL', CASCADE => TRUE ); END;
    08.01.2008 13:01:05 SQL-END: 01/08/2008 13:01:05 00:00:03
    08.01.2008 13:01:05     SQL-ERROR: 603 ORA-00603: ORACLE server session terminated by fat al error
    08.01.2008 13:01:05 System error: RSDU_ANALYZE_TABLE_ORA/ ORACLE
    08.01.2008 13:01:08 ABAP/4 processor: DBIF_REPO_SQL_ERROR
    08.01.2008 13:01:08 Job cancelled
    Listener is working fine, Checked the RFC connections, Tried restarting the system, tried adding space to the TEMP tablespace as well as PSAPBWP, but they didn't work.
    Please help.

    The problem got solved as there were DB errors like ORA-01114: IO error writing block to file 256 (block # 126218).
    Here the point to be notes is file 256. The number greater than 255 indicates a temp datafile. This indicates an issue with PSAPTEMP tablespace. When checked on PSAPTEMP tablespace, one of the filesystems where one temp data file sitting was full. The filesystem was 100% full. This will prevent the temp datafile to grow and shrink as and when required.
    So, adding more space to the filesystem solved the problem.
    Thanks to everyone who have shown interest in solving my problem.

  • DBIF_REPO_SQL_ERROR when activating Source System in BI

    Hi,
    Whenever I try to activate a new source system or any other objects it gets terminated.
    It generates a dump DBIF_REPO_SQL_ERROR
    I am on MaxDB and I checked for the free space it is about 45%.
    Following is displayed in SM21 System Log in red:
    Database error -1000 at INS access to table RSOLTPSOUR     
    > POS(1) Too many lock requests                            
    Database error -1000 at OPC access to table REPOLOAD       
    > POS(1) Too many lock requests                            
    Run-time error "DBIF_REPO_SQL_ERROR" occurred              
    > Short dump "070601 212500 firefox_ NSP_00 " generated
    But when I check SM12 then there are no locks displayed. Even i try search with above tables.
    Details of the dump:
    Runtime Errors         DBIF_REPO_SQL_ERROR
    Short text                 SQL error "-1000" occurred when accessing program
    Trigger Location of Runtime Error
                                  Program                       SAPLRSAOSINT                                        
                                  Include                         LRSAOSINTU08                                        
                                  Row                             308                                                                               
    Module type                 (FUNCTION)                                          
                                  Module Name               RSAOSINT_PSEUDO_DVERSION_WRITE                     
    Please advice on how to get rid of this error.
    Thank you,
    sam

    Anil,
    thnx for the note, but i have already followed the steps in it.
    any other workarounds you can suggest, are highly appreciated.
    thank you,
    sam

  • Error DBIF_REPO_SQL_ERROR while execute a query

    Dear gurus,
    i have a problem executing a query.
    the dump
    DBIF_REPO_SQL_ERROR
    SQL error 3114 occurred when accessing program
    The workaround is to delete the index of the cube.
    But when i recreate it, the problems occours again.
    Any suggestions?
    Tks

    Hi,
    Please ensure that you have made the necessary database settings as per SAP Note 1005758 and apply the patches.
    Also, ensure that you have enabled the required parameters as discussed in SAP Note 964858.
    Rgds,
    Colum

  • Runtime error DBIF_REPO_SQL_ERROR in production server

    Hello All,
    I am recieving the following running time error in my Production system. Any help would be really appreciated.
    Runtime Error          DBIF_REPO_SQL_ERROR
           Occurred on     06.09.2009 at   19:16:45
    *SQL error 3114 occurred when accessing program*
    What happened?
    The system is no longer linked to an ORACLE instance.
    No further operations can be performed on the database.
    What can you do?
    You cannot eliminate this error yourself.
    Please inform your database administrator.
    Make a note of the actions and input which caused the error.
    To resolve the problem, contact your
    SAP system administrator.
    With transaction ST22, for dump analysis, you can see and manage
    termination messages and, in particular, save them for longer periods of
    time.
    Make a note of the actions and input which 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.
    Error analysis
    The system attempted to access an ORACLE instance to which it is
    no longer linked.
    This can occur if the ORACLE instance has been stopped due to an
    error or an external operation.
    How to correct the error
    Database error text........: "ORA-03114: not connected to ORACLE"
    Triggering SQL statement...: "CX_SY_OPEN_SQL_DB=============CP "
    The current status of the ORACLE instance cannot be determined.
    It may still be inactive or the database administrator may have
    restarted it.
    In any case, all systems that have accessed the ORACLE instance
    must be restarted after the ORACLE instance has been restarted.
    If you were working on a central system, inform
    your system administrator.
    If you were working on an external local system, inform
    the person responsible for this system.
    If you were working on your own local system, restart
    the system yourself.
    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_REPO_SQL_ERROR" C
    "SAPLSALA" or "LSALAU01"
    "SALA_UPDATE_TRANS_SPEZ_MON"
    If you cannot solve the problem yourself, please send the
    following documents to SAP:
    1. A hard copy print describing the problem.
       To obtain this, select the "Print" function on the current screen.
    2. A suitable hardcopy prinout of the system log.
       To obtain this, call the system log with Transaction SM21
       and select the "Print" function to print out the relevant
       part.
    3. If the programs are your own programs or modified SAP programs,
       supply the source code.
       To do this, you can either use the "PRINT" command in the editor or
       print the programs using the report RSINCL00.
    4. Details regarding the conditions under which the error occurred
       or which actions and input led to the error.
    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_REPO_SQL_ERROR" C
    "SAPLSALA" or "LSALAU01"
    "SALA_UPDATE_TRANS_SPEZ_MON"
    If you cannot solve the problem yourself, please send the
    following documents to SAP:
    1. A hard copy print describing the problem.
       To obtain this, select the "Print" function on the current screen.
    2. A suitable hardcopy prinout of the system log.
       To obtain this, call the system log with Transaction SM21
       and select the "Print" function to print out the relevant
       part.
    3. If the programs are your own programs or modified SAP programs,
       supply the source code.
       To do this, you can either use the "PRINT" command in the editor or
       print the programs using the report RSINCL00.
    4. Details regarding the conditions under which the error occurred
       or which actions and input led to the error.
    Internal call code.........: "[REPO/*/43/LOAD/CX_SY_OPEN_SQL_DB=============CP
    Please check the entries in the system log (Transaction SM21).
    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_REPO_SQL_ERROR" C
    "SAPLSALA" or "LSALAU01"
    "SALA_UPDATE_TRANS_SPEZ_MON"
    If you cannot solve the problem yourself, please send the
    following documents to SAP:
    Already we have checked the SAPnotes 534729, 135942 and 112266 advice to configure all network
    components on the same fixed speed and full-duplex, instead of using the auto-negotiating.
    Please suggest... thanks in advace.
    Regards,
    Suresh
    Edited by: Suresh Kalagarla on Sep 9, 2009 11:27 AM

    I'd say the dump tells you what you need to do:
    > -
    > What happened?
    > -
    >
    > The system is no longer linked to an ORACLE instance.
    > No further operations can be performed on the database.
    >
    > -
    > What can you do?
    > -
    >
    > You cannot eliminate this error yourself.
    > Please inform your database administrator.
    > Make a note of the actions and input which caused the error.
    > -
    >
    > To resolve the problem, contact your
    > SAP system administrator.
    >

  • DBIF_REPO_SQL_ERROR after SGEN: Tablespace is possibly full

    Dear SAP gurus,
    This is an a SAP ERP60 EHP3 system with Oracle we  are in the process of patching it. First, We have download all sw components patches (EHP3 SPS6) we patched java stack and then the sw components -SAP_ABA and SAP_BASIS from SP17 to SP22.
    We ran SGEN for SAP_ABA and SAP_BASIS and it is when the issues start coming out.
    "2.043 generation error(s): Tablespace is possibly full (with load tables)"
    Then we tried to access any SAP Transaction related to ORacle:
    "DBIF_REPO_SQL_ERROR".
    From work process logs:
    C Wed Feb 15 11:02:26 2012
    C OCIStmtExecute() failed with -1=OCI_ERROR
    C SQL error 600:
    C *** ERROR => Error 600 in stmt_execute() from oci_execute_stmt(),
    orpc=119
    [dbsloci.c 12981]
    C *** ERROR => ORA-600 occurred when executing SQL stmt (parse error
    offset=0)
    [dbsloci.c 12983]
    C
    sc_p=0x5901b30,no=182,idc_p=0x5917a88,con=0,astyle='font-family:courier'
    ct=1,slen=67,smax=256,#vars=
    2,stmt=0x5dcaa30,table=D010INC
    C INSERT INTO "D010INC" ( "MASTER" , "INCLUDE" ) VALUES ( :A0 , :A1 );
    C
    sc_p=0x5901b30,no=182,idc_p=0x5917a88,con=0,astyle='font-family:courier'
    ct=1,slen=67,smax=256,#vars=
    2,stmt=0x5dcaa30,table=D010INC
    C Dumping DBSL stmt. cache:
    C prep=0,lit=0,nsql=0,lobret=0,xop=1,dbcnt=119,upsh=
    (nil),stmtp=0x5bcc0f8,rtc=0
    C IN :
    cols=2,rmax=387,xcnt=232,rpc=0,rowi=232,rtot=232,upto=4294967295,rsize=16
    0,vmax=32,bound=1,iobuf_p=0x5a2a7b0,vda_p=0x5db8470
    C lobs=0,lmax=0,lpcnt=0,larr=(nil),lcurr_p=(nil),rret=0
    C INSERT INTO "D010INC" ( "MASTER" , "INCLUDE" ) VALUES ( :A0 , :A1 );
    B ***LOG BYL=> DBQ action required because of database error
    [dbsh#3 @ 1104] [dbsh 1104 ]
    B SQL code: 600, SQL text: ORA-00600: internal error code, arguments:
    [4553], [2], [0], [], [], [], [], []
    B ***LOG BY4=> sql error 600 performing CLC on table D010INC
    [dbrepo#5 @ 6034] [dbrepo 6034 ]
    B ***LOG BY0=> ORA-00600: internal error code, arguments: [4553], [2],
    [0], [], [], [], [], [] [dbrepo#5 @ 6034] [dbrepo 6034 ]
    B DBREPO: new rc return for insert_inc_difference
    A TH VERBOSE LEVEL FULL
    We tried to extend the tablespace PSAPSR700 (which is related to table
    D010INC) but we are still getting dumps like "DBIF_REPO_SQL_ERROR".
    Can you please guide us how to proceed?This query is very urgent since we
    prefer that our developers do not work until we resolve the issue.
    Thanks in advance, Marc

    Thanks for your reply Venky,
    RMAN> connect target /
    connected to target database: SHD (DBID=1683093070)
    using target database control file instead of recovery catalog
    RMAN> backup check logical validate (datafile 2);
    Starting backup at 16-FEB-12
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=193 devtype=DISK
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 02/16/2012 12:22:36
    ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
    alert_SID.log
    Thu Feb 16 09:43:42 2012
    Errors in file /oracle/SHD/saptrace/usertrace/shd_ora_3380.trc:
    ORA-00600: internal error code, arguments: [4553], [2], [0], [], [], [], [], []
    Thu Feb 16 09:43:47 2012
    Doing block recovery for file 2 block 3455
    Block recovery from logseq 19230, block 22155 to scn 1338742588
    Thu Feb 16 09:43:47 2012
    Recovery of Online Redo Log: Thread 1 Group 2 Seq 19230 Reading mem 0
      Mem# 0: /oracle/SHD/origlogB/log_g12m1.dbf
      Mem# 1: /oracle/SHD/mirrlogB/log_g12m2.dbf
    Block recovery completed at rba 19230.22329.16, scn 0.1338742589
    Doing block recovery for file 2 block 297161
    Block recovery from logseq 19230, block 12545 to scn 1338742588
    Thu Feb 16 09:43:47 2012
    Recovery of Online Redo Log: Thread 1 Group 2 Seq 19230 Reading mem 0
      Mem# 0: /oracle/SHD/origlogB/log_g12m1.dbf
      Mem# 1: /oracle/SHD/mirrlogB/log_g12m2.dbf
    Block recovery completed at rba 19230.22329.16, scn 0.1338742589
    Doing block recovery for file 35 block 352889
    Block recovery from logseq 19230, block 22155 to scn 1338742590
    Thu Feb 16 09:43:48 2012
    Recovery of Online Redo Log: Thread 1 Group 2 Seq 19230 Reading mem 0
      Mem# 0: /oracle/SHD/origlogB/log_g12m1.dbf
      Mem# 1: /oracle/SHD/mirrlogB/log_g12m2.dbf
    Block recovery stopped at EOT rba 19230.22329.16
    Block recovery completed at rba 19230.22329.16, scn 0.1338742589
    Thu Feb 16 09:43:49 2012
    Errors in file /oracle/SHD/saptrace/usertrace/shd_ora_30410.trc:
    ORA-00600: internal error code, arguments: [4553], [2], [0], [], [], [], [], []
    Thu Feb 16 09:43:54 2012
    dev_server0
    Wed Feb 15 10:55:06 2012
    A  GENER request remote generation: CL_SRT_WSP_HELPER_METHODS=====CP.
    A
    A Wed Feb 15 10:55:19 2012
    A  GENER request remote generation: RSDSOSCCM.
    A
    A Wed Feb 15 10:55:23 2012
    A  GENER starting inline generation: RSDSOSCCM (reason: compile error during remote generation).
    C
    C Wed Feb 15 10:55:26 2012
    C     OCIStmtExecute() failed with -1=OCI_ERROR
    C     SQL error 600:
    C  *** ERROR => Error 600 in stmt_execute() from oci_execute_stmt(), orpc=9
    [dbsloci.c    12981]
    C  *** ERROR => ORA-600 occurred when executing SQL stmt (parse error offset=0)
    [dbsloci.c    12983]
    C  sc_p=0x58fd3f0,no=62,idc_p=0x5916100,con=0,act=1,slen=67,smax=256,#vars=2,stmt=0x5cecfb0,table=D010INC
    C  INSERT INTO "D010INC" ( "MASTER" , "INCLUDE" ) VALUES ( :A0 , :A1 );
    C  sc_p=0x58fd3f0,no=62,idc_p=0x5916100,con=0,act=1,slen=67,smax=256,#vars=2,stmt=0x5cecfb0,table=D010INC
    C  Dumping DBSL stmt. cache:
    C  prep=0,lit=0,nsql=0,lobret=0,xop=1,dbcnt=9,upsh=(nil),stmtp=0x5cedc58,rtc=0
    C  IN : cols=2,rmax=387,xcnt=9,rpc=0,rowi=9,rtot=9,upto=4294967295,rsize=160,vmax=32,bound=1,iobuf_p=0x5da5400,vda_p=0x5cee310
    C       lobs=0,lmax=0,lpcnt=0,larr=(nil),lcurr_p=(nil),rret=0
    C  INSERT INTO "D010INC" ( "MASTER" , "INCLUDE" ) VALUES ( :A0 , :A1 );
    B  ***LOG BYL=> DBQ action required because of database error            [dbsh#3 @ 1104] [dbsh    1104 ]
    B  SQL code: 600, SQL text: ORA-00600: internal error code, arguments: [4553], [2], [0], [], [], [], [], []
    B  ***LOG BY4=> sql error 600    performing CLC on table D010INC    [dbrepo#5 @ 6034] [dbrepo  6034 ]
    B  ***LOG BY0=> ORA-00600: internal error code, arguments: [4553], [2], [0], [], [], [], [], [] [dbrepo#5 @ 6034] [dbrepo  6034 ]
    B  DBREPO: new rc return for insert_inc_difference
    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_SAVE_SHMLOCKS entered.
    A  ** RABAX: level LEV_RX_SAVE_SHMLOCKS completed.
    A  ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.
    Regards, Marc

  • MS Sql error in production server: DBIF_REPO_SQL_ERROR

    Hi experts,
    I am getting this error in my production server.
    Environment : OS - Windows 2008, Database: MSsql 2005 sp2, ECC6.0
    when the job SAP_COLLECTOR_FOR_PERFMONITOR executes the dump occurs with the following error.
    DBIF_REPO_SQL_ERROR, SQL error 0 occurred when accessing program "CX_SY_OPEN_SQL_DB=============CP "
    and also i am not able to open db13 with ends up with abap dump.
    In the sql server log i found this error too.
    Database ID 5, Page (1:4804273) is marked RestorePending, which may indicate disk corruption. To recover from this state, perform a restore.
    Please help me on this.
    Regards
    Shankar PV

    I raised the Message with SAP and they asked to do the H/W audit. My H/W vendor executed the diagnostic reports and given the report as "NO H/W ISSUE".
    That we already get into know when i did the system refresh, (I Mean i moved the database to another machine there also i am getting those same error).
    As per the DBCC checkdb log we found 1 consistency errors in database 'PRD', and we found that the table too 'DB6PMPROT'.
    Since its the table for the the records of DB13, i can lose this table data. So I tried to delete the data from the table, tried to truncate the table
    and also tried deleting using the commands
    1. DELETE FROM [PRD].[prd].[DB6PMPROT]
    2. TRUNCATE TABLE [PRD].[prd].[DB6PMPROT]
    3. USE [PRD]
    GO
    IF EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID
    (N'[prd].[DB6PMPROT]') AND type in (N'U'))
    DROP TABLE [prd].[DB6PMPROT]
    4. DROP TABLE [PRD].[prd].[DB6PMPROT]
    For all the above mentioned commands the result is below
    Msg 829, Level 21, State 1, Line 3
    Database ID 5, Page (1:4804273) is marked RestorePending, which may
    indicate disk corruption. To recover from this state, perform a restore.
    Since the data in this table is not necessary, we need to drop and
    recreate the table.

  • DBIF_REPO_SQL_ERROR in CRMD_ORDER (CRM 2007) - ORA-03127: no new operations

    Dear Friends,
    I am using CRM 2007. I am facing below run time error: This problem comes frequently....
    Runtime Errors:  DBIF_REPO_SQL_ERROR
    Transaction......... "CRMD_ORDER"
    Program............. "????????????????????????????????????????"
    Screen.............. " "
    Screen Line......... 0
    Short text
        SQL error 3127 occurred when accessing program "SAPMS380 " part "LOAD".
    How to correct the error
        Database error text........: "ORA-03127: no new operations allowed until the
         active operation ends"
        Triggering SQL statement...: "SAPMS380 "
        Internal call code.........: "[REPO/*/43/LOAD/SAPMS380 ]"
        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" " "
        "????????????????????????????????????????" or " "
        If you cannot solve the problem yourself and want to send an error
        notification to SAP, include the following information:
    Internal notes
        The termination was triggered in function "db_info"
        of the SAP kernel, in line 251 of the module
         "//bas/700_REL/src/krn/runt/abload5.c#3".
        The internal operation just processed is " ".
        Internal mode was started at 20100119091358.
        Internal call code.........: "[REPO/*/43/LOAD/SAPMS380 ]"
    I have checked in SAP note also. But, i didnt get....
    Suggest me...
    Note: I dont know, how to create questions for SAP BASIS issue. If any body know, kindly suggest me...
    Thanks & Regards,
    Rajagopal
    Chennai - INDIA

    Looks like something you have to ask one of your SAP Basis administrators at your company (client). Tell them about Oracle db error. They will probably know what to do.
    what do you mean by:
    I dont know, how to create questions for SAP BASIS issue. If any body know, kindly suggest me...
    Just step up to one of them, and show him the error.

  • DBIF_REPO_SQL_ERROR  ABAP Dump

    Hi Experts
    I am getting Following ABAP Dump when i intializing the Planning area  and Displaying CVC's of the MPOS..
    Runtime Errors         DBIF_REPO_SQL_ERROR                   
    Date and Time          12/29/2008 15:46:29                                                                               
    Short text                                                  
         SQL error 3114 occurred when accessing program          
    What happened?                                              
         The system is no longer linked to an ORACLE instance.   
         No further operations can be performed on the database. 
    Plaese Help.
    regards
    kanth

    Hi kanth,
                     APO has Live cache that has to interact with underlying database ( Oracle in your case). The error tells you that that communication is not happening. This is a DB related issue. Let your basis guy know this issue and he should take care of it for you.

  • DBIF_REPO_SQL_ERROR while trying to activate ENVIRONMENTSHELL for BPC 10.0 NW on HANA

    Hi experts,
    I'm getting this short dump "DBIF_REPO_SQL_ERROR" while trying to activate the ENVIRONMENTSHELL(UJS_ACTIVATE_CONTENT) for BPC 10.0 NW on Hana database :
    Category                  Resource Shortage
    Runtime Errors         DBIF_REPO_SQL_ERROR
    Short Text
        SQL error "-10760" while accessing program "CX_SY_OPEN_SQL_DB=============CP" part "LOAD".
    What happened?
        Database error text: "Memory allocation failed."
    Error analysis
        Database error text: Memory allocation failed.
        Triggering SQL statement:  "CX_SY_OPEN_SQL_DB=============CP        "
    System environment
        SAP Release..... 740
        SAP Basis level 0005
        Application server... vSAPPRD
        Network address...... 172.16.10.230
        Operating system... Windows NT
        Release.............. 6.2
        Hardware type....... 4x AMD64 Level
        Character length..... 16 Bits
        Pointer length........ 64 Bits
        Work process number... 9
        Shortdump setting. full
        Database server... hana-prd
        Database type..... HDB
        Database name..... PRD
        Database user ID SAPPRD
       Terminal.......... Maha-HP
        Character set C
        SAP kernel....... 741
        Created on....... Mar 21 2014 17:31:58
        Created at....... NT 6.0 6002 x86 MS VC++ 16.00
        Database version SQLDBC 1.00.60.0379371
        Patch level....... 26
        Patch text.......
        Database............. HDB 1.0
       SAP database version. 741
       Operating system... Windows NT 5.1, Windows NT 5.2, Windows NT 6.0, Windows NT
       6.1, Windows NT 6.2, Windows NT 6.3
       Memory consumption
       Roll.... 0
       EM...... 44600400
       Heap.... 0
       Page.... 49152
       MM used. 33089488
       MM free. 4949248
    The program interrupted was SAPLSADB
    Thanks
    Maha

    Hi Maha,
    Please check the versions of:
    HANA server
    HANA client (on HANA server)
    HANA client (on the PAS)
    SAP Kernel (both the generic and HDB specific files)
    The versions between them should be in sync.
    My issue with the error: " CX_SY_OPEN_SQL_DB=============CP        " is resolved by applying the latest SAP Kernel 7.41 Patches which is currently patch level 43.
    Good luck!
    Regards,
    Mike

  • Runtime errors  DBIF_REPO_SQL_ERROR

    Hi All ,
    When i am creating source system selected Replicate as well opition ,its giving runtime error
    "DBIF_REPO_SQL_ERROR".
    Short Text :SQL error "-1000" occured when accessing the program

    Dear Venkat,
    When we were gettting an error like DBIF_REPO_SQL_ERROR it was mostly related to the Table Space issue. Hope this helps.
    Regards
    Vijay

  • 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

  • DBIF_REPO_SQL_ERROR with archive write program FI_DOCUMNT_WRI

    Hello community,
    we have a problem with the archive write program FI_DOCUMNT_WRI, it generates DBIF_REPO_SQL_ERROR on the table REPOSRC. We get a lot of dumps DBIF_REPO_SQL_ERROR, SQL-Error -913, ERROR: UNSUCCESSFUL EXECUTION CAUSED BY DEADLOCK OR TIMEOUT. The dumps shows the error in FORM badi_write resp. get %_badi-implementations proxy of the method get_instance.  We use the FI_DOCUMNT_WRI program in 50 times parallel mode. The syslog shows error at select access on report source table REPOSRC in the kernel object package SBAC. The statement cache shows only valid SQL statements. Our database expert means these are timeout errors and the reason is the high number of the parallelism. The database is DB2 9.1.5 with SAP ECC 6.0. Does somebody knows this problem or in a similar way?
    Thanks for tips and hints.
    Cheers
    Stefan
    Edited by: Stefan Schnell on Sep 14, 2010 4:19 PM

    Hello community,
    after running RUNSTATS the problem exists no longer.
    Thanks and cheers
    Stefan

  • DBIF_REPO_SQL_ERROR dump while executing the queries

    Hi Friends,
    Iam in a big mess . I have one query based on one my Zinfocube.This query ia attached in the workbook .. Previuolsy all was fine , but now whever iam executing this query it is throwing me the exception
    Query 0: Runtime error SQL error 3114 occurred when accessing program CX_ with parallel processing via RFC.
    When I checked in ST22 i got the following dump,
    DBIF_REPO_SQL_ERROR
    Short text
        SQL error 3114 occurred when accessing program
    What happened?
        The system is no longer linked to an ORACLE instance.
        No further operations can be performed on the database.
    What can you do?
        You cannot eliminate this error yourself.
        Please inform your database administrator.
        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.
        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.
    Error analysis
        The system attempted to access an ORACLE instance to which
        it is no longer linked.
        This situation may arise because the ORACLE instance
        has been stopped due to an error or an external operation.
    How to correct the error
        Database error text........: "ORA-03114: not connected to ORACLE"
        Triggering SQL statement...: "CX_SQL_EXCEPTION==============CP "
        The current status of the ORACLE instance cannot be determined.
        It may be still inactive or the database administrator may have
        restarted it.
        In any case, all systems that have accessed the ORACLE instance
        must be restarted after the ORACLE instance has been restarted.
        If you were working on a central system, inform
        your system administrator.
        If you were working on an external local system, inform
        the person responsible for this system.
        If you were working on your own local system, restart
        the system yourself.
        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" " "
        "CL_SQL_RESULT_SET=============CP" or "CL_SQL_RESULT_SET=============CM006"
        "NEXT_PACKAGE"
        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.
    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" " "
    "CL_SQL_RESULT_SET=============CP" or "CL_SQL_RESULT_SET=============CM006"
    "NEXT_PACKAGE"
    My Basis guy is saying that he has checked the data base parameters , and all are fine.
    Thanks in advance.

    Hi Akash,
    First check if the system is up and running by logging on the sys through SAP Logon.
    Check with the BASIS is all servers r running.
    if the sys is up ,the go to the query definition,and run the check on that and see if there is any error in the query definition.
    Let us knwo ur observations..
    Regards,
    Dhanya.

Maybe you are looking for

  • Will I ever be able to download again???

    I haven't been able to download for a month. I get several downloading problem messages.... network connection was terminated unexpectedly, network connection timed-out, network connection was reset, network connection could not be made are the messa

  • RFC problem: could not get functionname from XML requst (sic)

    I'm developing an interface that attempts to call a receiver RFC on an SAP 4.6c system.  It's a very small simple interface, and it's all working until it tries to call the RFC.  The error is Exception caught by adapter framework: error while process

  • Canon 7D support, when?

    When can we expect a release for the full support of the Canon 7D RAW files? As a software developer I don't understand why Adobe doesn't work with Canon/Nikon/Sony etc to support any new camera before it gets released? Thank you,

  • HGrid and view link ancestors /get lines selected

    Hello, I want to get selected the lines out of a HGrid component which uses Viewlinks in IExpense. I extended the Controller of the HGrid <b> AllocationsHGridCO </b>. The except of the HGrid RN structure as follows: <oa:tree usage="hGrid" id="HeaderN

  • Login problem for sqlplus 9i

    Hi All, My Oracle is 9i. How can I login as sys directly using sqlplus. I have tried the following command : "sqlplus sys/change_on_install@DB01 as sysdba" many thanks.