Use a common data set to create multiple scenarios for what-if analyses or multiple editions of data for publication A typical example might be an application to design an engineering project, in which multiple subprojects are concurrently developed in separate workspaces. Workspace locks prevent update conflicts between projects in separate workspaces. Workspace privileges control access to a workspace and its operations, and you can restrict workspace access to single-writer, read-only, or no access. Support a collaborative development effortĪ team can share access to a collection of updates and insertions for a collaborative project. A typical example might be a life sciences application in which Workspace Manager supports the discovery and quality assurance (QA) processes by managing a collection of updates before they are merged with the production data. You can organize the changes in a simple set of workspaces or in a complex workspace hierarchy. Until you make the changes public, they are invisible to other users of the database, who will access only the regular production data. You can review changes and roll back undesirable ones before making the changes public. Manage a collection of updates and insertions as a unit before incorporating them into production data The ongoing results of the activity are stored persistently, assuring concurrency and consistency.Īpplications that can benefit from Workspace Manager typically do one or more of the following operations: Users are permitted to create new versions of data to update, while maintaining a copy of the old data. Workspace Manager, often referred to as Workspace Manager, provides an infrastructure that enables applications to create workspaces and group different versions of table row values in different workspaces. # Port number to be used for by the Oracle Scheduler Agent. # list of custom components during custom install # This needs to be entered in case is selected in the # Host name to be used for by the Oracle Scheduler Agent. # selected in the list of custom components in custom install This needs to be entered in case oracle.ntoramts is #Description: Port number to be used for by the Oracle MTS Recovery Service to listen # oracle.dbdev:11.2.0.1.0 - "Oracle SQL Developer" # :11.2.0.1.0 - "Oracle Clusterware High Availability API" # oracle.ons:11.2.0.0.0 - "Oracle Notification Service" # :11.2.0.1.0 - "Oracle Multimedia Client Option" # :11.2.0.1.0 - "OLAP Analytic Workspace Manager and Worksheet" # :11.2.0.1.0 - "Enterprise Manager Minimal Integration" # oracle.xdk:11.2.0.1.0 - "Oracle XML Development Kit" # :11.2.0.1.0 - "Oracle Internet Directory Client" # Below is a list of components you may specify to install. # be specified in the form "internal-component-name:version" # Description: List of Client Components you would like to install # This property is considered only if INSTALL_TYPE is set to "Custom" #Example : INSTALL_TYPE = "Administrator" #Description: Installation type of the component. # en_GB: English (Great Britain) sk : Slovak # ar_EG: Egyptian zh_CN: Simplified Chinese # fr_CA: Canadian French es_MX: Mexican Spanish # pt_BR: Brazilian Portuguese lt : Lithuanian # ar : Arabic es : Latin American Spanish # Specify the languages in which the components will be installed. INVENTORY_LOCATION=C:\Program Files (x86)\Oracle\Inventory # Unix group to be set for the inventory directory. # (e.g., for systems with multiple hostnames and network interfaces). # hostname rather than using the first hostname found on the system # It can be used to force the installation to use an alternative # This variable holds the hostname of the system as set by the user. # Do not change the following system generated value. # can help to populate the variables with the appropriate # # Each variable is associated with a comment. # Specify values for the variables listed below to customize # # Copyright(c) Oracle Corporation 1998,2008. Not sure if its an issue with my response file?
0 Comments
Leave a Reply. |