Error TSV_TNEW_PAGE_ALLOC_FAILED caused by Function CHANGEDOCUMENT_READ

Hi,
I met the error TSV_TNEW_PAGE_ALLOC_FAILED when I call the function CHANGEDOCUMENT_READ.
However, I only import a day , a table and a objectclass.
CALL FUNCTION 'CHANGEDOCUMENT_READ'
      EXPORTING
        date_of_change             = c_day
        objectclass                = c_class
        tablename                  = c_table
        date_until                 = c_day
      TABLES
        editpos                    = i_editpos
      EXCEPTIONS
        no_position_found          = 1
        wrong_access_to_archive    = 2
        time_zone_conversion_error = 3
        OTHERS                     = 4.
And when I debug it, I found it get very huge data(Both CDHDR and CDPOS have more than 500,000 records).
Any suggestion will be helpful.
Thanks,
Franklin

It looks like you will read to call it multiple times including the parameters TIME_OF_CHANGE and TIME_UNTIL, But this will be very time consuming.
Check the documentation on these two parameters.
Rob

Similar Messages

  • Runtime errors: TSV_TNEW_PAGE_ALLOC_FAILED

    Hi,
    When I am trying to check the consistency of background jobs in SM65, It is throwig a runtime error TSV_TNEW_PAGE_ALLOC_FAILED. Kindly look into the below text message from ST22.
    ShrtText
        No storage space available for extending an internal table.
    What happened?
        You attempted to extend an internal table, but the required space was
        not available.
    What can you do?
        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.
        Try to find out (e.g. by targetted data selection) whether the
        transaction will run with less main memory.
        If there is a temporary bottleneck, execute the transaction again.
        If the error persists, ask your system administrator to check the
        following profile parameters:
        o  ztta/roll_area            (1.000.000 - 15.000.000)
               Classic roll area per user and internal mode
               usual amount of roll area per user and internal mode
        o  ztta/roll_extension       (10.000.000 - 500.000.000)
    o  abap/heap_area_total      (100.000.000 - 1.500.000.000)
           Amount of memory (malloc) for all users of an application
           server. If several background processes are running on
           one server, temporary bottlenecks may occur.
           Of course, the amount of memory (in bytes) must also be
           available on the machine (main memory or file system swap).
           Caution:
           The operating system must be set up so that there is also
           enough memory for each process. Usually, the maximum address
           space is too small.
           Ask your hardware manufacturer or your competence center
           about this.
           In this case, consult your hardware vendor
    abap/heap_area_dia:        (10.000.000 - 1.000.000.000)
           Restriction of memory allocated to the heap with malloc
           for each dialog process.
    Parameters for background processes:
    abap/heap_area_nondia:        (10.000.000 - 1.000.000.000)
           Restriction of memory allocated to the heap with malloc
           for each background process.
    Other memory-relevant parameters are:
    em/initial_size_MB:         (35-1200)
           Extended memory area from which all users of an
           application server can satisfy their memory requirement.
    Error analysis
    The internal table "IT_18" could not be enlarged further. To allow
    error handling, the table had to be deleted before this log was
    created. So, if you branch to the ABAP debugger from the display
    of this log, the table will there be displayed with 0 rows.
    At the moment of the termination, the following data was
    determined for the respective internal table:
    Storage location: "Session memory"
    Row width: 1296
    Number of rows: 1166120
    Allocated rows: 1166120
    Newly requested rows: 8 (in 1 blocks)
               Last error logged in SAP kernel
    Component............ "EM"
    Place................ "SAP-Server ord-sapprd_PRD_00 on host ord-sapprd (wp 0)"
    Version.............. 37
    Error code........... 7
    Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
    Description.......... " "
    System call.......... " "
    Module............... "emxx.c"
    Line................. 1878
    How to correct the error
        The amount of storage space (in bytes) filled at termination time was:
        Roll area...................... 1709536
        Extended memory (EM)........... 408685712
        Assigned memory (HEAP)......... 1190561024
        Short area..................... " "
        Paging area.................... 57344
        Maximum address space.......... " "
        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:
        "TSV_TNEW_PAGE_ALLOC_FAILED" C
        "SAPLSBPT" or "LSBPTFXX"
        "DO_TBTCO_CONSISTENCY_CHECK"
        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....... "ord-sapprd"
    Network address.......... "10.31.18.27"
    Operating system......... "Windows NT"
    Release.................. "5.2"
    Hardware type............ "16x Intel 80158"
    Character length......... 16 Bits
    Pointer length........... 32 Bits
    Work process number...... 0
    Kindly suggest me the options ASAP as this is happened in the production system.
    Thanks in advance,
    Suneetha Reddy

    Hi Sunnetha,
    SM65 is a resource hungry tcode, and always suggested to run during a off-business hours. Try to run when there is not much acvitity going on in the system.
    I'm not very much sure, but please check how many entries there in TBTCO table. as the dump gives indication of
    DO_TBTCO_CONSISTENCY_CHECK.
    Check RSBTCDEL(2) program is running daily or not. This runs as a background job to delete the old job information from the tables TBTC*. If this has not run, then you can run and delete older job logs and then retry.
    Which system you're using? ECC or BW??
    Note - parameter settings of BW largely varies from that of a ECC system.
    Thanks,
    Debasis.

  • Error calling pl/sql function in target column

    Hi guys,
    I get this error when calling my function in ODI:
    Caused By: java.sql.SQLSyntaxErrorException: ORA-00904: "mySchema"."GET_ODI_DEFAULT_VALUE(1)": ongeldige ID --> 1 is an IN parameter
    while in sql developer I get a good result with following query:
    select mySchema.get_odi_default_value(1) from dual;
    In my target table for the primary key I call a sequence from mySchema and this works fine.
    I've tried the following synxtax in the mapping of my target column:
    - <%=odiRef.getObjectName( "L","GET_ODI_DEFAULT_VALUE(1)", "D" )%>
    - <%=odiRef.getObjectName( "L","GET_ODI_DEFAULT_VALUE", "D" )(1)%>
    Thanks for you advice

    iadgroe wrote:
    how to bring oracle function into ODI
    I thought for objects like sequences and functions you had to use 'odiRef.getObjectName' to get access to them.
    Am I wrong because now I'm a little confused???Hi,
    Best practices would be to use getobjectname method as this way your not hardcoding anything into the interface and you are referencing the logical object only, which means you can change the logical object later and not have to worry about changing the interfaces.

  • Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED during extraction

    Hi,
    Anyone knows what the solution is to this problem:
    Runtime Errors         TSV_TNEW_PAGE_ALLOC_FAILED
    |Short text                                                                                |
    |    No more storage space available for extending an internal table.                              |
    |What happened?                                                                                |
    |    You attempted to extend an internal table, but the required space was                         |
    |    not available
    |Error analysis                                                                                |
    |    The internal table "\FUNCTION=CRM_UPLOAD_BTMBDOC_FILL\DATA=ET_BILLPLAN_D" could               |
    |     not be further extended. To enable                                                           |
    |    error handling, the table had to be delete before this log was written.                       |
    |    As a result, the table is displayed further down or, if you branch to                         |
    |    the ABAP Debugger, with 0 rows.                                                               |
    |                                                                                |
    |    At the time of the termination, the following data was determined for                         |
    |    the relevant internal table:                                                                  |
    |                                                                                |
    |    Memory location: "Session memory"                                                             |
    |    Row width: 1908                                                                               |
    |    Number of rows: 35912                                                                         |
    |    Allocated rows: 35912                                                                         |
    |    Newly requested rows: 8 (in 1 blocks)                                                         |
    |    Last error logged in SAP kernel                                                               |
    |                                                                                |
    |    Component............ "EM"                                                                    |
    |    Place................ "xxx"                   |
    |    Version.............. 37                                                                      |
    |    Error code........... 7                                                                       |
    |    Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "                  |
    |    Description.......... " "                                                                     |
    |    System call.......... " "                                                                     |
    |    Module............... "emxx.c"                                                                |
    |    Line................. 1897                                                                    |
    |                                                                                |
    |    The error reported by the operating system is:                                                |
    |    Error number..... " "                                                                         |
    |    Error text....... " "                                                                         |
    |How to correct the error                                                                          |
    |    The amount of storage space (in bytes) filled at termination time was:                        |
    |                                                                                |
    |    Roll area...................... 6221152                                                       |
    |    Extended memory (EM)........... 1826778184                                                    |
    |    Assigned memory (HEAP)......... 2000035456                                                    |
    |    Short area..................... " "                                                           |
    |    Paging area.................... 73728                                                         |
    |    Maximum address space.......... 4294967295                                                    |
    |                                                                                |
    |    If the error occures in a non-modified SAP program, you may be able to                        |
    |    find an interim solution in an SAP Note.                                                      |
    |    If you have access to SAP Notes, carry out a search with the following                        |
    |    keywords:                                                                                |
    |                                                                                |
    |    "TSV_TNEW_PAGE_ALLOC_FAILED" " "                                                              |
    |    "SAPLCRM_UPLOAD_BTMBDOC" or "LCRM_UPLOAD_BTMBDOCF36"                                          |
    |    "FILL_BILLPLAN"                                                                               |
    |                                                                                |
    |    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.                                                           |
    |                                                                                |

    Runtime Errors         TSV_TNEW_PAGE_ALLOC_FAILED
    Short text
    No more storage space available for extending an internal table
    |What happened?
    |    You attempted to extend an internal table, but the required space was
    |    not available.
    |Error analysis                                                                                |
    |    The internal table "\FUNCTION=CRM_UPLOAD_BTMBDOC_FILL\DATA=ET_BILLPLAN_D" could
    |     not be further extended. To enable
    |    error handling, the table had to be delete before this log was written.                       |
    |    As a result, the table is displayed further down or, if you branch to                         |
    |    the ABAP Debugger, with 0 rows.                                                               |
    |                                                                                |
    |    At the time of the termination, the following data was determined for                         |
    |    the relevant internal table:                                                                  |
    |                                                                                |
    |    Memory location: "Session memory"                                                             |
    |    Row width: 1908                                                                               |
    |    Number of rows: 35912                                                                         |
    |    Allocated rows: 35912                                                                         |
    |    Newly requested rows: 8 (in 1 blocks)                                                         |
    |    Last error logged in SAP kernel                                                               |
    |                                                                                |
    |    Component............ "EM"                                                                    |
    |    Place................ "SAP-Server XXXX"                   |
    |    Version.............. 37                                                                      |
    |    Error code........... 7                                                                       |
    |    Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "                  |
    |    Description.......... " "                                                                     |
    |    System call.......... " "                                                                     |
    |    Module............... "emxx.c"                                                                |
    |    Line................. 1897                                                                    |
    |                                                                                |
    |    The error reported by the operating system is:                                                |
    |    Error number..... " "                                                                         |
    |    Error text....... " "                                                                         |
    |                                                                                |
    |                                                                                |
    |                                                                                |
    |                                                                                |
    |How to correct the error                                                                          |
    |    The amount of storage space (in bytes) filled at termination time was:                        |
    |                                                                                |
    |    Roll area...................... 6221152                                                       |
    |    Extended memory (EM)........... 1826778184                                                    |
    |    Assigned memory (HEAP)......... 2000035456                                                    |
    |    Short area..................... " "                                                           |
    |    Paging area.................... 73728                                                         |
    |    Maximum address space.......... 4294967295                                                    |
    |                                                                                |
    |    If the error occures in a non-modified SAP program, you may be able to                        |
    |    find an interim solution in an SAP Note.                                                      |
    |    If you have access to SAP Notes, carry out a search with the following                        |
    |    keywords:                                                                                |
    |                                                                                |
    |    "TSV_TNEW_PAGE_ALLOC_FAILED" " "                                                              |
    |    "SAPLCRM_UPLOAD_BTMBDOC" or "LCRM_UPLOAD_BTMBDOCF36"                                          |
    |    "FILL_BILLPLAN"                                                                               |
    |                                                                                |
    |    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.                                                           |
    |                                                                                |

  • Rule Based ATP- Error in calling up function 'BAPI_APOATP_CHECK' in APO ser

    Hi Experts
    I hae configured Rule Based ATP with Multi-Level ATP check. I have completed all configuration required for Rule Based ATP but still facing an error
    " Error in calling up function 'BAPI_APOATP_CHECK' in APO server 'SC5CLNT001': Check instructions 30 / A does not exist for locat"
    Have any of you ever encountered this error?
    Regards,
    Sushovan Datta

    Dear Sushovan,
    Most likely cause of the above error is a missing requirement class in R/3 and missing Check mode in APO for material and plant combination.                            
    Please read the F1-Help for field check mode in APO:                    
    "Together with the business event, the check mode derived from the product master defines the type and scope of the checks carried out. It also controls forecast consumption.                                                                               
    SD (R/3) uses the requirement class of the requirement as check mode. As of R/3 Plugin 2000.1, the requirement class is transferred (via the strategy group in the material master) to the location-specific APO product master (ATP tab page). In the process, no plausibility check is carried out. For this reason, you should not enter any other check mode in the product master. (The check mode in the product master must agree with the requirement class from the R/3 system.)"                                                                               
    So please create for your material in corresponding plant the requirement class ' 030' assigned to the strategy group in MRP3 in R/3 and the same in the check mode field in //mat1 in APO.                                                                               
    Afterwards the gatp check will find the check mode and business event  (check instructions) and the error will be not appear again.            
    Regards,
    Tibor

  • I am getting error Error in calling up function 'BAPI_APOATP_CHECK' in APO server The current application triggered a termination

    I am getting error Error in calling up function 'BAPI_APOATP_CHECK' in APO server The current application triggered a termination
    when triggering for gatp.

    Hi Virender,
    This error can be experienced due to many reasons. based on my experience below reasons can cause this issue.
    1) If you are using allocation check if allocation is correctly set.
    2) In case you are using custom enhancements / user exits (in SD / GATP / CIF) check if any of them, causing this issue.
    In my case correction of allocation setup could resolve this issue, so check what is the reason in your case.
    Rgds
    Sourabh

  • Error in a formula function

    Hi,
    i ran the infopackge.load was failed.failed request is showing Record 1 :Error in a formula function (routine ROUTINE_0001 ), record 1 .why this error is coming.how can i solve this issue?
    Thanks,
    Ali

    Hi,
    As refered by the posts above , you need to edit the data in to PSA, now try going through the procedure below:
    1. Once data is loaded till PSA , ther will be a "process Manually Tab" in the status of the ip, press that.
    2. Now you will get the error in the processing packets .
    3.make the IP red , delete the failed request from target( Info cube), sice for DSO there is a specific procedure.
    4.now go bak to ip click on the psa tab, the error displays record '1', so select the first record in PSA, put the size of the record in the no. of error records and select " error record".
    5. now you will se this error record in the PSA.
    6. Click on the edit record , you will se the canonical structure of the record with its field.
    7. No try editing th record for there might be a entry which seems to be diff from other(compare with correctly loaded records).
    8. edit it , save the changes.
    9. now either recostructing the PSA or manually pushing the failed request to target.
    Hope this will serve your cause
    Thax & Regards
    Vaibhave Sharma

  • Report MB5L giving runtime error TSV_TNEW_PAGE_ALLOC_FAILED

    Hi,
    While running the Report MB5L we are getting the runtime
    error "TSV_TNEW_PAGE_ALLOC_FAILED"
    We tried to schedule this report at non-peak hours but it again got
    terminated with same error.
    We are using 12GB of RAM.
    ztta/roll_area 6500000
    ztta/roll_extension 4000317440
    abap/heap_area_total 3001024512
    abap/heap_area_dia: 5000683008
    abap/heap_area_nondia: 2000000000
    em/initial_size_MB: 8192
    Please find the attached screenshot of ST22 dump analysis.
    Regards,
    Prashant
    Edited by: Prashant Shukla on Feb 25, 2009 11:10 AM

    Hi Juan,
    Pls find the details below-:
    Runtime Errors         TSV_TNEW_PAGE_ALLOC_FAILED                                                  
    Date and Time          24.02.2009 23:31:32                                                                               
    Short text                                                                               
    No more storage space available for extending an internal table.                              
    What happened?                                                                               
    You attempted to extend an internal table, but the required space was                         
        not available.                                                                               
    If the error persists, ask your system administrator to check the                             
        following profile parameters:                                                                               
    Error analysis                                                                               
    The internal table "\FUNCTION=MBEW_EXTEND\DATA=SEARCH_MBEWH_TAB[]" could not be               
         further extended. To enable                                                                  
        error handling, the table had to be delete before this log was written.                       
        As a result, the table is displayed further down or, if you branch to                         
        the ABAP Debugger, with 0 rows.                                                                               
    At the time of the termination, the following data was determined for                         
        the relevant internal table:                                                                               
    Memory location: "Session memory"                                                             
        Row width: 372                                                                               
    Number of rows: 354608                                                                        
        Allocated rows: 354608                                                                        
        Newly requested rows: 32 (in 1 blocks)                                                        
    How to correct the error                                                                               
    The amount of storage space (in bytes) filled at termination time was:                                                                               
    Roll area...................... 6203136                                                       
        Extended memory (EM)........... 4001304840                                                    
        Assigned memory (HEAP)......... 2000059568                                                    
        Short area..................... " "                                                           
        Paging area.................... 32768                                                         
        Maximum address space.......... 18446697160833538863                                                                               
    If the error occures in a non-modified SAP program, you may be able to                        
        find an interim solution in an SAP Note.                                                      
        If you have access to SAP Notes, carry out a search with the following                        
        keywords:                                                                               
    "TSV_TNEW_PAGE_ALLOC_FAILED" " "                                                              
        "SAPLMG27" or "LMG27F02"                                                                      
        "SEARCH_EXIT"                                                                               
    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... "ecprdciclu"                                                            
        Network address...... "172.25.1.34"                                                           
        Operating system..... "Linux"                                                                 
        Release.............. "2.6.18-53.el5"                                                         
        Hardware type........ "x86_64"                                                                
        Character length.... 16 Bits                                                                  
        Pointer length....... 64 Bits                                                                 
        Work process number.. 19                                                                      
        Shortdump setting.... "full"                                                                               
    Database server... "isrecprdb2"                                                               
        Database type..... "ORACLE"                                                                   
        Database name..... "RPD"                                                                      
        Database user ID.. "SAPSR3"                                                                               
    Char.set.... "C"                                                                               
    SAP kernel....... 700                                                                         
        created (date)... "Nov 18 2008 20:45:39"                                                      
        create on........ "Linux GNU SLES-9 x86_64 cc3.3.3"                                           
        Database version. "OCI_102 (10.2.0.2.0) "                                                                               
    Patch level. 185                                                                               
    Patch text.. " "                                                                               
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."                
        SAP database version. 700                                                                     
        Operating system..... "Linux 2.6"                                                                               
    Memory consumption                                                                               
    Roll.... 6203136                                                                               
    EM...... 4001304840                                                                               
    Heap.... 2000059568                                                                               
    Page.... 32768                                                                               
    MM Used. 5803144952                                                                               
    MM Free. 199241240                                                                               
    User and Transaction                                                                               
    Client.............. 610                                                                      
        User................ "SANCHIT"                                                                
        Language key........ "E"                                                                      
        Transaction......... " "                                                                      
        Transactions ID..... "49A289F286FA2313E1000000AC190122"                                                                               
    Program............. "SAPLMG27"                                                               
        Screen.............. "SAPMSSY0 1000"                                                          
        Screen line......... 6                                                                        
    Information on where terminated                                                                   
        Termination occurred in the ABAP program "SAPLMG27" - in "SEARCH_EXIT".                       
        The main program was "RM07MBST ".                                                                               
    In the source code you have the termination point in line 558                                 
        of the (Include) program "LMG27F02".                                                          
        The program "SAPLMG27" was started as a background job.                                       
        Job Name....... "RM07MBST"                      
    Regards,
    Prashant

  • Error in Package containing function

    Hi, Here is my package that i am getting error - "PLS-00103: Encountered the symbol "=" when expecting one of the following"
    create or replace package pre_pkg
    is
    FUNCTION FUN_DATE (a_date date)
    RETURN number;
    end pre_pkg;
    create or replace package body pre_pkg
    is
    function FUN_DATE (a_date date)
    return number
    is
    BEGIN
    IF REGEXP_LIKE(a_date,'^\d{1}|d{2}/\d{1}|d{2}/\d{4} \d{2}:\d{2}:\d{2}.\d{3}$')
    AND (REGEXP_INSTR(a_date,'[AP]M',1)=0
    AND LENGTH(a_date) > 11
    AND LENGTH(TRUNC(to_char(TO_TIMESTAMP(a_date,'MM/DD/YYYY HH24:MIS.FF'),'YYYY')))=4)
    THEN
    return := 0;
    ELSIF REGEXP_LIKE(a_date,'^\d{1}|d{2}/\d{1}|d{2}/\d{4} \d{2}:\d{2}:\d{2} [AP]M$')
    AND (REGEXP_INSTR(a_date,'[AP]M',1) > 0
    AND LENGTH(TRUNC(to_char(TO_DATE(a_date,'MM/DD/YYYY HH:MIS AM'),'YYYY')))=4)
    THEN
    return := 0;
    ELSIF REGEXP_LIKE(a_date,'^\d{1}|d{2}/\d{1}|d{2}/\d{4}$')
    AND (REGEXP_INSTR(a_date,'[AP]M',1)=0
    AND LENGTH(TRIM(a_date)) < 11
    AND LENGTH(TRUNC(to_char(TO_DATE(a_date,'MM/DD/YYYY'),'YYYY')))=4)
    THEN
    return := 0;
    ELSE
    return := 1;
    END IF;
    EXCEPTION
    WHEN OTHERS THEN
    return := 1;
    END FUN_DATE;
    END pre_pkg;
    Can any one help me in this regard. I am using oracle 10g.

    Good practice for writing functions it so have a single exit point at the end of the function, rather than embedding return statements throughout it e.g.
    create or replace package pre_pkg is
      FUNCTION FUN_DATE (a_date date) RETURN number;
    end pre_pkg;
    create or replace package body pre_pkg is
      function FUN_DATE (a_date date) return number is
        v_retval number;
      BEGIN
        IF REGEXP_LIKE(a_date,'^\d{1}|d{2}/\d{1}|d{2}/\d{4} \d{2}:\d{2}:\d{2}.\d{3}$')
           AND (REGEXP_INSTR(a_date,'[AP]M',1)=0
           AND LENGTH(a_date) > 11
           AND LENGTH(TRUNC(to_char(TO_TIMESTAMP(a_date,'MM/DD/YYYY HH24:MIS.FF'),'YYYY')))=4)
        THEN
          v_retval := 0;
        ELSIF REGEXP_LIKE(a_date,'^\d{1}|d{2}/\d{1}|d{2}/\d{4} \d{2}:\d{2}:\d{2} [AP]M$')
           AND (REGEXP_INSTR(a_date,'[AP]M',1) > 0
           AND LENGTH(TRUNC(to_char(TO_DATE(a_date,'MM/DD/YYYY HH:MIS AM'),'YYYY')))=4)
        THEN
          v_retval := 0;
        ELSIF REGEXP_LIKE(a_date,'^\d{1}|d{2}/\d{1}|d{2}/\d{4}$')
           AND (REGEXP_INSTR(a_date,'[AP]M',1)=0
           AND LENGTH(TRIM(a_date)) < 11
           AND LENGTH(TRUNC(to_char(TO_DATE(a_date,'MM/DD/YYYY'),'YYYY')))=4)
        THEN
          v_retval := 0;
        ELSE
          v_retval := 1;
        END IF;
        RETURN v_retval;
      EXCEPTION
        WHEN OTHERS THEN
          return := 1;
      END FUN_DATE;
    END pre_pkg;
    /Other things to note:
    WHEN OTHERS exception is considered poor practice, especially if it doesn't raise an exception itself. Exception handlers should be written to cater for whatever exceptions you are expecting to happen, not a capture-all. Looking at your code, I wouldn't expect it to be raising any exceptions from the code itself.
    Curiously, your function seems very odd. It looks like you are trying to validate that a date is valid, but by virtue of the fact that it's a DATE datatype it will (with very few exceptions e.g corrupt dates) be valid. The fact that you pass a DATE datatype as the first parameter of your REGEXP_LIKE functions means that it is doing an implicit conversion of that DATE datatype to a VARCHAR2 datatype based on your sessions NLS_* settings, which could vary and cause your function to fail in other sessions. If the date were actually being passed into the funciton as a string (varchar2) then there are simpler ways to validate whether it's a valid date or not, simply by trying to turn the string into a DATE datatype and capturing the exception for invalid dates.

  • ERROR   OGG-00146  VAM function VAMInitialize returned unexpected

    I am configuring Golden Gate for MySQL and when i start extract it says extract started successfully but when i see its log file then i see this
    2011-03-04 01:55:10 ERROR OGG-00146 VAM function VAMInitialize returned unexpected
    result: error 600 - VAM Client Report <CAUSE OF FAILURE : Log index file
    does not exist,please check if binary logging is enabled - /var/lib/mysql//Hassan-bin.index
    WHEN FAILED : While initializing binary log configuration
    WHERE FAILED : MySQLBinLog Reader Module
    CONTEXT OF FAILURE : No Information Available!>.
    2011-03-04 01:55:10 ERROR OGG-01668 PROCESS ABENDING.
    then i changed MySQL bin log file name format to what it is saying and restarted MySQL service and again tried to start extract process. Now I am getting this error which is not clear to me
    011-03-04 23:13:14 ERROR OGG-00146 VAM function VAMInitialize returned unexpected
    result: error 600 - VAM Client Report <CAUSE OF FAILURE : Position time is
    prior then earliest time available in the log : Earliest time available in the
    log is 2011-03-04 23:08:25
    WHEN FAILED : SetInitialPosition by time stamp
    WHERE FAILED : MySQLBinLog Reader Module
    CONTEXT OF FAILURE : No Information Available!>.
    2011-03-04 23:13:14 ERROR OGG-01668 PROCESS ABENDING.
    any one can help me out why this is occuring

    I have just deleted all extract & replicat and reconfigured , now things are working fine.

  • Error in running a function to convert coordinates in degrees to decimal for EXCEL VBA

    For your information, I have 3 cross-posts regarding this question - and all I can said there is still no firm solution regarding this error.
    1) http://stackoverflow.com/questions/27634586/error-in-running-a-function-to-convert-coordinates-in-degrees-to-decimal-for-exc/27637367#27637367
    2) http://www.mrexcel.com/forum/excel-questions/826099-error-running-function-convert-coordinates-degrees-decimal-excel-visual-basic-applications.html#post4030377 
    3) http://www.excelguru.ca/forums/showthread.php?3909-Error-in-running-a-function-to-convert-coordinates-in-degrees-to-decimal-for-EXCEL-VB&p=16507#post16507
    and the story of the error is as below:
    Currently I am working on VBA excel to create a widget to verify coordinates whether it lies under the radius of ANOTHER predefined and pre-specified sets of coordinates.
    In the module, I want to convert the coordinates from degrees to decimal before doing the calculation - as the formula of the calculation only allow the decimal form of coordinates.
    However, each and every time I want to run the macros this error (Run-time error '5', invalid procedure call or argument) will appear. Then, the debug button will bring me to below line of coding:
    degrees = Val(Left(Degree_Deg, InStr(1, Degree_Deg, "°") - 1))
    For your information, the full function is as below:
    Function Convert_Decimal(Degree_Deg As String) As Double
    'source: http://support.microsoft.com/kb/213449
    Dim degrees As Double
    Dim minutes As Double
    Dim seconds As Double
    Degree_Deg = Replace(Degree_Deg, "~", "°")
    degrees = Val(Left(Degree_Deg, InStr(1, Degree_Deg, "°") - 1))
    minutes = Val(Mid(Degree_Deg, InStr(1, Degree_Deg, "°") + 2, _
    InStr(1, Degree_Deg, "'") - InStr(1, Degree_Deg, "°") - 2)) / 60
    seconds = Val(Mid(Degree_Deg, InStr(1, Degree_Deg, "'") + _
    2, Len(Degree_Deg) - InStr(1, Degree_Deg, "'") - 2)) / 3600
    Convert_Decimal = degrees + minutes + seconds
    End Function
    Thank you.
    Your kind assistance and attention in this matter are highly appreciated.
    Regards,
    Nina.

    You didn't give an example of your input string but try the following
    Sub test()
    Dim s As String
    s = "180° 30' 30.5""""" ' double quote for seconds
    Debug.Print Deg2Dec(s) ' 180.508472222222
    End Sub
    Function Deg2Dec(sAngle As String) As Double
    Dim mid1 As Long
    Dim mid2 As Long
    Dim degrees As Long
    Dim minutes As Long
    Dim seconds As Double ' or Long if only integer seconds
    sAngle = Replace(sAngle, " ", "")
    mid1 = InStr(sAngle, "°")
    mid2 = InStr(sAngle, "'")
    degrees = CLng(Left$(sAngle, mid1 - 1))
    minutes = CLng(Mid$(sAngle, mid1 + 1, mid2 - mid1 - 1))
    seconds = Val(Mid$(sAngle, mid2 + 1, 10)) ' change 10 to 2 if only integer seconds
    Deg2Dec = degrees + minutes / 60 + seconds / 3600
    End Function
    As written the function assumes values for each of deg/min/sec are included with unit indicators as given. Adapt for your needs.
    In passing, for any work with trig functions you will probably need to convert the degrees to radians.

  • SSRS countrow Aggregate error(Aggregate and lookup functions cannot be used in query parameter expressions.)

    Below expression works fine with text box but gives error in dataset expression.
    ="SET FMTONLY OFF select  "+ join(Parameters!Column.Value,",") +" FROM pamcustom.dbo.vw_HFL_HFD_HotfileData INNER JOIN pamcustom.dbo.HFL_HFB_HotFileBatch  on BatchID = HFB_intBatchID where BatchID ="+Parameters!BatchId.Value+"
    and "+Parameters!cmbTranType.Value+" "+ iif(CountRows("DS_Aml_Mnr_Iss_Desc")=Parameters!Mnr_Iss_Desc.count," "," and aml_mnr_iss_desc in "+"('" & join(Parameters!Mnr_Iss_Desc.Value,"','")
    & "')")+iif(CountRows("ds_ReportingCategory")=Parameters!ReportingCategory.count," "," and ReportingCategory in "+"('" & join(Parameters!ReportingCategory.Value,"','") & "')")+iif(CountRows("ds_NAICSubGroup")=Parameters!NAICSubGroup.count,"
    "," and naicsubgroup in "+"('" & join(Parameters!NAICSubGroup.Value,"','") & "')")+iif(CountRows("ds_PortTrading")=Parameters!PortTrading.count," "," and porttrading in "+"('"
    & join(Parameters!PortTrading.Value,"','") & "')")+iif(CountRows("ds_GL_LE")=Parameters!GL_LE.count," "," and gl_le in "+"('" & join(Parameters!GL_LE.Value,"','") &
    "')")+iif(CountRows("ds_coagroup")=Parameters!cmbCoaGrp.count," "," and coagroup in "+"('" & join(Parameters!cmbCoaGrp.Value,"','") & "')")+iif(CountRows("Portfolio")=Parameters!cmbPort.count,"
    "," and portfolio in "+"('" & join(Parameters!cmbPort.Value,"','") & "')")+IIf(IsNothing(Parameters!txtSecID.Value)," "," and secid in ('"+Replace(Parameters!txtSecID.Value,",","','")+"')")+iif(IsNothing(Parameters!minPortFilter.Value)
    and IsNothing(Parameters!MinPort.Value)," "," and portfolio "+Parameters!minPortFilter.Value+Parameters!MinPort.Value)+iif(IsNothing(Parameters!maxPortFilter.Value) and IsNothing(Parameters!MaxPort.Value)," ","
    and portfolio "+Parameters!maxPortFilter.Value+Parameters!MaxPort.Value)+iif(IsNothing(Parameters!minCoaFilter.Value) and IsNothing(Parameters!txtMinCoa.Value)," "," and portfolio "+Parameters!minCoaFilter.Value+Parameters!txtMinCoa.Value)+iif(IsNothing(Parameters!maxCoaFilter.Value)
    and IsNothing(Parameters!txtMaxCoa.Value)," "," and portfolio "+Parameters!maxCoaFilter.Value+Parameters!txtMaxCoa.Value)
    I guess the error " Aggregate and lookup functions cannot be used in query parameter expressions." is because I am using CountRow to ensure that if all values of multi select all selected i will not use that filter in where clause.
    Pls. guide...

    Hi, Include your parameter total count in the dataset for parameter and instead of using countrows() function use the count from dataset in the expression.
    Hope this helps.........
    Ione

  • Error While uploading the Function and Function_BP

    Hello,
    I am getting the following error while uploading the Functions and Funtions_BP using the Rule Upload functions.
    com.virsa.cc.comp.Function_upload.onActionUploadFunc(Function_upload.java:302) com.virsa.cc.comp.wdp.InternalFunction_upload.wdInvokeEventHandler(InternalFunction_upload.java:150) com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420) com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132) com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335) com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143) com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321) com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713) com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666) com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250) com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149) com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62) com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53) javax.servlet.http.HttpServlet.service(HttpServlet.java:760) javax.servlet.http.HttpServlet.service(HttpServlet.java:853) com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401) com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386) com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364) com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039) com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265) com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) java.security.AccessController.doPrivileged(Native Method) com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104) com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    The files which i am uploading the file from the Best practises only.
    What is the reason for this error?
    Did any one get this error?
    Regards,
    Kumar Rayudu
    Edited by: Kumar Rayudu on Aug 4, 2009 12:32 PM

    Hello Kumar,
    Have you uploaded the SAP text and object files? Upload them first and then try to upload functions.
    Harleen
    SAP GRC RIG

  • Error while activating the function module

    hi,
    am getting error while activating the function module i.e. program or report statement is missing.
    thank you in advance
    karthik

    hii vinu,
    hi there....
    make sure that the Processing type in Attributes tab is 'Normal function module'. Also chk the general data, it must be having some name in the Program Name and include name column.try checking the program names in se38, if the program is of type include or not. you can also chk by writting  a program call the function module and test it
    I hope this will solve the query. in my case, SAPLZ123 is the program name and LZ123U28 is the include name.
    or
    Its common prob with Function module.
    Goto SE80->Give Function group name->Right click on it->Activate.
    regards,
    Shweta

  • Error while executing planning Function

    Hi All,
    I'm getting some error while executing planning function. Below are errors. Please check and provide solution.
    Errors occurred when executing planning function RTFMPF01/RTFMPG01
    Value 08 of chara Region does not correspond to the attrib.val MI of chara Store
    Value 10 of chara Region does not correspond to the attrib.val RM of chara Store
    Value 11 of chara Region does not correspond to the attrib.val NA of chara Store
    Thanks,
    Vamsi

    Hi,
    Value 08 of chara Region does not correspond to the attrib.val MI of chara Store
    Looks like there is a characteristics relationship which derives the attribute store from Region.
    Check the master data for Region for attribute Store and the corresponding values.
    The values that are maintained in the master data will only be allowed to enter in the cube.
    Thanks
    pratyush

Maybe you are looking for