Lift and Shift to Oracle Data Integrator Cloud Service (ODICS) : Moving your Repository to the Cloud

  Oracle Data Integrator (ODI) is now available as a Cloud Service: Oracle Data Integrator Cloud Service (ODICS). For customers who are interested in a subscription model for their ODI installation and want to integrate and transform data in the Cloud, this is the solution. Customers who already have ODI developments on premises will want […]

Oracle Commerce Best Practices for Repository Item Cache Warming

Oracle Commerce customers often ask, “How should we warm our repository item cache for better page serving performance?” This article will address that question as well as some of the decisions that you’ll need to make along the way. First, let’s talk about what repository item cache warming is. Generally speaking, warming is when we […]

ODI 11g and 12c Repository Structures Available on MOS

We always recommend that customers use the ODI SDK to access the information stored in the ODI repository: the repository structure evolves from version to version, and the SDK shelters developers from these structural changes. This said, many developers still prefer to write their own SQL queries to read from the repositories directly, even if […]

How to Recover the RPD Repository Password in Fusion Applications or OBIEE

Introduction The RPD Repository file contains the metadata to create reports.  This includes details of the physical data sources and connections, the business model mapping with joins, and the presentation layer that is presented to report writers.  The RPD file is encrypted with the Repository Password.  Without that password – the BI Administration tool can […]

How Many ODI Master Repositories Should We Have?

Introduction A question that often comes up is how many Master Repositories should be created for a proper ODI architecture. The short answer is that this will depend on the network configuration. This article will elaborate on this very simplistic answer and will help define best practices for the architecture of ODI repositories in a […]

ODI: Restricting Visibility of Work Repositories

Introduction When ODI developers connect to the ODI studio, they can edit the connection parameters. In particular, they can manually select the Work Repository that they will connect to. Repository access can be password protected, but for security reasons it is best to not even list repositories that users should not have access to. This […]

Partitioned Repository for WebCenter Content using Oracle Database 11g

One of the biggest challenges for content management solutions is related to the storage management due the high volumes of the unstoppable growing of information.

Even if you have storage appliances and a lot of terabytes, thinks like backup, compression, deduplication, storage relocation, encryption, availability could be a nightmare.

One standard option that you have with the Oracle WebCenter Content is to store data to the database. And the Oracle Database allows you leverage features like compression, deduplication, encryption and seamless backup.

But with a huge volume, the challenge is passed to the DBA to keep the WebCenter Content Database up and running.

One solution is the use of DB partitions for your content repository, but what are the implications of this? Can I fit this with my business requirements?

Well, yes. It’s up to you how you will manage that, you just need a good plan. During you “storage brainstorm plan” take in your mind what you need, such as storage petabytes of documents? You need everything on-line? There’s a way to logically separate the “good content” from the “legacy content”?