JOB SCHEDULING QUERY

PLS HELP IN THIS REGARD
WHEN TO USE  JOB SCHEDULING FMS EG: JOB_OPEN / JOB_SUMBIT / JOB_CLOSE  AND WHEN TO SCHEDULE JOBS THRU SM-36?  PLS TELL ME IN RESPECT TO DEV / PRD SERVERS IE: IF I AM WORKING ON DEV SERVER WHICH PROCESS WILL I OPT  AND WAT TO USE IN PRD SERVER ?  WAT IS THE USE OF GET_PRINT_PARAMETERS IN JOB SCHEDULING?

Hi,
JOB_OPEN / JOB_SUMBIT / JOB_CLOSE -> Used to schedule a report/program in background i.e on background workprocess.
AND WHEN TO SCHEDULE JOBS THRU SM-36?- PLS TELL ME IN RESPECT TO DEV / PRD SERVERS IE: IF I AM WORKING ON DEV SERVER WHICH PROCESS WILL I OPT AND WAT TO USE IN PRD SERVER ?-> Background WP
WAT IS THE USE OF GET_PRINT_PARAMETERS _. used to find the print parameters e.g in case you wnat to write data to spool

Similar Messages

  • Errors in job scheduled SSIS package

    A job scheduled for SSIS package failed with the below errors:
    Microsoft (R) SQL Server Execute Package Utility  Version 10.50.4321.0 for 64-bit  Copyright (C) Microsoft Corporation 2010. All rights reserved.    
    Started:  5:00:02 AM  
    Error: 2015-01-02 05:06:39.25     
    Code: 0xC0202009     
    Source: Data Flow Task OLE DB Destination [46]     
    Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. 
    Error code: 0x80004005.  An OLE DB record is available.  
    Source: "Microsoft SQL Server Native Client 10.0"  
    Hresult: 0x80004005  
    Description: "Could not allocate a new page for database because of insufficient disk space in filegroup 'PRIMARY'. Create the necessary
    space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.".  End Error  Error: 2015-01-02 05:06:39.42     
    Code: 0xC0209029     
    Source: Data Flow Task OLE DB Destination [46]     
    Description: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR.  The "input "OLE DB Destination Input" (59)"
    failed because error code 0xC020907B occurred, and the error row disposition on "input "OLE DB Destination Input" (59)" specifies failure on error. An error occurred on the specified object of the specified component.  There may be
    error messages posted before this with more information about the failure.  
    End Error  Error: 2015-01-02 05:06:39.44     
    Code: 0xC0047022     
    Source: Data Flow Task SSIS.Pipeline     
    Description: SSIS Error Code DTS_E_PROCESSINPUTFAILED.  The ProcessInput method on component "OLE DB Destination" (46) failed
    with error code 0xC0209029 while processing input "OLE DB Destination Input" (59). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow
    task to stop running.  There may be error messages posted before this with more information about the failure.  
    End Error  Error: 2015-01-02 05:06:39.48     
    Code: 0xC02020C4     
    Source: Data Flow Task Flat File Source [1]     
    Description: The attempt to add a row to the Data Flow task buffer failed with error code 0xC0047020.  
    End Error  Error: 2015-01-02 05:06:39.50     
    Code: 0xC0047038     
    Source: Data Flow Task SSIS.Pipeline     
    Description: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED.  The PrimeOutput method on component "Flat File Source" (1) returned
    error code 0xC02020C4.  The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing.  There may be error
    messages posted before this with more information about the failure.  
    End Error  Error: 2015-01-02 05:16:23.49     
    Code: 0x00000000     
    Source: Execute SQL Task 1      
    Description: Could not allocate space for object 'bo.TLE'.'PK_new' in database because the 'PRIMARY' filegroup is full. Create disk space
    by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.  
    End Error  Error: 2015-01-02 05:16:23.70     
    Code: 0xC002F210     
    Source: Execute SQL Task 1 Execute SQL Task     
    Description: Executing the query "Sp_load" failed with the following error: "Warning: Null value is eliminated by an aggregate
    or other SET operation.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.  
    End Error  DTExec: The package execution returned DTSER_FAILURE (1).  
    Started:  5:00:02 AM  
    Finished: 5:16:27 AM  
    Elapsed:  984.928 seconds.  The package execution failed.  The step failed.
    Please help!!!!

    Hi,
    Based on the error message” Could not allocate a new page for database because of insufficient disk space in filegroup 'PRIMARY'. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth
    on for existing files in the filegroup”, we can know that the issue is caused by the there is no sufficient disk space in filegroup 'PRIMARY' for the database.
    To fix this issue, we can add additional files to the filegroup by add a new file to the PRIMARY filegroup on Files page, or setting Autogrowth on for existing files in the filegroup to increase the necessary space.
    As to the issue that the job executed successfully for the next run when executed, I think it can be caused by someone or something had made something to increase the space. 
    The following document about Add Data or Log Files to a Database is for your reference:
    http://msdn.microsoft.com/en-us/library/ms189253.aspx
    If there are any other questions, please feel free to ask.
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • How to do the job scheduling in BDC Call transaction

    Hi Experts,
    I've a Query like how to do the job scheduling in BDC Call transaction
      If anybody knows the answer please send me the reply.
      Thanks.
       Regards,
        Rekha

    Hi ,
    any progarm can be scheduled, wether it may be BDC or report thru SM36 Tcode.
    But do rememeber that if ur BDC is using GUI_UPLOAD function module, then it wont work , coz the function Gui_upload or GUI_DOWNLOAd wont work in back ground.
    If u r going to use OPEN_DATASET , READ dataset ....then it can be scheduled. i.e BDC can work if ur program retrievesz the data from Application server.
    Rvert back if any issues,
    Reward with poinst if helpful.
    Regards,
    Naveen

  • SAP tables that underlie job scheduler

    Has anyone ever queried the tables that support the job scheduling system in SAP?  I need to list each scheduled job name and the email recipients, where applicable, that receive the given job's output.  Our company was recently sold, and our email address domain is changing, so numerous jobs need checked and changed.  Having this ability would accelerate this process greatly.
    Thanks,
    Eric

    Hi Eric,
    This may be a question for one of the ABAP forums.
    The table is TBTCO. And the field is RECOBJKEY. You may need to do some debugging to figure out how to convert it back to an email address.
    Cheers,
    Ramki Maley.

  • Jobs schedule in Background.

    Hi Guys,
    I have some "Z" programs, those programs are job schedule programs, I want to know particular "Z" programs job schedule name, how we can find the job name using the program.
    Can please suggest in table these jobs will store.
    Is my query will clarify?
    Thanks,
    Gourisanakr

    Hi..
    Check this tables.
    TBTCS - Batch Schedule Table
    TBTCO - Batch Step overview table
    TBTCP - Job status overview.
    Award points if useful.
    Rdgs,
    Lakshmiraj

  • Requested start time during job scheduling population in local time.

    Hello Experts,
    Could you please help on the issue.
    Requested start time during job scheduling populated with local time even though we have assigned the GMT time zone.
    Could you please help , how to change the settings of request start time calender icon to populate the GMT time.
    thanks,
    Suresh.

    Hello Gerben,
    Thanks for the reply, even though the default time zone set as GMT in user settings, the requested start time calender pop up the local time instead of GMT time.
    Previously requested start time poped up  the GMT time, we have observed this change once we have ran the redwood script for time window elements change and imported some of the job definitions, applications & time windows from other system.
    Below is the script we have ran thought shell script
    Script Fuctionality
    1. Take the mentioned time window
    2. iteratate thought the time window elements and add 1 hour to the "time to day from" & "time to day to" parameters.
    3. set the changed parametes to time window and persist the changes.
    // Variable Declarations
    String timewindow = null;
    String query = null;
    TimeWindow tw = null;
    TimeWindowElement twe = null;
    long otdvalue = 3600000;
    long l1 = 0;
    long l2 = 0;
    long threshold = 0 ;
    long expvalue = 82800000;
    long expvalue1 = 85500000;
    long indto1 = 0;
    long indfrom1 = 300999;
    long indto2 = 2700000;
    long indfrom2 =  3000999;
    Job job = null;
    //Declare all the time windows in array
    String[] timewindows = {"XX_TIMEWINDOW_01_GMT"};
              for( int i = 0 ; i < timewindows.length; i++)
              timewindow =  timewindows<i>;
              jcsOut.println("TimeWindow"i":"+timewindows<i>);
              tw = jcsSession.getTimeWindowByName(timewindow);
              for (Iterator it1 = tw.getTimeWindowElements(); it1.hasNext();)
                   twe = (TimeWindowElement) it1.next();
                   Long otd = new Long(otdvalue);
                   jcsOut.println("************************");
                   jcsOut.println(twe.getTimeOfDayFrom());
                   jcsOut.println(twe.getTimeOfDayTo());
                   jcsOut.println("************************");
                   Long todf = (Long) twe.getTimeOfDayFrom();
                   Long todt = (Long) twe.getTimeOfDayTo();
                                      threshold = todf.longValue();
                            // if timeday from equal to 23 GMT assign the 0 GMT
                                      if(threshold == expvalue )
                    jcsOut.println("timewindow with 23 GMT");
                   l1 = indto1;
                   l2 = indfrom1;
                            //if timedayfrom equal to 23:45 GMT assign 0:45 GMT
                   else if(threshold == expvalue1)
                   jcsOut.println("timewindow with 23:45 GMT");
                   l1 = indto2;
                   l2 = indfrom2;
                            // Add 1 hour for current time of day from 
                   else
                   l1 = todf.longValue() + otdvalue;
                   l2 = todt.longValue() +  otdvalue;
                   Long ll1 = new Long(l1);
                   Long ll2 = new Long(l2);
                   twe.setTimeOfDayFrom(ll1);
                   twe.setTimeOfDayTo(ll2);
                   jcsOut.println("After Change:"+ twe.getTimeOfDayFrom());
                   jcsSession.persist();
    Once after the script competetion the time window time zone remains in GMT.
    Could you please check script once and  help us  the time zone change caused  the by script or not?
    Thanks,
    Suresh

  • Please help for job schedule

    i need create job schedule to be run daily at 1 AM the goal of this job to run the following query
    Delete
    From EJARIN.TEMP_CONTRACT_PROPERTIES TCP
    Where TCP.ENTRY_DATE<=to_date(sysdate-1);
    Commit;
    please help

    If you are in 9.2 or older release, you have just the Package DBMS_JOB to manage the Job.
    If you are in 10.1 or later release, DBMS_JOB or DBMS_SCHEDULER. But, it's recommended to use DBMS_SCHEDULER as it's a much more powerful tool.
    By using DBMS_JOB, you can create a Job like that:
    Just create a stored procedure which do your requirment then you can create job like below based on version..
    Example 1
    begin
      dbms_job.submit(:jobno,
                      '<PL/SQL stored procedure>;',
                       to_date('<date>','dd-mm-yyyy HH24:MI:SS'),
                      'SYSDATE + 1');
      commit;
    end;
    print jobno;By using DBMS_SCHEDULER, you can do like that for a STORED PROCEDURE:
    BEGIN
    DBMS_SCHEDULER.CREATE_JOB(
    job_name => '<job_name>',
    job_type => 'STORED_PRODECURE',
    job_action => '<schema>.<stored procedure>',
    repeat_interval => 'FREQ=DAYLY;BYHOUR=<hh>;BYMINUTE=<mm>;BYSECOND=<ss>',
    enabled => TRUE)
    END;best regards
    asp

  • Job scheduling

    Hi Friends,
             i have a problem with job scheduling.
    two jobs need to be scheduled. (job1 and job2)
    i used
    job_open.
    submit job1 using parameters.
    job_close.
    then for second job.
    job_open.
    submit job2 using parameter2.
    job_close.
    when i go and look in sm37. i see when job1 is running the job2 is in release status.
    but what we need is when job1 is running job2 should be in schedule status. it should start only after job1 is completed.
    in the job2 job_close i used job1 as the PRED_JOBNAME.
    but i when i run the program job2 is in released status , not in schedule mode.
    is there any way we can make the job2 in scheduled mode instead of release.
    can we use event to control this. if yes please let me know how we can do it.
    Thanks

    Hi,
    As Appana wrote - i'm not sure there's a problem, but why don't u make one job with 2 steps? this way u will be perfectly sure that job2 (2nd step in the new job) will run only after job1 (1st step n the new job)...
    Good luck
    Igal

  • Internal error occurs in background job scheduling

    Hi Experts,
    We are facing an error message "Internal error occurs in background job scheduling" while trying to execute a custom report(Z report) in background in SA38.
    Please find the following observation on our side on this message.
    1) This message is not coming for only one report not for others.
    2) SU53 screen shot shows that SE38 check is failed, but the weird thing is not happening for other report.
    3) Persons having SE38 auhtorization are able to run this report.
    Please advise.
    Thanks in advance,
    Viven

    What is the message ID and number? Have you tried OSS search and debugging?
    What does this program do, in a nutshell?

  • Background Job Scheduling

    Hi,
      I am scheduling a report to run in background.
    In this report it is creating background jobs automatically for different company codes.
    It submits the 1st background job and waits until it finishes.
    Then 2nd job starts in background and continues with other jobs.
    At end it finishes all the jobs and closes.
    Now my problem is.
    1.       Whether is it possible for us to submit all the jobs at 1 time. And execute at same time. Ie., 1st, 2nd job will start at same time.
    2.       If possible how can we do that.
    What I have written is
    loop at companycode.
    Create job name.
    call fun 'Job_Open'.
    submit xxxx user sy-uname via job job_name numer job_count
    to sap-spool
    spool parameters l_spool_parameter
    without spool dynpro
    with companycode
    with ......
    and return.
    endloop.
    Please help ASAP, urgent.

    hi praveen,
    Job Scheduling Explained
    Definition
    Before any background processing can actually begin, background jobs must be defined and scheduled. The scheduled time for when a job runs is one part of the job’s definition. There are several ways to schedule jobs:
    From Transaction SM36 (Define Background Job)
    With the "start program in the background" option of either Transaction SA38 (ABAP: Execute Program) or Transaction SE38 (the ABAP editor)
    Through the background processing system’s own programming interface. (Many SAP applications use the internal programming interface to schedule long-running reports for background processing.)
    Through an external interface.
    Scheduling Background Jobs   
    Use
    You can define and schedule background jobs in two ways from the Job Overview:
    ·         Directly from Transaction SM36. This is best for users already familiar with background job scheduling.
    ·         The Job Scheduling Wizard. This is best for users unfamiliar with SAP background job scheduling. To use the Job Wizard, start from Transaction SM36, and either select Goto ® Wizard version or simply use the Job Wizard button.
    Procedure
           1.      Call Transaction SM36 or choose CCMS ® Jobs ® Definition.
           2.      Assign a job name. Decide on a name for the job you are defining and enter it in the Job Name field.
           3.      Set the job’s priority, or “Job Class”:
    ·         High priority:      Class A
    ·         Medium priority: Class B
    ·         Low priority: Class C
           4.      In the Target server field, indicate whether to use system load balancing.
    ·         For the system to use system load balancing to automatically select the most efficient application server to use at the moment, leave this field empty.
    ·         To use a particular application server to run the job, enter a specific target server.
           5.      If spool requests generated by this job are to be sent to someone as email, specify the email address. Choose the Spool list recipient button.
           6.      Define when the job is to start by choosing Start Condition and completing the appropriate selections. If the job is to repeat, or be periodic, check the box at the bottom of this screen.
           7.      Define the job’s steps by choosing Step, then specify the ABAP program, external command, or external program to be used for each step.
           8.      Save the fully defined job to submit it to the background processing system.
           9.      When you need to modify, reschedule, or otherwise manipulate a job after you've scheduled it the first time, you'll manage jobs from the Job Overview.
    Note: Release the job so that it can run. No job, even those scheduled for immediate processing, can run without first being released.
    Specifying Job Start Conditions
    Use
    When scheduling a background job (either from Transaction SM36, Define Background Job or CCMS ® Jobs ® Definition), you must specify conditions that will trigger the job to start.
    Procedure
    Choose the Start condition button at the top of the Define Background Job screen.
    Choose the button at the top of the Start Time screen for the type of start condition you want to use (Immediate, Date/Time, After job, After event, or At operation mode) and complete the start time definition in the screen that appears.
    For the job to repeat, check the Periodic job box at the bottom of the Start Time screen and choose the Period values button below it to define the frequency of repetition (hourly, daily, weekly, monthly, or another specific time-related period). Then choose the Save button in the Period values screen to accept the periodicity and return to the Start Time screen.
    Once you’ve completed specifying the job start conditions, choose the Save button at the bottom of the Start Time screen to return to the Define Background Job screen.
    No job can be started until it is released, including jobs scheduled to start immediately. Since releasing jobs can be done only by a system administrator from the job management screen (Transaction SM37) or by other users who have been granted the appropriate Authorizations for Background Processing, no unauthorized user can start a job without explicit permission
    Managing Jobs from the Job Overview
    Use
    The Job Overview, or Job Maintenance, screen is the single, central area for completing a wide range of tasks related to monitoring and managing jobs, including defining jobs; scheduling, rescheduling, and copying existing jobs; rescheduling and editing jobs and job steps; repeating a job; debugging an active job; reviewing information about a job; canceling a job's release status; canceling and deleting jobs; comparing the specifications of several jobs; checking the status of jobs; reviewing job logs; and releasing a job so it can run.
    Procedures
    To display the Job Overview screen, choose CCMS ® Jobs ® Maintenance or call Transaction SM37. Before entering the Job Overview screen, the system first displays the Select Background Jobs screen. You'll need to complete this Job Selection screen to define the criteria for the jobs you want to manage. Once you've selected jobs to manage, you can choose from a wide range of management tasks:
    To copy a single existing job, choose Job ® Copy.
    To reschedule or edit job steps or attributes of a single job, choose Job ® Change. A job step is an independent unit of work within a background job. Each job step can execute an ABAP or external program. Other variants or authorizations may be used for each job step. The system allows you to display ABAP programs and variants. You can scan a program for syntax errors. You can also display the authorizations for an authorized user of an ABAP job step.
    To repeat a single job, choose Job ® Repeat scheduling.
    To debug an active job, choose Job ® Capture: active job. Only a single selection is allowed. If an active job seems to be running incorrectly (e.g., running for an excessively long time), you can interrupt and analyze it in debugging mode in a background process, and then either release it again or stop it altogether.
    You will be able to capture a background job only if you are logged on to the SAP server on which the job is running. To find server information in the Job Overview, select and mark the job, then choose Job ® Job details.
    To review information about a job, choose Job ® Job details. Details displayed can include:
    current job status
    periodicity, or the repetition interval
    other jobs linked to the current job, either as previous or subsequent jobs
    defined job steps
    spool requests generated by the current job
    To cancel a job's "Released" status, select the job or jobs from the Job Overview list and choose Job ® Release -> Scheduled.
    To cancel a job from running but keep the job definition available, select the job or jobs from the Job Overview list and choose Job ® Cancel active job.
    To delete a job entirely, select the job or jobs from the Job Overview list and choose Job ® Delete. Jobs with the status of Ready or Running cannot be deleted.
    To compare the specifications of more than one job, select the jobs from the Job Overview list and choose Job ® Compare jobs.
    To check the status of jobs, select the job or jobs from the Overview Job list and choose Job ® Check status. This allows you to either change the job status back to Planned or cancel the job altogether. This is especially useful when a job has malfunctioned.
    To review job logs, select a job or jobs with the status Completed or Canceled from the Job Overview list and
    regards
    karthik
    reward me points if helpfull

  • Job Scheduling in Solution Manager - Error creating Periodic Job

    Hi all,
    I am in the process of testing the Job Scheduling functionality using the Solution Manager.  I have setup the criteria manager, ec. in the satellite system, and done the config in Solman as well. 
    I am able to successfully setup up a 'on-time' job.
    it's only when I try to setup a periodic job, I end up getting following error
    Any thoughts?  Is there any piece of config that's missing?  All the SICF services needed for this functionality are running fine.
    Thanks for the help.
    500 Internal Server Error
    Error when processing your request
    What has happened?
    The URL https://fsspsm.target.com:/sap/bc/webdynpro/sap/wd_ags_ejr_job_req_gaf_app was not called due to an error.
    Note
    The following error text was processed in the system PSM : Message was not created
    The error occurred on the application server fsspsmap01_PSM_00 and in the work process 1 .
    The termination type was: ERROR_MESSAGE_STATE
    The ABAP call stack was:
    Function: BAPI_NOTIFICATION_CREATE of program SAPLDSWP_NOTIF
    Method: MSG_SUBMIT of program CL_DSMOP_BSP_NOTI_MODEL=======CP
    Method: SUBMIT_REQ_CRM_DATA of program CL_AGS_EJR_JOB_REQUEST_FACTORYCP
    Method: SUBMIT of program CL_AGS_EJR_JOB_REQUEST_FACTORYCP
    Method: PROCESS_SCENARIO_PERIODIC of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
    Method: PROCESS_JOB_SCENARIO of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
    Method: IF_AGS_EJR_JSM_PROC_FPM_CTRL~AFTER_PROCESS_EVENT of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
    Method: AFTER_PROCESS_EVENT of program /1BCWDY/K54G9RCMK7J4Z427H49S==CP
    Method: IWCI_IF_FPM_APP_CONTROLLER~AFTER_PROCESS_EVENT of program /1BCWDY/K54G9RCMK7J4Z427H49S==CP
    Method: CALL_UIBB_PROCESS_EVENT of program CL_FPM========================CP

    Hello,
    This is the basic Job Scheduling functionality and not the Redwood Job scheduling, correct?
    Have you performed the IMG Activiteis in SPRO?
    See the following Help link:
    http://help.sap.com/saphelp_sm70ehp1_sp23/helpdata/en/c5/7edcbd58ce4e29bc1baf1c4761d71f/frameset.htm
    Change a job
    You can change the scheduling of a job as long as it has not been completed. Proceed as follows:
    Make changes.
    Note
    When you change a periodic job, the system searches for the changeable successor and only changes this successor.
    If there is more than one changeable job with the same name, the system does not change any of these jobs.
    End of the note.
    Save your entries.
    To release the job in the target system, select Release.
    You go to the transaction SM37 in the target system.
    You just may want to ensure HTTP Services have been enabled. I realize you said the services workin SICF, but this needs to be verified as 500 Internal Server Error most often means the HTTP services are not activated.
    Regards,
    Paul

  • Error in Backup job scheduling in DB13

    Hi All
    Backup job scheduled in DB13 kicks error ,I am using Oracle as database and ERP6.0
    database and application are on diffrent servers.Before it was working fine,I didn't changed any password
    I can run backupjob sucessfully directly from BRtools on database server.Please provide any hint
    Job started
    Step 001 started (program RSDBAJOB, variant &0000000000060, user )
    No application server found on database host - rsh/gateway will be used
    Execute logical command BRBACKUP On host DLcSapOraG08
    Parameters:-u / -jid INLOG20090120204230 -c force -t online -m incr -p initerd.sap -w use_dbv -a -c force -p in
    iterd.sap -cds -w use_rmv
    BR0051I BRBACKUP 7.00 (31)
    BR0128I Option 'use_dbv' ignored for 'incr'
    BR0055I Start of database backup: bdztcorv.ind 2009-01-20 20.42.31
    BR0484I BRBACKUP log file: D:\oracle\ERD\sapbackup\bdztcorv.ind
    BR0280I BRBACKUP time stamp: 2009-01-20 20.42.32
    BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:
    'CONNECT /'
    ORA-01017: invalid username/password; logon denied
    BR0310E Connect to database instance ERD failed
    BR0280I BRBACKUP time stamp: 2009-01-20 20.42.32
    BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:
    'CONNECT /'
    ORA-01017: invalid username/password; logon denied
    BR0310E Connect to database instance ERD failed
    BR0056I End of database backup: bdztcorv.ind 2009-01-20 20.42.32
    BR0280I BRBACKUP time stamp: 2009-01-20 20.42.32
    BR0054I BRBACKUP terminated with errors
    BR0280I BRBACKUP time stamp: 2009-01-20 20.42.32
    BR0291I BRARCHIVE will be started with options '-U -jid INLOG20090120204230 -d disk -c force -p initerd.sap -cds -w use_rmv'
    BR0002I BRARCHIVE 7.00 (31)
    BR0181E Option '-cds' not supported for 'disk'
    BR0280I BRARCHIVE time stamp: 2009-01-20 20.42.33
    BR0301W SQL error -1017 at location BrDbConnect-2, SQL statement:
    'CONNECT /'
    ORA-01017: invalid username/password; logon denied
    BR0310W Connect to database instance ERD failed
    BR0007I End of offline redo log processing: adztcorw.log 2009-01-20 20.42.32
    BR0280I BRARCHIVE time stamp: 2009-01-20 20.42.33
    BR0005I BRARCHIVE terminated with errors
    BR0280I BRBACKUP time stamp: 2009-01-20 20.42.33
    BR0292I Execution of BRARCHIVE finished with return code 3
    External program terminated with exit code 3
    BRBACKUP returned error status E
    Job finished

    Hi,
    not sure if the recommendations given will address this issue.
    You are getting this error:
    BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:
    'CONNECT /'
    ORA-01017: invalid username/password; logon denied
    the log file indicates:
    > No application server found on database host - rsh/gateway will be used
    This indicated that the user that is connecting from the AS to the DB server is not properly configured to perform the DB tasks on it.
    So, first question would be to know if you have configured a gateway on the DB server and how, or if you are using remote shell.
    Second question, you can do backups on the DB server.
    > I can run backupjob sucessfully directly from BRtools on database server
    How did you run exactly the backup job (what is the exact command line, what is the exact OS user that executed it)?
    What is the OS of the DB server?
    I have reread your post, your OS is windows therefore you fall in the "typical" error in Windows.
    You have executed your backup as <sid>ADM and it works. Unfortunatelly, in windows, SAP is exectuted by SAPSERVICE<sid>, and this is the user who should be connecting to your DB server, and this is the user who cannot execute the backup.
    The fact that you can run the backup with <sid>ADM in Windows does not means that you have SAPService<sid> properly configured.
    For the error (see before) I think your ops$ user for this user is not properly configured in the DB server. take a look at the note mentioned by KT and pay attention to the SAPSERVICE<sid> configuration
    Edited by: Fidel Vales on Jan 24, 2009 12:45 AM

  • Regarding Background Job scheduling for file to file scenario

    Hi Guru's
    Good morining all of u
    I have one doubt on ...
    can we do background job scheduling for file to file scenario?
    Please give me response as early as possible.
    thanks and regards
    sai

    background jobscheduling for file adapter...
    you can schedule the file adapter according to your requirement as follows:
    In the  Communication Channel Monitoring Locate the link Availability Time Planning,  In Availability Time Planning, choose the Availability time as daily and say create, give the time details, select the communication channel in your case file adapter , goto the Communication Channels tab and filter and add the respective channel, save it
    /people/shabarish.vijayakumar/blog/2006/11/26/adapter-scheduling--hail-sp-19-

  • About Background job scheduling

    One file will be coming from oracle system. it would be stored at a particular path.
    I want to schedule for background job processing. how to do.

    Hi,
    You need to write a Program to place the file in the Application server, then only you can schedule a background job, you need to use the OPEN dataset, CLOSE DATASETS to do this one, then you can schedule the job .
    To schedule a job in the background job, look at the below links
    Re: background job schedule
    http://aspalliance.com/1129_Background_Processing_SAP_R3_System
    Regards
    Sudheer

  • Hi any one please explain background job scheduling

    Hi any one please explain background job scheduling . Good answer can be rewarded.
    Thanks

    Background jobs are pgms that are scheduled to be run in the Background without user interaction. So this can be done only for Type 1(executable) Program and not for Module-Pool Programs. Typically, a variant is defined and the pgm is run using the same.
    The transaction code is sm36 -Define Background job. Using the Start Condition tab you can define when you want the job to run (specific time or if it has to follow after a particular job is done etc.,) Using the Step tab you can assign the pgm name and variant.
    After the job is scheduled, you can check the status in sm37, along with the Job log and Spool.
    For more info:
    http://help.sap.com/saphelp_bw30b/helpdata/en/c4/3a7f87505211d189550000e829fbbd/content.htm

Maybe you are looking for