Obsolete parameters in pfile

Hi,
We have Oracle 10.2.0.3 database on AIX platform.For long ,our database has been running on pfile.We wanted our database to run on spfile and in that process,when we tried to "create spfile from pfile " we are getting the following errors.
SQL> create spfile from pfile;
create spfile from pfile
ERROR at line 1:
ORA-01078: failure in processing system parameters
ORA-32003: error occured processing parameter 'distributed_transactions'
LRM-00101: unknown parameter name 'distributed_transactions'
and similarly, for some other database,
SQL> create spfile from pfile;
create spfile from pfile
ERROR at line 1:
ORA-01078: failure in processing system parameters
ORA-32003: error occured processing parameter 'job_queue_interval'
LRM-00101: unknown parameter name 'job_queue_interval'
As 'distributed_transactions' and 'job_queue_interval' are obsolete parameters ,can I remove these parameter settings from pfile and go ahead creating the spfile or will it have some impact??
Could you please help us in resolving this issue....

Hi;
Your question is cover at:
obsolete parameters
Re: Removal of Obsolete parameters
Please dont forget to change thread status to answered if it possible when u belive your thread has been answered, it pretend to lose time of other forums user while they are searching open question which is not answered,thanks for understanding*
Regard
Helios

Similar Messages

How to remove obsolete parameters in oracle

hi,
can anyone tell me how to delete a obsolete parameter in oracle,wat are the steps to follow or is there any command
Thanks
renjy

how to remove obsolete parameters.

Deprecated and obsolete parameters in 10gR2

