I am trying to run the following code from a script file but it complains that syntax of (both instances of) grep is wrong.
When I copy and paste it to the terminal, it is OK. Any idea what the problem might be?
set i = `grep -c #define flags.h`
while ($i>20)
@ i--
my func (`cat... (4 Replies)
I have written a script to run on UNIX server. When I tested, it always hanged on after "date +"%D %T: XXXXXX script started." part. Then it wouldn't go further. UNIX server gave me one error message. I used the same code in another script. It works fine. I think the major problem may be in... (3 Replies)
grep -e doesn't work in Soalris.
Same script with grep -e worked on AIX/HP/LINUX..
I would like to search a list of patterns on "log.txt" like ...
grep -e FATAL -e ERROR log.txt
I get the error message as
grep: illegal option -- e
Usage: grep -hblcnsviw pattern file . . . (3 Replies)
I have a script which uses below for loop:
for (( i = 0 ; i <= 5; i++ ))
do
echo "Welcome $i times"
done
But when I run the script, it gives error message:
Syntex Error : Bad for loop variable
Can anyone guide to run it?
Thanks in advance. (10 Replies)
I am trying to find only those entries where 7018 and another number appear in the end of the line.
7018 2828 1423 2351
7018 2828 14887
2828 7018 1222
123 7018 1487
I am looking for a way to generate only the last two lines. I was trying to do just "grep '7018{1,5}" but it does not... (5 Replies)
Hi there,
the following script doesn't work. the first part works, then the second 'grep' fails with ': not found'. However, if I take out the second part (starting with the grep command) and put in a seperate script, it works.
everyone know what's wrong here? no two 'grep' in one script, that... (2 Replies)
I have a script that only works if I remove it from the looping scenario.
#!/bin/bash
# Set the field seperator to a newline
##IFS="
##"
# Loop through the file
##for line in `cat nlist.txt`;do
# put the line into a variable.
##dbuser=$line
echo "copying plugin..."
... (6 Replies)
Hi,
I'm trying to write a script that checks gvfs to see if a mount exists so I can run it from network-manager's status hooks. I thought I'd pipe the output of gvfs-mount -l to grep for the particular mounts I care about. When I do this in a bash script:
cmnd="gvfs-mount -l | grep -i... (4 Replies)
Working with IP addresses is a pain...
Here's my problem: I'm putting some interface information to a file:
3.185.201.2 | Tu1102
152.162.54.130 | Gi0/2.36
3.185.226.2 | Gi0/1
3.185.0.82 | Tu1
... (12 Replies)
Hello,
First of all, I'd like to say hello to all members of forum.
Can You please help me with the matter described below?
I am trying to fetch a data from the file to variable, I am doing this using below script:
returned=`tail -50 SapLogs.log | grep -i -E "Error|"`
echo $returned
... (2 Replies)
Discussion started by: jedzio
2 Replies
LEARN ABOUT SUSE
ocf_heartbeat_oracle
OCF_HEARTBEAT_ORACLE(7) OCF resource agents OCF_HEARTBEAT_ORACLE(7)NAME
ocf_heartbeat_oracle - Manages an Oracle Database instance
SYNOPSIS
oracle [start | stop | status | monitor | validate-all | methods | meta-data]
DESCRIPTION
Resource script for oracle. Manages an Oracle Database instance as an HA resource.
SUPPORTED PARAMETERS
sid
The Oracle SID (aka ORACLE_SID). (required, string, no default)
home
The Oracle home directory (aka ORACLE_HOME). If not specified, then the SID along with its home should be listed in /etc/oratab.
(optional, string, no default)
user
The Oracle owner (aka ORACLE_OWNER). If not specified, then it is set to the owner of file $ORACLE_HOME/dbs/*${ORACLE_SID}.ora. If this
does not work for you, just set it explicitely. (optional, string, no default)
ipcrm
Sometimes IPC objects (shared memory segments and semaphores) belonging to an Oracle instance might be left behind which prevents the
instance from starting. It is not easy to figure out which shared segments belong to which instance, in particular when more instances
are running as same user. What we use here is the "oradebug" feature and its "ipc" trace utility. It is not optimal to parse the
debugging information, but I am not aware of any other way to find out about the IPC information. In case the format or wording of the
trace report changes, parsing might fail. There are some precautions, however, to prevent stepping on other peoples toes. There is also
a dumpinstipc option which will make us print the IPC objects which belong to the instance. Use it to see if we parse the trace file
correctly. Three settings are possible: - none: don't mess with IPC and hope for the best (beware: you'll probably be out of luck,
sooner or later) - instance: try to figure out the IPC stuff which belongs to the instance and remove only those (default; should be
safe) - orauser: remove all IPC belonging to the user which runs the instance (don't use this if you run more than one instance as same
user or if other apps running as this user use IPC) The default setting "instance" should be safe to use, but in that case we cannot
guarantee that the instance will start. In case IPC objects were already left around, because, for instance, someone mercilessly
killing Oracle processes, there is no way any more to find out which IPC objects should be removed. In that case, human intervention is
necessary, and probably _all_ instances running as same user will have to be stopped. The third setting, "orauser", guarantees IPC
objects removal, but it does that based only on IPC objects ownership, so you should use that only if every instance runs as separate
user. Please report any problems. Suggestions/fixes welcome. (optional, string, default instance)
clear_backupmode
The clear of the backup mode of ORACLE. (optional, boolean, default false)
shutdown_method
How to stop Oracle is a matter of taste it seems. The default method ("checkpoint/abort") is: alter system checkpoint; shutdown abort;
This should be the fastest safe way bring the instance down. If you find "shutdown abort" distasteful, set this attribute to
"immediate" in which case we will shutdown immediate; If you still think that there's even better way to shutdown an Oracle instance we
are willing to listen. (optional, string, default checkpoint/abort)
SUPPORTED ACTIONS
This resource agent supports the following actions (operations):
start
Starts the resource. Suggested minimum timeout: 120.
stop
Stops the resource. Suggested minimum timeout: 120.
status
Performs a status check. Suggested minimum timeout: 5.
monitor
Performs a detailed status check. Suggested minimum timeout: 30. Suggested interval: 120.
validate-all
Performs a validation of the resource configuration. Suggested minimum timeout: 5.
methods
Suggested minimum timeout: 5.
meta-data
Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5.
EXAMPLE
The following is an example configuration for a oracle resource using the crm(8) shell:
primitive example_oracle ocf:heartbeat:oracle
params
sid=string
op monitor depth="0" timeout="30" interval="120"
SEE ALSO
http://www.linux-ha.org/wiki/oracle_(resource_agent)
AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors)
resource-agents 1.0.3 07/05/2010 OCF_HEARTBEAT_ORACLE(7)