Oracle8 Enterprise Edition Getting Started 
Release 8.0.5 for Windows NT 
A64416-01
 
Library		  
Product		  
Contents		  
Index
 

Prev Next

10
Administering a Database

This chapter describes how to administer Oracle8 Enterprise Edition.

Specific topics discussed are:

Managing Oracle Services

This section provides information on the following:

Oracle Service Naming Conventions for Multiple Oracle Homes

Oracle8 Enterprise Edition allows you to have multiple, active Oracle home directories on a single computer. Chapter 6, "Using Multiple Oracle Homes" describes this feature. Multiple Oracle homes affect the naming conventions for Oracle services. If you have only one Oracle home directory on a computer, there are no differences between the naming conventions for service names in this release and previous releases (that is, no Oracle home name and the SID is typically the default of ORCL). However, as you perform additional installations into Oracle home directories:

This affects service names. This table describes how two service names, OracleTNSListener80 and OracleServiceORCL, are affected when you install three Oracle8 databases into separate directories:

For the...  The Home Name is...  The SID is Named...  The Services are Named... 

First Oracle home installation on a computer. 

Not required. 

ORCL 

OracleTNSListener80 OracleServiceORCL 

Second Oracle home installation on a computer. 

Required; for this example, PROD is entered when prompted during installation. 

ORC1 

OraclePRODTNSListener80 OracleServiceORC1 

Third Oracle home installation on a computer. 

Required; for this example, SALES is entered when prompted during installation. 

ORC2 

OracleSALESTNSListener80 OracleServiceORC2 
 

These two figures show how the Services dialog box appears with two Oracle8 databases on a single computer:

. 

Available Oracle Services

Depending on the products that you have installed, a number of Oracle services are started when you restart your Windows NT computer. The three main Oracle services are:

Service Name  Description 

OracleServiceSID  

Created for the database instance SID. An Oracle instance is a logical term that refers to: 

  • an Oracle service called OracleServiceSID 
  • a database 

Each Oracle instance must have a system identifier (SID). A SID is a unique name for an Oracle database instance that can be up to four alphanumeric characters in length.  

For example, if the SID for the Oracle8 database is ORCL, it is appended to the service OracleService. Each file for the database instance ORCL in the ORACLE_HOME\DATABASE directory has ORCL as part of its name (for example, CTL1ORCL.ORA, LOG1ORCL.ORA, and INITORCL.ORA). The instance name is the same as the value of the ORACLE_SID registry configuration parameter.  

To connect to a specific Oracle database, users must specify a service name (database alias) that contains a SID for that database. 

OracleStartSID 

Starts the database instance SID automatically whenever the Windows NT computer restarts. 

OracleTNSListener801 

Listens for and accepts incoming connection requests from client applications. Automatically starts when the Windows NT computer restarts. 
 
1 This is the name for this service if you have only one Oracle home directory on your computer. Each additional Oracle home directory on your computer uses the naming convention OracleHOME_NAMETNSListener80 for this service. See Chapter 6, "Using Multiple Oracle Homes" for information.

See Appendix F, "Troubleshooting" for error messages that you can receive if you attempt to connect to the Oracle8 database without these services running.

Additional Oracle services related to specific products or database features are also available:

Service Name  Description 

OracleAgent 

Listens for and responds to job and event requests sent from the Oracle Enterprise Manager console. 

OracleConTextService801 

ConText server processes started on an NT server are normally terminated by Windows NT when the user logs off. This service can be used to start server processes that survive logouts. 

OracleExtprocAgent1 

Enables external procedure callouts from PL/SQL to the database to be implemented with multiple, light-weight threads instead of a single dedicated process. 

OracleWebAssistant2 

Enables information from database queries to be published to a Web page at specified time intervals. 
 
1 These are the names for these services if you have only one Oracle home directory on your computer. Each additional Oracle home directory on your computer uses the naming convention OracleHOME_NAMEConTextService80 or OracleHOME_NAMEExtprocAgent for these services. See Chapter 6, "Using Multiple Oracle Homes" for information. 
2 This is the name for this service if you have only one Oracle home directory on your computer. Each additional Oracle home directory on your computer uses the naming convention OracleWebAssistant1, OracleWebAssistant2, and so on for this service. See Chapter 6, "Using Multiple Oracle Homes" for information.

Services for network products are also available. See Net8 Getting Started for Windows NT and Windows 95/98 for information on Oracle network services.

Starting Oracle Services

Oracle services must be started for you to use the Oracle8 database and its products.

Start Oracle services in either of two ways:

To start Oracle Services from the Control Panel:

  1. Choose Start > Settings > Control Panel.

    2. The Control Panel window appears.
     

  2. Double-click Services.

    3. The Services dialog box appears.
     

  3. Find the service you want to start in the list, and verify that it has a status of Started. If it does not, select it and choose Start.
  4. Click Close to exit the Services dialog box.

To start Oracle Services from the MS-DOS command prompt:

Enter the following command to start an Oracle service at the MS-DOS command prompt: 

C:\> NET START SERVICE

where SERVICE is a specific service name, such as OracleServiceORCL.

If you cannot find OracleServiceSID or OracleTNSListener80 (or OracleHOME_NAMETNSListener80) in the list, use ORADIM80 to create them. See Chapter 9, "Creating a Database" for instructions on using ORADIM80.

Stopping Oracle Services

On occasion (for example, if you want to re-install the Oracle8 database), you must stop Oracle services. Stop Oracle services in either of two ways:

To stop Oracle8 Services from the Control Panel:

  1. Choose Start > Settings > Control Panel.

    2. The Control Panel window appears.
     

  2. Double-click Services.

    3. The Services dialog box appears.
     

  3. Select OracleTNSListener80 (or OracleHOME_NAMETNSListener80, where HOME_NAME is the Oracle home name for the listener to stop) and choose Stop.
  4. Select OracleServiceSID and choose Stop.

    5. The Stopping dialog box informs you that OracleStartSID will also be stopped.
     

  5. Click OK.

    6. Both OracleServiceSID and OracleStartSID are stopped.

To stop Oracle Services from the MS-DOS command prompt:

Enter the following command to stop an Oracle service at the MS-DOS command prompt: 

C:\> NET STOP SERVICE

where SERVICE is a specific service name, such as OracleServiceORCL.

Auto-starting Oracle Services

You can start Oracle services whenever the Windows NT computer is restarted. Use the Service dialog box to configure when and how the Oracle8 database is started.

To automatically start the Oracle8 database each time you restart:

  1. Choose Start > Settings > Control Panel.

    2. The Control Panel window appears.
     

  2. Double-click Services.

    3. The Services dialog box appears.
     

  3. Select the service OracleStartSID and choose the Startup button.

    4. The Service dialog box appears.
     

  4. Choose Automatic from the Startup Type field.
  5. Click OK.
  6. Click Close to exit the Services dialog box.

Starting and Shutting Down a Database with Server Manager

These instructions assume that a database instance is created and the services are started.

To start or shut down an Oracle8 database:

  1. Go to your Oracle8 database server.
  2. Start Server Manager at the MS-DOS command prompt:
    3. C:\> SVRMGR30
  3. Connect to the Oracle8 database with the INTERNAL user name:
    4. SVRMGR> CONNECT INTERNAL/PASSWORD
  4. Follow the instructions below:


If You Want to...  Then Enter... 

Start a database with the default parameter file 

SVRMGR> STARTUP  

This command uses the default INITSID.ORA file located in the ORACLE_HOME\ DATABASE directory. 

Start a database with a file other than the default parameter file 

SVRMGR> STARTUP PFILE=PATH\FILENAME  

This command uses the INITSID.ORA file specified in PATH\FILENAME. This example starts the database using a file named INIT2.ORA in C:\ORANT \RDBMS80: 

 

SVRMGR> STARTUP PFILE=C:\ORANT\RDBMS80\INIT2.ORA 

Stop the database 

SVRMGR> SHUTDOWN [MODE] 

 

where MODE is one of the following: 

 
  • Normal 
 

 

          The database waits for all currently connected users to disconnect and disallows any new 

          connections before shutting down. If you execute the SHUTDOWN command without any
          option, it defaults to this mode. 

 
  • Immediate 

 

          The database terminates and rolls back active transactions, disconnects clients, and 

          shuts down. 

 
  • Abort 
 

 

          The database terminates active transactions and disconnects users; it does not roll back 

          transactions. The database performs automatic recovery and rollback the next time it is 
          started. Use this mode only in emergencies. 
 
 
  1. Exit Server Manager:
    2. SVRMGR> EXIT
  2. You are returned to the MS-DOS command prompt.

    3. Note:  

    See "Choosing a Database Tool" in Chapter 3, "Database Tools Overview" for a list of other tools that can start the database and the Oracle8 Administrator's Guide for information on options you can specify when starting your database. 

     
     

Starting and Shutting Down a Database with Oracle Enterprise Manager

Oracle Enterprise Manager enables you to start and shut down your Oracle8 database in several different ways. This section describes how to use the Navigator and Instance Manager. You can also use SQL Worksheet.

See the Oracle Enterprise Manager Administrator's Guide for information on using these tools to start your database.

These instructions assume that a database instance is created and the services are started.

To start or shut down a database:

  1. Ensure that you:
  2. Go to your Oracle Enterprise Manager Console computer.
  3. Choose Start > Programs > Oracle Enterprise Manager > Enterprise Manager.

    4. The Repository Login Information dialog box appears:

  4. Enter the login information you created in "Step 2: Create a Repository User Account" of Chapter 8, "Post-Installation Configuration Tasks":

    5. The Oracle Enterprise Manager Console appears. The Navigator Window displays in the upper-left portion of the console.

  5. Double-click Databases in the Navigator window of the Oracle Enterprise Manager Console.

    6. The list of databases in your Oracle Enterprise Manager network appears.

  6. If you have never started or shut down a database with the Navigator, you must first perform steps 6a through 6h. If you have previously started or shut down a database with the Navigator, go to step 7.
    1. Select the database to administer.
    2. Choose Tools > Applications > Oracle Instance Manager from the main menu.

      3. The Login Information dialog box appears.

    3. Enter the INTERNAL user name and password, and Net8 service name for the Oracle8 database to start up or shut down.
    4. Click OK.

      5. The Oracle Instance Manager window appears.

    5. Double-click Initialization Parameters in the Navigator tree.

      6. The initialization parameters appear for the Oracle8 database that you want to start or shut down.

    6. Click Save.

      7. The Save Configuration dialog box appears.

    7. Enter an appropriate configuration name for the initialization parameters (for example, SALES_DB) and click OK.

      8. This action stores the initialization parameter information for the managed Oracle8 database in the repository.

    8. Choose Exit from the File menu.

      9. You are returned to the Oracle Enterprise Manager Console.

  7. Right-click the database in the Navigator tree that you want to start or stop.

    8. A menu appears with options for starting or shutting down the database:

  8. If you have never started or shut down a database with the Navigator, you must first perform steps 8a through 8b. If you have previously started or shut down a database with the Navigator, go to step 9.
    1. Choose Connect from the menu that appears.

      2. The Login Information dialog box appears.

    2. Enter the INTERNAL user name and password, and click OK.

      3. You are returned to the same menu with options for starting and shutting down the database.

  9. Select one of the following:


    10. If You Want to...  Then... 

    Start the database 
    1. Choose Startup. 
     

     

    The Startup dialog box appears: 
     

     

     
    1. Provide the appropriate information and choose OK. 
     

     

    Your Oracle8 database starts. 

     

    Shut down the database 
    1. Choose Shutdown. 
     

     

    The Shutdown Options dialog box appears: 
     

     

     
    1. Provide the appropriate information and choose OK. 
     

     

    Your Oracle8 database shuts down. 

     
     
     

Shutting Down a Database By Stopping a Service

You can immediately shut down the Oracle8 database by stopping the service OracleServiceSID. This automated procedure is equivalent to manually entering the following commands: 

