Deprecated versus obsolete

Hi,
This has puzzled me for several years. Can anyone tell me the difference between deprecated methods and obsolete methods? I would normally think that "obsolete" is worse than "deprecated", but that doesn't seem to be the case.
For instance, the Container method add(String, object) is "obsolete", but you don't get any warnings when you use it. Likewise, the java.awt.Choice method addItem() is supposed to be obsolete, but you don't get a compiler error or warning when you use it. On the other hand, the java.awt.List addItem() method is deprecated, and you do get a warning.
Why aren't the obsolete methods marked as deprecated, and why don't obsolete methods trigger compile-time warnings?
Anybody have an answer?
--Steve

Must be from a book.
OP: In your case the author's intent for using the
word 'obsolete' would be to mean that it is
deprecated. Nope, should've read his post.
From the API:
add
public Component add(String name,
Component comp)Adds the specified component to this container. This is a convenience method for addImpl
(java.awt.Component, java.lang.Object, int).
This method is obsolete as of 1.1. Please use the method add(Component,
Object) instead.
See Also:
add(Component, Object)I would think "obsolete" is just an informal "deprecated". It is
strange to have them refer to it as that without deprecating it,
however.

Similar Messages

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.

What is feature about programing on 10g that have been deprecated on 11g?

Hi All
     I knew just about new feature and enhancement on 11g but I don't know about programming feature that have been deprecated or obsoleted on 11g.
     Because my client concerned If they will upgrade to 11g, What have source codes been impacted or need to be rewritten?
     Updated : I opened SR for this question already if I got any information, I will share to you all ASAP.
Thank you for advance.
Hiko

Well, I know at least one 10g behavior that changed in 11g (and it is documented). In 10g XML extract method automatically applied pretty-print:
SQL> select *
2    from v$version
3 /
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bi
PL/SQL Release 10.2.0.5.0 - Production
CORE    10.2.0.5.0      Production
TNS for 64-bit Windows: Version 10.2.0.5.0 - Production
NLSRTL Version 10.2.0.5.0 - Production
SQL> set long 1000
SQL> with data as (
2                select xmltype(
3                                '<parameters>
4 <parameter name="result"><value>success</value></parameter>
5 <parameter name="showBirthday"><value>false</value></parameter>
6 <parameter name="_wrCommand"><value>clearCacheBefore</value></parameter>
7 </parameters>') val
8                   from dual
9               )
10 select value(x).extract('/parameters') res
11    from data,
12          table(xmlsequence(extract(val, '/parameters'))) x
13 /
RES
<parameters>
<parameter name="result">
    <value>success</value>
</parameter>
<parameter name="showBirthday">
    <value>false</value>
</parameter>
<parameter name="_wrCommand">
    <value>clearCacheBefore</value>
</parameter>
</parameters>
RES
SQL>
And on 11g XML method will not pretty-print. Using XMLSERIALIZE, will:
SQL> select *
2    from v$version
3 /
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
PL/SQL Release 11.2.0.3.0 - Production
CORE    11.2.0.3.0      Production
TNS for 64-bit Windows: Version 11.2.0.3.0 - Production
NLSRTL Version 11.2.0.3.0 - Production
SQL> set long 1000
SQL> with data as (
2                select xmltype(
3                                '<parameters>
4 <parameter name="result"><value>success</value></parameter>
5 <parameter name="showBirthday"><value>false</value></parameter>
6 <parameter name="_wrCommand"><value>clearCacheBefore</value></parameter>
7 </parameters>') val
8                   from dual
9               )
10 select value(x).extract('/parameters') res
11    from data,
12          table(xmlsequence(extract(val, '/parameters'))) x
13 /
RES
<parameters><parameter name="result"><value>success</value></parameter><paramete
r name="showBirthday"><value>false</value></parameter><parameter name="_wrComman
d"><value>clearCacheBefore</value></parameter></parameters>
SQL> with data as (
2                select xmltype(
3                                '<parameters>
4 <parameter name="result"><value>success</value></parameter>
5 <parameter name="showBirthday"><value>false</value></parameter>
6 <parameter name="_wrCommand"><value>clearCacheBefore</value></parameter>
7 </parameters>') val
8                   from dual
9               )
10 select xmlserialize(document extract(value(x),'/parameters') indent size = 2) res
11    from data,
12          table(xmlsequence(extract(val, '/parameters'))) x
13 /
RES
<parameters>
<parameter name="result">
    <value>success</value>
</parameter>
<parameter name="showBirthday">
    <value>false</value>
</parameter>
<parameter name="_wrCommand">
    <value>clearCacheBefore</value>
</parameter>
</parameters>
RES
SQL>
SY.

Way to know obsolete/moved packages in pacman?

Hi,
Is there a way to know which packages are right now installed on my system(say when I first installed Arch) but which are no longer in the repos or the devs might have changed/merged/renamed them into another packages and thus are no longer updated when I do a -Syu?
The reason is that after installing Alpha 4 and doing a -Syu, I have found many packages moved or merged thereby are now giving library errors or not loading etc. So sort of deprecated or obsolete list by pacman will help in upkeep of a rolling distro. I can get a list of such packages and maybe ask pacman to auto uninstall them if it is safe just the way we do autoclean. Also it will be great if we can see what/where they have been moved into the newer package names.
Any ideas/plans?

Allan wrote:
chakra-user wrote:Hmm but is there a way to see where they are moved into or what are they now called? For instance in Alpha 4 there was kdemod-partitonmanager which is no longer there afer a -Syu and so Iwant to remove kdemod-partitionmanager(and all deps and co-installed packages) but also install the new ones so they are kept updating.
So... you want to remove a package that is not there? The best way to achieve that is to do nothing and it will already be done. To find anything unneeded that was installed as a dep, use the command I gave above.
No!. I meant that kdemod-partitionmanager is installed on my machine as per A4(and thus also in my pacman DB) but is no longer in the repo. how can I see such packages and remove them and at the sametime also know(before removing them) where they are moved to so that I can use the new pkgnames if I want them to be useful to me.

Adobe, you can do so much better.

Last year I switched from an aging but fulling functioning macbook pro to a new spiffy, tiny 11" macbook air. Migration was slow but efficient with only one problem. CS3 did not migrate.
I was quite happy with CS3. It did what I needed it to do. PS and DW are key to a small subset of my work. I had been using these programmes since I built a Flash website in 2000/1, upgrading every few years, and then from Macromedia to Adobe.
I contacted Adobe. I was told, without apology, that they no longer supported installation issues on CS3. I couldn't believe this. I bought it less than 3 years ago. I was told I should upgrade to CS5. Well, I didn't want to, and I certainly didn't feel like there was $800 of value in it for me at this time (obviously I planned to update at some point). I was really mad.
A friend had a copy of CS4 with a spare install. He let me borrow it. This got me through some key website updates, but I had to unauthorise and return once these were done.
Eventually I got a copy of CS5 and I set about installing it last Friday.
6 hours of uninstalling, reinstalling and scouring these forums and I gave up. I would call tech support on Monday (today).
The details of the install failure will be no news to folk here, but there was no consistency from programme to programme - DW would stall, PS wouldn't quit without permissions failure and Illustrator and Flash would just crash...
Today I was about to call, but decided to get all the updates ready, so I was at adobe.com when a pop up chat helper offered help. OK, I'll try this. I let them into my computer - desktop access - and about an hour later Illustrator, Flash and the communication software crashed.
I start again, no way to contact the specific helper. Maybe 90 minutes later this next person concluded that there were permissions problems (duh) and that I should create a new admin account and see if the programmes worked there...
And what if they do, I asked?
No meaningful reply.
I made it clear that I was willing to do this if it could help solve the issue, I went ahead. Sure enough the programmes all functioned for user 'Test'.
'Excellent' said my helper.
"Why excellent?'
Surely you don't expect me to switch users to access Photoshop?
This person continued to act as if the issue was resolved, I maintained that it absolutely was not, and so eventually they gave me a phone number to call.
I never got far enough with the issues with Jim before the call was cut off. OK, Jim has my number, he'll call back. I'll just have a look at these permissions while I wait.
He did not call back.
While I was waiting - a couple of hours (I figured maybe he was consulting some genius) - I accessed the 'Test' account from mine (by adding my account permssions to view 'Test')
The pertinent folders and files were all very simple - all had permssions for 'Test' - read and write, and for Everyone - no access.
I looked at my folders- the ones in
User(me)/library/applications support/adobe, and the ones in User(me)/library/preferences
The permissions were all over the place. Some I had read and write, so read only, some I was not mentioned... and almost all had permssions given to 'wheel' to read and write. Clearly the CS5 installer is not doing what it wants to...
I set about cleaning the folders (and contents) up - making sure I had read and write, everyone had no access and deleting any other accounts.
It worked. I did it for just Illustrator first, and then updated the programmes and permssions as I went...
Then I called Adobe back and complained.
That was about 13 hours of my time to istall a suite of programmes.
It seems pretty clear to me that the DVD version of CS5 was printed up and then it became clear that the installer was not working for a significant percentage of customers. I have seen reference to these issues dating back to CS5's release, a long time ago. Adobe must know this. But what could they do? They have two choices with the DVDs - they recall them and replace them, or they leave them out there and deal with the fall out. I know what I think of Adobe, in this regard, now.
I know beta testing on the general public is common practice, but I do believe that Adobe has crossed a line here. How much work would it have taken to test the installers in just a couple of hunderd macs? This cannot have happened.
I'd love to dump my Adobe software and replace it with better stuff from better companies, if it's out there, but I don't have the time, and I feel like I have too much invested in the product (probably about $3000 since 1999). I'm sure Adobe knows and understands how they have many of us by the balls, so to speak, economically. Our position holds little leverage. The only thing we can do is complain and be vocal about it.
I will be posting this account on my website also. I encourage you all to share your stories. Adobe's customer service right now, is second to everyone. I have not experineced worse. It's hard to argue with the kids using their cracked copies.

While I certainly agree that Adobe has a responsibilty to fix
bugs,how in the world is it their responsibility to fix an Apple or
Microsoft problem?
It is not their responsibility. But working around such problems
is what they should do. Because if they don't, their apps are
unusable.
It is the responsibility of the O/S vendor to make sure that any
installation will not break an installed application...and that is
black and white.
It's not so simple, it depends on what the app does.
For instance, Adobe install many files in /Library. That is much more
likely to cause problems than files installed under /Applications.
And many problems are subtle. Suppose Adobe uses an Apple API in their
code, and it stops working in Lion. Why? Perhaps Adobe used the Apple
API in subtly wrong way that Apple didn't expect, and improvements in
the Apple code caused the subtlety to change? Whose fault is that?
Probably not Apple's. Adobe violated the spec.
What if Apple declared that the API was deprecated and obsolete, but
Adobe still used it because they wanted to retain compatibility with
10.4, which did not support the API that replaced it? Whose fault is
that? I think it is a lot less clear.
What if Adobe thinks Adobe is using an API correctly, but Apple thinks
they are not, and reasonable people can disagree? (I hear Companies are
People. And who would argue that Adobe and Apple are not reasonable?)
These are not clear-cut and black-and-white situations. To a large part,
everyone has to put aside their differences and try to work to improve
the situation.
Apple clearly doesn't give a damn about this and
never has.
It's easy to say this but it's not true. Apple hasn't put the same
degree of effort into compatibility, and there are many reasons for
it. But they do indeed make an effort not to break apps. Perhaps
their efforts come up wantings. Honestly, I'm not sure. It's very
tough to innovate while retaining compatibility (witness, reading ID
CS5.5 files in CS5), and the engineering tradeoffs are often not visible
to those of us wh oare users.
I'm happy to agree that Apple doesn't give enough damns for Bob. But
not that they give no damns at all.
And what happens if Adobe does workaround an Apple/MS bug and
Lion or Windows is fixed? Bang! Everything's broken again.
Proper application of a workaround should not then fail again when the
bug-being-worked-around is fixed. That would be a pretty bad workaround.
And in most cases, there's no need for such either/or -ness. And in
the remaining cases, it's all about the cost of making the workaround
good enough.

1503653.1 - should change the comptability to 11.0.0 from 10.2.0.5 before manuelly upgrade?

hi All,
i am trying to follow through the steps.
I will be porting the data from the old box into a new box ( windows 12.1.0.2.0)
I run the pre- tools script -> preupgrd.sql
it give me error or some warning to fix before doing the upgrade.
My question is , before i port over the data via a cold backup, should i first change the compatability to 11.0.0 from 10.2.0.5.0 (source db) then do a cold backup then port over the data to the new box then do the upgrade steps?
of course i can change the init.ora process to 300. As for the rest of the warning, i am not too sure is it necessary for me to do it since i will moving to a new box. Warning likes, EM database control, etc
                         [Update parameters]
         [Update Oracle Database 10.2.0.5.0 init.ora or spfile]
--> If Target Oracle is 32-bit, refer here for Update Parameters:
WARNING: --> "processes" needs to be increased to at least 300
--> If Target Oracle is 64-bit, refer here for Update Parameters:
WARNING: --> "sga_target" needs to be increased to at least 624951296
WARNING: --> "processes" needs to be increased to at least 300
                          [Renamed Parameters]
                     [No Renamed Parameters in use]
                    [Obsolete/Deprecated Parameters]
--> background_dump_dest         11.1       DESUPPORTED replaced by "diagnostic_dest"
--> user_dump_dest               11.1       DESUPPORTED replaced by "diagnostic_dest"
        [Changes required in Oracle Database init.ora or spfile]
                            [Component List]
--> Oracle Catalog Views                   [upgrade] VALID
--> Oracle Packages and Types              [upgrade] VALID
--> JServer JAVA Virtual Machine           [upgrade] VALID
--> Oracle XDK for Java                    [upgrade] VALID
--> Oracle Workspace Manager               [upgrade] VALID
--> OLAP Analytic Workspace                [upgrade] VALID
--> Oracle Enterprise Manager Repository   [upgrade] VALID
--> Oracle Text                            [upgrade] VALID
--> Oracle XML Database                    [upgrade] VALID
--> Oracle Java Packages                   [upgrade] VALID
--> Oracle Multimedia                      [upgrade] VALID
--> Oracle Spatial                         [upgrade] VALID
--> Data Mining                            [upgrade] VALID
--> Expression Filter                      [upgrade] VALID
--> Rule Manager                           [upgrade] VALID
--> Oracle OLAP API                        [upgrade] VALID
                              [Tablespaces]
--> SYSTEM tablespace is adequate for the upgrade.
     minimum required size: 1122 MB
--> UNDOTBS1 tablespace is adequate for the upgrade.
     minimum required size: 400 MB
--> SYSAUX tablespace is adequate for the upgrade.
     minimum required size: 619 MB
--> TEMP tablespace is adequate for the upgrade.
     minimum required size: 60 MB
--> EXAMPLE tablespace is adequate for the upgrade.
     minimum required size: 78 MB
                      [No adjustments recommended]
                          [Pre-Upgrade Checks]
WARNING: --> Process Count may be too low
     Database has a maximum process count of 150 which is lower than the
     default value of 300 for this release.
     You should update your processes value prior to the upgrade
     to a value of at least 300.
     For example:
        ALTER SYSTEM SET PROCESSES=300 SCOPE=SPFILE
     or update your init.ora file.
ERROR: --> Compatible set too low
     "compatible" currently set at 10.2.0.5.0 and must
     be set to at least 11.0.0 prior to upgrading the database.
     Do not make this change until you are ready to upgrade
     because a downgrade back to 10.2 is not possible once compatible
     has been raised.
     Update your init.ora or spfile to make this change.
WARNING: --> Enterprise Manager Database Control repository found in the database
     In Oracle Database 12c, Database Control is removed during
     the upgrade. To save time during the Upgrade, this action
     can be done prior to upgrading using the following steps after
     copying rdbms/admin/emremove.sql from the new Oracle home
   - Stop EM Database Control:
    $> emctl stop dbconsole
   - Connect to the Database using the SYS account AS SYSDBA:
   SET ECHO ON;
   SET SERVEROUTPUT ON;
   @emremove.sql
     Without the set echo and serveroutput commands you will not
     be able to follow the progress of the script.
WARNING: --> "DMSYS" schema exists in the database
     The DMSYS schema (Oracle Data Mining) will be removed
     from the database during the database upgrade.
     All data in DMSYS will be preserved under the SYS schema.
     Refer to the Oracle Data Mining User's Guide for details.
WARNING: --> Database contains INVALID objects prior to upgrade
     The list of invalid SYS/SYSTEM objects was written to
     registry$sys_inv_objs.
     The list of non-SYS/SYSTEM objects was written to
     registry$nonsys_inv_objs unless there were over 5000.
     Use utluiobj.sql after the upgrade to identify any new invalid
     objects due to the upgrade.
INFORMATION: --> OLAP Catalog(AMD) exists in database
     Starting with Oracle Database 12c, OLAP Catalog component is desupported.
     If you are not using the OLAP Catalog component and want
     to remove it, then execute the
     ORACLE_HOME/olap/admin/catnoamd.sql script before or
     after the upgrade.
INFORMATION: --> Older Timezone in use
     Database is using a time zone file older than version 18.
     After the upgrade, it is recommended that DBMS_DST package
     be used to upgrade the 10.2.0.5.0 database time zone version
     to the latest version which comes with the new release.
     Please refer to My Oracle Support note number 1509653.1 for details.
WARNING: --> Existing schemas with network ACLs exist
     Database contains schemas with objects dependent on network packages.
     Refer to the Upgrade Guide for instructions to configure Network ACLs.
INFORMATION: --> There are existing Oracle components that will NOT be
     upgraded by the database upgrade script. Typically, such components
     have their own upgrade scripts, are deprecated, or obsolete.
     Those components are: OLAP Catalog

Not something I've done before but it seems that setting the parameter to 11.0.0 is a pre-requisite.
http://docs.oracle.com/database/121/UPGRD/intro.htm#BHCJHGFA
A full backup isn't neccessary specifically for this upgrade. Just port your data over, change the compatibile parameter on the spfile/pfile on your target upgrade host and upgrade away.
Your source will be your backup so I would be inclined not to change things on there.
You can ignore some of the warning like EM dbcontrol as it states you can do it manually prior to the upgrade to save time, otherwise it will be done as part of the upgrade process anyway.
Other warnings like. OLAP and the timezone file (timezone is a recommendation) you will need to pay attention to and action, as well as the network ACL warning:
http://docs.oracle.com/database/121/UPGRD/preup.htm#BABEDAFB
http://docs.oracle.com/database/121/UPGRD/preup.htm#BABJGCIC

CS5 system requirements

I was looking at the System requirements for the CS5 Design Premium on Mac platform, it states that you need "Multicore Intel processor". If I only have the Dual 2GHz PowerPC G5 will CS5 Design Premium still work? All the other requirements I meet just fine. Thanks for the help.

Since you directly addressed me and Adobe, some thoughts ...
I fully understand your disappointment in Adobe's not supporting the version of MacOS you have on your system with the CS5 software. If it makes you feel any better, I personally will need to upgrade the MacBook Pro on my desktop to MacOS 10.6.x from MacOS 10.4.x; I never upgraded the OS because I never had reason to do so. For what I was using that Mac for, there was nothing new or compelling in 10.5 or 10.6 that made it worth my time and effort to do a clean MacOS install. Hopefully, I will not have problems doing that OS upgrade prior to my installation of CS5 software. And I'm not the only one within Adobe who has this problem.
Then why aren't we supporting older MacOS versions? Ideally we would but there are practical considerations that prevent that, whether you or I like those considerations or not.
(1)     If we support a particular OS configuration, it means that we must fully test the products under that environment. We cannot simply assume that they will work. If we didn't put an OS limitation on the product and didn't do due dilligence in testing in the older OS environments and there were problems, would you be satisfied? I doubt it and wouldn't blame you for being even more upset with Adobe. The cost of fulling testing on an older OS version used by a very small minority of our target market is no less than the cost of testing under the most current OS release.
(2)     Although Apple makes their OS releases look like "dot releases" (i.e., 10.3, 10.4, 10.5, 10.6, etc.), there are many more very major differences and incompatibilities between these "dot releases" than there are between different major versions of Windows during the same time period (i.e., Windows XP, Windows Vista, and Windows 7), at least from the programmers' point of view.
(3)     Building upon (2) above, the fact is that MacOS development over the years has been much more about neat and cool, cool and neatthan upwards application compatibility. Traditionally and historically, the supreme requirement of OS developers is to maintain upwards application compatibility. In other words, OS release n+1 should be able to run all applications that ran under OS release n with no programming changes and with the same results. New OS features should not break old ones. For the most part, Windows has been fairly successful in this arena with relatively few problems, most of which had to do with closing what ended up being unintended security holes. Only now in 64-bit Windows versions are ancient 16-bit applications finally obsolete. This is not the case with MacOS X. With each of the new "dot releases" (the things with the cat names), some existing APIs (Application Program Interfaces) are either deprecated (made obsolete) or broken and actually replaced with different APIs. Forgetting the cost of reprogramming to meet the new API specifications (which is quite considerable for large programs such the CS5 applications), the cost of accommodating (programming and testing for) multiple generations of APIs and taking different software code paths based on OS versions is staggering, adding tremendously to the program complexity and even possibly resulting in certain program features not being available depending upon the OS version.
Bottom line is that given how Apple develops, tests, and releases OS versions, Adobe needs to make prudent decisions as to what OS versions it can reasonably simultaneously support while maintaining some reasonable level of software functionality, performance, and quality.
Having read the full thread of the responses here, it would appear that the blocker to allowing you to upgrade the OS to a more current version that is supported by CS5 is associated with upward OS software compatibility and how it affects a video card's driver. Unfortunately, I suspect that the video card's manufacturer also got stung with OS upward compatibility issues and had to make decisions in terms of what to continue developing and supporting.
This certainly isn't great news for you and it does mean that one way or another you will need to upgrade more than one component to move forward, but I did want to address your question in as straightforward and honest a manner as I could.
           - Dov

ORA-32004: obsolete and/or deprecated parameter(s) specifiedORACLE instance

Hi friends,
i am trying to install BIW 3.0b (win-2000, oracle 9.2.0.1.0 (patch 9.1.0.4.1)& j2sdk 1_4_1)
while installing database instance i am getting this problem.
INFO 2007-09-26 15:57:09
Copying file C:/SAPinst ORACLE KERNEL/keydb.xml to: C:/SAPinst ORACLE KERNEL/keydb.1.xml.
INFO 2007-09-26 15:57:09
Creating file C:\SAPinst ORACLE KERNEL\keydb.1.xml.
INFO 2007-09-26 15:58:14
Processing of host operation t_HostInfo_SHARED succeeded.
INFO 2007-09-26 15:58:35
The 'saploc' share exists at directory 'E:\usr\sap'. Choosing drive E: as SAP System drive.
INFO 2007-09-26 16:00:26
Copying file C:/dump/export1/DB/ORA/DBSIZE.XML to: DBSIZE.XML.
INFO 2007-09-26 16:00:26
Creating file C:\SAPinst ORACLE KERNEL\DBSIZE.XML.
INFO 2007-09-26 16:00:26
Copying file system node C:\dump\export1/DB/ORA/DBSIZE.XML with type NODE to DBSIZE.XML succeeded.
INFO 2007-09-26 16:00:26
Processing of all file system node operations of table tORA_filecopy succeeded.
INFO 2007-09-26 16:00:26
Copying file C:/SAPinst ORACLE KERNEL/DBSIZE.XML to: C:/SAPinst ORACLE KERNEL/DBSIZE.1.XML.
INFO 2007-09-26 16:00:26
Creating file C:\SAPinst ORACLE KERNEL\DBSIZE.1.XML.
INFO 2007-09-26 16:00:26
Copying file C:/dump/export1/DB/DDLORA.TPL to: DDLORA.TPL.
INFO 2007-09-26 16:00:26
Creating file C:\SAPinst ORACLE KERNEL\DDLORA.TPL.
INFO 2007-09-26 16:00:26
Copying file system node C:\dump\export1/DB/DDLORA.TPL with type NODE to DDLORA.TPL succeeded.
INFO 2007-09-26 16:00:26
Processing of all file system node operations of table tORA_filecopy succeeded.
INFO 2007-09-26 16:00:33
Moving file C:/SAPinst ORACLE KERNEL/DDLORA.TPL to: orig_ddl_ora_tmp.tpl.
INFO 2007-09-26 16:00:33
Moving file C:/SAPinst ORACLE KERNEL/changed_ddl_ora_tmp.tpl to: DDLORA.TPL.
INFO 2007-09-26 16:00:33
Removing file C:/SAPinst ORACLE KERNEL/orig_ddl_ora_tmp.tpl.
INFO 2007-09-26 16:02:00
Package table created
PHASE 2007-09-26 16:02:10
SAP Business WareHouse
PHASE 2007-09-26 16:02:10
SAP Web Application Server
PHASE 2007-09-26 16:02:10
Request common parameters of SAP System
PHASE 2007-09-26 16:02:10
Create operating system accounts
INFO 2007-09-26 16:02:10
Changing account ACCOUNTID=S-1-5-21-1844237615-963894560-725345543-1004 ACCOUNTNAME=biwdev\SAP_LocalAdmin ACCOUNTTYPE=GROUP DESCRIPTION=SAP Local Administration Group MEMBERSHIPSEPARATOR=, OPMODE=CREATE succeeded.
INFO 2007-09-26 16:02:10
Changing account ACCOUNTID=S-1-5-21-1844237615-963894560-725345543-1005 ACCOUNTNAME=biwdev\SAP_BWD_LocalAdmin ACCOUNTTYPE=GROUP DESCRIPTION=SAP Local Administration Group MEMBERSHIPSEPARATOR=, OPMODE=CREATE succeeded.
INFO 2007-09-26 16:02:10
Changing account ACCOUNTID=S-1-5-21-1844237615-963894560-725345543-1006 ACCOUNTNAME=biwdev\SAP_BWD_GlobalAdmin ACCOUNTTYPE=GROUP DESCRIPTION=SAP Global Administration Group MEMBERSHIPSEPARATOR=, OPMODE=CREATE succeeded.
INFO 2007-09-26 16:02:10
Changing account ACCOUNTID=S-1-5-21-1844237615-963894560-725345543-1007 ACCOUNTNAME=ORA_BWD_DBA ACCOUNTTYPE=GROUP CONDITION=YES DESCRIPTION=Database Operator Group MEMBERSHIPSEPARATOR=, OPMODE=CREATE succeeded.
INFO 2007-09-26 16:02:10
Changing account ACCOUNTID=S-1-5-21-1844237615-963894560-725345543-1008 ACCOUNTNAME=ORA_BWD_OPER ACCOUNTTYPE=GROUP CONDITION=YES DESCRIPTION=Database Administration Group MEMBERSHIPSEPARATOR=, OPMODE=CREATE succeeded.
INFO 2007-09-26 16:02:10
Processing of all account operations of table t_SAPComponent_Accounts_Accounts_SHARED succeeded (operation CREATE).
INFO 2007-09-26 16:02:15
Changing account ACCOUNTID=S-1-5-21-1844237615-963894560-725345543-1009 ACCOUNTNAME=biwdev\bwdadm ACCOUNTTYPE=USER DESCRIPTION=SAP System Administrator MEMBERSHIP=biwdev\SAP_BWD_GlobalAdmin,biwdev\Users,Administrators,ORA_BWD_DBA,ORA_BWD_OPER,biwdev\SAP_LocalAdmin,biwdev\SAP_BWD_LocalAdmin MEMBERSHIPSEPARATOR=, OPMODE=CREATE USERPASSWORD=*... succeeded.
INFO 2007-09-26 16:02:15
Changing account ACCOUNTID=S-1-5-21-1844237615-963894560-725345543-1010 ACCOUNTNAME=biwdev\SAPServiceBWD ACCOUNTTYPE=USER CONDITION=YES DESCRIPTION=SAP System Service Administrator MEMBERSHIP=biwdev\SAP_BWD_GlobalAdmin,Administrators,ORA_BWD_DBA,ORA_BWD_OPER,biwdev\SAP_LocalAdmin,biwdev\SAP_BWD_LocalAdmin MEMBERSHIPSEPARATOR=, OPMODE=CREATE USERPASSWORD=*... succeeded.
INFO 2007-09-26 16:02:15
Processing of all account operations of table t_SAPComponent_Accounts_Accounts_SHARED succeeded (operation CREATE).
PHASE 2007-09-26 16:02:16
Request operating system user information
PHASE 2007-09-26 16:02:16
Request operating system user information
PHASE 2007-09-26 16:02:16
Request operating system user information
PHASE 2007-09-26 16:02:16
Request operating system user information
PHASE 2007-09-26 16:02:16
Request operating system user information
PHASE 2007-09-26 16:02:16
Request operating system user information
PHASE 2007-09-26 16:02:16
Request operating system user information
PHASE 2007-09-26 16:02:16
Request operating system user information
PHASE 2007-09-26 16:02:16
Request operating system user information
PHASE 2007-09-26 16:02:17
Request operating system user information
PHASE 2007-09-26 16:02:17
Request operating system user information
PHASE 2007-09-26 16:02:17
Request operating system user information
PHASE 2007-09-26 16:02:17
Request operating system user information
PHASE 2007-09-26 16:02:17
Request operating system user information
PHASE 2007-09-26 16:02:17
Request operating system user information
PHASE 2007-09-26 16:02:17
Request operating system user information
PHASE 2007-09-26 16:02:17
Request operating system user information
PHASE 2007-09-26 16:02:17
Request operating system user information
INFO 2007-09-26 16:02:17
Successfully added privileges 'SeTcbPrivilege SeAssignPrimaryTokenPrivilege SeIncreaseQuotaPrivilege' to account 'S-1-5-21-1844237615-963894560-725345543-1009' on host 'biwdev'!
INFO 2007-09-26 16:02:17
Successfully added privileges 'SeServiceLogonRight SeNetworkLogonRight' to account 'biwdev\SAPServiceBWD' on host 'biwdev'!
INFO 2007-09-26 16:02:17
Successfully added privileges 'SeTcbPrivilege SeAssignPrimaryTokenPrivilege SeIncreaseQuotaPrivilege' to account 'biwdev\bwdadm' on host 'biwdev'!
INFO 2007-09-26 16:02:18
Evaluating all 'tNT_RegistryEntries' table rows succeeded.
INFO 2007-09-26 16:02:19
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-09-26 16:02:20
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-09-26 16:02:21
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-09-26 16:02:21
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-09-26 16:02:22
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-09-26 16:02:23
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-09-26 16:02:24
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-09-26 16:02:24
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-09-26 16:02:53
Creating directory E:\oracle\BWD\sapdata1\system_1.
INFO 2007-09-26 16:02:53
Creating file system node E:\oracle\BWD/sapdata1\system_1 with type DIRECTORY succeeded.
INFO 2007-09-26 16:02:53
Processing of all file system node operations of table tORA_SapdataNodes succeeded.
INFO 2007-09-26 16:02:53
Processing of all file system node operations of table tORA_DatabaseServerNodes succeeded.
INFO 2007-09-26 16:02:53
Processing of all file system node operations of table tORA_SapdataNodes succeeded.
INFO 2007-09-26 16:02:55
Copying file C:/dump/master/NT/COMMON/INSTALL/INITSID.ORA to: E:\oracle\ora92\database\initBWD.ora.
INFO 2007-09-26 16:02:55
Creating file E:\oracle\ora92\database\initBWD.ora.
INFO 2007-09-26 16:02:55
Copying file system node C:\dump\master/NT/COMMON/INSTALL/INITSID.ORA with type FILE to E:\oracle\ora92\database\initBWD.ora succeeded.
INFO 2007-09-26 16:02:55
Copying file C:/dump/master/NT/COMMON/INSTALL/INITSID.SAP to: E:\oracle\ora92\database\initBWD.sap.
INFO 2007-09-26 16:02:55
Creating file E:\oracle\ora92\database\initBWD.sap.
INFO 2007-09-26 16:02:55
Copying file system node C:\dump\master/NT/COMMON/INSTALL/INITSID.SAP with type FILE to E:\oracle\ora92\database\initBWD.sap succeeded.
INFO 2007-09-26 16:02:55
Copying file C:/dump/master/NT/COMMON/INSTALL/INITSID.DBA to: E:\oracle\ora92\database\initBWD.dba.
INFO 2007-09-26 16:02:55
Creating file E:\oracle\ora92\database\initBWD.dba.
INFO 2007-09-26 16:02:55
Copying file system node C:\dump\master/NT/COMMON/INSTALL/INITSID.DBA with type FILE to E:\oracle\ora92\database\initBWD.dba succeeded.
INFO 2007-09-26 16:02:55
Processing of all file system node operations of table tORA_ServerConfig_FORMS succeeded.
INFO 2007-09-26 16:02:57
Processing of adapt operation tORA_ServerConfig succeeded.
INFO 2007-09-26 16:02:59
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-09-26 16:03:02
Moving file E:/oracle/ora92/database/initBWD.ora to: orig_init_ora_tmp.txt.
INFO 2007-09-26 16:03:02
Moving file C:/SAPinst ORACLE KERNEL/changed_init_ora_tmp.txt to: E:\oracle\ora92\database\initBWD.ora.
INFO 2007-09-26 16:03:02
Removing file C:/SAPinst ORACLE KERNEL/orig_init_ora_tmp.txt.
WARNING 2007-09-26 16:03:02
PROBLEM: 'E:\oracle\ora92/bin/oradim' not found. CAUSE: Unable to find application via absolute path in filesystem. Application could perhaps be found using environment variable path or is really missing. Trying to call the application nevertheless.
WARNING 2007-09-26 16:03:02
PROBLEM: 'E:\oracle\ora92/bin/oradim' not found. CAUSE: Unable to find application via absolute path in filesystem. Application could perhaps be found using environment variable path or is really missing. Trying to call the application nevertheless.
INFO 2007-09-26 16:03:02
'E:\oracle\ora92/bin/oradim -new -sid BWD -STARTMODE auto' returned with '20'.
INFO 2007-09-26 16:03:04
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-09-26 16:03:06
Changed working directory to C:\SAPinst ORACLE KERNEL.
ERROR 2007-09-26 16:03:13
CJS-00084 SQL Statement or Script failed. Error Message: ORA-32004: obsolete and/or deprecated parameter(s) specifiedORACLE instance started.
ERROR 2007-09-26 16:03:13
FJS-00012 Error when executing script.
Please let me know, what was tha problem.
Regards,
satish

I suggest you upgrade your Oracle installation to 9.2.0.7 or 9.2.0.8 and then try again.
Markus

Obsolete and deprecated parameters

Hi,
we got the error when i start the istance.
SQL> STARTUP
ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE instance started.
Total System Global Area 167772160 bytes
Fixed Size 1247900 bytes
Variable Size 75498852 bytes
Database Buffers 88080384 bytes
Redo Buffers 2945024 bytes
Database mounted.
Database opened.
How to find which parameters are obsolete and/or deprecated?

user3266490 wrote:
Hi,
we got the error when i start the istance.
SQL> STARTUP
ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE instance started.
Total System Global Area 167772160 bytes
Fixed Size 1247900 bytes
Variable Size 75498852 bytes
Database Buffers 88080384 bytes
Redo Buffers 2945024 bytes
Database mounted.
Database opened.
How to find which parameters are obsolete and/or deprecated?Hi
Check
http://azardba.blogspot.com/2009/08/ora-32004-obsolete-andor-deprecated.html
Regards
Azar
DBA

Obsolete and/or deprecated

Hi there,
I have recently installed Oracle 10g using DBCA. I then ran some scripts to utilise our internal application that runs on Oracle 9i. After shutting down the instance and restarting it, I get the following error:
ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE instance started.
Has anyone any ideas on how to locate this parameter? The alert log did not give me much info.
Regards
Ciara

Thanks for that, the list of deprecated values are as follows. Do I simply set them to false/0 to get rid of the error on startup?
NAME
lock_name_space
buffer_pool_keep
buffer_pool_recycle
max_commit_propagation_delay
remote_archive_enable
log_archive_start
parallel_server
parallel_server_instances
fast_start_io_target
logmnr_max_persistent_sessions
serial_reuse
NAME
max_enabled_roles
global_context_pool_size
plsql_compiler_flags
sql_trace
parallel_automatic_tuning
drs_start
Regards
Ciara

ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance

hi
how to fix this error??
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
ORACLE instance started.OS := OEL 5.6
DB:= 11R2 single instance
kind regards

no one wrote:
hi
how to fix this error??
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
ORACLE instance started.OS := OEL 5.6
DB:= 11R2 single instance
kind regardsThis parameter is deprecated in Oracle 10g
This parameter determines if the background process ARCH is started. It can be set to either true or false.
Of course, it makes no sense, if this parameter is set to true if the database is running in noarchive log mode. If ARCH is started with the database being in noarchive log mode, messages like media recovery disabled will be written into the alert.log file.

Obsolete and/or deprecated parameter(s) specified for plsql_compiler_flags

Hi All,
After upgrading the from 10.2.0.1 to 10.2.0.4 on linux. I am getting ORA-32004: obsolete and/or deprecated parameter(s) specified error for plsql_compiler_flags.
in alert log says
Deprecated system parameters with specified values:
plsql_compiler_flags
End of deprecated system parameter listing
Could you please help me how to fix this problem.
Thanks

Thank you Pavan and oradba.
even after changing to
ALTER SYSTEM SET plsql_compiler_flags = 'NATIVE' SCOPE=SPFILE;
ALTER SYSTEM SET plsql_code_type = "NATIVE" SCOPE=SPFILE;
still I am getting same error. Could you please help me to fix this problem.
Thanks

What reason ORA-32004: obsolete and/or deprecated parameter(s) specified ?

Hi
ORA-32004: obsolete and/or deprecated parameter(s) specified
Whenever i changed my test database from noarchive log mode to archive log mode, after i changed ,i startup database the above error occured.
following steps i do it,
SQL> archive log list;
Database log mode           No Archive Mode
Automatic archival           Disable
Archive destination:           c:\oracle\ora90\rdbms
Oldest on-line log sequence     0
Next log sequence           0
Current log sequence           0
Change your database No Archive mode to Archive mode
Your Database must in mount stage
SQL>shutdown immediate
SQL>startup mount
SQL> archive log list;
Database log mode           No Archive Mode
Automatic archival           Disable
Archive destination:           c:\oracle\ora90\rdbms
Oldest on-line log sequence     0
Next log sequence           0
Current log sequence           0
SQL> alter database archivelog;
Database altered.
SQL> archive log list;
Database log mode           Archive Mode
Automatic archival           Disable
Archive destination:           c:\oracle\ora90\rdbms
Oldest on-line log sequence     0
Next log sequence           0
Current log sequence           0
SQL>alter database open;
SQL>archive log list
Database log mode           Archive Mode
Automatic archival           Disable
Archive destination:           c:\oracle\ora90\rdbms
Oldest on-line log sequence      0
Next log sequence           0
Current log sequence           0
Automatic archival – Disable (the database archive mode but automatic
archival disable
So datas not archive.you must enable the automatic archival)
SQL>archive log start; (session level only enabled not instance level)
SQL> archive log list;
Database log mode           Archive Mode
Automatic archival           Enable
Archive destination:           c:\oracle\ora90\rdbms
Oldest on-line log sequence     0
Next log sequence           0
Current log sequence           0
If you want set instance level you change in parameter file
SQL>show parameter log_archive_start
Name                    Type           Value
log_archive_start boolean      FALSE
SQL>alter system set log_archive_start=true scope=spfile
System altered.
SQL>shut immediate
SQL>startup
ORA-32004: obsolete and/or deprecated parameter(s) specified
Database open.
sql>
But i resolved the problem
I want know the reason why the above error occured
database version : 10g
os : xp ( my laptop) Not office database
Regards
S.Azar
DBA

>
SQL>alter system set log_archive_start=true scope=spfile
System altered.
SQL>shut immediate
SQL>startup
ORA-32004: obsolete and/or deprecated parameter(s) specified
>
Precisely that parameter LOG_ARCHIVE_START is obsolete in 10g. You also don't need to enable the archiving with
archive log start
Simply changing into archive mode also brings up archiver processes since 10g :-)
Kind regards
Uwe
http://uhesse.wordpress.com

SQL*LOADER-Deprecated/Obsolete Features Between Oracle 8.1.7 and Oracle10G

Please let me know the Deprecated/Obsolete Features Between Oracle 8.1.7 and Oracle10G for SQL*LOADER.
I have gone through the documentations and found no notable Deprecated/Obsolete Features for SQL*LOADER.
If anybody has come across some of the features please publish.
Thanks in advance

Please refer
Migrating PL/SQL source code from Oracle 8.1.7 to Oracle 10g

ORA-32004: obsolete and or deprecated parameter

Oracle 11.1.7.0:
When I startup the db I get ORA-32004. There is no trace of which parameter is obsolete in alert logs. Neither do I see that parameter in v$obsolete_parameter. How can I look at what that parameter is?

I found it in alert log. Since it was one parameter I didn't see it clearly in the logs. This parameter was user_dump_dest. I reset this parameter. But we have a requirement to set this parameter becaus current filesystem doesn't have enough space. How can I set this so that the destination can be on different volume than $ORACLE_HOME?

Deprecated versus obsolete

Similar Messages

Maybe you are looking for