DIFFERENCES BETWEEN 10G AND 11G

DIFFERENCES BETWEEN 10G AND 11G

Oracle 10g was the upgraded version from Oracle 9i. It was a very stable version from the outset with many of the bugs in 9i fixed and with host of new features. Primarily it provided grid computing by provision of CPUs and data. To this end, Oracle Enterprise Manager (OEM) gave a powerful grid control mechanism. This version also provided enhancements for advanced extensions such as Oracle RAC (Real Application Clusters), Oracle Data Guard and Oracle Streams. 10g brought about automation of most administration tasks by introducing many self-managing features like automated database diagnostic monitor, automated shared memory tuning, automated storage management, and automated disk based backup and recovery.

Oracle 11g pushed the envelope further, enhancing many of the features found in 10g. It provided new components such as Oracle Application Express, Oracle SQL Developer, Oracle Real Application Testing, Oracle Configuration Manager (OCM), Oracle Warehouse Builder, Oracle Database Vault and Oracle Shadow Copy Service. Therefore 11g provides better performance and its release 2 has been geared for newer operating systems such as Windows 7, Server 2008 and latest versions of Linux, Unix, Solaris, etc.

What is the difference between 10g and 11g?

Compared with 10g, 11g provides more simplified, improved and automated memory management and better ability to diagnose faults through inbuilt infrastructure to prevent, detect, diagnose, and help resolve critical database errors, as well as, low database performance issues. It provides invisible indexes, virtual columns, table partitioning and the ability to redefine tables which have materialized view logs whilst online. A major difference in the two are the new security features found in 11g such as better password-based authentication with mixed case passwords, encryption on tablespace-level and enhancements for data pump encryption and compression.

11g continued the use of different editions used in 10g which are Enterprise Edition (EE), Standard Edition (SE), Standard Edition One (SE1), Express Edition (EX) and Oracle Database Lite for mobile devices.

Conclusion

All in all, 11g is a good upgrade from 10g with many positive enhancements on an evolving technology. The technical documentation which was good in 10g has become even better in 11g, a significant benefit for the DBAs, who depend on it daily. It is common for organizations not to utilize the full features of an Oracle database. Therefore, the benefits of an upgraded version must be properly utilized for the organization to reduce their cost of ownership, downtime and increase performance, which 11g can deliver.

Conclusion 2

Compared with 10g, 11g provides more simplified, improved and automated memory management and better ability to diagnose faults through inbuilt infrastructure to prevent, detect, diagnose, and help resolve critical database errors, as well as, low database performance issues. It provides invisible indexes, virtual columns, table partitioning and the ability to redefine tables which have materialized view logs whilst online. A major difference in the two are the new security features found in 11g such as better password-based authentication with mixed case passwords, encryption on tablespace-level and enhancements for data pump encryption and compression.

Key Differences between Application Developer 11g and Infrastructure 12c

Key Differences between Application Developer 11g and Infrastructure 12c

Oracle Fusion Middleware Infrastructure 12c is similar to the 11g Application Developer installation, except for the following differences:

·         Infrastructure 12c Includes Oracle WebLogic Server

·         Infrastructure 12c Requires Specific Database Schemas

·         Infrastructure 12c Domains Can Include Oracle HTTP Server

Infrastructure 12c Includes Oracle WebLogic Server

The Application Developer 11g installation required two separate installations (Oracle WebLogic Server and then Application Developer to add the Oracle JRF libraries and components). In Oracle Fusion Middleware 12c, a fresh installation requires only the Oracle Fusion Middleware Infrastructure distribution, which contains both Oracle WebLogic Server and the required Java Required Files technologies.

Note that the upgrade procedure does not require the configuration of a new Oracle Fusion Middleware 12c domain. Instead, you use the Reconfiguration Wizard to upgrade the domain.

Infrastructure 12c Requires Specific Database Schemas

Unlike the Application Developer 11g installation, the Infrastructure 12c installation requires that you create a set of required schemas in a supported database. In particular, you must use the 12c Repository Creation Utility (RCU) to create at least one required database schema before you can configure the Oracle Fusion Middleware Infrastructure 12c (12.1.2) software.

Depending upon your requirements, you must install one or more of the following database schemas before you can upgrade to Oracle Fusion Middleware Infrastructure 12c (12.1.2):

• The Service Table (STB) schema, which is a new schema required for all Oracle Fusion Middleware Infrastructure 12c installations. This schema enables a new Oracle Fusion Middleware 12c feature called Cross-Component Wiring.
• The OPSS schema, which provides a database-based security store for Oracle Platform Security Services.

You might be required to create the OPSS 12c (12.1.2) schema, depending upon whether or not you are using a security store in 11g and the type of security you are using.

• The IAU schema, which is used for the OPSS auditing capabilities.

You might be required to create the IAU 12c (12.1.2) schema, depending up whether or not you are using an Audit Data Store in 11g and the type of Audit Data Store you are using.

 Infrastructure 12c Domains Can Include Oracle HTTP Server

In Oracle Fusion Middleware 11g, Oracle HTTP Server instances are typically configured in a separate Oracle instance directory outside the 11gMiddleware home. Oracle HTTP Server 11g instances are managed using the Oracle Process Manager and Notification Server (OPMN) management software. Optionally, the Oracle HTTP Server 11g instances can be "associated with" the WebLogic domain.

In Oracle Fusion Middleware 12c, Oracle HTTP Server instances can be configured a part of an Oracle WebLogic Server domain, using the Oracle Fusion Middleware Configuration Wizard. When configured as part of an Oracle Fusion Middleware Infrastructure domain, Oracle HTTP Server instances can be managed using Oracle Enterprise Manager Fusion Middleware Control and the Oracle Weblogic Scripting Tool (WLST). In Oracle Fusion Middleware 12c, the Node Manager agent is responsible for delegating and executing management requests to OHS instances"

Configuring Oracle HTTP Server in a WebLogic Server Domain

Configuring Oracle HTTP Server in a WebLogic Server Domain

After you have installed Oracle HTTP Server, you can extend an existing Infrastructure domain with Oracle HTTP Server.

If you have not created the Oracle Fusion Middleware Infrastructure domain, you can create it at the same time as Oracle HTTP Server.However, in Selecting Advanced Configurations, ensure that you select System Components too.

• Stopping the Administration Server
  Before starting the configuration wizard, it is important to shut down the Administration Server. This prevents any configuration locks, saves, or activations from occurring during the configuration of the domain.
• Starting the Configuration Wizard
  Start the Configuration Wizard to begin configuring a domain.
• Navigating the Configuration Wizard Screens to Extend the Domain
  Use the Configuration Wizard to extend an existing Infrastructure domain with an Oracle HTTP Server instance.
• Starting the Servers
  After configuration is complete, you can use tools to manage your domain.

Stopping the Administration Server

Before starting the configuration wizard, it is important to shut down the Administration Server. This prevents any configuration locks, saves, or activations from occurring during the configuration of the domain.

To stop the Administration Server, go to the Domain_Home/Bin directory.

·         On UNIX operating systems:

./stopWebLogic.sh

• On Windows operating systems:

stopWebLogic.cmd

You may be prompted for the login credentials of the Administrator user you provided when you configured the Oracle Fusion Middleware Infrastructure domain.

Starting the Configuration Wizard

Start the Configuration Wizard to begin configuring a domain.

To start the Configuration Wizard:

1. Go to the bin directory:

(UNIX) ORACLE_HOME/oracle_common/common/bin

(Windows) ORACLE_HOME\oracle_common\common\bin

where ORACLE_HOME is your 12c (12.2.1.2) Oracle home.

2. Launch the Configuration Wizard:

(UNIX) ./config.sh

(Windows) config.cmd

Navigating the Configuration Wizard Screens to Extend the Domain

Use the Configuration Wizard to extend an existing Infrastructure domain with an Oracle HTTP Server instance.

The following sections step through the Configuration Wizard:

• Selecting the Domain Type and Domain Home Location
  You must specify the domain to be updated with Oracle HTTP Server.
• Selecting the Configuration Template for Oracle HTTP Server
  Use the Templates screen to select the template you require.
• Specifying the Database Configuration Type
  Use the Database Configuration type screen to specify details about the database and database schema.
• Specifying JDBC Component Schema Information
  Use the JDBC Component Schema screen to verify or specify details about the database schemas.
• Testing the JDBC Connections
  Use the JDBC Component Schema Test screen to test the data source connections.
• Selecting Advanced Configuration
  Use the Advanced Configuration screen to complete the domain configuration.
• Specifying the Oracle HTTP Server Details
  Use the OHS Server screen to configure the Oracle HTTP Server instance in the domain.
• Assigning System Components to Machines
  Use the Assign System Components to Machines screen to assign Oracle HTTP Server system components to the machine that you defined when you configured the initial Fusion Middleware Infrastructure domain..
• Reviewing Your Configuration Specifications and Configuring the Domain
  The Configuration Summary screen has detailed configuration information for the domain you are about to extend.
• Writing Down Your Domain Home and Administration Server URL
  The End of Configuration screen shows information about the domain you just configured.

Selecting the Domain Type and Domain Home Location

You must specify the domain to be updated with Oracle HTTP Server.

To specify the Domain type and Domain home directory:

1. On the Configuration Type screen, select Update an existing domain.
2. In the Domain Location field, select the Domain home location specified while configuring the Infrastructure domain.

Selecting the Configuration Template for Oracle HTTP Server

Use the Templates screen to select the template you require.

On the Templates screen, make sure Update Domain Using Product Templates is selected, then select one of the following templates:

• For a Full-JRF configuration, select Oracle HTTP Server (Collocated) - 12.2.1.2.0 [ohs].
• For a Restricted-JRF configuration, select Oracle HTTP Server (Restricted JRF) - 12.2.1.2.0 [ohs].

Specifying the Database Configuration Type

Use the Database Configuration type screen to specify details about the database and database schema.

On the Database Configuration type screen, all fields are pre-populated, because you already configured the domain to reference the Fusion Middleware schemas that are required for the Infrastructure domain. Verify and ensure that credentials in all the fields are the same that you have provided while configuring Oracle Fusion Middleware Infrastructure.

Verify the database connection information, then select Get RCU Configuration. The following output in the Connection Result Log indicates that the operation succeeded:

Connecting to the database server...OK

Retrieving schema data from database server...OK

Binding local schema components with retrieved data...OK

Successfully Done.

Specifying JDBC Component Schema Information

Use the JDBC Component Schema screen to verify or specify details about the database schemas.

Verify that the values populated on the JDBC Component Schema screen are correct for all schemas.

• Configuring GridLink Data Sources with Oracle RAC
• Configuring Multi Data Sources

Testing the JDBC Connections

Use the JDBC Component Schema Test screen to test the data source connections.

A green check mark in the Status column indicates a successful test. If you encounter any issues, see the error message in the Connection Result Log section of the screen, fix the problem, then try to test the connection again.

By default, the schema password for each schema component is the password you specified while creating your schemas. If you want different passwords for different schema components, manually edit them in the previous screen (JDBC Component Schema) by entering the password you want in the Schema Password column, against each row. After specifying the passwords, select the check box corresponding to the schemas that you changed the password in and test the connection again.

Selecting Advanced Configuration

Use the Advanced Configuration screen to complete the domain configuration.

On the Advanced Configuration screen, select:

• System Components

Specifying the Oracle HTTP Server Details

Use the OHS Server screen to configure the Oracle HTTP Server instance in the domain.

In the Listen Address field, specify the IP address of the host on which the Oracle HTTP Server instance will reside. Do not use localhost. For more information, see Specifying the Listen Address in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.

All of the remaining fields are pre-populated, but you can change the values as required. For example, verify that the default port numbers are not used by other services.

For more information about this screen, see OHS Server in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard .

Assigning System Components to Machines

Use the Assign System Components to Machines screen to assign Oracle HTTP Server system components to the machine that you defined when you configured the initial Fusion Middleware Infrastructure domain..

On the Assign System Components to Machines screen:

1. In the Machine list box, select the machine (for example, infra_machine_1) to which you want to assign the Oracle HTTP Serverinstance.
2. Assign the Oracle HTTP Server instance to the selected machine in one of the following ways:

·         Double-click ohs_1 in the System Components list box.

·         Select the ohs_1 in the System Components list box and click the right arrow.

Reviewing Your Configuration Specifications and Configuring the Domain

The Configuration Summary screen has detailed configuration information for the domain you are about to extend.

Review each item on the screen and verify that the information is correct. To make any changes, go back to a screen by clicking the Back button or selecting the screen in the navigation pane. Domain update does not start until you click Update.

Writing Down Your Domain Home and Administration Server URL

The End of Configuration screen shows information about the domain you just configured.

Make a note of the following items because you need them later:

• Domain Location
• Administration Server URL

You need the domain location to access scripts that start Node Manager and Administration Server, and you need the URL to access the Administration Server.

Click Finish to dismiss the Configuration Wizard.

Starting the Servers

After configuration is complete, you can use tools to manage your domain.

Follow the instructions in the following sections:

• Starting Node Manager
• Starting the Administration Server
• Starting the Oracle HTTP Server Instance

Starting Node Manager

To start the per-domain Node Manager:

1. Go to the DOMAIN_HOME/bin directory.
2. Start the Node Manager.

·         On UNIX operating systems, using nohup and nm.out as an example output file:

·         nohup ./startNodeManager.sh > LOG_DIR/nm.out&

where LOG_DIR is the location of directory in which you want to store the log files.

·         On Windows operating systems:

·         startNodeManager.cmd

Note:

On Windows operating systems, Oracle recommends that you configure Node Manager to run as a startup service. This allows Node Manager to start up automatically each time the system is restarted.

Starting the Administration Server

To start the Administration Server, go to the DOMAIN_HOME/bin directory.

On UNIX operating systems, run:

./startWebLogic.sh

On Windows operating systems, run:

startWebLogic.cmd

If you selected Production Mode on the Domain Mode and JDK screen when you created the domain, you see a prompt for the Administrator user login credentials as provided on the Administrator Account screen.

You can verify that the Administration Server is up and running by accessing the Administration Server Console. The URL is provided on the Configuration Success screen, as described in “Writing Down Your Domain Home and Administration Server URL” in (http://administration_server_host:administration_server_port/console). The default Administration Server port number is 7001.

Note:

Make sure that the database hosting your product schemas is up and running and accessible by the Administration Server.

4.4.3 Starting the Oracle HTTP Server Instance

To start the Oracle HTTP Server instance:

1. Log in to Oracle Fusion Middleware Control:

2.  http://administration_server_host:administration_server_port/em

The Administration Server host and port number were in the URL on the Configuration Success screen. The default Administration Server port number is 7001.

The login credentials were provided on the Administrator Account screen while installing.

3. Click WebTier in the navigation panel on the left side.
4. Select the Oracle HTTP Server instance you want to start (for example, ohs_1) and click Start Up from the top panel.

UNABLE TO LAUNCH REPORTS BUILDER

UNABLE TO LAUNCH REPORTS BUILDER

After installing and configuring Oracle Forms and Reports 12c, if you try to launch either Reports Builder (rwbuilder.bat) or Reports Converter (rwconverter.bat), both located in %ORACLE_HOME%\bin, you will most likely encounter the following error:

“Windows cannot find ‘\bin\rwbuilder.exe'” or “Windows cannot find ‘\bin\rwconverter.exe'”

The reason for the error is because the values for the DOMAIN_HOME and COMPONENT_NAME need to be filled out in both batch files. You may fix the error by completing these steps:

1.     Go to %ORACLE_HOME%\bin and make backups of both rwbuilder.bat and rwconverter.bat.

2.     Open up rwbuilder.bat in a text editor (Notepad, Wordpad, etc.)

3.     Look for $$domain_home$$ and $$component_name$$. Replace $$domain_home$$ with the full path to your domain home (Example: C:\Oracle\Middleware\user_projects\domains\FormsDomain) and $$component_name$$ with the name of your ReportsToolsComponent (Example: reptools1).

4.     Immediately before the line with “set DOMAIN_HOME=…”, insert the line: set ORACLE_HOME=<PATH_TO_ORACLE_HOME> where <PATH_TO_ORACLE_HOME> is the fully-written path to your Forms 12c Oracle home.

5.     Save and close the file.

6.     Repeat steps 2-5 for rwconverter.bat.

This is how the file looks before the changes are made:

This is how the file should look after the changes are made:

After making the changes above, Reports Builder and Reports Converter should open up normally.