I have an licensed Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Version 19.7.0.0.0. Furthermore I have another Oracle DB in a docker container that has been created as described in DockerFiles, whihc is 18.4.0 xe.
I want to transfer the schema/data from 19c to 18.4xe. I have used the following command to export the data from 19c:
expdp system/pwd#db DIRECTORY=export_dir_local SCHEMAS=MYSCHEMA CONSISTENT=yes EXCLUDE=statistics COMPRESSION=all VERSION=18.1.0 DUMPFILE=mydump.dmp LOGFILE=mydump.log
and then in the docker I import it by using
impdp system/pwd#localhost/xepdb1 directory=DUMP_DIR dumpfile=mydump.dmp exclude=STATISTICS LOGFILE=mydump.log
However when I run the command I receive the following error:
Import: Release 18.0.0.0.0 - Production on Wed Mar 3 19:15:39 2021
Version 18.4.0.0.0
Copyright (c) 1982, 2018, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 18c Express Edition Release 18.0.0.0.0 - Production
ORA-39002: invalid operation
while the log contains:
;;;
Import: Release 18.0.0.0.0 - Production on Wed Mar 3 19:15:39 2021
Version 18.4.0.0.0
Copyright (c) 1982, 2018, Oracle and/or its affiliates. All rights reserved.
;;;
Connected to: Oracle Database 18c Express Edition Release 18.0.0.0.0 - Production
Master table "SYSTEM"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
Job "SYSTEM"."SYS_IMPORT_FULL_01" successfully completed at Wed Mar 3 19:15:46 2021 elapsed 0 00:00:04
Job "SYSTEM"."SYS_IMPORT_FULL_01" successfully completed at Wed Mar 3 19:15:46 2021 elapsed 0 00:00:04
I have tried also to export it with COMPRESSION=NONO with the same error and by changing the version VERSION=18 or VERSION=18.4.0
but I receive the error:
Connected to: Oracle Database 18c Express Edition Release 18.0.0.0.0 - Production
ORA-39002: invalid operation
ORA-39358: Export dump file version 18.4.0 not compatible with target version 18.1.0.0.0
Furthermore in "show parameter compatible" I receive
NAME TYPE VALUE
----------------- ------- ------
compatible string 18.0.0
noncdb_compatible boolean FALSE
Any ideas? Thanks
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
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 am getting this error in the Icinga startup -
/pkgs/icinga/1.13.3.rhas5/bin/icinga /my-config/dit-icinga-app-master/config/icinga.cfg
Icinga 1.13.3
Copyright (c) 2009-2015 Icinga Development Team (http://www.icinga.org)
Copyright (c) 2009-2013 Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 07-15-2015
License: GPL
Icinga 1.13.3 starting... (PID=30807)
Local time is Fri Feb 05 16:45:17 EST 2016
idomod: IDOMOD 1.13.3 (07-15-2015) Copyright(c) 2005-2008 Ethan Galstad, Copyright(c) 2009-2015 Icinga Development Team (https://www.icinga.org)
idomod: Successfully connected to data sink. 0 queued items to flush.
Memory fault(coredump)
Log file does not reveal much
icinga.log
[1454708717] Icinga 1.13.3 starting... (PID=30807)
[1454708717] Local time is Fri Feb 05 16:45:17 EST 2016
[1454708717] LOG VERSION: 2.0
[1454708717] idomod: IDOMOD 1.13.3 (07-15-2015) Copyright(c) 2005-2008 Ethan Galstad, Copyright(c) 2009-2015 Icinga Development Team (https://www.icinga.org)
[1454708717] idomod: Successfully connected to data sink. 0 queued items to flush.
[1454708717] Event broker module 'IDOMOD' version '1.13.3' from '/pkgs/icinga_idoutils_libdbi_mysql/1.13.3/lib64/icinga/idomod.so' initialized successfully.
[1454708718] Event loop started...
icinga.log (END)
Icinga pre-flight check looks OK, so there is no issue with any of the configuration files.
Also, MySQL database is running on the node and I do see some data being inserted to it also in ido2db.debug logs.
Wondering where can I get more logs? Anybody has any leads? Appreciate your help.
Using Oracle impdp I'm getting error message:
UDI-00013 Message 13 not found
No message file for product=RDBMS, facility=UDI
How can I correct this?
You can get this error when your ORACLE_HOME environment variable is not set, or when it is set but not exported:
> unset ORACLE_HOME
> ORACLE_HOME=/dboracle/orabase/product/11.2.0.BTSP2
> impdp
UDI-00013: Message 13 not found; No message file for product=RDBMS, facility=UDI
UDI-00019: You may need to set ORACLE_HOME to your Oracle software directory
> export ORACLE_HOME
> impdp
Import: Release 11.2.0.3.0 - Production on Fri Mar 6 12:16:51 2015
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
Username:
If it's set, so you can see it with echo for example, make sure it is also exported with export ORACLE_HOME; you can also check which variables have been exported with export | grep ORACLE, so you can see if anything else is missing - maybe ORACLE_SID depending on your connect string.
These are usually set by an environment set-up script.
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.