Академический Документы
Профессиональный Документы
Культура Документы
On working days we had discuss lot about the tools used for Database
monitoring and where are the servers and what was the gateways used and the databases
naming conventions used and where to made concentration and where to look up for the
particular error and how to resolve that or what are the steps to escalate and whom to
mail about the issue. And he let me to know where does the password file exists and the
password for that file database.kdb. And the purpose of each databases and he made me
to identify which are the production databases and which are the development databases.
Duane updates me what are the things done on the database, for ex,
Updating patches for the DST issues and about the weekly maintenance done on the
databases and about recycling the database.
Duane had sent me many documents regarding the instructions of how to
get into the tool and how to monitor etc. He let me know what the fog light messages are
and which one to keep and which one to delete. Duane drives always and some time I
used to drive to dig around the issues by his guidance.
The following introduction was just the juice of our discussion made till now.
First of all, we need to make a VPN connection with DecisionOne VPN Server to
access the servers in Decisionone.
We need to check the health of the databases on a daily basis. For this we use
FOC.
1. Foglight Monitoring :
Foglight Install.
1- Review critical errors (a published list has not yet been compiled, this may be
developed as we go through the review of this document).
2- Review functionality.
3- Monitoring needed only for production databases.
4- When an issue is worked, document the resolution, send an email to
duane.wilcox@decisionone.com and david.baker@DecisionOne.com.
5- To get the description of an error, right-click (rc) on the message, click ‘show
details’.
6- To clear the error (like the one above), rc the error and select ‘clear event’.
7- To look at an agent’s rules (like oracle_FS80PR), highlight the agent, rc, select
‘edit’, click on ‘rules’.
8- This screen shows all of the rules defined.
12- Close that out. On main Foglight Operations Console, click ‘Tools’, then
‘Foglight Registry’.
13- Each of the areas have info to maintain, but we normally work in the ‘World’
area.
2. Control-M Monitoring:
NOTE: The user profile has been changed for most Unix accounts, to
automatically set the DISPLAY variable. So for the most part, step 4 is done
for you. If the error message displays that the DISPLAY has not been set, do
the following steps:
- Find the IP address of the laptop / pc you are on. Can be obtained by
doing ipconfig at a command prompt.
- In the smf001 session, at the prompt, enter "export
DISPLAY=xxx.xxx.xxx.xxx:0.0", where the xxx's are equal to your ISP
assigned TCP/IP Address
10. when the ‘Load Net’ menu appears, click on the middle ‘LOAD’ icon to open.
11. when the ‘SHOW’ menu appears, click on the upper left hand icon to close,
this is not needed.
12. The ECS gui (Enterprise Controlstation Network View) display window can
be resized by dragging the sides of the window.
13. Here’s the size of window that focuses on the active job list (jobs loaded for
today’s schedule).
Control-M – Displaying a Job
2. Right-click on the job. On the intermediate menu, select ‘Details’. This view
shows the detail of the current job from the active job file (a scheduled job).
3. Back on the Enterprise Controlstation Network View screen, right-click and
click on ‘View Sysout List’. This screen shows the list of job output from the
scheduled job. There are multiple entries if the job has been rerun.
Double-click on this entry to review the output of this backup job.
4. To rerun a job - after review of the sysout, and correcting any errors, go back
to the ECS Display. Right-click the job and click RERUN. The job will be
re-submitted under the job owner (oracle8i in this example).
Control-M - Forcing a Job to Run
From the first ECS Menu, click Scheduling, then Scheduling Definitions
Double Click the TABLE Definition you want
Color Indication:
Green – completed
Yellow – executing.
Red - error, need to be fixed
Grey – awaiting resource, do right-click on job, and do ‘WHY’
Blue - awaiting resource, do right-click on job, and do ‘WHY’
Resolve the WHY condition if necessary.