![]() ![]() A feature called "lazy locking" allows users to continue reading an object even when another user is updating that object. While a locking mechanism guarantees that only one user can write to an object at a time, it is rare for multiple users to attempt to write simultaneously to the same object. Therefore, the read-to-write ratio is typically at least 100 to 1. In Release 11 g, each user is constantly and automatically updating his or her Most Recently Used file, but each user's "read" operations still far outweigh the user's "writes" operations. The average user typically only reads from the catalog and rarely, if ever, writes to it. To achieve this scaling, the catalog adheres to the following guidelines: The catalog is designed to scale to thousands of concurrent users. The following search filters are all valid: When you pass a catalog search filter using SOAP, you must escape the following characters: Always verify your path code with an object name such as "Profit / Loss". It is very common to see code that assumes the forward slash (/) is always a path separator. The following logical path names are all valid: When you pass the path name of an object using SOAP, you must escape the following characters: The number of directory segments in a logical path name for an object must be not exceed 255 segments.įor example, a directory with a name such as /n1/n2/n3/n4/…./n253/n254/n255 is acceptable, while a name such as /n1/n2/n3/n4/…./n254/n255/n256 is unacceptable. The length of the logical path name for an object must not exceed 16000 Unicode characters. The length of the logical object name must not exceed 256 Unicode characters.įor more information on Unicode, see Section 17.1.3, "File System Guidelines for Catalogs." No restrictions exist on which characters are allowed in the logical name of an object in the catalog, provided that the characters are valid Unicode characters. The following list provides guidelines for object names: The object name that is visible to users, such as Analysis 1, is referred to as the logical object name. For example, an analysis called Analysis 1 is stored in a file named Analysis1. Section 17.12, "Replicating Oracle BI Presentation Catalogs"Įach object in the catalog is stored in its own file. Section 17.11, "Configuring for Full-Text Catalog Search" Section 17.10, "Archiving and Unarchiving Using Catalog Manager" Section 17.9, "Creating Reports to Display Catalog Data Using Catalog Manager" Section 17.8, "Searching for and Replacing Catalog Text Using Catalog Manager" Section 17.7, "Viewing and Editing Catalog Objects in XML" Section 17.6, "Working with Objects in Catalog Manager" Section 17.5, "Using the Catalog Manager Workspace" ![]() Section 17.4, "Starting Catalog Manager and Opening Catalogs" ![]() Section 17.2, "Maintaining the Oracle BI Presentation Catalog" Section 17.1, "About the Oracle BI Presentation Catalog" This chapter includes the following sections: This chapter describes how to configure and manage the Oracle BI Presentation Catalog and provides information about basic maintenance procedures and configuring for full-text searching. 26/44 17 Configuring and Managing the Oracle BI Presentation Catalog ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |