Dba related Query in ASE 16 - sybase-ase

Recently we have observed Update Statistics are getting failed for huge tables
in ASE 16. But we don't find enough information regarding failure in SID.Log.
Request to assist me on this.
Environment AIX7.1/SYBASE ASE16/ECC 6.0 EHP7

Usually this is due to insufficient space in the procedure cache. if so, there will be a mention of error 701 in the ASE errorlog file (run SELECT ##ERRORLOG to find its location)


Unexpectedly truncated mediumtext field in MariaDB

System: GNU/Linux LMDE 2, Linux 3.16
DB: MariaDB 10.0.30-MariaDB-0+deb8u1
Server: Apache/2.4.10
DB Interface Module: libmysql - 5.5.55
PHP: PHP 5.6.30-0+deb8u1 with mysqli + mbstring module
WCMS: Contao 3.0.5
Browser: Opera 12
At reworking one of my websites with the WCMS Contao, I get a strange behaviour with longer texts in »text« and »accordion« elements. After 4448 chars or 4598 bytes, the text is truncated. The DB field »text« in table »tl_content« has the size »mediumtext«, which is 16MB in size. Repeated correcting the article in Contao doesn’t help.
Then I tried the same correcting directly with phpMyAdmin in the versions 4.8.0-dev, 4.7.0, 4.4.2 and 4.1.1, but there’s still no changing of the truncated text. Only in phpMyAdmin 4.4.2 there was an additional message »Oops, something went wrong!!«. No error no., no explanation, only that meaningless message!
Does anyone know, what’s going wrong when longer texts are truncated, and what’s the solution for solving this? Thanks a lot!
Addendum 2017-08-22 16:00 GMT
MariaDB updated to 10.0.32-MariaDB-0+deb8u1
DB Interface Module updated to 5.5.57
another browser (Firefox 50.1.0) has the same problems
textfield updating not from browser+phpMyAdmin but bash will do the job perfectly!
Therefore my conclusion: It seems that the disfunctional part can be one or more of the followings:
browsers transmit per phpMyAdmin not enough data (unlikely)
JavaScript interferes (unlikely)
PHP interferes (unlikely)
DB interface module can’t stand with MariaDB
Addendum 2017-08-22 18:30 GMT
DB Interface Module libmariadb installed
Now I’m looking for the nessesary updates in /etc/php5/apache2/php.ini and/or other files. Any suggestions for the right places to edit to redirect the PHP MySQL functions to libmariadb?

ERROR 1911 (HY000) at line 113: Unknown option 'COMPRESSION'

I've been ripping my hair out over this one for the past view days!
Okay, so server background:
Centos 7 x86_64
Running Laravel
Running MariaDB
LAMP and all the good stuff is configured properly
I'm trying to reinstall a source from a previous project a friend worked on and handed over to me; it's just a for fun project;.
but regardless
I'm trying to import the .sql file he sent over,
Whenver I try to add the .sql to the DB it spits out this error:
ERROR 1911 (HY000) at line 113: Unknown option 'COMPRESSION'
Please help, I've been googling for days and I cannot find a single thing related to this that can benefit in fixing the problem,
I've tried restarting server multiple times, deleting DB's, making new ones, reinstalling laravel, mariadb, reinstalling centos, wiping servers, ect...
Change your table engine to 'InnoDB' and default collation to 'latin1_swedish_ci'.

The ASE PCI-Bridge is not able to process the requested dispatching- Sybase

I am trying to install a jar file in Sybase ASE-15.7 using the 'instjava' command.
I am getting the following error: The ASE PCI-Bridge is not able to process the requested dispatching. This is a fatal error, please contact your System Administrator (SA) for help.
I have enabled java and enabled pci using the following commands:
sp_configure "enable pci", 1
sp_configure "enable java", 1
After looking at the error on the net, i have found that the cause of the error is :
Error 16022 may be reported "The ASE PCI-Bridge is not able to process the requested dispatching. This is a fatal error, etc." when the PCI is unavailable with a stack trace in the error log showing modules "jvminit", "SYB_CreateJavaVM" and "terminate_process" although the stack trace information is unnecessary.
But there is no solution to the problem.
would anyone be able to offer any assistance in this case?
Have you tried to restart ASE?
Also I think sp_configure "enable pci", 1 requires that the sybpcidb database be created if it does not already exist.

InfiniDB ERROR 168 (HY000): Cannot execute the statement. DBRM is read only

I have following version of InfiniDB.
Server version: 5.1.39 MySQL Embedded / Calpont InfiniDB Enterprise
3.2.0-2 GA (Commercial)
I am getting following error when I execute insert/update/delete query.
ERROR 168 (HY000): Cannot execute the statement. DBRM is read only.
I restarted infinidb many times but the same error appears.
please help to resolve this issue.
I recently had the same problem and here are three steps that I did:
/usr/local/mariadb/columnstore/bin/dbrmctl status
/usr/local/mariadb/columnstore/bin/dbrmctl readwrite
/usr/local/mariadb/columnstore/bin/dbrmctl reload
Answering this for other folks who face the same problem..
There are a couple of things you can try:
(1) Restart the service, using service infinidb restart
(2) If the error continues, use the calpont command console cc and do a startSystem
Watch the crit.log, error.log files under /var/log/Calpont/ for errors...

“Error 1067: The process terminated unexpectedly” when trying to start MySQL

I'm using Windows 7 and running XAMPP MySQL SVC service. I'm seeing the following error:
Windows could not start the Mysql service on Local Computer.
Error 1067: The process terminated unexpectedly.
What does this mean, and how can I fix it?
Examine error log (start eventvwr.msc). MySQL typically writes something to the Application log.
In very rare cases it does not write anything (I'm only aware of one particular bug http://bugs.mysql.com/bug.php?id=56821, where services did not work at all). There is also error log file, normally named .err in the data directory that has the same info as written to windows error log.
You need to:
stop the MySQL service:
Open mysql path\data
Remove both ib_logfile0 and ib_logfile1.
Restart the service
I had the same problem. I am using mysql 5.6.11.
To solve this problem I had to change my-default.ini file in mysql-5.6.11-win32 folder
So I just pasted the following lines under line [mysqld]
Options basedir and datadir need to be modified for mysql location.
I had the same problem but I was confused with #Vladislav's answer and couldn't seem to find the solution from that. Of course, my problem may not be exactly the same as I encountered the problem when trying to upgrade XAMPP, but it also gave the same Error 1067 message.
With further search I found this:
The answer from that is straightforward, that is, to completely clean up the folder, which doesn't always happen. As in regards to XAMPP, I guess I backed up the necessary files first (data folder from mysql folder and the htdocs folder). Uninstall XAMPP. Check the xampp folder for any content that remains and delete everything. You may want to reboot afterwards, just in case. Then reinstall XAMPP. Copy the backed-up folders back to their respective places, and hopefully, mySql will work again in XAMPP.
This should solve the issue.
Same problem here. After analysing log reports via eventvwr.msc I found, that logging files were placed in folder which requires admin rights to update, so files cannot be created and install and startup process could not proceed.
So checking eventlog was very usefull.
I get this problem from time to time, and when I do, I have been able to solve it by using a backup of the database folder(s) that give the problem.
When you check your 'Event Viewer > Windows Log > Application', if you see an error:
InnoDB: Attempted to open a previously opened tablespace. Previous tablespace [database]/[table] uses space ID: 59 at filepath: .\[database]\[table].ibd. Cannot open tablespace [different db]/[different table] which uses space ID: 59 at filepath: .\[different db]/[different table].ibd
Then what works for me, is delete the first mentioned [database] folder in your MySQL data directory, and copy the backup of that database folder to where it was previously.
Then start MySQL, and it starts again for me, without this 1067 error.
Don't forget to check
innodb_data_home_dir = <your_directory_location>
innodb_log_group_home_dir = <your_directory_location>
on my.ini files. Wrong set value for these two variable make mysql process terminated and produce error 1067. Also check eventvwr.msc and mysql_error.log for detail error.
I had practically the same problem. in the log file I found this:
110903 9:09:39 InnoDB: 1.1.4 started; log sequence number 1595675
110903 9:09:40 [ERROR] Fatal error: Can't open and lock privilege tables: Incorrect key file for table 'user'; try to repair it
Apparently the user table has been corrupted. I replaced it with another copy (user.frm ; user.MYD ; user.MYI in mysql\data\mysql)
and thats works for me.
ps: am using xampp.
Search and destroy (or move cautiously) any my.ini files (windows or program files), which is affecting the mysql service failure. also check port 3306 is used by using either netstat or portqry tool. this should help. Also if there is a file system issue you can run check disk.
I just went throught same issue and I solved it the following way.
1 - found the .err file which logs all mysql issues, in win7, located under programData\MySQL\MySQL Server 5.6\data\
2 - Check the last entries from the file and, in my case, I found the error was coming from a flag (audit-log) that I set to "true" from the workbench interface the day before!
3 - went into the my.ini file, and removed audit-log=ON.
4 - launched mysql service and it worked!!
I've got the same problem, and what worked for me is in THIS OTHER ANSWER.
I didn't replicated it here because it is NOT A CORRECT THING TO DO.
Basically is a re-install being sure to delete everything very well and using 32 bit versions.
I had the same error. I checked the error logs: C:\ProgramData\MySQL\MySQL Server 5.5\data\inf3rno-PC.err. According to them
170208 1:06:25 [Note] C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld: Shutdown complete
170208 1:10:44 [Note] Plugin 'FEDERATED' is disabled.
170208 1:10:44 InnoDB: The InnoDB memory heap is disabled
170208 1:10:44 InnoDB: Mutexes and rw_locks use Windows interlocked functions
170208 1:10:44 InnoDB: Compressed tables use zlib 1.2.3
170208 1:10:44 InnoDB: Error: unable to create temporary file; errno: 2
170208 1:10:44 [ERROR] Plugin 'InnoDB' init function returned error.
170208 1:10:44 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
170208 1:10:44 [ERROR] Unknown/unsupported storage engine: INNODB
170208 1:10:44 [ERROR] Aborting
I think the important part here
170208 1:10:44 InnoDB: Error: unable to create temporary file; errno: 2
I changed the TMP and TEMP env variables from C:\Windows\Temp to %USERPROFILE%\AppData\Local\Temp yesterday, because I was unable to compress a directory and according to many post the solution is that. Now compression works, but mysql and apparently nod32 complains that they cannot create temporary files...
I added tmpdir=c:/server/mytmp to C:\Program Files\MySQL\MySQL Server 5.5\my.ini. And after that started the service again with services.msc. It is okay now.
So this can be a possible cause as well. I strongly suggest to everybody encountering this problem to check the error logs.
I use install file to repair. it works for me
please check the space available on drive where the db is stored. in my case it was stopped the service due to less space on drive.
There are many solutions for the problem. This worked for me
Right click on Service -> Properties -> Log on as system account.