Re: Oracle 8.1.6 on Windowns 2000

From: Bartek Papisz <Bartek.Papisz_at_quantum.pl>
Date: Thu, 15 Feb 2001 13:57:02 +0100
Message-ID: <982241832.708036@kwark.quantum.pl>

I had this oneself problem on Win2000 server and Oracle 8. 1. 7 problem I unknotted profiting from help Oracle here instruction :

Article-ID:         <Note:61621.1>
Alias:              OLS:11553533.61
Circulation:        PUBLISHED (EXTERNAL)
Folder:             platform.Microsoft.NT
Topic:              5.  Oracle on Windows NT FAQs
Title:              WINNT/WIN2000: Recreating Oracle Services and Instances
                    from the Command Line
Document-Type:      BULLETIN
Impact:             MEDIUM
Skill-Level:        NOVICE
Server-Version:     07.03.04.XX to 08.01.06.XX
Updated-Date:       07-NOV-2000 20:30:37
References:         <61716.1:77627.1>
Authors:            ABARDEEN.US
Attachments:        NONE
Content-Type:       TEXT/PLAIN
Keywords:           WINNT; CONFIGINFO; WIN2000;
Products:           5/RDBMS (07.03.04.XX to 08.01.06.XX);
Platforms:          100;  912;

PURPOSE

This bulletin explains how to create new database services and delete existing database services for an Oracle7, Oracle8, and Oracle8i database on Windows NT or Windows 2000 using the Oracle Instance Manager ORADIM
utility. It also explains how to start or stop an existing database using the
ORADIM utility.

Please note that only versions 8.1.6 or higher of the database are supported on Windows 2000. For more information, please see <Note:77627.1> Oracle Database Server Product Support Matrix for Windows 2000.

SCOPE & APPLICATION

The intended audience for this article is Oracle DBAs who have a moderate knowledge of Oracle7 or Oracle8 Server and an in-depth knowledge of Windows NT. This bulletin makes the following assumptions:

Oracle 7.3, 8.0 or 8.1 has been successfully installed.
All commands will be issued at the server itself.
You are logged on to the Windows NT server as Administrator or a user with Administrator privileges.

CONVENTIONS AND DEFAULTS

For the purposes of this discussion, the following conventions are used:

< > indicates a value that you must provide.
[ ] indicates an optional value that you can provide.

ORADIMxx refers to the ORADIM program specific to your version:

      Oracle 7.3:     ORADIM73
      Oracle 8.0:     ORADIM80
      Oracle 8.1:     ORADIM   (no version designation)

All ORADIMxx commands are issued from a DOS Command Prompt. While the commands in the bulletin may span several lines, they should be entered as a single command line when typing them at the command prompt.

ORADIMxx messages are not displayed on the screen, instead they are logged to a file. The file is overwritten with each ORADIMxx command. The filenames and locations are:

     Oracle 7.3:  <oracle_home>\RDBMS73\ORADIM73.LOG
     Oracle 8.0:  <oracle_home>\RDBMS80\ORADIM80.LOG
     Oracle 8.1:  <oracle_home>\DATABASE\ORADIM.LOG

RELATED DOCUMENTS

<Note:61716.1> "ORACLE DATABASE SERVICES ON WINDOWS NT"

NAMING ORACLE INSTANCES ON NT

Each instance of the database on the Windows NT/2000 server must be uniquely identified by a System IDentifier (SID). For Oracle 7.3 and 8.0, this is a string that is one to four alphanumeric characters long; however, for Oracle 8.1, the SID can be up to 64 alphanumeric characters long.

BACKGROUND

In order to start an existing database or create a new database, the Windows NT service OracleService<sid> must be created. This is the only service that is required for an Oracle database.

For versions 7.3 and 8.0: Optionally you may wish to have the Windows NT service OracleStart<SID> created which allows the database to be started automatically when the server is booted.

For version 8.1: No other service is required to autostart the database upon server reboot. (See Chapter 9 of the Oracle8i Getting Started for Windows NT for more information.)

The ORADIMxx utility makes changes to the server's registry so the commands must be executed at the server itself. If you wish to do these from a remote workstation, you must use a utility, such as PCAnywhere, which allows you to update a remote server's registry.

You may need to create or recreate the database services for the following reasons:

You want to create a new database by running scripts or entering the create database commands manually. Before this can be done the database service for the new SID must exist.
The database is no longer automatically starting when the server boots. Provided that the database can be started manually, recreating the database services will usually resolve this issue.
You want to change the INTERNAL password and also update the services so that the database will start with the new INTERNAL password.

COMMAND LINE VS GUI ORADIM (Oracle7 ONLY!)

In Oracle7 the ORADIM73 utility has both a command line and GUI mode. (The GUI version of ORADIM was desupported in Oracle8 Version 8.0 as it is replaced by the Database Configuration Assistant.)

The ORADIM73 GUI mode, invoked by entering ORADIM73 without any command line options or by selecting NT Instance Manager from the Oracle for Windows NT program group, allows you to create or delete a database including its associated datafiles.

The command line version of ORADIM allows you to recreate the database services which does not affect the database files themselves. It also allows you to start up and shut down the database.

INSTRUCTIONS

I. DELETING EXISTING SERVICES

     If you are creating services for a new database, skip to Part II.
     A.   If you are recreating existing database services, the
          password file for the instance will be recreated.  If the value
          for the INIT.ORA parameter REMOTE_LOGIN_PASSWORDFILE is set to
          EXCLUSIVE and you have granted other users SYSDBA and/or SYSOPER
          privileges, you will need to regrant these privileges to the
          users.  The following query, executed by a user with DBA
          privileges, will display the users granted the SYSDBA and/or
          SYSOPER privileges:

               SELECT * FROM V$PWFILE_USERS;

     B.   Perform a clean shutdown of the database using the
          appropriate DBA tool (SVRMGR23, SVRMGR30 or SVRMGRL) or
          Oracle Enterprise Manager Instance Manager.  Stopping the
          OracleService<SID> does NOT perform a clean shutdown of the
          database.

     C.   At the Command Prompt, type:

          ORADIMxx  -DELETE  -SID  <SID>

          This command will delete the OracleService<SID> and (in 7.3 and
          8.0) OracleStart<sid> services.

     D.   Verify that both services have been removed by checking the
Windows
          NT/2000 Services from Control Panel.  If you already have the
          Services panel open, you must exit out and reopen it as it does
not
          refresh.  On some systems it may take 10 - 15 seconds for the
          services to be removed.

          Proceed to part II if both services have been removed.  If both
          services still exist, repeat steps C and D again.  You may also
          want to review the ORADIM log file for any error messages.

     E.   In some cases the OracleStart<SID> service may not get
          deleted.  You can manually remove that service, or any Oracle
          service, with the following command:

          ORADIMxx  -DELETE  -SRVC  <service_name>

            where service_name is the full name of the oracle
            service.  Multiple service names may be specified by
            separating them with commas:

            ORADIMxx  -DELETE  -SRVC  ORACLESERVICEORCL,
            ORACLESTARTORCL

         Again, verify that the services have been deleted before

proceeding.

II. CREATING SERVICES

ORADIMxx -NEW -SID <SID> -INTPWD <password> -STARTMODE <mode> -PFILE <pfile> where: sid is the database SID password is the password for INTERNAL mode is the startup mode for the services, either AUTO or MANUAL pfile is the full path and name of the INIT<sid>.ORA file
Review the ORADIM log file for any errors. In some cases the existing password file cannot be erased by ORADIM, typically if the properties of the file have been altered. There will be an error in the ORADIM log file to this effect. Move, rename, or delete the existing password file, PWD<sid>.ORA located by default in <oracle_home>\DATABASE. This is normally a hidden file so you may need to change the View options in Explorer to show hidden files.
Verify that the services were created.
- Important Note * The OracleService<SID> service will be started if you specified AUTO for the start mode. The OracleStart<SID> service will not be started as ORADIM does not know whether these services are for an existing database or for one that has not yet been created.
If there are any errors in step B or both services were not created you must follow the steps in Part I to delete the existing services before you can recreate them.

III. STARTING THE ORACLE SERVICES AND/OR DATABASE INSTANCE

ORADIMxx -STARTUP -SID <SID> -USRPWD <password> - STARTTYPE <type> -PFILE <pfile> where: sid is the database SID password is the password for INTERNAL type is the startup type. SRVC will start just the service. SRVC, INST will start both the service and the database instance. pfile is the full path and name of the INIT<SID>.ORA file
Review the ORADIM log for any errors.

IV. SHUTTING DOWN THE ORACLE DATABASE INSTANCE AND/OR SERVICES

ORADIMxx -SHUTDOWN -SID <SID> -USRPWD <password> - SHUTTYPE <type> -SHUTMODE <mode> where: sid is the database SID password is the password for INTERNAL type is the shutdown type. INST will shutdown just the database instance. INST, SRVC will shutdown both the database instance and the service. mode is the type of database shutdown: N for Normal, I for Immediate, or A for Abort
Review the ORADIM log for any errors.

Excuse me behind so long letter

Bartek Received on Thu Feb 15 2001 - 06:57:02 CST