on 05-25-2016 10:23 PM
Hello guys,
Any known issues related to this error:?
I. 05/25 14:22:45. Finished checkpoint of "iws" (iws.db) at Wed May 25 2016 14:22
I. 05/25 14:29:25. Starting checkpoint of "iws" (iws.db) at Wed May 25 2016 14:29
I. 05/25 14:29:25. Finished checkpoint of "iws" (iws.db) at Wed May 25 2016 14:29
E. 05/25 14:29:30. *** ERROR *** Assertion failed: 101412 (16.0.0.1257)
Page number on page does not match page requested
I. 05/25 14:29:30. Connection terminated abnormally
I. 05/25 14:29:30. Disconnected TCPIP client's AppInfo: IP=10.26.9.226;HOST=SA09PC120;OSUSER=jzamora;OS='Windows 7 Build 7601 Service Pack 1';EXE='C:\sybase\Shared\Sybase Central 6.0.0\x64\scjview.exe';PID=0x4adc;THREAD=0x34c0;VERSION=11.0.1.5604;API=iAnywhereJDBC;TIMEZONEADJUSTMENT=-240
>IQ version: SAP IQ/16.0.102.1257/20056/P/sp10.03/Enterprise Linux64 - x86_64 - 2.6.18-194.el5/64bit/2015-08-20 17:45:23
That is the only trace in IQ mesage file. No stack traces or other errors. IQ just crashes.
Thank you
Regards
Jose
Tayeb, Lyna and John:
Thank you very much .
Regards
Jose
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Lyna,
Thank you. Should IQ be shutdown before running dbvalid?
Regards
Jose
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Tayeb, John;
Thank you.
We've already executed sp_iqcheckdb 'verify database' and it came clean( no errors ).
So as Tayeb mentioned I checked KBA 2206100 and it mentions CR 788383, which was resolved in IQ16 SP10.7. which I did not find in Market place. Just SP 10 PL 06 and SP 11.
Looking through SP 11 coverletter, CR788383 is not present. Do you know guys, if this CR is included in SP 11 base line..?
Regards
Jose
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
SP10 PL07 is not released yet. SP11 did not include the fix.
The CR in question involves calling a stored procedure or a user defined function defined with SQL SECURITY INVOKER.
Check if it is the case.
Otherwise it would be a catalog corruption to be checked with dbvalid utility as advised by Lyna.
Check if previously there were hardware access or disk full issues.
The Assertion failed: 101412 most likely indicates a corruption in the database.. System hardware (possibly a bad sector or disk controller ) be checked and validated periodically to ensure that is healthy and identify problems early. Databases should be validated periodically for the same reasons. The problem that lead to the assertion may be a random, one time event. Please do not assume that is the case however as if it is a precursor to a more serious problem, you need to know that as soon as possible. regards John
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jose,
This looks similar to issue addressed in KBA 2206100.
Regards,
Tayeb.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
94 | |
11 | |
11 | |
10 | |
9 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.