Error converting SQL Server text field to Oracle CLOB

I am trying to convert an SQL Server DB to Oracle DB using DB link. The issue I am facing is one of the SQL Server table contains text field and we are trying to convert the text field to CLOB.
The error I am getting is "SQL Error: ORA-00997: illegal use of LONG datatype"
The statement is something like this.
Insert into oracle_table
Select col_1,col_2,col_3,col_4,col_5 from sql_table@sqldblink;
Please help.

Hi,
This is a known restriction involving long columns -
(1) LONG datatype not supported with use of DBLINK when insert or update involves a select statement
(2) LONG datatype cannot be used in a WHERE clause, in INSERT into ... SELECT ... FROM
constructs, and in snapshots.
The workround is to use a PL/SQL procedure or try the SQLPLUS COPY command.
If you have access to My Oracle Support then review these notes -
Cannot Move A Long From non Oracle database Ora-00997: Illegal Use Of Long Datatype (Doc ID 1246594.1)
How To Workaround Error: Ora-00997: Illegal Use Of Long Datatype (Doc ID 361716.1)
Regards,
Mike

Similar Messages

Converting SQL Server text field containing XML string to XI XML via JDBC

Hello
My client has a SQL Server database containing a field of type Text which contains an XML string e.g.
<DispatchJob> <DispatchDateTime>2003-09-29T13:29:15</DispatchDateTime> <AssignedFSE>F118</AssignedFSE> <DispatchJobPurchase> <DealerID>14C5</DealerID> <DateOfPurchase>1997-10-01T00:00:00</DateOfPurchase> </DispatchJob>
I am using JDBC to access this but could someone please recommend the best and easiest solution for converting this string to XI XML for subsequent mapping to BAPI or IDOC or ABAP Proxy and transmission to SAP. There are other fields as well in the database table so thoughts at the moment are to use a normal graphical message mapping followed by an XSL mapping. Will an XSL mapping be able to do this and if so is that the best solution?
Also I need to do the reverse of this and take fields coming from SAP via BAPI,IDOC etc. and convert them to a single database table field as an XML string also via the JDBC adapter. What is the best way to do this. Could it be done simply with functions in the graphical mapping e.g. concatenate?
Thank you in advance.
Trevor

Hi Michal
Thanks for the prompt reply.
I was anticipating XSLT for reading from the SQL Server database and converting the XML string.
But how would you convert the individual fields from SAP into a single field as an XML string for storing in the SQL Server database? What approach would you use?
Regards
Trevor

Error converting SQL Server DDL and views to Oracle

I am trying to convert SQL Serve 2008 on windows to Oracle 11g using SQL Developer 3.2.20.09. I am using the jtds-1.2.7 drivers to connect to SQL Server.
I have made several attempts to run the conversion and am getting the tables, indexes, and triggers converted with no issue. However, my Procedures and views are not coming across. All of them are giving similar errors as:
"Failed To Convert Stored Procedure get_compvision > esp3.dbo.get_compvision:unexpected end of subtree: Line 0 Column 0"
When I log into the source SQL Server environment using SQL Developer, I get an empty SQL Editor window with "null" when I try to {right-click -> "Open"} on the Procedure.
Logging into SQL Server Administrator as the same user I can see the source code, so the issue appears to be related to SQL Developer and not my user privleges. I am a dbo alias in SQL Server.
In addition, if I click on a view, I can see the data and metadata, but not the SQL that defines the view. I see tabs for column, data, triggers, and details.
In addition, if I go to the "capture" for my Migration project and drill down to procedures, I can see them listed, but each and every procedure gives me a "/* DDL not accesible */" error. I get teh same results for views, triggers and indexes.
Can someone help me? I have been googling for days!
Edited by: user4714217 on Jan 24, 2013 12:54 PM

SELECT v.vnd_c, CASE v.use_parent_addr_flg WHEN 0 THEN a.str_1 ELSE pa.str_1 END AS str_1,
CASE v.use_parent_addr_flg WHEN 0 THEN a.str_2 ELSE pa.str_2 END AS str_2,
CASE v.use_parent_addr_flg WHEN 0 THEN a.str_3 ELSE pa.str_3 END AS str_3,
CASE v.use_parent_addr_flg WHEN 0 THEN a.city ELSE pa.city END AS city,
CASE v.use_parent_addr_flg WHEN 0 THEN a.state ELSE pa.state END AS state,
CASE v.use_parent_addr_flg WHEN 0 THEN a.zipcode ELSE pa.zipcode END AS zipcode,
CAST((CASE v.use_parent_addr_flg WHEN 0 THEN (CASE a.foreign_flg WHEN 1 THEN 'Y' ELSE 'N' END)
ELSE (CASE pa.foreign_flg WHEN 1 THEN 'Y' ELSE 'N' END) END) AS char(1)) AS foreign_flg,
CASE v.use_parent_addr_flg WHEN 0 THEN a.country ELSE pa.country END AS country,
CASE v.use_parent_addr_flg WHEN 0 THEN a.cre_d ELSE pa.cre_d END AS cre_d,
CASE v.use_parent_addr_flg WHEN 0 THEN a.mod_d ELSE pa.mod_d END AS mod_d,
CASE v.use_parent_addr_flg WHEN 0 THEN a.mod_by ELSE pa.mod_by END AS mod_by
FROM dbo.om_vendor AS v LEFT OUTER JOIN
dbo.om_address AS a ON a.vnd_id = v.vnd_id AND a.addr_c = 1 INNER JOIN
dbo.om_owner AS o ON v.owr_id = o.owr_id INNER JOIN
dbo.om_address AS pa INNER JOIN
dbo.primary_vendors AS pv ON pa.vnd_id = pv.vnd_id ON o.part_id = pv.part_id
WHERE (pa.addr_c = 1)
WHICH TRANSLATES TO
SELECT v.vnd_c ,
CASE v.use_parent_addr_flg
WHEN 0 THEN a.str_1
ELSE pa.str_1
END str_1 ,
CASE v.use_parent_addr_flg
WHEN 0 THEN a.str_2
ELSE pa.str_2
END str_2 ,
CASE v.use_parent_addr_flg
WHEN 0 THEN a.str_3
ELSE pa.str_3
END str_3 ,
CASE v.use_parent_addr_flg
WHEN 0 THEN a.city
ELSE pa.city
END city ,
CASE v.use_parent_addr_flg
WHEN 0 THEN a.STATE
ELSE pa.STATE
END STATE ,
CASE v.use_parent_addr_flg
WHEN 0 THEN a.zipcode
ELSE pa.zipcode
END zipcode ,
(CASE v.use_parent_addr_flg
WHEN 0 THEN (CASE a.foreign_flg
WHEN 1 THEN 'Y'
ELSE 'N'
END)
ELSE (CASE pa.foreign_flg
WHEN 1 THEN 'Y'
ELSE 'N'
END)
END) foreign_flg ,
CASE v.use_parent_addr_flg
WHEN 0 THEN a.country
ELSE pa.country
END country ,
CASE v.use_parent_addr_flg
WHEN 0 THEN a.cre_d
ELSE pa.cre_d
END cre_d ,
CASE v.use_parent_addr_flg
WHEN 0 THEN a.mod_d
ELSE pa.mod_d
END mod_d ,
CASE v.use_parent_addr_flg
WHEN 0 THEN a.mod_by
ELSE pa.mod_by
END mod_by
FROM om_vendor v
LEFT JOIN om_address a
ON a.vnd_id = v.vnd_id
AND a.addr_c = 1
JOIN om_owner o
ON v.owr_id = o.owr_id
JOIN om_address pa
JOIN primary_vendors pv
ON pa.vnd_id = pv.vnd_id
ON o.part_id = pv.part_id
WHERE ( pa.addr_c = 1 );
Edited by: user4714217 on Jan 24, 2013 1:43 PM

Converting SQL Server Stored Procedure to Oracle

Hi there,
I tried to use SwisSQL to convert my SQL Server stored procedure to Orcale without much success.
Is there anyone who could help me out with this?
My SQL Server Stored Procedure is:
CREATE PROCEDURE [dbo].[SP_BackgroundCheckRequest]
     --MASTER Table
     @MASTER_ID int,
     @PERSONNEL_ID int = NULL,
@DATE_OF_BIRTH datetime = NULL,
     @GENDER varchar(1) = NULL,
     @COUNTRY_OF_BIRTH varchar(3) = NULL,
@TOWN_OF_BIRTH varchar(100) = NULL,
     @STATE_OF_BIRTH varchar(50) = NULL,
     @CHECK_CATEGORY varchar(10) = NULL,
     @CHECK_TYPE varchar(10) = NULL,
     @PRIORITY varchar(10) = NULL,
     @PRIORITY_REASON varchar(100) = NULL,
     @SCREENING_LEVEL nchar(1) = NULL,
     @POSITION nchar(50) = NULL,
     @REQUEST_SOURCE varchar(60) = NULL,
     --NAME_TYPE Table
     @NAME_TYPE varchar(5) = NULL,
     @FAMILY_NAME varchar(50) = NULL,
     @FIRST_NAME varchar(50) = NULL,
     @MIDDLE_NAME varchar(50) = NULL,
     @TITLE varchar(10) = NULL,
     @PREFFERED_NAME varchar(40) = NULL,
     @PREVIOUS_NAME varchar(140) = NULL,
     --ADDRESS_TYPE Table
     @ADDRESS_TYPE varchar(10) = NULL,
     @ADDRESS_LINE_1 varchar(30) = NULL,
     @ADDRESS_LINE_2 varchar(30) = NULL,
     @ADDRESS_LINE_3 varchar(30) = NULL,
     @COUNTRY varchar(3) = NULL,
     @SUBURB varchar(50) = NULL,
     @STATE varchar(50) = NULL,
     @POSTCODE varchar(15) = NULL,
     @START_DATE varchar(10) = NULL,
     @END_DATE varchar(10) = NULL,
     --LICENSE_TYPE Table
     @LICENSE_TYPE varchar(5) = NULL,
     @LICENSE_AGENCY varchar(15) = NULL,
     @LICENSE_NUMBER varchar(100) = NULL,
     @LICENSE_SIGHTED varchar(1) = NULL,
     --PHONE_TYPE Table
     @TELEPHONE_TYPE varchar(5) = NULL,
     @TELEPHONE_NUMBER varchar(20) = NULL,
     @MOBILE_TYPE varchar(5) = NULL,
     @MOBILE_NUMBER varchar(20) = NULL,
     @EXTENSION_TYPE varchar(5) = NULL,
     @EXTENSION_NUMBER varchar(20) = NULL,
     --PASSPORT_TYPE Table
     @PASSPORT_TYPE varchar(5) = NULL,
     @PASSPORT_NUMBER varchar(50) = NULL,
     @PASSPORT_COUNTRY varchar(3) = NULL,
     @PASSPORT_SIGHTED varchar(1) = NULL
AS
BEGIN TRANSACTION
INSERT into MASTER (MASTER_ID, PERSONNEL_ID, DATE_OF_BIRTH, GENDER, COUNTRY_OF_BIRTH,
     TOWN_OF_BIRTH, STATE_OF_BIRTH, CHECK_CATEGORY, CHECK_TYPE, PRIORITY, PRIORITY_REASON,
     SCREENING_LEVEL, POSITION, REQUEST_SOURCE)
     VALUES (@MASTER_ID, @PERSONNEL_ID, @DATE_OF_BIRTH, @GENDER, @COUNTRY_OF_BIRTH,
     @TOWN_OF_BIRTH, @STATE_OF_BIRTH, @CHECK_CATEGORY, @CHECK_TYPE, @PRIORITY, @PRIORITY_REASON,
     @SCREENING_LEVEL, @POSITION, @REQUEST_SOURCE)
