![]() |
Hello and Welcome from United States to the UNIX and Linux Forums! Thank You for Visiting and Joining Our Global Community.
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| Windows & DOS: Issues & Discussions All Windows and DOS questions should go here as well. Discuss UNIX to Windows (Desktop or Server) here! |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Tech Article: Oracle Enterprise Manager Grid Control Architecture for Very Large Site | iBot | Oracle Updates (RSS) | 0 | 05-27-2009 05:00 PM |
| Tech Article: Oracle Enterprise Manager Grid Control Architecture for Very Large Site | iBot | Oracle Updates (RSS) | 0 | 02-18-2009 02:30 PM |
| how to do GRID COMPUTING? | nsharath | High Performance Computing | 5 | 01-31-2009 12:24 PM |
| How to automate check outs from version control? | siegfried | UNIX for Dummies Questions & Answers | 5 | 04-12-2008 01:35 AM |
| GRID containers technology | dheram | AIX | 1 | 07-25-2005 09:42 AM |
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
||||
|
Automate restart Grid control
Hi all,
I'm trying to write a batch program to automate restart of grid control. oraclehomes\db10g\bin\lsnrctl status >> %filename% oraclehomes\oms10g\bin\emctl status oms >> %filename% (This is just for testing.) However, i cannot seem to let both of the line to execute as the batch stopped when line 1 finish executing (without executing line 2). Any help is appreciated. Thanks. |
|
||||
|
Within the batch script, try preceding each of the two commands with "call " which will cause them to execute in their own batch shell, preventing the first job from exiting the whole batch job. (Not tested with your commands).
To read the help text about "call". From a "cmd" prompt: Code:
call /? |
|
||||
|
The "No longer listening on" messages will be in the Oracle listener log. Provided that you start a new log each time you start the Oracle listener, you can extract the messages with a MSDOS "find" command.
Not tried with your commands but you could try testing ERRORLEVEL immediately after executing the command, though I think that each command with the test for ERRORLEVEL would have to be in its own batch file executed from a call statement. We don't want to test the result of "call" itself. ERRORLEVEL is explained in the help text for "if". Code:
if /? |
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|