Problem of date on Informix 4GL

I have a problem for a basic imporation of data. I would like to know if there are problems of incomptibility between Informix 7.3 and Informix 7.2 with regard to the DBEXPORT and DBIMPORT. I do not manage to import a data base of IDS 7.2 towards 7.3. error: 1205 - Invalid month in date THANK YOU Cyrille I translated my message with ALTAVISTA, I am bad in English

Just make sure DBDATE is set to the same value on both machines. HTH Michael Cyrille de LAMBERT wrote: > I have a problem for a basic imporation of data. I would like to know if > there are problems of incomptibility between Informix 7.3 and Informix 7.2 > with regard to the DBEXPORT and DBIMPORT. I do not manage to import a data > base of IDS 7.2 towards 7.3. error: > 1205 - Invalid month in date > THANK YOU > > Cyrille > > I translated my message with ALTAVISTA, I am bad in English

Hello Still me. The problem that I have locate at the level of the format of date in the file which I must import, the dates are under a French format whereas the dates of my IDS are with the Americain format. How to configure IDS in order to have the French format? (file of configuration or command) US Format MM/DD/YYYY French Format DD/MM/YY Thank you still Cyrille I translated my message with ALTAVISTA, I am bad in English

Consultants - FREE Zero Impact Sql & Service Level Monitor ========================================================== The database and service level monitor with ZERO impact wins! Consultants build your SQL performance, tuning and service level consulting practices with the Zero Impact Sql and Service Level Monitoring products. Sql Power Tools will give Consultants a free copy of the industry breakthrough Zero Impact Sql Monitor and Zero Impact Service Level Monitor products! Excellent for monitoring with ZERO impact - database servers having 50 to 1000+ users and processing 50 to 1000+ SQL transactions per second. You may install the products on a laptop (takes a few minutes) and build your SQL performance, tuning and service level consulting practices. Once installed on a laptop, simply plug the laptop into a client's network and you will be IMMEDIATELY capturing and monitoring: 1. All or any subset of the SQL statements (with their performance) sent to the database server 24x7 with the Zero Impact Sql Monitor. Plus filter or reconstruct the SQL statements from any prior time period. Real-time alerts pinpoint poor performing production SQL. 2. Average end user response time, average database server response time, average network send and receive time plus other important Service Level metrics by monitoring interval with the Zero Impact Service Level Monitor. Product allows detection of trending poor database performance prior to end-users contacting the Help Desk, DBAs or Administrators. Real-time alerts pinpoint monitoring intervals with poor database server or end user performance. Refer to the following section 'IV. What can you do with the product line?'. I. Product overview: =================== The products scale to thousands of users and 1000+ transactions per second with no impact upon the database server, network or end users. Perfect for production, OLTP, WWW, eCommerce, 3-Tier, DSS, test, and SQL development database monitoring. Product line requires no connection to the database server, nor are agents installed on the server or client workstations. No software is installed upon the customer's server, network or client workstations. Requires no installation of performance impacting database monitors, probes, traces or database audits. Requires no intrusive middleware, gateways or proxy servers that impact the performance of end user SQL transactions. Product installation on a laptop is a three step process that takes a few minutes. Product GUI is intuitive and a snap to learn (no customer has required a class on product usage todate!) We will give you complete product support at no charge. II. How the product works: ========================= The product line non-intrusively analyzes the SQL network packet flow to the database server for end-user SQL and service level performance monitoring. In the SQL network packets are the SQL statements, results, error messages, show plans, I/O statistics and more. SQL statement performance is obtained from real-time network packet time stamps provided by the network adapter. Install the product on your laptop (takes a few minutes), then plug the laptop into a client's network (client does NOT need to assign you an IP address) and you will be IMMEDIATELY capturing and monitoring database server performance. The laptop needs to be connected to the network on the same subnet or switch as the database server. Then our product can non-intrusively view and analyze the SQL packet flow to the database server. Product is available for 95, 98, NT, AIX, HP-UX and Solaris laptops. From any laptop a database server on any other platform type can be monitored (e.g. Linux, SCO Unix, Sequent, DEC, etc.). III. Competitive monitoring approaches: ====================================== Other industry database monitoring approaches are less than satisfactory due to the following issues: 1. They do NOT capture or monitor 24x7 what causes 80% of all database server production performance problems (end-user SQL transactions). They monitor high level resources, the cause of about 20% of all database performance problems. 2. They do NOT monitor end-user or database server response time (service levels) at the SQL statement level for predictive identification of pending performance problems. (e.g. poor database performance caused by disk space fragmentation, skewed distribution statistics, outdated distribution statistics, increased transaction loads, poor performing SQL statements, blocked SQL transactions as well as other performance issues) 3. They are intrusive, difficult/expensive to install and setup, have a high cost of operation and are usually quite expensive. 4. They are so intrusive they may not be used 24x7 in production environments. i.e. they may only be used in development and test environments, not in production where SQL performance plus end user service level measurement is critical to success. 5. Other database monitors may not scale well when additional users are added or transaction processing requirements increase. 6. Other database monitors that do not measure Service Levels such as end-user response time, database server response time, network time and other metrics which allows DBAs, Administrators and Help Desks to proactively detect and resolve database performance issues prior to end user complaints. The real business payoff with database monitoring products is obtained when monitoring occurs at the end-user SQL transaction level, not when monitoring high level system resources (NT and UNIX allow availability, cpu utilization, I/O, memory, etc. to be easily monitored). Then the cause of production database server performance problems can be immediately pinpointed to specific SQL transactions. Plus service level monitoring proactively alerts DBAs, Administrators and Help Desks trending performance issues. IV. What can you do with the product line? ========================================= Build your SQL performance, tuning and database service level consulting practices. Assist your clients in pinpointing and resolving problematic SQL performance in production environments (a great service to your client and generates significant consulting revenues). Assist your clients is setting up 24x7 service level management programs for DBAs, Administrators and Help Desks. You may save your client an expensive hardware upgrade! From your laptop use the Zero Impact Sql Monitor and Zero Impact Service Level Monitor products to: 1. SQL capture (all or any subset) and performance monitoring in real-time or with offline SQL statement filtering. SQL statements can be pinpointed by end user response time, database server response time, network time, rows returned, login id, application group, host group, database, server, client IP address, pid, errors, and key words in SQL statement text. 2. SQL can be reconstructed by time periods by: end user response time, database server response time, network time, rows returned, login id, applic

Cyrille de LAMBERT wrote: > > Hello > Still me. The problem that I have locate at the level of the format of date > in the file which I must import, the dates are under a French format whereas > the dates of my IDS are with the Americain format. How to configure IDS in > order to have the French format? (file of configuration or command) > > US Format MM/DD/YYYY > French Format DD/MM/YY DBDATE=DMY2/export DBDATE Consider changing your date output format to use four digit years. Art S. Kagel