SQL Assistant v3.5.30 serial key or number

Caution:

5.2.1 Deinstallation Restrictions

The following sections describe deinstallation and deconfiguration restrictions. See Section 5.36.2, "Deinstallation Tool Known Bugs" for additional information.

5.2.2 Time Zone File Version

Oracle Database 11g release 2 (11.2) ships with time zone file versions 1 through 11. If your older database is using a time zone file version greater than 11, then you must obtain the corresponding time zone file patch for 11.2 prior to upgrading your database.

You can use to identify the time zone file version when upgrading your Oracle Database 10g or 11g databases. The Pre-Upgrade Information Tool ( and its counterpart used by the Database Upgrade Assistant) provides a warning if the time zone file version is not version 11. The warning recommends running the package to upgrade the database time zone version to the latest and to update data as well. The Pre-Upgrade Information Tool also populates three new database properties (, , and ) in that are pertinent to the time zone version and its upgrade. property records the actual time zone version in use. The other two database properties will be used when you upgrade your time zone version using package.

Note that, in release 11.2.0.1, you have the option to retain your current time zone version after migrating to 11.2. For example, whether your application uses any type, you do not need to run the package to upgrade your time zone version to the latest one available.

5.2.3 Oracle ASM Rolling Upgrade

Oracle Automatic Storage Management (Oracle ASM) rolling upgrade check does not allow rolling upgrade to be done from 11.1.0.6 to any later release (reference Bug 6872001). The following message is reported in the alert log:

is signalled by LMON which will then terminate the instance.

When trying to upgrade Oracle ASM from 11.1.0.6 to a later release of Oracle ASM, apply the patch for this bug to 11.1.0.6 instances before rolling upgrade starts. This patch can be applied to 11.1.0.6 instances in a rolling fashion.

After the patch has been installed, set the user environment variable to . For example:

5.2.4 UTC Time Zone Error When Upgrading From 9.2 to 11.2

When running upgrade scripts from Oracle9i Database release 2 (9.2) to Oracle Database 11g release 2 (11.2), you may encounter the following error:

This error occurs because the default time zone file for release 9.2 does not have the coordinated universal time (UTC) zone. This message is produced by Oracle Scheduler that, by default, selects the UTC time zone and checks it against the default time zone file of release 9.2. This error message is expected and you can ignore it.

5.2.5 Standard Edition Starter Database Upgrade

When the Standard Edition (SE) starter database is upgraded, the following components cannot be upgraded by the SE server because they require options that are not installed in the Standard Edition:

• OLAP Catalog

• OLAP Analytic Workspace

• Oracle OLAP API

• Oracle Spatial

After the upgrade, these components will have a value of in the view, and there will be some invalid objects in the associated component schemas. The Database Upgrade Assistant (DBUA) will show unsuccessful upgrades for these components (reference Bug 8621666).

5.2.6 Tablespace and Fast Recovery Area Sizing

The Oracle Database 11g Pre-Upgrade Information Utility () estimates the additional space that is required in the tablespace and in any tablespaces associated with the components that are in the database (for example, , ) (reference Bug 13067061). For a manual upgrade, be sure to run this utility on your existing database prior to upgrading.

The tablespace size estimates may be too small, especially if Oracle XML DB is installed in your database. However, to avoid potential space problems during either a manual upgrade or an upgrade using the Database Upgrade Assistant (DBUA), you can set one data file for each tablespace to for the duration of the upgrade.

If you are using file systems for data file storage, then be sure there is adequate space in the file systems for tablespace growth during the upgrade.

If you are using a Fast Recovery Area, then check that the size available is sufficient for the redo generated during the upgrade. If the size is inadequate, then an error will be written to the alert log, and the upgrade will stop until additional space is made available.

5.2.7 Setting Memory Target at Instance Startup on Linux

Starting with Oracle Database 11g release 1 (11.1), Oracle provides the option of automatically managing SGA and PGA with a combined parameter without having to set and explicitly. This is supported on Linux, Windows, Solaris, HPUX, and AIX (reference Bug 7258378).

If you see the error reported on Linux machines at Oracle instance startup when using the parameter, then check the size of . If is not configured, then mount it sized to be at least the value of . If is configured but the amount of available space reported (through ) is less than , then free the space or mount a larger to satisfy the size. Note that if you set the parameter greater than , then ensure that is sized to be at least the value of .

5.2.8 Upgrading Databases with Oracle Multimedia, Oracle Spatial, or XDK for Java

Oracle Multimedia (formerly called Oracle interMedia), Oracle Spatial, and Oracle XDK for Java use Oracle XML DB. If any of these components are installed with the database, then Oracle XML DB is automatically installed to support them.

5.2.9 Upgrading a Database With Oracle Warehouse Builder (OWB)

If you are upgrading a database with OWB installed and configured, the OWB component will not be upgraded as part of the database upgrade process and therefore the version of OWB will remain the same after the database upgrade (reference Bug 9473944). The OWB component must be upgraded as a separate step as described in the Oracle Warehouse Builder Installation and Administration Guide.

5.2.10 Compatibility with Oracle9i Database Release 2

Connecting the Oracle Database 11g release 2 (11.2) client or server to Oracle9i Database release (9.2.0.4 and above) is supported. Similarly, connecting Oracle9i client (release 9.2.0.4 and above) to Oracle Database 11g release 2 (11.2) is supported.

5.2.11 Enabling Automated Backups

While installing Oracle Database, the Specify Backup and Recovery Options screen may appear truncated if your system does not have the required fonts installed. If your system has only fixed-width fonts, then you may not be able to fully specify the required information in the Backup Job Credentials area of the screen. To work around this issue, do not select Enable Automated Backups on this screen. After the installation is complete, use Oracle Enterprise Manager 11g Database Control to enable automated backups.

5.2.12 Upgrading a Database With SQL Access Advisor Tasks

Due to internal structural changes to the SQL Access Advisor repository, a database upgrade resets all of the existing SQL Access Advisor tasks to their initial state. This action effectively deletes all of the recommendation information for tasks that have been successfully completed prior to the upgrade.

After upgrading, the recommendation information can be restored by reexecuting the existing SQL Access Advisor tasks.

5.2.13 Downgrade to Release 11.1.0.6

If you anticipate downgrading back to release 11.1.0.6, then apply the patch for Bug 7634119. This action avoids the following error:

Apply this patch prior to running .

5.2.14 Downgrade to Release 10.2.0.4

If you anticipate downgrading back to release 10.2.0.4, then apply the patch for Bug 4309607 to the 10.2.0.4 Oracle home prior to running . This patch is not needed for later 10.2.0.x patch releases. Applying this patch avoids the following error:

5.2.15 Downgrade from 11.2 to 10.2 Results in an Error

Downgrades from 11.2.0.1 to 10.2.0.4 can result in an error (reference BLR 8568714 and Bug 4309607).

To workaround this problem, apply patch 4309607 for 10.2.0.2 to the 10.2.0.2 Oracle home prior to downgrading from 11.2.0.1 to 10.2.0.2.

5.2.16 Rolling Upgrade for Oracle Clusterware

In Oracle Database 11g release 2 (11.2), there is a new prerequisite check during the rolling Oracle Clusterware upgrade cycle. On failure of this prerequisite check, the Oracle Database Upgrade Guide documents the following:

When upgrading Oracle Clusterware from Oracle Clusterware 10g release 2 (10.2) to Oracle Clusterware 11g release 2 (11.2), you must first apply the patchset version 10.2.0.3.0 or later to your existing Oracle Clusterware before it can be upgraded.

Follow the rolling upgrade procedure in Appendix F.5.1 of the Oracle Grid Infrastructure Installation Guide for Linux.

Apart from this proposed solution, there is an alternative. You can upgrade all of the nodes of the cluster simultaneously in a non-rolling manner. Choosing this solution voids the 10.2.0.3.0 patchset requirement.

5.2.17 Reusing the Oracle 9i Database Release 2 Listener Port on Release 11.2

If you reuse the same Oracle 9i Database release 2 (9.2) listener port for the listener while installing Oracle Clusterware release 11.2 on nodes that have Oracle RAC release 9i, then you must ensure that your 9.2 listener is stopped (reference Bug 8688350).

Alternatively, you can stop the 9.2 listener, add for the listener configuration in 9.2 file, and restart the 9.2 listener before continuing with the Oracle Grid Infrastructure for a cluster installation.

5.2.18 Upgrading a Database With Oracle Label Security (OLS)

If you are upgrading a pre-11.2 database with OLS installed and configured, then you need to do one of the following for the upgrade of the database to succeed:

• Run a custom installation of OLS in the 11.2 installation before starting the upgrade of the pre-11.2 database.

• If you do not want OLS in the upgraded database, then deinstall OLS before starting the upgrade.

If you do not run one of the previously mentioned actions, then you will encounter an error () during the upgrade (reference Bug 8707506). In addition, after executing the command, the following error appears:

5.2.19 Upgrading With Objects in the Recycle Bin

The recycle bin must be empty during an upgrade to avoid possible deadlock errors, as well as to minimize the time required to perform the upgrade (reference Bug 8632581).

To avoid this deadlock, use the statement to remove items and their associated objects from the recycle bin and release their storage space prior to upgrading your database.

5.2.20 Upgrading an 11.2 Database Where Oracle JVM Does Not Exist

During a database upgrade to 11.2, if Oracle JVM (which creates the PL/SQL package ) does not exist in the database, then the following error appears (reference Bug 8746395):

This error can be safely ignored and the upgrade will continue.

5.2.21 Diagnosability Framework Errors After Downgrading from Release 11.2 to 11.1

After downgrading from Oracle Database release 11.2 to 11.1, the error may occur in the alert log, or when using the ADR Command Interpreter (ADRCI) utility (reference Bug 6976775). An Alert Log example follows:

The following is an ADRCI example:

As a workaround, perform the following steps:

1. Determine the location of the ADR home:

   SQL> select value from v$diag_info where name = 'ADR Home'; VALUE ---------------------------------------------------------------- /ade/mfallen_g1/oracle/log/diag/rdbms/g1/g1

2. Stop the database instance.

3. Remove the ADR home directory using operating system utilities. (It is automatically re-created with the proper versions when the instance is restarted.)

5.2.22 Response File-Based Installation Issues

Note the following when doing a response file-based installation:

• While saving a response file, if a file with the specified response file name already exists at the destination location and the installation user does not have write permissions to overwrite the file contents, then the Installer does not prompt an error. Instead, the Installer silently fails as if it was successfully saved.

  As a workaround, always save the interview inputs (or response) to a new file. If the selected path already exists, then ensure that the installation user has sufficient privileges to overwrite the contents (reference Bug 8725384).

• The property in the response file does not have a single value that stands for all of the languages. If you need to install the product in all of the languages, then put all of the language codes in a comma-separated list. An example is provided in the sample response file that is shipped with the product (reference Bug 8630967).

• The property in the response file must not be provided with a value of . This value is reserved for Windows operating systems (reference Bug 8631270).

• While saving a response file for client installation in custom mode, a few components, even though they are selected, are not recorded in the saved response file (reference Bug 8722858). Manually enter these components in the response file for these components. For example:

  oracle.network.cman:11.2.0.1.0 -- "Oracle Connection Manager" oracle.network.listener:11.2.0.1.0 -- "Oracle Net Listener"

5.3.1 Edition-Based Redefinition

The following restrictions exist for Oracle Database 11g release 2 (11.2):

• If the clause is omitted when creating an edition, the new edition is created as the child of the database default edition. However, the Oracle Database SQL Language Reference manual specifies that the new edition is created as the child of the one edition that does not have a child (also known as the leaf edition). The Oracle Database SQL Language Reference manual is correct and the present behavior is incorrect (reference Bug 8681882).

• The command succeeds when the owner of the new editioning view is not editions-enabled. However the Oracle Database SQL Language Reference manual specifies that an editioning view must be owned by an editions-enabled user. The Oracle Database SQL Language Reference is correct and the present behavior is incorrect (reference Bug 8583698).

• If an updatable join view is defined on editioning views and the editioning views have triggers defined on them, then DML operations on the updatable join view may fail with various internal errors (reference Bug 8688904).

• DML on editioning views that are defined on tables that have an object type or nested table columns may result in external or internal () errors (reference bug 7697126).

5.3.2 Database Object Names

Oracle does not recommend using quoted identifiers for database object names. These quoted identifiers are accepted by SQL*Plus, but they may not be valid when using other tools that manage database objects.

5.4.1 Direct Insert Behavior Change

Direct insert requires memory for every partition loaded. The memory usage is even greater if the partitions are compressed. In previous releases, a direct insert would continue to allocate memory as rows were encountered for previously untouched partitions until all of the partitions were loaded or until it ran out of memory. In this case, the insert fails.

Starting in Oracle Database 11g release 2 (11.2), direct insert limits the memory that is allocated. If direct insert reaches the limit and it acquires rows for partitions that have not been loaded during the insert, then direct load stores those rows in the temporary tablespace. Once all rows have been passed in, direct load will load the rows it stored in the temporary tablespace.

5.4.2 Audit Default Behavior Changes

Default Audit behavior changes include:

• Audit filename is now prefixed with the instance name and ends with a sequence number. For example:

  instanceName_ora_pid_seqNumber.aud / instanceName_ora_pid_seqNumber.xml

• An existing audit file is never appended to. If an audit file already exists, the sequence number is incremented and written to .

• There is a preconfigured threshold for audit file growth. The audit file associated with an active session remains open until one of the following limits is reached:

  • After the audit record is written, the audit file size becomes 10 megabytes or more.

  • After the audit record is written, the audit file age becomes 5 days or more.

  Once one of these thresholds is reached, a new audit file with an incremented sequence number is opened for further audit records.

• There are no updates to anymore.

  • All logoff (action# 101) audit records are written separately.

  • If an event is audited , then every occurrence of the event becomes a new audit record in .

5.4.3 FILE_ACCESS_ROLE Default Behavior Change

The default behavior of the CTX system parameter has changed (reference Bug 8360111). Customers with existing Oracle Text indexes that use the file or URL datastore must take action to continue to use the indexes without error. The changes are as follows:

• If is null (the default), then access is not allowed. By default, users who were previously able to create indexes of this type will not be able to create these indexes after the change.

• is now checked for index synchronization and document service operations. By default, users will not be able to synchronize indexes of this type or use document service calls such as who were allowed to prior to this change.

• Only SYS will be allowed to modify . Calling as a user other than SYS will now raise the new error:

  DRG-10764: only SYS can modify FILE_ACCESS_ROLE

• Users can set to to explicitly disable this check (which was the previous default behavior).

5.4.4 Support for Raw Devices

Oracle Universal Installer (OUI) and Database Configuration Assistant (DBCA) do not support raw devices (or block devices on Linux). However, command-line utilities such as SQL*Plus and CRSCTL do support raw or block devices.

5.4.5 Oracle Clusterware and Oracle ASM Installed Into Oracle Grid Infrastructure for a Cluster Home

Oracle Clusterware and Oracle Automatic Storage Management (Oracle ASM) are installed into a single Oracle home called the Grid home. This installation is referred to as the Oracle Grid Infrastructure for a cluster installation.

When upgrading, you must upgrade both Oracle Clusterware and Oracle ASM at the same time.

5.4.6 Deprecated Parameters in the Oracle ASM Instance

The following initialization parameters are deprecated in the Oracle ASM instance:

• parameter

  If the is Oracle ASM and the Oracle RAC option is turned on, then you do not have to specify the parameter. In this case, the parameter defaults to .

• parameter

  Do not set the parameter in an Oracle ASM instance. To advance the disk group compatibility, change the
  attributes of the disk group.

5.4.7 Fixed Views

All parameter views (for example, ) in the Oracle ASM instance only report parameters that are relevant to the Oracle ASM instance.

5.4.8 Offset for CLOB and NCLOB APIs

Starting with Oracle Database 10g release 1 (10.1), APIs that write to a or cause error when the offset specified for the beginning of the write is not on a character boundary of the existing data.

APIs use UCS2 codepoint semantics for the amount and offset parameters on or when the database default or national character set is multibyte. The specified offset is not on a character boundary if it points to the low (second) surrogate of a surrogate pair. In such situations, error occurs and the data is not written. Thus, this prevents the corruption of the character in the target .

Contact Oracle Support Services to configure the database so that it does not return .

5.4.9 Use of the Append Hint Runs Out of Memory When Loading Many Partitions

Use of direct-path to load a large number of partitions can exceed memory limits, especially when data compression is specified (reference Bug 6749894). Starting in 11.2, the number of partitions loaded at the same time will be limited, based on the initialization parameter, to preserve memory. Rows that are not stored in the partitions that are currently being loaded are saved in the temporary tablespace. After all rows are loaded for the current set of partitions, other partitions are loaded from rows that are saved in the temporary tablespace.

This behavior helps prevent the direct-path from terminating because of insufficient memory.

5.4.10 Non-Uniform Memory Access Optimizations and Support Disabled in 11.2

With Oracle Database 11g release 2 (11.2), non-uniform memory access support is disabled by default. This restriction applies to all platforms and operating systems (reference Bug 8450932).

Non-uniform memory access optimizations and support in the Oracle Database are only available for specific combinations of Oracle version, operating systems, and platforms. Work with Oracle Support Services and your hardware vendor to enable non-uniform memory access support.

5.4.11 View Changes for Advanced Compression

The column in various table views, such as and , returns different values in 11.2 as compared to 11.1. The new values returned from a column are or . In 11.1, the value was and , respectively.

5.5.1 Oracle Database Data Files and Oracle ACFS

Oracle ACFS is the preferred file manager for non-database files. It is optimized for general purpose files. Oracle ACFS does not support any file that can be directly stored in Oracle ASM.

5.6.1 Reorganize Objects

The following applies to Reorganize Objects:

• The database can be adversely affected if metadata changes occur between the time the reorganization script is generated and the time it is completed.

• The database can be adversely affected if an offline reorganization is attempted while DDL is in progress against the tables being reorganized.

• Before using the Reorganize Objects wizard or the Make Tablespace Locally Managed wizard in Oracle Enterprise Manager, Oracle recommends that you back up your database.

5.6.2 Editing Multiple Objects

Oracle Enterprise Manager only supports having one browser window open for editing an object. For example, Oracle Enterprise Manager only supports editing one tablespace at a time.

5.6.3 Requirements for Proxy Settings for Oracle XML DB

The following are requirements for Oracle XML DB proxy settings:

• For an Oracle XML DB Resource to be created using a URL behind the firewall, the proxy in needs to be set.

• When registering an XML Schema based on a URL, the URL is interpreted by the database itself, in which case, the database proxy might need to be set.

5.6.4 Large Number of Database Objects May Require Increase in Heap Size

Oracle Enterprise Manager Database Control is configured with 192 MB (32-Bit)/384 MB (64-Bit) of heap memory. However, certain Oracle Enterprise Manager Database Control functionality (for example, Change Manager) may require higher memory settings if the database contains a large number of objects.

Memory settings can be increased using the following command:

Oracle Enterprise Manager Database Control must be restarted for the new settings to take effect.

5.6.5 New Oracle Database 11g Release 2 Features Supported by Oracle Enterprise Manager Database Control 11.2 Only

Management support for new features available with Oracle Database 11g release 2 (11.2.0.1), such as policy-managed databases and Oracle ASM Cluster File System, is available in Oracle Enterprise Manager Database Control 11.2 only.

Oracle Database 11g release 2 (11.2.0.1) features are supported in Oracle Enterprise Manager Grid Control 11.1.

Oracle Enterprise Manager Grid Control 10.2.0.5, which provides management support for previous Oracle Database versions, does not support new Oracle Database 11g release 2 (11.2) features. Single-instance database provisioning is also not supported by Grid Control 10.2.0.5.

Note that administrator-managed clustered databases that are upgraded to Oracle Database 11g release 2 (11.2) can continue to be monitored using Grid Control 10.2.0.5. For more information on Oracle Database 11g release 2 (11.2) monitoring support, click the Certify tab on the My Oracle Support web site (at ).

5.6.6 Database Control Patching

The following items apply to database patching procedures.

5.7.1 Configure and Use SSL Certificates to Setup Authentication

JDBC or Oracle Universal Connection Pool's (UCP) Oracle RAC features like Fast Connection Failover (FCF) subscribe to notifications from the Oracle Notification Service (ONS) running on the Oracle RAC nodes. The connections between the ONS server in the database tier and the notification client in the mid-tier are usually not authenticated. It is possible to configure and use SSL certificates to setup the authentication but the steps are not clearly documented.

The workaround is as follows:

1. Create an Oracle Wallet to store the SSL certificate using the interface:

   3. When prompted, provide as the password.

   6. Copy the wallet created in Step c to all other cluster nodes at the same location.

2. Stop the ONS server on all nodes in the cluster:

   srvctl stop nodeapps

3. Update the ONS configuration file on all nodes in the database tier to specify the location of the wallet created in Step 1:

   1. Open the file

   2. Add the parameter to the file:

   3. Restart the ONS servers with the :

      srvctl start nodeapps

4. If you are running a client-side ONS daemon on the mid-tier, there are two possible configurations:

   • ONS started from OPMN (like in OracleAS 10.1.3.x) which uses for its configuration.

   • ONS started standalone (like using ), which uses for its configuration.

   For case (1), refer to the OPMN Administrator's Guide for the Oracle Application Server release. This involves modifying the file to specify the wallet location.

   For case (2), refer to the section titled Configuration of ONS in Appendix B of the Oracle Database JDBC Developer's Guide. The client-side ONS daemon can potentially run of different machines. Copy the wallet created in Step 1 to those client-side machines and specify the path on that client-side machine in the file or in the file.

5. If you are running remote ONS configuration without a client-side ONS daemon, refer to the "Remote ONS Subscription" subsection of the "Configuring ONS for Fast Connection Failover" subsection of the "Using Fast Connection Failover" section of the "Fast Connection Failover" chapter in the Oracle Database JDBC Developer's Guide. Copy the wallet created in Step 1 to those client-side machines and specify the path on that client-side machine in the file or in the file.

   Alternatively, you can specify the following string as the argument:

   propertiesfile=location_of_a_Java_properties_file

   The Java properties file should contain one or more of the ONS Java properties listed below, but at least the property. The values for these Java properties would be similar to those specified in the "Remote ONS Subscription" subsection previously noted in this step:

   oracle.ons.nodes oracle.ons.walletfile oracle.ons.walletpassword

5.7.2 Changes in Default Security Settings

Java package is deprecated. Classes , , , and are part of this package (reference Bug 6736417).

5.7.3 UNLIMITED TABLESPACE Privilege Changes

The system privilege will be removed from the role in a future Oracle Database release (reference Bug 7614645).

5.8.1 Encrypted Tablespaces

• You cannot encrypt an existing tablespace with an statement. However, you can use Data Pump or SQL statements such as or to move existing table data into an encrypted tablespace.

• When recovering a database with encrypted tablespaces (for example, after a or a catastrophic error that brings down the database instance), you must open the wallet after database mount and before database open so the recovery process can decrypt data blocks and redo.

• The master encryption key for Transparent Data Encryption (TDE) tablespace encryption can leverage Hardware Security Modules (HSM) for full key management (for example, create, store, rotate, and retire). In 11.1.0.7, it was only possible to create and store the TDE tablespace encryption master key in HSM, not rotate. Master key for the TDE tablespace encryption can also be migrated from Oracle Wallet to HSM.

5.9.1 Oracle JVM

Oracle Database 11g Release 2 (11.2) includes a fully functional Java Virtual Machine (JVM), as well as the Java class libraries for Sun's Java Development Kit (JDK) 5.0. When combined with Oracle's JDBC and SQLJ, release 11.2.0.1 provides an enterprise class platform, Oracle JVM, for developing and deploying server-based Java applications. Refer to the Oracle JVM Readme file located at:

5.9.2 Announcing Oracle Universal Connection Pool (UCP) and Deprecation of JDBC Implicit Connection Cache in Favor of UCP

Starting with Oracle Database 11g release 1 (11.1.0.7), Oracle has released the new Universal Connection Pool for JDBC. For more details, see the Oracle Universal Connection Pool for JDBC Developer's Guide at the following Web page:

Consequently, Oracle is deprecating the existing JDBC connection pool (that is, Implicit Connection Cache) that was introduced in Oracle Database 10g release 1 (10.1). Your applications will continue to work until formal desupport in a future release at which time a desupport notice will be posted.

Oracle encourages you to plan to adopt UCP for new applications and plan to change existing applications as indicated in Transitioning to Oracle Universal Connection Pool (UCP) at the following Web page:

UCP download and code samples are located at the following Web page:

5.9.3 JDBC

The Oracle JDBC product supports the latest Java/JDBC standards. For more details, refer to the JDBC Readme file located at:

5.9.4 Web Services

As an alternative to Oracle Net, Oracle Database Web services provides nonconnected access to the database through standard Web services mechanisms. These include XML, SOAP, and WSDL, and can turn the database into a Web services provider. Similarly, the database itself can act as a Web service consumer and run external Web services. Important features of Web services include:

• A JAX-RPC based SOAP Client library supports invocation of external Web services from within the database, and applies the power of SQL to the results.

• Web Services Call-In: Deploying a JPublisher-generated Java class against Oracle Application Server 10g enables you to run database operations such as Java and PL/SQL procedures and packages, SQL queries, and DML operations.

• Web Services Call-Out: Deploying a JPublisher-generated Web services client from a WSDL and its PL/SQL wrapper supports invocation of external Web services from within the database.

5.10.1 Globalization Restrictions Within Oracle Secure Backup

The following globalization restrictions apply to Oracle Secure Backup:

• The Oracle Secure Backup Web Tool and command line interface are available in English only, and are not globalized. All messages and documentation are in English.

• Oracle Secure Backup does not support file names or RMAN backup names that are encoded in character sets that do not support null byte termination, such as Unicode UTF-16. Note that this restriction affects file names, not backup contents. Oracle Secure Backup can back up Oracle databases in any character set.

5.11.2 Configuring Oracle HTTP Server

When configuring Oracle HTTP Server for Oracle Application Express in a new installation, the database user must be an unlocked account. To unlock the account for database user , complete the following:

1. Start SQL*Plus and connect as to the database where Oracle Application Express is installed. For example:

   $ ORACLE_HOME/bin/sqlplus SQL> CONNECT SYS as SYSDBA Enter password: SYS_password

2. Run the following command:

   SQL> ALTER USER APEX_PUBLIC_USER ACCOUNT UNLOCK

5.11.3 Database Compatible Parameter and Enabling Network Services

To run the examples in the Oracle Application Express Post-Installation tasks in the section titled "Enabling Network Services in Oracle Database 11g" in the Oracle Database Installation Guide, the initialization parameter of the database must be set to at least 11.1.0.0.0. By default, an Oracle Database 11g database will already have the parameter set properly, but a database upgraded to 11g from a prior version may not.

Refer to the section titled "Creating and Configuring an Oracle Database" in the Oracle Database Administrator's Guide for information about changing database initialization parameters.

5.13.1 cron Configuration Issue

If you are denied access to , then the configuration of Oracle Configuration Manager fails with the following error:

After the installation is complete, set the environment variable to and try the configuration of Oracle Configuration Manager again using the following command:

5.15.1 Using the Oracle Internet Directory Configuration Assistant

The Oracle Internet Directory Configuration Assistant (OIDCA) enables you to create, upgrade, and delete an Oracle Context, configure the file , and convert an Oracle Context to an Identity Management Realm.

The OIDCA syntax is:

To see the usage of OIDCA, enter at the command prompt.

5.15.2 Creating an Oracle Context

The following syntax is used to create an Oracle Context in OIDCA; the parameters are described in the subsequent table.

Note the following points:

• The must exist for this operation to be successful.

• This valid DN should not exist in OID: .

• This valid DN must exist in OID: .

• The parameters and can also be passed as a properties file.

• Specify the parameter if you want to perform the operation using non-SSL mode.

• Specify the parameter if you want to perform the operation using SSL mode.

• Either the or the parameter must be specified, but not both.

Functionality

1. The OIDCA verifies that has a valid DN syntax and that the entry exists in Oracle Internet Directory. Note that the OIDCA cannot create a root explicitly. If there is no root Oracle Context, then OIDCA exits with an error.

2. If DN exists, then OIDCA verifies that the Oracle Context already exists.

   • If the Oracle Context already exists and is up-to-date, then OIDCA exits with the message .

   • If the Oracle Context already exists, but it is an older version, then OIDCA exits with the message .

   • If the Oracle Context does not exist, then OIDCA creates the Oracle Context under this DN.

5.15.3 Upgrading an Oracle Context

To upgrade an instance, use the following syntax; the parameters are listed in the subsequent table.

Note the following points:

• The must contain an for this operation to be successful.

• The DNs , and are both valid.

• The parameters and can also be passed as a properties file.

• Specify the parameter if you want to perform the operation using a non-SSL mode.

• Specify the parameter if you want to perform the operation using SSL mode.

• Either the or the parameter must be specified, but not both.

Functionality

1. OIDCA verifies that the has valid DN syntax and that exists in Oracle Internet Directory. OIDCA cannot upgrade a root explicitly. If there is no root , then OIDCA sends an error message.

2. If exists under ,

   • The OIDCA checks if the belongs to a realm, in which case it exits with the appropriate message. Note that instances that belong to a realm cannot be upgraded.

   • The OIDCA verifies that the is up-to-date, then exits with the message .

   • If the is not up-to-date, then the OIDCA upgrades the under this DN.

5.15.4 Deleting an Oracle Context

To delete an , use the following syntax; the parameters are listed in the subsequent table.

Note the following points:

• The must contain an for this operation to be successful.

• The DNs and are both valid.

• The parameters and can also be passed as a properties file.

• Specify the parameter if you want to perform the operation using a non-SSL mode.

• Specify the parameter if you want to perform the operation using SSL mode.

• Either the or the parameter must be specified, but not both.

Functionality

1. OIDCA verifies that the has valid DN syntax and that exists in Oracle Internet Directory.

2. If exists under ,

   • The OIDCA checks if the belongs to a realm, in which case it exits with the appropriate message. Note that instances that belong to a realm cannot be deleted.

   • If does not belong to a realm, then OIDCA deletes it.

5.15.5 Configuring the File ldap.ora

To configure the file , use the following syntax; the parameters are listed in the subsequent table.

Note the following points:

• Either the non-SSL or the SSL port must be specified. The other port is discovered.

• The parameters , , and can also be passed in within a properties file.

Functionality

1. Using the Discovery API, the OIDCA determines all the parameters not specified on the command line.

2. The OIDCA checks for the location using Discovery APIs.

   • If exists and the parameter is not specified, then exit with message .

   • If exists and the parameter is not specified, then update the existing using Discovery API.

   • If does not exist, then create a new file in a location in the following order:

     LDAP_ADMIN ORACLE_HOME/ldap/admin

5.15.6 Converting an Oracle Context to an Identity Management Realm

Oracle Database 10g entries must be stored in Oracle Internet Directory release 9.0.4 server. An Identity Management Realm release 9.0.4 is also required for Enterprise User Security, a feature of the Oracle Database 10g.

To convert an existing to an Identity Management Realm, use the following syntax. The parameters are listed in the subsequent table. Note that the root of the object is not converted.

Note the following points:

• The must exist under the specified .

• The DNs , and are both valid.

• The parameters and can also be passed in a properties file.

• Specify the parameter if you want to perform the operation using a non-SSL mode.

• Specify the parameter if you want to perform the operation using SSL mode.

• Either the or the parameter must be specified, but not both.

Functionality

1. The OIDCA checks if has valid DN syntax, and if it contains a valid .

2. If exists under

   • The OIDCA checks if the belongs to a realm. If it does, then it exits with an appropriate error message.

   • If does not belong to a realm, then OIDCA upgrades it to the latest version, and converts it to a realm.

Note also:

• If the nickname attribute is not , then configure it as a user configuration attribute using the Oracle Internet Directory Self-Service Console.

• If you want to use the Oracle Internet Directory Self-Service Console to manage the users and groups in the converted realm, then you must set up the administrative privileges appropriately. For details, refer to the Oracle Fusion Middleware Administrator's Guide for Oracle Internet Directory.

5.18.1 Moving ORADISM to Local Nodes from NFS on an Oracle Home

32-bit Oracle client on a 32-bit OS
64-bit Oracle client on a 64-bit OS

Memory: 2-4 GB of RAM. Probe OOB configuration requires 256 MB of RAM.
CPU: 3 GHz dual-core processor, 32-bit or 64-bit.

CA Unified Infrastructure Management 8.1 or later
Robot 7.62 or later (recommended)
Probe Provisioning Manager (PPM) probe version 2.39 or later (required for Admin Console)
The ppm version 3.30 is required to enable the new fields of the oracle probe version 5.0.
Java JRE 6 or later (required for Admin Console)
The probe requires the following additional probes:
ci_defn_pack 1.26 or later (required to view data on Unified Management Portal (UMP))
mps_language_pack 8.46 or later (required to view correct metric type on Admin Console)
Restart after you deploy the .
Windows: Oracle Client (Net Services) 11.x or 12.x
Linux and Solaris: Oracle Client 11.x or 12.x

Role-based login is also supported, for example, sys as sysdba
From NMS 7.5, RAC is supported but can only be configured from Admin Console.
Ensure that the Probe Provisioning Manager (ppm) 3.47 or later is available for AES encryption from the Administration Console.

When upgrading the probe to version 4.80 or later, the PDB_Count checkpoint is added as a template and is available in all the profiles. By default, the checkpoint is disabled. Enable the checkpoint to monitor the number of PDBs in a particular CDB. This checkpoint will work only for those profiles that are linked to a CDB connection. For other profiles, no result is displayed even if the checkpoint is enabled.
When upgrading the probe, any deleted default configurations, thresholds, or QoS are added back in the probe.

The probe does not support alarms for and
asm_disk_group_total_space
checkpoints.
For the resource_util checkpoint (with two default QoS), the probe creates a node on USM and displays one QoS data under it. The second QoS data displays under node.
(Applicable from version 5.01)
Create a key with value in the Raw Configure interface > section. When you enable this key, the probe displays both the default QoS data under node. If you do not define this key, or set it as , the probe displays the checkpoint data under two separate nodes.
Setting the key as changes the metric ID of the QoS and the USM view for the metric in the existing profiles. CA recommends you to clear the database before you enable the key.
A memory leak is observed when the probe connects to the Oracle 12c client or the server. This is a known issue with the Oracle 12 databases.
The probe may not connect to the database after you install or upgrade the Oracle client. Restart the probe after installing the client for a successful connection.
The oracle probe must not be configured on both the Infrastructure Manager (IM) GUI and Admin Console (AC) GUI.
The probe configuration for both the IM GUI and AC GUI is separate. For example, any profile that is created in the IM GUI is neither available on the AC GUI nor can be migrated. It must be created again.
While upgrading the oracle probe from version 4.56 and earlier to version 4.60 or later, ensure that the PPM, service_host, and MPSE are restarted for the RAC functionality to become usable.
The users cannot create custom alarm messages. Hence, they need to select an existing alarm message.
In Oracle RAC, from Oracle 11.1 and above, the term is replaced by in all checkpoints. Therefore, if any custom query in Oracle 11g or 12c includes the term , then no value is returned. The RAC functionality is supported and configured through Admin Console GUI only.
On Windows 64-bit platform, the probe cannot be installed into the default directory - "Program Files (x86)". A bug in Oracle Client is causing connection errors, if the application home directory name includes special characters, like "(" (Oracle Bug 3807408).
Error ORA-12705 together with log entry "OCIEnvCreate failed with rc = -1" can happen, if environmental variable NLS_LANG is set. Solution is to set this variable to empty space in the controller environment.
On 64-bit Linux, user may get a warning message of insufficient access rights when connection test is performed, even if all the required access rights are provided. The connection can still be used to schedule the profile. Ensure all the required access rights are provided to the user.
In custom checkpoints, if query tries to fetch data from a table with more than 32 columns, probe will limit the number of columns to 32.
If a custom QoS is added to an existing monitoring profile, the Unified Management Portal (UMP) creates a separate node, Custom, in the Metric section. It does not display the user-defined description and unit.
If a custom checkpoint is added to an existing monitoring profile, the UMP creates a separate node, Dynamic, in the Metric section. It does not display the user-defined description and unit.

The probe does not support alarms for and
asm_disk_group_total_space
checkpoints. A user can add thresholds for these checkpoints, however they are not saved.
The probe does not support renaming connections and profiles.
On version 4.90 of the probe, custom QoS in a checkpoint do not generate alarms if the default QoS of the checkpoint is deleted. This is applicable for AIX 6 and AIX 7 platforms.
While upgrading the oracle probe from version 4.56 and earlier to version 4.60 or later, ensure that the PPM, service_host, and MPSE are restarted for the RAC functionality to become usable.
The users cannot create custom alarm messages. Hence, they need to select an existing alarm message.
The oracle probe must not be configured on both the IM GUI and AC GUI.
The probe configuration for both the IM GUI and AC GUI is separate. For example, any profile that is created in the IM GUI is not available on the AC GUI and must be recreated.
Dynamic Population of Message Text
field with the corresponding field selected in the drop-down list at runtime is a limitation of the PPM. On creating a checkpoint with a new threshold, first select message and save it. After the reload operation, the message text field gets updated with the corresponding message text.
If you see PPM-023 error and
Unable to Retrieve Configuration
issues, click or reopen the AC GUI.
In Oracle RAC, from Oracle 11.1 onwards, the term is replaced by in all checkpoints. Therefore, if any custom query in Oracle 11g or 12c includes the term , then no value is returned.
To discover RAC-specific nodes, the ppm probe should be deployed on the same subnet as the oracle probe.
On Windows 64-bit platform, the probe cannot be installed into the default directory - "Program Files (x86)". A bug in Oracle Client is causing connection errors, if the application home directory name includes special characters, like "(" (Oracle Bug 3807408).
Error ORA-12705 together with log entry "OCIEnvCreate failed with rc = -1" can happen, if environmental variable NLS_LANG is set. Solution is to set this variable to empty space in the controller environment.
On 64-bit Linux, user may get a warning message of insufficient access rights when connection test is performed, even if all the required access rights are provided. The connection can still be used to schedule the profile. Ensure all the required access rights are provided to the user.
If the oracle probe is deployed on a non-Windows OS, the UMP displays the metrics and alarms on the robot and not on the Oracle server.
In custom checkpoints, if your query tries to fetch data from a table with more than 32 columns, the probe limits the number of columns to 32.
If a custom QoS is added to an existing monitoring profile, the UMP creates a separate node, Custom, in the Metric section. It does not display the user-defined description and unit.
If a custom checkpoint is added to an existing monitoring profile, the UMP creates a separate node, Dynamic, in the Metric section. It does not display the user-defined description and unit.
If a checkpoint has multiple QoS and you activate or deactivate one QoS, the other QoS of the checkpoint are also activated or deactivated.
If a checkpoint has multiple alarms and you activate or deactivate one alarm, the other alarms of the checkpoint are also activated or deactivated.
If you enable a checkpoint in the node, the checkpoint is enabled for all the monitoring profiles and all alarms are generated.
In custom checkpoints, if you edit a message variable, it adds a new message variable in the Message Variable table. To edit a message variable in custom checkpoint, delete and create a new message variable.
The probe generates alarms for a threshold of an active checkpoint even if you clear the field of the checkpoint.
If you change any default checkpoint in the Template, the changes are available in the new profiles only. Existing profiles are not impacted with these changes.

Deactivate the oracle probe.
Delete the alarms.cfg file located in the
CA UIM Installation Directory
> probes > Database > oracle folder.
Upgrade the probe to version 5.20 or later.
Navigate to your robot and open the probe Raw Configure interface.
Do not activate your probe now.
Navigate to the section, and set the key to 1. When you enable this key, the CI name is appended with “
##<Database Instance Name>
.” If there is no database name mentioned in the CI for a profile checkpoint, the probe adds the master database name in the defined format. Default: 0
Clear the folder of all the robots in your environment that have the oracle probe. The folder is located in the
CA UIM Installation Directory
.
Acknowledge all alarms from the probe.
Run the following queries on your UIM database to delete the QoS data from the probe:
delete from s_qos_data where probe = 'oracle'
delete from s_qos_definition where qos_group = 'QOS_ORACLE'
delete from nas_alarms where prid = 'oracle'
delete from cm_configuration_item_metric where ci_metric_type like '4.1%'
delete from cm_configuration_item where ci_type like '4.1%'
Restart the , , , , and probes.
Activate the oracle probe.