Results 1 to 6 of 6

Thread: every job fails

  1. #1
    Join Date
    Mar 2004
    Posts
    3

    Unanswered: every job fails

    every job that I run fails. e.g.backup

    Also, if a job fails where do I find the reason? Does Oracle write it somewhere?

  2. #2
    Join Date
    Jan 2004
    Location
    India
    Posts
    113
    Hi U need to mention the problem clearly.

    Backup can be Online ,Offline
    For Online-> using exp utility u can mention a log file which can be viewed for error messages.
    Offline backups are taken using some OS utility so can be determined from the files written by the OS itself.

    Error while execution of sql statements could be found in path defined
    by two parameters in the Init<sid>.ora
    background_dump_dest=%ORACLE_HOME%\RDBMS\trace
    user_dump_dest=%ORACLE_HOME%\RDBMS\trace

    Besides listener problem can be looked into the listener.log.

    Moreover tracing of events or statements can be done using
    set SQL_TRACE=true

    So you see a lot of things can be done.
    I think the above could help you to look into a good book.

    Cheers
    KAushik

  3. #3
    Join Date
    Mar 2004
    Posts
    3
    When I go into the OMS, click on a DB and then click backup. Then I follow the wizard til the end with a custom mode and run immediately, then the job shows up as failed in the jobs window in OMS. Thats it.



    Originally posted by kausik_m123
    Hi U need to mention the problem clearly.

    Backup can be Online ,Offline
    For Online-> using exp utility u can mention a log file which can be viewed for error messages.
    Offline backups are taken using some OS utility so can be determined from the files written by the OS itself.

    Error while execution of sql statements could be found in path defined
    by two parameters in the Init<sid>.ora
    background_dump_dest=%ORACLE_HOME%\RDBMS\trace
    user_dump_dest=%ORACLE_HOME%\RDBMS\trace

    Besides listener problem can be looked into the listener.log.

    Moreover tracing of events or statements can be done using
    set SQL_TRACE=true

    So you see a lot of things can be done.
    I think the above could help you to look into a good book.

    Cheers
    KAushik

  4. #4
    Join Date
    Apr 2003
    Location
    Greenville, SC (USA)
    Posts
    1,155
    It is possible that Oracle will write a trace file to UDUMP directory ...
    I would also look in BDUMP for SNPxxx files ... You should have a clue as to the problem from there (if they are truely erroring out ...

    If you want to find out why ... from sqlplus ...
    sql> execute dbms_job.run(jobnumber);

    If they are just NOT running ... Check parameter value of
    job_queue_processes and job_queue_interval ... ensure you have
    processes setup and the interval is in seconds


    HTH
    Gregg

  5. #5
    Join Date
    Mar 2004
    Posts
    10
    If the target platform is Windows, then for EM jobs to run you should give specific privileges to the user that runs the job:
    The privileges are:
    "Act as part of the Operating system"
    "Log on as a batch job"
    Thanks,
    Sudip Datta
    Server Technologies
    Oracle Corporation

  6. #6
    Join Date
    Jan 2004
    Location
    India
    Posts
    113
    If suggestions given above doesn't solve ur problem please post the error message (any Ora error message) or if u could find the log file associated with the backup.

    Kaushik

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •