Init.ora has format like *.db_name

What's the difference for init.ora has format with *. as prefix and without?
Eg. *.db_name='prod' vs. db_name=prod
Thanks!

initialization parameter files are of two kinds... One is static init.ora (normal text file) and another one is dynamic init.ora (binary file).
You will fine * in dynamic init.ora . Don't do any thing there. Don't try to edit it.
Example from dynamic init.ora..
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='C:\oracle\product\10.2.0/admin/orcl/udump'
If you use (dynamic init.ora) SPFILE then you can change few parameters when the database is up.
More details are here...
http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14231/create.htm#sthref441

Similar Messages

Oracle 11g init.ora file

1) I am a bit confused with init.ora file format in oracle 11g. In addition=
to the usual entries that are prefixed with *.<parameter>, it also has ent=
ries prefixed with <sid>.__<parameter>. I am not able to find an explanatio=
n of these <sid>__ entries from oracle 11g documentation. I am told by a co=
lleague that they are for instance, to cater for multiple-instances databa=
ses. Is that correct?
2) The presence of the <sid>.__ entries confuse me since some parameters ap=
pear in both <sid>__ and *. sections. What if the values for the same param=
eter are different, which one is used by oracle? I guess it's the <sid>.__ =
one?=20
3) In my case the database has only 1 instance, so I guess I can remove all=
<sid>.__ entries and only work with *. entries?
Thanks
Long

Hi,
the entries with double underscore in the spfile that you mention are not new in 11g but also show up in 10g.
They are caused by the background process MMAN (Memory Manager), that is active if you set SGA_TARGET>0 (in 10g) rsp. MEMORY_TARGET>0 (in 11g).
This MMAN modifies the Oracle Memory components like the shared pool and the buffer cache, using performance statistics captured by the MMON (Manageability Monitor) and storing the new size of the component in the spfile in order to make that size persistent through instance restarts.
The prefix of the SID is meaningless in case of a non-RAC database.
Kind regards
Uwe
http://uhesse.wordpress.com

Init.ora parameter

Hello,
I need to change the init.ora file to point to spfile, such as spfile='D:\oracle\product\11.2.0\db_1\database\spfile.ora'
currently the init.ora has all the variables that spfile has, but we would like to point to spfile from init.ora file.
for this do I have to restart the database to add the above command to init.ora file?
what are the other impacts, if I change init.ora to point ot spfile while the DB is online?
Thanks....

792290 wrote:
Hello,
I need to change the init.ora file to point to spfile, such as spfile='D:\oracle\product\11.2.0\db_1\database\spfile.ora'
currently the init.ora has all the variables that spfile has, but we would like to point to spfile from init.ora file.
for this do I have to restart the database to add the above command to init.ora file?
what are the other impacts, if I change init.ora to point ot spfile while the DB is online?
Thanks....
Assuming your pfile is using the default name in the default location ...
sql> conn / as sysdba
sql> shutdown immediate
sql> create spfile from pfile;
sql> startup;
sql> show parameter spfile
done.
At this point you should be running entirely off the spfile. The pfile is irrelevant, though as Joel mentioned, it's not a bad thing to recreate it from the spfile occasionally and back it up.
-- edit several hours later ...
I should have mentioned that that init file does NOT have an 'ifile' reference to the spfile.

Please help with: WARNING: The user_dump_dest init.ora parameter has been d

Hi gurus,
I have been getting this warning for a while but I can't find a way to get rid of it.
Fri Apr 08 10:29:04 2011
WARNING: The user_dump_dest init.ora parameter has been deprecated.
WARNING: Please remove the user_dump_dest parameter from the init.ora file.
WARNING: The diagnostic_dest init.ora parameter now determines the location of the diagnostic data
WARNING: The new location for the user logs and traces is c:\oracle\diag\rdbms\orcl\orcl\trace
I looked at the init.ora and init_SID.ora file and the pfile but I do not see this parameter. The only places I see this parameter user_dump_dest is through the show parameter user_dump_dest is SQL*Plus and the EM Initialization Parameters, and they both show c:\oracle\diag\rdbms\orcl\orcl\trace.
Please help me fix this warning.
Thank you!
Ben

Starting in Oracle11g we not longer have many of the original OFA file system structures and we see that the ancient dump destination init.ora parms (core_dump_dest, background_dump_dest, user_dump_dest) are placed by a single diagnostic_dest parameter, the place to go when Oracle wants to take a dump.
You can use the new initialization parameter diagnostic_dest to specify an alternative location for the diag directory contents.
As of Oracle Database 11g Release 1, the diagnostics for each database instance are located in a dedicated directory, which can be specified through the DIAGNOSTIC_DEST initialization parameter. The structure of the directory specified by DIAGNOSTIC_DEST is as follows:
<diagnostic_dest>/diag/rdbms/<dbname>/<instname>
This location is known as the Automatic Diagnostic Repository (ADR) Home. For example, if the database name is proddb and the instance name is proddb1, the ADR home directory would be <diagnostic_dest>/diag/rdbms/proddb/proddb1.
The following files are located under the ADR home directory:
Trace files - located in subdirectory <adr-home>/trace
Alert logs - located in subdirectory <adr-home>/alert. In addition, the alert.log file is now in XML format, which conforms to the Oracle ARB logging standard.
Core files - located in the subdirectory <adr-home>/cdumd
Incident files - the occurrence of each serious error (for example, ORA-600, ORA-1578, ORA-7445) causes an incident to be created. Each incident is assigned an ID and dumping for each incident (error stack, call stack, block dumps, and so on) is stored in its own file, separated from process trace files. Incident dump files are located in <adr-home>/incident/<incdir#>. You can find the incident dump file location inside the process trace file.
refer the link:-
http://download.oracle.com/docs/cd/B28359_01/server.111/b28320/initparams071.htm
http://www.dba-oracle.com/oracle11g/oracle_11g_diagnostic_dest_tips.htm

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;

Best config for init.ora

Hi,
I am using
OS:win 2k8 server 32 bit
Oracle Database:11g EE 11.2.0.1.0
RAM: 8GB
Like to now what is the best config parmaters for a OLTP with maximum of 100 users at the time
When i use the DBCA command i got the template of init.ora
where i am not seeing anything for PGA or SGA.
if i run the
SQL> show parameter db_cache_size
NAME                                 TYPE        VALUE
db_cache_size                        big integer 0
SQL> show sga
Total System Global Area 778387456 bytes
Fixed Size                  1374808 bytes
Variable Size             486540712 bytes
Database Buffers          285212672 bytes
Redo Buffers                5259264 bytes
SQL> show parameter target
NAME                                 TYPE        VALUE
archive_lag_target                   integer     0
db_flashback_retention_target        integer     1440
fast_start_io_target                 integer     0
fast_start_mttr_target               integer     0
memory_max_target                    big integer 1232M
memory_target                        big integer 1232M
parallel_servers_target              integer     16
pga_aggregate_target                 big integer 0
sga_target                           big integer 0
INIT.ORA(DBCA Configuration)
db_block_size=8192
open_cursors=300
db_domain=""
db_name=mydb
control_files=
db_recovery_file_dest=
db_recovery_file_dest_size=5218762752
compatible=11.2.0.0.0
diagnostic_dest=
memory_target=1287651328
processes=150
audit_file_dest=
audit_trail=db
remote_login_passwordfile=EXCLUSIVE
dispatchers="(PROTOCOL=TCP) (SERVICE=MYDBXDB)"
undo_tablespace=UNDOTBS1
Is the current setting is good or i need to fine tune my parameters
Max of 20 million records from max of 100 users per day
Your suggestions would be helpful for my configutations
Thanks in advance.

You cant generalize performance configuration. If it can be oracle would have don it. Fine tuning of parameter values is a on going process. Its not like you set it one and its done. You need to monitor it constantly and tune it on need basis.
Said that, the first thing that caught me is the setting of SGA_TARGET and PGA_AGGREGATE_TARGET. Both are set to 0 meaning Automated memory management is turned off.
Run the following two query
select name
     , value
from v$parameter
where upper(name) = 'PGA_AGGREGATE_TARGET'
    or upper(name) = 'WORKAREA_SIZE_POLICY'
    or upper(name) like '%\_AREA\_SIZE' escape '\';
select name
     , value
from v$parameter
where upper(name) in (
                          'SGA_TARGET'
                        , 'DB_CACHE_SIZE'
                        , 'SHARED_POOL_SIZE'
                        , 'LARGE_POOL_SIZE'
                        , 'JAVA_POOL_SIZE'
                        , 'STREAMS_POOL_SIZE'
This will indicate the memory related parameters that are manually set in your environment.

Init.ora parameters for banking application

hi
i would like know guidelines for setting
init.ora parameters for database, to handle
load of 2 million transactions per day,with
RAC setup for high availability.
thanks

You will get best practices from your production experiences and good advisors that oracle 10 has provided to you.
http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14223/toc.htm

Init.ora setting not effective after shutdown/startup

Hi there,
I've set optimizer_features_enable = 8.1.7 (both lower caps and upper caps) in init.ora
After shutting down oracle and starting up again,
show parameter opt still shows 9.2.0
SQL> show parameter opt
NAME TYPE VALUE
filesystemio_options string asynch
object_cache_optimal_size integer 102400
optimizer_dynamic_sampling integer 1
optimizer_features_enable string 9.2.0
optimizer_index_caching integer 0
optimizer_index_cost_adj integer 100
optimizer_max_permutations integer 2000
optimizer_mode string CHOOSE
I've to change other parameters e.g. shared_pool_size in the same init.ora file and it's effective after shutdown/restart.
Please advise how to set optimizer_features_enable.

9.x has something called SPFILE also...
SQL> show parameter spfile
If it shows a file name value, something like spfilesid.ora, changes to init.ora would make not much difference :)

Init.ora EVENT parameter to trace processes?

Thanks to all who read my question and offer suggestions!
I have seen in a book the ability to trace individual background processes.
It gave an example of adding the following 2 lines to the init.ora file:
event = "10246 trace name context forever"
event = "10500 trace name context forever"
After stopping and restarting it creates trace files for the PMON and SMON
processes in the Background_Dump_Dest folder.
But my question... is there any reference chart anywhere that shows you what
event numbers you would use for other background processes?
I am running 8.1.7 on Windows 2000
Thank you for your help!
[email protected]

Thanks Hemant again.
Pasted from the link.
<How the COMPATIBLE Initialization Parameter Operates
The COMPATIBLE initialization parameter operates in the following way:
It controls the behavior of your database. For example, if you run an Oracle Database 11g Release 2 (11.2) database with the COMPATIBLE initialization parameter set to 10.1.0, then it generates database structures on disk that are compatible with Oracle Database 10g Release 1 (10.1). >
So eventhough the oracle version is 11.2.0.2.0 it works more or less like 10.1.0.2.Is my understanding correct?If so,then there is no point in upgrading oracle to 11.2 if this parameter has a lower value.Pls correct me.
Thanks.

INIT.ora-COMPATIBLE parameter

Hi,
My oracle version is 11.2.0.2 but in INIT.ora the parameter COMPATIBLE is set to 10.1.0.2.0.How does it impact DB?Does it mean that optimizer will use 10.1.0.2 features? Does it affect the performance of DB/queries in any manner?How will it impact if i change the vaue of this parameter t0 11.2.0.2 in INIT.ORA?Please throw some light on it
SQL*Plus: Release 11.2.0.2.0 Production on Mon Sep 26 12:59:29 2011
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> show parameter compat
NAME TYPE VALUE
compatible string 10.1.0.2.0Thanks.

Thanks Hemant again.
Pasted from the link.
<How the COMPATIBLE Initialization Parameter Operates
The COMPATIBLE initialization parameter operates in the following way:
It controls the behavior of your database. For example, if you run an Oracle Database 11g Release 2 (11.2) database with the COMPATIBLE initialization parameter set to 10.1.0, then it generates database structures on disk that are compatible with Oracle Database 10g Release 1 (10.1). >
So eventhough the oracle version is 11.2.0.2.0 it works more or less like 10.1.0.2.Is my understanding correct?If so,then there is no point in upgrading oracle to 11.2 if this parameter has a lower value.Pls correct me.
Thanks.

Init.ora recommendations

Can anyone tell me what the init.ora settings/configuration recommendations for 9i are or where I can find a full list of them? Thank you for any help you can give me.

Hello
Cursor_sharing refers to how oracle will treat sql statements it has loaded in the shared pool. If, for instance, you were to issue the following sql statements
SELECT * FROM table WHERE column = 'ABC'
SELECT * FROM table WHERE column = 'DEF'
SELECT * FROM table WHERE column = 'HIJ'
SELECT * FROM table WHERE column = 'KLM'
Each is likely to have the same execution plan but oracle would need to store 4 separate copies of the statement in memory because litterals were used rather than bind variables. The cursor_sharing parameter allows you to tell oracle to ignore the litteral and treat it as a bind vaiable like so
SELECT * FROM table WHERE column = :Bind1
This means that oracle can treat this statement as a "template" for subsequent executions, which means that a) it doesn't have to be re-parsed and b) it only has to store 1 copy of the statement. This becomes more significant when you have 1000s of statements using litterals rather than bind variables...the database won't scale.
The different options you have for this parameter tell oracle how to behave when it comes across statements like this. This link will tell you what they mean.
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96536/ch131.htm#REFRN10025
As for db_block_buffers, I'm more used to setting up OLTP environments, so what is a good config for me may be useless for you. Have a look at these links :
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96520/toc.htm
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96532/toc.htm
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96533/toc.htm
HTH
David

Can we determine path of my INIT.ORA file from data dictionary views.

Hello Guru’s
I am new to oracle, My question is for the sake of my knowledge: I work on oracle 10G.
Is there any data dictionary view from where I can get the path of my INIT.ORA file.
Regards,

NewDay wrote:
Hello Guru’s
I am new to oracle, My question is for the sake of my knowledge: I work on oracle 10G.
Is there any data dictionary view from where I can get the path of my INIT.ORA file.
AFAIK , its no. You can check the path from the show parameter command like following,
SQL> show parameter spfile
NAME TYPE
VALUE
spfile string
/u01/app/oracle/product/10.2.0
/db_1/dbs/spfileorcl.ora
SQL>HTH
Aman....

Questions on init.ora file

Hi,
I have some questions on init.ora file. While checking the init file in my system i found that it defines a spfile in a non default location.
The parameter names are like
1) db1.__db_cache_size
2) *._kgl_large_heap_warning_threshold
3) *.sga_target
what do they indicate? I mean what does 'db1.__' , '*._' and '*.' indicate? There are multiple database in the Windows 2003 server and the db version is 10g R1
Regards,
SID
Edited by: SID3 on Jun 29, 2010 5:55 AM
Edited by: SID3 on Jun 29, 2010 5:56 AM

SID3 wrote:
From the discussion i guess the following points
1) db1._ means they are specific to databases.
2) *._ and * means they are used accross databases and chaging it in any of the initfile might affect all? I seriously doubt this.You are mistaken when speaking about database. Bear in mind, a database is not an instance.
* here means this parameter will apply to any instance of that database (if it is in RAC), or to the only one instance of that database (if it is in non-RAC).
Find out more :
http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_2013.htm#i2146449
Nicolas.

How to establish a single init.ora file for 3 node RAC under ASM

All,
Our environment is a combination of several different memory sized SUN machines (V880, V490 & 250R).
Setting up a single init.ora file that encompasses each of the nodes memory into the SGA sizing is our desired setup.
Though we have established the file, the question is getting each NODE on the RAC to use that single parameter
file to start its database instead of taking the default init.ora file in the default (asm/dbs) directory.
As we have performed fail-over testing, upon the restart of instances they have restarted with wrong memory
definitions that have hung the nodes when it took more memory then what was available and swap space began
to grow.
Steps to configure and enable this process is what I am looking for.
Thanks
Gerry

Gerry,
Here's what we do. Not sure if it is relevant to your situation ...
(on each node)
$ cat $ORACLE_HOME/dbs/initrac11d1.ora
SPFILE='+DATA/rac11d/spfilerac11d.ora'
(in ASM)
$ asmcmd
ASMCMD> ls -la +data/rac11d
Type Redund Striped Time Sys Name
Y CONTROLFILE/
Y DATAFILE/
Y ONLINELOG/
Y PARAMETERFILE/
Y TEMPFILE/
N spfilerac11d.ora => +DATA/RAC11D/PARAMETERFILE/spfile.267.685170285
The spfile has all parameters, qualified by node where applicable. For example :
$ sqlplus / as sysdba
SQL*Plus: Release 11.1.0.7.0 - Production on Wed May 6 19:00:45 2009
Copyright (c) 1982, 2008, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Release 11.1.0.7.0 - 64bit Production
With the Real Application Clusters option
SQL> create pfile='/tmp/sb.ora' from spfile;
File created.
SQL> Disconnected from Oracle Database 11g Release 11.1.0.7.0 - 64bit Production
With the Real Application Clusters option
$ cat /tmp/sb.ora
*.archive_lag_target=1800
*.audit_file_dest='/var/oracle/admin/rac11d/adump'
rac11d1.dispatchers='(address=(protocol=tcp)(host=msdbc11-vip)(port=64000))'
rac11d2.dispatchers='(address=(protocol=tcp)(host=msdbc12-vip)(port=64000))'
*.global_names=TRUE
rac11d1.instance_number=1
rac11d2.instance_number=2
rac11d1.undo_tablespace='UNDOTBS1'
rac11d2.undo_tablespace='UNDOTBS2'
Hope this helps,
Steve

The .txt file has formatting issues that need to be resolved

Transaction ZEHS20 runs a program that assigns a CCL Group to a specification header, based on its Active Ingredients. The transaction can be run in the background if desired with output being emailed to the user.The .txt file has formatting issues that need to be resolved. can u pls Help me to resolve this issue.
Thanks

What is the formatting issue like? Could you please elaborate a bit more.
If it is because of varying lengths in the data then it can be handled by utilising a CONCATENATE RESPECTING blanks.

Init.ora has format like *.db_name

Similar Messages

Maybe you are looking for