ITPub博客

首页 > Linux操作系统 > Linux操作系统 > 前两天升级时遇到了小问题(ORA-32004)

前两天升级时遇到了小问题(ORA-32004)

原创 Linux操作系统 作者:yxyup 时间:2007-01-11 00:00:00 0 删除 编辑

SQL> STARTUP;
ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE instance started.

Total System Global Area 413909504 bytes
Fixed Size 878156 bytes
Variable Size 128983124 bytes
Database Buffers 83886080 bytes
Redo Buffers 262144 bytes
Database mounted.
Database opened.
SQL>
SQL> host oerr ora 32004
32004, 00000, "obsolete and/or deprecated parameter(s) specified"
// *Cause: One or more obsolete and/or parameters were specified in
// the SPFILE or the PFILE on the server side.
// *Action: See alert log for a list of parameters that are obsolete.
// or deprecated. Remove them from the SPFILE or the server
// side PFILE.
SQL>


在Alert log 中发现如下信息

Deprecated system parameters with specified values:
dblink_encrypt_login
End of deprecated system parameter listing

这时怀疑这个参数在9205已经废弃了,在metalink上查了一把,果然是. 在initfile去掉就OK了


Subject: Complete Upgrade Checklist for Manual Upgrades from 8.X / 9.0.1 to Oracle9iR2 (9.2.0)
Doc ID: Note:159657.1 Type: BULLETIN
Last Revision Date: 23-NOV-2006 Status: PUBLISHED


PURPOSE
-------

This document is created for use as a guideline and checklist when
manually upgrading Oracle 8, Oracle 8i or Oracle 9i to Oracle 9i.

This document does not approach the upgrade of specific components.
To upgrade specific database components please use the steps described in
the migration guide chapter 3 page 3-25 of the Oracle 9.2 Migration guide
for Oracle 9.2 and chapter 7 page 7-24 of the oracle 9.0.1 Migration guide.
There it is explained how to upgrade following components:
XDK for Java, Session Namespace, CORBA, OSE, JSP, Oracle Spatial,
InterMedia, Oracle Text, Oracle Label Security, Oracle9i RAC,
Materialized views, Advanced Queueing Option and the recovery catalog.

NOTE: The 9.2 Rel1 Migration Guide does not contain information about how
to upgrade Intermedia (Image/Video/Audio). This has been corrected
in 9.2 Rel2 Migration Guide. Please refer to this Guide when upgrading
to 9.2 Rel1.

SCOPE & APPLICATION
-------------------

Database administrators


UPGRADE CHECKLIST
-----------------


UPGRADING THE DATABASE
----------------------
1. -----------------------------------------------------------------------------

Upgrade path for Oracle 8.0:
If your old release version is 8.0.5 or less (i.e 8.0.4 or 8.0.3), then direct
upgrade is NOT supported. You must first upgrade this version to 8.0.6. After
the upgrade to 8.0.6 or your version IS 8.0.6 , you can directly
upgrade your database to 9i.

Upgrade path for Oracle 8i:
If your old release version is 8.1.5 or 8.1.6, then direct upgrade to Oracle 9.2
is NOT supported. You must first upgrade this version to 8.1.7. After the
upgrade to 8.1.7 or your version IS 8.1.7, you can directly upgrade your
database to Oracle 9.2. However, if your target release is 9.0.1,
direct upgrade from 8.1.5 and 8.1.6 is supported.

If your old release is 8.0.5 or less, look at Note 133920.1 for manual upgrading
the database to 8.0.6 or higher.

Table 2-1 in Chapter 2: Preparing to Upgrade, Section 'Determine Your Upgrade
Path to the New Release" of the Oracle 9i Database Migration Guide Release 2
(9.2) also summarises information about supported direct upgrade paths.

What version is running? What option is installed?
Select * from v$version;
Select * from v$option;


2. -----------------------------------------------------------------------------

PERFORM a Full cold backup!!!!!!!

3. -----------------------------------------------------------------------------

Avoid running out of space during the migration:

- Prepare the system rollback segment:
Alter rollback segment system storage (maxextents 121 next 1M);

- Ensure plenty of free space in the SYSTEM tablespace. A minimum of 150 Mb
additional free space:
Select max(bytes) from dba_free_space where tablespace_name='SYSTEM';

