Hi
Our DBA said need to reboot Oracle Database server. which we have XMETA repository is placed.
I hope we can able to run the job via script only we can;t able to login Datastage Designer and Director.
Shall we need to stop the whole Datastage services if XMETA is down?
Thanks
Man
XMETA database is down. shall I run the jobs?
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
You cannot run any jobs until XMETA is back up.
Certus Solutions
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Theoretically you should stop engine, services and repository in that order, and start them in the reverse of that order.
Practically all tiers are reasonably robust, and will re-establish connections. In version 11.x even the client tier is able to re-establish connection.
Practically all tiers are reasonably robust, and will re-establish connections. In version 11.x even the client tier is able to re-establish connection.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
We run DataStage 8.7 on Windows Server 2008 with jobs scheduled via the Windows Task Scheduler.
From time to time, our XMETA database goes down.
Our experience is, that while the database is unavailable:
- We can't use Director, Designer or Administrator.
- Scheduled jobs start at their scheduled time, and run normally.
When the database is back, we have to shut down and restart as described by Ray in order to regain access to Director, Designer and Administrator.
From time to time, our XMETA database goes down.
Our experience is, that while the database is unavailable:
- We can't use Director, Designer or Administrator.
- Scheduled jobs start at their scheduled time, and run normally.
When the database is back, we have to shut down and restart as described by Ray in order to regain access to Director, Designer and Administrator.