|
|
Re: Difference between oracle8i and oracle9i [message #90510 is a reply to message #90499] |
Sat, 27 December 2003 06:26 |
William Robertson
Messages: 1643 Registered: August 2003 Location: London, UK
|
Senior Member |
|
|
8i introduced a number of features in SQL that could not be used in PL/SQL. Since we went to 9.2 it's been great to be able to use MERGE INTO, CASE and analytic functions within PL/SQL packages.
A lot of little things are improved in PL/SQL, such as CAST now being implicit in many situations when you used to have to code FROM TABLE(CAST(table_expression AS some_array_type) - you can now use FROM TABLE(table_expression). Also INDEX BY collections (associative arrays) can now INDEX BY other types besides BINARY_INTEGER (e.g. PLS_INTEGER, VARCHAR2).
In 9i you can use locally managed tablespaces for every tablespace including temp, rollback and system, while in 8i you were limited to regular data/index tablespaces. You also get automated undo management which is worth taking a look at (for example you can configure it to hold onto rollback blocks for longer, which could potentially help reduce ORA-01555 Snapshot Too Old errors).
I'm also planning to try out native compilation (stored PL/SQL compiled into C).
For the full list of new features, see the online documentation.
|
|
|
Re: Difference between oracle8i and oracle9i [message #90547 is a reply to message #90499] |
Fri, 13 February 2004 00:10 |
shbgupta
Messages: 4 Registered: November 2003
|
Junior Member |
|
|
Differences Between Debugging on Oracle8i or Oracle9i Release 1 and Oracle9i Release 2 DatabasesThe main differences between debugging on the Oracle8i Release 8.1.7 or Oracle9i Release 1 databases and debugging on the Oracle9i Release 2 database are as follows
Debugging Java stored procedures is supported in the Oracle9i Release 2 database only.
For Oracle8i or Oracle9i Release 1 databases, scalar data types such as NUMBER and VARCHAR2 are displayed as a single, nonexpandable entry in the Data and Watches window. For Oracle9i Release 2 databases, all data types (including scalars) are shown as expandable entries.
For Oracle8i or Oracle9i Release 1 databases, limited access to composite data types is provided. See "Known Issues" below for more information.
For Oracle8i or Oracle9i Release 1 databases, the Tracing Classes and Packages to Include and the Tracing Classes and Packages to Exclude entries, which are specified in Project | Project Settings - Debugger, are not used.
Known IssuesThe following are issues encountered when debugging against an Oracle8i or Oracle9i Release 1 database. These are limitations of the older API and will not be fixed.
Composite data typesThe JDeveloper data-related windows including the Data window, the Watches window, and the Inspector windows can display variables which are scalar types such as NUMBER, VARCHAR2, and the like. Other more complex types are also displayed including:
CURSOR
The value displayed will show the flags, rowcount, and knlflags.
RECORD
The debugger cannot display an entire record. However, you can enter an expression in the Watches or Inspector windows to see a given field in the record. For example, my_rec.my_field.
TABLE of <scalar>
The debugger displays a folder (similar to how it displays an array in Java stored procedures). The user can expand the folder to see the elements. The user can right-click the folder and choose Adjust Range to enter the range of indexes that should be displayed when the folder is expanded. The default range is 1...100. The more indexes in the range (even if the elements for those indexes don't exist in the table), the longer it will take to expand the folder.
TABLE of <composite>
The debugger displays a folder (similar to how it displays an array in Java stored procedures). If the user expands the folder, the debugger may not be able to display the elements. This includes tables of tables.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Re: Difference between oracle8i and oracle9i [message #90818 is a reply to message #90808] |
Tue, 25 January 2005 10:59 |
xyz
Messages: 9 Registered: January 2002
|
Junior Member |
|
|
Let's begin by taking a look at the differences between the Oracle9i database and the Oracle8i database. One of the most significant enhancements to Oracle9i is the elimination of the need to have a separate PGA area for all dedicated connections to the Oracle database. As we may remember from Oracle8i, dedicated Oracle connections were required to allocate a separate area within the RAM memory called a Program Global Area, or PGA. This PGA region contains the SORT_AREA_SIZE and additional RAM control structures that were used to maintain the state for the connected task. In Oracle 9i, the PGA region has been replaced by a new RAM region inside the Oracle SGA as specified by the PGA_AGGREGATE_TARGET parameter
Because all RAM memory usage is now handled completely within the Oracle SGA, the Oracle database administrator can fully allocate the Oracle server's RAM memory, up to 80 percent of the total RAM on the Oracle server. Oracle recommends that 20 percent of the RAM memory on a database server be reserved for operating system tasks.
As users connect to the Oracle9i database, RAM for their sort work areas are allocated within the PGA_AGGREGATE_TARGET region of Oracle9i. This allows Oracle9i perform far faster than Oracle8i because the memory is only allocated in used for the duration of the session upon which is immediately freed up to become available for use by other connected Oracle tasks
|
|
|
|
Re: Difference between oracle8i and oracle9i - Answer here [message #90825 is a reply to message #90499] |
Wed, 02 February 2005 05:10 |
Prasanna
Messages: 43 Registered: April 2001 Location: India
|
Member |
|
|
Oracle 9i is an upgrade version of Oracle.It offers lot of new and additional features, which are not available in oracle 8i.It offers, new features to both
developers and administrators.Oracle 9i is the obvious choice.
Differences Between Debugging on Oracle8i or Oracle9i Release 1 and Oracle9i Release 2 DatabasesThe main differences between debugging on the Oracle8i Release 8.1.7 or Oracle9i Release 1 databases and debugging on the Oracle9i Release 2 database are as follows
Debugging Java stored procedures is supported in the Oracle9i Release 2 database only.
For Oracle8i or Oracle9i Release 1 databases, scalar data types such as NUMBER and VARCHAR2 are displayed as a single, nonexpandable entry in the Data and Watches window. For Oracle9i Release 2 databases, all data types (including scalars) are shown as expandable entries.
For Oracle8i or Oracle9i Release 1 databases, limited access to composite data types is provided. See "Known Issues" below for more information.
For Oracle8i or Oracle9i Release 1 databases, the Tracing Classes and Packages to Include and the Tracing Classes and Packages to Exclude entries, which are specified in Project | Project Settings - Debugger, are not used.
Known IssuesThe following are issues encountered when debugging against an Oracle8i or Oracle9i Release 1 database. These are limitations of the older API and will not be fixed.
Composite data typesThe JDeveloper data-related windows including the Data window, the Watches window, and the Inspector windows can display variables which are scalar types such as NUMBER, VARCHAR2, and the like. Other more complex types are also displayed including:
CURSOR
The value displayed will show the flags, rowcount, and knlflags.
RECORD
The debugger cannot display an entire record. However, you can enter an expression in the Watches or Inspector windows to see a given field in the record. For example, my_rec.my_field.
TABLE of
The debugger displays a folder (similar to how it displays an array in Java stored procedures). The user can expand the folder to see the elements. The user can right-click the folder and choose Adjust Range to enter the range of indexes that should be displayed when the folder is expanded. The default range is 1...100. The more indexes in the range (even if the elements for those indexes don't exist in the table), the longer it will take to expand the folder.
TABLE of
The debugger displays a folder (similar to how it displays an array in Java stored procedures). If the user expands the folder, the debugger may not be able to display the elements. This includes tables of tables.
8i introduced a number of features in SQL that could not be used in PL/SQL. Since we went to 9.2 it's been great to be able to use MERGE INTO, CASE and analytic functions within PL/SQL packages.
A lot of little things are improved in PL/SQL, such as CAST now being implicit in many situations when you used to have to code FROM TABLE(CAST(table_expression AS some_array_type) - you can now use FROM TABLE(table_expression). Also INDEX BY collections (associative arrays) can now INDEX BY other types besides BINARY_INTEGER (e.g. PLS_INTEGER, VARCHAR2).
In 9i you can use locally managed tablespaces for every tablespace including temp, rollback and system, while in 8i you were limited to regular data/index tablespaces. You also get automated undo management which is worth taking a look at (for example you can configure it to hold onto rollback blocks for longer, which could potentially help reduce ORA-01555 Snapshot Too Old errors).
|
|
|
|
Re: Difference between oracle8i and SQL [message #90827 is a reply to message #90826] |
Wed, 02 February 2005 06:11 |
William Robertson
Messages: 1643 Registered: August 2003 Location: London, UK
|
Senior Member |
|
|
The "i" was a marketing label associated with releases 8.1 to 9.2. It's supposed to mean 'Internet' (perhaps due to the new Java features). Perhaps they also hoped it would make you think of fast cars.
I don't understand your question about SQL. Are you asking what it is used for?
|
|
|
Re: Difference between oracle8i and oracle9i [message #115344 is a reply to message #90499] |
Sat, 09 April 2005 22:27 |
kolluri_sridhar
Messages: 2 Registered: April 2005
|
Junior Member |
|
|
Hi!
Here are the differences between oracle 8i and 9i.
What ever i know i am giving it here.Please check once again.
1)ROWID in Oracle8i is different from Oracle9i.
2)Instead of triggers is not present in oracle8i where is it is an added advantage in 9i.
3)We cannot drop a column in atable in Oracle8i where as this is possible in 9i.
4)Snapshot views are not present in 8i where as it is present in 9i.
Regards,
Sridhar
|
|
|