Starting up 252 PDBs in Oracle Multitenant. The awkward thing here is that the XDB messages appear over 20 minutes AFTER the PDBs signaled the Opening message into the alert.log (see the time stamps above). Now after exchanging a few emails with some very helpful people in development there's an explanation for the XDB messages as well.
On UNIX- and Linux-based systems, including Oracle 12c, the software is installed and configured as a specific user and group. In most cases, the user is called oracle, the primary group oinstall, and the secondary group dba. Here’s a sample of how this user is defined:
On Windows systems, the software should be installed as a member of the Local Administrators group for the machine.
It’s common to have multiple versions of Oracle running on the same machine simultaneously. To avoid chaos, you need to organize how and where each version is installed. The framework commonly used to organize and install Oracle software is called Optimal Flexible Architecture (OFA). As the DBA, you can use this organizational hierarchy to install the Oracle software based on software versions and common directories used by all versions.
Key to the OFA is the directory environment variables ORACLE_BASE and ORACLE_HOME:
Here’s the hierarchy:
Now let’s describe each level of the hierarchy.
Here’s an example of how this hierarchy may exist on UNIX or Linux:
And on Windows:
When you install the database software with the Oracle installation tool (Oracle Universal Installer), it guides you through identifying these locations, but, you need to understand why each location is defined so you can better organize your software installations.
In the ORACLE_BASE directory, an Oracle Inventory directory is created as oraInventory. Within this directory, Oracle logs a record of all Oracle software that has been installed, patched, and removed from the server. This information is used so that the Oracle Universal Installer (OUI) and the OPatch utility can track software dependencies during installation and patching operations. The Oracle Inventory is managed automatically by the OUI and OPatch utilities.
Underneath ORACLE_BASE is an admin directory with named subdirectories for each Oracle database, as well as backup, config tool logs, the Fast Recovery Area, and product directories:
Of particular importance, under each ORACLE_BASE/admin/database name subdirectory is directories for auditing, Data Pump configuration files, configuration, and Oracle Security Wallet files:
Below you see directories for auditing, Data Pump, configuration, and Oracle wallets.
Oracle Alert Log
In previous versions of Oracle, bdump, cdump, and udump directories appeared underneath each database admin directory storing alert, trace, and core dump files. However, starting in Oracle 11g and continuing so in 12c, these directories appear in trace, alert, and incident subdirectories under the $ORACLE_BASE/diag/rdbms/database name directory. Here you see the location of key trace and alert files.
Oracle manages software installations based on their ORACLE_HOME directories. Multiple ORACLE_HOME directories can exist on a server, each corresponding to a different version of the database. Different versions can generally coexist without conflict as they only share the Oracle Inventory, oratab file, and database listener process. This separation of the software into different directories allows this separation and management to occur. Here’s an example of multiple ORACLE HOME directories:
In the preceding example, you see multiple ORACLE_HOME directories installed into different directories. Defining your environment variable settings to point to a specific ORACLE_HOME determines which one you’re using.
Database files (data, index, control, redo) are preferably stored in separate file systems allocated specifically for this purpose and separated by database names:
The oracle user in group dba needs to be able to read, write, and execute to the ORACLE_BASE and ORACLE_HOME directories, subdirectories, and files, as well as the database files themselves. If other users on this server need to execute programs on the server side, such as SQL*Plus or export/import or SQL*Loader, they need execute permissions on corresponding executables and, in some cases, libraries.
This appendix describes how you install, reinstall, upgrade, manage, and configure Oracle XML DB.
This appendix contains these topics:
Installing Oracle XML DBXdb Installed
You are required to install Oracle XML DB under the following conditions:
Installing or Reinstalling Oracle XML DB From Scratch
You can perform a new installation of Oracle XML DB with or without Database Configuration Assistant (DBCA). If Oracle XML DB is already installed, complete the steps in 'Reinstalling Oracle XML DB'.
Installing a New Oracle XML DB With Database Configuration Assistant
Oracle XML DB is part of the seed database and installed by Database Configuration Assistant (DBCA) by default. No additional steps are required to install Oracle XML DB. However, if you select the Advanced database configuration, then you can configure Oracle XML DB tablespace and FTP, HTTP, and WebDAV port numbers.
By default DBCA performs the following tasks during installation:
The Oracle XML DB tablespace holds the data stored in Oracle XML DB repository, including data stored using:
You can store data in tables outside this tablespace and access the data through the repository by having REFs to that data stored in the tables in this tablespace.
Dynamic Protocol Registration Registers FTP and HTTP Services with Local Listener
Oracle XML DB installation, includes a dynamic protocol registration that registers FTP and HTTP services with the local Listener. You can perform start, stop, and query with
lsnrctl . For example:
Oracle Xdb SchemaChanging FTP or HTTP Port Numbers
To change FTP or HTTP port numbers, update the tags
<ftp-port> and <http-port> in file, /xdbconfig.xml in Oracle XML DB repository.
After updating the port numbers dynamic protocol registration automatically stops FTP/HTTP service on old port numbers and starts them on new port numbers if the local Listener is up. If local Listener is not up, restart the Listener after updating the port numbers.
Postinstallation
As explained in the previous section, Oracle XML DB uses dynamic protocol registration to setup FTP and HTTP Listener services with the local Listener. So, make certain that the Listener is up when accessing Oracle XML DB protocols.
To allow for unauthenticated access to your Oracle XML DB repository data through HTTP, you must unlock the ANONYMOUS user account.
Installing a New Oracle XML DB Manually Without Database Configuration Assistant
After the database installation, you must run the following SQL scripts in
rdbms/admin connecting to SYS to install Oracle XML DB after creating a new tablespace for Oracle XML DB repository. Here is the syntax for this:
For example:
Reconnect to SYS again and run the following:
Oracle Xdb UserPostinstallation
After the manual installation, carry out these tasks:
Reinstalling Oracle XML DB
To reinstall Oracle XML DB follow these steps:
Upgrading an Existing Oracle XML DB Installation
Run the script,
catproc.sql , as always.
As a post upgrade step, if you want Oracle XML DB functionality, then you must install Oracle XML DB manually as described in 'Installing a New Oracle XML DB Manually Without Database Configuration Assistant'.
Upgrading Oracle XML DB From Release 9.2 to 10g Release 1 (10.1)
All Oracle XML DB upgrade tasks are handled automatically when you use Database Upgrade Assistant to upgrade your database from any version of Oracle9i release 2 to Oracle Database 10g release 1 (10.1).
Privileges for Nested XMLType Tables When Upgrading to Oracle Database 10g
In Oracle9i release 2 (9.2), when you granted privileges on an
XMLType table, they were not propagated to nested tables deeper than one level. In Oracle Database 10g, these privileges are propagated to all levels of nested tables.
Agilent 34401a software. 34401A Digital Multimeter, 6½ Digit. Product Status. This is the brochure for Keysight's range of digital multimeters from a bench top to a test rack to a handheld. Brochure 2015-12-11. Manage Software Licenses; Find a Manual; Update Firmware/Software; Browse Application Notes. Software Revision This guide is valid for the firmware that was. Lint-free, slightly dampened cloth. Do not use detergent or chemical solvents. Safety Symbols WARNING Main Power and Test Input Disconnect: Unplug instrument. The Agilent 34401A Digital Multimeter provides. View and Download Agilent Technologies 34401A user manual online. Agilent Technologies Agilent 34401A 6 Digit Multimeter User's Guide. 34401A Multimeter pdf manual download. Protection Limits The Agilent 34401A Digital Multimeter pro- vides protection circuitry to prevent damage to the instrument and to protect against the danger of.
When you upgrade from Oracle9i release 2 (9.2) to Oracle Database 10g with these nested tables, the corresponding nested tables (in Oracle Database 10g) will not have the right privileges propagated and users will not be able to access data from these tables. A typical error encountered is,
ORA-00942:table or view not found . The workaround is to reexecute the original GRANT statement in Oracle Database 10g. This ensures that all privileges are propagated correctly.
Configuring Oracle XML DB
The following sections describe how to configure Oracle XML DB. You can also configure Oracle XML DB using Oracle Enterprise Manager.
Oracle XML DB is managed through a configuration resource stored in Oracle XML DB repository,
/xdbconfig.xml .
The Oracle XML DB configuration file is alterable at runtime. Simply updating the configuration file, causes a new version of the file to be generated. At the start of each session, the current version of the configuration is bound to that session. The session will use this configuration for its life, unless you make an explicit call to refresh to the latest configuration.
Oracle XML DB Configuration File, xdbconfig.xml
Oracle XML DB configuration is stored as an XML resource,
/xdbconfig.xml conforming to the Oracle XML DB configuration XML schema: http://xmlns.oracle.com/xdb/xdbconfig.xsd
To configure or modify the configuration of Oracle XML DB, update the
/xdbconfig.xml file by inserting, removing, or editing the appropriate XML elements in xdbconfig.xml .
Oracle XML DB configuration XML schema has the following structure:
Top Level Tag <xdbconfig>
A top level tag,
<xdbconfig> is divided into two sections:
The following describes the syntax:
<sysconfig>
The
<sysconfig> section is further subdivided as follows:
It stores several general parameters that apply to all Oracle XML DB, for example, the maximum age of an access control list (ACL), whether Oracle XML DB should be case sensitive, and so on.
Protocol-specific parameters are grouped inside the
<protocolconfig> tag.
<userconfig>
The
<userconfig> section contains any parameters that you may want to add.
<protocolconfig>
The structure of the
<protocolconfig> section is as follows:
Under
<common> Oracle Database 10g stores parameters that apply to all protocols, such as MIME type information. There are also HTTP and FTP specific parameters under sections <httpconfig> and <ftpconfig> respectively.
<httpconfig>
Inside <httpconfig> there is a further subsection, <webappconfig> that corresponds to Web-based applications. It includes Web application specific parameters, for example, icon name, display name for the application, list of servlets in Oracle XML DB, and so on.
Oracle XML DB Configuration Example
The following is a sample Oracle XML DB configuration file:
Oracle XML DB Configuration API
The Oracle XML DB Configuration application program interface (API) can be accessed just like any other XML schema-based resource in the hierarchy. It can be accessed and manipulated using FTP, HTTP, WebDAV, Oracle Enterprise Manager, or any of the resource and Document Object Model (DOM) APIs for Java, PL/SQL, or C (OCI).
For convenience, there is a PL/SQL API provided as part of the
DBMS_XDB package for configuration access. It exposes the following functions:
Get Configuration, cfg_get()Oracle Database Alert Log
The
cfg_get() function returns a copy of the configuration as an XMLType :
Update Configuration, cfg_update()
The
cfg_update() function updates the configuration with a new one:
cfg_update() is auto-commit.
Example A-2 Updating the Configuration File Using cfg_update() and cfg_get()
If you have a few parameters to update in the configuration file, then you can use the following:
If you have many parameters to update, then the preceding example may prove too cumbersome. Use instead FTP, HTTP, or Oracle Enterprise Manager.
Refresh Configuration, cfg_refresh()
The
cfg_refresh() function updates the configuration snapshot to correspond to the latest version on disk at that instant:
Oracle Xdb Xmltype
Typically,
cfg_refresh() is called in one of the following scenarios:
Xdb Database
1 Comment
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |