After installing Oracle Linux 6:
uname -a
Linux ponos 2.6.39-400.109.1.el6uek.x86_64 #1 SMP Tue Jun 4 23:21:51 PDT 2013 x86_64 x86_64 x86_64 GNU/Linux
and making sure that all the pre-required packages are present, I downloaded "Oracle Database 12c Release 1 (12.1.0.1.0) for Linux x86-64", followed the pre-installation instructions and launched the installer.
The installer runs smoothly up to the "Execute Root Scripts" step.
During the "Oracle Database configuration", the "Oracle Net Configuration Assistant" throws error:
[INS-20802] Oracle Net Configuration Assistant failed.
The error log is empty:
-rw-rw----. 1 oracle oinstall 1197690 Jul 8 14:45 installActions2013-07-08_02-18-05PM.log
-rw-rw----. 1 oracle oinstall 0 Jul 8 14:30 oraInstall2013-07-08_02-18-05PM.err
-rw-rw----. 1 oracle oinstall 114 Jul 8 14:30 oraInstall2013-07-08_02-18-05PM.out
Questions:
Has anyone encountered the same problem and managed to resolve it?
Is this configuration essential to install/run the database?
Without closing the installer, try to do retry. It should work second time.
Related
I've been handed a SQL Server 2019 which should have CU15 installed. It has Integration Services installed and we use it for running SSIS jobs.
Looking at the assemblies on the disk we see a lot of this file version
2019.150.2000.5
So, I went over to this nice web page KB4518398 - SQL Server 2019 build versions and looking into the different file versions on specific assemblies.
Specifically I can see that we have a crash in odbcdest.dll and so I've concluded the the file version of this file (located in D:\Program Files\Microsoft SQL Server\150\DTS\PipelineComponents\ which is the 64-bit compiled version of that assembly) is also
2019.150.2000.5
which at least is logical.
But looking at the page from Microsoft referred in this question there have been a lot of updates in the different CU:s from the release of the RTM version. I've put together this list of all changes to odbcdest.dll from that page:
RTM/CU Date Version Size Link
------ ----- ------- ---- -------
RTM 2019-11-04 2019.150.2000.5
CU01 2020-01-07 2019.150.4003.23 376424 https://support.microsoft.com/en-us/topic/kb4527376-cumulative-update-1-for-sql-server-2019-a8dae09e-96b5-9f13-9092-977341fafe17
CU02 2020-02-03 2019.150.4013.40 369752 https://support.microsoft.com/en-us/topic/kb4536075-cumulative-update-2-for-sql-server-2019-1c344add-96bd-0810-433e-f7f9326c393c#file
CU03 2020-03-12 2019.150.4023.6 369544 https://support.microsoft.com/en-us/topic/kb4538853-cumulative-update-3-for-sql-server-2019-04829099-2b9f-863b-c8c1-aa82306a1ff4
CU04 2020-03-14 2019.150.4033.1 369752 https://support.microsoft.com/en-us/topic/kb4548597-cumulative-update-4-for-sql-server-2019-4b7b7c3f-0f14-3a9a-185c-3f973dabfe52
CU05 2020-06-10 2019.150.4043.16 316296 https://support.microsoft.com/en-us/topic/kb4552255-cumulative-update-5-for-sql-server-2019-084c602b-dc4a-d599-c857-5f18cec950fa
CU06 2020-07-25 2019.150.4053.23 316304 https://support.microsoft.com/en-us/topic/kb4563110-cumulative-update-6-for-sql-server-2019-757cb0fa-56ff-c6e4-d56b-a695b7fdc64e
CU07 2020-08-15 2019.150.4063.15 369552 https://support.microsoft.com/en-us/topic/kb4570012-cumulative-update-7-for-sql-server-2019-87ea390d-0def-6173-efd2-f6be8549d77d#bkmk_13585628
CU08 2020-09-13 2019.150.4073.23 316296 https://support.microsoft.com/en-us/topic/kb4577194-cumulative-update-8-for-sql-server-2019-ed7f79d9-a3f0-a5c2-0bef-d0b7961d2d72
CU09 2021-01-25 2019.150.4102.2 369552 https://support.microsoft.com/en-us/topic/kb5000642-cumulative-update-9-for-sql-server-2019-97ad5c3e-e002-4b6d-b566-698bf70ca44a#bkmk_13607161
CU10 2021-03-25 2019.150.4123.1 316304 https://support.microsoft.com/en-us/topic/kb5001090-cumulative-update-10-for-sql-server-2019-b6b696ec-6598-48d9-80ee-f1b85d7a508b
CU11 2021-05-27 2019.150.4138.2 316296 https://support.microsoft.com/en-us/topic/kb5003249-cumulative-update-11-for-sql-server-2019-657b2977-a0f1-4e1f-8b93-8c2ca8b6bef5
CU12 2021-07-19 2019.150.4153.1 316296 https://support.microsoft.com/en-us/topic/kb5004524-cumulative-update-12-for-sql-server-2019-45b2d82a-c7d0-4eb8-aa17-d4bad4059987
CU13 2021-09-23 2019.150.4178.1 369552 https://support.microsoft.com/en-us/topic/kb5005679-cumulative-update-13-for-sql-server-2019-5c1be850-460a-4be4-a569-fe11f0adc535#bkmk_13981081
CU14 2021-11-03 2019.150.4188.2 316320 https://support.microsoft.com/en-us/topic/kb5007182-cumulative-update-14-for-sql-server-2019-67b00a61-4f30-4a36-a5db-b506c47e563b#bkmk_14253624
CU15 2022-01-22 2019.150.4198.2 369544 https://support.microsoft.com/en-us/topic/kb5008996-cumulative-update-15-for-sql-server-2019-4b6a8ee9-1c61-482d-914f-36e429901fb6
CU16 2022-04-11 2019.150.4223.1 317352 https://support.microsoft.com/en-us/topic/kb5011644-cumulative-update-16-for-sql-server-2019-74377be1-4340-4445-93a7-ff843d346896
So, obviously Microsoft has done some working during the time from the RTM release.
Now, to my question.
If CU15 was installed why is the file version of this assembly still reporting the file version of the RTM?
It seems to me that that assembly has not been updated att all despite that CU15 should have been installed.
If we install CU16 would that upgrade Integration Services files? I would then expect 2019.150.4223.1 as the file version of odbcdest.dll
Below are an error from the event log that seems to indicate a real problem.
Fault bucket 1530726703783532086, type 5
Event Name: SQLException64
Response: Not available
Cab Id: 0
Problem signature:
P1: ISServerExec.exe
P2: 0.0.0.0
P3: 0000000000000000
P4: OdbcDest.dll
P5: 2019.150.2000.5
P6: 000000005D8A80CE
P7: -1073741819
P8: 000000000001C8EB
P9: 0000000000000000
P10:
Attached files:
\\?\C:\Program Files\Microsoft SQL Server\150\Shared\ErrorDumps\ISServer_2774_92f5b77a-8b53-4703-ae89-d252652ca787_0.mdmp
\\?\C:\Program Files\Microsoft SQL Server\150\Shared\ErrorDumps\ISServer_2774_92f5b77a-8b53-4703-ae89-d252652ca787_0.mdmp
\\?\C:\Program Files\Microsoft SQL Server\150\Shared\ErrorDumps\ISServer_2774_92f5b77a-8b53-4703-ae89-d252652ca787_0.tmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5DF5.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E15.tmp.xml
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_ISServerExec.exe_182514701e9ac3cc1cb72270426a8a84197f3757_00000000_1051626a
Analysis symbol:
Rechecking for solution: 0
Report Id: 008c56b8-4633-42b4-8fb1-22555163e580
Report Status: 2147487744
Hashed bucket: 1a4563239b9578ef153e3bd3b338d636
Cab Guid: 0
If I wanted to know what version/patch level of SQL Server, I'd run the following query
SELECT SERVERPROPERTY('ProductVersion') AS ProductVersion, ##VERSION AS MyVersion;
15.0.4223.1
Microsoft SQL Server 2019 (RTM-CU16) (KB5011644) - 15.0.4223.1 (X64) Apr 11 2022 16:24:07 Copyright (C) 2019 Microsoft Corporation Express Edition (64-bit) on Windows 10 Enterprise 10.0 (Build 19044: ) (Hypervisor)
The assembly reflects that patch level.
I don't have an unpatched machine handy, but I think you'd have to explicitly not upgrade your SSIS componentry
I created a machine with 6 GB of memory, using Ubuntu 20, and installed the latest version of SQL Server Microsoft SQL Server:
(RTM-CU8) (KB4577194) - 15.0.4073.23 (X64)
Sep 23 2020 16:03:08
Copyright (C) 2019 Microsoft Corporation
Express Edition (64-bit) on Linux (Ubuntu 20.04.1 LTS)
Exporadically the system suffers a fatal failure and restarts, taking almost a minute to return. I cannot detect the real reason for the failure and what I could do to resolve it.
I already set the maximum memory limit to 4gb thinking that the system was overflowing the machine's limit. Help me please
This program has encountered a fatal error and cannot continue running
at Mon Dec 21 14:31:38 2020 The following diagnostic information is
available:
Reason: 0x00000006
Message: Kernel bug check
Address: 0x3fff86a3be90
Parameters: 0xca6e6e240
Stack Trace:
file://package4/windows/system32/sqlpal.dll+0x000000000030E7D9
file://package4/windows/system32/sqlpal.dll+0x000000000030C769
file://package4/windows/system32/sqlpal.dll+0x000000000023BEEB
file:///windows/System32/Drivers/Afd.sys+0x0000000000006385
file:///windows/System32/Drivers/Afd.sys+0x000000000000686F
file:///windows/System32/Drivers/Afd.sys+0x000000000000631A
file://package4/windows/system32/sqlpal.dll+0x00000000002412B6
file://package4/windows/system32/sqlpal.dll+0x0000000000202FE2
file://package4/windows/system32/sqlpal.dll+0x0000000000347898
file:///Windows/system32/mswsock.dll+0x00000000000015EC
file:///Windows/SYSTEM32/WS2_32.dll+0x000000000000A6BE
file:///binn/sqllang.dll+0x00000000003C90B6
file:///binn/sqllang.dll+0x00000000003C9854
file:///binn/sqllang.dll+0x00000000000149CD
file:///binn/sqllang.dll+0x0000000000014DBA
file:///binn/sqllang.dll+0x00000000001FA73B
file:///binn/sqllang.dll+0x00000000001FA663
file:///binn/sqllang.dll+0x00000000001FA0EF
file:///binn/sqldk.dll+0x0000000000009FF3
file:///binn/sqldk.dll+0x000000000000A92D
file:///binn/sqldk.dll+0x000000000000A51E
file:///binn/sqldk.dll+0x00000000000217F2
file:///binn/sqldk.dll+0x000000000002215C
file:///binn/sqldk.dll+0x0000000000021F53
file:///Windows/SYSTEM32/KERNEL32.DLL+0x0000000000014414
file:///windows/system32/ntdll.dll+0x0000000000075541
+0x00000000E7E27000
Process: 90917 - sqlservr
Thread: 99182 (application thread 0x2c34)
Instance Id: 8638650d-adf3-4e7e-8b1b-6cdecd05544c
Crash Id: 43334ff2-47c7-4fb5-a22e-16f4e0728252
Build stamp: 98b2cf08cbfec4dc5f2c5d0e2a892c88d339a4da408744f2baf39941a977fa3c
Distribution: Ubuntu 20.04.1 LTS
Processors: 4 Total Memory: 6234537984 bytes
Timestamp: Mon Dec 21 14:31:38 2020
Last errno: 11 Last errno text: Resource temporarily unavailable Ubuntu 20.04.1 LTS Capturing core dump and information to
/var/opt/mssql/log... #033[0;1;39mHint: You are currently not seeing
messages from other users and the system.#033[0m #033[0;1;39m
Users in groups 'adm', 'systemd-journal' can see all messages.#033[0m
#033[0;1;39m Pass -q to turn off this notice.#033[0m #033[0;1;31mNo journal files were opened due to insufficient permissions.#033[0m #033[0;1;39mHint: You are currently not seeing
messages from other users and the system.#033[0m #033[0;1;39m
Users in groups 'adm', 'systemd-journal' can see all messages.#033[0m
#033[0;1;39m Pass -q to turn off this notice.#033[0m #033[0;1;31mNo journal files were opened due to insufficient permissions.#033[0m /usr/bin/tail: cannot open '/var/log/syslog' for
reading: Permission denied Mon 21 Dec 2020 02:31:40 PM -03 Capturing
program information Mon 21 Dec 2020 02:31:42 PM -03 Attempting to
capture a dump with paldumper for pid 90917
I'm trying to connect to an Oracle Cloud Database using the instant client from a CentOS 7 machine.
I created the databases in the OCI interface, I downloaded the wallet files and created one user with the DWROLE role.
I installed the bellow packages on the system
oracle-instantclient19.8-basic-19.8.0.0.0-1.x86_64.rpm
oracle-instantclient19.8-devel-19.8.0.0.0-1.x86_64.rpm
oracle-instantclient19.8-sqlplus-19.8.0.0.0-1.x86_64.rpm
oracle-instantclient19.8-tools-19.8.0.0.0-1.x86_64.rpm
I created set the bellow folders and set the env vars
export ORACLE_HOME=/usr/lib/oracle/19.8/client64
export TNS_ADMIN=$ORACLE_HOME/network/admin
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib
export PATH=$PATH:$ORACLE_HOME/bin
then I unzipped the wallet files to TNS_ADMIN
[root#workvm admin]# ll
total 40
-rw-r--r-- 1 root root 6733 Sep 17 2020 cwallet.sso
-rw-r--r-- 1 root root 6688 Sep 17 2020 ewallet.p12
-rw-r--r-- 1 root root 3276 Sep 17 2020 keystore.jks
-rw-r--r-- 1 root root 691 Sep 17 2020 ojdbc.properties
-rw-r--r-- 1 root root 317 Sep 17 2020 README
-rw-r--r-- 1 root root 114 Sep 17 2020 sqlnet.ora
-rw-r--r-- 1 root root 1813 Sep 16 14:18 tnsnames.ora
-rw-r--r-- 1 root root 3336 Sep 17 2020 truststore.jks
[root#workvm admin]# pwd
/usr/lib/oracle/19.8/client64/network/admin
The tnsnames.ora files have some autogenerated services defined
otakudb_high = (description= (retry_count=20)(retry_delay=3)(address=(protocol=tcps)(port=1522)(host=...)
otakudb_low = (...)
otakudb_medium = (...)
According to what I have read, I should be able to connect to the database by executing
sqlplus metalbob#otakudb_high
However, when I run it the connection halts and then errors out with the following message
[donhk#workvm ~]$ sqlplus metalbob#otakudb_high
SQL*Plus: Release 19.0.0.0.0 - Production on Wed Sep 16 14:01:52 2020
Version 19.8.0.0.0
Copyright (c) 1982, 2020, Oracle. All rights reserved.
Enter password:
ERROR: ORA-28791: certificate verification failure
[donhk#workvm ~]$
What is the correct procedure to connect to the remote database?
Edit after Joe answer:
This is how my sqlnet.ora file was prior to the changes
WALLET_LOCATION = (SOURCE = (METHOD = file) (METHOD_DATA = (DIRECTORY="?/network/admin")))
SSL_SERVER_DN_MATCH=yes
This is how I changed to make it work after joe answer
NAMES.DIRECTORY_PATH= (TNSNAMES)
WALLET_LOCATION = (SOURCE = (METHOD = file) (METHOD_DATA = (DIRECTORY="?/network/admin")))
SSL_SERVER_DN_MATCH=yes
There is no need to change the DIRECTORY, the trick was this
NAMES.DIRECTORY_PATH= (TNSNAMES)
Hope this helps someone!
Edit 2
I realized that after I bounced the machine, I was able to connect, maybe it was a network problem on the machine or a library not properly loaded
I wrote this up last week in How to connect to Oracle Autonomous Cloud Databases.
You can edit sqlnet.ora if you don't have the config files in the default network/admin directory. If they are in that directory then you don't need to edit it, because the pre-supplied path "?/network/admin" maps to the network/admin subdirectory under where the libclntsh.so file is.
The other alternative is to use "Easy Connect Plus" syntax like:
tcps://adb.ap-sydney-1.oraclecloud.com:1522/abc_cjjson_high.adb.oraclecloud.com?wallet_location=/Users/cjones/Cloud/CJJSON
Extract cwallet.so from the wallet zip, and stick it in a directory (I used /Users/cjones/Cloud/CJJSON). Then find the host, servicename, port etc from the wallet tnsnames.ora file and build up your easy connect string. Then you can 'throw away' the zip file since it is not needed :)
How to uninstall everything: mvfs, all services, albd, all files and folders?
For information a cleartool hostinfo -properties gives:
ClearCase 8.0.1.4 (AIX 1 7)
Scaling factor to initialize MVFS cache sizes: 24
MVFS cache sizes:
Free mnodes: 13967
Free mnodes for cleartext: 13967
File names: 20000
Directory names: 5000
Names not found: 20000
RPC handles: 240
Initial mnode table size: 63488
Blocks per directory: 6
Minimum free mnodes: 12570
Minimum free mnodes for cleartext: 13167
Cleartext idle lifetime: 259200
VOB hash table size: 8192
Cleartext hash table size: 2048
DNC hash table size: 4507
Thread hash table size: 511
Process hash table size: 511
Installed product: MultiSite version 8.0.1.1 (Fri Sep 20 16:09:14 EDT 2013) (8.0.1.01.00_2013C.FCS)
Installed product: MultiSite version 8.0.1.2 (Wed Dec 11 16:09:14 EDT 2013) (8.0.1.02.00_2013D.FCS)
Installed product: MultiSite version 8.0.1.3 (Wed Mar 19 00:31:17 EST 2014) (8.0.1.03.00_2014A.FCS)
Installed product: MultiSite version 8.0.1.3-iFix01 (Tue Apr 22 18:14:02 EDT 2014) (8.0.1.03.01_2014A.1.FCS)
Installed product: MultiSite version 8.0.1.04 (Wed Jun 11 00:31:23 EDT 2014) (8.0.1.04.00_2014B.D140610)
Installed product: ClearCase version 8.0.1.1 (Fri Sep 20 16:09:14 EDT 2013) (8.0.1.01.00_2013C.FCS)
Installed product: ClearCase version 8.0.1.2 (Wed Dec 11 16:09:14 EDT 2013) (8.0.1.02.00_2013D.FCS)
Installed product: ClearCase version 8.0.1.3 (Wed Mar 19 00:31:17 EST 2014) (8.0.1.03.00_2014A.FCS)
Installed product: ClearCase version 8.0.1.3-iFix01 (Tue Apr 22 18:14:02 EDT 2014) (8.0.1.03.01_2014A.1.FCS)
Installed product: ClearCase version 8.0.1.04 (Wed Jun 11 00:31:23 EDT 2014) (8.0.1.04.00_2014B.D140610)
This was installed via IBM installation Manager (IM), are you unable to uninstall it via Installation Manager? Most people try to use the GUI interface to IM, but if
there isn't enough XWindows installed, or
some of the GUI libraries are the wrong versions for the Eclipse shell to start, or
You are using telnet (Odd, but you can) or SSH without X forwarding,
you may get some "helpful" error messages. You can use the "imcl" command to do this from a terminal session by (note these paths are DEFAULT, and may not match your setup as a result) running:
/opt/IBM/InstallationManager/eclipse/tools/imcl -c
And following the prompts to remove that version of ClearCase. I recall CC 8.0.1 allows removal on the command line for this very reason. (Installing, upgrading, and uninstalling on Unix hosts without requiring X or X-forwards.)
I followed the instructions on https://ctors.net/2015/07/14/solr5_java8_debian8.
As the root
First I installed Java 8:
mkdir -p /opt/java
wget --no-cookies --no-check-certificate --header "Cookie: gpw_e24=http%3A%2F%2Fwww.oracle.com%2F; oraclelicense=accept-securebackup-cookie" "http://download.oracle.com/otn-pub/java/jdk/8u45-b14/jdk-8u45-linux-x64.tar.gz"
tar xvf jdk-8u45-linux-x64.tar.gz -C /opt/java
update-alternatives --install /usr/bin/java java /opt/java/jdk1.8.0_45/bin/java 1
update-alternatives --set java /opt/java/jdk1.8.0_45/bin/java
Then I installed Solr:
wget http://apache.belnet.be/lucene/solr/5.2.1/solr-5.2.1.tgz
tar xvf solr-5.2.1.tgz
./solr-5.2.1/bin/install_solr_service.sh solr-5.2.1.tgz
But the installation ends up with the following error message:
solr.service - LSB: Controls Apache Solr as a Service
Loaded: loaded (/etc/init.d/solr)
Active: failed (Result: exit-code) since Wed 2015-11-18 02:29:36 TMT; 5s ago
Process: 1679 ExecStart=/etc/init.d/solr start (code=exited, status=1/FAILURE)
Nov 18 02:29:36 solrhost su[1681]: Successful su for solr by root
Nov 18 02:29:36 solrhost su[1681]: + ??? root:solr
Nov 18 02:29:36 solrhost su[1681]: pam_unix(su:session): session opened for user solr by (uid=0)
Nov 1`enter code here`8 02:29:36 solruser solr[1679]: This script requires extracting a WAR file with either the jar or unzip utility, please install these utilities or con...assistance.
Nov 18 02:29:36 solrhost su[1681]: pam_unix(su:session): session closed for user solr
Nov 18 02:29:36 solrhost systemd[1]: solr.service: control process exited, code=exited status=1
Nov 18 02:29:36 solrhost systemd[1]: Failed to start LSB: Controls Apache Solr as a Service.
Nov 18 02:29:36 solrhost systemd[1]: Unit solr.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.
Service solr installed.
Does anyone have any idea what is going on?
solr needs unzip to work. Install unzip if it isn't available on the system.
apt-get install unzip
It should fix the problem.
I got my colleague to have a look at the issue. He found two causes of error:
1) Insufficient memory (my box had 512 MB RAM memory). Additional memory resolved the issue.
2) Wrong jdk package, that is, wrong architecture choice. For different JDK packages look here: http://www.oracle.com/technetwork/java/javase/downloads/java-se-6u24-download-338091.html.
Hope someday this will save someone else's time and nerves.
As for Debian and Solr developers, it would be great if you could come up with simple receipt about how to install Solr 5 under Debian 8. For example, https://www.digitalocean.com/community/tutorials/how-to-install-solr-5-2-1-on-ubuntu-14-04.