IF @@ERROR <> 0
BEGIN
     ROLLBACK
     RAISERROR ('Error inserting values into MASTER table!', 16, 1)
     RETURN
END
INSERT into NAME_TYPE (MASTER_ID,NAME_TYPE,FAMILY_NAME,FIRST_NAME,MIDDLE_NAME,TITLE)
     VALUES (@MASTER_ID,@NAME_TYPE,@FAMILY_NAME,@FIRST_NAME,@MIDDLE_NAME,@TITLE)
IF @@ERROR <> 0
BEGIN
     ROLLBACK
     RAISERROR ('Error inserting values into NAME_TYPE table!', 16, 1)
     RETURN
END
INSERT into ADDRESS_TYPE (MASTER_ID,TYPE,ADDRESS_LINE_1,ADDRESS_LINE_2,ADDRESS_LINE_3,
          COUNTRY,SUBURB,STATE,POSTCODE,START_DATE,END_DATE)
     VALUES (@MASTER_ID,@ADDRESS_TYPE,@ADDRESS_LINE_1,@ADDRESS_LINE_2,@ADDRESS_LINE_3,
          @COUNTRY,@SUBURB,@STATE,@POSTCODE,@START_DATE,@END_DATE)
IF @@ERROR <> 0
BEGIN
     ROLLBACK
     RAISERROR ('Error inserting values into ADDRESS_TYPE table!', 16, 1)
     RETURN
END
INSERT into LICENSE_TYPE (MASTER_ID,TYPE,AGENCY,NUMBER,SIGHTED_YN)
     VALUES (@MASTER_ID,@LICENSE_TYPE,@LICENSE_AGENCY,@LICENSE_NUMBER,@LICENSE_SIGHTED)
IF @@ERROR <> 0
BEGIN
     ROLLBACK
     RAISERROR ('Error inserting values into LICENSE_TYPE table!', 16, 1)
     RETURN
END
INSERT into PHONE_TYPE (MASTER_ID,TYPE,NUMBER)
     VALUES (@MASTER_ID,@TELEPHONE_TYPE,@TELEPHONE_NUMBER)
IF @@ERROR <> 0
BEGIN
     ROLLBACK
     RAISERROR ('Error inserting Telephone number into PHONE_TYPE table!', 16, 1)
     RETURN
END
IF ((@MOBILE_TYPE <> NULL) AND (@MOBILE_NUMBER <> NULL))
BEGIN
     INSERT into PHONE_TYPE (MASTER_ID,TYPE,NUMBER)
          VALUES (@MASTER_ID,@MOBILE_TYPE,@MOBILE_NUMBER)
     IF @@ERROR <> 0
     BEGIN
          ROLLBACK
          RAISERROR ('Error inserting Mobile number into PHONE_TYPE table!', 16, 1)
          RETURN
     END
END
IF ((@EXTENSION_TYPE <> NULL) AND (@EXTENSION_NUMBER <> NULL))
BEGIN
     INSERT into PHONE_TYPE (MASTER_ID,TYPE,NUMBER)
          VALUES (@MASTER_ID,@EXTENSION_TYPE,@EXTENSION_NUMBER)
     IF @@ERROR <> 0
     BEGIN
          ROLLBACK
          RAISERROR ('Error inserting Extension number into PHONE_TYPE table!', 16, 1)
          RETURN
     END
END
INSERT into PASSPORT_TYPE (MASTER_ID,NUMBER,COUNTRY,SIGHTED_YN)
     VALUES (@MASTER_ID,@PASSPORT_NUMBER,@PASSPORT_COUNTRY,@PASSPORT_SIGHTED)
IF @@ERROR <> 0
BEGIN
     ROLLBACK
     RAISERROR ('Error inserting values into PASSPORT_TYPE table!', 16, 1)
     RETURN
END
COMMIT

First, a basic concept. That also illustrates how different Oracle is (and PL/SQL) from SQL-Server (and T-SQL).
PL/SQL integrates two different languages. The PL language. The SQL language. It allows you to code SQL source code natively inside the PL language. The PL compiler is clever enough to do the rest - make calls to the SQL engine to create SQL cursors, bind PL variable values to bind variables in the SQL code. Etc.
PL is a "proper" programming language. It is much like Pascal (it is based on Ada, a close family member of Pascal). It is nothing at all like T-SQL.
Okay, now for the very basic rule for Oracle development.
Maximize SQL. This means using the SQL language to crunch data. It is the "closest" to the data. It is designed and optimised for dealing with data. Do your data processing using SQL.
Minimize PL/SQL. This means using the PL language not to crunch data, but to provide the conditional logic. Implement business rules. And then have the SQL language crunch the data as the data processing language.
Attempting to directly translate T-SQL code into PL/SQL is flawed. It is like trying to make coffee with teabags. Yeah, the tea may have caffeine it, but it is not coffee.
To do what that T-SQL script does, insert a row into a table, a typical PL/SQL equivalent will look as follows:
create or replace procedure InsertMaster( masterRow master%rowtype ) authid definer is
.. types and variables declared here
begin
-- masterRow is a record structure that matches the actual MASTER table
.. apply business rules and validation to the data.. raising user exceptions as needed
-- e.g. the POSITION column must be upper case
masterRow.position := upper(masterRow.position);
-- after the business logic and data validation we can add the row to the table
-- (PL will make the INSERT call to the SQL engine)
insert into master values masterRow;
end;No commit. The caller does the business transaction. It needs to decide when to commit to maintain the integrity of the data in the database. It may need to do several more calls, before committing.
With this approach, we can give the application schema (the caller) execute privs on this procedure. This procedure is defined with definer rights. This means it runs with the privs of owner of that procedure and MASTER table. It is trusted code. It does all the correct stuff to add a valid and checked row to the MASTER table. So we give the app schema execute privs on the procedure and no insert priv on the MASTER table.
The only way the caller can add row to the MASTER table is via this trusted procedure of ours.
And this is a typical approach in Oracle - using the PL/SQL (both PL language and SQL language) code to create an interface to a logical database in Oracle. Abstracting the complexities of SQL from the caller. Moving business and validation into PL. Allowing us the flexibility of modifying business and validation logic, without touching a single byte of caller/client code. Allowing us to manage and tune SQL performance without dealing with (badly designed and coded) SQL from a client - as the SQL resides in PL/SQL packages and procedures and functions.

How to convert SQL server stored procedures to Oracle 11g

Hi Experts,
In SQL server 30 stored procedures are there how to convert all the stored procedure
from SQL server to Oracle 11g.
Please help me,
Thanks.

ramya_162 wrote:
In SQL server 30 stored procedures are there how to convert all the stored procedure
from SQL server to Oracle 11g.
The single most fundamental concept you need to understand (grok in its fullness) is:
ORACLE IS NOT SQL-SERVER
There is very little, to NOTHING, in common between T-SQL (a language extension to SQL) and PL/SQL (integration of SQL with the language Ada, part of ALGOL family of languages that includes Pascal and C++).
So taking a T-SQL procedure and porting it as is to PL/SQL is plain stupid.
Why?
Oracle sucks at trying to be SQL-Server.
So how do you migrate from SQL-Server to Oracle?
By taking the REQUIREMENTS that the T-SQL procedures address, and addressing these requirements using Oracle SQL and PL/SQL.

Error migrating SQL Server 2000 database to Oracle.

