The error shown in the protocol might look like this:
System.IO.FileNotFoundException: Could not load file or assembly 'Oracle.DataAccess'
or refer to a missing DataAccess.dll in some other way.
The Oracle Client might not have finished successfully.
In this case the AdminTool / ConnectMaster cannot connect to database.
The following actions in the Command Prompt (cmd.exe) will help analyze the problem:
- Are you able to connect via the sqlplus Tool?
- sqlplus sys/<password>@<DBname> as sysdba
- Are you able to ping the DB?
- tnsping <DBname>
- Is Oracle client present in the PATH environment variable? (e.g.: C:\cm\oracle\product\19.0.0\client_1\bin)
- set path
- Is the Oracle client installation present in the expected folder?
- e.g.: C:\cm\oracle\...
Solution
The main reason for this is usually an incorrect path for the installation files. It's best to use short, top-level paths:
C:\temp for the installation packages
C:\cm for the ConnectMaster program
C:\cm\oracle for the Oracle Client
C:\oracle for the Oracle Server
Note: Extraction of the software ZIP files and installation should NOT be run from a network path. Copy them to a local path beforehand! |
Important: Make sure you unpack the installation files to a short, local path that does NOT contain spaces! e.g.: C:\temp\CM702_ora19c_x64_0205.1
Before extraction make sure the zip files are unblocked in the files properties.
|
Please make sure the Oracle Client was installed correctly:
Comments
0 comments
Please sign in to leave a comment.