SQL*DBA to Oracle Server Manager Migration Guide Go to Product Documentation Library
Library
Go to books for this product
Product
Go to Contents for this book
Contents



Go to previous file in sequence Go to next file in sequence

Migration Considerations


This chapter describes items to consider when you migrate from SQL*DBA to Oracle Server Manager:

Attention: Beginning with Oracle7 release 7.3, SQL*DBA will not be included as part of the database product set. Oracle Server Manager will be the only database administration tool provided with Oracle7 release 7.3.


Launching Applications

Several differences exist between launching Server Manager and launching SQL*DBA.

Modes

SQL*DBA

SQL*DBA used a variety of methods for starting up in different modes, including command line parameters or environment variables.

Server Manager

Server Manager graphical mode and the Server Manager line mode tool are separate applications.

Initialization

SQL*DBA

When initializing, SQL*DBA looked for a SQL script and executed the commands. This occurred before SQL*DBA either executed the user-specified SQL script or accepted user input, depending on the SQL*DBA startup parameters. The location of the script was operating system dependent. For example, on UNIX, the file name was:

$ORACLE_HOME/rdbms/admin/sqldba.sql

If this file was not present then SQL*DBA would generate error DBA-00383.

Server Manager

Server Manager does not use a startup script. DBA's using graphical mode Server Manager can take advantage of its launch in context feature to perform many initialization steps. DBA's using Server Manager line mode can also startup and execute a script by using the COMMAND parameter. Refer to the Oracle Server Manager User's Guide for more information about the launch in context feature and using Server Manager in line mode.

Attention: Server Manager requires a specific order for STARTUP parameters. The following table summarizes Server Manager STARTUP parmeters and where they must appear:

STARTUP Parameters Position
FORCE Anywhere after STARTUP
RESTRICT Anywhere after STARTUP
PFILE=<filename> Anywhere after STARTUP
OPEN | MOUNT | NOMOUNT Anywhere after STARTUP
RECOVER Immediately following OPEN
<database name> Immediately following OPEN or MOUNT
EXCLUSIVE | SHARED/ PARALLEL Anywhere after STARTUP
RETRY Immediately following SHARED/PARALLEL
QUIET Anywhere after STARTUP

Display of Line Numbers

SQL*DBA supported an environment variable for turning off the display of line numbers when entering multi-line commands. Server Manager does not support this feature.

Note: For additional information about compatibility issues between SQL*DBA and Server Manager, refer to Appendix A in this guide.


SQL Scripts

Server Manager is designed to be compatible with existing SQL*DBA scripts. However, during migration, some SQL scripts might need minor modifications.

LOGWIDTH

SQL*DBA allowed you to specify the width of spooled log files using the LOGWIDTH parameter. Server Manager does not support this parameter and only inserts end-of-line characters at the end of the lines.

STARTUP

If an error occurred during an intermediate step of a STARTUP command, SQL*DBA would shut down the database. Server Manager, in the same scenario, leaves the database in the last successfully completed state.

Note: This may have implications for the types of procedures you choose to use in recovering from a failed startup.

PFILE

Specific to the optional PFILE=filename parameter in both SQL*DBA and Server Manager, the equal sign ( = ) character was optional for SQL*DBA but is required for Server Manager.

Line Mode

SQL*DBA line mode aborted processing a SQL statement if a blank line was input. It was possible to have a malformed statement in a SQL script which did not cause an error because it was followed by a blank line. This caused the command to be aborted and SQL*DBA to proceed to the next command. A common example of this occurred when an improper comment syntax had been used in the script.

For example, a script which uses a SQL comment:

/*   . . .   */

in between valid SQL statements is incorrect. But if the comment was followed by a blank line, the command processing would be aborted and no error would be generated.

Server Manager does not abort processing a SQL statement if a blank line is inserted into it. As a result, a script which contained a problem that remained hidden while using SQL*DBA may generate an error while using Server Manager.

Spool Files

The name of the default spool file is different for the Server Manager than for SQL*DBA. The default spool file is the file to which output is spooled if no filename is specified with the SPOOL command.

The default spool filename for Server Manager is system specific.




Go to previous file in sequence Go to next file in sequence
Prev Next
Oracle
Copyright © 1996 Oracle Corporation.
All Rights Reserved.
Go to Product Documentation Library
Library
Go to books for this product
Product
Go to Contents for this book
Contents