Database-level error

Hi All,
I am facing the below issue with my JDBC channel:
Database-level error reported by JDBC driver during committ or rollback of database transaction. The JDBC driver returned the following error message: 'java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Unhandled token type: Unknown token: 0x01'. For details, contact your database server vendor.
Can some one please provide the input of how to resolve the above issue.
Regards,
Eswar

>
eswar7667 wrote:
> Hi All,
>
> I am facing the below issue with my JDBC channel:
>
> Database-level error reported by JDBC driver during committ or rollback of database transaction. The JDBC driver returned the following error message: 'java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Unhandled token type: Unknown token: 0x01'. For details, contact your database server vendor.
>
> Can some one please provide the input of how to resolve the above issue.
>
> Regards,
> Eswar
When you trying to execute a Transact-SQL that contain a clause COMPUTE or COMPUTE BY, and you use Microsoft SQL Server 2000 Driver JDBC SP1 for connecting to server Microsoft SQL Server 2000, the query can raise the exception:
[Microsoft][SQLServer 2000 Driver for JDBC]Unhandled token type: Unknown token: 0x01
To solve the problem, try to upload the DRIVER DataDirect Release 3.x for SQL Server JDBC.
For information regarding DataDirect Driver for SQL Server JDBC, take a look here:
http://www.datadirect-technologies.com/
ps. You can also try to upgrade MS driver to SP2
Edited by: spantaleoni on Feb 15, 2011 10:31 AM

Similar Messages

Database-level error reported by JDBC driver

Hi everyone,
I get an error in my Sender JDBC adapter. I am executing a stored procedure every minute. In total I have 34 JDBC senders for every different database. The error is like below. The problem is in Alert Inbox I cant see the rest of the message. This error occures just once every hour (average). I dont know why and I dont know what the rest of the error is saying.
Any ideas how i can see the rest of the message? And where the error might be?
Note: In communication channel monitoring everything is green.
Database-level error reported by JDBC driver while executing statement 'EXEC [TB

Hi,
obviously there are concurring accesses to the table your stored procedure is accessing. This is nothing serious, because SAP XI will retry the execution of the stored procedure according to the settings of the communication channels (3times all 5 minutes is the default). Additionally you can set the repeats in case of SQL errors in the extended tab of the communication channel configuration.
Tuning the transaction isolation levels might help to avoid the error but can decrease the consistency of the data as well. Default isolation level is always the highest available in a database (in case of SQL Server it should be SERIALIZABLE), so locks might easily occur. I would suggest to have a look at other applications accessing the tables and determine their isolation level.
All in all, I guess there shouldn't be real problems, because of the repeated execution of you stored procedure, but it's worth to have a look at the isolation level.
Regards Sven

JDBC: Database-level error

Hi Folks,
I'm trying a JDBC to JDBC scenario and I'm getting the following error.
*Database-level error reported by JDBC driver while executing statement 'select * from EMPLOYEE where flag = 'X'.'. The JDBC driver returned the following error message: 'java.sql.SQLException: [Microsoft][ODBC Microsoft Access Driver] Syntax error (missing operator) in query expression 'flag = 'X'.'.'. For details, contact your database server vendor.*
My select statement is : select * from employee where flag = 'X'.
Regards,
Santosh

Hi,
Try with following sql query.
select * from employee where flag = "X".
Hope this helps.
Thanks and Regards,
Kalpesh

Error while Assigning database level role (db_datareader) to SQL login (Domain Account)

Team,
I got an error while creating a User for Domain Account. Below is the screen shot of the error (error : 15401)
Database instance is on SQL 2000 SP3. ( I know it is out of support, But the customer is relutanct to upgrade)
On Google search, i found below article which is best matching for this error
http://support.microsoft.com/kb/324321
I have follows each step of troubleshooting. But still the issue persists.
Step 1. The login does not exist == The login is very much exist in the domain as i am able to add the same domain id to other database instances
Step 2. Duplicate security identifiers == i have used this query to find duplicate SID
/* SELECT name FROM syslogins WHERE sid = SUSER_SID ('YourDomain\YourLogin') */
But there was only one row returned with create date of today's.
Error while Assigning database level role (db_datareader) to SQL login (Domain Account)
Step 3. Authentication failure == Domain is available. User is able to login on other servers via RDP connection.
Step 4. Case sensitivity == Database collation is set to Case insensitivity. (CI)
Other two 5. Local Accounts & 6. Name resolution == is not applicable to me.
I tried other ways also.
A. Creating login and providing permission in one go only = User account is not created
B. Instead of GUI, use query to create login and provide required permission = Same error.
Does anybody has faced any such situation
Chetan

See the below output
srvid
sid
xstatus
xdate1
xdate2
name
password
dbid
language
isrpcinmap
ishqoutmap
selfoutmap
NULL
0x010500000000000515000000A1F66E1BFC1DC75D26E72530A2B80400
14
20:25.9
57:33.4
UKBAA\LHRAPPMuttavarapuS
NULL
1
us_english
0
0
0
Chetan

BR0970W Database administration alert - level: ERROR, type: HARMFUL_STATIST

Dear all,
We have recently migrated 4.6c/oracle9i/solaris 6800 5.8 to 4.6c/oracle10g/HPUX11.23
After the migration everything was succesfull. Except the below error, when I run a dbcheck from db13.
BR0970W Database administration alert - level: ERROR, type: FILE_OFFLINE, object: /oracle/DV2/mirrlogA/log_g1m2.dbf
BR0970W Database administration alert - level: ERROR, type: FILE_OFFLINE, object: /oracle/DV2/mirrlogB/log_g2m2.dbf
BR0970W Database administration alert - level: ERROR, type: FILE_OFFLINE, object: /oracle/DV2/mirrlogA/log_g3m2.dbf
BR0970W Database administration alert - level: ERROR, type: FILE_OFFLINE, object: /oracle/DV2/mirrlogB/log_g4m2.dbf
BR0970W Database administration alert - level: ERROR, type: HARMFUL_STATISTICS, object: (table) SAPR3.APQD
BR0970W Database administration alert - level: ERROR, type: HARMFUL_STATISTICS, object: (table) SAPR3.APQI
BR0970W Database administration alert - level: ERROR, type: HARMFUL_STATISTICS, object: (table) SAPR3.ARFCRSTATE
BR0970W Database administration alert - level: ERROR, type: HARMFUL_STATISTICS, object: (table) SAPR3.ARFCSDATA
BR0970W Database administration alert - level: ERROR, type: HARMFUL_STATISTICS, object: (table) SAPR3.ARFCSSTATE
BR0970W Database administration alert - level: ERROR, type: HARMFUL_STATISTICS, object: (table) SAPR3.ATAB
BR0970W Database administration alert - level: ERROR, type: HARMFUL_STATISTICS, object: (table) SAPR3.CDCLS
BR0970W Database administration alert - level: ERROR, type: HARMFUL_STATISTICS, object: (table) SAPR3.COIX
BR0970W Database administration alert - level: ERROR, type: HARMFUL_STATISTICS, object: (table) SAPR3.COIX_DATA40
BR0970W Database administration alert - level: ERROR, type: HARMFUL_STATISTICS, object: (table) SAPR3.DBTABLOG
BR0970W Database administration alert - level: ERROR, type: HARMFUL_STATISTICS, object: (table) SAPR3.DDLOG
BR0970W Database administration alert - level: ERROR, type: HARMFUL_STATISTICS, object: (table) SAPR3.DDNTF
BR0970W Database administration alert - level: ERROR, type: HARMFUL_STATISTICS, object: (table) SAPR3.DDNTT
BR0970W Database administration alert - level: ERROR, type: HARMFUL_STATISTICS, object: (table) SAPR3.DDXTF
BR0970W Database administration alert - level: ERROR, type: HARMFUL_STATISTICS, object: (table) SAPR3.DDXTT
BR0970W Database administration alert - level: ERROR, type: HARMFUL_STATISTICS, object: (table) SAPR3.EPIDXB
BR0970W Database administration alert - level: ERROR, type: HARMFUL_STATISTICS, object: (table) SAPR3.EPIDXC
BR0970W Database administration alert - level: ERROR, type: HARMFUL_STATISTICS, object: (table) SAPR3.GLSP
Can anyone help us to overcome the above issue
Regards
Senthil

Thank you Warren. I shall do that reply to you.
Also I have received the below error messages
oracle9i/solaris 6800 5.d to 4.6c(Kernel46D)/oracle10g/hpux11.23.
Everything works fine except the below Three errors:
BR0970W Database administration alert - level: ERROR, type: FILE_OFFLINE, object: /oracle/DV2/mirrlogA/log_g3m2.dbf
BR0970W Database administration alert - level: WARNING, type: IN_WRONG_TABLESPACE, object: (table) SAPR3.APQD, value: PSAPAPQDD
BR0978W Database profile alert - level: ERROR, parameter: LOG_ARCHIVE_START, value: FALSE (<> TRUE)
Can you help
Regards
Senthil

Database Connection Error

Hello,
We have crystal reports published on the BOBJ system and the datasource is SAP BI system . The reports were working fine
untill last monday when they started giving error " Database Connection Error " .
This is what happening, when we run the crystal report , it will come up with a pop up for selection and upon giving the selection and click on execute , it is giving error.
To start we have this issue in BOBJ dev system , but now we have the same issue in QA and Prod as well. I suspected
this has to do with license keys, but my BOBJ Admin *** basis team thinks otherwise.
I couldnt think of would have gone wrong or missing . Any ideas will be appreciated.
Thanks,
Ravi.

Ingo,
I tested the reports using the crystal designer, and they ran fine without issues . The same report when we run on BOBJ/infoview it is giving data base connection error. The same is happening across all the 3 systems( Dev, QA and Prod ).
I also tested the verify database on the crystal designer and it say " data is up to date".
As the client level integration seems to be working fine, I'm thinking there is a issue with server level integration.
Can you through some insight into the checks we can do get to the bottom?
Thanks,
Raju.

SYS user connects at database level, is it correct?

My senior colleague has given me following information about the sys user. I want to know, is it correct?
Since SYS user connects at the database level, therefore, on killing the active session of the SYS user,only the current statement is cancelled. The database session does not disconnect. Instead it continues to run the remaining statements in the script file in case we are running a script file containing a lot of SQL statements.
Moazzam

Moazzam wrote:
My senior colleague has given me following information about the sys user. I want to know, is it correct?
Since SYS user connects at the database level, therefore, on killing the active session of the SYS user,only the current statement is cancelled. The database session does not disconnect. Instead it continues to run the remaining statements in the script file in case we are running a script file containing a lot of SQL statements.Running a SQL script very likely means SQL*Plus is used. One of two types of Oracle sessions will be created via sqlplus. A dedicated session. Or a shared server session.
A dedicated session can also be local (sqlplus connects "directly" to the dedicated server process), or remote (sqlplus connects via tcp/ip to the dedicated server process).
A server session is usually "killed" using the alter system kill session command. Despite the differences between shared and dedicated server connections, the end result is the same. The session terminates abnormally (session UGA will be released, session will be cleaned up, rolled back, etc) - and the session ceases to exist.
So irrespective of how that sqlplus session runs that script - the session, when killed, will cause a sqlplus failure. And no subsequent script commands would be executed by that Oracle session.
What can happen is that sqlplus continues running, continues reading the script, and continues submitting commands to be executed. However, with the server session killed, there is no server process to service the commands submitted by the sqlplus client. In this case, sqlplus will throw the error "+SP2-0640: Not connected+" after each of the commands it tries to execute after the server session was killed.
The only time when sqlplus will be able to continue is when the session is not killed, but interrupted. The Oracle Call Interface (OCI) supports a OCIBreak() call - allowing the client to interrupt-and-abort the request that its server session is currently executing.
For example, sqlplus sends a OCIBreak() while it waits for a server response (e.g. waiting for the answer to a SQL select query), when the user presses Ctrl-Break to abort that request.
In this case, the session still exists - and the client can issue a new request that the session will service. But an OCIBreak() cannot be triggered (to my knowledge) externally from another Oracle session. You need to send the client process a "break request" (like a Ctrl-Break keystroke) in order to trigger that client process to make an OCIBreak() call to Oracle and interrupt its server process.

Multi-level error propagation during the execution of CFM2 transaction

Hi,
We are implementing SAP SCM 5.0 integrated to SAP R/3 Mills IS.
During the execution of CFM2 transaction, while trying to activate the integration model for the object u201COrdersu201D for the very first time, the following error message appears:
*"Multi-level error propagation carried out".*
There are also messages related to inbound queues blocked. In the case of maintenance orders, CIF_MNT_INBOUND message shows up. While working with Production orders, CIF_ORDER_INBOUND message emerges.
The items listed below should be taken into account:
-The production orders that are meant to be transferred to APO are regular production orders corresponding to several products.
-We are working with configurable materials.
-We are working with the active model (000) and for each plant we are using 2 different planning versions.
Regards,
Analía Nahmías

Dear Analía,
The corresponding error messages issued when executing //CCR indiacted the peg-ids are missing in liveCache.
Recommendations:
-Run transaction /SAPAPO/OM17 to check the internal consistency between database and liveCache within SCM system. Correct the inconsistencies
-Execute report /sapapo/cif_deltareport3 to correct the inconsistencies between ECC and SCM system
Regards,
Tibor

Error in file filename : Database Connector Error

Dears,
I face a problem from several days with one of my deployed reports to CMS.
The problem is the same reports run for some users and other users keeps to give them this error:
Error in file <filename>: Database Connector Error
Note: there is no filteration or any condition on users name and data resulted from this report is one for all users.
I tried everything, even i remove all objects from the report and keep only page headers it works.
But, if i readded any field from my DB object in crystal report the error appears again.
Please help, Thanks in advance.

Hello,
You are using the original release of Cr XI R2. This has likely been fixed after applying all Service Packs and Fix Packs.
You should update the BOE Servers also so before doing so please check with the BOE Administrator.
To get the BOE patches you have to log into Service Market Place. To get CR patches make sure you have your keycode saved and available.
Uninstall CR using the Add/Remove Programs in Control Panel and then use the Full version of CR XI R2 Service Pack 4 and you can then apply SP 6, if it requires SP 5 first please do so:
https://smpdl.sap-ag.de/~sapidp/012002523100011802732008E/crxir2_sp4_full_build.exe
https://smpdl.sap-ag.de/~sapidp/012002523100013876392008E/crxir2win_sp5.exe
https://smpdl.sap-ag.de/~sapidp/012002523100015859952009E/crxir2win_sp6.exe
We do recommend that BOE and CR be on the same patch level.
Thank you
Don

A Transport-level error

Our .net application throws an error when the wireless laptop switches from wireless access point to another inside a building. it seems like SQL is closing the existing connetion without notifying the application which thinks that sqlconnetion is still
in OPEN state. why does SQL close a connection without notifying the application? Our programming team does not want to open and close the connection on each transaction because they think it will slow down the application.
Error:
"A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)"

I would expect a disconnect error in such a case.
I don't think SQL Server has a design feature to follow mobile wireless devices.
Threads:
Timeout issue when connection to SQL Server in Wireless environment
Having disconnections with SQL Server using a wireless connection
QUOTE: "Ah, SQL Server connections (and the connection pooling mechanism) are not at
all tolerant of WiFi connections. I suggest you use a replication technology
as exposed by the SQL "Server" Compact Edition and ADO.NET 3.5 Sync
Services. This gives you a local DBMS to work with and connectivity designed
to work over an occasionally (and unreliable) connection."
You may try to adjust the TCP/IP Keep Alive parameter, but no guarantee though.
BOL: "Keep Alive
This parameter (in milliseconds) controls how often TCP attempts to verify that an idle connection is still intact by sending a
KEEPALIVE packet. The default is 30000 milliseconds."
LINK:
http://technet.microsoft.com/en-us/library/ms190771(v=sql.105).aspx
Related thread:
Wireless connections to SQL Databases
Kalman Toth Database & OLAP Architect
SQL Server 2014 Design & Programming
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

SQL Exceptions, transport-level errors on SharePoint 2010 App Server

SharePoint 2010 becomes inaccessible 2-3 times per day. It happens at approximately the same times: 8 PM, 1 AM and 1 PM. It is inaccessible for about 3-4 minutes and then comes back on its own.
During the time it is down, we see the following errors in the event viewer on the application server:
EventID: 5586 Task Category: Database -
Unknown SQL Exception 64 occurred. Additional error information from SQL Server is included below.A transport-level error has occurred when receiving results from the server.
(provider: TCP Provider, error: 0 - The specified network name is no longer available.)
EventID: 3 Task Category: None -
.Net SqlClient Data Provider: System.Data.SqlClient.SqlException: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error:
0 - The specified network name is no longer available.)
EventID: 6398 Task Category: Timer -
The Execute method of job definition Microsoft.Office.Server.Search.Monitoring.HealthStatUpdateJobDefinition (ID f9db48f1-f115-47ab-99b6-552460cbb782) threw an exception. More
information is included below. A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)
EventID: 8086 Task Category: Business Data -
The BDC Service application failed due to a SQL Exception: SQLServer host ums1spd1v. The error returned was: 'A transport-level error has occurred when sending the request to
the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)'
The SharePoint logs have errors during the same time period saying the same kinds of things: Sql exception raw message: A transport-level error has occurred when receiving results from the server,
The specified network name is no longer available, etc.
Our network administrator has looked at the issue and cannot find any network problems.
He setup a continuous ping from the app server to the database server.
Even during the times these errors are occurring, the app server is still able to reach the database server.
However, you cannot ping the app server itself during this time.
Our database administer cannot find any SQL Server issues.
There are no errors in the event viewer or the SQL logs on the database server.
In Central Admin, we can see that one or two jobs fail with SQL errors during the times these errors take place.
It is almost always the “User Profile Service Application – User Profile Language Synchronization Job” and often the “Health Statistics Updating” or “Crawl Log Report for Search Application Search Service Application”.
These jobs run successfully at many other times during the day.
Is there a good way to tell if the database, network or SharePoint itself is the root of these problems?
The database and network guys say there are no problems in their areas, but all I can find in the SharePoint logs is that it can’t reach the database server.
Thank you for any suggestions you may have!

Since these seem to happen at very specific times, I would run a NetMon trace at that window to capture what is going back and forth (or perhaps the timer service is just unable to reach the SQL server).
Trevor Seward, MCC
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Char NUMC(5) - need to store value at database level without leading Zeros.

Hi All
We have 0Mat_Item like infoobjects in SAP BI, which have data type Char NUMC(5). Here if u load value '1', it would show us '1' at front end (BI or reporting level) but at database level stores as u201800001u2019.
My requirement is to store this value without leading zeros at database level. I wrote code in transformation u201Cshift u2026 left deleting leading u20180u2019 u201C & could load the data into New data table and at database level as I was getting result without leading zero. But once I activate the request, it gives SID generation error u201CValue '1' of characteristic 0ME_XCHRATE is not a number with 000009 spaces.u201D
How to solve this issue so that I could store u20181u2019 value instead of u201800001u2019 value in the database & could able to activate in DSO.
Thanks....

Hi.....
System may be storing the data in that way to maintain consistency.
Alpha conversion is used to store data consistently. It does this by storing numeric values prefixed with 0s Eg. If you have defined a material as length 6 (of type Numc) then material number 1 is stored as 000001 but displayed as 1; this removes inconsistencies between 01 vs. 001.
U can add the conversion routine for this Infoobject in either below way...
In the BW side...in the Datasource Level
In the datasource >> Go to fields tab >> there search the R/3 field which is mapped to that Infoobject in the Transformation >> Then in the Conv.Routine column select the Alpha Conversion Routine and In the Format column select External....
In the Transformation
Write a field level routine for that particular field abd call the Alpha conversion routine there...
In the R/3 side
In the Customer exit ....Go to SE37 >> EXIT_SAPLRSAP_001 >> Double click on ZXRSAU01 >> search the datasource......write the code there....
Hope below link helps you.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/7108a690-0201-0010-4cbc-9bca94f9ad9c?quicklink=index&overridelayout=true
Regards,
Vinay.
Edited by: Vinay Joshi on Mar 10, 2011 4:54 AM

Error: EncryptedLocalStore database access error in AIR 3.4

Hi,
A few of our users were prompted to update to Adobe AIR 3.4 today. After doing this they were no longer able to use our Adobe AIR "desktop" app. I've downloaded the 3.4 SDK and run our app via ADT and I get the following error in the Introspector:
Error: EncryptedLocalStore database access error
Our app stores configuration info in the EncryptedLocalStore.
This has never occurred before and if I uninstall 3.4 and go back to 3.3 the problem does not exist. We need an urgent solution to this because we have hundreds of users who use our AIR app every day. We've told them NOT to update to 3.4 until further notice.
Any assistance would be greatly appreciated.
Brad.

Hello AIR developers,
I want to thank you for your patience and again apologize to you for catching you off guard with this change. Our team met today and our immediate plan is to roll the ELS changes back to the AIR 3.3 level. We are working on a timeline for when this update will be occur. We are treating this with the highest priority and expect it will not take long.
For those interested, here’s how and why this change occurred. Over the past year or two we’ve heard complaints about the reliability of our ELS implementation, especially on the Mac platform. We’ve known all along that we wanted to refactor this feature and remove dependence on third party libraries. We undertook this restructuring during the 3.4 release schedule and finished without hearing any major complaints from our internal or prerelease users. One assumption we made was that ELS data was treated like a volatile cache. In the past we’ve given guidance on the usage of ELS in both blogs and our help documentation, suggesting that developers should not depend on ELS as permanent data storage because it “can be lost for a variety of reasons”. Our position on this hasn’t changed, but we acknowledge and understand that some applications have come to depend on this data and if at all possible, we should do our best to persist it.
Going forward, we will most likely reimplement our changes from 3.4, however when doing this we will also work to provide a way to automatically upgrade and persist your application's data. We will also give plenty of advanced notice and make releases available on our labs.adobe.com site. We want this change to improve your lives by adding improved stability and we look forward to working with you on this in the future.
Thanks,
Chris

Database procedure error

Hi everyone,
I have form which has two database procedures in key commit trigger. If any error occurs while executing the second database procedure
I dont want to save the form and first database procedure values. Can anyone please tell me how to pass the database procedure error to
form so that it can stop the saving of form and first database procedure .
Thanks in advance for any reply.

Dear all,
Thanks for your kind reply.
I have tried using DBMS_ERROR_CODE in ON-ERROR trigger. My code appears like this.
create or replace procedure_name(parmeters) as --- This is a database procedure;
begin
procedure_body;
exception
when others then
Raise_application_error(-20025,'Error Message');
end;
In form in ON_ERROR trigger I have declared like this:
IF DBMS_ERROR_CODE = -20025 THEN
MESG('Error in Insertion');
Raise form_trigger_failure;
END IF;
I am not getting error message that I declared in ON_ERROR trigger instead I am getting error message from raise_application_error statement.
Could anyone please guide me exactly how to catch the database procedure in form level so that I can stop exceution of the form.

System Level Errors..

Hello,
Our database is 8i. We have jsp's calling oracle stored procedures. We have exception handlers in each of the database procedures. But some system level errors like MAX CURSORS OPEN(ORA-01000), PACKAGE STATE INVALID (ORA-04068) etc. are not captured thru the EXCEPTION HANDLER WHEN OTHERS. These actually are logged on the Default Server log on the application side. What i want to know is - is there a way where i can capture these kind of errors (the error code) thru the jsp (via the database stored procedure) and display appropriate error message instead of the application failing and then we have to look thru the logs to determine the error. I would appreciate your help in this regard.
Thanks,
Raghu

I want to get the value returned by SQLCODE not the complete message. I see in some cases errors returned to the App Server log saying:
java.sql.SQLException: Inserted value too large for column: oracle.jdbc.oracore.OracleTypeCHAR@32636a34
I know what is the problem here but would like to display a message saying 'Oracle Error#........
As u see in this example, there is no SQLCODE (ORA-?????)returned at all.

Database-level error

Similar Messages

Maybe you are looking for