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.
Similar Messages
-
Init.ora file parameter 'processses' not working
When I change the number of processes in my init.ora file from the default of 30 to 200, I get an error when accessing from SQLPlus that Oracle cannot be found. I run Oracle 8.1.6i on a Solaris v7 platform. Any suggestions???
I think your database could not "be found"
'cause it isn't up.
Change the init.ora file parameter 'processses' to 'processes' and restart
the database.
Oracle refuses starting up, if there are
mistyped parameters in init<SID>.ora.
C.Scholten -
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. -
How to set UTL_FILE parameter in the INIT.ORA file
Dear all,
How can i set UTL_FILE parameter in the INIT.ORA file.
Also let me know how to create a directory over there.I am new to this area.
Where exactly i can locate these details and create directory.
Regards,
Bala.post this in database forum
-
ORA-48108: invalid value given for the diagnostic_dest init.ora parameter
Hi All,
I am trying to start my oracle 11g database on windows 7 PC and i am getting below exception
SQL> startup mount
ORA-48108: invalid value given for the diagnostic_dest init.ora parameter
ORA-48140: the specified ADR Base directory does not exist [d:\oracle\app\product\11.2.0\dbhome_1\database\<oracle_base>]
ORA-48187: specified directory does not exist
OSD-00002: additional error information
O/S-Error: (OS 123) The filename, directory name, or volume label syntax is incorrect.
SQL>
Earlier it was working fine. For learning purpose, i have created spfile using pfile and after that i got this issue.
Please help.
Regards,
Sunilsunil907 wrote:
Hi,
I have provided diagnostic_dest folder location (physical path). Now i am getting some different kind of error on startup.
SQL> startup
ORACLE instance started.
Total System Global Area 1068937216 bytes
Fixed Size 2182592 bytes
Variable Size 616563264 bytes
Database Buffers 444596224 bytes
Redo Buffers 5595136 bytes
ORA-00205: error in identifying control file, check alert log for more info
Please help
What does your own research of 'ORA-00205' indicate?
the text of the error message is pretty self explanatory .. it couldn't find the control file.
The control files are specified by the "control_files" initialilzation paramter. When you get this error, the instance has started but was unable to mount the control file. since the init file (spfile) was processed and the instance started you can easily see what it thinks are the control files.
oracle:fubar$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Tue Jul 16 12:51:37 2013
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 835104768 bytes
Fixed Size 2217952 bytes
Variable Size 490735648 bytes
Database Buffers 339738624 bytes
Redo Buffers 2412544 bytes
ORA-00205: error in identifying control file, check alert log for more info
SQL> show parameter control
NAME TYPE VALUE
control_file_record_keep_time integer 7
control_files string /u01/app/oracle/oradata/FUBAR/
controlfile/o1_mf_8ybx4t7w_.ct
x, /u01/app/oracle/flash_recov
ery_area/FUBAR/controlfile/o1_
mf_8ybx4tom_.ctl
control_management_pack_access string NONE
SQL>
So what did you do in fixing your original problem that caused your control_files parameter to go south? -
Hi guys,
Following is the scenario:
1. Oracle DB Binaries: 11.2.0.2.2
2. Using dbca to create General Purpose Database and then modify initialization parameter "COMPATIBLE from 11.2.0.0.0 to 10.2.0.3.0" in the "All Initialization Parameters" window.
So, when I finally start installing database, I get following error during the install:
ORA-00201: control file version 11.2.0.0.0 incompatible with ORACLE version 10.2.0.3.0
ORA-00202: control file: '/u01/app/oracle/cfgtoollogs/dbca/infpp1/tempControl.clt'
IGNORE OR ABORT...
Now you might ask why i am doing this. Actually I want to install fresh 11grel2. database with lower compatible parameter. IMPORT DP custom schemas into this database making sure compatible is set to 10.2.0.3.0. Then run database with such settings for a week and finally change compatible parameter to 11.2.0.0.0
Any thoughts where i am going wrong? as the default template seems not accepting what i am interested to do.
regards,
AnjumIt is not clear why you need to have the compatible parameter set to 10.2.0.3 for the import - it will work perfectly fine with the default value (11.2.0.2) of the compatible parameter. As you have experienced, once you set this parameter, it cannot be changed to a lower value
http://docs.oracle.com/cd/E11882_01/server.112/e23633/intro.htm#CEGJDHGI
HTH
Srini -
Trying to find the init.ora parameter..
Hi,
I am trying to locate the init.ora parameter under the Oracle Database. I was under the impression, that it would be present in the same location as tnsnames.ora, but Ican see that it's not.
Can someone please advise the right location to look for the init.ora parameter file?
Thank You.It is a good practice to let us know the OS and DB version from the start of the thread, so a more accurate answer can be issued sooner.
From the above post I can see you are on a 10g Windows platform. Since 9i inti.ora is not used as the first option, but the spfile. 10g is the same thing, it can work with a pfile, but must probably you have an spfile.
Default location for a 10g spfile in a windows platform is here:
%ORACLE_HOME%\database\spfile%ORACLE_SID%.ora
In case you are working with a pfile, path is quite the same:
%ORACLE_HOME%\database\init%ORACLE_SID%.ora
You can find the path/name of your spfile from an instance parameter inside a SYSDBA session:
SQL> show parameter spfile
HR Madrid -
Regarding UTL_FILE parameter in the INIT.ORA file
Dear all,
How can i set UTL_FILE parameter in the INIT.ORA file.
Also let me know how to create a directory over there.I am new to this area.
Where exactly i can locate these details and create directory.
Regards,
Bala.Dear all,
How can i set UTL_FILE parameter in the INIT.ORA
file.
Also let me know how to create a directory over
there.I am new to this area.
Where exactly i can locate these details and create
directory.
Regards,
Bala.Taken note of yingkuan's comments about directory objects - which don't need a utl_file_dir entry - if you really still need to know (on e-business suite or some other product that needs them) then UTL_FILE_DIR is an initialisation parameter which takes a comma separated list of directories on the database server and to which the oracle software owner (usually oracle on *nix systems and system on windows) has read/write access. To set it therefore you'll need to identify or create your directory and then either
a) add the line UTL_FILE_DIR=/path/to/dir1, /path/to/dir2
to your init.ora if you are using one or use
b) ALTER SYSTEM SET UTL_FILE_DIR=/path/to/dir1, /path/to/dir2 SCOPE=SPFILE;
if you are using a server parameter file.
You should be able to find this and more information in the documentation for your version of Oracle.
Niall Litchfield
http://www.orawin.info/ -
Oracle 11g init.ora parameter settings
Hi Friends,
Oracle 11.2.0.1.0 on Suse Linux.
Can you please let me know what are the things need to be followed while setting init.ora parameters for the database?
And, can you please suggest me the best init.ora settings for the database?
Thanks
KSGHi JL Sir,
Thanks for your valuable guidance.
We have finally come up with the init.ora parameters. Please review and guide me further.
NAME VALUE
tracefiles_public TRUE
tracefile_identifier
processes 100
sessions 120
timed_statistics TRUE
timed_os_statistics 0
resource_limit TRUE
license_max_sessions 0
license_sessions_warning 0
cpu_count 2
instance_groups
event
shared_pool_size 268435456
sga_max_size 1075800904
shared_pool_reserved_size 13421772
large_pool_size 16777216
java_pool_size 167772160
java_soft_sessionspace_limit 0
java_max_sessionspace_size 0
pre_page_sga FALSE
shared_memory_address 0
hi_shared_memory_address 0
use_indirect_data_buffers FALSE
lock_sga FALSE
spfile ?/dbs/[email protected]
lock_name_space
enqueue_resources 1542
trace_enabled TRUE
nls_language american
nls_territory america
nls_sort
nls_date_language
nls_date_format DD-MON-RR
nls_length_semantics BYTE
nls_nchar_conv_excp FALSE
filesystemio_options asynch
disk_asynch_io TRUE
tape_asynch_io TRUE
dbwr_io_slaves 0
backup_tape_io_slaves FALSE
resource_manager_plan
cluster_interconnects
file_mapping FALSE
active_instance_count
control_files /u020/oradata/mecdb/control01.ctl, /u021/oradata/mecdb/control02.ctl, /u026/or
adata/mecdb/control03.ctl
db_file_name_convert
log_file_name_convert
db_block_buffers 0
db_block_checksum TRUE
db_block_size 8192
db_writer_processes 1
db_keep_cache_size 0
db_recycle_cache_size 0
db_2k_cache_size 0
db_4k_cache_size 0
db_8k_cache_size 0
db_16k_cache_size 0
db_32k_cache_size 0
db_cache_size 134217728
buffer_pool_keep
buffer_pool_recycle
db_cache_advice ON
max_commit_propagation_delay 700
compatible 11.2.0
remote_archive_enable true
log_archive_start TRUE
log_archive_dest /app/oracle/admin/mecdb/arch
log_archive_duplex_dest
log_archive_max_processes 2
log_archive_min_succeed_dest 1
standby_archive_dest ?/dbs/arch
log_archive_trace 0
fal_server
fal_client
log_archive_format mecdb_T%t_S%S.arc
log_buffer 1048576
log_checkpoint_interval 100000
log_checkpoint_timeout 72000
archive_lag_target 0
log_parallelism 1
db_files 1022
db_file_multiblock_read_count 16
read_only_open_delayed FALSE
cluster_database FALSE
parallel_server FALSE
parallel_server_instances 1
cluster_database_instances 1
standby_file_management MANUAL
gc_files_to_locks
thread 0
fast_start_io_target 0
fast_start_mttr_target 0
log_checkpoints_to_alert FALSE
recovery_parallelism 0
control_file_record_keep_time 7
logmnr_max_persistent_sessions 1
dml_locks 500
row_locking always
serializable FALSE
replication_dependency_tracking TRUE
instance_number 0
transactions 132
transactions_per_rollback_segment 5
max_rollback_segments 30
rollback_segments
transaction_auditing TRUE
undo_management AUTO
undo_tablespace undo1
undo_suppress_errors TRUE
undo_retention 900
fast_start_parallel_rollback LOW
db_block_checking FALSE
os_roles FALSE
rdbms_server_dn
max_enabled_roles 40
remote_os_authent FALSE
remote_os_roles FALSE
O7_DICTIONARY_ACCESSIBILITY TRUE
remote_login_passwordfile EXCLUSIVE
dblink_encrypt_login FALSE
license_max_users 0
global_context_pool_size
audit_sys_operations FALSE
db_domain world
global_names FALSE
distributed_lock_timeout 60
commit_point_strength 1
instance_name mecdb
service_names mecdb.world
dispatchers
mts_dispatchers
shared_servers 0
mts_servers 0
max_shared_servers 20
mts_max_servers 20
max_dispatchers 5
mts_max_dispatchers 5
circuits 0
mts_circuits 0
shared_server_sessions 0
mts_sessions 0
local_listener mecdb_lsnr
remote_listener
mts_service mecdb
mts_listener_address
mts_multiple_listeners FALSE
serial_reuse DISABLE
cursor_space_for_time FALSE
session_cached_cursors 0
remote_dependencies_mode TIMESTAMP
utl_file_dir *
plsql_v2_compatibility FALSE
plsql_compiler_flags INTERPRETED
plsql_native_c_compiler
plsql_native_linker
plsql_native_library_dir
plsql_native_make_utility
plsql_native_make_file_name
plsql_native_library_subdir_count 0
job_queue_processes 1
parallel_min_percent 0
create_bitmap_area_size 8388608
bitmap_merge_area_size 1048576
cursor_sharing EXACT
parallel_min_servers 0
parallel_max_servers 5
parallel_instance_group
parallel_execution_message_size 2152
hash_join_enabled TRUE
hash_area_size 131072
shadow_core_dump partial
background_core_dump partial
background_dump_dest /app/oracle/admin/mecdb/bdump
user_dump_dest /app/oracle/admin/mecdb/udump
max_dump_file_size 102400000
core_dump_dest /app/oracle/admin/mecdb/cdump
audit_file_dest /app/oracle/admin/mecdb/adump
hpux_sched_noage 0
oracle_trace_enable FALSE
oracle_trace_facility_path ?/otrace/admin/fdf
oracle_trace_collection_path ?/otrace/admin/cdf
oracle_trace_facility_name oracled
oracle_trace_collection_name
oracle_trace_collection_size 5242880
object_cache_optimal_size 102400
object_cache_max_size_percent 10
session_max_open_files 10
open_links 4
open_links_per_instance 4
optimizer_features_enable 11.2.0
fixed_date
audit_trail DB
sort_area_size 65536
sort_area_retained_size 0
db_name mecdb
open_cursors 200
ifile
sql_trace FALSE
os_authent_prefix ops$
optimizer_mode CHOOSE
sql92_security FALSE
blank_trimming FALSE
partition_view_enabled FALSE
star_transformation_enabled FALSE
parallel_adaptive_multi_user FALSE
parallel_threads_per_cpu 2
parallel_automatic_tuning FALSE
optimizer_max_permutations 2000
optimizer_index_cost_adj 100
optimizer_index_caching 0
query_rewrite_enabled false
query_rewrite_integrity enforced
sql_version NATIVE
pga_aggregate_target 536870912
workarea_size_policy auto
optimizer_dynamic_sampling 1
statistics_level TYPICAL
aq_tm_processes 0
hs_autoregister TRUE
dg_broker_start FALSE
drs_start FALSE
dg_broker_config_file1 ?/dbs/[email protected]
dg_broker_config_file2 ?/dbs/[email protected]
olap_page_pool_size 33554432
Thanks
KSG
Edited by: KSG on Apr 27, 2011 1:39 PM -
Init.ora parameter text_enable
What is the relevance of text_enable init.ora
parameter with Intermedia Text 8.1.6. The
parameter exists in the 8.1.6 database, is
not documented in Reference Manual on
Initialization Parameters.http://technet.oracle.com//products/intermedia/htdocs/text_techover.html?found
Scan for text_enable.
This document says it is no longer used in Oracle 8i.
Hope this helps. -
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. -
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!
BenStarting 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 -
FIX_CONTROL-init.ora parameter
hi team,
we are trying to change the following parameter in init.ora file in the below mentioned method , and this was recemmeded by oracle
**._fix_control='5705630:ON','5765456:3','6221403:ON','6329318:ON','6399597:ON','6430500:ON','6440977:ON','6626018:ON','6670551:ON','6972291:ON','7325597:ON','7692248:ON','7891471:ON'*
but the above mentioned method is accepting.
kindly help me
regards
karthick
Edited by: user11345217 on Jan 12, 2011 4:29 PMthis was recemmeded by oracle
but the above mentioned method is accepting.Two questions : why not go back to Oracle to complain ? And what mean "not accepting" ?
Depending of your db version, it could be a bug which prevents the database to start when given a wrong bug number (this is a known bug ref. #7509689). So, you dhould double check all those given bugs in the string.
Nicolas.
Edited by: N Gasparotto on Jan 12, 2011 12:10 PM -
Unsetting an init.ora parameter
Version : 11.2, 10.2
Platform : Solaris 10
To Unset an init.ora parameter , would you do
alter system set shared_pool_size='' scope=both sid = '*';
or
alter system reset shared_pool_size scope=both sid = '*';Tom wrote:
RESET doesn't seem to work well for me. I tried RESET for shared_pool_size and PARALLEL_MAX_SERVERS parameters.
After executing RESET
shared_pool_size should have gone back to its default value of 0 . It didn't
PARALLEL_MAX_SERVERS should have gone back 485 . It didn'tNeither of the above parameter reverted to default. PARALLEL_MAX_SERVERS is OS dependant. So I chose a parameter which is not OS dependant : SQL_TRACE
SQL_TRACE's default is FALSE. I set it to TRUE. Then I did a RESET. But this parameter didn't go back to FALSE.
Testing on 11.2.0.2
SQL> show parameter memory_target
NAME TYPE VALUE
memory_target big integer 1200M
SQL> show parameter shared_pool_si
NAME TYPE VALUE
shared_pool_size big integer 0
SQL>
SQL>
SQL> alter system set shared_pool_size = 50m scope=both;
System altered.
SQL> show parameter shared_pool_size
NAME TYPE VALUE
shared_pool_size big integer 64M
SQL>
SQL> alter system reset shared_pool_size;
System altered.
SQL> show parameter shared_pool_size
NAME TYPE VALUE
shared_pool_size big integer 64M
SQL>
SQL> show parameter PARALLEL_MAX_SERVERS
NAME TYPE VALUE
parallel_max_servers integer 485
SQL>
SQL>
SQL>
SQL> alter system set PARALLEL_MAX_SERVERS = 482 scope=both;
System altered.
SQL> show parameter PARALLEL_MAX_SERVERS
NAME TYPE VALUE
parallel_max_servers integer 482
SQL> alter system reset PARALLEL_MAX_SERVERS;
System altered.
SQL> show parameter PARALLEL_MAX_SERVERS
NAME TYPE VALUE
parallel_max_servers integer 482-- Test failed for SQL_TRACE parameter as well
SQL_TRACE's default is FALSE. I set it to TRUE. Then I did a RESET. But this parameter didn't go back to FALSE.
So, I had to manually set sql_trace = false scope=both . Here is what I did
SQL> show parameter sql_trace
NAME TYPE VALUE
sql_trace boolean FALSE
SQL>
SQL>
SQL> alter system set sql_trace = true scope=both;
System altered.
SQL> show parameter sql_trace
NAME TYPE VALUE
sql_trace boolean TRUE
SQL> alter system reset sql_trace;
System altered.
SQL> show parameter sql_trace
NAME TYPE VALUE
sql_trace boolean TRUE
SQL>
SQL> ----------------------> Since RESET didn't work, I am setting it manually
SQL>
SQL> alter system set sql_trace = false scope=both;
System altered.
SQL> show parameter sql_trace
NAME TYPE VALUE
sql_trace boolean FALSE
I retested it and found that we need to give sid='*' only then it will work. So alter system reset doesn't seems to make an immediate effects.
Have a look in my example.
SQL> show parameter shared_pool
NAME TYPE VALUE
shared_pool_reserved_size big integer 10M
shared_pool_size big integer 0
SQL> alter system set shared_pool_size=100m scope=both;
System altered.
SQL> alter system reset shared_pool_size;
System altered.
SQL> show parameter shared_pool
NAME TYPE VALUE
shared_pool_reserved_size big integer 10M
shared_pool_size big integer 100M
SQL> show parameter PARALLEL_MAX_SERVERS
NAME TYPE VALUE
parallel_max_servers integer 20
SQL> alter system set PARALLEL_MAX_SERVERS=50;
System altered.
SQL> show parameter PARALLEL_MAX_SERVERS
NAME TYPE VALUE
parallel_max_servers integer 50
SQL> alter system reset PARALLEL_MAX_SERVERS;
System altered.
SQL> show parameter PARALLEL_MAX_SERVERS
NAME TYPE VALUE
parallel_max_servers integer 50Now with SID='*'
SQL> show parameter shared_pool
NAME TYPE VALUE
shared_pool_reserved_size big integer 10M
shared_pool_size big integer 0
SQL> alter system set shared_pool_size=120m scope=both;
System altered.
SQL> alter system reset shared_pool_size sid='*';
System altered.
SQL> show parameter shared_pool
NAME TYPE VALUE
shared_pool_reserved_size big integer 10M
shared_pool_size big integer 120M
SQL> startup force
Total System Global Area 523108352 bytes
Fixed Size 1375704 bytes
Variable Size 293601832 bytes
Database Buffers 222298112 bytes
Redo Buffers 5832704 bytes
Database mounted.
Database opened.
SQL> show parameter shared_pool
NAME TYPE VALUE
shared_pool_reserved_size big integer 10M
shared_pool_size big integer 0Now for parallel_max_server test
SQL> show parameter parallel_max
NAME TYPE VALUE
parallel_max_servers integer 20
SQL> alter system set parallel_max_servers=20 scope=both;
System altered.
SQL> alter system set parallel_max_servers=30 scope=both;
System altered.
SQL> show parameter parallel_max
NAME TYPE VALUE
parallel_max_servers integer 30
SQL> alter system reset parallel_max_servers sid='*';
System altered.
SQL> show parameter parallel_max
NAME TYPE VALUE
parallel_max_servers integer 30
SQL> startup force
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instan
ORACLE instance started.
Total System Global Area 523108352 bytes
Fixed Size 1375704 bytes
Variable Size 293601832 bytes
Database Buffers 222298112 bytes
Redo Buffers 5832704 bytes
Database mounted.
Database opened.
SQL> show parameter parallel_max
NAME TYPE VALUE
parallel_max_servers integer 20My database is 11.2.0.1 were i tested
So we have seen that parameters returns to theri default values if you spcify sid='*' and bounce database.
Edited by: 909592 on Mar 23, 2012 1:43 PM -
ORA-00406: COMPATIBLE parameter needs to be 8.1.0.0.0 or greater
Hello there, I have an ERROR message while performing an Alter table instruction. Can anyone spot the flaw and propose possible solutions.
ALTER TABLE "ALMACEN2"."DINGRESOSALIDAALM"
DROP ("ITEMOTRABAJO", "IDORDENPRODUC", "IDEMPAQUE", "CANTEMPAQUE",
"TARA", "LIQUIDADO", "DEVUELTO", "ARANCEL", "DISTRIBUCION", "REVISADO",
"NUMPALETA", "DESPACHADO") CASCADE CONSTRAINTS;
S
Output:
ORA-00406: COMPATIBLE parameter needs to be 8.1.0.0.0 or greater
Thanks indeedoerr ora 40600406, 00000, "COMPATIBLE parameter needs to be %s or greater"
// *Cause: The COMPATIBLE initialization parameter is not high
// enough to allow the operation. Allowing the command would make
// the database incompatible with the release specified by the
// current COMPATIBLE parameter.
// *Action: Shutdown and startup with a higher compatibility setting.
Maybe you are looking for
-
everytime i try to download the software it makes me wait like 2 hours then at the last second it says connection timed out...idk what to do heelllp
-
Oracle Configuration Manager - EBS R12.1.1
Hi , EBS R12.1.1, on OEL 5.4 Is there forums for Oracle Configuration Manager? I am trying to configure it, but as usual the docs is very topsiturvy. Identifying If Oracle Configuration Manager Is Already Installed or Configured Oracle Configuration
-
Hi! How do I limit the character number that can be inserted into a JtextField and JPasswordField. For examen is the Password can be mam 6 characters, how do I do from limit the input? Thanks
-
Need a Query to update....below are requirements
Hi, I need a query to update table xx_cc_audit. below are requirements. In xx_cc_audit I have more than 1000 rows. In this table Column - contract_number is inserted as null for some rows. I need a query to update this xx_cc_audit table which will re
-
Can you change aspect ratio to any clip??
Hi im an avid user so still trying to get my head around final cut (recently brought a macbook pro) Im wondering whether its possible to change the aspect ratio on one clip within a sequence say 16:9 to 4:3 or vice versa...Its a very easy process wit