From the oracle documentation, the following initialization parameters have been deprecated or obsoleted in this release. in some cases, oracle specifies what superceded the original parameter but in most cases not. does anyone know how to find out more about what was replaced and by what?
see the following:
Appendix A: Initialization Parameters Obsolete in 10g
ENQUEUE_RESOURCES
DBLINK_ENCRYPT_LOGIN
HASH_JOIN_ENABLED
LOG_PARALLELISM
MAX_ROLLBACK_SEGMENTS
MTS_CIRCUITS
MTS_DISPATCHERS
MTS_LISTENER_ADDRESS
MTS_MAX_DISPATCHERS
MTS_MAX_SERVERS
MTS_MULTIPLE_LISTENERS
MTS_SERVERS
MTS_SERVICE
MTS_SESSIONS
OPTIMIZER_MAX_PERMUTATIONS
ORACLE_TRACE_COLLECTION_NAME
ORACLE_TRACE_COLLECTION_PATH
ORACLE_TRACE_COLLECTION_SIZE
ORACLE_TRACE_ENABLE
ORACLE_TRACE_FACILITY_NAME
ORACLE_TRACE_FACILITY_PATH
PARTITION_VIEW_ENABLED
PLSQL_NATIVE_C_COMPILER
PLSQL_NATIVE_LINKER
PLSQL_NATIVE_MAKE_FILE_NAME
PLSQL_NATIVE_MAKE_UTILITY
ROW_LOCKING
SERIALIZABLE
TRANSACTION_AUDITING
UNDO_SUPPRESS_ERRORS
Appendix B: Initialization Parameters Deprecated in 10g
LOGMNR_MAX_PERSISTENT_SESSIONS
MAX_COMMIT_PROPAGATION_DELAY
REMOTE_ARCHIVE_ENABLE
SERIAL_REUSE
SQL_TRACE
BUFFER_POOL_KEEP (replaced by DB_KEEP_CACHE_SIZE)
BUFFER_POOL_RECYCLE (replaced by DB_RECYCLE_CACHE_SIZE)
GLOBAL_CONTEXT_POOL_SIZE
LOCK_NAME_SPACE
LOG_ARCHIVE_START
MAX_ENABLED_ROLES
PARALLEL_AUTOMATIC_TUNING
PLSQL_COMPILER_FLAGS (replaced by PLSQL_CODE_TYPE and PLSQL_DEBUG)
my boss is pushing for explanations and i have no idea how to find the information (i personally am of the school that says if during the database creation, you get warning messages, it's gone and you just accept it...maybe i have been working with oracle too long?)
Thanks for any assistance.

Hi,
Check for these parameters in Oracle9i documentation. There are some mentioning of new parameters to be used for the deprecated parameters. Ofcourse, not all are available.
HTH
Regards,
Badri.

How to create pfile..

Hi guys,
The first step in creating a database manually is to create a pfile so that later on we can create a spfile from this pfile through command:
create spfile from pfile;
my question is how to create this pfile???
please help.
Imran Baig

If you do not have a spfile created you can take the model found in : <ORACLE_HOME>/dbs/init.ora
[oracle@ozawa dump]$ cd $ORACLE_HOME/dbs
[oracle@ozawa dbs]$
[oracle@ozawa dbs]$ ll
total 76
-rw-r--r-- 1 oracle oracle 12920 Mar 9 2002 initdw.ora
-rw-r--r-- 1 oracle oracle 8385 Mar 9 2002 init.ora
-rw-rw---- 1 oracle oracle 24 Jan 6 18:24 lkLCONVCLA
-rw-rw---- 1 oracle oracle 24 Feb 16 14:15 lkLDEVCARD
-rw-rw---- 1 oracle oracle 24 Dec 28 15:41 lkLDEVCNS0
-rw-rw---- 1 oracle oracle 24 Feb 8 09:24 lkLQACNS1
-rwSr----- 1 oracle oracle 1536 Jan 7 08:55 orapwLCONVCLA
-rwSr----- 1 oracle oracle 1536 Jan 6 16:17 orapwLDEVCARD
-rwSr----- 1 oracle oracle 1536 Jan 7 16:53 orapwLDEVCNS0
-rwSr----- 1 oracle oracle 1536 Feb 11 08:34 orapwLQACNS1
-rw-rw---- 1 oracle oracle 2560 Jan 6 18:24 spfileLCONVCLA.ora
-rw-rw---- 1 oracle oracle 2560 Jan 6 14:05 spfileLDEVCARD.ora
-rw-rw---- 1 oracle oracle 2560 Jan 4 11:12 spfileLDEVCNS0.ora
-rw-rw---- 1 oracle oracle 2560 Feb 6 17:09 spfileLQACNS1.ora
[oracle@ozawa dbs]$
[oracle@ozawa dbs]$
[oracle@ozawa dbs]$ more init.ora
# $Header: init.ora 06-aug-98.10:24:40 atsukerm Exp $
# Copyright (c) 1991, 1997, 1998 by Oracle Corporation
# NAME
# init.ora
# FUNCTION
# NOTES
# MODIFIED
# atsukerm 08/06/98 - fix for 8.1.
# hpiao 06/05/97 - fix for 803
# glavash 05/12/97 - add oracle_trace_enable comment
# hpiao 04/22/97 - remove ifile=, events=, etc.
# alingelb 09/19/94 - remove vms-specific stuff
# dpawson 07/07/93 - add more comments regarded archive start
# maporter 10/29/92 - Add vms_sga_use_gblpagfile=TRUE
# jloaiza 03/07/92 - change ALPHA to BETA
# danderso 02/26/92 - change db_block_cache_protect to dbblock_cache_p
# ghallmar 02/03/92 - db_directory -> db_domain
# maporter 01/12/92 - merge changes from branch 1.8.308.1
# maporter 12/21/91 - bug 76493: Add control_files parameter
# wbridge 12/03/91 - use of %c in archive format is discouraged
# ghallmar 12/02/91 - add global_names=true, db_directory=us.acme.com
# thayes 11/27/91 - Change default for cache_clone
# jloaiza 08/13/91 - merge changes from branch 1.7.100.1
# jloaiza 07/31/91 - add debug stuff
# rlim 04/29/91 - removal of char_is_varchar2
# Bridge 03/12/91 - log_allocation no longer exists
# Wijaya 02/05/91 - remove obsolete parameters
# Example INIT.ORA file
# This file is provided by Oracle Corporation to help you customize
# your RDBMS installation for your site. Important system parameters
# are discussed, and example settings given.
# Some parameter settings are generic to any size installation.
# For parameters that require different values in different size
# installations, three scenarios have been provided: SMALL, MEDIUM
# and LARGE. Any parameter that needs to be tuned according to
# installation size will have three settings, each one commented
# according to installation size.
# Use the following table to approximate the SGA size needed for the
# three scenarious provided in this file:
# -------Installation/Database Size------
# SMALL MEDIUM LARGE
# Block 2K 4500K 6800K 17000K
# Size 4K 5500K 8800K 21000K
# To set up a database that multiple instances will be using, place
# all instance-specific parameters in one file, and then have all
# of these files point to a master file using the IFILE command.
# This way, when you change a public
# parameter, it will automatically change on all instances. This is
# necessary, since all instances must run with the same value for many
# parameters. For example, if you choose to use private rollback segments,
# these must be specified in different files, but since all gc_*
# parameters must be the same on all instances, they should be in one file.
# INSTRUCTIONS: Edit this file and the other INIT files it calls for
# your site, either by using the values provided here or by providing
# your own. Then place an IFILE= line into each instance-specific
# INIT file that points at this file.
# NOTE: Parameter values suggested in this file are based on conservative
# estimates for computer memory availability. You should adjust values upward
# for modern machines.
# You may also consider using Database Configuration Assistant tool (DBCA)
# to create INIT file and to size your initial set of tablespaces based
# on the user input.
# replace DEFAULT with your database name
db_name=DEFAULT
db_files = 80 # SMALL
# db_files = 400 # MEDIUM
# db_files = 1500 # LARGE
db_file_multiblock_read_count = 8 # SMALL
# db_file_multiblock_read_count = 16 # MEDIUM
# db_file_multiblock_read_count = 32 # LARGE
db_block_buffers = 100 # SMALL
# db_block_buffers = 550 # MEDIUM
# db_block_buffers = 3200 # LARGE
shared_pool_size = 3500000 # SMALL
# shared_pool_size = 5000000 # MEDIUM
# shared_pool_size = 9000000 # LARGE
log_checkpoint_interval = 10000
processes = 50 # SMALL
# processes = 100 # MEDIUM
# processes = 200 # LARGE
parallel_max_servers = 5 # SMALL
# parallel_max_servers = 4 x (number of CPUs) # MEDIUM
# parallel_max_servers = 4 x (number of CPUs) # LARGE
log_buffer = 32768 # SMALL
# log_buffer = 32768 # MEDIUM
# log_buffer = 163840 # LARGE
# audit_trail = true # if you want auditing
# timed_statistics = true # if you want timed statistics
max_dump_file_size = 10240 # limit trace file size to 5 Meg each
# Uncommenting the line below will cause automatic archiving if archiving has
# been enabled using ALTER DATABASE ARCHIVELOG.
# log_archive_start = true
# log_archive_dest = disk$rdbms:[oracle.archive]
# log_archive_format = "T%TS%S.ARC"
# If using private rollback segments, place lines of the following
# form in each of your instance-specific init.ora files:
# rollback_segments = (name1, name2)
# If using public rollback segments, define how many
# rollback segments each instance will pick up, using the formula
# # of rollback segments = transactions / transactions_per_rollback_segment
# In this example each instance will grab 40/5 = 8:
# transactions = 40
# transactions_per_rollback_segment = 5
# Global Naming -- enforce that a dblink has same name as the db it connects to
global_names = TRUE
# Edit and uncomment the following line to provide the suffix that will be
# appended to the db_name parameter (separated with a dot) and stored as the
# global database name when a database is created. If your site uses
# Internet Domain names for e-mail, then the part of your e-mail address after
# the '@' is a good candidate for this parameter value.
# db_domain = us.acme.com # global database name is db_name.db_domain
# FOR DEVELOPMENT ONLY, ALWAYS TRY TO USE SYSTEM BACKING STORE
# vms_sga_use_gblpagfil = TRUE
# FOR BETA RELEASE ONLY. Enable debugging modes. Note that these can
# adversely affect performance. On some non-VMS ports the db_block_cache_*
# debugging modes have a severe effect on performance.
#_db_block_cache_protect = true # memory protect buffers
#event = "10210 trace name context forever, level 2" # data block checking
#event = "10211 trace name context forever, level 2" # index block checking
#event = "10235 trace name context forever, level 1" # memory heap checking
#event = "10049 trace name context forever, level 2" # memory protect cursors
# define parallel server (multi-instance) parameters
#ifile = ora_system:initps.ora
# define two control files by default
control_files = (ora_control1, ora_control2)
# Uncomment the following line if you wish to enable the Oracle Trace product
# to trace server activity. This enables scheduling of server collections
# from the Oracle Enterprise Manager Console.
# Also, if the oracle_trace_collection_name parameter is non-null,
# every session will write to the named collection, as well as enabling you
# to schedule future collections from the console.
# oracle_trace_enable = TRUE
# Uncomment the following line, if you want to use some of the new 8.1
# features. Please remember that using them may require some downgrade
# actions if you later decide to move back to 8.0.
#compatible = 8.1.0
[oracle@ozawa dbs]$
Joel Pérez
http://otn.oracle.com/experts

Oracle 10g Deprecated parameters !!

We are planning to upgrade the database.
I ran the u101iu.sql before the upgrade to know the
Deprecated parameters and obsolete parameters.
From Upgrade guide : it tells me the following parameters
have been obsolete :
DBLINK_ENCRYPT_LOGIN
HASH_JOIN_ENABLED
LOG_PARALLELISM
MAX_ROLLBACK_SEGMENTS
MTS_CIRCUITS
MTS_DISPATCHERS
MTS_LISTENER_ADDRESS
MTS_MAX_DISPATCHERS
MTS_MAX_SERVERS
MTS_MULTIPLE_LISTENERS
MTS_SERVERS
MTS_SERVICE
MTS_SESSIONS
Question is : Should I keep them in my initSID.ora file or
REMOVE them completely ?
If I remove them how the oracle will know about the
Dispatcher circuits and other information since I would like
to use shared server with dispatcher ?Right now Shared_server
value is 2 in initSID.ora file for 8.1.7 version.
Please let me know.
From,
Pranav

Just to add little bit -
My concern is for following parameters :
MTS_CIRCUITS
MTS_DISPATCHERS
MTS_LISTENER_ADDRESS
MTS_MAX_DISPATCHERS
MTS_MAX_SERVERS
Should I remove them or keep them for 10g upgrade ?
If I remove MTS_MAX_servers or mts_dispatcher,
How would I be able to user oracle in shared server mode
with more than one dispatcher ?
Please adivse.
Thanks in advance.
From
P

Session Parameters values

Hi group
How Can I retrieve the values of my current session parameters.
Thanks in advance
Rick

instance parameters?
PFILE parameters:
SELECT *
FROM v$parameter ;or
SPFILE parameters:
SELECT *
FROM v$spparameter ;

10.2.0.2 backup restore to 11.2.0

Hi. My task is to restore a backup created with 10.2.0.2 software DIRECTLY to the 11.2 on another host. This is migration to 11.2 using rman.
I followed instructions in this metalink document: [ID 369644.1] , section 1) Can I restore or duplicate my previous version database using a later version of Oracle?
I managed to:
1. create new 11.2 ORACLE_HOME
2. adjust PFILE (depreciated parameter, obsolete parameters, new paths)
3. restore and recover database using 11.2. The next step was to upgrade migrated database. So I issued STARTUP UPGRADE statement and run utlu112i.sql from 11.2 ORACLE_HOME.
SQL> @utlu112i.sql
ERROR:
ORA-04023: Object SYS.STANDARD could not be validated or authorized
It turned out that I must run utlu112i.sql script from 10.2 ORACLE_HOME as is stated in this thread: Upgrade to 11g failure ORA-04023
I don't understand how to accomplish this. Should I
1. install new ORACLE_HOME 10.2.0.2,
2. start sqlplus using adjusted PFILE,
3. run utlu112i.sql
Edited by: Przemek P on 2011-07-27 05:17

I met the same issue, the key point is that we aren't willing to run utlu112i.sql on our production database(10.2.0.2). So I want to copy data files and upgrade the db directly under the 11.2.0.2 home on another host.
I found some notes on metalink:
*+<moderator edit - MOS Doc content deleted>+*

Unable to find the utl_file_directory option in init.ora

Hi all these are the contents of init.ora file in nacedell server.i did'nt find any thing as utl_file_directory to update with my directory created through sql*plus using
command
create directory dir as 'c:\dir';
here are the contents of init.ora file
cat init.ora command is giving contents as
# $Header: init.ora 06-aug-98.10:24:40 atsukerm Exp $
# Copyright (c) 1991, 1997, 1998 by Oracle Corporation
# NAME
# init.ora
# FUNCTION
# NOTES
# MODIFIED
# atsukerm 08/06/98 - fix for 8.1.
# hpiao 06/05/97 - fix for 803
# glavash 05/12/97 - add oracle_trace_enable comment
# hpiao 04/22/97 - remove ifile=, events=, etc.
# alingelb 09/19/94 - remove vms-specific stuff
# dpawson 07/07/93 - add more comments regarded archive start
# maporter 10/29/92 - Add vms_sga_use_gblpagfile=TRUE
# jloaiza 03/07/92 - change ALPHA to BETA
# danderso 02/26/92 - change db_block_cache_protect to dbblock_cache_p
# ghallmar 02/03/92 - db_directory -> db_domain
# maporter 01/12/92 - merge changes from branch 1.8.308.1
# maporter 12/21/91 - bug 76493: Add control_files parameter
# wbridge 12/03/91 - use of %c in archive format is discouraged
# ghallmar 12/02/91 - add global_names=true, db_directory=us.acme.com
# thayes 11/27/91 - Change default for cache_clone
# jloaiza 08/13/91 - merge changes from branch 1.7.100.1
# jloaiza 07/31/91 - add debug stuff
# rlim 04/29/91 - removal of char_is_varchar2
# Bridge 03/12/91 - log_allocation no longer exists
# Wijaya 02/05/91 - remove obsolete parameters
# Example INIT.ORA file
# This file is provided by Oracle Corporation to help you customize
# your RDBMS installation for your site. Important system parameters
# are discussed, and example settings given.
# Some parameter settings are generic to any size installation.
# For parameters that require different values in different size
# installations, three scenarios have been provided: SMALL, MEDIUM
# and LARGE. Any parameter that needs to be tuned according to
# installation size will have three settings, each one commented
# according to installation size.
# Use the following table to approximate the SGA size needed for the
# three scenarious provided in this file:
# -------Installation/Database Size------
# SMALL MEDIUM LARGE
# Block 2K 4500K 6800K 17000K
# Size 4K 5500K 8800K 21000K
# To set up a database that multiple instances will be using, place
# all instance-specific parameters in one file, and then have all
# of these files point to a master file using the IFILE command.
# This way, when you change a public
# parameter, it will automatically change on all instances. This is
# necessary, since all instances must run with the same value for many
# parameters. For example, if you choose to use private rollback segments,
# these must be specified in different files, but since all gc_*
# parameters must be the same on all instances, they should be in one file.
# INSTRUCTIONS: Edit this file and the other INIT files it calls for
# your site, either by using the values provided here or by providing
# your own. Then place an IFILE= line into each instance-specific
# INIT file that points at this file.
# NOTE: Parameter values suggested in this file are based on conservative
# estimates for computer memory availability. You should adjust values upward
# for modern machines.
# You may also consider using Database Configuration Assistant tool (DBCA)
# to create INIT file and to size your initial set of tablespaces based
# on the user input.
# replace DEFAULT with your database name
db_name=DEFAULT
db_files = 80 # SMALL
# db_files = 400 # MEDIUM
# db_files = 1500 # LARGE
db_file_multiblock_read_count = 8 # SMALL
# db_file_multiblock_read_count = 16 # MEDIUM
# db_file_multiblock_read_count = 32 # LARGE
db_block_buffers = 100 # SMALL
# db_block_buffers = 550 # MEDIUM
# db_block_buffers = 3200 # LARGE
shared_pool_size = 3500000 # SMALL
# shared_pool_size = 5000000 # MEDIUM
# shared_pool_size = 9000000 # LARGE
log_checkpoint_interval = 10000
processes = 50 # SMALL
# processes = 100 # MEDIUM
# processes = 200 # LARGE
parallel_max_servers = 5 # SMALL
# parallel_max_servers = 4 x (number of CPUs) # MEDIUM
# parallel_max_servers = 4 x (number of CPUs) # LARGE
log_buffer = 32768 # SMALL
# log_buffer = 32768 # MEDIUM
# log_buffer = 163840 # LARGE
# audit_trail = true # if you want auditing
# timed_statistics = true # if you want timed statistics
max_dump_file_size = 10240 # limit trace file size to 5 Meg each
# Uncommenting the line below will cause automatic archiving if archiving has
# been enabled using ALTER DATABASE ARCHIVELOG.
# log_archive_start = true
# log_archive_dest = disk$rdbms:[oracle.archive]
# log_archive_format = "T%TS%S.ARC"
# If using private rollback segments, place lines of the following
# form in each of your instance-specific init.ora files:
# rollback_segments = (name1, name2)
# If using public rollback segments, define how many
# rollback segments each instance will pick up, using the formula
# # of rollback segments = transactions / transactions_per_rollback_segment
# In this example each instance will grab 40/5 = 8:
# transactions = 40
# transactions_per_rollback_segment = 5
# Global Naming -- enforce that a dblink has same name as the db it connects to
global_names = TRUE
# Edit and uncomment the following line to provide the suffix that will be
# appended to the db_name parameter (separated with a dot) and stored as the
# global database name when a database is created. If your site uses
# Internet Domain names for e-mail, then the part of your e-mail address after
# the '@' is a good candidate for this parameter value.
# db_domain = us.acme.com # global database name is db_name.db_domain
# FOR DEVELOPMENT ONLY, ALWAYS TRY TO USE SYSTEM BACKING STORE
# vms_sga_use_gblpagfil = TRUE
# FOR BETA RELEASE ONLY. Enable debugging modes. Note that these can
# adversely affect performance. On some non-VMS ports the db_block_cache_*
# debugging modes have a severe effect on performance.
#_db_block_cache_protect = true # memory protect buffers
#event = "10210 trace name context forever, level 2" # data block checking
#event = "10211 trace name context forever, level 2" # index block checking
#event = "10235 trace name context forever, level 1" # memory heap checking
#event = "10049 trace name context forever, level 2" # memory protect cursors
# define parallel server (multi-instance) parameters
#ifile = ora_system:initps.ora
# define two control files by default
control_files = (ora_control1, ora_control2)
# Uncomment the following line if you wish to enable the Oracle Trace product
# to trace server activity. This enables scheduling of server collections
# from the Oracle Enterprise Manager Console.
# Also, if the oracle_trace_collection_name parameter is non-null,
# every session will write to the named collection, as well as enabling you
# to schedule future collections from the console.
# oracle_trace_enable = TRUE
# Uncomment the following line, if you want to use some of the new 8.1
# features. Please remember that using them may require some downgrade
# actions if you later decide to move back to 8.0.
#compatible = 8.1.0
$

There are strange things in the file you posted, are you sure that's your init.ora ? where did you find it ?
Moreover, you use "cat" to list the file, but you name "c:\dir" the directory : what is your OS ?
Furthermore, if you use directories, then you don't need to set utl_file_dir in init.ora, and directories don't show up within parameters, you can see them by
SQL> select * from all_directories;

RMAN DUPLICATE FOR STANDBY FROM ACTIVE DATABASE fails

Hello
I'm trying to use RMAN DUPLICATE to create a standby database using Oracle 11.2.0.3 with PSU 6 on HP-UX.
Primary is 2 node RAC. Standby is also 2 node RAC.
Standby database instance is started in nomount mode.
I use:
duplicate target database for standby from active database
spfile
<some spfile parameters>
with PFILE I get:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/01/2013 12:41:13
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of sql command on clone_default channel at 10/01/2013 12:41:13
RMAN-11003: failure during parse/execution of SQL statement: alter system set spfile= '/opt/oracle/db11203/dbs/spfileCU1.ora'
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-01565: error in identifying file '/opt/oracle/db11203/dbs/spfileCU1.ora'
ORA-27037: unable to obtain file status
HPUX-ia64 Error: 2: No such file or directory
With SPFILE I get;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/01/2013 13:06:34
RMAN-05501: aborting duplication of target database
RMAN-05537: DUPLICATE without TARGET connection when auxiliary instance is started with spfile cannot use SPFILE clause
But I do have RMAN connexion to target database.
Thanks for your help.

Here is the output beginning of the script which clearly shows that I'm always connected to target database:
Recovery Manager: Release 11.2.0.3.0 - Production on Tue Oct 1 13:05:47 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: CU (DBID=1143962925)
connected to auxiliary database: CU (not mounted)
RMAN> set echo on
2> run
3> {
4> configure device type disk parallelism 10;
5>   allocate channel pr1 type disk;
6>   allocate channel pr2 type disk;
7>   allocate channel pr3 type disk;
8>   allocate channel pr4 type disk;
9>   allocate channel pr5 type disk;
10>   allocate channel pr6 type disk;
11>   allocate channel pr7 type disk;
12>   allocate channel pr8 type disk;
13>   allocate channel pr9 type disk;
14>   allocate channel pr10 type disk;
15>   allocate auxiliary channel st1 type disk;
16>   allocate auxiliary channel st2 type disk;
17>   allocate auxiliary channel st3 type disk;
18>   allocate auxiliary channel st4 type disk;
19>   allocate auxiliary channel st5 type disk;
20>   allocate auxiliary channel st6 type disk;
21>   allocate auxiliary channel st7 type disk;
22>   allocate auxiliary channel st8 type disk;
23>   allocate auxiliary channel st9 type disk;
24>   allocate auxiliary channel st10 type disk;
25>   duplicate target database for standby from active database
26>   spfile

Oracle not starting up throwing error

My listener problem is solved but the DB dosent start up and throws this error, I also have a dump of the startup.log and the copy of init.ora file.
[oracle@localhost ~]$ ./oracle.sh start
Starting Oracle: Password:
LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 24-DEC-2009 23:01:32
Copyright (c) 1991, 2005, Oracle. All rights reserved.
TNS-01106: Listener using listener name LISTENER has already been started
Password:
Failed to auto-start Oracle Net Listene using /ade/vikrkuma_new/oracle/bin/tnslsnr
Processing Database instance "sales": log file /u01/app/oracle/oracle/product/10.2.0/db_1/startup.log
OK
startup.log
/u01/app/oracle/oracle/product/10.2.0/db_1/bin/dbstart: Starting up database "sales"
Thu Dec 24 23:02:00 IST 2009
logger: Can't find init file for Database instance "sales".
logger: Error: Database instance "sales" NOT started.
init.ora
# $Header: init.ora 06-aug-98.10:24:40 atsukerm Exp $
# Copyright (c) 1991, 1997, 1998 by Oracle Corporation
# NAME
# init.ora
# FUNCTION
# NOTES
# MODIFIED
# atsukerm 08/06/98 - fix for 8.1.
# hpiao 06/05/97 - fix for 803
# glavash 05/12/97 - add oracle_trace_enable comment
# hpiao 04/22/97 - remove ifile=, events=, etc.
# alingelb 09/19/94 - remove vms-specific stuff
# dpawson 07/07/93 - add more comments regarded archive start
# maporter 10/29/92 - Add vms_sga_use_gblpagfile=TRUE
# jloaiza 03/07/92 - change ALPHA to BETA
# danderso 02/26/92 - change db_block_cache_protect to dbblock_cache_p
# ghallmar 02/03/92 - db_directory -> db_domain
# maporter 01/12/92 - merge changes from branch 1.8.308.1
# maporter 12/21/91 - bug 76493: Add control_files parameter
# wbridge 12/03/91 - use of %c in archive format is discouraged
# ghallmar 12/02/91 - add global_names=true, db_directory=us.acme.com
# thayes 11/27/91 - Change default for cache_clone
# jloaiza 08/13/91 - merge changes from branch 1.7.100.1
# jloaiza 07/31/91 - add debug stuff
# rlim 04/29/91 - removal of char_is_varchar2
# Bridge 03/12/91 - log_allocation no longer exists
# Wijaya 02/05/91 - remove obsolete parameters
# Example INIT.ORA file
# This file is provided by Oracle Corporation to help you customize
# your RDBMS installation for your site. Important system parameters
# are discussed, and example settings given.
# Some parameter settings are generic to any size installation.
# For parameters that require different values in different size
# installations, three scenarios have been provided: SMALL, MEDIUM
# and LARGE. Any parameter that needs to be tuned according to
# installation size will have three settings, each one commented
# according to installation size.
# Use the following table to approximate the SGA size needed for the
# three scenarious provided in this file:
# -------Installation/Database Size------
# SMALL MEDIUM LARGE
# Block 2K 4500K 6800K 17000K
# Size 4K 5500K 8800K 21000K
# To set up a database that multiple instances will be using, place
# all instance-specific parameters in one file, and then have all
# of these files point to a master file using the IFILE command.
# This way, when you change a public
# parameter, it will automatically change on all instances. This is
# necessary, since all instances must run with the same value for many
# parameters. For example, if you choose to use private rollback segments,
# these must be specified in different files, but since all gc_*
# parameters must be the same on all instances, they should be in one file.
# INSTRUCTIONS: Edit this file and the other INIT files it calls for
# your site, either by using the values provided here or by providing
# your own. Then place an IFILE= line into each instance-specific
# INIT file that points at this file.
# NOTE: Parameter values suggested in this file are based on conservative
# estimates for computer memory availability. You should adjust values upward
# for modern machines.
# You may also consider using Database Configuration Assistant tool (DBCA)
# to create INIT file and to size your initial set of tablespaces based
# on the user input.
# replace DEFAULT with your database name
db_name=sales
db_files = 80 # SMALL
# db_files = 400 # MEDIUM
# db_files = 1500 # LARGE
db_file_multiblock_read_count = 8 # SMALL
# db_file_multiblock_read_count = 16 # MEDIUM
# db_file_multiblock_read_count = 32 # LARGE
db_block_buffers = 100 # SMALL
# db_block_buffers = 550 # MEDIUM
# db_block_buffers = 3200 # LARGE
shared_pool_size = 3500000 # SMALL
# shared_pool_size = 5000000 # MEDIUM
# shared_pool_size = 9000000 # LARGE
log_checkpoint_interval = 10000
processes = 50 # SMALL
# processes = 100 # MEDIUM
# processes = 200 # LARGE
parallel_max_servers = 5 # SMALL
# parallel_max_servers = 4 x (number of CPUs) # MEDIUM
# parallel_max_servers = 4 x (number of CPUs) # LARGE
log_buffer = 32768 # SMALL
# log_buffer = 32768 # MEDIUM
# log_buffer = 163840 # LARGE
# audit_trail = true # if you want auditing
# timed_statistics = true # if you want timed statistics
max_dump_file_size = 10240 # limit trace file size to 5 Meg each
# Uncommenting the line below will cause automatic archiving if archiving has
# been enabled using ALTER DATABASE ARCHIVELOG.
# log_archive_start = true
# log_archive_dest = disk$rdbms:[oracle.archive]
# log_archive_format = "T%TS%S.ARC"
# If using private rollback segments, place lines of the following
# form in each of your instance-specific init.ora files:
# rollback_segments = (name1, name2)
# If using public rollback segments, define how many
# rollback segments each instance will pick up, using the formula
# # of rollback segments = transactions / transactions_per_rollback_segment
# In this example each instance will grab 40/5 = 8:
# transactions = 40
# transactions_per_rollback_segment = 5
# Global Naming -- enforce that a dblink has same name as the db it connects to
global_names = TRUE
# Edit and uncomment the following line to provide the suffix that will be
# appended to the db_name parameter (separated with a dot) and stored as the
# global database name when a database is created. If your site uses
# Internet Domain names for e-mail, then the part of your e-mail address after
# the '@' is a good candidate for this parameter value.
# db_domain = us.acme.com # global database name is db_name.db_domain
# FOR DEVELOPMENT ONLY, ALWAYS TRY TO USE SYSTEM BACKING STORE
# vms_sga_use_gblpagfil = TRUE
# FOR BETA RELEASE ONLY. Enable debugging modes. Note that these can
# adversely affect performance. On some non-VMS ports the db_block_cache_*
# debugging modes have a severe effect on performance.
#_db_block_cache_protect = true # memory protect buffers
#event = "10210 trace name context forever, level 2" # data block checking
#event = "10211 trace name context forever, level 2" # index block checking
#event = "10235 trace name context forever, level 1" # memory heap checking
#event = "10049 trace name context forever, level 2" # memory protect cursors
# define parallel server (multi-instance) parameters
#ifile = ora_system:initps.ora
# define two control files by default
control_files = (ora_control1, ora_control2)
# Uncomment the following line if you wish to enable the Oracle Trace product
# to trace server activity. This enables scheduling of server collections
# from the Oracle Enterprise Manager Console.
# Also, if the oracle_trace_collection_name parameter is non-null,
# every session will write to the named collection, as well as enabling you
# to schedule future collections from the console.
# oracle_trace_enable = TRUE
# Uncomment the following line, if you want to use some of the new 8.1
# features. Please remember that using them may require some downgrade
# actions if you later decide to move back to 8.0.
#compatible = 8.1.0

starts up the instance and shuts down immediately.
Here is the log
/u01/app/oracle/oracle/product/10.2.0/db_1/bin/dbstart: Starting up database "sales"
Thu Dec 24 23:26:47 IST 2009
SQL*Plus: Release 10.2.0.1.0 - Production on Thu Dec 24 23:26:47 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> Connected to an idle instance.
SQL> ORA-00371: not enough shared pool memory, should be atleast 62198988 bytes
SQL> Disconnected
/u01/app/oracle/oracle/product/10.2.0/db_1/bin/dbstart: Database instance "sales" warm started.

ORA32004, ORA error during installation

Hi,
During SAP installation I got below error
SAP 2004S
Oracle 10.2
Oracle installation was done successfully(SID-ANK) during SAP installation I am getting this error....
ERROR 2009-07-09 08:32:28
CJS-00084 SQL statement or script failed. DIAGNOSIS: Error message: ORA-32004: obsolete and/or deprecated parameter(s) specifiedORACLE instance started.
ERROR 2009-07-09 08:32:28
MUT-03025 Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined.
ERROR 2009-07-09 08:32:28
FCO-00011 The step createDatabase with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Doublestack_OneHost|ind|ind|ind|ind|3|0|NW_Cr
eateDB|ind|ind|ind|ind|10|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|NW_OraDBMain|ind|in
d|ind|ind|0|0|NW_OraDBStd|ind|ind|ind|ind|3|0|NW_OraDbBuild|ind|ind|ind|ind|5|0|c
reateDatabase was executed with status ERROR .
also during starting oracle...via SQL I am getting error
SQL> startup
ORA-24324: service handle not initialized
ORA-01041: internal error. hostdef extension doesn't exist
I am not sure if both issues are related to each other.
Just for info..
OracleServiceANK is in start mode
OracleANK102Listener is also in start mode.
Also attaching listener.ora sqlnet.ora and tnsnames.ora
listener.ora
Filename......: listener.ora
Created.......: created by SAP AG, R/3 Rel. >= 6.10
Name..........:
Date..........:
@(#) $Id: //bc/700-1_REL/src/ins/SAPINST/impl/tpls/ora/ind/LISTENER.ORA#3 $
ADMIN_RESTRICTIONS_LISTENER = on
LISTENER =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = IPC)
(KEY = ANK.WORLD)
(ADDRESS=
(PROTOCOL = IPC)
(KEY = ANK)
(ADDRESS =
(COMMUNITY = SAP.WORLD)
(PROTOCOL = TCP)
(HOST = INLD50057853A)
(PORT = 1521)
STARTUP_WAIT_TIME_LISTENER = 0
CONNECT_TIMEOUT_LISTENER = 10
TRACE_LEVEL_LISTENER = OFF
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SDU = 32768)
(SID_NAME = ANK)
(ORACLE_HOME = C:\oracle\ANK\102)
tnsnames.ora
Filename......: tnsnames.ora
Created.......: created by SAP AG, R/3 Rel. >= 6.10
Name..........:
Date..........:
@(#) $Id: //bc/700-1_REL/src/ins/SAPINST/impl/tpls/ora/ind/TNSNAMES.ORA#3 $
ANK.WORLD=
(DESCRIPTION =
(SDU = 32768)
(ADDRESS_LIST =
(ADDRESS =
(COMMUNITY = SAP.WORLD)
(PROTOCOL = TCP)
(HOST = INLD50057853A)
(PORT = 1521)
(CONNECT_DATA =
(SID = ANK)
(GLOBAL_NAME = ANK.WORLD)
sqlnet.ora
Filename......: sqlnet.ora
Created.......: created by SAP AG, R/3 Rel. >= 6.10
Name..........:
Date..........:
@(#) $Id: //bc/700-1_REL/src/ins/SAPINST/impl/tpls/ora/ind/SQLNET.ORA#3 $
AUTOMATIC_IPC = ON
TRACE_LEVEL_CLIENT = OFF
NAMES.DEFAULT_DOMAIN = WORLD
NAME.DEFAULT_ZONE = WORLD
SQLNET.EXPIRE_TIME = 0
SQLNET.AUTHENTICATION_SERVICES = (NTS)
TCP.NODELAY=YES
Please do let me know if you need more inputs.
Regards,
Ankit Baphna

Hi,
Thanks,
I got this...now
SQL> alter system set enqueue_resources='';
alter system set enqueue_resources=''
ERROR at line 1:
ORA-25138: ENQUEUE_RESOURCES initialization parameter has been made obsolete
SQL> create pfile from spfile;
create pfile from spfile
ERROR at line 1:
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
SQL> startup
ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE instance started.
Total System Global Area 356515840 bytes
Fixed Size                  1248984 bytes
Variable Size             188743976 bytes
Database Buffers          163577856 bytes
Redo Buffers                2945024 bytes
ORA-00205: error in identifying control file, check alert log for more info
Regards,
Ankit Baphna
Edited by: I041468 on Jul 9, 2009 10:56 AM

Note 830576 - Parameter recommendations for Oracle 10g

hi all DBA experts.
I am not good familiar with Oracle database while i read a Note 830576 - Parameter recommendations for Oracle 10g. in which SAP General Recommendation:
You should delete obsolete initialization parameters from the profile.
To determine which obsolete parameters are currently set, proceed as follows:
SQL> SELECT NAME FROM V$OBSOLETE_PARAMETER WHERE ISSPECIFIED = 'TRUE';
when i execute above command then result is no rows selected
while there are many parameters in above SAP Note which are already obsolete and not set in initSID.ora file.
for exp. the parameter OPTIMIZER_INDEX_COST_ADJ is showing
#### OPTIMIZER MODE
#optimizer_index_cost_adj = 10
as you know that this parameter is very important regarding System Performance.
now please guide me . I have to set these parameter or no need while there is not showing any parameters against obsolete command.
waiting you valuable reply.
Regards,

hi both,
thanks for knowledge sharing with me other SDN users,
Dear Orkun,
Ok. At this stage, I can recommend you that apply what they have suggested,
in the message. So, you already did a part of it by configuring
Oracle parameters, already.
SAP support sent me this file (PRD_Parameters)
*** INFORMATION 1 ***
*** INFORMATION 2 ***
*** INFORMATION 3 ***
*** INFORMATION 4 ***
*** INFORMATION 5 ***
*** INFORMATION 6 ***
*** INFORMATION 7 ***
*** INFORMATION 8 ***
*** INFORMATION 9 ***
*** INFORMATION 10 ***
*** INFORMATION 11 ***
_b_tree_bitmap_plans
_fix_control (4728348)
event (10753)
event (38087)
event (10183)
optimizer_index_cost_adj
star_transformation_enabled
event (10027)
event (10028)
event (10411)
event (10629)
event (14532)
_fix_control (5705630)
_fix_control (5765456)
_optimizer_mjc_enabled
_sort_elimination_cost_ratio
event (10091)
event (10142)
event (38068)
event (38085)
event (44951)
parallel_execution_message_size
parallel_threads_per_cpu
query_rewrite_enabled
log_archive_dest_1
log_archive_format
max_dump_file_size
optimizer_features_enable
log_archive_dest
_push_join_union_view
_cursor_features_enabled
_first_spare_parameter
event (10049)
db_writer_processes
parallel_max_servers
db_cache_size
pga_aggregate_target
processes
sessions
dml_locks
job_queue_processes
log_checkpoint_interval
remote_login_passwordfile
sga_max_size
shared_pool_reserved_size
sort_area_retained_size
sort_area_size
statistics_level
workarea_size_policy
they only highlighted these following parameters from above
**** INFORMATION 8 *** DB Patchset: 10.2.0.4.0
**** INFORMATION 9 *** DB Mergefix: 0 (released before 2008-07-11)
FYI... recently, i applied the Oracle Patches 10.2.0.4 in this sequence
MS Windows x86-64 (64-bit)
Patchset_10204_MSWIN-x86-64aa.bin
Patchset_10204_MSWIN-x86-64ab.bin
Patchset_10204_MSWIN-x86-64ac.bin
OPatch
OPatch_10205_Generic_v0.zip
Generic (32-bit / 64-bit)
p8350262_10204_Generic.zip
p7592030_10204_WIN_GENERIC.zip
p9254968_10204_WIN_GENERIC.zip
10204_Patch44_MSWIN-x86-64.zip
p9584028_102040_Generic.zip
p9843740_10204_Generic.zip
and please tell me , still i have to apply highlighted parameters or now no need.
Regards,

Problems with query settings

My model never saves changes of the query settings 'Maximum rows' and 'Suppress sum'. Every time I reopen my model the settings have the initial values '500' and ' '. For me it seems to be a bug.

Thanks for reporting this issue. It has been fixed and you will be able to see this fix in the next service pack.
Since, this issue is related to obsolete parameters, I believe, not having the fix immediately should not affect the operatability of your Visual Composer installation. In the meantime, you may employ a workaround as described below:
To change the values of maxrows and suppress sum fields:
1. double click on the query infoactor on the story board
2. on the side pane, you should see the properties of the query, the properties including maxrows and supress sum.
3. Make any change in the "Name" property. The save button should turn active.
4. Now make necessary changes in the values of maxrows and suppress sum.
5. Save.

StandBy database creation in oracle 10g

Respected Sir's
I have to create stand by database in oracle 10g i am working on (Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod) .Plz any body provide steps required for creating stand by database in oracle10g.Both the database db1 and db2 are running on archivelog.I am confuse how to set archivelog parameter that goes to db2(standby database) from db(primary database).Any one provide me steps to properly configuring the stand by database.
Thanks

Respected Sir
These are the detailed steps that i performed on standby and primary database.
On both the systems i install the oracle in E drive and the database i create in G drive and archive destination also in G drive.
Like G:\prod1\(all the datafiles,logfiles and control file).
G:\arch\(all the archive files).
ON PRIMARY DATABASE(IP:192.168.2.14):
1.First i create a database with DBCA and the database SID is prod1.
2.Put the database in archive mode and also enable the force logging.
3.Shutdown the Primary database and modify the following parameters in pfile.
log_archive_dest_1='LOCATION=G:\ARCH'
log_archive_dest_2 = "service=STDBY mandatory reopen=60"
log_archive_dest_state_1 = enable
log_archive_dest_state_2 = enable
log_archive_min_succeed_dest = 2
4.Mount the primary database and create the standby controle file and create the spfile from the modified pfile.
5.Shutdown the primary database and take the backup of all the datafile,logfile,standby controlfile ,passwordfile,pfile in a folder.
6.Startup the primary database.
Tnsname.ora Configuration.
Create the connection string using the Net Manager with name STDBY and in host name i provide the IP address of the standby database.
ON STANDBY DATABASE(IP 192.168.2.9):
Listener.ora Configuration.
Create a listener using the Net configuration Assistance.
1.I copy the datafile,logfile and standby controle file in g:\prod1
2.Copy the E:\oracle\product\10.2.0\admin\prod1 folder from primary database and past it on the same location on the standby database.
3.On standby pfile i change only the standby_archive_dest parameter to g:\arch.
4.Create the service with oradim -SID -NEW prod1 -STARTMODE manuall
5.Start the standby database in nomount mode.
6.Create the spfile from pfile and shutdown the database.
7.Startup the database in nomount mode using spfile.
8.ALTER DATABASE MOUNT STANDBY DATABASE;
These are the occurs when i use tnsping stdby on primary database.
C:\Documents and Settings\Administrator>TNSPING STDBY
TNS Ping Utility for 32-bit Windows: Version 10.2.0.1.0 - Production on 04-FEB-2009 12:03:55
Copyright (c) 1997, 2005, Oracle. All rights reserved.
Used parameter files:
E:\oracle\product\10.2.0\db_1\network\admin\sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.2.9
NECT_DATA = (SERVICE_NAME = prod1)))
OK (20 msec)
sqlnet.ora file on stand by database.
SQLNET.AUTHENTICATION_SERVICES= (NTS)
NAMES.DIRECTORY_PATH= (TNSNAMES, LDAP)
BEQUEATH_DETACH=yes
AUTOMATIC_IPC = ON
NAMES.DEFAULT_DOMAIN = IDEVELOPMENT.INFO
SQLNET.EXPIRE_TIME=2
This occurs when i use tnsping prod1 on standby database.
TNS Ping Utility for 32-bit Windows: Version 10.2.0.1.0 - Production on 04-FEB-2
009 12:01:40
Copyright (c) 1997, 2005, Oracle. All rights reserved.
Used parameter files:
E:\oracle\product\10.2.0\db_1\network\admin\sqlnet.ora
TNS-03505: Failed to resolve name
Please help me bec i have to create the stand database as soon as possible.Thanks Sir

Multiple Location of datafiles in Data Guard Environment

I have Data Guard setup in my oracle 10g database. Uptil now , all the datafiles were at same location, therefore db_file parameter setting in pfile was fine. Now I want to move my few of the datafiles at another location. Say, few of my datafiles would be in F:\ and some of them in G:\. How do I now set db_file parameters in Pfile ?

OK...
Alter database rename should be ok As long as both the PRIMARY directory strucures are same or if you have set the parameter db_file_name_convert
While asking a question..
You should post all the necessary information for us to help(is possible)
1.Oracle version
2.Os version
Thread spesific
3.Directory strucutrs of Both Priimary and Standby
4.Init .Ora of both PRIMARY AND STANDBY

Obsolete parameters in pfile

Similar Messages

Maybe you are looking for