I have an Enterprise Oracle Database 12.2.0.1.0 installed. The output of 'show compatible' is 12.2.0.1.4.
When I try to run EXPDP with the correct credentials, I get the following error:
Connected to: Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production
ORA-39001: invalid argument value
ORA-39021: Database compatibility version 12.2.0.1.4 is not supported.
After which EXPDP exists.
Should EXPDP's version be aligned with the 'compatible' parameter?
Related
Please could someone help me on similar/same issue as in this TOPIC - SSIS package that connects to an oracle DB using Attunity Connection Manager
My environment situation is:
DEV Virtual Machine: VS2019 Version 16.8.1 (Microsoft SQL Server Integration Services Designer Version 15.0.2000.132)
DEV SQL Sever: 2017 DEV (Microsoft SQL Server 2017 (RTM-CU22) (KB4577467) - 14.0.3356.20 (X64))
I have installed:
LINK Microsoft Connectors v5.0 for Oracle and Teradata ATTUNITY
(as i need SQL 2017 compatibility)
and
LINK Microsoft Connector for Oracle V1.0
(I have tried multiple time installing only 32 or only 64 versions, and uninstalling and restarting VMs)
I have SSIS package with Oracle Connection Manager.
In Visual Studio inside package:
IF SQL Target version is SQL 2019
Connection manager to oracle test: SUCCESS
Run Package: SUCCESS
Deply Package to SSIS DB: Fail (Reasonable -> I have SQL 2017 :)
IF SQL Target version is SQL 2017
Connection manager to oracle test: SUCCESS
Run Package: FAIL
ERROR in DEBUG MODE:
[OMS OrderLines ABBICS V_F_ORDERS_RO24881SRU 3] Error: The
AcquireConnection method call to the connection manager Oracle DB
failed with error code 0x80004005. There may be error messages posted
before this with more information on why the AcquireConnection method
call failed.
[SSIS.Pipeline] Error: OMS OrderLines ABBICS V_F_ORDERS_RO24881SRU
failed validation and returned error code 0x80004005.
Error: The ORACLE registry key cannot be opened. Verify that the Oracle Client for Windows x86 is installed properly.
Deply Package to SSIS DB: SUCCESS
Run Package on SQL Server (from SSIS Catalog or from JOB): FAIL -> Basically same errors as in package
I have tried running packages in 64 and 32 bit mode as well as running job in 32 bit mode. The only difference was
...Windows x86 is installed properly...
or
...Windows x64 is installed properly...
Thank you!
Wojciech
Finally I was able to solve that uninstalling everything and install what i mentioned in post above plus:
32-bit Oracle Data Access Components (ODAC) with Oracle Developer Tools for Visual Studio
ODAC 12.2c Release 1 and Oracle Developer Tools for Visual Studio (12.2.0.1.1)
https://www.oracle.com/database/technologies/dotnet-utilsoft-downloads.html
This fixed issue and package can be run in both 32 and 64 bit mode
The only question that remains, do i really need to install this whole package with unnecessary (for me) features? Now i have to install it on all DEV/UAT/PROD nodes :/ Is there any particular component I can install to get this up and running?
EDIT: To minimize installation components - >On machines with SQL server 2017 I did following things:
Downloaded 64-bit ODAC 12.2c Release 1 (12.2.0.1.0) Xcopy for Windows x64
(ODAC122010Xcopy_x64.zip) from LINK
Unzipped File on SQL VM
Run CMD as admin, navigate to unzipped location and run
install.bat basic F:\ORACLE myhome false true
This will install Oracle Instant Client Machine Wide
Added to system variable PATH value: F:\ORACLE\
This allows me run SQL jobs successfully (remember to install other components mentioned in main post!)
Had this error while installing Oracle DB 12.1.0.2 Enterprise (64-bit) on a VM with Windows Server 2016 (64 bit OS) with all the Hard/Software requirements. The installer file was unzipped in the same parent folder but I changed the folder name to: Oracle Database 12c Release 1 64 Enterprise (12.1.0.2.0).
Error while executing
"C:/app/oracle/product/12.1.0/dbhome_1/rdbms/admin/dbmssml.sql". Refer to
"C:/app/oracle/cfgtoollogs/dbca/orcl/dbmssml0.log" for more details. Error in
Process: C:/app/oracle/product/12.1.0/dbhome_1/perl/bin/perl.exe
The dbmssml0.log file is empty. Then the installer threw a:
[INS-20802] Oracle Database Configuration Assistant failed.
Cause - The plug-in failed in its perform method
Action - Refer to the logs or contact Oracle Support Services.
Log File Location
C:\Program Files\Oracle\Inventory\logs\installActions2020-08-03_03-57-18PM.log
Here is the installation log.
I'm a new Oracle user and I'm not sure how to read the log or locate the error, please let me know if need any additional details. Thanks in advance.
Regards,
Heber
Oracle 12.1 is not certified on Windows 2016, per the Database Installation Guide. But Oracle 12.2 is supported on Windows 2016.
There's a big difference between 12.1 and 12.2. Make sure you're always looking at the right version of the documentation.
This is probably a trendy question, But I promise you my problem is different.
Lately my server windows crashed and I was forced to install new windows.
I took a backup of the database "ReportServer" and "ReportServerTempDB".
Until then I didn't remember the SQL Server version was installed before the windows crashed.
Now when I try to attach these databases and run the report server, it tells me the following message
"The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is '163'. The expected version is '162'. (rsInvalidReportServerDatabase)"
I've made some research, and understood that my current installed SQL Server version is higher than the database, I tried installing some cumulative updates but when I run the updates it seems not to be recognizing the SQL Server version installed.
Current installed version: Microsoft SQL Server Enterprise: Core-based Licensing (64-bit) 2014 v12.0.2000.8
Previously installed version: Microsoft SQL Server 2012 Enterprise Not sure though.
My problem is that I can't open the ReportServer database because it's version is older and I can't install the right cumulative update to fix this issue. Can anyone point me to the right direction?
Much appreciated Thanksss!!.
My computer's operating system is Windows 7 64-bit. I just downloaded and install Oracle Express 11g Windows 64-bit. During installation it ask me to set password for both the SYS and the SYSTEM database accounts which I provide as P#ssword1. Everything went ok during installation.
Now I want to connect using SQL Plus. So I click on All Programs --> Oracle Database 11g Express Edition --> Run SQL Command Line to open SQL Plus.
There I type in connect system/P#ssword1 and press Enter key. But I get this error message: ORA-12154: TNS:could not resolve the connect identifier specified
SQL*Plus: Release 11.2.0.2.0 Production on Wed Jan 18 22:19:11 2017
Copyright (c) 1982, 2014, Oracle. All rights reserved.
SQL> connect system/P#ssword1 ERROR: ORA-12154: TNS:could not resolve
the connect identifier specified
SQL>
Why I cannot connect?
Thanks
Since you are using P#ssword1 as the password
Can you try the following for connecting to DB instance through SQL*PLUS?
connect system/"P#ssword1"
The reason for Oracle to throw the error is that it treats ssword1 (P#ssword1) as the connect identifier.
I'm trying to upgrade from teamcity 6.5 to 7.1.4a.
I get into maintenance mode at startup where it helpfully informs me that there is a :
Version mismatch: Configuration version is 544 but Database version is 454.
Data Directory
Directory path: /opt/TeamCity-7.1.4a/.BuildServer exists
Database properties file exists
Internal database file exists
Database
Database type: ORACLE
Database connection URL: **
Server: Oracle Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production With the Partitioning and Automatic Storage Management options
Server version: 11.2
Driver: Oracle JDBC driver 11.2.0.1.0
Driver version: 11.2
Versions
Software version: 544
Data directory version: 544
Database version: 454
All handy information, but how do I actually upgrade it. A google seems to indicate I should hit the 'upgrade' button. The problem being there isn't one.
So how do I actually upgrade it?
That issue happens with mismatch version of external database. In my case help update and restore Teamcity:
Upgrading from 8.1.6 to 9.0.1, TeamCity 9.0.1 will ask to upgrade drivers to the latest version 5.1. If the MySQL server version is 5.5 or newer, the JDBC driver version should be 5.1.23 or newer.
Upgrade to: Connector/J 5.1.34; Teamcity 9.0; MySQL 5.6.22 (MySQL 5.0.33+, 5.1.49+, 5.5+ (Please note that due to bugs in MySQL, versions 5.0.20, 5.0.22 and 5.1 up to 5.1.34 are not compatible with TeamCity))
Have you seen this Configuration version is XXX but Database version is YYY
One of the solution is to drop all the tables in the databases.