Server Administration :: ORA-32004 / Obsolete And / Or Deprecated Parameter(s) Specified
Nov 9, 2011I am getting the following error while starting database.
ORA-32004:obsolete and/or deprecated parameter(s) specified
I am getting the following error while starting database.
ORA-32004:obsolete and/or deprecated parameter(s) specified
I am having Oracle 10g - 10.2.0.1.0 version. When I am starting my Database I get the following message:
ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE instance started.
I want to know which parameter in my PFile is obsolete and what is the New Parameter replaced for that.
********************************************************************************
D:\>sqlplus / as sysdba
********************************************************************************
SQL*Plus: Release 10.2.0.1.0 - Production on Fri Oct 22 16:26:40 2010
Copyright © 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
********************************************************************************
SYS AS SYSDBA in MyDB....> startup
********************************************************************************
ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE instance started.
Total System Global Area 612368384 bytes
Fixed Size 1250428 bytes
Variable Size 121637764 bytes
Database Buffers 482344960 bytes
Redo Buffers 7135232 bytes
Database mounted.
Database opened.
SYS AS SYSDBA in MyDB....>
********************************************************************************
PFILE.ORA
********************************************************************************
*.db_name='MYDB'
*.db_unique_name='MYDB'
MYDB.__db_cache_size=473956352
MYDB.__java_pool_size=4194304
MYDB.__large_pool_size=4194304
MYDB.__shared_pool_size=121634816
[code]....
*******************************************************************************
i try to startup a database, and get that obsolete/deprecated parameter specified(ORA-32004: obsolete and/or deprecated parameter(s) specified)so i try to reset the parameter, but it seems it is already reset(not in spfile), so maybe this is in memory. SO now i try to reset with scope = memory or both, it gives this error(ORA-32029: resetting with SCOPE=MEMORY or SCOPE=BOTH is currently not supported).
what to do, because now i cannot reset with scope = memory and in spfile it is not there but still it comes in deprecated parameter.
I am getting the below error while executing "report obsolete" and "delete obsolete " commands in RMAN. except these two all the RMAN commands are working fine like "list backup summary" "list backup" .....
Error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 08/28/2012 11:03:04
RMAN-06004: ORACLE error from recovery catalog database: ORA-01403: no data found
OS: IBM AIX
Oracle Version: 9.2.0.8
I often use "alter session set xxx=xxx;" command to change parameter value temporarily. After that, how to reset parameter value to default and I don't want logout sqlplus.
View 3 Replies View RelatedSQL> alter system set sga_max_size=1G scope=spfile;
System altered.
SQL> startup force
ORA-12545: Connect failed because target host or object does not exis
SQL> show parameter sga
ERROR:
ORA-03114: not connected to ORACLE
SQL> startup force
ORA-24324: service handle not initialized
ORA-01041: internal error. hostdef extension doesn't exist
SQL> startup
ORA-24324: service handle not initialized
ORA-01041: internal error. hostdef extension doesn't exist
SQL> startup force
ORA-24324: service handle not initialized
ORA-01041: internal error. hostdef extension doesn't exist
How to change db timezone parameter. My application team has asked me to change the db timzone parameter by following sql.
ALTER database SET TIME_ZONE = '+10:00';
Is this way is the correct one , and do we have any impact on database and does it require a db bounce.
It always used to be that Automatic Memory Management and Linux huge pages were incompatible: you had to use one or the other. But 11.2.0.2 has new parameter, USE_LARGE_PAGES. This isn't documented apart from a few articles on metalink, but Googling it suggests that if it is on TRUE (the default) or ONLY then I can use AMM with huge pages.
View 3 Replies View RelatedI have a question ragarding undo tablespace. I want to ask that why only undo tablespace information we need to specify in parameter file. We do not specify any other tablespace information. Not even for temporary tablespace. Then why we need to give undo tablespace name while instance is creating.
View 5 Replies View Relatedwhich initializaion parameter cant be change after creating the database?
View 5 Replies View RelatedWe have migrated database data from physical servers to virtual servers. i want to ensure all database parameters are set correctly in both physical and vblock servers. My question is what are all the parameters need to check and compare in both servers to ensure database from both servers ( physical/vblock ) are in sync.
Database used -- RAC database
OS used -- RHL 5.7
When I list the parameters with "show parameter", I get only numeric value for hash_area_size with no unit, what is the unit for that value and conversion of it to MegaBytes.
View 3 Replies View RelatedI want to change cursor_sharing, open_cursors and session_cached_cursors parameter values for SPFILE (Only SPFILE) using SQL Query.
I have found following SQL Queries, but I don't know these queries are only for SPFILE or not.
ALTER SESSION SET cursor_sharing='EXACT';
ALTER system set open_cursors=2500;
ALTER SESSION set session_cached_cursors=70;
I need SQL Queries only for SPFILE.
I have a simple question about database sessions. The value of parameter "sessions" is set to 500 and the users connect to database through an application server(Jboss). There are more than 500 users connect to the database through application.
My question is, how more than 500 users can connect to the database without any issue, if we set the value of "sessions" parameter to 500?
quick check on a hidden parameter? I need to know the default value and possible values for _serial_direct_read on various releases, I have only 11.2.0.3 available right now and I'ld like to know this for 11.2.x.x 11.1.x.x, and 10.2.x.x.
Below is the query that will show what it is currently which (unless you've changed it) will be the default: auto for my 11.2.0.3. Then to see the options, try to set it to something wrong, my options are false/true/never/auto/always. I think false/true were the only choices for 10.2 and are maintained only for compatibility. But I can't rememebnr 11.1.
orcl>
orcl> set lin 80
orcl> select KSPPSTVL from x$ksppcv join x$ksppi using (indx) where ksppinm='_serial_direct_read';
KSPPSTVL
--------------------------------------------------------------------------------
auto
orcl>
orcl> alter system set "_serial_direct_read"=rubbish;
alter system set "_serial_direct_read"=rubbish
*
ERROR at line 1: ORA-00096: invalid value RUBBISH for parameter _serial_direct_read, must be from among false, true, never, auto, always
orcl>
update: added 11.1.x.x to my wishlist
How oracle deals with the setting of init.ora parameter compatible.
e.g. we have
DB Version=10.2.0.4
compatible=10.2.0
what is the possible leak for us ? Is there any description about the features changed in 10.2 up to 10.2.0.4 in all steps - so that we can check out which functions we do not have.
I have a question about spfile.
SQL> SELECT COUNT(*) FROM v$parameter WHERE value IS NOT NULL;
COUNT(*)
----------
246
SQL> SELECT COUNT(*) FROM v$spparameter WHERE value IS NOT NULL;
COUNT(*)
----------
20
v$parameter displays information about the initialization parameters that are currently in effect for the session,but v$spparameter displays information about the contents of the spfile.I want to know why the count of parameters whose values are not null in v$parameter is greater.where are they from? My initialization parameter file is spfile.
I am getting below in alert log:
Deprecated system parameters with specified values:
remote_os_authent
IS this parameter is supportable in 11G and also how can i remove it from SP file with out bouncing the instance.
While debugging an APEX 4.2 application today, I noticed a debug line DEPRECATED: public_check_authorizationwhen using APEX_UTIL.public_check_authorization in a before header PL/SQL process.
why this line appears? The documentation doesn't point out that this function is deprecated or is going to be this in the near future.
i write a select statement in proc that contains 44 columns.
when i precompile it. it is showing the error: implicit conversion of string literal to "char *" is deprecated.when i compile the same select with 40 columns it is not showing any error.
but for more than 40 columns (41-44) it is showing the above error.
In V$BACKUP_PIECE there are many backup pieces OBSOLETED and EXPIRED with fields: handle set to null and deleted to as "YES"
I ran the CROSSCHECK BACKUP and DELETE OBSOLETE and DELETE EXPIRED BACKUP, and they works.
But how can I remove these lines? Are they still important for anything?
We have EM (Cloud 12c) initiated scheduled backup jobs that perform (all below are online backups, obviously archivelog mode)
- level 0 Incremental 3AM on Sunday - with options backup all archive logs, delete input, delete obsolete
- level 1 Incremental (non cumulative) 3AM every other day - same options
Recovery window is set to 3 days, other options below:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 2;
[code]....
Everything appears to be working normally (archive logs are being backed up and once they are the archive logs themselves are being deleted from the FRA), but I'm having some trouble understanding the behavior of the delete obsolete.
With a recovery window of 3 days, on Monday at 11AM my expectation would be that I would find in backups the following:
- level 0s from day before (Sunday) and the previous Sunday (8 days prior)
- all level 1s from previous Sunday on (so Mon-Sat and this morning)
- archivelog backups from Friday until this morning
What I'm not understanding is that I'm seeing archivelog backups from last Monday, Tuesday, etc. - i would have thought these would have gone obsolete based on my recovery window, yet when I run report obsolete in RMAN nothing is showing up.
I am working on Oracle 10g Rel 2. I am unable to delete the OBSOLETE from rman
previously my senior use to take backup on remote m/c.
While giving the command
rman>delete obsolete
RMAN-06207: WARNING: 228 objects could not be deleted for DISK channel(s) due
RMAN-06208: to mismatched status. Use CROSSCHECK command to fix status
RMAN-06210: List of Mismatched objects
RMAN-06211: ==========================
RMAN-06212: Object Type Filename/Handle
RMAN-06213: --------------- ---------------------------------------------------
RMAN-06214: Backup Piece \192.168.1.162BACKUPFINPRODDB_T619092194_S12_P1
RMAN-06214: Backup Piece \192.168.1.162BACKUPFINPRODDB_T619093015_S13_P1
I've created a small script witch delete the obsolete and expired backups of RMAN.
The problem is: the "delete obsolete" and the "delete expired backup" command needs a confirmation with YES. I don't need to confirm the command and he deletes the backups directly?
Here is my little script:
#!/bin/ksh
export ORACLE_SID=dbtest2
export ORACLE_HOME=/home/oracle/srv/ora/product/11.2.0/dbtest_2
export ORACLE_BIN=/home/oracle/srv/ora/product/11.2.0/dbtest_2/bin
alias RMAN=$ORACLE_BIN/rman
[code].....
We observed that our RMAN backup was taking more time to complete. CROSSCHECK is the main culprit as because of having data in the catalog for more than 3 years.
So in the part of script we added delte obsolete recovery windoe of 14 days. (Redundancey 1).
Here the problem is we are getting error as
RMAN-03002 - failure of delete command
RMAN-06091 - NO channel allocated for maintenance (of an appropriate type).
Reason: Till 2 years back the backup was stored in tape and after that it got changed to disk. So allocating channel disk to delete obsolet is not working. How we can over come this.
We tried like allocating channel tape sbt_type. It got failed as no media manager information configured. We dont have that information.
How we can overcome this.
Oracle 10g
AIX 5.1
I have a problem in running delete obsolete or report obsolete using rman. Although the retention policy is set to "CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 60 DAYS;", when running delete obsolete or report obsolete it deletes or returns all the backupsets till sysdate. What should I do to solve this issue?
View 8 Replies View RelatedI am trying to delete the backupset using Delete Obsolete command, but i am unable to get the success. As per the oracle Doc after completion of Retention Period oracle automatically deletes the backupset. I have set the retention period of 8 days.
View 7 Replies View RelatedHow to create parameter files i.e. (.par) files for expdp/impdp..
View 1 Replies View RelatedWe are having daily syncing script which use to drop and import of one major schema.
When we do import with parameter BUFFER=209715200, it takes approximatively 4 hours & when we do without the parameter it takes 6 hours.
So i humbly request to above scenario of import process with buffer parameter in concern.
Also to expose, import is done in freeze hours.
I taking export using consistent parameter. Theoretically i can understand . practically i couldn't understand how it works.
for ex
I am updating tab1 table under sams user. table having one lakh records.
while updating the query using consistent=y and consistent=n. i mean
exp sams/sams file=cons.dmp owner=sams consistent=y
exp sams/sams file=cons2.dmp owner=sams consistent=n
then both files imported to separate user(sam ,san).
Updated info not visible in san and sam user.
I want to know practically how it works. I need perfect example. while using consistent=y and consistent=n