• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Oracle job is not running automatically

 
Ranch Hand
Posts: 31
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I m trying oracle database replication using snapshot (materialized view) with refresh fast attribute which requires materialized view log.
This internally creates a job (as I am refreshing the view periodically).
Job should run automatically after given time interval with refreshing the view.
It's running and giving status as failed also view is not getting refreshed. When I run the job manually view is getting refreshed!
Please provide solution... it's urgent.
 
Ranch Hand
Posts: 338
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
what are the errors that it is failing with?
 
pravin karne
Ranch Hand
Posts: 31
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am checking the job details like :
select * from user_jobs; & in it's result under failure column, failure count is increasing.
Also if job is running successfully then it should refresh materialized view means view should show/replicate new values inserted/ updated/ deleted in table.
Please reply soon... it's urgent!
[We are using Oracle 10g.]
 
Ranch Hand
Posts: 98
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
When a job execution attempt fails information about the failure is written to the database alert log and to a trace file. The alert log is in the database server file system directory pointed at by the background_dump_dest init parameter, and for jobs the trace file will be written to the same directory.

Look for a trace file dated the same as the date in the dba_jobs.last_run column for your failed job.
 
pravin karne
Ranch Hand
Posts: 31
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
There is nothing related to job in trace file and alertlog file...

When I perform DML operations on Master table, MV log populates with data but SNAPTIME$$ always
contains '1/1/4000' date. Also after running it's job manually MV refreshes with new values but
when job runs automatically then MV is not refreshing...
What will be the problem?
I am using Snapshot replication for remotely located table.
Any idea?
Thanks...
 
Paul Campbell
Ranch Hand
Posts: 338
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by pravin karne:
There is nothing related to job in trace file and alertlog file...

When I perform DML operations on Master table, MV log populates with data but SNAPTIME$$ always
contains '1/1/4000' date. Also after running it's job manually MV refreshes with new values but
when job runs automatically then MV is not refreshing...
What will be the problem?
I am using Snapshot replication for remotely located table.
Any idea?
Thanks...



Pravine, if there is nothing in the log (you should also check snapshot log) related to the job running and the materialized view is not refreshed... how do you know the automatic job is even being initiated? How is this job triggered?
 
pravin karne
Ranch Hand
Posts: 31
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
When we perform DML operations on master table.. then MV log gets populated with those values.
When we run the job manually then MV gets refresed and MV log is truncated...
but auto job is not refreshing MV and truncating MV log...
I am also not getting why it is so! checked job queue processes ... when we run it's command show parameter job_queue_processes then output is nothing... but I can see it's value set as 10 in SPFILE.ora and init.ora files... so what to do?
 
Paul Campbell
Ranch Hand
Posts: 338
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Pravine, did you resolve this... I haven't had time to get back to it.
 
pravin karne
Ranch Hand
Posts: 31
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Nope, it's not yet resolved....
Please help me out
Thanks
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic