cancel
Showing results for 
Search instead for 
Did you mean: 

sap crash: SQL error

former_member533538
Participant
0 Kudos

Dear Experts,

My sap may be crashed,every time i run most tcode,it will be terminated with an error,the error dump is as below:

Laufzeitfehler DBIF_RSQL_SQL_ERROR

Ausnahme CX_SY_OPEN_SQL_DB

Datum und Zeit 17.10.2011 13:26:03

-


-


Kurztext

SQL error in the database when accessing a table.

-


-


你能做什么?

Note which actions and input led to the error.

For further help in handling the problem, contact your SAP administrator

.

You can use the ABAP dump analysis transaction ST22 to view and manage

termination messages, in particular for long term reference.

-


-


如何更正此错误

Database error text........: "ORA-65285: Message 65285 not found;

product=RDBMS; facility=ORA

"

Internal call code.........: "[RSQL/FTCH/T371D ]"

Please check the entries in the system log (Transaction SM21).

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"

"CL_CBASE_CONVERT==============CP" or "CL_CBASE_CONVERT==============CM005"

| "CLASS_CONSTRUCTOR"

i can run db02 to check the database,the table space is enough,i can run SE38,but when i run the program in SE38,it will be terminated too,i can run SE11,but when i try to access any table,it will be terminated,i found in many case it will be crashed when i run the tcode which try to access database table,it will be terminated,i have checked database alert log and trace file,didn't find any error,what can i do to solve this issue?

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member188883
Active Contributor
0 Kudos

Hi,

Can you check whether your log directory is full or not ?

Else please share the full details of the log in ST22.

Regards,

Deepak Kori

vincentlim826
Employee
Employee
0 Kudos

I think firstly you should update your oracle client to latest patch. see SAP note #819829 ( i assume you are running unix-flavoured os)

do check dev_w* trace or syslog.

Regards,

Vincent