Oracle Idle Time errors

Any suggestions on how I can avoid "ORA-02396: exceeded maximum idle time, please connect again" errors?
Getting rid of the idle time restriction on the database is not an option, so I was looking for a parameter to tweak so Pages recovers better from Oracle idle timeouts.
What's happening are javascript errors and other errors in the logs when there is a timeout.

You may have issues that are not linked to timeout. Please check your database instance alert log:
$ oerr ora 3113
03113, 00000, "end-of-file on communication channel"
// *Cause: The connection between Client and Server process was broken.
// *Action: There was a communication error that requires further investigation.
//          First, check for network problems and review the SQL*Net setup.
//          Also, look in the alert.log file for any errors. Finally, test to
//          see whether the server process is dead and whether a trace file
//          was generated at failure time.

Similar Messages

  • Oracle idle time

    Hi all,
    In one of our test database(11.2.0.1.0),we want to disable idle time out for developers.
    There resource_limit=true and default profile has been assigned to all users,where idle time is unlimited.
    Also SQLNET.EXPIRE_TIME=0.
    But still the session gets ORA-03113 error, if the session has been idle for long time.
    We want the session not to be disconnected.
    By default,is Oracle following any idle time out limits.
    Need your help

    You may have issues that are not linked to timeout. Please check your database instance alert log:
    $ oerr ora 3113
    03113, 00000, "end-of-file on communication channel"
    // *Cause: The connection between Client and Server process was broken.
    // *Action: There was a communication error that requires further investigation.
    //          First, check for network problems and review the SQL*Net setup.
    //          Also, look in the alert.log file for any errors. Finally, test to
    //          see whether the server process is dead and whether a trace file
    //          was generated at failure time.

  • 0% idle time of cpu states from top command in oracle 8i /solaris 5.9

    Hi,
    for long time idle time is 0% in top command :
    database version:oracle 8.1.7.4.0
    operating system : sun solaris 5.9
    load averages: 9.32, 5.78, 6.13 15:22:13
    404 processes: 387 sleeping, 13 running, 4 on cpu
    CPU states: 0.0% idle, 78.2% user, 21.8% kernel, 0.0% iowait, 0.0% swap
    Memory: 16G real, 7535M free, 5842M swap in use, 9965M swap free
    PID USERNAME THR PRI NICE SIZE RES STATE TIME CPU COMMAND
    6928 oracle 11 20 0 0K 0K run 2:20 12.62% oracle
    23518 oracle 21 31 0 0K 0K run 24:37 11.69% oracle
    9664 oracle 20 30 0 0K 0K run 12:41 10.83% oracle
    15764 oracle 12 21 0 0K 0K run 2:18 10.28% oracle
    9214 oracle 19 21 0 0K 0K run 5:52 8.58% oracle
    13734 oracle 173 21 0 0K 0K cpu/3 311:23 6.11% oracle
    19271 oracle 1 59 0 0K 0K cpu/0 726:20 4.45% oracle
    10436 oracle 1 59 0 0K 0K sleep 81:41 4.39% oracle
    22400 oracle 11 59 0 0K 0K sleep 3:22 4.35% oracle
    9297 oracle 20 59 0 0K 0K cpu/2 7:39 3.66% oracle
    22175 oracle 19 59 0 0K 0K sleep 6:55 3.41% oracle
    9494 oracle 1 30 0 0K 0K run 0:02 2.99% oracle
    10719 oracle 1 59 0 0K 0K sleep 132:48 1.55% oracle
    210 oracle 1 59 0 0K 0K sleep 86:56 1.04% oracle
    22084 oracle 24 59 0 0K 0K sleep 2:50 0.92% oracle
    and sometime load average goes to 25-30 and cpu states is 0% idle in that load so how i can tune my database:
    Regards
    Prakash

    Hi,
    here 0% idle, 0% iowait
    one of the query explain plan i am posting over here:
    Operation     Object Name     Rows     Bytes     Cost     TQ     In/Out     PStart     PStop
    SELECT STATEMENT Hint=CHOOSE          77 K          11800                     
    COUNT STOPKEY                                        
    VIEW          77 K     32 M     11800                     
    SORT UNIQUE STOPKEY          77 K     10 M     8384                     
    HASH JOIN OUTER          77 K     10 M     4968                     
    HASH JOIN          77 K     9 M     4477                     
    HASH JOIN          54 K     2 M     3071                     
    TABLE ACCESS FULL     GA_INSTANCE     10      140      1                     
    HASH JOIN          75 K     2 M     3069                     
    HASH JOIN          75 K     1 M     2351                     
    INDEX FAST FULL SCAN     CUST_ACCT_ADDR_PK     75 K     960 K     282                     
    TABLE ACCESS FULL     ADDRESS     199 K     1 M     1960                     
    TABLE ACCESS FULL     CUST_ACCT     112 K     1 M     593                     
    TABLE ACCESS FULL     IQARA_CNR_ACT_LOG     89 K     6 M     1150                     
    TABLE ACCESS FULL     NI_STATIC_IP_ADDR     21 K     317 K     60                     
    Reagrds
    Prakash

  • ORACLE Forms Run Time error FRM -92050 failed to connect to server

    server name:
    osfsun.oklaXXX:9000
    Details:
    Java Exception
    Java.netNoRouteToHostException: operation timed out
    at java.net.plainsocketImpl.doConnect(Compiled Code)
    at java.net.plainsocketImpl.connectToAddress(plainsocketImpl:124)
    There is more....
    I have opened the port 9000 in my LAN firewall, I have checked Jinitiator control panel, I'm able to resolve web address but receive this web run time error,.anyhelp would be appreaciated.
    thanks

    I resolved this issue. It was related to the firewall using port 9000/ The issue was not related to Oracle.

  • Jdbc with oracle ....run time error!

    I'm trying to connect to Oracle using jdbc.
    this is the simple code for my program, I'm getting run time error...."memory could not be read"
    import java.sql.*;
    class MyCon{
    public static final String JDBC_URL = new String("jdbc:oracle:oci8:@BhDb1onlocalhost");
    public static final String USERNAME = new String("scott");
    public static final String PASSWORD = new String("tiger");
    public static void main(String args[])
    try {
         MyCon myob = new MyCon();
         DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
         Connection con = DriverManager.getConnection(JDBC_URL, USERNAME, PASSWORD);
         Statement stm = con.createStatement();
         ResultSet rs = stm.executeQuery("Select * from Providers");
         ResultSetMetaData rsmd = rs.getMetaData();
         while(rs.next()) {
         for(int count=1;count<=rsmd.getColumnCount();count++) {
              System.out.println(rs.getString(count));
    } catch(Exception e) {
         System.out.println("caught:"+e);
    I'm using windowsNT 4.0
    jdk1.2.2
    oracle 8.1.5
    classess111.zip is in my classpath
    thanx in advance.

    <<jdbc:oracle:oci8:@BhDb1onlocalhost>>
    I haven't ever used the oci8 driver, but you could use the thin driver as follows:
    jdbc:oracle:thin:@localhost:1521:BhDb1
    The thin driver is more portable since it doesn't require the NetClient to be installed.
    Hope this helps.

  • Idle time for Oracle user

    Hi,
    we have PS FSCM9 with Oracle DB 10g R2. For the moment idle time for Default profile of Oracle users in DB is UNLIMITED. I wonder if I change it to 90 Minutes (in order to have less memory usage for idle sessions) there would be a probleme for PeopleSoft ERP ?
    Thanks before.

    It could be an issue since Peoplesoft is working through Application server and connection pool. It could stopped (or killed) application server connection client, which you would avoid to be able to reconnect later on with other front end user.
    Nicolas.

  • Oracle 10.2 Predictive Analytics Spreadsheet Add-In - Run-time error 429

    Hi,
    I installed the "Oracle 10.2 Predictive Analytics Spreadsheet Add-In" for Excel. When I'm running Excel, and I click the OraclePA menu option "connect", I get the error:
    Run-time error 429:
    ActiveX component can't create object
    I am running Win-2000, and I have the 10.2.0.1.0 (with Data Mining Options) DB installed locally.
    Any ideas on how to resolve this error?
    Thanks.

    Hello,
    this is the typical error seen when trying to activate a program after installing it without restarting your computer first.
    you it tried to restart your computer ????
    What is version of the excel ?

  • Authorization error in Repository after idle time

    Hi all,
    I have a problem in ESR where after some idle time I suddenly loose all my authorizations to perform any actions in Repository (sometimes also Directory). I'm even denied the authorization to close objects or the entire ESR altogether.
    This happens after I have worked on an object, then leave it for some time (I have yet to find out the exact time). Then when I try to continue working on the object, a window pops up saying "User has no authorization".
    Note that I have all necessary roles, and I can perform all the actions when I force-shut the ESR (by killing the ESR-process on OS-level) and log on again. However the objects are locked and I need to remove the lock from the Integration Builder Administration page in order to change the object. This is very annoying!
    I have checked the Default Trace when this happens and found that the userID with which I am logged on has for some reason changed to J2EE_GUEST! I am guessing this is the reason I am not allowed to work on the object anymore, as J2EE_GUEST does not have the appropriate authorizations.
    The Default Trace shows the following (my real user ID is in this system ERIKEN):
    System exception 
    [EXCEPTION]
    javax.ejb.EJBAccessException: Principal: Message buffer:
    No messages available.
    Transient data:
    com.sap.security.core.persistence.imp.PrincipalDatabag Thu Feb 23 16:34:09 CET 2012
    UniqueID: USER.R3_DATASOURCE.J2EE_GUEST
    Type: USER
    Home data source: R3_DATASOURCE
    Private id part: J2EE_GUEST
    Existence not checked.
    "com.sap.security.core.usermanagement"|->"j_authscheme" (no time limit)="anonymous"
    Persistent data:
    com.sap.security.core.persistence.imp.PrincipalDatabag Thu Feb 23 16:34:09 CET 2012
    UniqueID: USER.R3_DATASOURCE.J2EE_GUEST
    Type: USER
    Home data source: R3_DATASOURCE
    Private id part: J2EE_GUEST
    Principal exists.
    Direct parents:
    GRUP: GRUP.R3_ROLE_DS.SAP_J2EE_GUEST
          GRUP.SUPER_GROUPS_DATASOURCE.EVERYONE
          GRUP.SUPER_GROUPS_DATASOURCE.Anonymous Users
    ROLE:
    Why does this happen?
    More importantly, how can I fix it?
    This happens in different systems, on different releases, but this particular system is PI 7.11 - SP08. Java version is 1.6.0_29.
    Appreciate any hints!
    Regards,
    Kenneth

    Dear Kenneth
    Solution in this note: 1622692 - PI ESR: No authorization for this action
    Please check
    Regards
    Sourabh

  • How to track clients idle time and force to Login View

    How can I force clients to the Login View after a period of idle time ( 1 hour). My mobile application consist of many views and need  the time out to work from any view. Your assistance is appreciated.Using Flash Builder 4.5 and AS 3.0.
    I was able to make it work using FlexEvent.Idle to determine the inactivity. But it only works when I am on the second view, if I go deeper (third view) it fails. Here is the code I am using and the error I get
    protected function view1_creationCompleteHandler(event:FlexEvent):void
         this.systemManager.addEventListener(FlexEvent.IDLE, userIdle);
    private function userIdle(e:FlexEvent):void
       if(e.currentTarget.mx_internal::idleCounter == 200)
        //do something!
        navigator.popToFirstView();
    ERROR MESSAGE
    ++++++++++++++++++++++++
    TypeError: Error #1009: Cannot access a property or method of a null object reference.
    at views::MainMenu/userIdle()[C:\Documents and Settings\spences\Adobe Flash Builder 4.5\EmployeeLogin\src\views\MainMenu.mxml:89]
    at flash.events::EventDispatcher/dispatchEventFunction()
    at flash.events::EventDispatcher/dispatchEvent()
    at mx.managers::SystemManager/idleTimer_timerHandler()[E:\dev\4.5.1\frameworks\projects\fram ework\src\mx\managers\SystemManager.as:3292]
    at flash.utils::Timer/_timerDispatch()
    at flash.utils::Timer/tick()
    Message was edited by: Stewart TVDSB

    Hi Nadeem,
    You can find the max session idle time in table APEX_040000.WWV_FLOWS, attribute MAX_SESSION_IDLE_SEC .
    brgds,
    Peter
    Blog: http://www.oracle-and-apex.com
    ApexLib: http://apexlib.oracleapex.info
    BuilderPlugin: http://builderplugin.oracleapex.info
    Work: http://www.click-click.at

  • Jdbc connection lost after idle time

    Dear users,
    i'm using the oracle 10g database. Now i found out that several programs (SQuirreL, QuantumDB,...) which use the ojdbc14 driver are losing connection to the database after about one hour idle time, but it is not set in db configuration to disconnect (eg parameter idle_time is not set). What could be the cause of this? Is this a error of jdbc (the java exception is something like socket lost) or is it a missconfiguration of the db?
    Thx for help.

    With a simple java program that makes a select on a database table over jdbc after one Hour idle_time this exception happens: (the program is started local on the database server so no firewall or router is between)
    java.sql.SQLException: No more data to read from socket
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:208)
    at oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1118)
    at oracle.jdbc.driver.T4CMAREngine.unmarshalSB1(T4CMAREngine.java:1070)
    at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:478)
    at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:207)
    at oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:790)
    at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1039)
    at oracle.jdbc.driver.T4CStatement.executeMaybeDescribe(T4CStatement.java:830)
    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1132)
    at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1272)
    at test$1.run(test.java:24)
    at test.main(test.java:55)

  • Run time error

    Dear All,
    During the transaction /n/sapapo/ccr (Reconsilation of transaction data) in client SCP 950, system displays the run time error which are attached herewith.
    This is the activity a used to execute regularly (Daily) and first time i recieved this message - -
    Runtime Errors         ASSERTION_FAILED                                                            
    Date and Time          13.07.2007 10:13:37                                                         
    ShrtText                                                                               
    The ASSERT condition has been violated.                                                       
    What happened?                                                                               
    In the current application program, the system recognized a situation                         
        involving the ASSERT statement that should not occur. A runtime error                         
        occurred, either because there was no activation ID entered or because                        
        the ID of the activation mode used was set to "Cancel.                                        
    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                                                                               
    The following activation ID was used: "No checkpoint group specified"                                                                               
    If the FIELDS addition was used with this ASSERT statement, the content                       
        of the first 8 fields is as follows:                                                          
        " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    How to correct the error                                                                               
    Probably the only way to eliminate the error is to correct the program.                                                                               
    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:                                                                               
    "ASSERTION_FAILED" C                                                                               
    "/SAPAPO/SAPLTIMESTAMP" or "/SAPAPO/LTIMESTAMPU08"                                            
        "/SAPAPO/TIMESTAMP_DIFFERENCE"                                                                
        If you cannot solve the problem yourself and you wish to send                                 
        an error message to SAP, include the following documents:                                                                               
    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.                                               
    System environment                                                                               
    SAP Release.............. "640"                                                                               
    Application server....... "scmprd"                                                            
        Network address.......... "172.16.10.47"                                                      
        Operating system......... "AIX"                                                               
        Release.................. "5.3"                                                               
        Hardware type............ "0002BFAAD700"                                                      
        Character length......... 16 Bits                                                             
        Pointer length........... 64 Bits                                                             
        Work process number...... 0                                                                   
        Short dump setting....... "full"                                                                               
    Database server.......... "scmprd"                                                            
        Database type............ "ORACLE"                                                            
        Database name............ "SCP"                                                               
        Database owner........... "SAPSCP"                                                                               
    Character set............ "C"                                                                               
    SAP kernel............... "640"                                                               
        Created on............... "Jan 18 2006 20:47:39"                                              
        Created in............... "AIX 1 5 00538A4A4C00"                                              
        Database version......... "OCI_920 "                                                                               
    Patch level.............. "109"                                                               
        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....................... 196923232                                                           
        Heap..................... 0                                                                   
        Page..................... 98304                                                               
        MM Used.................. 186636840                                                           
        MM Free.................. 1895288                                                             
        SAP Release.............. "640"                                                                               
    User and Transaction                                                                               
    Client.............. 950                                                                      
        User................ "SCMATP"                                                                 
        Language key........ "E"                                                                      
        Transaction......... "/SAPAPO/CCR "                                                           
        Program............. "/SAPAPO/SAPLTIMESTAMP"                                                  
        Screen.............. "SAPMSSY0 1000"                                                          
        Screen line......... 6                                                                        
    Information on where terminated                                                                   
        The termination occurred in the ABAP program "/SAPAPO/SAPLTIMESTAMP" in                       
         "/SAPAPO/TIMESTAMP_DIFFERENCE".                                                              
        The main program was "/SAPAPO/CIF_DELTAREPORT3 ".                                                                               
    The termination occurred in line 61 of the source code of the (Include)                       
         program "/SAPAPO/LTIMESTAMPU08"                                                              
        of the source code of program "/SAPAPO/LTIMESTAMPU08" (when calling the editor                
         610).                                                                               
    Source Code Extract                                                                               
    Line  SourceCde                                                                               
    31     lv_time_int_low      TYPE i,                                                            
       32     lv_timediff_int      TYPE i,                                                            
       33     lv_datediff_int      TYPE i,                                                            
       34     lv_time              TYPE t,                                                            
       35     ls_time              TYPE tstr_timestr.                                                 
       36                                                                               
    37 * check timestamp parameter                                                                 
       38 * ASSERT NOT iv_timestamp_high IS INITIAL.                                                  
       39 * ASSERT NOT iv_timestamp_low  IS INITIAL.                                                  
       40 * ASSERT iv_timestamp_low <= iv_timestamp_high.                                             
       41   IF iv_timestamp_high IS INITIAL                                                           
       42   OR iv_timestamp_low  IS INITIAL.                                                          
       43     RAISE invalid_parameter.                                                                
       44   ENDIF.                                                                               
    45   IF iv_timestamp_high < iv_timestamp_low.                                                  
       46     RAISE invalid_parameter.                                                                
       47   ENDIF.                                                                               
    48                                                                               
    49 * prepare timestamps                                                                        
       50 * .. split into date and time integers                                                      
       51   ls_timestamp_high = iv_timestamp_high.                                                    
       52   lv_date_int_high  = ls_timestamp_high-date.                                               
       53   lv_time_int_high  = ls_timestamp_high-time.                                               
       54   ls_timestamp_low  = iv_timestamp_low.                                                     
       55   lv_date_int_low   = ls_timestamp_low-date.                                                
       56   lv_time_int_low   = ls_timestamp_low-time.                                                
       57                                                                               
    58 * .. calc date diff                                                                         
       59 * .. check against max. allowed integer difference                                          
       60   lv_datediff_int = lv_date_int_high - lv_date_int_low.                                     
    >>>>>   ASSERT lv_datediff_int <= lc_datediff_intmax.                                             
       62                                                                               
    63 * calc time diff                                                                               
    64   lv_timediff_int = lv_time_int_high - lv_time_int_low.                                     
       65   IF lv_timediff_int < 0.                                                                   
       66     ADD 86400 TO lv_timediff_int.                                                           
       67     SUBTRACT 1 FROM lv_datediff_int.                                                        
       68   ENDIF.                                                                               
    69                                                                               
    70 * calc total duration                                                                       
       71   lv_duration_int = lv_datediff_int * 86400 + lv_timediff_int.                              
       72   lv_time = lv_timediff_int.                                                                
       73   ls_time = lv_time.                                                                        
       74   ls_duration-hours   = lv_duration_int DIV 3600.                                           
       75   ls_duration-minutes = ls_time-minute.                                                     
       76   ls_duration-seconds = ls_time-second.                                                     
       77                                                                               
    78   ev_duration_packed  = ls_duration.                                                        
       79   ev_duration_integer = lv_duration_int.                                                    
       80 ENDFUNCTION.                                                                               
    Contents of system fields                                                                         
    Name     Val.                                                                               
    SY-SUBRC 0                                                                               
    SY-INDEX 0                                                                               
    SY-TABIX 1                                                                               
    SY-DBCNT 1                                                                               
    SY-FDPOS 6                                                                               
    SY-LSIND 0                                                                               
    SY-PAGNO 0                                                                               
    SY-LINNO 1                                                                               
    SY-COLNO 1                                                                               
    SY-PFKEY                                                                               
    SY-UCOMM                                                                               
    SY-TITLE CIF - Comparison/Reconciliation of Transaction Data                                      
    SY-MSGTY                                                                               
    SY-MSGID                                                                               
    SY-MSGNO 000                                                                               
    SY-MSGV1                                                                               
    SY-MSGV2                                                                               
    SY-MSGV3                                                                               
    SY-MSGV4                                                                               
    Active Calls/Events                                                                               
    No.   Ty.          Program                             Include                             Line   
          Name                                                                               
    5 FUNCTION     /SAPAPO/SAPLTIMESTAMP               /SAPAPO/LTIMESTAMPU08                  61  
          /SAPAPO/TIMESTAMP_DIFFERENCE                                                                
        4 FORM         /SAPAPO/SAPLCIF_DELTA3              /SAPAPO/LCIF_DELTA3F17                349  
          COMPARE_ORDER_HEADER                                                                        
        3 FUNCTION     /SAPAPO/SAPLCIF_DELTA3              /SAPAPO/LCIF_DELTA3U03                125  
          /SAPAPO/CIF_DELTA3_COMP_ORDER                                                               
        2 FUNCTION     /SAPAPO/SAPLCIF_DELTA3              /SAPAPO/LCIF_DELTA3U01                871  
          /SAPAPO/CIF_DELTA3_COMP                                                                     
        1 EVENT        /SAPAPO/CIF_DELTAREPORT3            /SAPAPO/CIF_DELTAREPORT3              189  
          START-OF-SELECTION                                                                          
    Chosen variables                                                                               
    Name                                                                               
    Val.                                                                               
    No.       5 Ty.          FUNCTION                                                                 
    Name  /SAPAPO/TIMESTAMP_DIFFERENCE                                                                
    IV_TIMESTAMP_HIGH                                                                               
    #q1###                                                                               
    02073899                                                                               
    2001125C                                                                               
    IV_TIMESTAMP_LOW                                                                               
    ##q!####                                                                               
    00720899                                                                               
    2011125C                                                                               
    EV_DURATION_INTEGER                                                                               
    0                                                                               
    0000                                                                               
    0000                                                                               
    EV_DURATION_PACKED                                                                               
    000000                                                                               
    00000C                                                                               
    SYST-REPID                                                                               
    /SAPAPO/SAPLTIMESTAMP                                                                         
        0000000000000000000000000000000000000000                                                      
        0000000000000000000000000000000000000000                                                      
        2545454254545444554452222222222222222222                                                      
        F31010FF310C49D5341D00000000000000000000                                                      
    %_SPACE                                                                               
    0                                                                               
    0                                                                               
    2                                                                               
    0                                                                               
    LS_TIMESTAMP_HIGH                                                                               
    22000713182959                                                                               
    00000000000000                                                                               
    00000000000000                                                                               
    33333333333333                                                                               
    22000713182959                                                                               
    LV_DATE_INT_HIGH                                                                               
    803363                                                                               
    0042                                                                               
    0C23                                                                               
    LS_TIMESTAMP_HIGH-DATE                                                                               
    22000713                                                                               
    00000000                                                                               
    00000000                                                                               
    33333333                                                                               
    22000713                                                                               
    LV_TIME_INT_HIGH                                                                               
    66599                                                                               
    0002                                                                               
    0147                                                                               
    LS_TIMESTAMP_HIGH-TIME                                                                               
    182959                                                                               
    000000                                                                               
    000000                                                                               
    333333                                                                               
    182959                                                                               
    LS_TIMESTAMP_LOW                                                                               
    20071210182959                                                                               
    00000000000000                                                                               
    00000000000000                                                                               
    33333333333333                                                                               
    20071210182959                                                                               
    LV_DATE_INT_LOW                                                                               
    733021                                                                               
    0025                                                                               
    0BFD                                                                               
    LS_TIMESTAMP_LOW-DATE                                                                               
    20071210                                                                               
    00000000                                                                               
    00000000                                                                               
    33333333                                                                               
    20071210                                                                               
    LV_TIME_INT_LOW                                                                               
    66599                                                                               
    0002                                                                               
    0147                                                                               
    LS_TIMESTAMP_LOW-TIME                                                                               
    182959                                                                               
    000000                                                                               
    000000                                                                               
    333333                                                                               
    182959                                                                               
    SY-UNAME                                                                               
    SCMATP                                                                               
    000000000000                                                                               
    000000000000                                                                               
    544455222222                                                                               
    33D140000000                                                                               
    SCREEN-INPUT                                                                               
    1                                                                               
    0                                                                               
    0                                                                               
    3                                                                               
    1                                                                               
    LV_DATEDIFF_INT                                                                               
    70342                                                                               
    001C                                                                               
    0126                                                                               
    LV_TIMEDIFF_INT                                                                               
    0                                                                               
    0000                                                                               
    0000                                                                               
    SYST                                                                               
    #######################################&#332;###############################################&#19800; C#&#1280;##
        0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
        000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000500
        0000000000000000000000000000000800000004000000000000000000000000000000000000010900000005240000
        0000010200000000000001060100010C0000000C0000000002000000000000000000000000000B000001000803000C
    SY-REPID                                                                               
    /SAPAPO/SAPLTIMESTAMP                                                                         
        0000000000000000000000000000000000000000                                                      
        0000000000000000000000000000000000000000                                                      
        2545454254545444554452222222222222222222                                                      
        F31010FF310C49D5341D00000000000000000000                                                      
    %_DUMMY$$                                                                               
    0000                                                                               
    0000                                                                               
    2222                                                                               
    0000                                                                               
    No.       4 Ty.          FORM                                                                     
    Name  COMPARE_ORDER_HEADER                                                                        
    SYST-REPID                                                                               
    /SAPAPO/SAPLCIF_DELTA3                                                                        
        0000000000000000000000000000000000000000                                                      
        0000000000000000000000000000000000000000                                                      
        2545454254544445444543222222222222222222                                                      
        F31010FF310C396F45C413000000000000000000                                                      
    GC_APPEND_MODE                                                                               
    3                                                                               
    0                                                                               
    0                                                                               
    3                                                                               
    3                                                                               
    LS_FIELDS_TO_COMPARE-DUEDATE                                                                      
        X                                                                               
    0                                                                               
    0                                                                               
    5                                                                               
    8                                                                               
    SYST                                                                               
    #######################################&#332;###############################################&#19800; C#&#1280;##
        0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
        000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000500
        0000000000000000000000000000000800000004000000000000000000000000000000000000010900000005240000
        0000010200000000000001060100010C0000000C0000000002000000000000000000000000000B000001000803000C
    LS_APO_ORDER-ORDTYPE                                                                               
    5                                                                               
    0                                                                               
    0                                                                               
    3                                                                               
    5                                                                               
    GC_PLANNED_ORDER                                                                               
    5                                                                               
    0                                                                               
    0                                                                               
    3                                                                               
    5                                                                               
    LS_R3_ORDER-STATUSCNF                                                                               
    0                                                                               
    0                                                                               
    2                                                                               
    0                                                                               
    GC_ORDER_STATUS_NO_CONF                                                                               
    1                                                                               
    0                                                                               
    0                                                                               
    3                                                                               
    1                                                                               
    LS_APO_ORDER-STATUSCNF                                                                               
    0                                                                               
    0                                                                               
    2                                                                               
    0                                                                               
    GC_PRED_OUT_DEL                                                                               
    A                                                                               
    0                                                                               
    0                                                                               
    4                                                                               
    1                                                                               
    GC_TND_DELETE                                                                               
    CN                                                                               
    00                                                                               
    00                                                                               
    44                                                                               
    3E                                                

    Dear Sajit,
    Go through the following OSS Notes:
    <a href="https://websmp110.sap-ag.de/form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=901957&_NLANG=E">901957</a>, <a href="https://websmp110.sap-ag.de/form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1036880&_NLANG=E">1036880</a>, <a href="https://websmp110.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1067414&_NLANG=E">1067414</a>
    Regards,
    Naveen.

  • Crystal report not shown after application idle time

    i have a web page which uses around 10 session variables to store values on a button click.and after assign session values Response.Redirect("~/url",false); to a a page which contains crystal report viewer.and report should show those session values.after keeping the application idle for 45 mins i click on the button which assign session values.then it's redirecting to the report page but the report is not shown.it shows a empty page and no errors shown(only happens application is idle for nearly 45 mins other wise works fine)
    i'm using iis 7
    in the web.config i have set sessionState timeout="60" and application pool idle time out to 60 mins.
    any idea why this happens

    Make sure you are on SP 8
    Make sure you are using .Close and .Dispose on your report objects as you get done with them.
    What OS? (2003, 2008, 2012)
    Provide more info on the following:
    The problem is that the Crystal Report Viewer does not load after a few hours.
    What does that mean? Errors? Warnings? Behavior? Symptoms?
    - Ludek
    Senior Support Engineer AGS Product Support, Global Support Center Canada
    Follow us on Twitter

  • Xml Publisher  run time error '5148'

    Dear
    I am using XML publisher to convert data in excel from the oracle,so first i have generated data in xml by report builder and open xml file in Word document through >template builder >data > load xml data,it's find but i use insert menu and select all field then it give message which i have mentioned below,
    run time error '5148'
    The number must be between 1 to 63
    I think, is it column limitation because i have done this activity later but right now i have added more column so may be that's why it is showing the error but my client need to show data in excel,so how i can fulfill this requirement,is there any other solution ?
    Please help on this regard. thanks in advance.

    Just for future poor souls who may be pulling their hair out over the same issue, I eventually got to the bottom of this cryptic error message.
    Do not try to import all your fields at once if your group has over 63 of them, as it will fail.
    If you use the Insert Table option, and try to put all the fields in at once, it will give you a more meaningful message, and the one it SHOULD have given you in the first place, which is "A table cannot contain more than 63 columns".
    So - Import them, a few at a time. Then move them all into one group and you're good to go.

  • While doing SO, im getting run time error - reg;

    Hi,
    While doing sales order and whenever im doing save its  getting runtime error.
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          14.12.2011 10:55:26
    Short dump has not been completely stored (too big)
    Short text
        The current application triggered a termination with a short dump.
    What happened?
        The current application program detected a situation which really
        should not occur. Therefore, a termination with a short dump was
        triggered on purpose by the key word MESSAGE (type X).
    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
        Short text of error message:
        Maintain the current CRM release (table CRMPAROLTP)
        Long text of error message:
         Diagnosis
             Various transfer errors occur when transferring SAP sales orders to
             CRM or there is no status update or the status update has errors
             when transferring from CRM to the SAP system. This is caused by an
             incorrect entry for the CRM release in the SAP table CRMPAROLTP, or
             no entry is maintained at all.
         System Response
             To avoid data inconsistencies, this message causes a short dump.
         Procedure
             Maintain table CRMPAROLTP in your SAP system as is described in SAP
             Note 691710 and then repeat the process again.
         Procedure for System Administration
        Technical information about the message:
        Message class....... "V3"
        Number.............. 302
        Variable 1.......... " "
        Variable 2.......... " "
        Variable 3.......... " "
        Variable 4.......... " "
    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.
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          14.12.2011 10:55:26
    hort dump has not been completely stored (too big)
        If you have access to SAP Notes, carry out a search with the following
        keywords:
        "MESSAGE_TYPE_X" " "
        "SAPMV45A" or "MV45AF0B_BAPIDATEN_ERMITTELN"
        "BAPIDATEN_ERMITTELN"
        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.
    System environment
        SAP-Release 700
        Application server... "personal"
        Network address...... "192.168.2.11"
        Operating system..... "Windows NT"
        Release.............. "5.2"
        Hardware type........ "4x Intel 80686"
        Character length.... 16 Bits
        Pointer length....... 32 Bits
        Work process number.. 1
        Shortdump setting.... "full"
        Database server... "PERSONAL"
        Database type..... "ORACLE"
        Database name..... "GCU"
        Database user ID.. "SAPSR3"
        Char.set.... "C"
        SAP kernel....... 700
        created (date)... "Aug 29 2006 00:18:21"
        create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
        Database version. "OCI_10201_SHARE (10.2.0.1.0) "
        Patch level. 75
        Patch text.. " "
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          14.12.2011 10:55:26
    hort dump has not been completely stored (too big)
        Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
        SAP database version. 700
        Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
        Memory consumption
        Roll.... 8176
        EM...... 30311496
        Heap.... 0
        Page.... 139264
        MM Used. 14538320
        MM Free. 91952
    User and Transaction
        Client.............. 100
        User................ "INFO_SD"
        Language key........ "E"
        Transaction......... "VA01 "
        Program............. "SAPMV45A"
        Screen.............. "SAPMV45A 4001"
        Screen line......... 65
    Information on where terminated
        Termination occurred in the ABAP program "SAPMV45A" - in "BAPIDATEN_ERMITTELN".
        The main program was "SAPMV45A ".
        In the source code you have the termination point in line 338
        of the (Include) program "MV45AF0B_BAPIDATEN_ERMITTELN".
    Edited by: kiran35086 on Dec 14, 2011 6:30 AM

    Dear  kiran,
    This might be many reasons.If you have not done  configuration properly system will take you to dump(Run time error).
    Try read the diagnosis possibly you may understand the problem.
    If not You coordinate with your technical team.
    Thanks&Regards
    Raghu.k

  • Run time error QA32 of QM

    We are geting following run time error when executeing QA32 t-code of QM , error as follows ,
    Error analysis
    After a specific time, the program is terminated to make the work area
    available to other users who may be waiting.
    This is to prevent a work area being blocked unnecessarily long by, for
    example:
    - Endless loops (DO, WHILE, ...),
    - Database accesses with a large result set
    - Database accesses without a suitable index (full table scan)
    The maximum runtime of a program is limited by the system profile
    parameter "rdisp/max_wprun_time". The current setting is 600 seconds. If this
    time limit is
    exceeded, the system attempts to cancel any running SQL statement or
    signals the ABAP processor to stop the running program. Then the system
    waits another 60 seconds maximum. If the program is then still active,
    the work process is restarted.
    How to correct the error
    Programs with long runtime should generally be started as background
    jobs. If this is not possible, you can increase the system profile
    parameter "rdisp/max_wprun_time".
    Depending on the cause of the error, you may have to take one of the
    following measures:
    - Endless loop: Correct program;
    - Dataset resulting from database access is too large:
    Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table
    (for example);
    - Database has unsuitable index: Check index generation.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    Runtime Errors TIME_OUT
    Date and Time 30.06.2009 10:17:31
    Short dump has not been completely stored (too big)
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "TIME_OUT" " "
    "SAPLBSVA" or "LBSVAU14"
    "STATUS_PRE_READ"
    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.
    System environment
    SAP-Release 700
    Application server... "GALT"
    Network address...... "202.54.13.238"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "2x Intel 80686"
    Character length.... 8 Bits
    Pointer length....... 32 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database server... "GALT"
    Database type..... "ORACLE"
    Database name..... "PRD"
    Database user ID.. "SAPSR3"
    Char.set.... "English_United State"
    SAP kernel....... 700
    created (date)... "Oct 13 2006 00:08:41"
    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version. "OCI_10201_SHARE (10.2.0.1.0) "
    Patch level. 80
    Patch text.. " "
    Runtime Errors TIME_OUT
    Date and Time 30.06.2009 10:17:31
    Short dump has not been completely stored (too big)
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
    SAP database version. 700
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
    Memory consumption
    Roll.... 8112
    EM...... 16724736
    Heap.... 0
    Page.... 450560
    MM Used. 6688784
    MM Free. 626280
    User and Transaction
    Client.............. 400
    User................ "MGMTSER"
    Language key........ "E"
    Transaction......... "QA11 "
    Program............. "SAPLBSVA"
    Screen.............. "SAPMQEVA 0200"
    Screen line......... 41
    Information on where terminated
    Termination occurred in the ABAP program "SAPLBSVA" - in "STATUS_PRE_READ".
    The main program was "SAPMQEVA ".
    In the source code you have the termination point in line 61
    of the (Include) program "LBSVAU14".
    Source Code Extract
    Line SourceCde
    31
    32 OBJNR_TAB[] = JSTO_PRE_TAB[].
    33
    34 * Merken: jeweils bisherige Anzahl Einträge im Puffer
    35 DESCRIBE TABLE JSTO_BUF LINES JSTO_BUF_LINES.
    36 DESCRIBE TABLE JEST_BUF LINES JEST_BUF_LINES.
    37 DESCRIBE TABLE OBJNR_TAB LINES OBJNR_TAB_LINES. "Note978655
    38 ADD 1 TO JSTO_BUF_LINES.
    39
    40 l_percentage = OBJNR_TAB_LINES * 100 / JSTO_BUF_LINES. "Note978655
    41 * Small number of object numbers to be read, insert records "Note978655
    42 * sequentially to avoid expensive SORT on JSTO_BUF,JEST_BUF "Note978655
    43 IF ( l_percentage <= 1 OR OBJNR_TAB_LINES < 20 ) AND "Note978655
    44 get_change_documents IS INITIAL. "Note978655
    45 LOOP AT objnr_tab. "Note978655
    46 SELECT * FROM JSTO CLIENT SPECIFIED "Note978655
    47 FOR ALL ENTRIES IN OBJNR_TAB "Note978655
    48 WHERE MANDT EQ CLIENT "Note978655
    49 AND OBJNR = OBJNR_TAB-OBJNR. "Note978655
    50 READ TABLE JSTO_BUF WITH KEY MANDT = JSTO-MANDT "Note978655
    51 OBJNR = JSTO-OBJNR "Note978655
    52 BINARY SEARCH. "Note978655
    53 IF SY-SUBRC <> 0. "Note978655
    Runtime Errors TIME_OUT
    Date and Time 30.06.2009 10:17:31
    Short dump has not been completely stored (too big)
    54 JSTO_BUF = JSTO. "Note978655
    55 CLEAR JSTO_BUF-MOD. "Note978655
    56 JSTO_BUF-STSMA_OLD = JSTO_BUF-STSMA. "Note978655
    57 INSERT JSTO_BUF INDEX SY-TABIX. "Note978655
    58 ENDIF. "Note978655
    59 ENDSELECT. "Note978655
    60 "Note978655
    >>>>> SELECT * FROM JEST CLIENT SPECIFIED "Note978655
    62 FOR ALL ENTRIES IN OBJNR_TAB "Note978655
    63 WHERE MANDT EQ CLIENT "Note978655
    64 AND OBJNR = OBJNR_TAB-OBJNR. "Note978655
    65 READ TABLE JEST_BUF WITH KEY MANDT = JEST-MANDT "Note978655
    66 OBJNR = JEST-OBJNR "Note978655
    67 STAT = JEST-STAT "Note978655
    68 BINARY SEARCH. "Note978655
    69 IF SY-SUBRC <> 0. "Note978655
    70 JEST_BUF = JEST. "Note978655
    71 CLEAR JEST_BUF-MOD. "Note978655
    72 JEST_BUF-INACT_OLD = JEST_BUF-INACT. "Note978655
    73 INSERT JEST_BUF INDEX SY-TABIX. "Note978655
    74 ENDIF. "Note978655
    75 ENDSELECT. "Note978655
    76 ENDLOOP. "Note978655
    77 CLEAR: JSTO_BUF,JEST_BUF. "Note978655
    78 EXIT. "Note978655
    79 ENDIF. "Note978655
    80
    Contents of system fields
    Name Val.
    SY-SUBRC0
    SY-INDEX0
    SY-TABIX15
    SY-DBCNT15
    SY-FDPOS1
    SY-LSIND0
    SY-PAGNO0
    SY-LINNO1
    SY-COLNO1
    SY-PFKEYA101
    SY-UCOMMBU
    SY-TITLE Record Usage Decision: Characteristic Overview
    SY-MSGTY
    SY-MSGID
    SY-MSGNO000
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO0
    SY-DATUM20090630
    SY-UZEIT101723
    SY-XPROGSAPLQAMB
    SY-XFORMCONVERSION_EXIT
    Edited by: Raghavendra Balegar on Jul 3, 2009 12:21 PM

    No Dear,
    Not at all. I think it should work for atleast one month period.
    But sometimes depending on the database size and hardware, this criteria can vary.
    Regds,
    Anil

Maybe you are looking for

  • ORA-00204: error in reading (block string, # blocks string) of controlfile

    dear all when i start db with command  sqlplus "/as sysdba"  at the end it generate an error C:\Documents and Settings\idsadm>sqlplus "/as sysdba" SQL*Plus: Release 10.2.0.1.0 - Production on Mon Oct 20 12:47:37 2008 Copyright (c) 1982, 2005, Oracle.

  • Validation for Cost center for Goods issue against the cost centers

    Dear Friends In my client place we have 6 plants are defined and profit centers are defined for each plant. Hence here each plant is one profit center. Cost centers are defined plant wise. The requirement is when the goods issued to cost center syste

  • Remote XML Parser Problem

    Hi Friends; I have an application and i get some values from xml service.  I have 2 same project. One of them work in portal j2ee engine another is apache tomcat. But there is ~1minute time difference between them. Apache tomcat get quickly. What can

  • Help in "how to" with droid 2

    Hi all, I just got this Droid 2 for my birthday from children.... Now can someone please help me in telling me how to use it??? thanks, Boss

  • Drop Procedure

    Hi, I am trying to drop some procedure in my database, its not working. it says that object was locked, i checked the v$lock and dba_jobs_running, there is no lock. kindly tell how can i drop the procedure.