If the ECDA Option for Oracle (also referred to as DCO)
was already installed and a directory was created:
Set the environment variables by sourcing the $SYBASE/SYBASE.csh file and the $SYBASE/DCO_SYBASE.csh file.
Execute the $SYBASE/$SYBASE_DCO/install/DCConfig to configure a new DCO and proceed to step 11.
To install ECDA Option for Oracle in GUI mode
If you want to install using the console mode or a response file, refer to the Enterprise Connect Data Access Installation Guide for Linux and UNIX.
Use one of the following methods to download the software:
From the Sybase Software Product Download Center (SPDC) Web site, navigate to the directory where the ECDA software has been downloaded, uncompressed, and extracted. Download the ECDA 15.0. Then, use the GNU utilities to unzip and un-tar the software download to a new directory. When un-tarred, the directory should contain these files: media.inf, suite, archives, setup.
Insert the CD labeled ECDA 15.0 Options for Oracle for Sun Solaris.
Launch the installation program by executing the Sun Solaris setup routine:
./setup
If you see an error message saying that there is not enough temporary disk space, add this to your setup command:
./setup –is:tempdir someDirectory
where someDirectory is a directory with at least 100MB of disk space that the installation program can use.
On the Welcome window, click Next.
Select a geographic location that displays the license agreement. Select I Agree and click Next.
Enter the directory where you want to install ECDA:
In the destination directory, enter the directory where the Mirror Replication Agent software is installed. Click Yes to install into an existing directory.
If the destination directory exists, you receive a warning message that you are installing into an existing directory. Click Yes.
Select the Full setup and click Next.
Verify the modules to install. At a minimum, ECDA Option for Oracle, Connectivity, and Language Modules should be listed. Click Next.
You may receive a message:
There are newer files already installed and do you want to replace them?
Click No to All.
When you receive a message that the installation was successful, click Next.
The SySAM License Server window opens and displays this prompt:
Will licenses be obtained from the License Server?
If you answer Yes, you can leave both the license-mrx.lic and the license-dco.lic license files where they were installed in $SYBASE/SYSAM-2_0/licenses, or you can move the files to the SYSAM-2/licenses directory of your SySAM license server. In either case, the Mirror Replication Agent and ECDA Option for Oracle will verify the necessary licenses.
If you answer No, no further action is needed. The Mirror Replication Agent and ECDA Option for Oracle will use the license files (license-mrx.lic and the license-dco.lic) as they were installed in the SYBASE/SYSAM-2_0/licenses directory.
The SySAM Notification window prompts you to configure your server for e-mail notification. When configuration is enabled, you receive information about license management events that require attention. Select Yes and either accept the default values that are supplied, or enter these values from your worksheet (from the installation guide):
SMTP server host name
SMTP server port number
E-mail return address
Recipients of the notification
Message severity level of an event that will trigger e-mail. Your choices are:
Informational
Warning
Error
If you choose not to have e-mail alerts or severity messages logged, select No.
Click Next.
When you receive a message indicating that ECDA was successfully installed, click Finish.
For more information, see the Enterprise Connect Data Access Installation Guide.
To verify that you can connect to Oracle
Open a command window in the $SYBASE directory of your ECDA installation.
Change to the $SYBASE/DCO-15_0 directory.
Set the environment variables by sourcing the $SYBASE/DCO_SYBASE.csh file.
Use isql to log in to Oracle through the DirectConnect server:
isql –Uvaliduser –Ppassword –SDCOServer
where:
validuser and password – any valid user and password.
DCOServer is the DCO server name identified in the previous step.
Verify the connection to the standby Oracle database:
select banner from v$version go
BANNER ----------------------------------------------- Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod PL/SQL Release 10.2.0.1.0 - Production CORE 10.2.0.1.0 Production TNS for Solaris Version 10.2.0.1.0 - Production NLSRTL Version 10.2.0.1.0 - Production
(5 rows affected)
Exit isql.