Service "dg4sybs" has 1 instance s. The command completed successfully In this example, the service name is dg4sybs, which is the default SID value assigned during installation. To configure the Oracle database you must add connect descriptors to the tnsnames. You must edit the file manually. A sample of the tnsnames. Configuring tnsnames. Check the sqlnet. See "Syntax of listener. The Oracle client and the Oracle database can reside on different machines.
The gateway accepts connections only from the Oracle database. A connection to the gateway is established through a database link when it is first used in an Oracle session. In this context, a connection refers to the connection between the Oracle database and the gateway. The connection remains established until the Oracle session ends. Another session or user can access the same database link and get a distinct connection to the gateway and Sybase database.
Database links are active for the duration of a gateway session. To access the Sybase server, you must create a database link. A public database link is the most common of database links. When the Sybase database is updated by a transaction, the gateway becomes the commit point site.
The Oracle database commits the unit of work in the Sybase database after verifying that all Oracle databases in the transaction have successfully prepared the transaction. Only one gateway instance can participate in an Oracle two-phase commit transaction as the commit point site.
Variable Description dblink is the complete database link name. Create a Recovery Account and Password 2. This table needs to be in the same schema as the recovery account. Create a Recovery Account and Password For the gateway to recover distributed transactions, a recovery account and password must be set up in the Sybase database.
Set up a user account in the Sybase database. Both the user name and password must be a valid Sybase user name and password. Create the Transaction Log Table When configuring the gateway for two-phase commit, a table must be created in the Sybase database for logging transactions.
The gateway uses the transaction log table to check the status of failed transactions that were started at the Sybase database by the gateway and registered in the table. Moreover, storing plain-text as user name and password in the initialization file is not a good security policy.
There is now a utility called dg4pwd that should be used for encryption. Refer to Section 4. See Also: "Customize the Initialization Parameter File" on page for information about editing the initialization parameter file. Note: Updates to the transaction log table cannot be part of an Oracle distributed transaction. Create the transaction log table in the user account you created in "Create a Recovery Account and Password" on page Because the transaction log table is used to record the status of a gateway transaction, the table must reside at the database where the Sybase update takes place.
Also, the transaction log table must be created under the owner of the recovery account. You must run this script on each Sybase database that you want to access through the gateway. Encrypt Gateway Initialization Parameter Values The gateway uses user IDs and passwords to access the information in the remote database. Some user IDs and passwords must be defined in the gateway initialization file to handle functions such as resource recovery.
In the current security conscious environment, having plain-text passwords that are accessible in the initialization file is deemed insecure. The dg4pwd encryption utility has been added as part of Heterogeneous Services to help make this more secure.
This utility is accessible by this gateway. The initialization parameters that contain sensitive values can be stored in an encrypted form. Note: The information in the transaction log table is required by the recovery process and must not be altered. The table must be used, accessed, or updated only by the gateway. Note: To utilize the transaction log table, users of the gateway must be granted privileges on the table. For initdg4sybs2. Note: If you have multiple gateway SIDs for the same Sybase database because you want to use different gateway parameter settings at different times, follow the same procedure.
You create several initialization parameter files, each with different SIDs and different parameter settings. You must have an entry for each gateway instance, even when multiple gateway instances access the same database. The following example shows the entry for the original installed gateway first, followed by the new entries. You must have an entry for each gateway instance, even if the gateway instances access the same database.
The number can be found in the listener. The value for HOST is the name of the machine on which the gateway is running. The name also can be found in the listener. Ensure that the system meets all of the hardware and software requirements specified in "System Requirements for Oracle Database Gateway for Informix" on page See Table 4—3 for a description of the installation procedure of Oracle Database Gateway for Informix.
System Requirements for Oracle Database Gateway for Informix This section provides information about the hardware and software requirements for the gateway. Disk Space 1. To determine the amount of disk space available on the system enter the following commands: Software Requirements The following section describes the minimum software requirements for Oracle Database Gateway for Informix.
Operating System Table 4—2 lists the minimum operating system version required for Oracle Database Gateway for Informix. Select Oracle Database Gateway for Informix Encrypt Gateway Initialization Parameter Values 7.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.
If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Other names may be trademarks of their respective owners. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.
Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U. Government, then the following notice is applicable:. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. The terms governing the U. No other rights are granted to the U. This software or hardware is developed for general use in a variety of information management applications.
0コメント