 |
 |
| Index Search Add FAQ Ask Question |
|---|
$Date: 27-Jul-2001 $
$Revision: 1.24b $
$Author: Frank Naudé $
Services: Oracle on Windows NT and 2000 doesn't run as typical Windows processes, but as a Windows service. A service is basically a background process that is independent of who is using the console or system at any particular time. Services can be started at system boot time and can be compared to Unix daemon processes. To check that the required Oracle services are up and running, go to CONTROL PANEL/ SERVICES (or type "net start | more" from a DOS console window).
Multi Threaded: Unlike on Unix, the Oracle instance on NT and 2000 is implemented as a single operating system process. This process include threads that implement each of the tasks required for the instance to function. Therefore, there is a thread for each of the background (lgwr, dbwr, arch, etc.) and server tasks, plus a two-thread overhead. Because each thread shares the same memory space, there is no need to implement the SGA in shared memory. All memory it is available to all threads within the process.
Windows NT comes in two flavours: Workstation and Server. These terms are highly misleading, suggesting that a machine with server functions should run NT Server. That is not the case at all. The distinction between Workstation and Server is only important to NT itself. The Server product includes the NT domain administration tools and services. If you have more than one NT machine in a network you will probably want one of them to be an NT Server machine to act as the domain controller, but you probably DON'T want to run the Oracle database server on that machine.
The Oracle database server and tools will run equally well on an NT "Workstation" machine as on an NT "Server" machine, unless the Server machine is the Domain Controller for a busy domain, in which case it would be a poor choice to host a busy database server as well.
The same applies to the different Windows 2000 releases.
For Oracle releases below 8i, these command will have a XX suffix (eg svrmgr30), where XX is the utility's version number.
Before using any of these utilities, set the required environment variables. Look at this example:
DOS> set oracle_sid=oracle
DOS> svrmgrl
One can also create a new database from the Console Window. Start by generating some sample scripts using the Database Configuration Assistant. Modify them according to your standards, and run them to create your database.
Some of the other optional services are:
One can also specify autostart when creating new database services. Verify if this was done by opening Control Panel -> Services (Control Panel -> Administrative Tools -> Services on Windows 2000) and check if it is set to AUTOMATIC.
You may need to recreate the services mentioned above using the "oradim" (Instance Manager) utility. Start by opening a DOS command console window. Look at this example (assume a SID of TEST):
rem Delete the old service
ORADIM -DELETE -SID test -SRVC servicename
rem Create a new services with the STARTMODE AUTO property
oradim -new -sid TEST -intpwd ORACLE -startmode AUTO -pfile C:\orant\admin\TEST\pfile\initTEST.ora
net start "OracleAgent"
net start "OracleServiceSID" /y
net start "OracleTNSListener"
net start "OracleWWWListener9999"
To stop the services, use net stop instead of net start.
These commands are handy if you need to shut down the database for a cold (offline) backup. Do not put this batch file in your Windows startup group as the database will then only start when someone logs onto the server. The database will not start if the server is re-booted and waits on the log-on screen.
The following registry entries are also handy to prevent a SHUTDOWN ABORT when the OracleServiceSID service is stopped:
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE]
"ORA_SID_SHUTDOWN"="TRUE"
"ORA_SID_SHUTDOWN_TIMEOUT"="60"
orakill /? or orakill /h
for more details. Example:
SQL> select spid as thread, osuser, s.program
SQL> from sys.v_$process p, sys.v_$session s
SQL> where p.addr = s.paddr;
DOS> orakill.exe sid thread
The NTBACKUP command will not backup open files. Also, OCOPYxx.exe (e.g. OCOPY80.EXE distributed with Oracle8.0) will not backup files to tape, only to another disk location. Once the hotbackup to disk is complete, you can use the NTBACKUP utility to backup the files to tape.
Note 1: If you perform a hot backup your databases must run in archivelog mode, otherwise shutdown and do a cold backup. Read the Oracle Backup and Recovery FAQ for more details.
C:>at 12:00pm "my_backup"
Added a new job with job ID = 0
To get a list of scheduled jobs, execute the AT command without any
parameters: Eg:
C:>at
Status ID Day Time Command Line
----------------------------------------------------------------
0 Tomorrow 12:00 PM my_backup
For more info, type AT /?
Also note that several alternatives exist to the AT command. For example, there is a GUI utility in the NT Resource Kit CD-ROM for scheduling jobs. This utility will (supposedly) become part of the OS with version 5.0. It's a lot more convenient to use than its command-line counterpart AT.
| at | Schedule jobs to run | |
| hostname | Your machine name. Listed in LISTENER.ORA. | |
| ipconfig | Your machine's IP address. Listed in LISTENER.ORA. | |
| netstat | Monitor network connections. | |
Microsoft's commercial solution to the lack of a proper scripting language is called Microsoft SFS (Services for UNIX). SFS ships with a Unix borne shell, ActiveState Perl and other common Unix utilities like ls, crontab, grep, vi, top, ps, kill, etc. It also includes a Telnet Server to provide terminal access to your NT/2000 machines. This is extremely handy if you need to work from home.
More information about Windows Services for UNIX can be obtained from www.microsoft.com/windows/sfu.
Oracle FailSafe provides a high-availability database solution for Windows NT/2000 clusters. In the event of system failure, FailSafe will recover and restart the database on an alternative node within the cluster.
Oracle Parallel Server clusters databases for providing high availability and scalability through the use of shared storage systems. It allows users on multiple nodes to access a common Oracle database simultaneously. It enables multiple Oracle Server instances to run on different nodes of a cluster while providing concurrent access to common data.
Some of the benefits that MTS provides are:
|
|