Issue in production server.

Posted in 2017

Summary

After migrating a live IDS 12.10.FC8 database to a new server via dbexport/dbimport, the poster saw lock timeout errors, degraded performance, and smart-large-object errors ('bad smart-large-object address'/'unique ID does not match'). Suggestions: run/verify update statistics (AUS scheduling doesn't guarantee it ran), check table lock levels in systables and ALTER tables to row-level locking, test SLOBs with LOTOFILE, run oncheck, verify dbexport -ss plus the separate blob data and matching sbspace/ONCONFIG setup, or redo the move with an ontape backup/restore. No confirmation of a fix is recorded.

Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.

Topics: Performance & Tuning, Installation, Setup & Upgrades, Error Codes & Troubleshooting, Connectivity: ODBC / JDBC / .NET, Migration, Import/Export & Data Conversion, Java & JDBC Development

MUKESH TANUKU — Tue, 19 Sep 2017 11:40:05 — source: IIUG Forums & Mailing Lists

Hi Floks, Yesterday night I have done a activity that, Moving Live production server to New server. All the config parameters are set properly as like existing one and installed same version of informix IDS 12.10 FC8. Using DBEXPORT and DBIMPORT we have moved the data. Now the database is UP and RUNNING. Today we are facing an issue from application which is connected to the New database server and also Performance got downgraded. Please find the application server log below: NEURA_BIACH [19 Sep 2017 10:40:09: ERROR : org.hibernate.util.JDBCExceptionReporter.logExceptions(JDBCExceptionReporter.jav a:78)] : Could not position within a table (neura_biahmis_prod_live.number_ranges_tbl). NEURA_BIACH [19 Sep 2017 10:40:09: ERROR : org.hibernate.util.JDBCExceptionReporter.logExceptions(JDBCExceptionReporter.jav a:78)] : ISAM error: Lock Timeout Expired NEURA_BIACH [19 Sep 2017 10:40:09: ERROR : org.hibernate.util.JDBCExceptionReporter.logExceptions(JDBCExceptionReporter.jav a:78)] : Could not position within a table (neura_biahmis_prod_live.number_ranges_tbl). NEURA_BIACH [19 Sep 2017 10:40:09: ERROR : org.hibernate.util.JDBCExceptionReporter.logExceptions(JDBCExceptionReporter.jav a:78)] : ISAM error: Lock Timeout Expired NEURA_BIACH [19 Sep 2017 10:46:14: ERROR : org.hibernate.util.JDBCExceptionReporter.logExceptions(JDBCExceptionReporter.jav a:78)] : Smart-large-object error. NEURA_BIACH [19 Sep 2017 10:46:14: ERROR : org.hibernate.util.JDBCExceptionReporter.logExceptions(JDBCExceptionReporter.jav a:78)] : Smart Large Objects: open: Bad smart-large-object address. Object might have been deleted. NEURA_BIACH [19 Sep 2017 10:46:14: ERROR : com.cgsl.neura.clinical.LabInterFaceDAO.searchResultAuth(LabInterFaceDAO.java:14 88)] : org.hibernate.exception.GenericJDBCException: could not execute query NEURA_BIACH [19 Sep 2017 10:49:17: ERROR : org.hibernate.util.JDBCExceptionReporter.logExceptions(JDBCExceptionReporter.jav a:78)] : Smart-large-object error. NEURA_BIACH [19 Sep 2017 10:49:17: ERROR : org.hibernate.util.JDBCExceptionReporter.logExceptions(JDBCExceptionReporter.jav a:78)] : Smart Large Objects: unique ID does not match. Smart large object probably deleted.

↪ replying to MUKESH TANUKU

Fernando Nunes — Tue, 19 Sep 2017 12:03:29 — source: IIUG Forums & Mailing Lists

From a quick review of the error messages, sounds like you didn't run the update statistics and eventually that you only moved the data, but not thebinary large objects (BLOB). Regards. On Tue, Sep 19, 2017 at 12:40 PM, MUKESH TANUKU <mukeshbt1328@gmail.com> wrote: > Hi Floks, > > Yesterday night I have done a activity that, Moving Live production server > to > New server. > All the config parameters are set properly as like existing one and > installed > same version of informix IDS 12.10 FC8. > > Using DBEXPORT and DBIMPORT we have moved the data. Now the database is UP > and > RUNNING. > > Today we are facing an issue from application which is connected to the New > database server and also Performance got downgraded. > > Please find the application server log below: > > NEURA_BIACH [19 Sep 2017 10:40:09: ERROR : > org.hibernate.util.JDBCExceptionReporter.logExceptions( > JDBCExceptionReporter.java:78)] > : Could not position within a table > (neura_biahmis_prod_live.number_ranges_tbl). > NEURA_BIACH [19 Sep 2017 10:40:09: ERROR : > org.hibernate.util.JDBCExceptionReporter.logExceptions( > JDBCExceptionReporter.java:78)] > : ISAM error: Lock Timeout Expired > NEURA_BIACH [19 Sep 2017 10:40:09: ERROR : > org.hibernate.util.JDBCExceptionReporter.logExceptions( > JDBCExceptionReporter.java:78)] > : Could not position within a table > (neura_biahmis_prod_live.number_ranges_tbl). > NEURA_BIACH [19 Sep 2017 10:40:09: ERROR : > org.hibernate.util.JDBCExceptionReporter.logExceptions( > JDBCExceptionReporter.java:78)] > : ISAM error: Lock Timeout Expired > > NEURA_BIACH [19 Sep 2017 10:46:14: ERROR : > org.hibernate.util.JDBCExceptionReporter.logExceptions( > JDBCExceptionReporter.java:78)] > : Smart-large-object error. > NEURA_BIACH [19 Sep 2017 10:46:14: ERROR : > org.hibernate.util.JDBCExceptionReporter.logExceptions( > JDBCExceptionReporter.java:78)] > : Smart Large Objects: open: Bad smart-large-object address. Object might > have > been deleted. > NEURA_BIACH [19 Sep 2017 10:46:14: ERROR : > com.cgsl.neura.clinical.LabInterFaceDAO.searchResultAuth( > LabInterFaceDAO.java:1488)] > : org.hibernate.exception.GenericJDBCException: could not execute query > NEURA_BIACH [19 Sep 2017 10:49:17: ERROR : > org.hibernate.util.JDBCExceptionReporter.logExceptions( > JDBCExceptionReporter.java:78)] > : Smart-large-object error. > NEURA_BIACH [19 Sep 2017 10:49:17: ERROR : > org.hibernate.util.JDBCExceptionReporter.logExceptions( > JDBCExceptionReporter.java:78)] > : Smart Large Objects: unique ID does not match. Smart large object > probably > deleted. > > > ************************************************************ > ******************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > -- Fernando Nunes Portugal http://informix-technology.blogspot.com My email works... but I don't check it frequently...

↪ replying to Fernando Nunes

MUKESH TANUKU — Tue, 19 Sep 2017 12:06:21 — source: IIUG Forums & Mailing Lists

Update Statistics are automatically scheduled by Open Admin Tool. I have moved the data using DBEXPORT form Old server to DBIMPORT to new server, how can i miss BLOB's and CLOB's.

↪ replying to MUKESH TANUKU

MUKESH TANUKU — Tue, 19 Sep 2017 13:31:18 — source: IIUG Forums & Mailing Lists

Can anyone please help on this

↪ replying to MUKESH TANUKU

Fernando Nunes — Tue, 19 Sep 2017 14:05:41 — source: IIUG Forums & Mailing Lists

The fact that they're scheduled don't necessary mean they were already executed, specially because AUS contains two functions: One that evaluates what needs to be done and another that does. But besides that check the LOCK_LEVEL of your tables (SELECT tabname, locklevel FROM systables WHERE tabid > 99 AND tabtype = 'T'). If it's not "R" then do an ALTER TABLE for each one to set the lock mode to row. Regarding the SLOB error... try to use the LOTOFILE function on a table/record you know that has a smart blob... Regards. On Tue, Sep 19, 2017 at 1:06 PM, MUKESH TANUKU <mukeshbt1328@gmail.com> wrote: > Update Statistics are automatically scheduled by Open Admin Tool.> > I have moved the data using DBEXPORT form Old server to DBIMPORT to new > server, how can i miss BLOB's and CLOB's. > > > ************************************************************ > ******************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > -- Fernando Nunes Portugal http://informix-technology.blogspot.com My email works... but I don't check it frequently...

↪ replying to MUKESH TANUKU

Kern Doe — Tue, 19 Sep 2017 14:41:34 — source: IIUG Forums & Mailing Lists

Redo the migration but differently.Since the version of IDS is the same (hopefully your OS is also the same?) then use ontape to back up and restore this ontape on the new server. You can even restore w/o backing up to save time transferring the backup file. Let's go GreenThis email contains 100% recycled electrons. From: MUKESH TANUKU <mukeshbt1328@gmail.com> To: ids@iiug.org Sent: Tuesday, September 19, 2017 9:31 AM Subject: Re: Issue in production server. [39922] Can anyone please help on this ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

↪ replying to MUKESH TANUKU

Kern Doe — Tue, 19 Sep 2017 14:42:27 — source: IIUG Forums & Mailing Lists

Or you can run oncheck against the entire instance to see where the errors may be... Let's go GreenThis email contains 100% recycled electrons. From: MUKESH TANUKU <mukeshbt1328@gmail.com> To: ids@iiug.org Sent: Tuesday, September 19, 2017 9:31 AM Subject: Re: Issue in production server. [39922] Can anyone please help on this ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

↪ replying to MUKESH TANUKU

Marcus Haarmann — Wed, 20 Sep 2017 19:29:12 — source: IIUG Forums & Mailing Lists

Hi, I assume you either did not do a "dbexport -ss " or you did not copy the blob data to the destination server (this is stored in a separate file). Are you sure the dbspaces are correctly set up on the new machine and the declaration of the blob/clob columns (the put clause) did reach the correct dbspace ? What about the SBLOB parameters in onconfig ? Are these identical ? Marcus Haarmann Von: "MUKESH TANUKU" <mukeshbt1328@gmail.com> An: "ids" <ids@iiug.org> Gesendet: Dienstag, 19. September 2017 15:31:19 Betreff: Re: Issue in production server. [39922] Can anyone please help on this ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

Issue in production server.

Glossary

Your privacy choices