Hi,
I am new in SQL Developer.
I read most of the help manuals available on the net.
I am able to create connections to both SQL Server and Oracle database.
I am also able to create the migration repository on the Oracle database.
SQL server connection - TestSQL
Oracle database connection - TestOracle
Migration Repository - Migration_Repository.
Here is the problem am facing:
When I start Migrate to Oracle wizard, by right clicking the TestSQL database, I followed all the required steps and enter the necessary information. -
It starts creating the project - say, TEST but after that it gave the following error:
Migration actions have failed. Check the migration report for more details. : ORA-01400: cannot insert null into ("MIGRATIONS"."MD_PROJECT_ID").
Please help.

Thanks for your reply.
You are correct, there were some permission missing on the migration repository user.
I have given permissions and it worked fine.
but I can say that required permission mentioned in other posts and blogs on the Internet are not sufficient.
One has to provide more admin priviligies to this user.

Migration Workbench is messing up data in converted from SQL Server image fields.

I am working on porting a SQL Server 7 database to Oracle 8i (8.1.6 release 2). In the SQL Server database I have several tables that contain image fields that hold binary data (like Word documents, and other files). When I port the database to Oracle, the data in these fields gets garbled (the resultant records contain the correct amount of data (bytes), yet the data is different). Data in image fields that contain text oriented data ports correctly (i.e. if you just saved a long string in the field). Has anyone else posted a similar problem? Is there a workaround here to get the data stored in these image fields to port correctly?

The thing is DDL of SQL Server and Oracle are quite different, without the help of MW from SQL Developer. You can't convert SQL server version of DDL to Oracle version. Of course you can accomplish the same thing using other tools like ERwin and Visio. Since SQL Developer is free why bother?

How to convert SQL Server hierarchical query (CTE) to Oracle?

How to convert SQL Server hierarchical query (CTE) to Oracle?
WITH cte (col1, col2) AS
SELECT col1, col2
FROM dbo.[tb1]
WHERE col1 = 12
UNION ALL
SELECT c.col1, c.col2
FROM dbo.[tb1] AS c INNER JOIN cte AS p ON c.col2 = p.col1
DELETE a
FROM dbo.[tb1] AS a INNER JOIN cte AS b
ON a.col1 = b.col1

See: http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_10002.htm#i2129904
Ah, just spotted it's a delete statement - you won't be able to do it using subquery factoring in Oracle.
I had a go at trying to convert for you, but notice that you reference the cte from inside the cte... I can only assume you have a table called cte too...
DELETE FROM dbo.tb1
WHERE col1 = 12
OR col2 IN (SELECT col1 FROM cte)
Edited by: Boneist on 22-Jun-2009 09:19

Converting SQL Server 2000 to Oracle 9i

Hi,
I am working on the migration of stored procs from a SQL Server 2000 database to Oracle 9i. The sqlsrvr db contains 75 relatively complex procs using temporary tables to create intermediate resultsets for further processing.
The Oracle 9i environment has very strictly standards and temporary tables are not allowed.
Is it standard practice to use PL/SQL tables to simulate the functionality of temp tables?
I understand you can now use SQL against PL/SQL tables under certain circumstances.
I would envisage using the PL/SQL tables in multi-table joins with schema tables.
Any ideas whether I am going down the wrong path.
Thanks in advance,
Garrett Donnelly

Garrett,
Note that there is also an parser option to 'Generate8i temp tables', where the data in the permanent tables is seperated from other sessions by the use of an extra Session id colum.
Please post the results of your PL/SQL table experiences.
Regards,
Turloch
Oracle Migration Workbench Team

Migrating SQL Server 6.5 to Oracle 8

Hi,
I am currently converting some stored procedures from SQL Server 6.5 to Oracle 8 (PL/SQL). I am having trouble converting some nested sql statements such as the following to work in Oracle.
Example :
SELECT antall=COUNT(*), ulest=(SELECT ulest=COUNT(*) FROM soknad s, annonse
a WHERE a.kundeid=13817 AND s.annonseid=a.id and lest != '1') FROM soknad s,
annonse a WHERE a.kundeid=13817 AND s.annonseid=a.id
The Select is first getting a count on the two tables for a particular id, the second field in the statement has a nested select which does a similar count but has a further condition on it.
It could be done using two SELECT statements like this -
SELECT COUNT(*) AS antall
FROM soknad s, annonse a
WHERE a.kundeid = 13817
AND s.annonseid = a.id
SELECT COUNT(*)
FROM soknad s, annonse a
WHERE a.kundeid=13817
AND s.annonseid=a.id
AND lest != '1'
which may be workable but I would like to keep it as similar to the original as much as possible.
Any ideas would be great!
Thanks,
Brad

I have since found out subqueries in the select list are not supported by Oracle.
Brad
null

Migration from SQL Server 7.0 to Oracle 8.0.5

Can we migrate from SQL Server 7.0 to Oracle 8.0.5 directly without being converted to Oracle 8i objects

Hi,
U can convert from sql server to Oracle 8 but u've to look after the stored procedures in mssql server. If the stored procedures contains any temporary table concepts and resultset then some manual changes are required.
Thanx,
Durai.
null

Error in SQL server BCP LKM

Hi,
I am trying to load data from SQL server 2008 database to Oracle using ODI(LKM - MSSQL to ORACLE (BCP/SQLLDR).It is throwing error in the following command-
OdiOSCommand -ERR_FILE=C:\Users\SKUMAR~1.ADD\AppData\Local\Temp\X280101.out.err -OUT_FILE=C:\Users\SKUMAR~1.ADD\AppData\Local\Temp\X280101.out.log
bcp BHOOMI.dbo.C$_0MST_ACQUIDES out C:\Users\SKUMAR~1.ADD\AppData\Local\Temp\X280101.bcp -c -S -Usource -P<@=snpRef.getInfo("SRC_PASS") @> -t\b
I am using a Windows 7 machine. Please advise.
Regards,
Rashmik

Whats the error you are getting?

How to call a sql server stored procedure from oracle

Hi all,
Please anybody tell me how to call a sql server stored procedure from oracle.
I've made an hsodbc connection and i can do insert, update, fetch data in sql server from oracle. But calling SP gives error. when I tried an SP at oracle that has line like
"dbo"."CreateReceipt"@hsa
where CreateReceipt is the SP of sql server and hsa is the DSN, it gives the error that "dbo"."CreateReceipt" should be declared.
my database version is 10g
Please help me how can i call it... I need to pass some parameters too to the SP
thanking you

hi,
thank you for the response.
when i call the sp using DBMS_HS_PASSTHROUGH, without parameters it works successfully, but with parameters it gives the following error
ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
[Generic Connectivity Using ODBC][Microsoft][ODBC SQL Server Driver]Invalid parameter number[Microsoft][ODBC SQL Server Driver]Invalid Descriptor Index (SQL State: S1093; SQL Code: 0)
my code is,
declare
c INTEGER;
nr INTEGER;
begin
c := DBMS_HS_PASSTHROUGH.OPEN_CURSOR@hsa;
DBMS_HS_PASSTHROUGH.PARSE@hsa(c, 'Create_Receipt(?,?)');
DBMS_HS_PASSTHROUGH.BIND_VARIABLE@hsa(c,1,'abc');
DBMS_HS_PASSTHROUGH.BIND_VARIABLE@hsa(c,2,'xyz');
nr:=DBMS_HS_PASSTHROUGH.EXECUTE_NON_QUERY@hsa(c);
DBMS_HS_PASSTHROUGH.CLOSE_CURSOR@hsa(c);
end;
Create_Receipt is the sp which requires two parameters.
please give me a solution
thanking you
sreejith

How to convert sql server procedure in to plsql procedure

hi guys
i have requirement where in i have to convert sql server procedure into plsql procedure.
can some one help me out .
thanks,
Vamshi.D

Hi Vamshi,
As you want to convert sql server procedure in to plsql procedure
i.e SQL SERVER ->ORACLE Right
FYI
SQL SERVER Proc. Syntax are totally different as compared to ORACLE Proc.
So, better you study Logic of SQL-SERVER Proc and convert into
Oracle Procedure.
Thanks,
Samadhan

Sql Server Management Assistant (SSMA) Oracle okay for large database migrations?

All:
We don't have much experience with the SSMA (Oracle) tool and need some advice from those of you familiar with it. We must migrate an Oracle 11.2.0.3.0 database to SQL Server 2014. The Oracle database consists of approximately 25,000 tables and 30,000
views and related indices. The database is approximately 2.3 TB in size.
Is this do-able using the latest version of SSMA-Oracle? If so, how much horsepower would you throw at this to get it done?
Any other gotchas and advice appreciated.
Kindest Regards,
Bill
Bill Davidson

Hi
Bill,
SSMA supports migrating large database of Oracle. To migrate Oracle database to SQL Server 2014, you could use the latest version:
Microsoft SQL Server Migration Assistant v6.0 for Oracle. Before the migration, you should pay attention to the points below.
1.The account that is used to connect to the Oracle database must have at least CONNECT permissions. This enables SSMA to obtain metadata from schemas owned by the connecting user. To obtain metadata for objects in other schemas and then convert objects
in those schemas, the account must have the following permissions: CREATE ANY PROCEDURE, EXECUTE ANY PROCEDURE, SELECT ANY TABLE, SELECT ANY SEQUENCE, CREATE ANY TYPE, CREATE ANY TRIGGER, SELECT ANY DICTIONARY.
2.Metadata about the Oracle database is not automatically refreshed. The metadata in Oracle Metadata Explorer is a snapshot of the metadata when you first connected, or the last time that you manually refreshed metadata. You can manually update metadata
for all schemas, a single schema, or individual database objects. For more information about the process, please refer to the similar article:
https://msdn.microsoft.com/en-us/library/hh313203(v=sql.110).
3.The account that is used to connect to SQL Server requires different permissions depending on the actions that the account performs as the following:
• To convert Oracle objects to Transact-SQL syntax, to update metadata from SQL Server, or to save converted syntax to scripts, the account must have permission to log on to the instance of SQL Server.
• To load database objects into SQL Server, the account must be a member of the sysadmin server role. This is required to install CLR assemblies.
• To migrate data to SQL Server, the account must be a member of the sysadmin server role. This is required to run the SQL Server Agent data migration packages.
• To run the code that is generated by SSMA, the account must have Execute permissions for all user-defined functions in the ssma_oracle schema of the target database. These functions provide equivalent functionality of Oracle system functions, and
are used by converted objects.
• If the account that is used to connect to SQL Server is to perform all migration tasks, the account must be a member of the sysadmin server role.
For more information about the process, please refer to the similar article:
https://msdn.microsoft.com/en-us/library/hh313158(v=sql.110)
4.Metadata about SQL Server databases is not automatically updated. The metadata in SQL Server Metadata Explorer is a snapshot of the metadata when you first connected to SQL Server, or the last time that you manually updated metadata. You can manually update
metadata for all databases, or for any single database or database object.
5.If the engine being used is Server Side Data Migration Engine, then, before you can migrate data, you must install the SSMA for Oracle Extension Pack and the Oracle providers on the computer that is running SSMA. The SQL Server Agent service must also
be running. For more information about how to install the extension pack, see Installing Server Components (OracleToSQL). And when SQL Express edition is used as the target database, only client side data migration is allowed and server side data migration
is not supported. For more information about the process, please refer to the similar article:
https://msdn.microsoft.com/en-us/library/hh313202(v=sql.110)
For how to migrate Oracle Databases to SQL Server, please refer to the similar article:
https://msdn.microsoft.com/en-us/library/hh313159(v=sql.110).aspx
Regards,
Michelle Li

Error converting SQL Server text field to Oracle CLOB

Similar Messages

Maybe you are looking for