SQL*DBA to Oracle Server Manager Migration Guide | ![]() Library |
![]() Product |
![]() Contents |
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.
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 |
Note: For additional information about compatibility issues between SQL*DBA and Server Manager, refer to Appendix A in this guide.
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.
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.
The default spool filename for Server Manager is system specific.
![]() ![]() Prev Next |
![]() Copyright © 1996 Oracle Corporation. All Rights Reserved. |
![]() Library |
![]() Product |
![]() Contents |