My company is a software vendor. We develop software that is later deployed on the customer's environment, on their own machines. Our software uses various DBMS, depending on what the customer has. We do it for PostgreSQL, MySQL and so on.

Currently we have two new customers, which are using Oracle DB in their own production environments. We are obliged, however, to provide an user acceptance environments, which are ought to be 1:1 to the customer's production environment.

Hence my question - do we need to buy an Oracle DB license for ourselves, provided we're never going to have a production environment with that product? In another words - since the customer has the Oracle DB license do we also need to buy one only for testing purposes?
['https://dba.stackexchange.com/questions/96880', 'https://dba.stackexchange.com', 'https://dba.stackexchange.com/users/1172/']
If you want to shrink ibdata1, so that it should only contain the metadata, You may try these steps

To shrink ibdata1 once and for all you must do the following:

1. MySQLDump all databases into a SQL text file (as bkp\_all\_db.sql)
2. Drop all databases (except mysql schema)
3. Stop MySQL
`/etc/init.d/mysql stop`
4. Add the following lines to /etc/my.cnf

```
[mysqld]
innodb_file_per_table
innodb_flush_method=O_DIRECT
innodb_log_file_size=1G
innodb_buffer_pool_size=4G

```
5. Now remove ibdata1, so that there should only be the mysql schema in /var/lib/mysql

rm -f /var/lib/mysql/ibdata1 /var/lib/mysql/ib\_logfile

6. Start MySQL instance, This will recreate ibdata1, ib\_logfile0 and ib\_logfile1 at 1G each

service mysqld start
7. Reload bkp\_all\_db.sql into mysql (import). ibdata1 will grow but only contain table metadata

<http://mysqlrockstar.blogspot.in/2014/07/mysql-ibdata1-file-shrink.html>
The config items you added in should have little to no impact on the situation. n.b. you will probably also want `log-slave-updates`, ([details](https://dev.mysql.com/doc/refman/5.6/en/replication-options-slave.html#option_mysqld_log-slave-updates)) but leave that out until after you've imported the data, of you'll have 100's of GB's of binary logs created.

I think the real question is whether your OS is happy with a single file that size, bearing in mind that it wont get smaller, but may get larger. 

If it's going to be an issue you may want to look at `innodb_file_per_table` ([details](https://dev.mysql.com/doc/refman/5.6/en/innodb-multiple-tablespaces.html)) which 'basically' splits the data between `ibdata1` and a file for each table. (This involves reloading the dumpfile to take affect) (this is on by default from MySQL 5.6.6)

There are pros and cons for both options.