topic Re: exception CX_SY_NATIVE_SQL_ERROR syntax error in Application Development and Automation Discussions

exception CX_SY_NATIVE_SQL_ERROR syntax error

Former Member — Mon, 23 Mar 2009 11:54:09 GMT

Hi, while trying to catch exception I got this syntax error:

*The type "CX_SY_NATIVE_SQL_ERROR" is unknown. *

data:
myORADB  type dbcon-con_name,
lv_message type string,
lr_error TYPE REF TO cx_sy_native_sql_error,
ret type int4,
nTabs type int4 value 0 .

..............

.............

how to solve this, please do you have any idea? working on 4.6c system...

thanks,

nihad

Re: exception CX_SY_NATIVE_SQL_ERROR syntax error

Former Member — Mon, 23 Mar 2009 12:12:40 GMT

Hello Friend,

The class CX_SY_NATIVE_SQL_ERROR has been released internally in SAP version 4.6C.

May be you can not use that one as reference.

Generally, if you see TRY...CATCH statement to handle error has been promoted by SAP from version 6.0 onwards.

Regards

Krishnendu

Re: exception CX_SY_NATIVE_SQL_ERROR syntax error

Former Member — Mon, 23 Mar 2009 12:15:38 GMT

Hi,

Do you know how can I hande exeptions in 4.6c, related to DBCON connection to remote oracle db?

thanks,

Nihad

Re: exception CX_SY_NATIVE_SQL_ERROR syntax error

Former Member — Thu, 26 Mar 2009 15:13:14 GMT

Please stop duplicate posting multiple variants of the same question, and see SAP Note 1259369.

The forum rules are in the sticky post at the top of each forum page.

Kindly respect them.

Cheers,

Julius

Re: exception CX_SY_NATIVE_SQL_ERROR syntax error

Former Member — Thu, 26 Mar 2009 15:18:27 GMT

OK, I respect the rules

I will give answer to the question you erased:

It is possible to call oracle procedure in abap. Use statement:

EXEC SQL.

EXECUTE PROCEDURE proc_name (IN :field_name1, IN :field_name2)

ENDEXEC.

No duplicating any more, I promise

cheers,

Nihad

Re: exception CX_SY_NATIVE_SQL_ERROR syntax error

Former Member — Thu, 26 Mar 2009 15:34:17 GMT

Thanks!

Yes, to follow-up on existing questions with further progress or infos is the correct procedure - this keeps the answers together for others who search for it.

When the question is indeed a different one, then feel free to open a new thread and discuss it until conclusion.

Many thanks,

Julius