<p>The source database is quite large. The target database doesn't grow automatically. They are on different machines.</p>

<p>I'm coming from a MS SQL Server, MySQL background and IDS11 seems overly complex (I am sure, with good reason).</p>

[{'answer_id': 51770, 'author': 'nso1', 'author_id': 3027, 'author_profile': 'https://Stackoverflow.com/users/3027', 'pm_score': 1, 'selected': False, 'text': "<p>have you used the export tool ?  There used to be a way if you first put the db's into quiescent mode and then you could actually copy the DBSpaces across (dbspaces tool I think... its been a few years now).</p>\n\n<p>Because with informix you used to be able to specify the DBSpaces(s) to used for the table (maybe even in the alter table ?).  </p>\n\n<p>Check - dbaccess tool - there is an export command.<br>\nPut the DB's into quiesent mode or shut down, copy the dbspaces and then attach table telling it to point to the new dbspaces file.  (the dbspaces tool could be worth while looking at.. I have manuals around here.  they are 9.2, but it shouldn't have changed too much).</p>\n"}, {'answer_id': 53219, 'author': 'Simon', 'author_id': 5385, 'author_profile': 'https://Stackoverflow.com/users/5385', 'pm_score': 2, 'selected': False, 'text': '<p>One way to move data from one server to another is to backup the database using the dbexport command.</p>\n\n<p>Then after copying the backup files to the destination server run the dbimport command.</p>\n\n<p>To create a new database you need to create the DBSpace for the new database using the onmonitor tool, at this point you could use the existing files from the other server.</p>\n\n<p>You will then need to create the database on the destination server using the dbaccess tool. The dbaccess tool has a database option that allows you to create a database. When creating the database you specify what DBSpace to use.</p>\n\n<p>The source database may be made up of many chunks which you will also need to copy and attach to the new database.</p>\n'}, {'answer_id': 80499, 'author': 'RET', 'author_id': 14750, 'author_profile': 'https://Stackoverflow.com/users/14750', 'pm_score': 2, 'selected': False, 'text': "<p>The easiest way is dbexport/dbimport, as others have mentioned.</p>\n\n<p>The fastest way is using onpload, the High Performance Loader. If you have lots of data, but not a ridiculous number of tables, this is definitely worth pursuing. There are some bits and pieces on the IIUG site that may be of assistance in scripting the HPL to generate all the config you'll need.</p>\n"}, {'answer_id': 165597, 'author': 'SKapsal', 'author_id': 24721, 'author_profile': 'https://Stackoverflow.com/users/24721', 'pm_score': 2, 'selected': False, 'text': '<p>You have a few choices.<br>\n<br>\ndbexport/dbimport<br>\nonunload/onload<br>\nHPL (high performance loader) options.  </p>\n\n<p>I have personally used onunload/onload and dbexport/dbimport.  I have not used HPL.  I\'m using IDS 10.\n<br><br>\n<strong>onunload/onload</strong> <a href="http://publib.boulder.ibm.com/infocenter/idshelp/v10/index.jsp?topic=/com.ibm.mig.doc/mig138.htm" rel="nofollow noreferrer">IBM docs</a><br>\n<li>Back up the raw database to disk or tape in page size chunks\n<li>faster (especially if you go to disk)\n<li>Issues if the the database servers are on different operating systems or hardware or if they just have different page sizes.\n<br><br>\n<strong>dbexport/dbimport</strong>  <a href="http://publib.boulder.ibm.com/infocenter/idshelp/v10/index.jsp?topic=/com.ibm.mig.doc/mig138.htm" rel="nofollow noreferrer">IBM docs</a><br>\n<li>backup the database in delimited ascii files\n<li>writes an ascii schema of the database including all users, tables, views, indexes, etc. Everything about the structure of the database into one huge plain text file.\n<li>separate plain text files for each table of the database as well\n<li>not so fast\n<li>issues on dbimport on any table that has bad data, any view with incorrect syntax, etc.  (This can be a good thing, an opportunity to identify and clean)\n<li><b><i>DO NOT LEAVE THIS TAPE ON THE FRONT SEAT OF YOUR CAR WHEN YOU RUN INTO THE STORE FOR AN ICE CREAM (or you\'ll be on the news).</b></i>  Also read ... Not a very secure way to be moving data around. :)\n<li><b><i>Limitation:</i></b> Requires exclusive access to the source database.</p>\n\n<p>Here is a good place to start in the docs --> <a href="http://publib.boulder.ibm.com/infocenter/idshelp/v10/index.jsp?topic=/com.ibm.mig.doc/mig138.htm" rel="nofollow noreferrer">Migration of Data Between Database Servers</a></p>\n'}, {'answer_id': 488064, 'author': 'calvinkrishy', 'author_id': 53949, 'author_profile': 'https://Stackoverflow.com/users/53949', 'pm_score': 1, 'selected': False, 'text': '<p>If both the machines use the same version of IDS then another option would be to use ontape to take a backup on one machine one machine and restore on another. You can use the STDIO option and then just stream the backup onto the other machine where the restore could just restore from the STDIO.</p>\n\n<p>From the "Data Replication for High Availability and Distribution" redbook:</p>\n\n<pre><code>ontape -s -L 0 -F | rsh secondary_server "ontape –p"\n</code></pre>\n\n<p>You could also create a passwordless ssh connection b/w the hosts and transfer in a more secure way.</p>\n'}]
['https://Stackoverflow.com/questions/51673', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/5374/']