- Ensure plenty of free space in the ROLLBACK tablespace. Ensure that you have
at least 1 rollback segment of 70 Mb if the number of objects in the database
exceeds 5000:
Select count(*) from dba_objects;

If you run out of space in one of these tablespaces during the upgrade, you will
need to perform the upgrade again.

4. -----------------------------------------------------------------------------

Verify the certification of oracle 9i on the OS version you are using.
Verify all necessary OS patches are installed.
Example for Solaris:
$ showrev -p

You can also check the installation in Note 169706.1

5. ------------------------------------------------------------------------------

Upgrade will leave all objects (packages,views,...) invalid, except for tables.
All other objects must be recompiled manually.

List all objects that are not VALID before the upgrade.
This list of fatal objects.

Select substr(owner,1,12) owner, substr(object_name,1,30) object,
Substr(object_type,1,30) type,status from dba_objects where status <>'VALID';

To create a script to compile all invalid objects, before upgrading, run the
the script called utlrp.sql in the $ORACLE_HOME/rdbms/admin directory. This
script recompiles all invalid PL/SQL in the database including views.

$ cd $ORACLE_HOME/rdbms/admin
$ sqlplus sys/ as sysdba
SQL> @utlrp.sql

Run the script and than rerun the query to get invalid objects.

spool invalid_pre.lst
Select substr(owner,1,12) owner,
Substr(object_name,1,30) object,
Substr(object_type,1,30) type, status from
dba_objects where status <>'VALID';
spool off

This last query will return a list of all objects that cannot be recompiled
before the upgrade in the file 'invalid_pre.lst'

There should be not dictionary objects invalid.

6. -----------------------------------------------------------------------------

Verify the kernel parameters according to the installation guide of the
new version.
Example for Solaris:
$ cat /etc/system

7. ------------------------------------------------------------------------------

Ensure ORACLE_SID is set to instance you want to upgrade.
Echo $ORACLE_SID
Echo $ORACLE_HOME

8. -----------------------------------------------------------------------------

For all information regarding the national characterset,
please refer to Note 276914.1

Before proceeding please check the column names involved with Note 278725.1

As of Oracle 9i the National Characterset (NLS_NCHAR_CHARACTERSET)
will be limited to UTF8 and AL16UTF16.
Note 276914.1 The National Character Set in Oracle 9i and 10g

Any other NLS_NCHAR_CHARACTERSET will no longer be supported.
When upgrading to 9i the value of NLS_NCHAR_CHARACTERSET is based
on value currently used in the Oracle8 version.
If the NLS_NCHAR_CHARACTERSET is UTF8 then new it will stay UTF8.
In all other cases the NLS_NCHAR_CHARACTERSET is changed to AL16UTF16
and -if used- N-type data (= data in columns using NCHAR, NVARCHAR2 orNCLOB )
may need to be converted.
The change itself is done in step 31 by running the upgrade script.

If you are NOT using N-type colums *for user data* then simply go to step 9.
No further action required.

( so if: select distinct OWNER, TABLE_NAME from DBA_TAB_COLUMNS where
DATA_TYPE in ('NCHAR','NVARCHAR2', 'NCLOB') and OWNER not in
('SYS','SYSTEM'); returns no rows, go to point 9.)

If you have N-type colums *for user data* then check:

SQL> select * from nls_database_parameters where parameter
='NLS_NCHAR_CHARACTERSET';

If you are using N-type colums AND your National Characterset
is UTF8 or is in the following list:

JA16SJISFIXED , JA16EUCFIXED , JA16DBCSFIXED , ZHT32TRISFIXED
KO16KSC5601FIXED , KO16DBCSFIXED , US16TSTFIXED , ZHS16CGB231280FIXED
ZHS16GBKFIXED , ZHS16DBCSFIXED , ZHT16DBCSFIXED , ZHT16BIG5FIXED
ZHT32EUCFIXED

then also simply go to point 9.
The conversion of the user data itself will then be done in step 36.

If you are using N-type colums AND your National Characterset is NOT
UTF8 or NOT in the following list:

JA16SJISFIXED , JA16EUCFIXED , JA16DBCSFIXED , ZHT32TRISFIXED
KO16KSC5601FIXED , KO16DBCSFIXED , US16TSTFIXED , ZHS16CGB231280FIXED
ZHS16GBKFIXED , ZHS16DBCSFIXED , ZHT16DBCSFIXED , ZHT16BIG5FIXED
ZHT32EUCFIXED

(your current NLS_NCHAR_CHARACTERSET is for example US7ASCII, WE8ISO8859P1, CL8MSWIN1251 ...)
then you have to:
* change the tables to use CHAR, VARCHAR2 or CLOB instead the N-type
or
* use export/import the table(s) containing N-type columns
and truncate those tables before migrating to 9i.
The recommended NLS_LANG during export is simply the NLS_CHARACTERSET,
not the NLS_NCHAR_CHARACTERSET

9. -----------------------------------------------------------------------------

If you are upgrading from the 8.0.6 release check no users or roles are called
either MIGRATE or OUTLN.

Select * from dba_users where username in ('MIGRATE','OUTLN');
Select * from dba_roles where role in ('MIGRATE','OUTLN');

10. ----------------------------------------------------------------------------

Check for corruption in the dictionary, use the following commands in sqlplus
connected as sys:

Set verify off
Set space 0
Set heading off
Set feedback off
Set pages 1000
Spool analyze.sql
Select 'Analyze '||object_type||' '||object_name
||' validate structure;'
from dba_objects
where owner='SYS'
and object_type in ('INDEX','TABLE','CLUSTER');
spool off
This creates a script called analyze.sql.
Run the script.

This script (analyze.sql) should not return any errors.

11. ----------------------------------------------------------------------------

Ensure that all Snapshot refreshes are successfully completed.
And replication is stopped.
$ Sqlplus SYS/
Select distinct(trunc(last_refresh)) from dba_snapshot_refresh_times;

12. ----------------------------------------------------------------------------

Stop the listener for the database
$ lsnrctl
Lsnrctl> stop

13. ----------------------------------------------------------------------------

Ensure no files need media recovery:
$ sqlplus SYS/
Select * from v$recover_file;

This should return no rows

14. ----------------------------------------------------------------------------

Ensure no files are in backup mode:
Select * from v$backup where status!='NOT ACTIVE';

This should return no rows.

15. ----------------------------------------------------------------------------

Resolve any outstanding unresolved distributed transaction:

Select * from dba_2pc_pending;

If this returns rows you should do the following:

Select local_tran_id from dba_2pc_pending;
Execute dbms_transaction.purge_lost_db_entry('');
Commit;

16. ----------------------------------------------------------------------------

Disable all batch and cron jobs.

17. ----------------------------------------------------------------------------

Ensure the users sys and system have 'system' as their default tablespace.

Select username, default_tablespace from dba_users where username
in ('SYS','SYSTEM');

To modify use:
Alter user sys default tablespace SYSTEM;
Alter user system default tablespace SYSTEM;

18. ----------------------------------------------------------------------------

Optionally ensure the aud$ is in the system tablespace when auditing is enabled.
Select tablespace_name from dba_tables where table_name='AUD$';

19. ----------------------------------------------------------------------------

Note down where all control files are located.
Select * from v$controlfile;

20. ----------------------------------------------------------------------------

Note down all sysdba users.
Select * from v$pwfile_users;

If a passwordfile is used copy it to the new location. On unix the default
is $ORACLE_HOME/dbs/orapw.

On windows NT this is %ORACLE_HOME%databaseorapw

21. ----------------------------------------------------------------------------

Shutdown the database
$ sqlplus SYS/
SQL> Shutdown immediate

22. ----------------------------------------------------------------------------

Change the init.ora file:
- Make a backup of the init.ora file.
- Verify that the parameter DB_DOMAIN is set properly.
- Ensure there is a value for DB_BLOCK_SIZE
- Comment out the JOB_QUEUE_PROCESSES parameter, put in a new and set this
explicitly to zero, during the upgrade
- Comment out the AQ_TM_PROCESSES parameter, put in a new and set this
explicitly to zero, during the upgrade
- If archiving is enabled set LOG_ARCHIVE_START=TRUE
- Ensure that the USER_DUMP_DEST, BACKGROUND_DUMP_DEST and the CORE_DUMP_DEST
are set to an explicit directory
- Set the parameter _SYSTEM_TRIG_ENABLED explicitly to FALSE during the upgrade
- Set the parameter OPTIMIZER_MODE to CHOOSE during the upgrade
- Comment out obsoleted parameters(list in appendix A).
- Comment out SNAPSHOT_REFRESH_? parameters
- Either leave COMPATIBLE unset in your initialization parameter file or
set COMPATIBLE to 8.1.x. Setting this parameter a lower or a higher value
than 8.1.X results in an error during the upgrade.
- If you are using a passwordfile set the parameter
REMOTE_LOGIN_PASSWORDFILE=NONE (If you are using windows also set the
parameter SQLNET.AUTHENTICATION_SERVICES=(NTS) in the sqlnet.ora file.
- If you have set the parameter NLS_LENGTH_SEMANTICS to CHAR, change the value
to BYTE during the upgrade.
- If you are using a cluster database, set the parameter CLUSTER_DATABASE=FALSE
during the upgrade.
- If the parameter RESOURCE_MANAGER_PLAN is set, comment it out as a workaround
for Bug 2610769
- check MAX_ENABLED_ROLES parameter value. Increase it if the number of roles
in the Database is close to its value. When upgrading to higher versions,
new roles might be added . If the Database already contains high number of
roles, upgrade scripts can fail with error ORA-01925 as indicated in
Note 261632.1
- Ensure that the shared_pool_size and the large_pool_size are at least 150Mb

23. ----------------------------------------------------------------------------

Check for adequate freespace on archive log destination file systems.

24. ----------------------------------------------------------------------------

Ensure the NLS_LANG variable is set correctly:
$ echo $NLS_LANG

25. ----------------------------------------------------------------------------
If needed copy the listener.ora and the tnsnames.ora to the new location
(when no TNS_ADMIN env. Parameter is used)
cp $ORACLE_HOME/network/admin /network/admin

26. ----------------------------------------------------------------------------

If your Operating system is Windows NT, delete your services
With the ORADIM of your old oracle version.

For Oracle 8.0 this is:
C:ORADIM80 -DELETE -SID

For Oracle 8i or higher this is:
C:ORADIM -DELETE -SID

And create the new Oracle 9i service use ORADIM of the 9i ORACLE_HOME:

C:ORADIM -NEW -SID -INTPWD -MAXUSERS n
-STARTMODE MANUAL -PFILE %ORACLE_HOME%DATABASEinit.ora

27. ----------------------------------------------------------------------------

If needed copy the init.ora file to the new oracle_home or
Create a link to the init.ora.
cp $OLD_ORACLE_HOME/dbs/init.ora $NEW_ORACLE_HOME/dbs/init.ora
OR
ln -s /init/ora/file/path/init.ora $ORACLE_HOME/dbs/init.ora
Also check 'ifile' parameters in the init.ora, to be set to the correct file.
if an IFILE is used, verify the above mentioned parameter for the init.ora
and copy this to the correct location. Change the IFILE entry in the init.ora
file when this file changes from location.

28. ----------------------------------------------------------------------------
Update the oratab entry, to set the new ORACLE_HOME and disable automatic
startup:
::N

29. ----------------------------------------------------------------------------

Update the environment variables like ORACLE_HOME and PATH
$ . oraenv

30. ----------------------------------------------------------------------------

Make sure the following enviroment variables point to the new
Release directories:
- ORACLE_HOME
- PATH
- ORA_NLS33
- ORACLE_BASE
- LD_LIBRARY_PATH
- ORACLE_PATH

For HP-UX systems verify the SHLIB_PATH parameter points to the new release
directories.

$ env | grep ORACLE_HOME
$ env | grep PATH
$ env | grep ORA_NLS33
$ env | grep ORACLE_BASE
$ env | grep LD_LIBRARY_PATH
$ env | grep ORACLE_PATH

HP-UX:
$ env | grep SHLIB_PATH

31. ----------------------------------------------------------------------------

Run the upgrade script:
$ cd $ORACLE_HOME/rdbms/admin
Sqlplus /nolog
SQL> Connect sys/passwd_for_sys as sysdba

Use Startup RESTRICT when you are upgrading to Oracle 9.0.1:
SQL> Startup restrict

Use Startup MIGRATE when you are upgrading to Oracle 9.2:
SQL> Startup Migrate

Spool the output so you can take a look at possible errors after the upgrade:
SQL> Spool Upgrade.log

Run the appropriate script for your version.

From To: Only Script to Run
==== === ==================
8.0.6 9.0.1 u0800060.sql
8.0.6 9.2 u0800060.sql
8.1.5 9.0.1 u0801050.sql
8.1.5 9.2 Not Supported
8.1.6 9.0.1 u0801060.sql
8.1.6 9.2 Not Supported
8.1.7 9.0.1 u0801070.sql
8.1.7 9.2 u0801070.sql
9.0.1 9.2 u0900010.sql

Each of these scripts is a direct upgrade path from the version you are
on to 9i. You do not need to run catalog.sql and catproc.sql as these
two scripts are called from within the upgrade script.

The remainder of this step is only valid for upgrades towards Oracle 9.2:

Display the contents of the component registry to determine which components
need to be upgraded:
SQL> Select comp_name, version, status from dba_registry;

Run the script cmpdbmig.sql to upgrade the components which can be upgrade
with the SYSDBA privilege:

SQL> @cmpdbmig.sql

The components upgraded by this script are:
Jserver JAVAVM, oracle XDK for Java, Oracle 9i RAC, Oracle Data Mining,
OLAP analytical Workspace, Oracle 9i Java Packages, Messaging Gateway,
Oracle Workspace Manager, OLAP Catalog, Oracle Label Security.

Display the components which were upgraded:
SQL> Select comp_name, version, status from dba_registry;

End the spool of the upgrade:
SQL> Spool Off

32. ----------------------------------------------------------------------------

Restart the database:
SQL> Shutdown Immediate (DO NOT USE SHUTDOWN ABORT!!!!!!!!!)
SQL> Startup restrict

Executing this clean shutdown flushes all caches, clears buffers and performs
other database housekeeping tasks. Which is needed if you want to upgrade
specific components.

33. ----------------------------------------------------------------------------

Run script to recompile invalid pl/sql modules:
SQL> @utlrp

If there are still objects which are not valid after running the script run
the following:
spool invalid_post.lst
Select substr(owner,1,12) owner,
Substr(object_name,1,30) object,
Substr(object_type,1,30) type, status from
dba_objects where status <>'VALID';
spool off

Now compare the invalid objects in the file 'invalid_post.lst' with the invalid
objects in the file 'invalid_pre.lst' you create in step 5.

There should be no dictionary objects invalid.

34. ----------------------------------------------------------------------------

Edit init.ora file:
- Leave the parameter JOB_QUEUE_PROCESSES=0
- Leave the parameter AQ_TM_PROCESSES=0
- remove the parameter _system_trig_enabled from the init.ora file. This
parameter was explicitly set to false during the upgrade.
- modify the log_archive_dest parameter specify only the path, but make sure it
ends with a '/'. (remove the format)
e.g. log_archive_dest=/path/arch into log_archive_dest=/path/
- Modify the parameter log_archive_format and add the format previously
removed from the log_archive_dest.
E.g log_archive_format=arch%t_SID_%s.log
- If you are using a password file set the REMOTE_LOGIN_PASSWORDFILE parameter
to the value used before migration.

35. ----------------------------------------------------------------------------

Shutdown the database and startup the database.
$ sqlplus /nolog
SQL> Connect sys/passwd_for_sys as sysdba
SQL> Shutdown
SQL> Startup restrict

36. ----------------------------------------------------------------------------

For all information regarding the national characterset,
please refer to Note 276914.1

A) IF you are NOT using N-type colums for *user* data:

select distinct OWNER, TABLE_NAME from DBA_TAB_COLUMNS where
DATA_TYPE in ('NCHAR','NVARCHAR2', 'NCLOB') and OWNER not in
('SYS','SYSTEM');
did not return rows in point 8 of this note.

then simply:
$ sqlplus /nolog
SQL> connect sys/passwd_for_sys as sysdba
SQL> shutdown immediate
and goto step 37.

B) IF your version 8 NLS_NCHAR_CHARACTERSET was UTF8:

you can look up your previous NLS_NCHAR_CHARACTERSET using this select:
select * from nls_database_parameters where parameter ='NLS_SAVED_NCHAR_CS';

then simply:
$ sqlplus /nolog
SQL> connect sys/passwd_for_sys as sysdba
SQL> shutdown immediate
go to step 37.

C) IF you are using N-type colums for *user* data *AND*
your previous NLS_NCHAR_CHARACTERSET was in the following list:

JA16SJISFIXED , JA16EUCFIXED , JA16DBCSFIXED , ZHT32TRISFIXED
KO16KSC5601FIXED , KO16DBCSFIXED , US16TSTFIXED , ZHS16CGB231280FIXED
ZHS16GBKFIXED , ZHS16DBCSFIXED , ZHT16DBCSFIXED , ZHT16BIG5FIXED
ZHT32EUCFIXED

then the N-type colums *data* need to be converted to AL16UTF16:

To upgrade user tables with N-type colums to AL16UTF16 run the
script utlnchar.sql:

$ sqlplus /nolog
SQL> connect sys/passwd_for_sys as sysdba
SQL> @utlnchar.sql
SQL> shutdown immediate

go to step 37.

D)IF you are using N-type colums for *user* data *AND *
your previous NLS_NCHAR_CHARACTERSET was *NOT* in the following list:

JA16SJISFIXED , JA16EUCFIXED , JA16DBCSFIXED , ZHT32TRISFIXED
KO16KSC5601FIXED , KO16DBCSFIXED , US16TSTFIXED , ZHS16CGB231280FIXED
ZHS16GBKFIXED , ZHS16DBCSFIXED , ZHT16DBCSFIXED , ZHT16BIG5FIXED
ZHT32EUCFIXED

then import the data exported in point 8 of this note.
The recommended NLS_LANG during import is simply the NLS_CHARACTERSET,
not the NLS_NCHAR_CHARACTERSET

After the import:
$ sqlplus /nolog
SQL> connect sys/passwd_for_sys as sysdba
SQL> shutdown immediate

go to step 37.

37. ----------------------------------------------------------------------------

Now edit the init.ora:
- put back the old value for the JOB_QUEUE_PROCESSES parameter
- put back the old value for the AQ_TM_PROCESSES parameter
- If you change the value for NLS_LENGTH_SEMANTICS prior to the upgrade put
the value back to CHAR.
- If you changed the CLUSTER_DATABASE parameter prior the upgrade set it back to
TRUE
38. ----------------------------------------------------------------------------

Startup the database:
SQL> Startup

Create a server parameter file with a initialization parameter file
SQL> Create spfile from pfile;

This will create a spfile as a copy of the init.ora file located in the
$ORACLE_HOME/dbs directory.


39. ----------------------------------------------------------------------------

Modify the listener.ora file:
For the upgraded intstance(s) modify the ORACLE_HOME parameter
to point to the new ORACLE_HOME.

40. ----------------------------------------------------------------------------

Start the listener
$ lsnrctl
LSNRCTL> start

41. ----------------------------------------------------------------------------

Enable cron and batch jobs

42. ----------------------------------------------------------------------------

Change oratab entry to use automatic startup
SID:ORACLE_HOME:Y

43. ----------------------------------------------------------------------------

To use the new features in 9i change the compatible parameter to the new release.
When everything is well tested, update the compatible parameter in the init.ora
and restart to the new release number.
COMPATIBLE=9.0.X where x is the release number

----------------------------------------------------------------------------

UPGRADING THE JAVA ENGINE(Only for upgrades to 9.0.1)
-------------------------
1. -----------------------------------------------------------------------------
Check java has previously been installed:
Run the following query:
select count(*) from dba_objects where object_type like 'JAVA%'and
owner = 'SYS';

If this is >0 then java has been installed. If this value =0 java is not
installed and there is no reason to upgrade the java engine.

2. -----------------------------------------------------------------------------

Restart the database:
$ Sqlplus /nolog
SQL> connect sys/passwd_for_sys as sysdba
SQL> Shutdown immediate
SQL> startup restrict

3. -----------------------------------------------------------------------------

Run the appropriate script depending on what release you are coming from:
$ cd $ORACLE_HOME/javavm/install
Sqlplus /nolog
SQL> Connect sys/passwd_for_sys as sysdba
SQL> Spool catoutjava.log

From Only Script to Run
==== ==================
8.1.5 jvmu815.sql
8.1.6 jvmu816.sql
8.1.7 jvmu817.sql

After you have run this script, all user classes are invalid. These become
implicitly valid when you executed them. You can explicitly revalidate them
when executing the following command:

SQL> Alter Java Class resolve;

4. -----------------------------------------------------------------------------

Restart the database:
$ Sqlplus /nolog
SQL> connect sys/passwd_for_sys as sysdba
SQL> Shutdown immediate
SQL> startup restrict

----------------------------------------------------------------------------


Appendix A: Obsolete parameters in 9i:
--------------------------------------

_average_dirties_half_life
_lm_statistics
allow_partial_sn_results
always_anti_join
always_semi_join
arch_io_slaves
b_tree_bitmap_plans
backup_disk_io_slaves
cache_size_threshold
cleanup_rollback_entries
close_cached_open_cursors
compatible_no_recovery
complex_view_merging
cpu_count
db_block_checkpoint_batch
db_block_lru_extended_statisti
db_block_lru_latches
db_block_lru_statistics
db_block_max_dirty_target
db_file_simultaneous_writes
delayed_logging_block_cleanout
discrete_transactions_enabled
distributed_lock_timeout
distributed_recovery_connectio
distributed_transactions
fast_full_scan_enabled
freeze_DB_for_fast_instance_re
gc_defer_time
gc_latches
gc_lck_procs
gc_releasable_locks
gc_rollback_locks
hash_multiblock_io_count
instance_nodeset
job_queue_interval
job_queue_keep_connections
large_pool_min_alloc
lgwr_io_slaves
lm_locks
lm_procs
lm_procs
lm_ress
lock_sga_areas
log_block_checksum
log_files
log_simultaneous_copies
log_small_entry_max_size
ogms_home
ops_admin_group
ops_interconnects
optimizer_percent_parallel
optimizer_search_limit
parallel_default_max_instances
parallel_min_message_pool
parallel_server_idle_time
parallel_transaction_resource_
push_join_predicate
row_cache_cursors
sequence_cache_entries
sequence_cache_hash_buckets
shared_pool_reserved_min_alloc
snapshot_refresh_interval
snapshot_refresh_keep_connecti
snapshot_refresh_processes
sort_direct_writes
sort_multiblock_read_count
sort_read_fac
sort_spacemap_size
sort_write_buffer_size
sort_write_buffers
spin_count
temporary_table_locks
text_enable
use_ism
dblink_encrypt_login
log_archive_buffers
log_archive_buffer_size


Deprecated parameters:
----------------------

DRS_START replaced by DG_BROKER_START
MTS_CIRCUITS replaced by CIRCUITS
MTS_DISPATCHERS replaced by DISPATCHERS
MTS_MAX_DISPATCHERS replaced by MAX_DISPATCHERS
MTS_MAX_SERVERS replaced by MAX_SHARED_SERVERS
MTS_SERVERS replaced by SHARED_SERVERS
MTS_SESSIONS replaced by SHARED_SERVER_SESSIONS
PARALLEL_SERVER replaced by CLUSTER_DATABASE
PARALLEL_SERVER_INSTANCES replaced by CLUSTER_DATABASE_INSTANCES

RELATED NOTES:
--------------
Note 197737.1 Corruption / Internal Errors Possible after Upgrading a
Database to Oracle 9.2.0.1

Keywords:
---------

Upgrade migration migrate move convert 9i 9.2 9.0.1 8.1.7 8.0.6 8.1.5 8.1.6
Upgrade migration migrate move convert 9i 9.2 9.0.1 8.1.7 8.0.6 8.1.5 8.1.6
Upgrade migration migrate move convert 9i 9.2 9.0.1 8.1.7 8.0.6 8.1.5 8.1.6


来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/7364032/viewspace-17451/,如需转载,请注明出处,否则将追究法律责任。

上一篇: ORA-12838:
下一篇: create lv 测试
请登录后发表评论 登录
全部评论
暂无介绍

注册时间:2007-12-06

  • 博文量
    163
  • 访问量
    1316218