I am getting the following error message whilest working in Accpac Database Error (operation=SELECT, error=35455) [IBM][CLI Driver SQL30081N A ommunication error has been detected. I am using Accpac 5.3B on Windows2000 clients,IBM DB2 ver and Redhat Linux enterprise edition ver 3.0
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
IBM DB2 Database error 35455
- Thread starter Microiz
- Start date
jayconverse
MIS
What exactly are you doing in Accpac?
Is the error consistent?
Have you done the standard database tuning changes?
Jay Converse
IT Director
Systemlink, Inc.
Is the error consistent?
Have you done the standard database tuning changes?
Jay Converse
IT Director
Systemlink, Inc.
- Thread starter
- #3
This error pops up on every PC on the network in any module at the same time nomatter what the user is doing.
It is not consistant and does not happen all the time. I have done some database tuning but I would be very greatfull if you can post me your suggestions.
Eric Pika
Microbiz Technologies
It is not consistant and does not happen all the time. I have done some database tuning but I would be very greatfull if you can post me your suggestions.
Eric Pika
Microbiz Technologies
jayconverse
MIS
I just know the standard stuff:
1. Ensure that there are no network bottlenecks. For example, replace all network hubs with network switches. Use at least 100 Megabit switches.
2. Ensure that DB2 is at least at fix pack 7 (db2cmd -> db2level)
3. Backup existing DBM and database specific configuration settings by issuing the following db2 commands:
* db2 get dbm cfg > dbmcfg.txt
* db2 connect to myACCPACDB
* db2 get database cfg > dbcfg.txt
Re-run DB2 configuration Wizard and accept all recommended settings, unless otherwise advised by SAGE Customer Support. After which, re-issue the above commands and save them to different files for reference:
* db2 get dbm cfg > dbmcfg_new.txt
* db2 connect to myACCPACDB
* db2 get database cfg > dbcfg_new.txt
4. Test your db2 database connections by issuing the following command:
* db2 connect to myACCPACDB
Database connections to DB2 should be very quick. Otherwise, the DB2 buffer pool size is in question. Reference the buffer pool size configuration KB article: 12811 for more detail on this topic.
Article 12811 says:
This kind of behavior can be attributed to a number of performance issues. One notorious disconfigured
DB2 database parameter is the buffer pool size. If this parameter is not configured properly,
DB2 performance would suffer.
By default (if the configuration advisor had never been run), DB2 assigns 250 pages of 4KB per
page as the buffer pool size on a Microsoft Windows system while it will assign 1,000 - 4 KB
pages - on an Unix or Linux system.
If a database were to be moved from one server to another server, the buffer pool size configuration
is brought forward to the new server. Therefore, it is essential to run the configuration advisor
again after restoring a database, or after server hardware changes.
For performance reasons, the more memory assigned to the buffer pool the better. For a dedicated
DB2 server, assign at least half of system memory to the buffer pool.
When there is a performance issue, it is likely that the buffer pool size is configured too
small or too large. When buffer pool size is too large, DB2 will cause the operating system
to swap to disk. DB2 will not allow any connection to the database to complete unless the specified
memory size had been obtained from the operating system. The amount of memory taken by the process
db2syscs.exe correlate to the the buffer pool size.
Issue the following command to alter the database's buffer pool size:
Start | Run | DB2CMD
C:\>DB2 Connect to myACCPACDB
C:\>DB2 ALTER BufferPool ibmdefaultbp size x
where x is the number of 4KB pages to be assigned to the database.
For example, if the operating system has 2 GB of memory and we were to assign 50% of that to
the database's buffer pool, the number x can be calculated as such x ~ 1,000,000 KB / 4KB =
250,000 Pages. Our DB2 command would like something like this:
C:\>DB2 ALTER BufferPool ibmdefaultbp size 250000
where ibmdefaultbp is the default buffer pool name. There are other ways to configure DB2 buffer
pools such as assigning a buffer pool to each table space, or a temporary table space. For more
detail, following the link to the article Basic DB2 UDB Performance Tuning, Part 3 (
Jay Converse
IT Director
Systemlink, Inc.
1. Ensure that there are no network bottlenecks. For example, replace all network hubs with network switches. Use at least 100 Megabit switches.
2. Ensure that DB2 is at least at fix pack 7 (db2cmd -> db2level)
3. Backup existing DBM and database specific configuration settings by issuing the following db2 commands:
* db2 get dbm cfg > dbmcfg.txt
* db2 connect to myACCPACDB
* db2 get database cfg > dbcfg.txt
Re-run DB2 configuration Wizard and accept all recommended settings, unless otherwise advised by SAGE Customer Support. After which, re-issue the above commands and save them to different files for reference:
* db2 get dbm cfg > dbmcfg_new.txt
* db2 connect to myACCPACDB
* db2 get database cfg > dbcfg_new.txt
4. Test your db2 database connections by issuing the following command:
* db2 connect to myACCPACDB
Database connections to DB2 should be very quick. Otherwise, the DB2 buffer pool size is in question. Reference the buffer pool size configuration KB article: 12811 for more detail on this topic.
Article 12811 says:
This kind of behavior can be attributed to a number of performance issues. One notorious disconfigured
DB2 database parameter is the buffer pool size. If this parameter is not configured properly,
DB2 performance would suffer.
By default (if the configuration advisor had never been run), DB2 assigns 250 pages of 4KB per
page as the buffer pool size on a Microsoft Windows system while it will assign 1,000 - 4 KB
pages - on an Unix or Linux system.
If a database were to be moved from one server to another server, the buffer pool size configuration
is brought forward to the new server. Therefore, it is essential to run the configuration advisor
again after restoring a database, or after server hardware changes.
For performance reasons, the more memory assigned to the buffer pool the better. For a dedicated
DB2 server, assign at least half of system memory to the buffer pool.
When there is a performance issue, it is likely that the buffer pool size is configured too
small or too large. When buffer pool size is too large, DB2 will cause the operating system
to swap to disk. DB2 will not allow any connection to the database to complete unless the specified
memory size had been obtained from the operating system. The amount of memory taken by the process
db2syscs.exe correlate to the the buffer pool size.
Issue the following command to alter the database's buffer pool size:
Start | Run | DB2CMD
C:\>DB2 Connect to myACCPACDB
C:\>DB2 ALTER BufferPool ibmdefaultbp size x
where x is the number of 4KB pages to be assigned to the database.
For example, if the operating system has 2 GB of memory and we were to assign 50% of that to
the database's buffer pool, the number x can be calculated as such x ~ 1,000,000 KB / 4KB =
250,000 Pages. Our DB2 command would like something like this:
C:\>DB2 ALTER BufferPool ibmdefaultbp size 250000
where ibmdefaultbp is the default buffer pool name. There are other ways to configure DB2 buffer
pools such as assigning a buffer pool to each table space, or a temporary table space. For more
detail, following the link to the article Basic DB2 UDB Performance Tuning, Part 3 (
Jay Converse
IT Director
Systemlink, Inc.
- Status
Similar threads
- Locked
- Question
- Locked
- Question