You should have shell access to the server to make this easier.Īnother option is to install Informix on newer hardware. If you only have access via ODBC this will be a very long, tedious, and likely to be incomplete task. Once you have the data dumped and the tables created in your new database, you can import them using the tools for the database of your choice. Use DBSCHEMA to get the table structure to DDL and run that on your other database. You will need to create the table on the second database. You could use this (once for each table in the database), but it's probably going to be cumbersome. There are mailing lists available (which require you to belong, but membership is free) for discussing Informix in detail.Informix has an UNLOAD utility that will dump records to a flat file. There are other possible loading solutions, such as HPL (High-Performance Loader).įor more information about Informix, either use the various web sites already referenced ( is a link to the Informix section of IBM's web site), or use the International Informix User Group (IIUG) web site. There are other possible solutions - C-ISAM datablade being one such - but they are more expensive and probably not warranted. Certainly, that is the simplest way to do it. To get the data from SE to IDS, you will probably want to use DB-Export at the SE end and DB-Import at the Linux/IDS end. idx files are associated with IDS it is just extremely unlikely.įrom the information available, it sounds as though your production server is running SE. SE is rather different from (and much simpler than) Informix Dynamic Server (IDS). idx files are associated with Informix Standard Engine, aka Informix SE. idx files are associated with C-ISAM, or, when organized in a directory called dbase.dbs (where dbase is the name of your database), the. There's a lot that has been left out but I hope that this gives you the info that you need to move forward with your task. That can be found by executing onstat -c | grep ROOTDBS This means that the ROOTDBS needs to be the same in both instances. Option 2 simply requires that the paths for the data files are the same on both servers. BTW, the numbers listed in onstat -d are in pages, I believe that Linux is a 2K page. Use onstat -d on the production instance to find this out. Option 1 requires that you know what the dbspaces are named and how large they are. Restore it over your development instance. Use ontape or onbar to backup the entire production instance and.To copy the database from production to development. Create the dbspaces that you need in the new instance and use onunload and onload.idx files are known to the database by the logical dbspace name.Īrmed with this background info and assuming that the production and development servers are running the same OS and that your hardware is relatively the same, not a combination of PARISC, Itanium or x86/圆4, I'll throw a couple of options out for you. The dbspaces and files were created to contain your databases data but they technically belong to the instance. idx files do not belong to a database but belong the instance. Given this knowledge you now know that the. Most DBA's know better than to do that but it's something to be aware of. This means that more than one database can store data in any given dbspace. Informix is architected as a shared everything database engine, meaning all resources available to the instance are available to every database in that instance. You've asked a pretty complicated question without realizing it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |