question

Oh this is the status:

>systemctl status mysqld.service

mysqld.service - MySQL Community Server

Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled)

Active: activating (start-post) since Fri 2015-07-17 11:37:06 CDT; 2min 43s ago

Process: 10425 ExecStart=/usr/bin/mysqld_safe (code=exited, status=0/SUCCESS)

Process: 10415 ExecStartPre=/usr/bin/mysql-systemd-start pre (code=exited, status=0/SUCCESS)

Main PID: 10425 (code=exited, status=0/SUCCESS); : 10426 (mysql-systemd-s)

CGroup: /system.slice/mysqld.service

└─control

├─10426 /bin/bash /usr/bin/mysql-systemd-start post

└─11165 sleep 1

Jul 17 11:37:06 MySQL.etmp.local systemd[1]: mysqld.service holdoff time over, scheduling restart.

Jul 17 11:37:06 MySQL.etmp.local systemd[1]: Stopping MySQL Community Server...

Jul 17 11:37:06 MySQL.etmp.local systemd[1]: Starting MySQL Community Server...

Jul 17 11:37:06 MySQL.etmp.local mysqld_safe[10425]: 150717 11:37:06 mysqld_safe Logging to '/var/log/mysqld.log'.

Jul 17 11:37:06 MySQL.etmp.local mysqld_safe[10425]: 150717 11:37:06 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql

Jul 17 11:37:08 MySQL.etmp.local mysqld_safe[10425]: 150717 11:37:08 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

@mbarfield

I have tried several versions of MySQL now and I'm running into various errors when the daemon starts up. This is the one for the latest version of MySQL for the Oracle 7 Linux OS.

150717 11:27:06 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 2015-07-17 11:27:06 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation fo r more details). 2015-07-17 11:27:06 8276 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 50000) 2015-07-17 11:27:06 8276 [Warning] Buffered warning: Changed limits: max_connections: 214 (requested 10000) 2015-07-17 11:27:06 8276 [Warning] Buffered warning: Changed limits: table_cache: 400 (requested 2000) 2015-07-17 11:27:06 8276 [Note] Plugin 'FEDERATED' is disabled. 2015-07-17 11:27:06 8276 [Note] InnoDB: Using atomics to ref count buffer pool pages 2015-07-17 11:27:06 8276 [Note] InnoDB: The InnoDB memory heap is disabled 2015-07-17 11:27:06 8276 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2015-07-17 11:27:06 8276 [Note] InnoDB: Memory barrier is not used 2015-07-17 11:27:06 8276 [Note] InnoDB: Compressed tables use zlib 1.2.3 2015-07-17 11:27:06 8276 [Note] InnoDB: Using Linux native AIO 2015-07-17 11:27:06 8276 [Note] InnoDB: Not using CPU crc32 instructions 2015-07-17 11:27:06 8276 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2015-07-17 11:27:06 8276 [Note] InnoDB: Completed initialization of buffer pool 2015-07-17 11:27:06 8276 [Note] InnoDB: Highest supported file format is Barracuda. 2015-07-17 11:27:06 8276 [Note] InnoDB: 128 rollback segment(s) are active. 2015-07-17 11:27:06 8276 [Note] InnoDB: Waiting for purge to start 2015-07-17 11:27:07 8276 [Note] InnoDB: 5.6.23 started; log sequence number 1626097 2015-07-17 11:27:07 8276 [ERROR] /usr/sbin/mysqld: unknown variable 'default_character_set=utf8' 2015-07-17 11:27:07 8276 [ERROR] Aborting

Maybe other people have but I haven't seen it. Here is an idea that may be worthwhile trying...

Have you tried any of the SQL conversion tools available online? Some are free and others are paid versions but that is the first place I would start. I found this free version but I can't guarantee that it will create the build script 100% correctly. I did enter the MySQL schema into the interface and it produced an Oracle script. You may need to handcraft some of the commands for it to work with Oracle (maybe not). That's where the Oracle DBA can help fix any minor changes. I personally don't have an Oracle DB to test this but I think the conversion tool is worth a try.

Once you have the DB and schema built out then update the test report connection info under preferences and you should be good if you can connect to the DB.

Be cautious about letting the data grow out-of-bounds. With MySQL we have an aging script that purges old data over time. Eventually you will generate so much data that it will slow the DB down or fill up the HDD.