| Oracle® Streams Concepts and Administration 10g Release 1 (10.1) Part Number B10727-01 |
|
|
View PDF |
| Oracle® Streams Concepts and Administration 10g Release 1 (10.1) Part Number B10727-01 |
|
|
View PDF |
This appendix describes performing certain maintenance operations on an Oracle database with little or no down time. These maintenance operations include upgrading to a new version of the Oracle Database, migrating an Oracle Database to a different operating system or character set, upgrading user-created applications, and applying Oracle Database patches. The maintenance operations described in this appendix use the features of Oracle Streams to achieve little or no database down time.
This appendix contains these topics:
The following operations typically require substantial database down time:
You can achieve these maintenance operations with little or no down time by using the features of Oracle Streams. To do so, you use Oracle Streams to configure a single source replication environment where the original database is the source database and a copy of the database is the destination database for the changes made at the source.
Specifically, you can use the following general steps to perform the maintenance operation while the database is online:
The upgrade instructions in this appendix assume that all of the following statements are true for the database being upgraded:
The following sections provide detailed instructions for completing one of the maintenance operations:
To use Streams for a database version upgrade, the database must be Oracle9i release 2 (9.2). Before you begin the database version upgrade, decide whether you want to use the original Export/Import utilities or the Recovery Manager (RMAN) utility to instantiate the destination database during the operation. The destination database will replace the existing database that is being upgraded.
Consider the following factors when you make this decision:
Also, Oracle Corporation recommends that you do not use RMAN for instantiation in an environment where distributed transactions are possible. Doing so may cause in-doubt transactions that must be corrected manually.
After you decide which utility you want to use for instantiation, complete the steps in the appropriate section:
Complete the following steps to perform a database version upgrade using Export/Import and Oracle Streams:
See the Oracle installation guide for your operating system if you need to install Oracle, and see Oracle Database Administrator's Guide for information about creating a database.
Make sure the destination database has a different global name than the source database. This example assumes that the global name of the source database is orcl.net and the global name of the destination database during the upgrade is stms.net. The global name of the destination database is changed when the destination database replaces the source database at the end of the upgrade process.
NCLOB, LONG, LONG RAW, BFILE, ROWID, and UROWID, and user-defined types (including object types, REFs, varrays, and nested tables). In addition, Streams did not support temporary tables, index-organized tables, or object tables. See Oracle9i Streams for complete information about unsupported database objects.strmadmin. This Streams administrator will be copied automatically to the destination database during instantiation.CONNECT SYSTEM/MANAGER@orcl.net ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS;
SYS.AnyData queue that will stage changes made to the source database during the upgrade process. For example:
CONNECT strmadmin/strmadminpw@orcl.net EXEC DBMS_STREAMS_ADM.SET_UP_QUEUE();
CONNECT strmadmin/strmadminpw@orcl.net BEGIN DBMS_STREAMS_ADM.ADD_GLOBAL_RULES( streams_type => 'capture', streams_name => 'capture', queue_name => 'streams_queue', include_dml => true, include_ddl => true, include_tagged_lcr => true, source_database => NULL); END; /
Do not start the capture process.
CONSISTENT export parameter set to y:
exp SYSTEM/password FULL=y FILE=instant.dmp GRANTS=y ROWS=y CONSISTENT=y
STREAMS_INSTANTIATION import parameter set to y and the STREAMS_CONFIGURATION import parameters set to n:
imp SYSTEM/password FULL=y FILE=instant.dmp COMMIT=y LOG=import.log STREAMS_INSTANTIATION=y STREAMS_CONFIGURATION=n
See Oracle Database Utilities for information about performing an export/import using the original Export and Import utilities.
DBA_JOBS data dictionary view to list the jobs.SYS.AnyData queue. For example:
CONNECT strmadmin/strmadminpw@stms.net BEGIN DBMS_STREAMS_ADM.REMOVE_QUEUE( queue_name => 'strmadmin.streams_queue', cascade => false, drop_unused_queue_table => true); END; /
SYS.AnyData queue. This queue will stage changes propagated from the source database. For example:
CONNECT strmadmin/strmadminpw@stms.net EXEC DBMS_STREAMS_ADM.SET_UP_QUEUE();
CONNECT strmadmin/strmadminpw@orcl.net CREATE DATABASE LINK stms.net CONNECT TO strmadmin IDENTIFIED BY strmadminpw USING 'stms.net';
CONNECT strmadmin/strmadminpw@orcl.net BEGIN DBMS_STREAMS_ADM.ADD_GLOBAL_PROPAGATION_RULES( streams_name => 'orcl_to_stms', source_queue_name => 'strmadmin.streams_queue', destination_queue_name => 'strmadmin.streams_queue@stms.net', include_dml => true, include_ddl => true, include_tagged_lcr => true, source_database => 'orcl.net'); END; /
CONNECT strmadmin/strmadminpw@stms.net BEGIN DBMS_STREAMS_ADM.ADD_GLOBAL_RULES( streams_type => 'apply', streams_name => 'apply', queue_name => 'strmadmin.streams_queue', include_dml => true, include_ddl => true, include_tagged_lcr => true, source_database => 'orcl.net'); END; /
Complete the following steps to perform a database version upgrade using Recovery Manager (RMAN) and Oracle Streams:
See the Oracle installation guide for your operating system if you need to install Oracle, and see Oracle9i Database Administrator's Guide for information about creating a database.
Make sure the destination database has a different global name than the source database. This example assumes that the global name of the source database is orcl.net and the global name of the destination database during the upgrade is updb.net. The global name of the destination database is changed when the destination database replaces the source database at the end of the upgrade process.
NCLOB, LONG, LONG RAW, BFILE, ROWID, and UROWID, and user-defined types (including object types, REFs, varrays, and nested tables). In addition, Streams did not support temporary tables, index-organized tables, or object tables. See Oracle9i Streams for complete information about unsupported database objects.strmadmin and that the global name of the source database is orcl.net.CONNECT SYSTEM/MANAGER@orcl.net ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS;
SYS.AnyData queue that will stage changes made to the source database during the upgrade process. For example:
CONNECT strmadmin/strmadminpw@orcl.net EXEC DBMS_STREAMS_ADM.SET_UP_QUEUE();
CONNECT strmadmin/strmadminpw@orcl.net BEGIN DBMS_STREAMS_ADM.ADD_GLOBAL_RULES( streams_type => 'capture', streams_name => 'capture', queue_name => 'streams_queue', include_dml => true, include_ddl => true, include_tagged_lcr => true, source_database => NULL); END; /
Do not start the capture process.
DUPLICATE command by completing the following steps. These steps provide a general outline for using RMAN to duplicate a database. See the Oracle9i Recovery Manager User's Guide for detailed information about using RMAN.
orcl.net if one does not exist.DUPLICATE command. For example:
CONNECT SYSTEM/MANAGER@orcl.net SET SERVEROUTPUT ON SIZE 1000000 DECLARE until_scn NUMBER; BEGIN until_scn:= DBMS_FLASHBACK.GET_SYSTEM_CHANGE_NUMBER; DBMS_OUTPUT.PUT_LINE('Until SCN: ' || until_scn); END; /
Make a note of the until SCN value. This example assumes that the until SCN value is 439882. You will set the UNTIL SCN option to this value when you use RMAN to duplicate the database in Step e.
CONNECT SYSTEM/MANAGER@orcl.net ALTER SYSTEM ARCHIVE LOG CURRENT;
DUPLICATE command to instantiate the source database at the destination database. You can use the UNTIL SCN clause to specify an SCN for the duplication. Use the until SCN determined in Step b for this clause. Archived redo logs must be available for the until SCN specified and for higher SCN values. Therefore, Step c archived the redo log containing the until SCN.
Make sure you use TO database_name in the DUPLICATE command to specify the name of the duplicate database. In this example, the duplicate database is stms.net. Therefore, the DUPLICATE command for this example includes TO stms.net.
The following is an example of an RMAN DUPLICATE command:
rman RMAN> CONNECT TARGET SYS/change_on_install@orcl.net RMAN> CONNECT AUXILIARY SYS/change_on_install@stms.net RMAN> RUN { SET UNTIL SCN 439882; ALLOCATE AUXILIARY CHANNEL updb DEVICE TYPE sbt; DUPLICATE TARGET DATABASE TO updb NOFILENAMECHECK; }
ALTER SYSTEM statement to disable the RESTRICTED SESSION:
CONNECT SYSTEM/MANAGER ALTER SYSTEM DISABLE RESTRICTED SESSION;
DBA_JOBS data dictionary view to list the jobs.DUPLICATE command, the destination database has the same global name as the source database. For example:
CONNECT SYSTEM/MANAGER ALTER DATABASE RENAME GLOBAL_NAME TO stms.net;
SYSDBA privilege and run the following procedure:
|
Attention: Make sure you are connected to the destination database, not the source database, when you run this procedure because it removes the local Streams configuration. |
CONNECT SYS/CHANGE_ON_INSTALL@stms.net AS SYSDBA EXEC DBMS_STREAMS_ADM.REMOVE_STREAMS_CONFIGURATION();
See PL/SQL Packages and Types Reference for more information about the REMOVE_STREAMS_CONFIGURATION procedure.
CONNECT strmadmin/strmadminpw@stms.net CREATE DATABASE LINK orcl.net CONNECT TO strmadmin IDENTIFIED BY strmadminpw USING 'orcl.net';
DUPLICATE command duplicates the database up to one less than the SCN value specified in the UNTIL SCN clause. Therefore, you should subtract one from the until SCN value that you specified when you ran the DUPLICATE command in Step 7e. In this example, the until SCN was set to 439882. Therefore, the instantiation SCN should be set to 439882 - 1, or 439881.
CONNECT strmadmin/strmadminpw@stms.net BEGIN DBMS_APPLY_ADM.SET_GLOBAL_INSTANTIATION_SCN( source_database_name => 'orcl.net', instantiation_scn => 439881, recursive => true); END; /
SYS.AnyData queue. For example:
CONNECT strmadmin/strmadminpw@stms.net BEGIN DBMS_STREAMS_ADM.REMOVE_QUEUE( queue_name => 'strmadmin.streams_queue', cascade => false, drop_unused_queue_table => true); END; /
SYS.AnyData queue. This queue will stage changes propagated from the source database. For example:
CONNECT strmadmin/strmadminpw@stms.net EXEC DBMS_STREAMS_ADM.SET_UP_QUEUE();
CONNECT strmadmin/strmadminpw@orcl.net CREATE DATABASE LINK stms.net CONNECT TO strmadmin IDENTIFIED BY strmadminpw USING 'stms.net';
CONNECT strmadmin/strmadminpw@orcl.net BEGIN DBMS_STREAMS_ADM.ADD_GLOBAL_PROPAGATION_RULES( streams_name => 'orcl_to_stms', source_queue_name => 'strmadmin.streams_queue', destination_queue_name => 'strmadmin.streams_queue@stms.net', include_dml => true, include_ddl => true, include_tagged_lcr => true, source_database => 'orcl.net'); END; /
CONNECT strmadmin/strmadminpw@stms.net BEGIN DBMS_STREAMS_ADM.ADD_GLOBAL_RULES( streams_type => 'apply', streams_name => 'apply', queue_name => 'strmadmin.streams_queue', include_dml => true, include_ddl => true, include_tagged_lcr => true, source_database => 'orcl.net'); END; /
This section describes performing one of the following database maintenance operations on an Oracle Database 10g database:
You can use Streams to achieve little or no downtime during one of these operations. During the operation, the source database is the existing database on which you are performing database maintenance. The destination database is the database that will replace the source database at the end of the operation.
If you are upgrading user-created applications, then, typically, schema objects in the database change to support the upgraded applications. In Streams, row LCRs contain information about row changes that result from DML statements. A DML handler is a user procedure that processes row LCRs resulting from DML statements at a source database. A Streams apply process can pass row LCRs to a DML handler, and the DML handler can modify the row LCR to account for differences between a source database and a destination database.
The process for upgrading your user-created applications using Streams involves modifying and creating the schema objects at the destination database after instantiation. You can use one or more DML handlers at the destination database to process changes from the source database so that they apply to the modified schema objects correctly.
Before you begin the database maintenance operation, you should complete the following tasks to prepare your DML handlers:
Before you begin the database maintenance operation, decide whether you want to use Export/Import utilities (Data Pump or original) or the Recovery Manager (RMAN) utility to instantiate the destination database during the operation. Consider the following factors when you make this decision:
DUPLICATE command used for instantiation does not support migrating a database to a different operating system.DUPLICATE command used for instantiation does not support migrating a database to a different character set.After you decide which utility you want to use for instantiation, complete the steps in the appropriate section:
You may use Data Pump Export/Import or original Export/Import to instantiate the database during the database maintenance operation. Oracle Corporation recommends using Data Pump, and Data Pump may perform the instantiation faster than original Export/Import.
Complete the following steps to perform a maintenance operation using Export/Import and Oracle Streams:
See the Oracle installation guide for your operating system if you need to install Oracle, and see Oracle Database Administrator's Guide for information about creating a database.
Make sure the destination database has a different global name than the source database. This example assumes that the global name of the source database is orcl.net and the global name of the destination database during the database maintenance operation is stms.net. The global name of the destination database is changed when the destination database replaces the source database at the end of the maintenance operation.
strmadmin. This Streams administrator will be copied automatically to the destination database during instantiation.CONNECT SYSTEM/MANAGER@orcl.net ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE, FOREIGN KEY) COLUMNS;
SYS.AnyData queue that will stage changes made to the source database during the maintenance operation. For example:
CONNECT strmadmin/strmadminpw@orcl.net EXEC DBMS_STREAMS_ADM.SET_UP_QUEUE();
CONNECT strmadmin/strmadminpw@orcl.net BEGIN DBMS_STREAMS_ADM.ADD_GLOBAL_RULES( streams_type => 'capture', streams_name => 'capture', queue_name => 'streams_queue', include_dml => true, include_ddl => true, include_tagged_lcr => true, source_database => NULL); END; /
Do not start the capture process.
DBA_JOBS data dictionary view to list the jobs.SYS.AnyData queue. For example:
CONNECT strmadmin/strmadminpw@stms.net BEGIN DBMS_STREAMS_ADM.REMOVE_QUEUE( queue_name => 'strmadmin.streams_queue', cascade => false, drop_unused_queue_table => true); END; /
SYS.AnyData queue. This queue will stage changes propagated from the source database. For example:
CONNECT strmadmin/strmadminpw@stms.net EXEC DBMS_STREAMS_ADM.SET_UP_QUEUE();
CONNECT strmadmin/strmadminpw@orcl.net CREATE DATABASE LINK stms.net CONNECT TO strmadmin IDENTIFIED BY strmadminpw USING 'stms.net';
CONNECT strmadmin/strmadminpw@orcl.net BEGIN DBMS_STREAMS_ADM.ADD_GLOBAL_PROPAGATION_RULES( streams_name => 'orcl_to_stms', source_queue_name => 'strmadmin.streams_queue', destination_queue_name => 'strmadmin.streams_queue@stms.net', include_dml => true, include_ddl => true, include_tagged_lcr => true, source_database => 'orcl.net'); END; /
CONNECT strmadmin/strmadminpw@stms.net BEGIN DBMS_STREAMS_ADM.ADD_GLOBAL_RULES( streams_type => 'apply', streams_name => 'apply', queue_name => 'strmadmin.streams_queue', include_dml => true, include_ddl => true, include_tagged_lcr => true, source_database => 'orcl.net'); END; /
See Oracle Streams Replication Administrator's Guide for information about configuring DML handlers.
You may use RMAN to instantiate the database during either of the following database maintenance operations:
However, if you are migrating the database to a different operating system or character set, then you must use Export/Import for instantiation.
| See Also:
"Performing the Maintenance Operation Using Export/Import and Streams" if you are migrating the database to a different operating system or character set |
Complete the following steps to perform a database migration or apply a patch using RMAN and Oracle Streams:
See the Oracle installation guide for your operating system if you need to install Oracle, and see Oracle Database Administrator's Guide for information about creating a database.
Make sure the destination database has a different global name than the source database. This example assumes that the global name of the source database is orcl.net and the global name of the destination database during the database maintenance operation is stms.net. The global name of the destination database is changed when the destination database replaces the source database at the end of the maintenance operation.
strmadmin. This Streams administrator will be copied automatically to the destination database during instantiation.CONNECT SYSTEM/MANAGER@orcl.net ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE, FOREIGN KEY) COLUMNS;
SYS.AnyData queue that will stage changes made to the source database during the database maintenance operation. For example:
CONNECT strmadmin/strmadminpw@orcl.net EXEC DBMS_STREAMS_ADM.SET_UP_QUEUE();
CONNECT strmadmin/strmadminpw@orcl.net BEGIN DBMS_STREAMS_ADM.ADD_GLOBAL_RULES( streams_type => 'capture', streams_name => 'capture', queue_name => 'streams_queue', include_dml => true, include_ddl => true, include_tagged_lcr => true, source_database => NULL); END; /
Do not start the capture process.
DUPLICATE command by completing the following steps. These steps provide a general outline for using RMAN to duplicate a database. See the Oracle Database Backup and Recovery Advanced User's Guide for detailed information about using RMAN.
orcl.net if one does not exist.DUPLICATE command. For example:
CONNECT SYSTEM/MANAGER@orcl.net SET SERVEROUTPUT ON SIZE 1000000 DECLARE until_scn NUMBER; BEGIN until_scn:= DBMS_FLASHBACK.GET_SYSTEM_CHANGE_NUMBER; DBMS_OUTPUT.PUT_LINE('Until SCN: ' || until_scn); END; /
Make a note of the until SCN value. This example assumes that the until SCN value is 748045. You will set the UNTIL SCN option to this value when you use RMAN to duplicate the database in Step e.
CONNECT SYSTEM/MANAGER@orcl.net ALTER SYSTEM ARCHIVE LOG CURRENT;
DUPLICATE command with the OPEN RESTRICTED option to instantiate the source database at the destination database. The OPEN RESTRICTED option is required. This option enables a restricted session in the duplicate database by issuing the following SQL statement: ALTER SYSTEM ENABLE RESTRICTED SESSION. RMAN issues this statement immediately before the duplicate database is opened.
You can use the UNTIL SCN clause to specify an SCN for the duplication. Use the until SCN determined in Step b for this clause. Archived redo logs must be available for the until SCN specified and for higher SCN values. Therefore, Step c archived the redo log containing the until SCN.
Make sure you use TO database_name in the DUPLICATE command to specify the name of the duplicate database. In this example, the duplicate database is stms.net. Therefore, the DUPLICATE command for this example includes TO stms.net.
The following is an example of an RMAN DUPLICATE command:
rman RMAN> CONNECT TARGET SYS/change_on_install@orcl.net RMAN> CONNECT AUXILIARY SYS/change_on_install@stms.net RMAN> RUN { SET UNTIL SCN 748045; ALLOCATE AUXILIARY CHANNEL mgdb DEVICE TYPE sbt; DUPLICATE TARGET DATABASE TO mgdb NOFILENAMECHECK OPEN RESTRICTED; }
ALTER SYSTEM statement to disable the RESTRICTED SESSION:
CONNECT SYSTEM/MANAGER ALTER SYSTEM DISABLE RESTRICTED SESSION;
SYSDBA privilege and run the following procedure:
|
Attention: Make sure you are connected to the destination database, not the source database, when you run this procedure because it removes the local Streams configuration. |
CONNECT SYS/CHANGE_ON_INSTALL AS SYSDBA EXEC DBMS_STREAMS_ADM.REMOVE_STREAMS_CONFIGURATION();
See PL/SQL Packages and Types Reference for more information about the REMOVE_STREAMS_CONFIGURATION procedure.
DBA_JOBS data dictionary view to list the jobs.DUPLICATE command, the destination database has the same global name as the source database. For example:
CONNECT SYSTEM/MANAGER ALTER DATABASE RENAME GLOBAL_NAME TO stms.net;
CONNECT strmadmin/strmadminpw@stms.net CREATE DATABASE LINK orcl.net CONNECT TO strmadmin IDENTIFIED BY strmadminpw USING 'orcl.net';
748045, then run the following procedure:DUPLICATE command duplicates the database up to one less than the SCN value specified in the UNTIL SCN clause. Therefore, you should subtract one from the until SCN value that you specified when you ran the DUPLICATE command in Step 7e. In this example, the until SCN was set to 748045. Therefore, the instantiation SCN should be set to 748045 - 1, or 748044.
CONNECT strmadmin/strmadminpw@stms.net BEGIN DBMS_APPLY_ADM.SET_GLOBAL_INSTANTIATION_SCN( source_database_name => 'orcl.net', instantiation_scn => 748044, recursive => true); END; /
SYS.AnyData queue. For example:
CONNECT strmadmin/strmadminpw@stms.net BEGIN DBMS_STREAMS_ADM.REMOVE_QUEUE( queue_name => 'strmadmin.streams_queue', cascade => false, drop_unused_queue_table => true); END; /
SYS.AnyData queue. This queue will stage changes propagated from the source database. For example:
CONNECT strmadmin/strmadminpw@stms.net EXEC DBMS_STREAMS_ADM.SET_UP_QUEUE();
CONNECT strmadmin/strmadminpw@orcl.net CREATE DATABASE LINK stms.net CONNECT TO strmadmin IDENTIFIED BY strmadminpw USING 'stms.net';
CONNECT strmadmin/strmadminpw@orcl.net BEGIN DBMS_STREAMS_ADM.ADD_GLOBAL_PROPAGATION_RULES( streams_name => 'orcl_to_stms', source_queue_name => 'strmadmin.streams_queue', destination_queue_name => 'strmadmin.streams_queue@stms.net', include_dml => true, include_ddl => true, include_tagged_lcr => true, source_database => 'orcl.net'); END; /
CONNECT strmadmin/strmadminpw@stms.net BEGIN DBMS_STREAMS_ADM.ADD_GLOBAL_RULES( streams_type => 'apply', streams_name => 'apply', queue_name => 'strmadmin.streams_queue', include_dml => true, include_ddl => true, include_tagged_lcr => true, source_database => 'orcl.net'); END; /
See Oracle Streams Replication Administrator's Guide for information about configuring DML handlers.
Complete the following steps to finish the database maintenance operation:
CONNECT strmadmin/strmadminpw@stms.net BEGIN DBMS_APPLY_ADM.START_APPLY( apply_name => 'apply'); END; /
CONNECT strmadmin/strmadminpw@orcl.net BEGIN DBMS_CAPTURE_ADM.START_CAPTURE( capture_name => 'capture'); END; /
This step begins the process of replicating changes that were made to the source database during instantiation of the destination database.
capture, and the name of the apply process is apply, then run the following query at the source database:
CONNECT strmadmin/strmadminpw@orcl.net COLUMN ENQUEUE_MESSAGE_NUMBER HEADING 'Captured SCN' FORMAT 99999999999 COLUMN LWM_MESSAGE_NUMBER HEADING 'Applied SCN' FORMAT 99999999999 SELECT c.ENQUEUE_MESSAGE_NUMBER, a.LWM_MESSAGE_NUMBER FROM V$STREAMS_CAPTURE c, V$STREAMS_APPLY_COORDINATOR@stms.net a WHERE CAPTURE_NAME = 'CAPTURE' AND APPLY_NAME = 'APPLY';
When the two SCN values returned by this query are nearly equal, most of the changes from the source database have been applied at the destination database, and you can move on to the next step. At this point in the process, the values returned by this query may never be equal because the source database still allows changes.
If this query returns no results, then make sure the Streams clients in the environment are enabled by querying the STATUS column in the DBA_CAPTURE view at the source database and the DBA_APPLY view at the destination database. You can check the status of the propagation by running the query in "Displaying the Schedule for a Propagation Job".
If a Streams client is disabled, then try restarting it. If a Streams client will not restart, then troubleshoot the environment using the information in Chapter 15, "Troubleshooting a Streams Environment".
CONNECT strmadmin/strmadminpw@stms.net SELECT COUNT(*) FROM DBA_APPLY_ERROR;
If this query returns zero, then move on to the next step. If this query shows errors in the error queue, then resolve these errors before continuing. See "Managing Apply Errors" for instructions.
CONNECT SYSTEM/MANAGER@orcl.net ALTER SYSTEM ENABLE RESTRICTED SESSION;
SYS.AnyData queue, the apply process, supplemental logging specifications, and the Streams administrator. See the following sections for instructions:
If you no longer need database supplemental logging, then connect as an administrative user in SQL*Plus at the destination database, and run the following statement to drop it:
CONNECT SYSTEM/MANAGER@stms.net ALTER DATABASE DROP SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE, FOREIGN KEY) COLUMNS;
Also, the following statement drops a user named strmadmin:
DROP USER strmadmin CASCADE;
CONNECT SYSTEM/MANAGER@stms.net ALTER DATABASE RENAME GLOBAL_NAME TO orcl.net;
|
 Copyright © 2002, 2003 Oracle Corporation All Rights Reserved. |
|