Sponsored Content
Special Forums Windows & DOS: Issues & Discussions Automate restart Grid control Post 302369012 by methyl on Friday 6th of November 2009 08:27:31 AM
Old 11-06-2009
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 /?

You'll have to check Oracle documentation for the ERRORLEVEL values from Oracle commmands.
 

5 More Discussions You Might Find Interesting

1. AIX

GRID containers technology

Hi forum, I am aware that on Hp-Superdome technology (Blade Servers) is avaliable while on Solaris GRID technology is the latest in the market. I would like to know if similar high end technology is also available for AIX ? (1 Reply)
Discussion started by: dheram
1 Replies

2. High Performance Computing

Grid vs. Parallel vs. Distributed

Hello all, I was wondering if someone could either explain or maybe point me to another article somewhere that explains the difference between: distributed computing grid computing parallel computing I see these terms thrown around a lot in server and cluster environments, but I'd like a... (2 Replies)
Discussion started by: Heathe_Kyle
2 Replies

3. UNIX for Dummies Questions & Answers

How to automate check outs from version control?

I'm in a fustrating situation where I am repeatidly checking code, editing, synchronizing, finding something is broke, reverting all my changes and starting over. This if often easier than trying to merge my changes with someone who has beat me to the checkin. Is there a way I can mitigate... (5 Replies)
Discussion started by: siegfried
5 Replies

4. High Performance Computing

how to do GRID COMPUTING?

Hello, I want to know how to combine the processing power of given 2 FEDORA machines in LAN. Can you please tell me the commands,etc used to perform such an operations.Can you please give me the links where I can find more info on this topic. (5 Replies)
Discussion started by: nsharath
5 Replies

5. UNIX and Linux Applications

Running RMAN backups from grid control but using oracle account with rsa keys vs a password ?

I'm a sysadmin trying to help out one of our DBA's setup the RMAN backups (Oracle 11g on rhel5 ) so they can schedule and control them from the OEM grid control. But we want the oracle user to use ssh keys instead of a password. I have the working rsa keys in place for the user but the GUI seems to... (0 Replies)
Discussion started by: samael00
0 Replies
Apache::Session::Oracle(3pm)				User Contributed Perl Documentation			      Apache::Session::Oracle(3pm)

NAME
Apache::Session::Oracle - An implementation of Apache::Session SYNOPSIS
use Apache::Session::Oracle; #if you want Apache::Session to open new DB handles: tie %hash, 'Apache::Session::Oracle', $id, { DataSource => 'dbi:Oracle:sessions', UserName => $db_user, Password => $db_pass, Commit => 1 }; #or, if your handles are already opened: tie %hash, 'Apache::Session::Oracle', $id, { Handle => $dbh, Commit => 1 }; DESCRIPTION
This module is an implementation of Apache::Session. It uses the Oracle backing store and no locking. See the example, and the documentation for Apache::Session::Store::Oracle for more details. USAGE
The special Apache::Session argument for this module is Commit. You MUST provide the Commit argument, which instructs this module to either commit the transaction when it is finished, or to simply do nothing. This feature is provided so that this module will not have adverse interactions with your local transaction policy, nor your local database handle caching policy. The argument is mandatory in order to make you think about this problem. This module also respects the LongReadLen argument, which specifies the maximum size of the session object. If not specified, the default maximum is 8 KB. AUTHOR
This module was written by Jeffrey William Baker <jwbaker@acm.org>. SEE ALSO
Apache::Session::File, Apache::Session::Flex, Apache::Session::DB_File, Apache::Session::Postgres, Apache::Session perl v5.10.1 2010-10-18 Apache::Session::Oracle(3pm)
All times are GMT -4. The time now is 08:59 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy