crystal reports 2d barcode Starting Up the New Database in Font

Making QR Code JIS X 0510 in Font Starting Up the New Database

Shut down the current database if it s running, and start it up again with the updated init.ora parameter file under the new Oracle Database 10g home. You must use the new STARTUP UPGRADE command to start up your database under the Oracle 10.2 version, which tells Oracle to modify those initialization parameters that would otherwise cause errors during the upgrade (for example, the new startup mode will set the JOB_QUE_PROCESSES parameter to 0). The startup upgrade mode starts a restricted session and prepares the environment for the upgrade. Listing 8-2 shows how to start the database using the STARTUP UPGRADE command. Note that if you re storing your initialization parameter in the default location ($ORACLE_HOME/dbs), you don t need to specify its path when you use the STARTUP UPGRADE command. Listing 8-2. Starting the Database with the STARTUP UPGRADE Command [oracle@localhost admin]$ sqlplus /nolog SQL*Plus: Release 10.2.0.0.0 - Beta on Mon Feb21 16:43:14 2005 Copyright (c) 1982, 2004, Oracle. All rights reserved. SQL> CONNECT sys/sammyy1 AS SYSDBA Connected to an idle instance. SQL> STARTUP UPGRADE ORACLE instance started. Total System Global Area 314572800 bytes Fixed Size 1236756 Variable Size 99164396 Database Buffers 213909504 Redo Buffers 262144 Database mounted. Database opened. SQL> bytes bytes bytes bytes

Once you have brought up the database instance, you can create the Sysaux tablespace: SQL> CREATE TABLESPACE sysaux DATAFILE '/u10/oradata/prod/sysaux01.dbf' SIZE 500M REUSE EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO;

The database is now technically converted into an Oracle Database 10g version, as shown by the following query: SQL> SELECT * FROM V$VERSION BANNER ---------------------------------------------------------------Oracle Database 10g Enterprise Edition Release 10.2.0.0.0 - Beta PL/SQL Release 10.2.0.0.0 - Beta CORE 10.2.0.0.0 Beta TNS for Linux: Version 10.2.0.0.0 - Beta NLSRTL Version 10.2.0.0.0 - Beta SQL> In the next step, you actually upgrade the current database to the 10.2 version.

As of this writing, the Oracle Database 10g Release 2 (10.2) production version hasn t been officially released. The output from the previous SQL query notes that I used the 10.2 Beta version. While there could be changes in the final production version of the software, such changes will be focused on fixing bugs encountered during the Beta testing phase and won t introduce substantive functional modifications.

Although the database is opened and a query to V$VERSION reveals that your database is now an Oracle Database 10g database, you will have to run the upgrade script, which is your next task. Previously, each version of the Oracle server had a separate upgrade script. For Oracle 10.2, you need to use the same script to upgrade a database, no matter what its version, as long as it is in the upgrade-eligible list of database versions. This brand-new upgrade script is called catupgrd.sql, and it can be found in $ORACLE_HOME/rdbms/admin. This script automatically runs the appropriate upgrade script for the database version you re upgrading and uses procedures from the DBMS_REGISTRY package to execute various component upgrades. Make sure you re logged in as a user with SYSDBA privileges, and run the upgrade script from the new environment: SQL> @$ORACLE_HOME/rdbms/admin/catupgrd.sql

Oracle will create, drop, and alter some database objects as the upgrade process progresses, thus invalidating some internal Oracle packages and procedures. After the upgrade script has finished, you need to check for invalid objects: SQL> SELECT count(*) FROM DBA_OBJECTS 2 WHERE status = 'INVALID';

By running the Oracle-provided utlrp.sql script, you can do a recompilation and validation of all the objects invalidated during the upgrade process. During this process, utlrp.sql calls utlprp.sql (a wrapper based on the UTL_RECOMP package). Note that Oracle will dynamically compile each of the invalidated objects when they are accessed if you don t do it now. However, this runtime compilation of invalidated objects could slow down your database s performance.