. xfce4-systemload-plugin:amd64 1:1.2.4-1ubuntu1. xfce4-taskmanager 1.4.0-1. xfce4-terminal 0.8.10-1. xfce4-verve-plugin:amd64 2.0.1-1. xfce4-weather-plugin:amd64 0.11.0-1. xfce4-whiskermenu-plugin:amd64 2.5.3-1. xfce4-xkb-plugin:amd64 1:0.8.2-1. xfconf 4.16.0-2. xfdesktop4 4.16.0-1. xfdesktop4-data 4.16.0-1. SystemLoad SystemLoad can monitor the status of various system components. It is a modular platform to display different data sets. The goal of this project is to provide a simple monitor tool for displaying dynamic information. System load aggregates alert. Fully composable (you pick what you need) observability stack for metrics, logs, traces and synthetic monitoring integrated with Grafana.
This chapter contains instructions for obtaining and running the Repository Creation Utility (RCU).
This chapter contains the following sections:
2.1 Obtaining RCU
In 12c (12.1.3), RCU is available with the Oracle Fusion Middleware Infrastructure distribution. For information about how to install this software and obtain RCU, see Installing and Configuring the Oracle Fusion Middleware Infrastructure.
2.2 Starting RCU
After Oracle Fusion Middleware Infrastructure is installed, start RCU from the ORACLE_HOME/oracle_common/bin directory.
Note:
If you are running RCU using a non-English database, you will need to set the following language environment variables: LANG, LC_ALL, and NLS_LANG. Use the environment commands that are appropriate for your environment.
For example, for UNIX operating systems running csh enter the following:
On Linux operating systems:
On Windows operating systems:
RCU provides a command line interface in situations where Xserver is not available or you have access to telnet terminals without display capabilities. The command line interface also allows you to embed RCU from command line scripts or with some Oracle Fusion Middleware components (for example, Enterprise Manager).
For more information using the CLI, see Chapter 3.
2.3 Creating Schemas
This section contains the following:
2.3.1 Creating Schemas as a User with Full SYS or SYSDBA Privileges
If you are a user with full SYS or SYSDBA privileges, and are able to provide valid authentication credentials for database access, follow the instructions in Table 2-1 to create schemas.
Click on the screen name to see more detailed information for that screen. Unless otherwise noted, click Next to continue to the next screen.
Table 2-1 Schema Creation Steps for Full-Privilege Users
| Screen | Description |
|---|---|
This screen introduces you to RCU. You can choose to skip this screen each time you start RCU by selecting Skip This Page Next Time. | |
Select Create Repository, then select System Load and Product Load. If you do not have full SYS or SYSDBA privileges on the database, select Prepare Scripts for System Load and follow the schema creation instructions in Section 2.3.2. | |
Specify your database connection credentials. Remember that if you are creating schemas on an IBM DB2 database, you must have already created one operating system user for each schema you want to create. See Section 1.1.4 for more information. Click Next when you have specified your credentials. A separate dialog window will appear while RCU checks connectivity and some database prerequisites. When the database checking has passed without errors, click OK to dismiss the dialog window and go to the next screen. | |
Select the components for which you want to create schemas, and specify a prefix to group them together. You must remember the prefix and schema names for the components you are installing; you will need this information during the configuration phase of your product installation. Oracle recommends that you write these values down. | |
Specify the passwords for your schema owners. You must remember the passwords you enter on this screen; you will need this information during the configuration phase of your product installation. Oracle recommends that you write these values down. | |
This screen appears only if the Oracle home from which you started RCU contains Oracle Data Integrator or Oracle SOA Suite.
| |
Use this screen to configure the desired tablespace mapping for the schemas you want to create. When you click Next, a separate dialog window will appear asking you to confirm that you want to create these tablespaces. Click OK to proceed and dismiss the dialog window. A second dialog window will appear showing the progress of tablespace creation. After this is complete, click OK to dismiss this window and go to the next screen. | |
Verify the information on this screen, then click Create to begin schema creation. | |
Review the information on this screen to verify that the operation was completed successfully. Click Close to complete the schema creation and dismiss RCU. |
System Load Average
2.3.2 Creating Schemas as a User With Limited Database Privileges
If you are a user without SYS or SYSDBA privileges, or you are unable to provide valid authentication credentials for database access, follow the instructions in Table 2-2 to create schemas.
Table 2-2 Schema Creation Steps for Limited-Privilege Users
| Screen | Description |
|---|---|
This screen introduces you to RCU. You can choose to skip this screen each time you start RCU by selecting Skip This Page Next Time. | |
Select Create Repository, then select Prepare Scripts for System Load. See Section 1.2.1 for more information about these operations. | |
Specify your database connection credentials. Click Next when you have specified your credentials. A separate dialog window will appear while RCU checks connectivity and some database prerequisites. When the database checking has passed without errors, click OK to dismiss the dialog window and go to the next screen. NOTE: Performing system load and product load separately is only supported on Oracle or Oracle EBR databases. | |
Select the components for which you want to create schemas, and specify a prefix to group them together. You must remember the prefix and schema names for the components you are installing; you will need this information during the configuration phase of your product installation. Oracle recommends that you write these values down. | |
Use this screen to configure the desired tablespace mapping for the schemas you want to create. When you click Next, a separate dialog window will appear asking you to confirm that you want to create these tablespaces. Click OK to proceed and dismiss the dialog window. A second dialog window will appear showing the progress of tablespace creation. After this is complete, click OK to dismiss this window and go to the next screen. | |
Verify the information on this screen, then click Generate to begin script generation. By default, the scripts are located in the The names of the scripts generated are | |
N/A | After the scripts are created, someone with SYS or SYSDBA privileges should execute the script:
|
N/A | After the script is executed, start RCU again and perform the product load phase to complete schema creation. |
This screen introduces you to RCU. You can choose to skip this screen each time you start RCU by selecting Skip This Page Next Time. | |
Select Create Repository, then select Perform Product Load. See Section 1.2.1 for more information about these operations. | |
Specify your database connection credentials. Click Next when you have specified your credentials. A separate dialog window will appear while RCU checks connectivity and some database prerequisites. When the database checking has passed without errors, click OK to dismiss the dialog window and go to the next screen. | |
From the drop-down list, select the prefix you specified earlier in this procedure. Then, select the components for which you want to perform the product load. | |
Specify the passwords for your schema owners. You must remember the passwords you enter on this screen; you will need this information during the configuration phase of your product installation. Oracle recommends that you write these values down. | |
Verify the information on this screen, then click Create to begin schema creation. | |
Review the information on this screen to verify that the operation was completed successfully. Click Close to complete the schema creation and dismiss RCU. |
System Loadlibrary
2.3.3 Verifying Schema Version Numbers
When the schemas are created in your database, RCU creates and maintains a table called schema_version_registry. This table contains schema information such as version number, component name and ID, date of creation and modification, and custom prefix.
To verify that the schemas are installed properly, run the following query after login in to SQL*Plus:
The comp_name argument retrieves the name of the component, and version retrieves the version number. For example:
2.4 Dropping Schemas
To drop schemas from the database, start RCU (see Section 2.2), then follow the instructions in Table 2-3.
Click on the screen name to see more detailed information for that screen. Unless otherwise noted, click Next to continue to the next screen.
Table 2-3 RCU Screens and Description for Dropping Schemas
| Screen | Instructions and Action Required |
|---|---|
This screen introduces you to RCU. You can choose to skip this screen each time you start RCU by selecting Skip This Page Next Time. | |
Select Drop Repository. | |
Specify the connection details for your database, then click Next. A separate dialog window will appear while RCU checks connectivity and some database prerequisites. When the database checking as passed without errors, click OK to dismiss the dialog window and go to the next screen. | |
Select the prefix and the schemas you want to drop, then click Next. A separate dialog window will appear asking you to verify that you want to drop the selected schemas. Click OK to dismiss this window. A second dialog window appears while RCU checks the prerequisites for the schemas you are dropping. After this is complete, click OK to dismiss this window and go to the next screen. | |
Review the information on this screen, then click Drop to drop the schemas. | |
Note the location of the log files, then click Close to dismiss the screen. |
2.4.1 Dropping Shared Tablespaces
Tablespaces that are shared among multiple schemas will not be dropped. For example, if you created both the Audit Services (for example, DEV_IAU) and Metadata Services (for example, DEV_MDS) schemas, both schemas would use the temporary tablespace DEV_IAS_TEMP (see Section A.8.1, 'Default Tablespace Mappings').
If you then drop the DEV_IAU schema, the DEV_IAS_TEMP tablespace would not be dropped since it is also being used by the DEV_MDS schema.
2.4.2 Dropping Schemas and Deleting Datafiles (Windows Only)
If you used RCU to drop a schema from a Windows-based database, and you want to recreate the dropped schema, you will have to manually delete datafiles that were not automatically removed when the schema was dropped.
Systemload
Navigate to the DB_HOMEoradata directory and manually delete any remaining datafiles before recreating the schema. Oracle recommends that you check this directory for any remaining datafiles before you attempt to recreate any dropped schema.
Comments are closed.