Home » RDBMS Server » Server Administration » upgrade from 10g to 11g, startup upgrade error: LRM-00101: unknown parameter name 'diagnostic_dest'; (aix; 10g to 11g)
upgrade from 10g to 11g, startup upgrade error: LRM-00101: unknown parameter name 'diagnostic_dest'; [message #606917] Thu, 30 January 2014 12:31 Go to next message
cakeday
Messages: 31
Registered: May 2010
Member
i am upgrading a database from oracle version 10.2.0.3 to 11.2.0.3:

When i start the database in 10g -- It starts FINE
Then i run utlu112i.sql -- That comes clean with a few changes i need to make. (replace user_dump and bdump and add diagnostic_dump, which i did_

Then when i try to start the database in startup upgrade mode, it gives me the error:
SQL> LRM-00101: unknown parameter name 'diagnostic_dest'
ORA-01078: failure in processing system parameters
= = = = = =
i iam attaching the screen output and a copy of my 11g init file.
Please help. i have done the same migration in a development instance and all worked fine. for some reason, the test environment is giving me trouble.. same kind of environment, version, size and parameters..

STEP 1: starting the database as is, 10g:
SQL> startup pfile='/s051/admin/pfile/initS051.ora_10g'
ORACLE instance started.

Total System Global Area 4194304000 bytes
Fixed Size 2076560 bytes
Variable Size 1509949552 bytes
Database Buffers 2667577344 bytes
Redo Buffers 14700544 bytes
Database mounted.
Database opened.
======================================================================

STEP 2: Running utlu112i.sql -- which runs as normal:
SQL> @utlu112i.sql
Oracle Database 11.2 Pre-Upgrade Information Tool 01-30-2014 10:13:09
Script Version: 11.2.0.3.0 Build: 001
.
**********************************************************************
Database:
**********************************************************************
--> name: S051
--> version: 10.2.0.2.0
--> compatible: 10.2.0
--> blocksize: 8192
--> platform: AIX-Based Systems (64-bit)
--> timezone file: V2
.
**********************************************************************
Tablespaces: [make adjustments in the current environment]
**********************************************************************
--> SYSTEM tablespace is adequate for the upgrade.
.... minimum required size: 456 MB
--> UNDO001 tablespace is adequate for the upgrade.
.... minimum required size: 400 MB
--> SYSAUX tablespace is adequate for the upgrade.
.... minimum required size: 357 MB
--> TEMP tablespace is adequate for the upgrade.
.... minimum required size: 60 MB
.
**********************************************************************
Flashback: OFF
**********************************************************************
**********************************************************************
Update Parameters: [Update Oracle Database 11.2 init.ora or spfile]
Note: Pre-upgrade tool was run on a lower version 64-bit database.
**********************************************************************
--> If Target Oracle is 32-Bit, refer here for Update Parameters:
-- No update parameter changes are required.
.

--> If Target Oracle is 64-Bit, refer here for Update Parameters:
-- No update parameter changes are required.
.
**********************************************************************
Renamed Parameters: [Update Oracle Database 11.2 init.ora or spfile]
**********************************************************************
-- No renamed parameters found. No changes are required.
.
**********************************************************************
Obsolete/Deprecated Parameters: [Update Oracle Database 11.2 init.ora or spfile]
**********************************************************************
--> background_dump_dest 11.1 DEPRECATED replaced by "diagnostic_dest"
--> user_dump_dest 11.1 DEPRECATED replaced by "diagnostic_dest"
.

**********************************************************************
Components: [The following database components will be upgraded or installed]
**********************************************************************
--> Oracle Catalog Views [upgrade] VALID
--> Oracle Packages and Types [upgrade] VALID
.
**********************************************************************
Miscellaneous Warnings
**********************************************************************
WARNING: --> Database is using a timezone file older than version 14.
.... After the release migration, it is recommended that DBMS_DST package
.... be used to upgrade the 10.2.0.2.0 database timezone version
.... to the latest version which comes with the new release.
WARNING: --> Database contains INVALID objects prior to upgrade.
.... The list of invalid SYS/SYSTEM objects was written to
.... registry$sys_inv_objs.
.... The list of non-SYS/SYSTEM objects was written to
.... registry$nonsys_inv_objs.
.... Use utluiobj.sql after the upgrade to identify any new invalid
.... objects due to the upgrade.
.... USER PWRBATCH has 1 INVALID objects.
WARNING: --> Your recycle bin is turned on and currently contains no objects.
.... Because it is REQUIRED that the recycle bin be empty prior to upgrading
.... and your recycle bin is turned on, you may need to execute the command:
PURGE DBA_RECYCLEBIN
.... prior to executing your upgrade to confirm the recycle bin is empty.
WARNING: --> Database contains schemas with objects dependent on DBMS_LDAP package.
.... Refer to the 11g Upgrade Guide for instructions to configure Network ACLs.
.... USER PWRPLANT has dependent objects.
.
**********************************************************************
Recommendations
**********************************************************************
Oracle recommends gathering dictionary statistics prior to
upgrading the database.
To gather dictionary statistics execute the following command
while connected as SYSDBA:

EXECUTE dbms_stats.gather_dictionary_stats;

**********************************************************************
Oracle recommends reviewing any defined events prior to upgrading.

To view existing non-default events execute the following commands
while connected AS SYSDBA:
Events:
SELECT (translate(value,chr(13)||chr(10),' ')) FROM sys.v$parameter2
WHERE UPPER(name) ='EVENT' AND isdefault='FALSE'

Trace Events:
SELECT (translate(value,chr(13)||chr(10),' ')) from sys.v$parameter2
WHERE UPPER(name) = '_TRACE_EVENTS' AND isdefault='FALSE'

Changes will need to be made in the init.ora or spfile.

**********************************************************************
======================================================================
STEP 3: shutdown the database 10g:
SQL> shutdown immediate;
======================================================================

STEP 4: startup ugprade:
SQL> startup upgrade pfile='/s051/admin/pfile/initS051.ora_11g'
LRM-00101: unknown parameter name 'diagnostic_dest'
ORA-01078: failure in processing system parameters
======================================================================

My 11g initfile
S051.__db_cache_size=2667577344
S051.__java_pool_size=33554432
S051.__large_pool_size=50331648
S051.__shared_pool_size=1409286144
S051.__streams_pool_size=16777216
*.audit_trail=NONE #'db_extended'# if you want auditing
#*.background_dump_dest='/s051/admin/bdump'
*.compatible='10.2.0'
*.control_file_record_keep_time=16
*.control_files='/s051/sys001/control_001.ctl','/s051/sys002/control_002.ctl','/s051/sys003/co
ntrol_003.ctl'
*.core_dump_dest='/s051/admin/cdump'
*.db_block_size=8192
*.db_cache_size=400m
*.db_domain='sce.com'
*.db_file_multiblock_read_count=32# LARGE
*.db_files=200
*.db_name='S051'
*.dml_locks=500# LARGE
*.global_names=false
*.java_pool_size=20000000
*.job_queue_processes=10
*.large_pool_size=36m
*.log_archive_dest='/s051/arch001'
*.log_archive_format='S051_%t_%s_%r.arc'
*.log_buffer=263840# LARGE
*.log_checkpoint_interval=26000
*.log_checkpoints_to_alert=true
*.max_dump_file_size='10240'# limit trace file size to 5 Meg each
*.open_cursors=1000# for ABB software
*.optimizer_features_enable='10.1.0.5'
*.os_authent_prefix=''
*.parallel_max_servers=320
*.pga_aggregate_target=500M
*.processes=400# LARGE
*.query_rewrite_enabled='TRUE'
*.query_rewrite_integrity='TRUSTED'
*.session_cached_cursors=60
*.session_max_open_files=25
*.sga_max_size=3000M
*.sga_target=4000M
*.shared_pool_size=80000000# LARGE
*.streams_pool_size=1000000
*.timed_statistics=true
##*.undo_management='MANUAL'
*.undo_management='AUTO'
###*.undo_tablespace='UNDOTBS2'
*.undo_tablespace='UNDO001'
*.diagnostic_dest='/s051/oracle'
#*.user_dump_dest='/s051/admin/udump'
*.workarea_size_policy='AUTO'
Re: upgrade from 10g to 11g, startup upgrade error: LRM-00101: unknown parameter name 'diagnostic_dest'; [message #607228 is a reply to message #606917] Tue, 04 February 2014 02:03 Go to previous message
mrkamranumer
Messages: 11
Registered: January 2014
Junior Member
Dear just make export of those schemas which are required using Datapump and include version clause like version =10.0.2

Install 11g and create required schemas and Import this dump in your new 11g database using version =10.0.2

Thank You
Previous Topic: Multi Databases
Next Topic: different block size
Goto Forum:
  


Current Time: Thu Aug 21 09:53:55 CDT 2014

Total time taken to generate the page: 0.07622 seconds