Suggestion on running critical Oracle DBs on OVM

Login or Register for Dates, Times and to Reply

Thread Tools Search this Thread
# 8  
Thank you very much for all details. It gives me better understanding and more options to explore.
Login or Register for Dates, Times and to Reply

Previous Thread | Next Thread
Thread Tools Search this Thread
Search this Thread:
Advanced Search

Test Your Knowledge in Computers #296
Difficulty: Easy
Linux Mint 2.0 was based on Ubuntu 6.10 and used the Ubuntu 6.10 package repositories and using it as a codebase.
True or False?

7 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Run different SQL on multiple DBs using SHELL script

Hi Experts, I have a list of Dbs.In that DBs i need to execute some sql scripts. each sql script is unique and it should run on particular DB only. For example. i have DBs like MDC20V,NDC20V,ODC20V and sql scripts like MD.sql,ND.sql, MD.sql should run only in MDC20V and ND.sql should... (1 Reply)
Discussion started by: navsan420
1 Replies

2. Solaris

OVM Server for SPARC ... Need Your Help Guys !

I have two SPARC T4-2 servers: - Oracle Solaris 11.1 Installed. - Oracle VM Server for SPARC 3.0 software Installed. - Shared LUN provisioned to both servers from Clariion CX4 storage box (shared LUN to be used for the Live Migration of the VMs). - Oracle VM Agent 3.2.1 for SPARC installed. ... (14 Replies)
Discussion started by: Mack1982
14 Replies

3. Emergency UNIX and Linux Support

Oracle/Xen/OVM/OCFS2/Multipath/SAN Problems

Setup: Multiple Virtual Machines running OEL5 / Oracle RDBMS 11.2 OVM 2 / Xen 3.4.0 Cluster consisting of 3 Machines Shared SAN Storage synced with OCFS2 SAN connected with 4GB FC on 4 Paths per LUN SAN target are 2 EMC Clariion mirroring each other The problems we're facing are that... (6 Replies)
Discussion started by: pludi
6 Replies

4. Programming

Oracle Scheduled job not running as per schedule.

Hi, Though this is a unix forum mainly, am posting this oracle query here hoping to get a resolution. I have set up two scheduled jobs in oracle 11g for executiong a procedure in specific time intervals. One as Hourly and other as minutely. But the scheduled jobs are not running as per... (2 Replies)
Discussion started by: suresh_kb211
2 Replies

5. Infrastructure Monitoring

Test if Oracle listener is running

Hi All , I am new to shall scripting, i want write an script for oracle tns and listener. If tns working i want o/p as "Listener and TNS are working" else o/p should be ""Listener and TNS are not Working" below is the command in unix to check the tns status, if no output it means TNS... (3 Replies)
Discussion started by: abdul bari
3 Replies

6. Solaris

High I/O on Sun server running Oracle.

Hi, Currently we have a Sun Fire 480R running Solaris 9 and Oracle The server is fibre attached to a NetApp FAS3070. Two separate 100GB LUNs are presented to the server. The two LUNs are mounted as the file systems data and logs for the Oracle database. We are seeing high I/O... (1 Reply)
Discussion started by: gwhelan
1 Replies

7. Programming

Need help with C app on Oracle running on Solaris 6

Hello, I would really appreciate some help with a problem my current client is having. He has an old legacy app that does his company's financial accounting and ERP for manufacturing, etc. The app was written by a company called "Just in time" in Austin, TX, and they are no longer in business. ... (2 Replies)
Discussion started by: w0lf
2 Replies
CVSTRAC(1)						      General Commands Manual							CVSTRAC(1)

cvstrac - Low-ceremony bug tracker for projects under CVS SYNOPSIS
cvstrac [ command [ params ... ] ... ] DESCRIPTION
The cvstrac command is used to run the CVSTrac web service, or to initialise new databases for projects. Please read the section titled Security and Setup for details of the default password and why you should change it. This manual page was written for the Debian distribution because the original program source does contain a manual page. However CVSTrac is well documented at the CVSTrac Wiki, <>, and you will be able to fin d more up-to-date information there. OPTIONS
Running cvstrac without options produces a usage message. A summary of the command sequences which can be passed to cvstrac is included below. For more details, see /usr/share/doc/cvstrac on this system. chroot dir user Tells cvstrac to put itself into the chroot gaol dir and switch to the named user, dropping root privileges. These three parameters must be the first passed to cvstrac, and processing of command line parameters continues as normal after the chroot. init dir project Initialises a new CVSTrac database. dir is the name of the directory in which you want the database to reside, and project is the name of the project that CVSTrac will be hosting. The database file will be created as dir/project.db The following parameters cause CVSTrac to begin responding to HTTP requests by various methods. You will need to set up the database before use to ensure that only authorised users have administrative access. PLEASE READ and understand the section below entitled Security and Setup before using these commands, because unless you understand what to do you'll be leaving your system vulnerable to arbitrary code exe- cution as the user invoking CVSTrac. http dir [ project ] Causes CVSTrac to start running as an HTTP server on the standard input, displaying responses to the standard out. dir should be the name of a directory holding project database or databases created by cvstrac init and project is the name of a project database without the ".db" extension, as for cvstrac init. If the latter option is given, access is restricted to just the named project DB, and the access URL will change slightly. See below for details. cgi dir [ project ] Causes CVSTrac to respond as a CGI script. dir and project are interpreted as for cvstrac http. This invocation can be installed into a simple shell or Perl CGI script anywhere on a server supporting the Common Gateway Interface. server port dir [ project ] Causes CVSTrac to run as a self-hosted HTTP server on the specified port. dir and project are interpreted as above. Access to CVSTrac CVSTrac accesses databases created by its own init command, and is accessed remotely by HTTP. If you did not specify a single project to access in any of the http, cgi, or server commands, then the running CVSTrac instance can be used to access any database in that directory simply by modifying the URL, but you will need to supply the name of the database in order to access it. For self-hosted server instances of CVSTrac, and http instances started from inetd, the URL to use is of the form http://hostname[:port]/ if you specified a project in the invocation, or http://hostname[:port]/project/ if you didn't. If running as a CGI script, simply use the URL you would normally use for the CGI script, with the project name you wish to access tacked on if necessary, as above. For details of the default password, and why you should change it, read on! Security and Setup Once CVSTrac is installed and running, you should immediately access it as the setup user, and change the password. The username and pass- word of the setup user are both "setup". Passwords, rather counterintuitively, are changed by following the "Logout" hyperlink at the bot- tom of the main menu on the start screen. The setup user is able, in normal operation, to configure the service in a way that can cause arbitrary code to be executed under the same userid as CVSTrac itself. You should be aware of this, and the fact that this can easily lead to more serious exploits if the setup user is compromised. The chroot functionality described above is not a perfect fix for this, but can be used as an additional security measure. See the section below entitled Runtime Dependencies for details of what binaries the chroot gaol will need. Access to the CVS repository CVSTrac should be installed running as a user with read access to the CVS repository specified during the interactive setup. Certain com- mands, such as the ability to modify CVSROOT/passwd require the write permissions too. Runtime Dependencies Besides its libraries, CVSTrac requires the following binaries by default: co, rcsdiff, rlog and diff. If running cvstrac on a Debian sys- tem, these will have been installed as dependencies of the cvstrac package, or as part of the base system. SEE ALSO
The CVSTrac wiki and /usr/share/doc/cvstrac/examples on this system. AUTHOR
This manual page was written by Andrew Chadwick <>, for the Debian GNU/Linux system (but may be used by others). 1.1.4 6 October 2004 CVSTRAC(1)

Featured Tech Videos