Oracle Database 1. Release 2 (1. 1. 2. New Features. This chapter contains descriptions of all of the features that are new to Oracle Database 1. Release 2 (1. 1. 2. The following sections describe the new features for Oracle Database 1. Release 2 (1. 1. 2.

Support Hybrid Columnar Compression on Pillar Axiom and Sun ZFSSAOracle's Hybrid Columnar Compression (HCC) technology is a new (to Oracle Database 1. Release 2) method for organizing data within a database block. HCC utilizes a combination of both row and columnar methods for storing data. A logical construct called the compression unit is used to store a set of HCC- compressed rows.

1. 2 Connecting to Oracle Database and Exploring It. Example 2-6 Preserving Case and. CITY Old Code New Code.
2. QoS Management responds by automatically preventing new connections thus preserving existing.
3. Copying filesystems preserving files' metadata.

I took the "job," not realizing all they wanted was someone to install servers. I remember I had one old HP-UX box which had a. Unix -Vendor Service Contact Details. AIX Install packages, upgrade, patching commands;.

When data is loaded, groups of rows are stored in columnar format, with the values for a given column stored and compressed together. After the column data for a set of rows has been compressed, it is fit into the compression unit.

Storing column data together, with the same data type and similar characteristics, dramatically increases the storage savings achieved from compression. This feature extends Hybrid Columnar Compression to Pillar Axiom and Sun ZFS Storage Appliance (ZFSSA) storage. The support of Hybrid Columnar Compression on Pillar and ZFSSA enables Oracle Database users to utilize Oracle's Hybrid Columnar Compression on Pillar Axiom and Sun ZFS Storage Appliance (ZFSSA) storage hardware. This provides the storage benefits of Oracle's Hybrid Columnar Compression, which had previously been exclusive to the Oracle Exadata platform, to Oracle Database users who use Pillar Axiom or Sun ZFSSA storage (or both), enabling compression ratios of 1.

Support for SHA- 2 Certificate Signatures. With this new feature, the database can handle SHA- 2 (2. SHA- 1 signed certificates. These certificates are issued by a separate certificate authority and are exchanged between the database and a client when a secure database connection is being established (for example, where certificate- based network encryption and authentication are being used).

This enhancement is particularly critical for customers who are facing deadlines for when their certificate authorities will stop issuing older SHA- 1 signed certificates. TDE Hardware Acceleration for Solaris.

Transparent Data Encryption (TDE) can automatically detect whether the database host machine includes specialized cryptographic silicon that accelerates the encryption or decryption processing. How To Install Faux Brick Backsplash. When detected, TDE uses the specialized silicon for cryptographic processing accelerating the overall cryptographic performance significantly. In prior releases, cryptographic hardware acceleration for TDE was only available on Intel Xeon, and only for Linux. With release 1. 1.

Solaris 1. 1 running on both SPARC T- Series and Intel Xeon. Support for Multiple Certificates on Smart Card. Consider the scenario, a database user inserts a card containing one or more digital certificates into a card reader device and manually enters a corresponding personal identification number (PIN). Oracle has supported card- based authentication to the database and, starting with release 1. The database attempts to intelligently select which certificate to read and, if it cannot figure out which one to read, a selection box pops up on the Windows client machine. This is an important enhancement for customers who use card- based, two- factor authentication to log in to Oracle Database.

In August 2. 00. 4, the Homeland Security Presidential Directive Number 1. HSPD- 1. 2) was issued to unify the government's identification badge systems. The new guidelines are dictating the deployment of Common Access Cards (CAC) that contain digital certificates.

Qo. S Management Support for Oracle RAC Enterprise Edition. Oracle Database Quality of Service (Qo. S) Management allows system administrators to directly measure application service levels hosted on Oracle RAC Enterprise Edition databases.

Using a policy- based architecture, Qo. S Management correlates accurate run- time performance and resource metrics based on user- defined workload classes. Qo. S Management then presents them in an integrated Enterprise Manager dashboard to review real- time performance of consolidated applications.

In conjunction with Cluster Health Monitor (CHM), Qo. S Management's memory guard detects nodes that are at risk of failure due to the over commitment of memory. Qo. S Management responds by automatically preventing new connections thus preserving existing workloads and restores connectivity once sufficient memory is available again. The benefits of this feature aids in the schema and database consolidation of applications within Oracle Real Application Clusters yielding information technology efficiency and cost savings. This feature also actively protects application availability under high memory conditions with memory guard. Qo. S Management Support for Instance Caging on Oracle Exadata. Oracle Database Quality of Service (Qo.

S) Management allows system administrators to directly measure application service levels hosted on Oracle RAC Enterprise Edition databases. Using a policy- based architecture, Qo. S Management correlates accurate run- time performance and resource metrics based on user- defined workload classes, analyzes this data with its expert system to identify bottlenecks, and produces recommended resource adjustments to meet and maintain performance objectives under dynamic load conditions. Qo. S Management then presents the findings in an integrated Enterprise Manager dashboard to review real- time performance of consolidated applications. Along with moving the server between server pools, Qo.

S Management now also supports moving CPUs between databases within the same pool to better manage performance in consolidated Oracle Exadata deployments. This new support manages service- level agreements (SLA) for Online Transaction Processing (OLTP) database applications consolidated on Oracle Exadata yielding information technology efficiency and cost savings.

Oracle ACFS Snapshot Enhancements. The read/write snapshot feature for Oracle Automatic Storage Management Cluster File System (Oracle ACFS) adds support for fast creation of an Oracle ACFS snapshot image that can be both read and written without impacting the state of the Oracle ACFS primary file system hosting the snapshot images. With this enhancement, you can test new versions of application software on production file data reflected in the read/write snapshot image without modifying the original production file system. You can also run what- if scenarios on a real data set without modifying the original file system. Oracle ACFS Security and Encryption Features. The Oracle Automatic Storage Management Cluster File System (Oracle ACFS) security feature provides realm- based security for Oracle ACFS. The Oracle ACFS encryption feature enables data stored on disk (data- at- rest) to be encrypted.

Oracle ACFS security feature provides the ability to create realms to specify security policies for users or groups for accessing file system objects. The Oracle ACFS security feature provides finer- grained access control on top of the access control provided by the operating system. Oracle ACFS encryption feature provides the ability to keep data in an Oracle ACFS file system in encrypted format to prevent unauthorized use of data in the case of data loss or theft. Support for ACFS Replication and Tagging on Windows. Support for replication and tagging functionality is now available on the Windows platform. Oracle Automatic Storage Management Cluster File System (Oracle ACFS) replication enables replication of Oracle ACFS file systems across the network to a remote site, providing disaster recovery capability for the file system.

Oracle ACFS tagging assigns a common naming attribute to a group of files. Oracle ACFS replication can use this tag to select files with a unique tag name for replication to a different remote cluster site. The tagging option avoids having to replicate an entire Oracle ACFS file system.

Set up a cluster on AIXWhen you install onto a 6. Web. Sphere Portal installs as a 6. We can force a 3. Then use a response file to install IBM Web.

Sphere Portal and IBM WAS in a clustered environment. Record response files on the same OS you plan for the installation.

For multiple operating systems, record a response file for each operating system. We can force a 3. Also replace the following lines in the sample response files if you installed WAS and Web.

Sphere Portal from the live repository (Passport Advantage). This step does not install Web. Sphere Portal. You are only recording the response file used to install portal later. The user and group names must comply with both the database management system software requirements and Web. Sphere Portal requirements. When created the DB2 databases remotely, you can only create the databases manually.

Create the databases manually. If 5. 00. 00 is already is use, select a different port number.

The limitations on user names are. User names can contain one to eight characters. Names cannot begin with: IBM SQL SYS. Names cannot include accented characters. We can create a copy of the SQL scripts and edit this copy to manually grant permissions to configuration and runtime database users. These read- only templates should not be modified and contain invalid SQL syntax. Create our own version of these files to create runnable scripts.

To grant minimum privileges to a runtime database user to work with these tables, access needs to be provided for the objects individually. These roles are created and assigned automatically when you run.. Before you run these configuration tasks, the runtime database user can only access the database to validate configurations. As an alternative to creating and assigning this role automatically, you can create a copy of the SQL scripts templates located in the installation directory of IBM Web. Sphere Portal to use as a guide for creating executable scripts for manually granting permissions. These read- only templates should not be modified and contain invalid SQL syntax.

Create our own version of these files to create runnable scripts. When using an existing set of table spaces for the objects of the repository, specify this when executing the database transfer to the target database system. The default table spaces can be used to contain database objects; however the name of the default table space must be specified in the corresponding mapping files. This applies to all database domains that are transferred in a single database transfer.

We can update the fully. Materialize. Lob. Data property by running a configuration task.

For example.. We can then remove them when you are finished to keep the environment secure. Separate multiple files with a colon (: ); for example, enter.. The /path/to/db/jars should be one of the following options.

DB2 Type 2 driver db. DB2 Type 4 driver. A dynamic cluster monitors performance and load information and is able to dynamically create and remove cluster members based on the workload. On the Web. Sphere Portal primary node, install Web. Sphere Virtual Enterprise, apply all required ifixes, and augment the wp. When using the GUI, select.. Use manageprofiles.

Complete the following steps for on the primary node of the dynamic cluster. Run.. If the admin user ID and group name are different in the Web. Sphere Portal and dmgr configurations, choose one of the following options depending on your security policies. Add the existing admin user ID and group to the dmgr security configuration. To change the values in the Web. Sphere Portal configuration to match the dmgr values. If the dmgr cell is using a stand- alone LDAP user registry, complete these steps after the cluster- node- config- cluster- setup (static cluster) or cluster- node- config- dynamic- cluster- setup (dynamic cluster) task completes.

Save the changes and then run.. Type the same value that you provided for the Cluster.

Name parameter in wkplc. The task proceeds to create the new dynamic cluster. Therefore, the warning can be ignored. If you are uncertain of the server name, run the task.. Edit notes. ini on the Web server Set HTTPEnable.

Connector. Headers and HTTPAllow. Decoded. Url. Percent to 1.

If you are using Web. Dav, enable it in the Lotus Domino Webserver Administrative Console.

The recommended minimum value is 6. Adjust higher if you are retrieving data from a database. To update, edit plugin- cfg. Server. IOTimeout .

See Common questions about the Web server plug- in. We can enable/disable these directives by editing obj. If the Web server has these methods disabled. Enable HTTP tunneling to simulate PUT and DELETE requests, which means that POST requests are used instead. Create custom LDIF files in..

For example, if the default federated repository contains an ID such as wpsadmin, this ID cannot exist in the LDAP you are adding. This can happen if you install Web. Sphere Portal and then enable a Federated LDAP or Federated database user repository that does not contain that user. Also, users who sign up using the Self Care portlet do not have awareness. This command allows the Administrator to log in using the fully distinguished name instead of the short name.

We can ignore this line. Replace the WAS and portal administrator user and group IDs with users and groups that exist in the LDAP user registry. Stop and restart all required servers. If the server is stopped, to skip the validation..

Stop and restart all required servers. Remove the file system repository if you do not use it. If the file system repository is no longer needed, removing it can help prevent conflicts created by duplicate user identities existing in multiple repositories. We can add multiple LDAP user registries to the default federated repository although you can only add one LDAP server at a time.

This can happen if you install Web. Sphere Portal and then enable a Federated LDAP or Federated database user repository that does not contain that user.

Also, users who sign up using the Self Care portlet do not have awareness. This command allows the Administrator to log in using the fully distinguished name instead of the short name.

We can ignore this line. Replace the WAS and portal administrator user and group IDs with users and groups that exist in the LDAP user registry. Stop and restart all required servers. If the server is stopped, to skip the validation.. Stop and restart all required servers.

Remove the file system repository if you do not use it. If the file system repository is no longer needed, removing it can help prevent conflicts created by duplicate user identities existing in multiple repositories. We can add multiple database user registries to the default federated repository although you can only add one database user registry at a time. The tempdb collation is inherited from the master database, which you set when you install SQL Server. We can run this task from any node in the cluster.

This can happen if you install Web. Sphere Portal and then enable a Federated LDAP or Federated database user repository that does not contain that user. Also, users who sign up using the Self Care portlet do not have awareness. When configuring realm support, complete these steps for each base entry that exists in the LDAP and/or database user registry to create multiple realm support. If you are going to create multiple realms, create all required base entries within the LDAP user registries and/or database user registries.

All base entry names must be unique within the federated repository. Stop and restart the appropriate servers for the installation environment, and then update wkplc. Repeat these steps until all realms are created. For example, if you have two additional base entries (base entry 1 and base entry 2) to add to the realm you just created, update wkplc. Then update the properties file with the information for base entry 2 and then run this task. Edit wkplc. properties. Set value for new base entry under VMM realm configuration heading.

Save changes to wkplc.