ORA-01841 full year must be between .....error when order by

Hi all
i have this query with me ,when order by clause is included ,when it is removed ,i see the output with  so  many record counts
SELECT   porh.segment1,
         CASE
            WHEN popr.action_code = 'APPROVE'
            AND prall.full_name <> 'Sudheer T. Paraputhra'
            AND grdpr.short_name < 'PS-10'
               THEN prall.full_name
         END directman_pr,-----getting names of managers who perform PR approve action
         porh.description, porl.line_num,
         CASE
            WHEN popr.action_code = 'APPROVE'
            AND prall.full_name <> 'Sudheer T. Paraputhra'
            AND grdpr.short_name < 'PS-10'
            AND poph.action_code = 'SUBMIT'
               THEN TO_NUMBER (  TO_CHAR (  TO_DATE ('1', 'J')
                                          + (  poph.action_date
                                             - popr.action_date
                                          'J'
                               - 1
         END days_pr,------------------------------(calculating days from PR approval by manager to PO submit by user)
         poha.segment1 po_num, prall.full_name pr_approved_by,
         popr.action_date pr_approved_date,
         CASE
            WHEN poall_apprv.full_name <> 'Sudheer T. Paraputhra'
            AND grdpo_apprv.short_name < 'PS-10'
            AND poph_apprv.action_code = 'APPROVE'
            AND poph.action_code = 'SUBMIT'
               THEN TO_NUMBER (  TO_CHAR (  TO_DATE ('1', 'J')
                                          + (  poph_apprv.action_date
                                             - poph.action_date
                                          'J'
                               - 1
         END days_po,------calculating days  from PO submit action by user to PO approve action by managers
         popr.sequence_num pr_seq, popr.action_code pr_action,
         poall.full_name po_approved_by, poph.action_date po_approved_date,
         poph.sequence_num po_seq, poph.action_code po_action,
         poph_apprv.action_date po_approved_date_appr,
         poph_apprv.action_code apprv_action_code
    FROM po_requisition_headers_all porh,
         po_requisition_lines_all porl,
         po_req_distributions_all prda,
         po_distributions_all poda,
         po_headers_all poha,
         po_action_history popr,
         po_action_history poph,
         hr.per_all_people_f poall,
         hr.per_all_people_f prall,
         hr.per_all_assignments_f asgpo,
         hr.per_all_assignments_f asgpr,
         per_grades_vl grdpo,
         per_grades_vl grdpr,
         po_headers_all poha_apprv,
         po_distributions_all poda_apprv,
         po_action_history poph_apprv,
         hr.per_all_people_f poall_apprv,
         hr.per_all_assignments_f asgpo_apprv,
         per_grades_vl grdpo_apprv
   WHERE poph.employee_id = poall.person_id
     AND popr.employee_id = prall.person_id
     AND poall.person_id = asgpo.person_id
     AND prall.person_id = asgpr.person_id
     AND asgpr.grade_id = grdpr.grade_id(+)
     AND asgpo.grade_id = grdpo.grade_id(+)
     AND prda.distribution_id = poda.req_distribution_id
     AND poha.po_header_id = poda.po_header_id
     AND prda.requisition_line_id = porl.requisition_line_id
     AND porh.requisition_header_id = porl.requisition_header_id
     AND porh.requisition_header_id = popr.object_id
     AND poph.object_type_code = 'PO'
     AND poha.po_header_id = poph.object_id
     AND SYSDATE BETWEEN poall.effective_start_date AND poall.effective_end_date
     AND SYSDATE BETWEEN prall.effective_start_date AND prall.effective_end_date
     AND SYSDATE BETWEEN asgpo.effective_start_date AND asgpo.effective_end_date
     AND SYSDATE BETWEEN asgpr.effective_start_date AND asgpr.effective_end_date
     AND SYSDATE BETWEEN poall_apprv.effective_start_date
                     AND poall_apprv.effective_end_date
     AND SYSDATE BETWEEN asgpo_apprv.effective_start_date
                     AND asgpo_apprv.effective_end_date
     AND prda.distribution_id = poda_apprv.req_distribution_id
     AND poha_apprv.po_header_id = poda_apprv.po_header_id
     AND poph_apprv.employee_id = poall_apprv.person_id
     AND poall_apprv.person_id = asgpo_apprv.person_id
     AND asgpo_apprv.grade_id = grdpo_apprv.grade_id(+)
     AND poha_apprv.po_header_id = poph_apprv.object_id
     AND poph_apprv.object_type_code = 'PO'
     AND poph_apprv.action_code = 'APPROVE'
ORDER BY 4, 10, 14the calcuation works fine except for when order by clause is inlcuded
kindly help
Edited by: makdutakdu on Jun 1, 2010 2:51 PM

hi Alex,John
even i am confused as to why its happening ,
SELECT   porh.segment1,
         CASE
            WHEN popr.action_code = 'APPROVE'
            AND prall.full_name <> 'Sudheer T. Paraputhra'
            AND grdpr.short_name < 'PS-10'------------< 'PS-10'
               THEN prall.full_name
         END directman_pr,
         porh.description, porl.line_num,
         CASE
            WHEN popr.action_code = 'APPROVE'
            AND prall.full_name <> 'Sudheer T. Paraputhra'
            AND grdpr.short_name < 'PS-10'
            AND poph.action_code = 'SUBMIT'
               THEN TO_NUMBER (  TO_CHAR (  TO_DATE ('1', 'J')
                                          + (  poph.action_date
                                             - popr.action_date
                                          'J'
                               - 1
         END days_pr,
         poha.segment1 po_num, prall.full_name pr_approved_by,
         popr.action_date pr_approved_date,
         CASE
            WHEN poall_apprv.full_name <> 'Sudheer T. Paraputhra'
            AND grdpo_apprv.short_name < 'PS-10'
            AND poph_apprv.action_code = 'APPROVE'
            AND poph.action_code = 'SUBMIT'
               THEN TO_NUMBER (  TO_CHAR (  TO_DATE ('1', 'J')
                                          + (  poph_apprv.action_date
                                             - poph.action_date
                                          'J'
                               - 1
         END days_po,
         popr.sequence_num pr_seq, popr.action_code pr_action,
         poall.full_name po_approved_by, poph.action_date po_approved_date,
         poph.sequence_num po_seq, poph.action_code po_action,
         poph_apprv.action_date po_approved_date_appr,
         poph_apprv.action_code apprv_action_code
    FROM po_requisition_headers_all porh,
         po_requisition_lines_all porl,
         po_req_distributions_all prda,
         po_distributions_all poda,
         po_headers_all poha,
         po_action_history popr,
         po_action_history poph,
         hr.per_all_people_f poall,
         hr.per_all_people_f prall,
         hr.per_all_assignments_f asgpo,
         hr.per_all_assignments_f asgpr,
         per_grades_vl grdpo,
         per_grades_vl grdpr,
         po_headers_all poha_apprv,
         po_distributions_all poda_apprv,
         po_action_history poph_apprv,
         hr.per_all_people_f poall_apprv,
         hr.per_all_assignments_f asgpo_apprv,
         per_grades_vl grdpo_apprv
   WHERE poph.employee_id = poall.person_id
     AND popr.employee_id = prall.person_id
     AND poall.person_id = asgpo.person_id
     AND prall.person_id = asgpr.person_id
     AND asgpr.grade_id = grdpr.grade_id(+)
     AND asgpo.grade_id = grdpo.grade_id(+)
     AND prda.distribution_id = poda.req_distribution_id
     AND poha.po_header_id = poda.po_header_id
     AND prda.requisition_line_id = porl.requisition_line_id
     AND porh.requisition_header_id = porl.requisition_header_id
     AND porh.requisition_header_id = popr.object_id
     AND poph.object_type_code = 'PO'
     AND poha.po_header_id = poph.object_id
     AND SYSDATE BETWEEN poall.effective_start_date AND poall.effective_end_date
     AND SYSDATE BETWEEN prall.effective_start_date AND prall.effective_end_date
     AND SYSDATE BETWEEN asgpo.effective_start_date AND asgpo.effective_end_date
     AND SYSDATE BETWEEN asgpr.effective_start_date AND asgpr.effective_end_date
     AND SYSDATE BETWEEN poall_apprv.effective_start_date
                     AND poall_apprv.effective_end_date
     AND SYSDATE BETWEEN asgpo_apprv.effective_start_date
                     AND asgpo_apprv.effective_end_date
     AND prda.distribution_id = poda_apprv.req_distribution_id
     AND poha_apprv.po_header_id = poda_apprv.po_header_id
     AND poph_apprv.employee_id = poall_apprv.person_id
     AND poall_apprv.person_id = asgpo_apprv.person_id
     AND asgpo_apprv.grade_id = grdpo_apprv.grade_id(+)
     AND poha_apprv.po_header_id = poph_apprv.object_id
     AND poph_apprv.object_type_code = 'PO'
--AND PORH.SEGMENT1='6003' -------when i give a particular PR number it comes out correct even with the order by clause    
AND poph_apprv.action_code = 'APPROVE'
ORDER BY 4, 10, 14when the PORH.SEGMENT1 is commented in oorder to display days for all po/pr i get the error
kindly help me
or is there an alternate calculation to get the number of days
my date is in the format of 4/29/2009 9:13:51 AM
for my caluculation i ve just taken the dates as i require days only kindly help
Edited by: makdutakdu on Jun 2, 2010 7:52 AM

Similar Messages

  • Regarding the error ORA-01841: (full) year must be between -4713 and +9999,

    The issue is the code is not inserting the good records into the MIE table. This is becasue of the error 'OtherError GFSTM_INS_SNURK_NEW_TABLES_PA.gfstm_ins_asn_journal_pr:ORA-01841: (full) year must be between -4713 and +9999, and not be 0' This error is throwing out because of space issue in dt_asn_shipped.
    My requirement is to log error if any if not get the next record in the loop and insert it in the table if it has no error. The issue is good records are not getting inserted. The snurk_cmms_crct018_asn_journl in the cursor is a synonym which uses dblionk to connect to the remote db. The dt_asn_shipped data type is char(6) and the format is YYMMDD.
    declare
    CURSOR cur_asn_journal IS
    SELECT NVL(TRIM(cd_asn_plant),' ') cd_asn_plant,
         NVL(TRIM(no_journal),0) no_journal,
    NVL(TRIM(cd_ship_from),' ') cd_ship_from,
         TRIM(no_asn) no_asn,
    DECODE(LENGTH(dt_asn_shipped),6, to_date(to_char(to_date(trim(dt_asn_shipped),'YYMMDD'),
    'DD-MON-YY'),'DD-MON-YY'), '') dt_asn_shipped,
    TRIM(dt_processed) dt_processed,
    TRIM(in_manual) in_manual,
         TRIM(ts_last_update) ts_last_update     
    FROM snurk_cmms_crct018_asn_journl;
    BEGIN
    FOR l_rec_asn_journal IN cur_asn_journal LOOP
    BEGIN
    INSERT INTO gfstmie_st_cmms_asn_journal
    gsdb_site_code ,
    journal_num,
    gsdb_site_from_code,
    adv_shipping_notice_cnum,
    adv_sn_shipping_date,
    processed_date,
    manual_in_code,
    cmms_last_update_cdate,
    create_userid,
    create_dts,
    update_userid,
    update_dts
    ) VALUES
    l_rec_asn_journal.cd_asn_plant,
    l_rec_asn_journal.no_journal,
    l_rec_asn_journal.cd_ship_from,
    l_rec_asn_journal.no_asn,
    l_rec_asn_journal.dt_asn_shipped,
    l_rec_asn_journal.dt_processed,
    l_rec_asn_journal.in_manual,
    l_rec_asn_journal.ts_last_update,
    g_con_user_id,
         l_dts_current_gmt,
    g_con_user_id,
    l_dts_current_gmt
    EXCEPTION
    WHEN OTHERS THEN
    dbms_output.put_line('l_num_exception_pt_7');
    --To assign value to error attributes
    l_str_email_body := GFSTU_MSG_CONTEXT_STACKER_PA.gfstu_add_msg_context_fn(
    SQLERRM || l_str_process_track,
    g_con_package_name || l_con_proc_name,
    g_con_string_null);
    l_rec_apm_error_attributes.job_run_sakey := l_num_job_run_id;
    l_rec_apm_error_attributes.proj_acronym_code := GFSTM_PARM_SPECIFICATION_PA.g_con_proj_acronym_code_ta;           
    l_rec_apm_error_attributes.module_code := l_con_module_code;
    l_rec_apm_error_attributes.notes_text := l_str_email_body;
    l_rec_apm_error_attributes.msg_id := GFSTM_PARM_SPECIFICATION_PA.g_con_msg_id_invalid_date;
    --Calling procedure to log and notify subscribers of transaction
    --related errors and informational messages
    GFSTM_COMMON_UTL_PA.gfstm_log_message_pr(
    SUBSTR(l_str_email_body,1,2000),
    g_con_string_null,
    g_con_string_null,
    SUBSTR(l_str_email_body,1,2000),
    l_rec_apm_error_attributes,
    g_con_string_null,
    l_num_wait_time,
    l_num_wait_interval_time,
    l_str_msg_action_code,
    l_num_oracle_error_code,
    l_str_oracle_msg,
    l_num_return_code,
    l_num_status);
    END;
    END LOOP;
    WHEN OTHERS THEN
    DBMS_OUTPUT.PUT_LINE('l_num_exception_pt_12');
    DBMS_OUTPUT.PUT_LINE('l_num_exception_pt_2 '||l_str_procg_mode_code);
    --Rollback uncommitted transactions
    ROLLBACK;
    --Assigning failure status
    o_num_status := g_con_status_failure;
    --Assigning procedure end time in GMT
    l_dts_end_time := GFSTU_DATETIME_UTILITIES_PA.gfstu_to_gmt_fn;
    --To assign value to error attributes
    l_str_email_body := GFSTU_MSG_CONTEXT_STACKER_PA.gfstu_add_msg_context_fn(
    SQLERRM || l_str_process_track,
    g_con_package_name || l_con_proc_name,
    g_con_string_null);
    l_rec_apm_error_attributes.job_run_sakey := l_num_job_run_id;
    l_rec_apm_error_attributes.proj_acronym_code := GFSTM_PARM_SPECIFICATION_PA.g_con_proj_acronym_code_ta;           
    l_rec_apm_error_attributes.module_code := l_con_module_code;
    l_rec_apm_error_attributes.notes_text := l_str_email_body;
    l_rec_apm_error_attributes.msg_id := GFSTM_PARM_SPECIFICATION_PA.g_con_msg_id_oracle;
    --Calling procedure to log and notify subscribers of transaction
    --related errors and informational messages
    GFSTM_COMMON_UTL_PA.gfstm_log_message_pr(
    SUBSTR(l_str_email_body,1,2000),
    g_con_string_null,
    g_con_string_null,
    SUBSTR(l_str_email_body,1,2000),
    l_rec_apm_error_attributes,
    g_con_string_null,
    l_num_wait_time,
    l_num_wait_interval_time,
    l_str_msg_action_code,
    l_num_oracle_error_code,
    l_str_oracle_msg,
    l_num_return_code,
    l_num_status);
    --Calling procedure to update the job status
    GFSTM_COMMON_UTL_PA.gfstm_update_job_status_pr(
    l_num_job_run_id,
    GFSTM_PARM_SPECIFICATION_PA.g_con_process_abort,
    l_dts_end_time,
    g_con_perf_metric_code,
    g_con_zero,
    g_con_n,
    l_num_oracle_error_code,
    l_str_oracle_msg,
    l_num_return_code,
    l_num_status);
    END ;
    Thanks,
    Vinodh

    Hi,
    Could you not have reduced your question to what is relevant?
    You seem to be saying that this is your problem:
    SELECT DECODE ( LENGTH (dt_asn_shipped),
              6,
              TO_DATE ( TO_CHAR ( TO_DATE ( TRIM (dt_asn_shipped), 'YYMMDD'), 'DD-MON-YY'), 'DD-MON-YY'),
             dt_asn_shipped
    FROM   snurk_cmms_crct018_asn_journl;As far as I can see, problem might be that you decode on UNTRIMMED length.
    Also, you could get rid of some the to_date(to_char(to_date), which is nothing more than simply to_date()
    Try something like
    SELECT CASE LENGTH (TRIM (dt_asn_shipped))
             WHEN 6 THEN TO_DATE ( TRIM (dt_asn_shipped), 'YYMMDD')
           END
             dt_asn_shipped
    FROM   snurk_cmms_crct018_asn_journl;Regards
    Peter

  • Error ORA-01841: (full) year must be between -4713 and +9999, and not be 0

    Hi Experts,
    I seem to be getting the error "Error ORA-01841: (full) year must be between -4713 and +9999, and not be 0" when my dates are in the year 2000. Here's my SQL:
    DROP TABLE PER_ALL_ASSIGNMENTS_M_XTERN;
    create table PER_ALL_ASSIGNMENTS_M_XTERN(
    PERSON_NUMBER                    VARCHAR2(30 CHAR),
    ASSIGNMENT_NUMBER VARCHAR2(30 CHAR),
    EFFECTIVE_START_DATE                DATE,
    EFFECTIVE_END_DATE           DATE,
    EFFECTIVE_SEQUENCE           NUMBER(4),
    ASS_ATTRIBUTE_CATEGORY           VARCHAR2(30 CHAR),
    ASS_ATTRIBUTE1 VARCHAR2(150 CHAR),
    ASS_ATTRIBUTE_NUMBER20 NUMBER,
    ASS_ATTRIBUTE_DATE1 DATE,
    ASS_ATTRIBUTE_DATE2 DATE,
    ASS_ATTRIBUTE_DATE3 DATE,
    ASS_ATTRIBUTE_DATE4 DATE,
    ASS_ATTRIBUTE_DATE5 DATE,
    ASS_ATTRIBUTE_DATE6 DATE,
    ASS_ATTRIBUTE_DATE7 DATE,
    ASS_ATTRIBUTE_DATE8 DATE,
    ASS_ATTRIBUTE_DATE9 DATE,
    ASS_ATTRIBUTE_DATE10 DATE,
    ASS_ATTRIBUTE_DATE11 DATE,
    ASS_ATTRIBUTE_DATE12 DATE,
    ASS_ATTRIBUTE_DATE13 DATE,
    ASS_ATTRIBUTE_DATE14 DATE,
    ASS_ATTRIBUTE_DATE15 DATE,
    ASG_INFORMATION_CATEGORY           VARCHAR2(30 CHAR),
    ASG_INFORMATION1 VARCHAR2(150 CHAR),
    ASG_INFORMATION_NUMBER20 NUMBER,
    ASG_INFORMATION_DATE1 DATE,
    ASG_INFORMATION_DATE2 DATE,
    ASG_INFORMATION_DATE3 DATE,
    ASG_INFORMATION_DATE4 DATE,
    ASG_INFORMATION_DATE5 DATE,
    ASG_INFORMATION_DATE6 DATE,
    ASG_INFORMATION_DATE7 DATE,
    ASG_INFORMATION_DATE8 DATE,
    ASG_INFORMATION_DATE9 DATE,
    ASG_INFORMATION_DATE10 DATE,
    ASG_INFORMATION_DATE11 DATE,
    ASG_INFORMATION_DATE12 DATE,
    ASG_INFORMATION_DATE13 DATE,
    ASG_INFORMATION_DATE14 DATE,
    ASG_INFORMATION_DATE15 DATE
    organization external
    ( default directory APPLCP_FILE_DIR
    access parameters
    ( records delimited by newline skip 1
         badfile APPLCP_FILE_DIR:'PER_ALL_ASSIGNMENTS_M_XTERN.bad'
    logfile APPLCP_FILE_DIR:'PER_ALL_ASSIGNMENTS_M_XTERN.log'
    fields terminated by ',' OPTIONALLY ENCLOSED BY '"'
    (PERSON_NUMBER,     
    ASSIGNMENT_NUMBER,
    EFFECTIVE_START_DATE CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    EFFECTIVE_END_DATE CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    EFFECTIVE_SEQUENCE,
    ASS_ATTRIBUTE_CATEGORY,
    ASS_ATTRIBUTE1,
    ASS_ATTRIBUTE_NUMBER20,
    ASS_ATTRIBUTE_DATE1 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    ASS_ATTRIBUTE_DATE2 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    ASS_ATTRIBUTE_DATE3 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    ASS_ATTRIBUTE_DATE4 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    ASS_ATTRIBUTE_DATE5 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    ASS_ATTRIBUTE_DATE6 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    ASS_ATTRIBUTE_DATE7 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    ASS_ATTRIBUTE_DATE8 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    ASS_ATTRIBUTE_DATE9 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    ASS_ATTRIBUTE_DATE10 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    ASS_ATTRIBUTE_DATE11 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    ASS_ATTRIBUTE_DATE12 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    ASS_ATTRIBUTE_DATE13 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    ASS_ATTRIBUTE_DATE14 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    ASS_ATTRIBUTE_DATE15 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    ASG_INFORMATION_CATEGORY,
    ASG_INFORMATION1,
    ASG_INFORMATION_NUMBER20,
    ASG_INFORMATION_DATE1 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    ASG_INFORMATION_DATE2 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    ASG_INFORMATION_DATE3 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    ASG_INFORMATION_DATE4 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    ASG_INFORMATION_DATE5 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    ASG_INFORMATION_DATE6 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    ASG_INFORMATION_DATE7 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    ASG_INFORMATION_DATE8 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    ASG_INFORMATION_DATE9 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    ASG_INFORMATION_DATE10 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    ASG_INFORMATION_DATE11 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    ASG_INFORMATION_DATE12 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    ASG_INFORMATION_DATE13 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    ASG_INFORMATION_DATE14 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY",
    ASG_INFORMATION_DATE15 CHAR(20) DATE_FORMAT DATE MASK "DD-MON-YYYY"
    location ('PER_ALL_ASSIGNMENTS_M.csv')
    REJECT LIMIT UNLIMITED;
    ...and getting errors when data looks like the following:
    E040101,EE040101,*1-Aug-2000*,31-Dec-4712,1,,NDVC,YES,DE,SFC,N,STIP Plan - Pressure,,,,,,,E040101,,,,2080,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,5,,,,,,,,,,,,31113,31113,31113,31113,31113,31113,,,1-Jan-2012,31-Dec-2012,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
    ...error message:
    error processing column EFFECTIVE_START_DATE in row 19 for datafile /u05/dbadir/jmf/incident_logs/PER_ALL_ASSIGNMENTS_M.csv
    ORA-01841: (full) year must be between -4713 and +9999, and not be 0
    Thanks,
    Thai

    Here is a snippet of the bad file data:
    E040110,EE040110,01-Aug-00,31-Dec-12,1,,NDVC,YES,DE,SFC,N,STIP Plan - Pressure,,,,,,,E040110,,,,2080,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,5,,,,,,,,,,,,27667.2,27667.2,27667.2,27667.2,27667.2,27667.2,,,01-Jan-12,31-Dec-12,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
    E040100,EE040100,01-May-00,31-Dec-12,1,,NDVC,YES,DE,SFC,N,STIP Plan - Pressure,,,,,,,E040100,,,,2080,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,5,,,,,,,,,,,,31113,31113,31113,31113,31113,31113,,,01-Jan-12,31-Dec-12,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
    E040101,EE040101,01-Aug-00,31-Dec-12,1,,NDVC,YES,DE,SFC,N,STIP Plan - Pressure,,,,,,,E040101,,,,2080,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,5,,,,,,,,,,,,31113,31113,31113,31113,31113,31113,,,01-Jan-12,31-Dec-12,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
    E000916,EE000916,01-Oct-00,31-Dec-12,1,,NDVC,YES,NL,SFC-Commercial,E,SIP Plan - Control Technologies,,,,,,,E000916,21000000,555000,99000,2080,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,10,,,,,,,,,,,,34905.65,34905.65,34905.65,34905.65,34905.65,34905.65,,,01-Jan-12,31-Dec-12,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
    E000807,EE000807,03-Jan-00,31-Dec-12,1,,NDVC,YES,FR,SFC-Commercial,E,STIP Plan - Cross BU,,,,,,,E000807,,,,2080,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,3,,,,,,,,,,,,35448.56,35448.56,35448.56,35448.56,35448.56,35448.56,,,01-Jan-12,31-Dec-12,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
    E000851,EE000851,25-Apr-00,31-Dec-12,1,,NDVC,YES,FR,SFC-Commercial,E,SIP Plan - Control Technologies,,,,,,,E000851,21000000,555000,99000,2080,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,13,,,,,,,,,,,,43283.76,43283.76,43283.76,43283.76,43283.76,43283.76,,,01-Jan-12,31-Dec-12,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
    So, the successfully loaded data is being loaded where year=2003 in the CSV as year=0003. Even though the data is loaded fine the data is not correct. For some reason the external table is set to have the year truncated.

  • ORA-01841 - (full) year must be between -4713 and +9999, and not be 0

    Hi Comunnity,
    Let me explain the scenario:
    We want to replicate a number of Discoverer reports, adding more columns to the reports. Due to the internal structure of the views and materialized tables, we can not make the joins inside the Discoverer Administration Edition, so we have decided to replicate the original materialized table adding the columns in order to get what we want. So the new materialized table has built as follows:
    CREATE TABLE APPS.GUZMAN_STOCK_DEPRE_EXIST_MAT_X
    EMPRESA VARCHAR2(240 BYTE),
    COD_ORGANIZACION NUMBER,
    COD_SECCION VARCHAR2(40 BYTE),
    SECCION VARCHAR2(4000 BYTE),
    FAMILIA VARCHAR2(40 BYTE),
    NOMBRE_PRODUCTO VARCHAR2(240 BYTE),
    DESCRIPCION_ARTICULO VARCHAR2(240 BYTE),
    UNIDAD_EXISTENCIA_ACT NUMBER,
    PRECIO_MEDIO NUMBER,
    FECHA_ULT_VENTA DATE,
    FECHA_ULT_COMPRA DATE,
    FECHA_ULT_MOVIMIENTO DATE,
    PRECIO_ULT_COMPRA NUMBER,
    CLASE_UNIDAD VARCHAR2(40 BYTE),
    COD_ORG_INV NUMBER,
    ORG_INV_NAME VARCHAR2(240 BYTE),
    COD_ARTICULO NUMBER,
    AÑO VARCHAR2(2 BYTE),
    MES VARCHAR2(2 BYTE),
    ULTIMO_DIA_TRANS DATE,
    SEIS_MESES_ANTES DATE,
    DOCE_MESES_ANTES DATE,
    DIECIOCHO_MESES_ANTES DATE,
    SEIS_MESES NUMBER,
    SIETE_DOCE_MESES NUMBER,
    TRECE_DIECIOCHO_MESES NUMBER,
    FCOMVACIA NUMBER,
    TIPO_ARTICULO VARCHAR2(80 BYTE),
    TRANSACTION_ID NUMBER,
    FECHA_MOVIMIENTO DATE,
    TIPO_MOVIMIENTO VARCHAR2(80 BYTE)
    TABLESPACE APPLSYSD
    PCTUSED 40
    NOMONITORING;
    The bold fields are the new ones. So we added the materialized table as a new folder in our working business area and add the following new intems:
    Valor Compra = CASE WHEN Precio Ult Compra = 0 THEN Importe Stocks ELSE Unidad Existencia Act*Precio Ult Compra END
    Importe Stocks = Unidad Existencia Act*Precio Medio
    Depreciación = CASE WHEN Valor Compra < Importe Stocks THEN Importe Stocks-Valor Compra ELSE 0 END
    DiasMes = CASE WHEN ((((((Mes = '01' OR Mes = '03') OR Mes = '05') OR Mes = '07') OR Mes = '08') OR Mes = '10') OR Mes = '12') THEN 31 WHEN (((Mes = '04' OR Mes = '06') OR Mes = '09') OR Mes = '11') THEN 30 ELSE 28 END
    fecha_MES = TO_NUMBER(CONCAT(DiasMes,Mes))
    Nueva_Fecha = TO_DATE(CONCAT(fecha_MES,Ano))
    Dias = NVL(Nueva_Fecha-Fecha Ult Venta,0)
    PorcenDepre = CASE WHEN Dias = 0 AND DiasC < 181 THEN 0 WHEN Dias = 0 AND DiasC > 180 THEN 100 WHEN Dias < 181 THEN 0 WHEN Dias < 361 THEN 25 WHEN Dias < 540 THEN 50 WHEN Dias > 541 THEN 100 ELSE 0 END
    Valor Depr = Valor Compra*PorcenDepre/100
    DiasC = NVL(Nueva_Fecha-Fecha Ult Compra,0)
    PorcenDepreC = CASE WHEN DiasC = 0 THEN 100 WHEN DiasC < 181 THEN 0 WHEN DiasC < 361 THEN 25 WHEN DiasC < 540 THEN 50 WHEN DiasC > 541 THEN 100 ELSE 0 END
    Valor DepreC = Valor Compra*PorcenDepreC/100
    T6 = CASE WHEN Unidad Existencia Act >= SEISMESES THEN SEISMESES ELSE Unidad Existencia Act END
    T12 = CASE WHEN Unidad Existencia Act-T6 > DOCEMESES THEN DOCEMESES WHEN Unidad Existencia Act-T6 < DOCEMESES THEN Unidad Existencia Act-T6 WHEN Unidad Existencia Act-T6 = DOCEMESES THEN Unidad Existencia Act-T6 END
    T18 = CASE WHEN Unidad Existencia Act-( T6+T12 ) > DIECIOCHOMESES THEN DIECIOCHOMESES WHEN Unidad Existencia Act-( T6+T12 ) < DIECIOCHOMESES THEN Unidad Existencia Act-( T6+T12 ) WHEN Unidad Existencia Act-( T6+T12 ) = DIECIOCHOMESES THEN Unidad Existencia Act-( T6+T12 ) END
    TR = Unidad Existencia Act-( T6+T12+T18 )
    DT6 = T6*Precio Medio*0/100
    DT12 = ( T12*Precio Medio )*25/100
    DT18 = T18*Precio Medio*50/100
    DTR = TR*Precio Medio*100/100
    DTOTAL = DT6+DT12+DT18+DTRVCIA+DFCOMPVCIA
    SEISMESES = CASE WHEN NVL(Seis Meses,0) < 0 THEN 0 ELSE NVL(Seis Meses,0) END
    DOCEMESES = CASE WHEN NVL(Siete Doce Meses,0) < 0 THEN 0 ELSE NVL(Siete Doce Meses,0) END
    DIECIOCHOMESES = CASE WHEN NVL(Trece Dieciocho Meses,0) < 0 THEN 0 ELSE NVL(Trece Dieciocho Meses,0) END
    FCOMPVCIA = DECODE(Fecha Ult Compra,NULL,Unidad Existencia Act,0)
    TRVCIA = TR-FCOMPVCIA
    DTRVCIA = TRVCIA*Precio Medio*100/100
    DFCOMPVCIA = FCOMPVCIA*Precio Medio*100/100
    Due to Discoverer does not allow foreign characters (ñ), we have changed the name of Field Año to Ano (as you can check in the Nueva_Fecha calculated field).
    Now, when we select the fields (Empresa, Cod Sección, Nombre Producto, Unidad Existencia Act, Precio Medio, Fecha Ult Venta, Fecha Ult Compra, Fecha Ult Movimiento, Precio Ult Compra, Org Inv Name, Ano, Mes, Valor Compra, Importe Stocks, Depreciación, Dias, PorcenDepre, Valor Depr, DiasC, PorcenDepreC, ValorDepreC) in order to build a new report, Discoverer shows us the ORA-01841 Error.
    Can be produced the error by the way in which discoverer stores the Nueva_Fecha Field?, cause as we check the field in Adminostration Edition, it appears as TO_DATE(CONCAT(fecha_MES,'Ano')) (with the field Ano in simple quotes), or just by any other circumstance?
    Thanks a lot for your help.
    Luis.
    Update:*
    It seems that the problem comes with the item created in Discoverer Administration Edition "Nueva_Fecha":
    Nueva_Fecha = TO_DATE(CONCAT(fecha_MES,Ano))
    (Keep in mind that:
    fecha_MES = TO_NUMBER(CONCAT(DiasMes,Mes))
    DiasMes = CASE WHEN ((((((Mes = '01' OR Mes = '03') OR Mes = '05') OR Mes = '07') OR Mes = '08') OR Mes = '10') OR Mes = '12') THEN 31 WHEN (((Mes = '04' OR Mes = '06') OR Mes = '09') OR Mes = '11') THEN 30 ELSE 28 END
    ), so any created field that uses Nueva_Fecha or is derivated from Nueva_Fecha causes the error (e.g. --> Dias = NVL(Nueva_Fecha-Fecha Ult Venta,0))
    Then; How can we configure the field in order that discoverer deals with it as a date field?
    Regards,
    Luis.
    Edited by: GGOracle User on 27-may-2010 15:23

    Hi,
    I think you forgot the separator in the string you want to convert to date.
    Your problem lies in the format of the date you are trying to create.
    try
    Nueva_Fecha = TO_DATE(DiasMes||'-'||Mes||'-'||Ano ,'DD-MM-YYYY')
    BTW
    you can use || instead of CONCAT so that you can concatenate more than 2 values each time
    Tamir

  • -6502 ORA-06502: PL/SQL: numeric or value error when using 'Create CAPI Definition'

    I get an error when I try to create a CAPI definition with Headstart untilities (6i). I use HSU_CAPI revision 6.5.2.0
    The detailed information says the following:
    Message
    BLAPI.OPEN_ACTIVITY
    Start HSU_CAPI.run
    Number of Tables to create CAPI for 1
    Initial checks for table KCS_TENDERS with id 692754610572409851363604771392473242
    HSU_CAPT.initial_checks for table KCS_TENDERS
    HSU_CAPF.initial_checks for table KCS_TENDERS
    HSU_CAPC.initial_checks Custom Services for table KCS_TENDERS
    HSU_CAPB.initial_checks BRDD for table KCS_TENDERS
    bltext.get_lines_from_repository, p_text_type=CDINOT
    bltext.get_line_containing
    bltext.get_line_containing
    bltext.get_lines_from_repository, p_text_type=CDIPLS
    bltext.get_line_containing
    bltext.get_line_containing
    bltext.get_line_containing
    bltext.get_line_containing
    bltext.get_line_containing
    bltext.get_line_containing
    KCS_TENDERS Business Rule Design Definition BR_TNR001_CEV does not have any Trigger Columns. Rule will fire when any column is updated.
    bltext.get_lines_from_repository, p_text_type=CDINOT
    bltext.get_line_containing
    bltext.get_line_containing
    bltext.get_lines_from_repository, p_text_type=CDIPLS
    bltext.get_line_containing
    bltext.get_line_containing
    bltext.get_line_containing
    bltext.get_line_containing
    bltext.get_line_containing
    bltext.get_line_containing
    Creating CAPI for table KCS_TENDERS with id 692754610572409851363604771392473242
    Recreating KCS_TENDERS Table API/Trigger Logic - Event: Pre-Before-Insert-stmt, Open transaction.
    Write Text for element type APPLOG with id 753236628580304413262318236391196826 - Text type: ALCODE number of text lines = 6 - REPLACE
    Deleted old text
    Write Text for element type APPLOG with id 753236628580304413262318236391196826 - Text type: ALCMNT number of text lines = 1 - REPLACE
    Deleted old text
    Recreating KCS_TENDERS Table API/Trigger Logic - Event: Pre-Before-Update-stmt, Open transaction.
    Write Text for element type APPLOG with id 753236628580332747461215454262479002 - Text type: ALCODE number of text lines = 6 - REPLACE
    Deleted old text
    Write Text for element type APPLOG with id 753236628580332747461215454262479002 - Text type: ALCMNT number of text lines = 1 - REPLACE
    Deleted old text
    Recreating KCS_TENDERS Table API/Trigger Logic - Event: Pre-Before-Delete-stmt, Open transaction.
    Write Text for element type APPLOG with id 753236628580361081660112672133761178 - Text type: ALCODE number of text lines = 6 - REPLACE
    Deleted old text
    Write Text for element type APPLOG with id 753236628580361081660112672133761178 - Text type: ALCMNT number of text lines = 1 - REPLACE
    Deleted old text
    Recreating KCS_TENDERS Table API/Trigger Logic - Event: Post-After-Insert-stmt, Close transaction.
    Write Text for element type APPLOG with id 753236628580389415859009890005043354 - Text type: ALCODE number of text lines = 6 - REPLACE
    Deleted old text
    Write Text for element type APPLOG with id 753236628580389415859009890005043354 - Text type: ALCMNT number of text lines = 1 - REPLACE
    Deleted old text
    Recreating KCS_TENDERS Table API/Trigger Logic - Event: Post-After-Update-stmt, Close transaction.
    Write Text for element type APPLOG with id 753236628580417750057907107876325530 - Text type: ALCODE number of text lines = 6 - REPLACE
    Deleted old text
    Write Text for element type APPLOG with id 753236628580417750057907107876325530 - Text type: ALCMNT number of text lines = 1 - REPLACE
    Deleted old text
    Recreating KCS_TENDERS Table API/Trigger Logic - Event: Post-After-Delete-stmt, Close transaction.
    Write Text for element type APPLOG with id 753236628580446084256804325747607706 - Text type: ALCODE number of text lines = 6 - REPLACE
    Deleted old text
    Write Text for element type APPLOG with id 753236628580446084256804325747607706 - Text type: ALCMNT number of text lines = 1 - REPLACE
    Deleted old text
    Recreating KCS_TENDERS Table API/Trigger Logic - Event: Pre-Before-Delete-row, Save old data.
    Write Text for element type APPLOG with id 753236628580474418455701543618889882 - Text type: ALCODE number of text lines = 404 - REPLACE
    Deleted old text
    Write Text for element type APPLOG with id 753236628580474418455701543618889882 - Text type: ALCMNT number of text lines = 1 - REPLACE
    Deleted old text
    Recreating KCS_TENDERS Table API/Trigger Logic - Event: Pre-Insert, Call CAPI.
    Write Text for element type APPLOG with id 753236628580568865785358936523163802 - Text type: ALCODE number of text lines = 4 - REPLACE
    Deleted old text
    Write Text for element type APPLOG with id 753236628580568865785358936523163802 - Text type: ALCMNT number of text lines = 1 - REPLACE
    Deleted old text
    Recreating KCS_TENDERS Table API/Trigger Logic - Event: Pre-Update, Call CAPI.
    Write Text for element type APPLOG with id 753236628580597199984256154394445978 - Text type: ALCODE number of text lines = 4 - REPLACE
    Deleted old text
    Write Text for element type APPLOG with id 753236628580597199984256154394445978 - Text type: ALCMNT number of text lines = 1 - REPLACE
    Deleted old text
    Recreating KCS_TENDERS Table API/Trigger Logic - Event: Pre-Delete, Call CAPI.
    Write Text for element type APPLOG with id 753236628580625534183153372265728154 - Text type: ALCODE number of text lines = 17 - REPLACE
    Deleted old text
    Write Text for element type APPLOG with id 753236628580625534183153372265728154 - Text type: ALCMNT number of text lines = 1 - REPLACE
    Deleted old text
    Recreating KCS_TENDERS Table API/Trigger Logic - Event: Post-Insert, Call CAPI.
    Write Text for element type APPLOG with id 753236628580653868382050590137010330 - Text type: ALCODE number of text lines = 7 - REPLACE
    Deleted old text
    Write Text for element type APPLOG with id 753236628580653868382050590137010330 - Text type: ALCMNT number of text lines = 1 - REPLACE
    Deleted old text
    Recreating KCS_TENDERS Table API/Trigger Logic - Event: Post-Update, Call CAPI.
    Write Text for element type APPLOG with id 753236628580682202580947808008292506 - Text type: ALCODE number of text lines = 144 - REPLACE
    Deleted old text
    Write Text for element type APPLOG with id 753236628580682202580947808008292506 - Text type: ALCMNT number of text lines = 1 - REPLACE
    Deleted old text
    Recreating KCS_TENDERS Table API/Trigger Logic - Event: Post-Delete, Call CAPI.
    Write Text for element type APPLOG with id 753236628580767205177639461622139034 - Text type: ALCODE number of text lines = 282 - REPLACE
    Deleted old text
    Write Text for element type APPLOG with id 753236628580767205177639461622139034 - Text type: ALCMNT number of text lines = 1 - REPLACE
    Deleted old text
    HSU_CAPF.create_or_find_capi_pack
    hsu_capi.find_plm (kcs_tnr_capi, 692754610572409851363604771392473242, CAPI).
    capi package found in the context folder
    BLPLM.UPD
    FREE_FORMAT_TEXT_FLAG......... = Y
    IMPLEMENTATION_NAME........... = kcs_tnr_capi
    PLSQL_MODULE_TYPE............. = PACKAGE
    SCOPE......................... = PUBLIC
    COMPLETION_STATUS............. = COMPLETED
    NAME.......................... = kcs_tnr_capi
    PURPOSE....................... = Custom API package for implementing Business Rules and supporting TAPI
    Recreated Package KCS/ KCS_TNR_CAPI, preserving only the Revision History.
    HSU_CAPF.add_tags_er_av
    bltext.get_lines_from_repository, p_text_type=CDINOT
    bltext.get_line_containing
    bltext.get_line_containing
    bltext.get_lines_from_repository, p_text_type=CDINOT
    bltext.get_line_containing
    bltext.get_line_containing
    bltext.get_lines_from_repository, p_text_type=CDINOT
    bltext.get_line_containing
    bltext.get_line_containing
    bltext.get_lines_from_repository, p_text_type=CDINOT
    bltext.get_line_containing
    bltext.get_line_containing
    HSU_CAPF.create_specification
    HSU_CAPF.create_c_tabalias
    HSU_CAPF.create_c_tabalias_all
    HSU_CAPF.create_aggregate_value
    HSU_CAPF.create_aggregate_value
    HSU_CAPF.create_aggregate_value
    Activity aborted with ORACLE internal errors.
    -6502 ORA-06502: PL/SQL: numeric or value error: character string buffer too small
    What can I do about it???
    Thanks in advance.
    Menno Hoogsteen

    Working on the same project as Menno, I had the time to look into the problem.
    The problem is caused by the creation of the capi-function agregate_char_value in the packages hsu_capf. While creating this function the following code is executed:
    add(' -- allowable values:');
    add(' -- '||l_col_name_list);
    This last statement causes the problem because this table is very big. L_col_name_list contains 2391 characters wich is 393 characters to long. So i changed this code into:
    add(' -- allowable values:');
    add(' -- '||substr(l_col_name_list,1,1990));
    add(' -- '||substr(l_col_name_list,1990));
    and everything works fine. Perhaps something for a patch?
    Kind regards,
    Ruben Spekle

  • SCSM 2012 UR3 - "The Full adapter threw an exception" error when viewing "Deleted Items" view

    Has anyone expereinced the "The Full adapter threw an exception" eror in the SCSM 2012 console? 
    We get the error in both our dev and production environments when trying to view the "Deleted Items" view in the console (even after using powershell to remove all deleted iterms).  As just noted, interestingly enough we can view, delete, and restore
    deleted items using the corresponding Powershell commands.  It should be noted that neither of our two SCSM 2012 environments has a registered data warehouse server.  Below is a screen shot of the error as well as the associated error text and event
    log errors.
    Any help would be greatly apprecaited!
    Regards,
    JJ
    Console Dialog Error Test
    ============================
    Date: 10/17/2012 8:46:50 PM
    Application: Service Manager Console
    Application Version: 7.5.1561.0
    Severity: Error
    Message: An error occurred while loading the items.
    Microsoft.EnterpriseManagement.UI.ViewFramework.AdvancedListSupportException: The Full adapter threw an exception. See the FullUpdate property to see the exception.
       at Microsoft.EnterpriseManagement.UI.ViewFramework.AdvancedListSupportAdapter.DoAction(DataQueryBase query, IList`1 dataSources, IDictionary`2 parameters, IList`1 inputs, String outputCollectionName)
       at Microsoft.EnterpriseManagement.UI.DataModel.QueryQueue.StartExecuteQuery(Object sender, ConsoleJobEventArgs e)
       at Microsoft.EnterpriseManagement.ServiceManager.UI.Console.ConsoleJobExceptionHandler.ExecuteJob(IComponent component, EventHandler`1 job, Object sender, ConsoleJobEventArgs args)
    Associated Event Log Errors
    ============================
    Log Name:      Application
    Source:        MSSQLSERVER
    Date:          10/17/2012 8:46:49 PM
    Event ID:      8623
    Task Category: Server
    Level:         Error
    Keywords:      Classic
    User:          SYSTEM
    Computer:      jhqsrv08.jhq.net
    Description:
    The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected for extremely complex queries or queries that reference a very large number of tables or partitions. Please simplify the query. If you
    believe you have received this message in error, contact Customer Support Services for more information.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSSQLSERVER" />
        <EventID Qualifiers="49152">8623</EventID>
        <Level>2</Level>
        <Task>2</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2012-10-18T00:46:49.000000000Z" />
        <EventRecordID>339617</EventRecordID>
        <Channel>Application</Channel>
        <Computer>jhqsrv08.jhq.net</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Binary>AF21000010000000090000004A00480051005300520056003000380000000F00000053006500720076006900630065004D0061006E0061006700650072000000</Binary>
      </EventData>
    </Event>
    Log Name:      Operations Manager
    Source:        DataAccessLayer
    Date:          10/17/2012 8:46:49 PM
    Event ID:      33333
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      jhqsrv08.jhq.net
    Description:
    Data Access Layer rejected retry on SqlError:
     Request: MTV_Select_62f0be9f-ecea-e73c-f00d-3dd78a7422fc_Top -- (NonGenericDistinctFilterForAbstract=4cf77750-6688-8672-9470-036e0f4b48d6,26b2dff7-2ce9-59cf-4eb8-a6fb2d095d45,89992420-1297-0b8b-f3ca-1e53aa36f9e0,ed5ec2bf-6745-086...), (ObjectStatus_4AE3E5FE_BC03_1336_0A45_80BF58DEE57B0=47101e64-237f-12c8-e3f5-ec5a665412fb)
     Class: 16
     Number: 8623
     Message: The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected for extremely complex queries or queries that reference a very large number of tables or partitions. Please simplify
    the query. If you believe you have received this message in error, contact Customer Support Services for more information.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="DataAccessLayer" />
        <EventID Qualifiers="32768">33333</EventID>
        <Level>3</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2012-10-18T00:46:49.000000000Z" />
        <EventRecordID>935685</EventRecordID>
        <Channel>Operations Manager</Channel>
        <Computer>jhqsrv08.jhq.net</Computer>
        <Security />
      </System>
      <EventData>
        <Data>MTV_Select_62f0be9f-ecea-e73c-f00d-3dd78a7422fc_Top -- (NonGenericDistinctFilterForAbstract=4cf77750-6688-8672-9470-036e0f4b48d6,26b2dff7-2ce9-59cf-4eb8-a6fb2d095d45,89992420-1297-0b8b-f3ca-1e53aa36f9e0,ed5ec2bf-6745-086...),
    (ObjectStatus_4AE3E5FE_BC03_1336_0A45_80BF58DEE57B0=47101e64-237f-12c8-e3f5-ec5a665412fb)</Data>
        <Data>16</Data>
        <Data>8623</Data>
        <Data>The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected for extremely complex queries or queries that reference a very large number of tables or partitions.
    Please simplify the query. If you believe you have received this message in error, contact Customer Support Services for more information.</Data>
      </EventData>
    </Event>
    Log Name:      Operations Manager
    Source:        OpsMgr SDK Service
    Date:          10/17/2012 8:29:26 PM
    Event ID:      26319
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      jhqsrv08.jhq.net
    Description:
    An exception was thrown while processing GetManagedEntitiesByManagedEntityTypesAndCriteriaWithInstanceQueryOptions for session ID uuid:66ba50da-cdce-4d15-823c-92c41b46fe44;id=2425.
     Exception message: The creator of this fault did not specify a Reason.
     Full Exception: System.ServiceModel.FaultException`1[Microsoft.EnterpriseManagement.Common.UnknownDatabaseException]: The creator of this fault did not specify a Reason. (Fault Detail is equal to The query processor ran out of internal resources and could
    not produce a query plan. This is a rare event and only expected for extremely complex queries or queries that reference a very large number of tables or partitions. Please simplify the query. If you believe you have received this message in error, contact
    Customer Support Services for more information.).
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="OpsMgr SDK Service" />
        <EventID Qualifiers="49152">26319</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2012-10-18T00:29:26.000000000Z" />
        <EventRecordID>935679</EventRecordID>
        <Channel>Operations Manager</Channel>
        <Computer>jhqsrv08.jhq.net</Computer>
        <Security />
      </System>
      <EventData>
        <Data>GetManagedEntitiesByManagedEntityTypesAndCriteriaWithInstanceQueryOptions</Data>
        <Data>uuid:66ba50da-cdce-4d15-823c-92c41b46fe44;id=2425</Data>
        <Data>The creator of this fault did not specify a Reason.</Data>
        <Data>System.ServiceModel.FaultException`1[Microsoft.EnterpriseManagement.Common.UnknownDatabaseException]: The creator of this fault did not specify a Reason. (Fault Detail is equal to The query processor ran out of internal resources
    and could not produce a query plan. This is a rare event and only expected for extremely complex queries or queries that reference a very large number of tables or partitions. Please simplify the query. If you believe you have received this message in error,
    contact Customer Support Services for more information.).</Data>
      </EventData>
    </Event>

    I have the same problem and get following error:
    An exception was thrown while processing GetManagedEntitiesByManagedEntityTypesAndCriteriaWithInstanceQueryOptions
    I have contacted MS Support, but hey could not help
    either.
    I really
    need to fix it. Any help?

  • "caching-descriptor" must be declared error when using ejbc on WLS6.0 with EJB 1.1

    I'm compiling with ejbc an entity bean .jar. Using WLS 6.0. In the ejb-jar.xml,
    I've set version to EJB 1.1. I've made sure the weblogic-ejb-jar.xml has the caching-descriptor
    element defined (used to work with WLS 5.1).
    Thanks.
    Sayid
    Error is : org.xml.sax.SAXParseException: Element type "caching-descriptor" must
    be declare d. at weblogic.apache.xerces.framework.XMLParser.reportError(XMLParser.java
    :1008) at weblogic.apache.xerces.validators.common.XMLValidator.reportRecoverab
    leXMLError(XMLValidator.java:1236) at weblogic.apache.xerces.validators.common.XMLValidator.validateElement
    AndAttributes(XMLValidator.java:2673) at weblogic.apache.xerces.validators.common.XMLValidator.callStartElemen
    t(XMLValidator.java:818) at weblogic.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher
    .dispatch(XMLDocumentScanner.java:1222) at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocu
    mentScanner.java:380) at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:900)
    at weblogic.xml.process.ProcessorDriver.process(ProcessorDriver.java:128 ) at
    weblogic.ejb20.dd.xml.WebLogicEjbJarLoader_WLS600.process(WebLogicEjb JarLoader_WLS600.java:455)
    at weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:9 3) at
    weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:4 7) at weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:3
    8) at weblogic.ejbc20.runBody(ejbc20.java:665) at weblogic.utils.compiler.Tool.run(Tool.java:81)
    at weblogic.ejbc.main(ejbc.java:20) --------------- nested within: ------------------
    weblogic.xml.process.XMLParsingException: Element type "caching-descriptor" must
    be declared. - with nested exception: [org.xml.sax.SAXParseException: Element
    type "caching-descriptor" must be declar ed.] Line: 8 Column: 27 at weblogic.xml.process.ProcessorDriver.process(ProcessorDriver.java:132
    ) at weblogic.ejb20.dd.xml.WebLogicEjbJarLoader_WLS600.process(WebLogicEjb JarLoader_WLS600.java:455)
    at weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:9 3) at
    weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:4 7) at weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:3
    8) at weblogic.ejbc20.runBody(ejbc20.java:665) at weblogic.utils.compiler.Tool.run(Tool.java:81)
    at weblogic.ejbc.main(ejbc.java:20) ERROR: weblogic.xml.process.XMLParsingException:
    Element type "caching-descripto r" must be declared. - with nested exception:
    [org.xml.sax.SAXParseException: Element type "caching-descriptor" must be declar
    ed.] Line: 8 Column: 27

    but a bean's deployment descriptor lies in the
    meta-inf folder, right?Sorry, my mistake. I was thinking of WAR files while writing. Thanks for pointing out.
    Regards,
    $ Carol.

  • How to fix "Must be literal" error when using a4j:keepAlive tag?

    Hi everybody,
    When I use <a4j:keepAlive> tag of Richfaces like this:
    <a4j:keepAlive beanName="#{templateController.currentType}"/>I got the an error like this:
    /templates.xhtml @20,91 <a4j:keepAlive beanName="#{templateController.currentType}"> Must be literalIn my class, I have declared as:
    class TemplateController{
        private TemplateType currentType;
        public void setCurrentType(TemplateType type) {
        public TemplateType getCurrentType() {
    }I implemented as guide from Richfaces document but don't know why this happened.
    Could anyone tell me why? Please help me to fix it.
    I really appreciate it,
    Ringo
    Edited by: Ringo.CS on Jun 19, 2008 3:42 AM
    Edited by: Ringo.CS on Jun 19, 2008 3:43 AM

    No, the error message says that the value must be a literal and thus not an EL. I don't know anything about Ajax4jsf (you're in the wrong place to ask questions about it, rather use the forums of the Ajax4jsf manfacturer at jboss.com), but the attributename and errormessage together makes it logical to put just the raw managed bean name in there. If this is not what you're after, then just consult their documentation and forums at jboss.com.

  • Why an "ORA-01006: bind variable does not exist" error when no dynamic SQL?

    Hi all,
    While running PL/SQL in SQL Developer 3.2.09, I got the following error after adding a section of code. Note that nothing I'm doing has anything to do with dynamic SQL (which is what 01006 is supposedly about).
    Error report:
    ORA-01006: bind variable does not exist
    01006. 00000 - "bind variable does not exist"
    *Cause:   
    *Action:
    After commenting out the new chunk of code that caused the error, the error persisted.
    After deleting the new code, the error went away.
    What the heck!?!? If you have any ideas, please lay 'em on me.
    Thanks so much,
    Kim
    P.S. It's a few hundred lines of code, so I didn't append it to this post and I don't see how to attach a file.

    Let's review a few facts:
    1. You post a question in the sql developer forum that has no apparent relation to sql developer. You could confirm this by doing the test using sql*plus or some other tool.
    2. You provide NO information about what database you are even using. The only clue is an ORA -xxx message that means SOME version of Oracle is involved.
    3. You provide NO information about what the four digit version of Oracle DB is being used.
    4. You provide NO information about what the code in general or what that specific section of the code is even doing. The code could be doing literally anything that Oracle is capable of doing.
    That's a bit like calling a mechanic you don't know, telling them your car is making a funny noise and asking them what the problem with your car is.
    >
    While running PL/SQL in SQL Developer 3.2.09, I got the following error after adding a section of code. Note that nothing I'm doing has anything to do with dynamic SQL (which is what 01006 is supposedly about).
    Error report:
    ORA-01006: bind variable does not exist
    01006. 00000 - "bind variable does not exist"
    *Cause:
    *Action:
    The error gives no indication of where the error occurred in the code.
    >
    Your first clue that your troubleshooting method is seriously flawed is when you make statements that aren't supported by any evidence at all but appear to be nothing but your opinion.
    Your second clue is when those statements appear to directly contradict what Oracle is telling you.
    I'm talking about these two statements you make; which you state as if they were universal truths
    >
    nothing I'm doing has anything to do with dynamic SQL
    (which is what 01006 is supposedly about).
    >
    If thoe were true then your 'unstated' conclusion appears to be that Oracle is wrong in saying 'bind variable does not exist'
    Sorry - but I would place my money on Oracle.
    I'm sure the above may sound harsh - it is intended to be. My four major rules (there are more) when troubleshooting Oracle problems.
    1. Assume that Oracle is CORRECT when it tells you there is a problem.
    2. Assume that you are WRONG if your opinion conflicts with what Oracle is telling you - see rule #1.
    3. Don't make ANY other assumptions. You can form hypotheses but don't state them as facts until they are proven.
    4. Your 'opinion' is only useful to the extent that it can help you form meaningful hypotheses - see rule #3.
    >
    To reiterate, there is no dynamic SQL in the code.
    >
    To reiterate - if, as you state, that error relates to dynamic SQL and bind variables then it can not be disputed that:
    ORACLE DOESN'T AGREE WITH YOU!
    So let's try it my way and hypothesize that Oracle is correct (see rule #1 above).
    Then by definition this statement by Oracle is correct
    >
    ORA-01006: bind variable does not exist
    >
    And that should immediately raise this question:
    1. where might there be a bind variable that does not exist?
    which leads to a prerequisite question:
    2. where are ALL of the bind variables that might be being used?
    Question #2 is where you need to start your search. Here are at least five possibilities (there are more)
    1. your code - this should be easiest to check and you state that your 'anonymous' block does not have any.
    2. a table trigger - triggers that use the :NEW, :OLD or :PARENT pseudocolumns. Those psuedocolumns are BIND variables and the trigger code that uses them is, by definition, dynamic sql.
    3. a pl/sql package/function/procedure - any of these might be being called from trigger code or a view that is involved in the transaction. Any of these could take a parameter and/or use bind variables and cause your problem if that bind variable does 'not exist'.
    4. a functional index - can also trigger code from #3 above
    5. an audit trigger that logs the audit activity that your user or your code is performing. This code could be trying to use a SYS_CONTEXT environment variable that has not been created and cause a 'bind variable does not exist' error.
    See rule #1 - Oracle is CORRECT. Until you have identified and examined ALL of the code (not just your anonymous block) being executed and ruled it out you should continue with the hypotheses that Oracle is CORRECT.
    In the (extremely) unlikely event that you can show that Oracle is NOT correct you should file a SOR with Oracle.

  • Cookies must be enabled error when attempting to login into Apps

    I have the accept cookies set to from visited and also tried always.  I can't log into apps on my ipad.  : (

    I deleted cookies and browser history.  I launched Safari browsed to espn.com and randomly clicked on a few links within the site.  I then launched the espn app and I was able to sign in without the cookie error. 

  • I have bought a full TV series, but says error when i  try and continue download?

    I bought a whole television series but the last 7 episodes wont download, help?

    Hi there,
    You may find the articles below helpful.
    iTunes: How to resume interrupted iTunes Store downloads
    http://support.apple.com/kb/ht1725
    Downloading past purchases from the App Store, iBookstore, and iTunes Store
    http://support.apple.com/kb/HT2519
    -Griff W.

  • SRM and SRM-MDM: Error when ordering less than Price Base Quantity

    Hi!
    We face the following issue:
    We have an item without material master in the MDM-catalog. The price is scaled, and 5.00 EUR up to 100 items, and 4.80 EUR for more than 100 items
    If we order 90 items, the price is calculated to 5.00 EUR in MDM, BUT the price is displayed as 0.00 EUR per 100 items when transferred to SRM. The price is also 0.00 when transferring to SAP ERP backend.
    If we order 100 items or more, the price is calculated correctly in MDM, and also transferred correctly to SRM and ERP. This also applies if we order e.g.  110 items - everyting looks correct (price for 110 is 5.28 EUR).
    AND: in both cases, we can observe the price is correct in the OCI !
    So, something happens in SRM if we order less than the Price Base Quantoty
    SRM5.0, SRM-MDM 2.0
    Since the price is correct in the OCI we would suspect the error to be somewhere in SRM? Any ideas?
    brgs ziggy
    Edited by: ziggy ziggy on Oct 27, 2009 10:35 AM

    Hello Ziggy,
    Could you please check OSS notes 1311046 and 1296024.
    We found OSS note 1339905 and in the correction instructions were quite a few notes relating to a '0' price issue.
    Obviously I don't know on which support pack level you're on.
    Good luck,
    Franz

  • Error when ordering book -

    NSPlaceholderMutableString initWithString nil argument
    I ordered one with no problem, but second one gets this error every time i place an order.

    Same problem. The book almost finishes transferring, then I get a message that "an error occurred with one of the files. Check network, etc." My network is fine, however. Any ideas?

  • Server error when order PO

    Hi,
    We have one portal system and one SRM system. Both are connected trough one NAM acelerator, which is set in the portal SRM system definition (System administration -> system configuration -> portal andscape).
    We can open and edit any PO without problems but when we press the order button we obtain this error:
    Server error!
    And no dump appears in the portal log neither in the SRM logs.
    So any idea why is this happening?
    Thanks a lot and best regards, sapera

    hi,
    It was a problem with the harcode table.
    Bea

  • Network error when ordering prints

    I have been trying to order prints of over 1,000 of my photos and they appear to upload just fine and I am able to put in 1 4x6 on all photos. Then, it goes to a grey connecting line, which eventually turns blue. After awhile I get the network error message. I've tried several times over the last week to order the pictures and the same thing happens each time. Is there a limit to how many you can order at once? Do I need to split my order into two separate orders?

    Welcome to the Apple Discussions. You very well may be getting timed out on the upload/order process. I'd try splitting the order in two and see if that will go thru unimpeded.
    TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto (iPhoto.Library for iPhoto 5 and earlier) database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
    I've created an Automator workflow application (requires Tiger or later), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 6 and 7 libraries and Tiger and Leopard. Just put the application in the Dock and click on it whenever you want to backup the dB file. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.
    Note: There's now an Automator backup application for iPhoto 5 that will work with Tiger or Leopard.

Maybe you are looking for