C:\> SVRMGR30
SVRMGR> CONNECT INTERNAL/PASSWORD
SVRMGR> SHUTDOWN IMMEDIATE

This causes the database to terminate and roll back active transactions, disconnect clients, and shut down.

To use this feature, you must manually set either of two registry parameter values to TRUE in the registry:

Registry Parameter  When set to TRUE... 

ORA_SHUTDOWN 

Enables the selected Oracle8 database to be shut down. This includes any database in the current Oracle home. 

ORA_SID_SHUTDOWN 

Shuts down the Oracle8 database identified by the SID value. 
 

If either of these parameters is set to FALSE (the default setting), you cannot shut down the database by stopping OracleServiceSID. In addition, two other registry parameters are available:

ORA_SHUTDOWN_TIMEOUT, ORA_SID_SHUTDOWN, and ORA_SID_SHUTDOWN_TIMEOUT must be added to the registry. Where to add these parameters is determined by the Oracle home directory that you are using:

If You Have...  Then Add These Parameters in... 

One home directory 

HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE 

Additional directories 

HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEID  

where ID is incremented for each additional Oracle home directory on your computer. 
 

To immediately shut down the database by stopping OracleServiceSID:

  1. Set ORA_SHUTDOWN or ORA_SID_SHUTDOWN to TRUE in the registry. The exact location of these parameters is determined by the number of Oracle home directories on your computer:


    2. If You Have...  These Parameters are Located in... 

    One home directory 

    HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE 

    Two or more home directories 

    HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\ HOMEID  

    where ID is incremented for each additional Oracle home directory on your computer. 
     

    See Appendix C, "Configuration Parameters and the Registry" for instructions on adding and editing registry parameters.

  2. Stop and restart OracleServiceSID and restart the database for the change to take effect.
  3. Choose Start > Settings > Control Panel.

    4. The Control Panel window appears.

  4. Double-click Services.

    5. The Services dialog box appears.

  5. Select OracleServiceSID and choose Stop.

    6. This automatically starts Server Manager, issues the SHUTDOWN IMMEDIATE command, and shuts down your Oracle8 database.

Running Multiple Instances

To run multiple instances, ensure that you have already created each instance and started the services for each instance using ORADIM80 or the Services dialog box in Windows NT. You then run multiple instances by starting each of the instances using Server Manager.

To run multiple instances:

  1. Ensure that you have already created each instance.
  2. Ensure that you started the services for each instance using ORADIM80 or the Services dialog box of the Windows NT Control Panel.
  3. Set the ORACLE_SID configuration parameter at the MS-DOS command prompt to the SID for each instance you want to run:
    4. C:\> SET ORACLE_SID=SID

    where SID is the name of the Oracle8 database instance.

  4. Start Server Manager:
    5. C:\> SVRMGR30
  5. Connect as INTERNAL:
    6. SVRMGR> CONNECT INTERNAL/PASSWORD
  6. Start up the database with the new instance:
    7. SVRMGR> STARTUP PFILE=ORACLE_HOME\DATABASE\INITSID.ORA

    where SID is the name of the instance. With Server Manager, you can use the %ORACLE_HOME% variable for ORACLE_HOME.

Creating Password Files

Use the Password Utility ORAPWD80 to create password files. ORAPWD80 is automatically installed with the Oracle8 Utilities. Password files are located in the ORACLE_HOME\DATABASE directory and are named PWDSID.ORA, where SID identifies the Oracle8 database instance. Password files can be used for local or remote connections to an Oracle8 database. The example below describes how to perform a local connection.

To create a password file:

  1. Create a password file with ORAPWD80:
    2. C:\> ORAPWD80 FILE=PWDSID.ORA PASSWORD=PASSWORD ENTRIES=MAX_USERS

    The essential elements of a password file are:

    Element  Description 

    FILE 

    Specifies the password file name. 

    PASSWORD 

    Sets the password for the INTERNAL and SYS accounts. 

    ENTRIES 

    Sets the maximum number of entries in the password file. This corresponds to the maximum number of distinct users allowed to connect to the database with the SYSDBA and SYSOPER DBA privileges simultaneously. 
     

  2. Set the INITSID.ORA file parameter REMOTE_LOGIN_PASSWORDFILE to EXCLUSIVE or SHARED. Definitions for all possible values are described below:


    3. Element  Description 

    EXCLUSIVE 

    Specifies that only one instance can use the password file and that the password file contains names other than SYS and INTERNAL. Oracle8 looks in the registry for the value of the ORA_SID_PWFILE parameter. If a value is unspecified, it looks in the registry for the value of the ORA_PWFILE parameter, which points to a file containing the INTERNAL password as well as user names, passwords, and privileges. If that is not set, it uses the default of ORACLE_HOME\DATABASE\PWDSID.ORA. 

    SHARED 

    Specifies that multiple instances can use the password file (for example, a parallel server environment). However, the only users recognized by the password file are SYS and INTERNAL. You cannot log in with SYSOPER or SYSDBA privileges even if those privileges are granted in the password file. The SHARED value of this parameter affords backward compatibility with earlier releases. The Oracle8 database looks for the same files as it does when the value is EXCLUSIVE, but only the INTERNAL account is available for privileged access. This is the default value. 

    NONE 

    Specifies that the Oracle8 database ignores the password file and that privileged users are authenticated by the Windows NT operating system. 
     

  3. Start Server Manager:
    4. C:\> SVRMGR30
  4. Connect as INTERNAL:
    5. SVRMGR> CONNECT INTERNAL/PASSWORD
  5. Start the Oracle8 database:
    6. SVRMGR> STARTUP
  6. Grant appropriate privileges to each user who needs to perform database administration. For example:
    7. SVRMGR> GRANT SYSDBA TO SCOTT;

    If successful, the following message displays: 

    Statement Processed.

    This adds SCOTT to the password file and enables SCOTT to connect to the database with SYSDBA privileges. Use Server Manager to add or delete user names, user passwords, and user privileges in password files.

  7. Connect to the Oracle8 database with DBA privileges for SCOTT:
    8. SVRMGR> CONNECT SCOTT/TIGER AS SYSDBA

    You are connected to the Oracle8 database.

    Caution:  

    Copying or manually moving password files may result in ORADIM80 not being able to find a password to start an instance. 

     
     

    The password file is automatically hidden. This table describes how to see the password file:

    To...  Enter... 

    See the password file 

    C:\ORANT\DATABASE> ATTRIB  

    The password file displays:  

    A H C:\ORANT\DATABASE\PWDSID.ORA 

    Make the password file visible 

    C:\ORANT\DATABASE> ATTRIB -H PWDSID.ORA  

    Note: The password file must be visible before you can move or copy it. 

    Hide the password file again 

    C:\ORANT\DATABASE> ATTRIB +H PWDSID.ORA 
     
     

Connecting as INTERNAL with a Password File

You can connect as INTERNAL with a password file. The password for INTERNAL is ORACLE if you installed Oracle8 Enterprise Edition through the Oracle8 Enterprise Edition option. If you installed Oracle8 Enterprise Edition through the Custom installation option, the password for INTERNAL is whatever you entered when prompted during installation.

To connect as INTERNAL with a password file:

  1. Follow the procedures in "Creating Password Files" to create a password file with ORAPWD80.
  2. Set the INITSID.ORA file parameter REMOTE_LOGIN_PASSWORDFILE to EXCLUSIVE or SHARED.

    3. Note: When REMOTE_LOGIN_PASSWORDFILE is set to NONE, connecting remotely to a database as INTERNAL is prohibited even if the correct password is supplied. 

     
     
  3. Start Server Manager:
    4. C:\> SVRMGR30
  4. Connect to your Oracle8 database as follows:
    5. SVRMGR> CONNECT INTERNAL/PASSWORD

    where PASSWORD is the password created with ORAPWD80 or ORADIM80.

Changing the INTERNAL Password

Change the INTERNAL user account password with either ORADIM80 or ORAPWD80.

To change the password with ORADIM80:

  1. Delete the SID for the password you want to change:
    2. C:\> ORADIM80 -DELETE -SID SID

    where SID is the SID to delete.

  2. Create the same SID again and specify a new INTERNAL password:
    3. C:\> ORADIM80 -NEW -SID SID -INTPWD NEW_PASSWORD - MAXUSERS N

    where SID is the same SID to recreate, NEW_PASSWORD is the new INTERNAL password, and N is the maximum number of DBAs/operators who can be logged in at once with this password.

To change the password with ORAPWD80:

See the Oracle8 Administrator's Guide for specific instructions on using the ORAPWD80 Password Utility.

Encrypting Database Passwords

With the Oracle8 database, you can encrypt the password used to verify a remote database connection.

To enable password encryption:

  1. Add DBLINK_ENCRYPT_LOGIN to the initialization parameter INITSID.ORA file on the server computer.
  2. Set DBLINK_ENCRYPT_LOGIN equal to TRUE.
  3. Set the ORA_ENCRYPT_LOGIN configuration variable in the client computer to TRUE. See Appendix C, "Configuration Parameters and the Registry" for instructions on adding and setting configuration parameters in the registry.

Once these parameters are set to TRUE, whenever a user attempts a remote login, the Oracle8 database encrypts the password before sending it to the remote database. If the connection fails, the failure is noted in the audit log. The Oracle8 database then checks if either of these parameters is set to FALSE. If so, the Oracle8 database attempts the connection again using an unencrypted version of the password. If the connection is successful, the success is noted in the audit log, and the connection proceeds.

Note:  

Releases prior to release 7.1 do not support encrypted passwords. If you are connecting to an earlier version of the Oracle database, you must set the initialization parameter DBLINK_ENCRYPT_LOGIN to FALSE for the connection to succeed. 

 
 

Archiving Redo Log Files

When running Oracle Installer, there are two configuration options for installing an Oracle8 database. This table describes the archiving options provided with each option:

Configuration Option  What is the Archive Mode?  Is Automatic Archiving Enabled? 

Typical 

Automatically set to NOARCHIVELOG 

No 

Custom (through Oracle Database Assistant) 

Enables you to create your Oracle8 database in ARCHIVELOG mode by selecting the Archive Log check box of Oracle Database Assistant 

No 
 

In NOARCHIVELOG mode, redo logs are not archived. This protects the database from instance failure, but not from disk failure. Setting your archive mode to ARCHIVELOG and enabling automatic archiving causes redo log files to be archived. This protects the database from both instance and disk failure.

This section describes how to change the archive mode to ARCHIVELOG and enable automatic archiving. See the chapter "Archiving Redo Information" of the Oracle8 Administrator's Guide for complete descriptions of the ARCHIVELOG and NOARCHIVELOG modes.

Step 1: Change the Archive Mode to ARCHIVELOG

To change the archive mode to ARCHIVELOG:

  1. Start Server Manager at the MS-DOS command prompt:
    2. C:\> SVRMGR30
  2. Connect to the Oracle8 database with the INTERNAL user name:
    3. SVRMGR> CONNECT INTERNAL/PASSWORD
  3. If the database is open, shut it down:
    4. SVRMGR> SHUTDOWN
  4. Mount the database:
    5. SVRMGR> STARTUP MOUNT
  5. Enter the following command:
    6. SVRMGR> ARCHIVE LOG LIST

    The following output indicates the database is not in archive mode: 

    Database log mode              No Archive Mode
Automatic archival             Disabled
Archive destination            %RDBMS80%\
Oldest online log sequence     34
Current log sequence           37
  6. Change the archive mode to ARCHIVELOG:
    7. SVRMGR> ALTER DATABASE ARCHIVELOG;
  7. Enter the following command:
    8. SVRMGR> ARCHIVE LOG LIST

    The following output indicates the database is now in archive mode: 

    Database log mode              Archive Mode
Automatic archival             Disabled
Archive destination            %RDBMS80%\
Oldest online log sequence     34
Current log sequence           37
  8. Open the database:
    9. SVRMGR> ALTER DATABASE OPEN;
  9. Continue to "Step 2: Enable Automatic Archiving".

Step 2: Enable Automatic Archiving

To enable automatic archiving:

  1. Open the ORACLE_HOME\DATABASE\INITSID.ORA file.
  2. Find the following three parameters:
    3. # LOG_ARCHIVE_START = TRUE
# LOG_ARCHIVE_DEST = %ORACLE_HOME%\DATABASE\ARCHIVE
# LOG_ARCHIVE_FORMAT = "%%ORACLE_SID%%T%TS%S.ARC"
  3. Remove the # sign from in front of each.

    4.  
    Note:  

    The double quotes around LOG_ARCHIVE_FORMAT do not need to be removed. 

     
     
  4. Edit the LOG_ARCHIVE_DEST value to identify an existing drive and directory in which to archive your filled redo logs.
  5. Edit the LOG_ARCHIVE_FORMAT value to indicate the appropriate archiving format:

    6. Format  Description  Example 

    %%ORACLE_SID%%%T.ARC 

    Specifies the thread number. This number is padded to the left by zeroes. The default value is one with a range of up to three characters. 

    SID0001.ARC 

    %%ORACLE_SID%%%S.ARC 

    Specifies the log sequence number. This number is padded to the left by zeroes. The default value is one with a range of up to five characters. 

    SID0001.ARC 

    %%ORACLE_SID%%%t.ARC 

    Specifies the thread number. The number is not padded. The default value is one with no range limit on characters. 

    SID1.ARC 

    %%ORACLE_SID%%%sARC 

    Specifies the log sequence number. The number is not padded. The default value is one with no range limit on characters. 

    SID1.ARC 
     
  6. Save your changes.
  7. Exit the file.
  8. Shut down the database:
    9. SVRMGR> SHUTDOWN
  9. Restart the database
    10. SVRMGR> STARTUP
  10. Enter the following command:
    11. SVRMGR> ARCHIVE LOG LIST

    The following output indicates that automatic archiving of redo log files is enabled and an archiving destination is specified: 

    Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            C:\BACKUP
Oldest online log sequence     34
Current log sequence           37

Using the ORADEBUG Utility

The ORADEBUG utility is a debugging tool that sends debug commands through Server Manager to Oracle processes. It is primarily for use by developers and Oracle Support Services personnel. Only use this utility when instructed to do so by Oracle Support Services. Note that you must have database administrator privileges to use ORADEBUG.

To start ORADEBUG:

  1. Start Server Manager from the MS-DOS command prompt and connect to the database as INTERNAL. For example:
    2. C:\> SVRMGR30

SVRMGR> CONNECT INTERNAL/PASSWORD
  2. Enter the following at the Server Manager prompt:
    3. SVRMGR> ORADEBUG

    ORADEBUG runs and prompts you for parameters. To obtain a list of these parameters, enter the following at the Server Manager prompt: 

    SVRMGR> ORADEBUG HELP

    The output from most debug commands is written to a trace file. Trace files are created in the directory specified by the INITSID.ORA initialization parameters BACKGROUND_DUMP_DEST and USER_DUMP_DEST. By default, these parameters are set to ORACLE_HOME\RDBMS80\TRACE. If you want to find the location of your trace file, enter the following at the Server Manager prompt: 

    SVRMGR> ORADEBUG TRACEFILE_NAME

    If the output from a debug command produces more than one line of output, the result is sent to a trace file, and a message indicating that the command has completed is relayed to Server Manager. If the output from a debug command produces only one line of output, the output is relayed directly to Server Manager.

    Note:  

    There is currently a limitation when using ORADEBUG that can cause Server Manager to hang if you attempt to debug a thread that is blocking on input/output (I/O) until that I/O completes. 

     
     

 
Prev		  
Next
 		 Oracle 
Copyright © 1998 Oracle Corporation.
All Rights Reserved. 
 
Library		  
Product		  
Contents		  
Index