Problems creating a job

hi
I have package with a procedure naming do_job which have to create a job using
dbms_job.submit the owner of this package is a user named "HOL" , but when I try to run this package (I create a public synonym for the package and I gave execute grant to "DES") with another user like "DES" does not create the job.
Can any body help me
Thanks

Hi,
For job scheduling tips and samples, you cannot beat Dr. Tim Hall:
http://www.oracle-base.com
He also has a book "Oracle Job Scheduling" with lots of working job scheduling examples, very nice:
http://www.rampant-books.com/book_2005_1_scheduling.htm
HTH . . .
Don Burleson
"root hog or die"

Similar Messages

  • Problems creating background job for program (job open, submit and close)

    Hi gurus,
    im trying to start a background job using the FM BP_START_DATE_EDITOR to show the start date to the job or if it's imediate. this FM it's working fine, after call it im opening a job, submiting it and call the job close FM and the job close FM creates me the job.
    The problem it's when i go to the sm37 to see the job status the job has been canceled, and the job log says that i have to give a start date to the job.
    What i dont understand it's either the job is imediate or i choose a date to start the job always gives me this error...
    Below goes my code,
    any ideas will be rewarded
      CLEAR: stdt_modify_type, stdt_output.
      CALL FUNCTION 'BP_START_DATE_EDITOR'
           EXPORTING
                stdt_dialog                    = 'Y'
                stdt_input                     = stdt_input
                stdt_opcode                    = 14
           IMPORTING
                stdt_modify_type               = stdt_modify_type
                stdt_output                    = stdt_output
           EXCEPTIONS
                fcal_id_not_defined            = 1
                incomplete_last_startdate      = 2
                incomplete_startdate           = 3
                invalid_dialog_type            = 4
                invalid_eventid                = 5
                invalid_opcode                 = 6
                invalid_opmode_name            = 7
                invalid_periodbehaviour        = 8
                invalid_predecessor_jobname    = 9
                last_startdate_in_the_past     = 10
                no_period_data_given           = 11
                no_startdate_given             = 12
                period_and_predjob_no_way      = 13
                period_too_small_for_limit     = 14
                predecessor_jobname_not_unique = 15
                startdate_interval_too_large   = 16
                startdate_in_the_past          = 17
                startdate_is_a_holiday         = 18
                startdate_out_of_fcal_range    = 19
                stdt_before_holiday_in_past    = 20
                unknown_fcal_error_occured     = 21
                no_workday_nr_given            = 22
                invalid_workday_countdir       = 23
                invalid_workday_nr             = 24
                notbefore_stdt_missing         = 25
                workday_starttime_missing      = 26
                no_eventid_given               = 27
                OTHERS                         = 28.
      IF sy-subrc <> 0.
        MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        MOVE 'X' TO gv_flag.
      ENDIF.
      DATA jobname LIKE tbtcjob-jobname.
      DATA jobcount LIKE tbtcjob-jobcount.
      DATA job_release LIKE  btch0000-char1.
      DATA job_imediate TYPE c.
      CLEAR: jobname, jobcount, job_release.
      CONCATENATE 'MAPAEXEC' sy-uname sy-datum
                   INTO jobname SEPARATED BY space.
      CALL FUNCTION 'JOB_OPEN'
           EXPORTING
                jobname          = jobname
           IMPORTING
                jobcount         = jobcount
           EXCEPTIONS
                cant_create_job  = 1
                invalid_job_data = 2
                jobname_missing  = 3
                OTHERS           = 4.
      IF sy-subrc <> 0.
        MESSAGE i003(zmapas).
        EXIT.
      ENDIF.
      SUBMIT z_mapa_execucao_orcamental
             VIA JOB jobname NUMBER jobcount
             WITH ano EQ ano
             WITH so_perio IN so_perio
             WITH so_date IN so_date
             WITH so_org EQ so_org
             WITH so_num IN so_num
             AND RETURN.
      IF stdt_output-startdttyp EQ 'I'.
        CLEAR job_imediate.
        job_imediate = 'X'.
      ENDIF.
      CALL FUNCTION 'JOB_CLOSE'
           EXPORTING
                calendar_id                 = stdt_output-calendarid
                event_id                    = stdt_output-eventid
                event_param                 = stdt_output-eventparm
                event_periodic              = stdt_output-periodic  "?
                jobcount                    = jobcount
                jobname                     = jobname
                laststrtdt                  = stdt_output-laststrtdt
                laststrttm                  = stdt_output-laststrttm
                prddays                     = stdt_output-prddays  "??
                prdhours                    = stdt_output-prdhours  "?
                prdmins                     = stdt_output-prdmins  "??
                prdmonths                   = stdt_output-prdmonths
                prdweeks                    = stdt_output-prdweeks  "?
                predjob_checkstat           = stdt_output-checkstat
                pred_jobcount               = stdt_output-predjobcnt
                pred_jobname                = stdt_output-predjob
                sdlstrtdt                   = stdt_output-sdlstrtdt
                sdlstrttm                   = stdt_output-sdlstrttm
                strtimmed                   = job_imediate
                targetsystem                = stdt_output-instname
                start_on_workday_not_before = stdt_output-notbefore
                start_on_workday_nr         = stdt_output-wdayno
                workday_count_direction     = stdt_output-wdaycdir
           IMPORTING
                job_was_released            = job_release
           EXCEPTIONS
                cant_start_immediate        = 1
                invalid_startdate           = 2
                jobname_missing             = 3
                job_close_failed            = 4
                job_nosteps                 = 5
                job_notex                   = 6
                lock_failed                 = 7
                OTHERS                      = 8.
      IF sy-subrc <> 0.
        MESSAGE i003(zmapas).
        EXIT.
      ELSE.
        MESSAGE i004(zmapas) WITH jobname.
      ENDIF.
    Thanks in advance,
    Best Regards
    João Martins

    Hello João.
    In debug mode, check the value of variables you passed to parameters sdlstrtdt and sdlstrttm.
    As aditional info, I usually achieve your goal without FM BP_START_DATE_EDITOR.
    Check this code:
    CALL FUNCTION 'JOB_OPEN'
          EXPORTING
               jobname          = w_jobname
          IMPORTING
               jobcount         = w_jobcount
          EXCEPTIONS
               cant_create_job  = 1
               invalid_job_data = 2
               jobname_missing  = 3
               OTHERS           = 4.
    CHECK sy-subrc = 0.
    CLEAR seltab_wa.
    MOVE: t_jobs-param TO seltab_wa-selname,
    t_processar-line+34 TO seltab_wa-low.
    APPEND seltab_wa TO seltab.
    seltab_wa-selname = 'P_LOJA'.
    seltab_wa-low = t_processar-ficheiro+7(4).
    APPEND seltab_wa TO seltab.
    *** Submete o programa para o JOB
    SUBMIT (t_jobs-repid)
      WITH  SELECTION-TABLE seltab
      USER sy-uname
       VIA JOB w_jobname NUMBER w_jobcount
       AND RETURN.
    *** Encerra o JOB
      l_hora = sy-uzeit.
      ADD 60 TO l_hora.
    CALL FUNCTION 'JOB_CLOSE'
       EXPORTING
          jobcount           = w_jobcount
          jobname           = w_jobname
          sdlstrtdt            = sy-datum
          sdlstrttm           = l_hora
          targetserver       = w_servidor
       IMPORTING
          job_was_released     = l_liberado
       EXCEPTIONS
          cant_start_immediate = 1
          invalid_startdate    = 2
          jobname_missing      = 3
          job_close_failed     = 4
          job_nosteps          = 5
          job_notex            = 6
          lock_failed          = 7
          OTHERS               = 8.
    Regards.
    Valter Oliveira.

  • Execution problem while creating a job

    Hi,
    I have written a procedure to generate a csv file to a destination ( procedure name - sp_write_to_file).
    I have created a job for this procedure to be executed after every 2 minutes using the package dbms_job as follows;
    sql>VARIABLE jobno NUMBER;
    sql>execute DBMS_JOB.SUBMIT(:jobno,'sp_emp_write_file;',INTERVAL =>
    'SYSDATE+(2/24/60)');
    ---- I got a successful execution message as;
    PL/SQL procedure successfully completed.
    But the file is not getting generated.
    When i execute the job manually as;
    exec dbms_job.run(25); --- i got the job number as 25.
    Then the file gets created.
    What is the error ?
    plz guide.

    How about:
    execute DBMS_JOB.SUBMIT(25,'sp_emp_write_file;',INTERVAL => 'SYSDATE+(2/24/60)');
    commit;Also I'm not sure about the interval. Maybe you don't have to enter the interval as a string.
    Message was edited by:
    Sven W.

  • How to create a job card and how to add waranty card in sales order

    I have one scenario for CS.the scenario is realted to automotive industry. Basically its a trading industry of HCV,MCV,LCV apart from that they will do servicing also. First the customer comes for a service.he is having free services. he will have waranty for spare parts of the vehicle. once he comes for servicing first the executive will take complains from the customer after that a Job card will be issued to the customer. there his chasis no ,engine no and registration no will be there. once enter the chasis no entire customer details has to come. how many free services he is having for how many kilo meters.then job card will go to the spare parts dept.that dept will issue the spare parts.then they will invoice the customer. he will pay the payment.and finally the gate pass will be given to the customer to deliver the vehicle.
    painful area is how to create a job card and how to add waranty in sales order.
    Regards,
    Venkat

    Hi,
    Have u resolved it then Please let me know !!! It is a very interesting problem and owuld like to know the solution...
    Regards
    Krishna

  • Create Background Job after data saved in module

    Hello,
    I have a program that has a start selection screen with material group, you enter your data, execute.  When it has finished you get a ALV of sales order with items where you can make changes to dates and other details and save.  I would like to add a save in background option.  Is this possible? I assume it would be difficult because of the container.. it uses a bapi to save sale orders...
    The employees run this job which takes a little while.. at the end of the day.. they go home and of course SAP has timed out.  If they can run it in the background then no problem....
    Thanks,
    AJ

    well, you can pass the data from the same to an other program and submit it in background.
    Just create a job.
    CALL FUNCTION 'JOB_OPEN'
           EXPORTING
                jobname          = gv_jobname
           IMPORTING
                jobcount         = gv_jobcount
           EXCEPTIONS
                cant_create_job  = 1
                invalid_job_data = 2
                jobname_missing  = 3
                OTHERS           = 4.
      IF sy-subrc <> 0.
    *   no error required
      ENDIF.
    submit your program with job name and job count.
    CALL FUNCTION 'JOB_CLOSE'
           EXPORTING
                jobcount             = gv_jobcount
                jobname              = gv_jobname
                strtimmed            = 'X'
           EXCEPTIONS
                cant_start_immediate = 1
                invalid_startdate    = 2
                jobname_missing      = 3
                job_close_failed     = 4
                job_nosteps          = 5
                job_notex            = 6
                lock_failed          = 7
                OTHERS               = 8.
      IF sy-subrc <> 0.

  • Problems with background job

    Hi,
    I have problems when creating a job that is supposed to be run once in background. I use the common steps as described below. My problem is that the report is executed twice.
    - First it is executed synchronously when the job is created
    - Then it is executed in the normal job step as I want it to do
    I don't want it to be executed the first time because it creates data!!!
    Code:
    CALL FUNCTION 'JOB_OPEN'
         EXPORTING
              jobname  = w_jobid
         IMPORTING
              jobcount = w_jobnr
              sdlstrtdt = sy-datum
              sdlstrttm = sy-uzeit.
    SUBMIT (p_prog)
    WITH p_idocnr = p_idocno
               USER            p_user
               VIA   JOB       w_jobid
                     NUMBER  w_jobnr
                     AND       RETURN.
    CALL FUNCTION 'JOB_CLOSE'
         EXPORTING
              jobcount         = w_jobnr
              jobname          = w_jobid
              strtimmed        = 'X'
         IMPORTING
              job_was_released = w_jobrel.
    Does anyone have a clue of what I should do to prevent this?
    //  Regards  Hans

    Hi again,
    1. U are right.
    2. It will happen if we use SUBMIT.
    3. As per the help documentation,
        it will run the program in separate session,
       ( as soon as submit statement comes)
    4. and run the INITIALIZATION event.
    The VIA JOB addition also loads the program accessed in a separate internal mode when the SUBMIT statement is executed and the system performs all the steps specified before START-OF-SELECTION. This means the events LOAD-OF-PROGRAM and INITIALIZATION are triggered and selection screen processing is performed. If the selection screen is not processed in the background when VIA SELECTION-SCREEN is specified, the user of the calling program can eidit it and schedule the program accessed in the background request using the function Place in Job. If the user cancels selection screen processing, the program is not scheduled in the background job. In both cases, execution of the program executed is completed after selection screen processing and the system returns to the calling program due to the AND RETURN statement.
    regards,
    amit m.

  • Creating a Job to execute a .sh file

    Hi,
    I have an important issue creating a Job to execute a .sh file,
    the .sh (start_execution.sh) contains a lot of random calls like this:
    #!/bin/bash
    . /home/crm/.bash_profile
    . /home/crm/argentina/crm/crmdw/clusters/mt/mt_pull_push/start.sh
    . /home/crm/argentina/crm/crmdw/clusters/ota/ota/start.sh
    sqlplus dware/argu01@crmarg @/home/crm/crmdw/AR/exec_dw.sql "MT"
    sqlplus dware/argu01@crmarg @/home/crm/crmdw/AR/exec_dw.sql "OTA"
    sqlplus dware/argu01@crmarg @/home/crm/crmdw/AR/exec_dm.sql "DAILY_DOWNLOADS"then creating the next job
    Begin
    dbms_scheduler.create_job
    (job_name=>'job_AR',
    job_action=>'/home/crm/crmdw/AR/start_execution.sh',
    number_of_arguments=>1,
    job_type=>'executable',
    start_date => SYSDATE,
    repeat_interval => 'FREQ=MINUTELY; INTERVAL=20',
    enabled=>false,
    auto_drop => TRUE,
    comments=> 'Run shell-script test_dbms_scheduler.sh');
    dbms_scheduler.set_job_argument_value(job_name =>'job_AR', argument_position => 1, argument_value => 'Parameter passed from Oracle to Unix');
    dbms_scheduler.enable('job_AR');
    end;
    /the system executes all process at the same time instead of one to one,
    Is necessary the system executes one to one becouse is a Hierarchy of process with
    corresponding dependencies.
    what could I do to resolve the issue??
    any ideas??
    Thanks in advanced...

    the problem is the content of the .sh file(start_execution.sh) is generated ramdomly and automatically and the code is :
    FUNCTION F_GET_EXECUTION_PLAN
        CONN_STRING_TRG VARCHAR2--'dwa/arg@arg'
      , EXEC_TEMP_DIR VARCHAR2--'/home/crm/crmdw/AR/'
      ) RETURN CLOB AS
      BEGIN
      DECLARE
        v_conn_string_trg VARCHAR2(255);
        v_exec_temp_dir VARCHAR2(255);
        v_select_aux VARCHAR2(32767);
        v_select CLOB := ' ';
        v_process_type VARCHAR2(5);
        v_process_name VARCHAR2(50);
        v_location VARCHAR2(255);
        v_result NUMBER := 0;   
        TYPE t_array IS TABLE OF VARCHAR2(255);
        TYPE t_cursor IS REF CURSOR;
        v_array t_array := t_array();
        c1 t_cursor;   
      BEGIN 
        v_conn_string_trg := CONN_STRING_TRG;
        v_exec_temp_dir := EXEC_TEMP_DIR;
        DBMS_LOB.TRIM(v_select, 0);
        DBMS_LOB.APPEND(v_select, '#!/bin/bash' || chr(13) || chr(10));
        DBMS_LOB.APPEND(v_select, BASH_PROFILE || chr(13) || chr(10));
        DBMS_LOB.APPEND(v_select, chr(13) || chr(10));
        v_select_aux := '
          SELECT A.process_type, b.process_name, b.LOCATION
          FROM
            SELECT process_type, process_id, LEVEL level2
            FROM
              SELECT process_type, process_id, dep_process_type, dep_process_id
              FROM crmdw_master_dependencies
              WHERE dependency_type <> ''PREVIOUS_DATE''
              UNION ALL
              SELECT process_type, process_id, NULL, NULL
              FROM
                SELECT ''STG'' process_type, ID process_id
                FROM crmdw_master_stg
                UNION ALL
                SELECT ''DW'', ID
                FROM crmdw_master_dw
                UNION ALL
                SELECT ''DM'', ID
                FROM crmdw_master_dm
                MINUS
                SELECT d.process_type, d.process_id
                FROM crmdw_master_dependencies d
            START WITH dep_process_type IS NULL
            CONNECT BY PRIOR process_type = dep_process_type
            AND PRIOR process_id = dep_process_id
          ) a
          INNER JOIN
            SELECT 1 ordinal, ''STG'' process_type, s.ID process_id, s.process process_name, c.location, s.active 
            FROM crmdw_master_stg s
            INNER JOIN crmdw_master_clusters c ON (c.id = s.id_cluster)
            UNION ALL
            SELECT 2, ''DW'', ID, process, ''' || v_exec_temp_dir || ''', active
            FROM crmdw_master_dw
            UNION ALL
            SELECT 3, ''DM'', ID, process, ''' || v_exec_temp_dir || ''', active
            FROM crmdw_master_dm
          ) b ON (A.process_type = b.process_type AND A.process_id = b.process_id)
          WHERE b.active = 1
          ORDER BY b.ordinal, a.level2
        BEGIN
          OPEN c1 FOR v_select_aux;
          LOOP
            FETCH c1 INTO v_process_type, v_process_name, v_location;
            EXIT WHEN c1%NOTFOUND;
            v_result := F_CHECK_NEED_TO_EXECUTE (
                            v_process_type
                          , v_process_name
            IF (v_result = 1) THEN        
              IF (v_process_type = 'STG') THEN
                v_select_aux := '. '  || nvl(v_location, '/') || lower(v_process_name) || '/start.sh';
              ELSIF (v_process_type = 'DW') THEN
                v_select_aux := 'sqlplus ' || v_conn_string_trg || ' @' || v_location || 'exec_dw.sql "' || v_process_name || '"';
              ELSIF (v_process_type = 'DM') THEN
                v_select_aux := 'sqlplus ' || v_conn_string_trg || ' @' || v_location || 'exec_dm.sql "' || v_process_name || '"';
              ELSE
                v_select_aux := '';
              END IF;
              IF (v_array.COUNT > 0) THEN
                FOR i IN v_array.FIRST .. v_array.LAST LOOP
                  IF ((v_array.EXISTS(i)) AND (v_array(i) = v_select_aux)) THEN
                      v_array.DELETE(i);
                      EXIT;
                  END IF;
                END LOOP;
              END IF;
              v_array.EXTEND;       
              v_array(v_array.LAST) := v_select_aux;     
            END IF;
          END LOOP;
          CLOSE c1;
          FOR i IN v_array.FIRST .. v_array.LAST LOOP
            IF (v_array.EXISTS(i)) THEN
              DBMS_LOB.APPEND(v_select, v_array(i) || chr(13) || chr(10));
            END IF;
          END LOOP;     
        EXCEPTION
          WHEN OTHERS THEN
            DBMS_LOB.APPEND(v_select, chr(13) || chr(10));
        END;       
        RETURN v_select;
      END;
      END F_GET_EXECUTION_PLAN; 

  • Creating a job and scheduling a job error in OEM

    Hi, Everyone,
    I am trying to create and schedule a job thru OEM. In the the pl/sql block provide i have given my code like this
    begin
    SET SERVEROUTPUT ON;
    SPOOL C:\RFV_PROFILE_REPORT.LOG APPEND;
    SELECT TO_CHAR(SYSDATE, 'DD/MM/YY HH24:MI:SS') FROM DUAL;
    EXEC PAC_RFV_PROFILE_REPORT.CALL_ALL (200910);
    SELECT TO_CHAR(SYSDATE, 'DD/MM/YY HH24:MI:SS') FROM DUAL;
    SPOOL OFF;
    end;
    i have created the job and scheduled it but i am getting this error:
    Error # 6550
    Details ORA-06550: line 2, column 5: PL/SQL: ORA-00922: missing or invalid option ORA-06550: line 2, column 1: PL/SQL: SQL Statement ignored ORA-06550: line 3, column 7: PLS-00103: Encountered the symbol "C" when expecting one of the following: := . ( @ % ;
    could anyone pls help as this is very urgent.
    Thanks in advance

    Ah, the problem is you are confusing SQLPlus commands with PL/SQL.
    SET SERVEROUTPUT ON; -- This is a SQLPlus command, not necessary here.
    SPOOL C:\RFV_PROFILE_REPORT.LOG APPEND; -- This is a SQLPlus command, in PL/SQL to write out to a file you will need to call the UTL_FILE package to open a file for writing to. Except that the file you write to will appear on the database server, not your workstation, when the scheduled job runs.
    SELECT TO_CHAR(SYSDATE, 'DD/MM/YY HH24:MI:SS') FROM DUAL; -- In PL/SQL you need to SELECT columns INTO variables FROM tables. But in fact I guess you want to write the time to file using UTL_FILE again. However, you don't really need to do this, since scheduler will log the start time and run duration itself.
    EXEC PAC_RFV_PROFILE_REPORT.CALL_ALL (200910); -- This is the SQLPlus equivalent of the PL/SQL command:
    BEGIN
    PAC_RFV_PROFILE_REPORT.CALL_ALL (200910);
    END;
    SPOOL OFF; -- This is a SQLPlus command, not necessary here.
    So to summarise, all you really need is:
    BEGIN
    PAC_RFV_PROFILE_REPORT.CALL_ALL (200910);
    END;
    And the scheduled job will log the start time and duration in the database, which you can find here:
    SELECT * FROM USER_SCHEDULER_JOB_RUN_DETAILS

  • How to create a JOb

    Hi Experts,
    Previously i waw using bdc and was creating session.
    Now in place of BDC i am using BAPI .
    Now i cannot create  a session  so i am creating a job.
    Problem is that when i use bapi the record is created at same time.
    So before execting Job  using transaction SM37
    the records gets created.
    Can any  body please explain me how to solve this issue.
    Thanks & regards,
    Chetan

    Hi chetan,
    To create a new batch job you can go to transaction Sm36,wherein you can define the job name,job class and target server..then you can go to start condition and select whether it is a periodic job,or immediate job and accordingly you can schedule the job..Also the very important thing is in the Step funtion you should have valid ABAP program or any external program which should be used at the background...
    If you know the program then you can go to SE38 and create a variant for that program which can be later used in the newly created job.You can also copy an existing job and modify it according to the requirement by checking the job details in SM37.
    Just to summarise the Key transactions are : SM36 and SE38.
    JOB_OPEN: Create a Background Processing Job
    Use JOB_OPEN to create a background job. The function module returns the unique ID number which, together with the job name, is required for identifying the job.
    Once you have "opened" a job, you can add job steps to it with JOB_SUBMIT and submit the job for processing with JOB_CLOSE.
    For more information, please see the online documentation in the function module facility (transaction SE37)
    Sample Program: Creating a Job with JOB_OPEN
    Create your job with JOB_OPEN. The module returns a unique job
    number. Together with the jobname, this number identifies the
    job. Other parameters are available, but are not required.
    JOBNAME = 'Freely selectable name for the job(s) you create'.
    CALL FUNCTION 'JOB_OPEN'
    EXPORTING
    JOBNAME = JOBNAME
    IMPORTING
    JOBCOUNT = JOBNUMBER
    EXCEPTIONS
    CANT_CREATE_JOB = 01
    INVALID_JOB_DATA = 02
    JOBNAME_MISSING = 03
    OTHERS = 99.
    IF SY-SUBRC > 0.
    <Error processing>
    ENDIF.
    thanks
    katrhik

  • Creating the job to execute automatically the program RSWUWFML2

    Hi guys,
    Iu2019m setting up the job to send Workitems to internet periodically with the program RSWUWFML2, when I create the job It ask me for a responsible user in the u201Cstepu201D, this user is going to be the one to execute this job, I usually call this user u201CWORKFLOWu201D and I need to set the Email account (Workflow) for this user (Tcode SU01) because on this Email account  the system will be sending a kind of log for the workitems sent to users and which of them have been opened by the user.
    The question I have is in SU01 which u201CROLESu201D have to be set for this user to be able to make all the thinks to send the workitmes to the users and send this Email as a log and make all the things related to execute the RSWUWFML2 report.
    Tanks a lot

    >
    FelipeUribe wrote:
    > Hi Ravi, tanks a lot for your answer, The problem using user  WF-BACH as a user to be placed in the Job (Tcode SM36  -> Step u2026 field u201CUser = Background User Name for Authorization Checku201D) is that I get an error because this user canu2019t be a u201Ccommunicationu201D useru2026.the Tcode SWU3 create this user WF-BATCH automatically with this features.
    Hi Felipe
    Here's Help from the user type field in SU01 for B it says,
    System 'B'
    Use the system user type for internal system processes (-> background processing) or system-related processes (-> ALE, workflow, TMS, CUA).
    Dialog logon (using SAP GUI) is not possible.
    A user of this type is excluded from the general settings for password validity. Only user administrators can change the password using transaction SU01 (Goto -> Change Password).
    Multiple logons are permissible.
    I have checked one of our productive systems and it is set to B for WF-BATCH. The error message you get is because your WF-BATCH is a C type.
    Hope this helps.
    Good Luck
    Ravi

  • Could not create a Job with BI Scheduler

    Hi all, we are attempting to create a job but when it runs we receive the following error:
    +++ ThreadID: 564 : 2007-06-11 10:10:08.000
    Global Error: [nQSError: 77006] Oracle BI Presentation Server Error: Authentication failed.
    Error Codes: WKY9UVRD:
    Authentication Failure.
    Error Codes: IHVF6OM7:OPR4ONWY:U9IM8TAC
    Odbc driver returned an error (SQLDriverConnectW).
    State: 08004. Code: 10018. [NQODBC] [SQL_STATE: 08004] [nQSError: 10018] Access for the requested connection is refused.
    [nQSError: 43001] Authentication failed for Administrator in repository Star: invalid user/password. (08004)
    +++ ThreadID: 564 : 2007-06-11 10:10:08.000
    ...Trying main loop again.
    +++ ThreadID: 564 : 2007-06-11 10:10:08.000
    ... Sleeping for 9 seconds.
    +++ ThreadID: 564 : 2007-06-11 10:10:17.000
    Global Error: [nQSError: 77006] Oracle BI Presentation Server Error: Authentication failed.
    Error Codes: WKY9UVRD:
    Authentication Failure.
    Error Codes: IHVF6OM7:OPR4ONWY:U9IM8TAC
    Odbc driver returned an error (SQLDriverConnectW).
    State: 08004. Code: 10018. [NQODBC] [SQL_STATE: 08004] [nQSError: 10018] Access for the requested connection is refused.
    [nQSError: 43001] Authentication failed for Administrator in repository Star: invalid user/password. (08004)
    +++ ThreadID: 564 : 2007-06-11 10:10:17.000
    Terminal Error: Exceeded number of retries.
    +++ ThreadID: 564 : 2007-06-11 10:10:08.000
    Global Error: [nQSError: 77006] Oracle BI Presentation Server Error: Authentication failed.
    Error Codes: WKY9UVRD:
    Authentication Failure.
    Error Codes: IHVF6OM7:OPR4ONWY:U9IM8TAC
    Odbc driver returned an error (SQLDriverConnectW).
    State: 08004. Code: 10018. [NQODBC] [SQL_STATE: 08004] [nQSError: 10018] Access for the requested connection is refused.
    [nQSError: 43001] Authentication failed for Administrator in repository Star: invalid user/password. (08004)
    +++ ThreadID: 564 : 2007-06-11 10:10:08.000
    ...Trying main loop again.
    +++ ThreadID: 564 : 2007-06-11 10:10:08.000
    ... Sleeping for 9 seconds.
    +++ ThreadID: 564 : 2007-06-11 10:10:17.000
    Global Error: [nQSError: 77006] Oracle BI Presentation Server Error: Authentication failed.
    Error Codes: WKY9UVRD:
    Authentication Failure.
    Error Codes: IHVF6OM7:OPR4ONWY:U9IM8TAC
    Odbc driver returned an error (SQLDriverConnectW).
    State: 08004. Code: 10018. [NQODBC] [SQL_STATE: 08004] [nQSError: 10018] Access for the requested connection is refused.
    [nQSError: 43001] Authentication failed for Administrator in repository Star: invalid user/password. (08004)
    +++ ThreadID: 564 : 2007-06-11 10:10:17.000
    Terminal Error: Exceeded number of retries.
    Any help?
    Thank you.,
    Regards.

    I have the same Problem :-(
    In adittion I have an authentivication with LDAP.
    If I create the user in the Repository I can connect to it but I receive the following Problem:
    +++ ThreadID: 82c : 2007-10-10 12:17:40.000
    [nQSError: 77006] Oracle BI Presentation Server Error: A fatal error occurred while processing the request. The server responded with: Odbc driver returned an error (SQLDriverConnectW).
    Error Codes: OPR4ONWY:U9IM8TAC
    State: 08004. Code: 10018. [NQODBC] [SQL_STATE: 08004] [nQSError: 10018] Access for the requested connection is refused.
    [nQSError: 13024] Successful completion of init block 'IB_LDAP' is required. (08004)
    If drop the User the Repository and use an LDAP User, I receive the following:
    +++ ThreadID: 38c : 2007-10-10 13:13:21.000
    [nQSError: 77006] Oracle BI Presentation Server Error: A fatal error occurred while processing the request. The server responded with: Authentication Failure.
    Error Codes: IHVF6OM7:OPR4ONWY:U9IM8TAC
    Odbc driver returned an error (SQLDriverConnectW).
    State: 08004. Code: 10018. [NQODBC] [SQL_STATE: 08004] [nQSError: 10018] Access for the requested connection is refused.
    [nQSError: 43001] Authentication failed for ExtOV01 in repository Star: invalid user/password. (08004)
    Regards,
    Stefan Hess

  • Problems Creating PDFs

    A lot of problems creating PDFs come from using the wrong printer to create the PDF or underlying printfile.
    You should use Adobe's Distiller printer instance to create a PDF. This comprises the latest Adobe Postscript printer for your operating system plus the Distiller PPD.
    Don't use an HP printer to create your PDF. PostScript, or otherwise.
    Don't use a Xerox printer to create your PDF. PostScript or otherwise.
    See #1.
    Note: If you are outputting to a service bureau, you might want to use something other than the Distiller printer instance. However, if you encounter problems with your particular PDFs, try using the official method with the Distiller printer to see whether any problems are limited just to your setup. If problems persist, you might have to create your PostScript output using one printer driver and the PDF using Adobe's Distiller printer instance.
    Common problems include:
    Black and white, or greyscale, PDFs created from color FrameMaker books and documents.
    Distiller terminating the PDF creation process early, thus no PDF is created.
    Troubleshooting:
    For lack-of-color problems, first check you don't have Spot as Black set in the Frame Print dialog.
    Update the printer you are using to the latest Adobe PostScript printer driver version.
    Uninstall the printer you are using to create PDFs and to reinstall the latest version from scratch.

    FAQ: Creating PDF Files from FrameMaker Documents -- Why you should not use "save as PDF"! -- Windows & MacOS Only!
    Dov Isaacs - 07:02pm Dec 6, 2001 Pacific
    An issue that has come up over and over again on several FrameMaker and Acrobat/PDF email lists as well on the corresponding Adobe User-to-User forums is that of creation of PDF files. FrameMaker 5.5.6 and 6 have what looks like a convenient feature that is supposed to allow you to create PDF files via simply saving the document as a PDF file. I have gone on record as advising end-users not to use this approach for reliable creation of PDF files from FrameMaker documents under Windows and MacOS with FrameMaker 6 and earlier. Why do I most vociferously offer this advice and why doesn't the problem get fixed? And how SHOULD you create PDF files from FrameMaker?
    GOOD NEWS
    I will start with the good news. The "next major version" of FrameMaker will indeed have "save as PDF" re-implemented in a manner that it will be as reliable as printing to the "Acrobat Distiller" printer instance under Windows or the "Create Adobe PDF" desktop printer under MacOS. I am personally working with the FrameMaker development organization to make sure this really happens and is fully and properly tested and debugged! Furthermore, this next major revision of FrameMaker, unlike FrameMaker 6, will come with a Distiller installer that will properly install the "Acrobat Distiller" printer instance under Windows and the "Create Adobe PDF" desktop printer on the Macintosh (of course assuring that the latest PostScript driver is also automatically and correctly installed).
    DON'T USE "SAVE AS PDF"
    But what's wrong with "save as PDF" as currently implemented?
    The following are some of the SYMPTOMS reported over the last few years by FrameMaker users that were traced back to use of "save as PDF" under FrameMaker:
    (1) No PDF file is produced at all, possibly with a log file showing not-readily apparent PostScript errors during distillation.
    (2) The PDF file "loses" color in images. All or some images (raster, bitmap images, NOT vector artwork) appear in the PDF file in grayscale.
    (3) The resultant PDF file is on the wrong paper size, i.e., the document's logical page size does not match the output page size as seen in Acrobat or Acrobat Reader.
    (4) Some or all text in the resultant PDF file is blotchy looking or overly bold.
    (5) Some or all text in the resultant PDF file cannot be searched or indexed.
    (6) Some or all text in the resultant PDF file appears in Courier or in some other substitution font.
    (7) Interword or intercharacter spacing is a bit irregular in the resultant PDF file.
    (8) Content is missing in the margin areas of the page, i.e. you cannot do full-page bleeds.
    (9) Some or all page content is missing (other than margin areas).
    (10) Relatively inefficient PDF is generated.
    If this list by itself isn't enough for you, please note that some of these symptoms are very subtle and may escape attention when the PDF is first viewed or printed. Oftimes, it is when one attempts to manipulate the PDF file in Acrobat or repurpose its content or even view or print on a system other than the one on which the PDF file was created, that some of these symptoms make themselves obnoxiously visible (or invisible in some cases I won't make any bad jokes here about graphic examples!).
    It is important to understand that FrameMaker does NOT have its own native ability to create PDF. Any and all PDF created from FrameMaker documents is actually done by creating PostScript via the PostScript driver and having the Acrobat Distiller create PDF from that PostScript. The only exception to this is creation of PDF via the Acrobat PDFWriter driver, which is likewise not recommended (see below).
    In order for "save as PDF" to work correctly, FrameMaker must do the equivalent of calling Printer Setup and selecting the "Acrobat Distiller" printer instance under Windows or the "Create Adobe PDF" desktop printer under MacOS followed by setting the driver's options correctly for paper size, page range, etc., followed by sending the proper commands to the driver to create PostScript.
    Contrary to popular belief, PostScript as generated by the Windows and MacOS PostScript drivers is VERY device-dependent. The information in the PPD file associated with a printer driver instance provides critical parameters for generation of PostScript including:
    Whether the printer supports color (Acrobat Distiller does)
    What PostScript language level is supported (Acrobat Distiller 4.x and Acrobat Distiller 5.x are both PostScript language level 3)
    Whether native TrueType support is available (Acrobat supports native TrueType as Type 42 fonts)
    Available binary communications (Acrobat Distiller supports pure binary and ASCII, but NOT TCP, TBCP, or PJL)
    Resident fonts (Acrobat Distiller doesn't really have resident fonts)
    Available paper sizes and custom paper size availability (Acrobat Distiller supports a wide range of predefined sizes and continually variable "custom" sizes up to 200" by 200")
    Margins / printable areas (for PDF and the Acrobat Distiller, there are no margins in which imaging is not permitted)
    Device resolution (Acrobat Distiller can be set to any value from 72 to 4000 dpi; as a convenience, the Acrobat Distiller PPD provides a series of values for use by the driver. Since there is no inherent "resolution" of a PDF file, this parameter is used only for purposes of allowing PostScript programs that query for such a value to be satisfied and for the driver to be able to communicate this value to the operating system and/or application as required.)
    Paper handling (totally irrelevant to Acrobat Distiller if input or output tray selection via "setpagedevice" is found in the PostScript stream, it is ignored by Acrobat Distiller)
    Thus, if the wrong printer driver instance is selected (i.e., it isn't associated with the Acrobat Distiller PPD file) or that driver instance is improperly configured, improper PostScript will result and one or more of the symptoms described above can occur. As currently implemented, FrameMaker depending upon version will not necessarily choose the correct printer driver instance and/or correctly parameterize the print job via driver setup options. In fact, FrameMaker 5,5,6 might even try to generate PDF via calling a PCL driver, FAX driver, or even a non-PostScript inkjet printer!
    DON'T USE PDFWRITER
    The Acrobat PDFWriter is a relic of older versions of Acrobat. In fact, it is no longer installed by default in the "easy install" or the "typical install" of Acrobat 5. It hasn't really be updated since Acrobat 3 and only supports PDF 1.2. It is a GDI (Windows) / QuickDraw (MacOS) driver that directly generates PDF without any intermediary PostScript. Since it is not a PostScript printer driver, applications cannot pass through EPS graphics and/or PDFMark information (used for a wide variety of purposes by FrameMaker). For EPS graphics, most applications will send the low resolution TIFF (or PICT) EPS header in lieu of the PostScript text, if they send anything at all, to the driver. Forget about links, structure, or any other PDF "goodies." Expect that PDFWriter will fully "bite the dust" in the next major version of Acrobat.
    SO HOW DO I GENERATE PDF FILES FROM FRAMEMAKER 6 & EARLIER?
    The ONLY method that is really reliable for producing PDF files with FrameMaker 6 and earlier requires the generation of PostScript via a properly set printer driver instance associated with the Acrobat Distiller PPD and distillation of the resultant PostScript by Acrobat Distiller.
    Case 1: FrameMaker and the Full Acrobat 4.05 or Acrobat 5.0x Products
    PDF file from a "chapter" -- print directly to the Acrobat Distiller printer instance (Windows) or the Create Adobe PDF desktop printer (MacOS) already installed by Acrobat. If you check the "Acrobat data" option, then make sure to UNcheck the "print to file" option that gets set at the same time. As a result, the driver will automatically send the generated PostScript to the Distiller for you and delete the intermediate PostScript when done.
    PDF file from a "book" -- print directly to the Acrobat Distiller printer instance with the "print to file" option checked (Windows) or the Virtual Printer desktop printer (MacOS) associated with the Distiller PPD (see details below under Case 2/MacOS). You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
    In both the above sub-cases, the default driver options generally will be OK, but check on paper size and communication protocol (Use pure binary, not ASCII, for optimal performance AND no CTRL-D characters under Windows. Make sure to set Level 3 only and Binary under MacOS. Font inclusion "All" for Acrobat 4.05 and "None" for Acrobat 5 under MacOS.). With Acrobat 4.05, make sure you preset the Distiller to use the joboptions you want. With Acrobat 5, you can set this on a job-by-job basis via the driver printer setup interface (or print dialog on MacOS).
    Case 2: FrameMaker 6 and the Bundled Acrobat 4.05 Distiller
    Windows -- Create a new printer driver instance using the latest version of the Adobe Universal PostScript Driver Installer, downloadable from Adobe's web site AND the Acrobat Distiller PPD file (located in the XTRAS subdirectory of the Distiller directory). This driver instance should be set to print to the local port named "FILE:". Name this driver instance as "Acrobat Distiller". The default driver options generally will be OK, but check on paper size and communication protocol (use pure binary, not ASCII, for optimal performance AND no CTRL-D characters). Make sure you preset the Distiller to use the joboptions you want. Print directly to this Acrobat Distiller printer instance. Make sure that the "print to file" option is checked. You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
    MacOS -- Install the latest version of AdobePS 8.7.x, downloadable from Adobe's web site. In FrameMaker, go to Page Setup and select the "Virtual Printer" and go to the "Virtual Printer" window pane. Select the Acrobat Distiller PPD file (located in the XTRAS subfolder of the Distiller folder). Print directly to the "Virtual Printer" (Make sure to set Level 3 only, Binary, and font inclusion "All".). Make sure you preset the Distiller to use the joboptions you want. You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
    Case 3: Acrobat 3
    Acrobat 3 is not officially supported for the latest OS versions and I personally would no longer recommend its use for generation of PDF files given that Acrobat 5.0.5 is the current version of Acrobat.
    - Dov

  • ORA-01422: while trying to create a job

    Hi all,
    WE need a help from you, group of experts
    we are getting the following error
    ORA-01422: exact fetch returns more than requested number of rows
    ORA-06512: at "SYS.DBMS_ISCHED", while trying to create a job using the following code
    BEGIN
    DBMS_SCHEDULER.create_program
    (program_name => 'FAILURE_MONITOR_PRG',
    program_action => 'JOB_MGR.SPR_FAILURE_MONITOR',
    program_type => 'STORED_PROCEDURE',
    number_of_arguments => 1,
    enabled => FALSE
    DBMS_SCHEDULER.define_metadata_argument
    (program_name => 'FAILURE_MONITOR_PRG',
    argument_position => 1,
    metadata_attribute => 'EVENT_MESSAGE'
    DBMS_SCHEDULER.create_job
    (job_name => 'FAILURE_MONITOR_JOB',
    program_name => 'FAILURE_MONITOR_PRG',
    enabled => TRUE,
    auto_drop => FALSE,
    start_date => SYSDATE,
    event_condition => 'tab.user_data.event = ''FAILED''',
    queue_spec => 'event_queue'
    END;
    Oracle allows us to create the job if the parameter values for enabled is "false" in the DBMS_SCHEDULER.create_job call. But we got the same error
    when tried to enable the job using exec DBMS_SCHEDULER.ENABLE ('FAILURE_MONITOR_JOB');
    ORA-01422: exact fetch returns more than requested number of rows
    ORA-06512: at "SYS.DBMS_ISCHED", line 2751
    ORA-06512: at "SYS.DBMS_SCHEDULER", line 1794
    ORA-06512: at line 1
    Please help us to solve this issue
    Thanks,
    Reghu
    null

    Hi Ravi,
    Thank you for your kind support
    That issue has been solved. Problem was with the event queue and only for that particular job i mentioned in the first post (I was able to create other jobs with different Events using the same queue) . After recreating the event queue i am able to create the same job. I got the same error when I tired to drop the queue, and then I dropped the queue table itself. Do you have any idea about what might had caused the issue?
    Thanks
    Reghu

  • Cl_batch_event= raise creates a job

    Hello SCN,
    I have the following problem. I have a program that should start when an event is raised. For that I created a periodic job waiting for the event (start condition is after event). I thought that when I then raise the event using cl_batch_event=>raise, this job that was parked in SM37 would switch to "Active". That is sort of happening. But...
    My program should always run in maximum one instance. Either one instance or parking off in SM37. Unfortunately when I call cl_batch_event=>raise, it creates a new instance of the job with status "Released" and activates the previous job into status "Active". Even if no job for that event is defined, it creates this job for me. This means the job is replicating itself over time and eating system resources, causing problems with concurrent access to the DB etc.
    I understand I have no control over the kernel functionality in cl_batch_event=>raise, but is there anything I can do about this? I have coding in place that should prevent all of these problems (and I would swear it worked until recently), but cl_batch_event=>raise creating a job is for me surprising and suspicious. Is there either a way how to control this or has anyone else experienced that before?
    Cheers Otto

    So what I've done:
    a) I've configured SM62 and can see when my event is being raised
    b) I cleared everything in SM37 for my event, which means there are no scheduled, released, ready or active jobs related to my event.
    c) I went to SE24 for cl_batch_event=>raise and using F8 single tested my event. I got a line in SM62 where the details say:
    Number of Jobs            1
    Event Status              New
    Processing Status         OK
    My question is: I have no job waiting for the event. SM62 says there is one. When I then go and check SM37, I can see a job with name = program in the job, status = "Released"which is not doing anything. Is this correct? Can this be explained? (In case I didn't get the documentation right).
    cheers Otto

  • Error While creating a Job using JOB_OPEN

    Hello,
    I am trying to create a job in the output type of a standard transaction.
    But the job creation is failing. While debugging the transaction in update mode, I found out that the JOB_OPEN is coming out in the 'COMMIT WORK'.
    Is there any other way to create a job so that the program executes properly.
    Thanis/Regards,
    Abhijit Anandgaonkar.

    Hi,
    create a RFC function module....and inside the function module...create the batch job..
    in the output type processing program...call the RFC function module in background task..
    Thanks
    Naren

Maybe you are looking for