- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- TEXT and IMAGE datatypes as parameters and local v...
Operating System - HP-UX
1753587
Members
6759
Online
108796
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2003 02:45 PM
05-15-2003 02:45 PM
TEXT and IMAGE datatypes as parameters and local variables
Hi all,
having difficulties in using TEXT and IMAGE datatypes as stored procedure parameters or as local variables.
e.g.
CREATE PROCEDURE myproc
@a INT,
@b TEXT NULL
AS
BEGIN
--code for the procedure
END
Gives error as
'TEXT and IMAGE datatypes are invalid for parameters and local variables'
Please advice. Thanks
having difficulties in using TEXT and IMAGE datatypes as stored procedure parameters or as local variables.
e.g.
CREATE PROCEDURE myproc
@a INT,
@b TEXT NULL
AS
BEGIN
--code for the procedure
END
Gives error as
'TEXT and IMAGE datatypes are invalid for parameters and local variables'
Please advice. Thanks
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-18-2003 05:55 PM
05-18-2003 05:55 PM
Re: TEXT and IMAGE datatypes as parameters and local variables
Hi Prandip,
This may be of some help.
Error with LONG RAW / IMAGE data types :-
An assign statement such as: myvariable := :longrawcol;
or
if :image_item is null then
some logic;
end if;
produces compilation error:
PL/SQL ERROR 49 BAD BIND VARIABLE 'VARNAME'
or
ORA-00932 : inconsistent datatypes
Problem Explanation:
====================
A table with a long raw column exists on the database. The value of the long raw item cannot be used in an assign statement. You also cannot see if the image item is null with the if statement.
Solution Description:
=====================
PL/SQL v1 does not support long raw / image datatypes, this means it is not possible to perform any assignment through PL/SQL with this datatype. This is a limitation of PL/SQL.
Solution Explanation:
=====================
If you need logic in Oracle Forms to see if the long raw column is null then the workaround is:
a. Alter the database table and add a flag column.
b. Whenever you populate the record with an image, also populate the flag column with 'Y'.
c. Then in the form do the following if statement:
if :flag_column is null then
some login;
end if;
Within SQL*Plus, the long raw column cannot be copied with a create table command, insert statement or copy command.
SQL> create table table2 as select * from table1;
ERROR:
ORA-00932: inconsistent datatype
SQL> copy from user/pwd@db to user/pwd@db create table2 using select * from table1;
ERROR:
ORA-0932: inconsistent datatype
The COPY command can be used as a workaround for dealing with tables with long columns but not long raw. Using the copy command with long raw columns will result in ORA-932: inconsistent datatypes as illustrated above.
Solution References:
====================
Enhancement Requests
--------------------
153963
Abstract: SELECT LONG RAW GIVES INCONSISTENT DATATYPE
To retrieve long raw, use OCI or pre-compiler and do defines with the
appropriate datatype.
162373
Abstract: COPY A TABLE WITH "LONG RAW" GIVES ORA-932
293729
Abstract: OLE. PLS-49 OR ORA-932 WHEN ASSIGNING LONG RAW TO OLE-CONTAINER IN PL
This may be of some help.
Error with LONG RAW / IMAGE data types :-
An assign statement such as: myvariable := :longrawcol;
or
if :image_item is null then
some logic;
end if;
produces compilation error:
PL/SQL ERROR 49 BAD BIND VARIABLE 'VARNAME'
or
ORA-00932 : inconsistent datatypes
Problem Explanation:
====================
A table with a long raw column exists on the database. The value of the long raw item cannot be used in an assign statement. You also cannot see if the image item is null with the if statement.
Solution Description:
=====================
PL/SQL v1 does not support long raw / image datatypes, this means it is not possible to perform any assignment through PL/SQL with this datatype. This is a limitation of PL/SQL.
Solution Explanation:
=====================
If you need logic in Oracle Forms to see if the long raw column is null then the workaround is:
a. Alter the database table and add a flag column.
b. Whenever you populate the record with an image, also populate the flag column with 'Y'.
c. Then in the form do the following if statement:
if :flag_column is null then
some login;
end if;
Within SQL*Plus, the long raw column cannot be copied with a create table command, insert statement or copy command.
SQL> create table table2 as select * from table1;
ERROR:
ORA-00932: inconsistent datatype
SQL> copy from user/pwd@db to user/pwd@db create table2 using select * from table1
ERROR:
ORA-0932: inconsistent datatype
The COPY command can be used as a workaround for dealing with tables with long columns but not long raw. Using the copy command with long raw columns will result in ORA-932: inconsistent datatypes as illustrated above.
Solution References:
====================
Enhancement Requests
--------------------
153963
Abstract: SELECT LONG RAW GIVES INCONSISTENT DATATYPE
To retrieve long raw, use OCI or pre-compiler and do defines with the
appropriate datatype.
162373
Abstract: COPY A TABLE WITH "LONG RAW" GIVES ORA-932
293729
Abstract: OLE. PLS-49 OR ORA-932 WHEN ASSIGNING LONG RAW TO OLE-CONTAINER IN PL
Never give up, Keep Trying
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP