Download Repository Creation Utility BEST
Joelle Ridgeway
RCU supports multiple repositories (collection of related schemas) within a single physical database. For example, you could have one repository with only one schema named MDS and a second repository with two schemas named MDS and PORTAL. Both of these repositories can reside on the same database.
I'm running the Oracle Repository Creation Utility (RCU) as a precursor to installing WebCenter, and the schema creation process is stuck on the "Portal" step. The first 10-12 steps each took less than 30 seconds to complete, and the last step has been going for 2 hours 14 minutes.
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.
The Service Table schema is a special schema that is installed automatically whenever RCU is run. The service table stores basic schema configuration information (for example, schema prefixes and passwords) that can then be accessed and used by other Oracle Fusion Middleware components during domain creation.
The Repository Configuration Utility (RCU) is a necessary prerequisite for the creation of clustered domains in WebLogic 12c. It is recommended to install Forms and Reports Services as a clustered domain, even if it is for a single node, so it is also a prerequisite for those installations.
Follow the Oracle licensing guidelines for the Oracle database that hosts the repository. For more information, see Oracle Fusion Middleware Licensing Information UserManual in the Oracle documentation.
After the system load phase is complete, any user with the privileges described in Granting Permissions to Users for Querying System Load Objects can then run RCU again to complete the schema creation by performing the product load phase.
The Service Table schema is a special schema that is automatically created once per prefix. The service table stores basic schema configuration information (for example, schema prefixes and passwords) that can then be accessed and used by other Oracle Fusion Middleware components during domain creation.
A Repository database is needed for the Oracle GoldenGate Studio to store all the information of the architecture and mappings. To create the repository, Oracle GoldenGate studio provides us with REPOSITORY CREATION UTILITY (RCU). We need to run this to create the Repository.
5. You could load multiple repository (like Portal, webcenter, SOAINFRA) in single database. You could also load different version of same repository (like dev_soainfra, test_soainfra for DEV & Test instance resp.) in same database. (This is interesting feature for using single database for multiple Fusion Middleware Instances)
We have created a Fusion Middleware environment for DIsocverer . everything went on fine . it ran for two weeks . suddenly our database got correpted and our DBA team dropped the Database. In this database we have created the Repositiry using RCU . now when we are going to the discoverer login page it is givng the errror as it is pointing and searching for the lost databse. we have created a new database and created a new repository . we dont want to uninstall and reinstall again from scratch but just want to map the new repository instead of the new one . is there any chance to do this approach ?
Check in database if there is schema like DEV_ORABAM, DEV_SOAINFRA, DEV_ORASDPM, DEV_MDS and if password is same as you are entering above. If schemas are missing then create schema using RCU -fusion-middleware-11g-repository-creation-utility-rcu/
I want to carry out regular (monthly) cleanup of the RCU schemas like (DEV_MDS, DEV_SOAINFRA, DEV_ORABAM, DEV_IAS_ORASDPM) Over time, the tablespace seems to increase in size which is a concern. I tried the purge script for cleaning the composite instances, which does reclaim some space back. Example in DEV_SOAINFRA schema,inspite of purging there lots of records in tables like MEDIATOR_AUDIT_DOCUMENT, SYS_LOB0000076386C00004$$, MEDIATOR_CASE_DETAIL, MEDIATOR_PAYLOAD etc. How do one carry out a monthly cleanup of the SOA repository schemas, so it does not keep growing in size?
Back in an earlier post, I wrote about how to installed Fusion infrastructure, Webcenter Portal, Webcenter content. This post is about Repository creation Utility which is important task while setting up your Webcenter Portal/Content environment.
Once you confirmed there are no entries in System.SCHEMA_VERSION_REGISTRY$ table and start the RCU to create repository schemas with the prefix (DEV in my case). The RCU will go smooth and wont complain with any error.
hi,
We have databas server oracle 10g release 10.2.0.3.0 on separate solaris machine I am trying to install OBIEE 11g on solaris 10 on separate machine, while performing prerequiste for OBIEE 11G i am installing RCU for repository creation, but cant succeeded it show me error Current Platform is not supported Supported Platform are Linux and Windows. As in oracle.com there rcu available only for linux and windows my question is there is an alternative way to install repository, kindly send me prerequiste steps so that i install OBIEE 11G successfully.
Footnote: It is critical that if you want to remove an RCU schema, you do so through the RCU utility. If you try to drop the schema from your database directly, you will get all sorts of problems, including if you try to re-use the schema prefix for a different RCU repository:
Since we had the same issue with all of the Oracle installers, we had to use the silent install method for both the database software install and database creation. We are covering the steps for the silent installation and database creation quickly, in order to cover the OEM software installation in detail.
To install Edge on a node, you first install the Edge apigee-setup utility. If you are in an environment where your nodes do not have an external internet connection, you must also install a local copy of the Apigee repo.
If your Edge nodes are behind a firewall, or in some other way are prohibited from accessing the Apigee repository over the Internet, then you must create a local repository, or mirror, of the Apigee repo. That mirror must then be accessible to all nodes. Once created, nodes can then access that local mirror to install Edge.
To create the internal Apigee repository, you do require a node with an external internet access to be able to download the Edge RPMs and dependencies. Once you have created the internal repo, you can then move it to another node or make that node accessible to the Edge nodes for installation.
This step takes several minutes to complete but it does not matter; as said previously, the real optimization occurs in the instantiation step, not in the installation of the binaries or the creation of the model docbase; those steps are done only once (unless it is done outside the context of this project).
It is possible to specify as many docbases to be created (or instantiated, see later) in global_parameters.$dctm_machine as needed by specifying their stems on the command-line. So, if several docbases need be created, define them all in global_parameters and invoke the creation script as follows:
Granted, when using PostgreSQL , since the docbase creation demands a server listening on port 5432, there may be a short period of time when a server gets commonly used by several instances of dm_launch_server_config_program.sh. Also, multiple database server instances get started on port 5432, but with only the first one succeeding. Still, this should not be an issue since the databases and their locations are distinct. This glitch does not happen at instantiation time as the PostgreSQL server is always started from the beginning with a custom port.
The additional cost is 2 Gb of disk space since the documentum binaries are not shared between the repositories (i.e. each repository has its own $DOCUMENTUM and its own copy of the binaries), but disk space is so cheap these days that this is not prohibitive. When using Oracle, the above concurrency behavior does not apply.
Review the configuration parameters for PV creation here. Based on your requirements, update the values in the create-pv-pvc-inputs.yaml file located at $WORKDIR/weblogic-kubernetes-operator/kubernetes/samples/scripts/create-weblogic-domain-pv-pvc/. Sample configuration parameter values for an Oracle SOA Suite domain are:
Similar to the previous Oracle BI version, Oracle BI 12c requires a relational database repository schema to hold metadata concerning the installation, report scheduling, usage tracking, auditing, and other aspects of the environment. As an initial set of steps in the installation process, these very necessary repositories are created using the Repository Creation Utility (RCU) against the selected database server. Chapter 2, Installing the Pre-requisite Software, goes into greater detail about this crucial repository structure. In Oracle BI 11g, two database schemas were installed with the RCU-Metadata Services (MDS) and BIPLATFORM. However, in Oracle BI 12c there can be up to nine database repository ...
Subversion repository creation is an incredibly simple task. The svnadmin utility that comes with Subversion provides a subcommand (svnadmin create) for doing just that.
Assuming that the parent directory /var/svn exists and that you have sufficient permissions to modify that directory, the previous command creates a new repository in the directory /var/svn/repos, and with the default filesystem data store (FSFS). You can explicitly choose the filesystem type using the --fs-type argument, which accepts as a parameter either fsfs or bdb.
After running this simple command, you have a Subversion repository. Depending on how users will access this new repository, you might need to fiddle with its filesystem permissions. But since basic system administration is rather outside the scope of this text, we'll leave further exploration of that topic as an exercise to the reader.
df19127ead